Bug 124895

Summary: xorg-X11 report an error after activating the XKB configuration
Product: [Fedora] Fedora Reporter: Xavier Nicolovici <xavier>
Component: xorg-x11Assignee: Mike A. Harris <mharris>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 2   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:03:53 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 Xavier Nicolovici 2004-06-01 09:25:41 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510

Description of problem:
When logging into the system, a GNOME dialog box is opened saying that
the XKB configuration fails during activation.

The dialog box suggest to report the output of the following command:

* xprop -root | grep XKB
*****************************
_XKB_RULES_NAMES_BACKUP(STRING) = "xfree86", "pc105", "fr_CH", "", ""
_XKB_RULES_NAMES(STRING) = "xfree86", "pc105", "fr_CH", "", ""
*****************************

* gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb
*****************************
 layouts = [fr_CH]
 model = pc105
 overrideSettings = false
 options = []
*****************************

This problem does not seem to have any impact on the keyboard
configuration (everything works fine).



Version-Release number of selected component (if applicable):
org-X11-6.7.0-2

How reproducible:
Always

Steps to Reproduce:
1. Configure your keyboard as specified in the problem description
2. Log in to the GNOME environment
3.
    

Actual Results:  A GNOME dialog screen appears at intialization time
saying that the XKB configuration activation fails.

Expected Results:  No dialog box displayed.

Additional info:

Comment 1 Mike A. Harris 2004-06-01 10:17:49 UTC

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

Comment 2 Red Hat Bugzilla 2006-02-21 19:03:53 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.