Package Details: discord_arch_electron 1:0.0.111-1

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: 201
Popularity: 1.71
First Submitted: 2020-05-19 23:51 (UTC)
Last Updated: 2025-09-24 17:57 (UTC)

Dependencies (8)

Required by (28)

Sources (3)

Pinned Comments

Zoddo commented on 2022-09-15 17:54 (UTC) (edited on 2025-09-17 23:08 (UTC) by Zoddo)

Starting with 0.0.55-2 (2024-06-09):
  • Added a patcher to make Krisp work with this package (kudos to @SunRed). You need to manually enable it (see the end of this message).
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 is not available
An optional patcher is provided in the package to make Krisp work. To enable it, make sure python-capstone and python-pyelftools are installed, then set PATCH_KRISP=true in $XDG_CONFIG_HOME/discord.conf.
After an update, you'll need to restart Discord once for the patch to apply (Discord downloads Krisp dynamically during startup, so it cannot be patched on the first start).

Please note that 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 the package does not have to be updated if Discord ever silently updates the binary between client updates over their modules api.

Latest Comments

1 2 3 4 5 6 .. 42 Next › Last »

andyl98 commented on 2025-09-21 07:33 (UTC)

I am still having the same error when trying to use my webcam that @fouilliez was having in April:

~/.config/discord/logs/renderer_js.log

[error] TypeError: window.createDiscordStream is not a function

Is there any solution besides using the regular Arch discord package?

JotaRata commented on 2025-09-15 06:58 (UTC) (edited on 2025-09-15 06:59 (UTC) by JotaRata)

Discord doesn't display the tray icon on KDE Plasma, the jorunal shows the following error:


discord[1214]: systemTray: Failed to create tray icon: Error: Invalid GUID format - GUID must be a string
discord[1214]:     at show (/home/jota/.config/discord/0.0.109/modules/discord_desktop_core/core.asar/app/systemTray.js:216:16)
discord[1214]:     at setTrayIcon (/home/jota/.config/discord/0.0.109/modules/discord_desktop_core/core.asar/app/systemTray.js:148:5)
discord[1214]:     at IpcMainImpl.<anonymous> (/home/jota/.config/discord/0.0.109/modules/discord_desktop_core/core.asar/app/systemTray.js:68:62)
discord[1214]:     at IpcMainImpl.emit (node:events:519:28)
discord[1214]:     at IpcMainImpl.emit (node:domain:489:12)
discord[1214]:     at Session.<anonymous> (node:electron/js2c/browser_init:2:106370)
discord[1214]:     at Session.emit (node:events:519:28)
discord[1214]:     at Session.emit (node:domain:489:12)
discord[1214]: systemTray: Failed to create tray icon: Error: Invalid GUID format - GUID must be a string
discord[1214]:     at show (/home/jota/.config/discord/0.0.109/modules/discord_desktop_core/core.asar/app/systemTray.js:216:16)
discord[1214]:     at setTrayIcon (/home/jota/.config/discord/0.0.109/modules/discord_desktop_core/core.asar/app/systemTray.js:148:5)
discord[1214]:     at IpcMainImpl.<anonymous> (/home/jota/.config/discord/0.0.109/modules/discord_desktop_core/core.asar/app/systemTray.js:68:62)
discord[1214]:     at IpcMainImpl.emit (node:events:519:28)
discord[1214]:     at IpcMainImpl.emit (node:domain:489:12)
discord[1214]:     at Session.<anonymous> (node:electron/js2c/browser_init:2:106370)
discord[1214]:     at Session.emit (node:events:519:28)
discord[1214]:     at Session.emit (node:domain:489:12)

I installed discord using electron37

daryltucker commented on 2025-09-11 15:24 (UTC)

Installation was failing due to Node incompatibility. Running the following command in the terminal before installing fixed the issue for me: nvm install 22 . This updated my existing 22.X to 22.19.

ww998 commented on 2025-09-09 12:31 (UTC) (edited on 2025-09-09 12:32 (UTC) by ww998)

Had problems upgrading the package: ==> Starting build()... CANNOT RUN WITH NODE 20.19.5 asar requires Node >=22.12.0.

Realized that i had the LTS Nodejs "nodejs-lts-iron" installed instead of the standard package "nodejs"

Removed iron, Installed standard, Discord works again.

veganvelociraptr commented on 2025-09-07 07:42 (UTC)

@Zoddo, I fully agree. Thank you very much for you time helping me out finding the culprit.

Zoddo commented on 2025-09-06 21:01 (UTC)

@veganvelociraptr: You have nodejs 24.7.0 installed, but the exception reports Node.js v20.2.0.

This is your issue (asar 4 requires node 22+). You should investigate why a different node version is running.

oech3 commented on 2025-09-06 16:02 (UTC) (edited on 2025-09-06 16:06 (UTC) by oech3)

How about https://gist.github.com/oech3/805cda74a055fc532fe36b4df580db4d which does not use asar ?

1 2 3 4 5 6 .. 42 Next › Last »