After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 318326 - cannot open files with different mime types association (extension, contents)
cannot open files with different mime types association (extension, contents)
Status: RESOLVED DUPLICATE of bug 138033
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.12.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-10-09 09:15 UTC by Marius Andreiana
Modified: 2005-10-09 21:07 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Marius Andreiana 2005-10-09 09:15:00 UTC
When trying to open files for which the mime types association by extension and
contents differ nautilus will give an error (The filename ... indicates that
this file...). It usually happens with media files (extentions .wmv, .asf, .avi...)

This is a big pain as you can see from google too:
http://www.google.ro/search?q=nautilus+%22indicates+that+this+file%22&start=0&start=0&ie=utf-8&oe=utf-8&client=firefox&rls=org.mozilla:en-US:unofficial
A regular user will simply think that GNOME doesn't work, as the file can be
played properly in Windows.

Please add to the dialog box a checkbox 'Dont show this warning again" and add
another button after "Cancel" named "Open anyway", which will simply open the
file with one of the two associated applications (contents or extension).

Thanks
Comment 1 Marius Andreiana 2005-10-09 09:16:00 UTC
I know the proper fix is in mime types, but there are too many types to handle.
Implementing this in nautilus will make it more usable.
Comment 2 Christian Kirbach 2005-10-09 20:35:26 UTC
Yes, I have seen this as well.

For instance 
http://www.linuxquestions.org/questions/history/365345
has a solution for this by aliasing mime types.

I wonder if we should do this for a very few mime types to avoid confusion.

Comment 3 Christian Kirbach 2005-10-09 21:07:08 UTC
This has already been reported.

I have just been told work is in progress to revise the dialog.

*** This bug has been marked as a duplicate of 138033 ***