| Summary: | program crash when attempt to change a report and APPLY | ||
|---|---|---|---|
| Product: | [Applications] kmymoney | Reporter: | danz <dan.ziolkowski> |
| Component: | reports | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | dan.ziolkowski, me |
| Priority: | NOR | ||
| Version: | 5.1.1 | ||
| Target Milestone: | --- | ||
| Platform: | Appimage | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | run appimage is term | ||
|
Description
danz
2021-05-17 10:28:42 UTC
Tried to duplicate that using KMyMoney-5.1.1-9beaa4d-x86_64.AppImage without success. I opened the "Net Worth By Year" default report and changed the date range to "Last 12 months". No crash. What exactly do you do to reproduce the crash? Which report? Which settings? Anything you can think of. If you start the AppImage from a terminal window, do you see any details about the crash? What does it print there? Created attachment 138515 [details]
run appimage is term
(In reply to Thomas Baumgart from comment #1) > Tried to duplicate that using KMyMoney-5.1.1-9beaa4d-x86_64.AppImage without > success. I opened the "Net Worth By Year" default report and changed the > date range to "Last 12 months". No crash. > > What exactly do you do to reproduce the crash? Which report? Which settings? > Anything you can think of. If you start the AppImage from a terminal window, > do you see any details about the crash? What does it print there? favorite report/ custom household/ more often then not, program crashes after I make a change to report. If needed I would need time to further check other reports. Thanks DAN Looking at the trace you provided, I see that the crash happens in the nouveau graphics driver. This may be triggered by the charting part of KMyMoney but certainly cannot be controlled there, esp. since we are using an external library to do the graphing (kdiagram, v2.6.1 in the AppImages). so does that mean nothing can be done? Thanks DAN Dan, such errors would be typically reported to the Linux distribution maintainers. They should be able to take it from here and decide what's next. 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! 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! |