pacman -S archlinux-keyring Hangs in Arch Linux Termux PRoot

[SDRausty]

This error is important for aarch64 and armv7 users. Arch Linux in Termux PRoot x86_64 users are saying that this error is critical on their devices. Is this a PRoot issue?

$ pacman -S archlinux-keyring
warning: archlinux-keyring-20180108-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) archlinux-keyring-20180108-1

Total Installed Size:  0.90 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring                         [############################] 100%
(1/1) checking package integrity                       [############################] 100%
(1/1) loading package files                            [############################] 100%
(1/1) checking for file conflicts                      [############################] 100%
(1/1) checking available disk space                    [############################] 100%
:: Processing package changes...
(1/1) reinstalling archlinux-keyring                   [############################] 100%
==> Appending keys from archlinux.gpg...
==> Locally signing trusted keys in keyring...
  -> Locally signing key DDB867B92AA789C165EEFA799B729B06A680C281...

The process hangs forever on all architectures. I've tried:

cat startarch
#!/bin/bash -e
unset LD_PRELOAD
set PROOT_NO_SECCOMP=1
set PROOT_VERBOSE=9
exec proot --link2symlink -0 -r /data/data/com.termux/files/home/arch/ -b /dev/ -b /sys/ -b /proc/ -b /storage/ -b /data/data/com.termux/files/home -w /data/data/com.termux/files/home /bin/env -i HOME=/root TERM="xterm-256color" PS1='[termux@arch \W]$ ' LANG=en_US.UTF-8 PATH=/bin:/usr/bin:/sbin:/usr/sbin /bin/bash --login

Reference SDRausty/TermuxArch#33 pacman-key --populate archlinux hangs #33

[michalbednarski]

I yet have to figure out why, but it looks that smartcard daemon hangs. For now this can be worked around with:

mv /usr/lib/gnupg/scdaemon{,_}

[michalbednarski]

-> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
Hung?

Looks like you've restored scdaemon with pacman -S gnupg, remove it again and make sure scdaemon is not running before running pacman-key --populate

Termux command prompt never returned after proot logout. How can I get more information on what is going on?

Not all processes that were inside proot have exited (e.g. gpg-agent), make sure they aren't running or use proot --kill-on-exit to automatically kill remaining background processes when main process exits (See #3 for info about --kill-on-exit.

[michalbednarski]

Forget about removing scdaemon executable, I've found official way:

pacman-key --init
echo disable-scdaemon > /etc/pacman.d/gnupg/gpg-agent.conf
pacman-key --populate