gconf has various login errors with normal users after upgrade to gnome 2.2 (it happened on 2 different boxes, and I think I'll have to fix the other one). Normal users cannot login to gnome at all. With mine, they all had to do with the /etc/gconf/gconf.xml.mandatory directory. If it was the first user login to gnome after the upgrade, then the directory was missing (and could not be created). If root had actually logged into gnome once, then the directory was there for the next user login, but the permissions were in correct. In both cases, creating the directory or just fixing the permissions solved the problem.
is it reproducable ? i have never seen this myself and we need a reason as to why it happens before we can fix anything.
Duh, since it happened on both machines after the same gnome 2.2 upgrade, then it seems reproducable to me. However, you're the developer, not me :-) I think I have more USE flags than most people (I've never really seen any solid guidance on that; you seem to get a different opinion from everyone you ask). The forum thread above also points to other similar problems (though not identical) that other people had (or still have). Since creating the directory and/or fixing the permissions on said directory fixes the problem, I would have thought my description was plenty good enough to check the gconf ebuild and make sure that stuff gets created properly before the first login. Maybe it has something to do with my use flags (but you're the developer, so how do I know anything). I'll see if I can attach the make.conf files from those machines...
Created attachment 9796 [details] make.conf from athlon-tbird This is the second machine that had the gnome 2.2 gconf login error.
Created attachment 9797 [details] make.conf from k6-2 This is the first machine that had the gnome 2.2 gconf login error.
alright. i think i've got to the bottom of this. it was a misplaced touch command that wasn't doing what it was trained to do. can you try emerging the latest gconf (1.0.8-r4 or 2.2.0) to verify?
I already started an 'emerge -Up gnome' on my third gentoo machine (the oldest) a little while ago, so it should be just in time to pick up the changes. If not, I'll emerge gconf again when it's done.
Well, my emerge must have just missed it, since I got the exact same error... But re-emreging gconf fixed it right up, so it look okay now. Thanks :)
thanks for the verification.
