bug: ctrl + any key types the key repeatedly

i connect from ubuntu to a remote ubuntu, and when I'm connected, when using the CTRL it just types it repeatedly. (team viewer 13.0.6634, and both Ubuntu 16.04)

for examle:

CTRL+c will output in the terminal "ccccccccccccccccccccccccccccccccccccccccccccc"

it makes it really hard to work on a linux terminal as CTRL is oftenly used.

Find more posts tagged with

Comments

TVTesterDRB

Does anyone know if this bug was ever addressed and resolved?

I have installed the latest version of TeamViewer and, though I am not a gamer, I am experiencing this same issue using Adobe Photoshop and Lightroom. The issues being when you press and hold the space bar to toggle to the hand tool (good for quick zooming in/out and panning around an image once zoomed in), also holding alt/ctrl to toggle between the add and subtract tools for selections, the key(s) do not translate and results in a flicking application window.

I do not see any updates past the issue still existing back in 2021. Anyone have an update or found a workaround?

basillicus

https://community.teamviewer.com/English/discussion/comment/40794#Comment_40794

I had exactly this problem, using Team Viewer on Linux, Kubuntu 20.04. I found my source of the conflict, and a simple workaround to fix it.

In my system I configured it to switch keyboard layouts by pressing the two shifts simultaneously and that conflicts with Team Viewer, generating this problem . I changed it to a key combination that does not involve any of the Ctrl, Shift or Alt keys, and it looks like solves the problem so far.

In KDE environment: System Settings -> Keyboard -> Advanced: Switching to another Layout And change it to anything that does not involve Ctrl, Shift or Alf Keys. I used the (not-any-more) usless key Caps Lock to swithc keybord layouts, and it solved my problem so far.

LordHelmchen

https://community.teamviewer.com/English/discussion/comment/40625#Comment_40625

This problem started when Teamviewer-Linux was transformed from Wine to native. And the problem still persists in 2021. It has been like this on 3 different Linux OSse I have used since (Mint, Xubuntu and now Manjaro with XFCE) It's super annoying, it's "game breaking". Why don't you simply go back to using Wine with Teamviewer again?

CarbonPepper

I've had it with TeamViewer. With recent outages are a factor as well as this and such flakiness in achieving an unattended connection reliably.

Moving to **Third Party Product**. As I have several remote clients now running both teamviewer and **Third Party Product**. When TV fails (very often), **Third Party Product** can still make a connection. So it's not my config.

Edit. Oh look. The competitor's name has been automatically redacted. Well that just about says it all. It's **Third Party Product**

wellington1993

I'm still have that problem at: [Update: 14.0.14470] TeamViewer 14

Thanks.

Shift+Tab doesn't work either in from Ubuntu 18.04 to Win 10. Started looking for an alternative...

mozo

And middle click doesn't work again...

RafaelKa

Following solves this issue https://automatthias.wordpress.com/2008/06/03/ctrl-key-not-working-in-vnc/

dconf write /org/gnome/settings-daemon/peripherals/mouse/locate-pointer false

pavelhoral

I had issues with Shift key getting stuck when connecting from Kubuntu 18.04 to Windows 10. I was using "Both Shift together" as my main shortcut for switching keyboard layouts and when I disabled that, Teamviewer started working. So maybe you want to investigate in that direction.

https://ctrlv.cz/shots/2018/10/15/C4Sj.png

mampe71

I have following problem with teh trafered keys:
If I connect to my main computer from university or work and open from the accessed computer another rdp session to my homeserver - then the AltGr key compinations do not work. On the first hop to the main computer everything works fine. But not on the next hop.

slumbergod

I've completely given up on Teamviewer. I would have rolled back to the previous release which worked but it refuses to connect with anyone using version 13.

So I have gone back to **Third Party Product** and it works fine with no problems. In fact, it also fixes another bug in Teamviewer (the clipboard bug).

I wish everyone luck with Teamviewer but it is unusable and no one really knows how to fix the bug.

pieleric

I've just tried the "summer update" (13.2.13582), and I'm still facing the issue. To be precise, the issue I'm having is only with Shift (not Ctrl or Alt). From the moment that I press Shift, it stays "stuck". The standard keys are still sent normally (example a stays lowercase, and Shift+a is A), but special keys like arrow up/down/left/right, or delete, etc. are interpreted always with shift at the same. Also (and most annoying) is that mouse clicks are also considered with Shift down.

Both the controlled and controlling computers are running Ubuntu 16.04, with the same keyboard mapping (US international + AltGr). This doesn't happen if the controlling computer is on Windows.

When this happen, running xev, and clicking on the window shows this:

ButtonPress event, serial 37, synthetic NO, window 0x5c00001,
root 0x110, subw 0x0, time 1370688504, (49,134), root:(916,999),
state 0x1, button 1, same_screen YES

Note the "state = 0x1". Normally, it should be "state=0x0".

So far, I've found two ways to stop the Shift:

