Jeff Abrahamson on Tue, 4 Dec 2001 16:00:25 +0100 |
On Mon, Dec 03, 2001 at 08:59:38AM -0500, Rupert Heesom wrote: > After booting the PC up again, I found that the desktop didn't come up > properly. It keeps on trying to generate itself, then fails, and tries > again. In the beginning, I was able to get gtop loaded and saw that > nautilus kept on being spawned. > > If I log in as root, all is fine. I don't think root is using nautilus > as desktop manager because the Home Directory icon is a folder, not the > nautilus house. > > It seems to me that the easiest way of getting the normal user account's > desktop working again is to replace nautilus as the desktop manager. > After that I can try to repair nautilus somehow. > > I've looked at all the config files I can think of, but can't see how > the above can be achieved. Also, I have no idea what gnome config files > to look at anyway.... > > I've looked at /var/log/messages after attempting a normal user desktop > load. Included here is what seems to be relevant to the attempt - > > --------------------------------------------------------------- > Dec 2 23:13:37 localhost PAM_unix[4412]: (gdm) session opened for user colin by (uid=0) > Dec 2 23:13:39 localhost gnome-name-server[4626]: starting > Dec 2 23:13:39 localhost gnome-name-server[4626]: name server starting > Dec 2 23:13:43 localhost kernel: cdrom: This disc doesn't have any tracks I recognize! > Dec 2 23:14:10 localhost last message repeated 6 times > Dec 2 23:14:12 localhost gnome-name-server[4626]: input condition is: 0x10, exiting > Dec 2 23:14:12 localhost PAM_unix[4412]: (gdm) session closed for user colin > Dec 2 23:14:12 localhost gdm[4412]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 > > ----------------------------------------------------------------- > > Do the log entries make sense to anyone? I'm stumped! > > Can someone point me in the right direction?? You might try creating a new user and then setting him up with nautilus and gnome. If that fails, it's your installation. If that succeeds, it's a config thing for you personally. In the latter case, try nuking (or if you're very patient, selectively moving aside) config files until it works again. I find it's faster to reconfigure than to fiddle with which config file is right. In the former case, go back to red carpet. But that's a gnarlier case. -- Jeff Jeff Abrahamson <http://www.purple.com/jeff/> ______________________________________________________________________ Philadelphia Linux Users Group - http://www.phillylinux.org Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce General Discussion - http://lists.phillylinux.org/mail/listinfo/plug
|
|