Unable to run TV13 without display manager, even when using tar archive

Announcements

Would you like to be part of the TeamViewer task force to make our product even better? Start now with participating in our survey and help our product team to build an even better TeamViewer. Click here for more information.

Posted by j_darwin
Digon

Unable to run TV13 without display manager, even when using tar archive

I'm not using a display manager, I run startx directly.

According to this thread, Teamviewer should be able to run without display manager if I download and use the tar archive, but unfortunately the GUI still doesn't start.

$ ./teamviewer

Init...
CheckCPU: SSE2 support: yes
Checking setup...
Launching TeamViewer ...
Starting network process (no daemon)
Network process started (7737)
Launching TeamViewer GUI ...

Logs:

2018/01/08 00:10:32.508  7737 139992786697152 N   NetWatchdog: Internet is now connected
2018/01/08 00:10:32.509  7737 139992786697152 N   NetWatchDogLinux: initialized network manager connection
2018/01/08 00:10:32.509  7737 139992786697152 N   RemoteSettingsMDRelationshipWatchDog: DEVICE ISN'T A MANAGED DEVICE
2018/01/08 00:10:32.509  7737 139992059844352 N   RemoteSettingsStore: Cleanup all policies.
2018/01/08 00:10:32.509  7737 139992786697152 N   RemoteSettingsStoreListener: Establish connection.
2018/01/08 00:10:32.510  7737 139992059844352 N   RemoteSettingsStore::LoadLastReceivedPolicies : Storage Entry Remote_Settings_TVClientSetting_Policy empty
2018/01/08 00:10:32.510  7737 139992786697152 N   Using IPC-Port 5940
2018/01/08 00:10:32.510  7737 139992059844352 N   RemoteSettingsMDRelationshipWatchDog: DEVICE ISN'T A MANAGED DEVICE
2018/01/08 00:10:32.510  7737 139992786697152 N   Updated sessions: 
2018/01/08 00:10:32.510  7737 139992786697152 N   UpdateOnlineState newOnlineValue 0
2018/01/08 00:10:32.510  7737 139992786697152 N   UpdateOnlineState newOnlineValue 0
2018/01/08 00:10:32.511  7737 139991422326528 N   Using systemd-logind for suspend/resume monitoring
2018/01/08 00:10:33.046  7685 139980245552256 G   Logger started.
2018/01/08 00:10:33.046  7685 139980245552256 G   Found 0 core dump files ...
2018/01/08 00:10:33.047  7685 139980245552256 G   systemd: logind service available
2018/01/08 00:10:33.049  7685 139980245552256 G   systemd: New seat seat0 [path=/org/freedesktop/login1/seat/seat0, activeSession='c1', canGraphical=1, canTTY=1, canMultiSession=1]
2018/01/08 00:10:33.049  7685 139980245552256 G   LogindSessionInfo: New session LogindSessionInfo [id=c1 user=darwin state=user active=1 reliable=1 infoId=1591159457] [path=/org/freedesktop/login1/session/c1 TTY=tty1 seat=seat0 display= vtnr=1 owner=[SysUser: darwin [uid=1000, gid=989 home=/home/darwin gecos= shell=/bin/zsh]] idle=1(1515325702526228) active=1 type=tty class=user state=active timestamp=1515325710017432 service=login defaultCG= leader=755 audit=0 remote=0 rHost= rUser= killProc=0]
2018/01/08 00:10:33.051  7685 139980245552256 G   SysSessionInfoManager: observing sessions from logind is marked as reliable
2018/01/08 00:10:33.051  7685 139980245552256 G   SysSessionInfoManager: Session Information provided by VT [priority: 2]
2018/01/08 00:10:33.051  7685 139980245552256 G!  FrameBuffer: Cannot access /dev/fb0, frame buffer support unavailable
2018/01/08 00:10:33.052  7685 139980245552256 G   SysSessionInfoManager: own session cache set to '4294967295'
2018/01/08 00:10:33.052  7685 139980245552256 G   Running on Qt 5.10.0
2018/01/08 00:10:33.066  7685 139980245552256 G   Initialised XRandR extension 1.5 (base=89 error=147)
2018/01/08 00:10:33.083  7685 139980245552256 G   MonitorInfo: [XRandR 1.2] CRTC eDP-1 3840x2160@60Hz [0, 0, 3840, 2160] - 1
2018/01/08 00:10:33.083  7685 139980245552256 G   MonitorInfo: [XRandR 1.2] CRTC 1 has no outputs
2018/01/08 00:10:33.083  7685 139980245552256 G   MonitorInfo: [XRandR 1.2] CRTC 2 has no outputs
2018/01/08 00:10:33.083  7685 139980245552256 G   Virtual Desktop [0, 0, 3840, 2160]
2018/01/08 00:10:33.084  7685 139980245552256 G!! MonitorInfo: WorkingArea: Property error 14 (0), Errorcode=11
2018/01/08 00:10:33.090  7685 139980245552256 G   InterProcessBase:Smiley FrustratedecureNetwork created
2018/01/08 00:10:33.092  7685 139980245552256 G   AutoLogin::Login: enabled: 1
2018/01/08 00:10:33.092  7685 139980245552256 G   WindowsSessionStateManager(0x18d1540) state 0
2018/01/08 00:10:33.093  7685 139980245552256 G!!!Own session could not be resolved, unable to startup, Errorcode=11
2018/01/08 00:10:33.093  7685 139980245552256 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 5 failed with error 2, Errorcode=11
2018/01/08 00:10:33.093  7685 139980245552256 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 6 failed with error 2, Errorcode=11
2018/01/08 00:10:33.093  7685 139980245552256 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 9 failed with error 2, Errorcode=11
2018/01/08 00:10:33.093  7685 139980245552256 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 10 failed with error 2, Errorcode=11
2018/01/08 00:10:33.093  7685 139980245552256 G   interprocessbase:Smiley FrustratedecureNetwork destroyed
2018/01/08 00:10:33.095  7685 139980245552256 G   Shutting down System DBus

Result of checking dependencies:

 

$ ./tv-setup checklibs

    -=-   TeamViewer tar.xz check   -=-

  In order to use the tar.xz version of TeamViewer,
  you have to make sure that the necessary libraries are installed.

    Writing raw output to /home/darwin/Downloads/teamviewer/logfiles/DependencyCheck.log

 Analyzing dependencies ...

        All dependencies seem to be satisfied!


 

1 Reply
1 Reply
Posted by J_Reis
Trigon

Re: Unable to run TV13 without display manager, even when using tar archive

Just for the sake of keeping all our ducks in a row … I started a thread about this a few weeks ago.

I believe this fellow was also looking for this functionality. There may be a few others spread out here in the forums … and who knows how many "in the wild." No word from TV that I've seen, but hopefully it is on a 'to do' list somewhere.