Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 44718 - AltGr is non-functional in gdm
AltGr is non-functional in gdm
Product: Red Hat Linux
Classification: Retired
Component: gdm (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Havoc Pennington
Aaron Brown
: 48061 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2001-06-15 11:42 EDT by Patrick C. F. Ernzer
Modified: 2007-04-18 12:33 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-07-12 12:07:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Patrick C. F. Ernzer 2001-06-15 11:42:58 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.2-2 i686; en-US; rv:0.9.1)

Description of problem:
AltGr-<key> only generates <key>, thus making it impossible to enter
symbols that are only accessible in conjunction with AltGr.

How reproducible:

Steps to Reproduce:
1. Install RHL 7.0
2. Go to runlevel 5
3. try to enter a symbol that is accessible by pressing AltGr

Actual Results:  AltGr is ignored, thus some special signs (i.e. @ on a
French keyboard) are not accessible

Expected Results:  AltGr should work the same way in gdm as it does when
logged into X.

Additional info:
Comment 1 Havoc Pennington 2001-06-18 10:54:39 EDT
I'm not really sure how AltGr gets set up normally - Mike is there some file 
that is supposed to get loaded with the keymap in it?
Comment 2 Havoc Pennington 2001-07-12 12:07:11 EDT
*** Bug 48061 has been marked as a duplicate of this bug. ***
Comment 3 Havoc Pennington 2001-07-12 12:09:49 EDT
Fixed in rawhide. Believed to have been an X bug where grabbing the keyboard 
broke AltGr. gdm no longer grabs the keyboard in rawhide.

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