Usually when you start gimp (for example when opening some xcf from dolphin), it shows tool tips wrong way. It uses white text and white background of rectangle. But when you start gimp using start menu or alt+f2 menu, then it is working normally (white text on dark rectangle). Also, if you disable checkbox "Apply this colors to non-qt applications" in color settings, then gimp is always working normal. Video demonstration included. My current applications versions: archlinux 4.12.4-1-ARCH 64-bit gimp 2.8.22 kde plasma 5.10.4 kde frameworks 5.36.0 Qt 5.9.1
Please note that you're reporting the issue to kde-gtk-config.
That is the configuration module for GTK integration
Nevertheless, the issue is real. Moving to Breeze.
It has been known for a while that recent versions of GTK can no longer handle whatever 'Apply colors to non-Qt applications' is injecting. Only Oxygen-GTK on GTK2 can utilize this ever since theme engine support was removed from GTK3, so it's technically a configuration and/or GTK bug. That is to say, we as theme authors can do nothing about this. We have been working intermittently on a script to dynamically regenerate the theme according to color schemes, so when that is available, the color scheme dialog should check for either Breeze-GTK or Oxygen-GTK and trigger that script when Breeze is selected. In fact, it would probably be best to work some of this in before the completed scripts are in master. That is, the dialog should only apply the traditional setting when: 1. 'Apply colors to non-Qt applications' is checked. 2. Oxygen-GTK, QtCurve, or any other capable GTK theme is selected. While I would love it if we could fix this bug solely in the GTK theme, any permanent fix would rely on several moving parts. As such, this issue should be moved elsewhere in the long run.
*** Bug 343119 has been marked as a duplicate of this bug. ***
Is there a way to programmatically detect when the GTK theme won't support this? If so, we could disable or remove the checkbox when such a theme is active.
*** This bug has been marked as a duplicate of bug 355540 ***