[SRU] Fix black screen on second boot due to video drivers not being ready.

[Scarlett Gately Moore]

[ Impact ]

 * Users experience black screen on second boot after fresh install due to video drivers not being ready.

 * The patch adds a needs for systemd to wait until drivers are complete before sddm login manager.

[ Test Plan ]

 * New install. Reboot 2 times, you will run into a black screen ( seems random, all video drivers affected though )

 * With the random nature of the bug it cannot be cleanly reproduced. Of 3 computers only one of mine experienced the problem.

[ Where problems could occur ]

 * systemd services boot order? possibly affect something else?

 * Tested in oracular and no issues have arised.

[ Other Info ]

 * Closes {LP #2065321)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Brian Murray (brian-murray)]

I looked at the source code for sddm in Oracular and discovered that this change is included in it so I'm marking the Oracular task as Fix Released.

[Brian Murray (brian-murray)]

I don't understand why a second bug was created for this SRU when using bug 2063143 (of which bug 2065321 is a duplicate) would likely have more people willing to do the verification.

[Brian Murray (brian-murray)]

Hello Scarlett, or anyone else affected,

Accepted sddm into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sddm/0.20.0-2ubuntu4.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Scarlett Gately Moore (scarlettmoore)]

Hi,
This fixes the bug for me. Thanks, Scarlett

[Scarlett Gately Moore (scarlettmoore)]

As for the duplicate bug, I didn't know about the first bug when I ran into the issue. I was later pointed to the first bug and then I linked them. Sorry for any confusion.

[Mario Limonciello (superm1)]

I do think it makes sense to pull in the change you're doing for now, but I do want to mention this is tech debt to pick up that approach to avoid this issue as that isn't merged and there isn't really line of sight to a proper fix:

https://github.com/sddm/sddm/pull/1924

[Mario Limonciello (superm1)]

I also think it should target Jammy because eventually the 6.8 kernels will backport there and introduce this bug to even more people.

[Jan Rathmann (kaiserclaudius)]

I enabled proposed and installed the updated package with

$sudo apt install sdddm=0.20.0-2ubuntu4.1

But my /usr/lib/systemd/system/sddm.service still looks like this:

------------------------
[Unit]
Description=Simple Desktop Display Manager
Documentation=man:sddm(1) man:sddm.conf(5)
# Change this if you want to start sddm in a different tty
<email address hidden>
<email address hidden>

# If using tty1 and plymouth, sddm will fail till plymouth stops
# consider using:
## After=plymouth-quit.service
# or to forcefully stop plymouth and start earlier:
## Conflicts=plymouth-quit-wait.service
## After=plymouth-start.service plymouth-quit-wait.service
## OnFailure=plymouth-quit.service

# Ordering
Conflicts=plymouth-quit-wait.service
After=systemd-user-sessions.service plymouth-start.service plymouth-quit-wait.service plymouth-quit.service systemd-logind.service
OnFailure=plymouth-quit.service

[Service]
# temporary safety check until all DMs are converted to correct
# display-manager.service symlink handling
ExecStartPre=/bin/sh -c '[ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/bin/sddm" ]'
ExecStart=/usr/bin/sddm
Restart=always
RestartSec=1s
EnvironmentFile=-/etc/default/locale

[Install]
Alias=display-manager.service
------------------------

It seems it is lacking the changes from the patch.

[Jan Rathmann (kaiserclaudius)]

And indeed I get failing boots even with sdddm=0.20.0-2ubuntu4.1.

[cascagrossa (cascagrossa-cascao)]

Installed sddm proposed 0.20.0-2ubuntu4.1 and nothing changed, still freeze with black screen on boot.

As workaround inserting "plymouth.use-simpledrm" to kernel parameters in grub configuration does show plymouth theme and switches to sddm normally.

Dell Inspiron 15 3530, NVIDIA MX550/INTEL Raptor Lake-P [Iris Xe Graphics].

[dastillero (dastillero)]

Installed sddm proposed sddm proposed 0.20.0-2ubuntu4.1 and the issue persists, but adding the changes shown in https://github.com/sddm/sddm/pull/1924/files to sddm.service file the issue is fixed.

[cascagrossa (cascagrossa-cascao)]

Confirm that the sddm proposed 0.20.0-2ubuntu4.1 doesn't have the suggested patch, but adding manually that lines to "/usr/lib/systemd/system/sddm.service" fixed the issue.

[KDE (kde-community)]

0.20.0-2ubuntu4.1 is not the correct version. 0.20.0-2ubuntu5 is the version I had. Looking into what may have happened.

[Scarlett Gately Moore (scarlettmoore)]

It is the correct version, Rik fixed it for me. The patch is in there. Still investigating.

[Scarlett Gately Moore (scarlettmoore)]

Alright, found the issue. So it seems we ship a custom sddm.service in debian/ and we do not use the provided sddm.service from upstream, and thus my patch has no significance. I have now patched the custom sddm.service file that is shipped. Unfortunately I do not have upload rights here and have asked Rik to please upload the new version. Sorry for any inconvenience.
Scarlett

[Timo Aaltonen (tjaalton)]

Hello Scarlett, or anyone else affected,

Accepted sddm into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sddm/0.20.0-2ubuntu4.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[cascagrossa (cascagrossa-cascao)]

I can confirm that the package proposed 0.20.0-2ubuntu4.2 has the patch and fixed the issue for me.
Kubuntu 24.04 Dell Inspiron 15 3530, NVIDIA MX550/INTEL Raptor Lake-P [Iris Xe Graphics].

[captaintrav (captaintrav)]

AMD Ryzen 7 3700X, ASUS PRIME B450M-A II, AMD Radeon RX 6650 XT system and also affected. Just thought I'd comment as I initially thought it was something to do with amdgpu, because system was happily running 22.04

[walther (walther-tw)]

Can confirm that version 0.20.0-2ubuntu4.2 of sddm fixes this issue on my fresh Kubuntu install (with xserver-xorg-video-amdgpu, Radeon RX 6600 XT).
Thanks for your work on this! I spent the better part of a day searching for the cause since the logs contained no errors or warnings.

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for sddm has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package sddm - 0.20.0-2ubuntu4.2

---------------
sddm (0.20.0-2ubuntu4.2) noble; urgency=medium

  * Apparently we use a custom sddm.service in debian/ and not
  the upstream provided sddm.service. Second attempt (LP: #2066275)

 -- Scarlett Moore <email address hidden> Mon, 01 Jul 2024 14:53:35 +0100