Created attachment 126212 [details] discover output SUMMARY Unable to update event calendar via discover. STEPS TO REPRODUCE 1. Have event calendar v65 installed 2. Find event calendar in discover, click "update all" OBSERVED RESULT Widget is not updated EXPECTED RESULT Widget is updated Operating System: KDE neon 5.18 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 Kernel Version: 5.3.0-40-generic OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 V2 @ 3.20GHz Memory: 23,4 GiB of RAM This also affects KDE widget installer. All my machines are affected. I've also found this when publishing my own extension (https://store.kde.org/p/1359965/) it also never get updated (however discover shows that update is installed, in fact ~/.local/share/plasma/plasmoid/ stuff remains old. I thought that i;m doing something wrong, but now it seems like it's an updater issue.
Created attachment 126213 [details] local plasmoid metadata
Created attachment 126214 [details] install widget menu that shows that event calendar is updated
The actual error is: org.kde.knewstuff.core: Command ' "kpackagetool5 --install /tmp/eventcalendar-v66-plasma5.12.plasmoid --type Plasma/Applet" ' failed with code 4. The root cause could be in the KNewStuff backend, or in the KNewStuff framework itself, or with the applet. However the poor error message and logging is definitely another problem we should fix. Did Discover show this error message anywhere in the UI, or did you have to launch Discover via a terminal to see it in the console output?
1. No, discover UI just showed that widget is updated. 2. The worst issue is that widget is not updated even if update is successful. I mean I still have event calendar v63 on some of my devices, but plasma/discover is sure that it's v66. This could be really critical since a lot of users potentially are missing a lot of critical fixes like one that caused event calendar to consume a lot of cpu and spam google api requests when google calendar is down.
This got already fixed and was an issue with the kpackage backend. *** This bug has been marked as a duplicate of bug 424429 ***