teamviewer.com link icon
or
Ask The Community

Do you want to enjoy the new TeamViewer user interface for Windows?


Download the new version and let us know what you think about it! 👉 Please click here 👈

Teamviewer 13 not working on Fedora 26 - 64 bit?

Hi,

I am having trouble running teamviewer 13 on my fedora 26 machine. Version 12 run just fine. All i get is this

Init...
CheckCPU: SSE2 support: yes
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...

But no gui shows up? I installed teamviewer-13.0.6634-0.x86_64.rpm from the site for fedora distro.

Here is tail of the logfile
017/12/25 19:27:47.960 20569 139657429151040 G   Logger started.
2017/12/25 19:27:47.960 20569 139657429151040 G   Found 0 core dump files ...
2017/12/25 19:27:47.961 20569 139657429151040 G   systemd: logind service available
2017/12/25 19:27:47.962 20569 139657429151040 G   systemd: New seat seat0 [path=/org/freedesktop/login1/seat/seat0, activeSession='1', canGraphical=1, canTTY=1, canMultiSession=1]
2017/12/25 19:27:47.963 20569 139657429151040 G   LogindSessionInfo: New session LogindSessionInfo [id=1 user=root state=user active=1 reliable=1 infoId=2212294583] [path=/org/freedesktop/login1/session/_31 TTY=tty1 seat=seat0 display= vtnr=1 owner=[SysUser: root [uid=0, gid=0 home=/root gecos=root shell=/bin/bash]] idle=1(1513780808191110) active=1 type=tty class=user state=active timestamp=1513780809523267 service=login defaultCG= leader=1834 audit=1 remote=0 rHost= rUser= killProc=0]
2017/12/25 19:27:47.964 20569 139657429151040 G   SysSessionInfoManager: observing sessions from logind is marked as reliable
2017/12/25 19:27:47.965 20569 139657429151040 G   SysSessionInfoManager: Session Information provided by VT [priority: 2]
2017/12/25 19:27:47.965 20569 139657429151040 G   FBSessionObserver: Framebuffer device /dev/fb0 has 8bit depth. Only 32bit and 16bit are supported.
2017/12/25 19:27:47.965 20569 139657429151040 G!  FrameBuffer: Cannot access /dev/fb0, frame buffer support unavailable
2017/12/25 19:27:47.965 20569 139657429151040 G   SysSessionInfoManager: own session cache set to '4294967295'
2017/12/25 19:27:47.965 20569 139657429151040 G   Running on Qt 5.9.2
2017/12/25 19:27:48.010 20569 139657429151040 G   Initialised XRandR extension 1.5 (base=88 error=145)
2017/12/25 19:27:48.081 20569 139657429151040 G   MonitorInfo: [XRandR 1.2] CRTC DVI-I-0 [email protected] [1920, 176, 3200, 1200] - 1
2017/12/25 19:27:48.081 20569 139657429151040 G   MonitorInfo: [XRandR 1.2] CRTC DVI-D-0 [email protected] [3200, 120, 5120, 1200] - 1
2017/12/25 19:27:48.082 20569 139657429151040 G   MonitorInfo: [XRandR 1.2] CRTC DP-0 [email protected] [5120, 0, 7040, 1200] - 1
2017/12/25 19:27:48.082 20569 139657429151040 G   MonitorInfo: [XRandR 1.2] CRTC HDMI-0 [email protected] [0, 120, 1920, 1200] - 1
2017/12/25 19:27:48.082 20569 139657429151040 G   Virtual Desktop [0, 0, 7040, 1200]
2017/12/25 19:27:48.085 20569 139657429151040 G   InterProcessBase::SecureNetwork created
2017/12/25 19:27:48.086 20569 139657429151040 G   AutoLogin::Login: enabled: 1
2017/12/25 19:27:48.086 20569 139657429151040 G   WindowsSessionStateManager(0x2bdf800) state 0
2017/12/25 19:27:48.086 20569 139657429151040 G!!!Own session could not be resolved, unable to startup, Errorcode=11
2017/12/25 19:27:48.086 20569 139657429151040 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 5 failed with error 2, Errorcode=11
2017/12/25 19:27:48.086 20569 139657429151040 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 6 failed with error 2, Errorcode=11
2017/12/25 19:27:48.086 20569 139657429151040 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 9 failed with error 2, Errorcode=11
2017/12/25 19:27:48.086 20569 139657429151040 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 10 failed with error 2, Errorcode=11
2017/12/25 19:27:48.086 20569 139657429151040 G   interprocessbase::SecureNetwork destroyed
2017/12/25 19:27:48.089 20569 139657429151040 G   Shutting down System DBus


What could be wrong?

Comments

  • kozy
    kozy Posts: 1

    Hi, I am running into an identical issue. Did you ever get this working?

  • Yes, apparently teamviewer 13 requires lighdm or GDM to work. Not only to be installed as dependency, but X session needs to be started through tehm. Since i am starting my session via startx it dont work. If you login via gdm or lightdm then teamviewer work. I hope that this would be solved since i am sure then there are many linux people who dont start their sessions through *dm.