You are not logged in.
I am using Arch Linux with KDE on my Asus Vivobook 16 (X1605VAB-MB541WS). But everytime I press the Caps Lock or Print Screen key, the Brightness Decrease Key (Fn + F4) gets pressed. I tried running xev to examine the situation but it registered Caps lock and Print Screen as XF86MonBrightnessDown. I dual boot Windows 11 and this issue doesn't happen on Windows. Any help would be highly appreciated.
Last edited by lavish_jaat (2023-08-13 16:12:08)
Offline
I have the exact same issue on my Asus Zenbook S 13 (UX5304VA_UX5304VA). I didn't find this issue mentioned anywhere else online. I hope someone knowledgeable can help with that.
Offline
No one has replied to this issues since months.
Offline
I am facing same on UX5304VA. I am still debugging this problem, and also looking for help if anyone has
Offline
I have the exact same issue on my Asus Zenbook S 13 (UX5304VA_UX5304VA). I didn't find this issue mentioned anywhere else online. I hope someone knowledgeable can help with that.
Did you update your BIOS?
Offline
GalGR wrote:I have the exact same issue on my Asus Zenbook S 13 (UX5304VA_UX5304VA). I didn't find this issue mentioned anywhere else online. I hope someone knowledgeable can help with that.
Did you update your BIOS?
Yes I did but this problem isn't related to BIOS as it doesn't happen on Windows.
Offline
donjajo wrote:GalGR wrote:I have the exact same issue on my Asus Zenbook S 13 (UX5304VA_UX5304VA). I didn't find this issue mentioned anywhere else online. I hope someone knowledgeable can help with that.
Did you update your BIOS?
Yes I did but this problem isn't related to BIOS as it doesn't happen on Windows.
Sure, it works okay on Windows.
I asked because I wasn't sure I had this problem before I updated my BIOS. Now I can't downgrade to confirm.
Offline
I have an on-going ticket for a fix in the driver. In the meantime, do this to fix the annoying Caps lock
Offline
Hi All,
Upstream kernel drivers/platform/x86 subsys maintainer here.
I have an on-going ticket for a fix in the driver. In the meantime, do this to fix the annoying Caps lock
Thanks for also relaying this to this thread.
In the mean time a better fix for this has been queued up and will be send to Linus this Friday, after which it will hopefully get added to the 6.5.y stable kernels soon:
See: https://git.kernel.org/pub/scm/linux/ke … g/?h=fixes and then specifically the 3 asus-wmi patches queued in that branch.
Regards,
Hans
Offline
I am also facing this issue in Asus Vivobook 16 X1605VA. On top of this my single media key press is acting as a double key press. For example single "brighteness up" press would increase brightness twice. Mute key press would mute the audio then unmute on single press. Anyone else facing the issue? Any temporary solution?
Last edited by rajeevrdev (2023-10-23 15:18:37)
Offline
@hansdegoede highlighted this issue for me as well. But for some unknown reason mine doesn't get processed twice on the desktop. I think KDE filters duplicate events out. Which desktop are you on?
If you can run "sudo evtest", select Asus wmi and press the brightness up and unmute button, and share the output.
I am also facing this issue in Asus Vivobook 16 X1605VAB-MB541WS. On top of this my single media key press is acting as a double key press. For example single "brighteness up" press would increase brightness twice. Mute key press would mute the audio then unmute on single press. Anyone else facing the issue? Any temporary solution?
Last edited by donjajo (2023-10-23 15:20:56)
Offline
I am on Asus Vivobook 16 laptop on Linux Mint Cinnamon. Linux kernel 6.2.
"sudo evtest" on Mute key
Event: time 1698076402.375749, type 4 (EV_MSC), code 4 (MSC_SCAN), value 32
Event: time 1698076402.375749, type 1 (EV_KEY), code 113 (KEY_MUTE), value 1
Event: time 1698076402.375749, -------------- SYN_REPORT ------------
Event: time 1698076402.375762, type 1 (EV_KEY), code 113 (KEY_MUTE), value 0
Event: time 1698076402.375762, -------------- SYN_REPORT ------------
"sudo evtest" on Brightness Up key
Event: time 1698076460.052216, type 4 (EV_MSC), code 4 (MSC_SCAN), value 2f
Event: time 1698076460.052216, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 1
Event: time 1698076460.052216, -------------- SYN_REPORT ------------
Event: time 1698076460.052233, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 0
Event: time 1698076460.052233, -------------- SYN_REPORT ------------
This doubling pretty much affect all media keys that are working
Offline
This doubling pretty much affect all media keys that are working
Doubling? Those events are showing key down and key up. Look at the value parameter.
BTW, I do not see this phenomena on my Asus Vivobook K712EA
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
rajeevrdev wrote:This doubling pretty much affect all media keys that are working
Doubling? Those events are showing key down and key up. Look at the value parameter.
BTW, I do not see this phenomena on my Asus Vivobook K712EA
I am quoting Hans here from our previous conversion related to this bug (https://www.spinics.net/lists/kernel/msg4976255.html) . I thought same initially.
The 1 / 0 events are indeed press / release events that is
not the problem, the problem is that a single keypress reports
these events on 2 different /dev/input/event# nodes.
Are you on KDE?
Offline
Are you on KDE?
Sway on Wayland.
Are you on KDE on Wayland or Xorg?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Are you on KDE on Wayland or Xorg?
KDE on Wayland
Offline
The 1 / 0 events are indeed press / release events that is not the problem, the problem is that a single keypress reports these events on 2 different /dev/input/event# nodes.
Post #12 doesn't give that away.
What are those input devices?
Are you fine w/ simply deactivating one?
W/o X11 and the most brute-force way is to "evtest --grab" the device away.
Offline
The 1 / 0 events are indeed press / release events that is not the problem, the problem is that a single keypress reports these events on 2 different /dev/input/event# nodes.
Post #12 doesn't give that away.
What are those input devices?
Are you fine w/ simply deactivating one?
W/o X11 and the most brute-force way is to "evtest --grab" the device away.
My brightness key event is still captured by 2 input devices: Asus WMI hotkeys and Video Bus
Offline
Hence the plan t ograb one of those (eg. the video bus one) away so that it doesn't get to the rest of the system.
(For maybe clarification: I didn't mean "does the event show up in "evtest --grab", I meant to run "evtest --grab eventX" in the background to mute that device)
Offline
Hence the plan t ograb one of those (eg. the video bus one) away so that it doesn't get to the rest of the system.
(For maybe clarification: I didn't mean "does the event show up in "evtest --grab", I meant to run "evtest --grab eventX" in the background to mute that device)
I guess Video Bus has some other important events it captures?
Offline
Don't guess. Try.
Grab the device and see whether there're issues w/ that.
Offline
The brightness double keypress reporting should be fixed by this patch:
https://lore.kernel.org/platform-driver … edhat.com/
As for the patches fixing the spurious brightness down keypresses those have been queued up for merging into the next 6.5.y release, see:
https://git.kernel.org/pub/scm/linux/ke … inux-6.5.y
Offline
I tried reproducing the issue today. I think the Capslock and Print Screen key issue has been fixed.
The only issue now is that pressing Audio Up and Audio Down key is registered as two keypress instead of one.
Kernel: 6.5.9-arch2-1
DE - KDE Wayland
Last edited by lavish_jaat (2023-10-27 20:44:58)
Offline
@lavish_jaat
You wrote: "Audio Up and Audio Down key is registered as two keypress" do you really mean audio up/down or do you mean brightness up/down key-presses ?
Offline
@lavish_jaat
You wrote: "Audio Up and Audio Down key is registered as two keypress" do you really mean audio up/down or do you mean brightness up/down key-presses ?
I mean Audio Up and Audio Down. I never had any issues with Brightness Up or Brightness Down key.
Offline