Community

Nielsen_Knowhow · ‎03 Nov 2017,

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...

Nielsen_Knowhow · ‎15 May 2017,

Well, when Fedora/RH suggests Wayland is the way to go and TV can't run under Wayland due to somewhat higher security/separation in Wayland vs Xorg, I think you need to reconsider your point of view. Wayland is the problem but not the cause - TV needs to deal with a world in change as everybody has - Even Microsoft - Don't think they ever imagined they had to reactivate security updates on their deprecated systems, but guess what - They just had! I won't change my OS, but I might change TV to some other alternative if they keep on not solving the Wayland issue. Brgds, Axel

Nielsen_Knowhow · ‎20 Mar 2017,

Hi, Checked out the Wine versions - I'm still having only one issue - The Wayland. With Wayland, no TV - With Xorg, TV works.

Nielsen_Knowhow · ‎18 Mar 2017,

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

Nielsen_Knowhow · ‎18 Mar 2017,

It's definetely the Wayland/Xorg problem you are facing. I'm on TV v11 and upgraded 3 days ago to Fedora 25 (Wayland by default) - And as the daemon ran nicely after upgrading, I didn't discover the problems until 20 mins before I had an online appointment with a customer. Luckily I still have a workstation running Fedora 24 and I could fallback on that. The problem descriptions/errors are the same in TV11 and TV12 - So TV better get working to make the 12 work with Wayland if the want me so badly to buy the TV upgrade :-) Wayland has come to stay - It solves numerous security issues with Xorg. Brgds, Axel

Nielsen_Knowhow · ‎20 Dec 2016,

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

Community

Badges

Re: No connection to TeamViewer server

Re: TeamViewer 12 not connect in Fedora 25

Re: TeamViewer 12 not connect in Fedora 25

Re: No connection to TeamViewer server

Re: TeamViewer 12 not connect in Fedora 25

Re: Won't open after update to 12 on CentOS 7