New laptop. All of the power manager features relating to suspend/hibernate are disabled. All of the systemd services relating to suspend and hibernate are inactive. Despite this, the system shuts down, but does not power off. When boot I get the login screen. Repeatable on the two latest kernels. selinux disabled. Fedora 37 up to date. Before I beat up on the vendor, any suggestions?

On 15 Jan 2023, at 21:55, Geoffrey Leach <geoffleach.gl(a)gmail.com&gt; wrote: On Sun, 15 Jan 2023 13:25:53 -0700 stan via users <users(a)lists.fedoraproject.org&gt; wrote: >> On Sun, 15 Jan 2023 07:47:42 -0800 >> Geoffrey Leach <geoffleach.gl(a)gmail.com&gt; wrote: >> >> New laptop. All of the power manager features relating to >> suspend/hibernate are disabled. All of the systemd services relating >> to suspend and hibernate are inactive. >> >> Despite this, the system shuts down, but does not power off. When >> boot I get the login screen. >> >> Repeatable on the two latest kernels. selinux disabled. Fedora 37 up >> to date. >> >> Before I beat up on the vendor, any suggestions? > > If you shutdown from a console Ctl-Alt-(f3-f6), is the last message > you see something about power down? A recent thread informed me that > the console F keys are no longer fixed, so you might have to try > different F keys to get a virtual console. The command is > shutdown -P now > as root or sudo, to shutdown with power off. Thanks for the reply. I am embarrassed to admit it, but I have no idea how to get a console. That said, I think you have misinterpreted my problem. It's not that I can't hibernate, its that I'm getting hibernation when I don't ask for it. FWIW, my current theory is that my shiny new laptop is overheating.

_______________________________________________ users mailing list -- users(a)lists.fedoraproject.org To unsubscribe send an email to users-leave(a)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, report it: https://pagure.io/fedora-infrastructure/new_issue

On Sun, 15 Jan 2023 13:25:53 -0700 stan via users <users(a)lists.fedoraproject.org&gt; wrote: > If you shutdown from a console Ctl-Alt-(f3-f6), is the last message > you see something about power down? A recent thread informed me > that the console F keys are no longer fixed, so you might have to > try different F keys to get a virtual console. The command is > shutdown -P now > as root or sudo, to shutdown with power off. Thanks for the reply. I am embarrassed to admit it, but I have no idea how to get a console.

That said, I think you have misinterpreted my problem. It's not that I can't hibernate, its that I'm getting hibernation when I don't ask for it.

I have figured out that my problem has nothing to do with hibernate. Sorry for the confusion.

On Mon, 16 Jan 2023 11:47:10 -0700 Joe Zeff <joe(a)zeff.us&gt; wrote: > On 01/16/2023 11:33 AM, Geoffrey Leach wrote: > > I have figured out that my problem has nothing to do with > > hibernate. > > Sorry for the confusion. > > That's OK, much of troubleshooting is going down one blind alley > after another until one of them isn't.  Now, how about telling us > what turned out to be causing this so that we don't have to > reinvent > this specific wheel if/when we get caught by this? keyboard dies, followed mostly by screen blanking. No idea as to cause..

On Mon, Jan 16, 2023 at 5:26 PM Patrick O'Callaghan <pocallaghan(a)gmail.com&gt; wrote: > On Mon, 2023-01-16 at 12:22 -0800, Geoffrey Leach wrote: > > On Mon, 16 Jan 2023 11:47:10 -0700 > > Joe Zeff <joe(a)zeff.us&gt; wrote: > > > > > On 01/16/2023 11:33 AM, Geoffrey Leach wrote: > > > > I have figured out that my problem has nothing to do with > > > > hibernate. > > > > Sorry for the confusion. > > > > > > That's OK, much of troubleshooting is going down one blind > > > alley > > > after another until one of them isn't.  Now, how about telling > > > us > > > what turned out to be causing this so that we don't have to > > > reinvent > > > this specific wheel if/when we get caught by this? > > > > keyboard dies, followed mostly by screen blanking. No idea as to > > cause.. > > This may be a complete red herring, but since getting a new keboard > I've had a couple of occasions where waking my desktop from > hibernation > doesn't restore the screen, even though the system appears to be > working (I've checked via a remote login). The kb is a Logitech > wireless model, and it works correctly nearly all the time (over > 95%) > except when it doesn't. This is on X11 if it matters. Next time it > happens I'll try to remember to turn the kb off and on again to see > what happens. > This is probably not your issue, but I know there is a bug (that I have never reported) where if you hit a key at the exact instant that screen blanking starts, then the screen will never unblank. And like your symptom, the system is still working correctly. My guess is that there is a race condition like: - the blanking timer expires - the screen blanks                                          - a keystroke is processed,                                          - get a copy of the 'screen is blanked' flag - set the 'screen is blanked' flag                                          - clear 'screen is blanked' flag                                          - test 'screen is blanked' COPY if set unblank the screen That may not be the case, but that's what I've seen. I also have a dimming configured and I've seen a similar case of when I hit a key at the exact instant that the screen dims, then my screen is permanently in dim mode and keystrokes can't wake it.

On further reflection I'm more than half convinced that the problem has nothing to do with the keyboard. One detail I omitted to mention is that my display is connected via a HDMI switch, and when the system comes back after hibernation it's always set to the wrong port and I have to press a button to get the right one. It seems likely that this is the source of the problem i.e. a race between the system activating the display and me pressing the button at exactly the wrong moment.