GNOME Bugzilla – Bug 522180
crash in Deskbar: I was starting ubuntu fr...
Last modified: 2008-03-13 09:49:02 UTC
What were you doing when the application crashed? I was starting ubuntu from usb-install Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 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: 10300000 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 --------------------- aborting and using fallback: /usr/bin/metacity Avertissement du gestionnaire de fenêtres : La lecture du fichier de session enregistré /home/ubuntu/.metacity/sessions/default0.ms a échoué : L'ouverture du fichier « /home/ubuntu/.metacity/s ** Message: Pas de lancement du serveur du bureau à distance Initializing gnome-mount extension (gnome-panel:14586): Gtk-WARNING **: Attempting to read the recently used resources file at `/home/ubuntu/.recently-used.xbel', but the parser failed: L'ouverture du fichier « /home/ubuntu/.recently (gnome-panel:14586): GLib-CRITICAL **: g_bookmark_file_get_size: assertion `bookmark != NULL' failed (gnome-panel:14586): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -25 and height 24 evolution-alarm-notify-Message: Setting timeout for 57110 1205452800 1205395690 evolution-alarm-notify-Message: Fri Mar 14 00:00:00 2008 evolution-alarm-notify-Message: Thu Mar 13 08:08:10 2008 -------------------------------------------------- Traceback (most recent call last):
+ Trace 192285
dapplet = DeskbarApplet(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 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 486549 ***