It looks like the move to electron32 breaks the ability to resize the window in Gnome/Wayland. I don't know if it's broken elsewhere; but, it's definitely the case on multiple machines for me.
Confirmed working electron31 by modifying the PKGBUILD
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) |
« First ‹ Previous 1 2 3 4 5 6 7 .. 39 Next › Last »
It looks like the move to electron32 breaks the ability to resize the window in Gnome/Wayland. I don't know if it's broken elsewhere; but, it's definitely the case on multiple machines for me.
Confirmed working electron31 by modifying the PKGBUILD
Getting a weird error occasionally, some "Write EIO error". Accidentally closed it, will try to get logs soon.
In the future instead of downgrading the package you can also just remove the modules directory in ~/.config/discord/
that is now at the time of writing 0.0.60
.
Same as @katt, Discord is crashing on launch when enabling the Krisp patch right after discord loads the module.
splashScreen.updateSplashState launching launching {}
splashScreen.webContentsSend: SPLASH_UPDATE_STATE SPLASH_UPDATE_STATE [ { status: 'launching' } ]
blackbox: 2024-07-13T21:13:39.623Z 4 ✅ webContents.created web2 ""
blackbox: 2024-07-13T21:13:39.634Z 5 ✅ window.created win2 "Discord"
blackbox: 2024-07-13T21:13:39.637Z 6 ✅ webContents.did-finish-load web1
legacyModuleUpdater: installed-module discord_game_utils 1 1 true
legacyModuleUpdater: installed-module discord_krisp 1 1 true
mainScreen.UpdaterEvents: UPDATER_HISTORY_QUERY_AND_TRUNCATE
[WebContents] crashed (reason: crashed, exitCode: 139)... reloading
0.0.59 seems broken, first I thought it was just the krisp patching which seemed to work by disabling it, but only worked once. Only downgrading package works.
https://gist.github.com/kattjevfel/dd07943fe6c615f73ad83a791d94c0c1
edit: Downgrading package, disabling krisp patching and then updating works. Enabling krisp patching breaks everything again.
@brianc I personally prefer to pin the version as we've seen multiple times now that a new major electron version just randomly breaks things. At the request of @Zoddo though I kept it at just electron
if possible. There is an argument to be made for both approaches. I haven't given it much thought since.
@SunRed - I've been building discord myself using the discord-electron PKGBUILD from your repo ever since it was removed from the AUR. I noticed that you updated this package to depend on electron rather than pinning a version; but, you didn't do that in your package. Just curious as to the motivation before I move to this package.
After some testing I can say electron31 is too broken right now (someone did make an issue for the fullscreen crash: https://github.com/electron/electron/issues/42560)
I think reverting to electron30 should be safe (I did test that version for a good amount of time and it didn't crash for me)
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.