Bug 394043 - [PackageKit] Updater icon doesn't go away after updates are installed
Summary: [PackageKit] Updater icon doesn't go away after updates are installed
Status: RESOLVED FIXED
Alias: None
Product: Discover
Classification: Applications
Component: Updates (interactive) (show other bugs)
Version: 5.12.4
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords: triaged, usability
: 392364 395254 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-05-09 15:39 UTC by Lastique
Modified: 2023-08-05 17:37 UTC (History)
8 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 Lastique 2018-05-09 15:39:25 UTC
When a security package update is available, Updater icon with a red dot appears in the system tray. If I install updates (in the command line using apt or using Muon package manager or Discover), the icon doesn't disappear but changes to the "non-security updates available" (i.e. the one without the red dot). Clicking on the icon says "1 package to update". `sudo apt update && sudo apt dist-upgrade` does not find any packages to update.

I'm on Kubuntu 18.04, KDE Discover 5.12.4. The problem didn't appear in Kubuntu 17.10.
Comment 1 Nate Graham 2018-05-09 20:31:01 UTC
Do you have the Flatpak backend installed?
Comment 2 Lastique 2018-05-09 22:35:55 UTC
No, I assume I don't. I didn't install it explicitly and Discover shows "Install" buttons for both Flatpak and Snap backends.
Comment 3 Lastique 2018-05-09 22:40:58 UTC
Also, plasma-discover-flatpak-backend and plasma-discover-snap-backend packages are not installed.
Comment 4 Nate Graham 2018-05-09 22:41:17 UTC
Thanks, then this is Bug 385754.

*** This bug has been marked as a duplicate of bug 385754 ***
Comment 5 Nate Graham 2018-05-09 22:42:42 UTC
Er, I mean Bug 392063.

*** This bug has been marked as a duplicate of bug 392063 ***
Comment 6 Lastique 2018-05-10 00:53:29 UTC
In that bug, you say the Updater starts to work as expected if you remove the Flatpak backend. In my case I do *not* have Flatpak installed and it still doesn't work. Are you sure it is a duplicate?
Comment 7 Nate Graham 2018-05-10 02:18:53 UTC

*** This bug has been marked as a duplicate of bug 385754 ***
Comment 8 Nate Graham 2018-05-10 02:19:58 UTC
Hmm, I could have sworn we already had a bug tracking this... Oh well, let's use this one!
Comment 9 Nate Graham 2018-05-10 02:22:09 UTC
*** Bug 392364 has been marked as a duplicate of this bug. ***
Comment 10 Nate Graham 2018-06-13 13:21:54 UTC
*** Bug 395254 has been marked as a duplicate of this bug. ***
Comment 11 Neousr 2018-07-20 16:02:37 UTC
I can confirm this behavior in a new session the is always one "1" update even after a set of updates installed seconds before. 
Discover has the three backends installed , removing the flatpak one and login in and out will remove the "1" pending update.
Comment 12 Nate Graham 2018-07-20 16:04:38 UTC
if you run `flatpak update` on the command line, does it show any updates?
Comment 13 Neousr 2018-07-20 16:13:04 UTC
After updating by the command line multiple packages were downloaded/updated and when they were installing the notification icon on discover disappeared.
Comment 14 Nate Graham 2018-07-20 16:15:06 UTC
Sounds like you're hitting a different bug, then; in this case the Update Notifier plasmoid was correctly alerting you to the presence of additional updates! :)

Were those Flatpak updates visible in Discover? Or were they only visible when using the `flatpak` command in a terminal?
Comment 15 Neousr 2018-07-20 16:20:20 UTC
Discover notification said there is "1" one update pending then after opening the updates tab is was empty saying no "new" updates.

And using the command updated multiple packages i saw the name of at least 4 contrary of the one discover thinks it was.
Comment 16 Nate Graham 2018-07-20 16:24:35 UTC
OK. So that's a different bug: Bug 385754.
Comment 17 Neousr 2018-07-20 16:28:16 UTC
It seems so i will leave feedback on the other one.
Comment 18 Aleix Pol 2018-10-11 16:27:59 UTC
Can you still reproduce? I haven't seen this issue.
Comment 19 Nate Graham 2018-10-11 16:30:28 UTC
Cannot reproduce on 5.12.x or git master. All remaining occurrences have been due to Bug 385754. Recommend closing until and unless we get a reproducible case.
Comment 20 Andrew Crouthamel 2018-10-27 04:10:00 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 set the bug status 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 21 Nate Graham 2018-10-27 04:12:57 UTC
Closing now. No new report in a while, and we think we've fixed this.
Comment 22 Nate Graham 2018-12-27 02:59:37 UTC
*** Bug 402344 has been marked as a duplicate of this bug. ***