Fedora 43 installed here on Lenovo Thinkcentre M82.
My sytstem started exhibiting this behavior when I went into settings and set the power button to ‘Power Off’, from ‘Nothing’. Something is wrong with the coding of that option for my system, so that the system restarts instead of powering off. I’m speaking of this set of options:
My guess is there is an indexing issue going on between this gui and the linux behavior. When I set it to ‘Nothing’, initiating Power Off via the Fedora desktop, works fine. When set to ‘Power Off’, initiating a Fedora desktop power off via upper right corner, instead restarts the machine.
You posted in a Fedora 38 topic from 2023. You will get more attention if you start a new topic. Power switch handling requires cooperation between system firmware and the OS, so depends on your hardware and firmware.
Make sure you have current vendor updates. If that doesn’t fix the issue, post hardware details (install the inxi package and, in a terminal, run inxi -Fzxx. Post the output as pre-formatted web searchable text using the ‘</>` button from the top line of the text entry panel.
My apologies. I have been using Linux, and specifically Fedora, for only about a week. This is the first time I’ve ever heard of necro posting. One never knows the culture of a community. I googled and found a topic similar to the issue I have been experiencing, so I responded to it with my experience. I didn’t pay attention to how old the topic is. The risk to take is whether someone calls this out, or getting chastised with a “bro do you even google?” then links to an old thread where a topic has been beaten to death.
I take it that kind of behavior is not tolerated here.
Thanks - I’m such a newb I don’t even know how to “get vendor updates”. I’ve been using Linux and Fedora for perhaps a week, to give some life to a desktop computer MS says is unworthy of use for Win11. I have much to learn.
If you are using KDE Discover or Gnome Software Center, it should be automatic.
If not, or try it anyway, you can run
EDITED SEE BELOW
which is Firmware Update Manager.
If that yields no results, can you change the setting back?
There are also more complex ways to set what power buttons etc do from the command line. The function buttons are often buggy on Linux, as the vendors dont really participate as much as they should. Sometimes a kernel update will change their behaviour. However we should be able to get you back to your original settimg at least.
Appears the service was already available. I ran the refresh command and get a noticeWARNING: UEFI capsule updates not available or enabled in firmware setup.
I assume this is something I need to enable in the BIOS, correct?
Are you booting with UEFI or legacy BIOS?
To find out run cat /sys/firmware/efi/efivars. If that returns a message that it is a directory then you are using UEFI boot. If not then you are using legacy boot.
No, you should not need to enable use of fwupdmgr within bios. However, updates are probably not possible with fwupdmgr when using legacy boot.
There may be a bios update available for your system. If so then it probably would be wise to update the bios.
Be aware that updating the bios probably will require re-enrolling the signing key for the nvidia driver if you are using secure boot with nvidia drivers.
As the machine is now 12-13 years old, from what I can discern, there does not appear to be a Lenovo supported means to update the bios via Linux - the support page for the model only lists Windows tools for BIOS updates. Should have flashed it before I swapped hard drives I suppose! I still have the WIN10 HDD I can swap in to try to accomplish that.
It looks like you are using a older hardware. I get the same error. I searched today this message and it said that devices before 2015 miss this option.
Lenovo participates in the Linux Firmware Update project. Did you try installing the fwupd package and (in a terminal) running fwupdmgr get-devices? Look for a section called " System Firmware" and check the version against the Lenovo Support site. If there is a newer version, try running sudo fwupdmgr get-updates.
