Bug 258546

Summary: CTRL key release event in remote session lost when switching virtual screens by CTRL-F1, CTRL-F2 and so on
Product: [Applications] krdc Reporter: RenĂ© Krell <renda.krell>
Component: generalAssignee: Urs Wolfer <uwolfer>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description René Krell 2010-12-02 10:27:30 UTC
Version:           unspecified (using KDE 4.5.80) 
OS:                Linux

When using the standard shortcuts for switching virtual screens in KDE, CTRL-F1 for switching to screen 1, CTRL-F2 to screen 2 and so on, the release event of the CTRL key gets often lost for a KRDC session I'm leaving this way. If I switch again to the screen with KDRC the remote session behaves as if I leave CTRL pressed. I have to press CTRL again to get this reset to the normal behavior.

It seems like KWin or something like that catches this event and doesn't route it to the KRDC application.

Reproducible: Sometimes

Steps to Reproduce:
1. On virtual screen 2, open a KRDC session, regardless whether VNC or RDP
2. Launch some application on the remote session, where you can recognize the unreleases CTRL key, for instance in Windows Total Commander, which selects files or dirs when clicking on them while CTRL is pressed.
3. Switch to screen 1 using the shortcut CTRL-F1
4. Switch back to screen 2 using the shortcut CTRL F2

Actual Results:  
Total Commander for instance behaves as the CTRL key was pressed when clicking on entries, but CTRL isn't actually pressed.

Expected Results:  
Send the CTRL release event to the current KRDC session before leaving it.

OS: Linux (x86_64) release 2.6.34.7-0.5-desktop
Compiler: gcc
Comment 1 Urs Wolfer 2010-12-19 12:26:16 UTC

*** This bug has been marked as a duplicate of bug 162723 ***