Chromium continues to fail on Xenial with the title error message when the currently-shipped AppArmor profile is enforced.
I've updated my profile adjustments to address some new issues that have cropped up in recent builds of Chromium. Everyone who wants to get things working again, please add the following lines to /etc/apparmor.d/local/usr.bin.chromium-browser : # From https://bugs.launchpad.net/bugs/1471645 #include <abstractions/dbus> capability sys_admin, capability sys_chroot, capability sys_ptrace, owner @{PROC}/[0-9]*/setgroups w, owner @{PROC}/[0-9]*/gid_map w, owner @{PROC}/[0-9]*/uid_map w, @{PROC}/[0-9]*/stat r, @{PROC}/sys/net/ipv4/tcp_fastopen r, /bin/which ixr, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471645 Title: [trusty] [regression] chromium-browser crashed with SIGABRT in base::debug::BreakDebugger() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1471645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs