That denial might be the relevant one: Sep 26 14:49:10 ubuntu kernel: [ 53.916666] audit: type=1400 audit(1411735750.942:62): apparmor="DENIED" operation="socket_shutdown" profile="/usr/lib/chromium-browser/chromium- browser//chromium_browser_sandbox" pid=2965 comm="chrome-sandbox" family="unix" sock_type="stream" protocol=0 requested_mask="shutdown" denied_mask="shutdown" addr=none
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1374363 Title: Chromium profile prevents chromium-browser from starting (Could not close socketpair: Permission denied) Status in “apparmor” package in Ubuntu: Incomplete Bug description: When setting /etc/apparmor.d/usr.bin.chromium-browser to enforced mode, chromium browser no longer starts on fully updated utopic as of today. In the previous weeks this worked without problems, so something broke recently. With chromium in enforced mode I get "Could not close socketpair: Permission denied" when trying to launch chromium-browser. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1374363/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
