Unable To Run TeamViewer 13 Under CentOS 7 (amd64)

Home » CentOS » Unable To Run TeamViewer 13 Under CentOS 7 (amd64)
CentOS 16 Comments

Hi,

I am writing a book about Unix (Linux / FreeBSD) and my book needs documentation for TeamViewer13 running under CentOS 7 (64-bit).

Unfortunately, running TeamViewer does not get me a GUI — the install went smoothly and teamviewerd daemon is running.

This happens only under CentOS. Under Manjaro, the same tarball
(teamviewer_13.0.5494_amd64.tar.xz) gets me a nice TeamViewer window. But I need documentation for CentOS.

I have tried reinstalling via rpm (teamviewer_13.0.5693.x86_64.rpm), but that does not improve things. With the teamviewer command, I just get
“Launching TeamViewer GUI” – but nothing actually happens after that.

Can anyone please help me fix the issue ?

16 thoughts on - Unable To Run TeamViewer 13 Under CentOS 7 (amd64)

  • Hi Johnny,

    Thanks for replying.

    I seem to be having a very bad day.

    I uninstalled the old TV, and installed the version you indicated, but I
    get nothing at all:

    /home/bourne # teamviewer

    Init… CheckCPU: SSE2 support: yes Checking setup… Launching TeamViewer … Launching TeamViewer GUI …
    /home/bourne #

    I deleted ~/.config/teamviewer* and ~/.local/share/teamviewer*, but still no luck.

    Is it possible that this has something to do with CentOS 7 running as a vm (under VirtualBox) in my box ? (But then, Manjaro vm works fine).

    Tx again. Manish Jain

  • Thanks for replying.

    Yes, this is under xfce4.

    I had installed the qt5 deps myself via rpm. Since Johnny claims success, the idea I get is perhaps I should let the TV rpm pull in its own deps by itself, rather than being installed beforehand.

    Do you think it might be worth for me to recreate the vm and install Qt5
    indirectly via TV rpm ?

    This is all a bit confounding for the user, but this is the best idea I
    have.

    Thanks & Regards, Manish Jain

  • Maybe you have a customized $PS1 (or other shell) but with a shell prompt that includes ‘#’, it makes me wonder if you’re running this as the logged-into-X user or as root?

  • Hi Jonathan,

    Thanks for joining the thread.

    I am doing this as a normal user (bourne), logged in with xfce4.

    Thanks & Regards, Manish Jain

  • I recreated the vm – this time letting the TV rpm pull in all its deps. But the situation remains the same – No TV window from teamviewer.

    Thanks & Regards, Manish Jain

  • Hi Mark,

    Thanks for replying.

    There is no ~/.xsession-errors, and the only X log /var/log/Xorg.0.log shows no errors whatever.

    I can – if it helps – post the output of ‘strace teamviewer’ – but it would be huge.

    Thanks & Regards, Manish Jain

  • Hi Tim,

    Thanks for joining in.

    I get “access control disabled : clients can connect from any host”.

    I used a minimal iso for creating the vm. Would it help if I use a full iso ? Sounds dumb, but I can do anything to get TV working : – )

    Thanks & Regards, Manish Jain

  • På Tue, 19 Dec 2017 21:10:32 +0000
    Manish Jain
    skrev:

    I just tried with CentOS i Vbox. Updated CentOS first, and then installed TV from the link mentioned earlier. It gave me a GUI
    without any problems. This is a KDE install of CentOS 7.

    Allan.

  • Hi Allan,

    Thanks for joining in.

    I always do ‘yum check-update; yum update’ upon creating a CentOS vm. So I should be okay on the system update front.

    I have a lot of strange errors in TeamViewer’s own log, pasted at the bottom.

    Thanks & Regards, Manish Jain

    WindowsSessionStateManager(0x3640630) state 0
    2017/12/19 12:20:06.799 1370 140257674509632 G!!!Own session could not be resolved, unable to startup, Errorcode=11
    2017/12/19 12:20:06.799 1370 140257674509632 G!! ConfigurationHub::
    HandleRegistrationResponse(): registering for feature 5
    failed with error 2, Errorcode=11
    2017/12/19 12:20:06.799 1370 140257674509632 G!! ConfigurationHub::
    HandleRegistrationResponse(): registering for feature 6
    failed with error 2, Errorcode=11
    2017/12/19 12:20:06.799 1370 140257674509632 G!! ConfigurationHub::
    HandleRegistrationResponse(): registering for feature 9
    failed with error 2, Errorcode=11
    2017/12/19 12:20:06.799 1370 140257674509632 G!!
    WorkingProxy::Listener:: WorkingProxyResultHandler failed: 2, Errorcode=11
    2017/12/19 12:20:06.799 1370 140257674509632 G!
    WorkingProxy::Listener:: WorkingProxyResultHandler: setting default value ProxyType::Undefined
    2017/12/19 12:20:06.800 1370 140257674509632 G!!
    WorkingProxy::Listener:: WorkingProxyResultHandler failed: 2, Errorcode=11
    2017/12/19 12:20:06.800 1370 140257674509632 G!
    WorkingProxy::Listener:: WorkingProxyResultHandler: setting default value ProxyType::Undefined
    2017/12/19 12:20:06.800 1370 140257674509632 G!! ConfigurationHub::
    HandleRegistrationResponse(): registering for feature 10
    failed with error 2, Errorcode=11
    2017/12/19 12:20:06.800 1370 140257674509632 G
    interprocessbase::SecureNetwork destroyed
    2017/12/19 12:20:06.805 1370 140257674509632 G Shutting down System DBus

  • Is there a reason why you picked a non standard graphical system for CentOS?

    since this seems to use qt5 .. I would try installing KDE (KDE is on my laptop .. but I use gnome and was logged in via gnome when it worked).

    There is likely something that is part of GDM / Gnome / KDE that the package needs which is not installed in xfce. That would be my bet.

  • That is my guess too as of now. I set up a minimal system because I like to build up my system using nuts-and-bolts.

    Since that did not work well, I have flagged off the DVD download, and shall use KDE this time around. If K does not salvage the situation, I
    will post a new message to the forum.

    Thanks & Regards, Manish Jain

  • I have TV running now. I suppose there is something which does not get installed with minimal iso -> xfce, but gets pulled in with DVD iso -> kde.

    Thanks all for the help provided.

    Thanks & Regards, Manish Jain

LEAVE A COMMENT