Highlighted
Posted by pyperdown
Henagon

Teamviewer 14 on ubuntu 18.04 LTS with Cinnamon desktop. No GUI?

This has always been a easy to install product until now.  I cannot find anything telling in the logs so far, but the GUI will NOT launch.  Launching from the shell shows no errors.

 

$teamviewer

Init...
CheckCPU: SSE2 support: yes
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...
[jdavis@e-19-6321:/var/log/teamviewer14] $


I've installed all the qt5 stuff.  Looking for suggestions on troubleshooting further.


 

Start: 2019/04/24 10:02:52.816 (UTC-7:00)
Version: 14.2.8352
ID: 0
Loglevel: Info (100)
License: 0
Server: master5.teamviewer.com
IC: -**Please do not post TeamViewer IDs**
CPU: Intel(R) Xeon(R) CPU L5630 @ 2.13GHz
CPU extensions: y8
OS: Lx Ubuntu 18.04.2 LT (x86_64)
IP: 10.101.1.8
MID: -**Please do not post TeamViewer IDs**_359153ab9_76eea437ef2ebc4e
MIDv: 0
Proxy-Settings: Type=0 IP= User=

3 Replies
3 Replies
Posted by JeffersonDavis
Digon

Re: Teamviewer 14 on ubuntu 18.04 LTS with Cinnamon desktop. No GUI?

same here

Posted by JeffersonDavis
Digon

Re: Teamviewer 14 on ubuntu 18.04 LTS with Cinnamon desktop. No GUI?

$sudo service teamviewerd status
● teamviewerd.service - TeamViewer remote control daemon
Loaded: loaded (/etc/systemd/system/teamviewerd.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2019-05-06 13:13:19 PDT; 1min 19s ago
Process: 10048 ExecStart=/opt/teamviewer/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS)
Main PID: 10050 (teamviewerd)
Tasks: 27 (limit: 9830)
CGroup: /system.slice/teamviewerd.service
└─10050 /opt/teamviewer/tv_bin/teamviewerd -d

May 06 13:13:19 e-19-6321 systemd[1]: Starting TeamViewer remote control daemon...
May 06 13:13:19 e-19-6321 systemd[1]: teamviewerd.service: Can't open PID file /var/run/teamviewerd.pid (yet?)
May 06 13:13:19 e-19-6321 systemd[1]: Started TeamViewer remote control daemon.

Posted by JeffersonDavis
Digon

Re: Teamviewer 14 on ubuntu 18.04 LTS with Cinnamon desktop. No GUI?

Well, in my case at least, the solution was to install nscd.  Apparently it's needed to cough up session information if you're using an LDAP account, and perhaps in general as well.

Wondering if this needs to be added as a dependency?