3

Ubuntu 18.04.4 LTS

I've been ignoring this for months because it's just an annoyance, but does anyone know of an easy way to stop these messages from flooding my dmesg?

audit: type=1400 audit(1592907153.756:165): apparmor="DENIED" operation="file_mmap" profile="/snap/core/9289/usr/lib/snapd/snap-confine" name="/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0" pid=19919 comm="snap-confine" requested_mask="m" denied_mask="m" fsuid=0 ouid=0

I'd appreciate it. Thanks.

1 Answer 1

0

This is apparently a known issue:

"A workaround could be to avoid snap run and call node from /snap/node/current/... instead of through /snap/bin/node."

But to directly answer your question: "This is a limitation in apparmor itself, where we cannot say that snap-confine can inherit and pass a file descriptor to another process, whatever that file may be." (source)

You will find further explanations in the bug report. Discussions are ongoing.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .