GNOME Bugzilla – Bug 470805
crash in Deskbar: My gnome session was sta...
Last modified: 2007-12-26 18:22:22 UTC
What were you doing when the application crashed? My gnome session was starting. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.6 2007-08-14 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 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 (19 sec old) --------------------- Checking for Xgl: not present. Tracker version 0.6.1 Copyright (c) 2005-2006 by Jamie McCracken (jamiemcc@gnome.org) This program is free software and comes without any warranty. It is licensed under version 2 or later of the General Public License which can be viewed at http://www.gnu.org/licenses/gpl.txt Initialising tracker... throttle level is 0 ERROR: while reading file /usr/share/tracker/sqlite-stored-procs.sql on line 170 Initializing gnome-mount extension ** Message: Not starting remote desktop server PID TTY TIME CMD /usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format -------------------------------------------------- Traceback (most recent call last):
+ Trace 158265
text = action.get_verb () % action.get_escaped_name(text)
for key, value in self.get_name(text).items():
return {"name": self._name, "program": self._display_program_name}
*** Bug 470806 has been marked as a duplicate of this bug. ***
*** Bug 470807 has been marked as a duplicate of this bug. ***
*** Bug 470850 has been marked as a duplicate of this bug. ***
*** Bug 470851 has been marked as a duplicate of this bug. ***
*** Bug 470856 has been marked as a duplicate of this bug. ***
*** Bug 470867 has been marked as a duplicate of this bug. ***
*** Bug 470868 has been marked as a duplicate of this bug. ***
*** Bug 470870 has been marked as a duplicate of this bug. ***
*** Bug 470882 has been marked as a duplicate of this bug. ***
*** Bug 470883 has been marked as a duplicate of this bug. ***
*** Bug 470891 has been marked as a duplicate of this bug. ***
*** Bug 470892 has been marked as a duplicate of this bug. ***
*** Bug 470903 has been marked as a duplicate of this bug. ***
*** Bug 470905 has been marked as a duplicate of this bug. ***
*** Bug 470917 has been marked as a duplicate of this bug. ***
*** Bug 470919 has been marked as a duplicate of this bug. ***
*** Bug 470920 has been marked as a duplicate of this bug. ***
*** Bug 470935 has been marked as a duplicate of this bug. ***
*** Bug 470936 has been marked as a duplicate of this bug. ***
*** Bug 470943 has been marked as a duplicate of this bug. ***
*** Bug 470949 has been marked as a duplicate of this bug. ***
*** Bug 470956 has been marked as a duplicate of this bug. ***
*** Bug 470961 has been marked as a duplicate of this bug. ***
*** Bug 470971 has been marked as a duplicate of this bug. ***
*** Bug 470974 has been marked as a duplicate of this bug. ***
*** Bug 470976 has been marked as a duplicate of this bug. ***
*** Bug 470979 has been marked as a duplicate of this bug. ***
*** Bug 470980 has been marked as a duplicate of this bug. ***
*** Bug 470981 has been marked as a duplicate of this bug. ***
*** Bug 470984 has been marked as a duplicate of this bug. ***
*** Bug 470986 has been marked as a duplicate of this bug. ***
*** Bug 470992 has been marked as a duplicate of this bug. ***
*** Bug 470995 has been marked as a duplicate of this bug. ***
*** Bug 470996 has been marked as a duplicate of this bug. ***
*** Bug 470997 has been marked as a duplicate of this bug. ***
*** Bug 470999 has been marked as a duplicate of this bug. ***
*** Bug 471002 has been marked as a duplicate of this bug. ***
*** Bug 471020 has been marked as a duplicate of this bug. ***
*** Bug 471045 has been marked as a duplicate of this bug. ***
*** Bug 471049 has been marked as a duplicate of this bug. ***
*** Bug 471050 has been marked as a duplicate of this bug. ***
*** Bug 471066 has been marked as a duplicate of this bug. ***
*** Bug 471069 has been marked as a duplicate of this bug. ***
*** Bug 471071 has been marked as a duplicate of this bug. ***
*** Bug 471072 has been marked as a duplicate of this bug. ***
*** Bug 471073 has been marked as a duplicate of this bug. ***
*** Bug 471074 has been marked as a duplicate of this bug. ***
*** Bug 471075 has been marked as a duplicate of this bug. ***
*** Bug 471079 has been marked as a duplicate of this bug. ***
*** Bug 471080 has been marked as a duplicate of this bug. ***
*** Bug 471084 has been marked as a duplicate of this bug. ***
*** Bug 471086 has been marked as a duplicate of this bug. ***
Comment from bug 471086: "Looks like history format migration issues. Removing the deskbar history file(s) solved the problem for me."
*** Bug 471116 has been marked as a duplicate of this bug. ***
*** Bug 471105 has been marked as a duplicate of this bug. ***
*** Bug 471104 has been marked as a duplicate of this bug. ***
*** Bug 471103 has been marked as a duplicate of this bug. ***
*** Bug 471102 has been marked as a duplicate of this bug. ***
*** Bug 471100 has been marked as a duplicate of this bug. ***
*** Bug 471094 has been marked as a duplicate of this bug. ***
*** Bug 471141 has been marked as a duplicate of this bug. ***
*** Bug 471139 has been marked as a duplicate of this bug. ***
*** Bug 471138 has been marked as a duplicate of this bug. ***
*** Bug 471120 has been marked as a duplicate of this bug. ***
*** Bug 470842 has been marked as a duplicate of this bug. ***
The class changed, but the old one is stored in the history file. Delete your history file at ~/.gnome2/deskbar-applet and it works again.
(In reply to comment #66) > The class changed, but the old one is stored in the history file. > Delete your history file at ~/.gnome2/deskbar-applet and it works again. That's a good workaround, but was there a commit that will prevent this from occurring when upgrading?