Fedora - TV won't start

[coderforlife]

Hi,

I am having a fairly major problem with TV8.

Just tried to install TV on a new Fedora 19 x64 install with a Cinnamon Desktop. In the test virtual machine it works fine, but on the real machine it isn't really working at all. The only difference in setup is that the real machine already has Chrome and Google Voice and Video while the virtual machine has the VirtualBox Guest Additions. The real machine uses EFI while the virtual machine uses BIOS. Otherwise they should be the same (accept the hardware, obviously).

The first sign was that when running the TeamViewer GUI nothing would show up.

The research I have been able to do so far seems to point to the fact that teamviewerd is not getting to a "proper" state ever and is hanging somewhere. When using "teamviewer --info" the it says the daemon is running and active but it is not able to retrieve the TeamViewer ID. Restarting the daemon does not help. I believe the GUI is hanging because it is waiting for some response from the daemon. If the daemon is not running at all, the GUI pops up right away saying so.

Another oddity is that the "teamviewer --ziplogs" command seems to require root access on the real (non-working) machine while on the regular machine regular user access can run that command successfully.

Thanks for any help that anyone can provide!

[matt]

Try this

http://teamviewerforums.com/index.php?topic=1634.msg4063#msg4063

[vacaloca]

I had a similar problem -- mine is that upstart fails to load the teamviewer daemon on startup as it should, so I had to resort to supervisord to start the service -- see: http://ubuntuforums.org/showthread.php?t=2092298&page=3. That works with a few caveats:

1) I have to right click on the password login textbox on the unity-greeter in order to be able to type anything on the local or remote keyboard

2) Sometimes the screen on my client seems to indicate the connection is still up but, in reality, no mouse movements are shown on the server -- effectively the connection is dead, but the client does not report it.

2a I tried to scale the output when 2 displays were connected and this caused a failure in the manner of (2) above, and when trying to reconnect, I got stuck at 'connecting' and effectively locked myself out of my own machine... *sigh*

Running Ubuntu 13.10, NVIDIA 325.15 drivers.

[vacaloca]

I had a similar problem -- mine is that upstart fails to load the teamviewer daemon on startup as it should, so I had to resort to supervisord to start the service -- see: http://ubuntuforums.org/showthread.php?t=2092298&page=3. That works with a few caveats:

1) I have to right click on the password login textbox on the unity-greeter in order to be able to type anything on the local or remote keyboard

2) Sometimes the screen on my client seems to indicate the connection is still up but, in reality, no mouse movements are shown on the server -- effectively the connection is dead, but the client does not report it.

2a I tried to scale the output when 2 displays were connected and this caused a failure in the manner of (2) above, and when trying to reconnect, I got stuck at 'connecting' and effectively locked myself out of my own machine... *sigh*

Running Ubuntu 13.10, NVIDIA 325.15 drivers.

A bit of an update. (1) is still present, but it's a minor annoyance, so I'll live with it. The problems of 2 and 2a are actually related to teamviewer trying to switch to more than 256 colors, which is why it worked on my android phone that is on another network but not on my other machine that is on a faster connection.

