GNOME Bugzilla – Bug 504043
crash in Deskbar: Reading address book wit...
Last modified: 2007-12-19 04:34:04 UTC
What were you doing when the application crashed? Reading address book with Evolution Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (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: Clearlooks 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 --------------------- alarm-notify.c:393 (cal_opened_cb) file:///home/petr/.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) - 0x80eae40: Received at thread b33ffb90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80e5550 alarm-queue.c:581 (load_alarms_for_today) - From Mon Dec 17 00:00:00 2007 to Mon Dec 17 00:00:00 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call b (gnome-panel:6201): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 Traceback (most recent call last):
+ Trace 182118
path = gnomevfs.get_local_path_from_uri(file.get_uri())
PID TTY TIME CMD -------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/deskbar/core/CoreImpl.py", line 314, in on_module_initialized self._history.load() File "/usr/lib/python2.5/site-packages/deskbar/core/DeskbarHistory.py", line 113, in 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 474179 ***