Description of problem: I'm using WindowMaker WM. Starting xscreensaver and using (blank screen only) is OK. After reboot, I need to run the settings again
Version-Release number of selected component (if applicable):
How reproducible: Constantly
Steps to Reproduce:
1. Run WindowMaker WM (?)
2. Open $ xscreensaver
3. Setup preferences - Blank screen only
4. Make sure it works
5. Reboot and check it out.
Steps to Reproduce:
lost screen saver settings after reboot
Does ~/.xscreensaver get created?
How is xscreensaver loaded after a reboot?
I log in windowmaker and there is ~/.xscreensaver file (see attachment).
Xscreensaver doesn't start automatically. I may start it from Applications -> Tools -> Screensaver (there is warning about deamon not running (see another attachment) or just Run -> xscreensaver
Created attachment 270 [details]
Created attachment 271 [details]
Xscreensaver deamon not running
@spturtle, should WindowMaker start xscreensaver when it's available?
Is the bug still there?
(In reply to comment #5)
> @spturtle, should WindowMaker start xscreensaver when it's available?
Could it? Can the bug be assigned to you?
Yes it's still here.
I installed WindowMaker on a top of GNOME installation. Xsreensaver was installed as well.
After reboot (login to WindowMaker), gnome-screensaver is running "undergruond" (not visible), I have to stop it anyway (demon?) and start xscreensaver after that.
pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED
Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.
Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW.
This bug was filed against cauldron, but we do not have cauldron at the moment.
Please report whether this bug is still valid for Mageia 2.
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.
Closing as OLD.