16 Jan
2014
16 Jan
'14
2:21 a.m.
Michael DePaulo wrote:
2goclient or x2goserver? Let me know and I will try to reproduce it.
Either way, this should be reported as a bug with Fedora. The instructions are here. I haven't reported a bug to fedora before, but I have to other distros. Let me know if you need help. http://fedoraproject.org/wiki/How_to_file_a_bug_report
-Mike
On Wed, Jan 15, 2014 at 8:27 PM, Neal Becker <ndbecker2@gmail.com> wrote:
100% reproducible.
With the latest libssh f20 update, x2go uses 100% cpu (on 2 cpus)
Update to libssh.x86_64 0:0.6.0-1.fc20 I get an error message (as I showed) on connect, and 100% cpu
Downgrade to libssh-0.5.5-1.fc20.x86_64 Problem gone