[Update] TeamViewer 13 Beta

Update: Final has been released!
See [Update] TeamViewer 13

Dear fellow penguins,

today we are releasing TeamViewer 13 beta. With this release, TeamViewer Host for Linux is upgraded from "preview" to beta. By the end of the beta phase, the Linux Host will be a regular, fully supported TeamViewer client.

TeamViewer (full)
Before I go into details, I need to say that during beta, there is no TeamViewer 13 Linux client that provides outgoing connections. So, when installing the Linux Host beta, please keep in mind that you can (for some weeks) only connect from non-Linux systems. However, with the repository in place, you can of course switch between 13 and 12 as often as you like.

Yes, that's a bummer. I hope I can alleviate the pain a bit and convince you that the wait is worth it:
You may have noticed that during the last months we substantially improved the quality of the Host for Linux, but did not have a lot of updates of the full client.
The reason is, that the native Qt-based, Wine-less TeamViewer Host serves as the foundation of all future development. You read that right: TeamViewer 13 will have no Wine in it.
In vino veritas, but in Qt we trust.

TeamViewer Host
Now, back to this release:
As the Host has become pretty stable and almost feature complete, this release is mostly about polishing. The only thing you will immediately notice is the new look. Therefore I'll tell you about the things you'll probably not notice, just so you can appreciate them.

Some modifications have been made to improve compatibility with Ubuntu 17.10 and some other distros that use gdm as desktop manager.

The control window, which is visible during incoming connections, also has received some attention. It now features the typical handle and can be slid to the edge of the screen. It also now shows a list of the people that are currently connected to this machine. A list? Yes, actually more than one person can be connected at the same time, in case you didn't know.

Another area of work has been the tray icon, status notifier, app notifier or whatever you want to call it. TeamViewer, especially the Host, usually stays in the background and tries to not clutter your taskbar. To still be both visible and accessible, TeamViewer creates an icon in the notification area. In the past, this has been done the ancient X11 way. Of course, this will not be available in a Wayland future. But even today, some distributions no longer offer that, but only support the Freedesktop StatusNotifier.

On the other hand, some distributions do not offer that yet. So with this release, we support both. If it looks nice and shiny, possibly with icons in the menu, then it is the new, DBus-based StatusNotifier, that integrates well with every (supporting) desktop.

Every desktop? Well, almost. Gnome folks have decided that a vanilla Gnome should not support such icons. So, if it is missing on your Gnome desktop, you might want to install the
KStatusNotifierItem/AppIndicator Support plugin.

As always, updates are available via repositories and on our download page.
If you are interested in RedHat and CentOS, please also have a look here.

Enjoy!

All the best,
Daniel

Find more posts tagged with

Accepted answers

DanielStm

How about downloading it right now?
See [Update] TeamViewer 13 for direct download links.
Download page will be updated next week.

All comments

ChristianCay

Hi Chiron,

Thank you for your post.

Unfortunately, TeamViewer Full version 13 is not available.

Our developers are working hard to release a fully native solution.

We hope our Linux users love it.

However while the Full version is released, as a workaround you can do the following.

If you have google chrome installed on your device you may use the TeamViewer 13 Chrome browser extension.

If you don't have Google Chrome it's available for rpm and deb packages.

https://www.google.com/chrome/

Here is the download link for the TeamViewer Chrome browser extension:

https://chrome.google.com/webstore/detail/teamviewer/oooiobdokpcfdlahlmcddobejikcmkfo?hl=en

With this version, you will be able to connect with devices with TeamViewer 13.

This option you don't have to close TeamViewer 13 and start version 12.

Hope this solution works for you.

Best regards,

Christian

DanielStm

How about downloading it right now?
See [Update] TeamViewer 13 for direct download links.
Download page will be updated next week.

DanielStm

We understand that this is an unfortunate situation and there is nothing I'd love to do more than releasing it today. However, we need a bit more time to have something useful. It should be out in about 3 weeks.

This is a one-time event and should not happen again in the future. We just think in the long run everybody will be happier with the native version and the wait is worth it.

In the meantime, you could ask your customers to exit TeamViewer 13 (via tray icon) and have them start a QuickSupport 12.

netniV

