GNOME Bugzilla – Bug 504863
crash in Deskbar: Starting my gnome sessio...
Last modified: 2007-12-25 11:51:59 UTC
What were you doing when the application crashed? Starting my gnome session. Previous start said there was an error starting the Gnome settings daemon. I get that error from time to time. 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: Clearlooks Icon Theme: gnome 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 --------------------- alarm-queue.c:2003 (alarm_queue_add_async) - 0x80be410 alarm-queue.c:581 (load_alarms_for_today) - From Fri Dec 21 08:20:03 2007 to Fri Dec 21 08:20:03 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x814ab50: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80c04e8: Received at thread b5de1b90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80a6100 alarm-queue.c:581 (load_alarms_for_today) - From Fri Dec 21 08:20:03 2007 to Fri Dec 21 08:20:03 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80c04e8: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x8185848: -------------------------------------------------- Traceback (most recent call last):
+ Trace 182529
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 ***