GNOME Bugzilla – Bug 490777
crash in Deskbar: logout/login again
Last modified: 2007-10-27 16:01:04 UTC
What were you doing when the application crashed? logout/login again 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-386 #1 Sun Oct 14 22:36:54 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks 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 (24 sec old) --------------------- Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default. SESSION_MANAGER=local/zorba:/tmp/.ICE-unix/7341 Initializing gnome-mount extension /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:158: Invalid symbolic color 'tooltip_bg_color' /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:158: error: invalid identifier `tooltip_bg_color', expected valid identifier Window manager warning: "" found in configuration database is not a valid value for keybinding "toggle_shaded" Window manager warning: Failed to read saved session file /home/zorba/.metacity/sessions/default0.ms: Failed to open file '/home/zorba/.metacity/sessions/default0.ms': No such file or directory ** Message: Not starting remote desktop server Launching a SCIM daemon with Socket FrontEnd... Loading simple Config module ... Creating backend ... Loading socket FrontEnd module ... Starting SCIM as daemon ... GTK Panel of SCIM 1.4.7 -------------------------------------------------- Traceback (most recent call last):
+ Trace 173216
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 ***