Open Gamertech opened 4 months ago
This appears to be because some discord blobs have the executable stack flag set, which they do not appear to require. On 0.0.57, it also causes discord_voice.node to trigger the "Well, it looks like your Discord installation is corrupt." banner.
The flag can be unset using execstack(8), by first querying every ELF in ~/.var/app/com.discordapp.Discord/
with execstack -q
, and then running execstack -c
on every discord_<module>.node
file that reports the flag as being set (X
marker). Of course, discord should probably just fix their blobs so that they don't have the flag in the first place.
After updating the flatpak yesterday, Discord now triggers execheap on the first load and fails to start.
Previous recent updates it crashed on first load then works fine after that till next update, so possibly it crashed in a different way to usual and SELinux doesn't like it?