GNOME Bugzilla – Bug 515160
crash in File Browser: starting the system
Last modified: 2008-02-08 11:12:21 UTC
Version: 2.18.3 What were you doing when the application crashed? starting the system Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 76148736 vsize: 76148736 resident: 21610496 share: 17960960 rss: 21610496 rss_rlim: 4294967295 CPU usage: start_time: 1202460062 rtime: 37 utime: 29 stime: 8 cutime:0 cstime: 0 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 -1208621344 (LWP 2974)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 188515
Thread 1 (Thread -1208621344 (LWP 2974))
----------- .xsession-errors (6 sec old) --------------------- localuser:marascalchie being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2859 ** Message: failed to load session from /home/marascalchie/.nautilus/saved-session-TDQHTT (nautilus:2974): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000058 (Lista cont) Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --------------------------------------------------
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 439977 ***