GNOME Bugzilla – Bug 503487
crash in Deskbar: Deparately trying to rec...
Last modified: 2007-12-16 19:25:34 UTC
What were you doing when the application crashed? Deparately trying to reconfigure my xorg.conf settings. using sudo dpkg-reconfigure xserver-xorg 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 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: (null) Icon Theme: (null) 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 (224 sec old) --------------------- most likely the X server was shut down or you killed/destroyed the application. Window manager warning: Fatal IO error 104 (Connection reset by peer) on display ':2.0'. (gnome-panel:6830): GLib-GObject-CRITICAL **: g_object_run_dispose: assertion `G_IS_OBJECT (object)' failed (gnome-panel:6830): GLib-GObject-CRITICAL **: g_object_run_dispose: assertion `G_IS_OBJECT (object)' failed The application 'awn-applet-activation' lost its connection to the display :2.0; most likely the X server was shut down or you killed/destroyed the application. The application 'awn-applet-activation' lost its connection to the display :2.0; most likely the X server was shut down or you killed/destroyed the application. stacks_applet.py: Fatal IO error 104 (Connection reset by peer) on X server :2.0. awn-applet-activation: Fatal IO error 104 (Connection reset by peer) on X server :2.0. -------------------------------------------------- Traceback (most recent call last):
+ Trace 181802
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 ***