From: darmon77 <darmon77@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Tomb 2.8 error line 429, duplicate "getpasspass" output=$(pinentry_assuan_getpassgetpasspass | pinentry-curses)
Date: Mon, 14 Dec 2020 05:53:30 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27138@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2118 bytes --]
New issue by darmon77 on void-packages repository
https://github.com/void-linux/void-packages/issues/27138
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname: Void 5.9.13_1 x86_64 GNU/Linux Intel
* package: tomb-2.8_1
### Expected behavior
tomb open secreto.tomb -k secreto.tomb.key
tomb . Commanded to open tomb /home/darmon/secreto.tumb
tomb . Valid tomb file found: /home/darmon/secreto.tumb
tomb . Key is valid.
tomb . Mountpoint not specified, using default: /media/secreto
tomb (*) Opening faviola on /media/secreto
tomb . This tomb is a valid LUKS encrypted device.
tomb . Cipher is "aes" mode "xts-plain64:sha256" hash "sha256"
tomb . A password is required to use key /home/darmon/secreto.tomb.key
tomb . Password OK.
tomb (*) Success unlocking tomb secreto
tomb . Checking filesystem via /dev/loop1
fsck from util-linux 2.36
secreto: clean, 223/127512 files, 57720/509952 blocks
tomb (*) Success opening faviola.tumb on /media/secreto
tomb . Last visit by root(0) from /dev/pts/5 on Dennis
tomb . on date Mon Dec 14 15:43:14 2020
### Actual behavior
tomb open secreto.tomb -k secreto.tomb.key
tomb . Commanded to open tomb /home/darmon/secreto.tomb
tomb . Valid tomb file found: /home/darmon/secreto.tomb
tomb . Key is valid.
tomb . Mountpoint not specified, using default: /media/secreto
tomb (*) Opening faviola on /media/secreto
tomb . This tomb is a valid LUKS encrypted device.
tomb . Cipher is "aes" mode "xts-plain64:sha256" hash "sha256"
tomb . A password is required to use key /home/darmon/secreto.tomb.key
ask_password:59: command not found: pinentry_assuan_getpassgetpasspass
tomb [W] User aborted password dialog.
tomb [E] No valid password supplied.
### Steps to reproduce the behavior
**error line 429**
output=$(pinentry_assuan_getpassgetpasspass | pinentry-curses)
**Solution **
output=$(pinentry_assuan_getpass | pinentry-curses)
next reply other threads:[~2020-12-14 4:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 4:53 darmon77 [this message]
2020-12-14 7:35 ` biopsin
2020-12-14 13:23 ` ericonr
2020-12-14 17:44 ` biopsin
2020-12-14 17:50 ` ericonr
2020-12-14 18:09 ` darmon77
2020-12-15 14:13 ` [ISSUE] [CLOSED] " ericonr
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27138@inbox.vuxu.org \
--to=darmon77@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).