Re: [FreeRDP-devel] FreeRDP to Windows Server 2016 RDSH - Period key issue
Hi Neil,
On Tue, Oct 23, 2018 at 04:52:52PM +, Neil Broadbent via FreeRDP-devel
wrote:
> My understanding is that this is the correct place to ask for some support
> advice with FreeRDP. If i'm in the wrong spot, please let me know and I'll
> post to the appropriate location.
you are absolutely right here ;). You can also drop by in our irc
channel #freerdp on freenode for questions.
> Since switching from rdesktop to FreeRDP, the period key on the numeric
> keypad (US keyboard) has stopped functioning. Numlock itself works fine, as
> do all of the keypad numbers once numlock is engaged. Also, the key in
> question works as a delete key (as expected) with numlock disengaged, but
> with numlock engaged the period doesn't work. All other keys on the keyboard
> work as expected.
>
> I've recreated this outside of Thinlinc. From Ubuntu 18 Desktop,
> establishing a FreeRDP session directly to Windows 2016 has the same result.
> I have tried version 1 and version 2 builds of FreeRDP including the
> nightlies.
we haven't seen this issue yet and can't reproduce it here locally.
Just tried with the latest nightly
from Ubuntu 18.04 and Debian 9 as client machine to win 7/win 10/ win 2016 and
do get the expected keys on the remote side ('.' as well as 'DEL'). For the
test I've also used a US keymap.
So my guess would be that there are some differences in the key mapping.
Since you can reproduce it on Ubuntu could you provide us
the following information that that we can figure out what is going
on?
* output of "setxkbmap -print" on the Ubuntu side
* when you run xev on Ubuntu what do you get if you hit the Del/. key
with and without numlock enabled (I'm mainly interested in the key
press events xev shows)
* what keyboard language do you use on the windows side?
* for windows side keyboard debugging I tend to use a small utility
called KeyView.exe (you find it at
http://pub.freerdp.com/people/bmiklautz/KeyView.exe)
can you run it on the remote side when you are connected and tell me what you
get there when
pressing the key within the session?
For testing please use the latest nightly package from
https://ci.freerdp.com/job/freerdp-nightly-binaries/.
So long,
best regards
Bernhard
___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel
Re: [FreeRDP-devel] FreeRDP to Windows Server 2016 RDSH - Period key issue
Oh, obviously that was not meant for the mailing list :-) But in any case, let's hope we can find some solutions. Br, Peter On Wed, 24 Oct 2018, Peter Astrand wrote: Hi. It will be interesting to see if you get any response. I'm working with another customer which will deploy FreeRDP in ThinLinc later this year, and I know that there are some outstanding issues, for example wrt keyboard. I will take a look at some of the problems in a few weeks, let's keep in contact. Br, Peter On Tue, 23 Oct 2018, Neil Broadbent via FreeRDP-devel wrote: Hi All, My understanding is that this is the correct place to ask for some support advice with FreeRDP. If i'm in the wrong spot, please let me know and I'll post to the appropriate location. I've been working on deploying thin client solution using Cendio Thinlinc, which typically uses rdesktop to establish connections with a Windows session host. On advice from their devs, I've adjusted Thinlinc to connect to Windows with FreeRDP instead because of the superior multiple monitor support in FreeRDP. Since switching from rdesktop to FreeRDP, the period key on the numeric keypad (US keyboard) has stopped functioning. Numlock itself works fine, as do all of the keypad numbers once numlock is engaged. Also, the key in question works as a delete key (as expected) with numlock disengaged, but with numlock engaged the period doesn't work. All other keys on the keyboard work as expected. I've recreated this outside of Thinlinc. From Ubuntu 18 Desktop, establishing a FreeRDP session directly to Windows 2016 has the same result. I have tried version 1 and version 2 builds of FreeRDP including the nightlies. Through some digging I've found some information about the differences between how keyboards are handled by rdesktop and FreeRDP, as well as some mentions of making adjustments with XKB, but I am unsure where to start. Is this numeric keypad period issue a bug in FreeRDP or is this a case of there being something i need to tweak in ubuntu or the Windows terminal server? Any advice would be very greatly appreciated! Best regards, Neil ___ FreeRDP-devel mailing list FreeRDP-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel --- Peter Astrand Cendio AB https://cendio.com Teknikringen 8 https://twitter.com/ThinLinc 583 30 Linkopinghttps://facebook.com/ThinLinc Phone: +46-13-214600https://google.com/+CendioThinLinc --- Peter Astrand Cendio AB https://cendio.com Teknikringen 8 https://twitter.com/ThinLinc 583 30 Linkopinghttps://facebook.com/ThinLinc Phone: +46-13-214600https://google.com/+CendioThinLinc ___ FreeRDP-devel mailing list FreeRDP-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
Re: [FreeRDP-devel] FreeRDP to Windows Server 2016 RDSH - Period key issue
Hi. It will be interesting to see if you get any response. I'm working with another customer which will deploy FreeRDP in ThinLinc later this year, and I know that there are some outstanding issues, for example wrt keyboard. I will take a look at some of the problems in a few weeks, let's keep in contact. Br, Peter On Tue, 23 Oct 2018, Neil Broadbent via FreeRDP-devel wrote: Hi All, My understanding is that this is the correct place to ask for some support advice with FreeRDP. If i'm in the wrong spot, please let me know and I'll post to the appropriate location. I've been working on deploying thin client solution using Cendio Thinlinc, which typically uses rdesktop to establish connections with a Windows session host. On advice from their devs, I've adjusted Thinlinc to connect to Windows with FreeRDP instead because of the superior multiple monitor support in FreeRDP. Since switching from rdesktop to FreeRDP, the period key on the numeric keypad (US keyboard) has stopped functioning. Numlock itself works fine, as do all of the keypad numbers once numlock is engaged. Also, the key in question works as a delete key (as expected) with numlock disengaged, but with numlock engaged the period doesn't work. All other keys on the keyboard work as expected. I've recreated this outside of Thinlinc. From Ubuntu 18 Desktop, establishing a FreeRDP session directly to Windows 2016 has the same result. I have tried version 1 and version 2 builds of FreeRDP including the nightlies. Through some digging I've found some information about the differences between how keyboards are handled by rdesktop and FreeRDP, as well as some mentions of making adjustments with XKB, but I am unsure where to start. Is this numeric keypad period issue a bug in FreeRDP or is this a case of there being something i need to tweak in ubuntu or the Windows terminal server? Any advice would be very greatly appreciated! Best regards, Neil ___ FreeRDP-devel mailing list FreeRDP-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel --- Peter Astrand Cendio AB https://cendio.com Teknikringen 8 https://twitter.com/ThinLinc 583 30 Linkopinghttps://facebook.com/ThinLinc Phone: +46-13-214600https://google.com/+CendioThinLinc ___ FreeRDP-devel mailing list FreeRDP-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
