I’d be happy to help. I’m going to replicate your issue today on my own 11th gen.
While I get this set up, I do have some questions for you so I can best emulate what you’re experiencing. If any of these questions seem silly, are something you’ve already tried, please bear with me.
You indicated this happened on an upgrade from 22.04 to 22.10. So it is safe to assume these keys worked fine in 22.04?
Did you do any BIOS upgrades right before or right after upgrading to Ubuntu 22.10?
Do you have any power management tools installed like TLP or a custom Powertop configuration in use?
While I wait for a reply on this, I will work to replicate what you’re experiencing on my own computer.
I have live booted to Ubuntu 22.10 on X11 on my 11th gen Framework.
Testing actual key recognition (sensing presses themselves).
sudo showkey -k
I’m registering results for each key press holding Fn and pressing F1 through F12. So we’re seeing key presses. Please try this as well and see what you’re seeing.
Next let’s try the media keys. Still on the live install of Ubuntu 22.10:
Download a short wav file, opened it with the “Videos” application. Placed it on a loop so I could fully test the media keys.
Play, pause, << and >> all worked perfectly with the WAV file.
So this leads me to wonder if something went sideways with the upgrade process. Myself personally, I always prefer a home backup and a fresh installation for just such instances.
Please try this on your own system if possible, with a live USB of Ubuntu 22.10 and see if you see the same results.
You indicated this happened on an upgrade from 22.04 to 22.10. So it is safe to assume these keys worked fine in 22.04?
Yep! Worked like a charm.
Did you do any BIOS upgrades right before or right after upgrading to Ubuntu 22.10?
I did update the BIOS to 784 about a month ago, but this did not affect the Fn key or media keys.
Do you have any power management tools installed like TLP or a custom Powertop configuration in use?
Nope.
Using showkey -k, no code registeres when I press the Fn key alone. Pressing the Fn key with any other key produces the same keycode as the key alone. Also, I cannot activate the keyboard backlight using Fn+[space]. On other laptops I’ve owned, that was a hardware thing, but the Framework may be different.
@Matt_Hartley I figured it out! It was locales, of all things. Somehow during the upgrade, the locales got purged and were not regenerated. dpkg-reconfigure locales and a reboot solved the problem.
The fact that Fn+space wouldn’t adjust the backlight had me so convinced it was a kernel/hardware thing I didn’t even consider the keyboard language as a source of trouble.
It is possible. The Fn key has gone out to lunch twice since I posted this, but functioned again after a reboot. I thought before the locales issue the bug was persisting across reboots, but it could simply have been triggered twice.
I have experienced the same problem a couple of times. It is not frequent enough to be really a big deal. In my experience too, if it occurs, in my case, a reboot solves it.
11th or 12th gen? Is this a new issue or was it an issue on day one with 22.10 for you?
Which F keys are not doing what specifically?
If you’re on 12th gen, applied the Grub parameter, functions not using the Fn key will work such as brightness, airplane mode, etc. If however, you’re talking about using Fn + F1 through F12, what is the result desired and keys pressed in this case?
This now also happened to me a few times, several days between the occurrences with multiple daily suspend/resume cycles but no full reboot… suddenly the Fn Key stopped working, no PgUp/PgDn/Home/End/Functions Keys like mute/volume/… work anymore showkey didn’t show a keypress when pressing Fn key and when pressing e.g. Fn+F1 showed the same code as when only pressing just F1 … after reboot it still doesnt show a keypress for the Fn key, but Fn+F1 and just F1 show different keycode … same for others … so it seems the Fn key for some reason does not register anymore … also e.g. Fn+Esc does not toggle Fn Lock in this state… i cannot say how to reproduce it, only that rebooting seems to solve it … If you’d like further information next time it happens, i’d be happy to provide those
I have the same issue. It the function keys like prinscrn, F5 etc. seem to stop working after some time. A reboot solves the issue for me, but I dont know if this is a random linux problem or a framework problem. Is there any way to find out?
@Caspar_Gutsche I don’t think that any Windows user has reported this problem, so it looks like it is a problem on Linux only. I’d say it is also specific to Framework users, so it has to do with how the Linux firmware layer is bridging the software with the hardware…
I will try it out (actually in the linked info a user suggested to in addition to blacklisting, he just rmmod ed the module without rebooting… I am trying that right now…) let’s see if it helps
