Numlock keys + navigation keys not working

Do you see any improvements setting it to en-us? I haven't a US keyboard so I can't be sure it works properly, are there differences between them?

When I turn key mapping 'us' off, all functions mentioned seems to work. This might be related to https://bugs.launchpad.net/bugs/478215 in which I describe that many keys do not work, unless in 'us' mode.

So the situation is now:
- when in default mode, some keys like <>,.[]{} do not work (workaround: switch to 'us' mode)
- when in 'us' mode, numerical en navigational part do not work or not as expected.

Placed between a rock a hard place? :-(

Reassigning to remmina, mind trying with new version?

I've tested this again with Ubuntu 10.04 + Remmina 0.7.4: the situation is not changed from the original description, numerical + navigation keys do not work in 'us'-mode.

Under 'common'-mode, numerical + navigation keys DO work (just like the default setting 'node').

In running Ubuntu 12.04, and this is still an issue. My number keys on my "10 key pad" (that is built into my laptop), don't work in Remmina; they don't get sent to the remote desktop.

Fixing this, may be a simple as flipping a boolean value in the source code.

On my laptop, if turn my Num Lk key *OFF*, then I can type numbers. It is the opposite of what it is supposed to be.

I can confirm comment #6: Num lock on, number pad works as arrow keys and num lock off, number pad works as number keys. Surely this is straightforward to fix.

can someone please include the patch in the .deb
This bug seems to be corrected long time ago (https://github.com/FreeRDP/Remmina/issues/45)

Is this ever going to make it into the repository? Will appreciate it!

This patch: https://launchpadlibrarian.net/121155317/remmina_1.0.0-1ubuntu8_1.0.0-99linvinus1.diff.gz
Can also be used to solve this issue. Will any of the maintainers please fix it finally?

I'm now expirencing this issue in Ubuntu 13.10. My number keypad doesn't work with Remmina if the num-lock is either on OR off (Dell Stuido 17).

Ubuntu 13.10
Keyboard: Corsair Vengeance K60
Unity DE

Pressing the numlock key doesn't toggle numlock, it just remains off. xev(1) shows these events when pressing the key:

KeyPress event, serial 40, synthetic NO, window 0x4200001,
    root 0xde, subw 0x0, time 10592959, (189,1204), root:(255,1257),
    state 0x10, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 40, synthetic NO, window 0x4200001,
    root 0xde, subw 0x0, time 10593053, (189,1204), root:(255,1257),
    state 0x10, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

I managed to work around it using numlockx(1), but it's not a good solution for any non-technical users, and it doesn't allow me to toggle numlock easily.

Since 4 years and a half ago ... Was hoping to see this fixed in 14.04 LTS ...

I suspect that, in all this time, this bug has never gotten to the right person. Someone knows how to easily fix this, but that person isn't getting to this bug report.

Sidenote: In addition to Num-Lock, Cap-Locks is also backwards sometimes.

Same problem Ubuntu 14.04, connecting RDP to Win2012R2.

I have the same problem, with Lubuntu 14.04 connecting to Win 2008 R2.

This issue also ocurrs on 14.04 and 14.10.
Just for comparison i've tested both Fedora 20 and 21 development version and they are not affected by this issue.

My exact problem is that local keyboard "lights" are not synchronized with remote.
When I start a connection to a windows machine, I have to click on num lock, which disables my local num lock (along with the light) for local typing but numeric keyboard works for the remote windows session.

My personal solution is to turn num lock off before starting a session. I am also "biased" to have the numlock indicators on in any remote programm (such as any office word processor) in order to be sure that still everything works.

By the way this "http://askubuntu.com/questions/423260/turn-num-lock-permanently-on" says that problem is solved in "https://launchpad.net/~remmina-ppa-team/+archive/ubuntu/remmina-next"

I guest that the version in Ubuntu 15.10 finally fixed this bug.
I made the upgrade and now I have no problems with numlock, can somebody check also if in 15.10 the problem is gone?