GNOME Bugzilla – Bug 373857
crash in gThumb Image Viewer: Visualizar fotos
Last modified: 2007-10-03 15:16:37 UTC
What were you doing when the application crashed? Visualizar fotos Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 194805760 vsize: 0 resident: 194805760 share: 0 rss: 24436736 rss_rlim: 0 CPU usage: start_time: 1163255306 rtime: 0 utime: 65 stime: 0 cutime:62 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gthumb' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1227807056 (LWP 9019)] [New Thread -1425740896 (LWP 9035)] [New Thread -1417348192 (LWP 9034)] [New Thread -1408955488 (LWP 9033)] [New Thread -1324938336 (LWP 9023)] [New Thread -1257669728 (LWP 9021)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 85424
Thread 1 (Thread -1227807056 (LWP 9019))
*** Bug 380296 has been marked as a duplicate of this bug. ***
*** Bug 380669 has been marked as a duplicate of this bug. ***
*** Bug 382044 has been marked as a duplicate of this bug. ***
*** Bug 394358 has been marked as a duplicate of this bug. ***
Probably a libexif bug. Maybe this one: http://sourceforge.net/tracker/index.php?func=detail&aid=1306193&group_id=12272&atid=112272 - Mike
... or maybe not that particular bug. But it still looks like a libexif bug. Can anyone duplicate this bug? A better stacktrace would be helpful (see http://live.gnome.org/GettingTraces)! If there is a particular image that triggers this bug, please attach it to this report. Thanks. - Mike
*** Bug 398474 has been marked as a duplicate of this bug. ***
Can anyone supply a sample image that seems to trigger this bug? - Mike
*** Bug 423144 has been marked as a duplicate of this bug. ***
*** Bug 435685 has been marked as a duplicate of this bug. ***
I see a number of bugs marked as duplicates of this one. But none of them contains any image that could be used to reproduce the bug(s). There is just one link to a nearly 2-years old bug at libexif bug tracker which does contain an image - crash.jpg. However, the current CVS version of libexif doesn't seem to have problem with that crash.jpg. Could somebody please attach a sample image showing the bug with current CVS version of libexif? Thank you.
*** Bug 437778 has been marked as a duplicate of this bug. ***
*** Bug 437780 has been marked as a duplicate of this bug. ***
I think it is safe to say that this is no longer an issue with libexif 0.6.13. If this bug happens to you, upgrade libexif to the latest available version. A sample image was provided to me (bug 408659), but it does not crash current up-to-date systems. - Mike
*** Bug 426087 has been marked as a duplicate of this bug. ***
*** Bug 482978 has been marked as a duplicate of this bug. ***