Discover update refresh with fwupd disabled?

I run with fwupd disabled in the following manner
systemctl mask fwupd.service fwupd-refresh.service fwupd-refresh.timer
This is because I am running linux on a Microsoft Surface which has rather a lot of key unusual hardware, and rather aloof UEFI, for this reason a maintain I minimal windows partition just for maintaining hardware concerns.

I ran like this without issue for a long time, with Discover software update refresh working, which I used for updating flatpak applications. (Distro packages I update via dnf5 [Fedora 44])

However, recently plasma-discover updated to plasma-discover-6.7.0-1.fc44.x86_64 .
Since then Discover update hang at “Fetching updates” with a full blue bar, eventually greyed out.
I get the same if I run this from CLI via
plasma-discover --backends packagekit,flatpak,fwupd --mode update
However, the issue does not occur if I exclude fwupd by running it via
plasma-discover --backends packagekit,flatpak --mode update

I do not think that this is going to be something Fedora 44 specific, so I am beginning my progression here.

I am minded to log a question of a bug. However, before that I need to cover the question of:

  • Is there some more proper way of disabling fwupd if you wish to do so while still expecting Discover not to hang?

or similarly

  • Is there a ‘proper’ way of configuring Discover to cope with fwupd being disabled? i.e. First of all is this actually a misconfiguration on my part in terms of what I am trying to achieve?

I am confident that this issue has begin with the update of plasma-discover to 6.7.0-1 , but that does not ‘yet’ mean that this is a bug within its design or implementation.

(I could also uninstall the various fwupd packages just to ‘try’ that, but there is actually an older question that implies that wouldn’t work either, https://bugs.kde.org/show_bug.cgi?id=431634. As you can see I already have a workaround, so this discussion is intended to target precisely the requirements already outlined)

Many thanks in advance for anyone’s assistance

bug with status duplicate

of status (at this time) confirmed, follow the below.