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 437128 - crash in gThumb Image Viewer: I simply opened the app!...
crash in gThumb Image Viewer: I simply opened the app!...
Status: RESOLVED DUPLICATE of bug 356623
Product: gthumb
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2007-05-09 11:56 UTC by Shingoshi
Modified: 2007-05-09 12:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Shingoshi 2007-05-09 11:56:59 UTC 
What were you doing when the application crashed?
I simply opened the app! It crashed and never opened.


Distribution: Unknown
Gnome Release: 2.16.1 2006-10-21 (FRG gsb.sourceforge.net build for slackware)
BugBuddy Version: 2.16.0

Memory status: size: 196866048 vsize: 196866048 resident: 12754944 share: 9531392 rss: 12754944 rss_rlim: -1
CPU usage: start_time: 1178711634 rtime: 17 utime: 12 stime: 5 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47187844199072 (LWP 17417)]
[New Thread 1082132800 (LWP 17421)]
0x00002aeac31f0b9f in waitpid () from /lib64/libpthread.so.0

+ Trace 133244

Thread 1 (Thread 47187844199072 (LWP 17417))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 ??
    from /usr/lib64/libdbus-1.so.3
  • #6 ??
    from /usr/lib64/libdbus-1.so.3
  • #7 ??
    from /usr/lib64/libdbus-1.so.3
  • #8 ??
    from /usr/lib64/libdbus-1.so.3
  • #9 ??
    from /usr/lib64/libdbus-1.so.3
  • #10 ??
    from /usr/lib64/libdbus-1.so.3
  • #11 ??
    from /usr/lib64/libdbus-1.so.3
  • #12 ??
    from /usr/lib64/libdbus-1.so.3
  • #13 ??
    from /usr/lib64/libgnomevfs-2.so.0
  • #14 ??
    from /usr/lib64/libgnomevfs-2.so.0
  • #15 g_type_create_instance
    from /usr/lib64/libgobject-2.0.so.0
  • #16 ??
    from /usr/lib64/libgobject-2.0.so.0
  • #17 g_object_newv
    from /usr/lib64/libgobject-2.0.so.0
  • #18 g_object_new_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #19 g_object_new
    from /usr/lib64/libgobject-2.0.so.0
  • #20 ??
    from /usr/lib64/libgnomevfs-2.so.0
  • #21 ??
  • #22 g_type_create_instance
    from /usr/lib64/libgobject-2.0.so.0
  • #23 ??
    from /usr/lib64/libgobject-2.0.so.0
  • #24 g_object_newv
    from /usr/lib64/libgobject-2.0.so.0
  • #25 g_object_new_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #26 g_object_new
    from /usr/lib64/libgobject-2.0.so.0
  • #27 gth_location_new
  • #28 gth_browser_new
  • #29 ??
  • #30 main
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


Michael Chudobiak





          2007-05-09 12:03:48 UTC
        



Probably a duplicate of bug 356623. Try upgrading to the 2.10.x series.

- Mike

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