Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Starting screen sharing crashes the app in element call #1913

Open
JMoVS opened this issue Oct 10, 2024 · 5 comments
Open

Starting screen sharing crashes the app in element call #1913

JMoVS opened this issue Oct 10, 2024 · 5 comments
Labels
A-Electron A-Element-Call Group calls via Element Call A-VoIP O-Occasional Affects or can be seen by some users regularly or most users rarely O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Critical Prevents work, causes data loss and/or has no workaround T-Defect Z-Labs

Comments

@JMoVS
Copy link

JMoVS commented Oct 10, 2024

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

@JMoVS JMoVS added the T-Defect label Oct 10, 2024
@dosubot dosubot bot added A-Element-Call Group calls via Element Call O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Critical Prevents work, causes data loss and/or has no workaround labels Oct 10, 2024
@florianduros
Copy link
Member

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

Thanks

@JMoVS
Copy link
Author

JMoVS commented Oct 10, 2024

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
Copy link
Author

JMoVS commented Oct 10, 2024

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

@t3chguy t3chguy transferred this issue from element-hq/element-web Oct 10, 2024
@dosubot dosubot bot added A-Electron A-VoIP O-Occasional Affects or can be seen by some users regularly or most users rarely labels Oct 10, 2024
@Destinyg133
Copy link

Happens to me aswell

@hellfire103
Copy link

hellfire103 commented Oct 20, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Electron A-Element-Call Group calls via Element Call A-VoIP O-Occasional Affects or can be seen by some users regularly or most users rarely O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Critical Prevents work, causes data loss and/or has no workaround T-Defect Z-Labs
Projects
None yet
Development

No branches or pull requests

4 participants