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 477151 - crash in gThumb Image Viewer: trying to open .jpg file
crash in gThumb Image Viewer: trying to open .jpg file
Status: RESOLVED DUPLICATE of bug 453986
Product: gthumb
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2007-09-15 07:35 UTC by Rick Parsons
Modified: 2007-09-15 16:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Rick Parsons 2007-09-15 07:35:36 UTC
What were you doing when the application crashed?
trying to open .jpg file


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 77148160 vsize: 77148160 resident: 17993728 share: 11980800 rss: 17993728 rss_rlim: 4294967295
CPU usage: start_time: 1189841702 rtime: 51 utime: 45 stime: 6 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 -1208325888 (LWP 3125)]
[New Thread -1326675056 (LWP 3144)]
[New Thread -1326146672 (LWP 3143)]
[New Thread -1325618288 (LWP 3142)]
[New Thread -1220191344 (LWP 3131)]
[New Thread -1219662960 (LWP 3130)]
(no debugging symbols found)
0x008fa402 in __kernel_vsyscall ()

Thread 1 (Thread -1208325888 (LWP 3125))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 uricmp
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_markup_escape_text
    from /lib/libglib-2.0.so.0
  • #5 save_comment
    from /usr/lib/gthumb/libgthumb.so
  • #6 comments_load_comment
    from /usr/lib/gthumb/libgthumb.so
  • #7 ??
  • #8 ??
  • #9 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #11 uricmp
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #14 uricmp
    from /usr/lib/gthumb/libgthumb.so
  • #15 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #17 uricmp
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #20 image_loader_load_from_image_loader
    from /usr/lib/gthumb/libgthumb.so
  • #21 load_from_image_loader__step2
    from /usr/lib/gthumb/libgthumb.so
  • #22 uricmp
    from /usr/lib/gthumb/libgthumb.so
  • #23 uricmp
    from /lib/libglib-2.0.so.0
  • #24 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #25 uricmp
    from /lib/libglib-2.0.so.0
  • #26 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #27 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 main
  • #0 __kernel_vsyscall

Comment 1 Michael Chudobiak 2007-09-15 16:24:11 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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