* Patricio Rojo <[email protected]> [2025-06-27 18:13]:
Thanks for the quick reply. Indeed, it was the same I did (but running in bookworm):sudo install snap
nit: sudo apt install snapd
sudo snap install core**** error: cannot communicate with server: Post "http://localhost/v2/snaps/core": dial unix /run/snapd.socket: connect: connection refused
I can't reproduce this on bookworm either.
Then, after an exhaustive search I found that the problem appeared with apparmor service failed to initiate as explained originally, after adding /usr/sbin to /etc/environment the problem disappeared.However(!), the plot thickens as I just deleted /usr/sbin from /etc/environment to try getting the error again, but it didn't reappear. So, my guess is that the correct path is now stored somewhere in the profiles thanks to apparmor-utils?
That sounds unlikely, you can check your system with: dpkg --verify It should show modifications to the apparmor profiles.
Anyways, I cannot reproduce anymore in my system :s.
Given that we both can't reproduce the problem, do you agree to downgrade the bug to normal?
Cheers Jochen
signature.asc
Description: PGP signature

