Ctrl-Alt-Shift-F doesn't work anymore

[Torsten Kupke]

Hi,

since I have installed Windows 10 V. 1903, pressing Ctrl-Alt-Shift-F
doesn't work anymore to leave the full screen mode (nothing does
happen). Fortunately I have a small transparent clock widget, which is
running on my local Windows machine and I can click on. So I can use
Alt-Tab to switch to another local window on my Windows screen. Without
that Alt-Tab would only switch between Windows in the remote session. Is
there a workaround to get back the old reaction on Ctrl-Alt-Shift-F?

Best regards

Torsten

[DRC]

As a temporary workaround, you could edit the Start Menu shortcut for "TurboVNC Viewer" or "Java TurboVNC Viewer" and pass -fsaltenter as an argument to either vncviewer.exe or vncviewer-java.bat.  That will allow you to use Alt-Enter to switch in and out of full-screen mode.

Please indicate which version of the viewer (native or Java) you are using, and I will try to reproduce the problem.

[Torsten Kupke]

Hi DRC,

I use vncviewer.exe, version 2.2.1.

I will try your workaround.

Many thanks!

Best regards

Torsten

Am 19.06.19 um 18:35 schrieb DRC:

--
You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to turbovnc-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/a6dbf019-3940-2f12-af1b-6b6f9785140d%40virtualgl.org.
For more options, visit https://groups.google.com/d/optout.

[Torsten Kupke]

Hi again,

with -fsaltenter Alt-Enter doesn't work too. :'(

Best regards

Torsten

To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/2528cfd6-ed6c-283b-018b-7e2ab675c8d5%40hacon.de.

[DRC]

I'll try to reproduce whenever I have time, but in the meantime, please
verify whether the issue also exists in the Java viewer.

>>> <mailto:turbovnc-user...@googlegroups.com>.

>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/turbovnc-users/a6dbf019-3940-2f12-af1b-6b6f9785140d%40virtualgl.org

>>> <https://groups.google.com/d/msgid/turbovnc-users/a6dbf019-3940-2f12-af1b-6b6f9785140d%40virtualgl.org?utm_medium=email&utm_source=footer>.

>>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "TurboVNC User Discussion/Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to turbovnc-user...@googlegroups.com

>> <mailto:turbovnc-user...@googlegroups.com>.

>> To view this discussion on the web visit

>> https://groups.google.com/d/msgid/turbovnc-users/2528cfd6-ed6c-283b-018b-7e2ab675c8d5%40hacon.de
>> <https://groups.google.com/d/msgid/turbovnc-users/2528cfd6-ed6c-283b-018b-7e2ab675c8d5%40hacon.de?utm_medium=email&utm_source=footer>.

>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google
> Groups "TurboVNC User Discussion/Support" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to turbovnc-user...@googlegroups.com

> <mailto:turbovnc-user...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/turbovnc-users/03126e97-34b5-b75a-3e02-b83a6083ab4c%40hacon.de
> <https://groups.google.com/d/msgid/turbovnc-users/03126e97-34b5-b75a-3e02-b83a6083ab4c%40hacon.de?utm_medium=email&utm_source=footer>.

[Torsten Kupke]

Hi DRC,

I can't find vncviewer-java.bat in my install directory of TurboVNC.
There are only cvncviewer.exe, vncviewer.exe, putty.exe, unins000.exe,
unins001.exe and some other non-executable files.

Best regards

Torsten

[DRC]

You probably didn't select the Java viewer option when you installed it.

[Torsten Kupke]

May be so, don't know anymore. If I find time, I could try that.

--
Torsten Kupke
Development Planning/Disposition Systems

HaCon Ingenieurgesellschaft mbH
Lister Str. 15, 30163 Hannover, Germany
Tel. +49 511 33699-464
Fax. +49 511 33699-99
Torste...@hacon.de
http://www.hacon.de

Office/Sitz: Hannover, Registry Court/Amtsgericht: Hannover HRB 1712
Managing Directors/Geschäftsführer:
Michael Frankenberg (CEO), Andreas Dittmann (CFO), Claus Müller-Haude

HaCon - A Siemens Company

[Torsten Kupke]

Hi DRC,

I just installed the Java viewer. When double-clicking vncviewer-java.bat, it opens a huge cmd.exe window, and inside I read this:

jawt.dll path: C:\Program Files (x86)\Java\jre1.8.0_211\bin
You must use a amd64 Java Runtime Environment with this version of TurboVNC.

The second line appears in a popped up message box too. When I click OK, both disppear. Where can I get that amd64 Java Runtime Environment?

And could you reproduce this issue under Windows 10 V. 1903? It is still existent here.

Best regards

Torsten

[DRC]

You can either download and install the amd64 (x64) JRE from https://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html or simply install the 32-bit TurboVNC Windows package, which will match your existing 32-bit JRE. The need to install a JRE will go away in TurboVNC 3.0.

--
You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group.

To unsubscribe from this group and stop receiving emails from it, send an email to turbovnc-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/3618fdb2-a430-332f-61c2-9fe908fb0386%40hacon.de.

[Torsten Kupke]

Hi DRC,

I installed the x64 JRE from Oracle. Now I get this, when providing the same .vnc file to vncviewer-java.bat as to vncviewer.exe:

jawt.dll path: C:\Program Files\Java\jre1.8.0_211\bin
CConn: connected to host localhost port 35901
CConnection: Server supports RFB protocol version 3.8
CConnection: Using RFB protocol version 3.8
com.turbovnc.rdr.SystemException: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)
        at com.turbovnc.rfb.CSecurityTLS.processMsg(CSecurityTLS.java:155)
        at com.turbovnc.rfb.CSecurityTLS.processMsg(CSecurityTLS.java:119)
        at com.turbovnc.rfb.CSecurityStack.processMsg(CSecurityStack.java:40)
        at com.turbovnc.rfb.CSecurityVeNCrypt.processMsg(CSecurityVeNCrypt.java:179)
        at com.turbovnc.rfb.CSecurityTight.processMsg(CSecurityTight.java:56)
        at com.turbovnc.rfb.CConnection.processSecurityMsg(CConnection.java:210)
        at com.turbovnc.rfb.CConnection.processMsg(CConnection.java:61)
        at com.turbovnc.vncviewer.VncViewer.run(VncViewer.java:842)
        at java.lang.Thread.run(Unknown Source)

