touch-packages team mailing list archive

[Francesco Fumanti <1413165@xxxxxxxxxxxxxxxxxx>]

Here is the output of the command on a vivid installation, that has not
been updated since the middle of December 2014 and where the regression
was not present yet:

$ sudo apt-cache policy unity
unity:
  Installed: 7.3.1+15.04.20141128-0ubuntu1
  Candidate: 7.3.1+15.04.20150115-0ubuntu1
  Version table:
     7.3.1+15.04.20150115-0ubuntu1 0
        500 http://ubuntu.mirror.root.lu/ubuntu/ vivid/main amd64 Packages
 *** 7.3.1+15.04.20141128-0ubuntu1 0
        100 /var/lib/dpkg/status

And here the output of the command on my uptodate vivid installation
having the regression:

$ sudo apt-cache policy unity
unity:
  Installed: 7.3.1+15.04.20150115-0ubuntu1
  Candidate: 7.3.1+15.04.20150115-0ubuntu1
  Version table:
 *** 7.3.1+15.04.20150115-0ubuntu1 0
        500 http://ubuntu.mirror.root.lu/ubuntu/ vivid/main amd64 Packages
        100 /var/lib/dpkg/status

As far as I understand, the regression happened somewhere between the
two versions.

-- 
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:
  In Progress

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