<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/
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1354412 Title: unity8-dash crashed with SIGABRT in raise() while running first boot on flo Status in “qtubuntu” package in Ubuntu: New Status in “unity8” package in Ubuntu: Invalid Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1354412/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
