Bug 482653 – crash in gThumb Image Viewer:

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 482653 - crash in gThumb Image Viewer:


Summary:	crash in gThumb Image Viewer:


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-10-02 16:30 UTC by fois5
Modified:	2007-10-02 16:33 UTC

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

Description fois5 2007-10-02 16:30:25 UTC

What were you doing when the application crashed?



Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 591527936 vsize: 591527936 resident: 47788032 share: 16949248 rss: 64737280 rss_rlim: 893726720
CPU usage: start_time: 1191340934 rtime: 4490 utime: 4236 stime: 254 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/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 47448940312144 (LWP 15122)]
[New Thread 1199630656 (LWP 15139)]
[New Thread 1191237952 (LWP 15138)]
[New Thread 1182845248 (LWP 15137)]
[New Thread 1090525504 (LWP 15126)]
[New Thread 1082132800 (LWP 15124)]
(no debugging symbols found)
0x00002b278fa0cc5f in waitpid () from /lib64/libpthread.so.0

+ Trace 167175

Thread 1 (Thread 47448940312144 (LWP 15122))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /opt/gnome/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_object_unref
from /opt/gnome/lib64/libgobject-2.0.so.0
#4 gnome_vfs_drive_unref
from /opt/gnome/lib64/libgnomevfs-2.so.0
#5 g_list_foreach
from /opt/gnome/lib64/libglib-2.0.so.0
#6 gth_location_new
#7 g_closure_invoke
from /opt/gnome/lib64/libgobject-2.0.so.0
#8 g_signal_override_class_closure
from /opt/gnome/lib64/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /opt/gnome/lib64/libgobject-2.0.so.0
#10 g_signal_emit
from /opt/gnome/lib64/libgobject-2.0.so.0
#11 gnome_vfs_volume_monitor_emit_pre_unmount
from /opt/gnome/lib64/libgnomevfs-2.so.0
#12 gnome_vfs_volume_monitor_client_get_type
from /opt/gnome/lib64/libgnomevfs-2.so.0
#13 dbus_connection_dispatch
from /usr/lib64/libdbus-1.so.3
#14 dbus_server_setup_with_g_main
from /usr/lib64/libdbus-glib-1.so.2
#15 g_main_context_dispatch
from /opt/gnome/lib64/libglib-2.0.so.0
#16 g_main_context_prepare
from /opt/gnome/lib64/libglib-2.0.so.0
#17 g_main_loop_run
from /opt/gnome/lib64/libglib-2.0.so.0
#18 gtk_main
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#19 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Michael Chudobiak 2007-10-02 16:33:49 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 ***