[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
** 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 DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages 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 -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
This bug was fixed in the package libxi - 2:1.7.1.901-1ubuntu1~precise1 --- libxi (2:1.7.1.901-1ubuntu1~precise1) precise-proposed; urgency=low * Copy package to precise from saucy. * Compile correctly with both pointer barrier implementations. (LP: #1242633) * Fix build-depends and conflicts for precise. -- Maarten Lankhorst maarten.lankho...@ubuntu.com Wed, 04 Sep 2013 10:01:16 +0200 ** Changed in: libxi (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: unity (Ubuntu Precise) Status: Fix Committed = Fix Released -- 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/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 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/ubuntu/+source/libxfixes/+bug/1242633/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
This bug was fixed in the package libxfixes - 1:5.0-4ubuntu4.2 --- libxfixes (1:5.0-4ubuntu4.2) precise-proposed; urgency=low * Fix compile with upstream pointer barriers. (LP: #1242633) -- Maarten Lankhorst maarten.lankho...@ubuntu.com Wed, 04 Sep 2013 13:10:28 +0200 ** Changed in: x11proto-input (Ubuntu Precise) Status: Fix Committed = Fix Released -- 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/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 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/ubuntu/+source/libxfixes/+bug/1242633/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
** Branch linked: lp:ubuntu/precise-updates/libxi -- 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/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 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/ubuntu/+source/libxfixes/+bug/1242633/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
tested with the raring stack with no issues (on Intel Ivy Bridge). -- 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/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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
The linked bug already happened before the upload, so not a regression. ** Tags removed: verification-failed -- 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/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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
tested with the quantal stack, both unity unity-2d work -- 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/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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
Hello Maarten, or anyone else affected, Accepted x11proto-input into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/x11proto- input/2.3-1~precise1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: x11proto-input (Ubuntu Precise) Status: New = Fix Committed -- 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/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: New Status in “unity” source package in Precise: Fix Committed Status in “unity-2d” source package in Precise: New 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
** Branch linked: lp:ubuntu/precise-proposed/x11proto-input -- 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/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: New Status in “unity” source package in Precise: Fix Committed Status in “unity-2d” source package in Precise: New 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
Hello Maarten, or anyone else affected, Accepted qt4-x11 into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/qt4-x11/4:4.8.1-0ubuntu4.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: qt4-x11 (Ubuntu Precise) Status: New = Fix Committed -- 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/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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
** Branch linked: lp:ubuntu/precise-proposed/unity-2d -- 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/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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
** Also affects: libxfixes (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: libxi (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: qt4-x11 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: x11proto-input (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: unity (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: unity-2d (Ubuntu Precise) Importance: Undecided Status: New -- 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/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: New Status in “libxi” source package in Precise: Fix Committed Status in “qt4-x11” source package in Precise: New Status in “unity” source package in Precise: New Status in “unity-2d” source package in Precise: New Status in “x11proto-input” source package in Precise: New 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
Hello Maarten, or anyone else affected, Accepted libxi into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/libxi/2:1.7.1.901-1ubuntu1~precise1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: libxi (Ubuntu Precise) Status: New = Fix Committed ** Tags added: verification-needed -- 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/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: New Status in “libxi” source package in Precise: Fix Committed Status in “qt4-x11” source package in Precise: New Status in “unity” source package in Precise: New Status in “unity-2d” source package in Precise: New Status in “x11proto-input” source package in Precise: New 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
Hello Maarten, or anyone else affected, Accepted libxfixes into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/libxfixes/1:5.0-4ubuntu4.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: libxfixes (Ubuntu Precise) Status: New = Fix Committed -- 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/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: New Status in “unity” source package in Precise: New Status in “unity-2d” source package in Precise: New Status in “x11proto-input” source package in Precise: New 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
** Branch linked: lp:ubuntu/precise-proposed/libxi -- 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/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: New Status in “unity” source package in Precise: Fix Committed Status in “unity-2d” source package in Precise: New Status in “x11proto-input” source package in Precise: New 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
** Branch linked: lp:~ubuntu-branches/ubuntu/precise/libxfixes/precise- proposed -- 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/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: New Status in “unity” source package in Precise: Fix Committed Status in “unity-2d” source package in Precise: New Status in “x11proto-input” source package in Precise: New 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
Also affects libqt-x11, it queries for xinput 2.1 which breaks unity-2d pointer barriers. ** Also affects: qt4-x11 (Ubuntu) Importance: Undecided Status: New ** Changed in: qt4-x11 (Ubuntu) Status: New = In Progress ** Changed in: qt4-x11 (Ubuntu) Importance: Undecided = High ** Changed in: qt4-x11 (Ubuntu) Assignee: (unassigned) = Maarten Lankhorst (mlankhorst) -- 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/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 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
