LinuxQuestions.org - Gnome login problem with mounted /home partition

- Slackware - Installation (https://www.linuxquestions.org/questions/slackware-installation-40/)

- - Gnome login problem with mounted /home partition (https://www.linuxquestions.org/questions/slackware-installation-40/gnome-login-problem-with-mounted-home-partition-130909/)

Gnome login problem with mounted /home partition

I have a fat32 partition for my /home/steve directory which i have managed to allow all users rw access to. The problem is, when i try to log in as steve i get an error saying /home/steve/.gconf could not be found. It also mentions that the lock file could not be set at /home/steve/.gconf/%gconf-xml-backend.lock.ior. Ive tried logging in as root and sshing as the user steve, and i can read and write fine.

Ive tried deleting the .gconf directory and it is successfully recreating it on login so assume the umask in fstab is enough to set the rights.

The .xsession-errors I get only mention the gconf-sanity-check-2 failing. Does this mean that the first one is passing or is gconf-sanity-check-1 used for gconf 1?

The corresponding line in my fstab is as follows:

/dev/hde5 /home/steve vfat defaults,users,umask=000,uid=steve,gid=users 1 0

I read somewhere that NFS and this lock file can cause conflicts, but the partition is local so that shouldnt be a problem should it?

Any help would be greatly appreciated. Im running slackware 9 btw.

Steve

Hi!
I'm not sure why you would want to have your /home partition formatted as vfat (as it can cause problems), but it could be permission errors. You might want to try and unmount your /home partition create a local directory (mkdir /home) and try and login and see what happens.
Do text logins work?

Also, what about running
rm -rf /tmp
to clean out your root directory?
--Taj

Yeah, text based logins work a treat. the partition is mounted to /home/steve rather than just /home. It uses vfat because windows shares the same partition and I need the data on there to be shared.

Making the directory /home/steve and unmounting allows login. If text logins work with the partition mounted though, does this mean the problem is with gnome?

Hi!
What about KDE? Does it work?
--Taj

No, not while mounted. I got the error:

Could not read network connection list from /home/steve/.dcop....
Ensure that DCOP is running.

Ive tried loggin in unmounted into KDE and GNOME and they both work. Hmm, any ideas? KDE managed to create its own folder etc, but thats about it. :confused:

Cheers

steveybaby2

Hi,
Hmmm, that's strange. What does typing xinit do?
--Taj

Just tried it - in text only mode, i can login and xinit with no errors.

Just looked at the .xsession-errors file that was created when I tried to boot into KDE - it contains:

Code:

stderr is not a tty - where are you?

Error: Can not create link from "/home/steve/.kde/tmp-darkstar" to "/tmp/kde-steve"

Error: Can not create link from "/home/steve/.kde/tmp-darkstar" to "/tmp/kde-steveAhPjPc"

Error: Can not create link from "/home/steve/.kde/socket-darkstar" to "/tmp/ksocket-steve"

Error: Can not create link from "/home/steve/.kde/socket-darkstar" to "/tmp/ksocket-steveXJwdXe"

startkde: Starting up...

startkde: Running kpersonalizer...

iceauth:  error in locking authority file /home/steve/.ICEauthority

ICE Connection rejected!



DCOPClient::attachInternal. Attach failed Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed

ICE Connection rejected!



DCOPClient::attachInternal. Attach failed Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed

DCOPServer self-test failed.

iceauth:  error in locking authority file /home/steve/.ICEauthority

Error: Can not create link from "/home/steve/.kde/socket-darkstar" to "/tmp/ksocket-steve"

Error: Can not create link from "/home/steve/.kde/socket-darkstar" to "/tmp/ksocket-stevevGIoC3"

Creating link /home/steve/.kde/socket-darkstar.

kdeinit: Aborting. bind() failed: : Operation not permitted

Could not bind to socket '/home/steve/.kde/socket-darkstar/kdeinit-:0'

kdeinit: Aborting. bind() failed: : Operation not permitted

Could not bind to socket '/home/steve/.kde/socket-darkstar/kdeinit-:0'

QFont::setPointSize: Point size <= 0 (-3)

kdeinit: Aborting. bind() failed: : Operation not permitted

Could not bind to socket '/home/steve/.kde/socket-darkstar/kdeinit-:0'

Warning: connect() failed: : No such file or directory

kdeinit: Aborting. bind() failed: : Operation not permitted

Could not bind to socket '/home/steve/.kde/socket-darkstar/kdeinit-:0'

Could not register with DCOPServer. Aborting.

startkde: Shutting down...

Warning: connect() failed: : No such file or directory

Error: Can't contact kdeinit!

startkde: Running shutdown scripts...

startkde: Done.

I always get the stderr is not a tty - where are you?, so dont think thats anything to do with it. The errors when logging in with gnome are less helpful:

Code:

stderr is not a tty - where are you?

gconf-sanity-check-2 did not pass, logging back out

After reading this, ive tried to make a link with ln -s and just ln between my fat32 partition and ext3 partition and I got operation not permitted.

Is there a work around for this?

Thanks for all the help

steveybaby2

Might it be that creating symlinks on vfat is not allowed?
That seems like what the error log is trying to say...
--Taj

Duh! Looks like Ive got no choice then but to mount it under /home/steve/mydata.

Thanks a lot for your help anyway.

Cheers

steveybaby2 :cool: