GNOME Bugzilla – Bug 431726
crash in Gimmie: Clicked on the 'Library'...
Last modified: 2007-04-26 07:28:55 UTC
What were you doing when the application crashed? Clicked on the 'Library' tab. Application crashes Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.19-1.2911.6.5.fc6 #1 SMP Sun Mar 4 15:47:41 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled 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 (779 sec old) --------------------- root_geom = 543x836+52+136, root_size = 2560x1024 config_geom = 543x836 root_geom = 543x836+52+137, root_size = 2560x1024 config_geom = 543x836 root_geom = 543x836+52+138, root_size = 2560x1024 config_geom = 543x836 root_geom = 543x836+52+139, root_size = 2560x1024 config_geom = 543x836 root_geom = 543x836+52+140, root_size = 2560x1024 config_geom = 543x836 root_geom = 543x836+52+141, root_size = 2560x1024 config_geom = 543x836 root_geom = 543x836+52+142, root_size = 2560x1024 config_geom = 501x316 root_geom = 501x316+8+69, root_size = 2560x1024 -------------------------------------------------- Traceback (most recent call last):
+ Trace 129308
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 421620 ***