Starting screen sharing crashes the app in element call

[JMoVS]

Steps to reproduce

1. Open screensharing dialog
2. switch between window and full screen
3. Sometimes it just crashes the whole app then

Outcome

What did you expect?

element not crashing

What happened instead?

crash

Operating system

No response

Application version

1.11.80

How did you install the app?

No response

Homeserver

No response

Will you send logs?

Yes

[florianduros]

Hi !
Which element app are you using (https://element.io/download) ?
And how did you install the app?

Thanks

[JMoVS]

I'm using:

Version von Element: 1.11.80
Krypto-Version: Rust SDK 0.7.2 (7a21514), Vodozemac 0.7.0

downloaded from the website, auto updated.

the crash is when using the experimental element call, not the legacy element call functionality.

[JMoVS]

has happened a couple of times to me so not a one-off crash

[Destinyg133]

Happens to me aswell

[hellfire103]

This is happening to me, too. I got the following error output when I clicked the share screen button:

[12483:1020/155138.172949:ERROR:screen_capture_portal_interface.cc(48)] Failed to request session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[12483:1020/155138.172966:ERROR:base_capturer_pipewire.cc(81)] ScreenCastPortal failed: 3
(node:12483) UnhandledPromiseRejectionWarning: Failed to get sources.
(node:12483) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
[12548:0100/000000.206940:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
[12548:0100/000000.617104:ERROR:gpu_channel.cc(503)] Buffer Handle is null.
[1]    12483 segmentation fault (core dumped)  element-desktop --enable-features=WebRTCPipeWireCapturer

Of course, I am running the nightly version under Wayland on Arch Linux, so it's impressive anything works for me.

[pjaap]

Can confirm the crash on a freshly upgraded Debian Trixie with Plasma 6 on Wayland. Before, with Plasma 5 and X11, there were no issues. I get the Wayland screen share selection dialog, but selecting a window/screen ends up opening the dialog again. After the third trial, Element Desktop crashed.

PS: Same thing happens to a college of mine with Wayland. Now that KDE uses Wayland by default, this issue will become critical.

Another edit: Screen sharing in Firefox works btw. So not a general problem with screen sharing under Wayland.

Version von Element: 1.11.86
Krypto-Version: Rust SDK 0.7.2 (517d99b), Vodozemac 0.7.0

[pjaap]

Probably related to #1750

[MaFreiberger]

Same problem. Using Element flatpak in KDE Fedora under wayland.
It's impossible to use any form of Screensharing. No matter if i try to share the whole Desktop or a Window.

The screen sharing dialog appears with all possible options (whole screen, list of all open windows) but clicking on any of them has no effect.
As soon as i close the screen sharing dialog window, the whole App crashes and i need to restart it. Sometimes it also says that the App is already running even no window of it or icon in the taskbar is shown.
After restarting the App my (external USB) cameras mic is then not working any more, i need to switch on the camera video one time to get the camera mic working again.

[Thatoo]

Could we close in favor of #1750 ?