On 11/03/2017 07:58 PM, Robert Kudyba wrote:
> On another server that works OK I just killed an X2Go session from August!
> student 21855 0.0 0.0 151456 632 ? S Aug31 0:23
> /usr/lib64/nx/../x2go/bin/x2goagent -extension XFIXES -nolisten tcp -nolisten
> tcp -dpi 120 -D -auth /hom
>
> > Yes.
>
> That's weird, it sounds like sessions are accumulating in the database,
> but not
> printed out. This shouldn't happen, since sessions in the failed state
> should be
> automatically removed when executing this program (and also indirectly
> through
> this mechanism by x2gocleansessi
On 11/02/2017 08:57 PM, Robert Kudyba wrote:
> Yes.
That's weird, it sounds like sessions are accumulating in the database, but not
printed out. This shouldn't happen, since sessions in the failed state should be
automatically removed when executing this program (and also indirectly through
this m
Processing control commands:
> reassign -1 x2goclient 4.1.1.0
Bug #976 [x2goserver] error on login to ubuntu/debian -> stdin: is not a tty
Bug reassigned from package 'x2goserver' to 'x2goclient'.
No longer marked as found in versions 4.0.1.19-0~1064~ubuntu14.04.1.
Ignoring request to alter fixed
Control: reassign -1 x2goclient 4.1.1.0
Control: tag -1 not-a-bug
Control: close -1
Closing this bugreport as not a bug.
X2Go Client has seen some changes in the past, including spawning login shells,
which means that more shell startup scripts are executed now.
If these don't check for interact
