qmlscene crashed with SIGABRT in qt_message_fatal()

Bug #1271879 reported by Timo Jyrinki
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
qtubuntu
Confirmed
Undecided
Unassigned
unity-mir
New
Undecided
Unassigned
qtdeclarative-opensource-src (Ubuntu)
Invalid
Undecided
Unassigned
qtubuntu (Ubuntu)
Confirmed
Undecided
Unassigned
unity-mir (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I'm filing another bug just in case there is a different/new trace here.

Backtraced on the device directly, from http://q-jenkins.ubuntu-ci:8080/job/trusty-touch-maguro-smoke-ubuntu-clock-app-autopilot/146/artifact/clientlogs/

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: qmlscene 5.0.2-6ubuntu5
Uname: Linux 3.0.0-3-maguro armv7l
Architecture: armhf
CurrentDesktop: Unity
Date: Thu Jan 23 06:52:09 2014
ExecutablePath: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene
ExecutableTimestamp: 1386145664
ProcCmdline: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene ./ubuntu-clock-app.qml
ProcCwd: /usr/share/click/preinstalled/com.ubuntu.clock/1.0.300
Signal: 6
SourcePackage: qtdeclarative-opensource-src
StacktraceTop:
 qt_message_fatal (context=..., message=...) at global/qlogging.cpp:868
 QMessageLogger::fatal (this=this@entry=0xbed520bc, msg=0x4321d964 "QUbuntu: Could not create application instance") at global/qlogging.cpp:356
 QUbuntuIntegration::QUbuntuIntegration (this=0x42e1a000, input_factory=0x1) at ../../../../../src/platforms/ubuntu/ubuntucommon/integration.cc:75
 QUbuntuMirIntegration::QUbuntuMirIntegration (this=0x398308) at ../../../../../../src/platforms/ubuntu/ubuntumir/ubuntumircommon/integration.cc:39
 QUbuntuMirClientIntegrationPlugin::create (this=<optimized out>, system=..., paramList=...) at ../../../../../../src/platforms/ubuntu/ubuntumir/ubuntumirclient/main.cc:41
UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty video
_LogindSession: /user/32011.user/c1.session

Related branches

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :
Changed in qtdeclarative-opensource-src (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1269080, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-armhf-retrace
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :
Changed in qtubuntu (Ubuntu):
status: New → Confirmed
Changed in qtubuntu:
status: New → Confirmed
description: updated
Revision history for this message
Michał Sawicz (saviq) wrote :

"ApplicationManager REJECTED connection from app with pid 2921 as no desktop_file_hint specified"
 in unity8.log
somehow unity-mir and upstart didn't talk to each other about launched apps
so upstart didn't tell unity8/unity-mir that this app was launched, so it was rejected when it connected to Mir
we'd need to reproduce locally, any steps in particular?

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

It seems it happens on maguro only, and most of all with starting clock or calendar app. it's quite common: http://ci.ubuntu.com/smokeng/trusty/touch/maguro/156:20140131:20140115.1/6363/ubuntu-clock-app-autopilot/

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Link related. Gerry had this to add
"there's possibly a more fundamental underlying issue (sometimes an app seems to crash on startup on maguro, which confused unity-mir) so let's be wary"

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

Possible solution: https://code.launchpad.net/~ricmm/unity-mir/catch-starting-failure/+merge/203920
That branch fixes case when an app crashes during startup which confuses unity-mir. However why app crashes is still unknown.

Changed in qtubuntu:
assignee: nobody → rosa maria (rprosamaria383)
assignee: rosa maria (rprosamaria383) → nobody
assignee: nobody → rosa maria (rprosamaria383)
Changed in unity-mir:
assignee: nobody → rosa maria (rprosamaria383)
Changed in qtubuntu:
assignee: rosa maria (rprosamaria383) → nobody
assignee: nobody → rosa maria (rprosamaria383)
assignee: rosa maria (rprosamaria383) → nobody
Changed in qtdeclarative-opensource-src (Ubuntu):
assignee: nobody → rosa maria (rprosamaria383)
assignee: rosa maria (rprosamaria383) → nobody
Changed in qtubuntu (Ubuntu):
assignee: nobody → rosa maria (rprosamaria383)
Changed in qtubuntu:
assignee: nobody → rosa maria (rprosamaria383)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package unity-mir - 0.2+14.04.20140211.1-0ubuntu1

---------------
unity-mir (0.2+14.04.20140211.1-0ubuntu1) trusty; urgency=low

  [ thomas-voss ]
  * Refactor Oom(Score)Adj to rely on process-cpp helper library.

  [ Ricardo Mendoza ]
  * Catch application crashes when Application status is still
    ::Starting. (LP: #1271879)

  [ Gerry Boland ]
  * Update README for cmake instructions
 -- Ubuntu daily release <email address hidden> Tue, 11 Feb 2014 17:45:17 +0000

Changed in unity-mir (Ubuntu):
status: New → Fix Released
dobey (dobey)
Changed in qtubuntu:
assignee: rosa maria (rprosamaria383) → nobody
Changed in unity-mir:
assignee: rosa maria (rprosamaria383) → nobody
Changed in qtubuntu (Ubuntu):
assignee: rosa maria (rprosamaria383) → nobody
Revision history for this message
kevin gunn (kgunn72) wrote :

seems to be still recently happening
this bug has been dup'd

https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1365673

here's the recent reports of it happening
https://errors.ubuntu.com/problem/4618cad07e610ca3c59a3e07c582e963d4780359

Revision history for this message
Chris Gagnon (chris.gagnon) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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