2009/8/18 John H. Moe <john...@optushome.com.au>: > I've had what sounds like the same issue over a couple of builds and a > couple of different PCs, all on Gentoo, currently with FVWM 2.5.27.
First thing to check here then is, like Debian, they're not dicking about with the sources and applying out-of-band patches to add unwanted functionality which isn't applied here at upstream (often for good reasons). > The only thing I can add is that it *seems* to happen after I launch my > first KDE app (like KNetwalk, Kopete, K3B), but only sometimes. And if > the first one doesn't cause it, then it seems none do. From what I > understand, KDE apps have a few libs and/or programs that need to run in > the background to work properly, and once they're loaded they stay I suppose it's possible that some components of KDE are being loaded which are intercepting key events -- GNOME can do this for instance with its key-binding manager for multimedia keys which also let you bind other keys -- FVWM never gets the event for this, and so the effect is as you describe. Perhaps KDE do something similar? I wouldn't know, nor care. There's nothing in your config that would cause this that I can see. If you're not using FVWM 2.5.27, do so. Also in future, if all you wanted to do was print the bindings, you can use: PrintInfo bindings I added that for more or less this reason -- printed to STDERR. -- Thomas Adam
