Hide Forgot
Description of problem: When upgrade finished and the PC automatically rebooted, X did not start. Version-Release number of selected component (if applicable): 0.7.1-1.fc23 How reproducible: It happened twice: first with a desktop running Openbox with kdm as the display manager, and then again with a laptop running LXDE with kdm as the display manager, Steps to Reproduce: 1. dnf system-upgrade download --releasever=24 --allowerasing 2. dnf system-upgrade reboot Actual results: no kdm login prompt Expected results: kdm login prompt Additional info: The fix for the problem was to run this command: system-switch-displaymanager KDM I believe there should be a way to fix this using systemctl (equivalent to the command above) though I have not tried it.
It happened again, so it is 3 times out of 3. This time with a LXDE desktop. Because I was expecting it to happen I did a bit of debugging. Before update (dnf system-upgrade reboot): -- ll /etc/systemd/system/display-manager.service lrwxrwxrwx. 1 root root 35 Apr 28 2015 /etc/systemd/system/display-manager.service -> /usr/lib/systemd/system/kdm.service After update (dnf system-upgrade reboot): -- ll /etc/systemd/system/display-manager.service ls: cannot access '/etc/systemd/system/display-manager.service': No such file or directory How I fixed it this time: -- systemctl enable kdm.service Created symlink from /etc/systemd/system/display-manager.service to /usr/lib/systemd/system/kdm.service. -- Why don't more people have this issue? I suppose that what is different with me is that I do _not_ use the default login manager (kdm is not the default for LXDE).
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.