Package Details: teamviewer 15.59.3-1

Git Clone URL: https://aur.archlinux.org/teamviewer.git (read-only, click to copy)
Package Base: teamviewer
Description: All-In-One Software for Remote Support and Online Meetings
Upstream URL: http://www.teamviewer.com
Licenses: custom
Conflicts: teamviewer-beta
Provides: teamviewer
Submitter: Hilinus
Maintainer: swiftgeek (nickoe, astronautlevel)
Last Packager: swiftgeek
Votes: 1474
Popularity: 2.04
First Submitted: 2010-04-15 10:29 (UTC)
Last Updated: 2024-11-15 22:36 (UTC)

Pinned Comments

swiftgeek commented on 2023-08-01 19:17 (UTC) (edited on 2023-08-01 19:21 (UTC) by swiftgeek)

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

r7v commented on 2022-06-07 14:49 (UTC)

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

Latest Comments

« First ‹ Previous 1 .. 48 49 50 51 52 53 54 55 56 57 58 .. 127 Next › Last »

WFV commented on 2016-12-18 20:10 (UTC) (edited on 2016-12-18 21:34 (UTC) by WFV)

After re-installing 12 (after downgrade), still get mixed results - same with starting from terminal as nipsky, times out and get the proxy error message on the gui. Doing this restarts it to working, but isn't guaranteed at next reboot: # systemctl stop teamviewerd # systemctl enable teamviewerd # systemctl start teamviewerd the gui launches starting the service from systemctl and then connects EDIT: or just # systemctl restart teamviewerd works, maybe service is trying to start too soon in the boot?

nipsky commented on 2016-12-18 10:39 (UTC)

Hi, teamviewer opens no window for me when I start it, all I get in the console is: Init... CheckCPU: SSE2 support: yes XRandRWait: No value set. Using default. XRandRWait: Started by user. Checking setup... Launching TeamViewer ... Launching TeamViewer GUI ... The daemon is running of course, and also I already deleted the profile folder, didn’t help. Are there any debug options to get more out of it?

shoko commented on 2016-12-16 20:25 (UTC)

Since the upgrade to 12 teamviewerd will only work sporadically... I have to stop/start it 4-5times till it works. Same error messages as the others. I use Manjaro.

cereal.kkiller commented on 2016-12-13 11:25 (UTC)

Hi guys, has the issue reported by @keysona @Syco @M-Gregoire @blackace306 @edio regarding the connection between two Arch machines been resolved in any way?

Override commented on 2016-12-11 03:57 (UTC)

For anyone getting the "teamviewer daemon is not running!" message just type these commands into the terminal: -sudo systemctl enable teamviewerd.service <ENTER> then -systemctl start teamviewerd.service <ENTER> So far everytime I've started Teamviewer up after shuting my machine down it hasn't given me any errors yet.

WFV commented on 2016-12-10 20:14 (UTC)

Get same problem, Teamviewer won't connect and says check proxy settings. Sometimes it connects if I restart teamviewerd and reload daemons. Once connected it stays connected until next reboot. Just noting that occasionally I get same proxy message on a Windows 10pc with its equivalent rev 12. I downgraded to TV11 for now. (not wayland)

mozo commented on 2016-12-09 15:13 (UTC)

@Ham_Radio No, I'm with X11.

Angel_Caido commented on 2016-12-09 00:58 (UTC)

Same problem here. After upgrading teamviewer, I get the message "Only LAN connections are possible". I am using Xorg. The result of "loginctl show-session 1 -p Type" is: Type=x11 I will have to downgrade.

Ham_Radio commented on 2016-12-08 01:18 (UTC)

@mozo @dantopa Are you guys using wayland?

mozo commented on 2016-12-07 13:00 (UTC)

Mine doesn't connect too but nobody cares...

« First ‹ Previous 1 .. 48 49 50 51 52 53 54 55 56 57 58 .. 127 Next › Last »