Highlighted
Posted by aBgoz
Digon

Teamviewer 12.0.85 no start on Kali Linux 2017.2

Hi,

I am installing  Teamviewer 12.0.85 on Kali Linux (2017-10-16) with Debian 4.13.4, but not start, you do not see any errors during the installation.

one of the  processes is "defunct", I dont know if this has something to do

5394 pts/2    00:00:00 TeamViewer.exe <defunct>

This is where is lock

Init...
CheckCPU: SSE2 support: yes
XRandRWait: No value set. Using default.
XRandRWait: Started by user.
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...

I tried to install of several it in ways but the result is always the same, can anyboday help me?

 

Thanks and sorry for my English!!

8 Replies
Posted by Chiron
Hexagon

Re: Teamviewer 12.0.85 no start on Kali Linux 2017.2

I had the same problem, but with TeamViewer Host 13 beta. Try fixing broken dependencies.

sudo apt-get install -f
I don't work for TeamViewer. I'm just a user.
Posted by aBgoz
Digon

Re: Teamviewer 12.0.85 no start on Kali Linux 2017.2

Hi,

Tanks for your reply, but this not is the problem, already I did, & update, upgrade, dist-upgrade, installation of libraries manually :

libc6:i386 libgcc1:i386 libasound2:i386 libfreetype6:i386 zlib1g:i386 libsm6:i386 libxdamage1:i386 libxext6:i386 libxfixes3:i386 libxrender1:i386 libxtst6:i386 libxrandr2:i386
libdbus-1-3:i386 libexpat1:i386 libfontconfig1:i386 libjpeg62:i386 libpng12-0:i386 libxinerama1:i386

 The program is running, but no open nothing, the processes also is running:

aBgoz@kali:~$ ps -ef | grep teamv
root     27131     1  0 01:56 ?        00:00:01 /opt/teamviewer/tv_bin/teamviewerd -d
aBgoz    27785 27201  0 01:57 ?        00:00:01 /opt/teamviewer/tv_bin/wine/bin/wineserver
aBgoz    28214 28020  0 02:20 pts/1    00:00:00 grep teamv

In the log install don see anything wired:

lun nov  6 01:32:47 CET 2017
Action: Installing daemon (12.0.85001) for 'systemd' ...
installing /etc/systemd/system/teamviewerd.service (/opt/teamviewer/tv_bin/script/teamviewerd.service)
Try: systemctl enable teamviewerd.service
systemctl start teamviewerd.service

This is the logFile :

Start:              2017/11/06 02:46:11.621 (UTC+1:00)
Version:            12.0.85001
ID:                 xxxxxxxxx
Loglevel:           Info (100)
License:            10000
Server:             master10.teamviewer.com
IC:                 -xxxxxxxxxx
CPU:                Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz
CPU extensions:     g9
OS:                 Lx Kali Rolling (32-bit)
IP:                 192.168.42.xxx
MID:                xxxxxxxxxxc8045bfb89c7371d1fe0d28:50465d3cc760:0d99bc4c9def4df48a26bcxxxxxxxxxx
MIDv:               1
Proxy-Settings:     Type=0 IP= User=

