Bug 97457 - KXKB read wrong directory for international keyboard layout list
Summary: KXKB read wrong directory for international keyboard layout list
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86
Version: 9
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-06-16 07:09 UTC by Somsak Sriprayoonsakul
Modified: 2007-04-18 16:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-09-01 16:53:31 UTC
Embargoed:


Attachments (Terms of Use)

Description Somsak Sriprayoonsakul 2003-06-16 07:09:23 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
KXKB hardcode the path point to "symbols" file 
in "/usr/X11R6/lib/X11/xkb/symbols", however, the real path should 
be "/usr/X11R6/lib/X11/xkb/symbols/pc" or something like that. This result in 
wrong layout readed when selecting "us" keycode.

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

How reproducible:
Always

Steps to Reproduce:
1.Open international keyboard layout setting
2.Select the us keyboard layout and try selecting "generic101"
3.Switch to terminal that startx and error about xkb should appear
    

Actual Results:  Error about xkb showing at the terminal that startx

Expected Results:  No error shold appear there

Additional info:

Comment 1 Than Ngo 2003-06-16 10:35:31 UTC
It's a bug in XFree. please take a look here
http://bugs.kde.org/show_bug.cgi?id=55866

Comment 2 Mike A. Harris 2003-06-16 20:18:39 UTC
These types of bug reports against X, in particular any xkb related bug reports
should be reported directly to XFree86.org at http://bugs.xfree86.org so that
the xkb maintainer upstream is aware of it, and can fix it ASAP.  The second
benefit of reporting them upstream, is that they're fixed or resolved very
quickly by the upstream expert (meaning you get a fix faster), and that means
that the fix is fixed in the upstream repository so that everyone else benefits
too, not just Red Hat users.  It also keeps us in sync with upstream, which
means there is less maintenance.

Please report upstream, and paste a URL to the upstream report here if you'd
like me to track and backport the official fix when it is available.



Note You need to log in before you can comment on or make changes to this bug.