| 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.09 |
| First Submitted: | 2020-05-19 23:51 (UTC) |
| Last Updated: | 2024-11-19 19:20 (UTC) |
@Nairaner and @Icronos's workaround does not seem to work with electron19 using any wlroots-based compositors. Discord only shows the starting spinner and opens a window, but crashes immediately after:
Module ./ElectronTestRpc was not included.
[WebContents] crashed (reason: crashed, exitCode: 139)... reloading
Module ./ElectronTestRpc was not included.
[WebContents] double crashed (reason: crashed, exitCode: 139)... RIP =(
With the latest workaround the package even works on the latest version (19). The only downside is that the application has no icon in the taskbar. I tried this on Wayland, KDE.
Hey!
I recently installed this package and now found my syslog spammed full of this after starting the application (on startup):
Jul 18 22:34:02 larch discord-stable.desktop[3139]: [2022-07-18 22:34:02.498] [3162] (device_info_linux.cc:45): NumberOfDevices
Jul 18 22:34:02 larch discord-stable.desktop[3139]: [2022-07-18 22:34:02.610] [3162] (device_info_linux.cc:45): NumberOfDevices
Jul 18 22:34:02 larch discord-stable.desktop[3139]: [2022-07-18 22:34:02.611] [3162] (device_info_linux.cc:78): GetDeviceName
Any thoughts?
Greetings
Following @lcronos advice i modified it a little and it to more usable version for packaging. Change in app.asar.unpacked/app_bootstrap/requireNative.js:
module.paths = ["/home/" + process.env.USER + "/.config/discord/0.0.18/modules"];
It works with electron 18, wayland streaming is still broken
I think this is the reason Discord is broken on Electron 17+: https://github.com/electron/electron/issues/33504
If I run it in xwayland I can stream other xwayland windows, but if I run with ozone=wayland, I can't stream anything.
Ok, I just wanted to know if it's a regression for you since I'm looking into upgrading the package to electron 18.
16 just segfaults for me
@mkaito: Did it break only when updating to electron 18, or does it also break for you with electron 16?
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.
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-electronpackage 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):
Starting with 0.0.20-1 (2022-09-15):
$XDG_CONFIG_HOME/discord-flags.conf: this works likeelectron-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.