Community

It sound reasonable - As far as I remember, the root cause at my system was that the program had not the right permissions to open a window in Wayland - Hence it was not allowed to start the session in a Wayland window. For the time beeing I only run TeamViewer from my workstation - It uses Xorg due to some Nvidia driver compatibility issues... My notebook however, still has the issue, just chose not to use it for TeamViewer... ... View more

Hi All, After fiddling around a while I finally got to the conclusion that TV won't work on Wayland, no matter what others postulates. Both the tar and the rpm installation of 11 and 12 fails connecting to the teamviewerd, fails to get the Xorg auth (according to logs) and ultimately fails working. The second I change to Xorg it works though - Both 11 and 12 versions and both tar and .rpm. I'm at Fedora 25, properly updated and using Wayland. (For easy checking whether you are on Wayland or Xorg do Alt-F2 and try the "r" command - Wayland won't reload as Xorg will). If Teamviewer manages to make it work on Wayland, I'll definetely consider upgrading my 11 to 12, but not before! So far I run all my TV sessions selecting Xorg for that specific session. I want to stick to Wayland for all other purposes as this is the way the development goes. Brgds, Axel Nielsen ... View more

Well, I don't know in this case - But I just had the same problems in version 11. Instead of the quite drastically deletion of every TV file  from the system - I found the reason for my troubles in the /home/user/.config/teamviewer/client.conf The parameter  [strng] FT_Start_Directories = "" was ridicolous long and I simply deleted anything between the " " as many of the directories were not even at my computer. This solved the problem!   The reason I got into thinking this way was the preceeding TV sessions where I browsed a lot around and had many small sessions with the same customer. Maybe TV is not good at cleaning up config files when needed! Brgds, Axel ... View more