Ideally yes, but does anyone know really what fixed it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386653
Title:
[TOPBLOCKER] Scopes fail to launch when the network stack is not up
To manage
Doesn't look like it :-)
There could be a million reasons. In the absence of any other
information, I don't think we have a choice but to wait and see whether
it comes back. I could stare at our code for years without seeing the
bug (assuming there is one).
I guess the most important point here
the only thing that's gone in recently was the dbus update to clean up
dead client obj's
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386653
Title:
[TOPBLOCKER] Scopes fail to launch when the
I've tried rebooting my krillin on image 139 with airplane mode turned
on around 30 times this morning, and haven't seen this happen a single
time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have not been able to reproduce anymore, krillin #139
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386653
Title:
[TOPBLOCKER] Scopes fail to launch when the network stack is not up
To manage
** Changed in: unity8 (Ubuntu)
Status: Confirmed = Invalid
** Changed in: unity-scope-click (Ubuntu)
Status: Confirmed = Invalid
** Changed in: unity-scopes-api (Ubuntu)
Status: New = Invalid
** Changed in: unity-scope-scopes (Ubuntu)
Status: Confirmed = Invalid
--
Ideally instead of marking invalid, it should be marked as Fixed Released
with a link to the project branch and/or package that fixed it.
On Fri, Oct 31, 2014 at 2:20 PM, Thomas Strehl thomas.str...@canonical.com
wrote:
** Changed in: unity8 (Ubuntu)
Status: Confirmed = Invalid
**
** Summary changed:
- Scopes fail to launch when the network stack is not up
+ [TOPBLOCKER] Scopes fail to launch when the network stack is not up
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
assigning pete for now
** Changed in: unity-scope-scopes (Ubuntu)
Assignee: (unassigned) = Pete Woods (pete-woods)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386653
Title:
[TOPBLOCKER]
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) = Albert Astals Cid (aacid)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386653
Title:
[TOPBLOCKER] Scopes fail to launch when the
** Also affects: unity-scopes-api (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity-scopes-api (Ubuntu)
Importance: Undecided = Critical
** Changed in: unity-scopes-api (Ubuntu)
Assignee: (unassigned) = Michi Henning (michihenning)
--
You received this bug
while I have been able to reproduce this issue reliably on images up to
#135 I am not able to reproduce anymore on #139
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386653
Title:
[TOPBLOCKER]
I'm not seeing it either (on mako, build 293). The logs all look normal.
With flight mode on, the scopes that try to access things on the smart
scopes server log a bunch of exceptions, saying that they can't get the
proxy for those scopes. That's as expected, seeing that the
smartscopesproxy can't
13 matches
Mail list logo
