Author Topic: Teamviewer 12 on Fedora 25, control but no screen updates  (Read 4129 times)


  • Newbie
  • *
  • Posts: 2
Teamviewer 12 on Fedora 25, control but no screen updates
« on: December 29, 2016, 09:53:42 AM »
So I've just done a clean install of Fedora 25 on a Thinkpad T410, and have installed Teamviewer and little else. Of course out of the box this doesn't work since Fedora 25 uses Wayland by default. For some reason this manifests in the incorrect error message about not being able to connect, which isn't actually the problem at all. I've worked around this problem by switching to using Xorg instead of Wayland in /etc/gdm/custom.conf.

So, I tried connecting to this computer from a Windows computer, and from an Android client, and both show the same behavior:

  • The Teamviewer client ("Alice") connects to the instance running on Fedora ("Bob") successfully.
  • I can control the mouse and keyboard on Bob from Alice.
  • Alice never receives screen updates from Bob.
  • I can open applications on Bob, and they don't appear on Alice
  • I can disconnect from Bob, then reconnect, and I still see the same empty screen on Alice as I saw when I first connected.

The only difference between Android and Windows clients is that the Windows client will flicker the little Teamviewer session window, as it can't decide whether it should be visible or not, though it's been put away on Bob and so shouldn't be visible.

Clearly, Alice is just inventing its own version of what Bob should look like based on how it was first visible at the first connection attempt, but gets no further information about what Bob is actually doing.

I'd appreciate an assist, maybe some things to try...?

For what it's worth, the Thinkpad is running Intel graphics on a Core I5 M520 CPU. The Fedora 25 installation is essentially out-of-the-box, except for the switch to Xorg.



  • Newbie
  • *
  • Posts: 1
Re: Teamviewer 12 on Fedora 25, control but no screen updates
« Reply #1 on: March 12, 2017, 08:31:40 AM »
I have exacly the same here ( win10 to FC25 after removing Wyland )  But intrusting is that exactly the same phenomenon appears when I use the NoMachine software in place of Teamviewer, so the bugs are localized in FC25 and NOT on TV.
I also tried VNC ( tiger ) but its really a pain in the ass to let it work ) so I gave up with VNC.