I've seen this on Centos 6.5 with the Windows 7 x2go client, both 4.0.2.0.
I tried downgrading the client all the way back to 3.11 with no effect.
One interesting point - a colleague running x2goclient on Ubuntu 12 LTS (client version was 3.99) did *not* experience the problem.
In my environment it makes x2go unusable, so I'm now investigating xpra to get the resume/suspend functionality.
regards Alan
-- Alan Fitch