Bug 893697

Summary:	Keyboard mapping after upgrade
Product:	[Fedora] Fedora	Reporter:	TR Bentley <home>
Component:	distribution	Assignee:	Bill Nottingham <notting>
Status:	CLOSED DUPLICATE	QA Contact:	Bill Nottingham <notting>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	dennis, rvokal
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-01-09 18:31:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description TR Bentley 2013-01-09 18:16:59 UTC

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 TR Bentley 2013-01-09 18:20:52 UTC

Description of problem:
Upgraded my laptop from F17 to F18 via yum and instructions on Fedora site.
Since upgrade my keyboard has been mapped incorrectly until I run system-config-keyboard as root.
This fixes the problem until I reboot.

Version-Release number of selected component (if applicable):


How reproducible:
Every time

Steps to Reproduce:
1. Restart laptop
2. Keyboard mapped incorrectly
3. run system-config-keyboard
4. Keyboard mapped correctly.
  
Actual results:
Keys mapped incorrectly 

Expected results:


Additional info:

Comment 2 Bill Nottingham 2013-01-09 18:31:05 UTC


*** This bug has been marked as a duplicate of bug 889699 ***

Comment 3 Bill Nottingham 2013-01-09 18:31:38 UTC

See https://bugzilla.redhat.com/show_bug.cgi?id=889699#c24 , specifically.

Comment 4 Adam Williamson 2013-01-09 18:32:21 UTC

just to confirm the dupe, check that the package set when you did the bug upgrade included systemd 195-13 or earlier (I'm pretty sure it must have done). 'yum history' can tell you this. even if you get 195-14 with a later update, it won't fix the bug, because the %post script only gets one shot to run. but upgrades which include 195-15 will work fine.

Comment 5 TR Bentley 2013-01-09 18:47:00 UTC

This is correct I have systemd 195-13 installed.