2017/11/06 02:46:11.622 29052 4154813056 S   NetWatchdog: Internet is now connected
2017/11/06 02:46:11.622 29052 4154813056 S   NetWatchDogLinux: initialized network manager connection
2017/11/06 02:46:11.623 29052 4154813056 S   RemoteSettingsMDRelationshipWatchDog: DEVICE ISN'T A MANAGED DEVICE
2017/11/06 02:46:11.623 29052 3982490432 S   RemoteSettingsStore: Cleanup all policies.
2017/11/06 02:46:11.623 29052 4154813056 S   RemoteSettingsStoreListener: Establish connection.
2017/11/06 02:46:11.623 29052 3982490432 S   RemoteSettingsStore::LoadLastReceivedPolicies : Storage Entry Remote_Settings_TVClientSetting_Policy empty
2017/11/06 02:46:11.623 29052 3982490432 S   RemoteSettingsMDRelationshipWatchDog: DEVICE ISN'T A MANAGED DEVICE
2017/11/06 02:46:11.623 29052 4154813056 S   Using IPC-Port 5941
2017/11/06 02:46:11.623 29052 4154813056 S   Updated sessions: [ 0  L Debian-gdm ]  [ 1 C  aBgoz ]  [ 1000000  L root ]  
2017/11/06 02:46:11.623 29052 4154813056 S   UpdateOnlineState newOnlineValue 0
2017/11/06 02:46:11.623 29052 4154813056 S   Updated sessions: [ 0  L Debian-gdm ]  [ 1 C  aBgoz ]  [ 1000000  L root ]  
2017/11/06 02:46:11.623 29052 4154813056 S   UpdateOnlineState newOnlineValue 0
2017/11/06 02:46:11.623 29052 4154813056 S   Updated sessions: [ 0  L Debian-gdm ]  [ 1 C  aBgoz ]  [ 1000000  L root ]  
2017/11/06 02:46:11.624 29052 4154813056 S   UpdateOnlineState newOnlineValue 0
2017/11/06 02:46:11.624 29052 4154813056 S   UpdateOnlineState newOnlineValue 0
2017/11/06 02:46:11.624 29052 4154813056 S   UpdateResponseLinux: success 1 updated 0 rev 0
2017/11/06 02:46:11.625 29052 4011850560 S   Using systemd-logind for suspend/resume monitoring
2017/11/06 02:46:11.625 29052 4011850560 S   Session login for session 1
2017/11/06 02:46:11.625 29052 4011850560 S   CTerminalServer::RepeatedlyCheckForUserLogin() Don't start GUI for session 1
2017/11/06 02:46:17.837 29052 4119661376 S   CAcceptServer::HandleAccept: new connection from 127.0.0.1:36243
2017/11/06 02:46:17.880 29052 4107270976 S   Updated sessions: [ 0  L Debian-gdm ]  [ 1 C  aBgoz ]  [ 1000000  L root ]  
2017/11/06 02:46:17.880 29052 4107270976 S   UpdateOnlineState newOnlineValue 1
2017/11/06 02:46:17.880 29052 4107270976 S   TerminalServer: ProcessConnected type 2 PID 29078
2017/11/06 02:46:17.881 29052 3957312320 S   TeamViewer is going online!
2017/11/06 02:46:17.881 29052 4107270976 S   SysSessionInfoManager: updating session information for session 1 from GUI
2017/11/06 02:46:17.881 29052 4094688064 S   CKeepAliveClientClient::DoReconnectInternal: doing nothing, state = 0
2017/11/06 02:46:17.881 29052 4094688064 S   Activating Router carrier
2017/11/06 02:46:17.883 29052 4107270976 S   Updated sessions: [ 0  L Debian-gdm ]  [ 1 C  aBgoz ]  [ 1000000  L root ]  
2017/11/06 02:46:17.883 29052 4107270976 S   UpdateOnlineState newOnlineValue 1
2017/11/06 02:46:17.884 29052 4022336320 S   XSession: 1 [SysSession 1 [type=1 tty=2 pseudotty=0 info=1 id=305 user=aBgoz state=user active=1 reliable=1]]
2017/11/06 02:46:17.884 29052 4022336320 S   Updated sessions: [ 0  L Debian-gdm ]  [ 1 C  aBgoz ]  [ 1000000  L root ]  
2017/11/06 02:46:17.884 29052 4022336320 S   UpdateOnlineState newOnlineValue 1
2017/11/06 02:46:17.935 29052 4084202304 S   CInterProcessNetwork::SetDyngateIDforSession() id=2506xxxxx session=1 ptype=2
2017/11/06 02:46:17.935 29052 4084202304 S   UpdateOnlineState newOnlineValue 1
2017/11/06 02:46:18.305 29052 4144839488 S   NetWatchdog: Ping successful! Port: 5938
2017/11/06 02:46:18.306 29052 4144839488 S   CKeepAliveClientClient::HandlePing(): success
2017/11/06 02:46:18.306 29052 4144839488 S   Activating Router carrier
2017/11/06 02:46:18.306 29052 4144839488 S   CProcessCommandHandlerMasterConnect[2]::CreateMasterConnect(): master10.teamviewer.com:5938, Connection 2, proxy=''
2017/11/06 02:46:18.435 29052 4136446784 S   CProcessCommandHandlerMasterConnect[2]::HandleMasterConnect(): Sending MasterCommand addonchannels=0&client=TV&f=Login&gw=1&gwlevel=431&hideonlinestatus=0&httpout=1&ic=-1508514306&id=250695273&iguid={270c2d8c-1aff-4de1-8675-a00c9c91bc9c}&language=&licensetype=10000&mid=l9be382befc8045bfb89c7371d1fe0d28:50465d3cc760:0d99bc4c9def4df48a26bcd4691eb565&midf=16&midhistory=-1508514306_33dc6392_45fd536a76aca02f|l9be382befc8045bfb89c7371d1fe0d28:50465d3cc760:0d99bc4c9def4df48a26bcd4691eb565&midv=1&noofactivekeepalive=0&os=Lx Kali Rolling&port443out=0&rhash={84f2b489-bc47-d24b-b458-987b4c2ffa46}&runtime=1&smidv=1&sro=0&supportedfeatures=669940701&tcpout=1&usednsnames=1&v=12.0.85001
2017/11/06 02:46:18.524 29052 4084202304 S   CProcessCommandHandlerMasterConnect[2]::ReceivedMasterResponse(): Received MasterCommand OK_10000_-_2__server50102.teamviewer.com:5938_33239_1_-1_0.0.0.0__185.188.32.14_185.188.32.4_0_250695273_1_0_0_0_1943797625__server22704.teamviewer.com,server22801.teamviewer.com,server23301.teamviewer.com,server19602.teamviewer.com,server18505.teamviewer.com,server50304.teamviewer.com,server23701.teamviewer.com,server18908.teamviewer.com,server50102.teamviewer.com,server10004.teamviewer.com,server50605.teamviewer.com,server22505.teamviewer.com,server19401.teamviewer.com,server50703.teamviewer.com,server22201.teamviewer.com,server22909.teamviewer.com,server21502.teamviewer.com,server18802.teamviewer.com,server20801.teamviewer.com,server24601.teamviewer.com,server50901.teamviewer.com,server23503.teamviewer.com_ef/bc0goAIcD_
2017/11/06 02:46:18.524 29052 4084202304 S!  TcpCarrierBase[2]::SendCompleteQueue(): No Connections, Type_Tcp, Dir_Outgoing, Ending 0, SendQueue 1, CurrentSendQueue 0, SendCache 0
2017/11/06 02:46:18.525 29052 4084202304 S   Updated sessions: [ 0  L Debian-gdm ]  [ 1 C  aBgoz ]  [ 1000000  L root ]  
2017/11/06 02:46:18.525 29052 4084202304 S   UpdateOnlineState newOnlineValue 1
2017/11/06 02:46:18.525 29052 4084202304 S!  CKeepAliveClient::HandleLoginUserAnswer(): KeepAliveServer server50102.teamviewer.com:5938
2017/11/06 02:46:18.525 29052 4084202304 S   Activating Router carrier
2017/11/06 02:46:18.526 29052 4084202304 S   Carrier[2]::EndCarrierInternal(): ClientID: 0 SupportsEndSession: 0, SupportsCCmd2: 0, SessionType_MasterConnect, SendQueue: 0 (4 Bytes), CurrentSendQueue: 0 (0 Bytes), SendCache: 0 (0 Bytes)
2017/11/06 02:46:18.718 29052 4153232192 S   KeepAliveSessionOutgoing::ConnectSuccessHandler(): KeepAliveConnect to server50102.teamviewer.com successful
2017/11/06 02:46:18.866 29052 4153232192 S   KeepAliveSessionOutgoing::KeepAliveChannelInitialized(): KeepAliveConnection to server50102.teamviewer.com initialized
2017/11/06 02:46:18.866 29052 4153232192 S!! KeepAliveSession::KeepAliveChannelInitialized(): KeepAlive-Connection initialized with ID 4047xxxxx (IP: 212.81.xx.xxx), SendQueue 0 (0 Bytes), SendIndex 0, AckIndex 0, RemoteSessionID 3
2017/11/06 02:46:18.866 29052 4153232192 S!  KeepAliveSession::SendCompleteQueue(): SendQueue: 0 (0 Bytes), RemoteSession 3 (ClientID 4047xxxxx), Time: 0 ms
2017/11/06 02:46:18.945 29052 4119661376 S   TVRouterClock Schedule next request in 0 seconds
2017/11/06 02:46:18.945 29052 4119661376 S   TVRouterClock Schedule next request in 0 seconds
2017/11/06 02:46:18.948 29052 4084202304 S   SecureNetworkIPCAdapter::RegisterSharedBCmdCallback(): CC: 30, RegistrationID: e43c3ebb-37e9-42f5-9979-e07a66477b61, DyngateID: 2506xxxxx, ProcessType: 2, SessionID: 1
2017/11/06 02:46:18.949 29052 4107270976 S   CSendCommandToMaster::SendBCommandToMaster: CC=3 CT=38
2017/11/06 02:46:18.950 29052 4119661376 S   CSendCommandToMaster::SendBCommandToMaster: CC=3 CT=38
2017/11/06 02:46:18.950 29052 4094688064 S   CSendCommandToMaster::SendBCommandToMaster: CC=3 CT=38
2017/11/06 02:46:18.951 29052 4128054080 S   CSendCommandToMaster::SendBCommandToMaster: CC=3 CT=38
2017/11/06 02:46:18.951 29052 4084202304 S   CSendCommandToMaster::SendBCommandToMaster: CC=3 CT=38
2017/11/06 02:46:18.952 29052 4094688064 S   CSendCommandToMaster::SendBCommandToMaster: CC=3 CT=38
2017/11/06 02:46:18.952 29052 4107270976 S   CSendCommandToMaster::SendBCommandToMaster: CC=3 CT=38
2017/11/06 02:46:19.024 29052 4094688064 S   TVRouterClock: received router time: 20171106T014618.244541
2017/11/06 02:46:19.024 29052 4094688064 S   TVRouterClock Schedule next request in 43200 seconds
2017/11/06 02:46:19.499 29052 4107270976 S   AsyncMessaging::UnregisterAtAsyncMessageProvider(): Unregister successful

