| 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.09 |
| First Submitted: | 2020-05-19 23:51 (UTC) |
| Last Updated: | 2024-11-19 19:20 (UTC) |
no matter what I do, trying to run Discord with Ozone (for wayland) results in a crash
I have this same problem on a machine with an AMD card. Interestingly though I'm able to run Discord under Wayland just fine on my laptop that uses integrated Intel graphics. It's been this way for months now, and it's the same for the element-desktop package.
For some reason I'm getting no window decorations with this under Gnome+Wayland.
EDIT: Just found the CSD vs SSD debate for Gnome. If anyone else is wondering, Gnome on Wayland does not (will not?) support server-side window decorations.
Weird issue, no matter what I do, trying to run Discord with Ozone (for wayland) results in a crash. I've tried with the latest electron (14), I've tried 9, 10, 11, 12, and probably 13 too, I've tried on multiple installs, with multiple WMs, multiple different flags (like --enable-gpu, --disable-gpu-memory-buffer-video-frames, etc.) and nothing works. Same error every time too. Error log:
(electron) Sending uncompressed crash reports is deprecated and will be removed in a future version of Electron. Set { compress: true } to opt-in to the new behavior. Crash reports will be uploaded gzipped, which most crash reporting servers support.
Discord 0.0.16
Starting app.
Starting updater.
[Modules] Modules initializing
[Modules] Distribution: remote
[Modules] Host updates: enabled
[Modules] Module updates: enabled
[Modules] Module install path: /home/peter/.config/discord/0.0.16/modules
[Modules] Module installed file path: /home/peter/.config/discord/0.0.16/modules/installed.json
[Modules] Module download path: /home/peter/.config/discord/0.0.16/modules/pending
--2021-09-27 18:33:50-- https://sentry.io/api/146342/minidump/?sentry_key=384ce4413de74fe0be270abe03b2b35a
SSL_INIT
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving sentry.io (sentry.io)... 35.188.42.15
Connecting to sentry.io (sentry.io)|35.188.42.15|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 36 [text/plain]
Saving to: '/dev/fd/4'
0K
Failed to get crash dump id.
Report Id: e01dc017-c726-47
Segmentation fault
Since the update to 0.0.16, I am unable to drag files directly into discord to upload them to chats. Has anyone else experienced this issue? I am using KDE Plasma on X.
I got this error on wayland 1.19.0-1 sway-git r6780.b7b96399-1: edit: before I update, it worked very well.
Discord 0.0.16
Quitting secondary instance.
[75020:0923/232839.075527:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.InvalidArgs: No such interface “org.freedesktop.portal.FileChooser”
[75020:0923/232839.075680:ERROR:select_file_dialog_impl_portal.cc(237)] Failed to read portal version property
Really quick with the updates, wonderful work johnnyapol!
@MuffinBomber added you
That aside, is there a way to use Discord calls using Pipewire?
I installed Pipewire the other just to now find out that Discord doesn't like Pipewire in calls, at least when I use this package (this isn't mentioned in the Arch Wiki)
Edit: Scratch that, I don't get any audio at all from my headphones with Pipewire
@Neko-san I think we should move this conversation elsewhere as it is unrelated to the package itself. You can use the Discord web client and add me on 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-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.