GNOME Bugzilla – Bug 480089
crash in Gimmie: Open Linux --> Recently ...
Last modified: 2007-09-25 11:11:14 UTC
What were you doing when the application crashed? Open Linux --> Recently Used Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaGilouche Icon Theme: tangogenerator-20070729-1316 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 (102 sec old) --------------------- alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80db820: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/son/.evolution/tasks/local/system - Calendar Status 0 alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80dfd60: Received at thread b460bb90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80dc690 alarm-queue.c:581 (load_alarms_for_today) - From Tue Sep 25 08:23:07 2007 to Tue Sep 25 08:23:07 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80dfd60: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80de870: Received at threa/usr/bin/compiz.real (blur) - Warn: No stencil buffer. Region based blur disabled -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 165265
printer.connect("attributes_changed", lambda p: self.emit("reload"))
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 475020 ***