Comment 23 for bug 1464958

Revision history for this message
Mikko Rauhala (mjr-iki) wrote :

This is still a problem. I'm having the exact same issue (though on google-chrome-stable-44.0.2403.125-1 )

Adding

  /opt/google/chrome/chrome Cx -> chromium,
  /opt/google/chrome/chrome-sandbox Cx -> chromium,

to /etc/apparmor.d/abstractions/lightdm_chromium-browser did not help (I tried that in case it was a matter of yet more filename changes on google's packaging).

google-chrome --no-sandbox works around the issue, with obvious usability (manual startup or manual configuration of switch), stability and security drawbacks.