Hi James On 2015-06-10 11:10, James Cowgill <[email protected]> wrote:
This bug has been reported a few times upstream. … The argument against changing it was that easytag can infact handle the inode/directory MIME type properly so it should be allowed to have it in it's MimeTypes list.On balance (due to the issues it causes) I would probably lean towards removing it, which I see has already been done in git.
The MIME type is still present in the desktop file (and in the Nautilus extension for the master branch) in git.
David?
It is not really a problem of EasyTAG that installing a desktop file, with a valid list of accepted MIME types, causes a different part of the system to adjust its associations. There is no defined way to adjust MIME type associations across all desktop environments, and each environment handles this differently. Modern GNOME versions simply ignore the inode/directory MIME association on anything that is not Nautilus.
In this specific case, if gnome-open (an old GNOME2 component) fails and xdg-open succeeds, it simply means that each has a different way of handling a newly-installed desktop file with a MimeType key. If you want to work around the bugs (or unexpected behaviours) in each desktop environment by removing the inode/directory MIME type, that is something that is best done downstream. The root cause of the issue either needs fixing with a freedesktop.org specification for MIME type associations and desktop-specific (as well as desktop-neutral) defaults, or for the current specifications to be updated to do something similar.
As far as I know, this problem is not specific to the inode/directory MIME type, so I do not see why it should be singled out as a problematic case.
-- http://amigadave.com/
signature.asc
Description: Digital signature
