On Mon, 25 Apr 2011 14:08, Patrick Shanahan
* Yamaban
[04-25-11 05:08]: The issue found was the following: An install/update scriptlet modified /etc/sysconfig/windowmanager, and set an invalid "DEFAULT_WM", it was set to "kde4" (false), instead of "startkde" (right).
This does not appear to be the origin of the problem as my "DEFAULT_WM" is set to "kde4" and I do not have the problem. I also do not have "kde4" listed as a WM, but "kde4 Plasma".
repeat correct entry: DEFAULT_WM="startkde"
works, but is a "work-a-round" rather than a "solution".
First: /usr/bin/kde4 is a bash-script or starting apps in a kde4 env. Second: the central /etc/X11/xinit/xinitrc looks for $DEFAULT_WM in $PATH Third: Fail! Easy to follow, ne? For a permanent solution: either the script /usr/bin/kde4 will be renamed, or upgraded with a logic to detect when an "exec startkde" is appropiate. Or even better fix the install/update scriptlet permanent. Do NOT resort to bungling up a FUBAR situation. "kde4 Plasma" as DEFAULT_WM is plain wrong. For further info ask around at kde.org As a 'simple' user I'd like a package to run after install/update/upgrade and fail as seen. For further analyses: - Is the scriptlet in the kdm or in a other kde* package? - Just why mongs this scriptlet the DEFAULT_WM around when there is already a valid entry? - Is the script /usr/bin/kde4 upstream or openSUSE? But please check with others about what you propagate as solution. Yamban -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org