Linux - downgrade to version 15.27.3

Gigi183 · 2022-03-28T19:55:52+00:00

There was an error rendering this rich post.

The newest version (15.28.6) doesn't work on my Linux Mint installation. I have 15.27.3 on another machine and it is still working fine with the target computer. How can I downgrade to version 15.27.3?

Find more posts tagged with

Comments

.Carol.fg.

It's my pleasure to help! 😊

I'll be forwarding these extra details to the designated team.

Thanks again for all the time you took to look into this issue as well as the time to write us the information!

We value your feedback!

Best, Carol 👩🏻‍🦰🌷

FF123456

Thanks @.Carol.fg. !

One more thing I tried: since I have both 15.24.5 (works with the Wacom pen) and 15.25.5 (does not work with the Wacom pen) here that are quite similar, I also played a little around with these by installing Teamviewer 15.24.5 and then replacing the files in /opt/teamviewer/tv_bin/ one by one with the one from the new version in order to narrow down the problem.

My results:

if I replace only the folder the folder /opt/teamviewer/tv_bin/RTlib with all its content with the folder from v15.25.5, Teamviewer still works. This means the problem does not seem to originate from the QT libraries you bundled with the program or from another of the files in this folder.
if I replace the "resources" folder and the "teamviewer"executable itself with the new version and leave the rest of the installation (including the RTlib folder!) on v15.24.5, the program complains upon start that the daemon is not running, which is expected since I did not replace the "teamviewerd" file. But the "ok" button in this error message already does not react on clicks with the tablet pen any more.

Therefore, I can safely say the error can be found within the "teamviewer" executable itself (or in the resource file, but I believe this one only contains localised language strings).

I hope this makes the search easier for you.

.Carol.fg.

Oh nice, thanks @FF123456!

We appreciate the time you took to write the post and to get all the information together!

I have forwarded it to the designated team too. 😄

We will keep in touch, have a wonderful day!

Best, Carol 👩🏻‍🦰🌷

FF123456

@.Carol.fg. Thanks for the update!

I took the time to ask the developer of the Wacom driver some questions, and I managed to obtain some data with the xinput test-xi2 command I would like to share. It seems that in opposite to a mouse / touchpad, the Wacom tablet driver sends out some additional data to the program - could this somehow prevent Teamviewer to recognise the mouse interaction?

This is what a standard mouse / Touchpad click event looks like - the "valuators" section is empty:

EVENT type 15 (RawButtonPress)
    device: 2 (10)
    detail: 1
    flags: 
    valuators:

EVENT type 4 (ButtonPress)
    device: 10 (10)
    detail: 1
    flags: 
    root: 134.63/220.88
    event: 84.63/89.88
    buttons:
    modifiers: locked 0x10 latched 0 base 0 effective: 0x10
    group: locked 0 latched 0 base 0 effective: 0
    valuators:
    windows: root 0x1e0 event 0x7400001 child 0x7400002
EVENT type 7 (Enter)
    device: 2 (2)
    windows: root 0x1e0 event 0x7400001 child 0x0
    mode: NotifyGrab (detail NotifyInferior)
    flags:  [same screen]
    buttons: 1
    modifiers: locked 0x10 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    root x/y:  134.00 / 220.00
    event x/y: 84.00 / 89.00
EVENT type 9 (FocusIn)
    device: 3 (3)
    windows: root 0x1e0 event 0x7400001 child 0x0
    mode: NotifyNormal (detail NotifyNonlinear)
    flags:  [same screen]
    buttons: 1
    modifiers: locked 0x10 latched 0 base 0 effective: 0x10
    group: locked 0 latched 0 base 0 effective: 0
    root x/y:  134.00 / 220.00
    event x/y: 84.00 / 89.00
EVENT type 8 (Leave)
    device: 2 (2)
    windows: root 0x1e0 event 0x7400001 child 0x0
    mode: NotifyUngrab (detail NotifyInferior)
    flags: [focus] [same screen]
    buttons: 1
    modifiers: locked 0x10 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    root x/y:  134.00 / 220.00
    event x/y: 84.00 / 89.00
