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

[Patricio Rojo]

Dear Jochen,

Thanks for the quick reply. Indeed, it was the same I did (but running 
in bookworm):

sudo install snap
sudo snap install core

**** error: cannot communicate with server: Post 
"http://localhost/v2/snaps/core": dial unix /run/snapd.socket: connect: 
connection refused

---

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?

---

Anyways, I cannot reproduce anymore in my system :s.


Thanks!

    Pato




On 6/27/2025 1:55 AM, Jochen Sprickerhof wrote:
> Control: tag -1 moreinfo
>
> Hi Patricio,
>
> * Patricio Rojo <ss2 at wasabi.das.uchile.cl> [2025-06-26 14:56]:
>> Package: apparmor
>> Version: 3.0.8-3
>> Severity: grave
>> Justification: renders package unusable
>>
>> While trying to run snap I get the following error:
>>
>> """
>> cannot run daemon: state startup errors: [cannot reload snap-confine 
>> apparmor profile: cannot load apparmor profiles: exec: 
>> "apparmor_parser": executable file not found in $PATH
>> apparmor_parser output:
>> ]
>> """
>>
>> the easy solution is to manually add /usr/sbin to /etc/environment, 
>> but I doubt is the correct approach and it is hard to find that 
>> solution.  I hope I'm submitting the bug to the right package.
>
> Can you give more detailed instructions how to reproduce this?
>
> Do you mean snap as in /usr/bin/snap from the snapd package or a 
> specific snap?
>
> This works for me in a fresh trixie VM:
>
> sudo install snap
> sudo snap install hello-world
> hello-world
>
> Cheers Jochen