Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
|Summary:||upgrade from f23: kdm no longer enabled|
|Product:||[Fedora] Fedora||Reporter:||Dr. David Alan Gilbert <dgilbert>|
|Component:||kde-workspace||Assignee:||Than Ngo <than>|
|Status:||CLOSED EOL||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||24||CC:||awilliam, bcotton, bugzilla, contact, dgilbert, diego.ml, ealmanah, fuzz, george.seaton, jgrulich, jreznik, mbriza, me, ovasik, pg7724, pierluigi.fiorini, rdieter, sergio, than, yehielb|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2017-08-08 14:34:28 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:||1349664|
Description Dr. David Alan Gilbert 2016-05-19 12:32:33 UTC
Description of problem: I've upgraded two of my f23 hosts to f24 and on both of them I've been left at a text login prompt after upgrade since no display manager is enabled. My machines have both been running KDE in the past, in the ~f22 time, but I switched over to using an xfce session in f23. After the upgrade I did a: systemctl list-unit-files | grep dm and it showed I had both lightdm and kdm installed but both were disabled. I think I was using kdm in f23; indeed if I now do: journalctl -b -3|grep Starting|grep -i kde I see: May 18 10:54:28 dgilbert-t530 systemd: Starting The KDE login manager... So it looks like a machine running kdm (but perhaps not having a full kde installation) didn't get sensibly switched to a different display manager. I did the upgrade with dnf system-upgrade The fix was trivally just to use systemctl enable on lightdm and I now have a dm again. Version-Release number of selected component (if applicable): (Versions after upgrade) [dgilbert@dgilbert-t530 ~]$ rpm -qa | grep kdm kdm-settings-4.11.22-13.fc24.noarch f23-kdm-theme-23.0-6.fc24.noarch kdm-4.11.22-13.fc24.x86_64 f22-kdm-theme-22.3-7.fc24.noarch lightdm-1.10.6-4.fc24.x86_64 How reproducible: 2/2 Steps to Reproduce: 1. ?? Have an install with KDE, switch over to using an xfce session - not sure if I have a full KDE install any more? 2. Upgrade to f24 Actual results: No display manager is enabled Expected results: A display manager should be enabled after upgrade if one was enabled before. Additional info:
Comment 1 Rex Dieter 2016-05-19 12:41:14 UTC
Odd, of kdm was enabled previously, then kdm should still be enabled, what does this say? systemctl status kdm
Comment 2 Rex Dieter 2016-05-19 12:43:51 UTC
I guess it may be too late to check that, re-reading your comment(s), you already enabled lightdm, which in effect, would disable all other display managers (I believe). When you say " I had both lightdm and kdm installed but both were disabled", how did you check exactly? systemctl status lightdm systemctl status kdm or some other way? Another possibility: kdm was enabled, but was crashing or otherwise not starting properly after the upgrade.
Comment 3 Dr. David Alan Gilbert 2016-05-19 14:12:58 UTC
(In reply to Rex Dieter from comment #2) > I guess it may be too late to check that, re-reading your comment(s), you > already enabled lightdm, which in effect, would disable all other display > managers (I believe). > > When you say " I had both lightdm and kdm installed but both were disabled", > how did you check exactly? > systemctl status lightdm > systemctl status kdm > > or some other way? > > > Another possibility: kdm was enabled, but was crashing or otherwise not > starting properly after the upgrade. When it landed at the text console I did: systemctl list-unit-files | grep dm and it showed both kdm and lightdm as disabled. In my current state: [root@dgilbert-t530 dgilbert]# systemctl status kdm ● kdm.service - The KDE login manager Loaded: loaded (/usr/lib/systemd/system/kdm.service; disabled; vendor preset: Active: inactive (dead) I can go back through the logs with journalctl; since I'm still in my 1st f24 boot (in which I had no display manager): [root@dgilbert-t530 dgilbert]# journalctl -b 0 -u kdm -- No entries -- so I don't think it crashed (and I don't see anything in abrt-cli ls from today) Then -1 I think is the system-upgrade boot: [root@dgilbert-t530 dgilbert]# journalctl -b -1 -u kdm -- Logs begin at Mon 2013-12-09 16:12:48 GMT, end at Thu 2016-05-19 15:02:08 BST May 19 12:02:37 dgilbert-t530 systemd: Stopped The KDE login manager. In what I think was the last normal boot of f23 I see: [root@dgilbert-t530 dgilbert]# journalctl -b -2 -u kdm -- Logs begin at Mon 2013-12-09 16:12:48 GMT, end at Thu 2016-05-19 15:03:10 BST May 19 10:11:28 dgilbert-t530 systemd: Started The KDE login manager. May 19 10:11:28 dgilbert-t530 systemd: Starting The KDE login manager... May 19 10:11:28 dgilbert-t530 kdm: plymouth is running May 19 10:11:28 dgilbert-t530 kdm: plymouth is active on VT 1, reusing for May 19 10:11:28 dgilbert-t530 kdm: plymouth should quit after server start May 19 10:11:29 dgilbert-t530 kdm: Quitting Plymouth with transition May 19 10:11:29 dgilbert-t530 kdm: Is Plymouth still running? no May 19 11:38:08 dgilbert-t530 kdm: plymouth is NOT running May 19 11:38:08 dgilbert-t530 systemd: Stopping The KDE login manager... May 19 11:38:08 dgilbert-t530 systemd: Stopped The KDE login manager.
Comment 4 Rex Dieter 2016-05-19 14:19:54 UTC
Strange, I've no idea how kdm service could have gotten disabled in the upgrade process. It certainly is not intended. I'll triage this to kde-workspace (owner of kdm) for now, pending further investigation.
Comment 5 Fedora Blocker Bugs Application 2016-06-15 11:21:20 UTC
Proposed as a Freeze Exception for 24-final by Fedora user rdieter using the blocker tracking app because: Folks using kdm and upgrading to f24 currently end up with kdm being disabled. I *think* I know the cause, and if I'm right, the fix will need a freeze-exception to be included in GA release (an update can't fix it)
Comment 6 Rex Dieter 2016-06-15 18:25:11 UTC
adjusting summary to match symptoms
Comment 7 Paul Grabbe 2016-06-22 02:47:57 UTC
Had same problem after upgrade on two systems. However, I was running KDE with SDDM. Fixed with "systemctl enable sddm.service" and a reboot. So whatever the problem is with upgrade procedure, it is the same with kdm and sddm.
Comment 8 George 2016-06-22 06:21:25 UTC
+1 No KDM after upgrading to Fedora 24.
Comment 9 Adam Williamson 2016-06-23 23:37:27 UTC
This may be somehow caused by https://bugzilla.redhat.com/show_bug.cgi?id=1349664 , though on a quick look, the sddm spec file uses %systemd_post , which should result in this: if [ $1 -eq 1 ] ; then # Initial installation systemctl --no-reload preset sddm.service >/dev/null 2>&1 || : fi so it shouldn't run on an upgrade...
Comment 10 Rex Dieter 2016-06-24 21:52:50 UTC
*** Bug 1349855 has been marked as a duplicate of this bug. ***
Comment 11 Adam Williamson 2016-06-24 22:04:04 UTC
rex: i'm not really convinced this *is* caused by 1349664, at least not yet, I don't entirely see how it could be, unless you know of something else that would re-load the preset on upgrade.
Comment 12 Rex Dieter 2016-06-26 12:51:57 UTC
OK, my only other theory is that the problem here is because the package providing kdm.service changed f23: kde-settings-kdm f24: kdm-settings and on upgrade (with Obsoletes) the %postun scriptlet from kde-settings-kdm (effectively) disables it. This may be fixable with a %trigger, I'll try to investigate more soon.
Comment 13 Ben Cotton 2016-06-28 14:48:00 UTC
I also saw the same behavior on the two machines I upgrade (one from F23, the other directly from F22). Like the original report, I upgraded via dnf system-upgrade. Unlike the original report, kdm was the only display manager I have installed.
Comment 14 Aissen 2016-09-06 15:52:38 UTC
Just ran into this right now after upgrading from F23 to F24.
Comment 15 Rex Dieter 2016-12-13 14:49:16 UTC
*** Bug 1403730 has been marked as a duplicate of this bug. ***
Comment 16 Evgeny 2016-12-23 14:16:34 UTC
I have the same problem when switching from fedora 23 to fedora 24. The GUI is not working. kdm service was in the status of disabled. I turn it on command systemctl enable kdm Problem solved. I assume that the script is not finished with the update. ===== RUS ======================================================== У меня такая же проблема при переходе с fedora 23 до fedora 24. GUI не работал. kdm сервис был в статусе отключен. Я его включил командой systemctl enable kdm Проблема решена. Предполагаю что не доработан скрипт при обновление.
Comment 17 Fedora End Of Life 2017-07-25 20:49:20 UTC
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.
Comment 18 Fedora End Of Life 2017-08-08 14:34:28 UTC
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.