Bug 499590 - Skrooge crash when selecting the dashboard (either via keyboard or using mouse)
Summary: Skrooge crash when selecting the dashboard (either via keyboard or using mouse)
Status: RESOLVED NOT A BUG
Alias: None
Product: skrooge
Classification: Applications
Component: general (other bugs)
Version First Reported In: 25.1.0
Platform: openSUSE Other
: NOR crash
Target Milestone: 25.1.0
Assignee: Stephane MANKOWSKI
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-06 11:45 UTC by hypolyte.hy
Modified: 2025-10-25 15:57 UTC (History)
0 users

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


Attachments
Short GDB report on Skrooge 25.1.0 crash Os Opensuse Tumbleweed 6 Feb 25 (6.33 KB, text/plain)
2025-02-06 11:45 UTC, hypolyte.hy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description hypolyte.hy 2025-02-06 11:45:32 UTC
Created attachment 178014 [details]
Short GDB report on Skrooge 25.1.0 crash Os Opensuse Tumbleweed 6 Feb 25

SUMMARY
Complete application crash after selecting the main dashboard to vieww all accounts

STEPS TO REPRODUCE
1. open the app
2. select the main dashboard

OBSERVED RESULT
About 30s tempo to implement the command before crash

EXPECTED RESULT
Display of the dashboard

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Running Skrooge on Opensuse thumblewed virtualised (latest)
Tested on Manjaro (latest) same Skrooge version 25.1.0 : works fine no problem
Tried GDB in terminal but the program couldn’t go to the end (requesting zypper in skrooge-debuginfos 25.1.0 which is not in the depot). Run Gdb with Seer debugger (see attachement)
Comment 1 Stephane MANKOWSKI 2025-10-25 15:57:58 UTC
Hi,

I'm not able to resolve this ticket because:
- I'm not able to reproduce it.
- The crash file doesn't contain enough information

I think this is a packaging issue due to library misalignment.