I have bought the epomaker k870T keyboard and used it successfully these previous weeks under Ubuntu 20.04. The special function of the F keys, such as volume up/down on F12 and the rest never worked, but that didn't bother me, since they worked as simple F1-12 keys instead.
Today I tried to use my keyboard under Ubuntu, but it needed to be re-paired for some reason. After pairing it, it switched the entire keyboard identification to that of MAC. This means that my F keys are all special functions only, and altering them via the Fn key will only activate their Windows special function counterpart (the keyboard supports both OSes with different methods on them).
I suspect the issue occurred due to an automatic update of Ubuntu packages last week (which probably only took effect after a restart on the weekend), since last week everything worked up to Friday (the keyboard has not been used after that). My last package updates happened on Thursday and states the following package updates:
Start-Date: 2022-02-24 11:27:07
Commandline: aptdaemon role='role-commit-packages' sender=':1.525'
Upgrade:
libsasl2-modules-db:amd64 (2.1.27+dfsg-2, 2.1.27+dfsg-2ubuntu0.1),
snapd:amd64 (2.54.3+20.04.1ubuntu0.1, 2.54.3+20.04.1ubuntu0.2),
libsasl2-2:amd64 (2.1.27+dfsg-2, 2.1.27+dfsg-2ubuntu0.1),
language-pack-en:amd64 (1:20.04+20210802, 1:20.04+20220211),
ubuntu-drivers-common:amd64 (1:0.9.0~0.20.04.4, 1:0.9.0~0.20.04.5),
python3-distupgrade:amd64 (1:20.04.36, 1:20.04.37),
libsasl2-modules:amd64 (2.1.27+dfsg-2, 2.1.27+dfsg-2ubuntu0.1),
ubuntu-release-upgrader-core:amd64 (1:20.04.36, 1:20.04.37),
language-pack-en-base:amd64 (1:20.04+20210802, 1:20.04+20220211),
ubuntu-release-upgrader-gtk:amd64 (1:20.04.36, 1:20.04.37),
base-files:amd64 (11ubuntu5.4, 11ubuntu5.5),
teamviewer:amd64 (15.26.4, 15.27.3)
Remove: linux-oem-5.13-headers-5.13.0-1028:amd64 (5.13.0-1028.35),
linux-headers-5.13.0-1028-oem:amd64 (5.13.0-1028.35),
linux-image-5.13.0-1028-oem:amd64 (5.13.0-1028.35),
linux-modules-5.13.0-1028-oem:amd64 (5.13.0-1028.35)
End-Date: 2022-02-24 11:27:45
Is there any upgrade in this list that could have triggered this mis-identification of the OS as MAC by the keyboard?
Can I manually force the keyboard to accept my OS as Windows perhaps or do I need to roll back one of these packages?