That's what the TryExec= key is for, which evince has. I'm still not convinced it is an error, but if people want to do the work to the packages instead then that is fine.
You would do this: 1) Find .desktop file in package 'a' 2) Look for TryExec or Exec in that package 3) If not there, go and look in Contents 4) Check those packages for a Depends relationship on 'a', set that as the package for the component. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1553156 Title: evince not listed Status in appstream-glib package in Ubuntu: New Status in evince package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Triaged Bug description: Using current xenial, evince is not listed in gnome-software. The log states it's of unknow application type ... could it come from the fact that the .desktop is in the -common binary? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1553156/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
