Teamviewer GUI not starting anymore

I have version 12.0.85001-6 installed on Manjaro 17.05

For some reason the teamviewer program is not starting at all.

If I try running in a terminal, I can see the following - then nothing happens at all.

[adminuser@adminuser-pc ~]$ teamviewer

Init...
CheckCPU: SSE2 support: yes
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...
[adminuser@adminuser-pc ~]$

I've tried this on 2 machines both running the same os and latest version of teamviewer.

It used to work fine, but same problem on both machines of it not starting at all.

Any ideas how to resolve?

Thanks

 

Comments

  • btw, netstat shows following:

    [adminuser@adminuser-pc ~]$ sudo netstat -ntap | grep teamviewer
    [sudo] password for adminuser:
    tcp 0 0 127.0.0.1:5939 0.0.0.0:* LISTEN 894/teamviewerd
    tcp 0 0 127.0.0.1:5939 127.0.0.1:43831 ESTABLISHED 894/teamviewerd
    tcp 0 0 192.168.0.89:39790 37.252.232.51:5938 ESTABLISHED 894/teamviewerd
    [adminuser@adminuser-pc ~]$

    also tried solution below and the offending line doesn't exist in my client.conf file

    https://community.teamviewer.com/t5/Linux/Teamviewer-12-don-t-show-GUI-on-Ubuntu-16-04/m-p/4216#M476

     

     

  • johnk
    johnk Posts: 2

    I am running on Arch Linux and see similar behaviour.  

    After trying to launch the gui I see the following with ps -ef | grep teamv

    root 16684 1 0 16:23 ? 00:00:00 /opt/teamviewer/tv_bin/teamviewerd -d
    john 22282 20862 0 16:31 tty2 00:00:00 [TeamViewer.exe] <defunct>
    john 22395 1 0 16:31 ? 00:00:00 /opt/teamviewer/tv_bin/wine/bin/wineserver
    john 22432 22282 98 16:31 tty2 00:02:58 /opt/teamviewer//tv_bin/TVGuiSlave.64 31 1

    If I run from the command line there is no additional information

    journalctl -f shows

    Oct 13 16:31:02 WEBER-UNIX com.teamviewer.TeamViewer.desktop[22282]: Init...
    Oct 13 16:31:02 WEBER-UNIX com.teamviewer.TeamViewer.desktop[22282]: CheckCPU: SSE2 support: yes
    Oct 13 16:31:02 WEBER-UNIX com.teamviewer.TeamViewer.desktop[22282]: XRandRWait: No value set. Using default.
    Oct 13 16:31:02 WEBER-UNIX com.teamviewer.TeamViewer.desktop[22282]: XRandRWait: Started by user.
    Oct 13 16:31:02 WEBER-UNIX com.teamviewer.TeamViewer.desktop[22282]: Checking setup...
    Oct 13 16:31:02 WEBER-UNIX com.teamviewer.TeamViewer.desktop[22282]: Launching TeamViewer ...
    Oct 13 16:31:02 WEBER-UNIX com.teamviewer.TeamViewer.desktop[22282]: Launching TeamViewer GUI ...
    Oct 13 16:31:02 WEBER-UNIX gnome-shell[20862]: value "-nan" of type 'gfloat' is invalid or out of range for property 'y' of type 'gfloat'
    Oct 13 16:31:02 WEBER-UNIX gnome-shell[20862]: value "-nan" of type 'gfloat' is invalid or out of range for property 'y' of type 'gfloat'

    Any help appreciated

  • johnk
    johnk Posts: 2

    I noticed other users here https://aur.archlinux.org/packages/teamviewer/  have solved the problem.  Seems to be to do with lib32freetype2.  Downgrading the package allowed teamviewer to work for me.

  • Debian buster
    same problem the GUI didn't appear and downgrading libfreetype6 solved it. So not version  2.8.1-0.1 but 2.8-0.2 works.
    Don't forget to mark package to hold that version.

  • OpenSUSE 42.3 x 64 Plasma (KDE 5)

    libfreetype6 -> 2.6.3-4.1

    libfreetype6-32bit -> 2.6.3.-4.1

    TV GUI don't start !!! Stay "zombie" in process !!!

    HELP !!!!

  • Try to look at the log files if there is something interesting usually /var/log/teamviewer1* or :/opt/teamviewer/logfiles/

  • Something I have in gui.log: libicu52_1 and libicu52_1-32 bit installed !

    Spoiler
    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 (0x19de9f8 (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
    fixme:ntdll:NtQueryInformationToken QueryInformationToken( ..., TokenElevation, ...) semi-stub
    fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
    Unable to load library icui18n "Cannot load library icui18n: (icui18n: не вдалося відкрити файл об’єктів спільного використання: Немає такого файла або каталогу)"
    fixme:dbghelp:elf_search_auxv can't find symbol in module
    wine: Unhandled page fault on read access to 0x00000004 at address 0x7eb96a69 (thread 0009), starting debugger...
    err:seh:start_debugger Couldn't start debugger ("winedbg --auto 8 368") (2)
    Read the Wine Developers Guide on how to set up winedbg or another debugger
    fixme:nls:GetGeoInfoW -1 4 0x1bddd1c 3 0
    fixme:nls:GetGeoInfoW -1 4 0x1bddd64 3 0
    fixme:nls:GetGeoInfoW -1 4 0x1bddd64 3 0
    fixme:nls:GetGeoInfoW -1 4 0x1bddd64 3 0
    fixme:nls:GetGeoInfoW -1 4 0x1bddd64 3 0
    fixme:nls:GetGeoInfoW -1 4 0x1bddd64 3 0
    fixme:nls:GetGeoInfoW -1 4 0x1bddd64 3 0

     

    And which means:  

    icui18n: Unable to open file of shared objects: No such file or directory)
  • I found an easy way to install teamviewer, without manually changing all the library versions in the path. It's not a perfect solution, (it uses Nix, an alternative package manager), but it works:

    First, install nix:

    curl https://nixos.org/nix/install | sh

    then enable the unfree repositories

    echo "{ allowUnfree = true; }" > ~/.config/nixpkgs/config.nix

    install teamviewer

    nix-env -iA nixpkgs.teamviewer

    then, run the daemon as root

    sudo -E env "PATH=$PATH" teamviewerd

    and start the client

    teamviewer

    Please, note that you need to run these two last command each time you reboot, because the daemon will NOT be started automatically.

  • I solved this by entering the following four commands:

    sudo teamviewer daemon restart

    sudo teamviewer daemon disable

    sudo teamviewer daemon enable

    teamviewer

  • I had exactly the same issue.

    This is due to a 'gui.lock' file. Removing this lock file solved the issue. Path of this file is:

    /var/log/teamviewer14/username/gui.lock

     

  • I had this statment in my log file:

    GX1!! QML load error: qrc:/ui/EULADialog/EULADialog.qml:3:1: module "QtQuick.Controls" is not installed, Errorcode=11

    then:
    sudo apt -y install qml-module-qtquick-controls
    after this I deleted the:
    /gui.lock
    and worked.
  • I was starting kde plasma using startx from the commandline. Enablind sddm as login manager solved the problem for me.

    Maybe this will help someone else.

  • palacs
    palacs Posts: 1

    Issue still present in 2020 on Debian 9.10 (stretch), Debian 10.4 (buster), Ubuntu 18.04.4 (bionic) and Arch Linux. It's very disappointing that I couldn't find a recent Linux distribution where I could run TeamViewer. So guess what I can do. I have to start VirtualBox with bloated Windows 10 to get TeamViewer working. I would start a much lighter and faster Windows XP VirtualBox but you've removed XP support regardless of many customers still use XP on remotely accessed legacy systems (mostly insdustrial applications) where it can't be replaced.

    Why are you expecting people to buy TeamViewer in the first place if you can't provide proper support for it at all? Linux users are struggling with TeamViewer for at least 3 years, still you don't seem to do anything about it.

    If you're not compatible with recent versions of libfreetype, then do something about it. Refactor your code or ship your own freetype (LGPL allows that).

    If you're not willing to fix TeamViewer on Linux then just don't state that TeamViewer supports Linux and don't offer download of the Linux version. Because right now TeamViewer simply doesn't work on Linux.

  • nuhcan
    nuhcan Posts: 1

    Excellent message. I full support your comment...

    I installed TV host on Jetson Nano Ubuntu 18. 

    It worked very good at the first. bu I restart the system, It doesn't worked anymore...

    Init...

    Check CPU: arm7l | aarch64

    Checking setup...

    Launching TeamViewer...

    Launching Teamviewer GUI...

    Aborted (core dumped) 

    TV CPU Problem.jpg