Bug 1554550 - KDE live image notifies of available updates again (F28), via dnfdragora
Summary: KDE live image notifies of available updates again (F28), via dnfdragora
Alias: None
Product: Fedora
Classification: Fedora
Component: comps
Version: 28
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Stephen Gallagher
QA Contact:
Depends On:
Blocks: F28FinalBlocker F28Blocker-kde, F28Target-kde
TreeView+ depends on / blocked
Reported: 2018-03-12 23:58 UTC by Adam Williamson
Modified: 2018-03-19 18:16 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-03-19 18:16:07 UTC

Attachments (Terms of Use)

Description Adam Williamson 2018-03-12 23:58:21 UTC
Current F28 KDE live images notify of updates, via dnfdragora:


That's after openQA boots the live image and just lets it sit for 10 minutes. Note the "177 updates available." notification from dnfdragora. This is wrong, when running live, there should be no update notifications.

Proposing as a Final blocker, per "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_28_Final_Release_Criteria#Update_notification

Comment 1 Kevin Kofler 2018-03-13 03:33:25 UTC
comps-f28.xml.in lists dnfdragora-updater in @kde-desktop, which is wrong, it should list only dnfdragora. Plasma uses plasma-pk-updates, not dnfdragora-updater.

The fix:
was only applied to f26 and f27. Then dnfdragora-gui was renamed to dnfdragora-updater:
but this was already wrong on f28 and f29 before the rename.

Now if the people responsible for this mess can please fix it. I am not the maintainer of this stuff anymore and have not been for a couple years!

Comment 2 Adam Williamson 2018-03-13 04:52:21 UTC
Sorry Kevin, was just CCing KDE-adjacent folks, which in my mind usually maps to you and Rex :/

Comment 3 Adam Williamson 2018-03-13 16:04:59 UTC

Comment 4 Adam Williamson 2018-03-19 18:16:07 UTC
This looks fixed in current nightlies. The test is still failing, but it's a false failure caused by the network device notification (openQA doesn't expect that).

Note You need to log in before you can comment on or make changes to this bug.