Bug 493505 – crash in gThumb Image Viewer: Deleted the last image i...

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 493505 - crash in gThumb Image Viewer: Deleted the last image i...


Summary:	crash in gThumb Image Viewer: Deleted the last image i...


Status:	RESOLVED DUPLICATE of bug 485721

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-11-04 20:45 UTC by Martin Wildam
Modified:	2007-11-05 01:13 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Martin Wildam 2007-11-04 20:45:49 UTC

What were you doing when the application crashed?
Deleted the last image in the folder while in fullscreen mode


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2936.fc7xen #1 SMP Fri Sep 21 12:07:35 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 340545536 vsize: 340545536 resident: 243113984 share: 36253696 rss: 243113984 rss_rlim: 4294967295
CPU usage: start_time: 1194209265 rtime: 1892 utime: 1732 stime: 160 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 "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208973600 (LWP 10186)]
[New Thread -1452987504 (LWP 10261)]
[New Thread -1275229296 (LWP 10258)]
[New Thread -1274700912 (LWP 10257)]
[New Thread -1274172528 (LWP 10256)]
[New Thread -1273644144 (LWP 10255)]
[New Thread -1367450736 (LWP 10202)]
[New Thread -1366922352 (LWP 10201)]
[New Thread -1366393968 (LWP 10200)]
[New Thread -1271456880 (LWP 10189)]
[New Thread -1270928496 (LWP 10188)]
(no debugging symbols found)
0x00b1e402 in __kernel_vsyscall ()

+ Trace 175216

Thread 1 (Thread -1208973600 (LWP 10186))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/nosegneg/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 add_scheme_if_absent
from /usr/lib/gthumb/libgthumb.so
#5 uricmp
from /usr/lib/gthumb/libgthumb.so
#6 g_list_find_custom
from /lib/libglib-2.0.so.0
#7 ??
#8 gthumb_marshal_VOID__INT_BOXED
from /usr/lib/gthumb/libgthumb.so
#9 g_closure_invoke
from /lib/libgobject-2.0.so.0
#10 ??
from /lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#12 g_signal_emit
from /lib/libgobject-2.0.so.0
#13 gth_monitor_notify_update_files
#14 all_windows_notify_files_created
#15 ??
#16 ??
#17 ??
from /usr/lib/libgnomevfs-2.so.0
#18 ??
#19 ??
#20 ??
#21 ??
from /usr/lib/libgnomevfs-2.so.0
#22 ??
#23 ??
from /lib/i686/nosegneg/libpthread.so.0
#24 ??
#25 ??
from /usr/lib/libgnomevfs-2.so.0
#26 ??
#27 ??
#0 __kernel_vsyscall



----------- .xsession-errors (59 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------

Comment 1 Michael Chudobiak 2007-11-05 01:13:29 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 485721 ***