Hello everybody.
I’m experiencing since yesterday a higher time for booting (I know, it’s silly, but being new to Garuda I still like checking systemd-analyze daily).
It used to be 17-20s and now 35-40s, always and only due to pacman-init.service taking 25-30s.
I searched in the forum, in the Arch forum and the Internet in general, but I wasn’t able to find anything useful for me.
All the services are running, pacman-init.service executes and exits without errors.
Yesterday the sudo pacman -Syu upgraded the following (taken from pacman.log):
We have lots of issues with the PGP keys currently which could be solved by these systemd services maybe as it initializes the keyring on each boot, opinions?
╭─nico@T440p in ~ took 154ms
╰─λ cat /etc/systemd/system/pacman-init.service
File: /etc/systemd/system/pacman-init.service
# SPDX-License-Identifier: GPL-3.0-or-later
[Unit]
Description=Initializes Pacman keyring
Wants=haveged.service
After=haveged.service
Requires=etc-pacman.d-gnupg.mount
After=etc-pacman.d-gnupg.mount
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/bin/pacman-key --init
ExecStart=/usr/bin/pacman-key --populate chaotic
ExecStart=/usr/bin/pacman-key --populate archlinux
[Install]
WantedBy=multi-user.target
and the other one
╰─λ cat /etc/systemd/system/etc-pacman.d-gnupg.mount
File: /etc/systemd/system/etc-pacman.d-gnupg.mount
# SPDX-License-Identifier: GPL-3.0-or-later
[Unit]
Description=Temporary /etc/pacman.d/gnupg directory
[Mount]
What=tmpfs
Where=/etc/pacman.d/gnupg
Type=tmpfs
Options=mode=0755
Yes indeed, enabled it to prevent those countless posts regarding gpg key issues. Once we have new builders this will inevitably happen again as they use different keys to sign the packages
Well, I just tested bootup time, no noticable change of the time taken for reaching the desktop - yes, pacman-init still runs after reaching the desktop but thats only noticed by people running systemd-analyse blame . So I dont really feel the need to change that.
OK, I see.
So probably the time to reach the desktop is not changing (or at least changing much) for me too and that service continued in parallel after reaching the desktop.
So maybe I just discovered it doing the systemd-analyze and then blame due to the changed time, but as I said above "not a big issue" (now I understand why I didn't feel it as such ).
Sorry if I spoke out of turn, I didn't realize you guys had it enabled by default for that reason. Any posts on the Arch forum regarding the service seemed to indicate it was not needed on a system once installed.