Hello. I seem to be hitting the same bug and I have attached the drm_info output while the screen is stuck in the off state.
I see the the same Failed to post KMS update: drmModeAtomicCommit: Invalid argument and Page flip discarded: drmModeAtomicCommit: Invalid argument in my logs while the the monitor is stuck. It gets stuck when I turn my monitor off from inactivity or the monitor turns itself off after locking the computer. Putting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 in /etc/environment fixed it for me. Rarely the screen also flickers at random moment, turns dark for a second, and then turns back on. When I checked the logs after it, I see the drmModeAtomicCommit: Invalid argument lines again. I have Ubuntu 22.04 with an external monitor Single display setup. Also Intel. ** Attachment added: "drm_info.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5705009/+files/drm_info.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Upstream bugs ] https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098 https://gitlab.gnome.org/GNOME/mutter/-/issues/2268 https://gitlab.gnome.org/GNOME/mutter/-/issues/2749 [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
