Linux - downgrade to version 15.27.3

FF123456 · January 2023

@.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?

.Carol.fg. · January 2023

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 · January 2023

@.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. · January 2023

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 · January 2023

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. · January 2023

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 👩🏻‍🦰🌷

Linux - downgrade to version 15.27.3

Comments

Categories

This Week's Leaders