Hi Nicolas, I do not think it is so easy!
But let me go further into details. I am running plasma5 from Debian/stable, but also XFCE is installed as well as LXQT and some parts of GNOME. The GNOME parts are installed, because these are dependencies of some applications, which are GNOME related. Thus, I can not deinstall these. So far so well. Now to the weired things: In plasma (let me name it "KDE" further on) and in LXQT, none of the keys are working. I tried different keyboard setings, like "pc105" "nodeadkeys" as well as "DELL Latitude" "nodeadkeys". None of them is working. Otherwise in XFCE: Here the keys for screen brightness increase and decrease are working, but NOT "volume up" and "volume down". When in GNOME environment, then all keys are working, "volume up" and "down" as well as "screen brightness up" and "down". I am also running a livefile system from an USB-stick, it i KALI-Linux, which is debian based and the windowmanger in KALI is XFCE. Strange thing: In XFCE there all FN keys are working as they should - volume and brightness. Last thing: In console with no X11 started, the brightness keys are not working at all. Volume could not be tested. This is the actual state. When you say, this is a problem with the windowmanager, then maybe there is a conflict among XFCE, KDE, LXQT and GNOME. But the only way to abvoid this, might be to deinstall everything eslse but KDE. This is no good idea. Maybe I could try, to move some files away, like gconf or similar. GNOME is never used by me, but I often jump among KDE, LXQT and XFCE (as every windowmanager has its own advantages for special needs). The thing I am wondering is: Why is there no option in al windowmanagers just to use the default keyboard (default = the one configured in for console)? In XFCE it is using the standard keyboiard, in LXQT and KDE you can set from a menu (but not sure, if they will not use its own keymaps) and LXQT the same. But as I said: In console without X running, the FN keys are also not working! See, I believe it is not such easy! But no problem, it is not urgent. Best regards Hans > Then your problem is easy. If some keys did not generate events, getting > them to work might have been a nightmare or impossible. But since they > do, all you need to do is make sure there is a userland program running > that is listening for these events and acting on them. > > Traditionally, this has been the task of desktop environments. More > recently, systemd has taken over the handling of power-related buttons > and keys while leaving audio- and video- related keys to the desktop > environment. > > That means, by default, the power keys should work as soon as the system > starts booting but the audio and video keys should start working when a > desktop environment is running. > > If that is not happening or if you want the keys to be handled without a > desktop environment, you will need to explain the circumstances in more > details. > > Regards,
