Package Details: discord_arch_electron 0.0.78-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: 4.19
First Submitted: 2020-05-19 23:51 (UTC)
Last Updated: 2024-12-17 20:22 (UTC)

Dependencies (9)

Required by (25)

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

« First ‹ Previous 1 .. 16 17 18 19 20 21 22 23 24 25 26 .. 39 Next › Last »

mkaito commented on 2022-06-26 22:19 (UTC)

If I run it in xwayland I can stream other xwayland windows, but if I run with ozone=wayland, I can't stream anything.

Zoddo commented on 2022-06-26 22:10 (UTC)

Ok, I just wanted to know if it's a regression for you since I'm looking into upgrading the package to electron 18.

mkaito commented on 2022-06-26 21:49 (UTC)

16 just segfaults for me

Zoddo commented on 2022-06-26 18:27 (UTC) (edited on 2022-06-26 18:30 (UTC) by Zoddo)

@mkaito: Did it break only when updating to electron 18, or does it also break for you with electron 16?

mkaito commented on 2022-06-26 17:15 (UTC)

It doesn't let me share my screen though. It just gets stuck trying to load screens and windows and never gets past that. Not sure if pipewire is still locked behind an electron flag.

mkaito commented on 2022-06-26 16:58 (UTC)

Yep that does indeed work with electron 18 (and 19).

lcronos commented on 2022-06-23 12:48 (UTC) (edited on 2022-06-23 12:50 (UTC) by lcronos)

A little more testing and it seems the environment variable is not necessary, but the path update is necessary.

This should work for electron 17 and electron 18, but I haven't tested with them.

lcronos commented on 2022-06-23 12:47 (UTC) (edited on 2022-06-23 17:37 (UTC) by lcronos)

I seem to have gotten it to work with electron19. Full disclosure, I did this on Gentoo (which doesn't have electron16, only reason I tried lol), so YMMV.

There are two things to try. First, during the unpack step for the asar file, there is a file, app/app_bootstrap/requireNative.js which has a line that is asking for a path to a module location. I added ~/.config/discord/0.0.18/modules to the list. Then I ran export NODE_PATH=~/.config/discord/0.0.18/modules. electron-19 /usr/lib/discord/app.asar then worked as expected.

I'm not sure if the step where you edit the file is actually necessary, so you might try playing with these steps a bit.

EDIT: For just a little more detail, the change looks like this:

module.paths = ["/home/USER/.config/discord/0.0.18/modules"];

I'm not sure if there's an easy way to include this in the PKGBUILD, but you can do it manually and get newer electron versions working at least. Maybe someone a little more familiar with electron can figure out a better way to make this work.

Myrdden commented on 2022-06-18 12:49 (UTC)

Well, was having some success with electron16, but I've just updated this package and now none of them work. electron(18) and electron17 give the core not found error, while 16 and 15 are now just segfaulting.

gregory112 commented on 2022-06-17 05:41 (UTC)

@Devorlon I didn't disable Hardware Acceleration though (although I am using electron 16 with Discord Canary under Wayland), just the OpenH264 codec, and I can still watch streams. Disabling Hardware Acceleration makes the animation quite laggy so I tried it with that still on, and well it works.

@snvmk The problem with electron 17 seems to be an upstream problem though. I got the same problem with electron 17 or newer. I wonder how some people claimed they can make it work with electron 17?

« First ‹ Previous 1 .. 16 17 18 19 20 21 22 23 24 25 26 .. 39 Next › Last »