GNOME Bugzilla – Bug 453769
crash in Deskbar: Uprgaded to Feisty. Res...
Last modified: 2007-07-05 08:32:04 UTC
What were you doing when the application crashed? Uprgaded to Feisty. Restarted system at the end of upgrade process Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-386 #2 Thu Jun 7 20:16:13 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Glider 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 (10 sec old) --------------------- /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "ssteinbr" /etc/gdm/Xsession: Beginning session setup... /etc/X11/Xsession.d/40guidance-displayconfig_restore: 11: /usr/bin/displayconfig-restore: not found SESSION_MANAGER=local/dude:/tmp/.ICE-unix/5710 exec: 136: ~/.gnome-compiz-manager/openbox: not found Initializing gnome-mount extension ** (nautilus:5815): WARNING **: Can not caclulate _NET_NUMBER_OF_DESKTOPS ** (nautilus:5815): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS ** (nautilus:5815): WARNING **: Can not get _NET_WORKAREA ** (nautilus:5815): WARNING **: Can not determine workarea, guessing at layout -------------------------------------------------- Traceback (most recent call last):
+ Trace 145754
self.load (f)
mod_instance = getattr (mod, handler) ()
self.proxy_obj = self.bus.get_object('org.freedesktop.Tracker', '/org/freedesktop/tracker')
follow_name_owner_changes=follow_name_owner_changes)
_dbus_bindings.UInt32(0))
reply_message = self._connection.send_message_with_reply_and_block(message, timeout)
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 403752 ***