One note for your info: The connection configured by the .vnc file goes through an existing ssh tunnel with port 5901 at its remote end. So the client shouldn't establish and use its own one.

What can I do now?

Best regards

Torsten

To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/BC22AA58-43E6-4C15-8393-7E920962B0AC%40virtualgl.org.

[DRC]

That issue was fixed in TurboVNC 2.2.2. Are you sure you're running the
latest version?

On 7/1/19 1:15 PM, Torsten Kupke wrote:
> Hi DRC,
>

>> <mailto:tor...@hacon.de>> wrote:
>>
>>> Hi DRC,
>>>
>>> I just installed the Java viewer. When double-clicking
>>> vncviewer-java.bat, it opens a huge cmd.exe window, and inside I read
>>> this:
>>>
>>> jawt.dll path: C:\Program Files (x86)\Java\jre1.8.0_211\bin
>>> You must use a amd64 Java Runtime Environment with this version of
>>> TurboVNC.
>>>
>>> The second line appears in a popped up message box too. When I click

>>> OK, both disppear. Where can I get that *amd64 Java Runtime Environment*?

>>> <mailto:turbovnc-user...@googlegroups.com>.

>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/turbovnc-users/3618fdb2-a430-332f-61c2-9fe908fb0386%40hacon.de

>>> <https://groups.google.com/d/msgid/turbovnc-users/3618fdb2-a430-332f-61c2-9fe908fb0386%40hacon.de?utm_medium=email&utm_source=footer>.

>>> For more options, visit https://groups.google.com/d/optout.
>> --
>> You received this message because you are subscribed to the Google
>> Groups "TurboVNC User Discussion/Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to turbovnc-user...@googlegroups.com

>> <mailto:turbovnc-user...@googlegroups.com>.

>> To view this discussion on the web visit

>> https://groups.google.com/d/msgid/turbovnc-users/BC22AA58-43E6-4C15-8393-7E920962B0AC%40virtualgl.org
>> <https://groups.google.com/d/msgid/turbovnc-users/BC22AA58-43E6-4C15-8393-7E920962B0AC%40virtualgl.org?utm_medium=email&utm_source=footer>.

