| Summary: | Updates page shows 0 packages immediately after refresh despite new updates being available due to QML binding loop. | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | proteus5 |
| Component: | discover | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | aleixpol, kdedev |
| Priority: | NOR | ||
| Version First Reported In: | 6.5.0 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
I'm not able to reproduce this on KDE Neon Testing with Plasma I ran `sudo pkcon refresh` and then brought up Discover from the systray notification At first, the Updates page showed "Up to Date" but after a moment it changed to show the available updates I am also not able to reproduce this on Plasma built from git-master on Solus How long have you waited on the Updates page? I'm wondering if the time it takes the updates to appear is affected by system speed / resource usage. 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |
This issue persists from Plasma 6.4 (and is confirmed to be present in Plasma 6.5 on KDE neon) and causes a noticeable inconsistency between the Discover user interface and the actual update status reported by the backend. Steps to Reproduce: The system notifier (tray icon) signals that new updates are available. The user opens Discover and navigates to the Updates page. A repository refresh is executed (or has just concluded). The Updates page immediately displays the status "0 updates available," even though new packages have been found by the backend (APT/PackageKit). A short time later, the separate Discover Notifier daemon sends a correct pop-up notification showing the actual list of available updates.