Package Details: teamviewer 15.76.5-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: https://www.teamviewer.com/en/download/portal/linux/
Licenses: custom
Conflicts: teamviewer-beta
Provides: teamviewer
Submitter: Hilinus
Maintainer: swiftgeek (nickoe, astronautlevel)
Last Packager: swiftgeek
Votes: 1484
Popularity: 1.47
First Submitted: 2010-04-15 10:29 (UTC)
Last Updated: 2026-05-11 17:35 (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 .. 42 43 44 45 46 47 48 49 50 51 52 .. 129 Next › Last »

mozo commented on 2017-10-05 18:12 (UTC)

Same here: Init... CheckCPU: SSE2 support: yes XRandRWait: No value set. Using default. XRandRWait: Started by user. Checking setup... Launching TeamViewer ... Launching TeamViewer GUI ... And nothing happens...

Utini commented on 2017-10-05 14:37 (UTC)

I dont have wine installed on my system and teamviewer still doesnt start: teamviewer Init... CheckCPU: SSE2 support: yes Checking setup... Launching TeamViewer ... Launching TeamViewer GUI ...

<deleted-account> commented on 2017-10-01 21:46 (UTC)

Regarding the non start problem. In my case i was able to start teamviewer by setting WINEARCH=win32 in my profile. I haven't looked into the exact cause, but seems like the teamviewer embedded wine is conflicting with system installed wine.

severach commented on 2017-09-29 17:05 (UTC)

Teamviewer 12 is working fine in my teamviewer9 package. lib32-freetype2 2.8.1-1 is in testing. You should be running 2.8-2. wine 2.17-1, lib32-freetype2 2.8-2

figue commented on 2017-09-29 15:05 (UTC)

@irvin700 @Strit thanks. I finally have a workaround... I installed multilib/lib32-freetype2 (which is 2.8, in multilib-testing it's in 2.8.1) and install multilib/wine-staging-nine (which is 2.16 for now). Let's see if upstream fix it soon.

irvin700 commented on 2017-09-29 14:31 (UTC) (edited on 2017-09-30 01:22 (UTC) by irvin700)

Strit you fixed it!! Both the AUR and all-in-one tar versions work now. This is what what I did: [2017-09-29 10:28] [ALPM] downgraded lib32-freetype2 (2.8.1-1 -> 2.7.1-2) [2017-09-29 10:28] [ALPM] downgraded wine (2.17-1 -> 2.16-1) EDIT: I went ahead and upgraded wine to 2.18 and it seems to be working so far. lib32-freetype2 is the only version I retained at 2.7.1-2

Strit commented on 2017-09-29 14:22 (UTC)

I've heard that freetype2 2.8.1 results in teamviewer not launching. Did you guys try downgrading that one to 2.8? Wine 2.17 has the same issue.

ndandanov commented on 2017-09-29 06:57 (UTC)

irvin700, I did a similar thing to you regarding the dependencies and still no GUI. Before that everything seemed to work correctly. I do not think it is display manager related as I have a standard xfce4 installation with xfwm.

irvin700 commented on 2017-09-29 01:39 (UTC) (edited on 2017-09-29 01:40 (UTC) by irvin700)

This no longer starts up, no GUI. I tried downgrading all the dependencies but to no avail. Maybe I didn't get them all? Also, I also downloaded the all-in-one tar file from the official website, same thing! I wonder if it's display manager related, I use sddm.

ndandanov commented on 2017-09-28 14:49 (UTC)

I have the same issue as dml. I thought it would be because of an update in fontconfig and lib32-fontconfig, but rolling them back from 2.12.6-1 to 2.12.5-1 did not solve the issue. How are we about to proceed? Which logs/other information would be needed to debug the issues? Thanks!

« First ‹ Previous 1 .. 42 43 44 45 46 47 48 49 50 51 52 .. 129 Next › Last »