Bug 255290 - KDE apps running in GNOME and using QGtkStyle doesn't use gtk+ color scheme
Summary: KDE apps running in GNOME and using QGtkStyle doesn't use gtk+ color scheme
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kdeui (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-26 09:57 UTC by Yao Ziyuan
Modified: 2023-01-17 05:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yao Ziyuan 2010-10-26 09:57:45 UTC
Version:           4.5 (using KDE 4.5.2) 
OS:                Linux

A KDE app, e.g. KTorrent, when running in a GNOME environment and using the Qt widget style "GTK+" (QGtkStyle), should use gtk+'s current color scheme whenever applicable, but in reality, it doesn't. Most notably, Fedora 13's default gtk+ window background color is #ECEBEB, while a KTorrent running in Fedora 13's GNOME environment and using QGtkStyle uses KDE's window background color (#E0DFDF) instead. This is because KDE overrides gtk+'s color palette with KDE's own color palette even if KDE is not running as the current desktop environment.

Possible solutions:
1. Don't override gtk+'s color palette with KDE's when a KDE app is running in a non-KDE desktop environment (e.g. GNOME).
2. If the current KDE style is "GTK+" (QGtkStyle), don't override gtk+'s color palette.


Reproducible: Always

Steps to Reproduce:
1. Log into a KDE environment. In systemsettings, set the current KDE style to "GTK+" (QGtkStyle).
2. Log out and log into a GNOME environment. Run KTorrent in it. You will see KTorrent using KDE's window background color rather than gtk+'s.

Actual Results:  
You will see KTorrent using KDE's window background color rather than gtk+'s.

Expected Results:  
KTorrent running in GNOME and using QGtkStyle should use gtk+'s colors, e.g. window background color.

Possible solutions:
1. Don't override gtk+'s color palette with KDE's when a KDE app is running in a non-KDE desktop environment (e.g. GNOME).
2. If the current KDE style is "GTK+" (QGtkStyle), don't override gtk+'s color palette.
Comment 1 Yao Ziyuan 2010-10-26 10:21:34 UTC
Originally I thought it was a Qt bug and created this Qt bug report:
http://bugreports.qt.nokia.com/browse/QTBUG-14665

But a Qt developer pointed out it's actually a KDE bug (KDE shouldn't override gtk+'s color scheme in this case) and closed that bug report.
Comment 2 Yao Ziyuan 2010-10-27 08:57:28 UTC
This problem is made more evident when the current gtk+ theme is a dark one (e.g. Nodoka Midnight) while KDE4 uses its default Oxygen color scheme.
Comment 3 Jens Bache-Wiig 2010-10-27 12:58:47 UTC
Yes, I don't think this is isolated to QGtkStyle though. If you are not running inside the KDE environment, I don't think KDE should impose the KDE palette at all. A Related issue is that KDE uses the KDE icon theme while running inside a GNOME/XFCE environment whereas it should really be using the GTK icon theme to play nice.
Comment 4 Yao Ziyuan 2010-10-27 14:08:32 UTC
Another evidence is that Qt apps don't have this problem. If the current gtk+ theme is a dark one (Nodoka Midnight), a Qt app such as qtconfig-qt4 or qstardict will automatically use the dark color scheme.
Comment 5 Yao Ziyuan 2010-11-04 09:38:28 UTC
I just upgraded to Fedora 14 which uses KDE 4.5.2. It has improved regarding this bug, but not completely. Now if a KDE app is already running in GNOME, changing the current gtk+ theme will automatically change the running KDE app's theme and colors correctly. However, if the KDE app is then closed and restarted again, its colors are abducted by KDE to KDE's own colors again.
Comment 6 Andrew Crouthamel 2018-11-05 03:08:16 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Yao Ziyuan 2018-11-05 05:04:27 UTC
(In reply to Andrew Crouthamel from comment #6)
> Dear Bug Submitter,
> 
> This bug has been stagnant for a long time. Could you help us out and
> re-test if the bug is valid in the latest version? I am setting the status
> to NEEDSINFO pending your response, please change the Status back to
> REPORTED when you respond.
> 
> Thank you for helping us make KDE software even better for everyone!

No longer use KDE and can't re-test. Sorry.
Comment 8 Andrew Crouthamel 2018-11-17 05:03:16 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Justin Zobel 2022-12-18 08:18:07 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 10 Bug Janitor Service 2023-01-02 05:26:34 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 11 Bug Janitor Service 2023-01-17 05:17:55 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!