You are not logged in.

Pages: 1

#1 2026-09-15 20:36:19

cpvzimaurjzmxtovge
Member
Registered: 2021-11-21
Posts: 3

Systemd suspend doesn't go to deep sleep

Hi All,

I'm having trouble with suspending with systemd my desktop PC: AMD Ryzen 5 35003600 with Radeon 6700XT.

# cat /sys/power/mem_sleep
s2idle [deep]
# echo mem > /sys/power/state

works fine. System goes to deep sleep - fans turn off and I need to push power button to resume.

But when I try to use:

$ systemctl suspend

command or try using suspend option in Gnome (wayland), the screen goes black for a few seconds (fans on), then I'm greeted by lock screen.
I think it's probably something systemd related, because directly echoing into /sys/power/state works fine and system resumes correctly, but I can't tell what's wrong.

Here's my config:

$ cat /etc/systemd/sleep.conf
[Sleep]
AllowSuspend=yes
AllowHibernation=no
AllowSuspendThenHibernate=no
AllowHybridSleep=no
SuspendState=mem
MemorySleepMode=deep

and logs:

$ journalctl -b -g suspend
sep 15 22:11:07 desktop systemd-logind[635]: suspend requested from client PID 9489 ('systemctl') (unit user@1000.service)...
sep 15 22:11:07 desktop systemd-logind[635]: The system will suspend now!

Thanks for help

EDIT: fix typo in CPU name

Last edited by cpvzimaurjzmxtovge (2026-09-15 20:39:08)

Offline

#2 2026-09-16 00:29:35

chrislleyalves
Member
From: Brazil
Registered: 2026-09-15
Posts: 4
Website

Re: Systemd suspend doesn't go to deep sleep

It could be an issue related with your login display manager (lightdm, sddm, gdm...). Try disabling "lock screen after suspend" option on the power manager settings.

Offline

#3 2026-09-16 06:58:49

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,833

Re: Systemd suspend doesn't go to deep sleep

"journalctl -b -g suspend" won't tell anything here.
Please post your complete system journal for a boot covering the failed suspend 

sudo journalctl -b | nc termbin.com 9999

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#4 Yesterday 20:45:55

cpvzimaurjzmxtovge
Member
Registered: 2021-11-21
Posts: 3

Re: Systemd suspend doesn't go to deep sleep

I'm using gdm as display manger. Here are my gdm and power settings:

$ cat /etc/gdm/custom.conf
[daemon]
AutomaticLoginEnable=False
AutomaticLogin=user
[security]
[xdmcp]
[chooser]
[debug]
$ DCONF_PROFILE=gdm gsettings list-recursively org.gnome.login-screen
org.gnome.login-screen allowed-failures 3
org.gnome.login-screen banner-message-enable false
org.gnome.login-screen banner-message-path ''
org.gnome.login-screen banner-message-source 'settings'
org.gnome.login-screen banner-message-text 'Welcome!'
org.gnome.login-screen disable-restart-buttons false
org.gnome.login-screen disable-user-list false
org.gnome.login-screen enable-fingerprint-authentication true
org.gnome.login-screen enable-passkey-authentication true
org.gnome.login-screen enable-password-authentication true
org.gnome.login-screen enable-smartcard-authentication false
org.gnome.login-screen enable-switchable-authentication true
org.gnome.login-screen enable-web-authentication true
org.gnome.login-screen fallback-logo ''
org.gnome.login-screen logo ''
$ gsettings list-recursively org.gnome.login-screen
org.gnome.login-screen allowed-failures 3
org.gnome.login-screen banner-message-enable false
org.gnome.login-screen banner-message-path ''
org.gnome.login-screen banner-message-source 'settings'
org.gnome.login-screen banner-message-text ''
org.gnome.login-screen disable-restart-buttons false
org.gnome.login-screen disable-user-list false
org.gnome.login-screen enable-fingerprint-authentication true
org.gnome.login-screen enable-passkey-authentication true
org.gnome.login-screen enable-password-authentication true
org.gnome.login-screen enable-smartcard-authentication false
org.gnome.login-screen enable-switchable-authentication true
org.gnome.login-screen enable-web-authentication true
org.gnome.login-screen fallback-logo ''
org.gnome.login-screen logo '/usr/share/pixmaps/archlinux-logo-text-dark.svg'
$ gsettings list-recursively org.gnome.settings-daemon.plugins.power
org.gnome.settings-daemon.plugins.power ambient-enabled true
org.gnome.settings-daemon.plugins.power idle-brightness 30
org.gnome.settings-daemon.plugins.power idle-dim true
org.gnome.settings-daemon.plugins.power power-button-action 'interactive'
org.gnome.settings-daemon.plugins.power power-saver-profile-on-low-battery true
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 900
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing'
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 900
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend'

