On Mon, Jan 12, 2015 at 5:45 AM, Babutzka, Martin (EKP) <martin.babutzka@kit.edu> wrote:
Hey Mikes :-)
Thanks for your replies. We resolved the problem by recommending the x2go client version 4.0.2.1 to our users which includes a sufficiently old Vcxsrv. We are fine with this solution. Please keep this upstream-bug in vcxsrv in mind for the case more applications show the problem and replicated bug reports are created.
Thanks for your efforts on the x2go-software! Martin [...]
No problem.
I'm glad you have a workaround for the time being.
-Mike#2