[amdgpu] Black screen after screen lock

Bug #1871475 reported by snow
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mutter (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

When I lock the screen with "Windows" + "L" key combination the screen gets locked, but I expect it to stay on and be locked. In Ubuntu 20.04. when I do it the screen gets locked but get immediately black a sit would be in standby. The screen should stay on and show locked screen.

This black screen happens often, but sometimes not.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 7 20:51:27 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Picasso [17aa:5125]
InstallationDate: Installed on 2020-04-02 (4 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
MachineType: LENOVO 20NKS01Y00
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=024c6306-92b0-4cf4-88de-71e1f0671318 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/28/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R12ET46W(1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20NKS01Y00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T495
dmi.product.name: 20NKS01Y00
dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495
dmi.product.version: ThinkPad T495
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

Revision history for this message
snow (mrauschert) wrote :
affects: ubuntu → xorg (Ubuntu)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please try logging into "Ubuntu on Wayland" from the login screen and tell us if that avoids the problem.

tags: added: amdgpu
affects: xorg (Ubuntu) → mutter (Ubuntu)
summary: - Black screen after screen lock
+ [amdgpu] Black screen after screen lock
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

And in case the problem is a crash somewhere, please also follow these instructions:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

Changed in mutter (Ubuntu):
status: New → Incomplete
Revision history for this message
snow (mrauschert) wrote :

I confirm that the problem also exists with "Ubuntu on Wayland". The screen gets black after screen lock everytime.

snow (mrauschert)
Changed in mutter (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please wait until the problem happens again and then collect a fresh system log:

  journalctl -b0 > journal.txt

or if you had to reboot after it happened run:

  journalctl -b-1 > prevboot.txt

and then attach the resulting file here. Please also follow the instructions in comment #3.

Changed in mutter (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
snow (mrauschert) wrote :

The journal.txt file has been attached.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks. The only hint of a crash I can see is:

Apr 09 18:11:43 mx-ThinkPad-T495 gnome-shell[1061]: Connection to xwayland lost

so...

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in mutter (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.