[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



Hello Aurélien,
did you have a chance to test this? This is really anyoing.

I just discovered that it is also the other way round:
run (as root)
systemctl restart sddm
→ Console 7 is closed and programms running there are killed.

Again, all other (of my 12) consoles are unaffected.

Greetings

          Helge

Am Wed, Aug 07, 2024 at 03:47:37PM +0000 schrieb 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?
> 
> Am Sun, Jun 23, 2024 at 09:39:40AM +0200 schrieb Aurélien COUDERC:
> > Le 23 juin 2024 09:28:41 GMT+02:00, Helge Kreutzmann <debian@helgefjell.de> a écrit :
> > >Hello Sddm maintainers,
> > >I analysed this annyoing bug further. The following pattern seems to
> > >hold always:
> > 
> > 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]: getty@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]: getty@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 getty@tty7.service - Getty on tty7.
> 2024-08-07T17:25:25.325658+02:00 twentytwo systemd[1]: Stopping getty@tty7.service - Getty on tty7...
> 2024-08-07T17:25:25.325953+02:00 twentytwo systemd[1]: getty@tty7.service: Deactivated successfully.
> 2024-08-07T17:25:25.326075+02:00 twentytwo systemd[1]: Stopped getty@tty7.service - Getty on tty7.
> 2024-08-07T17:25:25.328211+02:00 twentytwo systemd[1]: run-credentials-getty\x40tty7.service.mount: Deactivated successfully.
> 
> > 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.
> 
> > Maybe testing with different display managers (gdm, lightdm) could also help narrowing down the issue ?
> 
> Yes, I still need to do this.
> 
> Greetings
> 
>          Helge
> -- 
>       Dr. Helge Kreutzmann                     debian@helgefjell.de
>            Dipl.-Phys.                   http://www.helgefjell.de/debian.php
>         64bit GNU powered                     gpg signed mail preferred
>            Help keep free software "libre": http://www.ffii.de/



-- 
      Dr. Helge Kreutzmann                     debian@helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

Attachment: signature.asc
Description: PGP signature


Reply to: