Bug 1179010

Summary: [abrt] nxagent: _XReply(): nxagent killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Reilly Hall <sly.midnight>
Component: nx-libsAssignee: Orion Poplawski <orion>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: ezwen-redhatbugzilla, orion, slyadmin, sly.midnight
Target Milestone: ---Keywords: Upstream
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/28e49167bd24d93d7fc5613dcabec0641f00b775
Whiteboard: abrt_hash:d98f212256ed0edc0382f9018a1fd7b27ae443ff
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 06:58:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Reilly Hall 2015-01-05 21:37:20 UTC 
Description of problem:
This seems to happen when I've had a nx2go client session going for most of the day.  Though it doesn't happen every day and seems to occur only about once a week at most.  I start my session at 9am, if it's going to happen it happens around 2pm more or less.

Causes KDE to be unresponsive and the other apps super sluggish.

Disconnecting or pausing the session causes it to abort and not be resumable.  Once it's like that, there's no way to salvage it.  Save what can be saved and exit and log back in.

Version-Release number of selected component:
nxagent-3.5.0.28-1.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        /usr/lib64/nx/../x2go/bin/x2goagent -extension XFIXES -nolisten tcp -nolisten tcp -dpi 96 -D -auth /home/sly/.Xauthority -geometry 1680x1050 -name X2GO-sly-209-1420466729_stDKDE_dp24 :209
crash_function: _XReply
executable:     /usr/lib64/nx/bin/nxagent
kernel:         3.17.7-300.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (2 frames)
 #0 _XReply at XlibInt.c:2249
 #1 _XIDHandler at XlibInt.c:2073
Comment 1 Reilly Hall 2015-01-05 21:37:23 UTC 
Created attachment 976611 [details]
File: backtrace
Comment 2 Reilly Hall 2015-01-05 21:37:24 UTC 
Created attachment 976612 [details]
File: cgroup
Comment 3 Reilly Hall 2015-01-05 21:37:25 UTC 
Created attachment 976613 [details]
File: core_backtrace
Comment 4 Reilly Hall 2015-01-05 21:37:26 UTC 
Created attachment 976614 [details]
File: dso_list
Comment 5 Reilly Hall 2015-01-05 21:37:26 UTC 
Created attachment 976615 [details]
File: environ
Comment 6 Reilly Hall 2015-01-05 21:37:27 UTC 
Created attachment 976616 [details]
File: exploitable
Comment 7 Reilly Hall 2015-01-05 21:37:28 UTC 
Created attachment 976617 [details]
File: limits
Comment 8 Reilly Hall 2015-01-05 21:37:29 UTC 
Created attachment 976618 [details]
File: maps
Comment 9 Reilly Hall 2015-01-05 21:37:29 UTC 
Created attachment 976619 [details]
File: open_fds
Comment 10 Reilly Hall 2015-01-05 21:37:30 UTC 
Created attachment 976620 [details]
File: proc_pid_status
Comment 11 Reilly Hall 2015-01-05 21:37:31 UTC 
Created attachment 976621 [details]
File: var_log_messages
Comment 12 Orion Poplawski 2015-01-05 22:22:11 UTC 
Filed upstream: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=717

This looks like infinite recursion in the _XIDHandler() libX11 code.  Not sure there is anything to be done besides trying to rebase nx-libs on a newer Xorg X11 release, but that's a pretty big undertaking.
Comment 13 Orion Poplawski 2015-07-14 21:09:06 UTC 
If you are feeling adventurous - please test out pre-release versions of nx-libs here: http://copr-fe.cloud.fedoraproject.org/coprs/orion/nxlibs36/ and let me know if it helps or makes things worse.
Comment 14 Fedora End Of Life 2015-11-04 15:52:13 UTC 
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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.
Comment 15 Fedora End Of Life 2015-12-02 06:58:03 UTC 
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.