As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of unity from precise-proposed was performed and bug 1263392 was found. Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the "verification-failed" tag from this bug report and tag 1263392 "bot-stop-nagging". Thanks!
** Tags added: verification-failed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxfixes in Ubuntu. https://bugs.launchpad.net/bugs/1242633 Title: unity pointer barriers sru bug Status in “libxfixes” package in Ubuntu: In Progress Status in “libxi” package in Ubuntu: In Progress Status in “qt4-x11” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity-2d” package in Ubuntu: In Progress Status in “x11proto-input” package in Ubuntu: In Progress Status in “libxfixes” source package in Precise: Fix Committed Status in “libxi” source package in Precise: Fix Committed Status in “qt4-x11” source package in Precise: Fix Committed Status in “unity” source package in Precise: Fix Committed Status in “unity-2d” source package in Precise: Fix Committed Status in “x11proto-input” source package in Precise: Fix Committed 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/ubuntu/+source/libxfixes/+bug/1242633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
