1. All entries from `lsof -Ua | grep screen` are owned by my usual user 2. This issue is occurring on a mac Mojave system; SELinux is not available, or the utility `setenforce`.
Any other suggestions? A previous thread in the mailing list (https://lists.gnu.org/archive/html/screen-users/2016-10/msg00008.html <https://lists.gnu.org/archive/html/screen-users/2016-10/msg00008.html>) suggested simply editing the source to eliminate the authentication function; unfortunately, the code has changed significantly since then and I wasn’t able to locate the relevant function anymore. Additionally, this bug report appears to be relevant too: https://savannah.gnu.org/bugs/?59878 <https://savannah.gnu.org/bugs/?59878> Thanks > On 28 Dec 2022, at 20:55, Robin Lee Powell <robinleepow...@gmail.com> wrote: > > You've basically got two options here that I can think of: > > 1. Your screen socket, or the directory it's in, is owned by a > different user; go looking at ownership. "root" or "nobody" > seem likely options. > > 2. SELinux is getting involved. While you should *not* run like > this long term, you can test this by running "sudo setenforce 0" > and trying again. > > On Tue, Dec 27, 2022 at 05:01:35AM +0000, Lavd Asir wrote: >> Hello, >> >> I’ve recently started using the master version and whenever I try to >> re-attach a screen session, I am prompted with the following: >> >> `screen used by XXX <YYY> on ZZZ` >> >> Then it asks for a password. The password for my username (and the only user >> on this machine) doesn’t work, it prints `Password incorrect` and exits. >> >> I used to use an older version of screen before, and I could reattach >> without a password prompt. >> >> Note that in this scenario screen is not Locked (via `C-a x`), just simply >> detached (`C-a d`). >> >> I am unable to reattach any screen session, what can I do? >> >> Operating system is Mojave. >> >> Thank you
