Upon further investigation, this actually seems to be related to running Synergy+. I'm not quite sure where the error is though, since it was working fine in 9.04 and the problem started when I went to 9.10 (same 1.3.4 release of Synergy+ running on both - 9.04 this problem did not exist, 9.10 exhibits the described behavior).
Upon further investigation, this actually seems to be related to running Synergy+. I'm not quite sure where the error is though, since it was working fine in 9.04 and the problem started when I went to 9.10 (same 1.3.4 release of Synergy+ running on both - 9.04 this problem did not exist, 9.10 exhibits the described behavior).