[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#255025: xlibs: Windows keys stopped working as modifiers to some other keys



barbier@linuxfr.org (Denis Barbier) writes:

> On Fri, Sep 03, 2004 at 11:43:34PM +0200, Denis Barbier wrote:
>> On Fri, Sep 03, 2004 at 02:34:48PM +0100, Bruce Stephens wrote:
> [...]
>> When loading server-0.xkb-4.3.0.dfsg.1-6, xev output seems right, as you
>> can see below, so I tag this bug as being unreproducible.  I have no
>> more idea at the moment to solve this bug, sorry.
>
> You can run
>  $ xkbcomp server-0.xkb-4.3.0.dfsg.1-6 :0
> in a Failsafe session or by running X manually to see if this bug still
> occurs when no window manager is launched.
>
> I forgot to mention that xkbcomp reports warnings, they are harmless.

I've found an acceptable solution to this.  If I use the sawfish
binding dialog, and say "Grab", and then press Windows-Left (or
whatever), sawfish reports that as H-Left, and it works.  So for the
moment everything's OK if I change sawfish's setting for its default
modifer to Hyper rather than Super.

xmodmap shows:
mod4        Super_L (0x7f),  Hyper_L (0x80)

So I suspect there's some confusion between the keys and modifiers in
sawfish: perhaps when it reads the event of a Windows keypress, it
reads mod4 and then turns that into Hyper (the first in alphabetical
order) or something.  I'm not sure whether this is an actual bug in
sawfish or not, however---I find it confusing, but possibly something
else (something in GNOME, for example) is setting the modifiers oddly
because of some old bit of configuration I have.

Thanks very much for the links to documentation about the xkb
configuration formats---this is an area that seems poorly documented
(perhaps reasonably, since most of us shouldn't touch it other than to
select options).  It might be worth adding the links to the FAQ?




Reply to: