Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I just had a very strange thing happen...while i was working, the icons disappeared from my gnome desktop. i thought it was a bit odd, but everything seemed to be working fine, so i ignored it. when i restarted X though, i got the following error message before being dropped back to command line:
could not resolve the address "xml:readwrite:/home/mcd/.gconf" in the configuration file "/etc/gconf/2/path": Failed to create or open '/home/mcd/.gconf/%gconf-xml-backend.lock/ior'
and when i ended up back at promt, these were the last messages visible:
cat: /home/mcd/.Xauthority: no such file or directory
gconf-sanity-check-2 did not pass. logging back out
xauth: error in locking authority file /home/mcd/.Xauthority
I checked, and there was no ior file in the %gconf-xml-backend.lock directory. in my home directory, there was .Xauthority-c but not .Xauthority. i tried renaming that file, but i still get the same message.
i can still startx as any other user, just not mcd
does anyone know what's going on here? i'm totally lost!
I don't have any answers, but a similar (not identical) thing happened to me. The first trouble I noticed was that it took approx. 30 sec instead of about one second to su to root in a virtual terminal. I wondered if starting my X session over would fix that, so I logged out, issued "startx" and X wouldn't start, due to "timeout locking .Xauthority." After several attempts with same result, I went to fix a glass of Diet Sprite. When I got back, X had started up and everything appeared normal. Apparently the "timeout" didn't matter so much! Another mystery...
Then I found I couldn't access my home directory in Midnight Commander, as jon, but I could do it as root (after waiting 30 sec. again for the su to take effect...). Puzzleder and puzzleder, I finally, after several more denials from ls and from mc when I was jon, I became root and changed ownership of the /home directory to jon. Result: everything is at normal speed again, and I can see my files, etc. as jon.
Which is nice, but makes me wonder what kind of security considerations are involved here! If any. And just what was going on in the first place. I notice the .Xauthority file was last modified at 11:57 AM yesterday--I have no idea what I was doing then, but I've been able to view my own directories many times in between, so something else happened between now and then.