EVENT type 4 (ButtonPress)
    device: 2 (10)
    detail: 1
    flags: 
    root: 134.63/220.88
    event: 84.63/89.88
    buttons:
    modifiers: locked 0x10 latched 0 base 0 effective: 0x10
    group: locked 0 latched 0 base 0 effective: 0
    valuators:
    windows: root 0x1e0 event 0x7400001 child 0x7400002
EVENT type 7 (Enter)
    device: 2 (2)
    windows: root 0x1e0 event 0x7400001 child 0x0
    mode: NotifyGrab (detail NotifyInferior)
    flags: [focus] [same screen]
    buttons: 1
    modifiers: locked 0x10 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    root x/y:  134.00 / 220.00
    event x/y: 84.00 / 89.00
EVENT type 16 (RawButtonRelease)
    device: 2 (10)
    detail: 1
    flags: 
    valuators:

EVENT type 5 (ButtonRelease)
    device: 10 (10)
    detail: 1
    flags: 
    root: 134.63/220.88
    event: 84.63/89.88
    buttons: 1
    modifiers: locked 0x10 latched 0 base 0 effective: 0x10
    group: locked 0 latched 0 base 0 effective: 0
    valuators:
    windows: root 0x1e0 event 0x7400001 child 0x7400002
EVENT type 5 (ButtonRelease)
    device: 2 (10)
    detail: 1
    flags: 
    root: 134.63/220.88
    event: 84.63/89.88
    buttons: 1
    modifiers: locked 0x10 latched 0 base 0 effective: 0x10
    group: locked 0 latched 0 base 0 effective: 0
    valuators:
    windows: root 0x1e0 event 0x7400001 child 0x7400002
EVENT type 8 (Leave)
    device: 2 (2)
    windows: root 0x1e0 event 0x7400001 child 0x0
    mode: NotifyUngrab (detail NotifyInferior)
    flags: [focus] [same screen]
    buttons:
    modifiers: locked 0x10 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    root x/y:  134.00 / 220.00
    event x/y: 84.00 / 89.00

And this is what comes from a graphics tablet pen - please note the valuators (in my case five) being handed over by the X server to the program:

EVENT type 15 (RawButtonPress)
    device: 2 (8)
    detail: 1
    flags: 
    valuators:
          0: 28385.00 (28385.00)
          1: 4290.00 (4290.00)
          2: 20457.00 (20457.00)
          3: 20.00 (20.00)
          4: 26.00 (26.00)
          5: -900.00 (-900.00)

EVENT type 4 (ButtonPress)
    device: 8 (8)
    detail: 1
    flags: 
    root: 2438.17/221.09
    event: 100.17/81.09
    buttons:
    modifiers: locked 0x10 latched 0 base 0 effective: 0x10
    group: locked 0 latched 0 base 0 effective: 0
    valuators:
        0: 28385.00
        1: 4290.00
        2: 20457.00
        3: 20.00
        4: 26.00
        5: -900.00
    windows: root 0x1e0 event 0x7400001 child 0x0

EVENT type 9 (FocusIn)
    device: 3 (3)
    windows: root 0x1e0 event 0x7400001 child 0x0
    mode: NotifyNormal (detail NotifyNonlinear)
    flags:  [same screen]
    buttons: 1
    modifiers: locked 0x10 latched 0 base 0 effective: 0x10
    group: locked 0 latched 0 base 0 effective: 0
    root x/y:  2438.00 / 221.00
    event x/y: 100.00 / 81.00

EVENT type 4 (ButtonPress)
    device: 2 (8)
    detail: 1
    flags: 
    root: 2438.17/221.09
    event: 100.17/81.09
    buttons:
    modifiers: locked 0x10 latched 0 base 0 effective: 0x10
    group: locked 0 latched 0 base 0 effective: 0
    valuators:
        0: 28385.00
        1: 4290.00
        2: 20457.00
        3: 20.00
        4: 26.00
        5: -900.00
    windows: root 0x1e0 event 0x7400001 child 0x0

EVENT type 17 (RawMotion)
    device: 2 (8)
    detail: 0
    flags: 
    valuators:
          0: 28382.00 (28382.00)
          1: 4289.00 (4289.00)
          2: 27405.00 (27405.00)
          3: 19.00 (19.00)
          4: 26.00 (26.00)
          5: -900.00 (-900.00)

