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

Bug #1365673 reported by errors.ubuntu.com bug bridge
82
This bug affects 4 people
Affects Status Importance Assigned to Milestone
qtmir (Ubuntu)
Fix Released
High
Gerry Boland
qtmir (Ubuntu RTM)
Fix Released
High
Unassigned
qtubuntu (Ubuntu)
Fix Released
High
Gerry Boland
unity8 (Ubuntu)
Invalid
High
Gerry Boland

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

Related branches

tags: added: qa-daily-testing qasoak rtm14
affects: qtdeclarative-opensource-src (Ubuntu) → qtubuntu (Ubuntu)
Revision history for this message
Chris Gagnon (chris.gagnon) wrote :
Revision history for this message
Chris Gagnon (chris.gagnon) wrote :
Revision history for this message
Chris Gagnon (chris.gagnon) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in qtubuntu (Ubuntu):
status: New → Confirmed
Revision history for this message
kevin gunn (kgunn72) wrote :
Changed in unity8 (Ubuntu):
importance: Undecided → High
status: New → Triaged
Changed in qtmir:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Gerry Boland (gerboland)
Changed in unity8 (Ubuntu):
assignee: nobody → Gerry Boland (gerboland)
kevin gunn (kgunn72)
tags: added: touch-2014-10-16
kevin gunn (kgunn72)
Changed in qtubuntu:
assignee: nobody → Gerry Boland (gerboland)
Changed in qtubuntu (Ubuntu):
assignee: nobody → Gerry Boland (gerboland)
importance: Undecided → High
Changed in qtubuntu:
importance: Undecided → High
kevin gunn (kgunn72)
tags: added: touch-2014-10-30
removed: touch-2014-10-16
Revision history for this message
Gerry Boland (gerboland) wrote :

This is message from a client trying to start, and unity8 either not expecting it and thus rejecting the client connection, or due to bug 1368101. Hard to know for certain

kevin gunn (kgunn72)
Changed in qtubuntu:
status: New → Triaged
Revision history for this message
Chris Gagnon (chris.gagnon) wrote :

The fix from bug #1368101 is in the 20141008.1 rtm image, it did not fix the issue.
see:
https://errors.ubuntu.com/oops/5eb5f232-4f2d-11e4-9ea7-fa163e4aaad4

description: updated
Changed in qtmir:
importance: High → Critical
Changed in qtubuntu:
importance: High → Critical
Changed in qtubuntu (Ubuntu):
importance: High → Critical
Changed in unity8 (Ubuntu):
importance: High → Critical
Revision history for this message
Victor Tuson Palau (vtuson) wrote :

not able to reproduce in my phone..

Revision history for this message
Gerry Boland (gerboland) wrote :

I've spent some time at this bug, running automated and random input tests to try reproduce it. I've found 1 probable cause for this issue: url-dispatcher starts apps if they're not running - and it appears to be possible that AppMan is told to respawn the same app around the same time - causing 2 instances of the same app to be executed - one of which AppMan will reject. I had this happen once anyway.

I suspect there's another issue causing this bug too (going by log file output anyway). Am still investigating.

So far, I've been unable to reproduce any user-facing fault related to this issue - AppMan is only rejecting a second instances of an app running.

Revision history for this message
Chris Gagnon (chris.gagnon) wrote :

I didn't see this in the 20141010.1 image on the krillin, the tests ran over a 3 day weekend.

Olli Ries (ories)
Changed in qtmir:
status: Triaged → Incomplete
Changed in qtubuntu:
status: Triaged → Incomplete
Revision history for this message
Olli Ries (ories) wrote :

marked incomplete based on comment #10, reopen when reproducable again

