Date: Sun, 26 Jun 2016 22:37:30 +0800
From: Ed Greshko<ed.greshko(a)greshko.com>
Subject: Re: No Graphical Login After Fedora 24 Upgrade From Fedora 23
To:users@lists.fedoraproject.org
Message-ID:<e943f66d-26d3-3eef-ce4d-58ff5806fe3a@greshko.com>
Content-Type: text/plain; charset=utf-8
On 06/26/16 22:21, 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.
Well, first of all, /etc/systemd/system/display-manager.service should*not* be a file,
but a symbolic link.
It should either link to /usr/lib/systemd/system/sddm.service or
/usr/lib/systemd/system/kdm.service if you are using kdm.
What does "systemctl status display-manager" return?
Mr Greshko,
Thanks very much for the correction. I did not look for symbolic links and I did not have
sddm installed on my system. I did have a kdm.service file and enabling kdm creates the
link as expected. 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.
The systemctl status display-manager command returns the following (before I added the
display-manager.service file):
[] display-manager.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
Regards,
---d.dembrow