GNOME Bugzilla – Bug 473612
crash in Deskbar: Started computer. Deskba...
Last modified: 2007-09-05 04:06:27 UTC
What were you doing when the application crashed? Started computer. Deskbar didn't start. Running gutsy. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.6 2007-08-14 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000000 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: SphereCrystal 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 (10 sec old) --------------------- to Tue Sep 4 23:36:59 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80d9b50: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80e04e8: Received at thread b562ab90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80d7e30 alarm-queue.c:581 (load_alarms_for_today) - From Tue Sep 4 23:36:59 2007 to Tue Sep 4 23:36:59 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80e04e8: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/matt/.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) - 0x80dc2b8: Received -------------------------------------------------- Traceback (most recent call last):
+ Trace 160413
dapplet = DeskbarApplet(applet)
self.__setup_mvc()
self.__core.run()
self._setup_keybinder()
self.set_keybinding( self.get_keybinding() )
if not self._keybinder.bind(binding):
self.bound = deskbar.core.keybinder.tomboy_keybinder_bind(keybinding, self.on_keyboard_shortcut)
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 466543 ***