Arch Linux User Repository

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.

I also tried the hack that was linked here earlier however that didn't work for me. It looks like the the one linked earlier, there are still permissions issues.

Ah thanks for explaining.

Here's my diff to not hardcode the electron version:

modified   PKGBUILD
@@ -2,8 +2,9 @@
 # Contributor: huyizheng
 # Contributor: johnnyapol <arch@johnnyapol.me>
 # Based off the discord community repo PKGBUILD by Filipe Laíns (FFY00) <lains@archlinux.org>
-pkgname=discord_arch_electron
 _pkgname=discord
+_electron=electron19
+pkgname=${_pkgname}_arch_electron
 pkgver=0.0.20
 pkgrel=1
 pkgdesc="Discord (popular voice + video app) using the system provided electron for increased security and performance"
@@ -12,7 +13,7 @@ provides=('discord')
 conflicts=('discord')
 url='https://discord.com'
 license=('custom')
-depends=('electron19')
+depends=("${_electron}")
 makedepends=('asar')
 optdepends=('libpulse: Pulseaudio support'
             'xdg-utils: Open files')
@@ -26,7 +27,7 @@ sha512sums=('720bc8a8b61cbbe3566c34065f9831571da121d210e3f2876c34cb964d60bab33f8
             SKIP)

 prepare() {
-  sed -i "s|@ELECTRON@|electron19|" discord-launcher.sh
+  sed -i "s|@ELECTRON@|${_electron}|" discord-launcher.sh
   sed -i "s|Exec=.*|Exec=/usr/bin/$_pkgname|" Discord/discord.desktop
 }

@Thaodan: you can use the electron19-flags.conf file (this still works) but it applies to all electron apps using that version. For example, I set some flags for Discord that are breaking VSCode (both use electron19 currently).

Why not use existing electron-flags${version+-$version}.conf?

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.

Opening a stream does make Electron dump and Discord reloads.
Started today (2022-09-13) for me.

Traces to av_buffer_get_opaque (libavutil.so.57 + 0x22034).

Recently Discord got an in-app update that interacted with Kwallet for me, so I'm not sure if this is because they're doing something with Linux suddenly or if it's just a fluke; however, I can't imagine what that fluke would be, if so, because I don't think Windows has a secrets keyring?

Funny though, they do this but then still don't have Linux-hosted stream audio working...

Having the same problem as @kode54. [WebContents] crashed (reason: crashed, exitCode: 139)... reloading after opening a stream or join a video call. With community/discord everything works. The problem appeared about a month ago, probably just after updating to 0.0.19

anyone know if the bundled electron comes with upstream discord uses ffmpeg4 or ffmpeg5 library versions? 0.0.136 working for me with a custom electron15 builded against ffmpeg4 instead of ffmpeg5 like arch do. with zero workgrounds like disable the openh264 acceleration or something (the infamous crash when join to a stream)

greetings

EDIT 0.0.138 still working with electron15(with ffmpeg4), so, I just keep it

EDIT2: tested with electron20 with ffmpeg4.4. get mic error (can't enable it). seems a problem with sdp and webrtc things

[1737753:0913/232750.263963:ERROR:sdp_offer_answer.cc(758)] Failed to set remote answer sdp: The order of m-lines in answer doesn't match order in offer. Rejecting answer.

EDIT3: tested with electron19 with ffmpeg4.4. the mic works, but i cant share my display. tested in X11 and wayland mode

EDIT4. tested electon 18, 17 and 16 with ffmpeg 4.4. only 16 and 15 versions works everityng without any workground

Well it looks like the openasar devs have come across some of the same fixes I did. It looks like they have it working on electron 20 as well, and there aren't any open issues about the mic not working on their git repo. Here's a blog post on electron20:

https://goose.icu/discord-electron-20/

I downloaded openasar and tried it to see what would happen, and the mic still doesn't work, but I get some error messages that don't appear with electron19. I'm not sure if this is relevant to the stock app.asar, but it might be worth looking at.

97681:0901/104247.716386:ERROR:ev_root_ca_metadata.cc(290)] Failed to register OID: 0
(node:97681) UnhandledPromiseRejectionWarning: Error: Script failed to execute, this normally means an error was thrown. Check the renderer console for the error.
    at node:electron/js2c/sandbox_bundle:57:405
    at EventEmitter.<anonymous> (node:electron/js2c/sandbox_bundle:45:375)
    at EventEmitter.emit (node:electron/js2c/sandbox_bundle:112:3752)
    at Object.onMessage (node:electron/js2c/sandbox_bundle:37:756)
(Use `electron-20 --trace-warnings ...` to show where the warning was created)
(node:97681) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)