touch-packages team mailing list archive

[Michael Terry <michael.terry@xxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: oxide-qt (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: unity8 (Ubuntu)
     Importance: Undecided
         Status: New

** Branch linked: lp:~mterry/oxide/mirserver

** Also affects: oxide-qt (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1439829

Title:
  Wizard crashes when trying to view HERE terms and conditions

Status in oxide-qt package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

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/ubuntu/+source/oxide-qt/+bug/1439829/+subscriptions