Dear Maintainer, * What exactly did you do (or not do) that was effective (or ineffective)? Starting kmymoney * What was the outcome of this action? * What led up to the situation? Starting kmymoney * What outcome did you expect instead? reinhard@apollon:~$ kmymoney WebConnect: Try to connect to WebConnect server WebConnect: Connect to server failed WebConnect: Running in server mode 22 -- exe=/usr/bin/kmymoney 13 -- platform=xcb 11 -- display=:0 17 -- appname=kmymoney 17 -- apppath=/usr/bin 10 -- signal=11 10 -- pid=66349 17 -- appversion=5.1.3 21 -- programname=KMyMoney 31 -- bugaddress=submit@bugs.kde.org KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kmymoney path = /usr/bin pid = 66349 KCrash: Arguments: /usr/bin/kmymoney KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi [1]+ Angehalten kmymoney
I also got this segfault on startup immediately after upgrading to 5.1.3-2+b3 and I wanted to note that manually downgrading to the 5.1.3-2+b2 package on https://snapshot.debian.org/package/kmymoney/5.1.3-2/#kmymoney_5.1.3-2:2b:b2 is a good work-around until this bug is fixed. Francois
Dear Maintainer,
The issue remains in update 5.1.3-2+b4.
---
Starting debugger gdb -nw -n -batch --init-eval-command=set debuginfod enabled
on -x /tmp/drkonqi.RgEIZt -x /tmp/drkonqi.XNrBEh -p 25098 /usr/bin/kmymoney
[New LWP 25101]
[New LWP 25100]
[New LWP 25099]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__syscall_cancel_arch () at
../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
warning: 56 ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S: No such
file or directory
Traceback (most recent call last):
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 608, in
print_preamble
print_preamble_internal()
~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 582, in
print_preamble_internal
resolve_modules()
~~~~~~~~~~~~~~~^^
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 565, in
resolve_modules
raise RuntimeError("No corefile found. Cannot resolve modules.")
RuntimeError: No corefile found. Cannot resolve modules.
No corefile found. Cannot resolve modules.
A debugging session is active.
Inferior 1 [process 25098] will be detached.
Quit anyway? (y or n) [answered Y; input not from terminal]
[Inferior 1 (process 25098) detached]
Sentry is attempting to send 2 pending events
Waiting up to 30 seconds
Press Ctrl-C to quit
Debugging ended with exit code '1' and exit status 'NormalExit'
found -1 5.1.3-2+b4 thanks
There is an error in going from version 5.1.3-2+b2 to version 5.1.3-2+b3. The dependency for libsqlcipher was changed from libsqlcipher1 to libsqlcipher2. I deleted libsqlcipher.so.3.50.4 and copied libsqlcipher.so.1.8.0 to libsqlcipher.so.3.50.4 and the error was gone. Reinhard
using LD_PRELOAD with libsqlcipher.so.1 when starting kmymoney is working Reinhard
Great, Reinhard. I updated to version 5.1.3-2+b4, and now it works perfectly following your instruction. Thank you. Valdinilson
Hi.
A few days ago a new version of kmymoney brought this new "crashing
at startup" behavior. This morning an upgrade let me hope that was
resolved. However it was still crashing (in debian testing). When I
wanted to test the "unstable" version that seemed more recent
(5.2.1-1), the output at startup was a bit different from the
previous one :
```bash
$ kmymoney
Model for "ST" loaded with 4 items in 0 ms
Monetary values will be formatted based on locale "fr_FR" Example: "123,45 €"
Long date format "dddd d MMMM yyyy"
Short date format "dd/MM/yyyy"
Narrow date format "dd/MM/yyyy"
WebConnect: Try to connect to WebConnect server
WebConnect: Connect to server failed
WebConnect: Starting server failed. Try to remove stale socket.
WebConnect: Running in server mode
KCrash: appFilePath points to nullptr!
KCrash: Application '<unknown>' crashing... crashRecursionCounter = 2
Erreur de segmentation (core dumped)kmymoney
```
When I come back to the "testing" version :
```bash
$ kmymoney
WebConnect: Try to connect to WebConnect server
WebConnect: Connect to server failed
WebConnect: Starting server failed. Try to remove stale socket.
WebConnect: Running in server mode
22 -- exe=/usr/bin/kmymoney
13 -- platform=xcb
11 -- display=:0
17 -- appname=kmymoney
17 -- apppath=/usr/bin
10 -- signal=11
9 -- pid=6362
17 -- appversion=5.1.3
21 -- programname=KMyMoney
31 -- bugaddress=submit@bugs.kde.org
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kmymoney path = /usr/bin pid = 6362
KCrash: Arguments: /usr/bin/kmymoney
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
void ReportInterface::maybePickUpPostbox()
Available memory (GiB): 26
QThread::setPriority: Cannot set priority, thread is not running
adjusting gdb profile for size MemoryFence::Size::Spacious
QSocketNotifier: Invalid socket 7 and type 'Read', disabling...
QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
[1]+ Stoppé kmymoney
$ echo $?
147
```
It exits with the 147 error code after a SIGSEGV.
Dr. Konqi lamentably fails and no core dump is to be found even
though I unlimited core dump size :
```
qrc:/ui/MainPage.qml:71:9: QML MainPageButton: Binding loop detected for property "icon.height":
qrc:/ui/MainPageButton.qml:15:5
qrc:/ui/MainPage.qml:53:9: QML MainPageButton: Binding loop detected for property "icon.height":
qrc:/ui/MainPageButton.qml:15:5
Unable to start Dr. Konqi
Re-raising signal for core dump handling.
[1]+ Erreur de segmentation (core dumped)kmymoney
```
PLEASE HELP :) My wife won't pardon me if I'm not able to tell her
our expenses projections.
working
I tried that too but :
```bash
$ sudo ldconfig -v 2>&1 | grep libsqlcipher
libsqlcipher.so.2 -> libsqlcipher.so.3.50.4
$ dpkg -l | grep sqlcip
ii libsqlcipher2:amd64 4.11.0-1
amd64 SQLCipher shared library
$ apt-cache search libsqlcipher
libsqlcipher-dev - SQLCipher development files
libsqlcipher2 - SQLCipher shared library
```
There is no version 1 of libsqlcipher available.
Greetings. Thomas Nemeth - 22.11.25, 09:11:00 CET: There is. But on https://snapshosts.debian.org Best,
Hello !
Indeed. I always forget that hack solution :)
Thanks. The workaround... works ;)
However, do notice that the version from "unstable" does ALSO need
that workaround. What I like in the "unstable" version is that there
is a *lot* fewer dependencies :)
Thomas.
Thomas Nemeth - 22.11.25, 11:35:15 CET: 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 Created the file manually, cause back then apt-listbugs did not trigger. Best regards,
I can make do with the unstable version for now. All I have to
do is to remember to remove the libsqlcipher1 package when the
fix is imported in testing.
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
```
Thomas.
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...
Greetings Thomas, greetings. Thomas Nemeth - 22.11.25, 12:18:20 CET: No. Above version still works with libsqlcipher1 directly. That was originally the whole point of the pinning. 😃 Best,
There's a bug logged to libsqlitecipher2 for this problem: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1121167 HTH
I have the exact same problem. Some investigation returned that kmymoney apparently is not compiled to have encrypted libcipher enabled. The same kmymoney version works if I add a snap version that has only difference it was compiled using encryption enabled for libcipher. Solution would be for now to compile kmymoney manually, but this works around apt which I do not like to to. Can you maybe "simply" release kmymoney with encryption enabled without changing anything else? Thanks and best regards.
I have implemented a stopgap patch in Debian sqlcipher 4.11.0-2 to prevent kmymoney from crashing due to its improper use of sqlcipher APIs. In the long run, either https://bugs.kde.org/show_bug.cgi?id=512485 or https://github.com/sqlcipher/sqlcipher/issues/578 shall be solved upstream. Thanks, Boyuan Yang