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 690764 - crashes when browsing into folders containing .jp2 files
crashes when browsing into folders containing .jp2 files
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: Views: All
3.6.x
Other Linux
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 773585 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-12-27 10:31 UTC by Fabien Givors
Modified: 2016-10-27 14:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
backtrace (3.76 KB, text/plain)
2013-01-26 23:01 UTC, António Fernandes
Details

Description Fabien Givors 2012-12-27 10:31:24 UTC
Dear developers,

When trying to display the content of a folder containing a JPEG2000 (.jp2) file, nautilus crashes.

I can easily reproduce this bug in the following nautilus versions : 3.4.2 and 3.6.1 (Debian testing and Debian experimental).

And you can very easily check whether it's still present in the version you're using.

Steps to reproduce the problem :

  TMPDIR=$(mktemp -d /tmp/debug.XXXX)
  wget "ftp://ftp.microimages.com/pub/tnt/data/jp2/NEBMOSAI.jp2" -O "$TMPDIR/buggy.jp2"
  nautilus "$TMPDIR"

and wait a couple of seconds.

Thanks,
Comment 1 António Fernandes 2013-01-26 23:01:37 UTC
Created attachment 234502 [details]
backtrace

I cannot reproduce the crash on nautilus git master (3.7.4). Nautilus does not crash and leave no output on terminal.

Anyway, I can reproduce the crash on version 3.6.3, on Fedora 18, so I attached the backtrace.

Perhaps noteworthy, it seems that 3.6.3 is trying to get a thumbnail (the icon of the file is status/image-loading.png) while 3.7.4 is not even trying (the icon is mimetypes/image-x-generic.png).
Comment 3 Carlos Soriano 2016-10-27 14:20:02 UTC
*** Bug 773585 has been marked as a duplicate of this bug. ***