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 448877 - crash in gThumb Image Viewer: removed SD media from re...
crash in gThumb Image Viewer: removed SD media from re...
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-06-18 18:55 UTC by simon
Modified: 2007-06-18 18:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description simon 2007-06-18 18:55:55 UTC 
What were you doing when the application crashed?
removed SD media from reader. Awesome app, BTW.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2952.fc6 #1 SMP Wed May 16 18:59:18 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 435286016 vsize: 0 resident: 435286016 share: 0 rss: 65794048 rss_rlim: 0
CPU usage: start_time: 1182191911 rtime: 0 utime: 11991 stime: 0 cutime:11484 cstime: 0 timeout: 507 it_real_value: 0 frequency: 0

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 -1208502576 (LWP 26995)]
[New Thread -1459848304 (LWP 27012)]
[New Thread -1449358448 (LWP 27011)]
[New Thread -1438868592 (LWP 27010)]
[New Thread -1428378736 (LWP 27009)]
[New Thread -1417888880 (LWP 27008)]
[New Thread -1275896944 (LWP 27003)]
(no debugging symbols found)
0x00d5b402 in __kernel_vsyscall ()

+ Trace 141952

Thread 1 (Thread -1208502576 (LWP 26995))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gth_location_new
  • #5 g_cclosure_marshal_VOID__OBJECT
    from /lib/libgobject-2.0.so.0
  • #6 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #7 g_signal_chain_from_overridden
    from /lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #10 gnome_vfs_volume_monitor_emit_pre_unmount
    from /usr/lib/libgnomevfs-2.so.0
  • #11 gnome_vfs_volume_monitor_client_shutdown_private
    from /usr/lib/libgnomevfs-2.so.0
  • #12 dbus_connection_dispatch
    from /lib/libdbus-1.so.3
  • #13 dbus_server_setup_with_g_main
    from /usr/lib/libdbus-glib-1.so.2
  • #14 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #15 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #17 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (91431 sec old) ---------------------
kdeinit: Got EXEC_NEW 'kio_http' from launcher.
kdeinit: Got EXEC_NEW 'kio_http' from launcher.
kdeinit: Got EXEC_NEW 'kio_http' from launcher.
DCOP: register 'anonymous-13235' -> number of clients is now 23
DCOP: register 'anonymous-13234' -> number of clients is now 24
kdeinit: Got EXEC_NEW 'kio_http' from launcher.
DCOP: register 'anonymous-13238' -> number of clients is now 25
DCOP: register 'anonymous-13236' -> number of clients is now 26
kdeinit: Got EXEC_NEW 'kio_http' from launcher.
kdeinit: Got EXEC_NEW 'kio_http' from launcher.
DCOP: register 'anonymous-13246' -> number of clients is now 27
kdeinit: Got EXEC_NEW 'kio_http' from launcher.
DCOP: register 'anonymous-13247' -> number of clients is now 28
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Michael Chudobiak 2007-06-18 18:58:04 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. Please upgrade to the 2.10.x series.


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