jelabarre59

@Ying_Q wrote:Hi @gideonse and @BenDice, Thank you for you message. If you think TeamViewer has mistakely marked your device usage and you would like to reset your TeamViewer ID, please fill in the form for reset request. Your "Reset Form" is BROKEN though. It has been broken for WEEKS now. And no one at TV seems willing…

@DanLester wrote:Most are functionally equivalent to TV in screen sharing, though TV is somewhat more capable in file sharing, and has a more robust user interface. Sometimes that's all you need anyway. I know for my purposes I just need to connect to a family member's machine to troubleshoot something (or to a machine in…

Considering I've tried it on multiple machines, multiple OS'es over a period of 2 or 3 years, and these being machines at different locations (different ISPs), I can only presume it's Google's standard brokenness that permeates their products from search on downwards. I'd just use some VNC configuration if I were able to…

@tjhall1000 wrote:honestly. while this issue has been happening.... i downloaded **Third Party Product** cuz i needed to watch my anime while not at home. cuz thats the only reason i use TV is to watch anime on my computer while im not home. [removed per Community Guidelines - Sales/Solicitation policy] im sad i never knew…

Same thing here. The "Commercial Use Suspected" form is BROKEN. I wouldn't put it past the TeamViewer folks to have broken it intentionally.

Nope. This solution may have worked 3 or 4 years ago, but there is nothing in the TV client to even see private messages, and the "Messaging" section of the website has no way to delete, block or report a message. For that matter the TV website won't even recognize the message as "Read", so it sits there forever in "New"…

The problem is Wayland isn't even close to being feature-compatible, yet it gets shoved out as a replacement, and any complaint that it is missing something gets a hostile response of "well, no one uses taht anyway". Really??? So if *I'M* asking for some function to be in place, something that existed in X11, that means…

To be fair to the TeamViewer folks, Wayland has been a disaster ever since it was introduced. They have shoved it out the door with only a bare minimum of the functionality X11 has, and mumble feeble excuses that either 1: "You don't need that" or 2: "we can figure that bit out in the next 5 years (or maybe 10)". Wayland…

Not seeing a "gear wheel" on my client.

Tested it against a couple MSWin machines (MSW7 & MSW10) from my LinuxMint 18.2 system and the unmute microphone is gone. It wasn't a question of a "nuisance" message, but rather that it looked and felt like a potential security hole. So I'm hoping you simply haven't hidden the prompt but left the hole there.

It would be great if you guys could make it so we could remotely roll back any newer version to a older one? That way if there is ever a problem like this one it is easily fixed/patched/ until a permanent solution is found.And if Auto-update is turned off & set to NEVER check for updates - TURN OFF the update notifications…

When someone releases the exploit that takes advantage of this bug (if they haven't already) TV will take notice of it. Really don't understand this; there's a code change that implemented this bug, a change that could go back to a particular build. Remove that code. Patch the rest. The longer they wait, the harder to…

The issue is it appears to be a security hole, or may mess up audio on one end or the other. It also is something that should be a preference setting, yet there's no checkbox to disable it. But my own take on it is it looks like a security hole more than an issue that you have an extra button to click.

On Linux Mint 18.2 (Ubuntu 16.04.1/xenial based) Intel(R) Core(TM) i3-2120 CPU @ 3.30GH 4.8.0-53-generic x86_64 ||/ Name Version Architecture Description +++-==============-============-============-================================= ii teamviewer:i38 12.0.76279 i386 Remote control and meeting soluti ||/ Name Version…

Got the MSWin remote machine to upgrade to build 81460, and tried again. It STILL gives me the error message when connecting from Linux. Linux client will need to be fixed as well (unless the MSWin side is still broken, I don't run MSWin at home, or even on my work machine so can't verify that).

Not fixed for Linux-to-MSWin connectivity. Confirmed the remote MSWin7 and my local Linux system are at the latest versions as of 26-Jul-17 (AM) (according to the download versions on the website). Error still comes up. Are people only checking against MSWin-to-MSWin? Because I haven't seen a Linux package update in weeks…

You would think the appropriate fix would be to back out the change that broke this in the first oplace, but I doubt Teamviewer has the competence to do so. 

@focusp wrote:Thanks, updating Team Viewer fixed the unmute micophone problem for me. That *ONLY* works if you're connecting from the same OS as the remote end is running. If you are on Linux and connecting to MSWin?? Sorry, still incapable of fixing that.

FIRSTLY: just how does the TV support team get away with marking this issue as "SOLVED"??? It is not for YOU to determine if it is solved or not. How very Microsoft of you to presume to mark it solved when it is not so. It is only for the customers to decide that, not managers trying to falsify their numbers. When you sign…

The "Remote Update" is only a solution if the local and remote are running the SAME operating system. If your remote are running MSWin and your local is Linux, even having the most recent versions for both will not fix the problem.

It seems it isn't even sufficient to have the latest version on both ends. You ALSO have to be using the same OS on both ends too, apparently. I have the latest Teamviewer on my brother's brand-net MSWin10 system. I downloaded the latest 64bit Debian package and installed it to my LinuxMint 18.1 system. You know what? SAME…

My presumption had been, when I saw this recently, that I had missed a configuration setting. From what I'm seeing here, it looks like TV has decided to ADD some unneeded and unwanted function, and has apparently deemed us unworthy of deciding whether we want it shut off. Unacceptable.