https://bugs.kde.org/show_bug.cgi?id=512307
--- Comment #11 from [email protected] --- A new version of kmymoney was available for installation (*.deb): 5.2.1-1 This did not fix the crash but this time there was no app crash notification popup, so "something" changed behind the scene. gdb bt delivers again: Thread 1 "kmymoney" received signal SIGSEGV, Segmentation fault. 0x00007ffff52e4153 in sqlcipher_find_db_index () from /lib/x86_64-linux-gnu/libsqlcipher.so.2 (gdb) bt #0 0x00007ffff52e4153 in sqlcipher_find_db_index () from /lib/x86_64-linux-gnu/libsqlcipher.so.2 #1 0x00007ffff52e7c8d in sqlite3_key_v2 () from /lib/x86_64-linux-gnu/libsqlcipher.so.2 #2 0x0000555555644408 in ?? () #3 0x0000555555618a56 in ?? () #4 0x00007ffff4c33ca8 in __libc_start_call_main (main=main@entry=0x555555617500, argc=argc@entry=1, argv=argv@entry=0x7fffffffdb38) at ../sysdeps/nptl/libc_start_call_main.h:58 #5 0x00007ffff4c33d65 in __libc_start_main_impl (main=0x555555617500, argc=1, argv=0x7fffffffdb38, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffdb28) at ../csu/libc-start.c:360 #6 0x00005555556191e1 in ?? () Should I open this issue for siduction linux rather than for kmymoney? -- You are receiving this mail because: You are watching all bug changes.
