Portage still lacks the important gtk-qt engine that allows GTK to use KDE widget styles. The “kde” overlay only has the live ebuild. Meanwhile, version 1.0 and 1.1 came out a long time ago. (See URL) How about reflecting that in Portage. :) Oh, and the “gtk” flag for “x11-libs/qt-gui” seems to do nothing. (Or is that, to show the GTK theme is QT?) Thanks! :) Reproducible: Always Steps to Reproduce:
1.1 is the broken version that was removed from Portage because it breaks mozilla apps, audacious and more
Then some other version. I’m using gtk-engines-qt-9999 *right now*. With Mozilla, GTK, Java and KDE apps. No problems at all, 100% stable. It’s really silly to expect users to have all their non-KDE apps look like they are out of the 90s or with some weird other theme, when there’s a solution that works perfectly fine. If you must, you make a snapshot, make it ~arch, and put it in the KDE HOWTOs. Since it’s about the most damn often question asked for KDE.
We mostly recommend users to use -qtcurve for both qt and gtk apps. Because -qt had too much issues.
(In reply to comment #3) > We mostly recommend users to use -qtcurve for both qt and gtk apps. Because -qt > had too much issues. Please don’t. qtcurve means losing the ability to use the style of your choice. It’s an all-around bad workaround. Instead, the better solution, is to fix -qt, if it has issues. Which is yet to prove, since as I said, it still works perfectly here. I think gtk-qt should be an essential core part of QT. Because, what good is a widget set, if 60% of the applications don't show/use it? With a bit of polishing of this package, it could be less than 20%.
time to try oxygen-gtk, seems to be the winner, we're just waiting for an actual release. sorry but wontfix
