From: Theodor Thornhill via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 64807@debbugs.gnu.org
Cc: Michael Albinus <michael.albinus@gmx.de>
Subject: bug#64807: 30.0.50; Editing files using sudo with fprintd hangs
Date: Sun, 23 Jul 2023 18:28:34 +0200 [thread overview]
Message-ID: <87edkyr3rh.fsf@thornhill.no> (raw)
Hi Emacs (and Michael, forgive me if this isn't relevant for you)
I'm using Ubuntu on a thinkpad with fingerprint scanner, and have
enabled it to be used when sudo is invoked, setting it in pam.d. Fprintd
is the program (I believe) that checks the fingerprint.
To make the issue a little clearer, I'll show an example that works like
intended in Emacs, and the one that does not.
Both
This works:
1. M-x eshell
2. type "sudo ls" then RET
3. observe that eshell prompts:
"Place your finger on the fingerprint reader"
4. If fingerprint is wrong or you wait for some period (10 seconds I
believe) it falls back to normal.
See example prompt:
```
$ sudo ls
Place your finger on the fingerprint reader
Cargo.lock Cargo.toml src target
$ sudo ls
Place your finger on the fingerprint reader
Verification timed out
[sudo] password for theodor:
Cargo.lock Cargo.toml src target
```
This doesn't work as intended:
1. C-x C-f /sudo:Theodor:/ RET
2. Observe that Emacs appears to be hanging
- the cursor is now spinning, and "C-x o" and friends doesn't work
3. Scan fingerprint
- all is ok
4. Wait for timeout
- enter password
- all is ok
So to sum up - in the eshell case we get some indication to scan the
fingerprint, in the sudo/tramp case we don't. Everything works as it
should, in that verification passes, but the UI is confusing, and it
appears to hang for other commands. C-g works.
Is there some way for Emacs to prompt for the fingerprint to be scanned,
and not to freeze up?
Let me know if I need to provide more information :)
Thanks,
Theo
next reply other threads:[~2023-07-23 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 16:28 Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-07-23 17:21 ` bug#64807: 30.0.50; Editing files using sudo with fprintd hangs Michael Albinus
2023-08-28 11:00 ` Michael Albinus
2023-09-17 7:11 ` Michael Albinus
[not found] ` <handler.64807.D64807.169493471128129.notifdone@debbugs.gnu.org>
2023-09-17 8:19 ` bug#64807: closed (Re: bug#64807: 30.0.50; Editing files using sudo with fprintd hangs) Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edkyr3rh.fsf@thornhill.no \
--to=bug-gnu-emacs@gnu.org \
--cc=64807@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=theo@thornhill.no \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).