Hi,
I just upgraded to version 15.13.6-1 and my issue is gone. TeamViewer receives an id when the system.d service is enabled permanently.
BR
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: | 1475 |
Popularity: | 1.63 |
First Submitted: | 2010-04-15 10:29 (UTC) |
Last Updated: | 2024-04-26 06:14 (UTC) |
« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 127 Next › Last »
Hi,
I just upgraded to version 15.13.6-1 and my issue is gone. TeamViewer receives an id when the system.d service is enabled permanently.
BR
md5 validity fails
Updated PKGBUILD with todays update: https://pastebin.com/vUj11Qry
System try issue as well. Manjaro 20.2. KDE Plasma 5.20.4
Here too systray is broken. Manjaro KDE - Qt v5.15.2
broken here too( the systray and copypaste)
@liviu.daniel I can confirm. System tray icon is broken for me as well on Manjaro KDE - QT v5.15.1
It breaks the system tray icon on Manjaro KDE flavor. QT version is 5.15.1.
Hi,
I am using teamviewer 15.11.6-1 and am facing the same issue as Ataraxy: https://aur.archlinux.org/packages/teamviewer/?O=10&PP=10#comment-756785
Nov 14 07:30:59 user systemd[1]: /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.
Additionally, I receive:
Nov 14 07:31:52 hostname systemd[1]: Starting TeamViewer remote control daemon...
Nov 14 07:31:52 hostname systemd[1]: teamviewerd.service: Can't open PID file /var/run/teamviewerd.pid (yet?) after start: Operation not permitted
Nov 14 07:31:52 hostname systemd[1]: Starting TeamViewer remote control daemon...
I checked that .pid file and though it is owned by root:root it has read rights for every user, so should be fine in my opinion:
-rw-r--r-- 1 root root 4 14. Nov 07:31 teamviewerd.ipc
-rw-r--r-- 1 root root 3 14. Nov 07:31 teamviewerd.pid
My problem is:
If I manually start the TeamViewer daemon (sudo systemctl start teamviewerd.service) after a reboot, I can regularly start and use TeamViewer. If I permanently enable the TeamViewer daemon (sudo systemctl enable teamviewerd.service) however, I can only start TeamViewer but it will never show me an ID.
In both cases, the daemon goes to active state and shows the exact same error messages. I have no clue why TeamViewer only generates the ID when the daemon is started manually (in both cases the TeamViewer HMI shows Ready to connect with a green circle next to it). Anyone else facing that issue?
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 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.conf
withSource: https://community.teamviewer.com/English/discussion/95696/teamviewer-15-stopped-working-on-debian-buster#M4399