Possible Issue: Keyboard function keys get triggered and makes other keys not work(Read Description)

[Bluey26]

Expected Behavior

Nothing here.

Current Behavior

I am not sure if this is caused by LXQt and i think this this could be related to openbox, i open this issue here because i still have this problem after a few years using LXQt.

From time to time i have the following issue:

My laptop has Fn (Function) keys, which allows me to increase/decrease volume and screen light, and also mute/unmute volume, between other functions.

Since i remember, i have had, in different Linux distributions (Lubuntu and Archlinux, i dont recall about Debian) this issue:

When i increase or decrease volume, they key combination seems to be 'clogged' or switch to being constantly pressed. During this issue, the other keyboard keys become unusable. For example: if i was increasing volume, from 10% to 13%, the volume keeps increasing until it reach 100% (shown thanks to lxqt volume notifications) and it keeps increasing (100 is the limit). In the other hand, if i have the volume at 50% and i want to decrease the volume and this happens, volume goes to 0% instead of the desired %. Mute goes mute/unmute contantly, also shown by lxqt notification system.

I find this issue a bit hard to explain, it does not happen to me always, and i have no way to reproduce it.

I suspect this being a openbox (or Xorg?) problem , and i only can add that this looked to no happen to me when i used the lxqt-labwc-session package some time ago (When i launched the lxqt-labwc session with its panel module).

Possible Solution

Steps to Reproduce (for bugs)

I do not know.

Context

Explained in current behavior

System Information

• Distribution & Version: Archlinux

• Kernel: 6.8.2-arch2-1

• Qt Version: 5.15.13

• liblxqt Version: liblxqt 1.4.0

• lxqt-build-tools: lxqt-build-tools-qt6-git 0.13.0.3.g880656b-1 and lxqt-build-tools 0.13.0-1

• Package version: lxqt-config 1.4.0-2

As i stated, this does not seem to be anything related to this current or newer versions, this happens to be since +4 years that i have been using LXQt.

I can provide more information, i didnt know what could be useful in this case.

---

PS: they way i have to 'workaround' this and being able to make the keyboard work again is to press several times the exact same keyboard combination. Sometimes it works at 1st triggering of the combinations, other times i have to press it several times.

[tsujan]

I haven't encountered an issue like that, but if you think it may be related to Openbox (which I neither use nor recommend), why not testing with another WM under X11?

[Bluey26]

That is a good idea, which i did not take in account.

As i was suggested, i will try (before using kwin or xfwm WMs) to use openbox without <keyboard>.......</keyboard> lines inside rc.xml to discard possible issues in the automatic opnbox key configuration. If that does not help, i will move into another WM for a few days and see what happens with the function keys issue.

[Bluey26]

An update into this: After 1 week using openbox without the keyboard section, the keyboard issue still persists.

I will test what happens in kwin from now. I also just noticed that the lxqt-config-monitor coredump i mentioned in the other issue is vanished (maybe it was an issue with openbox, because there is no coredump on startup with kwin_x11).

One thing i forgot to mention is that this keyboard issue could be caused by some hardware defect or bug, although this was not an issue back in Windows as far as i remember.

I will update next week to see if i find something relevant.

[tsujan]

this could be caused by some hardware defect

Not impossible, but such problems are usually caused by software.

Anyway, LXQt 2.0.0 will be released soon, based on Qt6.