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!
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
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
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
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
Spoke too soon. This is driving me nuts. There seems to be no way to get my remapping of caps lock as ctrl to work (although it worked once!).
I've tried a bunch of remote desktops: mate, xfce, lxqt. I've tried setting on x2go client I/O to configure keyboard, don't configure keyboard, auto- detect. I've tried in the x2go session various ways to configure the keyboard. The best I can manage is that caps lock does nothing (the worst I can get is caps lock is stuck on and can't be turned off).
I'm baffled. I'm not an X expert, but if I run xev within the x2go session and hit capslock I see something about a keysym "capslock". So the concept of capslock is being propagated to the remote session. But I can't seem to remap it to do anything (like ctrl as I want) either through any gui keyboard config, or using setxkbmap.
The current setxkbmap state is (as told by the remote session) setxkbmap -query rules: evdev model: pc105 layout: us options: ctrl:nocaps,caps:ctrl_modifier
Neal Becker wrote:
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
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
On Mon, Apr 27, 2020 at 3:40 PM Neal Becker <ndbecker2@gmail.com> wrote:
Spoke too soon. This is driving me nuts. There seems to be no way to get my remapping of caps lock as ctrl to work (although it worked once!).
I've tried a bunch of remote desktops: mate, xfce, lxqt. I've tried setting on x2go client I/O to configure keyboard, don't configure keyboard, auto- detect. I've tried in the x2go session various ways to configure the keyboard. The best I can manage is that caps lock does nothing (the worst I can get is caps lock is stuck on and can't be turned off).
I have just checked, that works for me without wayland being involved) I have checked with xfce. x2go had the "determine keyboard automatically" setting.
I'm baffled. I'm not an X expert, but if I run xev within the x2go session and hit capslock I see something about a keysym "capslock". So the concept of capslock is being propagated to the remote session. But I can't seem to remap it to do anything (like ctrl as I want) either through any gui keyboard config, or using setxkbmap.
The current setxkbmap state is (as told by the remote session) setxkbmap -query rules: evdev model: pc105 layout: us options: ctrl:nocaps,caps:ctrl_modifier
which looks correct.
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.
That is clearly a mate issue. Destop Enviroments should be configured to not change the keyboard at all. Maybe you can try with a new user and see if it also happens in the default. I had sessions where it worked. But once you changed anything in the keyboard settings via the DE's system settings you could never go back to the default as this could not be enterd into the dialogs. So try with a fresh clean profile.
Uli
OK, tried with a new user profile. Tried a number of times, deleting and re-creating the user between attempts. There doesn't seem to be any way to get this working on wayland. Went back to X11 on the client and it's working fine.
On Mon, Apr 27, 2020 at 10:20 AM Ulrich Sibiller <uli42@gmx.de> wrote:
On Mon, Apr 27, 2020 at 3:40 PM Neal Becker <ndbecker2@gmail.com> wrote:
Spoke too soon. This is driving me nuts. There seems to be no way to
get
my remapping of caps lock as ctrl to work (although it worked once!).
I've tried a bunch of remote desktops: mate, xfce, lxqt. I've tried setting on x2go client I/O to configure keyboard, don't configure keyboard, auto- detect. I've tried in the x2go session various ways to configure the keyboard. The best I can manage is that caps lock does nothing (the worst I can get is caps lock is stuck on and can't be turned off).
I have just checked, that works for me without wayland being involved) I have checked with xfce. x2go had the "determine keyboard automatically" setting.
I'm baffled. I'm not an X expert, but if I run xev within the x2go session and hit capslock I see something about a keysym "capslock". So the concept of capslock is being propagated to the remote session. But I can't seem to remap it to do anything (like ctrl as I want) either through any gui keyboard config, or using setxkbmap.
The current setxkbmap state is (as told by the remote session) setxkbmap -query rules: evdev model: pc105 layout: us options: ctrl:nocaps,caps:ctrl_modifier
which looks correct.
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.
That is clearly a mate issue. Destop Enviroments should be configured to not change the keyboard at all. Maybe you can try with a new user and see if it also happens in the default. I had sessions where it worked. But once you changed anything in the keyboard settings via the DE's system settings you could never go back to the default as this could not be enterd into the dialogs. So try with a fresh clean profile.
Uli
-- *Those who don't understand recursion are doomed to repeat it*
-
Neal Becker -
Ulrich Sibiller