Revision history [back]

This is the second time in a month I've had this problem, but I haven't found the cause or why it's behaving like this. I use a guest(Fedora 21) virtual-machine on a Fedora 21 host in VirtualBox for testing and I was going to install updates and the new kernel but I can't log-in...... it just loop's the log-in screen.

Why is this happening how can I repair this?

I can get a shell by using the other terminals(F1,F2,F3).

This is the second time in a month I've had this problem, but I haven't found the cause or why it's behaving like this. I use a guest(Fedora 21) virtual-machine on a Fedora 21 host in VirtualBox for testing and I was going to install updates and the new kernel but I can't log-in...... it just loop's the log-in screen.

Why is this happening how can I repair this?

I can get a shell by using the other terminals(F1,F2,F3).

This is the second time in a month I've had this problem, but I haven't found the cause or why it's behaving like this. I use a guest(Fedora 21) virtual-machine on a Fedora 21 host in VirtualBox for testing and I was going to install updates and the new kernel but I can't log-in...... it just loop's the log-in screen.

Why is this happening how can I repair this?

I can get a shell by using the other terminals(F1,F2,F3).

EDIT #1

I updated the system from a different virtual-console, re-installed @kde and installed kdm and set it to the default with system-switch-displaymanager but still the same issue persists. Any idea's?

This is the second time in a month I've had this problem, but I haven't found the cause or why it's behaving like this. I use a guest(Fedora 21) virtual-machine on a Fedora 21 host in VirtualBox for testing and I was going to install updates and the new kernel but I can't log-in...... it just loop's the log-in screen.

Why is this happening how can I repair this?

I can get a shell by using the other terminals(F1,F2,F3).

EDIT #1

I updated the system from a different virtual-console, re-installed @kde and installed kdm and set it to the default with system-switch-displaymanager but still the same issue persists. Any idea's?

EDIT #2

From my comment to pnadk's answer:

@pnadk I'm accepting this as the answer and thanks for the info, but if anyone else is reading this, it would be helpful to know more about the files/stuff that can cause this, the fix for me was log-in as another user and move all files(also hidden) from the broken users home directory to another location, and copy most of the hidden files(config files usually) from this healthy user to the broken users home directory and then I could login.