Bug 443253 – crash in gThumb Image Viewer: System was not being use...

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 443253 - crash in gThumb Image Viewer: System was not being use...


Summary:	crash in gThumb Image Viewer: System was not being use...


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-02 16:09 UTC by matthew
Modified:	2007-06-04 12:21 UTC

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

Description matthew 2007-06-02 16:09:38 UTC

What were you doing when the application crashed?
System was not being used when crash occurred.  This bug-buddy was sitting on the top of the screen when I got on the computer this morning.

There were 2 copies of gthumb running, neither which is on this virtual X11 screen.


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.2944.fc6 #1 SMP Tue Apr 10 17:46:00 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 1058516992 vsize: 1058516992 resident: 229343232 share: 15462400 rss: 229343232 rss_rlim: -1
CPU usage: start_time: 1180418534 rtime: 22519 utime: 21511 stime: 1008 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/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 46912498633136 (LWP 14869)]
[New Thread 1084229952 (LWP 14934)]
[New Thread 1178638656 (LWP 14882)]
[New Thread 1168148800 (LWP 14881)]
[New Thread 1157658944 (LWP 14880)]
[New Thread 1147169088 (LWP 14879)]
[New Thread 1094719808 (LWP 14873)]
0x000000369d00d96f in __libc_waitpid (pid=28704, stat_loc=0x7fffc709f8bc, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

+ Trace 137542

Thread 1 (Thread 46912498633136 (LWP 14869))

#0 __libc_waitpid
at ../sysdeps/unix/sysv/linux/waitpid.c line 41
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 gth_location_new
#4 IA__g_closure_invoke
at gclosure.c line 490
#5 signal_emit_unlocked_R
at gsignal.c line 2440
#6 IA__g_signal_emit_valist
at gsignal.c line 2199
#7 IA__g_signal_emit
at gsignal.c line 2243
#8 _gnome_vfs_volume_monitor_mounted
at gnome-vfs-volume-monitor.c line 769
#9 dbus_filter_func
at gnome-vfs-volume-monitor-client.c line 318
#10 dbus_connection_dispatch
from /lib64/libdbus-1.so.3
#11 dbus_server_setup_with_g_main
from /usr/lib64/libdbus-glib-1.so.2
#12 IA__g_main_context_dispatch
at gmain.c line 2045
#13 g_main_context_iterate
at gmain.c line 2677
#14 IA__g_main_loop_run
at gmain.c line 2881
#15 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#16 main

0x000000369d00d96f	41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

Comment 1 Michael Chudobiak 2007-06-04 12:21:25 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 ***