GNOME Bugzilla – Bug 486528
crash in Gimmie: music, ff, pidgin going ...
Last modified: 2007-10-14 13:29:59 UTC
What were you doing when the application crashed? music, ff, pidgin going online Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Wed Oct 10 06:00:47 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 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 (287 sec old) --------------------- alarm-notify.c:337 (alarm_msgport_replied) - 0x80dcd18: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/maexd/.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) - 0x80cfc78: Received at thread b4600b90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80cf2b0 alarm-queue.c:581 (load_alarms_for_today) - From Sun Oct 14 12:31:02 2007 to Sun Oct 14 12:31:02 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80cfc78: 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) - 0x80ceb48: PID TTY TIME CMD Message: device: default -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 170114
printer.connect("attributes_changed", lambda p: self.emit("reload"))
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 475020 ***