>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google
> Groups "TurboVNC User Discussion/Support" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to turbovnc-user...@googlegroups.com

> <mailto:turbovnc-user...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/turbovnc-users/b0f2b2cc-2d9d-70b8-7bfd-4a302b8a1de3%40hacon.de
> <https://groups.google.com/d/msgid/turbovnc-users/b0f2b2cc-2d9d-70b8-7bfd-4a302b8a1de3%40hacon.de?utm_medium=email&utm_source=footer>.

[Torsten Kupke]

Ok, that I missed. Just installed it. Now the connection works with the
java client. But the issue remains: Ctrl-Alt-Shift-F doesn't work.
Additionally the auto scroll feature doesn't work. Instead I have scroll
bars in the full screen window. But may be the auto scroll feature is
only implemented in the native Windows client.

I also tried the -fsaltenter option again. And no, Alt-Enter doesn't
work too.

Could you reproduce this issue under Windows 10 V. 1903 in the meantime?

[DRC]

The bump scroll feature is not implemented in the Java viewer. Most
users these days opt to use the automatic desktop resizing feature
instead of bump scrolling, so there hasn't been a demand for me to add
the latter (and thus no funding to do so.) Here is a list of other
features that are needed in the Java TurboVNC Viewer in order to avoid
feature regression vs. the Windows TurboVNC Viewer:

https://github.com/TurboVNC/turbovnc/milestone/4

In general, I am in need of project funding in order to complete the
TurboVNC 3.0 release-- particularly without feature regressions. I
mention this in hopes that someone listening might step up to sponsor
the release.

Both hotkeys work fine for me under Windows 10 1809. 1903 isn't
available in my Windows Update yet. I will test it when it becomes
available. I do note that, at least on my machine, it was necessary to
use left Alt, but if your keyboard layout has AltGr like most European
keyboards do, then there should only be one Alt.

DRC

[Torsten Kupke]

Hi DRC,

Am 02.07.2019 um 08:30 schrieb DRC:
> The bump scroll feature is not implemented in the Java viewer. Most
> users these days opt to use the automatic desktop resizing feature
> instead of bump scrolling, so there hasn't been a demand for me to add
> the latter (and thus no funding to do so.) Here is a list of other
> features that are needed in the Java TurboVNC Viewer in order to avoid
> feature regression vs. the Windows TurboVNC Viewer:
>
> https://github.com/TurboVNC/turbovnc/milestone/4
>
> In general, I am in need of project funding in order to complete the
> TurboVNC 3.0 release-- particularly without feature regressions. I
> mention this in hopes that someone listening might step up to sponsor
> the release.

Is there another way to donate than using digital coins or via Paypal?
Both I don't want to handle with. But I want to donate some money to the
project I'm using every day.

>
> Both hotkeys work fine for me under Windows 10 1809. 1903 isn't
> available in my Windows Update yet. I will test it when it becomes
> available.

May be Microsoft thinks, your Windows machine isn't ready to get Version
1903. They periodicly try to figure out this.

> I do note that, at least on my machine, it was necessary to
> use left Alt, but if your keyboard layout has AltGr like most European
> keyboards do, then there should only be one Alt.

Yes, I only have one Alt key on the left, but I tried AltGr too, also
without success.

Best regards

Torsten

[DRC]

On 7/2/19 1:59 PM, Torsten Kupke wrote:

Is there another way to donate than using digital coins or via Paypal? Both I don't want to handle with. But I want to donate some money to the project I'm using every day.

Venmo and wire transfer are the only other ways I can think of.  I use wire transfers for receiving large payments from general sponsors or funded development opportunities, but my bank dings me for a $16 transfer fee every time that happens, so it's not something I can afford to do unless the payment is relatively large.  If you have any other suggestions for methods of payment I should accept, I am receptive to that advice.

[Torsten Kupke]

Hi DRC,

Am 02.07.2019 um 20:59 schrieb Torsten Kupke:
> Hi DRC,
>

> Am 02.07.2019 um 08:30 schrieb DRC:

> ...

>>    I do note that, at least on my machine, it was necessary to
>> use left Alt, but if your keyboard layout has AltGr like most European
>> keyboards do, then there should only be one Alt.
>
> Yes, I only have one Alt key on the left, but I tried AltGr too, also
> without success.

