Thanks, that makes more sense, now why is apport not catching that one? Could you look if there is something registered in /var/log/apport.log?
does it makes a difference if you $ sudo service apport start force_start=1 then trigger the issue and see if apport picks the problem -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1871580 Title: Session killed instead of suspended on screen lock Status in gnome-session package in Ubuntu: Incomplete Bug description: Running focal (updated to 2020-04-08), ubuntu-on-wayland session. Trigger: either lock the screen manually (top-right-corner menu -> Lock) or wait for the auto-lock timer (Settings -> Privacy -> Screen Lock). Expected result: after unlock, previous session resumes. Observed: see login dialog instead of unlock dialog, previous session and all processes appear to have been killed. This is a fairly serious usability regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-session 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 10:35:16 2020 InstallationDate: Installed on 2019-05-27 (316 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-04-06 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