I can't see  option to disable "lock screen after suspend" anywhere.
Did you mean "Privacy & Security > Screen Lock > Automatic Screen Lock" setting?
Turning it off changes the suspend behavior. Computer still doesn't go to deep sleep, screen goes back and after few seconds it turns on again (without any interaction), but this time, instead of showing lock screen it goes directly to desktop.

Here are logs just after ran:

logger "before suspend" && systemctl suspend

then I logged back:

sep 17 22:21:23 desktop user[16679]: before suspend
sep 17 22:21:23 desktop systemd-logind[622]: suspend requested from client PID 16680 ('systemctl') (unit user@1000.service)...
sep 17 22:21:23 desktop rtkit-daemon[874]: Demoting known real-time threads.
sep 17 22:21:23 desktop rtkit-daemon[874]: Successfully demoted thread 3407 of process 3375.
sep 17 22:21:23 desktop NetworkManager[616]: <info>  [1789676483.0967] manager: sleep: sleep requested (sleeping: no  enabled: yes)
sep 17 22:21:23 desktop rtkit-daemon[874]: Successfully demoted thread 3252 of process 3147.
sep 17 22:21:23 desktop NetworkManager[616]: <info>  [1789676483.0968] device (enp34s0): state change: unavailable -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
sep 17 22:21:23 desktop rtkit-daemon[874]: Successfully demoted thread 3220 of process 3147.
sep 17 22:21:23 desktop systemd-logind[622]: The system will suspend now!
sep 17 22:21:23 desktop rtkit-daemon[874]: Successfully demoted thread 3147 of process 3147.
sep 17 22:21:23 desktop rtkit-daemon[874]: Successfully demoted thread 3161 of process 3149.
sep 17 22:21:23 desktop rtkit-daemon[874]: Successfully demoted thread 3149 of process 3149.
sep 17 22:21:23 desktop rtkit-daemon[874]: Successfully demoted thread 3156 of process 3146.
sep 17 22:21:23 desktop rtkit-daemon[874]: Successfully demoted thread 3146 of process 3146.
sep 17 22:21:23 desktop rtkit-daemon[874]: Demoted 8 threads.
sep 17 22:21:23 desktop NetworkManager[616]: <info>  [1789676483.1028] device (xx:xx:xx:xx:xx:xx): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
sep 17 22:21:23 desktop NetworkManager[616]: <info>  [1789676483.1030] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
sep 17 22:21:23 desktop NetworkManager[616]: <info>  [1789676483.1031] manager: NetworkManager state is now DISABLED (ASLEEP)
sep 17 22:21:23 desktop NetworkManager[616]: <info>  [1789676483.1033] device (wlan0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
sep 17 22:21:23 desktop NetworkManager[616]: <info>  [1789676483.1033] dhcp4 (wlan0): canceled DHCP transaction
sep 17 22:21:23 desktop NetworkManager[616]: <info>  [1789676483.1033] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
sep 17 22:21:23 desktop NetworkManager[616]: <info>  [1789676483.1033] dhcp4 (wlan0): state changed no lease
sep 17 22:21:23 desktop avahi-daemon[618]: Withdrawing address record for 192.168.50.68 on wlan0.
sep 17 22:21:23 desktop dhcpcd[631]: wlan0: pid 616 deleted IP address 192.168.50.68/24
sep 17 22:21:23 desktop dhcpcd[631]: wlan0: deleting route to 192.168.50.0/24
sep 17 22:21:23 desktop avahi-daemon[618]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.50.68.
sep 17 22:21:23 desktop avahi-daemon[618]: Interface wlan0.IPv4 no longer relevant for mDNS.
sep 17 22:21:23 desktop dhcpcd[631]: wlan0: deleting default route via 192.168.50.1
sep 17 22:21:23 desktop systemd[1]: Starting Network Manager Script Dispatcher Service...
sep 17 22:21:23 desktop systemd[1]: Started Network Manager Script Dispatcher Service.
sep 17 22:21:23 desktop gnome-shell[3375]: ../glib/gobject/gsignal.c:2723: instance '0x558a8fcbf3e0' has no handler with id '49944'
sep 17 22:21:23 desktop kernel: wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING)
sep 17 22:21:23 desktop dhcpcd[16715]: resolvconf: signature mismatch: /etc/resolv.conf
sep 17 22:21:23 desktop dhcpcd[16715]: resolvconf: run `resolvconf -u` to update
sep 17 22:21:23 desktop dhcpcd[631]: wlan0: rebinding lease of 192.168.50.68
sep 17 22:21:23 desktop dhcpcd[631]: wlan0: carrier lost
sep 17 22:21:23 desktop gnome-shell[3375]: Type GITypeInfo of property AccountsService.User::password-mode does not match return type GITypeInfo of getter get_password_mode. Falling back to slow path
sep 17 22:21:23 desktop gnome-shell[3375]: cutting-corners(assertAllDisposed): disposableCount = 2
sep 17 22:21:23 desktop gnome-shell[3375]: Assertion failed: cutting-corners(assertAllDisposed)
sep 17 22:21:23 desktop dhcpcd[16762]: resolvconf: signature mismatch: /etc/resolv.conf
sep 17 22:21:23 desktop dhcpcd[16762]: resolvconf: run `resolvconf -u` to update
sep 17 22:21:23 desktop dhcpcd[631]: wlan0: deleting address xxxx::xxxx:xxxx:xxxx:xxxx
sep 17 22:21:23 desktop avahi-daemon[618]: Withdrawing address record for xxxx::xxxx:xxxx:xxxx:xxxx on wlan0.
sep 17 22:21:23 desktop gnome-shell[3375]: ../glib/gobject/gsignal.c:2723: instance '0x558a90968870' has no handler with id '36721'
sep 17 22:21:23 desktop gnome-shell[3375]: ../glib/gobject/gsignal.c:2723: instance '0x558a90968870' has no handler with id '36722'
sep 17 22:21:23 desktop gnome-shell[3375]: ../glib/gobject/gsignal.c:2723: instance '0x558a90968870' has no handler with id '36723'
sep 17 22:21:23 desktop gnome-shell[3375]: ../glib/gobject/gsignal.c:2723: instance '0x558a90968870' has no handler with id '36724'
sep 17 22:21:23 desktop gnome-shell[3375]: ../glib/gobject/gsignal.c:2723: instance '0x558a90968870' has no handler with id '36725'
sep 17 22:21:23 desktop dhcpcd[16803]: resolvconf: signature mismatch: /etc/resolv.conf
sep 17 22:21:23 desktop dhcpcd[16803]: resolvconf: run `resolvconf -u` to update
sep 17 22:21:23 desktop wpa_supplicant[702]: wlan0: CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=3 locally_generated=1
sep 17 22:21:23 desktop wpa_supplicant[702]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
sep 17 22:21:23 desktop NetworkManager[616]: <info>  [1789676483.2103] device (wlan0): supplicant interface state: completed -> disconnected
sep 17 22:21:23 desktop NetworkManager[616]: <info>  [1789676483.2104] device (wlan0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
sep 17 22:21:23 desktop avahi-daemon[618]: Withdrawing address record for xxxx::xxxx:xxxx:xxxx:xxxx on wlan0.
sep 17 22:21:23 desktop avahi-daemon[618]: Leaving mDNS multicast group on interface wlan0.IPv6 with address xxxx::xxxx:xxxx:xxxx:xxxx.
sep 17 22:21:23 desktop avahi-daemon[618]: Interface wlan0.IPv6 no longer relevant for mDNS.
sep 17 22:21:23 desktop wpa_supplicant[702]: wlan0: PMKSA-CACHE-REMOVED xx:xx:xx:xx:xx:xx 0
sep 17 22:21:23 desktop dhcpcd[631]: wlan0: old hardware address: xx:xx:xx:xx:xx:xx
sep 17 22:21:23 desktop dhcpcd[631]: wlan0: new hardware address: xx:xx:xx:xx:xx:xx
sep 17 22:21:23 desktop NetworkManager[616]: <info>  [1789676483.2198] device (wlan0): set-hw-addr: set MAC address to xx:xx:xx:xx:xx:xx (scanning)
sep 17 22:21:23 desktop NetworkManager[616]: <info>  [1789676483.2217] device (wlan0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
sep 17 22:21:23 desktop gsd-sharing[3547]: Failed to stop gnome-user-share-webdav.service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-user-share-webdav.service not loaded.
sep 17 22:21:23 desktop gsd-sharing[3547]: Failed to stop rygel.service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
sep 17 22:21:23 desktop indicators[3550]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
sep 17 22:21:23 desktop indicators[3550]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
sep 17 22:21:23 desktop indicators[3550]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
sep 17 22:21:23 desktop dhcpcd[631]: wlan0: old hardware address: xx:xx:xx:xx:xx:xx
sep 17 22:21:23 desktop dhcpcd[631]: wlan0: new hardware address: xx:xx:xx:xx:xx:xx
sep 17 22:21:23 desktop NetworkManager[616]: <info>  [1789676483.3525] device (wlan0): set-hw-addr: reset MAC address to xx:xx:xx:xx:xx:xx (unmanage)
sep 17 22:21:23 desktop wpa_supplicant[702]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
sep 17 22:21:23 desktop wpa_supplicant[702]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
sep 17 22:21:23 desktop wpa_supplicant[702]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
sep 17 22:21:23 desktop wpa_supplicant[702]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
sep 17 22:21:23 desktop wpa_supplicant[702]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
sep 17 22:21:23 desktop wpa_supplicant[702]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
sep 17 22:21:23 desktop gnome-shell[3375]: Cursor update failed: drmModeAtomicCommit: Invalid argument
sep 17 22:21:23 desktop systemd-logind[622]: Error during inhibitor-delayed operation (already returned success to client): Unit sleep.target is masked.
sep 17 22:21:23 desktop NetworkManager[616]: <info>  [1789676483.9799] manager: sleep: wake requested (sleeping: yes  enabled: yes)
sep 17 22:21:23 desktop NetworkManager[616]: <info>  [1789676483.9800] device (enp34s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
sep 17 22:21:23 desktop gsd-usb-protection[3581]: Error calling USBGuard DBus to change the protection after a screensaver event: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.usbguard1': activation request failed: unknown unit
sep 17 22:21:23 desktop rtkit-daemon[874]: Resuming known real-time threads.
sep 17 22:21:23 desktop rtkit-daemon[874]: Successfully made thread 3407 of process 3375 owned by '1000' high priority at nice level -15.
sep 17 22:21:23 desktop rtkit-daemon[874]: Successfully made thread 3252 of process 3147 owned by '1000' RT at priority 20.
sep 17 22:21:23 desktop rtkit-daemon[874]: Successfully made thread 3220 of process 3147 owned by '1000' RT at priority 20.
sep 17 22:21:23 desktop rtkit-daemon[874]: Successfully made thread 3147 of process 3147 owned by '1000' high priority at nice level -11.
sep 17 22:21:23 desktop rtkit-daemon[874]: Successfully made thread 3161 of process 3149 owned by '1000' RT at priority 20.
sep 17 22:21:23 desktop rtkit-daemon[874]: Successfully made thread 3149 of process 3149 owned by '1000' high priority at nice level -11.
sep 17 22:21:23 desktop rtkit-daemon[874]: Successfully made thread 3156 of process 3146 owned by '1000' RT at priority 20.
sep 17 22:21:23 desktop rtkit-daemon[874]: Successfully made thread 3146 of process 3146 owned by '1000' high priority at nice level -11.
sep 17 22:21:23 desktop rtkit-daemon[874]: Resumed scheduling 8 threads.
sep 17 22:21:24 desktop kernel: Generic FE-GE Realtek PHY r8169-0-2200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-2200:00, irq=MAC)
sep 17 22:21:24 desktop NetworkManager[616]: <info>  [1789676484.1279] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
sep 17 22:21:24 desktop kernel: r8169 0000:22:00.0 enp34s0: Link is Down
sep 17 22:21:24 desktop NetworkManager[616]: <info>  [1789676484.1289] device (xx:xx:xx:xx:xx:xx): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
sep 17 22:21:24 desktop NetworkManager[616]: <warn>  [1789676484.1289] device (xx:xx:xx:xx:xx:xx): error setting IPv4 forwarding to '1': Resource temporarily unavailable
sep 17 22:21:24 desktop NetworkManager[616]: <info>  [1789676484.1290] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
sep 17 22:21:24 desktop NetworkManager[616]: <warn>  [1789676484.1290] device (p2p-dev-wlan0): error setting IPv4 forwarding to '1': Resource temporarily unavailable
sep 17 22:21:24 desktop NetworkManager[616]: <info>  [1789676484.1291] manager: NetworkManager state is now CONNECTED_LOCAL
sep 17 22:21:24 desktop NetworkManager[616]: <info>  [1789676484.1293] device (xx:xx:xx:xx:xx:xx): state change: unavailable -> disconnected (reason 'none', managed-type: 'full')
sep 17 22:21:24 desktop wpa_supplicant[702]: wlan0: nl80211: kernel reports: multicast RX registrations are not supported
sep 17 22:21:24 desktop wpa_supplicant[702]: p2p-dev-wlan0: nl80211: kernel reports: multicast RX registrations are not supported
sep 17 22:21:24 desktop NetworkManager[616]: <info>  [1789676484.1430] device (wlan0): supplicant interface state: internal-starting -> disconnected
sep 17 22:21:24 desktop NetworkManager[616]: <info>  [1789676484.1430] device (p2p-dev-wlan0): state change: unavailable -> unmanaged (reason 'unmanaged-link-not-init', managed-type: 'removed')
sep 17 22:21:24 desktop NetworkManager[616]: <info>  [1789676484.1432] Wi-Fi P2P device controlled by interface wlan0 created
sep 17 22:21:24 desktop NetworkManager[616]: <info>  [1789676484.1433] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/13)
sep 17 22:21:24 desktop NetworkManager[616]: <info>  [1789676484.1435] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
sep 17 22:21:24 desktop NetworkManager[616]: <warn>  [1789676484.1435] device (p2p-dev-wlan0): error setting IPv4 forwarding to '1': Resource temporarily unavailable
sep 17 22:21:24 desktop NetworkManager[616]: <info>  [1789676484.1438] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', managed-type: 'full')
sep 17 22:21:24 desktop NetworkManager[616]: <info>  [1789676484.1440] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', managed-type: 'full')
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7677] policy: auto-activating connection 'XXXXXXXXXX_nomap' (790da11b-d86c-4d37-bf31-fffc267d89b9)
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7679] device (wlan0): Activation: starting connection 'XXXXXXXXXX_nomap' (790da11b-d86c-4d37-bf31-fffc267d89b9)
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7680] device (wlan0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7681] manager: NetworkManager state is now CONNECTING
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7682] device (wlan0): state change: prepare -> config (reason 'none', managed-type: 'full')
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7683] device (wlan0): Activation: (wifi) access point 'XXXXXXXXXX_nomap' has security, but secrets are required.
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7683] device (wlan0): state change: config -> need-auth (reason 'none', managed-type: 'full')
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7688] device (wlan0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7689] device (wlan0): state change: prepare -> config (reason 'none', managed-type: 'full')
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7690] device (wlan0): Activation: (wifi) connection 'XXXXXXXXXX_nomap' has security, and secrets exist.  No new secrets needed.
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7690] Config: added 'ssid' value 'XXXXXXXXXX_nomap'
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7690] Config: added 'scan_ssid' value '1'
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7690] Config: added 'bgscan' value 'simple:30:-70:86400'
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7691] Config: added 'key_mgmt' value 'SAE FT-SAE'
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7691] Config: added 'psk' value '<hidden>'
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7691] Config: added 'ieee80211w' value '2'
sep 17 22:21:26 desktop wpa_supplicant[702]: wlan0: SME: Trying to authenticate with xx:xx:xx:xx:xx:xx (SSID='XXXXXXXXXX_nomap' freq=2427 MHz)
sep 17 22:21:26 desktop kernel: wlan0: authenticate with xx:xx:xx:xx:xx:xx (local address=xx:xx:xx:xx:xx:xx)
sep 17 22:21:26 desktop kernel: wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7787] device (wlan0): supplicant interface state: disconnected -> authenticating
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7788] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> authenticating
sep 17 22:21:26 desktop wpa_supplicant[702]: wlan0: SME: Trying to authenticate with xx:xx:xx:xx:xx:xx (SSID='XXXXXXXXXX_nomap' freq=2427 MHz)
sep 17 22:21:26 desktop kernel: wlan0: authenticate with xx:xx:xx:xx:xx:xx (local address=xx:xx:xx:xx:xx:xx)
sep 17 22:21:26 desktop kernel: wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
sep 17 22:21:26 desktop kernel: wlan0: authenticated
sep 17 22:21:26 desktop wpa_supplicant[702]: wlan0: PMKSA-CACHE-ADDED xx:xx:xx:xx:xx:xx 0
sep 17 22:21:26 desktop wpa_supplicant[702]: wlan0: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='XXXXXXXXXX_nomap' freq=2427 MHz)
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7976] device (wlan0): supplicant interface state: authenticating -> associating
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.7976] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
sep 17 22:21:26 desktop kernel: wlan0: associate with xx:xx:xx:xx:xx:xx (try 1/3)
sep 17 22:21:26 desktop kernel: wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x1411 status=0 aid=30)
sep 17 22:21:26 desktop wpa_supplicant[702]: wlan0: Associated with xx:xx:xx:xx:xx:xx
sep 17 22:21:26 desktop wpa_supplicant[702]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
sep 17 22:21:26 desktop kernel: wlan0: associated
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.8234] device (wlan0): supplicant interface state: associating -> 4way_handshake
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.8234] device (p2p-dev-wlan0): supplicant management interface state: associating -> 4way_handshake
sep 17 22:21:26 desktop wpa_supplicant[702]: wlan0: WPA: Key negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=CCMP]
sep 17 22:21:26 desktop wpa_supplicant[702]: wlan0: CTRL-EVENT-CONNECTED - Connection to xx:xx:xx:xx:xx:xx completed [id=0 id_str=]
sep 17 22:21:26 desktop dhcpcd[631]: wlan0: carrier acquired
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.8488] device (wlan0): supplicant interface state: 4way_handshake -> completed
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.8488] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "XXXXXXXXXX_nomap"
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.8488] device (p2p-dev-wlan0): supplicant management interface state: 4way_handshake -> completed
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.8489] device (wlan0): state change: config -> ip-config (reason 'none', managed-type: 'full')
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.8491] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
sep 17 22:21:26 desktop dhcpcd[631]: wlan0: IAID e3:7b:e9:36
sep 17 22:21:26 desktop kernel: wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by xx:xx:xx:xx:xx:xx
sep 17 22:21:26 desktop NetworkManager[616]: <info>  [1789676486.8689] dhcp4 (wlan0): state changed new lease, address=192.168.50.68, acd pending
sep 17 22:21:27 desktop NetworkManager[616]: <info>  [1789676487.0405] dhcp4 (wlan0): state changed new lease, address=192.168.50.68
sep 17 22:21:27 desktop avahi-daemon[618]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.50.68.
sep 17 22:21:27 desktop avahi-daemon[618]: New relevant interface wlan0.IPv4 for mDNS.
sep 17 22:21:27 desktop avahi-daemon[618]: Registering new address record for 192.168.50.68 on wlan0.IPv4.
sep 17 22:21:27 desktop NetworkManager[616]: <info>  [1789676487.0417] policy: set 'XXXXXXXXXX_nomap' (wlan0) as default for IPv4 routing and DNS
sep 17 22:21:27 desktop gsd-sharing[3547]: Failed to stop gnome-user-share-webdav.service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-user-share-webdav.service not loaded.
sep 17 22:21:27 desktop gsd-sharing[3547]: Failed to stop rygel.service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
sep 17 22:21:27 desktop NetworkManager[616]: <info>  [1789676487.0574] device (wlan0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
sep 17 22:21:27 desktop NetworkManager[616]: <info>  [1789676487.0581] device (wlan0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
sep 17 22:21:27 desktop NetworkManager[616]: <info>  [1789676487.0581] device (wlan0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
sep 17 22:21:27 desktop NetworkManager[616]: <info>  [1789676487.0583] manager: NetworkManager state is now CONNECTED_SITE
sep 17 22:21:27 desktop NetworkManager[616]: <info>  [1789676487.0586] device (wlan0): Activation: successful, device activated.
sep 17 22:21:27 desktop NetworkManager[616]: <info>  [1789676487.2067] manager: NetworkManager state is now CONNECTED_GLOBAL
sep 17 22:21:27 desktop dhcpcd[631]: wlan0: soliciting an IPv6 router
sep 17 22:21:27 desktop dhcpcd[631]: wlan0: rebinding lease of 192.168.50.68
sep 17 22:21:27 desktop dhcpcd[631]: wlan0: leased 192.168.50.68 for 86400 seconds
sep 17 22:21:27 desktop dhcpcd[631]: wlan0: changing route to 192.168.50.0/24
sep 17 22:21:27 desktop dhcpcd[631]: wlan0: changing default route via 192.168.50.1
sep 17 22:21:27 desktop dhcpcd[17079]: resolvconf: signature mismatch: /etc/resolv.conf
sep 17 22:21:27 desktop dhcpcd[17079]: resolvconf: run `resolvconf -u` to update
sep 17 22:21:28 desktop avahi-daemon[618]: Joining mDNS multicast group on interface wlan0.IPv6 with address xxxx::xxxx:xxxx:xxxx:xxxx.
sep 17 22:21:28 desktop avahi-daemon[618]: New relevant interface wlan0.IPv6 for mDNS.
sep 17 22:21:28 desktop avahi-daemon[618]: Registering new address record for xxxx::xxxx:xxxx:xxxx:xxxx on wlan0.*.
sep 17 22:21:30 desktop gdm-password][17102]: gkr-pam: unlocked login keyring
sep 17 22:21:30 desktop systemd[3126]: Started dbus-:1.1-org.gnome.Shell.CalendarServer@2.service.
sep 17 22:21:30 desktop gnome-shell-calendar-server[17365]: /usr/lib/gnome-shell-calendar-server: error while loading shared libraries: libecal-2.0.so.3: cannot open shared object file: No such file or directory
sep 17 22:21:30 desktop systemd[3126]: dbus-:1.1-org.gnome.Shell.CalendarServer@2.service: Main process exited, code=exited, status=127/n/a
sep 17 22:21:30 desktop systemd[3126]: dbus-:1.1-org.gnome.Shell.CalendarServer@2.service: Failed with result 'exit-code'.
sep 17 22:21:30 desktop systemd[3126]: Started dbus-:1.1-org.gnome.Shell.CalendarServer@3.service.
sep 17 22:21:30 desktop gnome-shell-calendar-server[17370]: /usr/lib/gnome-shell-calendar-server: error while loading shared libraries: libecal-2.0.so.3: cannot open shared object file: No such file or directory
sep 17 22:21:30 desktop systemd[3126]: dbus-:1.1-org.gnome.Shell.CalendarServer@3.service: Main process exited, code=exited, status=127/n/a
sep 17 22:21:30 desktop systemd[3126]: dbus-:1.1-org.gnome.Shell.CalendarServer@3.service: Failed with result 'exit-code'.
sep 17 22:21:30 desktop gnome-shell[3375]: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.gnome.Shell.CalendarServer': unit failed
                                           
                                           Stack trace:
                                             asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:115:23
                                             @resource:///org/gnome/shell/ui/init.js:20:20
                                             
sep 17 22:21:30 desktop gnome-shell[3375]: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.gnome.Shell.CalendarServer': unit failed
                                           
                                           Stack trace:
                                             asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:115:23
                                             @resource:///org/gnome/shell/ui/init.js:20:20
                                             
sep 17 22:21:30 desktop gsd-usb-protection[3581]: Error calling USBGuard DBus to change the protection after a screensaver event: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.usbguard1': activation request failed: unknown unit
sep 17 22:21:33 desktop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

Last edited by cpvzimaurjzmxtovge (Yesterday 20:48:40)

Offline

#5 Yesterday 21:44:35

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,833

Re: Systemd suspend doesn't go to deep sleep

sep 17 22:21:23 desktop systemd-logind[622]: Error during inhibitor-delayed operation (already returned success to client): Unit sleep.target is masked.

You probably have dhcpcd and NM concurrently enabled (disable dhcpcd) but that's unlikely the cause of the inhibition.

systemd-inhibit --list
systemctl status sleep.target
systemctl show sleep.target

And otherwise

seth wrote:

Please post your complete system journal for a boot covering the failed suspend

- not some tail.
God know where this goes south.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB