Results 1 to 9 of 9
Thread: startx troubles with 9.1... help
Enjoy an ad free experience by logging in. Not a member yet? Register.
startx troubles with 9.1... help
but when i tried "startx" the first time i got a first time wizzard or something that let me choose which GUI to use. I chose kde. and it looked like it was starting kde but it just keeps fluctuating and i get a busy cursor and a blue background and that's it. it does this every time I "startx".
does anyone know how to fix this?
or if more information is needed tell me where to find it?
maybe also could someone tell me how to change the default GUI to gnome so i can see if it's a kde problem or a general problem with x?
Erm, what distro is this? If it is SuSE 9.1 (the olny slightly modern 9.1 distro I know of), try runningCode:
Edit: just seen that this is in the mandriva forum, so you might want to run Mandrakes configuration tool MCC or it's X configuration tool drakex (not sure about the last one).
I did try mcc and changed the display configuration around...but i still have the same problem. I have an sis 540 motherboard with built in video card..and it looks like there's a driver for it in the list..but i've changed it to an Xfree driver (SiS) and still the same thing happens. I get a blue textured background and then a pannel pops up and disappears. a few windows do the same.. too fast to see anything in them. and then i get a single icon that keeps fluctuating. I end up with a blue background, and that's it.
when i press ctrl+alt+F1 i see lots of error messages like so:
Mcop warning: user defined signal handler found for SIG-PIPE, overriding kdesktop(a random number) got signal 11 ... <repeating with different numbers> ...
Hmm, it seems that there is something wrong with kde, have you tried re-installing kde? or maybe installing another desktop environment or windowmanager (such as fluxbox) ?
Sorry but i haven't got many more ideas on the subject
i actually installed redhat 9 on it aswell. and kde didn't work in redhat either. I think it's incompatability issues. but what exactly, i'm not sure.
instead of using a driver, why not try using a vesa framebuffer?Life is complex, it has a real part and an imaginary part.
09-13-2005 #7Originally Posted by AlexK
vesa driver is supported by all cards, it is just a non-fancy graphical driver. I am not sure if it can support high resolutions or not. Basicially what you do is during the graphics setup of the installation, just choose the vesa driver.Life is complex, it has a real part and an imaginary part.
It works! Fianlly!
I used the vesa driver and all is well.
thanks very much guys.