Arch Linux User Repository

Unofficial Discord client has a risk of BAN. Use discord if possible.

@zxp19821005 as I and multiple people have stated, the issue is within the legcord helper script, not legcord itself. The script is built at some point in the PKGBUILD, which upstream legcord has no control over. I've explained the issue in depth already, and don't feel like repeating myself. Please read the original comments carefully, or simply merge the provided change I offered.

@ofluffydev All the components version of the package, please send the issue to the upstream.

legcord-bin breaks for me on every update due to an issue in the shipped launcher script.

From what I can tell, the packaging templates legcord.sh like this:

_OPTIONS="@options@"
...
exec electron@electronversion@ "${_RUNNAME}" "${_OPTIONS}" ...

and the PKGBUILD substitutes @options@ with:

env ELECTRON_OZONE_PLATFORM_HINT=auto

That means the installed wrapper ends up passing "env ELECTRON_OZONE_PLATFORM_HINT=auto" as a literal argument to Electron instead of executing it as env ... electron.... On Hyprland this results in Legcord launching and immediately exiting / no window.

I’ve been going in locally and picking apart /usr/bin/legcord to fix it after each update, but obviously that gets overwritten again.

I haven’t modified/patched an AUR package before (only tinkered with local pacman repos for custom archiso), so I’m not 100% sure of the proper way to submit a fix right now. I’ll attempt to fix the PKGBUILD/launcher on my end, but I’m leaving this comment for the maintainer since it seems like a packaging bug.

Suggested fix: make the env part a command prefix, e.g.:

exec env ELECTRON_OZONE_PLATFORM_HINT=auto electron@electronversion@ "${_RUNNAME}" ...

(or adjust the template to exec @options@ electron... and avoid quoting/passing it as an argv token).

EDIT: Here's a patch file thingy if you'd like, you might have to regen checksums but it should fix the problem. Also I notice @TSTdoll mentioned this issue, maybe stop re-adding it on new updates? I've even thrown in a comment to remind whoever edits it in the future...

diff --git a/legcord.sh b/legcord.sh index 753d12d..34fcf5c 100644 --- a/legcord.sh +++ b/legcord.sh @@ -2,7 +2,10 @@ set -e _APPDIR="/usr/lib/@appname@" _RUNNAME="${_APPDIR}/@runname@" -_OPTIONS="@options@" +# NOTE: @options@ expands to something like: +# env ELECTRON_OZONE_PLATFORM_HINT=auto +# It must be used as a command prefix (not passed as an electron arg). +_OPTIONS=@options@ export PATH="${_APPDIR}:${PATH}" export LD_LIBRARY_PATH="${_APPDIR}/swiftshader:${_APPDIR}/lib:${LD_LIBRARY_PATH}" export ELECTRON_IS_DEV=0 @@ -33,7 +36,7 @@ if [[ "${_WAYLAND_OPTION}" == true ]]; then fi cd "${_APPDIR}" if [[ "${EUID}" -ne 0 ]] || [[ "${ELECTRON_RUN_AS_NODE}" ]]; then - exec electron@electronversion@ "${_RUNNAME}" "${_OPTIONS}" "${flags[@]}" "$@" || exit $? + exec ${_OPTIONS} electron@electronversion@ "${_RUNNAME}" "${flags[@]}" "$@" || exit $? else - exec electron@electronversion@ "${_RUNNAME}" "${_OPTIONS}" --no-sandbox "${flags[@]}" "$@" || exit > -fi \ No newline at end of file + exec ${_OPTIONS} electron@electronversion@ "${_RUNNAME}" --no-sandbox "${flags[@]}" "$@" || exit $? +fi

As I mentioned previously,

_OPTIONS="env ELECTRON_OZONE_PLATFORM_HINT=auto"

line still breaks Legcord for me, and commenting it out makes it work again. The line should be removed from the package like it previously was in 1a9a4b37dde0 before it was erroneously re-added in 7ecc825c4a68.

This line in /usr/bin/legcord makes it exit immediately after opening for me:

_OPTIONS="env ELECTRON_OZONE_PLATFORM_HINT=auto"

Output:

$ legcord; echo exited with status $?
Legcord has been run before. Skipping setup.
Setting env ELECTRON_OZONE_PLATFORM_HINT to auto
exited with status 0

I use Sway, but I can also reproduce this problem from X11 in i3wm.

Commenting out that line lets Legcord run like normal. for me. It looks like that line was removed in 1a9a4b37dde0 with commit message ozone wayland is not default because it should not be. But the line was re-added in 7ecc825c4a68 for some reason? So it should probably be removed again.

Is this package gonna get updated anytime soon?

Unofficial Discord client has a risk of BAN. Use discord if possible.