Bug 2467449
| Summary: | No update notifications on KDE Plasma since Fedora-Rawhide-20260413.n.0 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Williamson (Red Hat non-Fedora) <awilliam> | ||||
| Component: | plasma-discover | Assignee: | marcdeop | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | kde-sig, marcdeop | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | openqa | ||||||
| Fixed In Version: | Doc Type: | --- | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2026-05-07 00:32:19 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: |
|
||||||
Created attachment 2139867 [details]
journal from the 0413.n.0 failure
Hmm, actually, I think I forgot that we tested and found this is openQA-specific somehow, it's not happening in manual testing. And tests which *don't* do the special setup steps we do on the notification test sometimes happen to see notifications. Closing again. |
Since Fedora-Rawhide-20260413.n.0 , the openQA notification test is failing on KDE because we do not see an update notification as we expect to. Before that compose, we were reliably getting update notifications. In the system journal, I see: Apr 14 18:43:41 fedora DiscoverNotifier[2554]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID") around the time we log in to the desktop. I can't see why this started failing in 0413.n.0, though. Nothing remotely related leaps out at me from the changelog.