Hi,

I think I also hit this bug. My symptoms are that a binding that I
have for the "odiaeresis" key (a key for the character 'ö' present on
all Finnish keyboards) does not work. In addition, fvwm says at
startup:

[fvwm][ParseBinding]: <<ERROR>> No such key: odiaeresis

At least on one instance of the bug, the binding for "adiaeresis" (a
similar key for 'ä') worked but odiaeresis did not. Perhaps the X
server had registered some keys (or whatever it does to them at
startup) but not all of them when fvwm started. Like the submitter of
the bug, I also run X with startx (without xdm).

Restarting fvwm (with the menu entry Exit fvwm / Restart, bound to the
"Restart" command) seems to fix the bug.

However, this bug appears to be new: I have used the same bindings for
over a year in Debian etch (fvwm 2.5.18, X.Org 7.1.0) without any
problems, but they break every time with the current Debian testing
(fvwm 2.5.26, X.Org 7.3, more specifically fvwm 1:2.5.26-1 and
xserver-xorg 1:7.3+14). But I don't know whether the bug is a result
of a change in fvwm or a change in the X server.

I don't really have an idea of a possible fix. Perhaps there is a way
to wait for the X server to finish whatever it does to the keys at
startup? Or a config-file option to wait for a number of seconds at
startup, before doing anything to key bindings?

Or perhaps fvwm could somehow bind itself also to keys that don't
exist on the current keyboard (or whatever "No such key" means)?
XK_odiaeresis seems to be defined statically in
/usr/include/X11/keysymdef.h and XF86XK_PowerOff in
/usr/include/X11/XF86keysym.h, so the keys seem to exist in at least
some static form, so maybe it doesn't need to be an error that some
part of the X server API says that a key currently does not exist? (I
don't know how this sort of key binding is registered in X, so I can't
say if this is a feasible approach.)

-- 
-=- Rjs -=- [EMAIL PROTECTED], [EMAIL PROTECTED]



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to