Hi,
I upgraded F27 yesterday night and I cannot start sddm this morning. I
just get a black screen with the mouse.
Here is the output of systemctl status sddm:
● sddm.service - Simple Desktop Display Manager
Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled;
vendor preset: disabled)
On 07/07/18 12:29, Frédéric wrote:
> Hi,
>
> I upgraded F27 yesterday night and I cannot start sddm this morning. I
> just get a black screen with the mouse.
> Here is the output of systemctl status sddm:
> ● sddm.service - Simple Desktop Display Manager
>Loaded: loaded (/usr/lib/systemd/system
ok, but how to start X from the CLI though?
On Fri, Jul 6, 2018 at 11:30 PM, Ed Greshko wrote:
> On 07/07/18 12:29, Frédéric wrote:
> > Hi,
> >
> > I upgraded F27 yesterday night and I cannot start sddm this morning. I
> > just get a black screen with the mouse.
> > Here is the output of system
On 07/07/2018 06:10 PM, solarflow99 wrote:
ok, but how to start X from the CLI though?
If you normally boot to a CLI, startx will work, but each DE generally
has its own customized script. As an example, I use Xfce, and would
properly use startxfce4.
> in /etc/pam.d/sddm-greeter check to see if you have the line
> session optional pam_elogind.so
I had it, I commented it with "-" and now I get status active
(running) for sddm.
However, the login screen is still black with only the mouse.
journalctl says:
Jul 08 21:41:18 gamma
I have the same problem too
On Sun, Jul 8, 2018 at 12:46 PM, Frédéric wrote:
> > in /etc/pam.d/sddm-greeter check to see if you have the line
> > session optional pam_elogind.so
>
> I had it, I commented it with "-" and now I get status active
> (running) for sddm.
> However, t
Frédéric wrote:
> #2 0x7fc06f4677a7 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5)
This line means the fatal error was logged to syslog/journal. Look there
for more details.
-- Rex
___
users mailing list -- users@lists.fedoraproject.org
To un
>> #2 0x7fc06f4677a7 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5)
>
> This line means the fatal error was logged to syslog/journal. Look there
> for more details.
But isn't it what journalctl gives me which I just showed? Where else
should I look at?
F
_
