Raspberry Pi 4 fails to wake at login prompt

[spike speigel]

Raspberry Pi 4 running Ubuntu server 20.04 Focal (and perhaps 19.10 Eoan) fails to wake from sleep when no user is logged in and the screen is sitting at the gdm login prompt.

This has happened on two different systems. One system uses the official RPi 7 inch touchscreen via (LCD DSI Display Connector). The other system has a 10 inch non-touchscreen from SunFounder via (Micro HDMI).

Nothing wakes the Pi: Keyboard, mouse, or touchscreen.

After a user logs in and the screen locks on sleep the system wakes just fine with a lock screen.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
Uname: Linux 5.4.0-1001-raspi2 armv7l
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
Date: Sun Mar 1 20:03:12 2020
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: Upgraded to focal on 2020-02-28 (2 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
GsettingsChanges:
 b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
Package: gnome-shell 3.35.91-1ubuntu2
PackageArchitecture: armhf
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
Tags: focal uec-images third-party-packages
Uname: Linux 5.4.0-1001-raspi2 armv7l
UpgradeStatus: Upgraded to focal on 2020-02-28 (20 days ago)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
GsettingsChanges:
 b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'Sundry', 'YaST']"
 b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
Package: gnome-shell 3.35.91-1ubuntu2
PackageArchitecture: armhf
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
Tags: focal uec-images third-party-packages
Uname: Linux 5.4.0-1001-raspi2 armv7l
UpgradeStatus: Upgraded to focal on 2020-01-12 (69 days ago)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: XFCE
DistUpgraded: 2020-01-11 19:42:56,183 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
DistroCodename: focal
DistroRelease: Ubuntu 20.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:

Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8086:0808 Intel Corp.
 Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Package: xorg-server (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M video=HDMI-A-1:1280x800@60 smsc95xx.macaddr=DC:A6:32:1F:4B:D2 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
Tags: focal uec-images ubuntu reproducible
Uname: Linux 5.4.0-1001-raspi2 armv7l
UpgradeStatus: Upgraded to focal on 2020-01-12 (72 days ago)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
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 N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

[Daniel van Vugt (vanvugt)]

Please:

1. Run this command to send us more information about the installation:

   apport-collect 1865379

2. Follow these instructions:

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

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

There is an error report link, how should that be communicated?

[Daniel van Vugt (vanvugt)]

Error report links are public unless you feel something particularly personal has been shown on that page. So please paste the link here. And if you prefer you can change this bug page to Private using the setting at the top right of this page.

[spike speigel (frail-knight)]

This morning that system has stopped booting. I am not sure why. I can try and pull the SD card out and get the ID for the error report. If not, then I will need to pull all this information again from the second system that is displaying the same behavior.

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

light-locker
https://errors.ubuntu.com/oops/f8dd34c2-5f64-11ea-9802-fa163e102db1

https://errors.ubuntu.com/oops/97afb9a8-581c-11ea-a0ca-fa163e6cac46

light-locker
https://errors.ubuntu.com/oops/9126058e-5771-11ea-a0c4-fa163e6cac46

https://errors.ubuntu.com/oops/a7b9a3c2-5060-11ea-a094-fa163e6cac46

https://errors.ubuntu.com/oops/85763da4-496a-11ea-b91c-fa163e102db1

https://errors.ubuntu.com/oops/18d7f934-4231-11ea-b24e-fa163e983629

https://errors.ubuntu.com/oops/5f6b10c0-3b3d-11ea-a9f9-fa163e6cac46

https://errors.ubuntu.com/oops/a6876d34-34dd-11ea-a9dd-fa163e6cac46

light-locker
https://errors.ubuntu.com/oops/8df5b09c-30b8-11ea-a9bf-fa163e6cac46

light-locker
https://errors.ubuntu.com/oops/c64fff3e-2fa9-11ea-b86b-fa163e102db1

[spike speigel (frail-knight)]

I noted the ones that were light-locker. The others were apport and cups-browsed.

[Daniel van Vugt (vanvugt)]

The links in comment #12 aren't relevant sorry. And the log in comment #11 shows Xwayland went away so that seems to be why gnome-shell gave up. So I will move this bug to Xorg and next please run:

  apport-collect 1865379

again.

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

apport information

[spike speigel (frail-knight)]

Also wanted to note that when I ran apport-collect 1865379 this time that it noted package xorg-server not found. I don't know if that is relevant, or perhaps that makes sense??

[Daniel van Vugt (vanvugt)]

That's just a bug in the script. The script only supports binary package names and Launchpad only tracks source package names. So it's sometimes hard to get them to agree. It's not relevant here.

[Daniel van Vugt (vanvugt)]

Thanks again. I can't see any relevant errors in the above attachments so we are back to...

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.

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

This change was made by a bot.

[spike speigel (frail-knight)]

Hello, I have not forgotten about this.

1.) Does not exist.
2.) I've already reported.

I will have to apply the patch outlined in 3.) and cause the crash again. However, this system uses an SD card, and the first system had a corrupted boot partition after crashing a series of times. This crash might prevent me from collecting the data the crash creates.

I will give it a shot.

[Juerg Haefliger (juergh)]

I've noticed that the kernel you're running is quite old. Are you still able to reproduce this issue with a current image from http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/current/?

Also, how did you install xfce? Can you please detail the steps so we can try to reproduce the issue? Lastly, when your display goes off, does it turn off (go into standby) or is it just blanked?

[Sebastien Bacher (seb128)]

Deleting the focal targetting, please tag is rls-ff-incoming with explanation of why it should be an issue targetted to focal if you believe it's an important bug to get resolved

[Pamela Fong (katsiki)]

The symptom you reported seems the same as this one reported for Ubuntu 20.10,

https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1909678

Try the suggested workaround.

[Juerg Haefliger (juergh)]

No response to my question in #34 from April of last year so setting 'linux (Ubuntu)' to 'Invalid'.