SDDM issue after upgrade

Ylarod · 2021-09-26 00:56:33

After I upgrade my arch, and reboot. The screen shows 'DisplayPort no signal'.

However, just key in my password and it successfully entered KDE.

I tried reinstalling & downgrading nvidia driver, sddm, and changing themes. But it didn't work.

I don't know how to solve this issue. Can anyone give me a hand with this?

V1del · 2021-09-26 03:12:34

Sounds like the you run into the usual early loading race with the graphical environment trying to start before the driver is ready, see: https://wiki.archlinux.org/title/NVIDIA … de_setting set up the parameter and the mkinitcpio modules and the hook.

Ylarod · 2021-09-26 04:54:34

V1del wrote:

Sounds like the you run into the usual early loading race with the graphical environment trying to start before the driver is ready, see: https://wiki.archlinux.org/title/NVIDIA … de_setting set up the parameter and the mkinitcpio modules and the hook.

thanks for the reply !

I did those below, but still not working.

add `nvidia-drm.modeset=1` kernel parameter to /boot/grub/grub.cfg

add `nvidia`, `nvidia_modeset`, `nvidia_uvm` and `nvidia_drm` to /etc/mkinitcpio.conf

and run `sudo mkinitcpio -P`

then reboot.

full log here
https://gist.github.com/Ylarod/0154e7bb … 9d164d8e1e

V1del · 2021-09-26 09:37:47

Hmm no signs of an issue can you post your /var/log/Xorg.0.log, did you set up/configure any xorg config ?

Ylarod · 2021-09-26 09:46:22

V1del wrote:

Hmm no signs of an issue can you post your /var/log/Xorg.0.log, did you set up/configure any xorg config ?

Sure.
https://gist.github.com/Ylarod/5313d9bd … ac7cc57270

Ylarod · 2021-09-26 09:48:36

V1del wrote:

Hmm no signs of an issue can you post your /var/log/Xorg.0.log, did you set up/configure any xorg config ?

Xorg config is generated by `sudo nvidia-xconfig` without modification.
https://gist.github.com/Ylarod/5313d9bd … ac7cc57270

V1del · 2021-09-26 10:05:10

What happens if you remove that config file? Just running it to have ran it is never necessary and it can in fact generate config that uses invalid/outdated identifiers/identifiers that change between updates of kernel/xorg/module (case in point I don't see a world where

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Monitor Vendor"
    ModelName      "Monitor Model"
EndSection

is ever a valid monitor identifier). It's likely that the config in there is invalid, and then gets replaced with whatever kscreen does once you are logged in.

Last edited by V1del (2021-09-26 10:05:51)

Ylarod · 2021-09-26 10:49:39

V1del wrote:

What happens if you remove that config file? Just running it to have ran it is never necessary and it can in fact generate config that uses invalid/outdated identifiers/identifiers that change between updates of kernel/xorg/module (case in point I don't see a world where
Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Monitor Vendor"
    ModelName      "Monitor Model"
EndSection
is ever a valid monitor identifier). It's likely that the config in there is invalid, and then gets replaced with whatever kscreen does once you are logged in.

There was nothing changed after removing it.

Ylarod · 2021-09-26 10:51:18

V1del wrote:

What happens if you remove that config file? Just running it to have ran it is never necessary and it can in fact generate config that uses invalid/outdated identifiers/identifiers that change between updates of kernel/xorg/module (case in point I don't see a world where
Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Monitor Vendor"
    ModelName      "Monitor Model"
EndSection
is ever a valid monitor identifier). It's likely that the config in there is invalid, and then gets replaced with whatever kscreen does once you are logged in.

I saw many TypeError from sddm-greeter. Is something wrong with it ?

V1del · 2021-09-26 11:48:31

One other thing I can think of is a theming issue, maybe try one of the integrated themes/breeze, rather than McMojave.

seth · 2021-09-26 12:52:22

From the "no signal" SDDM, switch to a different VT (ctrl+alt+f2) and

export DISPLAY=:0
xrandr -q

