Search Criteria
Package Details: discord_arch_electron 0.0.18-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/discord_arch_electron.git (read-only, click to copy) |
---|---|
Package Base: | discord_arch_electron |
Description: | Discord (popular voice + video app) using the 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 |
Last Packager: | Zoddo |
Votes: | 124 |
Popularity: | 4.77 |
First Submitted: | 2020-05-19 23:51 (UTC) |
Last Updated: | 2022-06-08 19:05 (UTC) |
Dependencies (4)
- electron16 (electron16-bin)
- asar (make)
- libpulse (libpulse-bluedio, pulseaudio-pali, pulseaudio-dummy, libpulse-nosystemd-git, libpulse-nosystemd, libpulse-nosystemd-minimal-git, libpulse-airplay, pulseaudio-git) (optional) – Pulseaudio support
- xdg-utils (mimi-git, busking-git, xdg-utils-git, linopen, xdg-utils-handlr, xdg-utils-slock, mimi-bachoseven-git, xdg-utils-symlink-fix, mimejs-git, xdg-utils-mimeo, xdg-utils-lxqt, opener) (optional) – Open files
Required by (12)
- beautiful-discord-git (requires discord)
- devbook-bin (requires discord)
- discord-update-skip-git (requires discord)
- discordrpc (requires discord) (optional)
- discordupdater (requires discord)
- open-hexagon-git (requires discord) (optional)
- openasar-git (requires discord)
- plasticity-bin (requires discord) (optional)
- premid (requires discord) (optional)
- premid-git (requires discord) (optional)
- remoteit-desktop-bin (requires discord)
- sonic3air-bin (requires discord) (optional)
Latest Comments
DodoGTA commented on 2022-06-27 13:35 (UTC)
I think this is the reason Discord is broken on Electron 17+: https://github.com/electron/electron/issues/33504
mkaito commented on 2022-06-26 22:19 (UTC)
If I run it in xwayland I can stream other xwayland windows, but if I run with ozone=wayland, I can't stream anything.
Zoddo commented on 2022-06-26 22:10 (UTC)
Ok, I just wanted to know if it's a regression for you since I'm looking into upgrading the package to electron 18.
mkaito commented on 2022-06-26 21:49 (UTC)
16 just segfaults for me
Zoddo commented on 2022-06-26 18:27 (UTC) (edited on 2022-06-26 18:30 (UTC) by Zoddo)
@mkaito: Did it break only when updating to electron 18, or does it also break for you with electron 16?
mkaito commented on 2022-06-26 17:15 (UTC)
It doesn't let me share my screen though. It just gets stuck trying to load screens and windows and never gets past that. Not sure if pipewire is still locked behind an electron flag.
mkaito commented on 2022-06-26 16:58 (UTC)
Yep that does indeed work with electron 18 (and 19).
lcronos commented on 2022-06-23 12:48 (UTC) (edited on 2022-06-23 12:50 (UTC) by lcronos)
A little more testing and it seems the environment variable is not necessary, but the path update is necessary.
This should work for electron 17 and electron 18, but I haven't tested with them.
lcronos commented on 2022-06-23 12:47 (UTC) (edited on 2022-06-23 17:37 (UTC) by lcronos)
I seem to have gotten it to work with electron19. Full disclosure, I did this on Gentoo (which doesn't have electron16, only reason I tried lol), so YMMV.
There are two things to try. First, during the unpack step for the asar file, there is a file, app/app_bootstrap/requireNative.js which has a line that is asking for a path to a module location. I added
~/.config/discord/0.0.18/modules
to the list. Then I ranexport NODE_PATH=~/.config/discord/0.0.18/modules
.electron-19 /usr/lib/discord/app.asar
then worked as expected.I'm not sure if the step where you edit the file is actually necessary, so you might try playing with these steps a bit.
EDIT: For just a little more detail, the change looks like this:
I'm not sure if there's an easy way to include this in the PKGBUILD, but you can do it manually and get newer electron versions working at least. Maybe someone a little more familiar with electron can figure out a better way to make this work.
Myrdden commented on 2022-06-18 12:49 (UTC)
Well, was having some success with electron16, but I've just updated this package and now none of them work. electron(18) and electron17 give the core not found error, while 16 and 15 are now just segfaulting.
gregory112 commented on 2022-06-17 05:41 (UTC)
@Devorlon I didn't disable Hardware Acceleration though (although I am using electron 16 with Discord Canary under Wayland), just the OpenH264 codec, and I can still watch streams. Disabling Hardware Acceleration makes the animation quite laggy so I tried it with that still on, and well it works.
@snvmk The problem with electron 17 seems to be an upstream problem though. I got the same problem with electron 17 or newer. I wonder how some people claimed they can make it work with electron 17?
snvmk commented on 2022-06-16 11:43 (UTC)
Running with Electron 16 only shows gray splash screen, crashes, and repeatedly says:
Also was trying with electron17 and 18, but they didnt even come to this - they say (in GTK-like pop-up):
Any ideas?
dylif commented on 2022-06-15 16:24 (UTC)
Thanks @Devorlon, this worked for me.
Devorlon commented on 2022-06-10 11:03 (UTC)
@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.
dylif commented on 2022-06-09 02:42 (UTC)
@AkechiShiro I am having the same issue here on X11 using the amdgpu driver as well
StarterX4 commented on 2022-06-09 01:56 (UTC)
Latest Discord, still using outdated Electron (not working with latest), lol
roworu commented on 2022-06-08 19:06 (UTC) (edited on 2022-06-08 19:10 (UTC) by roworu)
Was unable to even open app as it required update =) Many thanks for fix!!
danejur commented on 2022-06-08 19:02 (UTC)
@bryiewes The latest version (0.0.18) appears to require a reinstallation of the entire client and can not utilize the built-in autoupdater.
bryiewes commented on 2022-06-08 17:58 (UTC)
This package should not be listed as out-of-date as discord autoupdates.
AkechiShiro commented on 2022-06-04 10:32 (UTC) (edited on 2022-06-04 10:35 (UTC) by AkechiShiro)
@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 commented on 2022-06-04 00:46 (UTC)
@HunabKu because i've only th bug in Wayland, but not in x11. It seems that something else comes into play.
AkechiShiro commented on 2022-05-20 20:23 (UTC)
@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.
gshinguji commented on 2022-05-20 18:55 (UTC)
Discord crashes anytime a stream is opened and it refuses to load videos with audio while in call.
Second issue may be due to me using PipeWire, but the streams still remain an issue as I see many other users with this problem.
HunabKu commented on 2022-05-11 11:30 (UTC) (edited on 2022-05-11 11:32 (UTC) by HunabKu)
@LevitatingRein seems to be a Wayland issue.
stick commented on 2022-05-09 11:54 (UTC)
@Neko-san me too, it's driving me insane... but the issue is for any notifications, not just Discord. I'm using mako notifications in sway, and even clicking a Signal notification crashes Signal.
Neko-san commented on 2022-05-06 12:33 (UTC)
Clicking on notifications has frequently been causing me crashes
zerophase commented on 2022-04-25 19:25 (UTC)
Getting:
/usr/lib/electron/electron: error while loading shared libraries: libicui18n.so.70: cannot open shared object file: No such file or directory
icu was recently updated.
LevitatingRein commented on 2022-04-18 19:58 (UTC)
I can't open any screenshares, Discord immediately crashes. That's the only issue I've been having.
mkaito commented on 2022-04-13 16:01 (UTC)
I've done some testing with various electron versions and flags that I've seen mentioned.
I've gotten as far as starting it with electron 16, but I get no window decorations. There's apparently a fix for that, merged in January, and backported to electron 17. Discord doesn't seem to work on 17 though, some JS error which I assume is an upstream problem.
Zoddo commented on 2022-04-02 15:46 (UTC) (edited on 2022-04-02 15:46 (UTC) by Zoddo)
@johnnyapol: Would you be able to support a "~/.config/discord-flags.conf" file like what electron does [1], but to apply some flags only to discord?
This could be really useful to implement some flags like the ones suggested Neko-san[2] to fix the slow/laggy animations on Discord.
In my case, adding these flags to
electron-flags.conf
causes other issues, like breaking VS Code.[1] https://github.com/archlinux/svntogit-community/blob/packages/electron16/trunk/electron-launcher.sh
[2] https://aur.archlinux.org/packages/discord_arch_electron#comment-819244
fitri commented on 2022-03-25 17:48 (UTC)
johnnyapol, please add
libxss
as runtime dependencies to fix... Discord installation is corrupt ...
banner on x11/xwayland for some versions ofelectron
.Visne commented on 2022-03-23 15:30 (UTC)
Has anyone gotten notification badges in the KDE toolbar working with this? I read everywhere that you need to install libunity, which I've done, but that doesn't change anything.
Alkaris commented on 2022-03-20 02:58 (UTC) (edited on 2022-03-20 03:54 (UTC) by Alkaris)
This update of Discord is completely broken. 0.0.17 refuses to load anything past the splash screen, and just presented with a blank window screen.
Also has thing when ran in Terminal saying
Module ./ElectronTestRpc was not included.
Sukid commented on 2022-03-18 23:48 (UTC)
@stick Electron16 seems to be working for me most of the time, with the occasional hiccup. still might try that.
stick commented on 2022-03-14 16:37 (UTC)
I created a new package for myself; set to depend on electron 13 because even with electron 15 wayland support is broken.
Hopefully I'll be able to request deletion eventually if the discord/electron/wayland bugs get fixed... until then, if anyone else wants it, it's there. It should auto-detect wayland and
--enable-features=UseOzonePlatform --ozone-platform=wayland
appropriately. Testers wanted :).discord_arch_electron_wayland
sl1pkn07 commented on 2022-03-14 15:54 (UTC) (edited on 2022-03-14 15:55 (UTC) by sl1pkn07)
@ltara_kitsune build electron15 with ffmpeg4 solve my transmiission issues (without @Kyuunex workground)
Itara_Kitsune commented on 2022-03-12 19:05 (UTC)
@stick: Unfortunately swapping to Electron15 (make sure you change the Depends argument as well if that is what you're wanting to use) does not appear to fix the stream-crash issue. It only fixes the issue @Visne mentioned that crops up for copy/pasting images from some browsers directly into Discord.
stick commented on 2022-03-12 17:44 (UTC) (edited on 2022-03-12 17:44 (UTC) by stick)
@Itara_Kitsune @Visne @mattj I built the package to test with electron15 (because I am having the same watching-a-stream-crashes-discord issue) but that does not fix it.
Is there something else I missed to make it run with electron15?
Itara_Kitsune commented on 2022-03-11 20:13 (UTC)
@Visne and @mattj - Yerp, same here. I can broadcast but the moment someone turns on their camera or streams, Discord crashes continually until the feed is shut down.
mattj commented on 2022-03-10 20:25 (UTC)
@Visne also got this - any video stream crashes the client.
Visne commented on 2022-03-10 20:16 (UTC)
Popping out a livestream doesn't seem to work, it just keeps loading.
Visne commented on 2022-03-07 08:58 (UTC)
@Itara_Kitsune Seems like you're right, that fixes it. Can this package be changed to use Electron 15? Or are there specific reasons to use 16?
Itara_Kitsune commented on 2022-03-04 03:16 (UTC) (edited on 2022-03-04 03:17 (UTC) by Itara_Kitsune)
@Visne I have noticed that such functionality affects Brave as well. It does not appear to happen for as long as this package is using Electron 15 - something I noticed when they temporarily set it to use such.
Visne commented on 2022-03-04 00:13 (UTC)
For some reason I can't paste images I copied from Firefox or Chromium into Electron Discord, but I can into the normal Discord. Also, I can paste images from other applications into Electron Discord, and I can paste images from Electron Discord into Electron Discord, and I can paste images from Firefox or Chromium into other applications. So basically, only pasting images from Firefox and Chromium into Discord doesn't work, and all other kinds of pasting work fine. Can anyone reproduce this bug?
sl1pkn07 commented on 2022-03-03 21:22 (UTC)
@Kyuunex thanks for the workground
allexj commented on 2022-02-28 22:16 (UTC)
it's absurd that Discord team hasn't implemented screen share under Wayland yet. What a negligence
vibhas77 commented on 2022-02-28 20:03 (UTC)
Getting the Error: Cannot find module 'discord_desktop_core',
@Ghosthree3 's comment to change the /usr/bin/discord to use electron15 instead of electron worked for me.
Ghosthree3 commented on 2022-02-28 13:30 (UTC)
@HunabKu that is absolutely horrific, do not do that. Just have
electron15
orelectron16
installed and edit the mention of it in/usr/bin/discord
, so that it saysexec electron15
orexec electron16
instead of justexec electron
.You could also edit the PKGBUILD to depend on
electron15
orelectron16
instead ofelectron
and change line 49 to use said version instead then build and install it, but I couldn't be bothered. I already had electron15 installed for something else so I just changed the/usr/bin/discord
wrapper to use it until this package gets fixed (again).HunabKu commented on 2022-02-28 07:00 (UTC) (edited on 2022-03-02 05:12 (UTC) by HunabKu)
Confirmed works with :
sudo pacman -Rcsn electron
sudo pacman -S electron16
sudo ln /usr/bin/electron16 /usr/bin/electron
git clone https://aur.archlinux.org/discord_arch_electron
cd discord_arch_electron
replace 'electron' by 'electron16' in PKGBUILD file
makepkg -si
cd ..
rm -rf discord_arch_electron
zangoku commented on 2022-02-27 23:55 (UTC)
A fatal javascript error occured
when launching discord.SunRed commented on 2022-02-27 17:20 (UTC)
This package should depend on electron16 (and better yet back to electron15 since 16 breaks wayland support for discord) instead of electron.
Zoddo commented on 2022-02-27 17:19 (UTC)
I can confirm what Spixmaster experienced. Using
electron16
fixes the issue.Spixmaster commented on 2022-02-27 15:20 (UTC)
With electron version 17.1.0, Discord crashes immediately with error
Error: Cannot find module 'discord_desktop_core'
.Kyuunex commented on 2022-02-25 10:44 (UTC)
those who are getting crashes when trying to watch Go Live streams, can disable "OpenH264" setting in "Voice & Video" section to fix it.
ChrisLane commented on 2022-02-22 09:40 (UTC) (edited on 2022-02-22 09:40 (UTC) by ChrisLane)
I'm unable to launch discord with the "--enable-features=UseOzonePlatform --ozone-platform=wayland" flags for native wayland support since the move back to the main "electron" 16 package.
I'm guessing this is an issue on the electron/electron package side but since I don't have any other electron apps I haven't been able to confirm that.
Output:
antsif-a commented on 2022-02-21 13:38 (UTC)
Last update doesn't depend on
electron15
but uses it in/usr/bin/discord
, any way to fix it?SilverMight commented on 2022-02-20 22:40 (UTC)
Any way to get BetterDiscord to work with this?
Freso commented on 2022-02-20 09:41 (UTC)
You forgot to update https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=discord_arch_electron#n49 when you "fixed" the electron dependency. :)
wertercatt commented on 2022-02-19 22:29 (UTC)
This package shouldn't depend on 'electron' if it requires 'electron15.'
Saancreed commented on 2022-02-19 13:37 (UTC)
@mattrick I think it's because Discord doesn't like ffmpeg 5.0, downgrading Electron to previous version (from before ffmpeg 5.0 rebuild,
electron-16.0.8-1
orelectron15-15.3.7-1
depending on which one you use) should fix it for now, just make sure you also haveffmpeg4.4
package installed.mattrick commented on 2022-02-19 06:46 (UTC)
Is anyone else having issues with joining screen shares crashing Discord on the 0.0.17 version? This is the error I get:
CareAgain commented on 2022-02-18 19:58 (UTC)
@Sukid If I add --disable-gpu-memory-buffer-video-frames along with --enable-features=UseOzonePlatform and --enable-features=UseOzonePlatform then it seems to stop crashing. So worth a shot.
Sukid commented on 2022-02-18 18:43 (UTC)
@mattj I still get segfaults often when using both the ozone wayland flags and hardware acceleration flags. ... although sometimes it doesn't segfault and I'm having trouble finding what the cause of that is.
JonathanB commented on 2022-02-18 18:20 (UTC)
The patch below forgets to reset the pkgrel to 1. Other than that, works great!
Riedler commented on 2022-02-18 11:56 (UTC) (edited on 2022-02-18 12:13 (UTC) by Riedler)
update the version to 0.0.17 and the sha512sum to 728c760f04770b197635d1fc1a2833c707ab462708cc0bf6fb165691c1375e14e3192f3806d3719325790459b39bd3425f5942d69a53019695f02c965214a5c9 to update the package please. I've tested it & it runs just as fine as before with those changes.
Also, electron 16 could be used as well. Works for me.
bu.domino commented on 2022-02-18 09:30 (UTC) (edited on 2022-02-18 09:49 (UTC) by bu.domino)
To those who don't know how to apply patches, just change the lines manually.
mattj commented on 2022-02-18 00:54 (UTC)
I'm not sure if it was the 0.0.17 update (with the below patch) that fixed it, but Ozone Wayland flags are now working again.
fosskers commented on 2022-02-18 00:12 (UTC) (edited on 2022-02-18 00:12 (UTC) by fosskers)
The patch worked like a charm, thanks.
pendo324 commented on 2022-02-17 19:35 (UTC)
Patch to update to 0.0.17:
SunRed commented on 2022-02-13 11:25 (UTC)
This package should be renamed to
discord-electron-bin
to be consistent with the-canary
package.Zoddo commented on 2022-02-11 21:30 (UTC)
I can confirm the bug has been fixed with recent updates of the
electron
package. I believe the package can be switched back to electron16.intersectRaven commented on 2022-01-27 23:29 (UTC)
The crash with electron v16 has been addressed by the electron package. It should be fine with electron-16.0.7-3.
tsweet64 commented on 2022-01-27 01:57 (UTC)
Yes, I'm having the same issue
mattj commented on 2022-01-26 19:21 (UTC)
Anybody else's not working with wayland? Using the latest discord and electron 15.
It just still uses XWayland...
dangpzanco commented on 2022-01-26 16:04 (UTC)
@katt please ignore my last post, I just run the update again and it worked. Not sure why it hanged. Yes, I'm using Manjaro and I updated via
pamac
.katt commented on 2022-01-26 15:26 (UTC)
@dangpzanco electron15 is in the official repos: https://archlinux.org/packages/community/x86_64/electron15/ Are you using some kind of arch-based distro?
dangpzanco commented on 2022-01-26 01:15 (UTC) (edited on 2022-01-26 16:06 (UTC) by dangpzanco)
I'm somehow not affected by the bug (on Electron 16.07).
Edit (ignore the following): Now the package won't build for me... Do I need to downgrade
electron
? How?intersectRaven commented on 2022-01-25 23:46 (UTC)
Seems it's got something to do with the latest electron update about wlroot. I just rolled back my electron instead of updating my AUR package that will use 15.
Neko-san commented on 2022-01-25 19:22 (UTC)
I get some kind of crash / restart every time I scroll up in a server :v
SeriousBug commented on 2022-01-25 18:59 (UTC)
Is anyone else experiencing crashes with this after an update?
Electron v16.0.7.
Strykar commented on 2021-12-27 15:16 (UTC) (edited on 2021-12-27 15:28 (UTC) by Strykar)
Fails to start with
A Javascript error occured in the main process
. I'm unable to copy the error log to paste here, but here's a screenshot: https://i.imgur.com/rVhDyfS.png Weirdly, it works fine if launched as/usr/bin/discord
from a terminalsailorzoop commented on 2021-12-03 07:41 (UTC)
Sadly this build doesn't like to work with other software. For example "discordrp-mpris" is giving me
ERROR:discord_rpc.async_:failed to open '/run/user/1000/discord-ipc-0': [Errno 111] Connection refused
Couldn't get betterdiscord working either.
juxuanu commented on 2021-11-26 00:51 (UTC)
Recent update of Electron to a new major version (16) does make Discord crash or behave buggy.
For now, downgrading Electron to its latest 15 version does fix it.
As a side note: I've been able to avoid Discord coredumping on start by launching it from terminal. I don't understand why.
CareAgain commented on 2021-11-11 23:29 (UTC)
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.
zachcheatham commented on 2021-10-22 03:00 (UTC) (edited on 2021-10-22 03:14 (UTC) by zachcheatham)
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.
peterthegray commented on 2021-09-27 23:34 (UTC) (edited on 2021-09-27 23:36 (UTC) by peterthegray)
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:
tsweet64 commented on 2021-09-24 07:30 (UTC)
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.
OctopusET commented on 2021-09-23 14:31 (UTC) (edited on 2021-09-23 14:35 (UTC) by OctopusET)
I got this error on wayland 1.19.0-1 sway-git r6780.b7b96399-1: edit: before I update, it worked very well.
jns0l3nt commented on 2021-09-22 19:06 (UTC)
Really quick with the updates, wonderful work johnnyapol!
Neko-san commented on 2021-08-19 04:25 (UTC) (edited on 2021-08-19 04:29 (UTC) by Neko-san)
@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
MuffinBomber commented on 2021-08-18 06:55 (UTC) (edited on 2021-08-19 22:27 (UTC) by MuffinBomber)
@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.
Neko-san commented on 2021-08-18 06:52 (UTC)
@MuffinBomber Running that loads Discord just fine but doing it with firejail didn't even get past the "launch loading" window:
MuffinBomber commented on 2021-08-18 06:46 (UTC)
@Neko-san Seems like GPU acceleration is broken for some reason. Try running
discord --disable-gpu
.Neko-san commented on 2021-08-18 06:30 (UTC)
I also added
gzip
andwget
to theprivate-bin
line you showed me because Discord was complaining it wasn't able to send crash reportsMuffinBomber commented on 2021-08-18 06:23 (UTC)
@Neko-san Hmmm... What does
firejail --debug discord
output?Neko-san commented on 2021-08-18 06:18 (UTC)
@MuffinBomber It "worked" but Discord just rendered a blank dark-mode window :/
MuffinBomber commented on 2021-08-18 05:40 (UTC)
@Neko-san Create ~/.config/firejail/discord.local that contains
Neko-san commented on 2021-08-17 08:06 (UTC)
Would someone be able to tell me how to run this in
firejail
? I tried to do so with:but it just wouldn't work :/
Neko-san commented on 2021-07-28 06:41 (UTC)
@johnnyapol A friend of mine found an awesome solution to an irritating issue I've had for ages
For some reason, Discord suffers from a weird low FPS issue on Linux and has for a long time but he figured out how to fix it just by appending this line to the end of the exec call in the .desktop file:
--enable-accelerated-mjpeg-decode --enable-accelerated-video --ignore-gpu-blacklist --enable-native-gpu-memory-buffers --enable-gpu-rasterization
Despite some of these arguments actually being enabled in the settings and not fixing the issue, doing this somehow fixes the slow and jagged loading and animations in Discord
IoIxD commented on 2021-07-13 19:00 (UTC) (edited on 2021-07-13 19:05 (UTC) by IoIxD)
This uses more memory then regular Discord on my end; close to 1GB used as opposed to vanilla Discord's 750-800MB. What exactly do you mean by "increased performance"?
EDIT: I reinstalled it one last time and it seems to use 0-1% cpu as opposed to Discord's 2%. I guess that's a performance improvement but it also randomly jumps up to 11% if not more, so I don't think it's worth it. I wager that on weaker hardware (I am using an 8 core Ryzen which boosts to 4GHz) it makes more of a difference.
monosans commented on 2021-07-07 08:48 (UTC)
Has anyone managed to use BetterDiscord with this package?
godvino commented on 2021-07-04 09:57 (UTC)
Would it be possible to integrate something like https://github.com/flathub/com.discordapp.Discord/pull/155 into this AUR package ?
perigoso commented on 2021-06-21 17:54 (UTC) (edited on 2021-07-01 14:19 (UTC) by perigoso)
I had the same issues as @Friz64, following his fix, i modified the PKGBUILD to use the existing repo pkg electron12, this fixed it without altering/downgrading the system default electron
Consider an approach like the vscode package PKGBUILD with a electron variable
_electron=electron12
since this seems to be a recurring issueI also agree the package should be renamed to
discord-electron
Friz64 commented on 2021-06-19 13:21 (UTC)
Arch Linux's update to electron 13 (13.1.2-1) has introduced some issues for me on GNOME/X11/AMD
Downgrading to electron 12 seems to solve my issue for now: https://wiki.archlinux.org/title/Downgrading_packages#Using_the_pacman_cache
Sukid commented on 2021-06-19 12:44 (UTC)
Anyone else crashing when trying to run this in Wayland mode?
Kyuunex commented on 2021-05-26 02:42 (UTC)
consider renaming the package to
discord-electron
allexj commented on 2021-05-22 13:20 (UTC) (edited on 2022-02-28 22:16 (UTC) by allexj)
in order to be able to share the ENTIRE screen, or to be able to share wayland only (not xwayland) windows it's not enough to have Pipewire installed, because there's one chromium flag to manually enable pipewire support. I don't know how to enable it in this package so I tried it using discord via Google Chrome browser, and enabling "enable-webrtc-pipewire-capturer" flag in chrome://flags, and now it works.
Is there a way to enable this flag in this package without the need to use Google Chrome to be properly share screen?
EDIT: you can do the same thing with Firefox
encrypt3d commented on 2021-05-20 00:43 (UTC)
The PKGBUILD isn't that large, it shouldn't take too much effort to tweak it to work with PTB if you want to try to do it yourself.
lunax commented on 2021-04-26 02:24 (UTC)
Someone make Discord PTB version of this? Or guide for it? Thanks in advance.
ersei commented on 2021-04-02 16:40 (UTC)
This can read from a flags file like the chromium package, but it would be under
$HOME/.config/electron-flags.conf
, and this is applied to all Electron packages using the system electron (I think).salad commented on 2021-04-02 15:41 (UTC) (edited on 2021-04-02 15:41 (UTC) by salad)
If anyone's having issues under a Wayland environment with Discord (or any
electron
app orchromium
) crashing when launching under Electron's Ozone Wayland, try passing the following flag toelectron
:--disable-gpu-memory-buffer-video-frames
This crash is caused by a bug that doesn't exist under Linux 5.10. This should fix crashing on Linux 5.11 and 5.12 (tested on rc4).
All my
electron
(andchromium
) flags for reference:--enable-features=UseOzonePlatform --ozone-platform=wayland --disable-gpu-memory-buffer-video-frames --enable-gpu
Spanner_Man commented on 2021-04-02 09:21 (UTC)
How would you go about using something like BetterDiscord with this?
glorious-yellow commented on 2021-03-30 20:04 (UTC)
Hi,
Can the start script read from a flags file (discord-flags.conf) like the
chromium
package?Thanks.
G4b1t commented on 2021-03-26 18:45 (UTC)
Confirmed, double back mouse button is stock Discord's problem.
melvyn2 commented on 2021-03-25 02:30 (UTC)
I'm having both the betterdiscord and mouse button problem; the mouse button problem is part of stock discord though.
G4b1t commented on 2021-03-24 19:46 (UTC)
I face a problem where using mouse button for going back registers twice. Any help how to fix or workaround this? I'm on Manjaro 21.0 Ornara KDE Plasma.
KarlWithK commented on 2021-03-24 01:22 (UTC)
Is anyone having trouble installing betterdiscord once it updates to the newest version? I'm getting a "your discord installation has continuously failed to update and is now very out of date" warning from discord if I try to do
betterdiscordctl install
. Does anyone know a solution for this?sumfahg commented on 2021-03-24 01:20 (UTC)
Same problem as @ibrokemypie and @shket, the standalone package works fine but as soon as I try to install betterdiscord, I get an error message about my installation being "way out of date."
RicArch97 commented on 2021-03-23 16:35 (UTC) (edited on 2021-03-24 01:33 (UTC) by RicArch97)
Fails with
electron12-bin
v12.0.1-1 with the following error:libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
. I have thelibva libva-mesa-driver
and 32 bit variants installed.UPDATE
Confirmed working with
electron12-bin v12.0.1-1
with version 0.0.14-1.r00tman commented on 2021-03-11 16:09 (UTC) (edited on 2021-03-11 16:09 (UTC) by r00tman)
electron-beta-bin
switched to version 13. Discord should still work well with version 12, e.g.,electron12-bin
BowDown097 commented on 2021-03-11 15:44 (UTC) (edited on 2021-03-11 15:45 (UTC) by BowDown097)
it seems this no longer works on latest release of electron-beta-bin (13.0.0.beta.3-1)
steen commented on 2021-03-09 02:22 (UTC)
This installs fine on aarch4, no reason to force x86_64 architecture
shket commented on 2021-02-27 22:07 (UTC) (edited on 2021-02-27 22:08 (UTC) by shket)
i have the same problem as @ibrokemypie. with betterdiscord this discord offers to download update from the website and don't start as well.
ibrokemypie commented on 2021-02-26 06:21 (UTC)
betterdiscord seems to break discord since the electron10 to electron change for me
r00tman commented on 2021-02-26 01:06 (UTC)
Thank you for the package!
BTW, with
electron-beta-bin
(electron 12) instead ofelectron10
, Discord finally runs natively on Wayland!In
/usr/bin/discord
, I just replacedelectron10
withelectron-beta
and added these arguments:--enable-features=UseOzonePlatform,WebRTCPipeWireCapturer --ozone-platform=wayland --enable-gpu
. IDK whether screen sharing/calls actually work, but other than that it works great.OctopusET commented on 2021-02-25 05:33 (UTC)
There is a bug that autostart script path is electron, not the discord.
monosans commented on 2021-02-06 10:31 (UTC)
The Electron 11 crash was fixed in Electron 11.2.2
Dennis commented on 2021-02-01 09:17 (UTC)
I am getting a segfault every time I try to screenshare in voicechats ( https://bbs.archlinux.org/viewtopic.php?id=263181 ). Is anyone else experiencing that issue and/or has a solution/ideas?
johnnyapol commented on 2021-01-13 18:02 (UTC)
Update on the situation: This is a confirmed regression in electron11 (not a discord bug). I will bump back up to electron11 pending a release containing the resolution of https://github.com/electron/electron/issues/27303 .
johnnyapol commented on 2021-01-13 16:21 (UTC)
Hi everyone - thanks for the comments. I've gone ahead and (temporarily) bumped the electron down to
electron10
in the repositories to work around this.le_tucan commented on 2021-01-13 15:33 (UTC)
In case you upgraded and did not keep the old version around, check out the archive https://archive.archlinux.org/packages/e/electron/ download both 11.1.1 files. Then install with
pacman -U /path/to/electron-11.1.1-1-x86_64.pkg.tar.zst
NoXPhasma commented on 2021-01-13 10:18 (UTC)
@mvdan It is indeed electron 11.2.0 to blame. Downgrading to 11.1.1 fixed the crash.
mvdan commented on 2021-01-13 09:32 (UTC)
Adding to what others said. The upgrade of community/electron to 11.2.0-1 is most likely to blame.
zangoku commented on 2021-01-13 07:37 (UTC) (edited on 2021-01-13 07:42 (UTC) by zangoku)
crashing with this:
Neko-san commented on 2021-01-13 06:20 (UTC) (edited on 2021-01-13 06:21 (UTC) by Neko-san)
After a repository update I just did, Discord seems to not want to start for some reason I can't discern. It attempts to but then doesn't.
It checks for updates then just closes.
Modelmat commented on 2021-01-11 01:42 (UTC)
Is it possible to get notifications to appear as "Discord", not Electron?
https://i.imgur.com/vFaVADj.png is how the notifications appear under KDE.
PrfStrwberry commented on 2021-01-06 08:55 (UTC) (edited on 2021-01-20 20:58 (UTC) by PrfStrwberry)
EDIT: it was caused by firejail. My config was to start every program by firejail with onetime setup #firecfg. After cleaning the entries with firecfg --clean discord started without any problem. Although one or two months ago, I was able to start discord with firejail enabled.
My discord will not start. When I use the .desktop file, nothing happens.
Typing discord in terminal and I will get this:
VGrol commented on 2020-12-28 11:10 (UTC)
Would it be possible to fix the naming convention of the running progress, in order to better support Beautifuldiscord?
It looks for the running executable, normally named 'discord', but this package makes it run under electron. The tag under
ps -eo comm=,
is what I believe to be the trigger.bitschiff commented on 2020-12-23 16:51 (UTC)
@Kyuunex there is a temporary solution. If you highlight the entire word before you right click on it, the spellchecker will show suggestions.
Kyuunex commented on 2020-12-22 20:23 (UTC)
spellcheck on this seems to be partially broken compared to the official, untouched discord. it does show the red underlines but it does not show suggestions
ChrisLane commented on 2020-12-22 13:58 (UTC) (edited on 2020-12-22 14:05 (UTC) by ChrisLane)
Nevermind, since I'm using the
electron-ozone
package, I think I just need to compile the latest version with the icu68 patch and it will useicu
68 from core.ChrisLane commented on 2020-12-22 12:17 (UTC) (edited on 2020-12-22 12:24 (UTC) by ChrisLane)
I had the same issue as @solace but discord was looking for version 67 of the lib. Since there's no icu67 package, I've created one, installed it and now discord runs.
My error was
So if you're having the same problem as me, you can add
icu67
to your dependencies.solace commented on 2020-12-22 07:44 (UTC)
Newest electron update (electron6-6.1.12-3) breaks discord electron. Discord fails to open. This is the output I get when I try to run it: electron: error while loading shared libraries: libicui18n.so.68: cannot open shared object file: No such file or directory
Zern commented on 2020-12-19 08:01 (UTC)
@fadedave Facing a simillar issue, seems to be releated to arch's electron update and betterdiscord. Looking through the electron dev console there is always an error saying:
Unable to load preload script: /home/$USER/.config/discord/0.0.13/modules/discord_desktop_core/injector/betterdiscord/preload.js
Removing betterdiscord fixes the issue.
Unfortunately Im not proficient enough in js to figure it out from there. Anyone have ideas?
fadedave commented on 2020-12-15 06:29 (UTC) (edited on 2020-12-15 06:29 (UTC) by fadedave)
Launching discord_arch_electron, I get the error message "Your installation is very out of date", and it doesn't let me use discord. The same version of the official app works fine.
KarlWithK commented on 2020-12-06 06:43 (UTC) (edited on 2020-12-06 06:48 (UTC) by KarlWithK)
As ChrisLane suggested, I got discord to launch by editing
/usr/lib/discord
to the following:thebombzen commented on 2020-12-05 14:32 (UTC)
Would it make sense to rename this package to discord-arch-electron from discord_arch_electron just for naming conventions? ngl the underscores are annoying me a bit
bool3max commented on 2020-12-05 14:17 (UTC) (edited on 2020-12-05 14:19 (UTC) by bool3max)
@jabra
Run discord using
electron /usr/lib/discord/app.asar
. However the/usr/bin/discord
was updated to reflect this change as far as I can see.The problem was that
/usr/lib/discord/app
was renamed to/usr/lib/discord/app.asar
jabra commented on 2020-12-05 14:11 (UTC)
Hi, I'm getting this error since the last update. Any there any known fixes?
ChrisLane commented on 2020-12-05 11:15 (UTC) (edited on 2020-12-05 15:54 (UTC) by ChrisLane)
Since the update yesterday, I've been unable to launch Discord. I get the following error:
Guessing Discord is perhaps not compatible with electron 11.0.1 just yet.
Edit: Launching from /usr/lib/discord/app.asar.unpacked worked
pitbuster commented on 2020-12-03 19:41 (UTC) (edited on 2020-12-03 19:41 (UTC) by pitbuster)
I noticed that the Discord window doesn't get the proper icon with this package, opposed to the situation with the
discord
package.Does anyone knows how to fix this?
NoXPhasma commented on 2020-11-25 00:08 (UTC)
@huyizheng Your updated PKGBUILD works for me, thank you.
huyz commented on 2020-11-24 13:20 (UTC)
@NoXPhasma @MGThePro I created an updated PKGBUILD to resolve this issue. BetterDiscord works fine at least in my case.
huyz commented on 2020-11-24 13:09 (UTC)
@NoXPhasma @MGThePro I found a temporary workaround of BetterDiscord:
Run
sudo asar p /usr/lib/discord/app /usr/lib/discord/app.asar
Then modify
/usr/bin/discord
and change/usr/lib/discord/app
into/usr/lib/discord/app.asar
. Now BetterDiscord should work.MGThePro commented on 2020-11-24 12:11 (UTC)
I'm having the same issue as NoXPhasma. Reverting to the second latest PKGBUILD fixed it for me as well.
NoXPhasma commented on 2020-11-22 18:30 (UTC)
The changes in the last version (0.0.12-4) broke the support for BetterDiscord for me. It still works in the package from the repositories and the previous AUR build.
johnnyapol commented on 2020-11-19 14:36 (UTC)
Thanks @huyizheng, I've gone ahead and tested it and it worked fine for me, I've pushed 0.0.12-4 to incorporate this.
huyz commented on 2020-11-19 06:07 (UTC)
Well, after I extract Discord's
app.asar
, I found that the filebuild_info.json
anddiscord.png
is only used once. So instead of hacking these files into system electron's directory, perhaps it's better to just hack Discord'sapp.asar
itself to point these files to Discord's directory.This hack is easy, just run
asar e app.asar app
to extractapp.asar
, then modifyapp_bootstrap/buildInfo.js
andapp_bootstrap/autoStart/linux.js
and change the path of these two files.Here's my new
PKGBUILD
that applies this hack:Sukid commented on 2020-11-12 05:47 (UTC)
Thank you so much for this. Combined with electron-ozone Discord is working better than it ever has on any platform for me!
IS it possible to get other electron apps running this way? Would love it for lbry in particular.
LiveLM commented on 2020-10-31 21:48 (UTC)
Thanks for making this! For some reason, the regular Discord package is very laggy for me. This performs way better.
johnnyapol commented on 2020-10-22 14:04 (UTC)
Hey @codicodi, version discord_arch_electron-0.1.12-3 has that now. Thanks for the suggestion!
codicodi commented on 2020-10-22 12:00 (UTC)
It would be nice if the shell wrapper (/usr/bin/discord) had an
exec electron ...
. The way it is now, shell process stays up for no reason until discord is closed.Hanabishi commented on 2020-10-22 11:36 (UTC)
The day when this package shine has come :)
Because Electron included in the official client doesn't work anymore.
Kodehawa commented on 2020-10-21 19:17 (UTC)
I agree with @aviallon in regards to the unconventional name. I think discord-system-electron-bin or discord-electron-bin will fit better :)
aviallon commented on 2020-10-13 11:35 (UTC)
Nice package! However, I think that the package name is a bit weird and doesn't follow conventional package naming. I think you should rename it to
discord-electron
, as there it is already used by some packages, and you do not need to remind AUR users that this is an Arch package. This is just my two cents, but I do think it would make more sense.PS: For renaming a package, ask a TU.
johnnyapol commented on 2020-09-10 20:21 (UTC) (edited on 2020-09-10 20:24 (UTC) by johnnyapol)
Hi EggheadCammy, update has been pushed. EDIT: Please use 0.0.12-2. The sha512 fails in 0.0.12-1
EggheadCammy commented on 2020-09-10 20:11 (UTC)
Please update PKGBUILD to support 0.0.12
trey.merkley commented on 2020-08-28 14:04 (UTC)
Just rebuilt and it works great. Thanks @johnnyapol!
johnnyapol commented on 2020-08-27 14:41 (UTC)
Thanks for the info @trey.merkley, I've gone ahead and fixed that in 0.0.11-2
trey.merkley commented on 2020-08-27 14:25 (UTC)
--start-minimized
option is currently borked, otherwise works really well, thanks!OmegaDarkMage commented on 2020-08-06 22:00 (UTC) (edited on 2020-08-06 22:00 (UTC) by OmegaDarkMage)
Cool, never thought I'd see spellcheck in Linux.
johnnyapol commented on 2020-08-06 17:56 (UTC) (edited on 2021-03-24 00:28 (UTC) by johnnyapol)
Last update: 3/23/2021
acolannino64 commented on 2020-07-28 02:36 (UTC)
nice, I can spell again! (working spellchecker with this build)