Seeing that my issue is indeed different from both other submitters, I decided to go ahead and post a separate report (bug 1272). https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1272 The underlying cause may be turn out to be the same, so my new bug report may end up being a duplicate, or maybe not; difficult to say at this point. Please everyone who suffers from a segfaulty nxagent after a recent update to post to one of these bug reports. We need to attract developers' attention.