EVENT type 6 (Motion)
    device: 8 (8)
    detail: 0
    flags: 
    root: 2438.91/221.04
    event: 100.91/81.04
    buttons: 1
    modifiers: locked 0x10 latched 0 base 0 effective: 0x10
    group: locked 0 latched 0 base 0 effective: 0
    valuators:
        0: 28382.00
        1: 4289.00
        2: 27405.00
        3: 19.00
        4: 26.00
        5: -900.00
    windows: root 0x1e0 event 0x7400001 child 0x0

EVENT type 8 (Leave)
    device: 2 (8)
    windows: root 0x1e0 event 0x7400001 child 0x0
    mode: NotifyNormal (detail NotifyInferior)
    flags: [focus] [same screen]
    buttons: 1
    modifiers: locked 0x10 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    root x/y:  2437.00 / 221.00
    event x/y: 99.00 / 81.00

EVENT type 7 (Enter)
    device: 2 (8)
    windows: root 0x1e0 event 0x7400002 child 0x0
    mode: NotifyNormal (detail NotifyAncestor)
    flags: [focus] [same screen]
    buttons: 1
    modifiers: locked 0x10 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    root x/y:  2437.00 / 221.00
    event x/y: 49.00 / 31.00


------- Numerous events of Types EVENT type 6 (Motion) and EVENT type 17 (RawMotion) in between here -------


EVENT type 16 (RawButtonRelease)
    device: 2 (8)
    detail: 1
    flags: 
    valuators:
          0: 28359.00 (28359.00)
          1: 4255.00 (4255.00)
          2: 0.00 (0.00)
          3: 16.00 (16.00)
          4: 28.00 (28.00)
          5: -900.00 (-900.00)

EVENT type 5 (ButtonRelease)
    device: 8 (8)
    detail: 1
    flags: 
    root: 2435.94/219.29
    event: 97.94/79.29
    buttons: 1
    modifiers: locked 0x10 latched 0 base 0 effective: 0x10
    group: locked 0 latched 0 base 0 effective: 0
    valuators:
        0: 28359.00
        1: 4255.00
        2: 0.00
        3: 16.00
        4: 28.00
        5: -900.00
    windows: root 0x1e0 event 0x7400001 child 0x7400002

EVENT type 5 (ButtonRelease)
    device: 2 (8)
    detail: 1
    flags: 
    root: 2435.94/219.29
    event: 97.94/79.29
    buttons: 1
    modifiers: locked 0x10 latched 0 base 0 effective: 0x10
    group: locked 0 latched 0 base 0 effective: 0
    valuators:
        0: 28359.00
        1: 4255.00
        2: 0.00
        3: 16.00
        4: 28.00
        5: -900.00
    windows: root 0x1e0 event 0x7400001 child 0x7400002

EVENT type 8 (Leave)
    device: 2 (2)
    windows: root 0x1e0 event 0x7400001 child 0x0
    mode: NotifyUngrab (detail NotifyInferior)
    flags: [focus] [same screen]
    buttons:
    modifiers: locked 0x10 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    root x/y:  2435.00 / 219.00
    event x/y: 97.00 / 79.00

A motion event of the Mouse pointer also has more valuators, as you can see in the above example. If you use a mouse, there are just two of them (sorry for the formatting - your forum software did not like me there):

EVENT type 6 (Motion)

device: 14 (14)

detail: 0

flags:

root: 95.87/168.87

event: 45.87/37.87

buttons:

modifiers: locked 0x10 latched 0 base 0 effective: 0x10

group: locked 0 latched 0 base 0 effective: 0

valuators:

0: 133.87

1: 199.87

windows: root 0x1e0 event 0x8400001 child 0x0

.Carol.fg.

Hi @FF123456 , 😃

Thanks for your post, we're happy to see you again!

Our development team is aware of the issue and they are working on a resolution.

As previously mentioned this process can take some time; therefore, we highly appreciate our users for their patience and understanding during this process. 🙏🏻

We also thank you for the additional details provided! I already forward them to the designated team.

As soon as the issue gets resolved, we will notify all the users in this discussion regarding it.

We will keep in touch!

