Cannot bring up the KDE at boot time.

swamprat · 01-30-2007, 09:51 AM

Hello all,

Yesterday I was in a console session and somehow I logged out but not via the KDE.

Now when I try to log back in I just have a terminal session but no KDE...just line commands.

I rebooted the machine but when it comes back up it still is just a terminal screen, no KDE, where I'm asked to enter my user name and password.

I logged in that way and I'm in root user.

I tried to do a startx command but got all sorts of errors. Is there anyway to get back to the KDE gui?

Using SuSe 9.2 Thanks.

reddazz · 01-30-2007, 10:38 AM

You have to post the errors you got if you want someone to help you out with your problem.

slackass · 01-30-2007, 11:37 AM

I had that happen and the way I got back to kde was:
root > init 5 > startkde

hope it helps

lauer · 02-02-2007, 01:27 AM

Yeah, but if he gets errors from startx, init 5 will fail too. Those error messages would be really helpful ... and of course the Xorg.log

swamprat · 02-02-2007, 03:42 PM

How true lauer.

However the way things are set up here I can't cut the information out of the terminal window and get them to you.

The machine is running in a VMware enviornment.

If I can find some way to do this I'll update this ticket.

Thanks for your replies.

killy9999 · 02-03-2007, 04:15 AM

Maybe screenshot? Or you can set up virtaul machine so it can use network.

lauer · 02-03-2007, 07:00 AM

Quote:

Originally Posted by swamprat

How true lauer.

However the way things are set up here I can't cut the information out of the terminal window and get them to you.

The machine is running in a VMware enviornment.

If I can find some way to do this I'll update this ticket.

Thanks for your replies.

Well, the Xorg.log is located in /var/log, or if you are trying startx, there should be a file .X.err in your home directory. Can't you transfer files from your virtual machine to your host machine, or access a USB stick or something?

ianio · 02-03-2007, 12:01 PM

if you were changing your resolution or messing with monitor settings when it was fine this could cause the command line on the next reboot.
if so on the command line...
log in as root
enter your root password.
type sax2 -r
this will run the config to get the monitor settings corrected. always choose "test" before applying resi changes.