Teamviewer 12 don't show GUI on Ubuntu 16.04
Hi,
I have this problem, installed Teamviewer 12 in my Ubuntu 16.04 machine (I previously had TW 11 without any problem), worked for few days then suddenly stopped working. Clicking on the dash icon or launching from the terminal the GUI don't show up, this is the output of the terminal:
rocco@rocco-HP-Notebook:~$ teamviewer
Init...
CheckCPU: SSE2 support: yes
XRandRWait: No value set. Using default.
XRandRWait: Started by user.
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...
rocco@rocco-HP-Notebook:~$
The only working solution is to purge teamviewer, delete every single trace from the system and reinstall.. however it works for a couple of days and the problem comes back! I already did it several times..
This is gui.log
fixme:service:scmdatabase_autostart_services Auto-start service L"MountMgr" failed to start: 2
fixme:service:scmdatabase_autostart_services Auto-start service L"PlugPlay" failed to start: 2
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 (0x1bfea08 (nil)): stub
fixme:process:SetProcessShutdownParameters (00000100, 00000000): partial stub.
fixme:win:EnumDisplayDevicesW ((null),0,0x33d98c,0x00000000), stub!
fixme:win:EnumDisplayDevicesW (L"\\\\.\\DISPLAY1",0,0x33dcd4,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),1,0x33d98c,0x00000000), stub!
wine: Unhandled exception 0x40000015 in thread 9 at address 0x7e580023:0x00edf4ef (thread 0009), starting debugger...
err:seh:start_debugger Couldn't start debugger ("winedbg --auto 8 252") (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
And this is the log:
2017/02/28 18:39:54.198 15303 140400868026560 gX0 Logger started.
2017/02/28 18:39:54.199 15303 140400868026560 gX0 Found 0 Minidump files ...
2017/02/28 18:39:54.199 15303 140400868026560 gX0 Found 0 core dump files ...
2017/02/28 18:39:54.200 15303 140400868026560 gX0 systemd: logind service available
2017/02/28 18:39:54.201 15303 140400868026560 gX0 systemd: New seat seat0 [path=/org/freedesktop/login1/seat/seat0, activeSession='c2', canGraphical=1, canTTY=1, canMultiSession=1]
2017/02/28 18:39:54.202 15303 140400868026560 gX0 SystemdSessionInfo: New session SystemdSessionInfo [id=c2 user=rocco state=user active=1 reliable=1 infoId=0] [path=/org/freedesktop/login1/session/c2 TTY= seat=seat0 display=:0 vtnr=7 owner=[SysUser_Lin: rocco [uid=1000, gid=1000 home=/home/rocco gecos=Rocco,,, shell=/bin/bash]] idle=0(1488301767399145) active=1 type=x11 class=user state=active timestamp=1488270660563935 service=lightdm defaultCG= leader=1354 audit=0 remote=0 rHost= rUser= killProc=0]
2017/02/28 18:39:54.202 15303 140400868026560 gX0 SysSessionInfoManager: Session Information provided by systemd [priority: 0]
2017/02/28 18:39:54.202 15303 140400868026560 gX0 SysSessionInfoManager: Session Information provided by VT [priority: 2]
2017/02/28 18:39:54.202 15303 140400868026560 gX0 XSocket observer: watching /tmp/.X11-unix
2017/02/28 18:39:54.202 15303 140400868026560 gX0 XSocket observer: adding XSession: 0
2017/02/28 18:39:54.202 15303 140400868026560 gX0! FrameBuffer: Cannot access /dev/fb0, frame buffer support unavailable
2017/02/28 18:39:54.202 15303 140400868026560 gX0 SysSessionInfoManager: assigned session 0 to info provider 'systemd'
2017/02/28 18:39:54.205 15303 140400868026560 gX0 Initialised XFixes extension (base=87 error=140)
2017/02/28 18:39:54.205 15303 140400868026560 gX0 TVGuiSlave.64: Running
2017/02/28 18:39:54.206 15304 4111583168 QX0 Logger started.
2017/02/28 18:39:54.207 15304 4111583168 QX0 Found 0 Minidump files ...
2017/02/28 18:39:54.207 15304 4111583168 QX0 Found 0 core dump files ...
2017/02/28 18:39:54.208 15304 4111583168 QX0 systemd: logind service available
2017/02/28 18:39:54.209 15304 4111583168 QX0 systemd: New seat seat0 [path=/org/freedesktop/login1/seat/seat0, activeSession='c2', canGraphical=1, canTTY=1, canMultiSession=1]
2017/02/28 18:39:54.210 15304 4111583168 QX0 SystemdSessionInfo: New session SystemdSessionInfo [id=c2 user=rocco state=user active=1 reliable=1 infoId=0] [path=/org/freedesktop/login1/session/c2 TTY= seat=seat0 display=:0 vtnr=7 owner=[SysUser_Lin: rocco [uid=1000, gid=1000 home=/home/rocco gecos=Rocco,,, shell=/bin/bash]] idle=0(1488301767399145) active=1 type=x11 class=user state=active timestamp=1488270660563935 service=lightdm defaultCG= leader=1354 audit=0 remote=0 rHost= rUser= killProc=0]
2017/02/28 18:39:54.210 15304 4111583168 QX0 SysSessionInfoManager: Session Information provided by systemd [priority: 0]
2017/02/28 18:39:54.211 15304 4111583168 QX0 SysSessionInfoManager: Session Information provided by VT [priority: 2]
2017/02/28 18:39:54.211 15304 4111583168 QX0 XSocket observer: watching /tmp/.X11-unix
2017/02/28 18:39:54.211 15304 4111583168 QX0 XSocket observer: adding XSession: 0
2017/02/28 18:39:54.211 15304 4111583168 QX0! FrameBuffer: Cannot access /dev/fb0, frame buffer support unavailable
2017/02/28 18:39:54.211 15304 4111583168 QX0 SysSessionInfoManager: assigned session 0 to info provider 'systemd'
2017/02/28 18:39:54.213 15304 4111583168 QX0 TVGuiDelegate: Running
2017/02/28 18:39:54.225 15304 4048550720 QX0! TVGuiDelegate: Socket closed on master
2017/02/28 18:39:54.305 15303 140400868026560 gX0 TVGuiSlave.64: Parent terminated
2017/02/28 18:39:54.313 15304 4111583168 QX0 TVGuiDelegate: Terminated
2017/02/28 18:39:54.405 15303 140400868026560 gX0 TVGuiSlave.64: Terminated
teamviewerd service is running.
Any idea?
Thank you
Best Answer
-
I solved in this way, looking at /home/user/.config/teamviewer/client.conf the parameter [strng] FT_Start_Directories = "" was ridicolous long and I simply deleted anything between the " " as many of the directories were not even at my computer. Now Teamviewer is back without any need to reinstall!
8
Answers
-
I solved in this way, looking at /home/user/.config/teamviewer/client.conf the parameter [strng] FT_Start_Directories = "" was ridicolous long and I simply deleted anything between the " " as many of the directories were not even at my computer. Now Teamviewer is back without any need to reinstall!
8 -
Awesome!
Had the same problem, this fixed it. Thank you very much, rok! You rok
1 -
Dang, I really wish this was the problem with mine. I don't even have that setting in my client.conf. I have to restart about 5 or 6 times per day via cmd line. It's horrible.
1 -
sudo netstat -ntap | grep teamviewer
tcp 0 [IP address removed by moderator] 0.0.0.0:* LISTEN 1091/teamviewerd
tcp 0 0 [IP address removed by moderator] [IP address removed by moderator] SPOJENO 1091/teamviewerdteamviewer –daemon start
Init...
xprop: unable to open display ''
CheckCPU: SSE2 support: yes
XRandRWait: No value set. Using default.
XRandRWait: Started by user.
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ... 3 hours...4 hours...never connecter via client to client but work only via WEB SITE CONNECT from TW account..
IDK..**bleep**..
0 -
Hi,
I have some a problem, but my client.conf don't have the parameter:
[strng] FT_Start_Directories = ""
my file client,conf only contains this:
TeamViewer User Settings
# It is not recommended to edit this file manually
[int32] LastCorrectorRun = 1
[strng] Meeting_UserName = "kali"where you put the parameter changed?
Thanks!!!
0 -
i'v same problem, missing [strng] FT_Start_Directories = ""
0 -
Same here.
Adding the string to client.conf doesn't work.
This is my log file:
qrc:/ui/QuickCommon/TVWindow.qml:16: TypeError: Cannot read property 'primaryMonitorArea' of null
qrc:/ui/MainWindow/MainWindowHost.qml:193: TypeError: Cannot read property 'incomingConnectionAllowed' of null
qrc:/ui/MainWindow/MainWindowHost.qml:205: TypeError: Cannot read property 'dynamicPasswordEnabled' of null
qrc:/ui/MainWindow/MainWindowHost.qml:243: TypeError: Cannot read property 'currentId' of null
qrc:/ui/MainWindow/MainWindowHost.qml:270: TypeError: Cannot read property 'dynamicPasswordEnabled' of null
qrc:/ui/MainWindow/MainWindowHost.qml:327: TypeError: Cannot read property 'dynamicPassword' of null
qrc:/ui/QuickCommon/TVStatusIndicator.qml:1: TypeError: Cannot read property 'statusColor_Green' of null1 -
Same, any solution yet?
1 -
I am using fedora 30 and did not had the file /home/user/.config/teamviewer/client.conf however tother log files are same in the thread. Any help?
@rok wrote:I solved in this way, looking at /home/user/.config/teamviewer/client.conf the parameter [strng] FT_Start_Directories = "" was ridicolous long and I simply deleted anything between the " " as many of the directories were not even at my computer. Now Teamviewer is back without any need to reinstall!
0