GNOME Bugzilla – Bug 440128
crash in Gimmie: Nothing special
Last modified: 2007-05-23 22:43:14 UTC
What were you doing when the application crashed? Nothing special Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000000 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 (1546 sec old) --------------------- alarm-queue.c:1837 (check_midnight_refresh) alarm-notify.c:349 (alarm_msg_received) - 0x80dbb00: Received at thread b64dcb90 alarm-queue.c:249 (midnight_refresh_async) alarm-queue.c:256 (midnight_refresh_async) - Reschedule the midnight update alarm-queue.c:1856 (check_midnight_refresh) - Posting a task to refresh alarm-queue.c:218 (queue_midnight_refresh) - Refresh at Tue May 22 02:00:00 2007 alarm-notify.c:349 (alarm_msg_received) - 0x80dca28: Received at thread b64dcb90 alarm-queue.c:249 (midnight_refresh_async) alarm-notify.c:337 (alarm_msgport_replied) - 0x80dbb00: Replied to GUI thread alarm-queue.c:218 (queue_midnight_refresh) evolution-alarm-notify-Message: Setting timeout for 54719 1179792000 1179737281 evolution-alarm-notify-Message: Tue May 22 02:00:00 2007 evolution-alarm-notify-Message: Mon May 21 10:48:01 2007 -------------------------------------------------- Traceback (most recent call last):
+ Trace 135302
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 ***