GNOME Bugzilla – Bug 624060
crash in Deskbar: I just upgraded from kar...
Last modified: 2010-07-11 02:04:17 UTC
What were you doing when the application crashed? I just upgraded from karmic to lucid. When I did a restart, the crash happened. Distribution: Ubuntu 10.04 (lucid) Gnome Release: 2.30.2 2010-06-25 (Ubuntu) BugBuddy Version: 2.28.0 System: Linux 2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 07:54:58 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10706000 Selinux: No Accessibility: Enabled GTK+ Theme: Silicon Icon Theme: Tango GTK+ Modules: gail:atk-bridge, 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 222795
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 --------------------- evolution-alarm-notify-Message: Sun Jul 11 00:00:00 2010 evolution-alarm-notify-Message: Sat Jul 10 15:00:48 2010 (evolution-alarm-notify:2905): evolution-alarm-notify-WARNING **: Could not create the alarm notify service factory, maybe it's already running... Traceback (most recent call last): File "/usr/share/system-config-printer/applet.py", line 20, in <module> import cups ImportError: No module named cups Tracker-Message: Checking directory exists:'/home/bwjohnson/.cache/tracker' Tracker-Message: Registering DBus service... Name:'org.freedesktop.Tracker' Starting log: File:'/home/bwjohnson/.local/share/tracker/trackerd.log' --------------------------------------------------
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 ***