Bug 1003641 - grey BG instead of selected BG
Summary: grey BG instead of selected BG
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: oxygen-gtk3
Version: 19
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: 2013-09-02 14:32 UTC by Gene Czarcinski
Modified: 2015-02-17 17:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 17:01:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 324544 0 None None None Never

Description Gene Czarcinski 2013-09-02 14:32:40 UTC
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:
Everytime

Steps to Reproduce:
1.
2.
3.

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 16:59:46 UTC
What oxygen-gtk3 version installed?
Can you try oxygen-gtk3-1.2.0 from updates-testing?
https://admin.fedoraproject.org/updates/FEDORA-2013-15593

Comment 2 Gene Czarcinski 2013-09-04 18:36:23 UTC
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 18:39:19 UTC
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 18:40:59 UTC
and, please confirm which versions of oxygen-gtk you are using to test,

rpm -q oxygen-gtk2 oxygen-gtk3

please.

Comment 5 Gene Czarcinski 2013-09-04 19:57:11 UTC
oxygen-gtk2-1.4.0-1.fc19.x86_64
oxygen-gtk3-1.2.0-1.fc19.x86_64

You suggested I use the one from testing ... I did.

Comment 6 Gene Czarcinski 2013-09-04 20:37:20 UTC
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: 
https://bugzilla.gnome.org/show_bug.cgi?id=707506

although three previous bug reports where closed as "not us"

Comment 7 nucleo 2013-09-05 12:06:48 UTC
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 14:47:04 UTC
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):
https://git.gnome.org/browse/gnome-themes-standard/commit/?id=0019a41584317e73cdd3e3c06c8b2f0ce1978a21
https://git.gnome.org/browse/gnome-themes-standard/commit/?id=127d02f515dc5daa4e0af967c85030415dbf95e6

I would have thought that this interface change would have gotten more publicity.

Comment 9 nucleo 2013-09-05 18:15:55 UTC
Can you add this on bugs.kde.org? I can't copy every your comment.

Comment 10 Gene Czarcinski 2013-09-05 18:26:37 UTC
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 19:41:33 UTC
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 17:01:42 UTC
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
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.