GNOME Bugzilla – Bug 553844
crash in Deskbar: Booting up?
Last modified: 2008-09-27 11:18:38 UTC
What were you doing when the application crashed? Booting up? Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.1 2008-04-15 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human 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 --------------------- xrdb: "*Text.foreground" on line 238 overrides entry on line 192 Window manager warning: Failed to read saved session file /home/ubuntu/.metacity/sessions/default0.ms: Failed to open file '/home/ubuntu/.metacity/sessions/default0.ms': No such file or directory Connection failure: Connection refused evolution-alarm-notify-Message: Setting timeout for 9840 1222387200 1222377360 evolution-alarm-notify-Message: Fri Sep 26 00:00:00 2008 evolution-alarm-notify-Message: Thu Sep 25 21:16:00 2008 seahorse nautilus module initialized Initializing nautilus-share extension ** (nautilus:15162): WARNING **: Unable to add monitor: Not supported Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or d Please ask your system administrator to enable user sharing. -------------------------------------------------- Traceback (most recent call last):
+ Trace 207350
tray = DeskbarTray(applet)
self.__setup_mvc()
self.__core.run()
self._setup_keybinder()
self.set_keybinding( self.get_keybinding() )
self._gconf.set_keybinding(binding)
self._client.set_string(self.GCONF_KEYBINDING, binding)
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 486549 ***