Description of problem: Using KDE live DVD image to install, the default session is set to failsafe. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Start Fedora 21 beta KDE live DVD 2. Logout and see the selected session Or 1. Install KDE live 2. on sddm, see the selected session 3. Actual results: KDE Plasma (failsafe) Expected results: KDE Plasma Additional info:
I think sddm lists those sorted/alphabetically, so looks like: KDE Plasma (failsafe) KDE Plasma Workspace is the sort order, which is unfortunate. Will see if there's something we can do about that.
Looks like a simple workaround would be to rename kde session files in /usr/share/xsessions kde-plasma.desktop => 01-kde-plasma.desktop kde-plasma-safe.desktop => 99-kde-plasma-safe.desktop
Went with safe approach of renaming just kde-plasma-safe.desktop => kde-plasma99-safe.desktop Still would be nice/ideal if sddm grew some new configuration option, like DefaultSession= or to cheat, and simply always prefer kde-plasma.desktop if present (that's what gdm does with gnome-shell apparently)
kde-workspace-4.11.14-3.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/kde-workspace-4.11.14-3.fc21
Proposed as a Freeze Exception for 21-final by Fedora user rdieter using the blocker tracking app because: KDE Plasma Workspace (failsafe) session is sorted first in sddm, so gets picked by default after kde (live,net) install... which yields a poor experience (with at least desktop effects disabled).
In the event that today's Go/No-Go decision is "slip one week", I'm +1 to this low-risk, high-value Freeze Exception. Given that the workaround is "Click to change the default session, and forever after it will work right", it's clearly not a candidate for a blocker.
F21 is signed off now, so dropping proposal as it's moot. Marking as CommonBugs.
kde-workspace-4.11.14-3.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.