FS#73269 - signal-desktop segfaults under wayland/sway from v5.27 onwards

Attached to Project: Community Packages
Opened by Jonas Große Sundrup (cherti) - Wednesday, 05 January 2022, 21:58 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 05 January 2022, 22:00 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
signal-desktop 5.27 breaks Wayland support by mostly (95+% of cases) segfaulting right on startup, at least under sway. If it doesn't segfault on startup, it does so when opening the first chat, although it is unclear what the actual underlying trigger is.

The issue has been reported upstream here:
https://github.com/signalapp/Signal-Desktop/issues/5719

but has been closed due to not being a supported platform.

I have used the PKGBUILD from the community repositories to build signal-desktop 5.28-beta1 as well and can confirm the issue. However, I am not familiar enough with the platform and tooling to claim that I have built it from source without any instructions, so I'm afraid I this might not qualify as a reason to reopen for upstream.

Additional info:
* package version: 5.27, 5.28-beta1
* stacktrace: see attached file


Steps to reproduce:
1. upgrade to Signal 5.27
2. run signal-desktop --enable-features=UseOzonePlatform --ozone-platform=wayland under sway in a terminal (to see the stacktrace)
3. observe the application segfaulting
4. if it didn't segfault, try to open a chat or return to 2.
This task depends upon

Closed by  Antonio Rojas (arojas)
Wednesday, 05 January 2022, 22:00 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#73266 

Loading...