Bug 1403730 - Upgrade from Fedora 23 to Fedora 25 disabled display manager (KDM)
Summary: Upgrade from Fedora 23 to Fedora 25 disabled display manager (KDM)
Keywords:
Status: CLOSED DUPLICATE of bug 1337546
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-workspace
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-12 09:50 UTC by Diego
Modified: 2016-12-13 14:49 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-13 14:49:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.