-
-
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
[Wayland] Intermittent segfault crash on startup #6247
Comments
not sure if this is the same issue, but I can reproduce this behaviour on fedora sliverblue (since version 6.5.0):
|
Unfortunately we don't officially support Fedora Linux right now, so I'd advise reaching out to maintainers of the package to see if they can help. Thanks! |
Same thing happens on Archlinux. |
Using Signal 6.8.0 through Flatpak on a Void Linux musl-based installation, similar issues… |
@dumol Unfortunately we don't officially support the Flatpak installation technique, or Void Linux, at the moment. I'd recommend that you reach out to the folks maintaining that Flatpak installation technique, see if they can help you out. |
@scottnonnenberg-signal Thanks, but the idea was to document that the same issue manifests itself when running Signal under Flatpak. So there's really no reason to look for solutions somewhere else, anyone else affected should wait for Signal (or Electron?) to fix this, AFAICT. |
Also happening to me Signal-desktop manually launched with Segfault after 4-5 seconds, this is the full output
|
I can confirm I reproduce this on signal-desktop stable (6.9.0) on NixOS. |
Reproduces on signal-desktop 6.10.1 with:
kernel log
|
Intermittent segmentation faults happen with latest Signal - 6.15.0 on Debian 12 as well. |
Segmentation fault happens moments after the window pops up - version 6.15.0 on Alpine Linux edge (musl based). |
Wait a month until signal starts using electron 23 (see #6112), that should fix this posting logs is not really going to help unless you've compiled signal yourself with debugging symbols enabled and can post a full backtrace |
I found workaround for greater stability. |
For anyone interested, I had the same issue on Arch until 6.18.1-1, it works fine at last. Maybe it helps to identify the cause? |
I can't seem to reproduce anymore either. |
For anyone ending up here via search -- actually, it's not the package update, my own setup was faulty. Having the following commands executed (here: via hyprland config) makes it not segfault anymore:
|
Still crashes on me with the second line included (the first one I already had). |
Please let us know how Signal Desktop 6.20.0-beta.1 works for you - it is on a newer version of Electron. |
Thanks, I noticed 6.20.0-beta.1 and 6.19.0 share the same Electron version. Tried 6.20.0-beta.1 briefly then installed 6.19.0, both didn't crash for me yet. |
Archlinux, sway on Wayland, extra/signal-desktop updated to 6.20.1-1
I also remove No segmentation fault, but the windows is not showing 😭
|
@hacktivateit it starts minimized to tray, add |
@hacktivateit |
thanks again! updated command |
I see no tray icon, and manually inspecting my DBus session bus it doesn't show up as registered to either of the two
I have another helpful argument for you: if you try sharing your screen in a video call, Signal will immediately crash, unless you use |
@PhoenixClank Using |
It was fixed, but now in 6.23.0 startup crashes are back again |
6.23.0 included an upgrade to Electron v25.2 -- you might try a fix suggested in electron/electron#37531 and linked issues. |
Until it's resolved on upstream electron follow this comment for workarounds element-hq/element-desktop#1026 (comment) |
Strangely, adding
|
I have tried Element and Tutanota flatpaks which were crashing constantly for me too but they have updated to Electron 26 and they started working normally on wayland. Looks like Signal will have to update electron in order to stop crashing. |
Hi, this workaround is not working on my debian 12 on Sway, as I use this option already and Signal crashes when clicking on the tray icon ( happens ~ half the time). |
When no workaround helps, automation will always come to the rescue! Run this very sophisticated script in the morning and go brew yourself some coffee, by the time you are back you'll have a working Signal instance 😁 Sometimes it takes over 10 attempts for me to launch Signal, so this is a huge time saver 😉 #!/bin/bash
while true; do
# Launch the main instance - it will run in background if you don't use tray
signal-desktop > /dev/null 2>&1 &
pid=$!
# Launch a second instance - it will exit, bringing the main instance to foreground
sleep 1
signal-desktop > /dev/null
# Move mouse cursor over the Signal window to trigger an intermittent segfault
sleep 1
ydotool mousemove 3 0
# Check if the main process has crashed
sleep 1
if kill -0 $pid 2> /dev/null; then
echo "Signal has finally launched!"
exit 0
else
echo "Signal has crashed, let's try again..."
fi
done |
After recent update there is nothing intermittent anymore, it crashes every single time. Had to switch to running it under Xwayland. |
for anyone who didn't follow the link from @pm4rcin I wanted to write it explicitly here---for me at least, the issue seems to be with running signal in wayland with tiling (I run sway). Immediately pressing EDIT: ok, sometimes the window doesn't appear for some reason? but it seems running it under XWayland once and then launching it under wayland makes the window appear 👍 |
I can confirm that Signal doesn't crash when it's floating by default ( |
Well, this work on non-HDPI display on my laptop, but my desktop PC still crash! |
Adding info about my setup (not sure if this relevant): integrated laptop screen is HiDPI (4K, scale factor: 2), external screen is not (1440p, scale factor: 1). Still 100% crash chance to crash Signal when output is external display. |
To confirm, |
I jumped to conclusion because 6.36.0 crashed 99% of time for me, now it's occasional, but startup crashes are still there. |
Thanks, that's solved it! |
I can confirm this problem on Ubuntu 23.10—which is officially supported, right? I am also using sway. Previously it worked to start 2 or 3 times with
This works for me, but it is a ridiculous workaround. Why can't signal just publish a decent library that interfaces with its server and then let regular devs make a frontend in Qt or GTK that doesn't suck? |
It's finally fixed! :) Let's hope that electron won't introduce more regressions like that in the future. |
Hooray! |
Bug Description
Signal Desktop Beta v6.3.0-beta.1 crashes shortly after starting, when started with
--ozone-platform=wayland
, approximately 50% of the time.Steps to Reproduce
signal-desktop-beta --ozone-platform=wayland
Actual Result:
The Signal window briefly appears then disappears. On the next execution, the "Application crashed" dialog appears. (Note: This occurs ~50% of the time. The other 50% Signal does not crash.)
Expected Result:
Signal does not crash.
Output
Platform Info
Signal Version: 6.3.0-beta.1
Operating System: Debian GNU/Linux bookworm/sid with Linux 6.2.0-rc3
Linked Device Version: 6.8.2
Link to Debug Log
https://debuglogs.org/desktop/6.3.0-beta.1/desktop-crash-e227e80a9fa0d3629e04b5e5bc2da13ff2111d52190d804bad3fe883cf2f2612.dmp
The text was updated successfully, but these errors were encountered: