On Friday 15 April 2005 01:50, elefino wrote:
SuSE 9.2 with KDE 3.4.
Used to be, a second person on my machine could do a text login at the F1 console, run "startx -- :1 and find themselves in a GUI session on F8. That second session type seemed to default to KDE, which is what I normally run when I login via the KDM login.
For a couple of months now, startx -- :1 launches an FVWM session, instead of KDE. I'm still running KDE on F7 (started from KDM login), but my wife is losing patience since she would prefer KDE for her session as well.
I've been snooping a trail of config files, and haven't seen anything that I recognize as the source of the problem.
If I recall, we first noticed it after I installed KDE 3.4. KDE 3.4 itself seems fine. I did a full install, rather than attempting an update.
update vs. full install of KDE? How do you mean? About your problem: the startx script starts the window manager defined by the environment variable $WINDOWMANAGER. If at the command prompt you run echo $WINDOWMANAGER you will see what it's set to. fvwm is what the system defaults to if it can't find the program set by $WINDOWMANAGER (well, it's the second choice, if it can't find kde) as you can see in /usr/X11R6/lib/X11/xinit/xinitrc I believe your problem is caused by a name change (or packaging problem). WINDOWMANAGER is set to 'kde' while the new kde doesn't provide the 'kde' link. I think you can probably solve your problem by running the command ln -s /opt/kde3/bin/startkde /usr/X11R6/bin/kde You can change the system default window manager (and therefore the default value of the $WINDOWMANAGER variable) by editing the script /etc/sysconfig/windowmanager