On Wed, 17 Sep 2025 20:10:35 +0800 ChangZhuo Chen (陳昌倬) <[email protected]> wrote:
> On Wed, Sep 17, 2025 at 02:00:31PM +0200, Stefano Brivio wrote: > > On Wed, 17 Sep 2025 19:47:05 +0800 > > ChangZhuo Chen (陳昌倬) <[email protected]> wrote: > > > On Wed, Sep 17, 2025 at 12:49:26PM +0200, Stefano Brivio wrote: > > > > 4. if 3. doesn't change anything, disable AppArmor altogether > > > > (temporarily, just for the test!) with 'aa-teardown', and try again? > > > > > > > > > > It works after `aa-teardown`: > > > > > > $ sudo aa-teardown > > > Unloading AppArmor profiles > > > > > > $ pasta -- true > > > No interfaces with usable IPv4 routes > > > No interfaces with usable IPv6 routes > > > > So it's AppArmor, but I can't reproduce this with the current policy (I > > still have to try with a fresh re-install of the package though). > > pasta does not creash with SIGSEGV after I successful run it after > `aa-teardown`, even with AppArmor enabled (check via `systemctl > status apparmor`). It's actually not pasta itself crashing, as it doesn't even start. It seems to be the shell, for whatever reason. But anyway, that doesn't matter much. > > ...oops, sorry, I meant to ask if you could try with > > 'aa-complain pasta' instead of aa-enforce (also as root or with sudo, > > I forgot to mention). > > $ sudo aa-complain pasta > Setting /usr/bin/pasta to complain mode. > Warning: profile pasta represents multiple programs > Warning: profile pasta represents multiple programs ...and, sorry, I took it for granted: try to run pasta after 'sudo aa-complain pasta'? -- Stefano
