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
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
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
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
Here's what strace says:
strace -p 3477 Process 3477 attached restart_syscall(<... resuming interrupted call ...>) = 0 recvfrom(6, 0x2909ac4, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable) recvfrom(6, 0x2909ac4, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable) poll([{fd=3, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=6, events=POLLIN}, {fd=16, events=POLLIN}, {fd=18, events=POLLIN}, {fd=22, events=POLLIN}], 7, 0) = 0 (Timeout) recvfrom(6, 0x2909ac4, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable) recvfrom(6, 0x2909ac4, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable) poll([{fd=3, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=6, events=POLLIN}, {fd=16, events=POLLIN}, {fd=18, events=POLLIN}, {fd=22, events=POLLIN}], 7, 0) = 0 (Timeout) ...
Neal Becker wrote:
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
Here's what strace says:
strace -p 3477 Process 3477 attached restart_syscall(<... resuming interrupted call ...>) = 0 recvfrom(6, 0x2909ac4, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable) recvfrom(6, 0x2909ac4, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable) poll([{fd=3, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=6, events=POLLIN}, {fd=16, events=POLLIN}, {fd=18, events=POLLIN}, {fd=22, events=POLLIN}], 7, 0) = 0 (Timeout) recvfrom(6, 0x2909ac4, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable) recvfrom(6, 0x2909ac4, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable) poll([{fd=3, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=6, events=POLLIN}, {fd=16, events=POLLIN}, {fd=18, events=POLLIN}, {fd=22, events=POLLIN}], 7, 0) = 0 (Timeout) ...
It appears to be stuck here:
gdb) where #0 0x0000003da1ceaa8d in poll () from /lib64/libc.so.6 #1 0x0000003da40495b4 in g_main_context_iterate.isra.24 () from /lib64/libglib-2.0.so.0 #2 0x0000003da40496dc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x0000003dad5b3185 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4 #4 0x000000304766bdb6 in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtGui.so.4 #5 0x0000003dad58312f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4 #6 0x0000003dad58347d in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4 #7 0x0000003dad5889bb in QCoreApplication::exec() () from /lib64/libQtCore.so.4 #8 0x00000000004db10a in x2goMain (argc=1, argv=<optimized out>) at ../ongetpass.cpp:107 #9 0x0000003da1c21d65 in __libc_start_main () from /lib64/libc.so.6 #10 0x00000000004197a9 in _start ()
Problem found!!
I can reproduce this at will
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
Am 16.01.2014 02:04, schrieb Neal Becker:
Problem found!!
I can reproduce this at will
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
fc20 = Fedora?
If so, re-post with "Fedora libssh Problem" in the subject so Orion Poplawski <orion@cora.nwra.com> and Michael "Mike#2" DePaulo <mikedep333@gmail.com> will notice it - they seem to be the resident Fedora gurus on this list - or, if you're comfortable doing that yourself, file a bug against x2goclient (on the X2Go bugtracker) and/or libssh (on the Fedora bugtracker).
-Stefan
-
Neal Becker -
Short, Kermit -
Stefan Baur