Pure Qt4 based applications only seem to be affected by this. If a widget is disabled, the color scheme does not indicate this in the text color. Reproducible: Always Steps to Reproduce: 1. Open any pure qt4 based application (Take CuteCom as an example) 2. Look for any disabled widgets (The close button should be disabled initially in cutecom) 3. Unless you try clicking on the disabled widget, you never know that it is disabled to begin with. Actual Results: The disabled widget in indistinguishable. Expected Results: The disabled widget should be grayed out.
Created attachment 90976 [details] Screenshot of cutecom; a pute qt4 based app. This is a picture for cutecom. The Close button is disabled but you can't tell looking at it.
I cannot reproduce here with my own pure Qt apps see: http://wstaw.org/m/2015/02/08/plasma-desktopvY2904.png I suspect an issue with either the color palette, or the application itself. Can you try - with another widget style - with another application - with another color palette Thx, Hugo
could you also try with qtconfig ? (that's the minimum Qt4 only app) Here it looks like this: http://wstaw.org/m/2015/02/08/plasma-desktopys2904.png And disabled widgets are definitly visible
Strange. I don't know what to attribute this bug to anything other than kubuntu packages. Changing the theme and application did not help. qt-config is broken in kubuntu 15.04. Which components should I change in the pallets to test disabled state?
You can check the kde settings for inactive/disabled colors in system-settings, as in http://wstaw.org/m/2015/02/09/plasma-desktopHf2904.png and see if these have an impact on the issues you are having.
Editing those settings for disabled seem to have no impact on pure Qt4 based apps. They do affect KDE/Qt4 apps as expected.
So, no more clue ... I think we agree it is not a Breeze bug though, and no idea whether it even is a kde bug. I'd suggest you go ask around on kubuntu forums ... It might be related to Qt installation. In the meanwhile, closing as invalid (sorry), because there is not much more help we can offer here. Feel free to re-open if you have any news on this, and thanks for reporting! Hugo
See https://bugreports.qt.io/browse/QTBUG-30034 I don't know which component is responsible for kdeglobals.