Skrooge segmentation fault

[scataldi]

Hi all,
I am a new Garuda user. I really like the philosophy behind the distro.
After a few weeks of good work and after an update my skrooge program stopped working.
When I launch it from shell I have this message:

##WARNING: Another action already registered for identifier edit_copy
##WARNING: Another action already registered for identifier edit_expandall
##WARNING: Another action already registered for identifier edit_collapseall
Errore di segmentazione (core dump creato)

skrooge version is 25.1.0-4

I have uninstalled and reinstalled the program together with its dependencies. Deleted its config file in ~/.config without success.
Can anybody help me?
Thank you

[SGS]

Welcome

This forum is not a general technical support forum.

If you post here for help, follow the template and post the output from garuda-inxi as preformatted text, please.

[Duke187]

Hello and Welcome

Did you research yourself a bit?

Looks like a packages bug again

[Solved] skrooge crashes at startup / Pacman & Package Upgrade Issues /...

Did you read this website it was using Kde4 and swapped to Kde5 and so on.

If it was working before the update maybe you can downgrade it yourself but if you run a update again it will be the newer Version also you get a Warning parrtialy upgrade not recommended.

maybe you can use the Flatpak Version.

Projects/Skrooge - KDE TechBase

[nepti]

There is dead silence on the web and all relevant bug trackers are empty, as well as the kde forum.

Short test with skrooge version 25.1.0-4 (extra-repo) on garuda-dr460nized-linux-zen-250308 in a VM: no issues, the package works flawlessly.

[filo]

Actually I’ve just installed it out of curiosity and it starts up and work correctly.

[Duke187]

Yes it worked here too on hypr i got some warnings but its opening and work .

[scataldi]

I’ve found a bug in the starting routine of skrooge. It was trying to open the last used file. For some reason it ended in a crash. Renaming the last file skrooge didn’t find it so it opened an empty instance. Then I was able to load the file correctly.
I hope this can help someone else.