Teamviewer 13 not working on Ubuntu/Xenial Linux

Options
typoworx
typoworx Posts: 2 ✭✭

$ teamviewer

Init...
CheckCPU: SSE2 support: yes
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...
Abgebrochen

$ tail /var/log/teamviewer13/gabriel/gui.log

Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior 2, swapInterval 1, profile  0) 

 

My system has a NVIDIA GPU which driver may be affected with this issue regarding some google research on this. Some QT Developers claim to have found a solution on this issue for another program throwing the same exception. No Idea if this helps on teamviewer:

https://forum.qt.io/topic/74998/failed-to-create-opengl-context-for-format-qsurfaceformat-in-qt-5-6-0/4

I have resolved... Add xcbintegration folder with libraries of xcbintegration on target.... Thanks a lot !!!

Comments

  • turf212
    turf212 Posts: 2 ✭✭
    Options

    Having the same issue as you with the exact same set-up.  Checking my system and I have the lib-xcb interfaces installed.  So unless they are meaning something else??

  • typoworx
    typoworx Posts: 2 ✭✭
    Options

    I've re-installed Teamviewer 12 (downgrade)... and surprisingly last update on my ubuntu xenial offered me Teamvewer 13 which was working fine! No Idea why. May be some other updates running with it fixed the problem?

  • turf212
    turf212 Posts: 2 ✭✭
    Options

    re-installed 12 and it's working (previously wasn't connecting.)  Will stay on that for the moment.

  • Battant
    Battant Posts: 5 ✭✭
    Options

     

    Hello,

    Since i I have install the ubuntu 18.04 beta vewrsion. I could'nt start teamviewver

     

    Details :

     Init...
    CheckCPU: SSE2 support: yes
    Checking setup...
    Launching TeamViewer ...
    Launchiteamviewer -version<br><br> TeamViewer 13.1.3026 (DEB)ng TeamViewer GU

    teamviewer I ...

     
    version :

    downloaded from :

    https://www.teamviewer.com/en/download/linux/

     

    teamviewer setup

    /opt/teamviewer/tv_bin/teamviewer-config: error while loading shared libraries: libdouble-conversion.so.1: cannot open shared object file: No such file or directory

     

    teamviewver log

    TeamViewer13_Logfile.log
    mparchet@mparchet-why:/var/log/teamviewer13$ tail TeamViewer13_Logfile.log
    2018/04/25 21:20:38.130 4650 139762462481344 S Updated sessions: [ X0 (450215437) CA mparchet ] [ Wc1 (1591159457) L gdm ] [ F (3510599056) L root ]
    2018/04/25 21:20:38.130 4650 139762462481344 S UpdateOnlineState newOnlineValue 0
    2018/04/25 21:20:38.131 4650 139762462481344 S Updated sessions: [ X0 (450215437) CA mparchet ] [ Wc1 (1591159457) L gdm ] [ F (3510599056) L root ]
    2018/04/25 21:20:38.131 4650 139762462481344 S UpdateOnlineState newOnlineValue 0
    2018/04/25 21:20:38.131 4650 139762462481344 S Updated sessions: [ X0 (450215437) CA mparchet ] [ Wc1 (1591159457) L gdm ] [ F (3510599056) L root ]
    2018/04/25 21:20:38.131 4650 139762462481344 S UpdateOnlineState newOnlineValue 0
    2018/04/25 21:20:38.131 4650 139762462481344 S UpdateOnlineState newOnlineValue 0
    2018/04/25 21:20:38.132 4650 139761809331968 S Using systemd-logind for suspend/resume monitoring
    2018/04/25 21:20:38.132 4650 139761809331968 S SessionLogon: session 450215437, desktop switched 0, last desktop session 4294967295
    2018/04/25 21:20:38.133 4650 139761809331968 S StartProcessesAsync: Session ready after 0s

    My configuration :

    uname -r
    4.15.0-20-generic

    ubuntu 18.04 64 bit

    lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 18.04 LTS
    Release: 18.04
    Codename: bionic

     

    Result :

     

    Teamviewer don't work

    Could you help me please to fix this issus

     

    Best regards

     Battant

  • jasjuang
    jasjuang Posts: 6 ✭✭
    Options

    @Battant I ran into the exact same problem as you do. Did you figure out a solution to this problem?

  • Battant
    Battant Posts: 5 ✭✭
    Options
    Hello, Yes, ubuntu 18.04 LTS stable is now out. I have 1. Backup file with deja-dup (duplicity) 2. downcloud ubuntu 18.04 LTS iso file and burn it on a dvd 3. restart with dvd 4. chose install ubutu 5. chose reinstall Best regards Battant
  • jasjuang
    jasjuang Posts: 6 ✭✭
    Options

    @Battant Thank you for your quick reply. I already install Ubuntu 18.04 LTS and it's up and running. But when I download teamviewer and install it with the same exact steps as you did I ran into the same exact problem. 

     

    Init...
    CheckCPU: SSE2 support: yes
    Checking setup...
    Launching TeamViewer ...
    Launching TeamViewer GUI ...

     

    And nothing shows up. I am wondering did you get teamviewer to work on your Ubuntu 18.04 machine?

  • Battant
    Battant Posts: 5 ✭✭
    Options
    Hello, You can remouve and reinstall teamviewer with therd follow steps : 1. sudo apt-get autoremove teamviewer 2. downloud the .deb file the website https://www.teamviewer.com/en/download/linux/ 3. when the file is downlouded open it with application manager and install it or in the terminal sudo dpkg .-i *.deb If it's not werk you can try this command teamviewer daemon start journalctl teamviewerd.service to save log in a file journalctl teamviewerd.service > teamviewer.log to see the log in a programme example gedit journalctl -u teamviewerd.service | less d next page u preview page to see only the n last file journalctl -u teamviewerd.service | tail -n -number What's your test's result's Best regards Battant
  • jasjuang
    jasjuang Posts: 6 ✭✭
    Options

     @Battant Yes I already tried re-installing teamviewer with `sudo dpkg -i teamviewer*deb` and that's the result I get. `journalctl teamviewerd.service` doesn't work for me. But I found a log file in ~/.local/share/teamviewer13/logfiles/TeamViewer13_Logfile.log

    ```

    2018/05/04 11:57:09.254 9040 4020068928 GX1 Logger started.
    2018/05/04 11:57:09.254 9040 4020068928 GX1 Found 5 core dump files ...
    2018/05/04 11:57:09.257 9040 4020068928 GX1 systemd: logind service available
    2018/05/04 11:57:09.258 9040 4020068928 GX1 systemd: New seat seat0 [path=/org/freedesktop/login1/seat/seat0, activeSession='3', canGraphical=1, canTTY=1, canMultiSession=1]
    2018/05/04 11:57:09.258 9040 4020068928 GX1 LogindSessionInfo: New session LogindSessionInfo [id=c2 user=gdm state=greeter active=0 reliable=1 infoId=3353246491] [path=/org/freedesktop/login1/session/c2 TTY=tty1 seat=seat0 display= vtnr=1 owner=[SysUser: gdm [uid=120, gid=125 home=/var/lib/gdm3 gecos=Gnome Display Manager shell=/bin/false]] idle=1(1525460118027493) active=0 type=x11 class=greeter state=online timestamp=1525459786398185 service=gdm-launch-environment defaultCG= leader=1196 audit=0 remote=0 rHost= rUser= killProc=0]
    2018/05/04 11:57:09.259 9040 4020068928 GX1 LogindSessionInfo: New session LogindSessionInfo [id=3 user=hypevr state=user active=1 reliable=1 infoId=1842515611] [path=/org/freedesktop/login1/session/_33 TTY=tty2 seat=seat0 display= vtnr=2 owner=[SysUser: hypevr [uid=1000, gid=1000 home=/home/hypevr gecos=hypevr,,, shell=/bin/bash]] idle=0(0) active=1 type=x11 class=user state=active timestamp=1525459817556871 service=gdm-password defaultCG= leader=1444 audit=3 remote=0 rHost= rUser= killProc=0]
    2018/05/04 11:57:09.261 9040 4020068928 GX1 SysSessionInfoManager: observing sessions from logind is marked as reliable
    2018/05/04 11:57:09.312 9040 4020068928 GX1! logind: failed to add session c2, scheduling for recheck
    2018/05/04 11:57:09.312 9040 4020068928 GX1 SysSessionInfoManager: Session Information provided by VT [priority: 2]
    2018/05/04 11:57:09.312 9040 4020068928 GX1! FrameBuffer: Cannot access /dev/fb0, frame buffer support unavailable
    2018/05/04 11:57:09.313 9040 4020068928 GX1 SysSessionInfoManager: own session cache set to '1842515611'
    2018/05/04 11:57:09.314 9040 4020068928 GX1 Running on Qt 5.9.5
    2018/05/04 11:57:09.375 9040 4020068928 GX1 Initialised XRandR extension 1.5 (base=89 error=147)
    2018/05/04 11:57:09.413 9040 4020068928 GX1 MonitorInfo: [XRandR 1.2] CRTC HDMI-0 3440x1440@50Hz [0, 0, 3440, 1440] - 1
    2018/05/04 11:57:09.413 9040 4020068928 GX1 MonitorInfo: [XRandR 1.2] CRTC 1 has no outputs
    2018/05/04 11:57:09.413 9040 4020068928 GX1 MonitorInfo: [XRandR 1.2] CRTC 2 has no outputs
    2018/05/04 11:57:09.413 9040 4020068928 GX1 MonitorInfo: [XRandR 1.2] CRTC 3 has no outputs
    2018/05/04 11:57:09.413 9040 4020068928 GX1 Virtual Desktop [0, 0, 3440, 1440]
    2018/05/04 11:57:09.450 9040 4020068928 GX1 MonitorInfo: [XRandR 1.2] CRTC HDMI-0 3440x1440@50Hz [0, 0, 3440, 1440] - 1
    2018/05/04 11:57:09.450 9040 4020068928 GX1 MonitorInfo: [XRandR 1.2] CRTC 1 has no outputs
    2018/05/04 11:57:09.450 9040 4020068928 GX1 MonitorInfo: [XRandR 1.2] CRTC 2 has no outputs
    2018/05/04 11:57:09.450 9040 4020068928 GX1 MonitorInfo: [XRandR 1.2] CRTC 3 has no outputs
    2018/05/04 11:57:09.451 9040 4020068928 GX1 Virtual Desktop [0, 0, 3440, 1440]
    2018/05/04 11:57:09.458 9040 4020068928 GX1 Loaded language 'en', using locale 'en'
    2018/05/04 11:57:09.458 9040 4020068928 GX1 InterProcessBase::SecureNetwork created
    2018/05/04 11:57:09.459 9040 4020068928 GX1 AutoLogin::Login: enabled: 1
    2018/05/04 11:57:09.459 9040 4020068928 GX1 Account::SetLoginState: new state: 1
    2018/05/04 11:57:09.459 9040 4020068928 GX1 WindowsSessionStateManager(0xb790490) state 0
    2018/05/04 11:57:09.459 9040 3802573632 GX1 InterProcessBase::StartTcpCommunicationInternal(): setting m_NetworkConnector to new TCP connector
    2018/05/04 11:57:09.459 9040 3802573632 GX1 Opening local TCP connection to 127.0.0.1:5939, tcp?
    2018/05/04 11:57:09.459 9040 3974101824 GX1 Local TCP connection established
    2018/05/04 11:57:09.555 9040 3974101824 GX1 SettingsIPCReception receive a SYNCHRONISE Settings command : UserSettings
    2018/05/04 11:57:09.555 9040 3944737600 GX1 Received Control_InitIPC_Response processtype=1
    2018/05/04 11:57:09.555 9040 3944737600 GX1 Received Control_InitIPC_Response runningProcesses=3
    2018/05/04 11:57:09.555 9040 3944737600 GX1 Control_InitIPC_Response: all processes 3 completely initialized

     

    Start: 2018/05/04 11:57:09.556 (UTC-7:00)
    Version: 13.1.3026
    ID: 0
    Loglevel: Info (100)
    License: 0
    Server: master8.teamviewer.com
    IC: -652071594
    CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
    CPU extensions: h9
    OS: Lx Ubuntu 18.04 LTS (x86_64)
    IP: 192.168.1.71
    Proxy-Settings: Type=0 IP= User=

    2018/05/04 11:57:10.356 9040 4020068928 GX1!!!Crash: Coredump '/home/hypevr/.local/share/teamviewer13/logfiles/TeamViewer_FI_13.1.3026_2018-05-04-115709.i386.core' could not been written. Error 14, Errorcode=14
    2018/05/04 11:57:10.356 9040 4020068928 GX1 Process received fatal SIGABRT

    ```

  • Menel
    Menel Posts: 9 ✭✭
    Options

    @jasjuang wrote:

    @Battant Thank you for your quick reply. I already install Ubuntu 18.04 LTS and it's up and running. But when I download teamviewer and install it with the same exact steps as you did I ran into the same exact problem. 

     

    Init...
    CheckCPU: SSE2 support: yes
    Checking setup...
    Launching TeamViewer ...
    Launching TeamViewer GUI ...

     

    And nothing shows up. I am wondering did you get teamviewer to work on your Ubuntu 18.04 machine?


    I've been running on 18.04LTS for a week, installed on the Saturday after it's launched, Teamviewer13 was up and running right away with no errors. But I'm using Intel Integrated i3-8100, so probably less issues, simple system.

  • Battant
    Battant Posts: 5 ✭✭
    Options
    Hello, Are you sure do you haven't a permission problem Could you try :in command line (ctrl + alt + t)to you can try chmod 770 /home/hypevr/.local/share/teamviewer13/logfiles Are you shure you don't have any disk problem ? disk full Before run journalctl -u, you should run teamviewer daemon start to check fsck to check disk or df -h to check disk space Are you sure you have been download 64 bit teamviewer version ? Thanks for your answers Best regards Battant
  • jasjuang
    jasjuang Posts: 6 ✭✭
    Options

    Thanks for the report. I am using a NVIDIA GPU with the latest 390.48 driver. Not sure if that complicated things.

  • jasjuang
    jasjuang Posts: 6 ✭✭
    Options

    @Battant I tried `chmod 770 /home/hypevr/.local/share/teamviewer13/logfiles` and it doesn't help. I run `df -h` and I have about 200G of free space. Yes I downloaded the 64 bit teamviewer. The teamviewer daemon wouldn't even start. 

    Are you using a NVIDIA GPU? @Menel reports that his setup works with the intel integrated GPU. I think that could be the difference.

  • Battant
    Battant Posts: 5 ✭✭
    Options
    Hello, Are you using a NVIDIA GPU? @Menel reports that his setup works with the intel integrated GPU. I think that could be the difference. You have an amd64 or another intel 64 but cpu ? I don't use the nvidia Gpu. because I have a laptop If you run ubutnu beta ? You should save package follow this link https://unix.stackexchange.com/questions/190853/backup-and-restore-list-of-installed-packages-and-apt-sources burn an dvd or make an usb pen Click install ubuntu click reinstall and restore your packages What's the result of this command. systemctl start teamviewerd.service Best regards Battant
  • jasjuang
    jasjuang Posts: 6 ✭✭
    Options
    I am using a desktop with NVIDIA GPUs. I suppose I can try to find a computer without the NVIDIA GPU to try it out, but teamviewer should make it work on NVIDIA GPU desktops. There are a lot of desktop that uses the NVIDIA GPUs. I ran `systemctl start teamviewerd.service`. It prompted me for the password. After I typed it, nothing happens.