Bug 1208959 - xsettings-kde not exposing color settings to gtk apps properly
Summary: xsettings-kde not exposing color settings to gtk apps properly
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xsettings-kde
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-04 13:44 UTC by Glenn Holmer
Modified: 2016-12-20 13:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 13:28:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Gtk theming issue (29.32 KB, image/png)
2015-04-07 17:37 UTC, Helio Chissini de Castro
no flags Details

Description Glenn Holmer 2015-04-04 13:44:09 UTC
Description of problem: Rollover text on the buttons on either side of the yumex window is almost illegible (almost the same color for foreground and background).

Version-Release number of selected component (if applicable):
Name        : xsettings-kde
Version     : 0.12.3
Release     : 10.fc22
Architecture: x86_64

How reproducible: Start yumex, hover mouse over buttons on either side

Actual results: Foreground and background colors of popup text are almost the same, making the text unreadable.

Expected results: There should be a constrast between the colors.

Additional info: I brought this up on Fedora KDE mailing list and Rex Dieter suggested I file this bug.

Comment 1 Helio Chissini de Castro 2015-04-07 17:37:12 UTC
I can reproduce with Firefox on today full Fedora 22 install

Attached a no scroll image of current behavior.

Comment 2 Helio Chissini de Castro 2015-04-07 17:37:57 UTC
Created attachment 1011864 [details]
Gtk theming issue

Comment 3 Jan Kurik 2015-07-15 14:19:08 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

Comment 4 Fedora End Of Life 2016-11-24 11:39:10 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2016-12-20 13:28:55 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.