webbrowser-app and all other Qt apps trying to get an EGL handle, via Mir
then.
This means : should the policy be updated to have all Qt apps get this
access level ? or should that stay as a per-app decision ?
On Tue, Feb 21, 2017 at 8:44 PM, Seth Arnold <email address hidden>
wrote:
> If webbrowser-app needs access to nvidia hardware (does it?) using the
> <abstractions/nvidia> file is probably easier than figuring out each
> access one at a time.
>
> Thanks
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1590561
>
> Title:
> webbrowser-app crashes on startup on fresh zesty Unity8: No suitable
> EGL configs found
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590561/+
> subscriptions
>
webbrowser-app and all other Qt apps trying to get an EGL handle, via Mir
then.
This means : should the policy be updated to have all Qt apps get this
access level ? or should that stay as a per-app decision ?
On Tue, Feb 21, 2017 at 8:44 PM, Seth Arnold <email address hidden>
wrote:
> If webbrowser-app needs access to nvidia hardware (does it?) using the nvidia> file is probably easier than figuring out each /bugs.launchpad .net/bugs/ 1590561 /bugs.launchpad .net/canonical- devices- system- image/+ bug/1590561/ +
> <abstractions/
> access one at a time.
>
> Thanks
>
> --
> You received this bug notification because you are a bug assignee.
> https:/
>
> Title:
> webbrowser-app crashes on startup on fresh zesty Unity8: No suitable
> EGL configs found
>
> To manage notifications about this bug go to:
> https:/
> subscriptions
>