Bug#788325: easytag: Don't register as default handler for directories
On 06/19/2015 09:38 PM, James Cowgill wrote: I think you could reorder the easytag entries in /etc/mailcap by doing some stuff with update-mime. i have added a fix in the master branch to use low-priorities mimetype associations in /etc/mailcap. However it won't fix this problem because desktop environments (including xdg-open and gnome-open) don't read /etc/mailcap, they read the mimeapps.list files. I can't see any way to set priorities for those (only user and desktop environment overrides). http://standards.freedesktop.org/mime-apps-spec/mime-apps-spec-1.0.1.html DoH!! [1] is quite explicit: there are no priorities... anyhow, your answer gave me two clues: - the good thing about that is, that i can now easily fix the problem for me, by adding the following to ~/.local/share/applications/mimeapps.list: [Removed Associations] inode/directory=easytag.desktop; - the bad thing is that this is on a per-user basis, and cannot be handled by the package. most likely the proper way would be to ensure that easytag does not appear in the [Default Applications] section (and that at least one proper filebrowser does appear in this section). but it also seems that Debian does not really maintain a mimeapps.list, which makes it rather hard to use :-( fgmadsr IOhannes [1] https://wiki.debian.org/MIME#Application_association signature.asc Description: OpenPGP digital signature
Bug#788325: easytag: Don't register as default handler for directories
On Fri, 2015-06-19 at 20:51 +0200, IOhannes m zmölnig (Debian/GNU) wrote: installing the easytag package adds an entry to my /etc/mailcap file, that registers easytag as a program to display non-text [directories] at the local site (from mailcap(5), with a clarification by me in brackets). now i think that this is the main problem: easytag's desktop files declares that it *can* handle directories. (i guess the use case is that in your favourite filesystem browser you ought to be able to right-click on a directory and be presented with a list of applications that could handle that directory; having easytag in that list makes total sense to me). however, this declaration somehow makes the package installation process believe that it *should* handle directories (which is plain wrong), by adding an entry to /etc/mailcap. most likely the problem is with the packaging (not necessarily the easytag package per se, but maybe the tools used). according to update-mime(8), it *is* possible to add priorities to mime-types (for exactly the kind of problem we are facing). right now, easytag does not do anything special to register the mime-type handler, so it seems that the packaging should actively lower the priority. I think you could reorder the easytag entries in /etc/mailcap by doing some stuff with update-mime. However it won't fix this problem because desktop environments (including xdg-open and gnome-open) don't read /etc/mailcap, they read the mimeapps.list files. I can't see any way to set priorities for those (only user and desktop environment overrides). http://standards.freedesktop.org/mime-apps-spec/mime-apps-spec-1.0.1.html Thanks, James signature.asc Description: This is a digitally signed message part
Bug#788325: easytag: Don't register as default handler for directories
On 06/16/2015 01:01 PM, James Cowgill wrote: The more I read about this situation affecting other projects, the more I think David is right. All easytag is doing is following the freedesktop spec and since easytag can handle directories, it should have the directory mime type registered to it. This should either be fixed in gnome-open or the spec should be updated to allow apps to specify priorities. i can follow david's arguing and agree that it is not a bug in easytag (upstream). however, i don't think that the problem is with gnome-open or the freedesktop specs. installing the easytag package adds an entry to my /etc/mailcap file, that registers easytag as a program to display non-text [directories] at the local site (from mailcap(5), with a clarification by me in brackets). now i think that this is the main problem: easytag's desktop files declares that it *can* handle directories. (i guess the use case is that in your favourite filesystem browser you ought to be able to right-click on a directory and be presented with a list of applications that could handle that directory; having easytag in that list makes total sense to me). however, this declaration somehow makes the package installation process believe that it *should* handle directories (which is plain wrong), by adding an entry to /etc/mailcap. most likely the problem is with the packaging (not necessarily the easytag package per se, but maybe the tools used). according to update-mime(8), it *is* possible to add priorities to mime-types (for exactly the kind of problem we are facing). right now, easytag does not do anything special to register the mime-type handler, so it seems that the packaging should actively lower the priority. gfmadr IOhannes signature.asc Description: OpenPGP digital signature
Bug#788325: easytag: Don't register as default handler for directories
Control: found -1 2.3.7-1 Control: tags = upstream wontfix On Wed, 2015-06-10 at 12:26 +0100, David King wrote: On 2015-06-10 11:10, James Cowgill james...@cowgill.org.uk 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. I was referring to the packaging repo and this commit: https://anonscm.debian.org/cgit/pkg-multimedia/easytag.git/commit/?id=06db31be783e83aa146605260306a33fe5a9b8c3 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. The more I read about this situation affecting other projects, the more I think David is right. All easytag is doing is following the freedesktop spec and since easytag can handle directories, it should have the directory mime type registered to it. This should either be fixed in gnome-open or the spec should be updated to allow apps to specify priorities. Other projects which kept this mime type: https://bugs.kde.org/show_bug.cgi?id=309204 http://redmine.audacious-media-player.org/issues/102 Other projects which removed it: https://code.google.com/p/rawtherapee/issues/detail?id=1398 Thanks, James signature.asc Description: This is a digitally signed message part
Bug#788325: easytag: Don't register as default handler for directories
Hi James On 2015-06-10 11:10, James Cowgill james...@cowgill.org.uk 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
Bug#788325: easytag: Don't register as default handler for directories
Hi, This bug has been reported a few times upstream. https://bugzilla.gnome.org/show_bug.cgi?id=694358 https://bugzilla.gnome.org/show_bug.cgi?id=726092 https://mail.gnome.org/archives/easytag-list/2014-March/msg6.html 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. David? James On Wed, 2015-06-10 at 10:47 +0200, IOhannes m zmoelnig wrote: Package: easytag Version: 2.2.6-1 Severity: normal Dear Maintainer, * What led up to the situation? installed easytag * What exactly did you do (or not do) that was effective (or ineffective)? open a directory, using $ gnome-open /tmp * What was the outcome of this action? easytag was started. * What outcome did you expect instead? open a directory in a file browser. btw, using $ xdg-open /tmp works as expected. mfgards IOhannes -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages easytag depends on: ii libc6 2.19-18 ii libflac81.3.1-2 ii libgcc1 1:5.1.1-9 ii libgdk-pixbuf2.0-0 2.31.4-2 ii libglib2.0-02.44.1-1 ii libgtk-3-0 3.14.5-1 ii libid3-3.8.3c2a 3.8.3-16 ii libid3tag0 0.15.1b-11 ii libogg0 1.3.2-1 ii libopus01.1-2 ii libopusfile00.6-1 ii libpango-1.0-0 1.36.8-3 ii libspeex1 1.2~rc1.2-1 ii libstdc++6 5.1.1-9 ii libtag1c2a 1.9.1-2.1 ii libvorbis0a 1.3.4-2 ii libvorbisfile3 1.3.4-2 ii libwavpack1 4.70.0-1 Versions of packages easytag recommends: ii gnome-icon-theme 3.12.0-1 ii gvfs 1.24.1-2+b1 ii yelp 3.16.1-1 easytag suggests no packages. -- no debconf information signature.asc Description: This is a digitally signed message part
Bug#788325: easytag: Don't register as default handler for directories
Package: easytag Version: 2.2.6-1 Severity: normal Dear Maintainer, * What led up to the situation? installed easytag * What exactly did you do (or not do) that was effective (or ineffective)? open a directory, using $ gnome-open /tmp * What was the outcome of this action? easytag was started. * What outcome did you expect instead? open a directory in a file browser. btw, using $ xdg-open /tmp works as expected. mfgards IOhannes -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages easytag depends on: ii libc6 2.19-18 ii libflac81.3.1-2 ii libgcc1 1:5.1.1-9 ii libgdk-pixbuf2.0-0 2.31.4-2 ii libglib2.0-02.44.1-1 ii libgtk-3-0 3.14.5-1 ii libid3-3.8.3c2a 3.8.3-16 ii libid3tag0 0.15.1b-11 ii libogg0 1.3.2-1 ii libopus01.1-2 ii libopusfile00.6-1 ii libpango-1.0-0 1.36.8-3 ii libspeex1 1.2~rc1.2-1 ii libstdc++6 5.1.1-9 ii libtag1c2a 1.9.1-2.1 ii libvorbis0a 1.3.4-2 ii libvorbisfile3 1.3.4-2 ii libwavpack1 4.70.0-1 Versions of packages easytag recommends: ii gnome-icon-theme 3.12.0-1 ii gvfs 1.24.1-2+b1 ii yelp 3.16.1-1 easytag suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
