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 441726 - crash in gThumb Image Viewer: Inserted CD into drive b...
crash in gThumb Image Viewer: Inserted CD into drive b...
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-28 02:35 UTC by Paul Wayper
Modified: 2007-05-28 12:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Paul Wayper 2007-05-28 02:35:13 UTC 
What were you doing when the application crashed?
Inserted CD into drive but had not yet got nautilus window.


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.2948.fc6 #1 SMP Fri Apr 27 19:48:40 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 344768512 vsize: 0 resident: 344768512 share: 0 rss: 98033664 rss_rlim: 0
CPU usage: start_time: 1180072525 rtime: 0 utime: 4799 stime: 0 cutime:4403 cstime: 0 timeout: 396 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 -1209059632 (LWP 3206)]
[New Thread -1442079856 (LWP 3772)]
[New Thread -1431590000 (LWP 3771)]
[New Thread -1421100144 (LWP 3770)]
[New Thread -1410610288 (LWP 3769)]
[New Thread -1346606192 (LWP 3768)]
[New Thread -1330898032 (LWP 3767)]
(no debugging symbols found)
0x00762402 in __kernel_vsyscall ()

+ Trace 136378

Thread 1 (Thread -1209059632 (LWP 3206))

  • #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 (2230 sec old) ---------------------
/usr/bin/xflock4: line 22: xlock: command not found
/usr/bin/xflock4: line 22: xscreensaver-command: command not found
/usr/bin/xflock4: line 22: xlock: command not found
/usr/bin/xflock4: line 22: xscreensaver-command: command not found
/usr/bin/xflock4: line 22: xlock: command not found
(xfce4-panel:2755): Gtk-WARNING **: idle activate multiple times without clearing the folder object first.
(Terminal:2867): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
Traceback (most recent call last):
  File "/usr/bin/puplet", line 248, in updates_avail_notify
    self._showNotify(notify, urgency)
  File "/usr/bin/puplet", line 191, in _showNotify
    if not self.notify.show():
gobject.GError: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the netw
--------------------------------------------------
Comment 1 Michael Chudobiak 2007-05-28 12:15:12 UTC 
Please upgrade to gThumb 2.10.x. This bug has been fixed.

- Mike

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