Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.rc > #405104

Bug#1120685: kmymoney segfaults when started

Show all headers | View raw

On Sat, 22 Nov 2025 12:18:20 +0100 Thomas Nemeth <tnemeth@free.fr> wrote:
> On Sat, 22 Nov 2025 11:50:11 +0100 Martin Steigerwald 
> <martin@lichtvoll.de> wrote:
> > 
> > My work-around currently still is:
> > 
> > % cat /etc/apt/preferences.d/kmymoney 
> > Explanation: Bug#1120685: kmymoney 5.1.3-2+b4 segfaults when started
> > Explanation: https://bugs.debian.org/1120685 
> > Package: kmymoney 
> > Pin: version 5.1.3-2+b2
> > Pin-Priority: 30000
> 
>     You still have to start kmymoney using LD_PRELOAD (at least that's
>     the case on my system). The problem is that even in that package,
>     kmymoney has been compiled against the version 2 of libsqlcipher :
> 
> ```bash
> ldd $(which kmymoney) | grep sqlcip
>         libsqlcipher.so.2 => /lib/x86_64-linux-gnu/libsqlcipher.so.2
> ```

    Well. There is that bug (in the build of the package against the
    wrong libsqlcipher version), but there is something else that
    troubles me :

```bash
$ sudo ldconfig -v 2>&1 | grep libsqlc
        libsqlcipher.so.1 -> libsqlcipher.so.1.8.0
        libsqlcipher.so.2 -> libsqlcipher.so.3.50.4
```

    libsqlcipher.so.2 is a link to libsqlcipher.so.3. The ABI between
    2 library versions major digit should not be fully compatible. Well
    readelf tells me that there are mainly _new_ functions. I don't have
    knowledge to check if the parameters of the functions that are the
    same in both versions are identical...

Back to linux.debian.bugs.rc | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Bug#1120685: kmymoney segfaults when started Thomas Nemeth <tnemeth@free.fr> - 2025-11-22 12:50 +0100
  Bug#1120685: kmymoney segfaults when started Dominique Dumont <domi.dumont@free.fr> - 2025-11-22 17:20 +0100

csiph-web