./@joplinapp-desktop: error while loading shared libraries: libicui18n.so.68: cannot open shared object file: No such file or directory

[mrcolumbo]

I just installed GarudaLinux and then installed Joplin-desktop from chaotic aur ......

It installed without error but when I try to start it via terminal i get this error

./@joplinapp-desktop: error while loading shared libraries: libicui18n.so.68: cannot open shared object file: No such file or directory

any ideas what I need to do different to get it running?

thanks a lot in advance

[jonathon]

@mrcolumbo

error while loading shared libraries: libicui18n.so.68: cannot open shared object file: No such file or directory

This could be a partial upgrade:

Locale settings defined outside /etc/locale.conf

You are in a partial upgrade state. Fully update your system. Given that icu is central to localisation that could well explain the other issue you're having.

or joplinapp-desktop needs to be rebuilt:

FireDragon not launching after update

The reason behind this is the recent icu upgrade, firedragon (and lots of other packages using this library such as ungoogled-chromium, thunderbird-appmenu) needed a rebuild as the shared library changed. Actually I forgot to raise pkgrel when rebuilding - the solution is therefore: sudo pacman -Syu firedragon The AUR PKGBUILDs are not up to date as Im currently waiting for a TU to approve pending requests regarding package name changes which were explained in the FireDragon thread …

An AUR package stopped working after an update

The normal reasons Generally, there will be two reasons why an AUR package has “stopped working”: A repo package was updated and the AUR package was built against an older (and incompatible) version of that repo package; The AUR package was updated and requires a repo package version not present on your system. The solutions to these: Rebuild the AUR package. Update your system fully. The other reasons The other, less frequent reasons, are The package file (PKGBUILD) has an issue and nee…

[dr460nf1r3]

Its updated, please let us know if that fixed the issue

[mrcolumbo]

it fixed it - thanks a lot !!!!