| Git Clone URL: | https://aur.archlinux.org/discord_arch_electron.git (read-only, click to copy) |
|---|---|
| Package Base: | discord_arch_electron |
| Description: | Discord using system provided electron for increased security and performance |
| Upstream URL: | https://discord.com |
| Keywords: | chat discord discord-stable discordapp electron video voice |
| Licenses: | custom |
| Conflicts: | discord |
| Provides: | discord |
| Submitter: | johnnyapol |
| Maintainer: | Zoddo (Thaodan, SunRed) |
| Last Packager: | Zoddo |
| Votes: | 197 |
| Popularity: | 4.27 |
| First Submitted: | 2020-05-19 23:51 (UTC) |
| Last Updated: | 2024-12-17 20:22 (UTC) |
This issue seems to be fixed with electron28.
Sadly we will have to wait until Discord updates their bootstrap code (they access require.main which isn't available anymore since electron switched their entry point to ESM in electron28). I tried to patch it, but they have too many references to require.main to do that easily.
I'll downgrade the package to electron26 for now.
@Zoddo: I'm on Wayland (here's a gdb backtrace: https://pastebin.com/ahJJRKem)
@DodoGTA: Interesting, I don't repro. Are you on X11 or Wayland? Do you have the exact error at hand?
It looks like Discord has to be downgraded to electron26 (27 crashes after some time with some ANGLE error and 28 doesn't work at all likely because of some ESM thing)
Sometimes it doesn't crash and I can successfully choose a window/screen, but it's loading forever.
Works for me on Wayland, but crashes when I try to screenshare (KDE Plasma 5, XDG-Desktop-Portal window opens for like a second and Discord crashes).
Screenshares work fine when I switch to electron22 in /bin/discord, even through xwaylandvideobridge.
@ItachiSan: Thanks for the reminder. I'm a bit blind currently as I don't use wayland on my machine, and I need to rebuild my test environment. I've reverted the package to electron24 for now, and will investigate once I can test on wayland again :)
@Zoddo & @Thaodan: I am following up my previous message regarding Wayland support.
Discord works with Electron 25 on XWayland but not Wayland. Discord works with Electron 24 on both XWayland and pure Wayland. I would suggest using Electron 24 for the time being. Let me know if you want anything for troubleshooting :)
Just wanted to come in and say thank you <3
This has solved the scrolling issues I've had for years and keeps forcing me to go back to Windows every now and then when I get fed up of it
@ItachiSan: Or the other way around the wrapper script discord-flags.conf is redundant if the flags apply to discord.
Pinned Comments
SunRed commented on 2024-06-09 20:34 (UTC)
After a chat with @Zoddo and me just taking too long to come back to this, there should everything now be included that was in my old
discord-electronpackage some migrated from (Krisp patcher, Wayland, autostart fix). Additionally I replaced the scrappy rizin patcher with a Python script someone from the nix community kindly made available.Instead of checking against a checksum to know whether the Krisp binary was patched the script is run on every start of the client that results in slightly longer start times but has the advantage that we don't have to update the package if Discord ever silently updates the binary between client updates over their modules api.
Cheers
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.