Teamviewer 15 stopped working on Debian Buster

jlinkels
jlinkels Posts: 4
in Linux only

I installed Teamviewer 15.7.6 on a fresh install of Debian Buster

Kernel 4.19.0-9-amd64

KDE Plasma Desktop 5

Installed 64 .deb through dpkg

It had been working without errors for 2 weeks. I restarted the machine. Then Teamviewer does not start anymore. When I start from a terminal, this is what I see:

jlinkels@donald-pc:/tmp$ teamviewer

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

No GUI appears. The daemon is running in the background:

jlinkels@donald-pc:/var/log/teamviewer15$ ps ax | grep teamv
21135 ? Sl 0:00 /opt/teamviewer/tv_bin/teamviewerd -d
22107 pts/4 S+ 0:00 grep teamv

There were no software updates, just a machine restart.

Then I uninstalled Teamviewer. Removed all files in ~/.config and ~/.local. Reinstalled. Same thing.

This is the logfile:

2020/06/25 00:21:49.697 21673 <ID> G Logger started.
2020/06/25 00:21:49.697 21673 <ID> G! Locale has been reset to C for compatibility
2020/06/25 00:21:49.700 21673 <ID> G Found 0 stack dump files ...
2020/06/25 00:21:49.700 21673 <ID> G Found 0 core dump files ...
2020/06/25 00:21:49.703 21673 <ID> G systemd: logind service available
2020/06/25 00:21:49.704 21673 <ID> G systemd: New seat seat0 [path=/org/freedesktop/login1/seat/seat0, activeSession='', canGraphical=1, canTTY=1, canMultiSession=1]
2020/06/25 00:21:49.706 21673 <ID> G SysSessionInfoManager: observing sessions from logind is marked as reliable
2020/06/25 00:21:49.706 21673 <ID> G SysSessionInfoManager: Session Information provided by VT [priority: 2]
2020/06/25 00:21:49.707 21673 <ID> G SysSessionInfoManager::SessionAdded: adding session SysSession **Please do not post TeamViewer IDs** [type=70 vt=7 tty=/dev/tty0 pseudotty=0 info=1 id=/dev/fb0 user=root state=greeter active=0 reliable=1]
2020/06/25 00:21:49.708 21673 <ID> G!! SysSessionInfoManager::GetOwnProcessSession: No session found!
2020/06/25 00:21:49.708 21673 <ID> G Running on Qt 5.11.3
2020/06/25 00:21:49.802 21673 <ID> G Initialised XRandR extension 1.5 (base=89 error=147) 
2020/06/25 00:21:50.054 21673 <ID> G MonitorInfo: [XRandR 1.2] CRTC HDMI-1 1920x1080@60Hz [2160, 0, 4320, 1215] - 1
2020/06/25 00:21:50.054 21673 <ID> G MonitorInfo: [XRandR 1.2] CRTC HDMI-2 1920x1080@60Hz [0, 0, 2160, 1215] - 1
2020/06/25 00:21:50.054 21673 <ID> G Virtual Desktop [0, 0, 4320, 1215]
2020/06/25 00:21:50.099 21673 <ID> G MonitorInfo: [XRandR 1.2] CRTC HDMI-1 1920x1080@60Hz [2160, 0, 4320, 1215] - 1
2020/06/25 00:21:50.099 21673 <ID> G MonitorInfo: [XRandR 1.2] CRTC HDMI-2 1920x1080@60Hz [0, 0, 2160, 1215] - 1
2020/06/25 00:21:50.099 21673 <ID> G Virtual Desktop [0, 0, 4320, 1215]
2020/06/25 00:21:50.107 21673 <ID> G!! SysSessionInfoManager::GetOwnProcessSession: No session found!
2020/06/25 00:21:50.115 21673 <ID> G!! ResourceLoader: loaded file '/opt/teamviewer/tv_bin/resources/TVResource_en.so' version () is not matching with application version (15.7.6)
2020/06/25 00:21:50.116 21673 <ID> G Loaded language 'en', using locale 'en'
2020/06/25 00:21:50.116 21673 <ID> G InterProcessBase::SecureNetwork created
2020/06/25 00:21:50.117 21673 <ID> G!! SysSessionInfoManager::GetOwnProcessSession: No session found!, Errorcode=11
2020/06/25 00:21:50.119 21673 <ID> G!! SysSessionInfoManager::GetOwnProcessSession: No session found!, Errorcode=11
2020/06/25 00:21:50.122 21673 <ID> G!! SysSessionInfoManager::GetOwnProcessSession: No session found!, Errorcode=11
2020/06/25 00:21:50.123 21673 <ID> G!! SysSessionInfoManager::GetOwnProcessSession: No session found!, Errorcode=11
2020/06/25 00:21:50.124 21673 <ID> G!! SysSessionInfoManager::GetOwnProcessSession: No session found!, Errorcode=11
2020/06/25 00:21:50.125 21673 <ID> G!! SysSessionInfoManager::GetOwnProcessSession: No session found!, Errorcode=11
2020/06/25 00:21:50.125 21673 <ID> G AutoLogin::Login: enabled: 1 
2020/06/25 00:21:50.125 21673 <ID> G AccountLoginStateMachine::Reset
2020/06/25 00:21:50.126 21673 <ID> G!! SysSessionInfoManager::GetOwnProcessSession: No session found!, Errorcode=11
2020/06/25 00:21:50.127 21673 <ID> G!! ApplicationLookOfflineState::ApplicationAppearanceOfflineState: state not loaded, Errorcode=11
2020/06/25 00:21:50.128 21673 <ID> G!! SysSessionInfoManager::GetOwnProcessSession: No session found!, Errorcode=11
2020/06/25 00:21:50.128 21673 <ID> G!!!Own session could not be resolved, unable to startup, Errorcode=11
2020/06/25 00:21:50.129 21673 <ID> G!! SysSessionInfoManager::GetOwnProcessSession: No session found!, Errorcode=11
2020/06/25 00:21:50.129 21673 <ID> G Chat::Stop: Stopping chat
2020/06/25 00:21:50.130 21673 <ID> G!! SysSessionInfoManager::GetOwnProcessSession: No session found!, Errorcode=11
2020/06/25 00:21:50.131 21673 <ID> G!! SysSessionInfoManager::GetOwnProcessSession: No session found!, Errorcode=11
2020/06/25 00:21:50.132 21673 <ID> G!! SysSessionInfoManager::GetOwnProcessSession: No session found!, Errorcode=11
2020/06/25 00:21:50.133 21673 <ID> G!! SysSessionInfoManager::GetOwnProcessSession: No session found!, Errorcode=11
2020/06/25 00:21:50.134 21673 <ID> G!! SysSessionInfoManager::GetOwnProcessSession: No session found!, Errorcode=11
2020/06/25 00:21:50.134 21673 <ID> G InterProcessBase::ShutdownIPC: Shutdown IPC
2020/06/25 00:21:50.134 21673 <ID> G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 9 failed with error 2, Errorcode=11
2020/06/25 00:21:50.134 21673 <ID> G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 5 failed with error 2, Errorcode=11
2020/06/25 00:21:50.134 21673 <ID> G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 6 failed with error 2, Errorcode=11
2020/06/25 00:21:50.134 21673 <ID> G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 14 failed with error 2, Errorcode=11
2020/06/25 00:21:50.134 21673 <ID> G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 10 failed with error 2, Errorcode=11
2020/06/25 00:21:50.134 21673 <ID> G interprocessbase::SecureNetwork destroyed
2020/06/25 00:21:50.137 21673 <ID> G Shutting down DBus IOHandler
Tagged:

