GNOME Bugzilla – Bug 483302
crash in Gimmie: clicked linux button
Last modified: 2007-10-05 19:19:31 UTC
What were you doing when the application crashed? clicked linux button 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 Sun Sep 23 19:50:39 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: CortlandChicken Icon Theme: Glossy-Glass 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 (9732 sec old) --------------------- alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) -------------------------------------------------- Traceback (most recent call last):
+ Trace 167658
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 ***