Bug 772646

Summary:	Hotkeys on Toshiba P855-S5200 are wrongly mapped, e.g. F3 puts computer to sleep
Product:	[openSUSE] openSUSE 12.1	Reporter:	Foolish Ewe <foolishewe>
Component:	Basesystem	Assignee:	Joey Lee <jlee>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 12.1
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Foolish Ewe 2012-07-23 14:30:02 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20100101 Firefox/13.0

I am running a new Toshiba P855-S5200, with OpenSUSE tumbleweed (12.1), and the F3 key puts the machine to sleep.  I don't use Apps that have the f3 key wired, but it could be a problem.   I also find that hotkeying (ctrl+alt+F7 for example) won't get me back to the KDE sessions if I do ctrl+alt+F1.  My current guess is that the mapping is misconfigured, but I'm not sure which component is responsible.

Reproducible: Always

Steps to Reproduce:
1.Boot using 12.1 Tumbleweed with KDE
2.Log In
3.Hit F3
Actual Results:  
Puts the machine to sleep (suspend to ram).

Expected Results:  
Whatever F3 should do.  If the previous action was searching, it should advance to the next search result.

uname -a
Linux linux-2kt2.site 3.4.5-33-desktop #1 SMP PREEMPT Wed Jul 18 09:09:22 UTC 2012 (cf1edf7) x86_64 x86_64 x86_64 GNU/Linux

dmesg output attached

Comment 1 Foolish Ewe 2012-07-26 23:04:15 UTC

Based on Bug 772997 (the 12.2 variant of this) I adjusted the bios settings so that the F3 and FN+F3 have the standard mapping as opposed to the non standard mapping.  I can now use F3 without putting the machine to sleep and get the search functionality under 12.1.

Here is output of showkey (after the BIOS adjustment), the first press and release event is for F3 the second time is FN+F3.  Note that although F3 no-longer puts the machine to sleep, now FN+F3 causes the machine to suspend to RAM.  This differs from the F3 key's action under windows (and according to the key cap's diagram) which is to increase the screen brightness.

sudo showkey
root's password:
kb mode was RAW
[ 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  28 release
^[ORkeycode  61 press
keycode  61 release
keycode 142 press
keycode 142 release

Comment 2 Foolish Ewe 2012-07-27 14:52:01 UTC

As per work on Bug 772997 (the 12.2 variant of this) this bug is resolved by the BIOS adjustment, so we should close this out.

Comment 3 Joey Lee 2012-07-30 09:17:43 UTC

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