What were you doing when the application crashed?
To reproduce I:
1) Insert a flash card into my card reader.
2) The dcim directory (on the card) is shown in the gthumb browser. There are no images here, so I navigate to the 145CANON subdirectory.
3) I click on ".." to return to the dcim directory.
4) I remove the card without unmounting first. Crash!

Note: This does not happen if I do not go to the 145CANON subfolder. That is, if I leave the browser view at dcim, it will not crash when I remove the card.

- Mike


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors (159 sec old) ---------------------
end from FAM server connection
end from FAM server connection
end from FAM server connection
** (gthumb:6530): CRITICAL **: gth_image_list_moveto: assertion `(pos >= 0) && (pos < priv->images)' failed
end from FAM server connection
end from FAM server connection
** (bug-buddy:6652): WARNING **: Couldn't load icon for Open Folder
warning: the debug information found in "/usr/lib/debug//usr/lib/gnome-vfs-2.0/modules/libfile.so.debug" does not match "/usr/lib/gnome-vfs-2.0/modules/libfile.so" (CRC mismatch).
Cannot access memory at address 0x0
Cannot access memory at address 0x0
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x3200003 (Bug Buddy); these messages lack timestamps and therefore suck.
--------------------------------------------------

Memory status: size: 281387008 vsize: 0 resident: 281387008 share: 0 rss: 20193280 rss_rlim: 0
CPU usage: start_time: 1163617217 rtime: 0 utime: 73 stime: 0 cutime:68 cstime: 0 timeout: 5 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208834352 (LWP 6779)]
[New Thread -1491678320 (LWP 6834)]
[New Thread -1481188464 (LWP 6833)]
[New Thread -1470698608 (LWP 6832)]
[New Thread -1365054576 (LWP 6828)]
[New Thread -1354564720 (LWP 6827)]
0x004aa402 in __kernel_vsyscall ()

+ Trace 86748