| 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) |
Anybody else's not working with wayland? Using the latest discord and electron 15.
electron15 --enable-features=UseOzonePlatform --ozone-platform=wayland --enable-accelerated-mjpeg-decode --enable-accelerated-video --ignore-gpu-blacklist --enable-native-gpu-memory-buffers --enable-gpu-rasterization --enable-gpu --enable-features=WebRTCPipeWireCapturer /usr/lib/discord/app.asar
It just still uses XWayland...
@katt please ignore my last post, I just run the update again and it worked. Not sure why it hanged. Yes, I'm using Manjaro and I updated via pamac.
@dangpzanco electron15 is in the official repos: https://archlinux.org/packages/community/x86_64/electron15/ Are you using some kind of arch-based distro?
I'm somehow not affected by the bug (on Electron 16.07).
Edit (ignore the following):
Now the package won't build for me... Do I need to downgrade electron? How?
Building discord_arch_electron...
==> Making package: discord_arch_electron 0.0.16-2 (ter 25 jan 2022 22:15:06)
==> Checking runtime dependencies...
==> Missing dependencies:
-> electron15
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.
Seems it's got something to do with the latest electron update about wlroot. I just rolled back my electron instead of updating my AUR package that will use 15.
I get some kind of crash / restart every time I scroll up in a server :v
Is anyone else experiencing crashes with this after an update?
$ discord
Discord 0.0.16
Starting app.
Starting updater.
[Modules] Modules initializing
[Modules] Distribution: remote
[Modules] Host updates: enabled
[Modules] Module updates: enabled
[Modules] Module install path: /home/kaan/.config/discord/0.0.16/modules
[Modules] Module installed file path: /home/kaan/.config/discord/0.0.16/modules/installed.json
[Modules] Module download path: /home/kaan/.config/discord/0.0.16/modules/pending
[5961:0125/135627.359538:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[Modules] No updates to install
[Modules] Checking for host updates.
[Modules] Host is up to date.
[Modules] Checking for module updates at https://discord.com/api/modules/stable/versions.json
[Modules] No module updates available.
[5924:0125/135628.044457:ERROR:file_io_posix.cc(152)] open /home/kaan/.config/discord/Crashpad/pending/a67826d9-ed70-4bf0-9ad0-2b3c1d568aa0.lock: File exists (17)
[WebContents] crashed (crashed)... reloading
[5924:0125/135631.747838:ERROR:file_io_posix.cc(152)] open /home/kaan/.config/discord/Crashpad/pending/d30d7386-6c9f-4eee-a2c8-380b44505907.lock: File exists (17)
[5924:0125/135631.747854:ERROR:file_io_posix.cc(152)] open /home/kaan/.config/discord/Crashpad/pending/a67826d9-ed70-4bf0-9ad0-2b3c1d568aa0.lock: File exists (17)
[WebContents] double crashed (crashed)... RIP =(
Electron v16.0.7.
Fails to start with A Javascript error occured in the main process. I'm unable to copy the error log to paste here, but here's a screenshot: https://i.imgur.com/rVhDyfS.png
Weirdly, it works fine if launched as /usr/bin/discord from a terminal
Sadly this build doesn't like to work with other software. For example "discordrp-mpris" is giving me
ERROR:discord_rpc.async_:failed to open '/run/user/1000/discord-ipc-0': [Errno 111] Connection refused
Couldn't get betterdiscord working either.
Recent update of Electron to a new major version (16) does make Discord crash or behave buggy.
For now, downgrading Electron to its latest 15 version does fix it.
As a side note: I've been able to avoid Discord coredumping on start by launching it from terminal. I don't understand why.
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.