Bug 186590

Summary:	Caps and num lock error
Product:	[Fedora] Fedora	Reporter:	Engel Fokkens <engelf>
Component:	control-center	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-03-11 04:44:48 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 Engel Fokkens 2006-03-24 16:16:26 UTC

Description of problem:
When pressing the Caps Lock or Num Lock key an error appears

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


How reproducible:


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


Expected results:


Additional info:
The erros: "An error occurred while loading or saving configuration information
for gnome-settings-daemon. Some of your configuration settings may not work
properly."
Details from the error: "Bad key or directory name:
"/desktop/gnome/peripherals/keyboard/host-)*\377/0/numlock_on": `)' is an
invalid character in key/directory names"

Comment 1 Ray Strode [halfline] 2007-08-15 21:41:20 UTC

are you still seeing this problem?  what is your hostname?

Comment 2 petrosyan 2008-03-11 04:44:48 UTC

The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present.  Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.

Setting status to "INSUFFICIENT_DATA".  If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested, 
please feel free to reopen the bug report.

Thank you in advance.