Hi!

After I updated plasma desktop on Arch linux, KDE 4.14, some applications like handbrake, Gnome mplayer or go-for-it are completely inverted black and white (white fonts on black canvas)... I have no idea how to fix that, the KDE color settings (also the GTK color settings in kdesystemsettings!) have no effect at all...

What do I have to do to make theses applications respect systemsettings... also these windows cannot be properly resized and use strange metrics. Like doubleclick on the titlebar to maximize widow does center handbrake vertically but maximises the window horizontically...

They still work kind of but some columns are too narrow due to nonresizable dialogboxes...

What do I have to do to fix this?

thx a lot,
piedro

Welcome to the gnomification of gtk+3

The clients btw. use client side decorations - you simply have to use what's been deemed to be the best for you.
There's no way to make that configurable, custom styling support has largely been withdrawn from gtk+3, it's been closed down to css and afaiu the clients css takes precedence (ie. if a client sets a white on black css, that's what you're supposed to use)

Replace your gtk+3 based applications if you want to control the look and feel of your desktop. /rant

As I do not know a lot about gnome I cannot really comment on your rant nor sing along... but in this case I am pretty sure this is not using the wrong or a predefined theme. This is like not themed at all or using the high contrast view for visually impaired users. Everything is just pitch black #000000 (I took the gimp color chooser and checked the color values... gimp looks perfectly fine by the way...) and the font is white #FFFFFF...

And the whole issue doesn't apply to all gnome applications.

Though I get your frustration with taking away choice from the user by the gnome development (if I get you right on that point...) that is not the problem I am talking about.

Anybody more ideas?

Thx,
piedro

screenshot?

About the screenshot: I cannot upload the screenshot here... so that doesn't work...

Also it is really unnecessary: Take the application "handbrake for example - every font is white "#ffffff" and everything else is black "#000000", builtin symbols are there and that's it. Maximizing the window does only horizontically maximize and all content disappears - just a black window. After resizing the window looks again as described above.

the same applies to "gnome mplayeer" - white fonts on black background. It looks like the gnome high contrast theme.

thx for helping, p.

The maximization is likely due to a fixed aspect or maximum geometry demanded by the window - in konsole run

Code: Select all

xprop | grep "program specified"

and click the window when the cursor turns into a '+' shape. Watch the output.

You can then loose this by running "kcmshell4 kwinrules", "detect window" (click handbrake) and in the "size & position" tab adjust the maximum geometry resp. disobey geometry restrictions.

You should be able to upload images (w/o registration) here
http://postimage.org/
here
http://tinypic.com/
or on a dozen other services

In case only some parts of the window are black, that's likely a bug with ubuntus overlay scrollbar plugin for gtk.

The output for gnome-mplayer is :

WM_CLASS(STRING) = "gnome-mplayer", "Gnome-mplayer"

There are no dimension or anything else whatsoever...

Also the module kwinrules doesn't exist and trying to righclick the window and go for extra windows rule gives a segmentation fault:

kdeinit5 PID: 23734 Signal: Segmentation fault

Also this is Arch Linux fully upgraded with plasma 5.4 as mentioned above, not Ubuntu and the windows are completey black not partially...


PIcture is here:




thx, piedro

piedro wrote:The output for gnome-mplayer is :
WM_CLASS(STRING) = "gnome-mplayer", "Gnome-mplayer"

How can that possibly match the grep? And the full xprop output would certainly be longer.

piedro wrote:Also the module kwinrules doesn't exist and trying to righclick the window and go for extra windows rule gives a segmentation fault:

kdeinit5 PID: 23734 Signal: Segmentation fault

Ah, but that's KDE5 - run "kcmshell5 kwinrules".
Crash is known bug, fixed in 5.3.2.

piedro wrote:Also this is Arch Linux fully upgraded with plasma 5.4 as mentioned above, not Ubuntu

I was just guessing from your distro icon....

piedro wrote:

I installed handbrake (and gtk3)
a) handbrake has (as predicted...) "program specified maximum size: 1920 by 768" - the window does not want to be higher than 768px. The rules will allow you to override this (didn't try but be careful, some clients happily crash because the didn't expect a bigger size)
Didn't try gnome-mplayer
b) Check ~/.config/gtk-3.0/settings.ini for a "gtk-theme-name" entry. Ensure it's absent or set tos something installed. The adwaita theme is provided by gnome-themes-standard.

There has been a misunderstanding on my side:

xprop | grep "program specified"

I was under the impression I have to replace the string "program specified" with the name of the program specified...
My bad, thx for the clarification... it works now as expected...


The content of settings.ini for gtk3 is correct as it should be, the theme is the default oxygen-gtk, which should be the one making sure that KDE and GTK look the same(, should it? That's what the documentation says...). In this settings.ini file all the entries match my choices from system-settings for the GTK-style of applications:

[Settings]
gtk-font-name=Lucida MAC Regular 11
gtk-theme-name=oxygen-gtk
gtk-icon-theme-name=breeze
gtk-fallback-icon-theme=breeze-dark
gtk-toolbar-style=GTK_TOOLBAR_ICONS
gtk-menu-images=1
gtk-button-images=1


So I guess the problem has to be here somewhere - the colour settings clearly do not get applied.

As for the geometry, I can live with that if it is fixed in 5.3.2 - I can wait for that.

So the problem remaining is: Where do the GTK3 applications get there themeing colors from?

thx for your help and efforts,
piedro

Oxygen-gtk3 is dead since gtk3 3.16 as gtk removed support for style engines.
See https://bugs.kde.org/show_bug.cgi?id=343555

Ok, thx for the bug report link, there seems to be a breeze-gtk theme now in the works but I tested and it is not working correctly yet... removing support for style engines is just an annoying move of the gnome camp... knowing how many projects and users rely on this...

well, I am disappointed - I guess, developments like these will prevent us from having a consistent professional and usable look and feel for a long time coming...

thx anyway,
piedro

btw: with the breeze-gtk theme from GIT handbrake looks kind of breezy but Gnome Mplayer still (or again) uses white fonts on dark canvas...

gnome-mplayer behaves rather strange with Elegant brit or "Adwaita Cupertino L" - like it's running into a theme conflict.

With Adwaita it's #DFE2DC on #393F3F (bright on dark gray) - as mentioned, that's the way gtk3 now is.

I assume the breeze theme is "broken" (or the gtk3 css engine is) in that it has !important entries overriding the application side css.

Well, that is exactly why using CSS for the desktop is not such a brilliant idea... as the name says it's cascading...
any design someone is working on can be rendered useless or uncontrollable by changes in gnome.

Using the theme customization tools in KDE is also inconsistent because they will only influence the native KDE applications.
So any theme designer will have to create a KDE theme, a GTK3 theme and a GTK2 theme to get the same look... and he or she has to keep these versions in sync otherwise we end up with different theme versions for different applications...

Just as we had a system to integrate look and feel somehow - now it's all in vain again...

So the way to do things, once again, is gnome users stick to gnome apps and KDE users stick to KDE apps...
Meaning either compromise on the funcionality of applications to use (e.g. use rekonq instead fo firefox) or deal with inconsistent and buggy look and feel...

I guess, I could rant on that all day, well,
thx for your help,
piedro