Bug 430163 - KMyMoney crash on opening
Summary: KMyMoney crash on opening
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 5.1.0
Platform: Debian stable Linux
: NOR crash
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2020-12-08 18:53 UTC by Daniel Elias
Modified: 2021-01-30 04:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Image01 (34.28 KB, image/png)
2020-12-24 00:10 UTC, Daniel Elias
Details
Image02 (17.89 KB, image/png)
2020-12-24 00:11 UTC, Daniel Elias
Details
Image03 (10.62 KB, image/png)
2020-12-24 00:12 UTC, Daniel Elias
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Elias 2020-12-08 18:53:26 UTC
Application: kmymoney (5.1.0)

Qt Version: 5.11.3
Frameworks Version: 5.54.0
Operating System: Linux 5.9.0-0.bpo.2-amd64 x86_64
Distribution: Debian GNU/Linux 10 (buster)

-- Information about the crash:
- What I was doing when the application crashed:
KMyMoney is configured to access the PostgreSQL database on a server. After configuring access, when starting the system, the currency configuration is requested. After configuration KMyMoney closes unexpectedly.

The crash can be reproduced every time.

-- Backtrace:
Application: KMyMoney (kmymoney), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7efd74ab2940 (LWP 232957))]

Thread 5 (Thread 0x7efd6a65d700 (LWP 232963)):
#0  0x00007efd7aa9300c in futex_wait_cancelable (private=0, expected=0, futex_word=0x55f951d51048) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x00007efd7aa9300c in __pthread_cond_wait_common (abstime=0x0, mutex=0x55f951d50ff8, cond=0x55f951d51020) at pthread_cond_wait.c:502
#2  0x00007efd7aa9300c in __pthread_cond_wait (cond=0x55f951d51020, mutex=0x55f951d50ff8) at pthread_cond_wait.c:655
#3  0x00007efd6abf8e83 in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x00007efd6abf8bd7 in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x00007efd7aa8cfa3 in start_thread (arg=<optimized out>) at pthread_create.c:486
#6  0x00007efd7ebbf4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7efd720b2700 (LWP 232962)):
#0  0x00007efd79e77e84 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007efd79e2d65c in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007efd79e2e06b in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007efd79e2e25c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007efd7f344743 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007efd7f2f215b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007efd7f141e76 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007efd7f59a545 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x00007efd7f14ba67 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007efd7aa8cfa3 in start_thread (arg=<optimized out>) at pthread_create.c:486
#10 0x00007efd7ebbf4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7efd732ef700 (LWP 232960)):
#0  0x00007efd7ebb4819 in __GI___poll (fds=0x7efd732eeb78, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007efd78b38cf7 in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007efd78b3a91a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007efd73c4dd79 in  () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007efd7f14ba67 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007efd7aa8cfa3 in start_thread (arg=<optimized out>) at pthread_create.c:486
#6  0x00007efd7ebbf4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7efd74aae700 (LWP 232959)):
#0  0x00007efd7aa9300c in futex_wait_cancelable (private=0, expected=0, futex_word=0x7efd7e9ea150) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x00007efd7aa9300c in __pthread_cond_wait_common (abstime=0x0, mutex=0x55f951c206e0, cond=0x7efd7e9ea128) at pthread_cond_wait.c:502
#2  0x00007efd7aa9300c in __pthread_cond_wait (cond=0x7efd7e9ea128, mutex=0x55f951c206e0) at pthread_cond_wait.c:655
#3  0x00007efd7eedc3bc in std::condition_variable::wait(std::unique_lock<std::mutex>&) () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x00007efd7df15542 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#5  0x00007efd7df15659 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#6  0x00007efd7eee1b2f in  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#7  0x00007efd7aa8cfa3 in start_thread (arg=<optimized out>) at pthread_create.c:486
#8  0x00007efd7ebbf4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7efd74ab2940 (LWP 232957)):
[KCrash Handler]
#6  0x00007efd7eafd7bb in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7  0x00007efd7eae8535 in __GI_abort () at abort.c:79
#8  0x00007efd7eeb2983 in  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007efd7eeb88c6 in  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007efd7eeb8901 in  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007efd7eeb8b89 in __cxa_rethrow () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x000055f95112be80 in  ()
#13 0x00007efd7eaea09b in __libc_start_main (main=0x55f951155920, argc=1, argv=0x7fffc0b832f8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffc0b832e8) at ../csu/libc-start.c:308
#14 0x000055f95115736a in _start ()
[Inferior 1 (process 232957) detached]

