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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1365673/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
