GNOME Bugzilla – Bug 495200
crash in Deskbar: Adding the applet to gno...
Last modified: 2007-12-19 04:34:01 UTC
What were you doing when the application crashed? Adding the applet to gnome panel. Also all of my programs will not show up in the Applications menu bar and my Preferences are gone from the System menu bar. All of this started after a power loss. 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: Human Icon Theme: Human 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 (22 sec old) --------------------- return expatbuilder.parse(file)
+ Trace 176495
result = builder.parseFile(fp)
parser.Parse(buffer, 0)
checking for valid crashreport now (gnome-help:6814): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup. (gnome-help:6814): atk-bridge-WARNING **: IOR not set. (gnome-help:6814): atk-bridge-WARNING **: Could not locate registry ** (nautilus:5950): CRITICAL **: dbus_g_proxy_cancel_call: assertion `pending != NULL' failed -------------------------------------------------- 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)) UnpicklingError: A load persistent id instruction was encountered, but no persistent_load function was specified.
*** Bug 502162 has been marked as a duplicate of this bug. ***
*** Bug 502170 has been marked as a duplicate of this bug. ***
*** Bug 503076 has been marked as a duplicate of this bug. ***
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 ***