Bug 392461 - Discover displays updates for removed plasmoids / widgets
Summary: Discover displays updates for removed plasmoids / widgets
Status: RESOLVED WORKSFORME
Alias: None
Product: Discover
Classification: Applications
Component: KNewStuff Backend (show other bugs)
Version: 5.12.4
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-28 17:08 UTC by Ashberian
Modified: 2020-12-21 04:34 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ashberian 2018-03-28 17:08:54 UTC
KDE Neon up to date ( 5.12.4 ) :

Installed "event calendar" plasmoid some time ago to check it out, removed it in less than 24 hours ( didn't suit my needs ) using the graphical tools for it .

Since then ( 5.12.2 ) , the update notifier plasmoid is constantly warning me about one new update avaliable ... iclick on it, Discover opens and displays a 0 bytes update avalaible for "event calendar". 

Even if i click the "update" button and Discover no longer shows any other update avaliable, the notifier plasmoid is stuck on this one update always avaliable... consequently, Discover is always trapped on this loop.
Comment 1 Aleix Pol 2018-04-09 15:37:04 UTC
Are you sure you uninstalled them? Can you try doing so?
Comment 2 Aleix Pol 2018-04-23 10:55:10 UTC
Plasma/KPackage should tell KNewStuff to uninstall a Plasmoid when a plasmoid is uninstalled.
Comment 3 Neousr 2018-08-30 16:40:59 UTC
It not only happens with uninstalled plasmoids for i can tell im getting 0 bytes updates on installed plasmoids, event calendar for example.

Sometimes discover gets the install size, tried updating several times and never gets completed for example event calendar updates and returns again on next round and the other plasmoids get stuck at 0% downloaded forcing to close discover.
Comment 4 Neousr 2018-08-30 18:15:52 UTC
Adding a little more information on the topic.

The 0 bytes on discover seems to be discover trying to update the plasmoid to an old version in my case v57 to version 57. When version 59 was available on the store.kde.org.

To remove the updates messages.

Go to the taskbar and access "Get new widgets" and update the plasmoid.

Then close it, reopen it again then  uninstall the plasmoid.

And then go to discover and uninstall from there (it seems to be bugged there).

After that discover showed the correct version and installed properly.

I found a couple of interactions (even other bug it seems) but in short installing and old version of a plasmoid in "get new widgets" will make discover miss behave.

It can be seen if you install or have and old plasmoid version going to discover > plasma addons and searching the plasmoid name. Either it will show  (install green button) even tho it was installed from "new widgets" or showing 0 bytes ( and the wrong version)

I cannot confirm what is triggering  since there are multiple symptoms including the 0 bytes when uninstalled as the original report.
Comment 5 Dan Leinir Turthra Jensen 2018-11-27 12:07:02 UTC
(In reply to Aleix Pol from comment #2)
> Plasma/KPackage should tell KNewStuff to uninstall a Plasmoid when a
> plasmoid is uninstalled.

It seems to me like the "proper" way to do this would be to make it possible for the KPackage installer to hold some kind of way to call a command post-uninstall (the way e.g. rpm and deb does)... That would then make it possible for KNewStuff to inject such a step, so e.g. kpackagetool would be able to request KNewStuff to remove all references to the content item having been installed.

Another option would be to add functionality to KNewStuff, which might have another step to ask for up to date information from the tool used to install something. This would require e.g. kpackagetool to remember where something was originally installed from, so we could do e.g. CheckStatusCommand=kpackagetool5 --install-status %f (the way the InstallationCommand and UninstallCommand entries work right now). This could then be run during the cache load step, and while this would arguably be considerably heavier than the current state, the current state is also not exactly brilliant, so...

i did think that it might be possible to do something like having kpackagetool know when something's initially been installed through knewstuff, so that it would be able to ask knewstuff to do the removal. But, that seems like that would be an unnecessarily roundabout way of doing it, especially considering kpackage would then have to be called again, from knewstuff, to perform the data removal (because knewstuff loses track of that data when kpackage installs it, which in turn would be why this problem exists in the first place...).

Thoughts?
Comment 6 Aleix Pol 2018-11-27 16:02:20 UTC
+1 to what Dan said.
It's an issue between knewstuff and KPackage.

knewstuff could though detect it disappeared and de-register it too.
Comment 7 Justin Zobel 2020-11-21 05:43:14 UTC
This sounds similar to an issue recently where icon themes etc weren't clearing after an update. I believe this was fixed fairly recently.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 8 Bug Janitor Service 2020-12-06 04:34:04 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Bug Janitor Service 2020-12-21 04:34:51 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!