Teamwiever mouse and keyboard not working in Zorin OS 17.2

General Help
1

Hello Everybody,

I noticed that once I upgraded from Zorin 16.x to 17.2 now my Teamviewer (installed via Zorin SW Manager back in Zorin 16.x version) does not allow my mouse nor keyboard to interact with a GUI of a PC I am connected to (machine with Zorin OS) - whereas in 16.4 this was not a problem.

Now, after connecting, user at the other end has to allow my connection (I get it, this is because of security), but even if they do, I cannot move the mouse or interact in any way with their screen, keyboard included (this was not a problem back in Zorin 16.x).

I checked the settings, there doesnĀ“t seem to be anything set in a wrong way.
I am connecting from Windows 10 Pro 64 bit -> Zorin, if it is of any relevance.

Does anybody know what should I do to enable interaction with the connected screen (i.e so my input via keyboard + mouse will be registered/reacted to)?

2

Haven't used teamviewer so much in the recent times, but did it upgrade versions while you went through the upgrade? It may also now have an option you have to enabled where you "allow remote connections to control the screen via mouse/keyboard" or something to that effect. I've run into it a couple times here and there, but it's been so long since I've dealt with teamviewer that I'm not sure what settings that has to choose from anymore.

1 Like
3

I will try to have a look for option like that.
I use the newest version and I assume the flatpak versions are also the newest ones.

4

I think this may be an issue due to Wayland, which is the new default window display manager starting in Zorin OS 17. Wayland is notorious for it being restrictive when sharing window access across programs, and remote sharing is one of the most iconic examples where it lacks the most.

You can quickly test this by switching to Xorg, instead. Logout of your account and use the wheel icon at the lower right corner, where you will have an option for "Zorin Desktop on Xorg", and try again.

5

ThatĀ“s what I thought as well, that Wayland is doing something wrong, but we found the culprit - it was easier than I thought:

When I try to connect to remote PC, there is a display, which I cannot see, where it asks user, whether he will allow me to connect to their desktop.

There are 2 different buttons:

  • Allow remote connection
  • Allow remote interaction

Guess which one he was pressing all the time before? :wink:
Only remote interaction allows you to interact, the other one works like a spectator mode.

@applecheeks37 - so the default settings were all correct :slight_smile:

3 Likes
6

That's really interesting, I don't use Teamviewer myself so I didn't know about the prompted options... I'll bookmark this answer as I suspect will come in handy in the future. Thanks for sharing!

1 Like
7

Glad that an easy solution was found :slight_smile:

8

The problem you found is not limited to any software or OS. When I was working, Head IT guy came to look at an issue on manager's PC. He quickly diagnosed the issue being PICNIC. Problem In Chair Not In Computer!

9

I donĀ“t blame him though - the person in question is my dad :slight_smile:

And although he is skilled with movie editing SW, the inner workings of OS eludes him, so sometimes I ask questions in this forum also in his stead.

We use teamviewer, if thereĀ“s some technical trouble and it is easier to have a look remotely than to explain.

2 Likes
10

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.