Re: [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found

Thanks Tyler! On Thu, Mar 16, 2017 at 4:16 AM, Tyler Hicks wrote: > ** Changed in: apparmor > Milestone: None => 2.12 > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/1590561 > > Title: > webbrowser-app

Re: [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found

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 <1590...@bugs.launchpad.net> wrote: >

Re: [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found

Interesting, and thanks for proposing a fix. I guess some further information will still be needed to understand whether to open the apparmor profile to access those, or if that is wrong from a confinement perspective. Can you find which Qt function and/or Oxide calls are made that trigger the

Re: [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found

@santosh: can you detail the apparmor denial, if any, that you experience when the app hangs? Also, when that happens, what are the function calls made by Oxide that trigger that ? Knowing which calls are made would probably help people on this thread to know where this breaks. (or hangs). On