Bug 772997

For normal behavior, you should press Fn+F3 for launch suspend or increase screen brightness, dependent on the function key definition with your machine.

On some notebook, there have BIOS option to define function key like "F3 = Fn+F3", and "Fn+F3 = F3", please check your BIOS have any option relate to function key behavior.

If not, please Use root account to run:
   #showkey

Then report what did you see when you press F3 key.

You were right about there being a bios setting called "special fn key" so that it treated the keys as if fn was pressed by default.  I switched it to "standard fn key" which appears to have improved the behavior in 12.1 tumbleweed that I'm currently running.  I'll need to boot of the 12.2 cd when I get home (I don't have it here).  Interestingly under Windows 7 and on the keycap the F3 key appears to be labeled as the increase screen brightness key, but under openSuse it is treated as the suspend key.

I got home and booted from the 12.2-RC1 KDE Live CD for x86-64.
Please recall that the BIOS setting was adjusted so the "standard key codes" is selected rather than the setting for "special key codes" which was in place when I filed this bug.

The first key press is F3, the second key press if FN+F3.  The second key press put the machine to sleep (i.e. suspend to RAM).

linux@linux:~> showkey
Couldn't get a file descriptor referring to the console
linux@linux:~> sudo showkey

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

kb mode was ?UNKNOWN?
[ if you are trying this under X, it might not work
since the X server is also reading /dev/console ]

press any key (program terminates 10s after last keypress)...

keycode  61 press
keycode  61 release
keycode 142 press
keycode 142 release
linux@linux:~> 
linux@linux:~> showkey

(In reply to comment #3)
> I got home and booted from the 12.2-RC1 KDE Live CD for x86-64.
> Please recall that the BIOS setting was adjusted so the "standard key codes" is
> selected rather than the setting for "special key codes" which was in place
> when I filed this bug.
> 
> The first key press is F3, the second key press if FN+F3.  The second key press
> put the machine to sleep (i.e. suspend to RAM).
> 
> linux@linux:~> showkey
> Couldn't get a file descriptor referring to the console
> linux@linux:~> sudo showkey
> 
> We trust you have received the usual lecture from the local System
> Administrator. It usually boils down to these three things:
> 
>     #1) Respect the privacy of others.
>     #2) Think before you type.
>     #3) With great power comes great responsibility.
> 
> kb mode was ?UNKNOWN?
> [ if you are trying this under X, it might not work
> since the X server is also reading /dev/console ]
> 
> press any key (program terminates 10s after last keypress)...
> 
> keycode  61 press
> keycode  61 release
> keycode 142 press
> keycode 142 release
> linux@linux:~> 
> linux@linux:~> showkey

Per showkey result, keycode on you machine is make sense now:

All keycode definition is in linux/input.h in Linux kernel:

#define KEY_F3                  61
#define KEY_SLEEP               142     /* SC System Sleep */

So, 61 is F3, 142 is KEY_SLEEP.


Do you think the BIOS option solve your issue?

The behavior is definitely better after the BIOS option was adjusted.
For the purposes of the fix, I think this is good enough, we should close this,
and the 12.1 variant of this bug, Bug 772646.

Thanks for your help.

On a side note, I have not yet identified all the keys, but FN+FX where x = 1..12
do not contain any key that maps to.  However the laptop's power button does the job.

#define KEY_WAKEUP              143     /* System Wake Up */

The previous message was garbled.  I was trying to say FX+FN where x is in 1..12 does not resolve to KEY_WAKEUP. I'll have to see if I can figure out the key mappings.  Is there a system utility that will dump the key map or should I use showkey to try every key combination?

(In reply to comment #6)
> The previous message was garbled.  I was trying to say FX+FN where x is in
> 1..12 does not resolve to KEY_WAKEUP. I'll have to see if I can figure out the
> key mappings.  Is there a system utility that will dump the key map or should I
> use showkey to try every key combination?

Yes, you need use showkey and press all Fn key.

Thanks for Follish's report, set this bug to INVALID because it causes by BIOS configuration.

Please feel free file any other bug if found.