GNOME Bugzilla – Bug 482024
crash in Deskbar: Happens on boot
Last modified: 2007-10-01 10:38:35 UTC
What were you doing when the application crashed? Happens on boot 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: Glossy Icon Theme: gnome 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 (476 sec old) --------------------- alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80df498: 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) - 0x80dfd98: Received/usr/bin/compiz.real (core) - Warn: No GLXFBConfig for depth 32 /usr/bin/compiz.real (resizeinfo) - Warn: Bind Pixmap to Texture failure /usr/bin/compiz.real (core) - Warn: No GLXFBConfig for depth 32 /usr/bin/compiz.real (resizeinfo) - Warn: Bind Pixmap to Texture failure /usr/bin/compiz.real (core) - Warn: No GLXFBConfig for depth 32 /usr/bin/compiz.real (resizeinfo) - Warn: Bind Pixmap to Texture failure /usr/bin/compiz.real (core) - Warn: No GLXFBConfig for depth 32 /usr/bin/compiz.real (resizeinfo) - Warn: Bind Pixmap to Texture failure /usr/bin/compiz.real (core) - Warn: No GLXFBConfig for depth 32 /usr/bin/compiz.real (core) - Warn: No GLXFBConfig for depth 32 /usr/bin/compiz.real (core) - Warn: No GLXFBConfig for depth 32 -------------------------------------------------- Traceback (most recent call last):
+ Trace 166726
self._history.load()
saved_history = cPickle.load(file(HISTORY_FILE)) EOFError
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 470985 ***