Package Details: discord-electron-openasar 0.0.94+834-2

Git Clone URL: https://aur.archlinux.org/discord-electron-openasar.git (read-only, click to copy)
Package Base: discord-electron-openasar
Description: Discord packaged with OpenAsar using system provided electron (v35) for increased security and performance
Upstream URL: https://discord.com
Keywords: discord discord-stable discordapp electron openasar
Licenses: custom
Conflicts: discord
Provides: discord
Submitter: SunRed
Maintainer: SunRed
Last Packager: SunRed
Votes: 12
Popularity: 1.03
First Submitted: 2023-04-03 07:00 (UTC)
Last Updated: 2025-05-08 20:00 (UTC)

Dependencies (12)

Required by (29)

Sources (4)

Pinned Comments

SunRed commented on 2024-01-04 14:30 (UTC) (edited on 2024-06-10 19:00 (UTC) by SunRed)

Electron flags

These can be set additionally in ~/.config/discord-flags.conf (or wherever your config directory is). Lines can be commented using #.

Krisp noise suppression

In order for Krisp to work, it has to be patched first by removing the signature check of the Krisp binary. Install the necessary optional dependencies, set PATCH_KRISP=true in ~/.config/discord.conf and restart your Discord client.
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 Next › Last »

SunRed commented on 2025-05-08 20:00 (UTC)

@painfularch This is apparently an Electron issue on GNOME https://github.com/electron/electron/issues/46538
I downgraded the Electron version for now again. Sorry for my late response.

brody commented on 2025-05-06 10:10 (UTC)

I cannot confirm the crash at startup.

painfularch commented on 2025-05-06 09:15 (UTC)

latest version crashes on startup with this error message:

(process:115291): Gtk-ERROR **: [redacted for privacy]: GTK 2/3 symbols detected. Using GTK 2/3 and GTK 4 in the same process is not supported

Is this an upstream problem or a PKGBUILD one?

SunRed commented on 2025-04-16 13:16 (UTC)

There seems to be some issue at the moment with screen sharing crashing the frontend by producing a TypeError: window.createDiscordStream is not a function even though screen sharing itself works. This doesn't seem related to OpenAsar or newer Electron versions as using an older Electron version produces the same error as well as using the official asar. I am not sure at this moment this is even resolvable without using Discord's packaged Electron runtime.

SunRed commented on 2025-01-20 16:48 (UTC)

@ItachiSan Updating electron34 to 34.0.0-3 fixes that issue. It was an issue with the PGO recompilation.

ItachiSan commented on 2025-01-20 16:44 (UTC)

Hi, I have a memory leak when running Discord via Plasma.

Using a terminal solves the issue.

ItachiSan commented on 2024-10-09 21:28 (UTC)

@SunRed 0.0.71 works for me too :)

SunRed commented on 2024-10-09 21:17 (UTC)

@ItachiSan The issue seems fixed with 0.0.71.

ItachiSan commented on 2024-10-06 20:22 (UTC)

Hi, verified that downgrading to 0.0.69 does the trick.

For everyone, just clone this repo and run: git checkout HEAD~ before building (will go 1 commit back, to 0.0.69).

@SunRed any clue when this will be fixed? It might be good to pin the message about this upstream issue.

SunRed commented on 2024-10-06 17:00 (UTC)

@darkbasic I noticed this issue. It seems to be an issue with OpenAsar: https://github.com/GooseMod/OpenAsar/issues/197 The only solution for now would be downgrading the discord package.

1 2 3 4 5 Next › Last »