qmlscene crashed with SIGABRT in QMessageLogger::fatal() during calendar, weather and clock app tests with image 139 and 140

[Para Siva]

This crash occurred during calendar, weather and clock app tests on maguro with image 139 and 140. Reverting libatspi2.0-0 to 2.10.1-0ubuntu1 made the crash NOT to occur.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: qmlscene 5.0.2-6ubuntu5
Uname: Linux 3.0.0-3-maguro armv7l
ApportVersion: 2.13.1-0ubuntu1
Architecture: armhf
CurrentDesktop: Unity
Date: Tue Jan 21 10:54:37 2014
ExecutablePath: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene
ExecutableTimestamp: 1386145664
InstallationDate: Installed on 2014-01-21 (0 days ago)
InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140121)
LocalLibraries: /android/system/lib/libEGL.so /android/system/lib/libm.so /android/system/lib/libdsyscalls.so /android/system/lib/libgccdemangle.so /android/system/lib/libstlport.so /android/system/lib/libcorkscrew.so /android/system/lib/libstdc++.so /android/system/lib/libcutils.so /android/system/lib/libz.so /android/system/lib/libc.so /android/system/lib/liblog.so /android/system/lib/libutils.so /android/system/lib/libGLESv2.so /android/system/lib/libGLES_trace.so
MarkForUpload: True
ProcCmdline: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene ./ubuntu-clock-app.qml
ProcCwd: /usr/share/click/preinstalled/com.ubuntu.clock/1.0.283
Signal: 6
SourcePackage: qtdeclarative-opensource-src
StacktraceTop:
 QMessageLogger::fatal(char const*, ...) const () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
 ?? () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqubuntumirclient.so
Title: qmlscene crashed with SIGABRT in QMessageLogger::fatal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty video
_LogindSession: /user/32011.user/c1.session
_MarkForUpload: True

[Apport retracing service (apport)]

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.