Arch Linux User Repository

As mentioned in @seyn6gk's comment

Without changing anything, since teamviewer 13 a desktop environment/login with display manager like lightdm/sddm/gdm is required.

startx users can follow workaround mentioned in @r7v s comment

Workaround for startx

Create drop-in /etc/systemd/system/getty@tty1.service.d/getty@tty1.service-drop-in.conf with

[Service]
Environment=XDG_SESSION_TYPE=x11

Source: https://community.teamviewer.com/English/discussion/95696/teamviewer-15-stopped-working-on-debian-buster#M4399

@bawrak: I tried launching teamviewer using my system's wine, but to no avail. Using the built-in, I get the exact same CLI messages as you, but mine keeps going past that point, don't why it does not for you. I suggest you ask for help here: http://teamviewerforums.com/index.php?board=2.0, unfortunately I don't really know what could go wrong.

Unfortunately no change after rm -r ~/.config/teamviewer8 I do get a small popup for maybe 1/2 a second saying wine is generating a new configuration, but nothing happens afterwards. CLI has same text as my first post below.

Well I'm getting a lot of errors too (http://pastebin.com/p5TTiJBx) but the GUI starts and I could succesfully connect to the demo server. Could you delete ~/.config/teamviewer8 and try again? This is where teamviewer stores its wine config. Doing this got rid of the failed auto-start service errors it throws at the beginning for me.

@Alucryd: Thanks. Updated now to teamviewer8-8.0.16675-6. Did systemctl --system deamon-reload and started the teamviewerd again. Running teamviewer8 still gives me the same error as below. Is it possible I am missing something else?

@bawrak: Alright, can you try it now? It runs again on my machine.

Well that's definitely a wine issue, but not the one in your system. teamviewer8 uses its own version. It happens to me too now, I'll see what I can do.

Thanks for your work on this. It does not work for me though. teamviewerd is running. Running teamviewer8 gives me: --------------- Init... Checking setup... Launching TeamViewer... 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) err:winspool:add_printer_driver failed with 1722 for L"wineps.drv" (L"Windows NT x86") fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub! fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:process:SetProcessShutdownParameters (00000100, 00000000): partial stub. fixme:resource:GetGuiResources (0xffffffff,0): stub fixme:win:EnumDisplayDevicesW ((null),0,0x33df44,0x00000000), stub! fixme:win:EnumDisplayDevicesW (L"\\\\.\\DISPLAY1",0,0x33dbfc,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),1,0x33df44,0x00000000), stub! ------------- And then nothing. It just hangs there with no GUI. I have mono installed and the latest version of wine if that is important. Any suggestions? Thanks

Is this reproducible on other distros, such as Ubuntu or Fedora? I'm searching...

@bandroix: No problem. There is indeed a daemon that must be launched for teamviewer to work (teamviewer fails to start if it is not running). As for what it's used for, I couldn't find any useful info on the internet, and of course the file is a binary so no peeking in it. You could try to connect to a computer running only the daemon to find out whether it enables this (only have one working computer at the moment so I can't test).