There are several separate issues here, and it doesn’t help that they are being tracked in the same place.
IIUC, the issue with the webbrowser-app snap on unity8 needs to be addressed in unity8 by relaxing the confinement that will allow apps to create a QOpenGLContext ("/dev/dri/*"?). It’s unclear to me whether the changes need to happen in unity8 itself, or in the "mir"/"unity8" interface definitions in snapd.
Regarding the other issue, the apparmor profile for webbrowser-app needs to be updated to use the ibus and nvidia abstractions. The profile is generated from a manifest, see https://bazaar.launchpad.net/~phablet-team/webbrowser-app/trunk/view/head:/debian/webbrowser-app-apparmor.manifest. IIUC, this won’t be sufficient to fix the issue, as the nvidia abstraction also needs to be updated. /etc/apparmor.d/abstractions/nvidia belongs to the apparmor package.
There are several separate issues here, and it doesn’t help that they are being tracked in the same place.
IIUC, the issue with the webbrowser-app snap on unity8 needs to be addressed in unity8 by relaxing the confinement that will allow apps to create a QOpenGLContext ("/dev/dri/*"?). It’s unclear to me whether the changes need to happen in unity8 itself, or in the "mir"/"unity8" interface definitions in snapd.
Regarding the other issue, the apparmor profile for webbrowser-app needs to be updated to use the ibus and nvidia abstractions. The profile is generated from a manifest, see https:/ /bazaar. launchpad. net/~phablet- team/webbrowser -app/trunk/ view/head: /debian/ webbrowser- app-apparmor. manifest. IIUC, this won’t be sufficient to fix the issue, as the nvidia abstraction also needs to be updated. /etc/apparmor. d/abstractions/ nvidia belongs to the apparmor package.