This package should be renamed to discord-electron-bin
to be consistent with the -canary
package.
Search Criteria
Package Details: discord_arch_electron 0.0.90-1
Package Actions
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: | 198 |
Popularity: | 2.23 |
First Submitted: | 2020-05-19 23:51 (UTC) |
Last Updated: | 2025-03-31 19:25 (UTC) |
Dependencies (9)
- electron
- libxss
- asar (make)
- curl (curl-gitAUR, curl-c-aresAUR) (make)
- libappindicator-gtk3 (optional) – Systray indicator support
- libpulse (pulseaudio-dummyAUR, libpulse-gitAUR) (optional) – Pulseaudio support
- python-capstone (optional) – Required for Krisp patcher
- python-pyelftools (python-pyelftools-gitAUR) (optional) – Required for Krisp patcher
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, xdg-utils-handlrAUR, openerAUR, xdg-utils-mimeoAUR, mimejs-gitAUR) (optional) – Open files
Required by (27)
- beautiful-discord-git (requires discord)
- cia-accesa (requires discord)
- clonehero-ptb (requires discord) (optional)
- devbook-bin (requires discord)
- discord-update-skip-git (requires discord)
- discordrpc (requires discord) (optional)
- discordupdater (requires discord)
- horizonxi-launcher-bin (requires discord) (optional)
- jfcord-appimage (requires discord) (optional)
- mbcord-appimage (requires discord) (optional)
- moonlight-stable-bin (requires discord) (optional)
- open-hexagon-git (requires discord) (optional)
- openasar-bin (requires discord) (optional)
- openasar-git (requires discord) (optional)
- openasar-install (requires discord)
- overlayed (requires discord) (optional)
- overlayed-bin (requires discord) (optional)
- overlayed-git (requires discord) (optional)
- plasticity-bin (requires discord) (optional)
- plasticity-bin-unstable (requires discord) (optional)
- Show 7 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 24 25 26 27 28 29 30 31 32 33 34 .. 40 Next › Last »
SunRed commented on 2022-02-13 11:25 (UTC)
Zoddo commented on 2022-02-11 21:30 (UTC)
I can confirm the bug has been fixed with recent updates of the electron
package.
I believe the package can be switched back to electron16.
intersectRaven commented on 2022-01-27 23:29 (UTC)
The crash with electron v16 has been addressed by the electron package. It should be fine with electron-16.0.7-3.
tsweet64 commented on 2022-01-27 01:57 (UTC)
Yes, I'm having the same issue
mattj commented on 2022-01-26 19:21 (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...
dangpzanco commented on 2022-01-26 16:04 (UTC)
@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
.
katt commented on 2022-01-26 15:26 (UTC)
@dangpzanco electron15 is in the official repos: https://archlinux.org/packages/community/x86_64/electron15/ Are you using some kind of arch-based distro?
dangpzanco commented on 2022-01-26 01:15 (UTC) (edited on 2022-01-26 16:06 (UTC) by dangpzanco)
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.
intersectRaven commented on 2022-01-25 23:46 (UTC)
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.
Neko-san commented on 2022-01-25 19:22 (UTC)
I get some kind of crash / restart every time I scroll up in a server :v
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):
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.