connect this OK:

aBgoz@kali:~$ ping server20204.teamviewer.com
PING server20204.teamviewer.com (217.146.2.5) 56(84) bytes of data.
64 bytes from server20204.teamviewer.com (217.146.2.5): icmp_seq=1 ttl=116 time=104 ms
64 bytes from server20204.teamviewer.com (217.146.2.5): icmp_seq=2 ttl=116 time=115 ms

 

 

thanks!!!

Posted by aBgoz
Digon

Re: Teamviewer 12.0.85 no start on Kali Linux 2017.2

Hi,

This is the log.GUI, and reviewing I do not see the fault ether

fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub!
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:process:SetProcessDEPPolicy (3): stub
fixme:msg:ChangeWindowMessageFilter 233 00000001
fixme:msg:ChangeWindowMessageFilter 4a 00000001
fixme:msg:ChangeWindowMessageFilter 407 00000001
fixme:msg:ChangeWindowMessageFilter 49 00000001
fixme:ver:GetCurrentPackageId (0x19dea08 (nil)): stub
fixme:process:SetProcessShutdownParameters (00000100, 00000000): partial stub.
fixme:win:EnumDisplayDevicesW ((null),0,0x32d98c,0x00000000), stub!
fixme:win:EnumDisplayDevicesW (L"\\\\.\\DISPLAY1",0,0x32dcd4,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),1,0x32d98c,0x00000000), stub!
fixme:module:load_library unsupported flag(s) used (flags: 0x00000060)
fixme:module:load_library unsupported flag(s) used (flags: 0x00000060)
fixme:module:load_library unsupported flag(s) used (flags: 0x00000060)
fixme:module:load_library unsupported flag(s) used (flags: 0x00000060)
fixme:resource:GetGuiResources (0xffffffff,0): stub

 

