GNOME Bugzilla – Bug 472684
crash in Deskbar: attempting to load the c...
Last modified: 2007-09-03 18:17:59 UTC
What were you doing when the application crashed? attempting to load the command replace --compiz 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: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: ThinIce Icon Theme: crystalsvg 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:519 (load_alarms) alarm-queue.c:548 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80d3788: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80d85a0: Received at thread b4de0b90 alarm-queue.c:2004 (alarm_queue_add_async) - 0x80bae40 alarm-queue.c:582 (load_alarms_for_today) - From Sat Sep 1 18:30:55 2007 to Sat Sep 1 18:30:55 2007 alarm-queue.c:519 (load_alarms) alarm-queue.c:548 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80d85a0: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/baekeland/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2053 (alarm_queue_add_client) - Posting a task alarm-notify.c:3 (gnome-panel:11459): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -19 and height 26 -------------------------------------------------- Traceback (most recent call last):
+ Trace 159718
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 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 466543 ***