touch-packages team mailing list archive

[Marco Trevisan (Treviño) <mail@xxxxxxxxx>]

** Changed in: unity
   Importance: Undecided => High

** Changed in: unity
       Status: New => Fix Released

** Changed in: unity
     Assignee: (unassigned) => Maarten Lankhorst (mlankhorst)

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

Title:
  unity pointer barriers sru bug

Status in Unity:
  Fix Released
Status in “libxfixes” package in Ubuntu:
  Fix Released
Status in “libxi” package in Ubuntu:
  Fix Released
Status in “qt4-x11” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity-2d” package in Ubuntu:
  Fix Released
Status in “x11proto-input” package in Ubuntu:
  Fix Released
Status in “libxfixes” source package in Precise:
  Fix Released
Status in “libxi” source package in Precise:
  Fix Released
Status in “qt4-x11” source package in Precise:
  Fix Released
Status in “unity” source package in Precise:
  Fix Released
Status in “unity-2d” source package in Precise:
  Fix Released
Status in “x11proto-input” source package in Precise:
  Fix Released

Bug description:
  x11proto-input, libxfixes, libxi, unity and unity-2d in precise needs
  updates to work with the new pointer barrier api from x1.14.

  [Impact]
   * Pointer barrier api has changed between 1.13 and 1.14. (xorg-server-lts-saucy)
   * Modifications in unity and unity-2d are required to support both api's.

  [Test Case]
   * Update all packages.
   * Test pointer barriers on an old xorg-server, they should continue to work.
   * Test pointer barriers on the new xorg-server, they should work.

  [Regression Potential]
    * Low, it enables a separate code path for pointer barriers. The code in unity is a bit different due to copying the rework from upstream unity and keeping the old paths for legacy pointer barriers. Upstream dropped the old paths.

  [Other Info]
    * It's a bit of a hack. The old pointer barrier symbols live in libxfixes, the new ones in libxi. Because of the overlap some modifications had to be made to allow both pointer barriers to be included. This works as well as it can.
   * Depending on the queried libxi2/libxfixes versions, old pointer barriers or new ones are used.

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