Bug#1072840: Acknowledgement (sddm: Sddm crashes regularly)

[Helge Kreutzmann]

Hello Sddm maintainers,
I analysed this annyoing bug further. The following pattern seems to
hold always:

1. Start X session (various window managers, doest not seem to be
relevant)

2. Start several user consoles.

3. Work for some time, switching back and forth between the
virtual consoles and X

4. Log out from one (or more) user consoles.

5. Sddm crashes, sometimes directly, sometimes I can go into X (and
back to the consoles) one final time.

Step 3 seems to be important, because I tried to omit it, i.e. use a
freshly booted system and start and close several consoles without
doing something there and sddm did *not* crash. (I switched back and
forth between consoles and X serveral times).

Could it be ssh related? Because I use ssh a lot (both in X and on the
console) and I did not use this in my tests (I can do so next time).

Is there anything I should watch out for, or any other programm which
might interact with sddm during step 3, which I should try to trigger
to make this bug step-by-step reproducible?

Thanks!

Greetings

Helge

[Aurélien COUDERC]

Dear Helge,

Post by Helge Kreutzmann
Hello Sddm maintainers,
I analysed this annyoing bug further. The following pattern seems to

can you see anything in the kernel or system logs (dmesg or journalctl) ?

Without logs it will be difficult to understand what is going on. But at first sight I would lean towards a graphics driver bug more than an SDDM bug.

Maybe testing with different display managers (gdm, lightdm) could also help narrowing down the issue ?


Happy hacking,
--
Aurélien

[Helge Kreutzmann]

Hello Aurélien,
the following is 100% reproducible:

(1. Boot machine )
2. Log into Console 7 (it only happens with 7)
3. Log out again

→ Sddm is gone

For all other consoles it works (I tried 2
6 and 8
12).

Can you try this as well?

Post by Aurélien COUDERC

Post by Helge Kreutzmann
Hello Sddm maintainers,
I analysed this annyoing bug further. The following pattern seems to

can you see anything in the kernel or system logs (dmesg or journalctl) ?

2024-08-07T17:24:58.765735+02:00 twentytwo sddm[1522]: Signal received: SIGTERM
2024-08-07T17:24:58.765803+02:00 twentytwo systemd[1]: Stopping sddm.service - Simple Desktop Display Manager...
2024-08-07T17:24:58.766008+02:00 twentytwo sddm-helper[3452]: Signal received: SIGTERM
2024-08-07T17:24:58.766946+02:00 twentytwo sddm-helper[3452]: [PAM] Closing session
2024-08-07T17:24:58.770046+02:00 twentytwo sddm-helper[3452]: [PAM] Ended.
2024-08-07T17:24:58.771092+02:00 twentytwo sddm[1522]: Auth: sddm-helper exited with 255
2024-08-07T17:24:58.771147+02:00 twentytwo sddm[1522]: Socket server stopping...
2024-08-07T17:24:58.771187+02:00 twentytwo sddm[1522]: Socket server stopped.
2024-08-07T17:24:58.771218+02:00 twentytwo sddm[1522]: Display server stopping...
2024-08-07T17:24:58.825643+02:00 twentytwo sddm[1522]: Display server stopped.
2024-08-07T17:24:58.825738+02:00 twentytwo sddm[1522]: Running display stop script ("/usr/share/sddm/scripts/Xstop")
2024-08-07T17:24:58.828508+02:00 twentytwo systemd[1]: sddm.service: Deactivated successfully.
2024-08-07T17:24:58.828736+02:00 twentytwo systemd[1]: Stopped sddm.service - Simple Desktop Display Manager.
2024-08-07T17:24:58.828895+02:00 twentytwo systemd[1]: sddm.service: Consumed 578ms CPU time, 160.9M memory peak.

Or 2nd try just afterwards (with some more context):
2024-08-07T17:25:21.985606+02:00 twentytwo systemd[1]: ***@tty7.service: Deactivated successfully.
2024-08-07T17:25:22.018143+02:00 twentytwo systemd[1]: run-credentials-getty\x40tty7.service.mount: Deactivated successfully.
2024-08-07T17:25:22.019192+02:00 twentytwo systemd[1]: ***@tty7.service: Scheduled restart job, restart counter is at 1.
2024-08-07T17:25:22.020508+02:00 twentytwo sddm[3717]: Signal received: SIGTERM
2024-08-07T17:25:22.020553+02:00 twentytwo systemd[1]: Stopping sddm.service - Simple Desktop Display Manager...
2024-08-07T17:25:22.020781+02:00 twentytwo sddm-helper[3826]: Signal received: SIGTERM
2024-08-07T17:25:22.021592+02:00 twentytwo sddm-helper[3826]: [PAM] Closing session
2024-08-07T17:25:22.023305+02:00 twentytwo sddm-helper[3826]: [PAM] Ended.
2024-08-07T17:25:22.025129+02:00 twentytwo sddm[3717]: Auth: sddm-helper exited with 255
2024-08-07T17:25:22.025175+02:00 twentytwo sddm[3717]: Socket server stopping...
2024-08-07T17:25:22.025212+02:00 twentytwo sddm[3717]: Socket server stopped.
2024-08-07T17:25:22.025241+02:00 twentytwo sddm[3717]: Display server stopping...
2024-08-07T17:25:22.080872+02:00 twentytwo sddm[3717]: Display server stopped.
2024-08-07T17:25:22.080989+02:00 twentytwo sddm[3717]: Running display stop script ("/usr/share/sddm/scripts/Xstop")
2024-08-07T17:25:22.083619+02:00 twentytwo systemd[1]: sddm.service: Deactivated successfully.
2024-08-07T17:25:22.083858+02:00 twentytwo systemd[1]: Stopped sddm.service - Simple Desktop Display Manager.
2024-08-07T17:25:22.085111+02:00 twentytwo systemd[1]: Started ***@tty7.service - Getty on tty7.
2024-08-07T17:25:25.325658+02:00 twentytwo systemd[1]: Stopping ***@tty7.service - Getty on tty7...
2024-08-07T17:25:25.325953+02:00 twentytwo systemd[1]: ***@tty7.service: Deactivated successfully.
2024-08-07T17:25:25.326075+02:00 twentytwo systemd[1]: Stopped ***@tty7.service - Getty on tty7.
2024-08-07T17:25:25.328211+02:00 twentytwo systemd[1]: run-credentials-getty\x40tty7.service.mount: Deactivated successfully.

Post by Aurélien COUDERC
Without logs it will be difficult to understand what is going on. But at first sight I would lean towards a graphics driver bug more than an SDDM bug.

I really don't think so.

Post by Aurélien COUDERC
Maybe testing with different display managers (gdm, lightdm) could also help narrowing down the issue ?

Yes, I still need to do this.

Greetings

Helge