Bug 1301283

Can you please test https://bodhi.fedoraproject.org/updates/x2goclient-4.0.5.1-1.fc23

Well, I've installed it and it seems to work, but I'm not sure if I'll be able to decide it fixes the hang since it is so random :-). If it does hang again, I'll certainly record that here.

I've been using the x2goclient-4.0.5.1-1.fc23.x86_64 pretty regularly, and still haven't seen it go into an infinite loop. Maybe it does fix the problem.

Let's hope it is then.  Feel free to reopen this bug if you see it again.

It finally went into an infinite loop again when I logged out of the remote session (but it sure seems much much less likely than it was before because I have used it quite a lot without seeing the problem again till just now).

For what it is worth, I ran an strace on the infinite looping program and I see this stuff repeated over and over:

recvmsg(7, 0x7ffd108fd890, 0)           = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(7, 0x7ffd108fd870, 0)           = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=4, events=POLLIN}, {fd=7, events=POLLIN}], 2, 0) = 0 (Timeout)
recvmsg(7, 0x7ffd108fd890, 0)           = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(7, 0x7ffd108fd870, 0)           = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=4, events=POLLIN}, {fd=7, events=POLLIN}], 2, 0) = 0 (Timeout)
...

I am changing the status back to NEW.

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

I still see this sometimes, it isn't as common as it once was.

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

I've run x2go from my fedora 26 desktop at work to my fedora 24 system at home and the fedora 26 x2goclient seems to always go into an infinite loop when I log out of the fedora 24 session by closing the last app which the .xinitrc file was waiting for.

An strace of the fedora 26 x2goclient infinite loop shows this stuff over and over:



recvmsg(6, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(6, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=7, events=POLLIN}, {fd=20, events=POLLIN}, {fd=25, events=POLLIN}, {fd=29, events=POLLIN}], 6, 0) = 0 (Timeout)
recvmsg(6, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(6, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=7, events=POLLIN}, {fd=20, events=POLLIN}, {fd=25, events=POLLIN}, {fd=29, events=POLLIN}], 6, 0) = 0 (Timeout)
recvmsg(6, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(6, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)

The /proc/pid/fd directory of this looping program looks like:

lr-x------ 1 tweety tweety 64 Jul 31 10:46 0 -> /dev/null
l-wx------ 1 tweety tweety 64 Jul 31 10:46 1 -> /dev/null
lrwx------ 1 tweety tweety 64 Jul 31 10:46 10 -> socket:[104619]
lr-x------ 1 tweety tweety 64 Jul 31 10:46 11 -> /dev/urandom
lrwx------ 1 tweety tweety 64 Jul 31 10:46 12 -> socket:[103698]
lrwx------ 1 tweety tweety 64 Jul 31 10:46 13 -> socket:[103712]
l-wx------ 1 tweety tweety 64 Jul 31 10:46 19 -> pipe:[103723]
l-wx------ 1 tweety tweety 64 Jul 31 10:46 2 -> /dev/null
lr-x------ 1 tweety tweety 64 Jul 31 10:46 20 -> pipe:[103724]
lrwx------ 1 tweety tweety 64 Jul 31 10:46 23 -> anon_inode:[eventfd]
lr-x------ 1 tweety tweety 64 Jul 31 10:46 25 -> pipe:[103725]
lr-x------ 1 tweety tweety 64 Jul 31 10:46 29 -> pipe:[103727]
lrwx------ 1 tweety tweety 64 Jul 31 10:46 3 -> anon_inode:[eventfd]
l-wx------ 1 tweety tweety 64 Jul 31 10:46 30 -> pipe:[103727]
lr-x------ 1 tweety tweety 64 Jul 31 10:46 4 -> pipe:[103691]
l-wx------ 1 tweety tweety 64 Jul 31 10:46 5 -> pipe:[103691]
lrwx------ 1 tweety tweety 64 Jul 31 10:46 6 -> socket:[103692]
lrwx------ 1 tweety tweety 64 Jul 31 10:46 7 -> socket:[103693]
lrwx------ 1 tweety tweety 64 Jul 31 10:46 8 -> anon_inode:[eventfd]

On the fedora 26 host system, I'm running:

x2goclient-4.1.0.0-1.fc26.x86_64

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.