No-one has seen this for months, so I'm marking as Invalid.
** Changed in: unity-scopes-api (Ubuntu RTM)
Status: Incomplete = Invalid
** Changed in: unity-scopes-shell (Ubuntu RTM)
Status: Incomplete = Invalid
** Changed in: unity8 (Ubuntu)
Status: Expired = Invalid
**
I have this on krillin, today image
--
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/1362619
Title:
unity8-dash hangs in scopes backend
Status in “unity8” package in
and image 33 too
--
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/1362619
Title:
unity8-dash hangs in scopes backend
Status in “unity8” package in Ubuntu:
Incomplete
I saw this on yesterdays images (cant recall if it was rtm-proposed or
devel-proposed or both)
Twice saw the Unity8 starting splash when open the welcome screen and it never
starts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I'm marking incomplete, jibel didn't see it either. It's not great that
we don't know what happened, let's revisit this if it comes back.
** Changed in: unity-scopes-api (Ubuntu RTM)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
The stack trace isn't all that complete. Quite a few frames are cut off.
But the ones that look right are as I would expect them to be for an
idle run time. There are no outgoing requests in flight, and everything
is basically idle.
Saviq, any pointers as to how I might reproduce and with which
So... I've just tried reproducing this on two devices with both devel-
proposed@233 and rtm-proposed@23, flashing, rebooting... I always got a
fully working dash on boot...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I went back to rtm-proposed@17, still nothing.
--
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/1362619
Title:
unity8-dash hangs in scopes backend
Status in “unity8”
I've rebooted at least 15 times with proposed@233 and didn't see the
problem :-(
--
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/1362619
Title:
unity8-dash hangs in scopes
Setting importance to high, it happens during normal operations of the
device and requires a reboot.
** Changed in: unity8 (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in
W dniu 02.09.2014 o 03:41, Michi Henning pisze:
Hmmm... The stack traces all look normal for an idle process. It could
be related to the thread starvation issue on the adapter side (which I
haven't gotten back to yet), but in that case, I would have expected a
timeout exception.
How long was
Got this again now during normal operation. I don't think unity8 can do
anything here, it looks like the deadlock is somewhere between scopes
and zmq.
** Summary changed:
- unity8-dash hangs on startup
+ unity8-dash hangs in scopes backend
** Description changed:
- This is a forced crash, it
** Changed in: unity-scopes-api (Ubuntu RTM)
Status: New = Confirmed
** Tags added: rtm14
** Changed in: unity-scopes-shell (Ubuntu RTM)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: unity-scopes-api (Ubuntu RTM)
Assignee: (unassigned) = Michi Henning (michihenning)
** Changed in: unity-scopes-shell (Ubuntu RTM)
Assignee: (unassigned) = Pete Woods (pete-woods)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hmmm... The stack traces all look normal for an idle process. It could
be related to the thread starvation issue on the adapter side (which I
haven't gotten back to yet), but in that case, I would have expected a
timeout exception.
How long was the dash hung before you took the stack trace? More
15 matches
Mail list logo
