My laptop and main machine are running 2.3.1 rc 1. If I screen share from my laptop to my main machine - I cannot get any control characters through to X apps on the main machine. Typing Ctrl-C on the laptop puts 'c' into an open xterm on the main machine. I think what is happening is KeyPress event, serial 22, synthetic NO, window 0x600001, root 0x45, subw 0x0, time 3665126062, (78,117), root:(162,507), state 0x0, keycode 67 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: "" KeyRelease event, serial 22, synthetic NO, window 0x600001, root 0x45, subw 0x0, time 3665127000, (78,117), root:(162,507), state 0x4, keycode 67 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: "" KeyPress event, serial 22, synthetic NO, window 0x600001, root 0x45, subw 0x0, time 3665127000, (78,117), root:(162,507), state 0x0, keycode 16 (keysym 0x63, c), same_screen YES, XLookupString gives 1 bytes: "c" KeyRelease event, serial 22, synthetic NO, window 0x600001, root 0x45, subw 0x0, time 3665127073, (78,117), root:(162,507), state 0x0, keycode 16 (keysym 0x63, c), same_screen YES, XLookupString gives 1 bytes: "c" This is from an xev running on the main machine. I didn't release the CTRL button when hitting the 'c'. It looks as if hitting the 'c' provokes a key up event. Odd.
Is this a regression? I changed the modifier key handling to _always_ update modifier keys on every event, not just NSFlagsChanged to work around stuck modifiers during space change, etc... so if it is a regression, then it is a bug in screen sharing because it's sending the 'c' event with the incorrect modifiers (and no corresponding NSFlagsChanged event beforehand). Can you please report this at bugreport.apple.com --Jeremy On Aug 19, 2008, at 03:19, Peter Collinson wrote:
My laptop and main machine are running 2.3.1 rc 1.
If I screen share from my laptop to my main machine - I cannot get any control characters through to X apps on the main machine.
Typing Ctrl-C on the laptop puts 'c' into an open xterm on the main machine.
I think what is happening is
KeyPress event, serial 22, synthetic NO, window 0x600001, root 0x45, subw 0x0, time 3665126062, (78,117), root:(162,507), state 0x0, keycode 67 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: ""
KeyRelease event, serial 22, synthetic NO, window 0x600001, root 0x45, subw 0x0, time 3665127000, (78,117), root:(162,507), state 0x4, keycode 67 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: ""
KeyPress event, serial 22, synthetic NO, window 0x600001, root 0x45, subw 0x0, time 3665127000, (78,117), root:(162,507), state 0x0, keycode 16 (keysym 0x63, c), same_screen YES, XLookupString gives 1 bytes: "c"
KeyRelease event, serial 22, synthetic NO, window 0x600001, root 0x45, subw 0x0, time 3665127073, (78,117), root:(162,507), state 0x0, keycode 16 (keysym 0x63, c), same_screen YES, XLookupString gives 1 bytes: "c"
This is from an xev running on the main machine.
I didn't release the CTRL button when hitting the 'c'. It looks as if hitting the 'c' provokes a key up event.
Odd.
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Ok, then I'm pretty certain it's a bug in screen sharing sending an incorrect [NSEvent modifiers] with the keypress... We didn't notice it before because we used to wait for an NSFlagsChanged event to update our modifier keys. Waiting like that caused us to actually *MISS* changes to the modifiers (such as the space-change stuck control). Now we update the modifiers on every NSEvent we receive. I'm affraid this bug will not be fixed in 2.3.1. Please file a bug at http://bugreport.apple.com and let me know the number so I can track it. Thanks, Jeremy On Aug 19, 2008, at 12:37, Jamie Kennea wrote:
On Aug 19, 2008, at 2:23 PM, Jeremy Huddleston wrote:
Is this a regression?
Yes, definitely. I've just started seeing this problem also with 2.3.1- rc1. I just tried screen sharing to a to machine with 2.3.0 installed and control modified keys works fine.
Jamie _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Sorry been away for some days.. done the report to bug reporter.
Your tracking number for this issue is Bug ID# 6165507.
On 20 Aug 2008, at 15:38, Jeremy Huddleston wrote:
Ok, then I'm pretty certain it's a bug in screen sharing sending an incorrect [NSEvent modifiers] with the keypress...
We didn't notice it before because we used to wait for an NSFlagsChanged event to update our modifier keys. Waiting like that caused us to actually *MISS* changes to the modifiers (such as the space-change stuck control). Now we update the modifiers on every NSEvent we receive. I'm affraid this bug will not be fixed in 2.3.1.
Please file a bug at http://bugreport.apple.com and let me know the number so I can track it.
Thanks, Jeremy
On Aug 19, 2008, at 12:37, Jamie Kennea wrote:
On Aug 19, 2008, at 2:23 PM, Jeremy Huddleston wrote:
Is this a regression?
Yes, definitely. I've just started seeing this problem also with 2.3.1- rc1. I just tried screen sharing to a to machine with 2.3.0 installed and control modified keys works fine.
Jamie _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
participants (3)
-
Jamie Kennea
-
Jeremy Huddleston
-
Peter Collinson