I ran rpm -Uvh --nodeps --force *.rpm as suggested in another thread with all the packages provided by suse..

It seemed to update.. things registerred as 3.2 BUT

When I restarted, in runlevel 5, it didn't boot to the gui login.. and when i logged in and ran startx I received an error stating, XIO : fatal IO error 104 (connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.

When I run startkde the following comes up.

xsetroot : unable to open display ''
xset: unable to open display ""
ksplash: cannot connect to xserver
kdeinit : Aborting. $DISPLAY is not set
Warning: connect() failed: : No such file or directory
Error: Can't contact kdeinit!
startkde: Running shutdown scripts
startkde one.

Any thought or do i have to reinstall.. the thought is when stuff like this breaks it's an opportuinity to learn.. so i would appreciate any insight.

Nearest I can figure, something is screwed with my display entry in the XFree86config file.. but it all looks ok to me.

Thanks for your help.

Are you using the nvidia driver? if so, you'll have to rerun the setup.

no i shouldn't be, this is in a thinkpad t20 with savage IX chipset..

how could i rerun the setup from a command line.. sorry, newb

startkde is no good. Use
startx
to see the error messages (startkde needs X running already; startx will start X and then start the default gui).

yah, sorry it was a long post.. if you check the top part the error messageis listed when i try to run startx

thanks

do you have a .xinitrc file in your home directory.
seems like that is missing
put a file ~/.xinitrc with startkde in it.
so ~/.xinitrc should look like:
that should work.It did(And still does) work for me.

Hi I just installed Debian linux and $display doesnt want to work for me for some reason. And I cant start X Server and am thrown back in the Shell.

Here is the error I wrote down:

xsetroot unable to open display
ksplash cannot connect to X server
Aborting $display is not set

How do I set it?
I'm going to try those commands above

startkde

and

startx

to see what happens. Maybe that will work