Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.

The power went out on my PC running CentOS 6.3 while I was logged in as a regular user. Since then, when I try to login from the GUI, my screen flashes to black then returns to the login screen, without any message (as if my user was rejected). I can still login as root.

I checked the /etc/passwd file and everything is fine.

Here is a partial dump of the /var/log/messages lines, linked to the login and immediate logout:

Jan  7 09:06:59 localhost acpid: client connected from 3054[0:0]
Jan  7 09:06:59 localhost acpid: 1 client rule loaded
Jan  7 09:07:00 localhost rtkit-daemon[2701]: Sucessfully made thread 3107 of process 3107 (/usr/bin/pulseaudio) owned by '42' high priority at nice level -11.
Jan  7 09:07:00 localhost rtkit-daemon[2701]: Sucessfully made thread 3109 of process 3107 (/usr/bin/pulseaudio) owned by '42' RT at priority 5.
Jan  7 09:07:00 localhost gdm-simple-greeter[3094]: Gtk-WARNING: gtkwidget.c:5460: widget not within a GtkWindow
Jan  7 09:07:00 localhost rtkit-daemon[2701]: Sucessfully made thread 3113 of process 3107 (/usr/bin/pulseaudio) owned by '42' RT at priority 5.
Jan  7 09:07:00 localhost rtkit-daemon[2701]: Sucessfully made thread 3114 of process 3107 (/usr/bin/pulseaudio) owned by '42' RT at priority 5.
Jan  7 09:07:08 localhost acpid: client 3054[0:0] has disconnect

Any suggestion as to debug/solve this issue?

share|improve this question
2  
1) Check space on /home. 2) Try to login to console (ctrl+shift+f2) –  dchirikov Jan 7 '13 at 8:54
3  
@dchirikov Unless CentOS does something oddball in that department, it's Ctrl+Alt+F2 to switch to the second virtual console. –  Michael Kjörling Jan 7 '13 at 9:01
    
@Michael Kjörling Of course Ctrl+Alt+F2. My mistake. –  dchirikov Jan 7 '13 at 9:06

1 Answer 1

Found the cause of the issue.

I could login through Ctrl+Alt+F2 but could not issue any command. The $PATH variable had been tempered with and was not referring to the right directories. Fixing the $PATH solved the issue.

Thanks for the tips!

share|improve this answer
1  
Was it changed in the startup scripts? Such a change must be investigated... –  vonbrand Jan 26 '13 at 3:01

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.