Public bug reported:

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.

** Affects: libxfixes (Ubuntu)
     Importance: High
     Assignee: Maarten Lankhorst (mlankhorst)
         Status: In Progress

** Affects: libxi (Ubuntu)
     Importance: High
     Assignee: Maarten Lankhorst (mlankhorst)
         Status: In Progress

** Affects: unity (Ubuntu)
     Importance: High
     Assignee: Maarten Lankhorst (mlankhorst)
         Status: In Progress

** Affects: unity-2d (Ubuntu)
     Importance: High
     Assignee: Maarten Lankhorst (mlankhorst)
         Status: In Progress

** Affects: x11proto-input (Ubuntu)
     Importance: High
     Assignee: Maarten Lankhorst (mlankhorst)
         Status: In Progress

** Changed in: unity-2d (Ubuntu)
     Assignee: (unassigned) => Maarten Lankhorst (mlankhorst)

** Changed in: unity-2d (Ubuntu)
    Milestone: None => ubuntu-12.04.4

** Changed in: unity-2d (Ubuntu)
   Importance: Undecided => High

** Changed in: unity-2d (Ubuntu)
       Status: New => In Progress

** Also affects: unity (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: x11proto-input (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: libxfixes (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: libxi (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: unity (Ubuntu)
       Status: New => In Progress

** Changed in: libxi (Ubuntu)
       Status: New => In Progress

** Changed in: libxfixes (Ubuntu)
       Status: New => In Progress

** Changed in: x11proto-input (Ubuntu)
       Status: New => In Progress

** Changed in: libxfixes (Ubuntu)
   Importance: Undecided => High

** Changed in: libxi (Ubuntu)
   Importance: Undecided => High

** Changed in: unity (Ubuntu)
   Importance: Undecided => High

** Changed in: x11proto-input (Ubuntu)
   Importance: Undecided => High

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

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

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

** Changed in: x11proto-input (Ubuntu)
     Assignee: (unassigned) => Maarten Lankhorst (mlankhorst)

** Description changed:

  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.
+ [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 work.
-  * Test pointer barriers on the new xorg-server, they should still work.
+  * 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.
+ [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.
+   * 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.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11proto-input in Ubuntu.
https://bugs.launchpad.net/bugs/1242633

Title:
  unity pointer barriers sru bug

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

_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to     : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

Reply via email to