When creating a node view with both translatable and non translatable fields, the view filter on language adds a join condition on the langcode of all fields (even those that have not been translated). This causes no results to be found in the languages that are other than the default language the non translated field were saved in.
For the same reason sorting does not work on untranslated fields. Things are sorted as expected in on language, but not in another.
Before applying the join to langcode on the fields, check whether the field is translatable.
User interface changes
None, I guess.
Original report by @vitalie