On Sat, Jan 05, 2002 at 03:50:28AM -0600, fvwm-bug wrote:
> FVWM Bug Tracking notification
>
> new message incoming/837
>
> Version: all newer than fvwm2-2.2.4-9
> CVS_Date:
> OS: redhat 7.x
> X_Server: 4.0.3
> Submission from: (NULL) (147.229.25.195)
>
>
> Hello,
>
> I am still using fvwm2-2.2.4-9 because newer versions have a bug.
> I use two different keyboard layouts (Czech and US) and I toggle
> between them by pressing left and right shift simultaneously.
> I found this problem:
Is this problem in 2.2.4 or in 2.4.x? If it is only in 2.2.4,
please tell the bug that you mentioned above. If it is in 2.4.x,
please provide the scripts and the keymaps you are using so that
I can try this myself.
> 1) I open an xterm (or rxvt)
> 2) I exit the xterm
> 3) when the Czech keyboard layout is active, fvwm ignores all
> key presses.
What does this mean? Do other windows still get input or is the
keyboard completely frozen? If only fvwm specific keystrokes do
not work anymore, please check if Q 5.5 from our FAQ helps
solving the problem.
----------------------------------------------------------------------
5.5 Why do NumLock, CapsLock and ScrollLock interfere with
ClickToFocus and/or my mouse bindings?
A: Because they are treated as modifiers. You can use the
IgnoreModifiers command to turn individual modifiers off for
bindings. With XFree86 the right command is
IgnoreModifiers L25
If you changed your modifiers manually or are using a different
X server use the 'xmodmap' command to find out which modifiers
correspond to the keys you want to switch off.
This command creates a lot of extra network traffic, depending
on your CPU, network connection, the number of Key Mouse commands
in your configuration file and the number of modifiers you want to
ignore. If you do not have a lightning fast machine or very few
bindings you should not ignore more than two modifiers. So do
not ignore scroll-lock if you have no problem with it.
A better way to solve this problem is to modify the keyboard
mapping of your X server. The commands
xmodmap -e "clear Lock"
xmodmap -e "clear Mod2"
xmodmap -e "clear Mod5"
remove the CapsLock, NumLock and ScrollLock from the keyboard map.
Pressing these keys has no effect then. To re-add them try this:
xmodmap -e "add Lock = Caps_Lock"
xmodmap -e "add Mod2 = Num_Lock"
xmodmap -e "add Mod5 = Scroll_Lock"
Fvwm has to be restarted to use the changes made by xmodmap.
Please refer to the man page of the xmodmap command for further
details.
----------------------------------------------------------------------
> The only way to restore the state is to toggle the keyboard to US.
> After that it is also possible to toggle it to Czech again and
> fvwm starts working properly. Czech keyboard itself is not a problem,
> fvwm works OK with it, but something wrong happens after exiting an
> xterm.
>
> I do not know what configuration files should I add, because I don't
> know where the problem is. But if you e-mail me, I will cooperate
> and do what you want.
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
