Bug 496784

Summary:	XKB error message
Product:	[Fedora] Fedora	Reporter:	david cossé <david.cosse1>
Component:	xorg-x11-xkb-utils	Assignee:	Peter Hutterer <peter.hutterer>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	low
Version:	rawhide	CC:	xgl-maint
Target Milestone:	---	Flags:	peter.hutterer: needinfo?
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-05-11 00:19:08 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 david cossé 2009-04-21 06:51:28 UTC

Description of problem:
on Lenovo R61 laptop ThinkPad is not well recognize and a message is splash to the screen during gnome login asking to do a bug report. The error message also appears when plug-in a usb mouse

Version-Release number of selected component (if applicable):
X server version data:
The X.Org Foundation
10601000

How reproducible:


Steps to Reproduce:
At gnome starting time
  
Actual results:



[root@localhost davidf]# xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "latin9", "terminate:ctrl_alt_bksp"
_XKB_RULES_NAMES(STRING) = "evdev", "evdev", "fr", "", ""
[root@localhost davidf]# gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
Le listage des entrées dans « /desktop/gnome/peripherals/keyboard/kbd » a échoué : Le contact du serveur de configuration a échoué ; causes possibles : vous n'avez pas activé le réseau TCP/IP pour ORBit ou des verrous NFS non valides existent suite à un blocage du système. Voir http://projects.gnome.org/gconf/ pour plus d'informations. (Détails -  1: La connexion à la session a échoué : Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)


Expected results:


Additional info:

Comment 1 Peter Hutterer 2009-05-11 00:19:08 UTC


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