Best Answer

Answers

  • Vatsilidis
    Vatsilidis Posts: 655 ⭐Star⭐

    Hi @jlinkels 

    Could you please try a complete uninstall of the app, the reboot and download again the app from the official website in order to make a fresh installation?

    I hope this help you.

    Best regards

  • jlinkels
    jlinkels Posts: 4

    I did that but it did not help.

    I did discover the cause though, but not the solution.

    When I log in locally, my session gets a seat assigned. I can see that with loginctl:

    jlinkels@donald-pc:~$ loginctl 
    SESSION  UID USER     SEAT  TTY
          3 1000 jlinkels seat0

    However, when I log in using NIS (what I do on my network) logind does nog assign my session a seat:

    jlinkels@donald-pc:~$ loginctl
    No sessions.

    This has implications for the use of the scanner, sound, webcam etc. Apparently as well on TeamViewer. Which is understandable as TeamViewer wants to share the screen.

    When I installed TeamViewer, I was still in local login mode, working on troubleshooting. Then I must have switched back to NIS, rebooted, and some days later I found that TeamViewer was not working.

    To make sure this is the problem, I switched back to local login and tested. TeamViewer is fine.

    So this is not a TeamViewer problem but a system problem. Which I do want to solve. For the scanner and other pluggable hardware I was able to modify udev rules and give group permissons to devices. Like it was done before Debian 10.

    Not sure if I can create such a workaround for TeamViewer as well. As I have no idea where and why TeamViewer checks for seats.

     

     

  • TomKan
    TomKan Posts: 5

    I am running a Debian 9 Server for UniFi and I just started having the exact same issue. I have been trying to decipher and fix this issue off and on for about 3 days. Can you give me any more input in to how you fixed it? I am a computer tech, but I mainly work with Windows.

  • TomKan
    TomKan Posts: 5


    I finally got mine "fixed" by downgrading to version 15.7 with sudo apt-get install teamviewer=15.7.6 -V so is this a TeamViewer issue or a systemd issue? I still recognize I am mostly clueless with Linux.

  • jlinkels
    jlinkels Posts: 4

    @TomKan Mine was an issue with systemd AND using NIS. It happens on Debian 10 and above. So if you are not using NIS or you are running Debian 9, it is unlikely causing that the seat assignment is causing your issue.

    If you open a terminal and issue the command loginctl, what do you see?

  • KennethM
    KennethM Posts: 1

    I gave the same issue I have un attended access set up to my Debian 10 pc, and when I upgrade to version 15.17. 7, I can connect for a few minutes and then it crashes it only works on version 15.15.5,


    Did someone managed to sort it out.

  • invidian
    invidian Posts: 2

    What fixed the issue for me was setting Environment=XDG_SESSION_TYPE=x11 for getty@tty1.service service, which runs agetty for autologin for me.

    TV on start tries to read this information from login1 session properties and I think it fails at this, as this env variable is no set by default by startx or anything. Maybe just running "XDG_SESSION_TYPE=x11 teamviewer" could work as well? I haven't checked though.

Trustpilot

Categories

This Week's Leaders