GNOME Bugzilla – Bug 473734
crash in Deskbar:
Last modified: 2007-09-05 04:06:41 UTC
What were you doing when the application crashed? 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 07:42:05 GMT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: default.kde 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) --------------------- Debug: Loading Beagle.Util.Conf+IndexingConfig from indexing.xml Debug: Loading Beagle.Util.Conf+DaemonConfig from daemon.xml /usr/bin/compiz.real (cube) - Warn: Failed to load slide: freedesktop Debug: Loading Beagle.Util.Conf+SearchingConfig from searching.xml /usr/bin/compiz.real (cubecaps) - Warn: Failed to load image: fusioncap.png /usr/bin/compiz.real (cubecaps) - Warn: Failed to load image: compizcap.png inotify_add_watch: No such file or directory /usr/bin/compiz.real (cube) - Warn: Failed to load slide: freedesktop /usr/bin/compiz.real (cubecaps) - Warn: Failed to load image: fusioncap.png /usr/bin/compiz.real (cubecaps) - Warn: Failed to load image: compizcap.png PID TTY TIME CMD ** (soffice:5926): CRITICAL **: GdkPixbuf* ResIdToPixbuf(USHORT): assertion `pSalBitmap != NULL' failed (soffice:5926): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed -------------------------------------------------- Traceback (most recent call last):
+ Trace 160514
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 ***