Bug 513456 - kmymoney killed by SIGSEGV
Summary: kmymoney killed by SIGSEGV
Status: NEEDSINFO WAITINGFORINFO
Alias: None
Product: kmymoney
Classification: Applications
Component: general (other bugs)
Version First Reported In: 5.2.1
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-12-17 00:04 UTC by mcm
Modified: 2025-12-17 18:28 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mcm 2025-12-17 00:04:41 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY


STEPS TO REPRODUCE
1. Entering financial transactions into ledger
2. Crashes upon entering transaction no message on screen
3. Program runs to create backtrace but sends to Redhat bugzilla and keeps asking for an API key which I have no idea how to generate.
4. Looks like it created a backtrace but I am unsure of how to send it to you. Seems like a flew of files in /Fedora/var/spool/abrt When I use Dolphin to go to that directory it will not let me see the file to attach.

OBSERVED RESULT
kmymoney crashes

EXPECTED RESULT
Transaction is entered

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
kmymoney
Comment 1 Jack 2025-12-17 00:20:21 UTC
Please state exactly what you did when it crashed.  Specifically what did you type or click on?  
Try running from command line to see if anything more useful is printed out to console.
Comment 2 mcm 2025-12-17 01:07:06 UTC
I was entering the category from a dropdown box. Further observations, it lost several of the previous transactions I had entered. After messing with all of the bugzilla stuff I also noticed I could not click on anything in the task bar anymore. Couldn’t start new programs, couldn’t shut down the machine had to do a hard power off. 

So only the programs that were running at the time of the crash were still functioning, but no new ones could be started. 

As I said, it did a backtrace but I do not know how to get you that info.  It is in the /var/spool/abrt directory which I can’t navigate to with dolphin. I was thinking I could just zip the directory with the backtrace files and attach it, but apparently that is not straightforward. 

Sent from my iPhone

> On Dec 16, 2025, at 6:20 PM, Jack <bugzilla_noreply@kde.org> wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=513456
> 
> Jack <ostroffjh@users.sourceforge.net> changed:
> 
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>             Status|REPORTED                    |NEEDSINFO
>         Resolution|---                         |WAITINGFORINFO
> 
> --- Comment #1 from Jack <ostroffjh@users.sourceforge.net> ---
> Please state exactly what you did when it crashed.  Specifically what did you
> type or click on?  
> Try running from command line to see if anything more useful is printed out to
> console.
> 
> --
> You are receiving this mail because:
> You reported the bug.
> You are on the CC list for the bug.
Comment 3 Jack 2025-12-17 01:27:25 UTC
When responding to a bug by email, please delete everything in the message except your response, as your entire message becomes the next bug comment, and all the extra quoted material can make the flow harder to follow.

KMyMoney only saves transactions (as with all of its data) when you explicitly do a Save, or the program does an auto-save.  You lost all data entered since the previous save.

You are going to have to ask on a Fedora forum or list about how to extricate the backtrace.  I would also consider filing a Fedora bug, since even if it was KMyMoney that crashed, the fact that you couldn't do anything else except restart the machine is a Fedora issue.

Aside from all that, running from command line to look at console output is the next thing for you to try.
Comment 4 Thomas Baumgart 2025-12-17 07:48:18 UTC
As a side note not related to the cause of the behavior you encounter: you mention

> ... I also noticed I could not click on anything in the task bar anymore.
>  Couldn’t start new programs, couldn’t shut down the machine ...

I see this myself now and then, especially after heavily switching between applications and virtual activities. I found out, that KWin is causing this and for me it helps to switch into virtual text console mode (e.g. Ctrl+Alt+F1), log into the regular user and kill the kwin process (it restarts automatically). Then switching back to graphical mode brings back full control while all applications are still running.
Comment 5 mcm 2025-12-17 18:28:12 UTC
Guess I need to keep a virtual terminal open as it wouldn’t let me open anything.   If it happens again I’ll try the ctl+alt+f1. 

Thanks for the pointer. 

Sent from my iPhone

> On Dec 17, 2025, at 1:48 AM, Thomas Baumgart <bugzilla_noreply@kde.org> wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=513456
> 
> --- Comment #4 from Thomas Baumgart <tbaumgart@kde.org> ---
> As a side note not related to the cause of the behavior you encounter: you
> mention
> 
>> ... I also noticed I could not click on anything in the task bar anymore.
>> Couldn’t start new programs, couldn’t shut down the machine ...
> 
> I see this myself now and then, especially after heavily switching between
> applications and virtual activities. I found out, that KWin is causing this and
> for me it helps to switch into virtual text console mode (e.g. Ctrl+Alt+F1),
> log into the regular user and kill the kwin process (it restarts
> automatically). Then switching back to graphical mode brings back full control
> while all applications are still running.
> 
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
> You reported the bug.