Yep, it's a Wayland issue. My expectation is Teamviewer could work as a client (see someone else's screen) using XWayland pretty easily, but there's probably substantially more work getting it to work as a server/host (to share my screen with someone else). Since there aren't separate client server programs, I think we just have to fallback to XOrg for now.
... View more
I'm using Fedora Linux, and successfully installed teamviewer_11.0.67687.i686.rpm. But I'm getting a dialog "No connection to TeamViewer server. Please check your internet connection. Most likely you use a proxy server and you have to enter the proper information in the options dialog." $ sudo systemctl status teamviewerd.service [sudo] password for chris: ● teamviewerd.service - TeamViewer remote control daemon Loaded: loaded (/etc/systemd/system/teamviewerd.service; enabled; vendor preset: disabled) Active: active (running) since Sat 2016-11-12 13:08:18 PST; 18min ago Main PID: 4751 (teamviewerd) Tasks: 14 (limit: 4915) CGroup: /system.slice/teamviewerd.service └─4751 /opt/teamviewer/tv_bin/teamviewerd -d Nov 12 13:08:18 f25h.localdomain systemd: Starting TeamViewer remote control daemon... Nov 12 13:08:18 f25h.localdomain systemd: teamviewerd.service: PID file /var/run/teamviewerd.pid not readable (yet?) after start: No such Nov 12 13:08:18 f25h.localdomain systemd: Started TeamViewer remote control daemon. I've also stopped firewalld just to test if it's the firewall. And there are no SELinux AVC messages. So I can't figure out why it can't connect to TeamViewer servers. On a Mac, on this same wireless network, I don't have this problem.
... View more