Package Details: discord-canary-electron-bin 0.0.125-1

Git Clone URL: https://aur.archlinux.org/discord-canary-electron-bin.git (read-only, click to copy)
Package Base: discord-canary-electron-bin
Description: Discord Canary (popular voice + video app) using the system provided electron for increased security and performance
Upstream URL: https://canary.discordapp.com
Keywords: discord discord-canary electron
Licenses: custom
Conflicts: discord-canary
Provides: discord-canary
Submitter: Kodehawa
Maintainer: Kodehawa (chaotic-aur)
Last Packager: chaotic-aur
Votes: 18
Popularity: 3.62
First Submitted: 2020-10-22 03:49
Last Updated: 2021-06-15 20:55

Required by (0)

Sources (3)

Pinned Comments

Kodehawa commented on 2020-10-22 04:06

A shoutout to https://aur.archlinux.org/packages/discord_arch_electron/ (use that one if you want stable instead of canary!) :p

This is just a PKGBUILD based on the original discord-canary PKGBUILD and the discord_arch_electron PKGBUILD to use with Canary instead.

I'll keep it updated as I use Discord daily, so it'll bother me about it being outdated as soon as I turn on my PC :)

  • Confirmed working with Electron 9, 10 and 11 (and electron-ozone).

Latest Comments

1 2 Next › Last »

PedroHLC commented on 2021-06-21 13:54

I can guarantee that flags (Vulkan backend, accelerated-video, Skia, oop-rasterization, zero-copy, harmony, v8-cache) work. But sadly (at least last time I checked), there is none to enforce pipewire's screen sharing to work.

I imagine we need someone to patch the JS side of this and implement the interface @fine2006 mentioned (something similar was discussed in MS' teams repo), or maybe a flag in the chromium-side to wrap the old screen-sharing to work out-of-box with the new one.

If someone comes with it, feel free to submit a PR to https://github.com/chaotic-aur/pkgbuild-discord-canary-electron-bin and the github-action will resubmit it here once it gets merged.

juxuanu commented on 2021-06-21 13:37

This uses electron, which can be configured with ~/.config/electron-flags.conf the same way you do with chromium-flags.conf

fine2006 commented on 2021-06-21 13:31

@allexj I face the same issue but it seems like discord hasn't implemented org.freedesktop.portal.ScreenCast, which is required for sharing things.

allexj commented on 2021-05-22 13:20

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?

salad commented on 2021-04-02 15:35

@Seqularise I was able to fix the crashing by passing the following flag to electron: --disable-gpu-memory-buffer-video-frames

Also fixes Chromium issues. My full flags are (not sure if --enable-gpu does anything, haven't tested): --enable-features=UseOzonePlatform --ozone-platform=wayland --disable-gpu-memory-buffer-video-frames --enable-gpu

Seqularise commented on 2021-02-24 21:31

Its crashing kwin-wayland with linux-5.11 I can reproduce this by downgrading\updating kernel

bbaovanc commented on 2021-02-10 23:13

Looks like they added Electron 11.2.3 to the repos. It works now! I might delete the discord-canary-electron10-bin package now.

Kodehawa commented on 2021-02-04 04:03

@sperg512 Ah. It wasn't tagged on electronjs.org. Should've checked github haha

I'll update electron-ozone tomorrow. One less patch to mantain is always good. I guess electron will be updated in the upcoming days on the main repos.

sperg512 commented on 2021-02-04 01:43

@Kodehawa incredible lie https://github.com/electron/electron/releases/tag/v11.2.2

Kodehawa commented on 2021-02-03 18:48

@sperg512 11.2.2 hasn't been released yet, sadly. Should be fine once it released. I patched electron-ozone to include a fix. Maybe open a bug report to the arch guys so it could be backported to 11.1.1?

Patch: https://aur.archlinux.org/cgit/aur.git/tree/0001-fix-don-t-throw-on-bad-icons-in-BrowserWindow-constr.patch?h=electron-ozone