Bug 80252
Summary: | Alt-backspace is passed to the application as plain backspace | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Alexandre Oliva <aoliva> |
Component: | vte | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | phoebe | CC: | mitr |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-01-14 04:04:04 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
Alexandre Oliva
2002-12-23 10:08:49 UTC
If your X events are right, in "xev" alt backspace will show as state = 0x8, BackSpace. If that shows up right it's probably a terminal issue, otherwise probably X keymap issue. Here are the events I get for Alt-Backspace: KeyPress event, serial 20, synthetic NO, window 0x2a00001, root 0x3f, subw 0x0, time 17005674, (73,88), root:(750,615), state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: "" KeyPress event, serial 25, synthetic NO, window 0x2a00001, root 0x3f, subw 0x0, time 17006091, (73,88), root:(750,615), state 0x8, keycode 22 (keysym 0xff08, BackSpace), same_screen YES, XLookupString gives 1 bytes: " KeyRelease event, serial 25, synthetic NO, window 0x2a00001, root 0x3f, subw 0x0, time 17006158, (73,88), root:(750,615), state 0x8, keycode 22 (keysym 0xff08, BackSpace), same_screen YES, XLookupString gives 1 bytes: " KeyRelease event, serial 25, synthetic NO, window 0x2a00001, root 0x3f, subw 0x0, time 17006630, (73,88), root:(750,615), state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: "" Looks like it's a terminal issue, then... This should be fixed in 0.10.9 and later. Please reopen this bug ID if you find that this is not the case. *** Bug 81475 has been marked as a duplicate of this bug. *** Confirmed fixed in phoebe2. |