- #TEAMVIEWER LINUX UPDATE#
- #TEAMVIEWER LINUX PATCH#
- #TEAMVIEWER LINUX FULL#
- #TEAMVIEWER LINUX SOFTWARE#
I recently switched to sway (wayland) - but I also tried gnome. "systemctl status teamviewerd" says "rvice: Can't open PID file /run/teamviewerd.pid (yet.". Teamviewer - previous versions of this package I'm using now "aur/teamviewer 15.5.6-1" has been working for years, but now things from 15.5.6-1 just stopped working, just after upgrading my system. (use the session number in the subsequent dbus-send calls) dbus-send -system -print-reply -dest=1 \ĭbus-send -system -print-reply -dest=1 \ sudo dbus-send -system -print-reply -dest=1 \ Systemd v246 added support for changing session type "on the fly" (see how sway implements that), but I couldn't make it work with Activate -> TakeControl -> SetType using dbus-send and then startx (I always get only owner of the terminal can take control).įeel free to try yourself as it should work. not working, I'm pretty sure it's because TV looks for session type ( loginctl session-status | grep Service:) and finds out its type is tty instead of x11 (or wayland). Zadkiel commented on 09:02 regarding startx etc.
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). In both cases, the daemon goes to active state and shows the exact same error messages. If I permanently enable the TeamViewer daemon (sudo systemctl enable rvice) however, I can only start TeamViewer but it will never show me an ID. If I manually start the TeamViewer daemon (sudo systemctl start rvice) after a reboot, I can regularly start and use TeamViewer. 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 14 07:31:52 hostname systemd: Starting TeamViewer remote control daemon.
Nov 14 07:31:52 hostname systemd: rvice: Can't open PID file /var/run/teamviewerd.pid (yet?) after start: Operation not permitted
#TEAMVIEWER LINUX UPDATE#
I am using teamviewer 15.11.6-1 and am facing the same issue as Ataraxy: Nov 14 07:30:59 user systemd: /usr/lib/systemd/system/rvice:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/teamviewerd.pid → /run/teamviewerd.pid please update the unit file accordingly.Īdditionally, I receive: Nov 14 07:31:52 hostname systemd: Starting TeamViewer remote control daemon. Teamviewer git:(master) ✗ ldd /opt/teamviewer/tv_bin/TeamViewer | grep libQt
#TEAMVIEWER LINUX SOFTWARE#
Pkgdesc='All-In-One Software for Remote Support and Online Meetings'
#TEAMVIEWER LINUX PATCH#
If you wouldn't mind applying the patch and adding aarch64 support next time you update the package, that would be great! Thank you! diff -git a/PKGBUILD b/PKGBUILD I applied the patch below and tested it on my Pinebook Pro, and it works great! I was able to use TeamViewer to connect out and remote control a different computer just like on my x86_64 machines.
#TEAMVIEWER LINUX FULL#
I would like to second Saeroshi's request to add aarch64 support to this package, please, except instead of using the more limited -host build of TeamViewer that Saeroshi suggested, I would really like to have the full TeamViewer build that we have for i686 and x86_64.
0 kommentar(er)
