Display does not wake from sleep

I’ve been having this issue lately and am having trouble deciphering the log. I do sudo journalctl -b -1 > log and then tail the log.

Essentially the CTRL ALT F2 doesn’t work (or maybe does, I can’t tell) because the screens themselves don’t wake up, this is an issue when I’ve locked or suspended the system for an extended period of time. If I come back in like five minutes it doesn’t happen. Hoping someone can help me figure this out:

Nov 11 10:54:11 latitude rtkit-daemon[1168]: Supervising 10 threads of 5 processes of 1 users.
Nov 11 10:54:11 latitude rtkit-daemon[1168]: Supervising 10 threads of 5 processes of 1 users.
Nov 11 10:56:03 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:03 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:03 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:03 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:03 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:03 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:03 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:03 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:04 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:04 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:04 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:04 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:05 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:05 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:05 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:05 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:48 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:48 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:48 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:48 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:48 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:48 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:48 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:48 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:48 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:48 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:48 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:56:48 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:58:15 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:58:15 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:58:15 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:58:15 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 10:58:15 latitude gnome-shell[1384]: libinput error: event5  - Logitech G403 HERO Gaming Mouse: client bug: event processing lagging behind by 23ms, your system is too slow
Nov 11 10:59:18 latitude gnome-shell[1980]: IPDL protocol error: Handler returned error code!
Nov 11 10:59:18 latitude gnome-shell[1980]: ###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
Nov 11 10:59:18 latitude gnome-shell[1980]: IPDL protocol error: Handler returned error code!
Nov 11 10:59:18 latitude gnome-shell[1980]: ###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
Nov 11 10:59:18 latitude gnome-shell[1980]: IPDL protocol error: Handler returned error code!
Nov 11 10:59:18 latitude gnome-shell[1980]: ###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
Nov 11 10:59:18 latitude gnome-shell[1980]: IPDL protocol error: Handler returned error code!
Nov 11 10:59:18 latitude gnome-shell[1980]: ###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
Nov 11 10:59:56 latitude rtkit-daemon[1168]: Supervising 10 threads of 5 processes of 1 users.
Nov 11 10:59:56 latitude rtkit-daemon[1168]: Supervising 10 threads of 5 processes of 1 users.
Nov 11 10:59:57 latitude rtkit-daemon[1168]: Supervising 10 threads of 5 processes of 1 users.
Nov 11 10:59:57 latitude rtkit-daemon[1168]: Supervising 10 threads of 5 processes of 1 users.
Nov 11 10:59:58 latitude systemd[1277]: vte-spawn-0f5fec10-2661-4480-9934-83e3eca42b75.scope: Succeeded.
Nov 11 10:59:58 latitude systemd[1277]: gnome-terminal-server.service: Succeeded.
Nov 11 11:00:34 latitude systemd[1]: Starting Cleanup of Temporary Directories...
Nov 11 11:00:34 latitude systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Nov 11 11:00:34 latitude systemd[1]: Finished Cleanup of Temporary Directories.
Nov 11 11:00:34 latitude audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 11 11:00:34 latitude audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 11 11:00:34 latitude kernel: audit: type=1130 audit(1605114034.460:78): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 11 11:00:34 latitude kernel: audit: type=1131 audit(1605114034.460:79): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 11 11:01:18 latitude rtkit-daemon[1168]: Supervising 10 threads of 5 processes of 1 users.
Nov 11 11:01:18 latitude rtkit-daemon[1168]: Supervising 10 threads of 5 processes of 1 users.
Nov 11 11:03:25 latitude systemd[1277]: Started Application launched by gsd-media-keys.
Nov 11 11:03:25 latitude dbus-daemon[730]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.448' (uid=0 pid=4681 comm="sudo systemctl suspend ")
Nov 11 11:03:25 latitude dbus-daemon[730]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Nov 11 11:03:25 latitude sudo[4681]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Nov 11 11:03:25 latitude audit[4681]: USER_ACCT pid=4681 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_permit,pam_time acct="dustin" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
Nov 11 11:03:25 latitude audit[4681]: CRED_REFR pid=4681 uid=0 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
Nov 11 11:03:25 latitude sudo[4681]:   dustin : TTY=unknown ; PWD=/home/dustin ; USER=root ; COMMAND=/usr/bin/systemctl suspend
Nov 11 11:03:25 latitude sudo[4681]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Nov 11 11:03:25 latitude audit[4681]: USER_START pid=4681 uid=0 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
Nov 11 11:03:25 latitude kernel: audit: type=1101 audit(1605114205.479:80): pid=4681 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_permit,pam_time acct="dustin" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
Nov 11 11:03:25 latitude kernel: audit: type=1110 audit(1605114205.479:81): pid=4681 uid=0 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
Nov 11 11:03:25 latitude kernel: audit: type=1105 audit(1605114205.479:82): pid=4681 uid=0 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
Nov 11 11:03:25 latitude NetworkManager[731]: <info>  [1605114205.4962] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Nov 11 11:03:25 latitude audit[4681]: USER_END pid=4681 uid=0 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
Nov 11 11:03:25 latitude audit[4681]: CRED_DISP pid=4681 uid=0 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
Nov 11 11:03:25 latitude NetworkManager[731]: <info>  [1605114205.4964] device (enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov 11 11:03:25 latitude sudo[4681]: pam_unix(sudo:session): session closed for user root
Nov 11 11:03:25 latitude systemd[1277]: app-gnome-sudo-4681.scope: Succeeded.
Nov 11 11:03:25 latitude kernel: audit: type=1106 audit(1605114205.489:83): pid=4681 uid=0 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
Nov 11 11:03:25 latitude kernel: audit: type=1104 audit(1605114205.489:84): pid=4681 uid=0 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
Nov 11 11:03:25 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 11:03:25 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 11:03:25 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 11:03:25 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 11:03:25 latitude NetworkManager[731]: <info>  [1605114205.5823] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov 11 11:03:25 latitude NetworkManager[731]: <info>  [1605114205.5825] manager: NetworkManager state is now ASLEEP
Nov 11 11:03:25 latitude NetworkManager[731]: <info>  [1605114205.5827] device (wlan0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Nov 11 11:03:25 latitude evolution[1997]: Network disconnected.  Forced offline.
Nov 11 11:03:25 latitude dbus-daemon[730]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.5' (uid=0 pid=731 comm="/usr/bin/NetworkManager --no-daemon ")
Nov 11 11:03:25 latitude systemd[1]: Starting Network Manager Script Dispatcher Service...
Nov 11 11:03:25 latitude kernel: e1000e: enp0s31f6 NIC Link is Down
Nov 11 11:03:25 latitude dbus-daemon[730]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 11 11:03:25 latitude systemd[1]: Started Network Manager Script Dispatcher Service.
Nov 11 11:03:25 latitude audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 11 11:03:25 latitude kernel: audit: type=1130 audit(1605114205.589:85): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 11 11:03:25 latitude kernel: wlan0: deauthenticating from 30:23:03:de:1d:22 by local choice (Reason: 3=DEAUTH_LEAVING)
Nov 11 11:03:25 latitude wpa_supplicant[786]: wlan0: CTRL-EVENT-DISCONNECTED bssid=30:23:03:de:1d:22 reason=3 locally_generated=1
Nov 11 11:03:25 latitude wpa_supplicant[786]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=0 noise=9999 txrate=0
Nov 11 11:03:25 latitude NetworkManager[731]: <info>  [1605114205.6096] device (wlan0): supplicant interface state: completed -> disconnected
Nov 11 11:03:25 latitude NetworkManager[731]: <info>  [1605114205.6099] device (wlan0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Nov 11 11:03:25 latitude avahi-daemon[727]: Withdrawing address record for 2601:2c0:8b00:9ff::cf7 on wlan0.
Nov 11 11:03:25 latitude avahi-daemon[727]: Withdrawing address record for fd81:77c2:c730::cf7 on wlan0.
Nov 11 11:03:25 latitude avahi-daemon[727]: Withdrawing address record for fd81:77c2:c730:0:9ff1:3610:7971:6fea on wlan0.
Nov 11 11:03:25 latitude avahi-daemon[727]: Withdrawing address record for 2601:2c0:8b00:9ff:e5df:b6d5:e61e:f474 on wlan0.
Nov 11 11:03:25 latitude avahi-daemon[727]: Leaving mDNS multicast group on interface wlan0.IPv6 with address 2601:2c0:8b00:9ff:e5df:b6d5:e61e:f474.
Nov 11 11:03:25 latitude avahi-daemon[727]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::70d6:ccd:2e2e:f9ca.
Nov 11 11:03:25 latitude avahi-daemon[727]: Registering new address record for fe80::70d6:ccd:2e2e:f9ca on wlan0.*.
Nov 11 11:03:25 latitude avahi-daemon[727]: Withdrawing address record for fe80::70d6:ccd:2e2e:f9ca on wlan0.
Nov 11 11:03:25 latitude avahi-daemon[727]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::70d6:ccd:2e2e:f9ca.
Nov 11 11:03:25 latitude avahi-daemon[727]: Interface wlan0.IPv6 no longer relevant for mDNS.
Nov 11 11:03:25 latitude NetworkManager[731]: <info>  [1605114205.6132] dhcp4 (wlan0): canceled DHCP transaction
Nov 11 11:03:25 latitude NetworkManager[731]: <info>  [1605114205.6132] dhcp4 (wlan0): state changed bound -> done
Nov 11 11:03:25 latitude NetworkManager[731]: <info>  [1605114205.6135] dhcp6 (wlan0): canceled DHCP transaction
Nov 11 11:03:25 latitude NetworkManager[731]: <info>  [1605114205.6135] dhcp6 (wlan0): state changed bound -> done
Nov 11 11:03:25 latitude avahi-daemon[727]: Interface wlan0.IPv4 no longer relevant for mDNS.
Nov 11 11:03:25 latitude avahi-daemon[727]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 10.1.0.134.
Nov 11 11:03:25 latitude avahi-daemon[727]: Withdrawing address record for 10.1.0.134 on wlan0.
Nov 11 11:03:25 latitude NetworkManager[731]: <info>  [1605114205.6192] device (wlan0): set-hw-addr: set MAC address to 0A:F1:E7:8A:A6:00 (scanning)
Nov 11 11:03:25 latitude avahi-daemon[727]: Joining mDNS multicast group on interface wlan0.IPv4 with address 10.1.0.134.
Nov 11 11:03:25 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 11:03:25 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 11:03:25 latitude avahi-daemon[727]: New relevant interface wlan0.IPv4 for mDNS.
Nov 11 11:03:25 latitude avahi-daemon[727]: Registering new address record for 10.1.0.134 on wlan0.IPv4.
Nov 11 11:03:25 latitude avahi-daemon[727]: Withdrawing address record for 10.1.0.134 on wlan0.
Nov 11 11:03:25 latitude avahi-daemon[727]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 10.1.0.134.
Nov 11 11:03:25 latitude avahi-daemon[727]: Interface wlan0.IPv4 no longer relevant for mDNS.
Nov 11 11:03:25 latitude NetworkManager[731]: <info>  [1605114205.6366] device (wlan0): supplicant interface state: disconnected -> interface_disabled
Nov 11 11:03:25 latitude NetworkManager[731]: <info>  [1605114205.6367] device (wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov 11 11:03:25 latitude NetworkManager[731]: <info>  [1605114205.6391] device (wlan0): set-hw-addr: reset MAC address to A0:A4:C5:00:D3:A4 (unmanage)
Nov 11 11:03:25 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 11:03:25 latitude gnome-shell[1384]: Ignoring excess values in shadow definition
Nov 11 11:03:25 latitude blueman-tray[1778]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 11 11:03:25 latitude wpa_supplicant[786]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
Nov 11 11:03:25 latitude gnome-shell[1384]: DWifi Debug: Device Current State: 100
Nov 11 11:03:25 latitude gnome-shell[1384]: An active wireless connection, in infrastructure mode, involves no access point?
Nov 11 11:03:26 latitude wpa_supplicant[786]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Nov 11 11:03:26 latitude gnome-shell[1384]: Bogus presentation time 0 travelled back in time, using current time.
Nov 11 11:03:26 latitude gsd-usb-protect[1573]: Error calling USBGuard DBus to change the protection after a screensaver event: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.usbguard1 was not provided by any .service files
Nov 11 11:03:26 latitude systemd[1]: Reached target Sleep.
Nov 11 11:03:26 latitude systemd[1]: Starting Suspend...
Nov 11 11:03:27 latitude systemd-sleep[4739]: Suspending system...
Nov 11 11:03:27 latitude kernel: PM: suspend entry (deep)
Nov 11 11:03:27 latitude kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Nov 11 11:03:27 latitude kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Nov 11 11:03:27 latitude kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Nov 11 11:03:27 latitude kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Nov 11 11:03:27 latitude kernel: ata3.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Nov 11 11:03:27 latitude kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Nov 11 11:03:27 latitude kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Nov 11 11:03:27 latitude kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Nov 11 11:03:27 latitude kernel: ata3.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Nov 11 11:03:27 latitude kernel: ata3.00: configured for UDMA/133
Nov 11 11:03:27 latitude kernel: ata3.00: Enabling discard_zeroes_data

Hardware information and configuration?

I have a Dell Latitude 5490 with a wd19tb thunderbolt dock. This happens on and off the dock.
image

This morning I woke by pressing the power button on my dock instead of keyboard. Then my keyboard and mouse didn’t work.

Nov 13 06:03:28 latitude kernel: hub 1-1.3:1.0: hub_ext_port_status failed (err = -71)
Nov 13 06:03:28 latitude kernel: hub 1-1.3:1.0: hub_ext_port_status failed (err = -71)
Nov 13 06:03:28 latitude kernel: hub 1-1.3:1.0: hub_ext_port_status failed (err = -71)
Nov 13 06:03:28 latitude kernel: usb 1-1.3-port3: cannot disable (err = -71)
Nov 13 06:03:28 latitude kernel: hub 1-1.3:1.0: hub_ext_port_status failed (err = -71)
Nov 13 06:03:28 latitude kernel: usb 1-1.3-port2: cannot disable (err = -71)
Nov 13 06:03:28 latitude kernel: hub 1-1.3:1.0: hub_ext_port_status failed (err = -71)
Nov 13 06:03:28 latitude kernel: usb 1-1.3-port5: cannot disable (err = -71)
Nov 13 06:03:28 latitude kernel: usb 1-1.3-port4: cannot disable (err = -71)
Nov 13 06:03:28 latitude kernel: usb 1-7: reset full-speed USB device number 5 using xhci_hcd

You’re got fairly new hardware, so have you tried the 5.9 kernel?

@linkthepirate

Do you have an external keyboard and mouse hooked up to the dock?

Yes, and earlier my system restarted from locking the screen:

Nov 14 13:49:03 latitude gnome-shell[2319]: Ignoring excess values in shadow definition
Nov 14 13:49:03 latitude gnome-shell[2319]: Ignoring excess values in shadow definition
Nov 14 13:49:03 latitude gnome-shell[2319]: Ignoring excess values in shadow definition
Nov 14 13:49:03 latitude gnome-shell[2319]: Ignoring excess values in shadow definition
Nov 14 13:49:03 latitude gnome-shell[2319]: Ignoring excess values in shadow definition
Nov 14 13:49:03 latitude gnome-shell[2319]: Ignoring excess values in shadow definition
Nov 14 13:49:03 latitude gnome-shell[2319]: Ignoring excess values in shadow definition
Nov 14 13:49:03 latitude gnome-shell[2319]: Ignoring excess values in shadow definition
Nov 14 13:49:03 latitude remmina[30995]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 14 13:49:03 latitude blueman-tray[3649]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 14 13:49:03 latitude gnome-shell[2319]: DWifi Debug: Device Current State: 100
Nov 14 13:49:03 latitude gnome-shell[2319]: libinput error: event9  - SteelSeries SteelSeries Apex M500 Gaming Keyboard: client bug: event processing lagging behind by 272ms, your system is too slow
Nov 14 13:49:04 latitude gsd-usb-protect[3368]: Error calling USBGuard DBus to change the protection after a screensaver event: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.usbguard1 was not provided by any .service files
Nov 14 13:49:04 latitude gnome-shell[2319]: Bogus presentation time 0 travelled back in time, using current time.

I typically keep to the lts kernel but I have tried for testing yes.

Make sure is plugged into usb2.

Um, I don’t have USB2

So the mouse or keyboard is hooked to the Dock and won’t wake display? I wonder if usb auto suspend is in play?

It’s only when it has been a while. Also if I press the power button on the dock instead of waking with keyboard it’s the opposite. Display turns on but peripherals do not work. Also I turned on tlp and set that to 0.

Nov 14 17:49:16 latitude systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Nov 14 17:49:16 latitude audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 14 17:49:16 latitude kernel: audit: type=1131 audit(1605397756.277:481): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:18 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:21 latitude gdm-password][6258]: gkr-pam: unlocked login keyring
Nov 14 17:49:21 latitude audit[6258]: USER_AUTH pid=6258 uid=0 auid=1000 ses=3 msg='op=PAM:authentication grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="link" exe="/usr/lib/gdm-session-worker" hostname=latitude addr=? terminal=/dev/tty1 res=success'
Nov 14 17:49:21 latitude kernel: audit: type=1100 audit(1605397761.661:482): pid=6258 uid=0 auid=1000 ses=3 msg='op=PAM:authentication grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="link" exe="/usr/lib/gdm-session-worker" hostname=latitude addr=? terminal=/dev/tty1 res=success'
Nov 14 17:49:21 latitude dbus-daemon[612]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.521' (uid=0 pid=6258 comm="gdm-session-worker [pam/gdm-password] ")
Nov 14 17:49:21 latitude dbus-daemon[612]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Nov 14 17:49:21 latitude gdm-password][6258]: pam_systemd_home(gdm-password:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Nov 14 17:49:21 latitude audit[6258]: USER_ACCT pid=6258 uid=0 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_access,pam_permit,pam_time acct="link" exe="/usr/lib/gdm-session-worker" hostname=latitude addr=? terminal=/dev/tty1 res=success'
Nov 14 17:49:21 latitude kernel: audit: type=1101 audit(1605397761.663:483): pid=6258 uid=0 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_access,pam_permit,pam_time acct="link" exe="/usr/lib/gdm-session-worker" hostname=latitude addr=? terminal=/dev/tty1 res=success'
Nov 14 17:49:21 latitude audit[6258]: CRED_REFR pid=6258 uid=0 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="link" exe="/usr/lib/gdm-session-worker" hostname=latitude addr=? terminal=/dev/tty1 res=success'
Nov 14 17:49:21 latitude kernel: audit: type=1110 audit(1605397761.665:484): pid=6258 uid=0 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="link" exe="/usr/lib/gdm-session-worker" hostname=latitude addr=? terminal=/dev/tty1 res=success'
Nov 14 17:49:21 latitude gnome-shell[3140]: DWifi Debug: Adding menu..
Nov 14 17:49:21 latitude gnome-shell[3140]: DWifi Debug: Device Current State: 100
Nov 14 17:49:21 latitude gnome-shell[3140]: Usage of object.actor is deprecated for ATIndicator
                                            get@resource:///org/gnome/shell/ui/environment.js:314:29
                                            _init@/home/link/.local/share/gnome-shell/extensions/removeaccesibility@lomegor/extension.js:37:9
                                            wrapper@resource:///org/gnome/gjs/modules/script/_legacy.js:82:27
                                            _Base.prototype._construct@resource:///org/gnome/gjs/modules/script/_legacy.js:18:10
                                            newClass@resource:///org/gnome/gjs/modules/script/_legacy.js:114:21
                                            enable@/home/link/.local/share/gnome-shell/extensions/removeaccesibility@lomegor/extension.js:72:19
                                            _callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:167:32
                                            _enableAllExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:599:22
                                            _enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:598:37
                                            _sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:626:18
                                            _emit@resource:///org/gnome/gjs/modules/core/_signals.js:133:47
                                            _sync@resource:///org/gnome/shell/ui/sessionMode.js:195:14
                                            popMode@resource:///org/gnome/shell/ui/sessionMode.js:163:14
                                            _continueDeactivate@resource:///org/gnome/shell/ui/screenShield.js:499:30
                                            deactivate/<@resource:///org/gnome/shell/ui/screenShield.js:490:44
                                            finish@resource:///org/gnome/shell/gdm/authPrompt.js:528:13
                                            finish@resource:///org/gnome/shell/ui/unlockDialog.js:870:26
                                            deactivate@resource:///org/gnome/shell/ui/screenShield.js:490:26
                                            ScreenShield/</<@resource:///org/gnome/shell/ui/screenShield.js:109:57
                                            _emit@resource:///org/gnome/gjs/modules/core/_signals.js:133:47
                                            _convertToNativeSignal@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:169:19
Nov 14 17:49:21 latitude gnome-shell[3140]: Usage of object.actor is deprecated for ClipboardIndicator
                                            get@resource:///org/gnome/shell/ui/environment.js:314:29
                                            _init@/home/link/.local/share/gnome-shell/extensions/clipboard-indicator@tudmotu.com/extension.js:92:9
                                            wrapper@resource:///org/gnome/gjs/modules/script/_legacy.js:82:27
                                            enable@/home/link/.local/share/gnome-shell/extensions/clipboard-indicator@tudmotu.com/extension.js:873:26
                                            _callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:167:32
                                            _enableAllExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:599:22
                                            _enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:598:37
                                            _sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:626:18
                                            _emit@resource:///org/gnome/gjs/modules/core/_signals.js:133:47
                                            _sync@resource:///org/gnome/shell/ui/sessionMode.js:195:14
                                            popMode@resource:///org/gnome/shell/ui/sessionMode.js:163:14
                                            _continueDeactivate@resource:///org/gnome/shell/ui/screenShield.js:499:30
                                            deactivate/<@resource:///org/gnome/shell/ui/screenShield.js:490:44
                                            finish@resource:///org/gnome/shell/gdm/authPrompt.js:528:13
                                            finish@resource:///org/gnome/shell/ui/unlockDialog.js:870:26
                                            deactivate@resource:///org/gnome/shell/ui/screenShield.js:490:26
                                            ScreenShield/</<@resource:///org/gnome/shell/ui/screenShield.js:109:57
                                            _emit@resource:///org/gnome/gjs/modules/core/_signals.js:133:47
                                            _convertToNativeSignal@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:169:19
Nov 14 17:49:21 latitude gnome-shell[3140]: loading user theme: /home/link/.themes/Arc-BLACK-3.36/gnome-shell/gnome-shell.css
Nov 14 17:49:21 latitude gnome-shell[3140]: Ignoring excess values in shadow definition
Nov 14 17:49:21 latitude gnome-shell[3140]: Ignoring excess values in shadow definition
Nov 14 17:49:21 latitude gnome-shell[3140]: Ignoring excess values in shadow definition
Nov 14 17:49:21 latitude gnome-shell[3140]: Ignoring excess values in shadow definition
Nov 14 17:49:22 latitude gnome-shell[3140]: Ignoring excess values in shadow definition
Nov 14 17:49:22 latitude gnome-shell[3140]: Ignoring excess values in shadow definition
Nov 14 17:49:22 latitude NetworkManager[614]: <info>  [1605397762.0945] agent-manager: agent[955f1cae001734f4,:1.78/org.gnome.Shell.NetworkAgent/1000]: agent registered
Nov 14 17:49:22 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:22 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:22 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:22 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:22 latitude gnome-shell[3140]: Ignoring excess values in shadow definition
Nov 14 17:49:22 latitude gnome-shell[3140]: Ignoring excess values in shadow definition
Nov 14 17:49:22 latitude gnome-shell[3140]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Nov 14 17:49:22 latitude gnome-shell[3140]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Nov 14 17:49:22 latitude gnome-shell[3140]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Nov 14 17:49:22 latitude gnome-shell[3140]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Nov 14 17:49:22 latitude gnome-shell[3140]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Nov 14 17:49:22 latitude gnome-shell[3140]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Nov 14 17:49:22 latitude gnome-shell[3140]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Nov 14 17:49:22 latitude gnome-shell[3140]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Nov 14 17:49:22 latitude gnome-shell[3140]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Nov 14 17:49:22 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:22 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:22 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:22 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:22 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:22 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:22 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:22 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:22 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:22 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:22 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:22 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:22 latitude gnome-shell[3140]: Can't update stage views actor StLabel is on because it needs an allocation.
Nov 14 17:49:22 latitude gnome-shell[3140]: Can't update stage views actor ClutterText is on because it needs an allocation.
Nov 14 17:49:22 latitude gsd-usb-protect[3405]: Error calling USBGuard DBus to change the protection after a screensaver event: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.usbguard1 was not provided by any .service files
Nov 14 17:49:52 latitude systemd[1]: systemd-hostnamed.service: Succeeded.
Nov 14 17:49:52 latitude audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 14 17:49:52 latitude kernel: audit: type=1131 audit(1605397792.159:485): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 14 17:49:52 latitude audit: BPF prog-id=18 op=UNLOAD
Nov 14 17:49:52 latitude audit: BPF prog-id=17 op=UNLOAD
Nov 14 17:49:52 latitude kernel: audit: type=1334 audit(1605397792.219:486): prog-id=18 op=UNLOAD
Nov 14 17:49:52 latitude kernel: audit: type=1334 audit(1605397792.219:487): prog-id=17 op=UNLOAD
Nov 14 17:50:59 latitude gnome-shell[3140]: Ignoring excess values in shadow definition
Nov 14 17:50:59 latitude gnome-shell[3140]: Ignoring excess values in shadow definition
Nov 14 17:50:59 latitude gnome-shell[3140]: Ignoring excess values in shadow definition
Nov 14 17:50:59 latitude gnome-shell[3140]: Ignoring excess values in shadow definition
Nov 14 17:51:00 latitude gnome-shell[3140]: DWifi Debug: Device Current State: 100

Looks to be something called USBguard missing but I tried installing it and it disabled everything, even after allowing device by ID.

There are two packages available for usbguard. One is usbguard and the other is usbguard-git which is in the AUR as per:

I haven’t used it before but it looks like it’s a access blocker for devices. You need to determine if it’s actually installed. You have to configure it before enabling it and starting it or all usb devices will automatically be blocked. The Arch wiki explains it if you can understand it.

Rules
To configure USBGuard to your needs, you can edit /etc/usbguard/rules.conf. However manual editing of the rules is normally not necessary. You can generate a ruleset based on your currently attached USB devices by executing usbguard generate-policy > /etc/usbguard/rules.conf as root.

Hope this helps. Go back an read through the wiki starting at installation, configuration, usage & rules.

Ok I got it rolling, and will report back tomorrow.
To be honest though, I feel like this is going a bit into left field. The issue seems to be a functional issue and we are installing a security “feature” app to try and resolve.

Well i don’t really know. It is a security feature but, when it goes to sleep and gets woken up it may have something to do with it? Don’t know but you can see if the same error message is there or not and whether it has any affect on this issue.

True, but my train of logic is, this is an optional feature, and by default all USB devices should be accepted. So the issue isn’t that the package isn’t installed but rather that it’s being depended on at all. I guess once I try to wake it up again I will see if the issue persists.

Well it’s likely a Gnome thing to do with Gnome keyring and such. I really don’t know as i don’t use Gnome much and haven’t seen this before. Like you say it may have nothing to do with your issue. It’s just another thing. :man_shrugging:

So I’ve had three successful wakes. Guess I will open an issue with GNOME. Or just leave it as I found a line in the config file to default allow.