Hey, lads. I was following manual on official wiki about session broker installation in wsgi mode. It feels to me that manual isn't complete though.Apparently installing apache2, py3, wsgi mod support, x2gobroker-authservice and x2gobroker-wsgi and putting some changes into
Hey, people.Currently experimenting with x2go as remote assistance solution on Ubuntu 18.04. Have standard pc105 keyboard and en,ru,kz layouts, x2go client on Windows 10.It works fine when I x2go into new separate session - keys work as they should on any layout. However if I log into local
Hey, lads. I was following manual on official wiki about session broker installation in wsgi mode. It feels to me that manual isn't complete though.Apparently installing apache2, py3, wsgi mod support, x2gobroker-authservice and x2gobroker-wsgi and putting some changes into
Ok, I tried adding options like " -keyboard clone", " -keyboard query" and "keyboard pc105/us,ru,kz", " -keyboard rmlvo/evdev", " -keyboard rmlvo/xfree86" on server in x2goagent.options.. No difference at all. Client has disabled keyboard detection.Like it's not working. I almost thought it needs
Entschuldigung for late reply. This was a busy week.Anyway. I've tested your suggestions:1) No difference if I force evdev rules running shadow session - still wrong codes for comma, dot, slash and stuff like that on Russian and English layouts (it works correctly on KZ layout though but it was
As much as I can see it makes absolutely no difference if x2goclient has switch set on auto-detect keyboard settings and on disabled keyboard detection. Same wrong keycodes. If I force russian keyboard in x2goclient it behaves differently: Shift+2 returns "!", not "@" for example. Comma and dot
