Ubuntu
unity8 package

unity8 crashed with SIGSEGV in QMetaObject::activate()

Bug #1253685 reported by Michał Sawicz
28
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Mir
Invalid
Critical
Unassigned
unity-mir
Fix Released
Critical
Gerry Boland
unity-mir (Ubuntu)
Fix Released
Critical
Unassigned
unity8 (Ubuntu)
Invalid
Critical
Unassigned

Bug Description

This happens on unity8 shutdown.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity8 7.83+14.04.20131106-0ubuntu1
Uname: Linux 3.4.0-3-mako armv7l
ApportVersion: 2.12.7-0ubuntu1
Architecture: armhf
Date: Thu Nov 21 16:30:06 2013
ExecutablePath: /usr/bin/unity8
ExecutableTimestamp: 1383710247
InstallationDate: Installed on 2013-11-20 (0 days ago)
InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20131120.2)
ProcCmdline: unity8
ProcCwd: /var/crash
Signal: 11
SourcePackage: unity8
StacktraceTop:
 isSignalConnected (signal_index=28, this=0x0) at kernel/qobject_p.h:233
 QMetaObject::activate (sender=sender@entry=0x475cd828, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3330
 QMetaObject::activate (sender=sender@entry=0x475cd828, m=<optimized out>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3320
 InputArea::surfaceChanged (this=this@entry=0x475cd828) at moc_inputarea.cpp:196
 InputArea::doSetSurface (this=0x475cd828, surface=0x0) at inputarea.cpp:105
Title: unity8 crashed with SIGSEGV in QMetaObject::activate()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty video

Related branches

lp:~gerboland/unity-mir/fix-shutdown-crash
PS Jenkins bot (community): Approve (continuous-integration)
Michał Sawicz: Approve
Diff: 36 lines (+7/-1)
2 files modified
src/modules/Unity/Application/inputarea.cpp (+6/-1)
src/modules/Unity/Application/inputarea.h (+1/-0)
lp:ubuntu/trusty-proposed/unity-mir
Revision history for this message
Michał Sawicz (saviq) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 QMetaObject::activate(QObject*, int, int, void**) () at kernel/qobject_p.h:233
 InputArea::doSetSurface(MirSurface*) () at inputarea.cpp:105
 QMetaObject::activate(QObject*, int, int, void**) () at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:127
 QObject::destroyed(QObject*) () at .moc/release-shared/moc_qobject.cpp:202
 QObject::~QObject() () at kernel/qobject.cpp:771

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 QMetaObject::activate(QObject*, int, int, void**) () at kernel/qobject_p.h:233
 InputArea::doSetSurface(MirSurface*) () at inputarea.cpp:105
 QMetaObject::activate(QObject*, int, int, void**) () at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:127
 QObject::destroyed(QObject*) () at .moc/release-shared/moc_qobject.cpp:202
 QObject::~QObject() () at kernel/qobject.cpp:771

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity8 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-armhf-retrace
Michał Sawicz (saviq)
information type: Private → Public
Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

this is the critical issue on image #28

Changed in unity8 (Ubuntu):
status: New → Confirmed
Changed in unity-mir:
status: New → Confirmed
Changed in mir:
status: New → Confirmed
Changed in unity8 (Ubuntu):
importance: Medium → Critical
Changed in mir:
importance: Undecided → Critical
Changed in unity-mir:
importance: Undecided → Critical
Revision history for this message
Michał Sawicz (saviq) wrote :

Steps to reproduce:
* ssh to the phone
* make sure the screen is on
* stop unity8
* unity8
* Ctrl+C

pkill unity8 when under gdb does the same, too.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I can't see any Mir code in the stack traces right now. The code named "Mir*" is actually in unity-mir. So not a Mir issue unless valgrind etc can point to something like heap corruption originating in Mir code.

Changed in mir:
status: Confirmed → Invalid
Michał Sawicz (saviq)
Changed in unity8 (Ubuntu):
status: Confirmed → Invalid
Changed in unity-mir:
status: Confirmed → In Progress
assignee: nobody → Gerry Boland (gerboland)
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:unity-mir at revision 149, scheduled for release in unity-mir, milestone phone-v1-freeze

Changed in unity-mir:
status: In Progress → Fix Committed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

unity-mir (0.1+14.04.20131119-0ubuntu2) trusty; urgency=low

  * Cherry-pick upstream patch to avoid Unity8 crashing on stop
    (LP: #1253685)
 -- Didier Roche <email address hidden> Tue, 26 Nov 2013 10:47:29 +0100

Changed in unity-mir (Ubuntu):
status: New → Triaged
importance: Undecided → Critical
status: Triaged → Fix Released
Michał Sawicz (saviq)
Changed in unity-mir:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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