Then login and compare it to a "xrandr -q" during the KDE session.

It seems to use 144Hz, possibly https://wiki.archlinux.org/title/Variable_refresh_rate issue?

Ylarod · 2021-09-26 16:10:45

V1del wrote:

One other thing I can think of is a theming issue, maybe try one of the integrated themes/breeze, rather than McMojave.

breeze tried, not working

Ylarod · 2021-09-26 16:12:46

seth wrote:

From the "no signal" SDDM, switch to a different VT (ctrl+alt+f2) and
export DISPLAY=:0
xrandr -q
Then login and compare it to a "xrandr -q" during the KDE session.
It seems to use 144Hz, possibly https://wiki.archlinux.org/title/Variable_refresh_rate issue?

TTY2:

Invalid MIT-MAGIC-COOKIE-1 key Can't open display :0

After Login:

Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 32767 x 32767
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm
   2560x1440     59.95 + 144.01*  120.00    99.95  
   1920x1080    119.88   100.00    60.00    59.94    50.00  
   1440x900      59.89  
   1440x576      50.00  
   1440x480      59.94  
   1280x1024     75.02    60.02  
   1280x720      59.94    50.00  
   1152x864      75.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32    56.25  
   720x576       50.00  
   640x480       75.00    72.81    59.94  
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)

Last edited by Ylarod (2021-09-27 04:59:17)

seth · 2021-09-26 16:17:33

Please use "code" tags.

Invalid MIT-MAGIC-COOKIE-1 key Can't open display :0

SDDM probably runs as root?

Ylarod · 2021-09-27 04:58:42

seth wrote:

Please use "code" tags.
Invalid MIT-MAGIC-COOKIE-1 key Can't open display :0
SDDM probably runs as root?

Yes, but how to solve it?

seth · 2021-09-27 06:06:43

Run xrandr as root?

HelloEdit · 2021-09-27 20:47:32

Hey everyone, I am experiencing the same problem here after an upgrade. Like OP said, keying the password work. I have something like this in my journal

sept. 26 13:40:50 msi-arch sddm[411]: Session started
sept. 27 00:27:41 msi-arch sddm[411]: Authentication error: "Process crashed"
sept. 27 00:27:41 msi-arch sddm[411]: Auth: sddm-helper crashed (exit code 15)
sept. 27 00:27:41 msi-arch sddm[411]: Authentication error: "Process crashed"
sept. 27 00:27:41 msi-arch sddm[411]: Auth: sddm-helper exited with 15
sept. 27 00:27:41 msi-arch sddm[411]: Socket server stopping...

Ylarod · 2021-09-28 13:49:33

seth wrote:

Run xrandr as root?

Can't open display

seth · 2021-09-28 13:51:53

didyouexportthedisplayvariable?

mmbossoni · 2021-09-29 21:09:45

I have the very same problem.
I exported the display variable and ran xrandr -q, but got invalid protocol message even when running as root.
Auto login does work, so KDE session itself is fine, just sddm is failing.

seth · 2021-09-29 21:13:08

https://github.com/archlinux/svntogit-p … m.sysusers

ps aux | grep sddm

Does it actually run as root?

Edit:
https://wiki.archlinux.org/title/Xhost
Don't forget to close the server again.

Last edited by seth (2021-09-29 21:14:16)

mmbossoni · 2021-09-30 00:07:09

Sorry if I'm being dumb but, I tried running xhost + as root and as sddm user after

su -m sddm

All of them resulted in

No Protocol Specified
Unable to open display :0.

As for ps command output

