Arch Linux User Repository

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-electron package 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

Starting with 0.0.26-1 (2023-03-31):

• Switched back to the main electron package (electron22)
• Watching cameras and streams is working again

Starting with 0.0.20-1 (2022-09-15):

• Bumped electron16 to electron19 (I still have blocking issues with electron20)
• Added support for $XDG_CONFIG_HOME/discord-flags.conf: this works like electron-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.

Discord 0.0.24 is out. Here is the diff. This is my first post, sorry if there are errors. It worked for me.

➜  discord_arch_electron git:(master) ✗ git diff --no-color --no-prefix --cached
diff --git PKGBUILD PKGBUILD
index 50e4989..eae33c8 100644
--- PKGBUILD
+++ PKGBUILD
@@ -6,7 +6,7 @@
 _pkgname=discord
 _electron=electron19
 pkgname=${_pkgname}_arch_electron
-pkgver=0.0.23
+pkgver=0.0.24
 pkgrel=1
 pkgdesc="Discord (popular voice + video app) using the system provided electron for increased security and performance"
 arch=('x86_64')
@@ -23,10 +23,10 @@ source=("https://dl.discordapp.net/apps/linux/$pkgver/$_pkgname-$pkgver.tar.gz"
         'discord-launcher.sh'
         'LICENSE.html::https://discord.com/terms'
         'OSS-LICENSES.html::https://discord.com/licenses')
-sha512sums=('d03b27180c95ca74c93323090ce5c1e4351577d27184cfbf5525439052505ba198fafbd4b1489f97ce4c103bc35d1cfb4cdb1c32fc9c80bc55e2373b7a894a39'
+sha512sums=('9e1aa15bc1b1d8ebd2819ba88e7c012c47966d7f150264e732c849d4f15023729f8de4e5a5eb999603fa6102a02313dbf7d178b33cfacca58018dcd214ed4e40'
             '6ca6dfbfb65bf4fec34aac4676f66bb602b5c4c3318fcc96236056d632c0c9af3c4eb775b491c2e722ed5de6a4c253677d6ee1a7be69e13045702fa3df8cf52f'
-            SKIP
-            SKIP)
+            '4be7cf0901f0235a5a90ffa29a5a4a33935459ebbf706f5fe2ad82a1af927deb589bdade9aedb980b8f6190809d3609b69c0fa5c8c2be420b48f858ee485100e'
+            'b667fdcfa9ffc767f91c995ce220da2fdfd096d96a2830dd035d276ea0deb19382e4691a93a6bb5906ca39af06d3f9eb60acaeef026c96282d6e8f987ac4d8db')

 prepare() {
   sed -i "s|@PKGNAME@|${_pkgname}|;s|@ELECTRON@|${_electron}|" discord-launcher.sh

Official Stable discord is now at electron 17, I will make some checks soon

Under wayland discord has window class (app ID, to be exact) "Electron". Which leads to issues like this one: https://bugs.kde.org/show_bug.cgi?id=453374

This does not happen with regular discord package but it's not clear if that's the issue with discord, electron, or something else.

@Zoddo I tried downgrading to Electron 16 with the method you provided but it didn't fix the issue.

@sbeve72: Sorry for the wall of text, but I wanted to clarify these points for everyone.

Regarding Krisp, sadly, I don't think it will ever work with this package. The discord_krisp module checks if the discord binary is signed by Discord (likely for licensing reasons). In the case of this package (using the system's electron), what ends up being verified is the electron binary, which is of course not signed by Discord.

The only way to workaround to this issue is to patch the discord_krisp module to bypass that signature check. Putting aside that I don't currently know any way to automate such patching, it's also a file that isn't packaged but dynamically downloaded by Discord in the user's home directory. Patching this file would therefore require some ugly hacks, like doing the patch in the launch wrapper script. But if we do that, what happens on the first launch when the module isn't yet downloaded, or later when Discord downloads an upgraded version? The result would be that Krisp would randomly stop to work until Discord is restarted (and the file patched again). That's unpredictable behavior.

--

Regarding crashes when watching a stream, the cause seems to be an incompatibility between the Discord H264 module (which is an already compiled native module) and the V8/nodejs version embedded by electron17+. Downgrading to electron16 fixes the issue. However, I want to avoid adding a dependency to another AUR package, unless absolutely necessary. That's why the package was updated to electron19 despite it breaking streams. A medium-term goal is also to be able to use a supported version of electron that still receives security updates (that's in the package description: "Discord [...] using the system provided electron for increased security…"). Downgrading to electron16 goes against this.

If you want to downgrade to electron16, changing the variable _electron=electron19 to _electron=electron16 in the PKGBUILD should be enough.

As an additional note, it looks like Discord has started some work to upgrade electron in their official build. This will hopefully come with fixes that make native modules compatible with newer electron versions.

--

I will update the pinned comment to summarize known issues and possible workarounds.

@Samega7Cattac Krisp setting doesn't show up in "Voice & Video" tab even with the latest PKGBUILD (with all cache removed).

Instead, I manually patched the Krisp binary in user dir (~/.config/discord/{version}/modules/discord_krisp/discord_krisp.node) as described in here, and this fixed the issue.

Krisp still doesn't work and today while trying to watch a friend's stream, it kept crashing. Are there fixes available for this? I already have the latest PKGBUILD and the icu package installed.

@Samega7Cattac icu package was already installed.

@haxibami Krisp should work since last package update, the binary can't be stripped for it to work and it was set by default now

Is there anyone successfully running Krisp noise suppression with this package? According to this issue, Krisp module may not load if Discord executable is not signed.