On Mon, Jan 07, 2002 at 11:51:03AM +0100, fvwm-workers wrote: > On Sun, Jan 06, 2002 at 09:32:18PM +0100, Hana Stara wrote: > > On Sun, 2002-01-06 at 02:14, Dominik Vogt wrote: > > > 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. > > > > > I tried there versions: > > > > fvwm2-2.2.5-4 ....... OK > > fvwm2-2.2.4-9 ....... OK > > fvwm-2.4.0 ....... bug > > fvwm-2.4.3 ....... bug > > fvwm-2.4.4 ....... bug > > > > As for the X server, I also tried XFree86-4.1.0-3 but > > with the same result. :-( > > > > > > 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. > > > > > I don't know how to find where the the keystrokes get lost. > > But now I found something that could help to localize the problem: > > If I exit ANY application, the resulting state is that no window has > > focus. When no window has focus, the problem occurs. But on the > > other hand I do not know if windows get input - because no window > > has focus :-( > > > > I wrote you that after exiting rxvt (xterm) the problem occurs > > - it is not correct. It happens, when no window has focus. > > > > Toggling keyboard to US and back to Czech does not help! > > Sorry for confusing, I made mistake. So I will try to define the > > problem once more: > > I am still not sure what the problem is you encounter. Please > answer these questions: > > - After the problem appears, can you still focus a window by > moving the mouse ofer it or by clicking on its title? > - If yes, can you type into that newly focused window? > - Do your fvwm keyboard shortcuts still work? > - Can you still move windows with the mouse? > > Are you saying that you can't focus a win > > _______________________________________________________________ > > || When no window has focus, the keyboard layout must be US. || > > --------------------------------------------------------------- > > And if it isn't? What exactly happens then? > > > As for the FAQ 5.5 - I don't understand that :-( > > My point was: if its only fvwm internal bindings that do not work > this may be caused by some modifier keys like num-lock changing > state when the keymap is changed. Toggling that key again would > help in this case. But with your explanations above I don't think > that is your problem. > > > > I use a non-standard keyboard layout - my friend Yeti has made > > a rpm package so I send that as an attachment. > > Um, can you just send the files in a tar.gz? I don't like to > install rpm packages on my system because I can't control where > they end up. Also, please post your fvwm config file. > > > But I don't think it is the source of problem. > > I don't think it's the source of the problem either, but I need it > to reproduce the problem. > > > Please tell me, what more diagnostics should I do. > > > > > ---------------------------------------------------------------------- > > > > > > > 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.
Well, I tried to get that rpm package running, but I have no idea how to do it. Furthermore I don't understand what all that code is good for. All you have to do to switch keymaps is to make two different .Xmodmap files (e.g. .Xmodmap.us and .Xmodmap.cz) and call $ xmodmap .Xmodmap.us or $ xmodmap .Xmodmap.cz No need to touch the installation of the X server. In fvwm, you could put these actions into a menu or bind them to key strokes: Key c a CMS Exec xmodmap /home/foo/.Xmodmap.cz Key u a CMS Exec xmodmap /home/foo/.Xmodmap.us It's even very easy to generate the .Xmodmap files since you already can activate them: # switch to cz map $ xmodmap -pke > .Xmodmap.cz # switch to us map $ xmodmap -pke > .Xmodmap.us Although I don't really understand what all these files from the rpm do, I think there is a good chance that patching the X server installation breaks something. 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]
