Bug 671949 – Cannot set solid color background when background fading is disabled

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 671949 - Cannot set solid color background when background fading is disabled


Summary:	Cannot set solid color background when background fading is disabled


Status:	RESOLVED INCOMPLETE

Product:	gnome-desktop
Classification:	Core
Component:	libgnome-desktop
Version:	3.3.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Desktop Maintainers
QA Contact:	Desktop Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2012-03-12 22:10 UTC by Hernando Torque
Modified:	2013-03-24 19:41 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Hernando Torque 2012-03-12 22:10:29 UTC

Originally reported on Launchpad (https://bugs.launchpad.net/nautilus/+bug/952084):

When I try to set a solid color as desktop background with background fading disabled, all I get is a black background, no matter what color I choose in the control center/System Settings. The same works fine if I either enable background fading or use a vertical or horizontal 'color-shading-type'.

TEST CASE:
1. Open the 'Appearance' pane of g-c-c.
2. Make sure you have a background image selected.
3. Disable background fading from the command line:

    gsettings set org.gnome.nautilus.desktop background-fade false

4. In the 'Appearance' pane, try to set a solid color other than black.

RESULT:
* No matter what color is set, the background will always stay black.

To go back to the working case, run the following from the command line:

    gsettings set org.gnome.nautilus.desktop background-fade true

Comment 1 William Jon McCann 2012-08-12 14:51:49 UTC

Does this still occur?

Comment 2 Tobias Mueller 2013-03-24 19:41:20 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!