When using Wayland in 21.04, the display often never wakes up after lock

[Chris Hall]

When using Wayland in 21.04, the display often never wakes up after lock up. Also, on boot up, desktop icons and most favorites on dash are not displayed, even though desktop icons are enabled. I can get them to show up only by re-enabling desktop icons. The workaround now is to disable Wayland, and the original xorg server works fine. The display driver is:

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)

The monitor is an HP 22cwa running of of a displayport interface.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
Uname: Linux 5.11.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 14 14:32:26 2021
DistUpgraded: 2021-07-28 16:05:54,589 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed
 virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:047e]
InstallationDate: Installed on 2018-12-04 (1044 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. OptiPlex 990
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to hirsute on 2021-07-28 (77 days ago)
dmi.bios.date: 11/24/2011
dmi.bios.release: 4.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 06D7TR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/24/2011:br4.6:svnDellInc.:pnOptiPlex990:pvr01:sku:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 990
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~21.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.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-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

[Daniel van Vugt (vanvugt)]

Thanks for the bug report. Since those are unrelated issues, please choose just one of them for this bug to be about.

[Chris Hall (cmhallmi)]

The most serious issue is the fact that with Wayland, the display
sometimes never wakes up, requiring a power shut off.

On 10/14/2021 9:59 PM, Daniel van Vugt wrote:
> Thanks for the bug report. Since those are unrelated issues, please
> choose just one of them for this bug to be about.
>
> ** Package changed: xorg (Ubuntu) => ubuntu
>
> ** Changed in: ubuntu
> Status: New => Incomplete
>

[Daniel van Vugt (vanvugt)]

OK, thanks.

Please:

1. Reproduce the bug in Wayland again.

2. Wait 10 seconds.

3. Reboot.

4. Run:

   journalctl -b-1 > prevboot.txt

5. Attach the resulting text file here.

6. Also consider trying Ubuntu 21.10 which was just released a couple of days ago.

[Daniel van Vugt (vanvugt)]

Please also check for crashes using these steps: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

[Chris Hall (cmhallmi)]

Thanks Daniel. Here's the prevboot.txt file. There were 2 separate crash
files generated when I booted using wayland. The first with my user
permission was generated immediately and this was when there were no
dash icons present. The second was generated with root ownership when
the screen tried to dim (a cursor was visible in the top left of the
screen). I needed to ctrl-alt-del to get the machine to reboot. It's a
Dell Optiplex 990 mini-tower. I will try to attach the 2 crash reports
using ubuntu-bug.

Chris

On 2021-10-17 10:21 p.m., Daniel van Vugt wrote:
> OK, thanks.
>
> Please:
>
> 1. Reproduce the bug in Wayland again.
>
> 2. Wait 10 seconds.
>
> 3. Reboot.
>
> 4. Run:
>
> journalctl -b-1 > prevboot.txt
>
> 5. Attach the resulting text file here.
>
> 6. Also consider trying Ubuntu 21.10 which was just released a couple of
> days ago.
>
> ** Summary changed:
>
> - Wayland only partially works
> + When using Wayland in 21.04, the display often never wakes up after lock
>
> ** Package changed: ubuntu => mutter (Ubuntu)
>

[Chris Hall (cmhallmi)]

One more thing. I was using Focal Fossa, but it was incompatible with a
library needed for a program I needed for my work (gle-graphics). This
forced me to upgrade to Groovy Gorilla and then Hirsute Hippo. My
problems started because 21.04 defaulted to wayland. I have tried out
Impish Indrie on an old Toshiba laptop, but the upgrade froze solid and
then after reboot it said it could only do a partial upgrade. The
partial upgrade works, but it has made me nervous at this time to try
and upgrade my much more important desktop. for now, I can live with
xorg, which works fine.

Chris

On 2021-10-17 10:21 p.m., Daniel van Vugt wrote:
> OK, thanks.
>
> Please:
>
> 1. Reproduce the bug in Wayland again.
>
> 2. Wait 10 seconds.
>
> 3. Reboot.
>
> 4. Run:
>
> journalctl -b-1 > prevboot.txt
>
> 5. Attach the resulting text file here.
>
> 6. Also consider trying Ubuntu 21.10 which was just released a couple of
> days ago.
>
> ** Summary changed:
>
> - Wayland only partially works
> + When using Wayland in 21.04, the display often never wakes up after lock
>
> ** Package changed: ubuntu => mutter (Ubuntu)
>

[Chris Hall (cmhallmi)]

I tried this with my 2 crash reports but ubuntu-bug reported an internal
error each time, so I doubt that they became attached to the bug report.

Chris

On 2021-10-18 3:40 a.m., Daniel van Vugt wrote:
> Please also check for crashes using these steps:
> https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
>

[Daniel van Vugt (vanvugt)]

If ubuntu-bug fails then try apport-cli instead.

[Daniel van Vugt (vanvugt)]

In the log of comment #6 it looks like you managed a soft reboot rather than the hard reboot I was expecting. That's good news for you but made understanding the log a bit more difficult. It appears the problem you hit was a gnome-shell crash:

Oct 18 12:52:58 fluffy gnome-shell[4425]: The program 'gnome-shell' received an X Window System error.
                                          This probably reflects a bug in the program.
                                          The error was 'BadRROutput (invalid Output parameter)'.
                                            (Details: serial 1470 error_code 145 request_code 139 (RANDR) minor_code 30)
                                            (Note to programmers: normally, X errors are reported asynchronously;
                                             that is, you will receive the error a while after causing it.
                                             To debug your program, run it with the GDK_SYNCHRONIZE environment
                                             variable to change this behavior. You can then get a meaningful
                                             backtrace from your debugger if you break on the gdk_x_error() function.)
Oct 18 12:52:58 fluffy kernel: traps: gnome-shell[4425] trap int3 ip:7f0e88877647 sp:7ffe8b7aa5a0 error:0 in libglib-2.0.so.0.6800.1[7f0e88834000+8d000]

So once you manage to report your .crash files (using apport-cli), please provide a link to what it created.

[Daniel van Vugt (vanvugt)]

Also, please edit /etc/environment and add a line:

  GDK_SYNCHRONIZE=1

That will slow the system slightly but will make the next crash occur in a more *debuggable* way. It will create a new unique crash so please tell us the link to that one too.

[Chris Hall (cmhallmi)]

I was able to upload the first crash, but no web browser opened so I
don't know where it went. The second crash would not upload because it
said that the crash was about a package that was not installed.

I edited the environment file and will try to reproduce teh bug tomorrow.

Chris

On 2021-10-18 9:46 p.m., Daniel van Vugt wrote:
> If ubuntu-bug fails then try apport-cli instead.
>

[Daniel van Vugt (vanvugt)]

Per the instructions in comment #5:

"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."

[Chris Hall (cmhallmi)]

The last error reported was on Oct 18 and the url is
https://errors.ubuntu.com/oops/33300c46-3036-11ec-ad49-fa163e102db1

I've rebooted into wayland, but so far the bug has not occurred. It's
possible that the synchronization is preventing it from happening. I
will wait a while longer and if it still does not happen, I will disable
synchronization and try again.

On 2021-10-19 2:13 a.m., Daniel van Vugt wrote:
> Per the instructions in comment #5:
>
> "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."
>

[Chris Hall (cmhallmi)]

After disabling the GDK_SYNCHRONIZE statement, I finally was able to get
the bug to reappear. I've attached a new prevboot file (after a power
button shot down and reboot). I also used apport-cli to upload the crash
report. It's url is
https://errors.ubuntu.com/oops/0005b74e-3103-11ec-b60f-fa163e6cac46

