GNOME Bugzilla – Bug 425329
crash in Gimmie: Clicked Library bar
Last modified: 2007-04-02 01:46:16 UTC
What were you doing when the application crashed? Clicked Library bar 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.20-1.2933.fc6 #1 SMP Mon Mar 19 11:38:26 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing 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 --------------------- btn = PlacesMenuButton(tooltips)
+ Trace 124209
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
** (bug-buddy:9391): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/gimmie/gimmie_gui.py", line 386, in do_clicked self.topic_win = self.topic.get_topic_window() File "/usr/lib/python2.4/site-packages/gimmie/gimmie_base.py", line 377, in get_topic_window self.topic_window = TopicWindow(self) File "/usr/lib/python2.4/site-packages/gimmie/gimmie_topicwin.py", line 1131, in __init__ self._add_toolbar_items() File "/usr/lib/python2.4/site-packages/gimmie/gimmie_topicwin.py", line 1155, in _add_toolbar_items for i in self.topic.get_toolbar_items(self.tooltips): File "/usr/lib/python2.4/site-packages/gimmie/gimmie_documents.py", line 396, in get_toolbar_items btn = PlacesMenuButton(tooltips)
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 ***