GNOME Bugzilla – Bug 488510
crash in Deskbar: Logging in.
Last modified: 2007-10-20 08:57:53 UTC
What were you doing when the application crashed? Logging in. 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: Glossy Icon Theme: Tangerine 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) - 0x80e03e0: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/elfortunawe/.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) - 0x80df000: Received at thread b4d75b90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80d53a0 alarm-queue.c:581 (load_alarms_for_today) - From Fri Oct 19 23:38:37 2007 to Fri Oct 19 23:38:37 2007 alarm-queue.c:518 (load_alarm/usr/bin/compiz.real (colorfilter) - Info: Loading filter negative-green (item negative-green). /usr/bin/compiz.real (colorfilter) - Info: Loading filter blueish-filter (item blueish-filter). /usr/bin/compiz.real (colorfilter) - Info: Loading filter sepia (item sepia). /usr/bin/compiz.real (colorfilter) - Info: Loading filter grayscale (item grayscale). /usr/bin/compiz.real (colorfilter) - Warn: Tried to load 5 filter(s), 3 succeeded. (gnome-panel:5516): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -4 and height 24 -------------------------------------------------- Traceback (most recent call last):
+ Trace 171614
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 ***