Package Details: teamviewer 15.53.6-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: 1477
Popularity: 2.43
First Submitted: 2010-04-15 10:29 (UTC)
Last Updated: 2024-04-26 06:14 (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 2 3 4 5 6 7 8 9 10 11 12 .. 127 Next › Last »

adrian5 commented on 2021-06-15 14:04 (UTC)

Small detail, but the teamviewer.desktop file points its Icon to "teamviewer.png" which doesn't exist by name. I thought to just symlink to the desktop file, but maybe it's meant to be copied and the icon size selected according to personal use case?

ArthurBorsboom commented on 2021-05-24 16:56 (UTC)

teamviewerd.service

/usr/lib/systemd/system/teamviewerd.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/teamviewerd.pid → /run/teamviewerd.pid; please update the unit file accordingly.

Needs to go upstream ?

bittin commented on 2021-05-03 11:25 (UTC)

Updated Teamviewer PKGBUILD: https://pastebin.com/xNNEzEHT

flo.lm commented on 2021-05-03 11:14 (UTC)

Also having the segfault after a few seconds.

Version 15.9.5 seems to work fine, as reported in other comments.

I used the tar from TeramViewer Host (available from them at https://download.teamviewer.com/download/linux/version_15x/teamviewer-host_15.9.5_amd64.tar.xz ).

The non-Host version 15.9.5 is also available there

scarecrow commented on 2021-04-30 19:43 (UTC) (edited on 2021-04-30 20:51 (UTC) by scarecrow)

I can confirm the segfault dakota is mentioning. Running kernel 5.12 and LightDM with nvidia binary driver. I upgraded to the last version (15.17.6) and it still segfaults. 15.9.5 works without issues.

dakotta commented on 2021-04-25 16:37 (UTC)

@abyss02 - I was afraid you would say that.

I'm running x11, with an SDDM display manager, an xinitrc session, and the nouveau video driver with early KMS start.

Additionally, the HP machine uses xorg-xrandr for multihead.

I'll be back onsite this week, so I can check the pacman log to see what exactly was updated. There may be some clues there.

Unless you read the stack trace? Is there anything there that suggests a direction to pursue?

I created a thread in the forum to discuss this: https://bbs.archlinux.org/viewtopic.php?id=265752 if you'd rather discuss there.

Cheers,

<deleted-account> commented on 2021-04-24 08:26 (UTC)

@dakotta: not here, teamviewer is very stable, cannnot reproduce your issue. are you running x11 or wayland?

dakotta commented on 2021-04-23 20:38 (UTC)

version 15.16.8 segfaults within 10 seconds of receiving incoming connections. [Outgoing connections seem to work okay.]

I have tested this on 2 different machines running 5.11.16-arch1-1 (once on a VMware virtual machine, once on an HP server)

http://ix.io/31hf

<deleted-account> commented on 2021-03-25 22:51 (UTC)

There is a new version available - 15.16.8-1. I already updated your PKGBUILD locally and built the new package. I would like to support you to have this package updated in future. How to achieve that?

callmejoe commented on 2021-02-22 03:56 (UTC) (edited on 2021-02-22 04:01 (UTC) by callmejoe)

@leanhtai01 that used to happen to me (and many others) on earlier versions of ver 15. but seemed to be fixed with ver 15.13. at least for me.