Best, Carol 👩🏻‍🦰🌷

FF123456

@.Carol.fg. It has been a while - are there any news you could share?

I found out two new things about this:

the problem only affects the Wacom pen input. If I use the Multitouch capabilities of my Wacom tablet instead (i.e. using the graphics tablet as a giant touch pad with my finger), Teamviewer behaves normally. This has been my workaorund for a while, but it is cumbersome.
The Ultimaker Cura software (https://ultimaker.com/de/software/ultimaker-cura) suffers from the same problem. I hope this might help you a little - it must be some piece of code that Teamviewer and Cura share and that you introduced in Teamviewer 15.25.5 - but which one?

FF123456

https://community.teamviewer.com/English/discussion/comment/137497#Comment_137497

Okay, now I finally could borrow a standard mouse and could test this. This is really weird - but I can confirm your finding and your workaround! Thanks!

@.Carol.fg. that might help your development team as we can specify the problem better now: Teamviewer 15.25.5 and up ignore any events (both mouse movements and clicks) sent to them from the Linux driver for graphic tablets. This means a Wacom tablet cannot be used as a mouse replacement in Teamviewer for Linux as I do for the sake of my hand. It works for any other software I tried - but not for Teamviewer. Could you update the ticket you had opened to include this information?

I can also confirm that this applies to the updated driver used in Linux Mint 21 as well.

sebastien2

Dears I have to say that I had a similar issue with 15.33.7.

the UI is just DEAD.

after searching a while I realize that that was my WACOM Tablet (intuos pro pth-451 in my case) . When using the tablet and clicking with the pen it didn´t work at all.

I found a mouse, and manage then to click on the different part of the interfaces.

If would be also user friendly to have the standard shortkeys like ALT+C for connection, ALT+E for Extra, as the menu was not even accessible at first

I was able to replicate the problem on 2x different PC.

Hope this helps someone.

FF123456

https://community.teamviewer.com/English/discussion/comment/136744#Comment_136744

Thanks a lot for the update @.Carol.fg.!

.Carol.fg.

Hello @FF123456 ,

Thanks for your message, I hope you doing well. 😄

Today I contacted our support team regarding this case for updates.

👉 They confirmed to me that the case is still open and under investigation by our development team.

Therefore, we don't have a solution to share just yet.

We appreciate your patience and understanding during this processing time.

Please let us know if you have any further questions.

Best,

Carol

FF123456

https://community.teamviewer.com/English/discussion/comment/134401#Comment_134401

Hi @.Carol.fg. Carol.f , are there any news about the topic? The current teamviewer version 15.32.3 still does not solve the issue - the only change I found was that the last working version 15.24.5 was removed from the "stable" repository which ist not what I had expected. 😒

Thankfully I have a working local backup...

FF123456

https://community.teamviewer.com/English/discussion/comment/134401#Comment_134401

@.Carol.fg. This is good news, thank you very much! If there is anything I can help you your developers with please tell me, I will gladly run any test software and send you its output if that helps.

.Carol.fg.

Hello everybody!

I hope you're all doing well 😊

Just to provide some updates regarding the case:

👉 Thanks to all the data provided we could get more attention to this issue that it's now being investigated by our development team directly. This is great news, but please keep in mind this process can take some time.

In the meantime, if you noticed relevant information, or found a solution, please share it with us in this discussion. 🙏🔔

Thanks again for the contributions, patience, and understanding.

Best,

Carol 👩🏻‍🦰🌷

DCJ

TV 15.30.3 wouldn't let me connect to a Linux Mint 20.3 Una if the screen was locked. Downgrading to 15.18.4 worked - thanks

FF123456

https://community.teamviewer.com/English/discussion/comment/134092#Comment_134092

@cli644 This is a little offtopic here, but please note that you mixed "upgrade" and "downgrade" in your post. By trying the command mentioned above you basically found out that an outdated version of Teamviewer works for you (which you might want to avoid using however due to possible security reasons) while the current one does not.

You might want to create a different thread though instead of hijacking this one since your connection problem does not have anything to do with the topic dicussed here from what I can tell.

cli644

https://community.teamviewer.com/English/discussion/comment/134083#Comment_134083

I am usually never joining on any forums however

Could not connect from Android device and Windows and other Linux machines to that specific 15.30.3. Either it would get stuck on "Initialising session" from Windows to Linux and just drop the connection without any error message and from Android to Linux it would just hang forever until it times out. No difference weather using TV ID, VPN IP or LAN IP. Any other machines were working properly.

Therefore that sudo apt install teamviewer=15.18.4 solved the critical problem!

Upgrade to 15.18.4 successfully solves the problem that the latest defective downgrade 15.30.3 introduced (or as it appears even few versions before).

Best regards

FF123456

Thanks for the information @.Carol.fg. !

I have to report though that I already had that setting disabled.

However, while doing so I finally thought about the obvious thing to help you:

deleted all Teamviewer configuration data that I could find by searching my harddisk for "teamviewer", leaving only the data used by the APT package manager.
installed a clean Teamviewer 15.21.4 directly from your apt package source (I completely had forgotten that these sources offer all the old versions - no need for digging for old deb installers in ominous places :-) )
changed the log file in Teamviewer to log everything
started Teamviewer, checked if it reacted to my mouse, closed it again and moved the resulting the log files from /opt/teamviewer/logfiles/[my Login] to a safe location
then worked my way upwards through all the old versions that you offer in your "stable" package source until I found the first one that did not work: 15.22.3 (okay), 15.23.9 (okay), 15.24.5 (okay), 15.25.5 (not okay) and for sake of completeness 15.30.3 (not okay). I repeated the "open-check-close-save logfiles" process for each version.

