https://bugs.kde.org/show_bug.cgi?id=428423
Piotr Mierzwinski <piotr.mierzwin...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #3 from Piotr Mierzwinski <piotr.mierzwin...@gmail.com> ---
(In reply to utomas from comment #2)
> I can reproduce same behaviour and I think I realise what might be happening.
>
> When you install an icon theme, for instance, it can have different versions
> of it, a dark and a light version, or maybe different release version, so a
> menu asking to choose a version appears. I think discover expects the same
> and so it get stucks because is waiting for your choose which is not showing
> on screen BTW.
>
> Sorry for my english :)
This is original report, but I created also duplicated one (I forgot about this
one) which has been took into account by developers and I thins issue has been
fixed. I didn't test it yet, because no happened update for stuff which cased
the issue for me.
Please check Bug 430812 for details.
And back to this report.
You are right. Sometimes happens that exists two or more versions of the same
package (dark and light or more colours), and Discover is not (or, considering
Bug 430812, wasn't) able to match proper one, so didn't update an interface,
but the update was still in progress, only we didn't see it. I was wrong saying
that update stuck. After enough of time when we wait, update might pass with
success. After we close Discover and open again turns out that system is up to
date. I discovered that to unblock such stuck progress (in the middle of
update), needs to open "System Settings" go to proper configuration, check
update and in"New Stuff" tool and click update there. And then after back to
Discover turns out that progress is showing correctly.
Shortly.
The issue was that Discover wasn't able to interpret correctly the answer from
external system, and just not updated progress bar, but he skipped this
package and was going further. I think this was fixed already. Check my
another bug report.
https://bugs.kde.org/show_bug.cgi?id=430812
I change status of this one as resolved, because this report is a duplication.
*** This bug has been marked as a duplicate of bug 430812 ***
--
You are receiving this mail because:
You are watching all bug changes.
