- #Fedora 23 login goes straight to xscreensaver login how to
- #Fedora 23 login goes straight to xscreensaver login install
- #Fedora 23 login goes straight to xscreensaver login password
Maybe some other screen locking program that integrates with lightdm would provide a better user experience. One additional annoyance is that when you do have the correct value for "*newLoginCommand" set, you have to authenticate twice to get back into an existing session-once for lightdm and once for xscreensaver. Otherwise, it requires the user to learn a number of things to either override the system setting (preferred) or somehow have each user override the setting-something that will be hit and miss for user experience.Īnother approach might be to replace xscreensaver with some other locking program like light-locker that might have better defaults. I don't know if there is a convenient way for the Xfce Spin or the Xfce packages to override the default setting for "*newLoginCommand", but that would give the user a better experience. For the Xfce Spin that is using lightdm, This should be "dm-tool switch-to-greeter". The actual issue is that the wrong command is provided for "*newLoginCommand" in /etc/xscreensaver/XScreenSaver.ad. This is really a configuration issue than an actual functionality problem. The user is returned to the lightdm login screen to allow a second user to login to the computer.
#Fedora 23 login goes straight to xscreensaver login password
The "New Login" turns gray and nothing happens. Xscreensaver does not accept login password JD jd1008 at Sun May 13 07:42. Hit a key or move the mouse to turn on the xscreensaver authentication screen. Have the user lock the screen, turning on xscreensaver.ģ. In the Xfce Spin, have a user create a new login session.Ģ. Start Explorer (Win+E, or Start - Programs - NT Explorer) Move to the systemrootsystem32 directory (e.g. This has been very reproducible for at least a few releases of Fedora (I've tried it since about Fedora 30 or 31).ġ. 86_64 (though, this issue has been around for a while).
Version-Release number of selected component (if applicable): I could be wrong, but we should think carefully before changing the current default.When xscreensaver is active, the "New Login" button does not work, meaning that a second user cannot create a new login session if xscreensaver is active.
Yeah, but it has no timed idle lock that I know of. I do not think light-locker works with GDM though. If theres a way to make it go to the log in screen at the main greeter when it.
#Fedora 23 login goes straight to xscreensaver login how to
to login to a different session instead of the auto-lock screen, I found this link which shows how to configure the settings. > If the user uses light-locker instead of xscreensaver, one should get the For some reason Ubuntu uses the Xscreensaver thing which doesnt look right and should kick me to the lightdm greeter log in screen.
> There is a easier alternative though (assuming lightdm is already enabled). Reply-to: Community support for Fedora users(In reply to Mukundan Ragavan from comment #4) You cannot set a time limit to autolock like xscreensaver has. The problem is that lightdm/dm-tool lock only works when you explicitly run it or at suspend/resume. > spin should use lightdm for screen locking instead of xscreensaver, correct? > What remains for discussion on the mailing list is whether or not the Xfce
Trouble setting up screen sharing on Fedora 27 Desktop. After I enter my password on the lock screen (cold boot, resume from sleep, anytime) the cursor moves to the bottom corner and everything locks up for 30 seconds, then the login / lock screen shows again. Cant login in Fedora 20 (VM) to KDE after password change. Fedora 33 Workstation: Gnome login screen freezes after password, then goes back to lock screen.
#Fedora 23 login goes straight to xscreensaver login install
That happend when I install jdk 11.0.2 and set /etc/environment. > manually locking the screen to provide the user with the same experience as I wrote good login and password but i got back to logging panel. > That means there is no way to trigger GDM on resume from suspend or when > Thanks for shedding some light! Now it's way more clear to me how these (In reply to Robert Orzanna from comment #3)
0 kommentar(er)
