@HunabKu, @LevitatingRein, @gshinguji, @dylif
Disabling 'Hardware Acceleration' under advanced, 'OpenH264 Video Codec provided by Cisco Systems, Inc.' and 'H.264 Hardware Acceleration' under Voice & Video > Advanced. Allows me to watch streams.
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: | 4.79 |
First Submitted: | 2020-05-19 23:51 (UTC) |
Last Updated: | 2024-11-25 19:51 (UTC) |
« First ‹ Previous 1 .. 17 18 19 20 21 22 23 24 25 26 27 .. 39 Next › Last »
@HunabKu, @LevitatingRein, @gshinguji, @dylif
Disabling 'Hardware Acceleration' under advanced, 'OpenH264 Video Codec provided by Cisco Systems, Inc.' and 'H.264 Hardware Acceleration' under Voice & Video > Advanced. Allows me to watch streams.
@AkechiShiro I am having the same issue here on X11 using the amdgpu driver as well
Latest Discord, still using outdated Electron (not working with latest), lol
Was unable to even open app as it required update =) Many thanks for fix!!
@bryiewes The latest version (0.0.18) appears to require a reinstallation of the entire client and can not utilize the built-in autoupdater.
This package should not be listed as out-of-date as discord autoupdates.
@HunabKu, @LevitatingRein, @gshinguji, let me be clear, I have encountered the same crashing while joining a screenshare on Discord under X11 on the following discord packages :
discord_arch_electron
from the AUR.discord-canary-electron-bin
from the AUR.discord
from [community]powercord-electron-git
from the AUR.Laptop Ryzen 7 3700U with an AMD iGPU (RX Vega 10).
@HunabKu because i've only th bug in Wayland, but not in x11. It seems that something else comes into play.
@HunabKu I'm under X11 and encountering the same bug, so I don't know why you said it is a Wayland only issue for screen share crashing discord.
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.