just tried the daily "unity-next" image on an asus netbook with intel
graphics, same error but restart won't help, crashes every time
** Summary changed:
- unity8-dash crashed with SIGABRT in raise() while running first boot on flo
+ unity8-dash crashed with SIGABRT in raise()
--
You received t
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qtubuntu (Ubuntu)
Status: New => Confirmed
--
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
i'm gonna go ahead and disagree that this rtm worthy
** Tags removed: rtm14 touch-2014-11-28
--
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 cr
** Tags removed: touch-2014-10-16
** Tags added: touch-2014-11-28
** Changed in: unity8 (Ubuntu)
Assignee: Albert Astals Cid (aacid) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
htt
my guess is that dash is being started before the unity8 mir
server is running
may be
i know not enought about upstart stuff
start on started unity8
is that too early?
hmm, need to check what "started" actually means
expect stop
Specifies that the job's main process will raise the SIGSTOP
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.
--
You received this bug notification because you are
Looking at the stacktrace is qtubuntu qFataling, not something we can
fix in unity8 side of things
** Also affects: qtubuntu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qtubuntu (Ubuntu)
Importance: Undecided => High
** Changed in: unity8 (Ubuntu)
Status: Triage
Has this been happening for you again?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1354412
Title:
unity8-dash crashed with SIGABRT in raise() while running first boot
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) => Albert Astals Cid (aacid)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1354412
Title:
unity8-dash crashed wi
** No longer affects: unity8
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1354412
Title:
unity8-dash crashed with SIGABRT in raise() while running first boot
on flo
St
** Changed in: unity8 (Ubuntu)
Importance: Undecided => High
** Changed in: unity8 (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/b
** Tags added: touch-2014-10-16
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1354412
Title:
unity8-dash crashed with SIGABRT in raise() while running first boot
on flo
** Also affects: unity8
Importance: Undecided
Status: New
** Changed in: unity8
Status: New => Triaged
** Changed in: unity8
Importance: Undecided => High
** Tags added: rtm14
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
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
UbuntuClie
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=
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 :/
** Changed in: unity8 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
** Tags removed: need-armhf-retrace
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1354412
Title:
unity8-dash crashed with SIGABRT in raise() while running first boot
on
Worked fine again after a reboot, so it might be a first boot issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1354412
Title:
unity8-dash crashed with SIGABRT in raise
18 matches
Mail list logo
