Package Details: discord_arch_electron 0.0.75-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: 195
Popularity: 5.19
First Submitted: 2020-05-19 23:51 (UTC)
Last Updated: 2024-11-19 19:20 (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 2 3 4 5 6 7 8 9 10 11 12 .. 38 Next › Last »

e00E commented on 2023-10-18 10:40 (UTC) (edited on 2023-10-18 10:48 (UTC) by e00E)

I just tested again. It still crashes. Maybe it is not Wayland in general but Sway specifically that crashes it? Some programs are confused by getting resized or not being floating in Sway.

Update: https://aur.archlinux.org/packages/discord-electron works for me. This might be due to different electron version being picked. discord_arch_electron does not fix the electron version, which made it use the plain electron package, which is 25. discord-electron forces electron-24. The maintainer has commented that they intentionally did not use 25 because it "resulted in unstable behavior".

Lightning5 commented on 2023-10-17 09:41 (UTC)

@e00E It works for me under Wayland. Try to set back to X, running it and then back to Wayland. If I remember correctly, first run has to be on X. Then it will work on Wayland :)

e00E commented on 2023-10-15 21:31 (UTC)

This package doesn't work with Wayland. I didn't read through a lot of comment history so maybe this has already been reported. By default when you run this package without xwayland, Discord doesn't start. If you add options that usually make electron work with Wayland, then Discord crashes after the splash screen.

aliu commented on 2023-10-09 19:54 (UTC)

If anyone is interested I also have an OpenASAR installer script that automatically searches all known possible directories

Thaodan commented on 2023-10-09 19:49 (UTC)

@Thaodan: The resource folder was asked by irisnk in this comment.

That sounds like a hack. If one wants openasar they should install discord patched with openasar... But not my call what he wants to do.

Zoddo commented on 2023-10-09 19:43 (UTC)

@Thaodan: The resource folder was asked by irisnk in this comment.

Thaodan commented on 2023-10-08 21:17 (UTC)

Why keep the resources folder? Electron doesn't care for the folder name, /usr/share/discord is enough.

Discord is architecture-dependent (it dynamically downloads native modules compiled for x86_64 on the first run). The asar archive doesn't contain anything architecture-dependent by itself, so I will move it to /usr/share/discord/resources/ on the next package update,

The discord package e.g. the host part of the package is not architecture dependent. Without the precompiled Electron it still runs on architectures (minus the features that require native node modules).

Mewio commented on 2023-10-08 16:43 (UTC)

@zoddo No problem! I figured I would report on it since the last report was some time ago.

Zoddo commented on 2023-10-08 15:10 (UTC)

Discord is architecture-dependent (it dynamically downloads native modules compiled for x86_64 on the first run).
The asar archive doesn't contain anything architecture-dependent by itself, so I will move it to /usr/share/discord/resources/ on the next package update, but I believe the PKGBUILD should continue to use arch=('x86_64') since the package will not run on other architectures.

@Mewio: Thanks for the report, I'll take a look at the pop-out issue.

aliu commented on 2023-10-08 14:47 (UTC)

Since the asar isn't architecture dependent shouldn't it be installed to /usr/share instead of /usr/lib?

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 38 Next › Last »