Google 그룹스는 더 이상 새로운 유즈넷 게시물 또는 구독을 지원하지 않습니다. 과거의 콘텐츠는 계속 볼 수 있습니다.

Bug#235652: xbase-clients: key remaped with xmodmap fails to respond as expected to shifting

조회수 5회
읽지 않은 첫 메시지로 건너뛰기

Dave Harding

읽지 않음,
2004. 3. 1. 오후 1:20:0704. 3. 1.
받는사람
Package: xbase-clients
Version: 4.3.0-2
Severity: normal

When remapping the "\|" key to the "Backspace" key and vice versa on a standard US 104 keyboard using:

xmodmap -e 'keycode 22 = backslash bar'
xmodmap -e 'keycode 51 = BackSpace'

Pressing "backspace" generates "\" when pressed as expected.
Pressing "Shift+backspace" does not generate "|", as expected. Pressing
"Shift+<|\>" also does not generate "|". This behavior has been
reported to function as expected to me since at lease XFree 3.3.x
but not >=4.3

Output of xev after remaping, upon pressing "backspace":

KeyPress event, serial 25, synthetic NO, window 0x1c00001,
root 0x48, subw 0x0, time 4265320, (674,173), root:(677,243),
state 0x0, keycode 22 (keysym 0x5c, backslash), same_screen YES,
XLookupString gives 1 bytes: "\"


Output of xev after remaping, upon pressing "Shift+Backspace":

KeyPress event, serial 25, synthetic NO, window 0x1c00001,
root 0x48, subw 0x0, time 4298603, (795,168), root:(798,238),
state 0x1, keycode 22 (keysym 0x5c, backslash), same_screen YES,
XLookupString gives 1 bytes: "\"


This appears to be distro & kernel independant, leading me to beleive
it's a problem in the upstream code.

A report under Red Hat 9:
https://www.redhat.com/archives/xfree86-list/2003-September/msg00028.html

Also the bug is present in NetBSD, here's the build info:

XFree86 Version 4.3.0.1
Release Date: 15 August 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: NetBSD/i386 1.6ZG [ELF] The NetBSD Foundation,
Inc.
Build Date: 19 December 2003
Before reporting problems, check http://www.XFree86.Org/
to make sure that you have the latest version.
Module Loader present

Cheers,

-Dave

-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.3-1077171141-dah-ganymede
Locale: LANG=C, LC_CTYPE=C

