TV 13.1 can not start on Debian 9.3

wuwen
wuwen Posts: 1
in Linux only

I have two vitual machines of Debian 9.3 ~ V1 and V2. I have been using TV 13.1 for a while on V1 and it worked just fine until a few days ago. I purged TV and reinstall, I upgraded it to 13.2 with no luck. I installed the same DEB to my V2 machine, it works fine at first. But after a day, similar issue happened to it as well. I don't recall what I have done to cause that.

I checked, I do have lightdm and I don't have ridiculous long directory name in my local configuration. So previous solution do not apply to me.

Here is the detail:

  1. the netstat shows that teamviewerd listening on TCP port = 5939
  2. type teamviewer from the command line, shows: 
    Init...
    CheckCPU: SSE2 support: yes
    Checking setup...
    Launching TeamViewer ...
    Launching TeamViewer GUI ...
  3. the log file at virtual machine V1 at ~/.local/share/teamviewer13/logfiles shows: 
    2018/09/02 15:40:17.084 23445 *please do not post TeamViewer IDs*90464 G   Logger started.
    2018/09/02 15:40:17.085 23445 *please do not post TeamViewer IDs*90464 G   Found 0 core dump files ...
    2018/09/02 15:40:17.087 23445 *please do not post TeamViewer IDs*90464 G   systemd: logind service available
    2018/09/02 15:40:17.089 23445 *please do not post TeamViewer IDs*90464 G   systemd: New seat seat0 [path=/org/freedesktop/login1/seat/seat0, activeSession='c2', canGraphical=1, canTTY=1, c
    anMultiSession=1]
    2018/09/02 15:40:17.090 23445 *please do not post TeamViewer IDs*90464 G   LogindSessionInfo: New session LogindSessionInfo [id=c2 user=lightdm state=greeter active=1 reliable=1 infoId=335
    3246491] [path=/org/freedesktop/login1/session/c2 TTY= seat=seat0 display=:0 vtnr=7 owner=[SysUser: lightdm [uid=112, gid=115 home=/var/lib/lightdm gecos=Light Dis
    play Manager shell=/bin/false]] idle=0(0) active=1 type=x11 class=greeter state=closing timestamp=*please do not post TeamViewer IDs*080954 service=lightdm-greeter defaultCG= leader=1240 a
    udit=0 remote=0 rHost= rUser= killProc=0]
    2018/09/02 15:40:17.092 23445 *please do not post TeamViewer IDs*90464 G   SysSessionInfoManager: observing sessions from logind is marked as reliable
    2018/09/02 15:40:17.092 23445 *please do not post TeamViewer IDs*90464 G   SysSessionInfoManager: Session Information provided by VT [priority: 2]
    2018/09/02 15:40:17.092 23445 *please do not post TeamViewer IDs*90464 G!  FrameBuffer: Cannot access /dev/fb0, frame buffer support unavailable
    2018/09/02 15:40:17.093 23445 *please do not post TeamViewer IDs*90464 G   SysSessionInfoManager: own session cache set to '*please do not post TeamViewer IDs*'
    2018/09/02 15:40:17.094 23445 *please do not post TeamViewer IDs*90464 G   Running on Qt 5.7.1
    2018/09/02 15:40:17.234 23445 *please do not post TeamViewer IDs*90464 G   Initialised XRandR extension 1.5 (base=89 error=147)
    2018/09/02 15:40:17.234 23445 *please do not post TeamViewer IDs*90464 G   MonitorInfo: [XRandR 1.2] CRTC Virtual-0 1920x1080@60Hz [0, 0, 1920, 1080] - 1
    2018/09/02 15:40:17.234 23445 *please do not post TeamViewer IDs*90464 G   MonitorInfo: [XRandR 1.2] CRTC 1 has no outputs
    2018/09/02 15:40:17.234 23445 *please do not post TeamViewer IDs*90464 G   MonitorInfo: [XRandR 1.2] CRTC 2 has no outputs
    2018/09/02 15:40:17.235 23445 *please do not post TeamViewer IDs*90464 G   MonitorInfo: [XRandR 1.2] CRTC 3 has no outputs
    2018/09/02 15:40:17.235 23445 *please do not post TeamViewer IDs*90464 G   Virtual Desktop [0, 0, 1920, 1080]
    2018/09/02 15:40:17.235 23445 *please do not post TeamViewer IDs*90464 G   MonitorInfo: [XRandR 1.2] CRTC Virtual-0 1920x1080@60Hz [0, 0, 1920, 1080] - 1
    2018/09/02 15:40:17.235 23445 *please do not post TeamViewer IDs*90464 G   MonitorInfo: [XRandR 1.2] CRTC 1 has no outputs
    2018/09/02 15:40:17.235 23445 *please do not post TeamViewer IDs*90464 G   MonitorInfo: [XRandR 1.2] CRTC 2 has no outputs
    2018/09/02 15:40:17.235 23445 *please do not post TeamViewer IDs*90464 G   MonitorInfo: [XRandR 1.2] CRTC 3 has no outputs
    2018/09/02 15:40:17.235 23445 *please do not post TeamViewer IDs*90464 G   Virtual Desktop [0, 0, 1920, 1080]
    2018/09/02 15:40:17.245 23445 *please do not post TeamViewer IDs*90464 G   Loaded language 'en', using locale 'en'
    2018/09/02 15:40:17.245 23445 *please do not post TeamViewer IDs*90464 G   InterProcessBase::SecureNetwork created
    2018/09/02 15:40:17.247 23445 *please do not post TeamViewer IDs*90464 G   AutoLogin::Login: enabled: 1
    2018/09/02 15:40:17.248 23445 *please do not post TeamViewer IDs*90464 G   WindowsSessionStateManager(0x4031910) state 0
    2018/09/02 15:40:17.248 23445 *please do not post TeamViewer IDs*90464 G!!!Own session could not be resolved, unable to startup, Errorcode=11
    2018/09/02 15:40:17.248 23445 *please do not post TeamViewer IDs*90464 G   Chat::Stop: Stopping chat
    2018/09/02 15:40:17.249 23445 *please do not post TeamViewer IDs*90464 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 9 failed with error 2, Errorcode=11
    2018/09/02 15:40:17.249 23445 *please do not post TeamViewer IDs*90464 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 5 failed with error 2, Errorcode=11
    2018/09/02 15:40:17.249 23445 *please do not post TeamViewer IDs*90464 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 6 failed with error 2, Errorcode=11
    2018/09/02 15:40:17.249 23445 *please do not post TeamViewer IDs*90464 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 10 failed with error 2, Errorcode=11
    2018/09/02 15:40:17.249 23445 *please do not post TeamViewer IDs*90464 G   interprocessbase::SecureNetwork destroyed
    2018/09/02 15:40:17.253 23445 *please do not post TeamViewer IDs*90464 G   Shutting down System DBus
  4. Another thing might or might not relevent is if I run "sudo teamviewer setup", I receive 
    TeamViewer daemon is not running, setup cannot continue. Please activate the TeamViewer daemon before invoking setup.
    eventhough the daemon is running and listening. Before this error, I did not see this message when I do the setup.
  5. in /opt/teamviewer/logfiles/TeamViewer13_Logfile.log, I see: 
    2018/09/02 15:56:26.963 23675 *please do not post TeamViewer IDs*89376 C   Logger started.
    2018/09/02 15:56:26.964 23675 *please do not post TeamViewer IDs*89376 C   Found 0 core dump files ...
    2018/09/02 15:56:26.965 23675 *please do not post TeamViewer IDs*89376 C   systemd: logind service available
    2018/09/02 15:56:26.967 23675 *please do not post TeamViewer IDs*89376 C   systemd: New seat seat0 [path=/org/freedesktop/login1/seat/seat0, activeSession='c2', canGraphical=1, canTTY=1, canMultiSession=1]
    2018/09/02 15:56:26.968 23675 *please do not post TeamViewer IDs*89376 C   LogindSessionInfo: New session LogindSessionInfo [id=c2 user=lightdm state=greeter active=1 reliable=1 infoId=*please do not post TeamViewer IDs*] [path=/org/freedesktop/login1/session/c2 TTY= seat=seat0 display=:0 vtnr=7 owner=[SysUser: lightdm [uid=112, gid=115 home=/var/lib/lightdm gecos=Light Display Manager shell=/bin/false]] idle=0(0) active=1 type=x11 class=greeter state=closing timestamp=*please do not post TeamViewer IDs*080954 service=lightdm-greeter defaultCG= leader=1240 audit=0 remote=0 rHost= rUser= killProc=0]
    2018/09/02 15:56:26.970 23675 *please do not post TeamViewer IDs*89376 C   SysSessionInfoManager: observing sessions from logind is marked as reliable
    2018/09/02 15:56:26.970 23675 *please do not post TeamViewer IDs*89376 C   SysSessionInfoManager: Session Information provided by VT [priority: 2]
    2018/09/02 15:56:26.973 23675 *please do not post TeamViewer IDs*89376 C   SysSessionInfoManager: own session cache set to '*please do not post TeamViewer IDs*'
    2018/09/02 15:56:26.984 23675 *please do not post TeamViewer IDs*89376 C   InterProcessBase::SecureNetwork created
    2018/09/02 15:56:26.990 23675 *please do not post TeamViewer IDs*89376 C   AutoLogin::Login: enabled: 1
    2018/09/02 15:56:26.990 23675 *please do not post TeamViewer IDs*61408 C   InterProcessBase::StartTcpCommunicationInternal(): setting m_NetworkConnector to new TCP connector
    2018/09/02 15:56:26.991 23675 *please do not post TeamViewer IDs*61408 C   Opening local TCP connection to 127.0.0.1:5939
    2018/09/02 15:56:26.991 23675 *please do not post TeamViewer IDs*50752 C   Local TCP connection established
    2018/09/02 15:56:26.991 22224 *please do not post TeamViewer IDs*09376 S   CAcceptServer::HandleAccept: new connection from 127.0.0.1:42510
    2018/09/02 15:56:27.036 22224 *please do not post TeamViewer IDs*31264 S!! Process IPC connection failed, session not found: type = 1048576 pid = 23675, Errorcode=11
    2018/09/02 15:56:30.991 23675 *please do not post TeamViewer IDs*58048 C!! InterProcessBase::HandleTimer: Init-IPC timed out (state: 2, send: 255, rec: 58)
    2018/09/02 15:56:30.991 23675 *please do not post TeamViewer IDs*58048 C   CTcpProcessConnector::CloseConnection(): PID=0
    2018/09/02 15:56:30.991 23675 *please do not post TeamViewer IDs*65344 C   CTcpProcessConnector::HandleRead(): Socket gracefully closed (PID=0)
    2018/09/02 15:56:30.991 23675 *please do not post TeamViewer IDs*65344 C!! CTcpProcessConnector::HandleRead(): m_EventFunction is null
    2018/09/02 15:56:30.991 22224 *please do not post TeamViewer IDs*09376 S   CTcpProcessConnector::HandleRead(): Socket gracefully closed (PID=23675)
    2018/09/02 15:56:30.991 23675 *please do not post TeamViewer IDs*65344 C   CTcpProcessConnector::CloseConnection(): PID=0
    2018/09/02 15:56:30.991 22224 *please do not post TeamViewer IDs*09376 S   CTcpProcessConnector::CloseConnection(): PID=23675
    2018/09/02 15:56:30.991 22224 *please do not post TeamViewer IDs*09376 S   CInterProcessNetwork::NewInterProcessDataAvailable(): ConnectionClosed session=*please do not post TeamViewer IDs* ptype=1048576
    2018/09/02 15:56:30.991 22224 *please do not post TeamViewer IDs*09376 S   UpdateOnlineState newOnlineValue 0
    2018/09/02 15:56:31.241 23675 *please do not post TeamViewer IDs*65344 C!  InterProcessBase::HandleRetryTimer(): Retrying TCP communication (failed to connect to service)
    2018/09/02 15:56:31.242 23675 *please do not post TeamViewer IDs*65344 C   InterProcessBase::StartTcpCommunicationInternal(): setting m_NetworkConnector to new TCP connector
    2018/09/02 15:56:31.242 23675 *please do not post TeamViewer IDs*65344 C   Opening local TCP connection to 127.0.0.1:5939
    2018/09/02 15:56:31.242 23675 *please do not post TeamViewer IDs*50752 C   Local TCP connection established
    2018/09/02 15:56:31.242 22224 *please do not post TeamViewer IDs*09376 S   CAcceptServer::HandleAccept: new connection from 127.0.0.1:42512
    2018/09/02 15:56:31.288 22224 *please do not post TeamViewer IDs*09376 S!! Process IPC connection failed, session not found: type = 1048576 pid = 23675, Errorcode=11
    2018/09/02 15:56:39.242 23675 *please do not post TeamViewer IDs*65344 C!! InterProcessBase::HandleTimer: Init-IPC timed out (state: 2, send: 255, rec: 58), Errorcode=115
    2018/09/02 15:56:39.242 23675 *please do not post TeamViewer IDs*65344 C   CTcpProcessConnector::CloseConnection(): PID=0
    2018/09/02 15:56:39.242 23675 *please do not post TeamViewer IDs*65344 C   CTcpProcessConnector::HandleRead(): Socket gracefully closed (PID=0)
    2018/09/02 15:56:39.242 23675 *please do not post TeamViewer IDs*65344 C!! CTcpProcessConnector::HandleRead(): m_EventFunction is null
    2018/09/02 15:56:39.242 23675 *please do not post TeamViewer IDs*65344 C   CTcpProcessConnector::CloseConnection(): PID=0
    2018/09/02 15:56:39.242 22224 *please do not post TeamViewer IDs*16672 S   CTcpProcessConnector::HandleRead(): Socket gracefully closed (PID=23675)
    2018/09/02 15:56:39.242 22224 *please do not post TeamViewer IDs*16672 S   CTcpProcessConnector::CloseConnection(): PID=23675
    2018/09/02 15:56:39.242 22224 *please do not post TeamViewer IDs*16672 S   CInterProcessNetwork::NewInterProcessDataAvailable(): ConnectionClosed session=*please do not post TeamViewer IDs* ptype=1048576
    2018/09/02 15:56:39.242 22224 *please do not post TeamViewer IDs*16672 S   UpdateOnlineState newOnlineValue 0
    2018/09/02 15:56:39.492 23675 *please do not post TeamViewer IDs*50752 C!  InterProcessBase::HandleRetryTimer(): Retrying TCP communication (failed to connect to service)
    2018/09/02 15:56:39.492 23675 *please do not post TeamViewer IDs*50752 C   InterProcessBase::StartTcpCommunicationInternal(): setting m_NetworkConnector to new TCP connector
    2018/09/02 15:56:39.493 23675 *please do not post TeamViewer IDs*50752 C   Opening local TCP connection to 127.0.0.1:5939
    2018/09/02 15:56:39.493 23675 *please do not post TeamViewer IDs*58048 C   Local TCP connection established
    2018/09/02 15:56:39.493 22224 *please do not post TeamViewer IDs*16672 S   CAcceptServer::HandleAccept: new connection from 127.0.0.1:42514
    2018/09/02 15:56:39.536 22224 *please do not post TeamViewer IDs*16672 S!! Process IPC connection failed, session not found: type = 1048576 pid = 23675, Errorcode=11
    2018/09/02 15:56:42.083 23675 *please do not post TeamViewer IDs*89376 C   Configuration: Shutdown initiated
    2018/09/02 15:56:42.083 23675 *please do not post TeamViewer IDs*89376 C!  Configuration: Wizard did not shut down in time
    2018/09/02 15:56:42.083 23675 *please do not post TeamViewer IDs*89376 C!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 9 failed with error 2, Errorcode=11
    2018/09/02 15:56:42.083 23675 *please do not post TeamViewer IDs*89376 C!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 5 failed with error 2, Errorcode=11
    2018/09/02 15:56:42.083 23675 *please do not post TeamViewer IDs*89376 C!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 6 failed with error 2, Errorcode=11
    2018/09/02 15:56:42.083 23675 *please do not post TeamViewer IDs*89376 C   InterProcessBase::StopCommunication(): resetting m_NetworkConnector
    2018/09/02 15:56:42.084 23675 *please do not post TeamViewer IDs*72640 C   CTcpProcessConnector::CloseConnection(): PID=0
    2018/09/02 15:56:42.084 23675 *please do not post TeamViewer IDs*89376 C   interprocessbase::SecureNetwork destroyed
    2018/09/02 15:56:42.084 23675 *please do not post TeamViewer IDs*50752 C   CTcpProcessConnector::HandleRead(): Socket gracefully closed (PID=0)
    2018/09/02 15:56:42.084 23675 *please do not post TeamViewer IDs*50752 C!! CTcpProcessConnector::HandleRead(): m_EventFunction is null
    2018/09/02 15:56:42.084 22224 *please do not post TeamViewer IDs*31264 S   CTcpProcessConnector::HandleRead(): Socket gracefully closed (PID=23675)
    2018/09/02 15:56:42.084 23675 *please do not post TeamViewer IDs*50752 C   CTcpProcessConnector::CloseConnection(): PID=0
    2018/09/02 15:56:42.084 22224 *please do not post TeamViewer IDs*31264 S   CTcpProcessConnector::CloseConnection(): PID=23675
    2018/09/02 15:56:42.084 22224 *please do not post TeamViewer IDs*31264 S   CInterProcessNetwork::NewInterProcessDataAvailable(): ConnectionClosed session=*please do not post TeamViewer IDs* ptype=1048576
    2018/09/02 15:56:42.084 22224 *please do not post TeamViewer IDs*31264 S   UpdateOnlineState newOnlineValue 0
    2018/09/02 15:56:42.086 23675 *please do not post TeamViewer IDs*89376 C   Shutting down System DBus
    2018/09/02 15:56:42.087 23675 *please do not post TeamViewer IDs*89376 C   InterProcessConfigurationHub::SendToConfigurationHandler(): IPC not available, could not send command: CC=1 CT=110
    2018/09/02 15:56:42.087 23675 *please do not post TeamViewer IDs*89376 C   InterProcessConfigurationHub::SendToConfigurationHandler(): IPC not available, could not send command: CC=1 CT=110
    2018/09/02 15:56:42.087 23675 *please do not post TeamViewer IDs*89376 C   InterProcessConfigurationHub::SendToConfigurationHandler(): IPC not available, could not send command: CC=1 CT=110
  6. By the way, on machine V2 logfile, I don't see that "Can not access /dev/fd0" error message in its log. Since, TV can not start on V2 as well, I guess that warning does not really matter.

Any help is really appreciate!

Tagged:
Trustpilot

Categories

This Week's Leaders