GNOME Bugzilla – Bug 530869
crash in Deskbar: just started my computer...
Last modified: 2008-05-01 12:25:08 UTC
What were you doing when the application crashed? just started my computer, nothing else Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.21.92 2008-03-04 (Ubuntu) BugBuddy Version: 2.21.90 System: Linux 2.6.24-11-generic #1 SMP Fri Feb 29 22:08:31 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome 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 (122 sec old) --------------------- ** (gnome-settings-daemon:10459): DEBUG: Starting keybindings manager ** (gnome-settings-daemon:10459): DEBUG: Plugin keybindings: active ** (gnome-settings-daemon:10459): DEBUG: GnomeSettingsModule 0x8057318 initialising ** (gnome-settings-daemon:10459): DEBUG: Loading /usr/lib/gnome-settings-daemon-2.0/libxrdb.so ** (gnome-settings-daemon:10459): DEBUG: Registering GsdXrdbPlugin ** (gnome-settings-daemon:10459): DEBUG: Creating object of type GsdXrdbPlugin ** (gnome-settings-daemon:10459): DEBUG: GsdXrdbPlugin initializing ** (gnome-settings-daemon:10459): DEBUG: Activating xrdb plugin ** (gnome-settings-daemon:10459): DEBUG: Plugin xrdb: active ** (gnome-settings-daemon:10459): WARNING **: Error opening directory '/etc/gnome/config': No such file or directory ** (gnome-screensaver:10685): WARNING **: screensaver already running in this session (evolution:10159): Gdk-WARNING **: gdk_xsettings_watch_cb(): Couldn't find window to unwatch -------------------------------------------------- Traceback (most recent call last):
+ Trace 196589
self.load (f)
modules = self.import_module (filename)
if not getattr(module, "has_requirements" )():
if is_preferred_browser("epiphany"):
if http_handler.find(test) != -1:
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 518941 ***