You are not logged in.
Hi guys,
I installed TeamViewer 8, enabled and started teamviewerd, but I am not able to log into the machine, if no user is logged in and has started the TeamViewer application.
Does anyone know, whether it is possible to configure teamviewerd.service, so that I can access the machine without a user being logged in? With google and on the TeamViewer website I could not find any useful peace of information.
Thx & Regards,
hcjl
Last edited by hcjl (2014-06-20 10:45:19)
Offline
i am interested in this myself . . .
came across this: http://drpaudel.com.np/?p=341
but it would have to be updated for systemd
Offline
starting the service is not the problem, because the service files are included in the aur package. if you enable the service with
sudo systemctl enable teamviewerd.service
then it is started during boot.
the problem is, that i cannot log in unless a user is logged in an started the teamviewer client.
Offline
Ok I have the same problem.
Perhaps an update will fix this.
Anyone resolved this?
I have this issue connecting from Arch to Ubuntu 12.04.
Offline
enable auto login, i figured out the service enable immediately after reading how to start it, so you will have to forego security with an auto login until someone smarter replies lol
Offline
@fallen00sniper
i know that i could do that, but that's exactly what i don't want;-)
Offline
The best answer I have seen so far is auto-login but running a screen lock command at startup.
Offline
I enjoy using team viewer and i am new to arch linux, however when i heard this thread, i remembered when i used freebsd... i noticed that i could reboot the system from ssh and wait for it to boot and then i could logon... also during the boot of freebsd, i had jails and squids running and they would be operational before i would login, i was amazed by this and was happy my system ran like that...
the point is, is there any way to solve your problem you could make arch do that, that way you can have the security of a remote machine yet allowing you to not have to physically do anything in order to manage it?
Offline
Is there a fix for this? Not counting the autologin with screenlock.
>systemctl status teamviewerd.service
teamviewerd.service - TeamViewer remote control daemon
Loaded: loaded (/usr/lib/systemd/system/teamviewerd.service; enabled)
Active: active (running) since Mon 2013-09-16 19:04:56 CEST; 1min 49s ago
Process: 415 ExecStart=/opt/teamviewer8/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS)
Main PID: 519 (teamviewerd)
CGroup: name=systemd:/system/teamviewerd.service
└─519 /opt/teamviewer8/tv_bin/teamviewerd -d
but can't connect until user starts the app
Offline
Is there a fix for this? Not counting the autologin with screenlock.
>systemctl status teamviewerd.service teamviewerd.service - TeamViewer remote control daemon Loaded: loaded (/usr/lib/systemd/system/teamviewerd.service; enabled) Active: active (running) since Mon 2013-09-16 19:04:56 CEST; 1min 49s ago Process: 415 ExecStart=/opt/teamviewer8/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS) Main PID: 519 (teamviewerd) CGroup: name=systemd:/system/teamviewerd.service └─519 /opt/teamviewer8/tv_bin/teamviewerd -d
but can't connect until user starts the app
Ditto.
Offline
Here's a possible solution. It is a bit of a kluge but so it goes. It was outlined by Fluky Logs on BlogSpot. Some manual editing required.
Setup for auto login for an account you want to use to access your LINUX box......(I know, wait for it)......but lock the desktop immediately. Then unlock the desktop with the normal password.
http://flukylogs.blogspot.com/2011/08/t … rt-in.html
Now I have yet to do this, maybe tomorrow. I'm set to go to sleep.
Those of you who have contributed to this thread should be congratulated for being persistent.
Cheers,
John S Wolter
Offline
If you look into the /opt/teamviewer9 directory you will see that the desktop application uses Wine. Does Wine run outside of an X-session? Most likely not. That may explain why even when teamviewer.service is running, the desktop application needs to run for a desktop connection.
The service runs in the root context, not such a great idea. I can only speculate that the .service is a systems level interface that provides the connection between the user level Wine program and the underlying kernel services.
While teamviewer is useful, I'm starting to think that VNC over SSH may have sufficient utility. It may also be a more direct way to achieve the goal of remote desktop. As always TightVNC for the desktop and Putty for the command line is available for M$ Windoze. This combination may work sufficiently well. The teamviewer thing I like is the online alert that the system is available.
I'm going to test this to see if the speed complaints have any basis. The server and client are of good performance so it may be enough.
Offline
@johnswolter
for me teamviewer is a nice to have. alternatively i use x2go which works like a charm on windows and linux boxes.
Offline
Works now with TeamViewer 9.
Offline