[Update: 14.1.3399] TeamViewer 14

2

Comments

  • Moogwi
    Moogwi Posts: 2

    uname -a
    Linux PC-AL 4.9.0-5-686-pae #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) i686 GNU/Linux

    TV crash with this message (seg fault):

    2018/12/04 17:03:46.587 1042 **Please do not post TeamViewer IDs** S Activating Router carrier
    2018/12/04 17:03:46.587 1042 **Please do not post TeamViewer IDs** S CProcessCommandHandlerMasterConnect[3]::CreateMasterConnect(): master1.teamviewer.com:443, Connection 3, proxy=''
    2018/12/04 17:03:47.344 1042 **Please do not post TeamViewer IDs** S CTcpProcessConnector::HandleRead(): Socket gracefully closed (PID=1314)
    2018/12/04 17:03:47.344 1042 **Please do not post TeamViewer IDs** S CTcpProcessConnector::CloseConnection(): PID=1314
    2018/12/04 17:03:47.344 1042 **Please do not post TeamViewer IDs** S InterProcessNetwork::ProcessDisconnected(): ConnectionClosed session=**Please do not post TeamViewer IDs** ptype=2
    2018/12/04 17:03:47.344 1042 **Please do not post TeamViewer IDs** S ProcessControlBase[2]::ProcessDisconnected: Process pid 1314 in session **Please do not post TeamViewer IDs** disconnected
    2018/12/04 17:03:47.344 1042 **Please do not post TeamViewer IDs** S NetworkControlLinux::ShouldDelayOffline: Start delay update online state
    2018/12/04 17:03:47.344 1042 **Please do not post TeamViewer IDs** S NetworkControl::UpdateOnlineState alwaysOnline=1 delayOffline=1 otherProcess=0 restart=0
    2018/12/04 17:03:48.889 1042 **Please do not post TeamViewer IDs** S CProcessCommandHandlerMasterConnect[3]::HandleMasterConnect(): Sending MasterCommand client=TV&connectionmode=1&f=RequestRoute2&homeserver=&ic=**Please do not post TeamViewer IDs**&id=**Please do not post TeamViewer IDs**&id1=**Please do not post TeamViewer IDs**&id2=**Please do not post TeamViewer IDs**&licensedremoteaccesstypes=0&mid=lc218b78290d047b386c1250089b5dc06:30b5c200cb20:b7839149ab39488ebb6e6371f4f394fa&midv=1&v=14.0.14470
    2018/12/04 17:03:48.988 1042 **Please do not post TeamViewer IDs** S CProcessCommandHandlerMasterConnect[3]::ReceivedMasterResponse(): Received MasterCommand CONNECT@188.172.245.136_0_128000_**Please do not post TeamViewer IDs**_**Please do not post TeamViewer IDs**_32504__1_0_16778176_128000_16778176:128000;**Please do not post TeamViewer IDs**:1280000;4:640000_**Please do not post TeamViewer IDs**_**Please do not post TeamViewer IDs**_FR-MRS-ANX-R005.teamviewer.com_eQBwZWCBGNdjjAE=_eQBwZWCBGNdjjAE=
    2018/12/04 17:03:48.988 1042 **Please do not post TeamViewer IDs** S! TcpCarrierBase[3]::SendCompleteQueue(): No Connections, Type_Tcp, Dir_Outgoing, Ending 0, SendQueue 1, CurrentSendQueue 0, SendCache 0
    2018/12/04 17:03:48.988 1042 **Please do not post TeamViewer IDs** S Activating Router carrier
    2018/12/04 17:03:48.988 1042 **Please do not post TeamViewer IDs** S CommandHandlerRouting[4]::CreateActiveSession(): outgoing session to **Please do not post TeamViewer IDs** via FR-MRS-ANX-R005.teamviewer.com, protocol Port443
    2018/12/04 17:03:48.988 1042 **Please do not post TeamViewer IDs** S Carrier[3]::EndCarrierInternal(): ClientID: 0 SupportsEndSession: 0, SupportsCCmd2: 0, SessionType_MasterConnect, SendQueue: 0 (4 Bytes), CurrentSendQueue: 0 (0 Bytes), SendCache: 0 (0 Bytes)
    2018/12/04 17:03:50.891 1042 **Please do not post TeamViewer IDs** S ProcessControlBase[2]: Process 1314 in session **Please do not post TeamViewer IDs** has terminated
    2018/12/04 17:03:50.891 1042 **Please do not post TeamViewer IDs** S SysSessionInfoManager: updating session information for session **Please do not post TeamViewer IDs** from GUI
    2018/12/04 17:03:50.891 1042 **Please do not post TeamViewer IDs** S SysSession updated: XSession: 0 [SysSession **Please do not post TeamViewer IDs** [type=88 vt=7 tty= pseudotty=0 info=1 id=2 user=user11 state=user active=1 reliable=1]]
    2018/12/04 17:03:50.891 1042 **Please do not post TeamViewer IDs** S OSSessionEventTranslatorLinux::SessionUpdated: old osSessionID: **Please do not post TeamViewer IDs** username: user11 userLoggedIn: 1 locked: 0 primarySession: 1 unusableState: 0 connected: 1
    2018/12/04 17:03:50.891 1042 **Please do not post TeamViewer IDs** S OSSessionEventTranslatorLinux::SessionUpdated: new osSessionID: **Please do not post TeamViewer IDs** username: user11 userLoggedIn: 1 locked: 0 primarySession: 1 unusableState: 0 connected: 1
    2018/12/04 17:03:53.989 1042 **Please do not post TeamViewer IDs** S!! HttpRequestImpl::CurlFinished(): curl request failed: Timeout was reached (28), Connection timed out after 5000 milliseconds
    2018/12/04 17:03:53.989 1042 **Please do not post TeamViewer IDs** S!! Port443Connection::RequestFinishedCallback: failed with HTTP status code = 0
    2018/12/04 17:03:53.989 1042 **Please do not post TeamViewer IDs** S Activating Router carrier
    2018/12/04 17:03:53.989 1042 **Please do not post TeamViewer IDs** S CProcessCommandHandlerMasterConnect[5]::CreateMasterConnect(): master1.teamviewer.com:443, Connection 5, proxy=''
    2018/12/04 17:03:53.989 1042 **Please do not post TeamViewer IDs** S! TcpCarrierBase[4]::SendCompleteQueue(): No Connections, Type_Tcp, Dir_Outgoing, Ending 0, SendQueue 1, CurrentSendQueue 0, SendCache 0
    2018/12/04 17:03:53.989 1042 **Please do not post TeamViewer IDs** S Carrier[4]::EndCarrierInternal(): ClientID: 0 SupportsEndSession: 0, SupportsCCmd2: 0, SessionType_RoutingSession, SendQueue: 0 (4 Bytes), CurrentSendQueue: 0 (0 Bytes), SendCache: 0 (0 Bytes)
    2018/12/04 17:03:53.990 1042 **Please do not post TeamViewer IDs** S CGatewaySession[4]::EndSession(): Session to **Please do not post TeamViewer IDs** ended. Estimated capacity=0kBit/s, Latency=0ms
    2018/12/04 17:03:54.032 1042 **Please do not post TeamViewer IDs** S CProcessCommandHandlerMasterConnect[5]::HandleMasterConnect(): Sending MasterCommand actionid=**Please do not post TeamViewer IDs**&f=ServerUnavailable&ic=**Please do not post TeamViewer IDs**&id=**Please do not post TeamViewer IDs**&mid=lc218b78290d047b386c1250089b5dc06:30b5c200cb20:b7839149ab39488ebb6e6371f4f394fa&midv=1&serverip=FR-MRS-ANX-R005.teamviewer.com&v=14.0.14470
    2018/12/04 17:03:54.073 1042 **Please do not post TeamViewer IDs** S CProcessCommandHandlerMasterConnect[5]::ReceivedMasterResponse(): Received MasterCommand OK
    2018/12/04 17:03:54.073 1042 **Please do not post TeamViewer IDs** S! TcpCarrierBase[5]::SendCompleteQueue(): No Connections, Type_Tcp, Dir_Outgoing, Ending 0, SendQueue 1, CurrentSendQueue 0, SendCache 0
    2018/12/04 17:03:54.073 1042 **Please do not post TeamViewer IDs** S Carrier[5]::EndCarrierInternal(): ClientID: 0 SupportsEndSession: 0, SupportsCCmd2: 0, SessionType_MasterConnect, SendQueue: 0 (4 Bytes), CurrentSendQueue: 0 (0 Bytes), SendCache: 0 (0 Bytes)
    2018/12/04 17:04:17.344 1042 **Please do not post TeamViewer IDs** S NetworkControl::UpdateOnlineState alwaysOnline=1 delayOffline=0 otherProcess=0 restart=0

  • Moogwi
    Moogwi Posts: 2

    ~$ uname -a
    Linux PC-AL 4.9.0-5-686-pae #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) i686 GNU/Linux

    TV crash (seg fault) with this message:

    2018/12/04 17:03:46.587  1042 **Please do not post TeamViewer IDs** S   Activating Router carrier
    2018/12/04 17:03:46.587  1042 **Please do not post TeamViewer IDs** S   CProcessCommandHandlerMasterConnect[3]::CreateMasterConnect(): master1.teamviewer.com:443, Connection 3, proxy=''
    2018/12/04 17:03:47.344  1042 **Please do not post TeamViewer IDs** S   CTcpProcessConnector::HandleRead(): Socket gracefully closed (PID=1314)
    2018/12/04 17:03:47.344  1042 **Please do not post TeamViewer IDs** S   CTcpProcessConnector::CloseConnection(): PID=1314
    2018/12/04 17:03:47.344  1042 **Please do not post TeamViewer IDs** S   InterProcessNetwork::ProcessDisconnected(): ConnectionClosed session=**Please do not post TeamViewer IDs** ptype=2
    2018/12/04 17:03:47.344  1042 **Please do not post TeamViewer IDs** S   ProcessControlBase[2]::ProcessDisconnected: Process pid 1314 in session **Please do not post TeamViewer IDs** disconnected
    2018/12/04 17:03:47.344  1042 **Please do not post TeamViewer IDs** S   NetworkControlLinux::ShouldDelayOffline: Start delay update online state
    2018/12/04 17:03:47.344  1042 **Please do not post TeamViewer IDs** S   NetworkControl::UpdateOnlineState alwaysOnline=1 delayOffline=1 otherProcess=0 restart=0
    2018/12/04 17:03:48.889  1042 **Please do not post TeamViewer IDs** S   CProcessCommandHandlerMasterConnect[3]::HandleMasterConnect(): Sending MasterCommand client=TV&connectionmode=1&f=RequestRoute2&homeserver=&ic=**Please do not post TeamViewer IDs**&id=**Please do not post TeamViewer IDs**&id1=**Please do not post TeamViewer IDs**&id2=**Please do not post TeamViewer IDs**&licensedremoteaccesstypes=0&mid=lc218b78290d047b386c1250089b5dc06:30b5c200cb20:b7839149ab39488ebb6e6371f4f394fa&midv=1&v=14.0.14470 
    2018/12/04 17:03:48.988  1042 **Please do not post TeamViewer IDs** S   CProcessCommandHandlerMasterConnect[3]::ReceivedMasterResponse(): Received MasterCommand CONNECT@188.172.245.136_0_128000_**Please do not post TeamViewer IDs**_**Please do not post TeamViewer IDs**_32504__1_0_16778176_128000_16778176:128000;**Please do not post TeamViewer IDs**:1280000;4:640000_**Please do not post TeamViewer IDs**_**Please do not post TeamViewer IDs**_FR-MRS-ANX-R005.teamviewer.com_eQBwZWCBGNdjjAE=_eQBwZWCBGNdjjAE=
    2018/12/04 17:03:48.988  1042 **Please do not post TeamViewer IDs** S!  TcpCarrierBase[3]::SendCompleteQueue(): No Connections, Type_Tcp, Dir_Outgoing, Ending 0, SendQueue 1, CurrentSendQueue 0, SendCache 0
    2018/12/04 17:03:48.988  1042 **Please do not post TeamViewer IDs** S   Activating Router carrier
    2018/12/04 17:03:48.988  1042 **Please do not post TeamViewer IDs** S   CommandHandlerRouting[4]::CreateActiveSession(): outgoing session to **Please do not post TeamViewer IDs** via FR-MRS-ANX-R005.teamviewer.com, protocol Port443
    2018/12/04 17:03:48.988  1042 **Please do not post TeamViewer IDs** S   Carrier[3]::EndCarrierInternal(): ClientID: 0 SupportsEndSession: 0, SupportsCCmd2: 0, SessionType_MasterConnect, SendQueue: 0 (4 Bytes), CurrentSendQueue: 0 (0 Bytes), SendCache: 0 (0 Bytes)
    2018/12/04 17:03:50.891  1042 **Please do not post TeamViewer IDs** S   ProcessControlBase[2]: Process 1314 in session **Please do not post TeamViewer IDs** has terminated
    2018/12/04 17:03:50.891  1042 **Please do not post TeamViewer IDs** S   SysSessionInfoManager: updating session information for session **Please do not post TeamViewer IDs** from GUI
    2018/12/04 17:03:50.891  1042 **Please do not post TeamViewer IDs** S   SysSession updated: XSession: 0 [SysSession **Please do not post TeamViewer IDs** [type=88 vt=7 tty= pseudotty=0 info=1 id=2 user=user11 state=user active=1 reliable=1]]
    2018/12/04 17:03:50.891  1042 **Please do not post TeamViewer IDs** S   OSSessionEventTranslatorLinux::SessionUpdated: old osSessionID: **Please do not post TeamViewer IDs** username: user11 userLoggedIn: 1 locked: 0 primarySession: 1 unusableState: 0 connected: 1
    2018/12/04 17:03:50.891  1042 **Please do not post TeamViewer IDs** S   OSSessionEventTranslatorLinux::SessionUpdated: new osSessionID: **Please do not post TeamViewer IDs** username: user11 userLoggedIn: 1 locked: 0 primarySession: 1 unusableState: 0 connected: 1
    2018/12/04 17:03:53.989  1042 **Please do not post TeamViewer IDs** S!! HttpRequestImpl::CurlFinished(): curl request failed: Timeout was reached (28), Connection timed out after 5000 milliseconds
    2018/12/04 17:03:53.989  1042 **Please do not post TeamViewer IDs** S!! Port443Connection::RequestFinishedCallback: failed with HTTP status code = 0
    2018/12/04 17:03:53.989  1042 **Please do not post TeamViewer IDs** S   Activating Router carrier
    2018/12/04 17:03:53.989  1042 **Please do not post TeamViewer IDs** S   CProcessCommandHandlerMasterConnect[5]::CreateMasterConnect(): master1.teamviewer.com:443, Connection 5, proxy=''
    2018/12/04 17:03:53.989  1042 **Please do not post TeamViewer IDs** S!  TcpCarrierBase[4]::SendCompleteQueue(): No Connections, Type_Tcp, Dir_Outgoing, Ending 0, SendQueue 1, CurrentSendQueue 0, SendCache 0
    2018/12/04 17:03:53.989  1042 **Please do not post TeamViewer IDs** S   Carrier[4]::EndCarrierInternal(): ClientID: 0 SupportsEndSession: 0, SupportsCCmd2: 0, SessionType_RoutingSession, SendQueue: 0 (4 Bytes), CurrentSendQueue: 0 (0 Bytes), SendCache: 0 (0 Bytes)
    2018/12/04 17:03:53.990  1042 **Please do not post TeamViewer IDs** S   CGatewaySession[4]::EndSession(): Session to **Please do not post TeamViewer IDs** ended. Estimated capacity=0kBit/s, Latency=0ms
    2018/12/04 17:03:54.032  1042 **Please do not post TeamViewer IDs** S   CProcessCommandHandlerMasterConnect[5]::HandleMasterConnect(): Sending MasterCommand actionid=**Please do not post TeamViewer IDs**&f=ServerUnavailable&ic=**Please do not post TeamViewer IDs**&id=**Please do not post TeamViewer IDs**&mid=lc218b78290d047b386c1250089b5dc06:30b5c200cb20:b7839149ab39488ebb6e6371f4f394fa&midv=1&serverip=FR-MRS-ANX-R005.teamviewer.com&v=14.0.14470 
    2018/12/04 17:03:54.073  1042 **Please do not post TeamViewer IDs** S   CProcessCommandHandlerMasterConnect[5]::ReceivedMasterResponse(): Received MasterCommand OK
    2018/12/04 17:03:54.073  1042 **Please do not post TeamViewer IDs** S!  TcpCarrierBase[5]::SendCompleteQueue(): No Connections, Type_Tcp, Dir_Outgoing, Ending 0, SendQueue 1, CurrentSendQueue 0, SendCache 0
    2018/12/04 17:03:54.073  1042 **Please do not post TeamViewer IDs** S   Carrier[5]::EndCarrierInternal(): ClientID: 0 SupportsEndSession: 0, SupportsCCmd2: 0, SessionType_MasterConnect, SendQueue: 0 (4 Bytes), CurrentSendQueue: 0 (0 Bytes), SendCache: 0 (0 Bytes)
    2018/12/04 17:04:17.344  1042 **Please do not post TeamViewer IDs** S   NetworkControl::UpdateOnlineState alwaysOnline=1 delayOffline=0 otherProcess=0 restart=0

     

  • Enkidu
    Enkidu Posts: 1

    Hi,

    I use TeamViewer 14.0.14470 on LinuxMint 18.3.
    On my tablet, a Lenovo Yoga 2 Pro with Android 5, latest version of QuickSupport
    On my phone, OnePlus 3T, Android 7, also latest version of QuickSupport.

    Problem:
    When I enter PartnerID in TV on Mint and I confirm connection on phone/tablet it says connected, but not window is being opened.

    Trying the same from a Windows PC, everything is working.
    Trying the same with TV 13, all is working as expected.

    Where's the problem? Any hint for me?

    Tnx,
    Enkidu

  • beast-usa
    beast-usa Posts: 88

    It would be really great if there was an update that let 13 connect to 14 until 14 is fixed. I can work fine on one computer if it doesn't crash when connecting. Some times even two or three then CRASH and start over! The crash gives no error nothing TV just closes. I have purged it a few times, tried to make Win version run in wine, un-installed, clean install, un-install, install 13 and upgrade to 14. With all the same results updated everything on Linux to the newest versions... Still up to 40 ramdom crashes before I give up and go to Winblows.

    It's super annoying using TV in VM Windows on Linux. :( I normally work on 4 to 20 computers at the same time which is impossible now unless I use VM or just log into Winblows 10.

    I really think that should be #1 on the list ALWAYS make the old version work on the new one. Not all of them but at least one version back until the newest version works. 12 to 13, 13 to 14 that way we can keep working while you guys fix the problems. Without dual boot and VM I would be up a creek right now.

  • swissbuechi
    swissbuechi Posts: 1

    The signin to my account works now in 14..014470 on Ubuntu 18.04.

  • beast-usa
    beast-usa Posts: 88

    I rolled back to Ubuntu/Xubuntu 16.0.4 and upgraded 13 to 14 newest version and only had one crash last night. And it even gave me an error report which I submitted.

    So what seemed to fix all my problems in TeamViewer 14 was not using Xubuntu 18.0.4. I will do an image back-up of the working version of Xubuntu 16.0.4. Then upgrade to 18.0.4 and see if the random crashing comes back. I will post the results after the upgrade if it's crash city again I will just stick with 16.0.4.

  • beast-usa
    beast-usa Posts: 88

    Well it's better but still not right. :(
    Now that I have all the updates installed on 16.0.4 it's crashing more and more and after about 6 crashes TV won't start until I restart the computer.

    PLEASE FIX LINUX :)

  • beast-usa
    beast-usa Posts: 88

    Please FIX 14! The Linux version is a joke!

    Added all the things most of us DID NOT WANT, made it HUGE and annoying and it's not stable! I have spent so many hours, rolling back to Xubuntu/Ubuntu 16.0.4 LTS, upgrading to 18.0.4, clean install of 16.0.4, clean install of 18.0.4. With all the same results works great until I do updates as soon as I update either 16 or 18 it just crashes OVER & OVER & OVER!!!

    Then I start stupid winblows in VM and do my work in VM! The main reason I liked this software is for Linux, linux is my primary OS.

    I'm not willing to waste anymore of my time trying to make the POS 14 work! 13 was fine it only needed tabbed browsing then you added all this garbage, made it HUGE and a waste of screen space and 98% of the time NOT STABLE!

  • MattiViljanen
    MattiViljanen Posts: 13

    Linux version is limited feature-wise and not yet ready for production use. The biggest issue are that service queue can't be processed, and Alt-Tab and Windows keys don't get redirected to session properly. Two more minor ones are that there is no way to start Management Console from the UI, and there are a lot of settings missing (especially in the advanced section).

    If you advertise the Linux support, the software should live up to it.

  • MattiViljanen
    MattiViljanen Posts: 13

    I just installed TeamViewer 14.1.3399, and here are my quick comments on it:

    • Service Quere connections can be assigned with a right click on the device in the Computers & Contacts list, connected, and closed afterwards (this may already have been possible with 14.0, but I just now discovered the right click)
    • Selecting "Properties" from a service queue device results in glitchy UI and TeamViewer must be restarted (sometimes killed) in order for it to recover (this was with 14.0 as well, didn't report it until now)
    • Alt-Tab, Alt+Shift-Tab and Windows keys still don't get redirected (using Wayland here)

    On the positive side:

    • Connection menu now has Open Management Console item. Yes!
    • The freezing sessions should have feen fixed (I actually didn't realise I had this issue until I read about it - I blamed my Internet connection, but that has proven to be stable in all later TeamViewer freezing cases for me)

    I really get the feeling I am only complaining all the time. The truth is that I can do practically all tasks with my Linux setup, too, with not at all too serious caveats. I still couldn't recommend the Linux variant to a non-technical person, but hey, I guess everyone using TeamViewer at this side of help desk are technical personnell after all :)

    Great work! Let the change log grow long!

  • beast-usa
    beast-usa Posts: 88

    I didn't even try 14.1 I gave up and I'm uninstalling 14 on all my customers computers reinstalling 13.2. Since there is no way to do this remotely I'm using DWAGENT which has zero problems in Linux and 100% free.

    I don't know if everyone else only connects to one computer at a time? But 14 just does not work on Xubuntu 16.0.4 or 18.04 clean install or upgrade. I can connect until I install any updates after updates it just crashes over & over on any over one computer.

    Connect to one all good maybe a second one or crash on the second or third connection. I normally connect to 10 plus computers at one time. And yes I have the paid version.

  • MattiViljanen
    MattiViljanen Posts: 13

    @beast-usa There are crash-related fixes in 14.1.3399, so please at least test it on your setup to see if anything has changed. I have update to it and, so far, I haven't found anything gone backwards.

  • DanielStm
    DanielStm Posts: 224 Staff member 🤠

    Just wanted to let you know that TV 14.1 available. I updated / enhanced the article above.
    @MattiViljanen, basically you nailed it :) And yes, the "properties" should not be there for service queue. I was made aware of it a few days ago, but too late for this release. MCO link was already available in the C&C tab, but maybe not obvious enough. I hope we can get the keyboard-forwarding (Alt-Tab) in the coming months.

    @beast-usa, if you think the UI is huge - did you discover you can resize it and even have a slim portrait mode? (@DialectKBA might also find that interesting)
    I understand that crashes are frustrating. It should be gone now. The thing is, some people complained here about instabilites, but I did not receive crash dumps we could investigate. The crash when starting a connection from C&C could only be fixed because one colleague here observed it and I could reproduce it. If you observe crashes, please use Help / Feedback to send us the crash data. That time is likely better invested than trying to work around a bug in the code. Crashes have high priority for us, but we can only fix them if we have useful bugreports with crash dumps.
    Same for @Moogwi, if you still have issues.
    One more thing @beast-usa. Agreed, TV13 was very disruptive on Linux. I think TV14 much less so (with the exception of that crash that hopefully is now fixed for you). In the upcoming months you might notice that we are transitioning away from yearly big releases to smaller increments. Especially the next few months will bring few changes, but improve quality.
    So, if there are still crashes and other major glitches (not missing features), please let us know soon.

    @Enkidu: Connecting to mobile (Android, iOS) is currently not implemented in the native TeamViewer for Linux (TV13, TV14). It was in TV12, which was Wine based. To learn more about this transition, have a look at the previous announcements linked in above article.

    @Ctuchick: Fluxbox issue should be fixed.
    @swissbuechi: glad to hear :robothappy:

    Cheers,
    Daniel

     

    Linux Developer
  • Ctuchick
    Ctuchick Posts: 4

    @DanielStm

    14.1.3399 - 0x0 pixel dialogs are fixed

    Thanks mate

  • beast-usa
    beast-usa Posts: 88

    After I rolled back about 60 computers :( 14.1 is out. I did try 14.1 to 13.2 and it isn't crashing yet. I'm not upgrading any of the 13.2's until I know it's working 100% it's just to hard to login with something else, uninstall & reinstall.

    @DanielStm 
    I have dragged it to as small as it will drag still almost twice as wide as 13.2 :( What and where do I find "Portrait Mode"? Is that just the list of computers like before? Stability is my main concern and the only feature I want is tabbed windows since I work on groups at a time.

  • DanielStm
    DanielStm Posts: 224 Staff member 🤠

    @beast-usa, if you make it tall, you can drag it half-width.
    Tabbed session windows, I suppose? I can not promise them for the near future, as we have other features missing that are asked for more often.

    Cheers,
    Daniel

    Linux Developer
  • beast-usa
    beast-usa Posts: 88

    @DanielStm
    Yep I already do that stretch it full height of one of my 40 inch screens. Then drag it as small as it will go still twice as wide as 13. :( I guess most people are not working on more then one at a time. That's when tabbed is great I almost never work on less 4 at a time. Once in awhile I do get the one at a time. No rush on tabbed but it was the only feature I wanted all the rest of this stuff I never use. I guess it's because I work on so many at once most of the features mean nothing to me. Stability on multiple systems is #1. Upload speed would be #2 but I have been adding what I upload to my website then using their browser to download. Well a browser I add Slimjet "Turbo Download". I try your upload, restart it twice one time it's super fast next time (same computer) it's super slow. Then I just down load the stuff not a big deal.

    Thank you SO MUCH for the fix in 14.1! 

  • MattiViljanen
    MattiViljanen Posts: 13
    @beast-usa I also typically many connections at the same time, and for my brain, it is better to have three monitors and each session in its own window. That way I can see what is going on in the sessions (especially if the client computer has multiple displays) at a glance. I find the tab system unintuitive, but it is clear that both styles have their users and uses :)

    What it comes to upload speed, we have long since given up on TeamViewer file transfer speeds. For small files it's fine, but anything larger and we take an alternative route. And many bigger downloads can be obtained directly from a download site, so there is that, too.
  • DanielStm
    DanielStm Posts: 224 Staff member 🤠

    @beast-usa, that sounds wrong to me. If you make it tall, you should be able to drag to as slim as 400px, which is definitely less than ever before. "Control Remote Computer" is then placed below "Allow Remote Control". Maybe what you're seeing is a HiDPI issue? If you want to discuss that further, please open a new topic and maybe add a screenshot.

    @MattiViljanen, sad to hear that. When was the last time you actually tried? Our performance team really put a lot of effort in making file transfer speeds fast. If the speed is way below the theoretical max, there are (to my knowledge) two main reasons: 1) switching to UDP failed. TeamViewer always attempts to switch to a UDP connection, which will be fast. In fallback mode, speeds are much lower. That is why you might see dramatic differences between two connections. 2) you have a IPv6-only connection. It's a variation of the above, because in this case it will currently never be UDP, but this is currently being worked on.
    If you have a well-defined test case between two locations where you observe that switching to UDP often fails, you might contact support and request it to be investigated.

    Linux Developer
  • MattiViljanen
    MattiViljanen Posts: 13

    @DanielStm I tried the transfer speed at some point after version 14 was out (that was from my Windows 10 to a Windows Server 2012 R2 I think). The speed is not that bad, it can reach a few megabytes per second, but if the limit is 10MB/s on both ends, it never gets maxed out. Then we just throw the file to a local server and use SFTP to get it fast. Our firewall is quite proactive and nosey, so that may have something to do with it. 1-2MB/s is okay really, but when there are gigabytes to transfer, every bit counts (pun intended). Due to our firewall I don't think we can be used as a significant test case really, but I'll test the transfer speeds the next time I have a chance. Thanks!

  • beast-usa
    beast-usa Posts: 88

    Just under twice as wide I only use contacts it doesn't start that small each time it starts with Allow Remote Control on the left and Control Remote Computer on the right. Then I switch to contacts drag it to this size the old size was smaller, opened on contacts and took up less space it was perfect.

    huge-new-tv.jpg
    If I'm stuck with the new huge size oh well nothing I can do about it now. But PLEASE don't make it any bigger. :( Main thing is it's working again this month jumpin into VM every five minutes was driving me to drink! LOL  

  • JohnTrav
    JohnTrav Posts: 13

    .., we are aware that some of our customers are still on systems that don't sport Qt 5.5 (or 5.6). For this reason, we added a compatibility library to our repository, providing Qt for TeamViewer if you don't have it. This enables you to update from TV13 to TeamViewer 14 on Debian 8 and Ubuntu 14.04...

    How do we gat this compatibility library ? I am (stuck) on Linux Mint 17.3 (hardware compatibility issues) which is based on Ubuntu 14.04, so I only have qt4, not qt5...

    I am not now surprised that 14.1.3399 didn't work on my machine, for the time being I have installed 14.0.14470, which works for me. No crashes yet...
    JT:

  • HelloWorld1
    HelloWorld1 Posts: 1

    Now it doesn't run GUI on debian 8!

  • beast-usa
    beast-usa Posts: 88

    @MattiViljanen
    I like the tabs because I use my other monitors for text info, password, encryption keys, file/folders. And most of my work is scheduled so I do about 20 things on each one. So I just start on the left #1 process 1, #2 process 1 and so on. Makes it very fast not needing to minimize to get to text/info files or folders with software I need for each system. Not being in tabs is OK up to about 10 then it just gets crazy. 20 tabs for me is just so much faster then 20 windows.

    In the winblows version you can turn tabs on or off or remove one or two really slow systems and put them on a different screen.

    Tabs lol are also the reason I love the Linux folder system so much more the windows. I have 2 file explorer windows open with 4 to 6 tabs in each one. Each tab a different part of whats needed that night.

    Like most computer people a have a touch of OCD. :) 

  • cool-cat
    cool-cat Posts: 3

    I am still having issues with TeamViewer 14.1.3399. When I open the program, the remote control ID and password show in the GUI as expected, but the program freezes after a few seconds (without connecting to anyone or doing anything else). I am running Linux Mint 18 64-bit. This has always occured on TeamViewer 13 and 14 using either the .deb file or the tar.xz. TeamViewer 10, 11, and 12 work fine. I am not sure how to attach log files, so I copied below the few lines that had errors. Can anyone help diagnose the problem?

    2018/12/29 16:17:18.121 18799 **Please do not post TeamViewer IDs**72896 GX0!! DecryptByteArray exception: StoredDataCipherAES: Invalid Ciphertext, error: "StreamTransformationFilter: invalid PKCS #7 block padding found", Errorcode=11
    2018/12/29 16:17:18.121 18799 **Please do not post TeamViewer IDs**72896 GX0!! ApplicationLookOfflineState::ApplicationAppearanceOfflineState: state not loaded, Errorcode=11
    2018/12/29 16:17:18.121 18799 **Please do not post TeamViewer IDs**72896 GX0   ManagerHolderStateMachine: Switching from None to NotReady
    2018/12/29 16:17:18.121 18799 **Please do not post TeamViewer IDs**48288 GX0   ChatManager::ChatManager: created
    2018/12/29 16:17:18.121 18799 **Please do not post TeamViewer IDs**48288 GX0   ChatManager::Factory: ChatManager created
    2018/12/29 16:17:18.122 18799 **Please do not post TeamViewer IDs**48288 GX0   IncomingBetterChatCommandHandler::IncomingBetterChatCommandHandler: created
    2018/12/29 16:17:18.122 18799 **Please do not post TeamViewer IDs**48288 GX0   IncomingCommandRegistration::Start: registering for ready state properties
    2018/12/29 16:17:18.122 18799 **Please do not post TeamViewer IDs**72896 GX0   Initialised XFixes extension (base=87 error=140)

  • Delta1
    Delta1 Posts: 2
    TeamViewer 14.1.3399 is a complete mess on linux mint 19.1
    When marked to start when computer boots unlike version 13.2, It will always run in the foreground and closing the window completely stops the listener (teamviewer.d) instead of the foreground application

    Also putting a lot of load on processor since the foreground application is always running and stuck on the taskbar

    Completely STUPID update to such a great software

    PS - dont break what already works

    Going back to tw13.2
  • Delta1
    Delta1 Posts: 2
    Too many bugs
    The screen shared is completely distorted
    https://imgur.com/a/tqRkTZw
    Also in the 2nd image, there are 2 services running besides teamviewerd
    I have already configured unattended access but still the foreground window stays and closing that completely stops the receiver
  • ggonmar
    ggonmar Posts: 1

    Hi, 
    am I the only one not being able to log into my TeamViewer account? It's like the  "Log In" button just went numb....

  • cool-cat
    cool-cat Posts: 3

    I don't have an account, but my program freezes seconds after opening so I couldn't log in anyways. 1 CPU thread runs at 100% for about a minute, then the program either closes or crashes. Does your program freeze?

  • CarlosJ
    CarlosJ Posts: 1
    rm -rf ~/.config/teamviewer
Trustpilot

Categories

This Week's Leaders