Reported using DrKonqi
Comment 1 Daniel Elias 2020-12-08 19:33:00 UTC
PostgreSQL 12.5 (Debian 12.5-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
Comment 2 Daniel Elias 2020-12-08 19:40:37 UTC
Qt5 lib versions:

libqt5core5a:amd64 (5.11.3+dfsg1-1+deb10u4)
libqt5sql5:amd64 (5.11.3+dfsg1-1+deb10u4)
libqt5sql5-psql:amd64 (5.11.3+dfsg1-1+deb10u4)
Comment 3 Jack 2020-12-08 20:19:06 UTC
What do you mean "currency configuration is requested?"  Is this trying to set up a new instance of KMM using Postgres or are you trying to access an already set up database?
If you invoke KMM from command line, is there any other output to console that might be useful in tracking down the cause?
Comment 4 Jack 2020-12-08 20:19:37 UTC
(sorry - hit "Save" too soon)
Comment 5 Daniel Elias 2020-12-08 20:32:15 UTC
(In reply to Jack from comment #3)
> What do you mean "currency configuration is requested?"  Is this trying to
> set up a new instance of KMM using Postgres or are you trying to access an
> already set up database?
> If you invoke KMM from command line, is there any other output to console
> that might be useful in tracking down the cause?

Hello!
1. I'm trying access a new instance of KMM using Postgres. I think the currency configuration is the last step before configuration accounts, which I haven't yet reached.
2. When I invoke KMM from the terminal (Linux), and follow the same procedure (currency configuration), I get this:

terminate called after throwing an instance of 'MyMoneyException'
  what():  Unknown account id 'AStd::Asset' /build/kmymoney-wh5VtB/kmymoney-5.1.0/kmymoney/mymoney/storage/mymoneystoragemgr.cpp:142
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kmymoney path = /usr/bin pid = 291268
KCrash: Arguments: /usr/bin/kmymoney 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0

It should be noted that the error occurs in both cases: when I select the currency and close the window, or when I simply close the currency selection window without defining it.
Comment 6 Bug Janitor Service 2020-12-23 04:34:22 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Daniel Elias 2020-12-24 00:08:23 UTC
I added screenshots of the screens, following the steps until the error occurred.
In fact, this error occurs in any type of database.
Comment 8 Daniel Elias 2020-12-24 00:10:24 UTC
Created attachment 134297 [details]
Image01

First screen, when I enter the information about connecting to the database.
Comment 9 Daniel Elias 2020-12-24 00:11:20 UTC
Created attachment 134298 [details]
Image02

Second screen, when I select the currency information and confirm.
Comment 10 Daniel Elias 2020-12-24 00:12:19 UTC
Created attachment 134299 [details]
Image03

Error that occurs after entering currency information.
Comment 11 Jack 2020-12-31 01:03:09 UTC
I've finally got posgresql set up, but cannot replicate your problem.  (I do get a different error saving to postgres, but I'll raise that separately after some more troubleshooting.)  
Please specify more completely the steps you take.  You first screenshot shows the information to create the database in the first place.  When I create a new data file, that is the last screen in the process.  Your second screen, the currency information, is NOT the initial selection of a currency for a new file, but one where you can add additional currencies to your existing file.  I do not understand why you would get this screen after saving a new database.  In addition, the fact that you do get to this screen after the database screen implies that the database was correctly saved.  In your third image, can you redo it, expanding the details?  Are they exactly the same as the backtrace in the initial post?
Comment 12 Bug Janitor Service 2021-01-15 04:33:46 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 13 Bug Janitor Service 2021-01-30 04:33:21 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!