Bug 360832 - Updater NOT SOLVED! Remains in System Tray reporting needed updates after successful update
Summary: Updater NOT SOLVED! Remains in System Tray reporting needed updates after suc...
Status: RESOLVED FIXED
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-21 19:16 UTC by dexy
Modified: 2020-12-12 15:16 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dexy 2016-03-21 19:16:03 UTC
Further Platform/OS info: Kubuntu 15.10 amd64., Problem has persisted over several updates.

Click on System Tray (black shield with red X) icon reports "4 packages to update, of which 2 are security updates." Click of Update button gives a brief flash on screen of a listing of 2 lines, then refresh (of Apt?) and display of 2 required updates. Updating these, the System Tray icon shows no change - repeat all the above first line. Click of Update button now shows a brief flash of the green shield "software up to date", then refresh (of Apt?) and display of green shield "software up to date". System Tray icon remains  black shield with red X.

Further info, mostly user-interface inadequacy:
   During Update, the Progress Bar at top remains at about 1/5 shaded and "Updating" until complete. This process consists of several stages, notably firstly "Downloading..." . These could/should be each reported and the graphic Bar report (overall or each stage?) percentage completed.
   Just a "homologation" suggestion ...
Hopefully helpfully

Reproducible: Always

Steps to Reproduce:
1. Read Details above
2.
3.

Actual Results:  
Again read Details above

Expected Results:  
System tray icon goes "hidden" and, if shown (by System Tray "Show hidden icons"), shows green shield "fully updated" or similar.
Comment 1 Aleix Pol 2016-03-22 00:42:06 UTC
The problem is solved, ask your packagers (Kubuntu?) to apply the fix to the packages you use.
Comment 2 Nikola Schnelle 2016-03-24 23:58:46 UTC
(In reply to Aleix Pol from comment #1)
> The problem is solved, ask your packagers (Kubuntu?) to apply the fix to the
> packages you use.

Where is the fix for this bug (what commits)?

Kubuntu guys want to include it in 16.04 release.
Comment 3 EllisIsPfroh 2016-03-25 02:21:28 UTC
@ Nikola
 take a look at the changelog of Plasma 5.5 via kde.org Announcements
 - https://www.kde.org/announcements/plasma-5.5.5.php -->
 - https://www.kde.org/announcements/plasma-5.5.4-5.5.5-changelog.php

in addition those bugs are listed there (Plasma-Discover - NOT Discover (which is for hardware detection)):
https://bugs.kde.org/show_bug.cgi?id=347602
https://bugs.kde.org/show_bug.cgi?id=358359

and you find the commit there too.

best regards
Comment 4 EllisIsPfroh 2016-03-25 02:37:58 UTC
@ Nikola Schnelle:

Also worth looking at -> changelog of Plasma 5.6.0

https://www.kde.org/announcements/plasma-5.5.5-5.6.0-changelog.php

... has even more fixes for Plasma-Discover (search for bug #347602 there)

<OT> considered finding the KDE-Announcements quite professional & helpful <OT>
Comment 5 Aleix Pol 2016-03-29 11:22:24 UTC
@Nikola if Kubuntu releases 5.6 stable release, it will get the fix.
Comment 6 Nikola Schnelle 2016-03-29 11:27:57 UTC
(In reply to Aleix Pol from comment #5)
> @Nikola if Kubuntu releases 5.6 stable release, it will get the fix.

I have found the commit/fix.

Kubuntu 16.04 will ship plasma 5.5.5 by default. I pinged yofel and he backported the fix so 16.04 wont have this bug. I can confirm it is fixed (atm in staging ppa for those interested).

Thank you Aleix for fixing the bug.
Comment 7 dexy 2016-03-30 06:25:05 UTC
...
> backported the fix so 16.04 wont have this bug. I can confirm it is fixed
> (atm in staging ppa for those interested).

Staging PPA? OK, so it still won't get into my running 15.10?

I don't full understand these ppas. I have backports in my sources - do I need staging as well? If so, please give the deb line for the source.
Is backports what is fixed for previous releases, staging what is fixed for the next that might work in the active release? Why isn't the fixed version in the normal update stream, and appearing by muon updater ?
Comment 8 Nikola Schnelle 2016-03-30 06:40:41 UTC
(In reply to dexy from comment #7)
> ...
> > backported the fix so 16.04 wont have this bug. I can confirm it is fixed
> > (atm in staging ppa for those interested).
> 
> Staging PPA? OK, so it still won't get into my running 15.10?
> 
> I don't full understand these ppas. I have backports in my sources - do I
> need staging as well? If so, please give the deb line for the source.
> Is backports what is fixed for previous releases, staging what is fixed for
> the next that might work in the active release? Why isn't the fixed version
> in the normal update stream, and appearing by muon updater ?

Probably the fix wont be backported to 15.10. Most kubuntu devs left kubuntu so there are a few people working on it and 16.04 LTS is top priority. 16.04 will be released soon so you can upgrade to it.

Staging is only for development release (currently 16.04) and only for testing so no, you don't need it.

Btw this is kde bug tracker, not a forum. Join kubuntu-devel on freenode irc or kubuntu forums, if you have questions or if you want to help kubuntu project.
Comment 9 dexy 2016-03-30 06:51:11 UTC
On 30/03/16 19:40, Nikola Schnelle via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=360832
>
> --- Comment #8 from Nikola Schnelle <n.schnelle@gmail.com> ---
> (In reply to dexy from comment #7)
>> ...
>>> backported the fix so 16.04 wont have this bug. I can confirm it is fixed
>>> (atm in staging ppa for those interested).
>> Staging PPA? OK, so it still won't get into my running 15.10?
>>
>> I don't full understand these ppas. I have backports in my sources - do I
>> need staging as well? If so, please give the deb line for the source.
>> Is backports what is fixed for previous releases, staging what is fixed for
>> the next that might work in the active release? Why isn't the fixed version
>> in the normal update stream, and appearing by muon updater ?
> Probably the fix wont be backported to 15.10. Most kubuntu devs left kubuntu so
> there are a few people working on it and 16.04 LTS is top priority. 16.04 will
> be released soon so you can upgrade to it.
>
> Staging is only for development release (currently 16.04) and only for testing
> so no, you don't need it.
>
> Btw this is kde bug tracker, not a forum. Join kubuntu-devel on freenode irc or
> kubuntu forums, if you have questions or if you want to help kubuntu project.
>
Thanks Nikola. A bit wiser now, and patience ... :) Kubuntu Forums led 
me here.
Comment 10 mgolden 2020-12-12 15:16:44 UTC
Discover is no longer part of Muon, so I am moving this ticket to the Discover product. From the end of the discussion it sounds like it was already resolved by 16.04. Please reopen if it is still a problem.