This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours
Bug 83609 - Error in Yugoslav key mappings (xmodmap.yu)
Error in Yugoslav key mappings (xmodmap.yu)
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: gnome-applets (Show other bugs)
8.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Mark McLoughlin
Mike McLean
: Triaged
Depends On:
Blocks: 79579 CambridgeTarget
  Show dependency treegraph
 
Reported: 2003-02-06 04:40 EST by Gojko Adzic
Modified: 2007-04-18 12:50 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-08-27 06:44:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Gojko Adzic 2003-02-06 04:40:23 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
in file xmodmap.yu:

Both uppercase and lowercase letter L (keycode 46) map to the lowercase l.

The backspace does not work well in xterm (possibly other programs as well). 


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


How reproducible:
Always

Steps to Reproduce:
1.add gnome keyboard applet to panel
2. add yugoslav keymap to applet
3. type uppercase letter L, or try to use backspace in xterm
    

Actual Results:  lowercase letter l is displayed instead of uppercase L,
backspace does not work

Expected Results:  uppercase L, working backspace

Additional info:

fix: modify following two lines

keycode 22: BackSpace Delete
keycode 46: l l lstroke

to 

keycode 22: BackSpace  
keycode 46: l L lstroke
Comment 1 Alexander Larsson 2003-08-27 06:44:16 EDT
This seems to work for me in 2.3.6-1 at least. The L has been changed in the
xmodmap, but not the backspace, but backspace still works for me.
If this still doesn't work for you, please reopen the bug.

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