jpeg-2000 files cause Nautilus to crash
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
Diagnosing this bug may be complicated by Bug #1443809. I am currently using a custom thumbnailer for jpeg-2000 files, but before I did so, I had created a number of jpeg-2000 files. While there were some cases where they caused a crash, I think the eventual result was that they all had 'failed thumbnails' created for them. Possibly eog created valid thumbnails for them. (I can't check to see what happened because I deleted my old thumbnails folder after upgrading.)
With no custom thumbnailers, nautilus will crash upon encountering a jpeg-2000 file, with file suffix .jp2. As noted in Bug #1444790, it doesn't crash if the jpeg-2000 file has a different suffix; it just produces a 'failed thumbnail' in the thumbnails folder, which for current Ubuntu versions is ~/.cache/
If the thumbnail check was performed because the jpeg-2000 file was renamed from an inappropriate suffix to .jp2, or because it was renamed by some other method while not looking at the directory containing that file (such as the command line, or maybe using the 'undo' function in nautilus though this would require 1) having a normal or failed thumbnail 2) renaming the file 3) deleting the thumbnail 4) nautilus would have to stop using the cached thumbnail, and I don't think it does), nautilus will crash without invoking eog for thumbnail creation, and so will continue to crash whenever that folder is viewed.
A jpeg-2000 file can be generated using mogrify from imagemagick with the command 'mogrify -format jp2 image.jpg'.
The advantages and disadvantages of jpeg-2000, compared to jpeg, are described here: http://
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: nautilus 1:3.10.
ProcVersionSign
Uname: Linux 3.16.0-30-generic x86_64
NonfreeKernelMo
ApportVersion: 2.14.7-0ubuntu8.3
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr 15 22:52:39 2015
GsettingsChanges:
b'org.
b'org.
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
Do you still see that issue in newer Ubuntu versions? If so could you add a file example to the bug?