qmlscene crashed with SIGABRT in qt_message_fatal()

[Timo Jyrinki]

Just trying to retrace the latest mako-only qmlscene crash that might be behind the recent mako-only AP problems. However, the backtrace does not look too promising.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: qmlscene 5.4.0-4ubuntu1
Uname: Linux 3.4.0-6-mako armv7l
ApportVersion: 2.16.1-0ubuntu2
Architecture: armhf
CurrentDesktop: Unity
Date: Mon Feb 23 04:52:43 2015
ExecutablePath: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene
ExecutableTimestamp: 1423811187
InstallationDate: Installed on 2015-02-23 (0 days ago)
InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150223-020203)
ProcCmdline: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene /tmp/tmpu15lsm1i.qml
ProcCwd: /home/phablet
Signal: 6
SourcePackage: qtdeclarative-opensource-src
StacktraceTop:
 ?? () from /lib/arm-linux-gnueabihf/libc.so.6
 raise () from /lib/arm-linux-gnueabihf/libc.so.6
 abort () from /lib/arm-linux-gnueabihf/libc.so.6
 QMessageLogger::fatal(char const*, ...) const () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
 ?? () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqpa-ubuntumirclient.so
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dialout dip plugdev sudo tty video

[Apport retracing service (apport)]

StacktraceTop:
 qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1414
 QMessageLogger::fatal (this=0x0, this@entry=0xbeb990f8, msg=0xb3a8d35c "UbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is\nrunning, and the correct socket is being used and is accessible. The shell may have\nrejected the incoming connectio"...) at global/qlogging.cpp:639
 UbuntuClientIntegration::UbuntuClientIntegration (this=<optimized out>) at ../../../src/ubuntumirclient/integration.cpp:80
 UbuntuMirClientIntegrationPlugin::create (this=<optimized out>, system=...) at ../../../src/ubuntumirclient/plugin.cpp:36
 loadIntegration (argv=0x1, argc=@0xbeb9937c: 2, parameters=..., key=..., loader=0xb6681f84 <_ZZN12_GLOBAL__N_112Q_QGS_loader13innerFunctionEvE6holder>) at kernel/qplatformintegrationfactory.cpp:56

[Timo Jyrinki (timo-jyrinki)]

This kind of bug usually needs upstart logs to know what happened before the "not being able to connect" phase.

[Launchpad Janitor (janitor)]

[Expired for qtdeclarative-opensource-src (Ubuntu) because there has been no activity for 60 days.]