You are not logged in.
So it's actually not the original issue - the key is received, it maybe just doesn't do what you expect it to do?
What did originally handle the key (xbindkey shortcut, acpid, …)?
if u mean key code that we used, It was `e073 192` on Ubuntu
Offline
No, I mean: what handles the key?
Apparently it is properly generated, so your "does not work" base is now that whatever should happen when this key is pressed does not happen.
Therfore the question which daemon is supposed to handle the key (and configured to do what with it).
Offline
No, I mean: what handles the key?
Apparently it is properly generated, so your "does not work" base is now that whatever should happen when this key is pressed does not happen.
Therfore the question which daemon is supposed to handle the key (and configured to do what with it).
Since there is no output on `acpi_listen` I guess it should be something else, how can I do some research about this?
Offline
If you didn't configure it, most likely your DE or networkmanaging service will handle the key.
Offline
If you didn't configure it, most likely your DE or networkmanaging service will handle the key.
Im using XDM as my Display Manager, XFCE as my Desktop Environment, Network-Manager as my network managing service,
How can I configure it?
Is there an article or something like that, that can help?
Offline
Offline
As a first step, I'd check whether there's a key even in xev. If there isn't the key might be grabbed. In this case, stop the NM service and alter your xinitrc to only "exec xterm" right after the inclusion of the system scripts (ie. avoid all custom stuff). See whether you now get an event in xev.
Offline
Ok, Im getting out of my mind, I booted Ubuntu live again to check something, Actually there is nothing by default for `e073` on Ubuntu, some module (ideapad_laptop) handles it I guess, I checked it up with `getkeycodes` and e073 has nothing set on,
Then I restarted to Arch, I saw something intresting, `ideapad_laptop: timeout in read_ec_cmd` in the boot log (TTY#1), and something else is with this message in log, Fn + F6 works well
Right now I just want to bang my head against the wall, I cant understand, Why sometimes it works, Sometimes it doesnt? without any change, it just happens
Offline
Why sometimes it works, Sometimes it doesnt?
https://bugzilla.redhat.com/show_bug.cgi?id=1331974 - sounds like a BIOS issue…
Offline
Why sometimes it works, Sometimes it doesnt?
https://bugzilla.redhat.com/show_bug.cgi?id=1331974 - sounds like a BIOS issue…
I also found this topic: https://forums.linuxmint.com/viewtopic.php?t=187410
Same laptop, Seems like the same issue
Offline
New update )
I found out what happens that makes FN + F6 doesn't work, I didn't find any reason, but now I can reproduce the problem every time I want
Everytime I boot my Windows to play Games, the key stops working on the next boot on Arch, I don't boot Windows using GRUB, I use Assist button to boot (It's a physical button next to power, it goes straight to the boot menu), Go too Boot Menu, and I choose the partition with Windows Boot Loader, I'm not sure if it is why I have the problem or not, but Everytime I boot the Windows, this happens
Also found how to fix the problem, Everytime this happens, I have to boot Ubuntu live once, the on the next boot to Arch, problem is gone
It's funny and still I can't understand Why!?
Last edited by DarkSun (2018-10-24 00:08:29)
Offline
Offline
I turned the fast startup off on my Windows, still got the problem
Last edited by DarkSun (2018-11-16 18:13:21)
Offline