GNOME Bugzilla – Bug 511521
crash in Deskbar:
Last modified: 2008-01-23 16:02:53 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: (null) Icon Theme: Mac4Lin_Icons_v0.4 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 (148 sec old) --------------------- nm-applet: Fatal IO error 104 (Connection reset by peer) on X server :0.0. avant-window-navigator: Fatal IO error 104 (Connection reset by peer) on X server :0.0. x-session-manager: Fatal IO error 104 (Connection reset by peer) on X server :0.0. not present. Trying again with indirect rendering: Checking for texture_from_pixmap: evolution-alarm-notify: Fatal IO error 104 (Connection reset by peer) on X server :0.0. (vino-session:5565): GnomeUI-WARNING **: While connecting to session manager: IO error occured opening connection. (update-notifier:5571): GnomeUI-WARNING **: While connecting to session manager: IO error occured opening connection. The application 'update-notifier' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. -------------------------------------------------- Traceback (most recent call last):
+ Trace 186480
dapplet = DeskbarApplet(applet)
self.__setup_mvc()
self.__core = CoreImpl(deskbar.MODULES_DIRS)
self._gconf = GconfStore.get_instance()
GconfStore.__instance = GconfStore()
self.__connect_notifications()
self._client.add_dir(self.GCONF_DIR, gconf.CLIENT_PRELOAD_RECURSIVE)
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 473854 ***