https://bugzilla.novell.com/show_bug.cgi?id=786242
https://bugzilla.novell.com/show_bug.cgi?id=786242#c9
Stanislav Brabec changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
InfoProvider| |morfeokmg@gmail.com
--- Comment #9 from Stanislav Brabec 2012-11-09 19:46:39 CET ---
Thanks.
It is not an X issue. It is something between kernel, hardware and its helper
scripts. Kernel sends volume codes after resume.
---
Only event0 is interesting for us.
Guessing that you pressed F3, F1 and F2. They are bound to volume keys in
already in the kernel, and very probably also in hardware: scancodes a0, ae, b0
are codes usually used for volume keys. (But /lib/udev/keymaps/module-lenovo
indicates, that Linux uses different volume keys on Lenovo notebooks.)
Could you generate event0_before.txt, pressing the same keys? I don't know,
whether keyboard returns different scancodes, or whether kernel changes its
binding.
---
There is yet another tool for key codes tracking:
/lib/udev/keymap -i /dev/input/event0
(Works properly only in Linux console, evtest works in root virtual console as
well.)
---
The "diff teclasAntesSuspension.txt teclasDespuesSuspension.txt" indicates
something different:
The first keyboard definition expected US-style keyboard, the second keyboard
definition expected international-style keyboard, which has three more keys. It
may be bug, or just the desktop environment issue.
If you keyboard has dedicated keys for "ñ", "\|º" and "¿¡", then it is a yet
another bug (and these keys probably don't work before suspension). If your
keyboard does not have these keys, then it is pointless.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.