Bug 131223 - After update choice of session type in kdm not possible
Summary: After update choice of session type in kdm not possible
Status: RESOLVED DUPLICATE of bug 132898
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: KDE (show other bugs)
Version: Final
Hardware: i586 Other
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-28 08:28 UTC by Andreas Kuntzagk
Modified: 2006-01-09 17:32 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Kuntzagk 2005-10-28 08:28:12 UTC 
I updated from 9.1 to 10.0 (retail version). Now after a login KDE is always starting regardless of the choosen session type (GNOME, IceWM etc.). 
But the choosen session type is remembered and displayed as last session type after logout.
Comment 1 Andreas Kuntzagk 2005-10-28 13:35:56 UTC 
Additional info: 

Choosing session type for newly created users works but not for existing before update.
Comment 2 Daniel Heath 2005-10-28 20:50:05 UTC 
I have been having simular problems.  I changed everything from tcsh to bash.  (Reset the X Server?)  I also refreshed ~/.profile, ~/.bashrc to defaults from /etc/skel.  This seemed to fix the problem.  I also notice that a new user with tcsh as the default has the same problem.
Comment 3 Stephan Kulow 2005-11-21 15:34:18 UTC 
do you have a ~/.xsession ?
Comment 4 Kristian Harder 2006-01-05 22:40:48 UTC 
I can confirm that the session type selection in the default system (i.e. without any .xsession etc) only works if a user has login shell bash, not tcsh. I am using session type fvwm2, which worked perfectly fine until I switched my login shell to tcsh in the yast2 user manager. From that point on my session type selection was ignored and KDE was started always. As soon as I switched back to bash I could run fvwm2 again.
Comment 5 Kristian Harder 2006-01-05 23:04:25 UTC 
Ok, there it is:
https://bugzilla.novell.com/show_bug.cgi?id=132898
Comment 6 Stephan Kulow 2006-01-09 17:32:12 UTC 

*** This bug has been marked as a duplicate of 132898 ***