Bug 477546 - KDE Neon doesen't start to install due Calamares undefined symbol
Summary: KDE Neon doesen't start to install due Calamares undefined symbol
Status: RESOLVED FIXED
Alias: None
Product: neon
Classification: KDE Neon
Component: Live/Install images (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2023-11-26 09:01 UTC by Egor Kuznetsov
Modified: 2024-02-05 21:33 UTC (History)
4 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Egor Kuznetsov 2023-11-26 09:01:59 UTC 
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1.  Download KDE Neon Unstable (neon-unstable-20231119-1118)
2.  Boot into it in virtual machine
3.  Try to click on "Install system" or start manually from terminal via

OBSERVED RESULT
Calamares doesen't start

EXPECTED RESULT
Calamares start, all gonna install

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.81.80
KDE Frameworks Version: 5.245.0
Qt Version: 6.6.0
Kernel Version: 6.2.0-36-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 5500U with Radeon Graphics
Memory: 7.7 GiB of RAM
Graphics Processor: llvmpipe
Manufacturer: QEMU
Product Name: Standard PC (Q35 + ICH9, 2009)
System Version: pc-q35-8.1

ADDITIONAL INFORMATION
Error message: /usr/bin/_neon.calamares: symbol lookup error: /lib/x86_64-linux-gnu/libcalamares.so.3.3: undefined symbol: _ZN10FileSystem11nameForTypeENS_4TypeERK11QstringList
Comment 1 Egor Kuznetsov 2023-11-30 08:52:19 UTC 
Fixed in latest release, maybe can close it
Comment 2 duha.bugs 2024-02-05 21:33:52 UTC 
(In reply to Egor Kuznetsov from comment #1)
> Fixed in latest release, maybe can close it

Thanks. Closing. If this issue reappears please reopen the bug report