Bug 1403730

Summary: Upgrade from Fedora 23 to Fedora 25 disabled display manager (KDM)
Product: [Fedora] Fedora Reporter: Diego <diego.ml>
Component: kde-workspaceAssignee: Than Ngo <than>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: jgrulich, johannbg, jreznik, lnykryn, mbriza, me, msekleta, muadda, rdieter, smparrish, ssahani, s, systemd-maint, than, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-13 14:49:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Diego 2016-12-12 09:50:40 UTC 
Description of problem:
I've used Fedora 23 with KDM display manager up to a couple of days ago.
Then I've upgraded to Fedora 25. Unfortunately, after the upgrade the KDM display manager didn't show up anymore.
Checking /etc/systemd/system/display-manager.service I noticed it wasn't present, so I reenable the service with:
systemctl enable kdm.service
and it started to work again.

Anyhow I'm a bit puzzled on why it stopped to work in first place.


Version-Release number of selected component (if applicable):
systemd-231-10.fc25.x86_64


How reproducible:
always

Steps to Reproduce:
1. Fedora 23 with KDM
2. upgrade to Fedora 25

Actual results:
No display manager after upgrade.

Expected results:
KDM display manager starts, or at least, it is replaced with another display manager if it is actually deprecated.
Comment 1 Zbigniew Jędrzejewski-Szmek 2016-12-12 13:33:10 UTC 
Systemd just executes the configuration if receives from other tools. I think KDE changed to sddm by default, this is probably related to those changes somehow.
Comment 2 Rex Dieter 2016-12-13 14:49:16 UTC 

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