Bug 1003641 - grey BG instead of selected BG
grey BG instead of selected BG
Product: Fedora
Classification: Fedora
Component: oxygen-gtk3 (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Rex Dieter
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-09-02 10:32 EDT by Gene Czarcinski
Modified: 2015-02-17 12:01 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-02-17 12:01:42 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
KDE Software Compilation 324544 None None None Never

  None (edit)
Description Gene Czarcinski 2013-09-02 10:32:40 EDT
Description of problem:
With the file manager (nautilus) handling the desktop on (org.gnome.desktop.background.show-desktop-icons is enabled) and this theme is selected for the Gtk+ theme, then the background is grey.  If the file manager is NOT handling the desktop, then the selected background is correctly displayed.

Note:  This is NOT the only theme with this problem.  So far as I cn tell, only the Adwaita, Zukitwo, and Zukiwi gtk3 themes do not have the problem.

Version-Release number of selected component (if applicable):
Fedora 19, gnome 3

How reproducible:

Steps to Reproduce:

Actual results:
correct background displayed only if file manager not handling the desktop.

Expected results:
correct background displayed

Additional info:
Comment 1 nucleo 2013-09-02 12:59:46 EDT
What oxygen-gtk3 version installed?
Can you try oxygen-gtk3-1.2.0 from updates-testing?
Comment 2 Gene Czarcinski 2013-09-04 14:36:23 EDT
I have been doing some testing with other themes and the problem has been when those themes had a specification of something like:
* {
	/* inherit the color from parent by default */
	color: inherit;
	background-color: @bg_color;
Replacing this with something like:
.background {
    background-color: @theme_bg_color;
    color: @theme_fg_color;

.background.client-decorated {
    background-color: transparent;

.background.window-content {
    background-color: @theme_bg_color;
    color: inherit;
seems to work but I am sure is not really correct.

But, this might point you in the correct direction.
Comment 3 Rex Dieter 2013-09-04 14:39:19 EDT
Sounds like you're not talking about oxygen-gtk anymore, but gtk theme handling in general.  Can you please clarify?
Comment 4 Rex Dieter 2013-09-04 14:40:59 EDT
and, please confirm which versions of oxygen-gtk you are using to test,

rpm -q oxygen-gtk2 oxygen-gtk3

Comment 5 Gene Czarcinski 2013-09-04 15:57:11 EDT

You suggested I use the one from testing ... I did.
Comment 6 Gene Czarcinski 2013-09-04 16:37:20 EDT
It could be that the folks writing the themes were doing something they should not have been doing.  Or, it could be that someone changed the rules of the game.

I have opened an upstream problem against nautilus: 

although three previous bug reports where closed as "not us"
Comment 7 nucleo 2013-09-05 08:06:48 EDT
Fix from comment 2 needs testing https://bugs.kde.org/show_bug.cgi?id=324544#c3
You can add comment on bugs.kde.org.
Comment 8 Gene Czarcinski 2013-09-05 10:47:04 EDT
Apparently the rules changed.  The Adwaita theme was updated some time ago so it does not have the problem:

The themes probably needed to be updated because there was some change on the
gtk+ side. What makes me believe so are these changes which were made to
Adwaita (months before nautilus desktop changed):

I would have thought that this interface change would have gotten more publicity.
Comment 9 nucleo 2013-09-05 14:15:55 EDT
Can you add this on bugs.kde.org? I can't copy every your comment.
Comment 10 Gene Czarcinski 2013-09-05 14:26:37 EDT
queued up getting an ID ... just what I wanted, an ID on another bug reporting system
Comment 11 Fedora End Of Life 2015-01-09 14:41:33 EST
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 12 Fedora End Of Life 2015-02-17 12:01:42 EST
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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

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.