dx-packages team mailing list archive

[Daniel Holz <1413165@xxxxxxxxxxxxxxxxxx>]

I'm getting this bug now in trusty. Any chance to backport the fix?

Here is the output of

sudo apt-chache policy unity

unity:
  Installiert:           7.2.4+14.04.20150316-0ubuntu1
  Installationskandidat: 7.2.4+14.04.20150316-0ubuntu1
  Versionstabelle:
 *** 7.2.4+14.04.20150316-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     7.2.2+14.04.20140714-0ubuntu1.1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
     7.2.0+14.04.20140416-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Package

I'm using Ubuntu on a tablet computer, so I pretty much depend on a
working onscreen keyboard.

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

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

Status in Unity:
  Fix Released
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