Bug 194506

Summary: kdm changes session selection with no feedback
Product: [Unmaintained] kdm Reporter: gene smith <gds>
Component: generalAssignee: kdm bugs tracker <kdm-bugs-null>
Status: RESOLVED DOWNSTREAM    
Severity: normal CC: kevin.kofler, rdieter
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description gene smith 2009-05-29 05:40:20 UTC 
Version:            (using KDE 4.2.3)
OS:                Linux
Installed from:    Fedora RPMs

In KDM if you select a session type that differs from your last session (e.g., were running KDE, now want to run Gnome) and then entered your User ID and password, it runs KDE again instead. The problem is that as soon as you put in your user ID, it resets the session type selection to the previous session type for that user, regardless of what was just selected.

Actually, gdm does the same thing. However, with it you can see at the bottom of the screen that the act of entering your user ID has changed the session type back to what it was. You have to be watching pretty close with gdm but at least you can see that it changes. With kdm, unless you already know what it is doing, it can seem like it will not switch your session type even though you just selected a new one (because the state of the session buttons are not visible unless you open it up and look).

See https://bugzilla.redhat.co/show_bug.cgi?id=502953 
for additional discussion of this "bug". (Maybe this is halfway between a bug and a "wish"?)
Comment 1 Oswald Buddenhagen 2009-05-29 09:09:40 UTC 
redhat - FAIL.
Comment 2 Kevin Kofler 2009-05-29 14:00:24 UTC 
I believe this bug is caused by Than's kdebase-workspace-4.1.80-session-button.patch.
Comment 3 Rex Dieter 2009-05-29 16:30:16 UTC 
sorry for the noise... time to go bust heads for patching something without documenting or upstreaming it.
Comment 4 Oswald Buddenhagen 2009-07-11 14:43:05 UTC 
btw, in case you (redhat guys) want to fix bug #174431 the right way: introduce a new variable forcedWm. once an item is explicitly selected, the implicit "(previous)" would go away and a "(forced)" would "follow" the currently checked item.