Just to try to rule things outâŚdo you see that behavior on a Live USB of Fedora 37? Or a Live USB of any other OS?
On your keyboard, is there a hardware-set combination that is related - like, is Fn+Up Arrow intended to control volume? (Thinking like a stuck key that might have happened by coincidence?)
I might not have explained what I meant by that - does your keyboard look like this, where some keys have additional functions mapped to them that can be accessed by holding the Fn key (usually next to Ctrl in the bottom-left corner) and pressing that key?
(image taken from a Brave Image Search for âacer aspire keyboard layoutâ)
If so, itâs theoretically possible that something in software is causing your PC to act like Fn is always being held down, but something physical with the keyboard is a very likely cause of this kind of issue, so itâs worth making sure that the Fn key / any of the other keys arenât stuck or obstructed in any way.
If itâs not, it may be worth looking at some of the responses to this thread to see different options for key combinations that may help reset the Fn keyâs status?
And for what itâs worth, the things Iâm talking about here arenât even related to keyboard shortcuts like what youâd see listed in the GNOME Settings app, as these arenât seen by the PC as key âcombinationsâ but as key inputs of their own - like thereâs a âbrightness upâ key as far as the PC is concerned, for example.
Hope that helps! As @grumpey said, using the inxi script (might need installed via sudo dnf install inxi) and posting the results as Preformatted text (for legibility) would be helpful in any further troubleshooting.
You may not believe that the issue disappeared. I do not know what happened internally.
Maybe you are right @johnandmegh. The Fn key was stucked. Because before checking sudo showkey
I have a funny story related to this (I have a laptop too) - a couple of months ago I could not figure out why a game I was playing (Hades) was running at a very low framerate - like the Nvidia GPU wasnât getting used (this was on Pop!_OS, which has âhybrid modeâ and âdedicated graphics modeâ).
I went through all the different ways I could think of to trigger the game to use the Nvidia GPU - setting the OS to dedicated mode, adding elements to the .desktop file, reinstalling via Steam, and I just could not figure it out. I put together an extensive post for Reddit with all the steps I had taken, my system info, etc.
Right after I submitted that post, I noticed something looked different on the end of the top bar in GNOMEâŚit was the power icon. The place where the power cord from the laptop itself plugs into the brick (which on my model, then separately goes to the wall) had come apart, so even though I looked at the laptop itself and saw it plugged in, and looked at the wall outlet and saw it plugged inâŚit wasnât actually plugged in! As a result, it was using âpower saverâ mode on battery. Connecting that cord back together fixed the problem!
The reason I mention this story isâŚsometimes all visual indications would be that a component is working and isnât the cause of a problem, but thereâs something thatâs harder to see that still relates to that component and you just need some help looking for it. Hopefully it stays working for you!
If you find that you have some other sticky key issues, the first few seconds of this video may be helpful in seeing how to pop a key off of that keyboard and clean underneath (although I personally get nervous using metal tools for such things - Iâve had better luck with a guitar pick, myself!):
