Package Details: discord-canary-electron-bin 0.0.381-2

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 (FivePB, Auxim)
Last Packager: Auxim
Votes: 37
Popularity: 0.41
First Submitted: 2020-10-22 03:49 (UTC)
Last Updated: 2024-05-04 14:59 (UTC)

Dependencies (17)

Required by (9)

Sources (4)

Pinned Comments

Kodehawa commented on 2020-10-22 04:06 (UTC) (edited on 2024-01-04 20:06 (UTC) by Kodehawa)

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.

Discord on the latest version uses Electron 22 by itself. Might be worth using the official version if that is what you're after.

!! As Electron 28 joined the official repos, I've pinned this to electron26 instead, as using Electron 28 results on a crash at startup. If it ever works with Electron 28, please let me know.

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9

Kodehawa commented on 2021-01-24 16:46 (UTC) (edited on 2021-01-26 14:56 (UTC) by Kodehawa)

Color me surprised, but the Discord bug is still in electron 11.2.1. Guess I'll have to eat it for now...

More info:

Upstream bug report: https://github.com/electron/electron/issues/27303

(Open at the time of comment) PR: https://github.com/electron/electron/pull/27441

Until those bugs are fixed go back to electron 11.1.1 (or earlier, if you fancy) else discord will NOT start! Hold the electron update if you have it on your cache still.

EDIT: I updated electron-ozone with a patch for the fix. There's still an issue on mainline electron which will be fixed on 11.2.2.

juxuanu commented on 2021-01-14 14:12 (UTC)

I will hold the update of Electron for now. When the upstream issue is fixed and a new release happens, I'll update it again.

Thanks for the info.

Kodehawa commented on 2021-01-13 18:46 (UTC)

@juxuanu This is an issue upstream on Electron 11

https://github.com/electron/electron/issues/27303 You can use electron10 meanwhile. (Change the PKGBUILD with the contents of https://aur.archlinux.org/cgit/aur.git/commit/?h=discord_arch_electron&id=430c1ca7b9fdb668a6c18db215b6f6c8f4c1d766)

I personally don't know if I should change it to electron10, since I use this package with electron-ozone and that's definitely not Electron 10. Little cursed for sure, but oops.

You all can tell me what you all want though.

Kodehawa commented on 2021-01-13 14:37 (UTC)

@juxuanu huh, does this also break the discord_arch_electron package?

Seems like it is. I'll take a look, but Discord does some very specific stuff and uses their own fork of Electron. Maybe something broke in-between there.

juxuanu commented on 2021-01-13 10:29 (UTC)

Latest electron update from community repos breaks this package. You can try launching from terminal to check that out. Downgrading electron fixes the problem. Any ideas?

Kodehawa commented on 2020-11-20 08:19 (UTC)

Applied https://aur.archlinux.org/packages/discord_arch_electron/#comment-776307 to this aswell.

Kodehawa commented on 2020-10-22 04:06 (UTC) (edited on 2024-01-04 20:06 (UTC) by Kodehawa)

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.

Discord on the latest version uses Electron 22 by itself. Might be worth using the official version if that is what you're after.

!! As Electron 28 joined the official repos, I've pinned this to electron26 instead, as using Electron 28 results on a crash at startup. If it ever works with Electron 28, please let me know.