Second screen is not always made to awaken when using multiple displays. Desktop is multiple display, but only laptop screen is on while second screen sometimes remains off

[Brendan_P]

New bug for me. Issue was fine till last week. I think this may be related to the following as it started happening shortly thereafter.

I have XPS13 with second monitor, all working fine till I lock screen or suspend. Then my second monitor will not 'resume'. I.e. stays off.

This behaviour started after (or shortly after) playing a wine game using Lutris to launch. Shutting game down and almost immediately hitting suspend on the laptop. Was rushing out.

It's a wild shot in the dark but I think something got messed up / not saved correctly in this process.

To get it working I need to unplug monitor (using USB-C > HDMI) > suspend > plug in monitor > resume and sometimes still need to open display settings before it 'kicks in'. Damn annoying. Hope someone can help :)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Tue Jul 7 16:44:52 2020
DistUpgraded: 2020-05-15 15:17:42,708 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Dell UHD Graphics 620 [1028:082a]
InstallationDate: Installed on 2019-01-29 (525 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. XPS 13 9360
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-05-15 (53 days ago)
dmi.bios.date: 11/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.13.0
dmi.board.name: 0PVG6D
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PVG6D:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 082A
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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-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

[Daniel van Vugt (vanvugt)]

Problems with locking the screen (and gnome-shell then crashing) lately have mostly been bug 1877774, which you don't seem to have the fix for... To get the fix please try:

  sudo apt update
  sudo apt full-upgrade
  Reboot

and then verify your gnome-shell package is at least version 3.36.3.

[Brendan_P (brendan-p)]

Thanks @Daniel. That seems to resolve the issue.

Busy testing and will confirm if it's fully resolved or not.

[Brendan_P (brendan-p)]

I've added additional feedback here > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877774

[Daniel van Vugt (vanvugt)]

This bug has now been reopened. Please try to reword it into a simple description of a single problem.

[David Rasch (rasch)]

I have the 3.36.3 package installed
ii gnome-shell 3.36.3-1ubuntu1~20.04.2 amd64 graphical shell for the GNOME desktop

I'm experiencing a crash upon resume from sleep, something with either gnome-shell or screensaver crashes. After suspend, I can see my screen (without much of the window decorations or layouts) before it eventually restarts things and then I can unlock my screen normally.

I have a dell xps 13 9380,

ERROR: apport (pid 693953) Thu Jul 16 20:11:08 2020: this executable already crashed 2 times, ignoring
ERROR: apport (pid 694509) Thu Jul 16 20:28:01 2020: called for pid 693961, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 694509) Thu Jul 16 20:28:01 2020: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR: apport (pid 694509) Thu Jul 16 20:28:01 2020: debug: session gdbus call: (true,)

ERROR: apport (pid 694509) Thu Jul 16 20:28:01 2020: this executable already crashed 2 times, ignoring
ERROR: apport (pid 699014) Thu Jul 16 23:00:33 2020: called for pid 694516, signal 6, core limit 0, dump mode 1
ERROR: apport (pid 699014) Thu Jul 16 23:00:33 2020: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR: apport (pid 699014) Thu Jul 16 23:00:33 2020: debug: session gdbus call: (true,)

ERROR: apport (pid 699014) Thu Jul 16 23:00:33 2020: this executable already crashed 2 times, ignoring
ERROR: apport (pid 779097) Fri Jul 17 17:10:53 2020: called for pid 699036, signal 6, core limit 0, dump mode 1
ERROR: apport (pid 779097) Fri Jul 17 17:10:53 2020: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR: apport (pid 779097) Fri Jul 17 17:10:53 2020: debug: session gdbus call: (true,)

ERROR: apport (pid 779097) Fri Jul 17 17:10:53 2020: this executable already crashed 2 times, ignoring

[Daniel van Vugt (vanvugt)]

Brendan_P, Please try to reword this bug into a simple description of a _single_ problem.

David, Please open a new bug by running: ubuntu-bug gnome-shell

[Daniel van Vugt (vanvugt)]

Thanks Brendan. Next please try selecting 'Ubuntu on Wayland' from the login screen. Does that avoid the bug?

[Brendan_P (brendan-p)]

Apologies for the delayed reply. I've done some additional testing, including the Wayland session. Here my findings:

removed .config/monitors.xml and .config/monitors.xml~
unplugged monitor cable, unplugged monitor power
shutdown > start-up
Set display preferences for single/laptop screen
shutdown > start-up
plugged in monitor power
plugged in monitor to laptop
- no change -
opened display settings
monitor starts up as second screen
changed settings as needed for both screens > apply > keep settings
second monitor switches off
shutdown and restart > second monitor on and with correct settings
lock screen > wait for second monitor to go back to sleep
-- correct behaviour resumes --
wake screen > both monitors resume as expected
suspend machine > resume > both monitors resume as expected
-- END--
unplug second monitor > single/laptop display resumes correctly
plug second monitor back in, display remains unchanged (laptop/single only)
unplug second monitor
suspend laptop
plug in second monitor
resume laptop, second monitor remains off
logout
login screen displayed with second screen now enabled
login
display resets to multiple display desktop but second screen remains off
remove second screen > display resets correctly to single laptop screen
shutdown
--- correct behaviour resumes --
plugin in second monitor
start
both screens active including login
login
both screens working as expected
lock screen > all screens suspend
move mouse to active screens > both resume and can login
suspend
suspend machine > resume > both monitors resume as expected
suspend > unplug second monitor > resume > single display/laptop works as expected
-- END --
suspend > plugin in second monitor > resume > display remains in "single" mode > second monitor remains off
restart gnome-shell (Alt+F2 > r) display resets to correct two display setup with second monitor on
lock screen > monitor suspend > move mouse to activate screens > only laptop screen wakes up
shutdown
--- correct behaviour resumes --
start
both screens active including login
login
both screens working as expected
lock screen > all screens suspend
move mouse to active screens > both resume and can login
suspend
suspend machine > resume > both monitors resume as expected
END TESTING

Wayland
---------
setup second display, all working as expected (lock screen and suspend resume work fine)
remove second screen > screen resets to single display
plug in second screen > no change
open display settings > display settings do not recognise second screen
logout
login screen, both displays work
login > both displays working as expected (lock screen and suspend resume work fine)
suspend > remove second display > resume
single display resets as expected
suspend > add second screen > resume
second screen remains off, display remains in 'single' display mode.
logout
login screen, both displays work
login > both displays working as expected (lock screen and suspend resume work fine)
END WAYLAND TESTING

Thanks for the time and effort all.

[Lucas Ariel Pasut (calusa97)]

hello, I need help with the same error. In my case use a laptop and a extra monitor. When lock the system, the screen of the laptop is freezes. I am running the 3.36.8 gnome version con ubuntu 20.4 Focal. Is a clean installation. in the path /.local/share/gnome-shell only have this application_state gnome-overrides-migrated notifications