Changed in qtubuntu (Ubuntu):
status: Confirmed → Incomplete
Changed in unity8 (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Chris Gagnon (chris.gagnon) wrote :

I was able to reproduce this by putting the phone in flight mode and repeatedly opening the gmail app

https://errors.ubuntu.com/oops/e3efce40-5ae1-11e4-a164-fa163e339c81

Revision history for this message
Chris Gagnon (chris.gagnon) wrote :

this happened 19 times yesterday in the long running tests

Changed in unity8 (Ubuntu):
status: Incomplete → Confirmed
Changed in qtubuntu (Ubuntu):
status: Incomplete → Confirmed
Changed in qtubuntu:
status: Incomplete → Confirmed
Changed in qtmir:
status: Incomplete → Confirmed
Revision history for this message
Chris Gagnon (chris.gagnon) wrote :
Revision history for this message
kevin gunn (kgunn72) wrote :

marking as high per RTM bug review

Changed in qtmir:
importance: Critical → High
Changed in unity8 (Ubuntu):
importance: Critical → High
Changed in qtubuntu (Ubuntu):
importance: Critical → High
Olli Ries (ories)
Changed in qtubuntu:
importance: Critical → High
kevin gunn (kgunn72)
tags: added: ota-2
removed: touch-2014-10-30
tags: added: ota-1
removed: ota-2
Revision history for this message
Ying-Chun Liu (paulliu) wrote :

If using trunk version it doesn't crash at all.

Olli Ries (ories)
Changed in canonical-devices-system-image:
assignee: nobody → Canonical Devices Products (canonical-devices-products-team)
importance: Undecided → High
milestone: none → r1
status: New → Confirmed
Revision history for this message
Chris Gagnon (chris.gagnon) wrote :
Michał Sawicz (saviq)
Changed in unity8 (Ubuntu):
status: Confirmed → Triaged
Changed in unity8 (Ubuntu RTM):
status: New → Triaged
milestone: none → 14.09-ota-1
importance: Undecided → High
affects: unity8 (Ubuntu RTM) → qtmir (Ubuntu RTM)
Changed in unity8 (Ubuntu):
status: Triaged → Incomplete
Changed in qtmir:
status: Confirmed → Triaged
Revision history for this message
Michał Sawicz (saviq) wrote :

We'll need more time to investigate this, I'm thinking ww05-2015.

Changed in qtmir (Ubuntu RTM):
milestone: 14.09-ota-1 → none
Changed in canonical-devices-system-image:
status: Confirmed → New
Changed in canonical-devices-system-image:
milestone: ww51-2014 → ww05-2015
status: New → Confirmed
kevin gunn (kgunn72)
summary: /usr/lib/arm-linux-
- gnueabihf/qt5/bin/qmlscene:6:qt_message_fatal:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPlugin::create:loadIntegration
+ gnueabihf/qt5/bin/qmlscene:6:qt_message_fatal:QMessageLogger::fatal:
+ UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPlugin::create:loadIntegration
Changed in canonical-devices-system-image:
milestone: ww05-2015 → ww09-2015
Changed in canonical-devices-system-image:
assignee: Canonical Devices Products (canonical-devices-products-team) → Kevin Gunn (kgunn)
Revision history for this message
Gerry Boland (gerboland) wrote :

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.

Revision history for this message
Michał Sawicz (saviq) wrote :

In light of this, and no known user impact, I'd drop this from the RTM list.

Changed in canonical-devices-system-image:
status: Confirmed → New
no longer affects: canonical-devices-system-image
Revision history for this message
Gerry Boland (gerboland) wrote :

It has been a year, I've not heard this complaint in some time. I'm marking this as fixed, please re-open if it happens to you.

Changed in qtmir:
status: Triaged → Fix Released
Changed in qtubuntu:
status: Confirmed → Fix Released
Changed in qtmir (Ubuntu RTM):
status: Triaged → Fix Released
Changed in qtubuntu (Ubuntu):
status: Confirmed → Fix Released
Changed in unity8 (Ubuntu):
status: Incomplete → Invalid
Michał Sawicz (saviq)
no longer affects: qtubuntu
Michał Sawicz (saviq)
affects: qtmir → qtmir (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.