GNOME Bugzilla – Bug 445500
crash in Gimmie: Clicked the "Linux" butt...
Last modified: 2007-09-04 21:13:40 UTC
What were you doing when the application crashed? Clicked the "Linux" button, nothing happened and Gimmie subsequently crashed. 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-generic #2 SMP Wed May 23 01:46:23 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Tangerine 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 (68 sec old) --------------------- alarm-queue.c:560 (load_alarms_for_today) - From Fri Jun 8 12:51:42 2007 to Fri Jun 8 12:51:42 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80c55c8: Replied tmodinfo: could not find module fglrx (evolution-2.10:32242): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution-2.10:32242): camel-WARNING **: camel_exception_get_id called with NULL parameter. Couldn't open sftp://sune@griffenfeld.dk:22/freebusy.ics: Operation not permitted (evolution-2.10:32242): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution-2.10:32242): camel-WARNING **: camel_exception_get_id called with NULL parameter. -------------------------------------------------- Traceback (most recent call last):
+ Trace 139368
self._show()
self.topic_win = self.topic.get_topic_window()
self.topic_window = TopicMenu(self)
TopicView.__init__(self, topic)
self.sidebar = Sidebar(topic)
self.add_sources()
for source in self.topic.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()
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 ***