Forum / NoMachine for Linux / “Grab the keyboard input” does not work anymore
- This topic has 10 replies, 3 voices, and was last updated 4 months, 2 weeks ago by Britgirl.
-
AuthorPosts
-
June 27, 2024 at 07:52 #48651maxim-nomachineParticipant
It sends such shortcuts like Alt+F4 to local host and to remote host. Previously it was possible to send it to remote one only.
I guess it is related in some way to KDE updates, but maybe I am wrong, I am not able to dissect it.
Operating System: openSUSE Tumbleweed 20240625
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.6-1-default (64-bit)
Graphics Platform: X11NXPLAYER – Version 8.11.3
June 27, 2024 at 14:47 #48653BritgirlKeymasterWhat is the OS on the nxplayer side?
Did you try a reboot on the openSUSE side? Is the issue just the Alt F4 key or other Alt+ combinations? Are other keys affected?Please describe the steps you take to reproduce the behaviour.
June 27, 2024 at 19:33 #48655olafParticipantI also noticed similar issue after KDE Plasma was updated to 6.1.0 on client-side computer. Shortcut keys are now captured by local computer running NoMachine client instead of being sent over to remote computer.
Thank you!
June 28, 2024 at 08:06 #48654maxim-nomachineParticipantWhat is the OS on the nxplayer side?
The version provided is nxplayer side. Version of the remote one is OpenSUSE Leap 15.6.
Did you try a reboot on the openSUSE side?
Yes, both sides. All updates are installed, systems are rebooted.
Is the issue just the Alt F4 key or other Alt+ combinations?
I assigned custom shortcut Meta+R in System Settings | Shortcuts
The app executed in both systems: local and remote (if grab is enabled, if not then only local system).
Please describe the steps you take to reproduce the behaviour.
Nothing specific most likely it started to happen after update of local side. Maybe some incompatibility with fresh rolling libs.
I just tested another environment and it works fine:
Operating System: openSUSE Tumbleweed 20240621
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Kernel Version: 6.9.5-1-default (64-bit)
Graphics Platform: X11After updating to latest version (zypper dup) it has the same grab input issue. Updated system the same as originally tested one:
Operating System: openSUSE Tumbleweed 20240625
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.6-1-default (64-bit)
Graphics Platform: X11June 28, 2024 at 09:40 #48658BritgirlKeymasterCan you start the player from a terminal instead like this?
/usr/NX/bin/nxplayer --activegrab
Btw, Check what’s configured in your nxs file because this setting will override your global setting (configured in Player). You can check what’s in the .nxs file by locating it in the directory defined in the ‘Connections and recordings’ field from the Settings -> Player -> Folders panel of the User Interface.
June 28, 2024 at 14:32 #48659maxim-nomachineParticipantCan you start the player from a terminal instead like this?
/usr/NX/bin/nxplayer –activegrabCheck what’s configured in your nxs file because this setting will override your global setting (configured in Player). You can check what’s in the .nxs file by locating it in the directory defined in the ‘Connections and recordings’ field from the Settings -> Player -> Folders panel of the User Interface.
What is the reason to do that?
I wrote:
I assigned custom shortcut Meta+R in System Settings | Shortcuts The app executed in both systems: local and remote (if grab is enabled, if not then only local system).
Obviously it says that I have the way to confirm if grab was really enabled or not.
/usr/NX/bin/nxplayer –activegrab
It was tested before I created this issue. It does not have any effect.
June 28, 2024 at 15:14 #48662BritgirlKeymasterIt was tested before I created this issue. It does not have any effect.
I see, I didn’t see you mention that earlier. Anyway, we are still unable to reproduce the problem with grabbing the keyboard on Plasme 6. But we did find a bug report on the KDE bugzilla. It seems very like your issue.
https://bugs.kde.org/show_bug.cgi?id=489113
For now, we suggest to downgrade to the environment that you said is working for you and wait for KDE to release a fix.
June 28, 2024 at 21:57 #48664maxim-nomachineParticipantOK, I will check with KDE if you think nothing should be made on NoMachine side.
Just one question. Should grab work in Wayland session?
July 29, 2024 at 17:11 #48944BritgirlKeymasterWe’re not aware of keyboard grab not working on Wayland. Did you try?
August 3, 2024 at 05:25 #49018maxim-nomachineParticipantYes, I tried and it does not work in Wayland.
But VMWare Workstation can successfully grab keyboard input for its window in any DE.
So grab in VMWare works even for updated KDE >= 6.1.x
I do not know what other can be considered as a test.
I will wait version 6.2.0 to check fixed KDE issue: Version Fixed In: 6.2.0
August 7, 2024 at 17:36 #49114BritgirlKeymasterWe’ve been able to reproduce unusual behaviour with KDE 6.1 as well, but not the exact same problem as yours. We will keep the investigation open for the time being and wait for KDE 6.2 to come out so that we can check against that.
Edit: KDE 6.2 was released, fixing https://bugs.kde.org/show_bug.cgi?id=489113
-
AuthorPosts
This topic was marked as solved, you can't post.