[Bug 1987409] Re: All open applications close after "screen blank" in Ubuntu 22.04 using Wayland
@vanvugt The first option you gave me didn't work, so I included the links to the errors in the main body of my original bug description as per the second option you listed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1987409 Title: All open applications close after "screen blank" in Ubuntu 22.04 using Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987409/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987409] [NEW] All open applications close after "screen blank" in Ubuntu 22.04 using Wayland
Public bug reported: Ubuntu Version: 22.04 gnome-shell Version: 42.2-0ubuntu0.2 What I Expected to Happen: After user inactivity, computer goes into a locked state. When I log back in after user inactivity, all my previously opened applications are still running. What Actually Happened: After user inactivity, all my applications in my session are closed after logging back in. Details: This occurred on a workstation that was wiped of its previous data and Ubuntu 22.04 installed from a flashdrive. I am getting very similar results to a bug in: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987209 About my system (from About menu in Settings) - Dell OptiPlex 3050 - 32 GB RAM - Intel® Core™ i7-7700 CPU @ 3.60GHz × 8 - AMD® Radeon rx 550 / 550 series / Mesa Intel® HD Graphics 630 (KBL GT2) - GNOME Version: 42.2 Monitors being used: - Dell U2211Ht 22" - Acer G226HQL 22" - LG 32MA68HY 27" I have reproduced this error by setting the 'Screen Blank' setting to 1 minute (just so I don't have to wait very long), then waiting for the system to enter the screen blank state. The following then happens. 1. Everything seems to be fading out as normal 2. Screens no longer have data that needs to be displayed, they go into sleep mode 3. After a brief period, screens are forced back on (where when this problem isn't happening, screens will remain in sleep mode until input provided by user) 4. System displays the dark login screen as if I was never logged in. 5. After signing in, all my open applications have been closed. I have managed to circumvent this issue by choosing the option 'Ubuntu on xorg' before signing in, or by uncommenting the line #WaylandEnable=false in /etc/gdm3/custom.conf. I then repeat the test described above after using either of these methods and my session is saved, no issues. I have attached my own results that I found after a 'journalctl -b0'. The text in the file are some of the lines before and after the line: gnome-shell[]: segfault at Links to error reports (I got a bunch trying to replicate the issue): - https://errors.ubuntu.com/oops/f429c99a-2262-11ed-978c-fa163e993415 - https://errors.ubuntu.com/oops/a07c3a5c-225e-11ed-978c-fa163e993415 - https://errors.ubuntu.com/oops/4b027458-225c-11ed-978c-fa163e993415 - https://errors.ubuntu.com/oops/d1cc8831-225a-11ed-978c-fa163e993415 - https://errors.ubuntu.com/oops/cd660830-225a-11ed-b154-fa163ef35206 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 23 08:36:52 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-16 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Attachment added: "journalctl_results.txt" https://bugs.launchpad.net/bugs/1987409/+attachment/5610992/+files/journalctl_results.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1987409 Title: All open applications close after "screen blank" in Ubuntu 22.04 using Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987409/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987209] Re: gnome-shell (Wayland) crashes with SIGSEGV when screen locker activates (jj), immediately after meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed
I am getting very similar results. For work a desktop computer was wiped and then imaged with Ubuntu 22.04. Like francois-lafont, I have noticed that when the system 'screen blank' activates, all my open windows in my session are closed after logging back in. About my system (from About menu in Settings) - Dell OptiPlex 3050 - 32 GB RAM - Intel® Core™ i7-7700 CPU @ 3.60GHz × 8 - AMD® Radeon rx 550 / 550 series / Mesa Intel® HD Graphics 630 (KBL GT2) - GNOME Version: 42.2 Monitors being used: - Dell U2211Ht 22" - Acer G226HQL 22" - LG 32MA68HY 27" Again, like francois-lafont's testing, I have reproduced this error by setting the 'Screen Blank' setting to 1 minute, then waiting for the system to enter the screen blank state. The following then happens. 1. Everything seems to be fading out as normal 2. Screens no longer have data that needs to be displayed, they go into sleep mode 3. After a brief period, screens are forced back on (where when this problem isn't happening, screens will remain in sleep mode until input provided by user) 4. System displays the dark login screen as if I was never logged in. 5. After signing in, all my open applications have been closed. I have managed to circumvent this issue by choosing the option 'Ubuntu on xorg' before signing in, or by uncommenting the line #WaylandEnable=false in /etc/gdm3/custom.conf. I then repeat the test described above after rebooting gdm3 and my session is saved, no issues. I have attached my own results that I found after a 'journalctl -b0'. The text in the file are some of the lines before and after the line: gnome-shell[]: segfault at ** Attachment added: "journalctl_results.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987209/+attachment/5610891/+files/journalctl_results.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1987209 Title: gnome-shell (Wayland) crashes with SIGSEGV when screen locker activates (jj), immediately after meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
