Yes, did a secondary click copy and paste just now, then added a sudo and same, with result:
Ultra-Series-1:~$ sudo gsettings set org.gnome.settings-daemon.plugins.power power-button-action ‘interactive’
[sudo: authenticate] Password:
The provided value is outside of the valid range
The apt update command is also recommended by Linux group guys. Is it different than going into System Settings and doing Software Update?
Thanks for the sleep clarifications, I had no idea there are multiple levels…
While doing all this, a Notification came on the screen:
which is quite possibly not related to this Topic but gives this newb the chills. I mean, my general inclination is to ignore as dodgy a notification from an “unknown app”, esp when it refers to something important like UEFI (has something to do with secure booting is all I know) and has initials ‘dbx’. I can understand abbreviations for Terminal but for a notification, couldn’t they spell it out to make it sound less scary… Hm. Should I post that as a new topic or will I get shamed for showing ignorance?
It is slightly because it allows you to see what’s available for update before you update it and you get to decide if you want to upgrade it. This is technically the equivalent of it (which I suggest you do update one way or the other before the firmware update):
sudo apt full-upgrade
I hear you and I would agree. I don’t think you’ll get shamed but at the same time I cannot predict what the response will be. UEFI dbx update will be updating the Secure Boot block list stored in your computer’s firmware. db is for safe signatures and dbx is for updating unsafe signatures. The unknown app seems a bit sketchy. Try to see what app is trying to install this but don’t install it from them. I would update it directly by using the following:
fwupdmgr get-updates
So according to ChatGPT, this has curly quotes instead of single quotes for some reason (the fact that there is a difference seems dumb to me). If you have TextEditor, paste it in there as plain text (just make sure the quotes are not slanted) before copying and pasting it to the terminal. Hopefully that will prevent the curly quotes. Otherwise I have no clue. It’s listed as an option so it should work.
Thanks for the additional research. I typed it in Terminal letter by letter, proofread twice, gave the password and got a different failure notice.
Typed again, confirming again that every letter and space was correct, and used the single quote mark on the keyboard instead of pasting, with again the result:
(process:10812): dconf-WARNING **: 19:42:28.040: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)
Ah well. I guess I’ve troubled you enough with this, I very much appreciate your patience and effort. If I find a solution before the topic is closed, I’ll post an update. For now it’s over my head and I back to the OP for now I’ll get in the habit of shutting down more often and verifying charging on the LED and so on. If anything that seems to me out of the ordinary occurs I’ll shut down. Plenty of things here in the Linux and maybe Windows world take two steps instead of the one I’m used to from Mac so I’ll be more alert to that kind of thing.
Many Thanks!
