Forum Replies Created
-
Posts
-
From screenfetch
OS: Fedora
Kernel: x86_64 Linux 4.18.19-100.fc27.x86_64
Shell: bash 4.4.23
Resolution: 1920×1080
DE: Cinnamon 3.8.9 <——- I think this is what you want to know?
WM: Muffin
WM Theme: cinnamon (Arc-Dark-solid)
GTK Theme: Arc-Dark-solid [GTK2/3]
Icon Theme: Mint-Y
CPU: Intel Xeon E5-1607 v4 @ 4x 3.1GHz [36.0°C]
GPU: Quadro M2000/PCIe/SSE2
RAM: 13178MiB / 32090MiBYeah, that’s the setting I modified. It’s been set as you suggested for over a week now with multiple reboots since.
No. I made that change early on in this triage. It made no discernible difference to my experience. Certainly no impact in the area of the CTRL key.
I don’t know what Wayland or Xorg are, but I did modify some setting to disable something related to Wayland that came up while searching around for help on this issue. I set some config value to 0 or 1 or something.
I’ve now uncovered a completely reproducible “recipe” for this. It happens every single time I close out and then reopen my NoMachine session.
1. Open NoMachine session to remote server.
2. Open a terminal. This isn’t strictly required, but makes the issue more obvious.
3. Hit CTRL + C (seemingly any CTRL + Key combo works, but this is the most straightforward).
4. Try to type “123”. Actually, only “1” will be typed and no other characters or keys work. Unable to click into other open windows, etc.
5. Repeat steps 3 and 4 to your heart’s content.6. System only gets unstuck when you hit CTRL + C several times in a row or press both CTRL keys simultaneously.
In my environment, this is working absolutely every time now.
I’ve also ruled out a few other things:
– It’s not my local keyboard that’s the issue. There’s no physical CTRL key issue. I’ve used the virtual keyboard on both the local and remote host and observed the same behavior.
– It’s seemingly related to the NoMachine session. I’ve logged onto that remote server directly – I have physical access to it from time to time – and repeated the process above and am unable to reproduce the issue. As soon as I reconnect via NoMachine (same login session, nothing was logged out at any point), the issue resurfaces. However, it ONLY resurfaces through NoMachine. If I try to do the procedure through the physical machine I’m connecting to, things are fine. In fact, they are fine in the NoMachine session after I do anything in the physical machine. But if I do nothing on the physical machine and hit the CTRL key on via NoMachine right after login, the problem appears.
– This problem is repeatable for every new terminal or terminal tab opened until I hit both CTRL keys, at which point it seemingly doesn’t happen for some time in any of the open terminals.
It happens in ALL applications.
The ‘xev’ output looks like this. Nothing interesting happening through this tool. All key combinations are showing press and release events. I didn’t see anything that looked like a release event was skipped. However, when I switched over to another terminal, I was able to get it to happen within 2 presses – and it annoyingly closed my terminal too.
KeyPress event, serial 38, synthetic NO, window 0x5e00001,
root 0x235, subw 0x0, time 422987320, (70,184), root:(931,642),
state 0x10, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: FalseKeyPress event, serial 38, synthetic NO, window 0x5e00001,
root 0x235, subw 0x0, time 422987385, (70,184), root:(931,642),
state 0x14, keycode 54 (keysym 0x63, c), same_screen YES,
XLookupString gives 1 bytes: (03) “”
XmbLookupString gives 1 bytes: (03) “”
XFilterEvent returns: FalseKeyRelease event, serial 38, synthetic NO, window 0x5e00001,
root 0x235, subw 0x0, time 422987500, (70,184), root:(931,642),
state 0x14, keycode 54 (keysym 0x63, c), same_screen YES,
XLookupString gives 1 bytes: (03) “”
XFilterEvent returns: FalseKeyRelease event, serial 38, synthetic NO, window 0x5e00001,
root 0x235, subw 0x0, time 422987690, (70,184), root:(931,642),
state 0x14, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: FalseCan I run xev in the background and not use the tester app to log the key presses?