[Acer Aspire E5-576] When locking computer with Win+L, screen goes black permanently

[Jack Glazko]

I had a workaround for this in 20.04, press and hold Win+L so it types letters into the input field as you lock the computer. This kept the screen from going black, and I could manually dim the laptop screen (fn+brightness) and walk away. In 22.04 the screen now fades to black immediately when I press Win+L, even though I can see the first few characters being entered on the input field as the screen fades to black.

Black screen (as in fade to black for inactivity) seems to be irreversible on this computer, no amount of mouse-wiggling, 3 finger salute (ctrl-alt-delete), or usb dongle removal and reattachment will cause the display to wake up. In 20.04 I could get around this on computer lock by continuing to press Win+L until the input box had lots of input. That seemed to stop the screen from dimming in 20.04. Not working in 22.04.

The only way I have found out of this is to do a hard power down (7+ seconds pressing power button). For obvious reasons I prefer not to do this often.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 15 22:03:08 2022
DistUpgraded: 2022-08-15 15:36:20,169 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:121a]
InstallationDate: Installed on 2022-03-14 (154 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0408:a030 Quanta Computer, Inc. HD WebCam
 Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire E5-576
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-08-15 (0 days ago)
dmi.bios.date: 10/24/2017
dmi.bios.release: 0.0
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.32
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ironman_SK
dmi.board.vendor: KBL
dmi.board.version: V1.32
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.10
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.32:bd10/24/2017:br0.0:efr1.10:svnAcer:pnAspireE5-576:pvrV1.32:rvnKBL:rnIronman_SK:rvrV1.32:cvnChassisManufacturer:ct10:cvrChassisVersion:sku0000000000000000:
dmi.product.family: Aspire E 15
dmi.product.name: Aspire E5-576
dmi.product.sku: 0000000000000000
dmi.product.version: V1.32
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

[Daniel van Vugt (vanvugt)]

Thanks for the bug report. Next time the problem happens, after rebooting please run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

[Daniel van Vugt (vanvugt)]

Thanks. That's unusual in that there is nothing in the log to indicate a problem. Can you repeat the above steps, but wait at least 10 seconds on the black screen before powering down? If there are any log messages to explain the issue then they can take up to 5 seconds to be written to disk.

If a second log does not explain it then next please add this to /etc/environment to get detailed debug logging about the display:

  MUTTER_DEBUG=kms

and then repeat the above steps.

[Jack Glazko (jglazko)]

Just going to post a workaround on this, but not fixed. Just frustrated that I can't seem to get the level of detail needed. I've tried repeatedly to get more informmation on a lockup/reboot without success.

From what I can see, press-hold of Win + L is not causing an event after the first keystroke, so it's not sending any interrupt/key information to whatever process is handling powersave. No idea why it's not able to come back out of powersave after it has gone completely dark.

The workaround is to NOT press-hold Win+L for the autorepeated keystroke, but to press Win+L repeatedly and very fast to keep the screen from going dark.

That's all the time I'm willing to spend grasping for the why straws. Hopefully I've given some more insight with this comment that it appears to be going dark only on the press-hold keystroke autorepeat. So at least people can get around this issue. I have absolutely no clue why I can never get the screen out of power save, which is the root cause.

[Launchpad Janitor (janitor)]

[Expired for Ubuntu because there has been no activity for 60 days.]