I'm going to disable wayland again as the system is a little too flaky
with it enabled.

On 2021-10-19 2:13 a.m., Daniel van Vugt wrote:
> Per the instructions in comment #5:
>
> "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."
>

[Chris Hall (cmhallmi)]

On second thought, I re-enabled wayland and turned on GDK_SYNCHRONIZE
and I'll give it a day or so to see if the bug crops up again. There's
definitely something wrong about gdm3 calling wayland because after
boot, icons that should appear on the dash only do so AFTER you run a
program, like a terminal via ctrl-alt-T.

On 2021-10-19 2:13 a.m., Daniel van Vugt wrote:
> Per the instructions in comment #5:
>
> "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."
>

[Chris Hall (cmhallmi)]

I got a case of failing to wake up with GDK_SYNCHRONIZE turned on, and
I've attached the output from journalctl. However, there's no new crash
file. Am turning off wayland for now.

On 2021-10-19 2:13 a.m., Daniel van Vugt wrote:
> Per the instructions in comment #5:
>
> "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."
>

[Daniel van Vugt (vanvugt)]

Thanks. Those crashes are from gnome-shell crashing in libglib-2.0.so.0.6800.1+43647 but we don't have any useful debug symbols in them :(

Please open the Extensions app and ensure you don't have any extensions enabled other than the Ubuntu ones.

Please also upgrade to 21.10 when you can as we are more keen to find out if such bugs exist there.

[Launchpad Janitor (janitor)]

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