Bug 434598 – crash in gThumb Image Viewer: Logging out

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 434598 - crash in gThumb Image Viewer: Logging out


Summary:	crash in gThumb Image Viewer: Logging out


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-04-30 13:53 UTC by tim
Modified:	2007-04-30 13:55 UTC

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

Description tim 2007-04-30 13:53:15 UTC

What were you doing when the application crashed?
Logging out


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 241115136 vsize: 0 resident: 241115136 share: 0 rss: 33173504 rss_rlim: 0
CPU usage: start_time: 1177940654 rtime: 0 utime: 426 stime: 0 cutime:402 cstime: 0 timeout: 24 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gthumb'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227766096 (LWP 6147)]
[New Thread -1374692448 (LWP 6156)]
[New Thread -1366299744 (LWP 6155)]
[New Thread -1357907040 (LWP 6154)]
[New Thread -1331430496 (LWP 6151)]
[New Thread -1260368992 (LWP 6149)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 131450

Thread 1 (Thread -1227766096 (LWP 6147))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/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 /usr/lib/libgobject-2.0.so.0
#6 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#7 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#8 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit
from /usr/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_get_type
from /usr/lib/libgnomevfs-2.so.0
#12 dbus_connection_dispatch
from /usr/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 /usr/lib/libglib-2.0.so.0
#15 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#16 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#17 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#18 main
#0 __kernel_vsyscall

Comment 1 Michael Chudobiak 2007-04-30 13:55:16 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. You may want to check for a software upgrade.


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