The particular key cannot be imported; it's not in public key servers yet.
On Mon, 21 Jun 2021, Eli Schwartz via arch-general wrote:
> On 6/21/21 11:36 PM, Jude DaShiell via arch-general wrote:
> > Pacman could do with a feature to bypass authors packages and keys so
> > those don't disrupt upda
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On Mon, 21 Jun 2021, Jude DaShiell via arch-general wrote:
Pacman could do with a feature to bypass authors packages and keys so
those don't disrupt updates.
IMO, ignoring signatures is a severe security issue and should not be
done light-
On 6/21/21 11:36 PM, Jude DaShiell via arch-general wrote:
> Pacman could do with a feature to bypass authors packages and keys so
> those don't disrupt updates.
They don't disrupt updates. The keys are updated via archlinux-keyring,
or via an "Import this key?" prompt via WKD / the SKS pool.
If
Pacman could do with a feature to bypass authors packages and keys so
those don't disrupt updates.
Now I know, what causes the problems:
$ ps ax | grep xsettingsd
1212 tty1 Z 0:00 [xsettingsd]
So, where can I find the error detail message?
Regards
P.
Am 21.06.21 um 20:00 schrieb Peter Nabbefeld via arch-general:
After some investigation, it seems to be caused by some missing
After some investigation, it seems to be caused by some missing GTK
updates/configuration changes:
- I've installed GTK2 and GTK3
- I just noticed GTK4 is available, but not installed
- Only 3 themes are available, which seem to be integrated with GTK3+
recently.
So /usr/share/themes probably ev
