Bug 476910 - application launcher crashed on plasma 5.27.80
Summary: application launcher crashed on plasma 5.27.80
Status: RESOLVED NOT A BUG
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: 5.27.80
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: qt6
: 477011 (view as bug list)
Depends on:
Blocks:
 
Reported: 2023-11-13 01:14 UTC by Firestar-Reimu
Modified: 2023-11-14 19:59 UTC (History)
3 users (show)

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

Attachments
screenshot of application launcher (577.17 KB, image/png)
2023-11-13 01:14 UTC, Firestar-Reimu 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Firestar-Reimu 2023-11-13 01:14:41 UTC 
Created attachment 163101 [details]
screenshot of application launcher

Operating System: Arch Linux 
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.245.0
Qt Version: 6.6.0
Kernel Version: 6.6.1-arch1-1 (64-bit)
Graphics Platform: X11

When I update to 5.27.80, the application launcher crashed (cannot open) and says:

file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/main.qml:20:1: Cannot load library /usr/lib/qt6/qml/org/kde/plasma/private/kicker/libkickerplugin.so: (libAppStreamQt.so.3: cannot open shared object file: No such file or directory)
Comment 1 Firestar-Reimu 2023-11-13 01:16:43 UTC 
But I have that `.so` file

(base) [firestar @ ArchLinux ~] (09:15:50)
$ cd /usr/lib/qt6/qml/org/kde/plasma/private/kicker/

(base) [firestar @ ArchLinux kicker] (09:15:56)
$ ls -l
total 600
-rwxr-xr-x 1 root root 607160 Nov 13 05:42 libkickerplugin.so
-rw-r--r-- 1 root root     57 Nov 13 05:42 qmldir
Comment 2 Antonio Rojas 2023-11-13 07:09:01 UTC 
Please read the wiki page section https://wiki.archlinux.org/title/Official_repositories#Testing_repositories , especially the red box.
Comment 3 Nicolas Fella 2023-11-14 19:59:40 UTC 
*** Bug 477011 has been marked as a duplicate of this bug. ***