root         551  0.0  0.1 141844 17824 ?        Ssl  18:19   0:00 /usr/bin/sddm
root       61380  3.5  0.2 25267808 48848 tty1   Ss+  21:00   0:01 /usr/lib/Xorg -dpi 0 -background none -seat seat0 vt1 -auth /var/run/sddm/{8c9dca35-afff-417d-bd62-9929ab9d9939} -noreset -displayfd 18
root       61387  0.0  0.1  64668 16632 ?        S    21:00   0:00 /usr/lib/sddm/sddm-helper --socket /tmp/sddm-auth08aecebc-3428-4947-b837-f777735039a2 --id 7 --start /usr/bin/sddm-greeter --socket /tmp/sddm-:0-MyxXAB --theme /usr/share/sddm/themes/breeze --user sddm --greeter
sddm       61389  0.2  0.0  16588  9736 ?        Ss   21:00   0:00 /usr/lib/systemd/systemd --user
sddm       61390  0.0  0.0 168752  3184 ?        S    21:00   0:00 (sd-pam)
sddm       61397  3.2  0.9 1623632 151680 ?      Sl   21:00   0:01 /usr/bin/sddm-greeter --socket /tmp/sddm-:0-MyxXAB --theme /usr/share/sddm/themes/breeze
sddm       61400  0.0  0.0  12020  5204 ?        Ss   21:00   0:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
marcelo    61425  0.0  0.0   6828  2340 tty2     S+   21:01   0:00 grep sddm

mmbossoni · 2021-09-30 00:28:49

OK, executed xrandr on Xsetup script of sddm
xrandr output there is the same when logged in.
But I don't know if that is enough because it will just list resolutions of the X server for root user, not for sddm-greeter.

seth · 2021-09-30 06:19:37

*Exactly* the same?
The critical part is where the "+" and the "*" are.

mmbossoni · 2021-09-30 20:27:00

This is from sddm

DP-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 527mm x 296mm
   1920x1080     60.00 + 144.00*  119.98   119.88    99.93    59.94    50.00  
   1680x1050     59.88

This is from logged session

DP-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 527mm x 296mm
   1920x1080     60.00 + 144.00*  119.98   119.88    99.93    59.94    50.00  
   1680x1050     59.88

I also tried to force xrandr to setup sddm to 1920x1080@60, but same black screen.
Also, connected to it using x11vnc, black screen as well.

Last edited by mmbossoni (2021-09-30 20:28:18)

Arch Linux

#1 2021-09-26 00:56:33

SDDM issue after upgrade

#2 2021-09-26 03:12:34

Re: SDDM issue after upgrade

#3 2021-09-26 04:54:34

Re: SDDM issue after upgrade

#4 2021-09-26 09:37:47

Re: SDDM issue after upgrade

#5 2021-09-26 09:46:22

Re: SDDM issue after upgrade

#6 2021-09-26 09:48:36

Re: SDDM issue after upgrade

#7 2021-09-26 10:05:10

Re: SDDM issue after upgrade

#8 2021-09-26 10:49:39

Re: SDDM issue after upgrade

#9 2021-09-26 10:51:18

Re: SDDM issue after upgrade

#10 2021-09-26 11:48:31

Re: SDDM issue after upgrade

#11 2021-09-26 12:52:22

Re: SDDM issue after upgrade

#12 2021-09-26 16:10:45

Re: SDDM issue after upgrade

#13 2021-09-26 16:12:46

Re: SDDM issue after upgrade

#14 2021-09-26 16:17:33

Re: SDDM issue after upgrade

#15 2021-09-27 04:58:42

Re: SDDM issue after upgrade

#16 2021-09-27 06:06:43

Re: SDDM issue after upgrade

#17 2021-09-27 20:47:32

Re: SDDM issue after upgrade

#18 2021-09-28 13:49:33

Re: SDDM issue after upgrade

#19 2021-09-28 13:51:53

Re: SDDM issue after upgrade

#20 2021-09-29 21:09:45

Re: SDDM issue after upgrade

#21 2021-09-29 21:13:08

Re: SDDM issue after upgrade

#22 2021-09-30 00:07:09

Re: SDDM issue after upgrade

#23 2021-09-30 00:28:49

Re: SDDM issue after upgrade

#24 2021-09-30 06:19:37

Re: SDDM issue after upgrade

#25 2021-09-30 20:27:00

Re: SDDM issue after upgrade

Board footer