You are not logged in.

#1 2026-08-18 08:48:53

romeo-72
Member
Registered: 2024-12-07
Posts: 6

Upgrading KDE Frameworks to version 6.29

Hi everyone,

I encountered a small issue today where Dolphin completely refused to open immediately after upgrading KDE Frameworks to version 6.29. When launching dolphin via the terminal, it returned the following shared library error:

dolphin: error while loading shared libraries: liblmdb.so.1: cannot open shared object file: No such file or directory

Upon checking /usr/lib/, the lmdb package (version 0.9.35-1) only provides /usr/lib/liblmdb.so, but the current Dolphin binary explicitly looks for the older .so.1 naming convention, creating a broken dependency/binary mismatch.
Temporary Workaround for anyone facing the same issue is to create a symlink to trick the system into using the available library:

sudo ln -s /usr/lib/liblmdb.so /usr/lib/liblmdb.so.1
sudo ldconfig

The pkgs for Dolphin (or Baloo) needs a rebuild against the updated lmdb structure to eliminate this error out-of-the-box. Hope this helps the maintainers push an official fix quickly!

Offline

#2 2026-08-18 08:52:40

user_58181
Member
Registered: 2025-02-12
Posts: 2

Re: Upgrading KDE Frameworks to version 6.29

The problem appears to be with baloo 6.29.0-1and is already reported here:

Arch Linux baloo packaging issue #1

balooctl6: error while loading shared libraries: liblmdb.so.1: cannot open shared object file: No such file or directory

Temporary workaround

Downgrading Baloo to 6.28.0-1 fixes Dolphin.

If the previous package is still in the pacman cache:

sudo pacman -U /var/cache/pacman/pkg/baloo-6.28.0-1-x86_64.pkg.tar.zst

Otherwise install it from the Arch Linux Archive:

sudo pacman -U https://archive.archlinux.org/packages/b/baloo/baloo-6.28.0-1-x86_64.pkg.tar.zst

To temporarily prevent upgrading Baloo back to the broken version, add this under `[options]` in `/etc/pacman.conf`: `IgnorePkg = baloo`

Remove it once the package is fixed.

Offline

Board footer

Powered by FluxBB