Ubuntu

Blank Screen initiates then fails

Bug #1881212 reported by Graham Williams on 2020-05-28

This bug report is a duplicate of: Bug #1877774: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_changed() [when locking the screen] [usually due to dash-to-panel]. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu	Incomplete	Undecided	Unassigned

Bug Description

Blank Screen initiates after timeout (usually 5 minutes but set to 1 minute to replicate this bug), screen goes blank on both laptop and external Dell, but immediately comes back on. Whilst it is blanking, any running applications show their windows (which is not usual) but it appears gnome-shell and the window manager are not running (no dash and no window decorations).

Disconnecting external monitor exhibits the same Blank Screen failure on the laptop screen.

I have turned Automatic Screen Lock off for now to remove that as a cause.

I have also had intermittent failure of gnome-shell.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 29 09:07:11 2020
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
v4l2loopback, 0.12.3, 5.4.0-31-generic, x86_64: installed
v4l2loopback, 0.12.3, 5.4.0-33-generic, x86_64: installed
virtualbox, 6.1.6, 5.4.0-31-generic, x86_64: installed
virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
InstallationDate: Installed on 2020-02-25 (93 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20QFCTO1WW
ProcEnviron:
LANGUAGE=en_AU:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_AU.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-05-01 (27 days ago)
dmi.bios.date: 03/18/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET47W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN2HET47W(1.30):bd03/18/2020:svnLENOVO:pn20QFCTO1WW:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
dmi.product.family: ThinkPad X1 Yoga 4th
dmi.product.name: 20QFCTO1WW
dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th
dmi.product.version: ThinkPad X1 Yoga 4th
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

Tags:

Revision history for this message

Graham Williams (gjwkayon) wrote on 2020-05-28:

CurrentDmesg.txt Edit (251.4 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (22.9 KiB, text/plain; charset="utf-8")
DpkgLog.txt Edit (2.2 MiB, text/plain; charset="utf-8")
Lspci.txt Edit (22.1 KiB, text/plain; charset="utf-8")
Lspci-vt.txt Edit (2.0 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (1.5 KiB, text/plain; charset="utf-8")
Lsusb-t.txt Edit (2.5 KiB, text/plain; charset="utf-8")
Lsusb-v.txt Edit (107.7 KiB, text/plain; charset="utf-8")
MonitorsUser.xml.txt Edit (4.8 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (10.3 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (8.7 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (11.5 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (331.8 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (3.3 MiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (89.5 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (33.0 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (109.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2020-05-29:

Thanks for the bug report. This sounds like gnome-shell has crashed and is being restarted:

> Whilst it is blanking, any running applications show their windows (which is not usual) but it appears gnome-shell and the window manager are not running (no dash and no window decorations).

When gnome-shell crashes the apps are still running on the bare Xorg server so it looks different.

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2020-05-29:

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.

affects:	xorg (Ubuntu) → ubuntu
Changed in ubuntu:
status:	New → Incomplete

Revision history for this message

Graham Williams (gjwkayon) wrote on 2020-05-29:

Thanks. Yes - I can see now that it is a gnome-shell segfault. Turning off the gnome-shell extension dash-to-panel (https://extensions.gnome.org/extension/1160/dash-to-panel/) resolves the issue. I notice on the extension's page someone has also reported the problem there. Workaround for now is to disable the dash-to-panel extension until it is updated.

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2020-05-29:

Since you mention dash-to-panel and crashing when the screen locks, I think this is probably bug 1877774. So let's assume that until proven otherwise.