Description of problem: Delete key does not work properly in x2go session. Version-Release number of selected component (if applicable): $ rpm -q x2goserver x2goclient x2goserver-4.0.1.6-5.fc19.x86_64 x2goclient-4.0.1.1-1.fc19.x86_64 How reproducible: Always Steps to Reproduce: 1. run x2goclient. Configured for default keyboard pc105/us 2. connect to x2goserver 3. hit delete key Actual results: Delete key will actually delete. Expected results: In the MATE desktop, the delete key triggers the screenshot application as if print screen was used Additional info: xev captures the following event KeymapNotify event, serial 37, synthetic NO, window 0x0, keys: 4294967222 0 0 0 0 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 The keyboard file in the x2go session has the following contents: rules=evdev model=pc104 layout=us variant= options=terminate:ctrl_alt_bksp
Oops. Apologies, I got the Actual results: and Expected results: flipped in the above report.
I think this *might* be a dupe of 1033876. Could you try x2goserver-4.0.1.8-2 and see if that fixes it for you?
I couldn't find 4.0.1.8-2 looks like it was obsoleted. Found 4.0.1.9-1 in koji but that one simply just didn't work (server session would open and close). I haven't had a chance to debug it yet, but thought I'd mention this.
Problem reproduced here, connecting from x2goclient-4.0.1.2-1.fc19.x86_64 to x2goserver-4.0.1.9-2.fc19.x86_64.
I think this may be fixed with nx-libs-3.5.0.21-5. Please test https://admin.fedoraproject.org/updates/edit/nx-libs-3.5.0.21-5.fc19
Upgraded everything "*nx*" "*x2*" available from updates-testing, did not make a difference.
Something happened recently and this started working now. I note a nx-libs-3.5.0.22-1 update about a week ago. Maybe this did it?
Remains broken here.
Try using the new "Auto detect keyboard settings" in x2goclient perhaps? I'm at a loss now - it's working for me now too.
(In reply to Orion Poplawski from comment #9) > Try using the new "Auto detect keyboard settings" in x2goclient perhaps? Works for me too with that setting, thanks. I had it set to "Do not configure keyboard" when it didn't.