Arch Linux User Repository

For anyone who hasn't discovered this already, you can ameliorate the impact of delayed AUR version updates by setting the following in your ~/.config/discordcanary/settings.json file:

{
  // preceding settings (add a trailing comma ,)
  "SKIP_HOST_UPDATE": true
}

Package version vs actual version often get out of sync, because the update mechanism break. Sometimes, when I update the package, it still launches old version. Downgrading have no effect, since it downloads the latest version as versions aren't pinned. It is effectively launcher wrapper and not packaged discord-canary anymore

Hiya, you can automate the hash checks, see my example for discord-canary-electron-bin here: https://github.com/ninetailedtori/Improved-PKGBUILDs/tree/discord-canary-electron-bin !

Krisp stopped working recently, perhaps a glibc update or something?

20:03:44.050 › [MediaEngineStore] Failed to load Krisp module: /home/<foo>/.config/discord/0.0.134/modules/discord_krisp/discord_krisp.node: undefined symbol: _ZN7OrtApis12CreateStatusE12OrtErrorCodePKc

I know the latest comment says this is fixed, but I am still having the same issue with "DiscordCanary" not being found.

chmod: cannot access '/home/ixvari/.cache/paru/clone/discord-canary/pkg/discord-canary/opt/discord-canary/DiscordCanary': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...

The version it says it is downloading is 1.0.927-1

Issues are fixed now, the package is installable and runnable again. I'll keep an eye on discord-ptb to see when the packaging changes roll out there.

@KubeRoot The package version bumps are indeed automated on a headless machine, with Discord occasionally pushing multiple version bumps (that each invalidate the previous version) in one day (yesterday it was... 9 bumps?) that is the only viable solution.

@Skycontroller Discord appears to have progressively been pulling in packaging changes over time, presumably there was a point in time between 2022 and now where Path and a full-path Exec was not part of the desktop file.

This does not currently build:

==> Making package: discord-canary 1.0.927-1 (Fri 17 Apr 2026 09:32:12 PM EDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found discord-canary-1.0.927.tar.gz
  -> Found LICENSE.html
  -> Found OSS-LICENSES.html
==> Validating source files with sha512sums...
    discord-canary-1.0.927.tar.gz ... Passed
    LICENSE.html ... Skipped
    OSS-LICENSES.html ... Skipped
==> Extracting sources...
  -> Extracting discord-canary-1.0.927.tar.gz with bsdtar
==> Starting prepare()...
==> Removing existing $pkgdir/ directory...
==> Entering fakeroot environment...
==> Starting package()...
chmod: cannot access '/home/kusoneko/.cache/aurutils/sync/discord-canary/pkg/discord-canary/opt/discord-canary/DiscordCanary': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...

Similarly, if I change the chmod line from $_pkgname to $pkgname that error goes away, however a new one appears, for the next chmod line:

==> Starting package()...
chmod: cannot access '/home/kusoneko/.cache/aurutils/sync/discord-canary/pkg/discord-canary/opt/discord-canary/chrome-sandbox': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...

That file indeed does not exist in the 1.0.927 archive downloaded from discord:

$ tar -tf discord-canary-1.0.927.tar.gz
DiscordCanary/
DiscordCanary/discord-canary.desktop
DiscordCanary/updater_bootstrap
DiscordCanary/discord.png
DiscordCanary/discord-canary
DiscordCanary/postinst.sh

I made a diff with the changes I made to make it build, however I do not know if something else needs changing or not (Note that the prepare() function is not modified because the directory in the tarball is still written DiscordCanary despite the new executable name matching the aur pkgname). :

diff --git a/PKGBUILD b/PKGBUILD
index 4d4955e..521e6a9 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -29,17 +29,17 @@ package() {
   install -d "$pkgdir"/opt/$pkgname
   cp -a $_pkgname/. "$pkgdir"/opt/$pkgname

-  chmod 755 "$pkgdir"/opt/$pkgname/$_pkgname
+  chmod 755 "$pkgdir"/opt/$pkgname/$pkgname # The executable is now discord-canary and not DiscordCanary

   rm "$pkgdir"/opt/$pkgname/postinst.sh

   install -d "$pkgdir"/usr/{bin,share/{pixmaps,applications}}
-  ln -s /opt/$pkgname/$_pkgname "$pkgdir"/usr/bin/$pkgname
+  ln -s /opt/$pkgname/$pkgname "$pkgdir"/usr/bin/$pkgname # The executable is now discord-canary and not DiscordCanary
   ln -s /opt/$pkgname/discord.png "$pkgdir"/usr/share/pixmaps/$pkgname.png
   ln -s /opt/$pkgname/$pkgname.desktop "$pkgdir"/usr/share/applications/$pkgname.desktop

   # setuid on chrome-sandbox
-  chmod u+s "$pkgdir"/opt/$pkgname/chrome-sandbox
+#  chmod u+s "$pkgdir"/opt/$pkgname/chrome-sandbox # There isn't a chrome-sandbox file anymore

   install -Dm644 LICENSE.html "$pkgdir"/usr/share/licenses/$pkgname/LICENSE.html
   install -Dm644 OSS-LICENSES.html "$pkgdir"/usr/share/licenses/$pkgname/OSS-LICENSES.html

The package seems to be currently broken, the executable seems to have been renamed from DiscordCanary to discord-canary? I'm a bit confused because the package seems to be getting rapidly updated, but not sure if those are just automated untested version bumps, or if there's something weirder going on.

Hey, any reason why we are appending Path to the .desktop file at the end? It already ships with it. Cheers