teamviewer.com link icon
or
Ask The Community

TM is able to connect but refuses to login (connection problems blabla) (ubuntu)

Hey Guy's, Girls and others...

I just installed teamviewer on the latest ubuntu and everything works fine except login in.

It's connecting and shows connected but then...



There was a connectivity issue. Please check your internet connection and try again. So if there is a connectivity issue why would it be able to connect in the first place... Any one a idea how i could fix this?
«1

Comments

  • Hello.

    I have a computer running Linux Mint 18 32 bits with the latest version of TV (13.2.13582).

    It used to work fine but for some reason, it got disconnected from my TV account and I now cannot login again. I have the TV GUI showing up normally when I start TV and it seems to work fine save for one problem login to my TV account : be it from the 'Computers and contacts' window or from the Option window, it's the same : I can type my login and my password but nothing happens at all when I click the 'open session' button. The button blinks for a small instant but nothing else changes. No error message, nothing.

    PS: I also have problems with the TV Community web site. Unless I start a private session with the browser, I cannot have access to any page of the web site except the 'Complete your registration' page, which is ridiculous since I already have an account, but I cannot login since I am automatically redirected to this page every time I ask for any URL of the web site.

  • Hello,

    I have the same problem, I just installed teamviewer 13.2.13582, on debian stretch. I can open teamviewer, and connect to a remote host.

    When I click on the "login" button in the GUI, nothing happens, I can't log in.

    In log file, I have :

    2018/09/09 01:00:12.885  8007 140702851701760 GT!! AccountLoginStateMachine : : SetLoginName: unexpected state, Errorcode=11
    2018/09/09 01:00:12.885 8007 140702851701760 GT!! AccountLoginStateMachine : : OnError::Trace: SetLoginState(1); SetLoginState(3); SetLoginName(); SetLoginState(4); SetLoginState(3); SetLoginName(); SetLoginState(4); SetLoginState(3); SetLoginName(); SetLoginState(4); SetLoginName(); SetLoginState(3); StartLogin(); SetLoginName(); SetLoginState(4); StartLogin(); SetLoginName(); SetLoginState(3); StartLogin(); SetLoginName(); SetLoginState(4); StartLogin(); SetLoginState(3); SetLoginState(3); SetLoginState(3); SetLoginName(); SetLoginState(4); StartLogin(); SetLoginName(); , Errorcode=11

     

    And in root, when I do "teamviewer setup", when I validate the password step, I get an error: "There was a connectivity problem. Please check your Internet connection and try again."

     Would the 2 problems be related to ?

  • Hello,

    I have the same problem, I just installed teamviewer 13, on debian stretch, I can open teamviewer, and connect to a remote host.

    When I click on the "login" button in the GUI, nothing happens, I can't identify myself. In log file, I have :

    2018/09/09 01:15:52.927  8007 140702851701760 GT!! AccountLoginStateMachine::SetLoginName: unexpected state, Errorcode=11
    2018/09/09 01:15:52.927 8007 140702851701760 GT!! AccountLoginStateMachine::OnError::Trace: SetLoginState(1); SetLoginState(3); SetLoginName(); SetLoginState(4); SetLoginState(3); SetLoginName(); SetLoginState(4); SetLoginState(3); SetLoginName(); SetLoginState(4); SetLoginName(); SetLoginState(3); StartLogin(); SetLoginName(); SetLoginState(4); StartLogin(); SetLoginName(); SetLoginState(3); StartLogin(); SetLoginName(); SetLoginState(4); StartLogin(); SetLoginState(3); SetLoginState(3); SetLoginState(3); SetLoginName(); SetLoginState(4); StartLogin(); SetLoginName(); SetLoginState(3); StartLogin(); SetLoginState(3); SetLoginName(); SetLoginState(4); StartLogin(); SetLoginName(); SetLoginState(3); StartLogin(); SetLoginName(); SetLoginState(4); StartLogin(); SetLoginName(); , Errorcode=11

    And on the console in root, when I do "teamviewer setup", when I validate the password step, I get an error: "There was a connectivity problem. Please check your Internet connection and try again."

    Would the two problems be related to ?

  • In my setup (manjaro), I had to install a dependency, nss-mdns, and it fixed the grayed login! Not sure your issue is the same though.

  • Htanks jsamr.

    I installed the libnss-mdns package, but it didn't solve the problem.
    It seems I forgot 1 lines in the log, so see the new console output :

    2018/09/10 17:46:13.441 11959 140195302520576 GT!! SSOAuthentication: :IsSSOActive(): Unable to determine if SSO is active! Error was: SecureNetworkTransport:4, Errorcode=11
    2018/09/10 17:46:13.442 11959 140195302520576 GT!! AccountLoginStateMachine: :OnLoginStarted::IsSsoActive failed, Errorcode=11
    2018/09/10 17:46:13.442 11959 140195302520576 GT!! AccountLoginStateMachine: :OnError::Trace: SetLoginState(1); SetLoginState(3); SetLoginName(); SetLoginState(4); SetLoginName(); SetLoginState(3); StartLogin(); SetLoginState(3); SetLoginName(); SetLoginState(4); StartLogin(); SetLoginName(); SetLoginState(3); StartLogin(); SetLoginState(3); SetLoginName(); SetLoginState(4); StartLogin(); SetLoginName(); SetLoginState(3); StartLogin(); SetLoginName(); SetLoginState(4); StartLogin(); SetLoginState(3); SetLoginState(3); SetLoginName(); SetLoginState(4); StartLogin(); SetLoginName(); SetLoginState(3); StartLogin(); SetLoginName(); SetLoginState(4); StartLogin(); SetLoginState(3); SetLoginName(); SetLoginState(4); StartLogin(); SetLoginName(); SetLoginState(3); StartLogin(); SetLoginState(3); SetLoginName(); SetLoginState(4); StartLogin(); SetLoginState(3); SetLoginState(3); SetLoginName(); SetLoginState(4); StartLogin(); SetLoginState(3); SetLoginName(); SetLoginState(4); StartLogin(); SetLoginName(); SetLoginState(3); StartLogin(); SetLoginName(); SetLoginState(4); StartLogin(); SetLoginName(); SetLoginState(3); StartLogin(); SetLoginName(); SetLoginState(4); StartLogin(); SetLoginName(); SetLoginState(3); StartLogin(); SetLoginState(3); SetLoginState(3); SetLoginState(3); SetLoginName(); SetLoginState(4); StartLogin(); , Errorcode=11

    I tried with a password in alphanumeric, to check if there was a problem with the special characters, and it didn't change anything.

  • Didn't work for me eather :(

     

  • same problem here. cannot login. e-mail address is filled out. but both fields and the button are grayed out.

    13.2.13352

    Ubuntu 18.04.1

    Please help. Cannot work!

  • I never got any answer that made sense from this forum but reinstalling the deb package seems to have solved the problem.

  • Well, no, in the end, it's more complex than that :

    Every time I reboot the computer, the same problem occurs again : it is impossible to login because nothing happens when I click the 'open session' button. I may close and reopen TV, it's the same.

    The only way I found to make it work is to remove the .deb package and reinstall it again. Then I can log in normally, logout if I want, log in again, quit TV, open it again, it works.

    But, bloody **bleep**, I am not going to reinstall TV every time I restart the **bleep** computer !

     

  • even apt purge and reinstalling isn't helping here. it is really super annoying!!!

  • DanielStm
    DanielStm Posts: 224 Staff

    Are all of you here really talking about the same thing? (Because @whitelabelgroup talks about login, but also connecting, which can be read as connect to a device, rather than login in to the account)

    Anyway, signing in to the account seems to be an issue with the summer release on all platforms for some (few) people.

    @exactt, @codermjb: Until we release a fix, I can only suggest some workarounds:
    * restart the GUI (close TeamViewer via tray icon, start again)
      if this helps, it might also help to
    * disable "start with system" and start it manually then
    * sudo teamviewer daemon restart
    * go back to previous version (apt install teamviewer=13.1.8286)

    I hope that at least one of these is acceptable/viable/working for those affected.

    Cheers,
    Daniel

    Linux Developer
  • kosnik
    kosnik Posts: 7

    Hello,

    From what I understood, with my level of English not terrible, it's the same problem, but, maybe I'm wrong.
    I tried to uninstall TV13 and then install it again, I tried to install TV14, I tried to stop the daemon, and restart it.

    And it didn't solve my problem.
    I think for now I'm going to do without connecting with the TV GUI.

  • DanielStm
    DanielStm Posts: 224 Staff

    @kosnik: Please
    * stop the daemon
    * teamviewer ps    (should not list any process, if it does, kill them. Check again, make sure none is left)
    * start the daemon
    * start TeamViewer

    If your problem persists, please explain exactly what it is, because I'm uncertain what you can do and what does not work.

    Cheers,
    Daniel

    Linux Developer
  • kosnik
    kosnik Posts: 7

    @DanielStmthank for your help

    # teamviewer daemon stop
    systemctl stop teamviewerd.service
    # teamviewer psJe suis actuellement en version 14.0.8346, si besoin je peut réinstaller une version 13.
    root 7413 0.0 0.0 131720 4088 pts/5 S+ 18:00 Je suis actuellement en version 14.0.8346, si besoin je peut réinstaller une version 13. 0:00 /bin/bash /usr/bin/teamviewer ps
    # teamviewer daemon start
    systemctl start teamviewerd.service
    # teamviewer ps
    root 8549 0.1 0.0 1873380 9780 ? Sl 18:02 0:00 /opt/teamviewer/tv_bin/teamviewerd -d
    root 8803 0.0 0.0 131720 4152 pts/5 S+ 18:03 0:00 /bin/bash /usr/bin/teamviewer ps
    $ teamviewerJe suis actuellement en version 14.0.8346, si besoin je peut réinstaller une version 13.
    Init...
    CheckCPU: SSE2 support: yes
    Checking setup...
    Launching TeamViewer ...
    Launching TeamViewer GUI ...

    Then I go to the "Login" tab, I fill in the email and password fields, the "Login" button is blue, but if I click on it nothing happens.

    I am currently in version 14.0.8346, if necessary I can reinstall version 13.

     

    20181023_174455.png

     

  • DanielStm
    DanielStm Posts: 224 Staff

    @kosnik, is the behavior the same on TV13 and TV14? Does it help to click again? (Or press enter in the password field twice?)

    @exactt, can you please line out how the behavior is for you? I'm still not convinced everybody in this thread experiences the same thing.

    Cheers,
    Daniel

    Linux Developer
  • exactt
    exactt Posts: 22

    @DanielStmI can't reproduce it everytime I start Teamviewer. I also tried TV14 but reverted back as I was told in the release notes thread that I have to have a subscription, which i don't, in order to use TV14 correctly.

    Anway the problem has 3 effects: Sometimes login fields are grayed out. Sometimes the login screen is just a white and black (or gray) area on top of each other. And sometimes I can enter my password but I cannot submit. Just nothing happens at all.

  • kosnik
    kosnik Posts: 7

    Indeed, there are different behaviors between @exactll's return and mine, because I am always the same non-response.

    My login submission problem is the same on TV13 and TV14. Here are the Debian packages I tried with have the same behavior:
    - teamviewer_13.2.2.13582_amd64.deb
    - teamviewer_13.2.2.26559_amd64.deb
    - teamviewer_14.0.8346_amd64.deb
    As well as any intermediate versions, obtained following updates with apt.

    Clicking or pressing the enter key, once or several times, does not govern the interface.

    In the logs (/var/log/teamviewer14/TeamViewer14_Logfile.log), when I press the "log in" button, I have this:

    2018/10/26 12:48:50.105 12231 **Please do not post TeamViewer IDs**16800 S   SecureNetworkConnection:: SendCallbackHandler(): [ remoteID: 25 connection: **Please do not post TeamViewer IDs** remoteConnection: 0 ], Error: RCommand (Timeout)
    2018/10/26 12:48:50.105 12231 **Please do not post TeamViewer IDs**16800 S SecureNetworkConnection:: SendCallbackHandler(): [ remoteID: 25 connection: **Please do not post TeamViewer IDs** remoteConnection: 0 ] Resetting connection due to error RCommand (Timeout)
    2018/10/26 12:48:50.105 12231 **Please do not post TeamViewer IDs**16800 S RetryHandle:: HandleRetry(): Trying resend to 25 failed with error SecureNetworkTransport:4, retrying (2 retries remaining) BCmd: CC=66 CT=1
    2018/10/26 12:49:02.110 12231 **Please do not post TeamViewer IDs**94912 S SecureNetworkConnection:: SendCallbackHandler(): [ remoteID: 25 connection: **Please do not post TeamViewer IDs** remoteConnection: 0 ], Error: RCommand (Timeout)
    2018/10/26 12:49:02.110 12231 **Please do not post TeamViewer IDs**94912 S SecureNetworkConnection:: SendCallbackHandler(): [ remoteID: 25 connection: **Please do not post TeamViewer IDs** remoteConnection: 0 ] Resetting connection due to error RCommand (Timeout)
    2018/10/26 12:49:02.110 12231 **Please do not post TeamViewer IDs**94912 S RetryHandle:: HandleRetry(): Trying resend to 25 failed with error SecureNetworkTransport:4, retrying (1 retries remaining) BCmd: CC=66 CT=1

    If I type the command 'teamviewer setup' in the log, I have this:

     

     

    2018/10/26 13:03:14.064 18891 **Please do not post TeamViewer IDs**06592 CT   Logger started.
    2018/10/26 13:03:14.065 18891 **Please do not post TeamViewer IDs**06592 CT Found 0 core dump files ...
    2018/10/26 13:03:14.067 18891 **Please do not post TeamViewer IDs**06592 CT systemd: logind service available
    2018/10/26 13:03:14.070 18891 **Please do not post TeamViewer IDs**06592 CT systemd: New seat seat0 [path=/org/freedesktop/login1/seat/seat0, activeSession='', canGraphical=0, canTTY=0, canMultiSession=0]
    2018/10/26 13:03:14.072 18891 **Please do not post TeamViewer IDs**06592 CT LogindSessionInfo: New session LogindSessionInfo [id=3 user=kosnik state=user active=1 reliable=1 infoId=**Please do not post TeamViewer IDs**] [path=/org/freedesktop/login1/session/_33 TTY=??? seat= display= vtnr=**Please do not post TeamViewer IDs** owner=[SysUser: kosnik [uid=1000, gid=1000 home=/home/kosnik gecos=kosnik,,, shell=/bin/bash]] idle=0(0) active=1 type=tty class=user state=active timestamp=**Please do not post TeamViewer IDs**886478 service=su defaultCG= leader=1666 audit=3 remote=0 rHost= rUser=root killProc=0]
    2018/10/26 13:03:14.075 18891 **Please do not post TeamViewer IDs**06592 CT SysSessionInfoManager: observing sessions from logind is marked as reliable
    2018/10/26 13:03:14.076 18891 **Please do not post TeamViewer IDs**06592 CT SysSessionInfoManager: Session Information provided by VT [priority: 2]
    2018/10/26 13:03:14.076 18891 **Please do not post TeamViewer IDs**06592 CT! FrameBuffer: Cannot access /dev/fb0, frame buffer support unavailable
    2018/10/26 13:03:14.078 18891 **Please do not post TeamViewer IDs**06592 CT SysSessionInfoManager: own session cache set to '**Please do not post TeamViewer IDs**'
    2018/10/26 13:03:14.085 18891 **Please do not post TeamViewer IDs**06592 CT!! ResourceLoader: loaded file '/opt/teamviewer/tv_bin/resources/TVResource_fr.so' version (8346) is not matching with application version (14.0.8346), Errorcode=11
    2018/10/26 13:03:14.086 18891 **Please do not post TeamViewer IDs**06592 CT InterProcessBase:: SecureNetwork created
    2018/10/26 13:03:14.089 18891 **Please do not post TeamViewer IDs**06592 CT AutoLogin:: Login: enabled: 1
    2018/10/26 13:03:14.089 18891 **Please do not post TeamViewer IDs**06592 CT AccountLoginStateMachine::Reset
    2018/10/26 13:03:14.089 18891 **Please do not post TeamViewer IDs**85376 CT InterProcessBase:: StartTcpCommunicationInternal(): setting m_NetworkConnector to new TCP connector
    2018/10/26 13:03:14.089 18891 **Please do not post TeamViewer IDs**85376 CT Opening local TCP connection to 127.0.0.1:5939
    2018/10/26 13:03:14.089 18891 **Please do not post TeamViewer IDs**03104 CT Local TCP connection established
    2018/10/26 13:03:14.090 12231 **Please do not post TeamViewer IDs**09696 S CAcceptServer:: HandleAccept: new connection from 127.0.0.1:53420
    2018/10/26 13:03:14.131 12231 **Please do not post TeamViewer IDs**16800 S+ IpcInitConnection:: Received_Control_InitIPC: Connecting process: 18891
    2018/10/26 13:03:14.132 12231 **Please do not post TeamViewer IDs**16800 S+ RemoteSettingsAdministration: Receive signal new process [Type = 1048576] is online
    2018/10/26 13:03:14.132 12231 **Please do not post TeamViewer IDs**16800 S+ RemoteSettingsAdministration:: TriggerSynchronisationOfAllRemoteableMachineSettings ProcessType: [1048576] SessionId: [**Please do not post TeamViewer IDs**]
    2018/10/26 13:03:14.133 12231 **Please do not post TeamViewer IDs**16800 S+ RemoteSettings: MachineSettings:: SynchroniseAllRemoteableMachineSettings()
    2018/10/26 13:03:14.179 18891 **Please do not post TeamViewer IDs**10400 CT SettingsIPCReception receive a SYNCHRONISE Settings command : UserSettings
    2018/10/26 13:03:14.179 12231 **Please do not post TeamViewer IDs**95104 S+ IpcInitConnection:: Received_Control_InitIPC: Send InitIPC_Response to process: 18891
    2018/10/26 13:03:14.179 18891 **Please do not post TeamViewer IDs**95808 CT Received Control_InitIPC_Response processtype=1
    2018/10/26 13:03:14.179 18891 **Please do not post TeamViewer IDs**95808 CT Received Control_InitIPC_Response runningProcesses=1048577
    2018/10/26 13:03:14.180 18891 **Please do not post TeamViewer IDs**95808 CT Control_InitIPC_Response: all processes 1048577 completely initialized
    2018/10/26 13:03:14.180 12231 **Please do not post TeamViewer IDs**87616 S+ ConfigurationControllerImpl:: TriggerRequest(): Sending out request for session **Please do not post TeamViewer IDs** with features {9}
    2018/10/26 13:03:14.180 18891 **Please do not post TeamViewer IDs**95808 CT+ ConfigurationHub::HandleRegistrationResponse(): feature 9 registered successfully
    2018/10/26 13:03:14.180 12231 **Please do not post TeamViewer IDs**95104 S+ ConfigurationControllerImpl:: TriggerRequest(): Not ready for requests, state is 2
    2018/10/26 13:03:14.180 12231 **Please do not post TeamViewer IDs**94912 S+ ConfigurationControllerImpl:: TriggerRequest(): Not ready for requests, state is 2
    2018/10/26 13:03:14.180 18891 **Please do not post TeamViewer IDs**13536 CT+ ConfigurationHub:: HandleRegistrationResponse(): feature 5 registered successfully
    2018/10/26 13:03:14.180 18891 **Please do not post TeamViewer IDs**13536 CT+ ConfigurationHub:: HandleRegistrationResponse(): feature 6 registered successfully
    2018/10/26 13:03:14.180 12231 **Please do not post TeamViewer IDs**95104 S UpdateOnlineState alwaysOnline=0 modifiedOnline=0 otherProcess=1 restart=0
    2018/10/26 13:03:14.180 12231 **Please do not post TeamViewer IDs**95104 S+ tvnetwork:: Online: online state 1
    2018/10/26 13:03:14.223 18891 **Please do not post TeamViewer IDs**50016 CT+ ConfigurationHub:: HandleRegistrationResponse(): feature 5 registered successfully
    2018/10/26 13:03:14.223 18891 **Please do not post TeamViewer IDs**50016 CT+ ConfigurationHub:: HandleRegistrationResponse(): feature 6 registered successfully
    2018/10/26 13:03:14.223 18891 **Please do not post TeamViewer IDs**50016 CT+ ConfigurationHub:: HandleRegistrationResponse(): feature 9 registered successfully
    2018/10/26 13:03:14.223 18891 **Please do not post TeamViewer IDs**50016 CT+ SecureNetwork:: RegisterBCommandCallback(): CC: 61, RegistrationID: 6e3c1823-77e6-4513-9f47-b1b9cd04acf9
    2018/10/26 13:03:14.223 18891 **Please do not post TeamViewer IDs**50016 CT InterProcessBase:: SecureNetworkCallbackHandle created (RegistrationID: 6e3c1823-77e6-4513-9f47-b1b9cd04acf9)
    2018/10/26 13:03:14.223 18891 **Please do not post TeamViewer IDs**19392 CT Account:: UpdateState: KA = 1, active = 1
    2018/10/26 13:03:14.224 18891 **Please do not post TeamViewer IDs**06592 CT Account:: SetLoginState: new state: 2
    2018/10/26 13:03:14.224 12231 **Please do not post TeamViewer IDs**09504 S SecureNetworkIPCAdapter:: RegisterSharedBCmdCallback(): CC: 61, RegistrationID: 6e3c1823-77e6-4513-9f47-b1b9cd04acf9, DyngateID: **Please do not post TeamViewer IDs**, ProcessType: 1048576, SessionID: **Please do not post TeamViewer IDs**
    2018/10/26 13:03:14.224 18891 **Please do not post TeamViewer IDs**50016 CT!! InterProcessBase:: ProcessControlCommand Command 39 not handled, Errorcode=11
    2018/10/26 13:03:14.273 12231 **Please do not post TeamViewer IDs**31392 S+ ConfigurationControllerImpl:: ProcessConfigurationResponse(): configuration for session **Please do not post TeamViewer IDs** contains 1 features
    2018/10/26 13:03:14.273 12231 **Please do not post TeamViewer IDs**31392 S+ ConfigurationControllerImpl:: ParseReceivedConfigurations(): configuration for session **Please do not post TeamViewer IDs**, feature 9, contains 3 settings
    2018/10/26 13:03:14.273 12231 **Please do not post TeamViewer IDs**31392 S+ ConfigurationControllerImpl:: HandleConfiguration(): Ready for next request
    2018/10/26 13:03:14.273 12231 **Please do not post TeamViewer IDs**31392 S+ ConfigurationControllerImpl:: TriggerRequest(): Sending out request for session **Please do not post TeamViewer IDs** with features {5,6}
    2018/10/26 13:03:14.366 12231 **Please do not post TeamViewer IDs**02400 S+ ConfigurationControllerImpl:: ProcessConfigurationResponse(): configuration for session **Please do not post TeamViewer IDs** contains 2 features
    2018/10/26 13:03:14.366 12231 **Please do not post TeamViewer IDs**02400 S+ ConfigurationControllerImpl:: ParseReceivedConfigurations(): configuration for session **Please do not post TeamViewer IDs**, feature 5, contains 2 settings
    2018/10/26 13:03:14.367 12231 **Please do not post TeamViewer IDs**02400 S+ ConfigurationControllerImpl:: ParseReceivedConfigurations(): configuration for session **Please do not post TeamViewer IDs**, feature 6, contains 1 settings
    2018/10/26 13:03:14.367 12231 **Please do not post TeamViewer IDs**02400 S+ ConfigurationControllerImpl:: HandleConfiguration(): Ready for next request
    2018/10/26 13:03:14.367 12231 **Please do not post TeamViewer IDs**02400 S+ ConfigurationControllerImpl:: TriggerRequest(): No more requests in queue
    2018/10/26 13:03:54.062 18891 **Please do not post TeamViewer IDs**06592 CT Account:: SetLoginState: new state: 3
    2018/10/26 13:03:54.062 18891 **Please do not post TeamViewer IDs**95808 CT Account:: UpdateState: KA = 1, active = 1
    2018/10/26 13:03:54.062 18891 **Please do not post TeamViewer IDs**06592 CT Account:: SetLoginState: new state: 2
    2018/10/26 13:03:54.062 18891 **Please do not post TeamViewer IDs**95808 CT AccountLogin:: Start: Trying account authentication
    2018/10/26 13:03:54.069 12231 **Please do not post TeamViewer IDs**87616 S CSendCommandToMaster:: SendBCommandToMaster: CC=3 CT=4
    2018/10/26 13:04:24.062 18891 **Please do not post TeamViewer IDs**06592 CT Configuration: Shutdown initiated
    2018/10/26 13:04:24.063 18891 **Please do not post TeamViewer IDs**06592 CT Configuration: Wizard shut down
    2018/10/26 13:04:24.063 12231 **Please do not post TeamViewer IDs**94912 S InterProcessNetwork: Received DisconnectIPC from processID 18891 (ProcessType: 1048576 in Session **Please do not post TeamViewer IDs**) with reason 2
    2018/10/26 13:04:24.063 12231 **Please do not post TeamViewer IDs**94912 S+ ConfigurationIPCCommandHandler:: HandleProcessDisconnect(**Please do not post TeamViewer IDs**, 1048576) removing 3 registrations
    2018/10/26 13:04:24.063 18891 **Please do not post TeamViewer IDs**57312 CT CTcpProcessConnector:: HandleRead(): Socket gracefully closed (PID=12231)
    2018/10/26 13:04:24.063 18891 **Please do not post TeamViewer IDs**57312 CT CTcpProcessConnector:: CloseConnection(): PID=12231
    2018/10/26 13:04:24.063 18891 **Please do not post TeamViewer IDs**57312 CT InterProcessBase:: EventFunctionInternal(): IPC-Connection Closed
    2018/10/26 13:04:24.063 18891 **Please do not post TeamViewer IDs**57312 CT CTcpProcessConnector:: CloseConnection(): PID=12231
    2018/10/26 13:04:24.063 18891 **Please do not post TeamViewer IDs**57312 CT CTcpProcessConnector:: CloseConnection(): Shutdown socket returned error 107: Transport endpoint is not connected
    2018/10/26 13:04:24.063 12231 **Please do not post TeamViewer IDs**09504 S CTcpProcessConnector:: HandleRead(): Socket gracefully closed (PID=18891)
    2018/10/26 13:04:24.064 12231 **Please do not post TeamViewer IDs**09504 S CTcpProcessConnector:: CloseConnection(): PID=18891
    2018/10/26 13:04:24.064 12231 **Please do not post TeamViewer IDs**09504 S InterProcessNetwork:: ProcessDisconnected(): ConnectionClosed session=**Please do not post TeamViewer IDs** ptype=1048576
    2018/10/26 13:04:24.064 12231 **Please do not post TeamViewer IDs**09504 S CTcpProcessConnector:: CloseConnection(): Shutdown socket returned error 107: Transport endpoint is not connected
    2018/10/26 13:04:24.069 18891 **Please do not post TeamViewer IDs**20832 CT!! AccountLogin:: OnTimeout: no master response
    2018/10/26 13:04:24.069 18891 **Please do not post TeamViewer IDs**20832 CT! MainThreadCall:: Post: The instance is already gone.
    2018/10/26 13:04:24.069 18891 **Please do not post TeamViewer IDs**20832 CT! MainThreadCall:: Post: The instance is already gone.
    2018/10/26 13:04:24.069 18891 **Please do not post TeamViewer IDs**20832 CT! MainThreadCall:: Post: The instance is already gone.
    2018/10/26 13:04:24.070 18891 **Please do not post TeamViewer IDs**32288 CT+ FBSessionObserver: thread_interrupted
    2018/10/26 13:04:24.072 18891 **Please do not post TeamViewer IDs**06592 CT Shutting down System DBus

    If necessary, I can provide other log

     

  • exactt
    exactt Posts: 22

    My log file looks identical.

    Please fix this! I think we have to escalate this to regular support. I paid for this software and cannot login. It is totally rediculous!

  • Hi Everyone, I attempted all the provided "fixes", nothing helped. My version of the issue is I cannot login. I'm positive I have the correct email/password -- it works through the browser. I enter the password and it gets rejected.

    System is Ubuntu 18.04.1 LTS

    Relevant parts of the log is below. ID's scrubbed as requested :

    2018/11/16 11:26:39.137  7467 ID GX1   Account::UpdateState: KA = 1, active = 1
    2018/11/16 11:26:39.138 7467 ID GX1 Account::SetLoginState: new state: 2
    2018/11/16 11:26:39.138 7467 ID GX1 InterProcessBase::SecureNetworkCallbackHandle created (RegistrationID: 2ce8cc7a-dd9f-485b-be6a-d7b9b0f4281f)
    2018/11/16 11:26:39.138 7467 ID GX1 ManagerHolderStateMachine: Switching from NotReady to ReadyForLogin
    2018/11/16 11:26:39.733 7467 ID GX1 IpcRouterClock: received router time: 20181116T162639.714122
    2018/11/16 11:26:45.494 7467 ID GX1!! AppIndicatorHandler: Unhandled AppIndicator action: 0, Errorcode=11
    2018/11/16 11:26:49.248 7467 ID GX1!! AppIndicatorHandler: Unhandled AppIndicator action: 0, Errorcode=11
    2018/11/16 11:27:03.880 7467 ID GX1 Account::SetLoginState: new state: 3
    2018/11/16 11:27:03.882 7467 ID GX1 ControlCenterIPCImplementation::RegisterPacketCallback(): CC: 14, CT: 5, CallbackID: {398a660e-9b26-4298-bea9-9ddeda40156d}
    2018/11/16 11:27:03.884 7467 ID GX1 ControlCenterIPCImplementation::RegisterPacketCallback(): CC: 14, CT: 7, CallbackID: {9f17b71d-b766-46c6-a77a-1f92adfa0714}
    2018/11/16 11:27:03.885 7467 ID GX1 ControlCenterIPCImplementation::RegisterPacketCallback(): CC: 14, CT: 13, CallbackID: {c9e027ac-17f2-41b3-aec7-ffecdf9fa029}
    2018/11/16 11:27:03.886 7467 ID GX1 ControlCenterIPCImplementation::RegisterPacketCallback(): CC: 14, CT: 15, CallbackID: {5869bc99-cf38-4cfe-9bff-ebf2428d3e50}
    2018/11/16 11:27:03.887 7467 ID GX1 ControlCenterIPCImplementation::RegisterPacketCallback(): CC: 14, CT: 53, CallbackID: {8404d060-44bf-43da-b953-21232d9ca5c9}
    2018/11/16 11:27:03.887 7467 ID GX1 AccountLogin::Start: Trying account authentication
    2018/11/16 11:27:04.111 7467 ID GX1 AccountLogin::HandleChallenge: Try V2Login
    2018/11/16 11:27:04.330 7467 ID GX1!! AccountLogin::Error: Authentication failed with error 24 of category 2, Errorcode=11
    2018/11/16 11:27:04.330 7467 ID GX1 AccountStorageConnector: Invalidated
    2018/11/16 11:27:04.341 7467 ID GX1 InterProcessBase::SecureNetworkCallbackHandle created (RegistrationID: 5a19a7ab-bcb1-4e7c-b661-f1753cec1b3e)
    2018/11/16 11:27:04.341 7467 ID GX1 InterProcessBase::SecureNetworkCallbackHandle destroyed (RegistrationID: 6e4df672-e142-4dee-a86f-6bfce660d9de)
    2018/11/16 11:27:04.341 7467 ID GX1 Account::SetLoginState: new state: 2
  • chip1
    chip1 Posts: 2

    I have the same issue and the same entries in my logs as @kosnik

    I have not been able to use Teamviewer on my Ubuntu box for several months.

  • We are facing the same issue with the following versions:

    - 13.2.13582
    - 13.2.26559
    - 14.0.14470
    - 14.0.12762

    Please take a look at this!

  • I have the same problem.

    Fedora Workstation 29 (64 bit, GNOME)
    TeamViewer 14.0.14470 (64 bit)

    I can not log on. Button "Sign In" does not work.

    One note: Log on is functional only in the first use after a fresh installation. When you reboot the computer and try to log on the second time it does not work.

    Temporary solution: Purge TeamViewer including config files etc. and install it again. And again, and again, and again...

    This bug I have seen in several previous versions.

  • @DanielStmcould you please take a look at this? This hasn't been fixed since multiple versions and is a blocker for updating! Kinda annoying to have always have so many problems when updating teamviewer..

  • chip1
    chip1 Posts: 2

    I agree, TV please look at this.  It has been months since I have been able to access my Ubuntu boxes via TV.

  • Hello.

    I still have this issue (on Linux Mint 18 32 bits with now TV 14.1.3399). For a while it seemed not to happen any more, but now it's happening again.

    I don't have the login button greyed out any more, but I still cannot login (nothing happens if I press the button or Enter). Reinstalling the deb package works until computer reboot or after a while (If I leave TV on before going to bed, when I wake up, TV is disconnected and says "please check your connection" while the connection works perfectly fine for all other softwares on the computer).

    "sudo teamviewer daemon restart" also seems to work : TV restarts and is logged in automatically as it should be.

    An extract of the logs (with ID replaced by xxxxxxx) :

    [Logfiles removed]

     

     

  • elep331
    elep331 Posts: 7

    In version 14.2.2558 is still the same problem...!

  • bsimonch
    bsimonch Posts: 2

    For your information

    Same problem with one PC, running a fresh installed W10, through Wifi, both with full Teamviewer and with just TeamviewerQS.

    2019/03/21 10:56:23.537 7020 1504 G1 SecureNetworkConnection::SendCallbackHandler(): [ remoteID: 46 connection: **Please do not post TeamViewer IDs** remoteConnection: 0 ] Resetting connection due to error RCommand (Command not handled by receiver)
    2019/03/21 10:56:23.537 7020 1504 G1 RetryHandle::HandleRetry(): Trying resend to 46 failed with error SecureNetworkTransport:4, retrying (2 retries remaining) BCmd: CC=51 CT=9

    On the same PC, but through wired Ethernet, it works fine.

    On another PC, with same software (perhaps excepted wifi software), it works fine through both Wifi and Ethernet

     

     

  • elep331
    elep331 Posts: 7

    Could anyone from TeamViewer team comment on this bug? It remains in many versions without a fix.

  • elep331
    elep331 Posts: 7

    Unfortunately, version 14.2.8352 still has the same bug.

  • Same here with TV For Raspbian :

     

    [email protected]:~# teamviewer info

    TeamViewer 14.2.8352 (DEB)

     

    019/06/04 09:36:51.044 18396 **Please do not post TeamViewer IDs** CT   Logger started.
    2019/06/04 09:36:51.046 18396 **Please do not post TeamViewer IDs** CT Found 0 stack dump files ...
    2019/06/04 09:36:51.046 18396 **Please do not post TeamViewer IDs** CT Found 0 Minidump files ...
    2019/06/04 09:36:51.049 18396 **Please do not post TeamViewer IDs** CT systemd: logind service available
    2019/06/04 09:36:51.053 18396 **Please do not post TeamViewer IDs** CT systemd: New seat seat0 [path=/org/freedesktop/login1/seat/seat0, activeSession='c1', canGraphical=1, canTTY=1, canMultiSession=1]
    2019/06/04 09:36:51.057 18396 **Please do not post TeamViewer IDs** CT LogindSessionInfo: New session LogindSessionInfo [id=c4 user=root state=user active=1 reliable=1 infoId=**Please do not post TeamViewer IDs**] [path=/org/freedesktop/login1/session/c4 TTY= seat= display= vtnr=**Please do not post TeamViewer IDs** owner=[SysUser: root [uid=0, gid=0 home=/root gecos=root shell=/bin/bash]] idle=0(0) active=1 type=tty class=user state=active timestamp=**Please do not post TeamViewer IDs**138029 service=sshd defaultCG= leader=15759 audit=0 remote=1 rHost=192.168.1.12 rUser= killProc=0]
    2019/06/04 09:36:51.060 18396 **Please do not post TeamViewer IDs** CT LogindSessionInfo: New session LogindSessionInfo [id=c1 user=root state=user active=1 reliable=1 infoId=**Please do not post TeamViewer IDs**] [path=/org/freedesktop/login1/session/c1 TTY=/dev/tty1 seat=seat0 display= vtnr=1 owner=[SysUser: root [uid=0, gid=0 home=/root gecos=root shell=/bin/bash]] idle=1(**Please do not post TeamViewer IDs**209999) active=1 type=tty class=user state=active timestamp=**Please do not post TeamViewer IDs**127383 service=login defaultCG= leader=530 audit=0 remote=0 rHost= rUser= killProc=0]
    2019/06/04 09:36:51.062 18396 **Please do not post TeamViewer IDs** CT LogindSessionInfo: New session LogindSessionInfo [id=c5 user=root state=user active=1 reliable=1 infoId=**Please do not post TeamViewer IDs**] [path=/org/freedesktop/login1/session/c5 TTY= seat= display= vtnr=**Please do not post TeamViewer IDs** owner=[SysUser: root [uid=0, gid=0 home=/root gecos=root shell=/bin/bash]] idle=0(0) active=1 type=tty class=user state=active timestamp=**Please do not post TeamViewer IDs**031242 service=sshd defaultCG= leader=18343 audit=0 remote=1 rHost=192.168.1.12 rUser= killProc=0]
    2019/06/04 09:36:51.065 18396 **Please do not post TeamViewer IDs** CT SysSessionInfoManager: observing sessions from logind is marked as reliable
    2019/06/04 09:36:51.066 18396 **Please do not post TeamViewer IDs** CT SysSessionInfoManager: Session Information provided by VT [priority: 2]
    2019/06/04 09:36:51.072 18396 **Please do not post TeamViewer IDs** CT SysSessionInfoManager: own session cache set to '**Please do not post TeamViewer IDs**'
    2019/06/04 09:36:51.089 18396 **Please do not post TeamViewer IDs** CT!! ResourceLoader: loaded file '/opt/teamviewer/tv_bin/resources/TVResource_en.so' version (8352) is not matching with application version (14.2.8352), Errorcode=11
    2019/06/04 09:36:51.089 18396 **Please do not post TeamViewer IDs** CT InterProcessBase::SecureNetwork created
    2019/06/04 09:36:51.090 18396 **Please do not post TeamViewer IDs** CT InterProcessBase::StartTcpCommunicationInternal(): setting m_NetworkConnector to new TCP connector
    2019/06/04 09:36:51.091 18396 **Please do not post TeamViewer IDs** CT Opening local TCP connection to 127.0.0.1:5940
    2019/06/04 09:36:51.091 18396 **Please do not post TeamViewer IDs** CT Local TCP connection established
    2019/06/04 09:36:51.091 18304 **Please do not post TeamViewer IDs** S CAcceptServer::HandleAccept: new connection from 127.0.0.1:59240
    2019/06/04 09:36:51.195 18396 **Please do not post TeamViewer IDs** CT SettingsIPCReception receive a SYNCHRONISE Settings command : UserSettings
    2019/06/04 09:36:51.196 18396 **Please do not post TeamViewer IDs** CT Received Control_InitIPC_Response processtype=1
    2019/06/04 09:36:51.196 18396 **Please do not post TeamViewer IDs** CT Received Control_InitIPC_Response runningProcesses=1048577
    2019/06/04 09:36:51.197 18396 **Please do not post TeamViewer IDs** CT Control_InitIPC_Response: all processes 1048577 completely initialized
    2019/06/04 09:36:51.198 18304 **Please do not post TeamViewer IDs** S MultiUserSessionDesignator::LoginTSUser: sessionID=**Please do not post TeamViewer IDs** user=root
    2019/06/04 09:36:51.199 18304 **Please do not post TeamViewer IDs** S CSendCommandToMaster::SendBCommandToMaster: CC=3 CT=49
    2019/06/04 09:36:51.199 18304 **Please do not post TeamViewer IDs** S! LicenseTracker::GetLicenseOfSession() Unknown session: **Please do not post TeamViewer IDs** active session **Please do not post TeamViewer IDs**
    2019/06/04 09:36:51.199 18304 **Please do not post TeamViewer IDs** S NetworkControl::UpdateOnlineState alwaysOnline=1 delayOffline=1 otherProcess=1 restart=0
    2019/06/04 09:36:51.235 18304 **Please do not post TeamViewer IDs** S TeamViewerIDTracker::NewSessionRegistered: sessionID = **Please do not post TeamViewer IDs**, userID = **Please do not post TeamViewer IDs**
    2019/06/04 09:36:51.241 18396 **Please do not post TeamViewer IDs** CT!! InterProcessBase::ProcessControlCommand Command 39 not handled
    2019/06/04 09:36:51.242 18396 **Please do not post TeamViewer IDs** CT InterProcessBase::SecureNetworkCallbackHandle created (RegistrationID: 144b4f4b-5ed6-441f-b277-209debc8fdc3)
    2019/06/04 09:36:51.242 18396 **Please do not post TeamViewer IDs** CT Account::UpdateState: KA = 1, active = 1
    2019/06/04 09:36:51.242 18396 **Please do not post TeamViewer IDs** CT Account::SetLoginState: new state: 2
    2019/06/04 09:36:51.242 18304 **Please do not post TeamViewer IDs** S SecureNetworkIPCAdapter::RegisterSharedBCmdCallback(): CC: 86, RegistrationID: 144b4f4b-5ed6-441f-b277-209debc8fdc3, DyngateID: **Please do not post TeamViewer IDs**, ProcessType: 1048576, SessionID: **Please do not post TeamViewer IDs**















    2019/06/04 09:37:28.433 18396 **Please do not post TeamViewer IDs** CT Account::SetLoginState: new state: 3
    2019/06/04 09:37:28.434 18396 **Please do not post TeamViewer IDs** CT Account::UpdateState: KA = 1, active = 1
    2019/06/04 09:37:28.434 18396 **Please do not post TeamViewer IDs** CT Account::SetLoginState: new state: 2
    2019/06/04 09:37:28.434 18396 **Please do not post TeamViewer IDs** CT AccountLogin::Start: Trying account authentication
    2019/06/04 09:37:28.599 18304 **Please do not post TeamViewer IDs** S CSendCommandToMaster::SendBCommandToMaster: CC=3 CT=4




    2019/06/04 09:37:58.434 18396 **Please do not post TeamViewer IDs** CT Configuration: Shutdown initiated
    2019/06/04 09:37:58.435 18396 **Please do not post TeamViewer IDs** CT Configuration: Wizard shut down
    2019/06/04 09:37:58.436 18304 **Please do not post TeamViewer IDs** S InterProcessNetwork: Received DisconnectIPC from processID 18396 (ProcessType: 1048576 in Session **Please do not post TeamViewer IDs**) with reason 2
    2019/06/04 09:37:58.436 18396 **Please do not post TeamViewer IDs** CT CTcpProcessConnector::HandleRead(): Socket gracefully closed (PID=18304)
    2019/06/04 09:37:58.436 18396 **Please do not post TeamViewer IDs** CT CTcpProcessConnector::CloseConnection(): PID=18304
    2019/06/04 09:37:58.436 18396 **Please do not post TeamViewer IDs** CT InterProcessBase::EventFunctionInternal(): IPC-Connection Closed
    2019/06/04 09:37:58.437 18396 **Please do not post TeamViewer IDs** CT CTcpProcessConnector::CloseConnection(): PID=18304
    2019/06/04 09:37:58.437 18304 **Please do not post TeamViewer IDs** S CTcpProcessConnector::HandleRead(): Socket gracefully closed (PID=18396)
    2019/06/04 09:37:58.437 18396 **Please do not post TeamViewer IDs** CT CTcpProcessConnector::CloseConnection(): Shutdown socket returned error 107: Transport endpoint is not connected
    2019/06/04 09:37:58.437 18304 **Please do not post TeamViewer IDs** S CTcpProcessConnector::CloseConnection(): PID=18396
    2019/06/04 09:37:58.437 18304 **Please do not post TeamViewer IDs** S InterProcessNetwork::ProcessDisconnected(): ConnectionClosed session=**Please do not post TeamViewer IDs** ptype=1048576
    2019/06/04 09:37:58.438 18304 **Please do not post TeamViewer IDs** S CTcpProcessConnector::CloseConnection(): Shutdown socket returned error 107: Transport endpoint is not connected
    2019/06/04 09:37:58.598 18396 **Please do not post TeamViewer IDs** CT!! AccountLogin::OnTimeout: no master response, Errorcode=2
    2019/06/04 09:37:58.599 18396 **Please do not post TeamViewer IDs** CT! MainThreadCall::Post: The instance is already gone.
    2019/06/04 09:37:58.599 18396 **Please do not post TeamViewer IDs** CT! MainThreadCall::Post: The instance is already gone.
    2019/06/04 09:37:58.599 18396 **Please do not post TeamViewer IDs** CT! MainThreadCall::Post: The instance is already gone.
    2019/06/04 09:37:58.609 18396 **Please do not post TeamViewer IDs** CT Shutting down System DBus
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!