Versions of packages xbase-clients depends on:
ii cpp 4:3.3.3-2 The GNU C preprocessor (cpp)
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
ii libdps1 4.3.0-2 Display PostScript (DPS) client li
ii libexpat1 1.95.6-8 XML parsing C library - runtime li
ii libfontconfig1 2.2.1-16 generic font configuration library
ii libfreetype6 2.1.7-2 FreeType 2 font engine, shared lib
ii libice6 4.3.0-2 Inter-Client Exchange library
ii libncurses5 5.3.20030719-5 Shared libraries for terminal hand
ii libpng12-0 1.2.5.0-5 PNG library - runtime
ii libsm6 4.3.0-2 X Window System Session Management
ii libstdc++5 1:3.3.3-1 The GNU Standard C++ Library v3
ii libxaw7 4.3.0-2 X Athena widget set library
ii libxcursor1 1.0.2-4 X Cursor management library
ii libxext6 4.3.0-2 X Window System miscellaneous exte
ii libxft2 2.1.2-5 FreeType-based font drawing librar
ii libxi6 4.3.0-2 X Window System Input extension li
ii libxmu6 4.3.0-2 X Window System miscellaneous util
ii libxmuu1 4.3.0-2 lightweight X Window System miscel
ii libxpm4 4.3.0-2 X pixmap library
ii libxrandr2 4.3.0-2 X Window System Resize, Rotate and
ii libxrender1 0.8.3-5 X Rendering Extension client libra
ii libxt6 4.3.0-2 X Toolkit Intrinsics
ii libxtrap6 4.3.0-2 X Window System protocol-trapping
ii libxtst6 4.3.0-2 X Window System event recording an
ii libxv1 4.3.0-2 X Window System video extension li
ii xlibmesa-gl [libgl1] 4.3.0-2 Mesa 3D graphics library [XFree86]
ii xlibmesa-glu [libglu1] 4.3.0-2 Mesa OpenGL utility library [XFree
ii xlibs 4.3.0-2 X Window System client libraries m
ii xlibs-data 4.3.0-2 X Window System client data
ii zlib1g 1:1.2.1-4 compression library - runtime

-- no debconf information


--
To UNSUBSCRIBE, email to debian-x...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Denis Barbier

읽지 않음,
2004. 3. 1. 오후 3:10:1704. 3. 1.
받는사람
On Mon, Mar 01, 2004 at 12:55:25PM -0500, Dave Harding wrote:
> Package: xbase-clients
> Version: 4.3.0-2
> Severity: normal
>
> When remapping the "\|" key to the "Backspace" key and vice versa on a standard US 104 keyboard using:
>
> xmodmap -e 'keycode 22 = backslash bar'
> xmodmap -e 'keycode 51 = BackSpace'
>
> Pressing "backspace" generates "\" when pressed as expected.
> Pressing "Shift+backspace" does not generate "|", as expected. Pressing
> "Shift+<|\>" also does not generate "|". This behavior has been
> reported to function as expected to me since at lease XFree 3.3.x
> but not >=4.3

Hi,

I believe that this is due to /etc/X11/xkb/symbols/pc/pc:
key <BKSP> {
type="CTRL+ALT",
symbols[Group1]= [ BackSpace, Terminate_Server ]
};
and thus is not a bug.

You have to set type to TWO_LEVEL if you want Shift+backspace to produce
a bar. For the record, I proposed in
http://lists.debian.org/debian-user-french/2004/debian-user-french-200402/msg01539.html
a solution (in French, but it mostly consists of shell commands) for
someone who needed to customize his function keys without root access.
I will be glad to learn if there are better alternatives to customize
XKB.

Denis

Dave Harding

읽지 않음,
2004. 3. 3. 오후 12:20:0804. 3. 3.
받는사람
On Mon, Mar 01, 2004 at 08:54:03PM +0100, Denis Barbier wrote:
> On Mon, Mar 01, 2004 at 12:55:25PM -0500, Dave Harding wrote:
> > Package: xbase-clients
> > Version: 4.3.0-2
> > Severity: normal
> >
> > Pressing "backspace" generates "\" when pressed as expected.
> > Pressing "Shift+backspace" does not generate "|", as expected. Pressing
> > "Shift+<|\>" also does not generate "|". This behavior has been
> > reported to function as expected to me since at lease XFree 3.3.x
> > but not >=4.3

> I believe that this is due to /etc/X11/xkb/symbols/pc/pc:


> key <BKSP> {
> type="CTRL+ALT",
> symbols[Group1]= [ BackSpace, Terminate_Server ]
> };
> and thus is not a bug.

Thank you and I appologize for my inabilty to locate that information on
my own. I was still curious as to the change of behavior between
versions of XFree86 prior to 4.3. I examined the change log available
at:
http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/CHANGELOG?rev=HEAD

In the changelog I found:

"675. Fix some problems with the addition of multi-layout scheme to
xkb: some keys that aren't 'alphabetic' should be treated as
such to allow CapsLock+Shift working as expected; sometimes it
is required to load an include file more than once due to
multi-layout configuration, also fix some typos (#5545, Ivan Pascal).

674. XKB programable 'special combinations' (such as Ctrl+Alt+<key>)
also send usual key evants (press and release). Although the
keysym generated in this case is NoSymbol such events can confuse
some applications (#5546, Ivan Pascal)."

And seeming most relevant to this bug:

"672. Temporarily enable the hard-coded Ctrl-Alt-Backspace terminate
sequence until a better fallback mechanism is implemented (Egbert
Eich)."

These appear to be under the XFree86 4.2.99.3 (21 December 2002)
release.

If setting the type to TWO_LEVEL works without breaking anything (as 672
implies) it would seem this, or the previous behavior of treating BKSP
as a regular key[1] should be the default behavior.

[1] /etc/X11/xkb/symbols/us on XFree86 Version 4.2.1.1 (Debian
4.2.1-12.1 20031003005825 ja...@nocrew.org):
<snip>
key <BKSP> { [ BackSpace ] };
</snip>

You've empowered me with the knowledge of how to make the changes
myself. I don't know enough about XFree86 to determine if the fallback
mechanism that caused the original hardcoding of the Ctrl+Alt-Backspace
has been implimented. If it has I would suspect the hardcoding of being
a bug, as it is no longer what the developers intended. If the fallback
feature has not been implemented... perhaps this should be wishlist?

Anyhow I leave it to your providence as a DD and I again thank you for
your forthcoming help,

-Dave

Debian Bug Tracking System

읽지 않음,
2004. 3. 3. 오후 5:20:0904. 3. 3.
받는사람
Your message dated Wed, 3 Mar 2004 22:43:14 +0100
with message-id <20040303214...@zobe.linuxfr.org>
and subject line Bug#235652: xbase-clients: key remaped with xmodmap fails to respond as expected to shifting
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 1 Mar 2004 17:57:34 +0000
>From ha...@gnuisance.net Mon Mar 01 09:57:34 2004
Return-path: <ha...@gnuisance.net>
Received: from sccrmhc12.comcast.net [204.127.202.56]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Axrfa-0004Bp-00; Mon, 01 Mar 2004 09:57:34 -0800
Received: from jupiter (pcp04594272pcs.brnmll01.nj.comcast.net[68.45.166.137])
by comcast.net (sccrmhc12) with ESMTP
id <2004030117570301200h0brbe>; Mon, 1 Mar 2004 17:57:03 +0000
Received: from [192.168.5.15] (helo=ganymede)
by jupiter with esmtp (Exim 3.36 #1 (Debian))
id 1Axrf4-0002Ov-00; Mon, 01 Mar 2004 12:57:02 -0500
Received: from dave by ganymede with local (Exim 3.36 #1 (Debian))
id 1AxrdV-0000w2-00; Mon, 01 Mar 2004 12:55:26 -0500
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Dave Harding <ha...@gnuisance.net>
To: Debian Bug Tracking System <sub...@bugs.debian.org>
Subject: xbase-clients: key remaped with xmodmap fails to respond as expected to
shifting
X-Mailer: reportbug 2.49
Date: Mon, 01 Mar 2004 12:55:25 -0500
Message-Id: <E1AxrdV-0000w2-00@ganymede>
Delivered-To: sub...@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_01
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no
version=2.60-bugs.debian.org_2004_03_01
X-Spam-Level:

Cheers,

-Dave

-- no debconf information

---------------------------------------
Received: (at 235652-done) by bugs.debian.org; 3 Mar 2004 21:43:16 +0000
>From bar...@linuxfr.org Wed Mar 03 13:43:16 2004
Return-path: <bar...@linuxfr.org>
Received: from zobe.linuxfr.org [212.27.33.220]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Aye96-0002gs-00; Wed, 03 Mar 2004 13:43:16 -0800
Received: by zobe.linuxfr.org (Postfix, from userid 1015)
id 6270BE8B3; Wed, 3 Mar 2004 22:43:14 +0100 (CET)
Date: Wed, 3 Mar 2004 22:43:14 +0100
To: 23565...@bugs.debian.org
Subject: Re: Bug#235652: xbase-clients: key remaped with xmodmap fails to respond as expected to shifting
Message-ID: <20040303214...@zobe.linuxfr.org>
References: <E1AxrdV-0000w2-00@ganymede> <2004030119...@zobe.linuxfr.org> <20040303165610.GA21023@ganymede>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040303165610.GA21023@ganymede>
User-Agent: Mutt/1.3.28i
From: bar...@linuxfr.org (Denis Barbier)
Delivered-To: 23565...@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_01
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=HAS_BUG_NUMBER autolearn=no
version=2.60-bugs.debian.org_2004_03_01
X-Spam-Level:

On Wed, Mar 03, 2004 at 11:56:10AM -0500, Dave Harding wrote:
[...]


> > > Pressing "backspace" generates "\" when pressed as expected.
> > > Pressing "Shift+backspace" does not generate "|", as expected. Pressing
> > > "Shift+<|\>" also does not generate "|". This behavior has been
> > > reported to function as expected to me since at lease XFree 3.3.x
> > > but not >=4.3
>

> > I believe that this is due to /etc/X11/xkb/symbols/pc/pc:
> > key <BKSP> {
> > type="CTRL+ALT",
> > symbols[Group1]= [ BackSpace, Terminate_Server ]
> > };
> > and thus is not a bug.
>
> Thank you and I appologize for my inabilty to locate that information on
> my own.

As your problem is quite specific and you were able to fix it, I am
closing this bug. This does not mean that current files are perfect,
but keeping this bug open does not help.
If you are interested in this issue, please let's discuss it on the
debian-x mailing list instead.

> I was still curious as to the change of behavior between versions of
> XFree86 prior to 4.3.

Right, there are indeed good reasons to be curious, some changes seem
to be quite harmful. The multi-layout scheme is much more powerful,
but for many users who do not need it, it also breaks compatibility :(

> I examined the change log available at:
> http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/CHANGELOG?rev=HEAD
>
> In the changelog I found:
>
> "675. Fix some problems with the addition of multi-layout scheme to
> xkb: some keys that aren't 'alphabetic' should be treated as
> such to allow CapsLock+Shift working as expected; sometimes it
> is required to load an include file more than once due to
> multi-layout configuration, also fix some typos (#5545, Ivan Pascal).
>
> 674. XKB programable 'special combinations' (such as Ctrl+Alt+<key>)
> also send usual key evants (press and release). Although the
> keysym generated in this case is NoSymbol such events can confuse
> some applications (#5546, Ivan Pascal)."

Huh, there does not seem to be any such bug in XFree86 bugzilla.
On the other hand http://bugzilla.xfree86.org/show_bug.cgi?id=1128
is about your exact same bug report. It tells that disbling XKB is
another solution for this problem.

> And seeming most relevant to this bug:
>
> "672. Temporarily enable the hard-coded Ctrl-Alt-Backspace terminate
> sequence until a better fallback mechanism is implemented (Egbert
> Eich)."
>
> These appear to be under the XFree86 4.2.99.3 (21 December 2002)
> release.
>
> If setting the type to TWO_LEVEL works without breaking anything (as 672
> implies) it would seem this, or the previous behavior of treating BKSP
> as a regular key[1] should be the default behavior.
>
> [1] /etc/X11/xkb/symbols/us on XFree86 Version 4.2.1.1 (Debian
> 4.2.1-12.1 20031003005825 ja...@nocrew.org):
> <snip>
> key <BKSP> { [ BackSpace ] };
> </snip>

According to the URL above, upstream did not consider changing current
definitions (and this statement is less than 1 month old), so they
should certainly be patched with great caution only. In other words,
Debian maintainers won't (IMHO of course) apply patches in this area
unless they are approved by XFree86 upstream. But they might instead
backport upstream patches, e.g. to provide the "srvrkeys:none" option
described in the URL above. So if you want to see this (or any other)
problem fixed in Debian XFree86 4.3, you could try to identify patches
applied upstream, and request that they get backported into Debian.

Denis

Branden Robinson

읽지 않음,
2004. 3. 4. 오후 10:00:2504. 3. 4.
받는사람
On Wed, Mar 03, 2004 at 01:48:06PM -0800, Denis Barbier wrote:
> On Wed, Mar 03, 2004 at 11:56:10AM -0500, Dave Harding wrote:
> [...]
> > > > Pressing "backspace" generates "\" when pressed as expected.
> > > > Pressing "Shift+backspace" does not generate "|", as expected. Pressing
> > > > "Shift+<|\>" also does not generate "|". This behavior has been
> > > > reported to function as expected to me since at lease XFree 3.3.x
> > > > but not >=4.3
> >
> > > I believe that this is due to /etc/X11/xkb/symbols/pc/pc:
> > > key <BKSP> {
> > > type="CTRL+ALT",
> > > symbols[Group1]= [ BackSpace, Terminate_Server ]
> > > };
> > > and thus is not a bug.
> >
> > Thank you and I appologize for my inabilty to locate that information on
> > my own.
>
> As your problem is quite specific and you were able to fix it, I am
> closing this bug. This does not mean that current files are perfect,
> but keeping this bug open does not help.
> If you are interested in this issue, please let's discuss it on the
> debian-x mailing list instead.

Well, that decision may have been a little hasty.

> > I was still curious as to the change of behavior between versions of
> > XFree86 prior to 4.3.
>
> Right, there are indeed good reasons to be curious, some changes seem
> to be quite harmful. The multi-layout scheme is much more powerful,
> but for many users who do not need it, it also breaks compatibility :(
>
> > I examined the change log available at:
> > http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/CHANGELOG?rev=HEAD
> >
> > In the changelog I found:
> >
> > "675. Fix some problems with the addition of multi-layout scheme to
> > xkb: some keys that aren't 'alphabetic' should be treated as
> > such to allow CapsLock+Shift working as expected; sometimes it
> > is required to load an include file more than once due to
> > multi-layout configuration, also fix some typos (#5545, Ivan Pascal).
> >
> > 674. XKB programable 'special combinations' (such as Ctrl+Alt+<key>)
> > also send usual key evants (press and release). Although the
> > keysym generated in this case is NoSymbol such events can confuse
> > some applications (#5546, Ivan Pascal)."
>
> Huh, there does not seem to be any such bug in XFree86 bugzilla.
> On the other hand http://bugzilla.xfree86.org/show_bug.cgi?id=1128
> is about your exact same bug report. It tells that disbling XKB is
> another solution for this problem.

Those are patch sequence number from the (private) XFree86 patches
mailing list, not Bugzilla IDs.

There's no way to get at those patches as they were submitted unless
you're a member of The XFree86 Project, Inc., but since they have cvsweb
open, the patches as applied *can* be retrieved.

I'm familiar with David Dawes's commit log conventions, and I suspect
from the above that the patches were applied as submitted, with cosmetic
changes at most.

> According to the URL above, upstream did not consider changing current
> definitions (and this statement is less than 1 month old), so they
> should certainly be patched with great caution only. In other words,
> Debian maintainers won't (IMHO of course) apply patches in this area
> unless they are approved by XFree86 upstream. But they might instead
> backport upstream patches, e.g. to provide the "srvrkeys:none" option
> described in the URL above. So if you want to see this (or any other)
> problem fixed in Debian XFree86 4.3, you could try to identify patches
> applied upstream, and request that they get backported into Debian.

Yes, and if someone would do this, we can take a serious look at
applying them.

Hence why I'm not sure the bug should be closed; just tagged "moreinfo"
until it can be tagged "patch".

Denis, if you agree, please do this.

--
G. Branden Robinson | The basic test of freedom is
Debian GNU/Linux | perhaps less in what we are free to
bra...@debian.org | do than in what we are free not to
http://people.debian.org/~branden/ | do. -- Eric Hoffer

signature.asc

Denis Barbier

읽지 않음,
2004. 3. 5. 오전 2:00:1404. 3. 5.
받는사람
reopen 235652
tags 235652 + moreinfo
thanks

On Thu, Mar 04, 2004 at 09:34:51PM -0500, Branden Robinson wrote:
[...]


> Hence why I'm not sure the bug should be closed; just tagged "moreinfo"
> until it can be tagged "patch".
>
> Denis, if you agree, please do this.

Sure, done.

Debian Bug Tracking System

읽지 않음,
2004. 3. 5. 오전 2:10:0504. 3. 5.
받는사람
Processing commands for con...@bugs.debian.org:

> reopen 235652


Bug#235652: xbase-clients: key remaped with xmodmap fails to respond as expected to shifting

Bug reopened, originator not changed.

> tags 235652 + moreinfo


Bug#235652: xbase-clients: key remaped with xmodmap fails to respond as expected to shifting

There were no tags set.
Tags added: moreinfo

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

새 메시지 0개