[Update: 13.1.3026] Spring Update
Dear Linux community,
last week we have released the spring update for TeamViewer Host (13.1.1548), leveraging under-the-hood improvements of the TeamViewer 13.1 code base. In addition, the Host now notifies the user about Wayland limitations in the same way as the full version. It also informs the user when started to run in the background and no tray icon is available. Separate SUSE packages are available, too.
Benefiting from the same code base improvements, today we are releasing the full TeamViewer 13.1 client for Linux.
As indicated in the previous announcement, this release is mostly about stabilizing. But still, a bunch of useful additions snuck in.
Computers & Contacts
The C&C window is now restored at its previous position. Groups can now be collapsed. And, most notably, service cases in the service queue now show up in the list.
Remote Control
The toolbar has a new look and learned to start a file transfer within a running remote control session. You can now also change the resolution of the remote screen. We expect to have most of the missing items ready for the next release.
TAR and SUSE Packages
The TAR package learned to check for QtQuickControls when running tv-setup checklibs. This should resolve the confusing situation that checklibs did not find missing (shared library) dependencies but TeamViewer still did not start.
Much to our dismay, it is not possible to express RPM dependencies in a way that can be satisfied on both, RedHat and SUSE based distros. Again, QtQuickControls.
Therefore, SUSE packages are now available as a separate download which also makes the repository work.
SUSE package migration |
Note: If you have previously tinkered your way to make the RPM package or repository work on SUSE, we strongly recommend to remove it and replace it with the new SUSE package. While the binaries are completely identical, the dedicated package should enable smooth updates in the future. Note: Removing the package also removes an existing account assignment. Therefore, after installing the new package, you might want to assign in again. |
What's more
As some desktop environments do not support status notification icons (a.k.a. tray icons), we added a notification to let the user know that TeamViewer runs in the background (if the start-with-system option is enabled) and no icon could be created. If you start TeamViewer manually, it should always become visible.
On DEB systems, the teamviewer repo list command now lists available packages.
Linux specific documentation has been greatly revised, reworked and extended. Please have a look:
Linux Knowledge Base
- How to install TeamViewer on Linux
- How to install TeamViewer on Ubuntu
- How to install TeamViewer on RedHat and CentOS
- How to install TeamViewer on other Linux distributions
- How to install TeamViewer on Linux without graphical user interface
- How to use the TAR package for Linux
- How to update TeamViewer on Linux via repository
- System Tray, StatusNotifier and TeamViewer for Linux
Further Reading
- State of Wayland & TeamViewer
- Previous announcements: Beta, Final, Christmas, Valentine
As always, packages are available via repositories and on the TeamViewer Linux download page.
All the best,
Daniel
Comments
@malmax66 wrote:
@rosch wrote:Can you at least update the download to include the "Full Screen"?
The current version is hurting my eyes..
Hi,
my version has the possibility to run in a maximized window. I don't know, if there is also the choice to run it in a "Full Screen Mode" without the window-frames. But when I use maximized it has an acceptable quality :smileywink:
Yes I'm talking about the real full screen, without any Linux window frames.
@rosch wrote:Can you at least update the download to include the "Full Screen"?
The current version is hurting my eyes..
Hi,
my version has the possibility to run in a maximized window. I don't know, if there is also the choice to run it in a "Full Screen Mode" without the window-frames. But when I use maximized it has an acceptable quality :smileywink:
I am still experiencing problems with Linux Host. When I connect to a Linux machine with extended display (two monitors) from a Windows or other Linux machine, the two displays are augmented together as one single display. I do not have the option of focusing on one screen or switching between the screens.
Thanks Daniel for picking up on this!
@DanielStm wrote:But the cost of achieving and maintaining that was... high.
Okay I see now what's going on. I did not realize the TW12 was based on Wine. Now it makes sense. I thought the defeaturing was just some mindless design decition by some desk hero. Sorry about that.
@DanielStm wrote:Multimonitor support
You could do this: Switch to TV13, and use two parallel connections (one per screen). Wait until the repository offers you an update (few more weeks). It'll be in there. :robothappy:
That's a good solution to my problem for the time being, thanks!
@DanielStm wrote:
Full screen
I can't promise that for the next update, but it's on the list.
Workaround: Personally I'm a KDE Plasma lover. One of the reasons is that you can do fancy thing to any window, including fullscreening the TeamViewer remote window. (Alt+F3, more actions, full screen) :robothappy:
Thats a very handy feature of KDE Plasma! Unfortunately I am using cinnamon and it does not offer anything similar. Switching the desktop environment for that however is not feasible for me. I will just have to wait. But I am glad to hear it's on the list!
I mostly just want the core functionality that USED to exist in 12, working in 13.
I was forced to upgrade my licenses to 13 because a single customer upgraded their hosts. 13 is missing a ton of very basic functionality though. Can't even rename machines in your computers/contacts list.
I've asked TV for 2 months about some of this basic stuff, and haven't got a response yet. On the hunt for a new application at this point, which **bleep** because they've got me vendor locked pretty good and it'll be a massive job to get all of my clients moved over (around 800 workstations and 200+ servers, and half the workstations on mobile and never come into any of my offices).
@DanielStmthanks for the update and - as many have also said - for the Linux focus. It may be a small-ish portion of your user population but it's an important one IMHO, ie: tech-savvy people who are well positioned to recommend TeamViewer further.
There are a number of users (myself included) who really miss the meeting feature but this isn't addressed in your update beyond an ominous "... when we shift our development focus to meeting", which suggests it isn't even on your radar?
There are a gazillion apps to do stuff like chatting but TeamViewer is was one of the few that supported screen sharing on Linux...
Hey guys, time for another round of Q&A :robothappy:
In-session chat: @duki92, @ndit, @JNA, thanks for your valuable feedback. We have put it high in the priority list.
@QPG you are, I assume, the only person who ever found out this actually worked with the old Linux version :robotwink: (It works because the wrapper forwards unknown params to the Wine binary)
I think it will come back at some point, shouldn't be complicated. Just can't promise a date.
@vkovalchuk: connecting to mobile devices is, unfortunately, not yet implemented. Coming soon™.
@EpsilonAlpha: Sound support has two parts: Forwarding computer sounds and VoiP. The former was never before implemented for Linux I think, as it is mostly a gimmick. VoiP will come back when we shift our development focus to meeting.
@yolor: I can confirm that. However, it's not actually detecting Wayland... Rather, on the affected 32-bit systems, the UI is just completely broken and showing random things. Possibly a bug in the 32-bit Qt libs. We'll investigate.
@cranesmart: Our UI still uses the "classic" layout, which may change eventually. Yes, things are still missing as we've been starting over. We're working on it. See the previous announcements linked in the article to appreciate the progress during the last months.
@sglatz: As your most pressing question seems to be why on earth those features are currently not there, I'd like to point you to the previous announcements (linked above) explaining the advantages of starting over with a native client instead of pushing the Wine-based client further beyond the limits it imposed on development. It is nice to hear that some people actually think that the old client "worked well", as we tried hard.
But the cost of achieving and maintaining that was... high.
Multimonitor support
You could do this: Switch to TV13, and use two parallel connections (one per screen). Wait until the repository offers you an update (few more weeks). It'll be in there. :robothappy:
Full screen
I can't promise that for the next update, but it's on the list.
Workaround: Personally I'm a KDE Plasma lover. One of the reasons is that you can do fancy things to any window, including fullscreening the TeamViewer remote window. (Alt+F3, more actions, full screen) :robothappy:
Cheers,
Daniel
Hi, I've got 2 feature request - It might not be Linux specific but since I am using the Linux Client ( mostly to connect to Windows Machines when doing homeoffice ) I thought I would just post it here and hope it will reach the right people somehow.
So here goes
1. Multimonitor Support
At my company many people use multiple monitors and I am one of them. When doing homeoffice I need the ability to open each of these Monitors in a separate window so that I can see what I am doing at a glance.
In TV13 it seems I can only switch between Monitors but that's just not efficient. People with multiple monitors usually have them for a reason: because they need several windows open >at the same time<. Showing only one at a time completely defies the purpose of having multiple monitors in the first place.
I can imagine that it is a rare setup and not many people are affected by it but It was perfectly integrated in TV12, why throw it away? Is there any chance it will come back? I am stuck on TV12 because of this (jeopardizing my companies Software infrastructure while I am at it because everyone else is using TV13 and those two dont play nice with each other, so I am pretty alone on my island... )
2. Fullscreen Mode
In TV12 there was a fullscreen mode which actually filled the whole screen. It worked like a charm. With same resolution monitor locally and remotely it was just like you actually sat over there.
Now the best that we got is the maximize window button which is not the same. It's ugly! First of all there is this rescaling going which offends my eyes and then a major portion of the screen is cluttered with the window frame and my local taskbars which I do not need because I am working remotely.
Now, I feel this feature is not too exotic. Sure It might not be critical for short remote control session but for longer sessions having your local taskbar and the window frame constantly in your face is really annoying.
Again: It was perfect in TV12, why throw it away? Any chance it will ever be coming back?
Best regards,
Stefan
I can only second @duki92 and @ndit request. For us, the in-session chat is the blocking feature that prevents switching to TV13 for now. No sound is needed as our support sessions often take place in very noisy environments and with people not fluent in english.
Basically, in our remote support sessions, we use in-session chat every time, and sometimes file transfer.
When chat capability was announced, that was relief (the chat feature is already a bit clunky in TV12, because the chat window can't get the focus), just to discover that it is in fact instant messaging. So please, please, please, push this feature closer to the top of the requested features.
1. It says wayland session is detected even on X11 session, not a big deal though.
2. On 32 bit system i can't connect and i can't see some symbols and menu, on 64 bit everything works. (example in a screenshot). I've tried different themes, launched under new user, nothing is working out. However 13.0.9865 version works on 32 bit system.
@apesofhoveThanks for your reply, I never got any indicator that tells me that it would be a "commercial only" Function. It's simply nowhere visible inside the Software anymore, the whole settings Tab is gone for Audio-Settings.
Neither is it listend unter the Features of a Commerical License:
https://www.teamviewer.com/de/pricing/
I would even consider the "Business" License when it's sure that it's a commercial only-Function! But i don't buy the License blindly just that a Support Member (which you can just approach with a license) tells me that this doesn't work.
So can a Teamviewer-Staff Member please confirm this?
@ThePooNSwitching to a different OS is no Option for me, not even in a VM.
First of all is most of the Software i use Linux specific
Secondary are there a couple of good Reasons why i gone away from Windows
I can't believe why no one of the Staff can tell me when the Audio Support will come back :smileysad:
Looks like doesn't work.
I have installed TV QuickSupport 13.1.8752QS on Android 4.1.1 tablet -- and then TeamViewer (teamviewer_13.1.3026_amd64.deb) on Ubuntu 16.04 LTS (had to install libqt5x11extras5 and qtdeclarative5-controls-plugin as a prerequisite). Started QS, got ID. Started TV, entered Partner ID, tried to connect. A dialog "Allow Remote Control?" appears on tablet, I confirm. On Ubuntu the button reverts to "CONNECT", no windows open etc. **bleep**?
I tried with UDF switched off, no difference.
The ability to collapse the menus in the computers & contacts is a serious usability improvement. I'm not confident enough to upgrade my endpoints to TeamViewer13 host yet in case I need to revert to TV12, but I have manged to keep TeamViewer 13 installed on the Linux workstation that I make all of my connections from.
One item that hasn't come up in the community is the inability to call this version of TeamViewer with "teamviewer --control %f" while passing it a .tvc file. This has broken integration with Solarwinds MSP RMM. Will this capability be returning at some point?
Yeah, in-session chat. Let me explain my situation as I don't really know a lot about these things:
I work as an online teacher. When there are issues, connectivity or any other kind, they connect to my computer to test my connection, check platform related stuff and so on. Once they get connected, I need to inform them of issues I have so they can help me. I guess I can do that only via in-session chat or audio communication.
I have no use of computers'n'contacts chat (since different it person connects each time) and to be honest, I didn't even know it existed until it was announced in previous update and I thought it was about in session chat, hah.
I guess audio commmunication may be a bit easier for me, but it doesn't really matter, I would be happy with any of these 2.
Thank you for your support.
@MalteGerth: okay, fair point. (I think it's only if it's a non-installed TeamViewer). As said, it's scheduled to be fixed.
@cowst: As far as I can tell, the license activated on your account is TV11, which likely is the issue. If you need help to activate a newer license, please contact support.
@mozo: On the Ctrl+C issue, please join this thread: ctrl key not working.
@duki92, @ndit: So both of you want the in-session chat rather than the Computers'n'Contacts Chat? That's good to know. So far, I didn't think it to be as important as the other one.
Great update Daniel, this version will be 100% usable for me as it looks by the features. Just did my first "quicksupport session" with a costumer. Working great.
I know there is many missing features and possible improvements still, some of the very important for some. But for me, the important stuff is now covered. I won't have to rely on my windows VM for teamviewer daily anymore, but maybe still on some occations.
Good work, keep it up.
For me personally, chat and meeting would be the next wanted features.
Thank you for your commitment.
However, I rely on communication with the person on the other part of remote connection. Either audio or simple chat, however as this isn't possible due to current limitations. I was hoping it will come soon, but... Due to it being neccessary for my work, I'm forced to use Windows, which is driving me you know where.
Looking forward to incorporating at least chat in a remote connection.
Duplicate, see message here:
native TV13: Praises, Challenges, Problems, Wishes