cursor moves in small jumps about once every 1/2 second on 10.10 alpha 2

[fejes]

Binary package hint: synergy

I just upgraded to Kubuntu 10.10 alpha 2, and was surprised to discover that sharing the cursor is no longer "smooth" between the two computers. The "server" is running Kubuntu 10.04, the "client" is a laptop running 10.10a2.

When both the server and the client were running 10.04, the cursor moved smoothly (except while the wall paper was changing on the server, which just caused the shared cursor to freeze momentarily), and reacted appropriately. However, now that I have upgraded to 10.10 on the client, it has become unusable, as the cursor moves from position to position in small jumps, about once every half second.

The network connection hasn't changed, so I doubt this is related to a network issue, although it may be possible that there is a network problem with Kubuntu 10.10.

The only relevant hardware I can think to report is the wireless :
(from lspci)
05:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)

The client is a Dell Vostro 1000 laptop
The server is a Dell Optiplex 755

Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: synergy 1.3.1-6ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-9.14-generic 2.6.35-rc5
Uname: Linux 2.6.35-9-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Thu Jul 22 09:06:30 2010
EcryptfsInUse: Yes
InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
ProcEnviron:
 LANGUAGE=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: synergy

[fejes (anthony-fejes)]

Running from the command line as root (sudo) does not change this behaviour. (This was a workaround that worked for ubuntu versions before 8.04, I believe.)

[fejes (anthony-fejes)]

This appears to be a wireless network problem, as this issue disappears if the wireless connection is replaced by a wired connection. As soon as the wired connection is removed, and the connection reverts to wireless, synergy becomes unusable again.

Not sure how to begin tracking down the source of the issue however.