Description of problem: I wanted to try sddm instead of kdm. So I've installed sddm and uninstalled kdm. Afterwards, I was left with text mode, as sddm did not start ... Version-Release number of selected component (if applicable): systemd-208-17.fc20.x86_64 How reproducible: (always?) Steps to Reproduce: 1. do a stock Fedora install 2. yum install sddm 3. yum remove kdm 4. reboot Actual results: you're in text mode Expected results: X is started, sddm greets you Additional info: seems that the systemd presets just don't cut it, despite sddm is listed in /usr/lib/systemd/system-preset/85-display-manager.preset ...
(In reply to Karel Volný from comment #0) > Additional info: > seems that the systemd presets just don't cut it, despite sddm is listed in > /usr/lib/systemd/system-preset/85-display-manager.preset ... I think that problem is that only one display manager can be enabled at the time. Please try again but this time swap steps 2. and 3., hence remove kdm first and then install ssdm.
This is a known issue, but I am not sure it's really an error: we will not reenable units after a conflicting unit is removed, and I am pretty sure we shouldn't.
It would probably make sense to call systemctl preset from %postrans script. This way installation order in transaction wouldn't matter. Martin, any comments? Of course such change should apply to other display managers as well.
(In reply to Lennart Poettering from comment #2) > This is a known issue, but I am not sure it's really an error: we will not > reenable units after a conflicting unit is removed, and I am pretty sure we > shouldn't. I'm not sure I'm getting this ... in my POV it isn't a matter of "reenabling" but rather choosing the "best" available to satisfy the dependency, if installing something can change the default (which one "wins"), why uninstalling should be any different? (In reply to Michal Sekletar from comment #3) > It would probably make sense to call systemctl preset from %postrans script. sddm calls %systemd_post/preun/postun sddm.service from %post, %preun and %postun - isn't it enough? (what do the systemd_* macros do?) > This way installation order in transaction wouldn't matter. how do I understand the problem now, it lies with kdm that it doesn't have any %post script that would update the presets ...? [in the current implementation of presets ... still I'd like to see it being more dynamic, not relying on the post(un)install magic] > Martin, any comments? ping?
I dont't really understand why this should be handled explicitly in all the related packages from the preset. What would make sense would be to detect (in systemd) that the current choice from a particular preset is being removed and then act upon it by choosing another present one from the list according to their order.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.