Plover AppImage from AUR wont start

[Lord3n20]

I am using Arch Linux with the cachyos repos. I had the same problem when I removed the repos.
What I did:
Install very basic Arch Linux with dwm, dmenu, twmn, st, firefox, yay
Added the cachyos repos
Installed plover-appimage from the arch extra-repository with yay

Started via st because it woudnt start with dmenu
Expected behavior:
plover starts.
Actual behavior:
enzo@tux ~ $ plover notify-send: /tmp/.mount_plovercCTAg4/usr/lib/libsystemd.so.0: version LIBSYSTEMD_251' not found (required by /usr/lib/libmount.so.1)
`
Same error with dunst (I tried it cause notify-send doesnt like twmn)

Does anyone have an idea how to resolv this issue?
I moved from artix with wayland to arch with dwm just to be able to use my starboard in german (Javelin would also be a workaround for me, I do not know how to set it up properly for german though)

[aqwek]

All AUR packages for plover are unofficial. The only up to date one is plover, and plover-appimage package hasn't been updated since February. I don't have any contact with the current maintainer of this package, so the only solutions to this at the moment is to use the AppImage from the releases page, or use the (buggy) plover AUR package.

[M108]

This issue also impacts the AppImage from the releases page as well (and it appears to impact other AppImage releases for other applications and not just Plover). Here's a full detailed root cause analysis and a work around

raspberrypi/rpi-imager#1577 (comment)

Please let me know if you get this work for you

[M108]

While I was able to reproduce the issue on my own CachyOS instance (version 7.0.9-1), I couldn't reproduce this issue on ElementaryOS and it worked out-of-the-box for the most part.

[gorbit99]

I'm also seeing this issue both with the AUR version and with the release version

EDIT: After doing the fix from above (extracting the appimage, removing the problematic lib file, repackaging), I still had 2 issues come up:

1. I didn't have a notification daemon running. The plover AUR package didn't care about this, but the appimage doesn't start at all. Installing and launching dunst fixed this issue.
2. For some reason the pkexec calls meant for installing udev rules just didn't want to work, even when I entered my password correctly or copy pasted it in just to make sure, it told me that I wasn't authorized and stopped. I had to manualy create the plover group, add myself to it and create the relevant udev rule file.

[VaagaiTheVague]

I'm on Omarchy. I experienced the same issue with v5.3.0, but the v5.4.0　AppImage runs flawlessly on my system now.

[Lord3n20]

I resorted to using Javelin instead, that one works on everthing I wanna use Steno on and even allows me to use my keyboard another way.
Link to the Javelin Tools etc:
https://lim.au/