GNOME Bugzilla – Bug 488585
crash in Deskbar:
Last modified: 2007-10-20 14:25:45 UTC
What were you doing when the application crashed? 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 Sun Oct 14 23:05:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: MurrineSmoothBeige Icon Theme: Oxygen-Refit 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 --------------------- alarm-notify.c:337 (alarm_msgport_replied) - 0x80e49c0: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0xb44007a0: Received at thread b5d64b90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80ebd90 alarm-queue.c:581 (load_alarms_for_today) - From Sat Oct 20 13:55:33 2007 to Sat Oct 20 13:55:33 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0xb44007a0: 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) - 0xb44004/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format Throttle level is 20 Nie można otworzyć pliku /home/pawel/Pulpit/firefox.desktop z aktywatorem panelu: No such file or directory Nie można otworzyć pliku /home/pawel/Pulpit/evolution-mail.desktop z aktywatorem panelu: No such file or directory -------------------------------------------------- Traceback (most recent call last):
+ Trace 171673
self._history.load()
saved_history = cPickle.load(file(HISTORY_FILE))
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 474179 ***