Dan Espen wrote: > Michael Großer <[email protected]> writes: > >> Thomas Adam wrote: >>> On Fri, Oct 28, 2011 at 10:34:13AM +0200, Michael Großer wrote: >>>> Thomas Adam wrote: >>>> > On Fri, Oct 28, 2011 at 09:50:06AM +0200, Michael Großer wrote: >>>> >> Michelle Konzack wrote: >>>> >> > Hello [email protected], >>>> >> >> I have quite a large config with some whistles and bells and maybe a >>>> >> >> couple dirty hacks in it and I use Archlinux (which means bleeding >>>> >> >> edge, >>>> >> >> constant updates and such), I think the first version I tried was >>>> >> >> 2.5.27, >>>> >> >> and not a single feature was broken with an update. >>>> >> > >>>> >> > I have strted using Fvwm2 in March 1999 and the config works up to >>>> >> > NOW. >>>> >> >>>> >> Last year, I came back to fvwm after 10 years and started to learn >>>> >> how to configure it. I started with version 2.5.26 (Debian Lenny). >>>> >> >>>> >> Eleven days ago, I migrated an existing (still dirty, but extremly >>>> >> powerful) >>>> >> configuration to a new Debian Squeeze plattform with "FVWM 2.5.30". >>>> >> >>>> >> I had to change the order of some code to make my config work >>>> >> with "FVWM 2.5.30". >>>> > >>>> > So you swapped around the Key binding lines after the function >>>> > definitions? >>>> > This simply just isn't true -- they both work the same. >>>> > >>>> > -- Thomas Adam >>>> >>>> I also couldn't believe this. Maybe, the 2.5.30 has a bug that is fixed >>>> in later releases? >>> >>> No, this won't be true either. >>> >>>> Whatever! I just leave this order now to be able to use all versions >>>> of FVWM, even the buggy ones. >>>> >>> >>> No, it's never just "Whatever!". If you've found a problem, I want to know >>> about it. All I can tell you with absolute certainty is it has nothing to >>> do with you reordering lines in your config. >>> >>> So put your config somewhere with it still exhibiting the problem for you, >>> and I'll take a look. >>> >>> -- Thomas Adam >> >> >> Hi! >> >> The reason was another bug, which let me think that I have to change the >> order >> of something in the config files. >> >> The real bug is the following: >> >> - When I use FVWM 2.5.30 on a Debian Squeeze system with KDM >> as X display manager, then the key bindings for some keys of >> my German keyboard do not work until I restart FVWM. >> >> Back in the days, I changed the order of something in my config files, >> restarted FVWM, and then the key bindings worked. This let me think that >> the order was the reason. >> >> - But the real cause why the key bindings worked after the restart of >> FVWM was because I restarted FVWM! >> >> You can download my FVWM config here: >> http://www.jumping-blue-turtle.com/fvwm/will_disappear_on_2012-01-31/8999_bugdemo_001.tar.bz2 >> >> It contains the file "0003_simple_keyboard_bindings". There, I added the >> following >> lines of code: >> >>> # demonstrate the >>> bug................................................................. >>> Key Plus A N Exec exec xterm >>> Key Numbersign A N Exec exec xterm >>> Key Minus A N Exec exec xterm >> >> This code is supposed to open an xterm when I press the "+", the "#" >> or the "-" key on my German keyboard: >> http://upload.wikimedia.org/wikipedia/commons/3/3c/Cherry_keyboard_105_keys.jpg >> --> All three keys are near the right Shift key as you can see on the >> picture. >> ----> And, here in Germany, we don't need a Shift key to use "+", "#" or "-". >> >> When I reboot one of my Debian Lenny systems, then all works fine. >> >> When I reboot my Debian Squeeze system, then nothing happens if I press >> these keys. Only after I restart FVWM (for example by pressing my >> short-cut "Ctrl+Alt+Pause"), these three keys open xterm windows >> when I hit them. >> >> * Can anybody reproduce this behaviour? >> * Is this a known bug? >> * What could be the cause of this behaviour? >> * What can I do to let these keys work without having to restart FVWM? > > My latest Fedora upgrade left me with a US-international setup > that caused a few keys to stop working. Qoute keys became "dead" prefix keys. > > The tools I use to fix this are xev and xmodmap. > > Using xev you can see what the key generates and xmodmap allows you to > change the key to what you want. > > I'm not clear on how restarting Fvwm would matter. > Fvwm is really just working with the keys as generated by the X Server. > > Maybe you should post more info on what your keys are generating and how > you restart fvwm. I don't have much experience with KDM. I always get > the > feeling that these DM things are doing something mysterious. > I boot to run level 3 and let my profile run startx. > That reads my .xinitrc which runs xmodmap early on to get the keyboard > working to my satisfaction.
Hi! Thanks for your answer. As usual, I will put this onto my to-do list, and tackle this problem when "FVWM" is topic again. Meanwhile, perhaps other people have ideas too? Michael
