When I click Application Launcher I get this error instead of the menu: Error loading QML file: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/Kickoff.qml:38:34: Type FullRepresentation unavailable file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/FullRepresentation.qml:98:13: Type FavoritesView unavailable file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/FavoritesView.qml:151:23: Type KickoffItem unavailable file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/KickoffItem.qml:184:13: Cannot assign to non-existent property "usesPlasmaTheme" Reproducible: Always Steps to Reproduce: 1. Upgrade kubuntu 15.10 to KDE Neon (steps: http://neon.kde.org.uk/download) 2. Reboot the computer 3. Click to Application Launcher Actual Results: Does not show the menu. Not open applications Expected Results: Should display the application menu Distro Version : Kubuntu 15.10 Kernel Version: 4.2.0-29-generic (64Bits) KDE Frameworks 5.20.0 Qt 5.5.1 (built against 5.5.1)
Created attachment 97336 [details] Not open the application launcher
The same error appeared after fridays(19th thursday) update of existing (and working) system.
I've the same problem since the last update, but removing the two lines 183 (animated) and 184 (usePlasmaTheme) fixes this problem. Unfortunately I've more problems since the last update (krunner doesn't work anymore, systemsettings doesn't show all modules). I guess it has something to do with plugin loading. Will wait a few days for a new update before creating a bug report, though. There is a reason why it's still called unstable :D
I can confirm that removing mentioned two lines solved the problem. At the other side, it is true that the amount of problems is huge. For example the search engine is not working even more for me.
I confirm that I also have the exact same problems after friday's 2016-02-19 update
Same symptoms here.
(In reply to Mathias Kraus from comment #3) > I've the same problem since the last update, but removing the two lines 183 > (animated) and 184 (usePlasmaTheme) fixes this problem. > > Unfortunately I've more problems since the last update (krunner doesn't work > anymore, systemsettings doesn't show all modules). I guess it has something > to do with plugin loading. Will wait a few days for a new update before > creating a bug report, though. There is a reason why it's still called > unstable :D Which file contains these two lines?
file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/KickoffItem.qml
Probably plasma-frameworks too old, please paste apt-cache policy plasma-framework and try apt update; apt full-upgrade then log out and in again
(In reply to Jonathan Riddell from comment #9) > Probably plasma-frameworks too old, please paste > > apt-cache policy plasma-framework > > and try apt update; apt full-upgrade then log out and in again Yes, I mentoired that I have old plasma, but there is no way how to upgrade (your suggested solution doesnt work). jankup@jankup-ThinkPad-E550:~$ sudo apt-cache policy plasma-framework plasma-framework: Installed version: 4:5.17.0+git20160105.1645+15.10-0 Candidate: 4:5.17.0+git20160105.1645+15.10-0 Tabulka verzí: *** 4:5.17.0+git20160105.1645+15.10-0 0 100 /var/lib/dpkg/status 5.18.0+git20160218.1706+15.10-0 0 500 http://archive.neon.kde.org.uk/unstable/ wily/main amd64 Packages 5.15.0-0ubuntu1 0 500 http://cz.archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
Doesn't fix for me either... tsuther@AngryButler99:~$ sudo apt-cache policy plasma-framework plasma-framework: Installed: 4:5.17.0+git20160105.1645+15.10-0 Candidate: 4:5.17.0+git20160105.1645+15.10-0 Version table: *** 4:5.17.0+git20160105.1645+15.10-0 0 100 /var/lib/dpkg/status 5.18.0+git20160218.1706+15.10-0 0 500 http://archive.neon.kde.org.uk/unstable/ wily/main amd64 Packages 5.18.0-0ubuntu1~ubuntu15.10~ppa2 0 500 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu/ wily/main amd64 Packages 5.15.0-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
The problem with Application Launcher can be fixed by downloading and installing plasma-framework 5.18 from http://archive.neon.kde.org.uk/unstable/pool/main/p/plasma-framework/ However, Krunner still won't work and right click functionality to add desktop and panel widgets remains broken.
you're a victim of the epoch bug the first round of packages had, you'll need to remove plasma-framework and reinstall apt remove plasma-framework apt install neon-desktop
apt remove plasma-framework apt install neon-desktop This does indeed fix the problem for me.
I can also confirm that the problem with the application launcher and the other widgets was fixed after the aforementioned solution, and that the problem with the search and the right click remains
Yes, to clarify, the reported QML errors are fixed, but launcher search does not work, also have rt-click issues.
There are other packages which need to be updated: libkf5plasma5 libkf5plasmaquick5 libkf5solid5 libkf5solid5-data libkf5sonnet5-data libkf5sonnetcore5 libkf5sonnetui5 libkf5threadweaver5 qml-module-org-kde-solid qtdeclarative-kf5solid sonnet-plugins These are all at version 4:5.17 but the newer version (5.18) will not be installed because of the 4 in front of the old version number. You have to manually select the new version. You can also check if there are more old libs on your system by using aptitude. Just run aptitude, type l (small letter L) and then "~i~V4:5.17" without quotation marks. Just check everything on that list for a newer version than installed. With an updated system, everything works again.
(In reply to Mathias Kraus from comment #19) > There are other packages which need to be updated: > libkf5plasma5 > libkf5plasmaquick5 > libkf5solid5 > libkf5solid5-data > libkf5sonnet5-data > libkf5sonnetcore5 > libkf5sonnetui5 > libkf5threadweaver5 > qml-module-org-kde-solid > qtdeclarative-kf5solid > sonnet-plugins > > These are all at version 4:5.17 but the newer version (5.18) will not be > installed because of the 4 in front of the old version number. You have to > manually select the new version. > > You can also check if there are more old libs on your system by using > aptitude. Just run aptitude, type l (small letter L) and then "~i~V4:5.17" > without quotation marks. Just check everything on that list for a newer > version than installed. > > With an updated system, everything works again. I can confirm, that described solution solved all my problems on laptop. On my desktop computer the plasma is totaly borken (no menus, no launchers, nothing), but it could be caused by some previous atempts to repair.
(In reply to Jonathan Riddell from comment #14) > you're a victim of the epoch bug the first round of packages had, you'll > need to remove plasma-framework and reinstall > > apt remove plasma-framework > apt install neon-desktop This removed most kde applications, installed lots of gnome stuff, and then broke my installation. However, re-install fixed most things. All my versions are now at 5.18 and most things are working fine but I still have no right click functionality on desktop. I love to live dangerously! Good to have /home on a separate partition!
(In reply to Mathias Kraus from comment #19) > There are other packages which need to be updated: > libkf5plasma5 > libkf5plasmaquick5 > libkf5solid5 > libkf5solid5-data > libkf5sonnet5-data > libkf5sonnetcore5 > libkf5sonnetui5 > libkf5threadweaver5 > qml-module-org-kde-solid > qtdeclarative-kf5solid > sonnet-plugins > > These are all at version 4:5.17 but the newer version (5.18) will not be > installed because of the 4 in front of the old version number. You have to > manually select the new version. > > You can also check if there are more old libs on your system by using > aptitude. Just run aptitude, type l (small letter L) and then "~i~V4:5.17" > without quotation marks. Just check everything on that list for a newer > version than installed. > > With an updated system, everything works again. When you say everything works, are you getting rt click functionality on desktop? I'm not. What am I missing?
I fixed this by deleting .config and resetting desktop to defaults. Now all working OK.