GNOME Bugzilla – Bug 114486
nautilus segfault on startup on non-root users in VNC
Last modified: 2004-12-22 21:47:04 UTC
From: jay <> To: submit@bugs.gnome.org X-Mailer: bug-buddy 2.2.0 Subject: nautilus segfault on startup on non-root users in VNC Package: nautilus Severity: normal Version: 2.2.1 Synopsis: nautilus segfault on startup on non-root users in VNC Bugzilla-Product: nautilus Bugzilla-Component: Desktop BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: On startup, I see a menu bar, gray desktop with no icons and a dialog box "Application 'nautilus'' (process 1669) has crashed due to a fatal error. (Segmentation fault)" If I open a terminal windoe from the menu and try to launch nautilus manually (nautilus &) i get the same thing. If I su to root and launch nautilus manually, I get no errors. The vnc session for root works perfectly. Steps to reproduce the problem: 1. Try to start nautilus as a non-root user 2. 3. Actual Results: Menu bar, blank desktop, no icons. Expected Results: Menu bar, desktop picture with icons. How often does this happen? Every time Additional Information: Just tried upgrading to latest 2.4.20-18.9 smp kernel no help. 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)...[New Thread 1087926592 (LWP 1669)] (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)...0xffffe002 in ?? ()
+ Trace 37522
Thread 1 (Thread 1087926592 (LWP 1669))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-05 10:29 ------- Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Please read Andrew Sobala's comment in bug 113084. This appears to be a duplicate of that bug, and that bug is a duplicate of has been marked as a duplicate of 111147. So I'm marking as a dup of 111147. *** This bug has been marked as a duplicate of 111147 ***