thanks!!!

Posted by Chiron
Hexagon

Re: Teamviewer 12.0.85 no start on Kali Linux 2017.2


This is the logFile :


2017/11/06 02:46:11.625 29052 4011850560 S   Session login for session 1
2017/11/06 02:46:11.625 29052 4011850560 S   CTerminalServer::RepeatedlyCheckForUserLogin() Don't start GUI for session 1


Have you checked your config file? /home/<user>/.config/teamviewer/client.conf I don't know what setting would do this, but you may find something interesting.

There are also a few other solutions for similar issues.

 

Since your process is defunct, you may have a stability problem rather than settings.

"defunct", which means the process has either completed its task or has been corrupted or killed, bu...

Good luck. If you find a solution, please post it!

I don't work for TeamViewer. I'm just a user.
Posted by aBgoz
Digon

Re: Teamviewer 12.0.85 no start on Kali Linux 2017.2

Thanks for your reply Chiron, I have a question ¿why teamviewer don't create the file client.conf?

aBgoz@kali:/opt/teamviewer/config$ ls
global.conf

I have reinstalled with:

1ª option:

sudo apt-get autoremove teamviewer

sudo apt-get purge teamviewer

wget download.teamviewer.com/download/teamviewer_i386.deb

2ª option:

sudo apt-get --purge remove teamviewer

wget download.teamviewer.com/download/teamviewer_i386.deb

3ª option:

sudo rm -rf /home/*/.local/share/teamviewer* /home/*/.config/teamviewer /opt/teamviewer

wget download.teamviewer.com/download/teamviewer_i386.deb

...but always is missing the file client.conf. , ¿any idea of why this?, also I tried downloaded the file "teamviewer_12.0.85001_i386.deb", but nothing

 

Thanks for help me!!!

Posted by aBgoz
Digon

Re: Teamviewer 12.0.85 no start on Kali Linux 2017.2

Hi,

I have he the file client.config and your setting is:

TeamViewer User Settings
# It is not recommended to edit this file manually


[int32] LastCorrectorRun = 1
[strng] Meeting_UserName = "kali"

I don't have in the file the parameter [strng] FT_Start_Directories = "" , that is the "solution", ¿why does this happen? 

Can the file be created manually?

This change is named in  several sites, but I don't it is found. The problem persists

 

Thanks!!!

Posted by JBitall
Photon

Re: Teamviewer 12.0.85 no start on Kali Linux 2017.2

I am having this exact same issue and have tried many solutions has anyone got it to work? 

Posted by carrot22
Electron

Re: Teamviewer 12.0.85 no start on Kali Linux 2017.2

I found the solution to this issue here:

https://community.teamviewer.com/t5/Linux/teamviewer-12-for-linux-antergos-no-opening/m-p/15972#M644

Check out kl's answer regarding moving some libfreetype6 files to a teamviewer folder. Doing this fixed teamviewer's GUI on my Rolling Kali