GNOME Bugzilla – Bug 446610
crash in Open Folder: Just rebooted....
Last modified: 2007-06-12 16:30:42 UTC
Version: 2.18.1 What were you doing when the application crashed? Just rebooted.... Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 77299712 vsize: 77299712 resident: 21123072 share: 18042880 rss: 21123072 rss_rlim: 4294967295 CPU usage: start_time: 1181621139 rtime: 64 utime: 56 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 -1208891680 (LWP 2309)] (no debugging symbols found) 0x00d39402 in __kernel_vsyscall ()
+ Trace 140241
Thread 1 (Thread -1208891680 (LWP 2309))
----------- .xsession-errors (27 sec old) --------------------- localuser:cgr1rhF7x86d1 being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2180 Initializing nautilus-flac-converter extension Initializing nautilus-image-converter extension seahorse nautilus module initialized Initializing nautilus-search-tool extension 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:2309): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name --------------------------------------------------
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 ***