#352 rhbz#1903294 plasma-discover doesnt refresh metadata
Closed 2 years ago by blockerbot. Opened 2 years ago by blockerbot.

Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1903294
Information from BlockerBugs App:
1903294

Current vote summary

Commented but haven't voted yet: jbwillia, bcotton, lruzicka, coremodule

The votes have been last counted at 2021-04-19 19:31 UTC and the last processed comment was #comment-728296

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review
A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)


this would be a nice to have but dnfdragora is also installed by default so
FinalBlocker -1

dnfdragora doesn't run by default, so that wouldn't satisfy the Final criterion:

Release-blocking desktops must notify the user of available updates, but must not do so when running as a live image.

I think I'll be FinalBlocker +1, but I want to wait until tomorrow to verify that the behavior still exists before I cast a vote.

TBH really never needed discover for anything useful, so my vote if wanted FinalBlocker -1, FreezeException +1 propably. Besides I mostly disable or ignore desktop notifications in favor of dnf-automatic running smoothly in background.

Okay, so after some more testing, I'm going to go with

FinalBlocker +1

It seems like this is a long-standing bug in PackageKit that plasma-pk-updates papers over by always forcing a refresh. So the options for resolving this blocker are:

  1. Updating plasma-discover by using pkcon refresh force instead of pkcon refresh
  2. Switching back to plasma-pk-updates instead of plasma-discover
  3. Fixing the underlying PackageKit bug

FinalBlocker +1

If someone relies on Discover, then we should not expect them to also check with dnf or Dnfdragora if there are any updates.

I'm gonna vote a weak:
FinalBlocker +1
it's kinda on the edge of just being an FE for me, but eh. Let's just accept it and push the fix. I will also vote:
FinalFE +1
in the interests of getting one or the other accepted. Can folks who didn't want to vote +1 blocker vote +1 FE if they think it deserves an FE at least?
REVOTE FinalBlocker

The following votes have been closed:

Oh, sorry, I miscounted there. We're only at a total of +2.

@adamwill Not sure, does my vote count as well? TBH I'll agree with @jbwillia about available workarounds, so better try to document that as known bug.
FinalBlocker -1
FinalFE +1

FinalBlocker -1
FinalFE +1

Discover must work properly, and I see that kde spin SIG are getting some advance in developing a workaround for that.
FinalBlocker +1

FinalBlocker +1

We shouldn't expect the end user to know that after installation the default upgrade method doesn't work and to know they need to use dnf or dnfdragora temporarily to solve this issue. For a newcomer to Fedora having to apply a workaround right on the beggining after installing it for having updates would be a sign of Fedora being a low quality OS. Most of them will probably think there aren't any upgrades until they realize something is happening.

Not mentioning this bug could also impact normal package installation through Discover, not only upgrades, because people using discover won't be able to install the latest version of a package at least.

@carlis well, they don't. All they have to do is hit the Refresh button in Discover. That always seems to do the trick for me.
edit: although I guess in the bug, @bcotton said it didn't for him, so, hm.

Anyway, we at least have the votes now for:
AGREED AcceptedFinalFE

The following votes have been closed:

Discussed during the 2021-04-19 blocker review meeting: [0]

The decision to delay the classification of this as a blocker bug was made as there isn't a clear consensus on blocker status here. It is already accepted as a freeze exception issue and a fix is prepared, so we expect that will resolve it shortly.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-04-19/f34-blocker-review.2021-04-19-16.00.txt

@carlis well, they don't. All they have to do is hit the Refresh button in Discover. That always seems to do the trick for me.
edit: although I guess in the bug, @bcotton said it didn't for him, so, hm.

neither worked for me. btw after applying the fix now seems to work both the automatic notification and the refresh button. So I hope others can confirm this is fixed too so we can close the bug.

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

2 years ago

Release F34 is no longer tracked by BlockerBugs, closing this ticket.

Login to comment on this ticket.

Metadata