Is there a reason why the source package does not get updated automatically? - mathisbuilder
I will second this question, as the package is out-of-date again.
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.19 |
First Submitted: | 2020-05-19 23:51 (UTC) |
Last Updated: | 2024-11-19 19:20 (UTC) |
« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 38 Next › Last »
Is there a reason why the source package does not get updated automatically? - mathisbuilder
I will second this question, as the package is out-of-date again.
Neither rolling back to Electron 16, nor using files from the comment 883680 fix the crashes when trying to watch one's stream. So annoying to switch to browser every time. Though Discord works with Electron 22, if no one noticed.
I tested DiscordCanary it does work now with the latest Electron.
Is there a reason why the source package does not get updated automatically?
Waiting update for 0.0.25 :
Package : https://transfert.free.fr/GUr5fg
I tried to fiddle around with the same package on OpenSUSE. I found out that if would use openasar that the package works fine with the latest Electron. Need to check video streaming and so on thou.
@gudvinr That's a problem of Electron and is already fixed on Electron >= 20.
No way to fix crashes on streams / camera. Tried various versions of electron.
I have created a Proof Of Concept .so that patches the krisp binary at runtime to work with discord_arch_electron I used a technique that's rather version-change proof so it shouldn't need updates that often.
Unfortunately, Discord reverted back their official build to electron13. I hope this is only temporary. The few tests I did while on 0.0.23 showed that Discord still doesn't start on electron20+, and watching streams still causes core dumps, but I didn't have the time to investigate deeper.
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.