Pkcon refresh: Key is stored in legacy trusted.gpg keyring

Because discover-plasma is not starting I use the terminal. when I

pkcon refresh

I get a fatal error since this evening…

fatal error: W: file:/var/lib/preinstalled-pool/dists/jammy/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

With the following lines about ppa’s not (yet) available

E: Index of /freecad-maintainers/freecad-stable/ubuntu jammy InRelease is not (yet) available (503 Service Unavailable [IP: 185.125.190.80 443])
E: Index of /libreoffice/ppa/ubuntu jammy InRelease is not (yet) available (503 Service Unavailable [IP: 185.125.190.80 443])
E: Index of /mozillateam/ppa/ubuntu jammy InRelease is not (yet) available (503 Service Unavailable [IP: 185.125.190.80 443])
E: Index of /pipewire-debian/pipewire-upstream/ubuntu jammy InRelease is not (yet) available (503 Service Unavailable [IP: 185.125.190.80 443])
E: Index of /pipewire-debian/wireplumber-upstream/ubuntu jammy InRelease is not (yet) available (503 Service Unavailable [IP: 185.125.190.80 443])
E: Index of /saiarcot895/chromium-beta/ubuntu jammy InRelease is not (yet) available (503 Service Unavailable [IP: 185.125.190.80 443])

Is this something to worry about?

No, the first is just a message that this method of key storage is going away at some point in the future.
(you can disable or delete the unused repo file /etc/apt/sources.list.d/preinstalled-pool.list which will remove the warning message)

The second was from an outage on the PPA servers earlier in the day. It should be back up now, or it is for me.

2 Likes

Thanks!

I tested just a minute ago and you’re correct: PPA servers back up and running