[07:21] <juergh> facemyer, best to open a bug. Run 'ubuntu-bug linux' on the affected machine.
[16:54] <nteodosio> Could someone please have a look at bug 1996217? I suspect it is kernel related given the nature of the logs.
[16:54] -ubottu:#ubuntu-kernel- Bug 1996217 in chromium-browser (Ubuntu) "SIGTRAP on launch 109.0.5396.2-2184" [Undecided, New] https://launchpad.net/bugs/1996217
[17:33] <sarnold> nteodosio: my wild guess is that whoever owns the chromium snap needs to fiddle with the yaml to ask for the perfmon capability in appamor policy or the pkey_mprotect() syscall in their seccomp policy
[17:38] <ogra> sarnold, luckily snaps can not "fiddle with apparmor or seccomp policy" ...
[17:38] <ogra> else the security model woud be pointless 😉
[17:38] <sarnold> ogra: well okay then the owner needs to ask you to ask amurray to allow it when he returns from vacation :)
[17:38] <ogra> nteodosio, you want to file a feature request or bug against snapd to get that included in some interface
[17:39] <ogra> sarnold, correct 🙂
[17:39] <nteodosio> Thank you for the pointers! I'll follow your advice.
[17:40] <ogra> nteodosio, though if it actually exists in some interface already, the snappy-debug tool would know ... try running it side by side with the browser
[17:41] <nteodosio> Will do!