← Back to team overview

touch-packages team mailing list archive

[Bug 1350555] Re: DefaultIndicatorPage: should use Loader status to determine the visible property

 

This bug was fixed in the package unity8 -
8.00+14.10.20140731.1-0ubuntu1

---------------
unity8 (8.00+14.10.20140731.1-0ubuntu1) utopic; urgency=low

  [ Gerry Boland ]
  * Fix the run.sh script - pretend to be running with qtmir and emit
    SIGSTOP at the right time

  [ Ying-Chun Liu ]
  * Implement Attribute UI. (LP: #1282460)

  [ Albert Astals ]
  * Hide search history popup as soon as you start typing As discussed
    with Mike and Saviq
  * Compile with for scopes-v3 unity-api
  * PageHeader: Unfocus search field when search entry is selected
  * Show search field if the search query changes
  * Test: Add a condition for art.height being > 0 means stuff has
    already been layouted a bit without it it can happen that we get 0
    for everything at startup and tests still pass
  * Remove leftover in test of an old headerless implementation

  [ Michael Zanetti ]
  * Drop Recent apps category from Dash (LP: #1281092)
  * update launcher count emblems to match new spec (LP: #1338984)

  [ Bill Filler ]
  * disable predictive text for dash search field (LP: #1340409)

  [ CI bot ]
  * Resync trunk

  [ Antti Kaijanmäki ]
  * DefaultIndicatorPage: use Loader status to determine the visible
    property. (LP: #1350555)
 -- Ubuntu daily release <ps-jenkins@xxxxxxxxxxxxxxxxxxx>   Thu, 31 Jul 2014 16:51:01 +0000

** Changed in: unity8 (Ubuntu)
       Status: New => Fix Released

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

Title:
  DefaultIndicatorPage: should use Loader status to determine the
  visible property

Status in The Unity 8 shell:
  In Progress
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  While working on ModemInfoItem for indicator-network I discovered a
  bug on how the items of an indicator are laid out.

  This bug was very obscure, but I managed to reproduce it reliably, so
  I decided to try to fix it. Unfortunately I'm not completely sure what
  is the actual mechanism behind this bug, but I managed to figure out
  how to fix it anyway and I managed to reduce an simplified example
  which mimics the way unity8 loads the indicator items.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8/+bug/1350555/+subscriptions