GNOME Bugzilla – Bug 481703
crash in Deskbar: Open preferences menu
Last modified: 2007-09-30 10:10:08 UTC
What were you doing when the application crashed? Open preferences menu Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 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 (258 sec old) --------------------- ** (evince:6625): WARNING **: Failed to connect to socket /tmp/dbus-hrtsCoEFPd: Conexión rechazada (evince:6625): Gtk-WARNING **: Unable to parse accelerator 'ZOOM_IN_ACCEL' for action 'ViewZoomIn' (evince:6625): Gtk-WARNING **: Unable to parse accelerator 'ZOOM_OUT_ACCEL' for action 'ViewZoomOut' (evince:6625): Gtk-WARNING **: Unable to parse accelerator 'FULLSCREEN_ACCEL' for action 'ViewFullscreen' (evince:6625): Gtk-WARNING **: Unable to parse accelerator 'PRESENTATION_ACCEL' for action 'ViewPresentation' /bin/sh: /usr/bin/esd: not found *** CLB *** Initializing Google Browser Sync... *** CLB *** Instanciating core objects... *** CLB *** Registering with XPCOM... *** CLB *** Adding categories... *** CLB *** Google Browser Sync initialized succesfully! -------------------------------------------------- Traceback (most recent call last):
+ Trace 166490
("Prefs", lambda a,b: self.__controller.on_show_preferences(a)),
prefs = DeskbarPreferences(self._model)
self.__enable_newstuffmanager( self.__is_nsm_available() )
bus = dbus.SessionBus()
mainloop=mainloop)
bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
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 366899 ***