GNOME Bugzilla – Bug 488603
crash in Open Folder: just logging in
Last modified: 2007-10-20 14:42:20 UTC
Version: 2.18.3 What were you doing when the application crashed? just logging in Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-4.fc7 #1 SMP Fri Oct 12 20:26:14 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks_Cairo-Hedgehog Icon Theme: Neu Memory status: size: 76922880 vsize: 76922880 resident: 22552576 share: 17145856 rss: 22552576 rss_rlim: 4294967295 CPU usage: start_time: 1192884398 rtime: 27 utime: 24 stime: 3 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 -1208527136 (LWP 4126)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 171686
Thread 1 (Thread -1208527136 (LWP 4126))
----------- .xsession-errors --------------------- SESSION_MANAGER=local/unix:/tmp/.ICE-unix/4007 Tracker version 0.6.3 Copyright (c) 2005-2007 by Jamie McCracken (jamiemcc@gnome.org) This program is free software and comes without any warranty. It is licensed under version 2 or later of the General Public License which can be viewed at http://www.gnu.org/licenses/gpl.txt Initialising tracker... Could not set idle IO priority...attempting best effort 7 priority Throttle level is 0 Initializing nautilus-open-terminal extension ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name (nautilus:4126): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed --------------------------------------------------
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 439977 ***