GNOME Bugzilla – Bug 449763
crash in Deskbar: crash just after nautilu...
Last modified: 2007-06-26 17:35:03 UTC
What were you doing when the application crashed? crash just after nautilus startup on session login Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: OSX-theme Icon Theme: OSX 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 --------------------- (avant-window-navigator:10463): Gnome-CRITICAL **: gnome_program_locate_file: assertion `program != NULL' failed (avant-window-navigator:10463): Gnome-CRITICAL **: gnome_program_locate_file: assertion `program != NULL' failed (avant-window-navigator:10463): Gnome-CRITICAL **: gnome_program_locate_file: assertion `program != NULL' failed LOADED : /usr/share/applications/pidgin.desktop LOADED : /usr/share/applications/amule.desktop LOADED : /usr/share/applications/gnome-terminal.desktop LOADED : /usr/share/applications/gimp-2.2.desktop LOADED : /usr/share/applications/quodlibet.desktop APPLET : /usr/lib/awn/applets/taskman.desktop APPLET : /usr/lib/awn/applets/trash.desktop inotify_add_watch: No such file or directory (gnome-panel:10428): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -19 and height 24 -------------------------------------------------- Traceback (most recent call last):
+ Trace 142653
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. *** This bug has been marked as a duplicate of 403752 ***