Package Details: discord-electron 0.0.50-1

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

Dependencies (9)

Required by (21)

Sources (2)

Pinned Comments

SunRed commented on 2024-01-04 14:30 (UTC) (edited on 2024-01-04 14:30 (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 rizin, set PATCH_KRISP=true in ~/.config/discord.conf and restart your Discord client.

SunRed commented on 2022-10-23 08:55 (UTC) (edited on 2024-04-09 19:48 (UTC) by SunRed)

Features of this Discord AUR package:

  • Launch script uses an additional option to enable Wayland on supported systems and allows defining additional custom Electron flags (e.g. to enable gpu acceleration).
  • The launch script includes a patch that allows for Krisp noise suppression support.
  • Use of newer system provided Electron version that also makes the package leaner.

For streaming / sharing a screen on Wayland I recommend using discord-screenaudio in tandem with this package.

Maintenance of this package is done in my Gitea repo.

Latest Comments

1 2 3 4 Next › Last »

SunRed commented on 2024-04-10 17:55 (UTC)

@LRitzdorf I am afraid that has been my fault. When I tested it first I didn't encounter this error but testing it again in a virtual machine I could reproduce it. I made a mistake when I moved the asar into the resources subfolder. An update should come up shortly.

LRitzdorf commented on 2024-04-10 00:52 (UTC) (edited on 2024-04-10 16:16 (UTC) by LRitzdorf)

Versions of this package that use Electron 29 (i.e. since 0.0.48-2) appear to be broken, for reasons that'll require someone more familiar with JS than me to fully diagnose. The core issue seems to be that the discord_desktop_core module is missing; full stdout pasted here for reference. Edit: tried (re)moving ~/.config/discord/, with the same result.

SunRed commented on 2024-04-09 19:30 (UTC)

@DJXJD @reeeeeeeeeeelity Sorry for just now coming back to this. I've moved the Discord asar into a resources subfolder that should make Discord client mods like vencord compatible. I couldn't be bothered before looking into this as I don't use vencord and don't want to run random install scripts via curl without knowing what they do (linux install method from their website).
Keep in mind though that vencord specifically crashes with an Electron version greater than 27, so it's quite pointless to use it with a package like this without changing the Electron version.

SunRed commented on 2024-04-09 19:30 (UTC)

@muflone I've read up on the apparent merge request that was filed by someone on discord_arch_electron. Originally this package was called discord-electron-bin before I renamed it to discord-electron because Discord has no non-proprietary version in which case the -bin suffix can be omitted. I created the package originally because the then-maintainers of discord_arch_electron didn't want to include the --ozone-platform-hint=auto start flag for Wayland compatibility, so I just created a separate one. At some point I uploaded discord-electron-openasar that I actually use myself and so I kept this package as an unmodded alternative to it with the same changes.
There were also some other concerns with this package like the Krisp patching that was merely dependent on whether a particular package was installed or not that I apparently addressed since then as it bothered me as well (it now requires a config variable to be set). There are some changes this package includes that are not present or different in discord_arch_electron that I would like to see there but never bothered to contact them. Some of them they apparently adopted.
I could look into contacting them about my changes but to get rid of the silly naming problem discord_arch_electron ideally should be merged/renamed into something else, maybe even this one but that is just my opinion. Sadly replaces does not really work with AUR packages but users should see at least using yay or paru if a package is not available on the AUR anymore and quickly find the new one.

muflone commented on 2024-03-31 23:25 (UTC)

@SunRed I've read the reasons for you creating this package but in the first place it shouldn't have been created.

If the discord_arch_electron package had some issues you should have discussed with the maintainer to fix it, instead of duplicating this package.

Now this package is a mere duplicate and needs to be removed.

brianc commented on 2024-03-07 16:33 (UTC)

No worries @SunRed - I figured I'd done the work anyway; so, I may as well submit a PR and save you the five minutes. :D

SunRed commented on 2024-03-07 06:10 (UTC)

@brianc The issue was a slight misconfiguration when I changed something with the OAuth sources after the last major Gitea update, thanks for letting me know.
There shouldn't be any reason though to create a pull request for mere version updates, if you have something else to add to the package, contributions are welcome.

Cheers.

brianc commented on 2024-03-07 03:15 (UTC)

Having trouble connecting to that Gitea instance (all of the OAuth is failing); but, I was able to patch for 0.0.44 easily enough. Just update the version and the sha512sum accordingly and the package will build and install.

DJXJD commented on 2024-02-16 07:51 (UTC)

I second @reeeeeeeeeeelity's comment. Would really appreciate being able to use Vencord with this package, as well as the openasar variant!

1 2 3 4 Next › Last »