Bug 664238

Summary:	setxkbmap settings are forgotten after suspend
Product:	[Fedora] Fedora	Reporter:	Skippy <lecotegougdelaforce>
Component:	xkeyboard-config	Assignee:	Peter Hutterer <peter.hutterer>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	14	CC:	avi.rei, moabi2000, peter.hutterer
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-02-23 04:33:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Skippy 2010-12-19 13:41:04 UTC

Description of problem:
Setxkbmap settings are forgotten after the computer has been in suspend mode.


Version-Release number of selected component (if applicable):
xkeyboard-config v.1.9 r.7.fc14
Gnome 2.32.0
Kernel 2.6.35.9-64.fc14.i686
up-to-date F14


How reproducible:
(Almost ?) always.


Steps to Reproduce:
1. Boot on F14.
2. Set some settings with setxkbmap command (e.g. "setxkbmap fr -variant bepo").
3. Go to suspend mode (e.g. by closing your laptop if this behaviour is enabled in gnome-power-preferences).
4. Get out of suspend mode and try to type anything (e.g. your password if the screen is locked).
  

Actual results:
Keyboard preferences are back to defaults.


Expected results:
Keyboard preferences should be the same as before to go to suspend mode.


Additional info:
Dell Latitude E6410.

Comment 1 Peter Hutterer 2011-02-23 04:33:14 UTC

This is expected behaviour. During suspend, the keyboard device is removed from the server as it is disabled. When it comes back it comes back as a new device.

This means two things:
- the setxkbmap configuration that only applied to the keyboard that was disabled went away when the keyboard went away.
- gnome will apply the configured keyboard settings when it sees new devices

For keyboard configuration to stick it has to be configured either in the xorg.conf.d snippets or in gnome directly for per-user configuration.

For more info, see http://who-t.blogspot.com/2010/06/keyboard-configuration-its-complicated.html

Comment 2 Peter Hutterer 2011-02-23 04:33:30 UTC

*** Bug 582123 has been marked as a duplicate of this bug. ***

Comment 3 Aviad Reich 2011-12-08 05:58:00 UTC

(In reply to comment #1)
> This is expected behaviour. During suspend, the keyboard device is removed from
> the server as it is disabled. When it comes back it comes back as a new device.
> 
> This means two things:
> - the setxkbmap configuration that only applied to the keyboard that was
> disabled went away when the keyboard went away.
> - gnome will apply the configured keyboard settings when it sees new devices
> 
> For keyboard configuration to stick it has to be configured either in the
> xorg.conf.d snippets or in gnome directly for per-user configuration.
> 
> For more info, see
> http://who-t.blogspot.com/2010/06/keyboard-configuration-its-complicated.html

KDE users, try: 
System Settings > Input Devices > Keyboard > Advanced > Ctrl key position > Swap Ctrl and Caps Lock
(taken from https://bbs.archlinux.org/viewtopic.php?pid=904087)