-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Core Dump on wayland #6260
Comments
Can confirm, I also get a coredump with a segfault. The bug is not always immediate, I even got one time where it was seemingly fine. Platform InfoSignal Version: Signal 6.3.0 Operating System: Debian testing with swaywm compositor Linked Device Version: N/A |
Do you get a chance to submit a crash report to Signal when you restart? Or maybe you could try starting it in wayland, getting the crash, and then starting it under X and then you could submit the crash report to us? |
I can confirm as well. I've been able to generate a coredump file, @scottnonnenberg-signal do your want me to upload it somewhere? Debug log from application start right after the crashing instance: https://debuglogs.org/desktop/6.4.1/66eb78545db94b52e4acd98264ce444ab915bd96b2986d0dc15f4d9cf0c5df2f.gz Platform info
|
Related: #6247 |
@samsapti Ideally what we'd get from you is a crash dump from within Signal Desktop. It's only available on beta installs, but it's much more likely that we'll get useful information out of it. If you start up, crash, and then start up successfully, it should give you the ability to upload it. |
Here is a crash dump from my system: Signal version: 6.9.0-beta.1 |
@tpeacock19 Thanks for that crash dump - that gives us a call stack we can work with! |
For anyone looking for a workaround: signal-desktop 6.2.0-1 does not have this issue on Wayland. For project maintainers: would it be helpful to generate more crash dumps? I'd be happy to do that if it helps. :) |
I updated my
I don't have X on my system or an easy way to get X set up to get debug logs. I've attached the coredump system log as well. |
Intermittent crashes in Wayland on startup persist with 6.18.1 |
I'm seeing this very consistently under sway on Arch with signal version
It makes Signal basically unusable for me. I have to start it up ~10 times to get one session to stick. |
@jamesob I have observed two kinds of crashes:
The first kind can be solved by sticking with 6.18.1 and that isn't a solution, just what I and other Wayland users do to get by. It can take multiple attempts to start 6.18.1 as well, but usually less than 5. |
Sway workaround for startup crash:
Found the workaround here: element-hq/element-desktop#1026 (comment) |
Same problem on river/wayland, same fix as for Sway:
|
The issue also exists using GNOME 45.0 (Arch Linux x86_64, up-to-date, both on the regular Linux and Linux LTS kernel). For me, the issue only started getting bad about maybe 2-4 weeks ago - did not have the crashes as often previously. Signal however works fine when using XWayland. Signal is at version 6.34.0 from the Arch Linux repos. |
I think this may be related to whether the compositor has the window marked as maximized or not. I'm running Sway. When running under XWayland, toggling the window between floating or not produces log lines like the following:
where |
Bug Description
When launching signal with the arguments:
--enable-features=UseOzonePlatform --ozone-platform=wayland
, it shows the window briefly and then sometimes coredumps.Steps to Reproduce
signal-desktop --enable-features=UseOzonePlatform --ozone-platform=wayland
Actual Result:
It coredumps
Expected Result:
It runs fine
Platform Info
Signal Version:
Signal 6.3.0
Operating System:
EndeavourOS with hyprland compositor
Linked Device Version:
N/A
Link to Debug Log
Couldn't copy the URL somehow. See the attached file for the debug log instead.
debuglog.txt
The text was updated successfully, but these errors were encountered: