State of Wayland & TeamViewer
Sign In with Xorg instead of WaylandTL;DR:
On Wayland, currently only outgoing remote control is supported. If you need incoming remote control, you have to sign in with classic Xorg.
[Edit]
You can also disable Wayland for gdm, as bl4ckOut pointed out in the first comment. However, note that this only allows you to connect to the login screen. When logging in, make sure to use Xorg, as shown on the right.
Background
Some people assume that TeamViewer should just workβ’ on Wayland, as Qt does all the work. That is partially true. The UI does not care about being started on Xorg or Wayland. But TeamViewer is deeply integrated with the system. It needs to know what kind of session it deals with, so it can handle incoming connections properly, especially if you connect to the login screen and then start a new user session. Therefore, TeamViewer knows Xorg sessions and frambuffer terminal sessions (you can connect to these). TeamViewer 13 now also knows Wayland sessions. That was the easy part.
From a developer perspective, we would be more than happy to leave the archaic X11 technology stack behind and jump on the new and shiny Wayland train. However, that is not as simple as it may seem. By design, Wayland does not provide an interface to do remote control (screen capturing, mouse and keyboard emulation). This is to keep the Wayland core lean. The idea is that the compositor provides these interfaces, which could mean that TeamViewer would have to implement different interfaces for every desktop environment we want to support. This is unfortunate, but it's even more unsatisfying that these interfaces are not available yet. The closest to having something useful is Gnome, so it is likely that it will be the first desktop where we can support Wayland.
Summary
Yes, we want full Wayland support, just as much as you, and we will work on it. Just know that it's a bit more complicated than 'just make it happen', as it is for most of the other features.
All the best,
Daniel
Find more posts tagged with
Hello Daniel,
as much as I appreciate the efforts the teamviewer team takes to build a native linux client, to me as a professional linux user (yes, also on the desktop!) the decision to only publish the native client, for me is a constant nuissance (and even more). As I am using presentation mode on a daily basis, am stuck with the last installer, delivering TV13 WIN, wrapped with wine.(works perfectly, btw!)
I do not use the native client because it lacks a major feature, so I will not be of any help when testing it, unfortunately. But in my daily work life I have to annoy my communication partners constantly to download old quickjoin of quicksupport versions, even if they have recent teamviewer installed, to collaborate with my colleagues. Of I am running TV on a WIn Terminalserver, which can be a pain.
Is there solution in sight, either getting a recent version based on wine (will be greatfull to request it via support), or even better, a Linux native client sporting the ole' presentation mode?
Thank you and best wishes
Stefan
I don't think so! At least not now.
Does anyone else have the same problem with wayland. I can't log in to my account and am unable to connect to any machine. I use my phone to test as I know that this works on a windows machine at least.
I'm on 20.04 but on 19.10 the same problem occured
EDIT: Okay it seems to be a problem with phone connections. It works with a Windows server. Logging in also works after reinstalling so that's good.
Hi linuxlore,
I have a similar problem on Fedora 33 Workstation - empty Recent Connections and the GUI becomes unclickable after a few clicks - which is going on for a month or two (earlier it was fine).
I would usually just logout and enter the X.org session, work with Teamviewer, and after finishing, relogin into the normal Wayland session. After playing around, I discovered that restarting the teamviewerd daemon after logging in makes the GUI behave normally again - although it still segfaults after closing the connection.
We have recieved an email from TeamViewer telling us that the price of our licence will be increased by 4,4% and for argument, they have made a newer versions that takes MacOs, Android and Windows... Ok we can undrestand this augmentation if Linux was included on these newer versions... Is it legal that they force us to pay extra for no real service ?
Regards,
I think it is safe to say that there has been progress - unfortunately backwards. It doesn't work for outgoing connections on Wayland now it seems. I have just tried Wayland on my Ubuntu 20.04 install and although it starts and warns me that it won't work for inbound connections (which I don't actually need as I am just supporting family which is out), the list of Computers and Contacts is missing (just an empty Recent Connections header) and the Chat is not clickable at all (not that I actually use that, I'm generally on the phone or there is nobody at the other end at all). Thankfully I have other options I can move to.
Isn't it possible to use a DBUS API ([removed per Community Guidelines]) for this? It seems that it's implemented by different desktop environments already.
[Third party product]
Funny thing (not) is, the removed links were not in violation of the forum guidelines, because they were a link to API descriptions (and not a third-party product) that TeamViewer would need to use to implement remoting.
@DanielStm explicitly wrote the following: "By design, Wayland does not provide an interface to do remote control" and "TeamViewer would have to implement different interfaces for every desktop environment", but this isn't correct any more. The DBUS API link is standardized and already implemented by different desktop environments. They "just" have to use it, but instead the link is removed with the hint: "Third party product" ...
This is frustrating and disappointing.
Good morning, I would like to know if there is a date for the launch of teamviewer running on wayland completely, since it is the future of linux and teamviewer is lagging behind other tools that already offer it. In my case, I am waiting for it to be released to make a purchase of the license. while I continue with the competition
Hi @Hrakason,
so far it's only available in the preview version, which - unfortunately - is only supported on Debian based systems in general.
As soon as the public release 15.29 will finally be available (please be patient for some more days), you can also test the Wayland support on Fedora.
If you are using a Debian based version, the easiest way to update to the preview is as follows:
sudo teamviewer repo preview sudo apt update sudo apt upgrade
Best,
Kerstin
Can someone provide a correct repo address for RPM preview or development version of Teamviewer.
I can't find it anywhere, I tried to filled it myself but no luck so far.
On my PoP Os - DEB version - I can go into Extras - Option and pick a version I want - or I can change it in sources.list.d.
But I want to test it on Fedora - no luck there.
Thanks!
I'm glad to see that I'm not the only one visiting this post in 2022! I understand that it takes time to implement complex features such as this, so it would be greatly appreciated if someone could give a status update on the state of Wayland support for Linux - whether or not it's being actively developed still and maybe even a soft timeline of what to expect (i.e. later this year / next year / never / etc.)
Thank you π
Hello dear Community friends,
I have quite some news for you...
We started working on supporting Wayland! π
Please find more information in our Blogpost here:
I hope you will be able to try it out.
We would appreciate any feedback! π
All the best,
/JeanK
Community Manager
The problem is Wayland isn't even close to being feature-compatible, yet it gets shoved out as a replacement, and any complaint that it is missing something gets a hostile response of "well, no one uses taht anyway". Really??? So if *I'M* asking for some function to be in place, something that existed in X11, that means the Wayland-fanboys imply that *I'M* nobody.
SystemD merely tries to do tto much. It's trying to be the entire OS in itself, rather than a minimal, specific-purpose service to load other services. And in shoehorning itself into every corner of your system, it breaks cross-platform support (when projects like GTK or Gnome build in SystemD dependencies, it means those become BROKEN everyplace else). It's doing TOO much, too many things it shouldn't be touching. It's the difference between "do one thing and do it well" vs "jack of all trades, master of NONE".