You are not logged in.
I updated the system (including archlinux-keyring), prepared to power off (including turning off the tethered network, hope that's not a problem), and then issued the `poweroff` command. Then, however, the shutdown hanged for a minute while waiting for something archlinux-keyring related to happen.
These seem to be the relevant journal contents
# journalctl | grep -E '^Jan 31 19:0' | grep -E -i -I 'keyring|g(nu)?pg' | grep -v -E '[^a-zA-Z_]audit[^a-zA-Z_]'
Jan 31 19:05:59 aceramd archlinux-keyring-wkd-sync[91783]: gpg: signal Terminated caught ... exiting
Jan 31 19:05:59 aceramd systemd[1]: Stopping Refresh existing keys of archlinux-keyring...
Jan 31 19:06:01 aceramd systemd[481]: Closed GnuPG network certificate management daemon.
Jan 31 19:06:01 aceramd systemd[481]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan 31 19:06:01 aceramd systemd[481]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Jan 31 19:06:01 aceramd systemd[481]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Jan 31 19:06:01 aceramd systemd[481]: Closed GnuPG cryptographic agent and passphrase cache.
Jan 31 19:07:30 aceramd systemd[1]: archlinux-keyring-wkd-sync.service: State 'final-sigterm' timed out. Killing.
Jan 31 19:07:30 aceramd systemd[1]: archlinux-keyring-wkd-sync.service: Killing process 91635 (dirmngr) with signal SIGKILL.
Jan 31 19:07:30 aceramd systemd[1]: archlinux-keyring-wkd-sync.service: Killing process 91784 (conn fd=5) with signal SIGKILL.
Jan 31 19:07:30 aceramd systemd[1]: archlinux-keyring-wkd-sync.service: Failed with result 'timeout'.
Jan 31 19:07:30 aceramd systemd[1]: Stopped Refresh existing keys of archlinux-keyring.
Jan 31 19:07:30 aceramd systemd[1]: archlinux-keyring-wkd-sync.service: Consumed 1min 33.114s CPU time.
Jan 31 19:07:30 aceramd systemd[1]: archlinux-keyring-wkd-sync.timer: Deactivated successfully.
Jan 31 19:07:30 aceramd systemd[1]: Stopped Refresh existing PGP keys of archlinux-keyring regularly.Seems to be something GPG-related. Any tips for preventing this from happening again?
Offline
it should not happen overly frequent and likely coincided with you disabling the network in the middle of it's operation. You could either adjust the timer to run at more reasonable times for you, or disable it at chance of increasing package installation issues due to outdated keyrings.
Offline