Bug #2335
KDE Plasma workspace kickoff menu no longer works
0%
Description
As of the most recent update, Plasma Workspace menus no longer pop up the expected menu. Instead, an error message pops up with the following content:
Error loading QML file: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/Kickoff.qml:31:1: plugin cannot be loaded for module "org.kde.plasma.private.kicker": Cannot load library /usr/lib/qt/qml/org/kde/plasma/private/kicker/libkickerplugin.so: (/usr/lib/qt/qml/org/kde/plasma/private/kicker/libkickerplugin.so: undefined symbol: _ZN9KFileItemC1ERK4QUrlNS_21MimeTypeDeterminationE)
A similar message is shown for any other application-menu I attempt to use - the Dashboard, Launcher and Menu options.
I have attempted removing and re-installing KDE Plasma and its dependencies, which has not fixed the issue.
Arch upstream does not appear to have this bug.
History
Updated by GnuRock almost 5 years ago
I have the same problem
Error al cargar archivo QML: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/Kickoff.qml:31:1: plugin cannot be loaded for module "org.kde.plasma.private.kicker": Cannot load library /usr/lib/qt/qml/org/kde/plasma/private/kicker/libkickerplugin.so: (/usr/lib/qt/qml/org/kde/plasma/private/kicker/libkickerplugin.so: undefined symbol: _ZN9KFileItemC1ERK4QUrlNS_21MimeTypeDeterminationE)
Updated by bill-auger almost 5 years ago
so far i have determined
- both files named in the error message are in the 'plasma-desktop' package
- both files named in the error message exist in the filesystem
- the missing symbol does exist in the named .so
- the 'plasma-desktop' package and all of its direct dependencies come from arch
- the problem is not reproducible on an arch system
undefined symbol: _ZN9KFileItemC1ERK4QUrlNS_21MimeTypeDeterminationE
$ pkgfile Kickoff.qml extra/plasma-desktop $ pkgfile libkickerplugin.so extra/plasma-desktop $ ls -l /usr/lib/qt/qml/org/kde/plasma/private/kicker/libkickerplugin.so -rwxr-xr-x 1 root root 558920 Jun 7 12:43 /usr/lib/qt/qml/org/kde/plasma/private/kicker/libkickerplugin.so $ ls -l /usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/Kickoff.qml -rw-r--r-- 1 root root 4619 Jun 7 12:43 /usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/Kickoff.qml $ objdump -T /usr/lib/qt/qml/org/kde/plasma/private/kicker/libkickerplugin.so | grep MimeTypeDetermination 0000000000000000 DF *UND* 0000000000000000 _ZN9KFileItemC1ERK4QUrlNS_21MimeTypeDeterminationE $ readelf -Ws /usr/lib/qt/qml/org/kde/plasma/private/kicker/libkickerplugin.so | grep MimeTypeDetermination 471: 0000000000000000 0 FUNC GLOBAL DEFAULT UND _ZN9KFileItemC1ERK4QUrlNS_21MimeTypeDeterminationE
Updated by bill-auger almost 5 years ago
- Status changed from unconfirmed to confirmed
- Subject changed from KDE Plasma workspace menus no longer work. to KDE Plasma workspace kickoff menu no longer works
after downgrading 'plasma-desktop' to 5.15.5-1 (and all deps that it originally pulled in), the problem disappeared
[core] SigLevel = PackageRequired Server=https://archive.archlinux.org/repos/2019/05/30/$repo/os/$arch [extra] SigLevel = PackageRequired Server=https://archive.archlinux.org/repos/2019/05/30/$repo/os/$arch [community] SigLevel = PackageRequired Server=https://archive.archlinux.org/repos/2019/05/30/$repo/os/$arch
one thing i noticed was that with the current packages there were no graphical icons on the desktop, but after downgrading they all appeared normally - so it does seem to be related to mimetypes
these are the packages that i downgraded to their 2019-05-30 state
accountsservice appstream appstream-qt baloo bc bluez bluez-qt breeze-icons convertlit ebook-tools frameworkintegration gdb gdb-common guile2.0 kactivities-stats kded kdelibs4support kdesu kemoticons kfilemetadata kholidays kidletime kinit kirigami2 kjsembed knotifyconfig kpeople krunner kunitconversion kwayland kxmlrpcclient libcanberra-pulse libdmtx libmbim libpwquality libqalculate libqmi libstemmer libxres libzip modemmanager modemmanager-qt networkmanager-qt noto-fonts pipewire plasma-framework ppp prison qqc2-desktop-style qt5-graphicaleffects qt5-quickcontrols qt5-quickcontrols2 qt5-tools sbc sddm socat ttf-hack xcb-util-cursor xorg-bdftopcf xorg-font-util xorg-font-utils xorg-xmessage xorg-xsetroot bluedevil breeze breeze-gtk drkonqi kactivitymanagerd kde-cli-tools kde-gtk-config kdecoration kdeplasma-addons kgamma5 khotkeys kinfocenter kmenuedit knetattach kscreen kscreenlocker ksshaskpass ksysguard kwallet-pam kwayland-integration kwin kwrited libkscreen libksysguard milou oxygen plasma-browser-integration plasma-desktop plasma-integration plasma-nm plasma-pa plasma-sdk plasma-vault plasma-workspace plasma-workspace-wallpapers polkit-kde-agent powerdevil sddm-kcm systemsettings user-manager xdg-desktop-portal-kde
Updated by bill-auger almost 5 years ago
after returning [core], [extra], and [community] to current, and enabling the [kde-unstable] repo, then upgrading 'plasma-desktop' and it's deps, the desktop was totally unusable
[kde-unstable] Include = /etc/pacman.d/mirrorlist
after disabling the [kde-unstable] repo and bringing everything back to the current state, only a small number of packages needed to downgrade, and the original bug returned
warning: kwin: downgrading from version 5.16.0-2 to version 5.16.0-1 warning: qt5-graphicaleffects: downgrading from version 5.13.0rc2-1 to version 5.12.3-1 warning: qt5-quickcontrols: downgrading from version 5.13.0rc2-1 to version 5.12.3-1 warning: qt5-quickcontrols2: downgrading from version 5.13.0rc2-1 to version 5.12.3-1 warning: qt5-tools: downgrading from version 5.13.0rc2-2 to version 5.12.3-1
Updated by PsiGuy60 almost 5 years ago
I have, for now, downgraded plasma-desktop back to 5.15.5-1, in which this issue is not present. Its dependencies were initially also downgraded, but have been re-updated.
Updated by PsiGuy60 almost 5 years ago
Issue seems to no longer be present as of version 5.16.1-2 of the plasma-desktop package. Kickoff menu, as well as other panel menus, function as they should.
Updated by bill-auger almost 5 years ago
- Status changed from confirmed to not-a-bug
working for me now too - there was probably a dependency that needed to catch up