GNOME Bugzilla – Bug 444166
crash in Gimmie:
Last modified: 2007-07-04 17:50:45 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 (269 sec old) --------------------- pas-id-46646DC100000020-birthday has recurrences pas-id-4663210A00000000-birthday has recurrences pas-id-46646DC100000003-birthday has recurrences pas-id-46646DC100000018-birthday has recurrences pas-id-46646DC10000001D-birthday has recurrences pas-id-46646DC100000008-birthday has recurrences pas-id-46646DC100000013-birthday has recurrences pas-id-46646DC10000001C-birthday has recurrences ** Message: <info> You are now connected to the wired network. ** Message: <info> You are now connected to the wired network. ** Message: <info> You are now connected to the wired network. X connection to :0.0 broken (explicit kill or server shutdown). -------------------------------------------------- Traceback (most recent call last):
+ Trace 138302
self._show()
self.topic_win = self.topic.get_topic_window()
self.topic_window = TopicMenu(self)
self._add_toolbar_items()
for i in self.topic.get_toolbar_items(self.tooltips):
btn = PlacesMenuButton(tooltips)
self.set_menu(PlacesMenu())
for item in device_source.get_items():
for i in self.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 423474 ***