One other issue: I've had problems with my keyboard layout for a long time under X11. I run with Capslock remapped to Ctrl. Now running on wayland, I set x2go client to "do not configure keyboard". When I reconnect to my session (running mate), in settings it has layout (system/preferences/hardware/keyboard/layout/options) set 'ctrl position: caps lock as ctrl'. I have to turn this off. Now caps lock is working as ctrl as I want. But every time I reconnect I have to go through this setting, otherwise caps lock is not acting as ctrl, it's acting as caps lock.
Ulrich Sibiller wrote:
At the same time. You might not be able to run the same desktop environment in both sessions but you can try with different users or just two terminals.
Uli
On Sun, Apr 26, 2020 at 4:03 PM Neal Becker <ndbecker2@gmail.com> wrote:
You mean running 2 at the same time or sequentially?
On Sun, Apr 26, 2020, 10:01 AM Ulrich Sibiller <uli42@gmx.de> wrote:
On Sun, Apr 26, 2020 at 2:25 PM Neal Becker <ndbecker2@gmail.com> wrote:
I just updated to kde-20 on fedora 31, and once again trying kde over wayland. Previously x2go wouldn't work, but trying it now it seems to be working!
Good to hear that! So it seems that was tied to Xwayland rather than x2go.
A colleague of mine had tested just that (I think on ArchLinux). The first session worked, but starting a second one lead to crashes of the whole desktop. Can you confirm?
Uli
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user