Mageia forum • View topic - Trouble with Kmymoney 5

Page 1 of 1

Trouble with Kmymoney 5

Posted: Jun 15th, '18, 20:19

by mark9117

4.14.44-desktop-2.mga
Kmymoney 5.0

At some point in recent history, Kmymoney stopped allowing me to create new accounts. I enter the information for the account, press "Finish" and Kmymoney crashes dead away.

I opened the issue with the Kmymoney support folks and they suggested I try a backtrace. I got this:

Code: Select all: (gdb) run Starting program: /usr/bin/kmymoney [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffdbc0f700 (LWP 12896)] [New Thread 0x7fffd2d6e700 (LWP 12900)] [New Thread 0x7fffc97e4700 (LWP 12904)] [New Thread 0x7fffc8fe3700 (LWP 12905)] [New Thread 0x7fffc0a84700 (LWP 12908)] 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 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 Plugins: checkprinting loaded Plugins: csvexporter loaded Plugins: csvimporter loaded Plugins: gncimporter loaded Plugins: icalendarexporter loaded Plugins: kbanking loaded KBankingPlugin: No AqB4 config found. KBankingPlugin: No AqB3 config found. Plugins: kbanking pluged Plugins: ofximporter loaded Plugins: qifexporter loaded Plugins: qifimporter loaded Plugins: reconciliation report loaded Plugins: weboob loaded Online plugins found 3 Cost center model created with items 0 Payees model created with items 0 reading file start parsing file startDocument reading securities endDocument libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile [New Thread 0x7fff70bff700 (LWP 12915)] [New Thread 0x7fff6b7ff700 (LWP 12916)] Thread 1 "kmymoney" received signal SIGSEGV, Segmentation fault. 0x00007ffff60a214b in MyMoneyInstitution::pixmap(int) const () from /lib64/libkmm_mymoney.so.5 (gdb)

Something appears to be borked with MyMoneyInstitution:pixmap(int), etc. I have no idea what that may mean.

Can anybody shed some light on this? Is there a resolution at hand?

Thanks much!

Mark

Re: Trouble with Kmymoney 5

Posted: Jun 16th, '18, 19:31

by doktor5000

mark9117 wrote:I opened the issue with the Kmymoney support folks and they suggested I try a backtrace.

Not sure why you submit the results of the backtrace here, as that is primarily a means for the application developers to take a look what is going on during runtime.
Did you submit the results of the backtrace to them? And during the time when that backtrace ran, did you actually create a new account?

Re: Trouble with Kmymoney 5

Posted: Jun 16th, '18, 19:40

by mark9117

Yes and yes.

That is to say I attempted to create an account. Also it has been brought to my attention that the backtrace submitted is incomplete - there is no actual backtrace!

I'll be making another pass at that tonight.

I'm assuming no other such issue has surfaced in the forum?

Re: Trouble with Kmymoney 5

Posted: Jun 17th, '18, 15:25

by doktor5000

For the backtrace, usually gdb should tell you which debuginfo packages to install. See also https://wiki.mageia.org/en/Debugging_so ... liminaries and the rest of that wiki page.

And there are very few threads about kmymoney at all: search.php?keywords=kmymoney

Regarding the backtrace, at the final gdb prompt in your post, you would need to issue "bt" or "bt full" without quotes as gdb command, same as with "run" in the beginning to receive the actual backtrace.
See e.g. the first post in https://bugs.launchpad.net/ubuntu/+sour ... ug/1692784 on what an actual backtrace should look like with debuginfo packages installed.

mark9117 wrote: I got this:

Code: Select all
(gdb) run Starting program: /usr/bin/kmymoney [...] [New Thread 0x7fff70bff700 (LWP 12915)] [New Thread 0x7fff6b7ff700 (LWP 12916)] Thread 1 "kmymoney" received signal SIGSEGV, Segmentation fault. 0x00007ffff60a214b in MyMoneyInstitution::pixmap(int) const () from /lib64/libkmm_mymoney.so.5 (gdb)

Re: Trouble with Kmymoney 5

Posted: Jun 18th, '18, 00:13

by mark9117

And here is that backtrace output just for the record. I've submitted this to the folks at Kmymoney. I'll update and close this issue once I find out more from them just to get things documented here in case someone else runs into the same trouble.

