[pkg-apparmor] Bug#1108358: “apparmor_parser”: executable file not found in $PATH

[Patricio Rojo]

Hi Jochen,

   I'll be happy to try helping digging up the root of the error and 
agree with the change of severity.

   This is the relevant output of 'dpkg --verify' grepping for snap or app:

missing  /usr/share/dbus-1/services/io.snapcraft.Prompt.service
??5?????? c /etc/apparmor.d/usr.sbin.ntpd
??5?????? c /etc/apparmor.d/usr.sbin.mysqld
missing     /var/cache/app-info
missing     /var/cache/app-info/xmls

   Let me know about anything else you might need.


        Pato



On 6/28/2025 2:15 AM, Jochen Sprickerhof wrote:
> * Patricio Rojo <pato at das.uchile.cl> [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