If the Ubuntu 13.10 machine does try to switch to more than 256 colors (because it wasn't set to Custom display settings) then I am unable to connect to it anymore and it gets stuck on (yellow circle) 'Connecting...' until I reboot the machine.

As long as I connect to the Ubuntu 13.10 box with 'Custom' display settings it gets set to 256 colors and works correctly. I noticed that it was hanging in the manner described in (2) above when it was trying to negotiate the higher color view, which prompted me to switch to the custom display settings.

Seems like Teamviwer needs to set up its game and support newer Linux distributions! Hopefully this helps someone else fraught with disconnections or Teamviewer service not starting on boot!

[fedorauser]

I've got the EXACT same problem on my machine (only using real machine). 2 weeks ago, TV worked fine. Afterwards I re-installed my system and since then nothing worked.


/opt/teamviever8/logilfes/TeamViewer8_Logfile.log

Code: [Select]

2013/10/28 00:51:06.631 10633 4149193536 S0   CAcceptServer::HandleAccept: new connection from 127.0.0.1:56600
2013/10/28 00:51:06.673 10633 4149193536 S0!  XSession: Unable to open XAuthority file "/home/user/.Xauthority"
2013/10/28 00:51:06.692 10633 4149193536 S0!  XSession: Unable to open XAuthority file "/run/gdm/auth-for-gdm-726cz3/database"
2013/10/28 00:51:06.695 10633 4149193536 S0   TerminalServer: ProcessConnected type 2 PID 10951
2013/10/28 00:51:06.695 10633 4149193536 S0   SysSessionInfoManager_Lin: updating session information for session 0 from GUI
2013/10/28 00:51:06.895 10633 4149193536 S0!!!Crash: Coredump has been written at '/opt/teamviewer8/logfiles/TeamViewer_S_8.0.2093120131028T005106.core'
2013/10/28 00:51:06.895 10633 4149193536 S0   DeleteOldDumps: found 6 dump files ...
2013/10/28 00:51:06.896 10633 4149193536 S0   TeamViewer_Service received fatal SIGABRT
2013/10/28 00:51:07.006 11052 4151727936 S0   Starting as daemon
2013/10/28 00:51:07.008 11052 4151727936 S0   UpdateOnlineState newOnlineValue 0
2013/10/28 00:51:07.011 11052 4151727936 S0   MID: Read from disk failed.
                   
                   
                   
Start:              2013/10/28 00:51:07.012
Version:            8.0.20931
ID:                 0
Loglevel:           Info (100)
License:            0
Server:             master7.teamviewer.com
IC:                 1886678094
CPU:                Unknown
OS:                 Lx Fedora 19 (Schröd (32-bit)
IP:                 192.168.0.10,10.184.1.6
MID:                0xe06995b35038_615cfedc_d41d8cd98f00b204
MIDv:               0
Proxy-Settings:     Type=1 IP= User=

2013/10/28 00:51:07.012 11052 4151727936 S0!! CInterProcessNetwork::Start(): Port 5959 is in use. Trying next port
2013/10/28 00:51:07.012 11052 4151727936 S0   Using IPC-Port 5960
2013/10/28 00:51:07.016 11052 4151727936 S0   SystemdSessionInfoProvider: systemd-logind service available
2013/10/28 00:51:07.016 11052 4151727936 S0   systemd: updating session info by inotify
2013/10/28 00:51:07.016 11052 4151727936 S0   SystemdSeat: New seat seat0 [path=/org/freedesktop/login1/seat/seat0, activeSession='1', canGraphical=1, canTTY=1, canMultiSession=1]
2013/10/28 00:51:07.017 11052 4151727936 S0   SystemdSession: New session 1 [path=/org/freedesktop/login1/session/_31, TTY= seat=seat0 display=:0 vtnr=1 uid=SysUser_Lin: user [uid=1000, gid=1000 home=/home/user gecos=user shell=/bin/bash] idle=0(1382914353006446) active=1 type=x11 class=user state=active timestamp=1382902473687515 service=gdm-password defaultCG=systemd:/user/1000.user/1.session leader=1446 audit=1 remote=0 rHost= rUser= killProc=0] SysSession_Lin: 10001 [id=1, type=3 user=user tty=1 pseudotty=0 state=user active=1 reliable=1 info=0]
2013/10/28 00:51:07.017 11052 4151727936 S0   Session Information provided by systemd
2013/10/28 00:51:07.018 11052 4151727936 S0   XSocketSessionObserver: watching /tmp/.X11-unix
2013/10/28 00:51:07.029 11052 4151727936 S0!  XSession: Unable to open XAuthority file "/home/user/.Xauthority"
2013/10/28 00:51:07.036 11052 4151727936 S0!  XSession: Unable to open XAuthority file "/run/gdm/auth-for-gdm-726cz3/database"
2013/10/28 00:51:07.037 11052 4151727936 S0!  XSession: Unable to open XAuthority file "/home/user/.Xauthority"
2013/10/28 00:51:07.043 11052 4151727936 S0!  XSession: Unable to open XAuthority file "/run/gdm/auth-for-gdm-726cz3/database"
2013/10/28 00:51:07.043 11052 4151727936 S0   UpdateOnlineState newOnlineValue 0
2013/10/28 00:51:08.013 11052 4139776832 S0   TerminalServer::SessionLogin for session 0
2013/10/28 00:51:08.013 11052 4139776832 S0   CTerminalServer::RepeatedlyCheckForUserLogin() Don't start GUI for session 0

teamviewer --info

Code: [Select]

TeamViewer                      8.0.20931

 teamviewerd status              teamviewerd.service - TeamViewer remote control daemon
   Loaded: loaded (/etc/systemd/system/teamviewerd.service; enabled)
   Active: active (running) since Mo 2013-10-28 00:51:07 CET; 6min ago
 Main PID: 11052 (teamviewerd)
   CGroup: name=systemd:/system/teamviewerd.service
           ??11052 /opt/teamviewer8/tv_bin/teamviewerd -d

Okt 28 00:51:07 localhost.localdomain systemd[1]: PID 10633 read from file /var/run/teamviewerd.pid does not exist.
Okt 28 00:51:07 localhost.localdomain systemd[1]: Started TeamViewer remote control daemon.
Okt 28 00:51:20 localhost.localdomain systemd[1]: Started TeamViewer remote control daemon.
Okt 28 00:51:59 localhost.localdomain systemd[1]: Started TeamViewer remote control daemon.

TeamViewer ID: not found
Try restarting the TeamViewer daemon (e.g. teamviewer --daemon restart)
And also, the restart didn't work. I don't see how the link to the ubuntuforums will help us. But I'm not a pro user.

[fedorauser]

I I was enabling daemon + rebooting few times, suddenly the GUI showed up. I was happy bla bla. Next reboot, GUI didn't show up
BUT!

Code: [Select]

TeamViewer                      8.0.20931

 teamviewerd status              teamviewerd.service - TeamViewer remote control daemon
   Loaded: loaded (/etc/systemd/system/teamviewerd.service; enabled)
   Active: active (running) since Mi 2013-10-30 14:23:08 CET; 35s ago
  Process: 3071 ExecStart=/opt/teamviewer8/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS)
 Main PID: 3073 (teamviewerd)
   CGroup: name=systemd:/system/teamviewerd.service
           ??3073 /opt/teamviewer8/tv_bin/teamviewerd -d

Okt 30 14:23:08 localhost.localdomain systemd[1]: PID 742 read from file /var/run/teamviewerd.pid does not exist.
Okt 30 14:23:08 localhost.localdomain systemd[1]: Started TeamViewer remote control daemon.

 TeamViewer ID:                   45XXXX572 Which means, TeamViewer is running, and in theory, people can access my pc. (In theory, not really - can't see the password. Do I?).

But what can I do to see the GUI again?