GNOME Bugzilla – Bug 470587
crash in Home Folder: reiniciando o X
Last modified: 2007-10-19 22:54:01 UTC
What were you doing when the application crashed? reiniciando o X Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.18.1-kanotix-1 #1 SMP PREEMPT Tue Oct 17 06:32:12 CEST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: H2O-gtk2-Ruby Icon Theme: Gion Memory status: size: 66994176 vsize: 66994176 resident: 17784832 share: 11657216 rss: 17784832 rss_rlim: 4294967295 CPU usage: start_time: 1188185609 rtime: 38 utime: 30 stime: 8 cutime:2 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226450752 (LWP 1897)] (no debugging symbols found) 0xb766fbf1 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 158103
Thread 1 (Thread -1226450752 (LWP 1897))
----------- .xsession-errors --------------------- from _gobject import * ImportError: /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so: undefined symbol: _Py_ZeroStruct (nautilus:1897): Nautilus-Python-WARNING **: could not import gobject Initializing gnome-mount extension ** (nautilus:1897): WARNING **: Cannot connect to system bus: org.freedesktop.DBus.Error.FileNotFound : Failed to connect to socket /var/run/dbus/system_bus_socket: Arquivo ou diret\xf3rio n\xe3o enco ** (nautilus:1897): WARNING **: Could not initialize hal context (nautilus:1897): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed (nautilus:1897): GLib-GObject-CRITICAL **: g_object_weak_ref: assertion `G_IS_OBJECT (object)' failed Shutting down gnome-mount extension --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 356181 ***