It looks like you're running KDE and thus this could be related to akonadi and strigi. Try disabling the PIM database and turning off file indexing and see if that helps! It did wonders for me!
Kermit Short DCS-5
On Wed, 2014-01-15 at 15:16 -0500, Neal Becker wrote:
Neal Becker wrote:
I was a happy x2go user up until just now. I ran a yum update, perhaps related.
Now ever time I connect, x2go client uses 100% cpu (actually, 100% of 2 cpus)
Perhaps related, I always get an error message, a picture is attached.
I tried
rm -rf ~/.x2go
on the server, to make sure I'm getting a clean start
Perhaps related, updates on the client include:
Jan 15 14:40:25 Updated: kde-runtime-flags-4.11.5-2.fc20.noarch Jan 15 14:40:26 Updated: kde-runtime-libs-4.11.5-2.fc20.x86_64 Jan 15 14:40:29 Updated: kde-runtime-4.11.5-2.fc20.x86_64 Jan 15 14:40:29 Updated: kde-runtime-drkonqi-4.11.5-2.fc20.x86_64
X2Go-User mailing list X2Go-User@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-user