I just tested the Java client again, because I remembered, that it
supports F8 to display a pulldown menu, which has a Close connection
entry. That's the way I use directly on the console of the TVNC server
to close the session connection. And yes, F8 works under Windows 10 1903
too. However I will use the native Windows client furthermore, because
of the missing bump scroll feature in the Java client. Therefore I would
prefer, that the native Windows client would support the F8 menu too.
>
> Best regards
>
> Torsten

[DRC]

On 7/7/19 5:31 AM, Torsten Kupke wrote:
> I just tested the Java client again, because I remembered, that it
> supports F8 to display a pulldown menu, which has a Close connection
> entry. That's the way I use directly on the console of the TVNC server
> to close the session connection. And yes, F8 works under Windows 10 1903
> too. However I will use the native Windows client furthermore, because
> of the missing bump scroll feature in the Java client. Therefore I would
> prefer, that the native Windows client would support the F8 menu too.

The Windows 10 update number is confusing me. The latest update
(6/2019) was just made available to me, and I updated to it, but my
installation is still numbered 1803, not 1903. So I'm not 100% sure
that I am using the same version you are using. I can confirm, however,
that I am still unable to reproduce the hotkey problem despite updating
to the latest bits that are available as of today.

The equivalent of the F8 menu in the native Windows TurboVNC Viewer is
the Windows system menu, which is accessed by clicking on the upper left
of the title bar. Normally you could also pop up that menu with
Alt-Space, but the Windows TurboVNC Viewer transmits that key sequence
to the server. It is possible to implement an F8 menu in the native
Windows TurboVNC Viewer (which would basically just involve popping up
the existing system menu when F8 is pressed), but given that the native
Windows TurboVNC Viewer is going away in TurboVNC 3.0, I would much
rather spend my time shoring up any deficiencies that currently exist in
the Java TurboVNC Viewer vs. the native viewer.

Given that I am unable to reproduce the problem, there's no way I can
fix it. However, here are some possible solutions that I could
implement if your organization can provide funding for my labor:

1. An F8 menu in the native Windows TurboVNC Viewer. Given that this
would have to be implemented in the stable 2.2.x branch, I would need to
make it optional and disabled by default.

2. Allow Alt-Space to optionally pop up the native viewer's system menu
rather than transmitting that sequence to the server. This would also
have to be disabled by default. Given your general problems with any
Alt key sequences, you would need to first confirm that Alt-Space works
properly with other applications.

3. Add an option to the Java TurboVNC Viewer in TurboVNC 3.0 that would
allow the user to change the modifier key sequence used for the various
hotkeys. However, I'm not confident that this would fix the problem
you're experiencing, because if Alt-Enter isn't working, then that
points to a broader problem with modifier key events. Changing the
modifier keys probably wouldn't work around that problem.

[Torsten Kupke]

Hi DRC,

Am 08.07.19 um 22:39 schrieb DRC:

> On 7/7/19 5:31 AM, Torsten Kupke wrote:
>> I just tested the Java client again, because I remembered, that it
>> supports F8 to display a pulldown menu, which has a Close connection
>> entry. That's the way I use directly on the console of the TVNC server
>> to close the session connection. And yes, F8 works under Windows 10 1903
>> too. However I will use the native Windows client furthermore, because
>> of the missing bump scroll feature in the Java client. Therefore I would
>> prefer, that the native Windows client would support the F8 menu too.
> The Windows 10 update number is confusing me. The latest update
> (6/2019) was just made available to me, and I updated to it, but my
> installation is still numbered 1803, not 1903. So I'm not 100% sure
> that I am using the same version you are using. I can confirm, however,
> that I am still unable to reproduce the hotkey problem despite updating
> to the latest bits that are available as of today.

Your Windows 10 version definitly is one year older than my one. And
between both there was version 1809, which you missed too. Maybe you
only will get the newest version, if you explicitly search for Windows
Updates (there is a button in the Windows Update section of the Windows
Settings tool to do that). But be careful! Make a complete system
backup, before you start the version upgrade! If you don't upgrade,
Microsoft soon will stop support for your old version. Maybe Microsoft
will try to force you to upgrade. But maybe too, that your machine isn't
compatible with versions higher than 1803. In that case you should buy a
new one. ;-)

