Arch Linux User Repository

Wayland/KDE users: the kalu-kde package supports the latest tray icon spec (SNI) properly since version 4.6.0 and will work for you. This package is for legacy (X11 / xembed) desktops.

I may merge the two packages in the future, in favor of one package that just supports everything (theoretically, kalu-kde already should - but I haven't tested that enough for me to feel save doing it now).

Wayland/KDE users: the kalu-kde package supports the latest tray icon spec (SNI) properly since version 4.6.0 and will work for you. This package is for legacy (X11 / xembed) desktops.

I may merge the two packages in the future, in favor of one package that just supports everything (theoretically, kalu-kde already should - but I haven't tested that enough for me to feel save doing it now).

@Thulinma Thanks for your help. I've confirmed that the package was built correctly with libalpm 15.0.0. The problem turned out to be with my custom package repository, specifically a caching issue that caused an outdated version to be prioritized locally despite the correct version being present on the server. Installing directly from the built package fixed the discrepancy. I appreciate your help in resolving this issue.

@acrion: Most likely you simply need to rebuild the package. Chances are it was built while you still had libalpm 14 installed, thus introducing the outdated dependency.

I wanted to follow up on the recent discussions about kalu’s compatibility with pacman 7.0.0. While it seems that the package has been updated to allow building against pacman 7.0, I’m still encountering issues when trying to run kalu after updating to version 4.5.2-2.

Specifically, I'm getting the following error:

kalu: error while loading shared libraries: libalpm.so.14: cannot open shared object file: No such file or directory

I’ve noticed that pacman 7.0.0 comes with libalpm 15.0.0, which might be the root cause of this issue. I've opened a GitHub issue to track this problem: https://github.com/Thulinma/kalu/issues/9

Has anyone else experienced this issue or found a workaround? If not, it might be worth investigating whether the kalu source code itself needs updates to work with the new libalpm version.

@Thulinma, I understand you're maintaining both the AUR package and the GitHub repository. Do you think this issue requires changes in the source code rather than just the PKGBUILD?

I’m happy to provide any additional information or assist with testing if needed.

Installing right now, but, isn´t it weird how jacky just vanished one day?

Thanks @Rhinoceros, that saved me a lot of time checking this myself - I've gone ahead and updated the package to allow building against pacman 7.0 (and updated pkgrel to 2).

@Thulinma I mentioned on the kalu-kde page, but I think it just needs a rebuild under pacman 7. It seems to work fine. (BTW if you want to add me as a co-maintainer, I can just bump the pkgrel and modify pacman>=6.1 for now.)

Just a quick note that I'm aware pacman updated to 7.0.0 - I'll take a look at what's needed to make kalu work again ASAP. Unfortunately I'm currently at a trade show, so it might take a day or two. Sorry for the wait!

I am getting that the package is incompatible for aarch64 systems. Can you please add aarch64 to the "arch" section? Thanks

@Thulinma No problem, priorities are very understandable. If you could share a reproducer for the crash I'd be willing to assist. For the moment kalu works flawlessly again on my arch box. Did several updates without crashing. Best of luck and thanks again for your time.