GNOME Bugzilla – Bug 622681
crash in Deskbar:
Last modified: 2010-06-25 10:45:24 UTC
What were you doing when the application crashed? Distribution: Ubuntu 10.04 (lucid) Gnome Release: 2.30.0 2010-03-31 (Ubuntu) BugBuddy Version: 2.28.0 System: Linux 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 22:02:19 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10706000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist 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 222575
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 --------------------- Starting log: File:'/home/tux/.local/share/tracker/trackerd.log' (gnome-power-manager:1827): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.24.1/gobject/gsignal.c:2273: signal `proxy-status' is invalid for instance `0x8b760f8' (gnome-panel:1838): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x895c360 (gnome-panel:1838): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x895c360 Xlib: extension "GLX" missing on display ":0.0". /usr/bin/compiz (core) - Fatal: Root visual is not a GL visual /usr/bin/compiz (core) - Error: Failed to manage screen: 0 /usr/bin/compiz (core) - Fatal: No manageable screens found on display :0.0 Unable to open desktop file evolution-mail.desktop for panel launcher 17 Unable to find a synaptics device. --------------------------------------------------
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 ***