Ubuntu Version:
Xubuntu 24.04.2 LTS, kernel 6.13.2.061302-generic
Desktop Environment (if applicable):
XFCE
Problem Description:
When I select Suspend from the Log Out menu, the display goes dark but the system does not enter the low power state. After a few seconds, a log in screen appears but it won't accept my password. I have to shut the system down and restart to resume normal operation.Relevant System Information:
Screenshots or Error Messages:
What I’ve Tried:
Did it ever work?
Does the login screen look like normal?
Are there any relevant errors to be found in the logs? Try grep EE /var/log/Xorg.0.log. You could also hunt around in journalctrl -b -1 for something relevant, or just post up the tail end of it, e.g. journalctl -b -1 | tail -n 200 | pastebinit.
24.04 never worked. 22.04 worked fine.
The login screen looks normal.
Tail end of journalctl:
Feb 21 16:44:47 Office systemd-logind[1365]: The system will suspend now!
Feb 21 16:44:47 Office NetworkManager[1457]: [1740185087.3795] manager: sleep: sleep requested (sleeping: no enabled: yes)
Feb 21 16:44:47 Office NetworkManager[1457]: [1740185087.3797] device (wlp0s20f3): state change: disconnected → unmanaged (reason ‘sleeping’, sys-iface-state: ‘managed’)
Feb 21 16:44:47 Office ModemManager[1486]: [sleep-monitor-systemd] system is about to suspend
Feb 21 16:44:47 Office NetworkManager[1457]: [1740185087.4017] device (p2p-dev-wlp0s20f3): state change: disconnected → unmanaged (reason ‘sleeping’, sys-iface-state: ‘managed’)
Feb 21 16:44:47 Office NetworkManager[1457]: [1740185087.4021] manager: NetworkManager state is now ASLEEP
Feb 21 16:44:47 Office NetworkManager[1457]: [1740185087.4023] device (enp3s0): state change: activated → deactivating (reason ‘sleeping’, sys-iface-state: ‘managed’)
Feb 21 16:44:47 Office wpa_supplicant[1480]: p2p-dev-wlp0s20: CTRL-EVENT-DSCP-POLICY clear_all
Feb 21 16:44:47 Office wpa_supplicant[1480]: p2p-dev-wlp0s20: CTRL-EVENT-DSCP-POLICY clear_all
Feb 21 16:44:47 Office wpa_supplicant[1480]: nl80211: deinit ifname=p2p-dev-wlp0s20 disabled_11b_rates=0
Feb 21 16:44:47 Office dbus-daemon[1338]: [system] Activating via systemd: service name=‘org.freedesktop.nm_dispatcher’ unit=‘dbus-org.freedesktop.nm-dispatcher.service’ requested by ‘:1.13’ (uid=0 pid=1457 comm=“/usr/sbin/NetworkManager --no-daemon”)
Feb 21 16:44:47 Office systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service…
Feb 21 16:44:47 Office dbus-daemon[1338]: [system] Successfully activated service ‘org.freedesktop.nm_dispatcher’
Feb 21 16:44:47 Office systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Feb 21 16:44:47 Office NetworkManager[1457]: [1740185087.4376] device (enp3s0): state change: deactivating → disconnected (reason ‘sleeping’, sys-iface-state: ‘managed’)
Feb 21 16:44:47 Office wpa_supplicant[1480]: wlp0s20f3: CTRL-EVENT-DSCP-POLICY clear_all
Feb 21 16:44:47 Office avahi-daemon[1335]: Withdrawing address record for fe80::127c:61ff:fe3f:16d7 on enp3s0.
Feb 21 16:44:47 Office avahi-daemon[1335]: Leaving mDNS multicast group on interface enp3s0.IPv6 with address fe80::127c:61ff:fe3f:16d7.
Feb 21 16:44:47 Office NetworkManager[1457]: [1740185087.4563] dhcp4 (enp3s0): canceled DHCP transaction
Feb 21 16:44:47 Office avahi-daemon[1335]: Interface enp3s0.IPv6 no longer relevant for mDNS.
Feb 21 16:44:47 Office NetworkManager[1457]: [1740185087.4563] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Feb 21 16:44:47 Office wpa_supplicant[1480]: wlp0s20f3: CTRL-EVENT-DSCP-POLICY clear_all
Feb 21 16:44:47 Office NetworkManager[1457]: [1740185087.4563] dhcp4 (enp3s0): state changed no lease
Feb 21 16:44:47 Office wpa_supplicant[1480]: nl80211: deinit ifname=wlp0s20f3 disabled_11b_rates=0
Feb 21 16:44:47 Office avahi-daemon[1335]: Withdrawing address record for 192.168.0.220 on enp3s0.
Feb 21 16:44:47 Office avahi-daemon[1335]: Leaving mDNS multicast group on interface enp3s0.IPv4 with address 192.168.0.220.
Feb 21 16:44:47 Office avahi-daemon[1335]: Interface enp3s0.IPv4 no longer relevant for mDNS.
Feb 21 16:44:47 Office systemd-resolved[1116]: enp3s0: Bus client reset search domain list.
Feb 21 16:44:47 Office systemd-resolved[1116]: enp3s0: Bus client set default route setting: no
Feb 21 16:44:47 Office systemd-resolved[1116]: enp3s0: Bus client reset DNS server list.
Feb 21 16:44:47 Office NetworkManager[1457]: [1740185087.4922] device (enp3s0): state change: disconnected → unmanaged (reason ‘sleeping’, sys-iface-state: ‘managed’)
Feb 21 16:44:47 Office systemd[1]: Reached target sleep.target - Sleep.
Feb 21 16:44:47 Office systemd[1]: Starting systemd-suspend.service - System Suspend…
Feb 21 16:44:47 Office systemd-sleep[7185]: Performing sleep operation ‘suspend’…
Feb 21 16:44:47 Office kernel: PM: suspend entry (deep)
Looks normal. I’m at a loss.
Where are you getting this kernel version?
Does booting into a different kernel version help?
What kernel version were you using in 22.04?
I downloaded the kernel from 9to5 Linux.
Booting into a different kernel version does not help.
In 22.04 I was using whatever kernel version was in the ISO I downloaded. I don’t remember what it was.
What hardware is this system?
What kind of graphics hardware does it have?
If this hardware contains NVIDIA graphics, what driver were you using for that in 22.04 and what driver(s) have you tried using for it in 24.04?
What is the reason you were seeking to use a newer kernel than is available in stock Ubuntu repositories?
What specific different kernel version did you try?
Homebrew, ASUS motherboard, Core-i9 cpu, 32mb system memory, 60g ssd.
The graphics hardware is on the motherboard, not Nvidia.
I went to the newer kernel when the stock Ubuntu kernel would not suspend.
I don’t remember the stock kernel version in 24.04.1.
Thank you for the details. When I’ve had issues that present like this, it ended up being firmware level issues in my case. Is there a firmware update available for your computer/motherboard that you could apply?
I discovered the problem. Disconnecting the keyboard enables suspend to work as it should. I need to check and see if there is some setting on the keyboard that will resolve the issue, otherwise I’ll have to replace the keyboard.
Update: I traced the problem to the Logitech G915 keyboard dongle. Suspend works fine until I insert the dongle into a USB port. It is not an Ubuntu issue after all, sorry for the fuss.
mike
This topic was automatically closed after 30 days. New replies are no longer allowed.