With password screen saver doesn't need password to unlock Without password does ask for it. They are mixed up.
This is dupped by BUG #121
*** Bug 121 has been marked as a duplicate of this bug. ***
This is excellent, you marked both bugs as dups of each other without any notice of it being resolved, yet both of them are closed.
*** Bug 1525 has been marked as a duplicate of this bug. *** in RH's AfterStep the start/Screen_savers submenus seem to have reverse meanings so that when one tries to start a screen saver with password a screen saver without password is started and vice versa. -- aspa ------- Additional Comments From seva.uic.edu 03/18/99 11:57 ------- This is another dup of bug #12 /Seva ------- Additional Comments From seva.uic.edu 03/18/99 12:01 ------- This is another dup of bug #12 /Seva
*** Bug 724 has been marked as a duplicate of this bug. *** The /usr/share/afterstep/fixed/start/Screen_savers/With_password directory contain files/commands that invoke the xlock without password, while /usr/share/afterstep/fixed/start/Screen_savers/Without_passw ord directory contain files/commands that invoke xlock with password. The names of these two directories should be swapped. ------- Additional Comments From dkl 01/07/99 15:41 ------- This has been verified to be true on a machine in the test lab. The files are backwards from they way they should be. This has been assigned to a developer.fixed in AfterStep-1.7.75-1 (RawHide).
*** Bug 630229 has been marked as a duplicate of this bug. ***
Commits pushed to master at https://github.com/openshift/origin https://github.com/openshift/origin/commit/5efdc671055eab97ea6b887c875fb954cb01fcf7 fix issue#12. Give some slack for etcd to come alive. https://github.com/openshift/origin/commit/5d26b0caee3138abe820ef65bb620365314c7d29 Merge pull request #14 from rajatchopra/master fix issue#12. Give some slack for etcd to come alive.