Good day.

I just now opened an arch-linux bug, saying that the new Thunar 1.6.0 "broke" my PDF viewing:

https://bugs.archlinux.org/task/32974

As this says, I'm not really sure where this issue belongs but it seems that the Thunar people will be the ones able to answer whether or not the change in behaviour is intentional at least. Cut and paste from the above link: 

===
After auto-upgrading to the newest thunar (1.6.0), PDF viewing broke for me. I use "evince" as my PDF viewer, which thunar would all of a sudden not use anymore (nor add to its list of "recommended applications" in the file-context menu for PDF files).

The issue is caused by the datum "NoDisplay=true" in

/usr/share/applications/evince.desktop

and commenting out that line fixes it -- but I'm not sure if this is to be considered a Thunar, Evince or Arch Linux problem, since I'm not all that sure what the idea is of NoDisplay=true. Up to now it seems to have only been relevant in a global desktop-menu context, but has with the new Thunar apparently become relevant in its file-context as well.

When searching for the issue it I hit upon this:

https://bugs.archlinux.org/task/4775?opened=1214&status[0]=

which says that the "NoDisplay=true" was at least back then intentional for evince.

Given that Thunar did not use to pay attention to NoDisplay in file-context, it could be a simple Thunar problem. If it is however intentional, then I guess it might be evince specifically or Arch Linux globally since "NoDisplay" seems more of a distribution choice then an application's choice. I believe it's ultimately handled by mime-type stuff (through update-desktop-database) which to me muddies up even further where this issue belongs.

Could someone with the oversight transport it to the right channel? (although I guess I'll also open a report on the XFCE bugzilla)
===

Many thanks in advance for the attention.

Regards,
Rene