Thanks! It looks like most of the errors are in fact caused by previous errors:
i915 0000:00:02.0: [drm:drm_atomic_crtc_check [drm]] [CRTC:45:pipe A] requesting event but off i915 0000:00:02.0: [drm:drm_atomic_check_only [drm]] [CRTC:45:pipe A] atomic core check failed ... KMS: [atomic] KMS update failed: drmModeAtomicCommit: Invalid argument So those could be improved, but they're not the root cause. The root cause seems to be a failure of the first frame (modeset) when waking from sleep: i915 0000:00:02.0: [drm:intel_hdmi_compute_clock [i915]] picking 12 bpc for HDMI output (pipe bpp: 36) i915 0000:00:02.0: [drm:intel_hdmi_compute_config [i915]] bad AVI infoframe i915 0000:00:02.0: [drm:intel_modeset_pipe_config [i915]] Encoder config failure: -22 That "-22" is the first "Invalid argument". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
