* 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". -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org

* Felix Miata [04-25-11 08:23]:

On 2011/04/25 08:08 (GMT-0400) Patrick Shanahan composed:

...

works, but is a "work-a-round" rather than a "solution".

Or maybe is required for startx to start a plasma session instead of another kdm instance?

08:25 Crash: ~ > grep WM /etc/sysconfig/windowmanager DEFAULT_WM="kde4" starts "kde4 Plasma" -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org

* Felix Miata [04-25-11 08:47]:

On 2011/04/25 08:25 (GMT-0400) Patrick Shanahan composed:

...

08:25 Crash: ~> grep WM /etc/sysconfig/windowmanager DEFAULT_WM="kde4"

...

starts "kde4 Plasma"

Even on fresh virgin system with multiple DTEs installed, or with ~/.dmrc containing something other than default/plasma/kde?

I only installed kde4 which came with icewm and twm. ~/.dmrc contains: [Desktop] Session=kde-plasma -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org

On Mon, 25 Apr 2011 14:08, Patrick Shanahan wrote:

* 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

On 2011/04/25 14:46 (GMT+0200) Yamaban composed:

Patrick Shanahan wrote:

...

* Yamaban composed:

...

...

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".

Here now in Tumbleweed with 4.6.3, using none of kde-plasma, kde, kde4 or startkde will startx open a KDE4 session. Trying produces this .xsession-errors: http://fm.no-ip.com/Tmp/SUSE/xsession-errors-114T-0startx Only setting it to kde or startkde can I login through the login manager successfully without an existing ~/.dmrc pointing to kde-plasma, or selecting kde plasma as session type. kde4 or kdm just restart the login manager.

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.

So now in 4.6.3, what is working for those who wish startx to work instead of using the login manager and whose only purposely installed window manager is KDE? * permissions.local has last line "/usr/bin/xorg root:root 4711" uncommented, and /usr/bin/Xorg is -rws--x--x. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org

* ka1ifq [04-25-11 16:03]:

Patrick,

Is there an official way to do the update?

I put together a test system and wish to do the upgrade, still too chicken to update my desktop system.

Tnx, Mike.

...

* 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".

--

--- Sent from my Suse Linux Desktop. ---

I installed 11.4 x86_64 via the net-install cd onto a new box and added repos: KDE_Extra KDE_Extra_46 KDE_Release_46 Packman Repository did "zypper ref; zypper -v dup; SuSEconfig; ldconfig; zypper -v ps" and was good-to-go. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org