<br><tt><font size=2>freenx-knx-bounces@kde.org wrote on 26/02/2014 18:46:09:<br>
<br>
> Somehow my caps-lock state got out of sync with an NX/freenx session.</font></tt>
<br>
<br><tt><font size=2>Yup happens all the time,</font></tt>
<br><tt><font size=2> also with alt tightvn-vnc ( which has a nice
button to put it back)</font></tt>
<br><tt><font size=2>(</font></tt>
<br><tt><font size=2>I always end up with alt depressed after alt-tabb-ing
round to a session</font></tt>
<br><tt><font size=2>even tho I released alt :("</font></tt>
<br>
<br><tt><font size=2>I've seen it with just about every remote etc</font></tt>
<br><tt><font size=2><br>
> I run multiple simultaneous NX sessions, sometimes mixed with VNC,<br>
> vmware, x2go and synergy from the same desktop</font></tt>
<br>
<br><tt><font size=2>busy</font></tt>
<br>
<br><tt><font size=2>> so I'm not too surprised at something getting
the keyboard state wrong.</font></tt>
<br><tt><font size=2>> But, is there any way to fix it short of terminating
that session and<br>
> everything running in it? A suspend/reconnect still comes back
with<br>
> the state reversed from the actual keyboard - and from what any of
the<br>
> other apps on the local desktop see.</font></tt>
<br>
<br><tt><font size=2>Hmm well sort of there is.</font></tt>
<br>
<br><tt><font size=2>Method No.1 is to have a script on the NX server to
switch it</font></tt>
<br><tt><font size=2>independently of the client . . .</font></tt>
<br>
<br><tt><font size=2>You can probably download one, I haven't felt the
need yet.</font></tt>
<br>
<br>
<br><tt><font size=2>Method No. 2 - catch the right moment to switch the
client caps lock</font></tt>
<br>
<br><tt><font size=2>The two ends start off a connection with the</font></tt>
<br><tt><font size=2> then current state
of num-lock shift-lock etc</font></tt>
<br><tt><font size=2>then</font></tt>
<br><tt><font size=2> monitor key presses</font></tt>
<br><tt><font size=2>so</font></tt>
<br><tt><font size=2> sometimes
a key press gets missed if occurs at the wrong time</font></tt>
<br><tt><font size=2>so</font></tt>
<br><tt><font size=2>if you hit connect in the nxclient with caps lock</font></tt>
<br><tt><font size=2>then</font></tt>
<br><tt><font size=2>UN-CAPS LOCK just as the X session is starting, (after
authentication)</font></tt>
<br><tt><font size=2>you can get the session to miss the key-press.</font></tt>
<br>
<br>
<br><tt><font size=2>But you'll need to try a few times to get to know
when to do it.</font></tt>
<br>
<br>
<br><tt><font size=2>NOTES</font></tt>
<br><tt><font size=2>I've seen a few instances with the OpenNX client against
Opensuse 12.2 where</font></tt>
<br><tt><font size=2>I couldn't reconnect at all if there was a mismatch</font></tt>
<br><tt><font size=2> i.e I hit
caps lock by mistake in the session then disconnected</font></tt>
<br>
<br><tt><font size=2>(just tried it again and got</font></tt>
<br>
<br><tt><font size=2>Loop: PANIC! Can't identify NX port in string ':'.</font></tt>
<br><tt><font size=2>Error: Can't identify NX port in string ':'.</font></tt>
<br>
<br><tt><font size=2>followed by an actual re-connect, but with the WP
top menu fonts</font></tt>
<br><tt><font size=2>all messed up.</font></tt>
<br>
<br><tt><font size=2>BUT</font></tt>
<br><tt><font size=2>I wouldn't say that 12.2 was a typical distro version
tho</font></tt>
<br><tt><font size=2>and</font></tt>
<br><tt><font size=2>I've slightly modded my OpenNX too</font></tt>
<br><tt><font size=2>but I can't be bothered going through the source with</font></tt>
<br><tt><font size=2>OpenNX in its current state)</font></tt>
<br>
<br>
<br><tt><font size=2>A good fix is to disable caps lock which is mostly
useless,</font></tt>
<br><tt><font size=2>if not most useless.</font></tt>
<br>
<br><tt><font size=2>(I guess that 99%+ of caps lock use is by accident</font></tt>
<br><tt><font size=2>With me it's 100%</font></tt>
<br><tt><font size=2>( except when testing caps lock issues))</font></tt>
<br>
<br><tt><font size=2>see</font></tt>
<br><tt><font size=2> </font></tt><a href=http://capsoff.org/><tt><font size=2>http://capsoff.org</font></tt></a>
<br>
<br><tt><font size=2>but of course</font></tt>
<br><tt><font size=2>that doesn't solve alt and ctrl issues</font></tt>
<br>
<br>
<br><tt><font size=2><br>
> <br>
> -- <br>
> Les Mikesell<br>
> lesmikesell@gmail.com<br>
</font></tt>