GNOME Bugzilla – Bug 99161
nautilus crashes anytime I try to run gnome-control-center
Last modified: 2004-12-22 21:47:04 UTC
Package: nautilus Severity: normal Version: 2.0.7 Synopsis: nautilus crashes anytime I try to run gnome-control-center Bugzilla-Product: nautilus Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.0.5) Description: Description of Problem: After upgrading to gnome2/gdm2 I find that, from within my gnome session, if I try to run gnome-control-center -- nautilus (running to draw my desktop) segfaults. The only thing I can think that makes my box odd is that I've previously run ximian desktop -- though I've tried to remove all the ximian packages. Steps to reproduce the problem: 1. boot machine to gdm2 standard greeter 2. once logged in, go to a console and type gnome-control-center 3. watch it core Actual Results: never see gnome control center, just watch nautilus core over and over until I log out and log back in. Expected Results: gnome-control-center should pop up and let me change my settings How often does this happen? every time. Additional Information: I could provide anything else you need to know -- my email addy is mccorkle@devteam.org Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 1024 (LWP 7201)] [New Thread 2049 (LWP 7202)] [New Thread 1026 (LWP 7203)] [New Thread 2051 (LWP 7204)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x40b01a59 in wait4 () from /lib/libc.so.6
+ Trace 30717
Thread 4 (Thread 2051 (LWP 7204))
Thread 3 (Thread 1026 (LWP 7203))
Thread 1 (Thread 1024 (LWP 7201))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-11-21 01:07 ------- The original reporter (mccorkle@devteam.org) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
*** This bug has been marked as a duplicate of 65109 ***