Legcord stopped showing up as a system tray icon after latest stable update

[zanzum]

Thanks for the update and I appreciate all the work and time that goes into this.

One issue though that happened after the update. Legcord (Alternative Discord app mainly less resources.) stopped showing up as a system tray icon. No issue with regular Discord app and I can see discord in the Adaptation tab as well but no Legcord. No change after the latest Electron update either because that’s what I thought a new bug might have been introduced maybe still is there or somewhere else. Not sure if this is the right place to post this, it did happened after the update though and I haven’t put up an “ticket” on there github yet.

EDIT: Same with Goofcord by the way.

kinfo
Operating System: Manjaro Linux
KDE Plasma Version: 6.7.4
KDE Frameworks Version: 6.29.0
Qt Version: 6.11.1
Kernel Version: 7.2.0–1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 7900X 12-Core Processor
Memory: 64 Gibyte of RAM (62.0 Gibyte usable)
Graphics Processor 1: AMD Radeon RX 7900 XTX
Graphics Processor 2: AMD Ryzen 9 7900X 12-Core Processor

Thanks in advance.

[scotty65]

As legcord is an AUR package, did you remember to rebuild it after the system update? AUR packages often require rebuilding after system updates to ensure they link correctly to updated system libraries and other packages.

I noticed that the prebuilt version legcord-bin does have some recent comments on its AUR page which you might want to browse through, including this one:

ofluffydev commented on 2026-02-27 11:32 (AEDT) (edited on 2026-02-27 11:41 (AEDT) by ofluffydev)

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

If legcord-bin is installed on your system, then you might want to look at replacing it with the legcord package:

pamac build legcord

to see if it works better on your system. The prebuilt legcord-bin binary would have been built against Arch packages, and as you are on Manjaro Stable branch, there could be issues due the packages not being up-to-date with Arch.

AUR (en) - legcord

I just built legcord on my Unstable branch system and it launched without any issues. It doesn’t display a tray icon though even though I switched it on in the settings, however that could be due to me not setting up any accounts. But you might want to see if it works okay on your system.

---

Also, it is normally recommended that users wanting to install AUR packages should switch to Unstable branch (they can often be okay on Testing branch, which is usually about a week behind Arch).

Required reading for using the AUR:

[HowTo] Use the AUR

Difficulty: ★★☆☆☆ What is AUR? The Arch User Repository is an online repository, managed by the Arch community rather than the Arch packagers. AUR differs from the Manjaro repositories by multiple, important key points: AUR does not contain packages, but PKGBUILDs. See below for details. AUR is not managed by Manjaro. There is thus no official support for AUR packages. Package compatibility is not ensured for all points in time. See below for details. AUR is not managed by Arch …

[Need-To-Know] About Manjaro and AUR

TL:DR DISCLAIMER: AUR packages are user produced content. Any use of the provided files is at your own risk. sudo pacman-mirrors -aS unstable sudo pacman -Syu base-devel When you sync your system any CUSTOM package may cease to function without warning OR your system may cease to function due to a CUSTOM package - therefore one must remove all CUSTOM packages before an issue can be validated as related to Manjaro. custom packages - unsupported - you are on your own! Examples → Spectac…

Arch User Repository - ArchWiki

[Teo]

There is an upstream bug affecting all electron based apps - they don’t create tray icons anymore. We can only wait for the next patched version.

[zanzum]

Thanks @scotty65

I did remove it both in pamac gui and through pacman and installed other versions as well to test if only that version was affected that wasn’t the case though same thing with other’s I tried.

Thanks @Teo seems like I wasen’t totally wrong about Electron then and the bug is still there.

Cheers for the insight and info guys.

[Teo]

Until the next fixed electron arrives systemwide, you can try a flatpak or appimage. They would have their own electron built in, and it might be slightly older or newer and not affected.

[zanzum]

Thanks for the tip @Teo about there older versions didn’t know that. appimage/flatpak.

I think I wait till this bug is resolved and hopefully the prio is high enough to fix that as soon as possible. I just use vesktop in the meantime, it’s okey but not showing if you have messages to look into that legcord does have and I like that about it. so that’s where the sys tray icon comes in without it you can’t see if you have messages to still look into.

[Yochanan]

@Teo

They would have their own electron built in, and it might be slightly older or newer and not affected.

Correct. Upstream is using 43.2.0 which is unaffected.

[zanzum]

@Yochanan Damn. you’re right. The flathub version install is broken(missing link/shortcut) though, it started Electron and not the app so I had to kfind (locate/whereis didn’t show me.) it’s location. And then install Electron43. Fixed with some tinkering. Thanks guys.