Bug 510203

Summary: kasts crashes silently
Product: [Applications] kasts Reporter: Cherkah <cherkaba>
Component: generalAssignee: bart
Status: RESOLVED FIXED    
Severity: crash    
Priority: NOR    
Version First Reported In: 25.08.1   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: backtraces kasts
gdb-trace
kasts-25-08-03_backtrace

Description Cherkah 2025-10-03 17:43:22 UTC
Created attachment 185486 [details]
backtraces kasts

SUMMARY
at system boot kasts has produced a crash log

STEPS TO REPRODUCE
1.  don't know that spent once


OBSERVED RESULT
i can relaunch it without any issue

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.16.9-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland


ADDITIONAL INFORMATION
Comment 1 Cherkah 2025-10-03 21:24:08 UTC
Created attachment 185493 [details]
gdb-trace
Comment 2 Cherkah 2025-10-03 21:25:44 UTC
This happened again:
The application is in the thumbnail tray.
If you close Kasts (right-click/close), it crashes.

see the gdb-trace attachment
Comment 3 Cherkah 2025-11-14 08:43:39 UTC
Created attachment 186767 [details]
kasts-25-08-03_backtrace
Comment 4 Cherkah 2025-11-14 08:45:20 UTC
find an other kasts's crash in the kasts-25-08-03_backtrace. 
kasts version: 25.08.03
Comment 5 bart 2025-11-16 13:32:31 UTC
It's not exactly clear when the crash is happening.  I don't see a lot of clues in the backtraces.

Is this when you try to close the app?
Comment 6 Cherkah 2025-11-16 13:38:56 UTC
it doesn't happend anymore? juste 2 times! but since,  kasts and kde/plasma have pushed updates which probably solved the issue. 
The software no longer has this problem in my case.
Comment 7 bart 2025-11-16 13:41:48 UTC
Ok.  I've seen similar crashes in the past before. I'm pretty sure that these are not happening in kasts itself, but in one of the underlying kde libraries. So, with every kde frameworks update there is a chance that such bugs are solved. This might be what happened.

I'll close the bug report now. If it happens again, then feel free to reopen or open an new bug report.