On 05/27/11 00:22, Jesús J. Guerrero Botella wrote: > 2011/5/26 Jake Moe <jakesaddr...@gmail.com>: >> I'm having a weird issue I'm hoping someone here can help with. I've >> asked on the FVWM mailing list, but they can't reproduce with my config, >> so I'm hoping someone here with experience with the KDE/QT side of >> things might be able to offer a suggestion. > I saw your question in the fvwm mailing list. If Thomas Adam couldn't > help there I don't think anyone here will be able to. But stay tuned, > just in case... I, like him, couldn't reproduce this. I've > occasionally used lots of kde applications with fvwm without this > problem. >> It seems to only be limited to QT/KDE, but I have no idea if it's a >> "bug" in FVWM, or a "feature" in KDE that needs disabling. Hope this >> description makes sense. Does anyone have any ideas? > Well, in my book, a kde app is an application that links against the > kde foundations (kdelibs), a qt-only app is an application that links > against any or many of the qt parts, but not against kdelibs. smplayer > seems to fall into the later category. > > It could help if you were able to reproduce this with a minimal single > config file and try some more qt and kde programs. I've tried it with SMplayer, Kdevelop, Kate, KMyMoney, and KolourPaint and they all exhibit the same behaviour. Gnome and other X apps don't exhibit the same behaviour, it seems limited to KDE apps.
I'll try to strip down a config and see if I can't find what option does it. I think I might also move my .kde4 folder temporarily and see if it still happens. Thanks for the reply. Jake Moe
