Arch Linux

0BADC0DE

Member

From: Regnum Utriusque Siciliae

Registered: 2018-02-21

Posts: 342

[SOLVED][KDE/Plasma/Wayland] TeamViewer v15.30.3 from AUR coredumps

I installed it from "aur/teamviewer 15.30.3-1".
The server starts up almost clean.
These are my daemon logs.
This is what my systemctl reports with "systemctl status teamviewerd". Please note the PID file warning/error.
I can see the teamviewerd server is up and running.
Then I start the client by cli with a simple "teamviewer" which is actually "/opt/teamviewer/tv_bin/script/teamviewer" with this variable setup:

QT_QPA_PLATFORM=wayland

The applications says this.
Then aborts with a core dump.
In "~/.local/share/teamviewer15/logfiles" I find:
- startup.log
- gui.log
- a file containing what is appears to be a call stack trace
- a bzip2-compressed code dump from /opt/teamviewer/tv_bin/TeamViewer

Reinstalling (obviously) doesn't help.
None of the comments in the AUR page seems to work or make any sense. The machine I need to reach has TV v15 too, but I cannot install anything there.
So rustdesk and the likes is not an option ATM.

Any hint?

Last edited by 0BADC0DE (2022-07-14 17:01:22)

---

Maybe Computers Will Never Become As Intelligent
As Humans. Surely They Won't Ever Become So Stupid.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,300

Re: [SOLVED][KDE/Plasma/Wayland] TeamViewer v15.30.3 from AUR coredumps

The GUI log  shows that the custom QT5 build included with teamviewer does not include wayland support, so drop that environment and use xwayland/switch that to xcb for starting teamviewer

Last edited by V1del (2022-07-14 14:54:53)

0BADC0DE

Member

From: Regnum Utriusque Siciliae

Registered: 2018-02-21

Posts: 342

Re: [SOLVED][KDE/Plasma/Wayland] TeamViewer v15.30.3 from AUR coredumps

The GUI log  shows that the custom QT5 build included with teamviewer does not include wayland support, so drop that environment and use xwayland/switch that to xcb for starting teamviewer

Still not working. No coredump and slightly different results in logs.

TeamViewer15_Logfile.log
gui.log
startup.log

Last edited by 0BADC0DE (2022-07-14 15:11:57)

---

Maybe Computers Will Never Become As Intelligent
As Humans. Surely They Won't Ever Become So Stupid.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,300

Re: [SOLVED][KDE/Plasma/Wayland] TeamViewer v15.30.3 from AUR coredumps

How are you starting your session? What's your output of

loginctl session-status

? FWIW it works just fine here on a KDE Wayland session started with SDDM. And I do faintly remember teamviewer throwing a fit if you don't have a session started by a display manager but it might also just be up to whether XDG_SESSION_TYPE is set to something useful.

A wait we see it in the log session type is set to tty. Try starting plasma with

XDG_SESSION_TYPE=wayland startplasma-wayland

Last edited by V1del (2022-07-14 15:37:44)

0BADC0DE

Member

From: Regnum Utriusque Siciliae

Registered: 2018-02-21

Posts: 342

Re: [SOLVED][KDE/Plasma/Wayland] TeamViewer v15.30.3 from AUR coredumps

In order.

This is the output of my loginctl session-status.

I cannot use SDDM as AFAIK Wayland is supported only in v0.20, while Arch only ships 0.18. I use aur/tbsm 0.6-1 instead.

For XDG_SESSION_TYPE I have:

$ echo $XDG_SESSION_TYPE
wayland

I start Wayland/KDE/Plasma via tbsm... I can try your suggestion later (my Arch box is my daily working device).
What I can see from the log, I am already actually using startplasma-wayland.

Last edited by 0BADC0DE (2022-07-14 15:49:31)

---

Maybe Computers Will Never Become As Intelligent
As Humans. Surely They Won't Ever Become So Stupid.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,300

Re: [SOLVED][KDE/Plasma/Wayland] TeamViewer v15.30.3 from AUR coredumps

The problem from this output is that your loginctl session considers the session type to be tty, which is why teamviewer assumes you are only in a tty. As for SDDM while it will start a xorg server for itself, it can start a wayland session just fine. You could also opt for sddm-git to get the native wayland support.

0BADC0DE

Member

From: Regnum Utriusque Siciliae

Registered: 2018-02-21

Posts: 342

Re: [SOLVED][KDE/Plasma/Wayland] TeamViewer v15.30.3 from AUR coredumps

The problem from this output is that your loginctl session considers the session type to be tty, which is why teamviewer assumes you are only in a tty. As for SDDM while it will start a xorg server for itself, it can start a wayland session just fine. You could also opt for sddm-git to get the native wayland support.

So, bottom line is that tbsp isn't setting up the session properly. Is it?

Will give a(nother) try to sddm, though.

UPDATE
With sddm v0.19 it works. I am disabling tbsm for now. Thanks.

Last edited by 0BADC0DE (2022-07-14 16:59:51)

---

Maybe Computers Will Never Become As Intelligent
As Humans. Surely They Won't Ever Become So Stupid.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,300

Re: [SOLVED][KDE/Plasma/Wayland] TeamViewer v15.30.3 from AUR coredumps

Pretty much, note that at least with the stable SDDM as included in the Arch packages there can be a bug where the shutdown is delayed when shutting down from a Wayland session unless you switch back to the TTY SDDM is on with Ctrl+Alt+F1 (since the wayland session will be started on TTY2 to grant control of the devices to the Wayland compositor)