Date: Sun, 26 Jun 2016 11:41:21 -0400 From: "Mark C. Allman"mcallman@allmanpc.com Subject: Re: No Graphical Login After Fedora 24 Upgrade From Fedora 23 To:users@lists.fedoraproject.org Message-ID:2f2ce2bd-5601-811c-6024-2aa8da6a7e83@allmanpc.com Content-Type: text/plain; charset=utf-8
On 06/26/2016 10:21 AM, David Dembrow wrote:
After completing the fedora 24 upgrade on a fedora 23 system there was no graphical login and the system appeared to be running in console mode (run level 3).
I have always used KDE as the display manager and desktop. I noticed a similar problem posted but none of its recommendations were appropriate for my system.
I found the graphical.target set as the default (systemctl get-default). Then I noticed the graphical.target expects to have a display-manager.service but the display-manager.service file was missing. from the /etc/systemd/system directory.
I copied the /etc/systemd/system/display-manager.service file from a fedora 23 system and enabled the service (systemctl enable display-manager.service). Started the service (systemctl start display-manager.service) and poof the graphical kde login manager and desktop returned.
Should this get posted as a bug or is the kde login manager expected to disappear with wayland? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct:http://fedoraproject.org/code-of-conduct Guidelines:http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away:http://ask.fedoraproject.org
It's now the sddm.service. I had the same problem. We all need the usual "dnf install sddm, systemctl enable sddm; systemctl start sddm."
After I looked at a display-manager.service instance on one of my remaining F23 systems I remembered that sddm was on the way: [me@rigel ~]$ cat /etc/systemd/system/display-manager.service [Unit] Description=Simple Desktop Display Manager Documentation=man:sddm(1) man:sddm.conf(5) Conflicts=getty@tty1.service After=systemd-user-sessions.servicegetty@tty1.service plymouth-quit.service
[Service] ExecStart=/usr/bin/sddm Restart=always #PrivateTmp=yes
[Install] Alias=display-manager.service
It worked for me but that doesn't mean it solves the problem for everyone.
-- Mark C. Allman -- Founder, See How You Ski,www.seehowyouski.com -- Sr. Project Manager, Allman Professional Consulting,www.allmanpc.com -- Twitter: @allmanpc
Mr Allman,
Thanks for the reply. I did not have sddm installed, I did have kdm (but without a link to display-manager). I can use sddm if that is going to be the future, but I still prefer kdm - and with some advice from this list I can correctly use either one.
Regards, ---d.dembrow