On 08/15/18 12:21, Thomas Letherby wrote:
Here's the full output of the commands used, and I pulled the
logs again:
https://pastebin.com/RfpfRqSj
I've not had a chance to dredge through them myself yet, I should be able to
tonight or tomorow I hope. In the mean time is there any other logs/diagnostics I
should check that might help?
Since this is in the output...
root@testlaptop ~]# systemctl status sddm
● sddm.service - Simple Desktop Display Manager
Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; vendor preset:
disabled)
Active: active (running) since Tue 2018-08-14 08:18:38 MST; 11min ago
Docs: man:sddm(1)
man:sddm.conf(5)
Main PID: 1435 (sddm)
Tasks: 4 (limit: 4915)
Memory: 87.9M
CGroup: /system.slice/sddm.service
├─1435 /usr/bin/sddm
└─1439 /usr/libexec/Xorg -nolisten tcp -auth
/var/run/sddm/{0ce5722f-5756-4200-99f9-c1c48ca177ce} -background none -noreset
-displayfd 16 -seat seat0 vt1
Aug 14 08:18:38 testlaptop.test.domail systemd[1]: Started Simple Desktop Display
Manager.
Aug 14 08:18:39 testlaptop.test.domail sddm-helper[1570]:
pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
And is exactly what you'd see on a system which has been rebooted and working
normally before a login. I would do the following as a "test"
I would install another DM. Just as "kdm", "lightdm", or
"gdm". Then I would do
systemctl -f enable (whatever DM you've picked)
And then reboot.
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.