Anyone else crashing when trying to run this in Wayland mode?
Search Criteria
Package Details: discord_arch_electron 0.0.78-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: | 197 |
Popularity: | 4.19 |
First Submitted: | 2020-05-19 23:51 (UTC) |
Last Updated: | 2024-12-17 20:22 (UTC) |
Dependencies (9)
- electron
- libxss
- asar (make)
- curl (curl-quiche-gitAUR, curl-http3-ngtcp2AUR, 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 (25)
- 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)
- 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)
- premid (requires discord) (optional)
- Show 5 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 27 28 29 30 31 32 33 34 35 36 37 .. 39 Next › Last »
Sukid commented on 2021-06-19 12:44 (UTC)
Kyuunex commented on 2021-05-26 02:42 (UTC)
consider renaming the package to discord-electron
allexj commented on 2021-05-22 13:20 (UTC) (edited on 2022-02-28 22:16 (UTC) by allexj)
in order to be able to share the ENTIRE screen, or to be able to share wayland only (not xwayland) windows it's not enough to have Pipewire installed, because there's one chromium flag to manually enable pipewire support. I don't know how to enable it in this package so I tried it using discord via Google Chrome browser, and enabling "enable-webrtc-pipewire-capturer" flag in chrome://flags, and now it works.
Is there a way to enable this flag in this package without the need to use Google Chrome to be properly share screen?
EDIT: you can do the same thing with Firefox
encrypt3d commented on 2021-05-20 00:43 (UTC)
The PKGBUILD isn't that large, it shouldn't take too much effort to tweak it to work with PTB if you want to try to do it yourself.
lunax commented on 2021-04-26 02:24 (UTC)
Someone make Discord PTB version of this? Or guide for it? Thanks in advance.
<deleted-account> commented on 2021-04-17 11:24 (UTC)
electron 12.0.4-2:
/usr/lib/electron/electron: error while loading shared libraries: libicui18n.so.69: cannot open shared object file: No such file or directory
ersei commented on 2021-04-02 16:40 (UTC)
This can read from a flags file like the chromium package, but it would be under $HOME/.config/electron-flags.conf
, and this is applied to all Electron packages using the system electron (I think).
salad commented on 2021-04-02 15:41 (UTC) (edited on 2021-04-02 15:41 (UTC) by salad)
If anyone's having issues under a Wayland environment with Discord (or any electron
app or chromium
) crashing when launching under Electron's Ozone Wayland, try passing the following flag to electron
:
--disable-gpu-memory-buffer-video-frames
This crash is caused by a bug that doesn't exist under Linux 5.10. This should fix crashing on Linux 5.11 and 5.12 (tested on rc4).
All my electron
(and chromium
) flags for reference:
--enable-features=UseOzonePlatform --ozone-platform=wayland --disable-gpu-memory-buffer-video-frames --enable-gpu
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.