GNOME Bugzilla – Bug 479386
crash in Gimmie: opening linux tab
Last modified: 2007-09-23 14:37:21 UTC
What were you doing when the application crashed? opening linux tab 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 Fri Aug 31 00:55:27 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks 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 (57 sec old) --------------------- alarm-queue.c:560 (load_alarms_for_today) - From Sat Sep 22 20:00:01 2007 to Sat Sep 22 20:00:01 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:516 (load_alarms) -evolution-alarm-notify-Message: alarm.c:235: Requested removal of nonexistent alarm! evolution-alarm-notify-Message: Setting timeout for 86400 1190592000 1190505600 evolution-alarm-notify-Message: Sun Sep 23 20:00:00 2007 evolution-alarm-notify-Message: Sat Sep 22 20:00:00 2007 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c0003e (Desktop Se) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. ** (gnome-system-monitor:30119): WARNING **: SELinux was found but is not enabled. -------------------------------------------------- Traceback (most recent call last):
+ Trace 164735
self._show()
self.topic_win = self.topic.get_topic_window()
self.topic_window = TopicMenu(self)
TopicView.__init__(self, topic)
self.sidebar = Sidebar(topic)
gtk.VBox.__init__(self, False, 4)
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 416060 ***