cannot log in anymore - boots fine, stuck at login screen

I initially installed the KDE3 desktop, as that was what I was used to, and I knew it was well-tested and stable. I later installed KDE4 to try. Things are great; a little slow, but that was expected (old computer). Then I installed GNOME – it looks and works great.

I was just getting settled, then all of a sudden, I can’t login anymore. I was switching from KDE4 back to KDE3. I mis-typed the password. Okay, no big deal. So I made sure to type it slower. The screen goes black like it’s going to login, and then the next thing I see is the login screen again. I knew I hadn’t typed it wrong, so I switched the session type to GNOME. No go. I tried KDE4 again. No go. So, I restarted the computer… same thing.

Luckily, I have the computer dual-booted – I am posting this from XP.

Can anyone help?

I haven’t the foggiest clue as to what could be wrong. I spent a great deal of time setting things up and installing needed software. I would really LOVE to avoid a “format-reinstall” fix.

Thanks in advance.

Im currently having the exact same problem. I can still logon in Console tho, and I can also logon X using root username and password. I thought that I had somehow succesfully screwed up my profile, and with a friends idea, i tried to run this command

rm -rf .*

to remove all the profile settings,but still didnt work. And then i used YaST2 to remove the profile entirely and created a brand new profile. Yet it fails. Hope someone has any idea how to fix this. Thanks

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Um… regarding the ‘rm’ command, where in the filesystem were you?
Typically using that particular exact command without a full path is a
really really bad idea because, with ‘root’ privileges, you could easily
destroy your entire system including personal data in home directories.

Good luck.

Huz wrote:
| Im currently having the exact same problem. I can still logon in Console
| tho, and I can also logon X using root username and password. I thought
| that I had somehow succesfully screwed up my profile, and with a
| friends idea, i tried to run this command
|
| rm -rf .*
|
| to remove all the profile settings,but still didnt work. And then i
| used YaST2 to remove the profile entirely and created a brand new
| profile. Yet it fails. Hope someone has any idea how to fix this.
| Thanks
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIcYCH3s42bA80+9kRAl1LAJ46hxO4cKpt+eaimaBVkufTTIUfPwCbB1JY
AjtvOc6dQax0UaMIzS64sqw=
=O9Ej
-----END PGP SIGNATURE-----

I was in Home dir. Like I said, I used it to delete the profile configs.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Okay, well, I’m not sure how that will help logins. Do you see anything
in /var/log/messages during the login attempt? It’s very possible that
PAM is setup to allow logins at the command line but not via the GUI.
Post the contents of /etc/nsswitch.conf and possibly the /etc/pam.d/xdm
(and gdm) files. They may not help, but they may. Mostly I’m curious
about the ‘messages’ file’s content during a login.

Good luck.

Huz wrote:
| ab@novell.com;1834172 Wrote:
|> -----BEGIN PGP SIGNED MESSAGE-----
|> Hash: SHA1
|>
|> Um… regarding the ‘rm’ command, where in the filesystem were you?
|> Typically using that particular exact command without a full path is a
|> really really bad idea because, with ‘root’ privileges, you could
|> easily
|> destroy your entire system including personal data in home
|> directories.
|>
|> Good luck.
|>
|
| I was in Home dir. Like I said, I used it to delete the profile
| configs.
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIcYcT3s42bA80+9kRAh0pAJ9XkSQFxuSdNLoXgah/n0U+CDrIhgCfZr9M
gFlEpfK2lzDMPtDDqkSerk0=
=Er+8
-----END PGP SIGNATURE-----

On Mon, 07 Jul 2008 01:46:04 GMT
Huz <Huz@no-mx.forums.opensuse.org> wrote:

>I thought
>that I had somehow succesfully screwed up my profile, and with a
>friends idea, i tried to run this command
>
>rm -rf .*
>
>to remove all the profile settings,but still didnt work.

That is a very bad command to run. If you had been root, you could
have lost a lot of data! (I know, I did it once!)

If you want to delete all of the hidden directories, and all their
sub-directories in your home directory then, as your normal user, do
this:

rm -rf .[a-zA-Z0-9]*

But that is still a bad option – you might delete something you need
(browser bookmarks and such). The best way to handle this is to create
a new user and see if that helps. If it does, you can copy data from
the old directory (and try the various hidden directories to see if you
can find which one broke it, so you don’t repeat it).


Kevin Nathan (Arizona, USA)
Linux is not a destination, it’s a journey – enjoy the trip!

Linux 2.6.22.18-0.2-default
10:04pm up 1 day 3:37, 21 users, load average: 0.40, 0.45, 0.49

Ok, Im trying to give what you’re asking, Im just learning Linux and I hope Im giving you the right thing.

var/log/messages :
Jul 4 20:04:20 linux-bm7z gconfd (Huz-2984): starting (version 2.22.0), pid 2984 user ‘Huz’
Jul 4 20:04:20 linux-bm7z gconfd (Huz-2984): Failed to get lock for daemon, exiting: Failed to get a lock: couldn’t create directory `/tmp/gconfd-Huz/lock’: No space left on device
Jul 4 20:04:21 linux-bm7z kdm: :0[2996]: Cannot save user authorization in home dir
Jul 4 20:04:25 linux-bm7z kdm: :0 '[3035]: Cannot save user authorization in home dir

etc/nsswitch.conf :

passwd: files nis

shadow: files nis

group: files nis

passwd: compat
group: compat

hosts: files mdns4_minimal [NOTFOUND=return] dns
networks: files dns

services: files
protocols: files
rpc: files
ethers: files
netmasks: files
netgroup: files nis
publickey: files

bootparams: files
automount: files nis
aliases: files

/etc/pam.d/xdm :
#%PAM-1.0
auth include common-auth
account include common-account
password include common-password
session required pam_loginuid.so
session include common-session
session required pam_resmgr.so

/etc/pam.d/gdm :
#%PAM-1.0
auth include common-auth
account include common-account
password include common-password
session required pam_loginuid.so
session include common-session
session required pam_resmgr.so
auth optional pam_gnome_keyring.so auto_start
session optional pam_gnome_keyring.so

Im shooting blind here. But I hope this would help. :slight_smile:

I have deleted my profile and created a brand new one, but its still like that when I try to login with the new one. Anything else that might work? Im still linux noob so I’m kinda shooting blind :slight_smile: Hope you guys can help me out here.

I maybe wrong but think you’ll find this is the problem.

Failed to get lock for daemon, exiting: Failed to get a lock: couldn’t create directory `/tmp/gconfd-Huz/lock’: No space left on device

You need to find some space, a live distro maybe or something like gparted disc and reclain some extra for /

To make sure that this is the problem try df -h should show that there is no or very little room left on /

Yeah,that seems to fix the problem. My drive was full. Thanks mate :slight_smile: