GNOME Bugzilla – Bug 444569
crash in Gimmie:
Last modified: 2007-09-14 22:36:55 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) 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 (703 sec old) --------------------- --- Hash table keys for warning below: --> file:///home/thomas (nautilus:3496): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) --- Hash table keys for warning below: --> file:///home/thomas (nautilus:3506): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) Loading "installonlyn" plugin Loading "installonlyn" plugin libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 8df56d05 Importing GPG key 0x8DF56D05 "Fedora Linux (RPMS) <security@fedora.us>" from http://macromedia.mplug.org/FEDORA-GPG-KEY -------------------------------------------------- Traceback (most recent call last):
+ Trace 138633
self.sidebar.connect("set-source", lambda sb, source: self._set_source(source))
self.get_zoom_level())
return [x for x in items if self._filter_compare(x, days_ago)]
for i in self.get_items_uncached():
for item in source.get_items_uncached():
yield DriveItem(drive)
raise ValueError, "Cannot find URI to open for drive '%s'" % drive
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 ***