Note that the crash is fixed in 1.6 by http://bazaar.launchpad.net /~oxide-developers/oxide/1.6/revision/944 - in this case, Oxide will run in software compositing mode.
Marking 1.6 as Won't Fix, as the change in http://bazaar.launchpad.net /~oxide-developers/oxide/oxide.trunk/revision/1025 won't change that behaviour. This is because the mirserver QPA plugin doesn't allow Oxide to access the platform handle for the share context if one is provided (see https://code.launchpad.net/~mterry/oxide/mirserver/+merge/255128/comments/634515), which is required for GPU compositing. On trunk (1.7), Michael's change enables Oxide to use the EGLImage compositing path, but that doesn't exist in 1.6 (it requires http://bazaar.launchpad.net/~oxide- developers/oxide/oxide.trunk/revision/1017). ** Changed in: oxide/1.6 Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1439829 Title: Wizard crashes when trying to view HERE terms and conditions Status in Oxide Webview: Fix Released Status in Oxide 1.6 series: Won't Fix Status in oxide-qt package in Ubuntu: Fix Committed Status in oxide-qt package in Ubuntu RTM: Won't Fix Bug description: Flash like so: ubuntu-device-flash touch --channel=ubuntu-touch/devel-proposed- customized-here --wipe And you'll have the HERE bits on your phone. Now go through the wizard, click on the "terms and conditions" link on the location screen to see the Nokia terms. Your screen will seem frozen and unity8 will crash. This is what we see in the logs: [0402/192155:WARNING:oxide_qt_browser_startup.cc(161)] Unrecognized Qt platform: mirserver [0402/192155:ERROR:gl_implementation_osmesa.cc(22)] Failed to load /usr/lib/arm-linux-gnueabihf/oxide-qt/libosmesa.so: /usr/lib/arm-linux-gnueabihf/oxide-qt/libosmesa.so: cannot open shared object file: No such file or directory And it's because oxide expects the platform to start with "ubuntu" but unity8 translates "ubuntumirclient" to "mirserver" which oxide does not expect. So it falls back to non-GLES2 mode and can't find libosmesa.so, crashing. It's not clear to me *why* unity8 is doing that. But until we sort that out, oxide can simply support "mirserver" too. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1439829/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
