GNOME Bugzilla – Bug 617148
crash in Deskbar: Add the deskbar on the p...
Last modified: 2010-04-29 02:25:51 UTC
What were you doing when the application crashed? Add the deskbar on the panel Distribution: Ubuntu 10.04 (lucid) Gnome Release: 2.30.0 2010-03-31 (Ubuntu) BugBuddy Version: 2.28.0 System: Linux 2.6.34-1-386 #4~oga1-Ubuntu SMP Fri Apr 23 02:36:29 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10800000 Selinux: No Accessibility: Disabled GTK+ Theme: elementary Icon Theme: elementary-monochrome GTK+ Modules: globalmenu-plugin 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 Traceback (most recent call last):
+ Trace 221606
from deskbar.ui.DeskbarApplet import DeskbarApplet
from deskbar.ui.AbstractCuemiacDeskbarIcon import AbstractCuemiacDeskbarIcon
from deskbar.ui.CuemiacWindowController import CuemiacWindowController
from deskbar.ui.preferences.DeskbarPreferences import DeskbarPreferences
from deskbar.ui.preferences.AccelEntry import AccelEntry
----------- .xsession-errors --------------------- ** (gnome-settings-daemon:2220): WARNING **: Connection failed, reconnecting... ** (gnome-settings-daemon:2220): WARNING **: Connection failed, reconnecting... ** (gnome-settings-daemon:2220): WARNING **: Connection failed, reconnecting... ** (gnome-settings-daemon:2220): WARNING **: Connection failed, reconnecting... ** (gnome-settings-daemon:2220): WARNING **: Connection failed, reconnecting... ** (gnome-settings-daemon:2220): WARNING **: Connection failed, reconnecting... ** (gnome-settings-daemon:2220): WARNING **: Connection failed, reconnecting... ** (gnome-settings-daemon:2220): WARNING **: Connection failed, reconnecting... --------------------------------------------------
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 bug 612990 ***