Red Hat Bugzilla – Bug 1001051
Desktop background does not work in gnome classic
Last modified: 2015-06-29 20:41:32 EDT
Description of problem:
When I install F20 Alpha TC1 and log in into Gnome classic mode, it shows only gray desktop background. When I try to set background to some image, nothing happens. When I click on Applications -> Activities overview, background is displayed in it.
This sounds like the https://bugzilla.gnome.org/show_bug.cgi?id=706665 GNOME bug, which was fixed in nautilus a couple of days ago. In any case, this is most likely a nautilus issue, reassigning.
*** Bug 993550 has been marked as a duplicate of this bug. ***
Can we please have a fc19 update of nautilus to verify the fixing of the bug?
nautilus-3.8.2-2.fc19 has been submitted as an update for Fedora 19.
This nautilus does not work for me, but I do not run gnome classic.
why were you begging for an update then ?
and in what way does it not work ?
See comment #2.
And the background issue is not fixed.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing nautilus-3.8.2-2.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
See comment #9.
Euhm.. Make that comment #8.
could i get a screenshot of the problem ? i just updates an f19 installation to my nautilus build, and could not reproduce the gray background problem with nautilus rendering the desktop
It is simply the desktop with icons etc on it but the background replaced by a grey mass.
Real background is visible when we press the windows key.
I don't know what is the problem with F19 and/or gnome-shell, but it works now in F20 gnome-classic, TC5.
Is there anoy logging that I can provide to help fix the issue for non-classic gnome?
Is there any logging that I can provide to help fix the issue for non-classic gnome?
nautilus-3.8.2-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
$ rpm -q nautilus
See comment #8.
See comment #13.
See comment #15 and #16.
Oh, BTW, one other approach would be to look at comment #2 and declare that bug really different, we could then proceed with https://bugzilla.redhat.com/show_bug.cgi?id=993550 for finding the root cause of the non-classic situation.
$ rpm -q nautilus
Still not working as it should. What logs do you need?
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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'
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 20 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.