Bug 404177 - Enter schedule from loan causes Application crash
Summary: Enter schedule from loan causes Application crash
Status: RESOLVED FIXED
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 5.0.3
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on: 402505
Blocks:
  Show dependency treegraph
 
Reported: 2019-02-10 15:03 UTC by k.buzko
Modified: 2020-05-17 10:22 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description k.buzko 2019-02-10 15:03:37 UTC
SUMMARY
When trying to enter scheduled Loan transaction Application crashes

STEPS TO REPRODUCE
1. Have a loan with scheduled payments
2. Try to enter the tranasction (Enter acion on Home screen or in Ledgers list)
3. App crash

OBSERVED RESULT
Aplication is closed

EXPECTED RESULT
Window with details of entered transaction should show up

SOFTWARE/OS VERSIONS
Windows: 10
Comment 1 Ralf Habacker 2019-02-11 12:12:15 UTC
Can this be reproduces on linux ?

If not, I suggest to create a usable backtrace on Windows.
Comment 2 Ralf Habacker 2019-02-11 13:22:00 UTC
(In reply to Ralf Habacker from comment #1)
> Can this be reproduces on linux ?
> 
> If not, I suggest to create a usable backtrace on Windows.

Thanks to Hannah von Reth, packages with debug symbols will be created with the binary packages from tomorrow on. See https://community.kde.org/Projects/KDE_on_Windows/Tools#WinDbg for a receipt to get back traces.
Comment 3 Thomas Baumgart 2020-01-11 17:32:36 UTC
Is this reproducible with newer versions?
Comment 4 k.buzko 2020-01-12 20:10:14 UTC
I'm using kmymoney 5 since then. On v.5 it does not occure.
Comment 5 Bug Janitor Service 2020-01-27 04:33:18 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 6 k.buzko 2020-01-27 17:56:31 UTC
Changing status to reported
Comment 7 Thomas Baumgart 2020-05-17 10:22:09 UTC
As mentioned in comment #5 the problem does not occur in newer versions.