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 .. 46 47 48 49 50 51 52 53 54 55 56 .. 127 Next › Last »

shieldwed commented on 2017-02-08 21:18 (UTC)

@logion i tried creating a PKGBUILD from the tar ball. see https://gist.github.com/shieldwed/de48b0c74a240eeaf91e93b7b17ceaac in this package the file "libpng12.so.0" is missing, but i think this might be ok due to the dependency to lib32-libpng12. This PKGBUILD is not quite finished since starting teamviewer from a terminal window, it is faulting with: /opt/teamviewer/tv_bin/script/tvw_exec: line 9: /opt/teamviewer/logfiles/startup.log: Permission denied Error: LockStartup: internal error 1 maybe you got an idea?

logion commented on 2017-02-08 10:20 (UTC) (edited on 2017-02-08 10:25 (UTC) by logion)

In regards to the "Not ready. Please check your connection" error in teamviewer. There is a thread on the TV forums detailing this issue (https://community.teamviewer.com/t5/TeamViewer-11/No-connection-to-TeamViewer-server/td-p/720), some conclusions are as follows: * Error shows up on wayland systems, but not an x server systems (I'm only running wayland, and also suffer from this issue under wayland; can't check with X server) * Using the unsupported systems tar ball under wayland (https://download.teamviewer.com/download/teamviewer_i386.tar.xz), solves the connection issue. I can confirm this is the case and I can remote desktop to my Wintel machine at home from my arch wayland machine at the office. * Under wayland remote users can not control the local machine, they see a black rectangle. Did not test this. As for the PKGBUILD AUR file, for X server users there does not need to be any change. For those using wayland, I would suggest trying with the unsupported system tarball instead of the deb package files. @nipsky: is the teamviewerd.service running (systemctl status teamviewerd.service)?

nipsky commented on 2017-02-08 08:26 (UTC)

Hi, teamviewer freezes on start for me before even showing any GUI, here’s the terminal output: Init... CheckCPU: SSE2 support: yes XRandRWait: No value set. Using default. XRandRWait: Started by user. Checking setup... Launching TeamViewer ... Launching TeamViewer GUI ... Am I the only one with this problem?

swiftgeek commented on 2017-02-07 00:46 (UTC)

@otrazhenije no one should try it, at most magically i386 build works better for you (x86_64 works very reliable here FYI) Don't give ideas for bypassing package manager on AUR -.-

otrazhenije commented on 2017-02-06 09:38 (UTC) (edited on 2017-02-06 12:58 (UTC) by otrazhenije)

Faced the same problem Solved with: 1. Download https://download.teamviewer.com/download/teamviewer_i386.tar.xz 2. Extract 3. rsync to /opt/teamviewer, overwrite existing files You should try

cubethethird commented on 2017-02-03 01:15 (UTC) (edited on 2017-02-06 05:20 (UTC) by cubethethird)

Link to relevant support thread: https://community.teamviewer.com/t5/TeamViewer-12/Not-ready-Please-check-your-connection-after-upgrade-to-v12/m-p/2177 Users with this issue describe 3 possible causes/solutions: - Incorrect DNS lookups -> change DNS server/manual entries - Error in service startup -> restart the service - Usage of IPv6 -> disable IPv6 in router/modem settings Sadly none of these solutions work for me, including the Remmina workaround recommended.

summonholmes commented on 2017-01-28 00:03 (UTC)

Regarding the connection errors of the previous comments, I've found a temporary workaround. Install Remmina, then install the TeamViewer plugin (AUR). If teamviewerd is active, Remmina will execute TeamViewer in a connected state. Hope this helps.

joanmanel commented on 2017-01-26 13:37 (UTC)

Hey purboo, what exactly did you do, because I executed that command, then open teamviewer, and I get the same error.

purboo commented on 2017-01-22 08:10 (UTC)

I got this error: "Not Ready. Please check your connection. " And it works after I execute this command: $ sudo systemctl restart teamviewerd.service I am very curious about what causes the no-connection problem.

wangyue9014 commented on 2017-01-17 08:57 (UTC)

can't connect to server. it say: Not ready. Please check your connection.

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