Help with latest TeamViewer

[MintBurgundy]

Hi there, long time reader of this forum , first time poster. I am currently running LinuxMInt12 LIsa 32bit on an old laptop. The main purpose for the computer is to stream media 24x7 from a series of esata ext hdd's. I use teamviewer from my phone and other laptops etc constantly, I very rarely ever use this computer locally. After setting up Linux Mint, I had installed teamviewer 7 from the software center and had been using it daily with no problems. Recently, I updated my client on a windows7 laptop, and noticed that the .deb package on the teamviewer website was a newer revision than what I was running. I downloaded the newest version for 32bit (V 7.0.9348) and everything seemed fine until I went to initiate a sesion from another client.

Upon beginning a remote control session (either using IP over LAN or using teamviewer's servers) the team viewer client on mint provides the following error:



On Mint, the teamviewer sidebar is still displayed, and the remote client is listed as being in session,

On my other client, (have tried with android phones, tablet, and win7) no session is displayed, but the connection is listed, if I try to connect again it prompts me that a session is already in progress, however no usable session window ever opens.

I was hoping by sheer luck that perhaps I could simply remove the newer version and re-install the version form the software manager my fav noob trick that has saved me in the past , however I am unable to actually open the teamviewer7 app within the software manager...


Has anyone else encountered a similar problem? I am very novice in the ways of linux so I am unsure of what to try next to troubleshoot my situation.
Any help from this community would be great.

[MintBurgundy]

No one else has had an issue with this? I have only seen one other thread pertaining to ubuntu 12.04 64bit and teamviewer but not for 32bit.... I tried installing 12.04 too and that too causes the same errors as I had on Mint12, I guess since I can not fix it I will have to use vnc instead.