element-desktop: Nightly (using electron 25.1.x) crashes on launch on wayland (sway)

Steps to reproduce

Launching element-desktop-nightly in wayland native mode on sway fails since around a week - most likely since 3d2006ca50cbc11f07d2356324a05f0e92b4670c (upgrades electron from 24.x to 25.x). Electron is now at 25.1.0.

In order to reproduce, run:

element-desktop-nightly --enable-features=UseOzonePlatform --ozone-platform=wayland

Outcome

The application immediately crashes, the logs tell:

Enabling Sentry with dsn=https://029a0eb289f942508ae0fb17935bd8c5@sentry.matrix.org/6 environment=nightly
Starting auto update with base URL: https://packages.element.io/nightly/update/
Auto update not supported on this platform
Fetching translation json for locale: en_EN
Changing application language to en-us
Fetching translation json for locale: en-us
Resetting the UI components after locale change
Resetting the UI components after locale change
zsh: segmentation fault  element-desktop-nightly --enable-features=UseOzonePlatform 

This issue is similar to #873, but doesn’t require any fancy dual monitor config and also doesn’t yield the same error message, therefore I filed a separate issue. Also, it is worse, as there is no workaround here (apart from running in xwayland mode).

Operating system

Debian Linux (Bookworm)

Application version

Element nightly 2023061901

How did you install the app?

element.io deb repository

Homeserver

matrix.org

Will you send logs?

No

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Reactions: 4
  • Comments: 19 (2 by maintainers)

Most upvoted comments

this fixed it for me in the sway config: for_window [app_id="Element"] floating enable

It looks like Electron 26 has fixed the issue. No more crashes for me. I’ve also experienced problems with tutanota but they also updated to 26 and it works flawlessly now. 😃

Thank you @Stunkymonkey, that workaround works for signal-desktop 6.28.0 too!

maybe this bugreport is also relevant or helps finding the root cause: ostreedev/ostree#2900

This is another unrelated bug that happened at the same time.