[Touch-packages] [Bug 1387952] Re: dash didn't start at all on boot

2015-01-15 Thread Launchpad Bug Tracker
[Expired for unity8 (Ubuntu) because there has been no activity for 60
days.]

** Changed in: unity8 (Ubuntu)
   Status: Incomplete = Expired

-- 
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/1387952

Title:
  dash didn't start at all on boot

Status in unity8 package in Ubuntu:
  Expired

Bug description:
  After a spontaneous reboot (bug 1387949), the unity8 dash never
  started.  Instead, I had a black screen with functional indicators at
  the top and a functional launcher bar available from a left swipe.
  Not sure what caused this, but I suspect it may have been related to
  one of the changes which landed just hours earlier in silo rtm-010 (
  https://trello.com/c/enrjHgsd/ ).

  I have not yet been able to reproduce this failure, but haven't booted
  many times to try it yet.

  A potentially relevant crash dump is attached; looks like an issue
  with the flickr scope.  No other crash files were created at the time.

  This was on krillin rtm image 139.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1387952/+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


[Touch-packages] [Bug 1387952] Re: dash didn't start at all on boot

2014-11-15 Thread Selene Scriven
No luck yet.  I'll let it auto-expire if I can't make it happen again.

** Changed in: unity8 (Ubuntu)
   Status: New = Incomplete

-- 
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/1387952

Title:
  dash didn't start at all on boot

Status in “unity8” package in Ubuntu:
  Incomplete

Bug description:
  After a spontaneous reboot (bug 1387949), the unity8 dash never
  started.  Instead, I had a black screen with functional indicators at
  the top and a functional launcher bar available from a left swipe.
  Not sure what caused this, but I suspect it may have been related to
  one of the changes which landed just hours earlier in silo rtm-010 (
  https://trello.com/c/enrjHgsd/ ).

  I have not yet been able to reproduce this failure, but haven't booted
  many times to try it yet.

  A potentially relevant crash dump is attached; looks like an issue
  with the flickr scope.  No other crash files were created at the time.

  This was on krillin rtm image 139.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1387952/+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


[Touch-packages] [Bug 1387952] Re: dash didn't start at all on boot

2014-11-06 Thread kevin gunn
really wonder if this is potentially related to bug 1387214

-- 
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/1387952

Title:
  dash didn't start at all on boot

Status in “unity8” package in Ubuntu:
  New

Bug description:
  After a spontaneous reboot (bug 1387949), the unity8 dash never
  started.  Instead, I had a black screen with functional indicators at
  the top and a functional launcher bar available from a left swipe.
  Not sure what caused this, but I suspect it may have been related to
  one of the changes which landed just hours earlier in silo rtm-010 (
  https://trello.com/c/enrjHgsd/ ).

  I have not yet been able to reproduce this failure, but haven't booted
  many times to try it yet.

  A potentially relevant crash dump is attached; looks like an issue
  with the flickr scope.  No other crash files were created at the time.

  This was on krillin rtm image 139.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1387952/+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


[Touch-packages] [Bug 1387952] Re: dash didn't start at all on boot

2014-11-06 Thread Selene Scriven
Sorry, I haven't been able to reproduce this one at all...  only saw it
one time.

-- 
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/1387952

Title:
  dash didn't start at all on boot

Status in “unity8” package in Ubuntu:
  New

Bug description:
  After a spontaneous reboot (bug 1387949), the unity8 dash never
  started.  Instead, I had a black screen with functional indicators at
  the top and a functional launcher bar available from a left swipe.
  Not sure what caused this, but I suspect it may have been related to
  one of the changes which landed just hours earlier in silo rtm-010 (
  https://trello.com/c/enrjHgsd/ ).

  I have not yet been able to reproduce this failure, but haven't booted
  many times to try it yet.

  A potentially relevant crash dump is attached; looks like an issue
  with the flickr scope.  No other crash files were created at the time.

  This was on krillin rtm image 139.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1387952/+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