My employer hardly will sponsor your work, because here too few users
use TuboVNC. And I myself only could pay via SEPA bank transfer. But I
don't know, wether this is possible to your country.

I surely will have to wait for TurboVNC 3.0, I think.

Best regards

Torsten

[DRC]

On 7/9/19 12:25 PM, Torsten Kupke wrote:

Your Windows 10 version definitly is one year older than my one. And between both there was version 1809, which you missed too. Maybe you only will get the newest version, if you explicitly search for Windows Updates (there is a button in the Windows Update section of the Windows Settings tool to do that). But be careful! Make a complete system backup, before you start the version upgrade! If you don't upgrade, Microsoft soon will stop support for your old version. Maybe Microsoft will try to force you to upgrade. But maybe too, that your machine isn't compatible with versions higher than 1803. In that case you should buy a new one. ;-)

(BTW, it's a virtual machine, not a physical one.)  I was finally able to make it update by running the Windows Update Assistant.  I can confirm that Ctrl-Alt-Shift-F no longer works, although Alt-Enter works fine for me as long as I use the left Alt key and pass /fsaltenter on the TurboVNC Viewer command line.  Also, quite oddly, the other Ctrl-Alt-Shift key sequences work fine.  It is just Ctrl-Alt-Shift-F that does not work.  Investigating.

Also, re-reading your original post, the issue with Alt-Tab can be worked around by disabling keyboard grabbing.  The default behavior is to always grab the keyboard and thus transmit special keystrokes (Alt-Tab, Alt-Esc, etc.) to the server when in full-screen mode, but you can disable that behavior in the TurboVNC Viewer options.

Unfortunately SEPA bank transfers cannot be sent to the U.S.

[DRC]

I spent some time trying to diagnose the issue but was unable to.  The proximate cause is that, when Ctrl-Alt-Shift-F is pressed, Windows sends the TurboVNC Viewer application a WM_KEYUP event but not an associated WM_KEYDOWN event for the 'F' key.  Thus, the Win32 TranslateAccelerator() function does not detect the hotkey.  In other words, the operating system is swallowing the key press for the 'F' key whenever Ctrl-Alt-Shift is pressed.  I googled around but could not find any documentation indicating why that might be occurring, although it does appear that others are having the same problem:
https://superuser.com/questions/1445551/what-does-ctrlaltshiftf-key-combination-in-windows-10-pro-version-1903

I also could not find any documentation indicating why Ctrl-Alt-Shift-F is reserved, nor does that hotkey have any visible effect when pressed.  My gut says that there is probably some new O/S feature that is monitoring that hotkey, and if so, it should be possible to disable that feature or change its hotkey.  Otherwise, I have no ideas other than the features I proposed in the previous message, which I am unwilling to implement without funding.  I also have no idea why you can't make Alt-Enter work, since it works for me.  Using Alt-Enter would be the preferred workaround for this.

I would consider adding a new hotkey to toggle full-screen mode, but:
(a) I first need to understand whether it's possible to work around this issue at the O/S level (for instance, by changing or disabling a particular feature.)
(b) The Alt-Enter feature already does that, and given that that feature already works fine for me, I am disinclined to add yet another full-screen hotkey.

I'm sorry, but that's the limit of what I can do for free at the moment.  If you discover any new information that might be helpful, please follow up.

DRC

[Torsten Kupke]

Hi DRC,

now Alt-Enter works for me too. Formerly I tried "-fsaltenter" between
the exe and the vnc file paths. That didn't work. And "/fsaltenter" at
the same place also didn't. But "/fsaltenter" behind both works:

"C:\Program Files\TurboVNC\vncviewer.exe"
C:\Users\Torsten\Documents\ws-torsten-5901.vnc /fsaltenter

Regarding the issue with Ctrl-Alt-Shift-F we could try to contact
Microsoft Support. But I suppose, that would hardly be successful.
Perhaps you in the US have more chances for this than we in Europe.

Many thanks for the Alt-Enter workaround!

Best Regards

Torsten

[DRC]

OK, glad that you are able to make Alt-Enter work. I will consider
making that option accessible from the GUI in TurboVNC 3.0, which would
be an easy modification.