I actually think it is crazy to release for one platform and not another. It should have been held back until it was ready on all platforms. This is the equivalent of saying, we have an update of new features for your car but you can only use it on the driveway.

A number of times over the past three weeks this has caught me out when I needed to jump quickly back to one machine, only to remember that I now have no access to that machine as I can't afford to reboot it twice to uninstall TV 13 and put TV 12 back on.

As I don't have access to the source, I also don't understand why such a block is put in place to prevent an older client connecting unless there has been such a major change in the protocol. If that is true, then I revert back to what I said originally, it should have been held until a client was available for all the current platforms.

DanielStm

@skoehler wrote:
I really hope it's coming early next week.

It will.
Let me assure you, we Linux developers are waiting for this release as much as you are.
We have been working towards this for a long time in the background.
It already worked well, but users might not always understand why things are missing or which things are not working.
We wanted to make sure that users are not too disappointed by the lack of initial features.

As there are thousands of downloads every day, it is important that the audience has a way of understanding why there are less features than in TV12, even if they don't look here first. Therefore, as part of the polishing, we added a relase notes link.

Another late addition: unaware users will be informed that incoming remote control is not possible (yet) if they start it on Wayland. (You can do outgoing RC).
It's just a little detail, but it will save thousands of headaches...
(And yes, this also implies that it will start on Wayland, which previous releases didn't.)

Also more little details and under-the-hood improvements.

Thanks for your understanding

tfenster

On the contrary it is absolutely amazing to see teamviewer go into the right direction and having to live with a workaround for 3 weeks (!) is really a very small prize to pay

dagnotland

when can we expect the beta full version for linux? already some of the customers we serve that run the full version have upgraded to the beta and being stuck on 12 is a pita...

I run Arch and prefer not having to deal with Windows any more than I have to.

Chiron

Thank you @ChristianCay! This will work until v13 is released for Linux.

Here is the download link for the TeamViewer Chrome browser extension: -- https://chrome.google.com/webstore/detail/teamviewer/oooiobdokpcfdlahlmcddobejikcmkfo?hl=en

JNA

The remote connection is available and working true, but the chat feature, which is very useful and very used is not present.

It was very buggy in preceding versions (window focus could not be set on the chat window) and I was hoping this would be fixed on this one.

ChristianCay

Dear JNA,

Thank you for your post.

You may use the chat through the management console.

To do so please log in using your TeamViewer account to https://login.teamviewer.com

Hope this works for you.

Best regards,

Christian

JNA

Sorry, I don't understand. We're using Teaviewer for remote control with generated passwords. On the host side, is it possible to open a management console?

Do you plan to integrate the text chat and the file transfer feature in TV13 under Linux?

Best regards,

@ChristianCay wrote:
Dear JNA,
Thank you for your post.
You may use the chat through the management console.
To do so please log in using your TeamViewer account to https://login.teamviewer.com
Hope this works for you.

Best regards,
Christian

bulletxt

Hi,

1: will this native version support Microsoft NTLM Proxy authentication?
2: is it Qt4 or Qt5 ?

Bugul

When will the Linux version for TV13 released?

DanielStm

1: will this native version support Microsoft NTLM Proxy authentication?
2: is it Qt4 or Qt5 ?

It is Qt5.5 (for full TeamViewer), as a dependency not as part of the package.
Qt 5.2 for the Host currently.

NTLM is currently not supported. It seems to be requested rarely, but needs major effort to implement. If we do it, not in the near future. Do you know of Linux applications that support it? Might be interesting which libraries they rely on.

When will the Linux version for TV13 released?

We decided to release it early next week.
It is almost done now. Today is hopefully the last day we change the code, cleaning some rough edges. And some days of testing of course.

bulletxt

On Ubuntu, you can install "cntlm" package. It's a proxy that can connect to NTLM proxy, it has a basic file configuration. One could configure this and then tell teamviewer to connect to this localhost proxy..

The problem is that when NTLM password expires it becomes a mess to tell user to open such file configuration as root, modify password and restart the service..

skoehler

TeamViewer 12 on Linux can't connect to TV 13 on Windows. I am forced to boot a Windows VM to connect to some my friends' machines. Anything (even an alpha/beta) would be useful now. But I can't find a TeamViewer 13 for Linux. I really hope it's coming early next week.

BRalexporto

I'm anxiously awaiting this version. Thanks for the effort to keep Team Viewer compatible for Linux systems.

Karpiu

Is there chance to turn off screen visible on remote desktop under Linux in 13 ?

netniV

Well it did force me to upgrade from 17.04 to 17.10 as I started the install with "dpkg -i" but it failed due to dependancies, so then I ran "apt --fix-broken install" to fix those as it is known to sometimes happen. Once that was done, I had to do several "apt update && apt upgrade -y" runs followed by "apt dist-upgrade" (note that it was already mostly upgrade to 17.10 at this point) and then "apt autoremove". Once I did all that, then got connected and it seems stable ... which then led me to my questions....

How do we switch screens on multiple monitors? There seems to be no obvious toolbar at the moment.

Why does the APT sources list have the wrong info?

W: Conflicting distribution: https://downloads.plex.tv/repo/deb public InRelease (expected public but got )
W: Skipping acquire of configured file 'tv13/binary-amd64/Packages' as repository 'http://linux.teamviewer.com/deb stable InRelease' doesn't have the component 'tv13' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'tv13/binary-i386/Packages' as repository 'http://linux.teamviewer.com/deb stable InRelease' doesn't have the component 'tv13' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'tv13/i18n/Translation-en' as repository 'http://linux.teamviewer.com/deb stable InRelease' doesn't have the component 'tv13' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'tv13/i18n/Translation-en_GB' as repository 'http://linux.teamviewer.com/deb stable InRelease' doesn't have the component 'tv13' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'tv13/dep11/Components-amd64.yml' as repository 'http://linux.teamviewer.com/deb stable InRelease' doesn't have the component 'tv13' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'tv13/dep11/icons-64x64.tar' as repository 'http://linux.teamviewer.com/deb stable InRelease' doesn't have the component 'tv13' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'tv13/binary-amd64/Packages' as repository 'http://linux.teamviewer.com/deb preview InRelease' doesn't have the component 'tv13' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'tv13/binary-i386/Packages' as repository 'http://linux.teamviewer.com/deb preview InRelease' doesn't have the component 'tv13' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'tv13/i18n/Translation-en' as repository 'http://linux.teamviewer.com/deb preview InRelease' doesn't have the component 'tv13' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'tv13/i18n/Translation-en_GB' as repository 'http://linux.teamviewer.com/deb preview InRelease' doesn't have the component 'tv13' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'tv13/dep11/Components-amd64.yml' as repository 'http://linux.teamviewer.com/deb preview InRelease' doesn't have the component 'tv13' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'tv13/dep11/icons-64x64.tar' as repository 'http://linux.teamviewer.com/deb preview InRelease' doesn't have the component 'tv13' (component misspelt in sources.list?)

Should the teamviewer.list just be removed?

tfenster

Any chance for a armhf / raspberry version of the client?

DanielStm

@tfenster wrote:
Any chance for a armhf / raspberry version of the client?

Let me help you here: Ask the same question in the [Update] TeamViewer 13 thread, maybe with Raspberry as subject line, Raspberry in bold, and add the a line "Give thumbs up if you want that, too".

Starting next week, that other thread will be viewed by thousands. This is your chance :smileywink:
I will take the result to management.

scasagrande

How about the file transfer feature? (Using Linux to connect to a Windows PC in this case.)

DanielStm

@netniV: TeamViewer will surely install fine on 17.04, even on 16.04 and before.
Use apt install /path/to/file (it must have a slash, so apt knows it's a file...) or a graphical installer, it is much cleaner than using --fix-broken.
On the repository: Yes, the warnings are annoying. Will be fixed as time permits.

@JNA, @scasagrande Chat is on the high-prio list, as well as file transfer.
Setting the focus properly is one thing that is harder than you ever think it could be with Wine, but should be a problem of the past with the new Qt based UI.

Please have a look at [Update: 13.0.6634] Christmas Update

All the best,
Daniel

JedenTag

@tfenster wrote:
... having to live with a workaround for 3 weeks (!) is really a very small prize to pay.

I already paid full price. For a full solution.

Chiron

In the meantime, you could ask your customers to exit TeamViewer 13 (via tray icon) and have them start a QuickSupport 12.

This is incredibly frustrating.