GNOME Bugzilla – Bug 412178
crash in Deskbar: Just after boot up
Last modified: 2007-02-26 14:57:14 UTC
What were you doing when the application crashed? Just after boot up Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.17.91 2007-02-12 (Ubuntu) BugBuddy Version: 2.17.3 System: Linux 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled 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 --------------------- (evolution-2.10:10000): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", (evolution-2.10:10000): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", (evolution-2.10:10000): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", (evolution-2.10:10000): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", (evolution-2.10:10000): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", (evolution-2.10:10000): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", (evolution-2.10:10000): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", CalDAV Eplugin starting up ... -------------------------------------------------- Traceback (most recent call last):
+ Trace 113972
self.load (f)
mod_instance = getattr (mod, handler) ()
self.tracker = bus.get_object('org.freedesktop.Tracker','/org/freedesktop/tracker')
follow_name_owner_changes=follow_name_owner_changes)
_dbus_bindings.UInt32(0))
reply_message = self._connection.send_message_with_reply_and_block(message, timeout)
Possible duplicate of 403752.
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 406153 ***
*** Bug 411853 has been marked as a duplicate of this bug. ***