GNOME Bugzilla – Bug 444039
crash in Gimmie: ouverure de gimmie
Last modified: 2007-09-04 21:12:03 UTC
What were you doing when the application crashed? ouverure de gimmie Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-386 #2 Wed May 23 01:42:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: UbuntuStudio Icon Theme: UbuntuStudio 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 --------------------- self.set_menu(PlacesMenu())
+ Trace 138208
device_source = computer.get_source_for_uri("source://Devices")
for source in self.get_sidebar_source_list():
self.do_reload()
source_list.append(AdministrationSource())
self.system_settings_menu_source = self.system_settings_menu_tree.get_toplevel_flat_source()
-------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/gimmie/gimmie_gui.py", line 386, in do_clicked self.topic_win = self.topic.get_topic_window() File "/usr/lib/python2.5/site-packages/gimmie/gimmie_base.py", line 377, in get_topic_window self.topic_window = TopicWindow(self) File "/usr/lib/python2.5/site-packages/gimmie/gimmie_topicwin.py", line 1131, in __init__ self._add_toolbar_items() File "/usr/lib/python2.5/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.5/site-packages/gimmie/gimmie_documents.py", line 396, in get_toolbar_items btn = PlacesMenuButton(tooltips) File "/usr/lib/python2.5/site-packages/gimmie/gimmie_documents.py", line 283, in __init__ self.set_menu(PlacesMenu())
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 421732 ***