Teamvewier loses and gets back the focus (in the controlling computer). Note: pressing "Alt" or "Win" on Ubuntu causes Teamviewer to lose the focus, as Unity displays a menu.
Stop the Teamviewer connection and restart.

LH_Mouse

The same on Linux Mint 19 MATE. However I managed to find a workaround:

Press the left Alt key.
Press the left Ctrl key.
Release the Alt key.
Press the other combination key e.g. C.
The remote computer responses now as if Ctrl+C was pressed.

Have a nice day.

LH_Mouse.

DanielStm

We've just released our summer update. It contains some improvements for the keyboard handling. Some of you had already tested it and gave mixed feedback. It seems that the behavior is better, but not completely well.
Please leave your feedback on your experience, good or bad.
If you have clues when it happens or how to stop it (e.g. reconnecting), please also share.

Thanks,
Daniel

mwildam

I also tried the current TeamViewer 13 version on Ubuntu 16.04 versus 18.04 in both directions and works in both directions. I am on build 13.1.8286. I am pretty sure that at least with an older build of TeamViewer 13 it did not work on Ubuntu 16.04 either (although it was a different machine and not the one I used right now for testing). I hope all these inputs help nailing the problem. However, for my daily work I am currently migrating to Ubuntu 18.04 so for me the problem seems to be solved for the future.

mwildam

I tried also connecting from the Ubuntu 14.04 (local) to 18.04 (remote, both TeamViewer 13) and then I have the issue, which vice versa I do not have.

This is my locale on the Ubuntu 14.04 and also on the 18.04 - both are the same:

LANG=en_US.UTF-8
LANGUAGE=en_US
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=de_AT.UTF-8
LC_TIME=de_AT.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=de_AT.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=de_AT.UTF-8
LC_NAME=de_AT.UTF-8
LC_ADDRESS=de_AT.UTF-8
LC_TELEPHONE=de_AT.UTF-8
LC_MEASUREMENT=de_AT.UTF-8
LC_IDENTIFICATION=de_AT.UTF-8
LC_ALL=

Keyboard layout are both the same (german).

mwolf

On my Manjaro Rolling and Archlinux the Issue is still here as well.

Waiting for 13.2 on Linux.

mwildam

Sorry for the delay - I was away and under stress - I made further tests (that also required a lot more effort):

Completely new machine, Latest Ubuntu 18.04 and Teamviewer 13 at local and remote: CTRL+C, CTRL+V and other combinations do work now.
Having other machine with older Ubuntu and TeamViewer 13 on both sides does not help - has the issue. Connecting from the new machine to the older (Ubuntu 14.04) with both TeamViewer 13 it works (although I did not expect that). From new machine with Ubuntu 18.04 to remote Windows machine with TeamViewer 13 on both sides works while from the Ubuntu 14.04 to the same remote Windows machine both TeamViewer 13 has the issue.

mozo

Nobody urges you Daniel. The feedback and the lack of information are the missing parts. Thank you for your reply

DanielStm

@kkog, @mozo: Actually we are actively working on this, but I have been reluctant to say it'll be fixed with the next update, as I'm trying to make sure it is actually fixed.
This bug is pretty nasty, as it does not always occur for everybody, so when we thought it's fixed (because it no longer seems to appear), we were not 100% sure.
Also, I did not try to educate anybody, I tried to figure out whether certain usage patterns trigger the bug.

Meanwhile, I sent a test build to affected people to get verification. First replies sound promising, no faulty behavior reported back. So I'm cautiously optimistic it's fixed.

Cheers,
Daniel

mozo

And this solution does not work for me at all

kkog

And stuff is apparently not taking this issue very seriously. They are saying things like release ctrl before pressing keys. What is this? Instead of educating us on how to use the keyboard, solve this stupid problem!

mozo

This is really annoyng bug and it will be great to receive some info about the fixing progress or some feedback from the developer. To remain silent isn't a wise strategy in this case.

kkog

Will you solve this annoying problem or should we find another remote controller???

dretarastra

I revert back to TeamViewer 12 for now,that version is the most recent one that works well for me.

slumbergod

ATTN Devs: any progress identifying the cause yet? Any progress fixing it? Any workarounds?

slumbergod

@daniel if it is possible could you keep us in the loop regarding progress on this bug. One of the things that has really annoyed me with Teamviewer 13 is the way features were rolled out to linux users without being full transparent about the watered-down limitations. It would be a nice change for developers to keep us informed so we feel like progress is being made. This bug is so frustrating for some of us that I am close to abandoning TV13.

mwildam

I have the problem since install of TeamViewer 13 and it never went away.

slumbergod

I'm using a Spanish keyboard and I am connecting to machines with US English keyboards.

This issue with Shift / Control Keys only started happening for me a few weeks ago. Prior to that I cannot recall this problem happening and I would connect with Teamviewer most days. So it could be related to an update. I have no idea when Teamviewer was last updated but I install Ubuntu updates every day or two.

DanielStm

@mwildam wrote:
I am on a german keyboard - could this make a difference?

So am I. :robotwink:
No, no difference, but thanks for the input.

Cheers,
Daniel