Bug 119717

Summary: shift + l doesnt produce L when using Serbian keyboard
Product: Red Hat Enterprise Linux 3 Reporter: Igor Loncarevic <redhat>
Component: gnome-appletsAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-09-09 17:44:22 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 Igor Loncarevic 2004-04-01 19:20:49 UTC
Description of problem:

When choosing Serb keymap from gnome-applet Keyboard Layout Switcher
2.2.2 combination of shift + l is not producing big l (L) it stays on
small l (l).

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

gnome-applets-2.2.2-2
Keyboard Layer Switcher 2.2.2

How reproducible:

Always. 

Steps to Reproduce:
1. Add Serb keymap via Keyboard Layer Switcher gnome-applet
2. Make Serb keymap current keyboard
3. Start typing
  
Actual results:

l

Expected results:

L

Additional info:

The very same problem persists in Red Hat Linux 9 and Fedora Core 1

Comment 1 Mark McLoughlin 2004-05-31 11:00:11 UTC
Does "Serbian standard xkb keymap" work for you ?

The difference between the two is that "Serb keymap" does "gkb_xmmap
yu" and "standard xkb keymap" does "setxkbmap sr".

Comment 2 Igor Loncarevic 2004-06-01 19:46:02 UTC
"setxkbmap sr" is giving me correct L, but note that standard xkb
keymap is giving Cyrilic Serbian.

In first case it was Latin Serbian version that needs to be fixed.

Thanks

Comment 3 Mark McLoughlin 2004-06-02 05:59:53 UTC
In /usr/share/xmodmap/xmodmap.yu, try changing:

keycode  46 = l l Lstroke

to

keycode  46 = l L Lstroke

Does that fix it ?

Comment 4 Igor Loncarevic 2004-06-02 21:33:29 UTC
Hi Mark,

Yes it does!




Comment 5 Ray Strode [halfline] 2005-09-09 17:44:22 UTC
This problem is resolved Red Hat Enterprise Linux 4. Red Hat does not currently
plan to provide a resolution for this in a Red Hat Enterprise Linux 3 update for
currently deployed systems.

With the goal of minimizing risk of change for deployed systems, and in response
to customer and partner requirements, Red Hat takes a conservative approach when
evaluating changes for inclusion in maintenance updates for currently deployed
products. The primary objectives of update releases are to enable new hardware
platform support and to resolve critical defects.