GNOME Bugzilla – Bug 441867
crash in Gimmie:
Last modified: 2007-09-04 21:19:50 UTC
What were you doing when the application crashed? Distribution: Fedora release 6.93 (Rawhide) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors (1673 sec old) --------------------- Major opcode of failed request: 23 (X_GetSelectionOwner) Atom id in failed request: 0x0 Serial number of failed request: 104841 Current serial number in output stream: 104841 --- Hash table keys for warning below: --> file:///root (nautilus:5106): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) Window manager warning: Received a _NET_WM_MOVERESIZE message for 0xe00be8 (ssh: 63.99); these messages lack timestamps and therefore suck. Window manager warning: Received a _NET_WM_MOVERESIZE message for 0xe01d3c (etc on 63.); these messages lack timestamps and therefore suck. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e00021 (Music Play) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. -------------------------------------------------- Traceback (most recent call last):
+ Trace 136481
for i in items:
for i in self.get_items_uncached():
yield DriveItem(drive)
raise ValueError, "Cannot find URI to open for drive '%s'" % drive
*** Bug 457046 has been marked as a duplicate of this bug. ***
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 421620 ***