| Summary: | Updater NOT SOLVED! Remains in System Tray reporting needed updates after successful update | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | dexy |
| Component: | discover | Assignee: | Dan Leinir Turthra Jensen <leinir> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | 887sam, aleixpol, echidnaman, ellisistfroh, mgolden, n.schnelle, stasnel |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
dexy
2016-03-21 19:16:03 UTC
The problem is solved, ask your packagers (Kubuntu?) to apply the fix to the packages you use. (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. @ 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 @ 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> @Nikola if Kubuntu releases 5.6 stable release, it will get the fix. (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. ...
> 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 ?
(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. 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. 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. |