I've been unable to suspend my computer for a week or two now. I believe the issue started after a Friday sync, but I'm unsure which. Running $ sudo systemctl --failed shows the following output:
UNIT LOAD ACTIVE SUB DESCRIPTION
● nvidia-powerd.service loaded failed failed nvidia-powerd service
● systemd-suspend.service loaded failed failed System Suspend
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
2 loaded units listed.
$ sudo systemctl status systemd-suspend
× systemd-suspend.service - System Suspend
Loaded: loaded (/usr/lib/systemd/system/systemd-suspend.service; static)
Drop-In: /usr/lib64/systemd/system/service.d
└─10-timeout-abort.conf
Active: failed (Result: exit-code) since Fri 2023-08-18 18:29:17 CDT; 18h ago
Docs: man:systemd-suspend.service(8)
Main PID: 54401 (code=exited, status=1/FAILURE)
CPU: 1.536s
Aug 18 18:29:05 solus-blase systemd-sleep[54405]: Failed to connect to non-global ctrl_ifname: (nil) error: No such file or directory
Aug 18 18:29:05 solus-blase (sd-executor)[54402]: /usr/lib64/systemd/system-sleep/wpa_supplicant.sh failed with exit status 255.
Aug 18 18:29:05 solus-blase systemd-sleep[54401]: Entering sleep state 'suspend'...
Aug 18 18:29:15 solus-blase systemd-sleep[54401]: Failed to put system to sleep. System resumed again: Device or resource busy
Aug 18 18:29:15 solus-blase (sd-executor)[54419]: /usr/lib64/systemd/system-sleep/wpa_supplicant.sh failed with exit status 255.
Aug 18 18:29:15 solus-blase systemd-sleep[54423]: Failed to connect to non-global ctrl_ifname: (nil) error: No such file or directory
Aug 18 18:29:17 solus-blase systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
Aug 18 18:29:17 solus-blase systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
Aug 18 18:29:17 solus-blase systemd[1]: Failed to start System Suspend.
Aug 18 18:29:17 solus-blase systemd[1]: systemd-suspend.service: Consumed 1.536s CPU time.
Unsure if it's related but $ sudo systemctl status nvidia-powerd.service
× nvidia-powerd.service - nvidia-powerd service
Loaded: loaded (/usr/lib/systemd/system/nvidia-powerd.service; disabled; preset: enabled)
Drop-In: /usr/lib64/systemd/system/service.d
└─10-timeout-abort.conf
Active: failed (Result: exit-code) since Thu 2023-08-17 16:59:52 CDT; 1 day 19h ago
Main PID: 947 (code=exited, status=1/FAILURE)
CPU: 3ms
Aug 17 16:59:51 solus-blase systemd[1]: Starting nvidia-powerd service...
Aug 17 16:59:51 solus-blase /usr/bin/nvidia-powerd[947]: nvidia-powerd version:1.0(build 1)
Aug 17 16:59:52 solus-blase /usr/bin/nvidia-powerd[947]: No matching GPU found
Aug 17 16:59:52 solus-blase /usr/bin/nvidia-powerd[947]: Failed to initialize RM Client
Aug 17 16:59:52 solus-blase systemd[1]: nvidia-powerd.service: Main process exited, code=exited, status=1/FAILURE
Aug 17 16:59:52 solus-blase systemd[1]: nvidia-powerd.service: Failed with result 'exit-code'.
Aug 17 16:59:52 solus-blase systemd[1]: Failed to start nvidia-powerd service.
(From my understanding 'nvidia-powerd.service' is incompatible with AMD CPUs and it's safe to just disable it?)
I haven't had much luck searching for solutions to this issue. Found this Reddit post relating to Solus, but no solution. Found a few other posts relating to Raspberry Pis and Ubuntu, but wasn't sure how to apply any of that to my situation.
Any help would be appreciated, thanks!
