| 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.27 |
| First Submitted: | 2020-05-19 23:51 (UTC) |
| Last Updated: | 2024-12-17 20:22 (UTC) |
The client keeps crashing when I start a screenshare. I thought this was fixed in electron31, as I remember I had to rollback to electron29 to get it working again. However, it keeps crashing even with electron33.
And apparently, Discord has finally fixed screensharing on Linux, when can we expect the feature to be fixed in this package?
@igo95862 Due to this line it should have already defaulted to wayland before if you're on wayland. At least on kde and hyprland I can say that window resizing works as expected and global hotkeys don't work in either mode (unless you pass through all keystrokes to all xwayland applications which is a security concern) because Discord currently does not implement the necessary wayland protocol to register shortcuts.
Obviously on x11 it would default to x11 in either case. Something in your environment must have changed this behavior before.
One of the recent electron versions seems to default to wayland which breaks some stuff like global hotkeys or window resizing. To force X11 I've ran discord with the XDG_SESSION_TYPE environment variable set to x11.
@cubanismo: Thanks, I've updated the package.
You can also follow the instructions in the wiki to allow Discord to start on old versions while waiting for the package to be updated :)
https://wiki.archlinux.org/title/Discord#Discord_asks_for_an_update_not_yet_available_in_the_repository
FYI, Discord's not letting me on today with 0.0.75. Needed to apply this trivial patch to PKGBUILD to update to 0.0.76 and get back online:
diff --git a/PKGBUILD b/PKGBUILD
index 9517234..ecd14d6 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -9,7 +9,7 @@
_pkgname=discord
_electron=electron
pkgname=${_pkgname}_arch_electron
-pkgver=0.0.75
+pkgver=0.0.76
pkgrel=1
pkgdesc="Discord using system provided ${_electron} for increased security and performance"
arch=('any')
@@ -29,7 +29,7 @@ optdepends=('libpulse: Pulseaudio support'
source=("https://dl.discordapp.net/apps/linux/${pkgver}/${_pkgname}-${pkgver}.tar.gz"
'discord-launcher.sh'
'krisp-patcher.py') # original: https://github.com/sersorrel/sys/blob/main/hm/discord/krisp-patcher.py
-sha512sums=('3c05f5ca4faebbe4973ffd977a17da6f398a1725fd3be18d9b025faf3ed7b99cb71e7b3219147492e1180b7b341b05886aeeb39f15a85b180b633db56c9821b7'
+sha512sums=('3a5bdd4ce366f142c40e6acc4ab9faf1f61480c8aaa984abb3c37755e586ee2143c083af561595ff18f6587d3bceffe9d27c9b1069134abd612f63e7db636ee6'
'e11a60419c6ee5944aefc1ac16a5b496518fae626627d37a5bf636975bd21b1d9b6118ec3f44e7f4283befe5fa14737ad28dc38d975967789247ac0e66c352f3'
'42cef68c1f7d574b4fbe859a4dc616e8994c7d16f62bcae3ff1f88e1edc58ac37b39c238d7defa9c97ceda417fcd6224cf0a0fd2608b8d18d0877e3c1befa59c')
@chrisalash This is a feature not supported by Discord on Linux in general. The only way currently to share the screen with sound (on Wayland/Pipewire only) is to use Vencord/Vesktop. In the past there also was discord-screenaudio but that package is deprecated now.
How can I get screenshare with sound working?
@brianc @DodoGTA they probably broke window decoration. Here, at least on compositors that implement server side decoration, Discord official client uses SSD, not client side decoration.
@brianc I can't reproduce the issue with KWin Wayland (so it might be some GNOME-specific bug)
@brianc I think the official client updated to electron 31, so probably want to use that for now.
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.