Red Hat Bugzilla – Bug 1268862
[abrt] x2goclient: ssh_poll_ctx_remove(): x2goclient killed by SIGSEGV
Last modified: 2016-11-25 03:36:55 EST
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 ssh_poll_ctx_remove at /usr/src/debug/libssh-0.7.2/src/poll.c:564
#1 ssh_poll_free at /usr/src/debug/libssh-0.7.2/src/poll.c:311
#2 ssh_socket_close at /usr/src/debug/libssh-0.7.2/src/socket.c:447
#3 ssh_client_connection_callback at /usr/src/debug/libssh-0.7.2/src/client.c:436
#4 ssh_socket_nonblocking_flush at /usr/src/debug/libssh-0.7.2/src/socket.c:641
#5 ssh_socket_write at /usr/src/debug/libssh-0.7.2/src/socket.c:622
#6 ssh_packet_write at /usr/src/debug/libssh-0.7.2/src/packet.c:509
#7 packet_send2 at /usr/src/debug/libssh-0.7.2/src/packet.c:579
#8 packet_send at /usr/src/debug/libssh-0.7.2/src/packet.c:604
#9 ssh_channel_send_eof at /usr/src/debug/libssh-0.7.2/src/channels.c:1085
Created attachment 1079953 [details]
Created attachment 1079954 [details]
Created attachment 1079955 [details]
Created attachment 1079956 [details]
Created attachment 1079957 [details]
Created attachment 1079958 [details]
Created attachment 1079959 [details]
Created attachment 1079960 [details]
Created attachment 1079961 [details]
Created attachment 1079962 [details]
Created attachment 1079963 [details]
Created attachment 1079964 [details]
Created attachment 1079965 [details]
Looks like this is in libssh, let's see what they say. Can you reproduce the crash?
Hi Orion, thanks for stepping in.
I can't reproduce the crash at will but it has been a recurring issue lately, what do you have in mind?
Does it seem correlated to any particular activity, or just happens at random during a session?
Hmm, as far I can tell it happens at random. Would it help if I check the journal for any related information? I don't know what else I could do to hand you more feedback.
possibly running "x2goclient --debug" and seeing what is output when it crashes if anything.
I'm not sure if this is libssh its fault. You can run it using valgrind it might reveal the issue ...
Hello Orion, Andreas,
Sorry for the late reply, I've been super-busy at work lately.
I just ran x2goclient through Valgrind and the x2Go client crashed when trying to connecto to a server, hosted on my F22 home server:
Please don't hesitate in letting me know if I can be of any further help.
Arghh, that's looks like a failure inside valgrind itself. It would be worth attaching it to this report for posterity.
My bad, apologies.
I will try to reproduce the error in x2go and report back accordingly.
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'
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.
Please report it to https://red.libssh.org/