GNOME Bugzilla – Bug 471045
crash in Deskbar: I was shooting the cat
Last modified: 2007-08-28 14:22:29 UTC
What were you doing when the application crashed? I was shooting the cat Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.6 2007-08-14 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-10-generic #1 SMP Wed Aug 22 07:42:05 GMT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Blubuntu Icon Theme: Tango 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 (24 sec old) --------------------- alarm-notify.c:337 (alarm_msgport_replied) - 0x6d3790: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/zapek/.evolution/calendar/local/system - Calendar Status 0 alarm-queue.c:2053 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x6cb840: Received at thread 42845950 alarm-queue.c:2004 (alarm_queue_add_async) - 0x6b9460 alarm-queue.c:582 (load_alarms_for_today) - From Tue Aug 28 01:00:00 2007 to Tue Aug 28 01:00:00 2007 alarm-queue.c:519 (load_alarms) alarm-queue.c:548 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x6cb840: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2053 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x6cd5e0: Received at t PID TTY TIME CMD /usr/share/themes/Blubuntu/gtk-2.0/gtkrc:169: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. -------------------------------------------------- Traceback (most recent call last):
+ Trace 158455
text = action.get_verb () % action.get_escaped_name(text)
for key, value in self.get_name(text).items():
return {"name": self._name, "program": self._display_program_name}
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 470805 ***