Package Details: discord_arch_electron 0.0.89-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: 197
Popularity: 1.51
First Submitted: 2020-05-19 23:51 (UTC)
Last Updated: 2025-03-24 18:50 (UTC)

Dependencies (9)

Required by (27)

Sources (3)

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

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):
  • 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.

Latest Comments

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

scrykita commented on 2025-01-28 21:25 (UTC)

You can temporarily load discord without updating by adding this line to your ~/.config/discord/settings.json

"SKIP_HOST_UPDATE": true,

Ph_rel commented on 2025-01-28 09:14 (UTC)

Please may you update to v0.0.82 ?

SunRed commented on 2025-01-15 17:42 (UTC)

@b4shful This issue is fixed with asar version 3.2.18-2.

DodoGTA commented on 2025-01-15 13:51 (UTC) (edited on 2025-01-15 13:51 (UTC) by DodoGTA)

@b4shful It's definitely the asar package itself (because there was a packaging step missing after the program was migrated to TypeScript)

b4shful commented on 2025-01-15 13:25 (UTC) (edited on 2025-01-15 13:27 (UTC) by b4shful)

Getting a build error after the asar package in the Extra repo was updated to 3.2.18-1 (released 2 hours ago at the time of this post).

node:internal/modules/cjs/loader:1244
  throw err;
  ^

Error: Cannot find module '../lib/asar'
Require stack:
- /usr/lib/node_modules/@electron/asar/bin/asar.js
    at Function._resolveFilename (node:internal/modules/cjs/loader:1241:15)
    at Function._load (node:internal/modules/cjs/loader:1066:27)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:220:24)
    at Module.require (node:internal/modules/cjs/loader:1327:12)
    at require (node:internal/modules/helpers:136:16)
    at Object.<anonymous> (/usr/lib/node_modules/@electron/asar/bin/asar.js:15:12)
    at Module._compile (node:internal/modules/cjs/loader:1566:14)
    at Object..js (node:internal/modules/cjs/loader:1718:10)
    at Module.load (node:internal/modules/cjs/loader:1305:32) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/usr/lib/node_modules/@electron/asar/bin/asar.js' ]
}

Node.js v23.4.0
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: discord_arch_electron-exit status 4

I worked around this in the meantime by downgrading asar to the previous version (3.2.8-1). Not sure if the issue lies with the asar package or this AUR package, but wanted to mention it here just in case.

Haven't looked into it too deeply, but that asar version bump in the Arch repos from 3.2.8 to 3.2.18 seems mighty large, so perhaps there's some slight breaking change there.

mihalycsaba commented on 2025-01-11 18:24 (UTC)

I can't resize the window on gnome wayland.

xinayder commented on 2024-12-16 22:16 (UTC)

The client keeps crashing when I start a screenshare. I thought this was fixed in electron31, as I remember I had to rollback to electron29 to get it working again. However, it keeps crashing even with electron33.

And apparently, Discord has finally fixed screensharing on Linux, when can we expect the feature to be fixed in this package?

SunRed commented on 2024-12-07 08:52 (UTC)

@igo95862 Due to this line it should have already defaulted to wayland before if you're on wayland. At least on kde and hyprland I can say that window resizing works as expected and global hotkeys don't work in either mode (unless you pass through all keystrokes to all xwayland applications which is a security concern) because Discord currently does not implement the necessary wayland protocol to register shortcuts.
Obviously on x11 it would default to x11 in either case. Something in your environment must have changed this behavior before.

igo95862 commented on 2024-12-06 22:50 (UTC)

One of the recent electron versions seems to default to wayland which breaks some stuff like global hotkeys or window resizing. To force X11 I've ran discord with the XDG_SESSION_TYPE environment variable set to x11.

Zoddo commented on 2024-11-25 19:53 (UTC)

@cubanismo: Thanks, I've updated the package.

You can also follow the instructions in the wiki to allow Discord to start on old versions while waiting for the package to be updated :)
https://wiki.archlinux.org/title/Discord#Discord_asks_for_an_update_not_yet_available_in_the_repository

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