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 495268 - crash in gThumb Image Viewer:
crash in gThumb Image Viewer:
Status: RESOLVED DUPLICATE of bug 468801
Product: gthumb
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2007-11-09 12:41 UTC by patrick
Modified: 2007-11-09 13:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description patrick 2007-11-09 12:41:49 UTC
What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 66621440 vsize: 66621440 resident: 27906048 share: 20762624 rss: 27906048 rss_rlim: 4294967295
CPU usage: start_time: 1194609132 rtime: 80 utime: 72 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gthumb'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208445216 (LWP 6621)]
[New Thread -1241420912 (LWP 6628)]
[New Thread -1240892528 (LWP 6627)]
[New Thread -1240364144 (LWP 6626)]
[New Thread -1229345904 (LWP 6624)]
[New Thread -1228817520 (LWP 6623)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208445216 (LWP 6621))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
    from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-tga.so
  • #5 ??
    from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-tga.so
  • #6 gdk_pixbuf_loader_close
    from /usr/lib/libgdk_pixbuf-2.0.so.0
  • #7 gdk_pixbuf_loader_write
    from /usr/lib/libgdk_pixbuf-2.0.so.0
  • #8 gdk_pixbuf_get_file_info
    from /usr/lib/libgdk_pixbuf-2.0.so.0
  • #9 ??
  • #10 ??
  • #11 ??
    from /lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #13 ??
    from /lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #15 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (1958 sec old) ---------------------
Max failures exceeded, exiting now
[DEBUG]: Creating Buffer for 'New Note 3'...
[DEBUG]: Saving 'Scratch'...
[DEBUG]: Saving 'Scratch'...
[DEBUG]: Saving 'Scratch'...
[DEBUG]: Unable to load icon 'system-search'.
[DEBUG]: Saving 'Scratch'...
[DEBUG]: Saving 'Scratch'...
(Tomboy:2936): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping th
[DEBUG]: Saving 'Scratch'...
[DEBUG]: Saving 'Scratch'...
[DEBUG]: Saving 'Scratch'...
[DEBUG]: Saving 'Scratch'...
[DEBUG]: Saving 'Scratch'...
--------------------------------------------------
Comment 1 Michael Chudobiak 2007-11-09 12:45:52 UTC
What version of gthumb are you using?

Could you email the image that causes the crash (looks like a tga image) to mjc@avtechpulse.com for analysis?

- Mike
Comment 2 patrick 2007-11-09 13:17:21 UTC
It's gthumb version "GNOME gthumb 2.10.7" on a fedora 7 system. I've emailed you two of the files that cause the crash.

oh, and you can knock the priority down from high/critical if you like, that seems a bit excessive to me!
Comment 3 Michael Chudobiak 2007-11-09 13:37:53 UTC
This is a known bug that has been fixed.

Your image does crash Fedora 6 and 7, but it works OK on Fedora 8 - so you might want to upgrade.

- Mike


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