"stuck" meta key problem / NX-client / Mac / PC / Linux

[David Rogoff]

Hi all.

I've got a strange one thats messing me up and I'm not sure where to look.

Here's my situation:

Running GNU Emacs 23.1.1 (x86_64-unknown-linux-gnu, X toolkit, Xaw3d
scroll bars)

of 2010-02-19 on Linux (Red-Hat Enterprise).

I'm accessing the Linux desktop using NX-Client
(http://www.nomachine.com/products.php) from both a WinXP-SP3 PC at
work and an OS/X 10.6.2/3 ac Mini at home.

When I start a session/virtual desktop from home everything is fine.
However, when I disconnect and then reconnect to the session from work,
all my emacs windows think the meta key is being held down. For
example, when I hit the up arrow, I get the message "M-up is
undefined". It makes emacs unusable, requiring me to kill the editor
and start again, which sucks because I usually have a dozen buffers
going.

When I ran a PC at home, this didn't happen. It's something to do with
the meta mapping. On the Mac, something (NX-Client?) is mapping the
Windows key (= Apple command key) as meta, instead of Alt (= Apple
Option key). I think it's getting confused when I suspend the session
on the Mac and pick it up on the PC that it think the meta is on. This
doesn't affect other Linux windows or if I start a new emacs.

Any ideas? Is there some way to un-stick meta?

Thanks much!

David

[Colin S. Miller]

David Rogoff wrote:
> Hi all.
>
> I've got a strange one thats messing me up and I'm not sure where to look.

<snip>

>
> When I start a session/virtual desktop from home everything is fine.
> However, when I disconnect and then reconnect to the session from work,
> all my emacs windows think the meta key is being held down. For
> example, when I hit the up arrow, I get the message "M-up is
> undefined". It makes emacs unusable, requiring me to kill the editor
> and start again, which sucks because I usually have a dozen buffers going.
>

<snip>

> Any ideas? Is there some way to un-stick meta?
>
> Thanks much!
>
> David
>

David,
Did you use Meta-TAB to leave the VNC?
In this situation, I've seen VNC programs
send the meta keydown event to all the apps running
inside it, but not the meta keyup event.
Try tapping the meta key after you restore the connection.

Running xkeycaps inside the VNC will show which key X thinks is pressed.

HTH,
Colin S. Miller

--
Replace the obvious in my email address with the first three letters of the hostname to reply.

[rroh...@gmail.com]

I just had the same issue after using Ctrl-Alt-E: The Alt-key up event was lost and the cursor was stuck in the "hand" state. I was able to get rid of it by switching to full screen (Ctrl-ALt-F) and hitting both Alt keys a couple times. Soon Alt-Tab worked in the client and then I could also dismiss the Ctrl-Alt-E notification.