touch-packages team mailing list archive

[Launchpad Bug Tracker <1413165@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package unity - 7.3.1+15.04.20150227-0ubuntu1

---------------
unity (7.3.1+15.04.20150227-0ubuntu1) vivid; urgency=medium

  [ Andrea Azzarone ]
  * Draw osk above unity shell. (LP: #1413165)
  * Remove FontSettings.*. Add the possibility to specify the font size
    and the font weight without chaning the default font name. Fix lp
    886478. (LP: #886478)
  * Remove unitydialog plugin.

  [ Luke Yelavich ]
  * Explore children when a view or layout is added (LP: #1066157)
  * Move the unity a11y present environment call
  * Set focus to FALSE on window deactivation (LP: #1066157)
 -- CI Train Bot <ci-train-bot@xxxxxxxxxxxxx>   Fri, 27 Feb 2015 15:38:19 +0000

** Changed in: unity (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1413165

Title:
  Regression: Default on-screen keyboard Onboard not properly above dash

Status in Unity:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  Some recent update of broke the default on-screen Onboard to work
  properly on dash.

  In fact, Onboard is shown in dash, as if it was located under dash. It
  is particularly visible, when the dash is maximized and covers the
  whole screen. However, if I drag Onboard to position it under an icon
  in dash and I click on the icon, the corresponding application is not
  started; the click goes down to Onboard, which types the letter of the
  Onboard key placed at the position of the click.

  So, in a few words: dash draws Onboard as if it was covered by dash,
  but Onboard behaves as if it is located over dash.

  Having a vivid backup from about one month ago, we were able to
  determine that the regression seem to have happened because of the
  update of libunity-core and the related packages somewhere between one
  month ago and today. In fact, the problem appeared in the test after
  updating the following packages and versions to the version shipping
  currently in the repositories.

  libunity-core-6.0-9   7.3.1+15.04.20141128-0ubuntu1
  libcairo-gobject2   1.13.0~20140204-0ubuntu1
  libcairo-script-interpreter2   1.13.0~20140204-0ubuntu1
  libcairo2   1.13.0~20140204-0ubuntu1
  libcairo2-dev   1.13.0~20140204-0ubuntu1
  unity   7.3.1+15.04.20141128-0ubuntu1
  unity-schemas   7.3.1+15.04.20141128-0ubuntu1
  unity-services   7.3.1+15.04.20141128-0ubuntu1

  Cheers

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