Files ending with jpg must be renamed jpeg to open

[Anders S. Nordbø]

This bug has been reported before (as a Nautilus-related bug), but was rejected because it was not related directly to Nautilus. The issue is still unresolved it seems, because I had to manually edit ~/.local/share/mime/globs as outlined here:

http://ubuntuforums.org/showthread.php?p=2138876

in order to open images in Nautilus the normal way. This is an unnecessary annoyance especially for new users, because usually digital camera software saves images with "jpg" or "JPG" suffix, not the "jpeg" suffix as demanded by the ~/.local/share/mime/globs file. In the post referred to above user pyro explains how to fix the problem. Hopefully the cause of this bug can be found so this will not annoy new Ubuntu users.

What happens is when I double click an image named picture.jpg an error message pops up saying this file can be harmful etc, and that you should rename it to jpeg. This is a bad approach. A file named jpeg is not any less harmful than a file named jpg. Let's sort this out.

Not being able to view your images for the main file browser (Nautilus) is a very serious bug, and should be treated as such. Imagine a user just installed Ubuntu and has little or no skills in configuring even the simplest things. He plugs his digital camera into the USB port to test if Ubuntu can do what Windows can. But when he tries to view the pictures Ubuntu (as he would see it) fails! Although this isn't really Ubuntu or Nautilus bug it certainly will put the user off Ubuntu - "What? It can't even open images? Well, back to windows it is..."

[Dan O'Huiginn (daniel-ohuiginn)]

I see what you mean. There have been quite a few reports of this on the forums, as well as bugs like #42992 and #37547

Some people are reporting that this happens after installing f-spot. Do you have f-spot installed?

[Dan O'Huiginn (daniel-ohuiginn)]

Also, what version of Ubuntu are you running? All the other reports are Dapper, as far as I can see.

[Anders S. Nordbø (anders-sandberg-nordbo)]

Yes i have f-spot installed, however it was installed for me automatically during Ubuntu setup. I'm running Edgy AMD64.

[Dan O'Huiginn (daniel-ohuiginn)]

I'm setting this to confirmed as it's now been reported in detail several times now in forums and other bug reports. Setting the package to f-spot on the basis of http://ubuntuforums.org/showthread.php?p=2138876

[spanella (spanella)]

this bug seems to have resurfaced in gutsy just a few weeks ago.
http://ubuntuforums.org/showthread.php?t=414033
http://ubuntuforums.org/showthread.php?t=494991
http://ubuntuforums.org/showthread.php?t=589861

I for one am running Gutsy and have had F-spot installed since day 1 but the warnings just arose recently.

[John - Richmond (moshuptrail)]

A few notes about this...
If you rename the file to .jpeg, double-click on it, it works. (we knew that)
If you then rename it back to .jpg, you can now double-click on it and it will open in Image Viewer!

A similar problem has been reported for MP3 files:
http://ubuntuforums.org/showthread.php?t=617301&highlight=file+type

[spanella (spanella)]

there is a solution here:
http://ubuntuforums.org/showthread.php?t=589861
alternatively, it should be ok just to erase the file it tells you to fix (~/.local/share/mime/globs), anything there is autocreated in the first place.

i just went ahead and erased the whole '.local' folder to make sure it went away and everything works fine here now. some personal settings may be lost, but easily fixed. also lost album covers, could have left those.

[Sebastien Bacher (seb128)]

the issue described there is an incorrect local configuration and not a fspot bug