GNOME Bugzilla – Bug 622389
crash in Deskbar: Doing an update
Last modified: 2010-06-22 19:46:59 UTC
What were you doing when the application crashed? Doing an update Distribution: Ubuntu 10.04 (lucid) Gnome Release: 2.30.0 2010-03-31 (Ubuntu) BugBuddy Version: 2.28.0 System: Linux 2.6.31-22-generic #60-Ubuntu SMP Thu May 27 00:22:23 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10706000 Selinux: No Accessibility: Disabled GTK+ Theme: Ambiance Icon Theme: ubuntu-mono-dark GTK+ Modules: canberra-gtk-module 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 222525
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 (16 sec old) --------------------- Tracker-Message: Registering DBus service... Name:'org.freedesktop.Tracker' Starting log: File:'/home/dorlan/.local/share/tracker/trackerd.log' Unable to find a synaptics device. ** (nm-applet:24060): WARNING **: _nm_object_get_property: Error getting 'WwanHardwareEnabled' for /org/freedesktop/NetworkManager: (16) No such property WwanHardwareEnabled /usr/bin/compiz (core) - Fatal: Support for non power of two textures missing /usr/bin/compiz (core) - Error: Failed to manage screen: 0 /usr/bin/compiz (core) - Fatal: No manageable screens found on display :0.0 ** (nm-applet:24060): DEBUG: old state indicates that this was not a disconnect 0 Failure: Module initalization failed Initializing nautilus-gdu extension Unable to open desktop file evolution-mail.desktop for panel launcher --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 617299 ***