On 9/23/25 3:08 PM, Joe Average wrote:
Samuel Sieb wrote:
...
More details?
What's happening?
Logs?
booted was last F43 Kernel (6.17.0-0.rc7.56.fc43.x86_64)
on an command line I do: sudo systemctl suspend
box goes done, case lights are out for ~1 sec , but box wakes up immedialy.
Suspending messes with the logs, but it looks like the suspend/resume
part is taking about 8 secs.
Sep 23 23:41:01 obelix.fritz.box kernel: Filesystems sync: 0.013 seconds
Sep 23 23:41:09 obelix.fritz.box kernel: Freezing user space processes
I don't see any failure to suspend, so it looks like it's suspending,
but something in the hardware is triggering it back on.
Can you try suspending it remotely from another computer? Or try the
methods I mention below.
initial boot is without errors.
so here is only the "sudo journalctl -b0"-part since I triggert "sudo systemctl
suspend":
Why are you doing it that way? Your user should be able to run it, but
also why not use the gui or shortcut key or even the power button to
trigger the suspend?
--
_______________________________________________
test mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
