20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on

[Bjorn Helgaas]

Dell 5520 laptop -> Dell Thunderbolt dock -> HDMI -> external monitor.
Running 20.04, i915 driver.

Laptop lid closed, using external monitor only. When external monitor turns off (after sleep-display-ac), keyboard/mouse activity should turn it back on, but do not. Opening and closing the laptop lid does turn the external monitor back on. Laptop is not suspended; I can ssh in from another machine.

Happy to collect any additional information.

To reproduce:
- On Dell 5520 laptop connected to Dell Thunderbolt dock connected to external monitor via HDMI
- Close laptop lid
- Use external monitor, external keyboard, external mouse
- Leave system idle for "sleep-display-ac" time
- System puts external monitor in power-save mode
- Move mouse, type on keyboard
- No response, external monitor remains in power-save mode
- Open laptop lid
- External monitor turns on
- Close laptop lid
- External monitor remains on, I'm able to work as usual
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: bjorn 1993 F.... pulseaudio
 /dev/snd/controlC1: bjorn 1993 F.... pulseaudio
 /dev/snd/controlC0: bjorn 1993 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Ubuntu 20.04
HibernationDevice: RESUME=UUID=39f2962e-3115-438f-a447-03558db08edb
InstallationDate: Installed on 2018-06-08 (725 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. Precision 5520
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nouveau.runpm=0 vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-31-generic N/A
 linux-backports-modules-5.4.0-31-generic N/A
 linux-firmware 1.187
Tags: focal
Uname: Linux 5.4.0-31-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-29 (34 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/17/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.0
dmi.board.name: 0R6JFH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: 1203147
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.product.sku: 07BF
dmi.sys.vendor: Dell Inc.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1881644/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1881644

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Bjorn Helgaas (bjorn-helgaas)]

apport information

[Bjorn Helgaas (bjorn-helgaas)]

apport information

[Bjorn Helgaas (bjorn-helgaas)]

apport information

[Bjorn Helgaas (bjorn-helgaas)]

apport information

[Bjorn Helgaas (bjorn-helgaas)]

apport information

[Bjorn Helgaas (bjorn-helgaas)]

apport information

[Bjorn Helgaas (bjorn-helgaas)]

apport information

[Bjorn Helgaas (bjorn-helgaas)]

apport information

[Bjorn Helgaas (bjorn-helgaas)]

apport information

[Bjorn Helgaas (bjorn-helgaas)]

apport information

[Bjorn Helgaas (bjorn-helgaas)]

apport information

[Bjorn Helgaas (bjorn-helgaas)]

apport information

[Bjorn Helgaas (bjorn-helgaas)]

apport information

[Bjorn Helgaas (bjorn-helgaas)]

apport information

[Bjorn Helgaas (bjorn-helgaas)]

apport information

[Bjorn Helgaas (bjorn-helgaas)]

apport information

[Bjorn Helgaas (bjorn-helgaas)]

apport information

[Kai-Heng Feng (kaihengfeng)]

Hi Bjorn,

This doesn't seem to be a linux kernel bug. Since the desktop is Cinnamon, can you please test Ubuntu proper [1]?

At least I can't reproduce the issue on Dell Latitude 9510 + Dell WD19TB + HDMI display.

[1] http://cdimages.ubuntu.com/daily-live/current/groovy-desktop-arm64.iso

[Bjorn Helgaas (bjorn-helgaas)]

I'm sure it's not a Linux kernel bug. I don't have any idea *where* the bug is, and https://wiki.ubuntu.com/Bugs/FindRightPackage suggested "linux" as a safe bet.

Sorry, I didn't realize Cinnamon wasn't supported by Ubuntu. I will either live with the behavior or switch to the supported Ubuntu desktop. Feel free to close as "not our bug" or whatever is appropriate.

[Kai-Heng Feng (kaihengfeng)]

Is Mint in use? How was Cinnamon Desktop installed? Let's see if I can figure out which package should be file a bug against.

[Bjorn Helgaas (bjorn-helgaas)]

I'm not using Mint. I started with Ubuntu 18.04 in June 2018, installed the "cinnamon" package, and recently updated to 20.04. I don't know if this is a regression because I didn't start using this configuration until after moving to 20.04. Pretty sure cinnamon came from the ubuntu repo; my only apt sources change is for chrome.

[Kai-Heng Feng (kaihengfeng)]

Maybe file a bug at the main project [1], and let the Mint community triage the bug.

[1] https://github.com/linuxmint/cinnamon