This doesn't seem to be fixed. I now have three separate machines, all tracking testing with a sprinkle of unstable packages (which includes those for kwin and kde-window-manager), none of which run kwin_x11 at login. They do all have the correct x-window-manager alternative set, and I can manually start kwin_x11 after login.
>From my investigation, the problem is that ksmserver, which is what starts the window manager, by default attempts to find the "kwin" binary, but this binary no longer exists. Evidence for this is that I see 'KSMServer::wmProcessChange: Window manager "kwin" failed to launch' in my .xsession-errors file, and examining the source code (http://api.kde.org/4.x-api/workspace-apidocs/plasma-workspace/html/ksmserver_2startup_8cpp_source.html, lines 233 and 234) suggests this really is the name of the binary ksmserver is looking for. If correct, I should be able to work around the issue by (as root) creating a link /usr/bin/kwin that points to kwin_x11. Indeed, I just checked, and that does appear to work. Peace, Brendon -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5235696.9Bl4xkkpuZ@chi
