Bug 389834 - KMyMoney crashed on File>Recent>xxxxxx.mny
Summary: KMyMoney crashed on File>Recent>xxxxxx.mny
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.6.6
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords: drkonqi, triaged
Depends on:
Blocks:
 
Reported: 2018-02-03 15:42 UTC by Dick
Modified: 2018-11-06 14:46 UTC (History)
2 users (show)

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


Attachments
attachment-13308-0.html (2.95 KB, text/html)
2018-02-05 02:22 UTC, Dick
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dick 2018-02-03 15:42:00 UTC
Application: kmymoney (4.6.6)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.4.0-109-generic x86_64
Distribution: Ubuntu 16.04.3 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I was trying to re-open the file containing my KMyMoney data so that account balances would be updated, etc.

-- Backtrace:
Application: KMyMoney (kmymoney), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x00007fe4a81ad428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#7  0x00007fe4a81af02a in __GI_abort () at abort.c:89
#8  0x00007fe4a8af084d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007fe4a8aee6b6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007fe4a8aee701 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007fe4a8aee919 in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x00000000004a2ef9 in main (argc=<optimized out>, argv=0x7ffd143bac78) at /build/kmymoney-E9qJ0t/kmymoney-4.6.6/kmymoney/main.cpp:185

Possible duplicates by query: bug 389801, bug 389217, bug 389148, bug 389069, bug 388864.

Reported using DrKonqi
Comment 1 Jack 2018-02-04 03:41:16 UTC
4.6.6 is pretty old.  Can you possibly update to 4.8.1 or 4.8.0?  Also, the title says xxxxxx.mny - is this a typo for xxxxxx.kmy?

Also, just to confirm, you can start kmymoney OK with no file, but the crash is only when you try to open a recent data file?  When was the last time you successfully had that file open?
Comment 2 Thomas Baumgart 2018-02-04 07:10:39 UTC
Yes, 4.6 is old and unmaintained. To start KMyMoney without opening a file please start with the -n command line option.
Comment 3 Dick 2018-02-05 02:22:42 UTC
Created attachment 110344 [details]
attachment-13308-0.html

Thanks for working on this. First, yes, I should have said xxxxxx.kmy.

Secondly, I use Ubuntu and KMyMoney loads whenever I power on or restart. I
don't typically shut down on a daily basis. The file xxxxxx.kmy loads
automatically and is the only file I use. It's open in KMyMoney right now.
Rarely is there a problem, but it's not every day that I attempt to reload
the xxxxxx.kmy file in order to record automatic deposits and payments.
That's what I was doing when the crash occurred.

I will try loading KMyMoney from a command line with  the -n option, but it
sounds as if I should put my efforts toward upgrading.

Thanks again.

*Dick Oakland*
1601 Wheeler Rd
Apt G6
Madison  WI  53704-7056
Dick's Cell: (920) 931-2670


On Sun, Feb 4, 2018 at 1:10 AM, Thomas Baumgart <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=389834
>
> Thomas Baumgart <tbaumgart@kde.org> changed:
>
>            What    |Removed                     |Added
> ------------------------------------------------------------
> ----------------
>          Resolution|---                         |WAITINGFORINFO
>              Status|UNCONFIRMED                 |NEEDSINFO
>
> --- Comment #2 from Thomas Baumgart <tbaumgart@kde.org> ---
> Yes, 4.6 is old and unmaintained. To start KMyMoney without opening a file
> please start with the -n command line option.
>
> --
> You are receiving this mail because:
> You reported the bug.
>
Comment 4 Thomas Baumgart 2018-02-05 11:47:34 UTC
Maybe, you also look out for a backup file. Could be, that your KMY file is corrupted due to the crash. In that case, an upgrade will not help either.
Comment 5 Andrew Crouthamel 2018-10-07 04:28:56 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 set the bug status 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 6 Andrew Crouthamel 2018-11-06 14:46:45 UTC
Dear Bug Submitter,

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!