1 |
I'm trying to understand why one PC in particular fails to start SDDM since an |
2 |
update to x11-misc/sddm-0.18.1-r6 and ends up with a blank page on VT7. I |
3 |
suspect some pam module malfunction, but I don't understand why this happens |
4 |
or how to troubleshoot it. Interestingly, if I restart the display-manager |
5 |
service manually, SDDM starts and no longer exits. :-/ |
6 |
|
7 |
This is what syslog shows upon boot: |
8 |
================================ |
9 |
Apr 9 09:20:04 localhost sddm-helper[4074]: pam_unix(sddm-greeter:session): |
10 |
session opened for user sddm(uid=104) by (uid=0) |
11 |
Apr 9 09:20:04 localhost kernel: elogind-daemon[1349]: New session c1 of user |
12 |
sddm. |
13 |
Apr 9 09:20:05 localhost chronyd[3554]: Selected source 192.169.1.1 |
14 |
Apr 9 09:20:05 localhost sddm-helper[4074]: pam_unix(sddm-greeter:session): |
15 |
session closed for user sddm |
16 |
Apr 9 09:20:05 localhost kernel: elogind-daemon[1349]: Removed session c1. |
17 |
========================================== |
18 |
|
19 |
Checking if the display manager service has died I see rc-service reports it |
20 |
is running! Then, ps reveals this much: |
21 |
|
22 |
root 3757 0.1 0.1 137296 17092 ? Ssl 12:21 0:00 /usr/bin/sddm |
23 |
root 3898 5.7 0.5 1009092 85500 tty7 Ssl+ 12:21 0:02 /usr/bin/X - |
24 |
nolisten tcp -auth /var/run/sddm/{77032685-d24f-482b-9634-49fce5f11fa0} - |
25 |
background none -noreset -displayfd 17 -seat seat0 vt7 |
26 |
|
27 |
but all I get on VT7 is a blank screen with a cursor on the top left and no |
28 |
mouse or a graphic DM. |
29 |
|
30 |
|
31 |
Then I login as root on a console and restart the service: |
32 |
================================================ |
33 |
Apr 9 09:20:38 localhost login[3935]: pam_unix(login:session): session opened |
34 |
for user root(uid=0) by LOGIN(uid=0) |
35 |
Apr 9 09:20:38 localhost kernel: elogind-daemon[1349]: New session 2 of user |
36 |
root. |
37 |
Apr 9 09:20:38 localhost login[4087]: ROOT LOGIN on '/dev/tty1' |
38 |
Apr 9 09:20:41 localhost start-stop-daemon[4111]: Will stop /usr/bin/sddm |
39 |
Apr 9 09:20:41 localhost start-stop-daemon[4112]: Will stop /usr/bin/sddm |
40 |
Apr 9 09:20:41 localhost start-stop-daemon[4112]: Will stop PID 3787 |
41 |
Apr 9 09:20:41 localhost start-stop-daemon[4112]: Sending signal 15 to PID |
42 |
3787 |
43 |
Apr 9 09:20:41 localhost kernel: [drm] enabling PCIE gen 2 link speeds, |
44 |
disable with radeon.pcie_gen2=0 |
45 |
Apr 9 09:20:41 localhost kernel: [drm] PCIE GART of 1024M enabled (table at |
46 |
0x0000000000040000). |
47 |
Apr 9 09:20:41 localhost kernel: radeon 0000:01:00.0: WB enabled |
48 |
Apr 9 09:20:41 localhost kernel: radeon 0000:01:00.0: fence driver on ring 0 |
49 |
use gpu addr 0x0000000080000c00 |
50 |
Apr 9 09:20:41 localhost kernel: radeon 0000:01:00.0: fence driver on ring 1 |
51 |
use gpu addr 0x0000000080000c04 |
52 |
Apr 9 09:20:41 localhost kernel: radeon 0000:01:00.0: fence driver on ring 2 |
53 |
use gpu addr 0x0000000080000c08 |
54 |
Apr 9 09:20:41 localhost kernel: radeon 0000:01:00.0: fence driver on ring 3 |
55 |
use gpu addr 0x0000000080000c0c |
56 |
Apr 9 09:20:41 localhost kernel: radeon 0000:01:00.0: fence driver on ring 4 |
57 |
use gpu addr 0x0000000080000c10 |
58 |
Apr 9 09:20:41 localhost kernel: debugfs: File 'radeon_ring_gfx' in directory |
59 |
'1' already present! |
60 |
Apr 9 09:20:41 localhost kernel: debugfs: File 'radeon_ring_cp1' in directory |
61 |
'1' already present! |
62 |
Apr 9 09:20:41 localhost kernel: debugfs: File 'radeon_ring_cp2' in directory |
63 |
'1' already present! |
64 |
Apr 9 09:20:41 localhost kernel: debugfs: File 'radeon_ring_dma1' in |
65 |
directory '1' already present! |
66 |
Apr 9 09:20:41 localhost kernel: debugfs: File 'radeon_ring_dma2' in |
67 |
directory '1' already present! |
68 |
Apr 9 09:20:42 localhost kernel: [drm] ring test on 0 succeeded in 1 usecs |
69 |
Apr 9 09:20:42 localhost kernel: [drm] ring test on 1 succeeded in 1 usecs |
70 |
Apr 9 09:20:42 localhost kernel: [drm] ring test on 2 succeeded in 1 usecs |
71 |
Apr 9 09:20:42 localhost kernel: [drm] ring test on 3 succeeded in 4 usecs |
72 |
Apr 9 09:20:42 localhost kernel: [drm] ring test on 4 succeeded in 4 usecs |
73 |
Apr 9 09:20:42 localhost kernel: [drm] ib test on ring 0 succeeded in 0 usecs |
74 |
Apr 9 09:20:42 localhost kernel: [drm] ib test on ring 1 succeeded in 0 usecs |
75 |
Apr 9 09:20:42 localhost kernel: [drm] ib test on ring 2 succeeded in 0 usecs |
76 |
Apr 9 09:20:42 localhost kernel: [drm] ib test on ring 3 succeeded in 0 usecs |
77 |
Apr 9 09:20:42 localhost kernel: [drm] ib test on ring 4 succeeded in 0 usecs |
78 |
Apr 9 09:20:43 localhost sddm-helper[4209]: pam_unix(sddm-greeter:session): |
79 |
session opened for user sddm(uid=104) by (uid=0) |
80 |
Apr 9 09:20:43 localhost kernel: elogind-daemon[1349]: Existing logind |
81 |
session ID 2 used by new audit session, ignoring. |
82 |
Apr 9 09:20:43 localhost kernel: elogind-daemon[1349]: New session c2 of user |
83 |
sddm. |
84 |
===== |
85 |
|
86 |
Thereafter SDDM runs on VT7 as expected without exiting. The ps output shows |
87 |
more: |
88 |
|
89 |
root 4187 0.0 0.1 137444 15656 ? Ssl 12:22 0:00 /usr/bin/sddm |
90 |
root 4197 3.8 0.5 1009092 83352 tty7 Ssl+ 12:22 0:01 /usr/bin/X - |
91 |
nolisten tcp -auth /var/run/sddm/{9cb9ef8e-f25b-4272-9605-8da9ddbef75c} - |
92 |
background none -noreset -displayfd 17 -seat seat0 vt7 |
93 |
root 4213 0.0 0.0 54060 12948 ? S 12:22 0:00 /usr/libexec/ |
94 |
sddm-helper --socket /tmp/sddm-auth500f20d1-4477-420c-9eec-3a53462ef3e6 --id 2 |
95 |
--start /usr/bin/sddm-greeter --socket /tmp/sddm-:0-ivjakp --user sddm -- |
96 |
greeter |
97 |
sddm 4214 3.5 0.7 997596 111548 ? Sl 12:22 0:01 /usr/bin/ |
98 |
sddm-greeter --socket /tmp/sddm-:0-ivjakp |
99 |
sddm 4220 0.0 0.0 4696 2408 ? S 12:22 0:00 dbus-launch |
100 |
--autolaunch dd882e08972cbb412f072c225d00d9b6 --binary-syntax --close-stderr |
101 |
sddm 4221 0.0 0.0 4824 2040 ? Ss 12:22 0:00 /usr/bin/ |
102 |
dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session |
103 |
|
104 |
Any ideas why this is happening, on this PC only and how to fix it? |