Code: Select all: Thread 1 "kmymoney" received signal SIGSEGV, Segmentation fault. 0x00007ffff60a214b in MyMoneyInstitution::pixmap(int) const () from /lib64/libkmm_mymoney.so.5 (gdb) bt #0 0x00007ffff60a214b in MyMoneyInstitution::pixmap(int) const () at /lib64/libkmm_mymoney.so.5 #1 0x00000000007ff4f1 in InstitutionsModel::slotObjectModified(eMyMoney::File::Object, MyMoneyObject const*) () #2 0x00007ffff1876c7e in QMetaObject::activate(QObject*, int, int, void**) () at /lib64/libQt5Core.so.5 #3 0x00007ffff61181b0 in MyMoneyFile::objectModified(eMyMoney::File::Object, MyMoneyObject const*) () at /lib64/libkmm_mymoney.so.5 #4 0x00007ffff605655b in MyMoneyFile::commitTransaction() () at /lib64/libkmm_mymoney.so.5 #5 0x00007ffff60602d5 in MyMoneyFileTransaction::commit() () at /lib64/libkmm_mymoney.so.5 #6 0x00000000006253d1 in NewAccountWizard::Wizard::newAccount(MyMoneyAccount&) () #7 0x000000000050c862 in KAccountsView::slotNewAccount() () #8 0x00007ffff1876c7e in QMetaObject::activate(QObject*, int, int, void**) () at /lib64/libQt5Core.so.5 #9 0x00007ffff2329532 in QAction::triggered(bool) () at /lib64/libQt5Widgets.so.5 #10 0x00007ffff232ba00 in QAction::activate(QAction::ActionEvent) () at /lib64/libQt5Widgets.so.5 #11 0x00007ffff2423080 in QAbstractButtonPrivate::click() () at /lib64/libQt5Widgets.so.5 #12 0x00007ffff2423195 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /lib64/libQt5Widgets.so.5 #13 0x00007ffff24f24aa in QToolButton::mouseReleaseEvent(QMouseEvent*) () at /lib64/libQt5Widgets.so.5 #14 0x00007ffff236b918 in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #15 0x00007ffff24f257c in QToolButton::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #16 0x00007ffff232f51c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #17 0x00007ffff23373a3 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #18 0x00007ffff184bc68 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #19 0x00007ffff233600f in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () at /lib64/libQt5Widgets.so.5 #20 0x00007ffff2385096 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () at /lib64/libQt5Widgets.so.5 #21 0x00007ffff23879db in QWidgetWindow::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #22 0x00007ffff232f51c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #23 0x00007ffff23369c7 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #24 0x00007ffff184bc68 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #25 0x00007ffff1d9db5b in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib64/libQt5Gui.so.5 #26 0x00007ffff1d9f945 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /lib64/libQt5Gui.so.5 #27 0x00007ffff1d7ae7b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Gui.so.5 #28 0x00007fffd5125a10 in userEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5XcbQpa.so.5 #29 0x00007fffe7853b32 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #30 0x00007fffe7853e88 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #31 0x00007fffe7853f2c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #32 0x00007ffff189e776 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #33 0x00007ffff1849e0a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #34 0x00007ffff18529c8 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #35 0x0000000000471182 in runKMyMoney(QApplication&, std::unique_ptr<QSplashScreen, std::default_delete<QSplashScreen> >, QUrl const&, bool) () #36 0x000000000046fc5e in main ()

Re: Trouble with Kmymoney 5

Posted: Jun 18th, '18, 13:45

by doktor5000

You may want to add a link here to where you reported this to kmymoney folks, so that others with the same issue might also be able to followup on that.

Re: Trouble with Kmymoney 5

Posted: Jul 20th, '18, 06:23

by mark9117

So after some back and forth and a couple of "bumps" in the mailing list, the issue ends in a resounding nothing. See the short email excerpt below:

From: Thomas Baumgart <thb@net-bembel.de>
To: Mark Adams <mark9117@gmail.com>
Subject: Re: Kmymoney crashes when trying to create a new account
Date: Thu, 19 Jul 2018 21:16:18 +0200

Hi Mark Adams,

unfortunately no Can you build from source? I have no idea why this crash happens and thus can't give an advice for a workaround.

Regards

Thomas

On Donnerstag, 19. Juli 2018 19:48:11 CEST you wrote:

> Bump.
>
> Any idea?
>
>
>
> On 07/15/2018 02:25 PM, Mark Adams wrote:
>> Hey there,
>>
>> I do not have the "Breeze" theme available. I have installed some
>> variants of the Breeze theme, and I am still unable to create a new
>> account.
>>
>> I even tried creating a new file and was unable to create an account
>> in it without it crashing.
>>
>> Creating an account is a fairly basic function in a piece of financial
>> software. Is there not something that can be done here? Is there no
>> work around? Can I not edit a text file somewhere?
>>
>> Any help appreciated.
>>
>>
>> Mark

That's from the kmymoney mailing list: https://mail.kde.org/mailman/listinfo/kmymoney

Another user was having similar trouble and solved it by applying the Breeze theme. I don't have the Breeze theme installed, lots of variants of Breeze, but no Breeze. Changing themes did not resolve the issue for me.

I may try to install from source. I really like Kmymoney and intend to keep using it, but the inability to create a new account could be a show stopper. I intend to fire up kde (which I love but has developed too many stability issues to continue to use, hence, my conversion to Mate) and see if I can create an account under that IDE. Until then, it's an unsettled issue.

Mark

Re: Trouble with Kmymoney 5

Posted: Oct 15th, '18, 00:48

by Gelsenbury

I can confirm this issue. The last few lines in the konsole are:

Code: Select all: libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile Segmentation fault (core dumped)

I'm surprised about this because the rest of KMyMoney has been working really well for me.