GNOME Bugzilla – Bug 341619
ask "make this session the default session?" on change, not afterwards on next login.
Last modified: 2007-05-01 14:14:51 UTC
Hi! i did a testcase and it seems like gdm is inconsistent in changing languages and sessions. All i wanted to is use failsafe xterm and not change the default session type, so lets go on: 1) GDM started, default sesssion is Gnome (default ubuntu dapper setting) 2) press Session and choose "Failsafe Xterm" 3) login with name/password 4) Xterm starts without any questions 5) work with xterm 6) logout 7) back in gdm, ready for other users for example --- 8) login with name/passwort (expecting to use the default session) 9) gdm-question: "Do you want to make GDM_Failsafe.XTerm.desktop the default for future sessions?" [Just Log in] [cancel] [Make default] 10) user stucks probably he presses Just Log in (to what?) or he presses Cancel and goes this never ending dream goes allong with 2) where he chooses gnome for example. Lets go on with [Just Log in] 11) Gnome starts 12) work with gnome 13) logout 14) back in gdm, ready for other users for example --- 15) User sees gdm and logs in with name/password 16) since last time he answered [Just Log in] go to 9) Assuming the user only wanted to fix something without starting the gnome desktop, this produced a lot of questions on later logins. Solution, or wanted behavior: Look how language switching works, because the difference in terms of a testcase is: 1) default session is german on the system --- 2) user sven-tek chooses english(UK) (intended only for the next session) 3) login with name/password 4) gdm-question: Do you wish to make english(UK) the default for future sessions? [Just for this session] [Cancel] [Make default] 5) i answer [J.f.t.s.] 6) Gnome starts in english, work 7) logout, back to gdm --- 8) simply login with name/password 9) Gnome starts in german --> Okay, no later questions came up You see, session switching is a little bit broken. kind regards, Sven
*** Bug 318696 has been marked as a duplicate of this bug. ***
Fixed in CVS head and 2.14 branch.
*** Bug 368648 has been marked as a duplicate of this bug. ***