This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.9
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-oem-6.1 verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2009164

Title:
  Fix screen that remains blank forever after it gets locked

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  Once screen is locked under gnome-shell, the screen never wakes up and
  remains in blank forever.

  [Fix]
  "drm/i915: Create resized LUTs for ivb+ split gamma mode" makes gamma
  LUT operations in atomic context, so userspace can no longer misuse libdrm.

  "drm/i915: Rework legacy LUT handling" starts to use the reworked gamma
  LUT.

  Pull the whole series and series they depends upon to properly support
  gamma LUT.

  [Test]
  The easier way to reproduce the issue is to
  1) Login under Wayland
  2) Logout and login under X
  3) Go back to wayland
  4) Super + L to screenlock

  With the LUT reworked series applied, screen can always come back
  alive.

  [Where problems could occur]
  Regression can happen on refactoring patches with "no functional change
  intended", let alone overhauls like this one.

  So only OEM-6.1 and Unstable are targeted to contain the potential
  regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2009164/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to