Bug 511605

Summary: Kasts does not start - symbol lookup error
Product: [Applications] kasts Reporter: maizjoris
Component: generalAssignee: bart
Status: RESOLVED FIXED    
Severity: major    
Priority: NOR    
Version First Reported In: 25.08.2   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description maizjoris 2025-11-04 09:37:09 UTC 
SUMMARY
Kasts application does not start in any way, either via desktop shortcut or KRunner.
If initiated via "kasts" command in Konsole, it immidiately stops responding with error message:

kasts: symbol lookup error: /lib64/libKMediaSession.so: undefined symbol: _ZN6QAudio13convertVolumeEfNS_11VolumeScaleES0_, version Qt_6


STEPS TO REPRODUCE
1. Type "kasts" pharse in Konsole and confirm with Enter
2. Observe whether application starts or error message is displayed

OBSERVED RESULT
Application does not start and error message is displayed.

EXPECTED RESULT
Kasts application should start

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.6-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-5300U CPU @ 2.30GHz
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: Intel® HD Graphics 5500
Manufacturer: Dell Inc.
Product Name: Latitude E7450

ADDITIONAL INFORMATION
Comment 1 bart 2025-11-04 09:46:48 UTC 
Please report this to Fedora. Most likely, kasts hasn't been recompiled after upgrade of Qt to 6.10.
I got the same error after my system got updated to qt6.10, but it was completely fine after recompilation.

If that still doesn't solve it, feel free to reopen this ticket so I can have closer look.
Comment 2 maizjoris 2025-11-04 12:32:31 UTC 
(In reply to bart from comment #1)
> Please report this to Fedora. Most likely, kasts hasn't been recompiled
> after upgrade of Qt to 6.10.
> I got the same error after my system got updated to qt6.10, but it was
> completely fine after recompilation.
> 
> If that still doesn't solve it, feel free to reopen this ticket so I can
> have closer look.

Thanks. For the record, here is a downstream bug report https://bugzilla.redhat.com/show_bug.cgi?id=2412226