GNOME Bugzilla – Bug 433065
crash in Gimmie: Trying to open it
Last modified: 2007-05-13 23:07:14 UTC
What were you doing when the application crashed? Trying to open it 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-386 #2 Sun Apr 15 07:34:00 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: T-ish-Ubuntulooks Icon Theme: OSX 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 (896 sec old) --------------------- alarm-notify.c:393 (cal_opened_cb) file:///home/david/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x80e9098: Received at thread b35c2b90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80d7e50 alarm-notify.c:337 (alarm_msgport_replied) - 0x80d7738: Replied to GUI thread alarm-queue.c:560 (load_alarms_for_today) - From Tue Apr 24 13:28:33 2007 to Tue Apr 24 13:28:33 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80e9098: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80d85c0: Connecting to daemon [ ### ] Connecting to daemon [ ### ] Connecting to daemon [ ### ] Connecting to daemon [ ### ] -------------------------------------------------- Traceback (most recent call last):
+ Trace 130321
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 the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 416060 ***