Bug 447264 – crash in gThumb Image Viewer: Unmounting a USB volume.

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 447264 - crash in gThumb Image Viewer: Unmounting a USB volume.


Summary:	crash in gThumb Image Viewer: Unmounting a USB volume.


Status:	RESOLVED DUPLICATE of bug 356623

Product:	gthumb
Classification:	Other
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Paolo Bacchilega
QA Contact:	Paolo Bacchilega

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-13 18:31 UTC by Jake Gage
Modified:	2007-06-13 18:32 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Jake Gage 2007-06-13 18:31:14 UTC

What were you doing when the application crashed?
Unmounting a USB volume.


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.18-1.2869.fc6 #1 SMP Wed Dec 20 14:51:19 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 342003712 vsize: 0 resident: 342003712 share: 0 rss: 106332160 rss_rlim: 0
CPU usage: start_time: 1181755835 rtime: 0 utime: 826 stime: 0 cutime:779 cstime: 0 timeout: 47 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 -1209137456 (LWP 5705)]
[New Thread -1443902576 (LWP 5714)]
[New Thread -1433412720 (LWP 5713)]
[New Thread -1422922864 (LWP 5712)]
[New Thread -1412433008 (LWP 5711)]
[New Thread -1379247216 (LWP 5708)]
[New Thread -1263486064 (LWP 5707)]
(no debugging symbols found)
0x00b63402 in __kernel_vsyscall ()

+ Trace 140735

Thread 1 (Thread -1209137456 (LWP 5705))

#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 ---------------------
ScimInputContextPlugin()
~ScimInputContextPlugin()
ScimInputContextPlugin()
WARNING: please edit ~/.scim/global and change /DefaultConfigModule to kconfig
DCOP: unregister 'anonymous-5963'
kdeinit: PID 5963 terminated.
closing
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x186 specified for 0x4a00161 (Reminder -).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x186 specified for 0x4a00040 (Reminder -).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x186 specified for 0x4a00161 (Reminder -).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x186 specified for 0x4a00161 (Reminder -).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x186 specified for 0x4a00161 (Reminder -).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x186 specified for 0x4a00161 (Reminder -).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x186 specified for 0x4a00161 (Reminder -).
closing
--------------------------------------------------

Comment 1 Michael Chudobiak 2007-06-13 18:32:54 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 356623 ***