> I installed the latest series of packages from kde.tdyc.com just now on > another machine of mine. As usual, I ran 'update-alternatives --config x- > window-manager' to reset x-window-manager to KDE (for some reason it goes > back > to enlightenment every single time there's any major update to KDE2). > However, instead of seeing a kde2 executable in the list, I saw it had been > changed to /usr/bin/kwin. Fine, I say to myself, and select that one. > > Logging in from xdm winds up with a blank screen and the X cursor, and > nothing > running that I can see using 'top'. Same with running startx from a user > account. I see that /usr/bin/kde2 still exists and was installed at the same > time as /usr/bin/kwin. What's the deal?
yes...kwin doesn't seem to wanna work as a window manager... :) kde2 does still exist but it is not a window manager...it is a session manager. And Debian policy states that it cannot be a x-window-manager since it's a session manager. A x-session-manager option is being discussed currently...but until then there is not going to be a default startx option for KDE. (you can always add your own manually). I'm still doing some testing and tweaking to find other ways around this... Ivan -- ---------------- Ivan E. Moore II [EMAIL PROTECTED] http://snowcrash.tdyc.com GPG KeyID=90BCE0DD GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
