GNOME Bugzilla – Bug 471514
crash in Deskbar: i don't know
Last modified: 2007-08-30 02:22:56 UTC
What were you doing when the application crashed? i don't know 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: UbuntuStudio Icon Theme: UbuntuStudio 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 (7 sec old) --------------------- to Wed Aug 29 21:51:36 2007 alarm-queue.c:519 (load_alarms) alarm-queue.c:548 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x80de0e0: Received at thread b43feb90 alarm-queue.c:2004 (alarm_queue_add_async) - 0x80dbd60 alarm-notify.c:337 (alarm_msgport_replied) - 0x80da070: Replied to GUI thread alarm-queue.c:582 (load_alarms_for_today) - From Wed Aug 29 21:51:36 2007 to Wed Aug 29 21:51:36 2007 alarm-queue.c:519 (load_alarms) alarm-queue.c:548 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x80dcea0: Received at thread b43feb90 alarm-queue.c:2004 (alarm_queue_add_async) - 0x80/usr/share/themes/UbuntuStudio/gtk-2.0/gtkrc:214: Unable to locate image file in pixmap_path: "panel.png" /bin/sh: /usr/bin/esd: not found -------------------------------------------------- Traceback (most recent call last):
+ Trace 158822
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 ***