GNOME Bugzilla – Bug 524358
crash in Deskbar: It happened on system st...
Last modified: 2008-03-25 19:21:57 UTC
What were you doing when the application crashed? It happened on system startup. 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 Feb 12 07:42:25 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glider Icon Theme: Tangerine 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 (8 sec old) --------------------- alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80c5e88: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80c9710: Received at thread b4e63b90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80c90b0 alarm-queue.c:581 (load_alarms_for_today) - From Tue Mar 25 20:56:30 2008 to Tue Mar 25 20:56:30 2008 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80c9710: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/emils/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80f8e50:/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format -------------------------------------------------- Traceback (most recent call last):
+ Trace 193309
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 ***