unity8-dash crashed with SIGABRT in raise()

[Ricardo Salveti]

phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 178
device name: flo
channel: ubuntu-touch/utopic-proposed
last update: 2014-08-08 12:06:09
version version: 178
version ubuntu: 20140808
version device: 20140805.2

On a clean flash, on flo, unity8 started with a black screen. After looking the crash files, that was because unity8-dash crashed with a sigabort.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: unity8 8.00+14.10.20140806.1-0ubuntu1
Uname: Linux 3.4.0-3-flo armv7l
ApportVersion: 2.14.5-0ubuntu3
Architecture: armhf
CurrentDesktop: Unity
Date: Fri Aug 8 12:07:23 2014
ExecutablePath: /usr/bin/unity8-dash
ExecutableTimestamp: 1407367539
InstallationDate: Installed on 2014-08-08 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140808-020205)
ProcCmdline: unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop
ProcCwd: /home/phablet
Signal: 6
SourcePackage: unity8
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 cdrom dialout dip plugdev sudo tty video

[Ricardo Salveti (rsalveti)]

Worked fine again after a reboot, so it might be a first boot issue.

[Michał Sawicz (saviq)]

The crash dump unfortunately won't give us much, we'd need the unity8-dash.log file from ~/.cache/upstart to see the abort message :/

[Ricardo Salveti (rsalveti)]

phablet@ubuntu-phablet:~$ cat .cache/upstart/unity8-dash.log
UbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is
running, and the correct socket is being used and is accessible. The shell may have
rejected the incoming connection, so check its log file
UbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is
running, and the correct socket is being used and is accessible. The shell may have
rejected the incoming connection, so check its log file

[Ricardo Salveti (rsalveti)]

phablet@ubuntu-phablet:~$ cat .cache/upstart/unity8.log
()
qtmir.mir: MirServerConfiguration created
qtmir.mir: MirPlacementStrategy::MirPlacementStrategy
qtmir.mir: SessionListener::SessionListener - this= SessionListener(0x19e11e4)
qtmir.mir: PromptSessionListener::PromptSessionListener - this= PromptSessionListener(0x19e2784)
QtCompositor::setAllWindowsExposed true
qtmir.applications: UnityApplicationPlugin::registerTypes - this= UnityApplicationPlugin(0xadd55580) uri= Unity.Application
qtmir.applications: applicationManagerSingleton - engine= QQmlEngine(0x19f9748) scriptEngine= QObject(0x0)
qtmir.mir: SessionListener::starting - this= SessionListener(0x19e11e4) session= 0xadb00974
qtmir.mir: SessionListener::focused - this= SessionListener(0x19e11e4) session= 0xadb00974
qtmir.applications: ApplicationManager::ApplicationManager (this=%p) qtmir::ApplicationManager(0x1b04b88)
unity::action::ActionManager::ActionManager(QObject*):
 Could not determine application identifier. HUD will not work properly.
 Provide your application identifier in $APP_ID environment variable.
qtmir.applications: applicationManagerSingleton - engine= QQmlEngine(0x19f9748) scriptEngine= QQmlEngine(0x19f9748)
qtmir.applications: surfaceManagerSingleton - engine= QQmlEngine(0x19f9748) scriptEngine= QQmlEngine(0x19f9748)
qtmir.surfaces: MirSurfaceManager::MirSurfaceManager - this= qtmir::MirSurfaceManager(0x1c51570)
file:///usr/share/unity8/Shell.qml:525:5: QML Binding: Binding loop detected for property "target"
Initializing AalServicePlugin
Creating a new static Service instance
virtual int AalMediaPlayerControl::volume() const

virtual QMediaPlayer::State AalMediaPlayerControl::state() const

virtual QMediaPlayer::MediaStatus AalMediaPlayerControl::mediaStatus() const

virtual QMediaPlayer::MediaStatus AalMediaPlayerControl::mediaStatus() const

file:///usr/share/unity8/Notifications/Notification.qml:378: TypeError: Cannot read property 'actionLabel' of null
file:///usr/share/unity8/Notifications/Notification.qml:378: TypeError: Cannot read property 'actionLabel' of null
file:///usr/share/unity8/Notifications/Notification.qml:378: TypeError: Cannot read property 'actionLabel' of null
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/MainView.qml:202:5: QML StyledItem: Binding loop detected for property "style"
file:///usr/share/unity8/Notifications/Notification.qml:378: TypeError: Cannot read property 'actionLabel' of null
file:///usr/share/unity8/Notifications/Notification.qml:378: TypeError: Cannot read property 'actionLabel' of null
DisplayWindow::DisplayWindow
Window 0x186bd60: 0x19e4a60 0x1

createPlatformOpenGLContext QOpenGLContext(0x1d6b810)
Creating a new static Service instance
virtual int AalMediaPlayerControl::volume() const

virtual QMediaPlayer::State AalMediaPlayerControl::state() const

virtual QMediaPlayer::MediaStatus AalMediaPlayerControl::mediaStatus() const

virtual QMediaPlayer::MediaStatus AalMediaPlayerControl::mediaStatus() const

file:///usr/share/unity8/Notifications/Notification.qml:378: TypeError: Cannot read property 'actionLabel' of null
file:///usr/share/unity8/Shell.qml:499:9: QML Notifications: Binding loop de...

[Michał Sawicz (saviq)]

Has this been happening for you again?

[Albert Astals Cid (aacid)]

Looking at the stacktrace is qtubuntu qFataling, not something we can fix in unity8 side of things

[Gerry Boland (gerboland)]

Is unity8-dash definitely being started after unity8 emits SIGSTOP - which is its way of telling upstart that the mir server is ready for incoming connections?

If not, dash might have tried to connect to mir, before unity8 has brought up mir.

[Albert Astals Cid (aacid)]

<greyback__> my guess is that dash is being started before the unity8 mir server is running
<tsdgeos> may be
<tsdgeos> i know not enought about upstart stuff
<tsdgeos> start on started unity8
<tsdgeos> is that too early?
<greyback__> hmm, need to check what "started" actually means
<greyback__> expect stop
<greyback__> Specifies that the job's main process will raise the SIGSTOP signal to indicate that it is ready. init(8) will wait for this signal before running the job's post-start script, or considering the job to be running.
<greyback__> hmm, think the state "started" after post-start script run
<greyback__> so my theory is bad
<greyback__> I'm quoting http://upstart.ubuntu.com/cookbook/

[kevin gunn (kgunn72)]

i'm gonna go ahead and disagree that this rtm worthy

[Launchpad Janitor (janitor)]

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

[Alexander Dobetsberger (masternoob)]

just tried the daily "unity-next" image on an asus netbook with intel graphics, same error but restart won't help, crashes every time