Bug 2139092
| Summary: | Update notifications don't show up in Plasma 5.26 | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> | ||||||||||||
| Component: | plasma-discover | Assignee: | Rex Dieter <rdieter> | ||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 37 | CC: | agurenko, ales.astone, awilliam, hygorhernane, jgrulich, kde-sig, me, nope1000000, rdieter, robatino, than | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | Unspecified | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | plasma-discover-5.26.2-3.fc37 | Doc Type: | If docs needed, set a value | ||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2022-11-08 01:49:03 UTC | Type: | Bug | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Embargoed: | |||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Kamil Páral
2022-11-01 12:14:50 UTC
Created attachment 1921533 [details]
plasma 5.26 - notifications menu
Created attachment 1921534 [details]
plasma 5.25 - banner
Created attachment 1921535 [details]
plasma 5.25 - notifications menu
Comment 1 shows how it looks like in RC 1.5, comment 2 and comment 3 show how it looked like in RC 1.4. Created attachment 1921536 [details]
rpm -qa in RC 1.5
Created attachment 1921537 [details]
rpm -qa in RC 1.4
Proposing as a blocker: "Release-blocking desktops must notify the user of available updates, but must not do so when running as a live image. " https://fedoraproject.org/wiki/Fedora_37_Final_Release_Criteria#Update_notification Please note that the systray icon could be considered satisfactory, even when a banner is missing. Proposing for a discussion. Isn't it on purpose? https://pointieststick.com/2022/08/26/this-week-in-kde-re-bindable-mouse-buttons/#new-features > Discover now lets you choose the frequency with which it notifies you about new updates! And within those frequencies, it’s now less aggressive about notifying you; no longer will you have the experience of updating, rebooting, and then immediately getting a notification about another update Great findings, Alessandro. I looked at my settings and it's set to Daily. I should note that this is a clean installation, so whatever the value is, I wasn't notified before, and yet it still fails to produce the notification. Also, I installed the VM yesterday, but the notification isn't shown even today. But it's very likely that the change is related to the links you posted, thanks. The question is whether the lack of a banner notification is intentional or not. Blocker discussion ticket is here: https://pagure.io/fedora-qa/blocker-review/issue/1000 I think notifications should be set to weekly btw. oh god, now I have to defeat stupid KDE heuristics as well as stupid GNOME heuristics[0]? joy. [0] https://pagure.io/fedora-qa/os-autoinst-distri-fedora/blob/main/f/tests/desktop_notifications.pm#_28 the precedent here is when the desktop does clever-clever stuff like this, we defer to the relevant WG/SIG in determining what the 'intended' behaviour is, within reason. For e.g. if the intent is only that a notification will show up within a day of install, and that does work, we consider the criterion satisfied. So, we do need to get the KDE team's input here. Just eyeballing the code, there seems to be at least a possibility that it may have a bug causing update notifications never to be shown on new profiles. But that may not be the case, I'm not 100% sure. I'll try and test it out with some debug prints if nobody answers my question on the upstream commit. apol agreed with me that the code looked buggy, and now there's an MR upstream: https://invent.kde.org/plasma/discover/-/merge_requests/404 . I'm doing a scratch build with it backported and will try and hack that into the openQA test to see if it helps. It did help. I'm doing an official build now. FEDORA-2022-23a0a34ea5 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-23a0a34ea5 (In reply to Fedora Update System from comment #16) > FEDORA-2022-23a0a34ea5 has been submitted as an update to Fedora 37. > https://bodhi.fedoraproject.org/updates/FEDORA-2022-23a0a34ea5 Tested, notifications show up now. FEDORA-2022-23a0a34ea5 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-23a0a34ea5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-23a0a34ea5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. I edited the fix for this into the same update that initially caused it, so it doesn't really need blocker status. FEDORA-2022-23a0a34ea5 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. |