Bug 1034313
Summary: | delete key is not mapped properly in x2go session | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andy Wang <dopey> |
Component: | x2goserver | Assignee: | Orion Poplawski <orion> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | orion, stefan.hoelldampf, ville.skytta |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-02-21 15:37:58 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andy Wang
2013-11-25 15:13:55 UTC
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. |