|Summary:||x11/cinnamon-screensaver does not unlock|
|Product:||Ports & Packages||Reporter:||Usama Khan <usama.cit>|
|Component:||Individual Port(s)||Assignee:||freebsd-gnome (Nobody) <gnome>|
|Severity:||Affects Many People||CC:||vishwin|
Description Usama Khan 2021-02-27 16:58:12 UTC
x11/cinnamon (4.8.6) session does not unlock. Steps to reproduce: 1. Do a fresh install of FreeBSD. 2. Install x11/cinnamon (4.8.6) and x11/lightdm. 3. Lock screen (or leave for some time so that the session locks by itself). 4. Try to unlock, the session will not unlock whatsoever. 5. Switch to TTY1, and it will show following message: "gnome-keyring-daemon: couldn't initialize slot with master password: The password or PIN is incorrect 6. The only way to recover is to either kill X Server or Reboot.
Comment 1 Charlie Li 2021-02-27 19:24:28 UTC
This is a known issue, for us, since at least 4.0, regardless of display manager or lack thereof. It is a bit of a heisenbug because I suspect there are various PAM idiosyncrasies involved as well, given that we use OpenPAM whereas they expect Linux-PAM. Unfortunately, the workaround for now is to disable screen locking in screensaver settings (the screensaver itself still works). As such, this is probably more appropriate for x11/cinnamon-screensaver than x11/cinnamon.
Comment 2 Usama Khan 2021-02-28 11:59:49 UTC
(In reply to Charlie Li from comment #1) As you've mentioned that the topic is appropriate for "x11/cinnamon-screensaver", so is changing the "Topic" is enough? or Does only a Moderator can assign it to "x11/cinnamon-screensaver"?
Comment 3 Charlie Li 2021-03-01 00:28:33 UTC
(In reply to Usama Khan from comment #2) Good enough. The subject is only for automating the initial assignee instead of a generic nobody@. As for the issue itself, this will probably go upstream once I get a better understanding of what's happening in the background.