Machine turns itself back on after shutdown (or sleep)

Hi folks,

I’ve been grappling with this issue for some time now, but I’ve found it intractable - which potentially shows I’m still pretty green, but well, I am. So, the issue:

  • After shutting down the machine (ostensibly successfully - lights go off, etc), and after an extended (but also not clearly regular) period, the machine turns itself back on.

  • There is a similar result when in sleep mode - it doesn’t go into hibernation as per power options, but gets stuck in the grub (password) screen.

  • (Straight) hibernation works well.

  • When booting the machine (other than in hibernation), the system invariably starts with a collection of programmes open which doesn’t match the previous session. There is some consistency in that it is usually the same set set of programmes (though not always - sometimes [not obvious when] there are variations); and even though I close some of them, they will return on the next boot. Peculiarly, while the session is killing all browsers other than Firefox, it keeps track of the open tabs (i.e. I may reboot and come back to a different set of open software, but the firefox tabs are intact).

The issue is the same on two machines which I configured (pretty much) identically. They are two (vanilla) laptops of different gen archs, so it strikes me as implausible this may be a hardware issue. What I suppose is relevant, beyond the fact I’m running tumbleweed, is that this is my first time using Btrfs (because, you know, when in Rome…); and that as I alluded to above, I encrypted the volumes using LUKS. Again, what I did was (ostensibly) pretty vanilla, and I didn’t deviate from the hand holding of the setup wizard.

Beyond that, I’ve been banging my head against this particular wall for some weeks now, but beyond getting some insight into Btrfs and the tradeoffs of encrypting the whole file system, and potentially accepting that this may be the reason for the machine to go sleep - stuck on grub awaiting password (though the why is not necessarily obvious to me, I’m afraid), I really have no clue what is going on. I suppose part of the issue is I have no idea as to what to even start looking for. So, either solutions (and, as I said, I am pretty green, so it wouldn’t amaze me this was an obvious problem…) or any tips as to how to start debugging would be much appreciated.

Hi, welcome to these forums

This looks like you’re running KDE’s Plasma desktop, where Plasma restores a saved session. Please confirm that you are running the Plasma desktop.

Re. the reboot/suspend issue: are you the one that posted on reddit? If so, you have already fixed it :smiley:

Thanks for the quick reply!

Ah, yes, sorry - using plasma desktop. Just had a quick look at those options (which I, erm, clearly knew existed), and they’re set for ending/restoring session. Even then, I shouldn’t be playing (and closing…) the same Mahjong game since January, should I?

I’m not that particular redditor (though, clearly, we are doppelgängers), but if he’s come upon a fix it’d be great if you could point me to the thread.

You may want to create a new user in Yast, log out from your current user, log in the new one and see if shutdown/sleep works. Then it would be some mis-configuration in your user’s settings.

Yeah, that’s not out of the realm of possibility. Thanks for the suggestion, I’ll give it a go.

Also, as a follow up to this, (Reddit - Dive into anything), but I’m afraid I can’t blame network boot - it’s been deactivated in bios for quite some time; and this wasn’t an issue anyway in any of the other distros I hopped through (or leap 42.3).