i can confirm with @cubethethird and @disconnect3d that if you are getting "not ready", just logout of gnome and login again using setting "Gnome on X.org".
Search Criteria
Package Details: teamviewer 15.59.3-1
Package Actions
| 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) |
Dependencies (5)
Required by (3)
Sources (4)
- https://dl.teamviewer.com/download/linux/version_15x/teamviewer_15.59.3_amd64.deb
- https://dl.teamviewer.com/download/linux/version_15x/teamviewer_15.59.3_arm64.deb
- https://dl.teamviewer.com/download/linux/version_15x/teamviewer_15.59.3_armhf.deb
- https://dl.teamviewer.com/download/linux/version_15x/teamviewer_15.59.3_i386.deb
num1champ commented on 2017-03-15 00:42 (UTC) (edited on 2017-03-15 00:43 (UTC) by num1champ)
disconnect3d commented on 2017-03-09 09:13 (UTC)
Same here as @cubethethird. Simply logout and login into "Gnome on X.org" fixed the issue with "not ready" connection.
I have also tried other screen sharing tools before (e.g. chrome desktop share) - when someone connected to me the only thing they saw was a black screen.
Moving to xorg fixed this as well...
cubethethird commented on 2017-03-05 02:54 (UTC)
For myself, and I imagine for many others, the issue is related to the usage of Wayland (at least on Gnome). Running it through X.org works normally, and reinstalling the application does not seem to affect this.
erkexzcx commented on 2017-03-05 00:28 (UTC)
How to fix "not ready. No connection" issue for teamviewer12, which was not present in teamviewer11:
1. Quit your current teamviewer, running in the system.
2. Disable & stop "teamviewerd" service.
3. Uninstall teamviewer from your system. At this point should be no teamviewer services preinstalled and/or running in the system.
4. sudo rm -rf /etc/teamviewer*
5. rm -rf ~/.config/teamviewer*
6. Install teamviewer (this AUR package).
7. Enable & start "teamviewerd" service.
8. Open teamviewer - it should work by now.
Also, people in official teamviewer forum suggested to disable ipv6 in your router/network profile as this makes teamviewer v12 to work again. However, above steps solved the issue to me and it was not necesarry
Message to maintainer - please add post uninstall script (if possible) to delete content at least from /etc/teamviewer* and a note to delete manually ~/.config/teamviewer*
swiftgeek commented on 2017-03-01 10:30 (UTC)
That would be upstream bug then, please report it instead of quietly patching for it
severach commented on 2017-03-01 01:24 (UTC)
I solved the no connect problem years ago in my teamviewer9 package. It's caused by a missing .Xauthority file which teamviewer>=9.0 needs for no good reason. The supported distros always have this file but the others may not. My teamviewer9 package fixes this problem automatically. Editing the teamviewer9 PKGBUILD allows you to install any version 8 to 12.
Autostart has never fully worked, probably because I use startx. I don't even need it to. I only need Teamviewer as a client. Access to the Linux desktop isn't valuable. Anything I need from afar I can get through SSH.
Teamviewer will freeze if you've started it without the daemon loaded then later start it with the daemon loaded. You must kill all TV processes and delete the config files to switch between daemon and non daemon mode.
ata commented on 2017-02-28 23:41 (UTC)
WFV
sudo pacman -Rn teamviewer
yaourt -S teamviewer11
WFV commented on 2017-02-14 04:51 (UTC) (edited on 2017-02-22 20:55 (UTC) by WFV)
The GUI auto start option worked sometimes but mostly not, back to square one, can't get it to connect no matter what again after -Syu.
Rigoberto commented on 2017-02-10 01:48 (UTC)
en español: lo lamento no tengo tiempo para pensar en ingles:
la solución de emergencia es wine y describiré tal cual me funciono:
1) descargar teamviewer12.exe
2) instalarla con playonlinux
2.1) que playonlinux cree un nuevo disco virtual-wine (32 bit win10)
2.2) hacer la instalación propiamente tal, pero al finalizar, no colocar ningún enlace en el escritorio porque no servirá.
3) ir a ../.PlayOnLinux/wineprefix/teamviewer(nombre del disco virtual)/drive_c/Program Files/TeamViewer y abrir con wine TeamViewer.exe
tal vez lo que comento es tonto, pero lo intente instalar de 50 maneras distintas y puede que para alguien sea un menester de emergencia (indique la forma exacta en que lo hice pero tuve errores en varios intentos (versiones anteriores entorno xp 64 bits etc., tiene que ser teamviewer12 instalarlo en una arquitectura de 32 bits y para win 10). saludos muy cordiales.
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.
startxusers can follow workaround mentioned in @r7v s commentr7v 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.confwithSource: https://community.teamviewer.com/English/discussion/95696/teamviewer-15-stopped-working-on-debian-buster#M4399