Graphical Login Screen Problems on 9.2
 

Wow, I can't begin to explain the strange problems that I've been having with starting window managers on Suse 9.2. I don't know why it's acting so strange. Instead of repeating myself I'll gather the threads that I started which dealt with this problem:

Thread about Fluxbox not starting under "startfluxbox" in Runlevel 3
http://www.linuxquestions.org/questi...hreadid=257283

Thread about my problems of starting Gnome under "startgnome-session" and starting KDE under "startkde"
http://www.linuxquestions.org/questi...hreadid=253387

Turning on the Graphical Login screen (Runlevel 5)
http://www.linuxquestions.org/questi...hreadid=243339

To quickly summarize my problem here I go... I had Suse Linux stop at runlevel 3 so as a result, I have to put "start--insert WM here" to get a window manager to start. The window managers that I have installed are KDE, Gnome, Fluxbox, and XFCE. For some odd reason I can start any of these window managers if I edit the file, .xinitrc, to load it when i type "startx." When I try their native start command (ie startkde, startgnome-session, etc), the window manager will not load. The only exception to this whole situation is XFCE. XFCE is able to load under "startxfce4" but its only one that can start with its native command. That's my first problem.

The next problem I have has to do with the Graphical login screen. When the login screen is working correctly, you're supposed to be able to choose which Window Manager you want loaded and Suse should take care of the rest. Well, that didn't happen for me. When I looked at the Window Manager menu on the Graphical login, all the window managers I have installed are listed. The problem comes when I choose one window manager. No matter what window manager I choose, it'll load KDE everytime. During installation I had KDE be the default window manager but I should be able to switch Window Managers with ease regardless.

So I don't know what the problem is. I don't even know if anyone else is having a similar problem. I started out with Suse 9.1 then upgraded to Suse 9.2. When I had 9.1, I had the same problem so I don't know if the problem would be solved if I were to do a complete install of Suse 9.2. Just some more information, I have an Averatec 3200 laptop if that info is of any help to you guys. Please help me because I'm so confused! Suse has been pretty good about a lot of things but this is just so odd. :scratch:

I'd first try a repair or upgrade via the suse 9.2 cd's or thru an ftp server, before i'd try a reinstall. If that doesn't work then a reinstall will fix that problem. I have 9.2 running on a laptop and 3 pc's since 8.0 and i've never had that problem or seem it before. I'm guessing it was a corrupt package from a previous installation that was not included when you updated to 9.2.