| 1 |
2011/5/26 Jake Moe <jakesaddress@×××××.com>: |
| 2 |
> I'm having a weird issue I'm hoping someone here can help with. I've |
| 3 |
> asked on the FVWM mailing list, but they can't reproduce with my config, |
| 4 |
> so I'm hoping someone here with experience with the KDE/QT side of |
| 5 |
> things might be able to offer a suggestion. |
| 6 |
|
| 7 |
I saw your question in the fvwm mailing list. If Thomas Adam couldn't |
| 8 |
help there I don't think anyone here will be able to. But stay tuned, |
| 9 |
just in case... I, like him, couldn't reproduce this. I've |
| 10 |
occasionally used lots of kde applications with fvwm without this |
| 11 |
problem. |
| 12 |
|
| 13 |
> It seems to only be limited to QT/KDE, but I have no idea if it's a |
| 14 |
> "bug" in FVWM, or a "feature" in KDE that needs disabling. Hope this |
| 15 |
> description makes sense. Does anyone have any ideas? |
| 16 |
|
| 17 |
Well, in my book, a kde app is an application that links against the |
| 18 |
kde foundations (kdelibs), a qt-only app is an application that links |
| 19 |
against any or many of the qt parts, but not against kdelibs. smplayer |
| 20 |
seems to fall into the later category. |
| 21 |
|
| 22 |
It could help if you were able to reproduce this with a minimal single |
| 23 |
config file and try some more qt and kde programs. |
| 24 |
|
| 25 |
-- |
| 26 |
Jesús Guerrero Botella |
Archives