If you are still using the --ozone-platform=wayland
, it looks like this should be replaced by --ozone-platform-hint=auto
with electron20+.
If this doesn't fix the segfault, could you get a coredump (in most case, systemd will store one for you, check coredumpctl list
), open it with gdb
and print the backtrace (bt
command)?
This should at least tell us if the segfault is coming from electron itself, or from a Discord's native module (last time I checked, Discord modules included some symbols).
Pinned Comments
Zoddo commented on 2022-09-15 17:54 (UTC) (edited on 2023-03-31 17:24 (UTC) by Zoddo)
Starting with 0.0.26-1 (2023-03-31):
Starting with 0.0.20-1 (2022-09-15):
$XDG_CONFIG_HOME/discord-flags.conf
: this works likeelectron-flags.conf
, you can set in this file the command line flags you want to pass to electron when running Discord (there are some useful flags in the wiki, especially if you are experiencing lag in the Discord UI).FAQ
Discord requires an update, but this package isn't yet updated
Check the wiki.
The Discord UI is lagging
Try to add the flags recommended in the wiki in
$XDG_CONFIG_HOME/discord-flags.conf
.Krisp not working
This is an issue that will likely never be fixed for this package. The Krisp module checks if Discord binaries are signed by Discord, which is not the case with this package.
See this comment and this GitHub issue for more details and possibles workarounds.