Hi there, folks.
I’m new to Fedora, just setup a Fedora 40 KDE on my Zephyrus G14 (2023) recently, so far, the experiences seem nice. However, sometimes, I cannot shutdown or logout my machine using the UI in the menu, and I must shutdown using command line. Click the button simply do nothing at all, no notification,… As I look into the log, I notice each time I press that, it produces couples of something like this: hibernation is restricted; see man kernel_lockdown.7
which is pretty weird since I do not try to hibernate the machine. I don’t have the time to investigate more into it, but my best guess is some process try to block the feature, could be the im-chooser since I remember using that couple of times when I have the error.
Long story short, do you guy have situation when shutdown/logout button not working before, what might be the root cause for this?
A web search for this gets a number of hits with info.
I wonder if you have a swap file configured that is triggering this message.
What is the output of swapon?
There are claims that you can ignore the message is you are not trying to hibernate.
Apparently this is an related to secure boot.
You could try turning off secure boot and see if the login issue is fixed.
Then work on how to have logout and secure boot enabled.
Yeah I look at some of those as well, gonna try to look into it a bit more when I have time. And fyi, yes I do enable Secure Boot, more specifically I’m using an dualboot system with BitLocker + LUKS enabled, so it might has something to do with that. However, the problem is I’m not trying to hibernate/sleep, just try to shutdown or logout, even restart, but neither of them work, and the hibernatelog happens every time I try to press any of those button.
I can confirm that I am experiencing the same problem.
I am unable to perform a reboot, shutdown, or logout.
However, I can confirm that reboot and shutdown from the terminal are functional.
that bug was closed but i still experience it on a fully up-to-date (as of this morning) fedora 40 instance using the x11 version of plasma workspace (and plasma 6.1.1-1 in general).
The same goes for me, mostly with log out now, sometimes, even when shutdown/reboot work (I test it after test the log out in this case), the log out button still does nothing and produces hibernation is restricted; see man kernel_lockdown.7
Now that I really look into the bug, it might not be the same issue that I’m having, since I’m using Wayland, not X11 (I do have x11 installed, but the issue happens on Wayland)
I’m using the latest available kernel (currently 6.9.8, if I’m not mistaken), and I’ll verify that ASAP. However, the problem persists across multiple kernel versions, so I don’t believe it’s kernel-specific.
The error message I encounter is hibernation is restricted; see man kernel_lockdown.7, which might be related to my dual-boot setup with SecureBoot, LUKS, and even BitLocker on the Windows side.
The issue is difficult to replicate consistently. Sometimes I can shut down/log out my machine without problems, while other times the kernel_lockdown message appears and the shutdown/log out button doesn’t work.
I’ve noticed a pattern: if I boot my machine, log in, and do nothing (or wait a short while), I’m unlikely to encounter the error. However, if I use my machine for a while (performing multiple tasks like coding, web browsing, etc.), I’m more likely to face the problem when trying to shut down or even when logging out to try the new Cosmic DE
I’m curious if you’re seeing the same log entries as I am. Every time I press a button (such as the shutdown button), I use ksystemlog to monitor the journal, and I see specific messages appear. Are you experiencing something similar? If so, could you share what messages you’re seeing in your logs when you attempt to shut down or encounter this issue?
Hmm I see, If I understand correctly, you’re suggesting that the issue is related to Secure Boot rather than the dual-boot setup itself. However, I’m a bit confused about a few points:
If this is caused by Secure Boot, does it mean that LUKS is attempting to encrypt the swap partition each time I shut down or log out?
Would this explain why I don’t encounter the error when I boot up the machine and turn it off immediately? Is it because the swap hasn’t been utilized in that short period?
The puzzling part is that I’m using Fedora’s default zram configuration. I haven’t set up a separate swap partition or created any additional partitions for swap.
Given these circumstances, I’m curious about how this interaction between Secure Boot, LUKS, and swap is occurring on my system. Do you have any insights on how this might be happening without a dedicated swap partition?