I found a couple of problems in the previous patch.
The test for isEmpty had the sense backwards.
I also reduced the number of writes to the wake-up pipe
and increased the amount read from the pipe per call.
The select-based code (which ubuntu doesn't use) also had
a couple of defects that I found and fixed after forcing the
non-poll based code to be used.

I don't see how those problems could lead to the assertion in
XGetXCBBuffer.  There may be a latent problem with reentrant
calls to Xlib that still hides on my single cpu system.
A dual core system may help to bring out that bad behavior.
But I haven't put hardy on such a system yet.

** Attachment added: "fix for lag of synergyc on input"
   http://launchpadlibrarian.net/14027236/synergy_diffs

-- 
2.6.24-8 Introduces Network Issue
https://bugs.launchpad.net/bugs/194029
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to