← Back to team overview

touch-packages team mailing list archive

[Bug 1365673] Re: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene:6:qt_message_fatal:QMessageLogger::fatal: UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPlugin::create:loadIntegration

 

This bug consistently evades me. I've spent much time trying to
reproduce this to no avail.

This fail will occur if mir client process are *not* launched via
ubuntu-app-launch - as unity8 will not accept mir connections it doesn't
expect, causing the client to crash with this error. The obvious
possibility is a race where unity8 is informed of a client launch only
after client tries to connect - but the logs don't indicate this.

There could be a bug somewhere in the stack causing a client to be
launched twice, the first will be accepted, the second rejected and
crashing. The logs do seem to indicate this possibility, but I cannot
pinpoint where.

Logs from ubuntu-app-launch & upstart might help shed light.
Any suggestions on increasing the odds of reproducing this would be appreciated.

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

Title:
  /usr/lib/arm-linux-
  gnueabihf/qt5/bin/qmlscene:6:qt_message_fatal:QMessageLogger::fatal:
  UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPlugin::create:loadIntegration

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Qt integration with the Mir display server:
  Triaged
Status in QT Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete
Status in qtmir package in Ubuntu RTM:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding qtdeclarative-opensource-src.  This problem was most
  recently seen with version 5.3.0-3ubuntu10, the problem page at
  https://errors.ubuntu.com/problem/4618cad07e610ca3c59a3e07c582e963d4780359
  contains more details.

  steps to reproduce:
  run the lrt switch test

  1. open a bunch of apps
  2. swipe the screen to show the app selector
  3. pick an app at random
  4. swipe the screen again to show the app selector
  5. pick an app at random
  6. repeat steps 2-5 until crash shows in /var/log

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1365673/+subscriptions


References