GNOME Bugzilla – Bug 437145
crash in Deskbar:
Last modified: 2007-05-09 13:52:28 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Glider Icon Theme: clear 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 (14 sec old) --------------------- alarm-notify.c:337 (alarm_msgport_replied) - 0x810f780: Replied to GUI thread alarm-queue.c:evolution-alarm-notify-Message: Setting timeout for 34815 1178751600 1178716785 evolution-alarm-notify-Message: Thu May 10 00:00:00 2007 evolution-alarm-notify-Message: Wed May 9 14:19:45 2007 inotify_add_watch: No such file or directory (gnome-panel:7097): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -15 and height 24 (evolution-2.10:7119): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution-2.10:7119): e-utils-WARNING **: Plugin 'Bogofilter junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0' ** (evolution-2.10:7119): DEBUG: mailto URL command: evolution %s ** (evolution-2.10:7119): DEBUG: mailto URL program: evolution -------------------------------------------------- Traceback (most recent call last):
+ Trace 133256
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)
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 for tracker. *** This bug has been marked as a duplicate of 403752 ***