LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora (https://www.linuxquestions.org/questions/fedora-35/)
-   -   Fedora 12: unable to log in on GUI (https://www.linuxquestions.org/questions/fedora-35/fedora-12-unable-to-log-in-on-gui-790592/)

andybp85 02-21-2010 01:40 PM

Fedora 12: unable to log in on GUI
 
I'm working on getting my 3 computers to do daily backups. I set my desktop, running Fedora 12, up to do daily incremental dumps via cron with full backups on Sunday. Today, while it was doing its backup, it ran low on hard drive space, and kde locked up. I was able to restart because I had konsole open, but after the reboot I now can't log in on kde with my username. However, root can log into kde just fine, and I can log in as my user from the terminal no problem.

My /home/user/.xsession-errors only has the following:
No protocol specified
xrdb: Can't open display ':0'
No protocol specified
xmodmap: unable to open display ':0'
No protocol specified
Noprotocol specified
xterm Xt error: Can't open display: :0


Can anyone point me in the right direction? Thanks!!

nt20000 02-21-2010 02:03 PM

Quote:

Originally Posted by andybp85 (Post 3871688)
I'm working on getting my 3 computers to do daily backups. I set my desktop, running Fedora 12, up to do daily incremental dumps via cron with full backups on Sunday. Today, while it was doing its backup, it ran low on hard drive space, and kde locked up. I was able to restart because I had konsole open, but after the reboot I now can't log in on kde with my username. However, root can log into kde just fine, and I can log in as my user from the terminal no problem.

My /home/user/.xsession-errors only has the following:
No protocol specified
xrdb: Can't open display ':0'
No protocol specified
xmodmap: unable to open display ':0'
No protocol specified
Noprotocol specified
xterm Xt error: Can't open display: :0


Can anyone point me in the right direction? Thanks!!

try deleting the x session files in /tmp folder should help if the x session is failing to start

regards
nt20000

andybp85 02-21-2010 09:57 PM

Turned out the disk was full. also deleted the lock files for good measure. Thanks for the help :)


All times are GMT -5. The time now is 12:48 AM.