Grant Edwards wrote:
On 2010-07-05, Dale<rdalek1...@gmail.com> wrote:
Grant Edwards wrote:
The point is that if you always start with a text login, it's easy to
log in and fix whatever keeps X/KDE from working. That's why I gave
up on graphical logins about 15 years ago.
The reason it wouldn't load is that a LOT of packages, including KDE,
needed to be recompiled after the libpng upgrade. I already knew that.
Text or GUI login would not matter. Recompiling the packages was fixing
the problem already so having a text login wouldn't help on that either.
When I run into a problem with the GUi loading, I just do a ctrl alt F1,
log in and fix it. That is my text login trick.
As long as ctrl-alt-F1 works, that's cool. It hasn't happened to me
for a while, but it didn't used to be at all difficult to get X broken
enough that ctrl-alt-F1 wouldn't work.
In that off chance, use the SysRq keys to get it back. If that doesn't
work, you got to reboot anyway.
I can also check the X
logs that way too. It seems to me that the way you are doing is the
hard way. I just type in my password to log in and it appears you have
to log in on a console, type a command then let it load.
I type my username, my passowrd and then I type x and hit enter.
Yea, more stuff to type in for the off change the GUI doesn't work.
That's a lot of typing for a rare failure. So far, the only time I
could not switch back to a console was when trying to use hal with xorg.
I'll keep my way. I like it easy when possible then do it the hard
way if I run into a problem that requires it.
No worries.
Dale
:-) :-)