This means: I can now safely say that a change that has been made between version 15.24.5 and 15.25.5 causes these mouse problems.

Then, I checked the logfiles:

gui.log shows some errors, but it is identical for both version 15.24.5 and 15.25.5.
startup.log has only the Teamviewer version number as a difference, so I left these out
Teamviewer15_logfile.log however shows one interesting error in line 29 of the logfile that might help your R&D: "unable to increase the thread priority for thread 7fef663fc700". This error (with differing thread id's) occurs on every version that I tested here and that works on my computer, while it does not occur on the versions that do not work as they should. I have no clue however what that thread might do, but if it does not throw this error, it seems to have a negative effect on mouse detection.

I have attached the logfiles for version 15.24.5 and 15.25.5 for your convenience als PDF files, with the relevant line in the "Teamviewer15_Logfile" files marked and comments added.

gui_teamviewer_15.24.5.log.pdf

gui_teamviewer_15.25.5.log.pdf

startup_teamviewer_15.24.5.log.pdf

startup_teamviewer_15.25.5.log.pdf

TeamViewer15_Logfile_teamviewer_15.24.5.log.pdf

TeamViewer15_Logfile_teamviewer_15.25.5.log.pdf

Edit: if you find it helpful, I can provide you with the log files for the other versions I tested as well.

.Carol.fg.

Hello @FF123456,😃

Thanks for the additional information! I appreciate it! 🙌✨

I could gather some information too in the meantime... but nothing concrete just yet...

... Would you mind testing it?

So basically a new feature that was recently implemented had some reports of "connection issues" and "TeamViewer stop responding". The feature is Play computer sounds and music

I wish I could just say for you to open the Options and check if it's marked or not, but since GUI is not clickable, you would need to try downgrading to version 15.18.4 using the command line below → uncheck this feature → update TeamViewer to the newest version again, and check if it's any better.

(for Debian-Ubuntu-Linux mint-Deepin-Raspberry Pi only)

the command to downgrade TeamViewer is:

sudo apt install teamviewer=15.18.4

if you have the TeamViewer Host then it be

sudo apt install teamviewer-host=15.18.4

Once again I appreciate your kindness and patience during the resolution of this issue. 🌷

Best,

Carol

FF123456

https://community.teamviewer.com/English/discussion/comment/133878#Comment_133878

Hello @.Carol.fg., thank you for your continued investigation.

In the meantime, I tested the new version 15.30.3 and could narrow down the topic a little. The basic problem (program does not react to mouse interaction) persists, so it is back to 15.21.4 for me.

But I found the following thing: Even if the Teamviewer window seems to be unresponsive, it does work perfectly well - when the program window is active, you can use the keyboard to switch between the GUI elements and e.g. open the menu or type in a partner id. This means that Teamviewer really only fails to catch any mouse click events on Mint 20.3 Cinnamon here.

Maybe this helps a little. If there is something I can do from my side to support your developers, please do not hesitate to contact me.

I also tried to start Teamviewer with Xephyr in a separate X session to check if maybe some Cinnamon settings cause the problem, but failed miserably - Teamviewer seems to happily ignore the DISPLAY environment variable set in the shell and thus starts in the main X session (i.e. my Cinnamon Desktop) nevertheless.

.Carol.fg.

Hello @FF123456 and @CedricGannet ,

Thank you for the additional feedback, and detailed information! 💯

I firstly would like to apologize for any possible misunderstanding on my part.

👉 I attempted to contact our support team once again regarding this issue.

However, my colleagues in the support department could not reproduce the issue reported. They did multiple tests and no issue was found on TeamViewer GUI, connectivity, nor with the remote control. 🤔

💭 At this point, I can only think that it may be a thirds party app (like a bank app), firewall, or antivirus blocking TeamViewer and freezing the GUI... Regarding connectivity issues, it could be caused by a great variety of issues including IPv6 and DNS.

I know you all looking for a solution, and I appreciate every single comment with further details, however, this issue doesn't seem to be affecting all users, so we will need to keep investigating. 🔍

If you get to the bottom of this issue during this time being, I would highly appreciate if you could share the solution with others here in the Community. 🔔🌟

We will keep in touch.

Best,

Carol

FF123456

https://community.teamviewer.com/English/discussion/comment/133820#Comment_133820

Hello @.Carol.fg. and thanks for the welcome!

LinuxMint 20.3 does not use Wayland, so I can safely exclude that possible reason (I also doublechecked to be 100% sure, my session type is reported as "X11").

Your second hint tells me I might have written my explanation in way that it is misunderstandable - with "starting fine but does not register any mouse interaction at all" I meant that I can start the teamviewer program on my computer and the program window looks perfectly fine, but when I try to do interact with it (i.e. try to click onto anything in the Teamviewer program window with the mouse - menu, "Partner ID" entry field, "Connect" button - in short any GUI elements), nothing happens. This is the behaviour mentioned in the beginning of the thread.

Thus, I am afraid I cannot even open the options menu you showed.

With the other posts here, it seems that the current versions of Teamviewer runs fine on LinuxMint 20.2 but does not run correctly for some reason on Mint 20.3.

CedricGannet

https://community.teamviewer.com/English/discussion/comment/133148#Comment_133148

I'm Afraid I had the same problem on version 15.29.4. I'm running Linux Mint 20.2 as follows:

-Version-

Kernel : Linux 5.4.0-110-generic (x86_64)

Version : #124-Ubuntu SMP Thu Apr 14 19:46:19 UTC 2022

C Library : GNU C Library / (Ubuntu GLIBC 2.31-0ubuntu9.9) 2.31

Distribution : Linux Mint 20.2

I had version 15.29.4 installed and it wasn't working as a client in a way very similar to what Gigi183 described. After much investigation, I decided to go back to 15.27.3. Not easy, as I couldn't find a way of downloading the earlier version. Eventually, I googled "teamviewer_15.27.3_amd64.deb" and downloaded it from a mirror (VERY DANGEROUS). I uninstalled and purged the later version and nervously installed the earlier. It worked fine.

I then upgraded back to version 15.29.4 and IT STILL WORKED! There is certainly an issue here but I suspect a clean re-install would have sorted the problem.

.Carol.fg.

Hello @FF123456 ,

Welcome to the TeamViewer Community! 🎉

So if it is "starting fine, but does not register any mouse interaction at all" this sounds a bit different from the previous issue where the connection was not happening.

👉 Do you have Wayland on? Did you try to disable it and use the Xorg?

(TeamViewer v15.29.4 had improvements with Wayland, but there are still a few issues reported.)

👉 Also, please make sure that the configuration on the Advanced Options on both devices (the one that starts the connection, and the one that receives the connection) is set to Full access. Please also consider checking on the TeamViewer toolbar if Disable remote input is not checked.

Let me know how if you need further help 😊

Best,

Carol

FF123456

Sorry for reactivating this topic but I fear I have to report the exact same problem on LinuxMint 20.3, but the latest version still does not cure it. Any Teamviewer version higher than 15.21.4 starts fine, but does not register any mouse interaction at all.

Tested with Teamviewer 15.29.4 (both .deb and the tar file and the host), 15.25.5 (.deb file only) and, 15.21.4 (.deb file and host) and 15.16.8 (again, .deb file only). I uninstalled the previous version in all cases but also treid to install 15.21.4 first and then upgrade to 15.29.4. A "sudo apt –fix-missing update" does not find any missing dependencies.

My system information:

System:    Kernel: 5.4.0-110-generic x86_64 bits: 64 compiler: gcc v: 9.4.0 
           Desktop: Cinnamon 5.2.7 wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una 
           base: Ubuntu 20.04 focal 
Machine:   Type: Desktop Mobo: ASRock model: B450 Gaming-ITX/ac serial: <filter> 
           UEFI: American Megatrends v: P3.70 date: 11/18/2019 
CPU:       Topology: 6-Core model: AMD Ryzen 5 2600 bits: 64 type: MT MCP arch: Zen+ rev: 2 
           L2 cache: 3072 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 81594 
           Speed: 1550 MHz min/max: 1550/3400 MHz Core speeds (MHz): 1: 1548 2: 1549 3: 1541 
           4: 1550 5: 1550 6: 1550 7: 1550 8: 1549 9: 1550 10: 1549 11: 1550 12: 1539 
Graphics:  Device-1: NVIDIA TU117 [GeForce GTX 1650] vendor: Micro-Star MSI driver: nvidia 
           v: 510.73.05 bus ID: 0a:00.0 chip ID: 10de:1f82 
           Display: x11 server: X.Org 1.20.13 driver: nvidia 
           resolution: 1280x1024~60Hz, 2560x1440~60Hz 
           OpenGL: renderer: NVIDIA GeForce GTX 1650/PCIe/SSE2 v: 4.6.0 NVIDIA 510.73.05 
           direct render: Yes 
Audio:     Device-1: NVIDIA vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 0a:00.1 
           chip ID: 10de:10fa 
           Device-2: AMD Family 17h HD Audio vendor: ASRock driver: snd_hda_intel v: kernel 
           bus ID: 0c:00.3 chip ID: 1022:1457 
           Sound Server: ALSA v: k5.4.0-110-generic 
Network:   Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel 
           bus ID: 08:00.0 chip ID: 8086:24fb 
           IF: wlp8s0 state: down mac: <filter> 
           Device-2: Intel I211 Gigabit Network vendor: ASRock driver: igb v: 5.6.0-k port: f000 
           bus ID: 09:00.0 chip ID: 8086:1539 
           IF: enp9s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           IF-ID-1: vmnet1 state: unknown speed: N/A duplex: N/A mac: <filter> 
           IF-ID-2: vmnet8 state: unknown speed: N/A duplex: N/A mac: <filter> 
Drives:    Local Storage: total: 2.29 TiB used: 711.40 GiB (30.4%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 PRO 512GB size: 476.94 GiB 
           speed: 31.6 Gb/s lanes: 4 serial: <filter> 
           ID-2: /dev/sda vendor: Samsung model: SSD 870 EVO 1TB size: 931.51 GiB speed: 6.0 Gb/s 
           serial: <filter> 
           ID-3: /dev/sdb vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB speed: 6.0 Gb/s 
           serial: <filter> 
           ID-4: /dev/sdc type: USB model: USB007 mini-USB6BU size: 28.0 MiB serial: <filter> 
Partition: ID-1: / size: 139.17 GiB used: 55.21 GiB (39.7%) fs: ext4 dev: /dev/nvme0n1p5 
           ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p6 
Sensors:   System Temperatures: cpu: 48.6 C mobo: N/A gpu: nvidia temp: 41 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 30% 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/anonbeat-guayadeque-focal.list 
           1: deb http: //ppa.launchpad.net/anonbeat/guayadeque/ubuntu focal main
           No active apt repos in: /etc/apt/sources.list.d/appimagelauncher-team-stable-focal.list 
           Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
           1: deb https: //ftp.halifax.rwth-aachen.de/linuxmint una main upstream import backport
           2: deb http: //ftp.halifax.rwth-aachen.de/ubuntu focal main restricted universe multiverse
           3: deb http: //ftp.halifax.rwth-aachen.de/ubuntu focal-updates main restricted universe multiverse
           4: deb http: //ftp.halifax.rwth-aachen.de/ubuntu focal-backports main restricted universe multiverse
           5: deb http: //security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
           6: deb http: //archive.canonical.com/ubuntu/ focal partner
           Active apt repos in: /etc/apt/sources.list.d/signal-xenial.list 
           1: deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https: //updates.signal.org/desktop/apt xenial main
           Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
           1: deb [arch=amd64] https: //repo.skype.com/deb stable main
           Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
           1: deb https: //linux.teamviewer.com/deb stable main
           Active apt repos in: /etc/apt/sources.list.d/termius.list 
           1: deb [arch=amd64] https: //deb.termius.com squeeze main
Info:      Processes: 419 Uptime: 5h 52m Memory: 31.35 GiB used: 4.91 GiB (15.6%) Init: systemd 
           v: 245 runlevel: 5 Compilers: gcc: 9.4.0 alt: 7/9 Client: Unknown python3.8 client 
           inxi: 3.0.38

.Carol.fg.

Hello @KMNug53 ,

Thank you for your feedback and for testing it in your system as well! 💯✨

I am grateful the issue got corrected on our side with version 15.29.4.

@Gigi183 you may want to try v15.29.4 as well.

Please let us know if it also corrected the connectivity on our side. 🍀🤞

👉 This new version also had a few improvements for compatibility with Wayland. You can read more about it here:

https://community.teamviewer.com/English/discussion/122410/teamviewer-support-on-wayland-experimental-state

Best,

Carol 🙋‍♀️🌷

KMNug53

15.29.4 appears to have resolved the issue. TV on Mint now connects to Windows as expected.

KMNug53

Just to confirm Gigi183's findings.

Mint Kernel: 5.4.0 - 109, TeamViewer 15.28.6, Windows 10 Home 21H2 OS build 19044.1645

With 'Incoming LAN connections' set to 'accept exclusively':

Windows 10 can connect to Mint.

Mint cannot connect to Windows 10 (no error thrown) Clicking 'Connect' yields no response.

With 'Incoming LAN connections' set to 'accept':

Windows 10 can connect to Mint

Mint cannot connect to Windows 10 (error msg: 'Could not connect to partner')

Gigi183

One more for anyone who finds this: do a google search for how to install specific versions of a package. You can find what you need to roll back teamviewrer to 15.27.3 from the command line and then hold it so that it doesn't update.

Gigi183

Ok. Just FYI, you almost certainly have a problem on your end. My office setup is like this:

A Windows machine

A Linux machine running Fedora

A Linux machine running Linux Mint

I use teamviewer, exclusively with LAN connections, to control each computer from the other, though the typical workflow is to target the Windows machine from either the Fedora or Mint machine.

Here's what works: Fedora (15.27.3) can control Mint (15.28.6). Fedora (15.27.3) can control Windows (15.28.4). Mint (15.28.6) cannot connect to anything. I updated Fedora to 15.28.6, and that broke the ability of Fedora to control anything - the exact same problem existed on the Fedora box on 15.28.6 that exited on the Mint box: I click on the connect button and Teamviewer does not respond. There is no indication that the connection is failing. It is simply not getting going.

Then I downgraded every computer to 14 and I'm back to full functionality. I will wait a few update cycles before I try version 15 again.

.Carol.fg.

Hello @Gigi183 ,

Thanks for the additional feedback!

I could not simulate the issue on my side. 🤔

I also verified that our support team did not receive similar cases reporting this issue... Therefore, I'm not to sure why you're having troubles with the GUI on the newest version. (On our website we offer the newest version of any major version which the services are still supported.)

I'm grateful that v14 is working on your system, and I agree with you that it makes sense use it for now.

If I get any new updates about what could be causing you this issue, I will let you know 😉

If in the mean time you get to a solution, please share here with us. This may be of great help for other users 😃🍀

Best,

Carol 🙋‍♀️