From: Oleander via <help-guix@gnu.org>
To: manu@beffara.org, remco@remworks.net, help-guix@gnu.org
Subject: Re: swaylock does not accept my correct password and fails to unlock
Date: Mon, 25 Dec 2023 08:58:31 +0000 [thread overview]
Message-ID: <tdwdV1C_QcnMjNJ2dW9719P23SE3piN6UVV9h2p6fUYrX5_9tk3qIu9VjeD_wxBIDs_8NlIDbYKEkYW5CFEG3XcnnSPhIOYoQ48D2J1TLcA=@protonmail.com> (raw)
In-Reply-To: <20231222092405.GE1380@beffara.org>
I added the suggested entry and now swaylock works fine.
Thanks Emmanuel and Remco for helping!-------- Original Message --------
On Dec 22, 2023, 09:24, Emmanuel Beffara wrote:
> Hello, De Remco van 't Veer le 22/12/2023 à 08:56: > This works for me but I am not sure it's still needed. I am pretty sure > swaylock does not like to be setuid anymore. I faced the same issue some time ago, not sure when. Indeed the issue was with swaylock complaining about setuid. My system configuration contains the following simpler entry, which uses screen-locker-configuration: (operating-system ... (services (cons* ... (service screen-locker-service-type (screen-locker-configuration (name "swaylock") (program (file-append swaylock "/bin/swaylock")) (using-pam? #t) (using-setuid? #f))) ... %desktop-services)) ... ) -- Emmanuel
prev parent reply other threads:[~2023-12-28 18:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 14:09 swaylock does not accept my correct password and fails to unlock Oleander via
2023-12-22 7:56 ` Remco van 't Veer
2023-12-22 8:24 ` Emmanuel Beffara
2023-12-22 8:57 ` Remco van 't Veer
2023-12-22 14:20 ` Oleander via
2023-12-22 15:10 ` Remco van 't Veer
2023-12-22 15:10 ` Emmanuel Beffara
2023-12-25 8:58 ` Oleander via [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='tdwdV1C_QcnMjNJ2dW9719P23SE3piN6UVV9h2p6fUYrX5_9tk3qIu9VjeD_wxBIDs_8NlIDbYKEkYW5CFEG3XcnnSPhIOYoQ48D2J1TLcA=@protonmail.com' \
--to=help-guix@gnu.org \
--cc=7059548@protonmail.com \
--cc=manu@beffara.org \
--cc=remco@remworks.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.