Description of problem:
On a fedora using openbox I installed nitrogen to manage my wallpaper.
I got an trouble to save the change made in single screen layout.
In fact when I do nitrogen --restore teh previous wallpaper comeback . The file bg-saved.cfg is not modified when I change my wallpaper using the command nitrogen or nitrogen --save.
But if I do the same in dual screen using the same computer and system the save is done and a nitrogen --restore give back the right wallpaper configuration.
If I edit manually the file everything is fine. So it's look like teh trouble is only applicable for writing in single screen layout.
Version-Release number of selected component (if applicable):
Nom : nitrogen
Architecture : x86_64
Version : 1.5.2
Révision : 9.20131218git.fc20
Steps to Reproduce:
1. install the nitrogen paquet
2. have a fedora with openbox or not
3. running in single screen configuration
nitrogen-1.5.2-11.20140405git.fc20 has been submitted as an update for Fedora 20.
nitrogen-1.5.2-11.20140405git.fc19 has been submitted as an update for Fedora 19.
Thanks for reporting this :) The updates above should fix it.
nitrogen-1.5.2-11.20140405git.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
nitrogen-1.5.2-11.20140405git.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
unfortunatly this didn't help. There is still the same error messages . What is weird is that it's only happening in single screen layout.
Humph, confirmed. This is extra weird because when I tested it in a VM it worked fine.
nitrogen-1.5.2-13.fc19 has been submitted as an update for Fedora 19.
nitrogen-1.5.2-13.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing nitrogen-1.5.2-13.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
nitrogen-1.5.2-13.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
nitrogen-1.5.2-13.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
Unfortunatly this bug is still part of the actuallity. In Two screen layout no troubles. But if you use only one monitor, at every reboot the background switch to the default one.
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.