GNOME Bugzilla – Bug 488627
crash in Gimmie: i right-clicked on the b...
Last modified: 2007-10-21 21:35:48 UTC
What were you doing when the application crashed? i right-clicked on the bibliothek 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 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: Human Icon Theme: Human 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 (598 sec old) --------------------- alarm-notify.c:337 (alarm_msgport_replied) - 0x80e26e8: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/michael/.evolution/calendar/local/system - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80dc9b8: Received at thread b3d61b90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80bf050 alarm-queue.c:560 (load_alarms_for_today) - From Sat Oct 20 16:29:56 2007 to Sat Oct 20 16:29:56 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80dc9b8: 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_rece Verbinden mit Daemon [ ### ] Verbinden mit Daemon [ ### ] Verbinden mit Daemon [ ### ] Verbinden mit Daemon [ ### ] Verbinden mit Dae Verbinden mit Daemon [ ### ] Verbinden mit Daemon [ ### ] Verbinden mit Daemon [ ### ] Verbinden mit Daemon [ ### ] Verbinden mit Daemon [ ### ] Verbinden mit -------------------------------------------------- Traceback (most recent call last):
+ Trace 171706
for mi in self.topic.get_context_menu_items():
self._add_templates(menu)
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 413620 ***