On Mon, Aug 9, 2021 at 10:53 AM George Avrunin <avru...@math.umass.edu> wrote: > > Aug 06 17:47:32 ext.math.umass.edu kernel: Lockdown: systemd-logind: > hibernation is restricted; see man kernel_lockdown.7 > Aug 06 17:47:32 ext.math.umass.edu kernel: Lockdown: systemd-logind: > hibernation is restricted; see man kernel_lockdown.7 > Aug 06 17:47:32 ext.math.umass.edu NetworkManager[2111]: <info> > [1628286452.1872] manager: sleep: sleep requested (sleeping: no enabled: yes) > Aug 06 17:47:32 ext.math.umass.edu NetworkManager[2111]: <info>
Yeah I have a bit of a gripe with systemd that it doesn't, by default, insert the sleep request in the log. What exactly requested it? User hit the power button? User closed the lid? Some service like apcuspd requested it? I dunno, seems like an obvious thing that needs to go in the log, one line. And for NetworkManager to be the first indication that S3 or s2idle was requested is not helpful at all, I see this too in cases when I close the lid or the GNOME Shell power save timeout is reached (screen dim or whatever it's called). I don't know all the different ways sleep can be requested but we need the logs to indicate where this request is coming from. I don't know for sure but maybe you can boot with systemd.log_level=debug and get more detail, probably way too much detail because it's very verbose. But I'm not sure how to narrow it down. But either way, I think it's worth a thread on systemd-devel@ and ask if a single line of info about sleep being initiated can be dumped into the log by default? -- Chris Murphy _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
