Description of problem: With plasma-discover-5.22.90-3.fc35, repo configuration suffers from redrawing issues and confusing item reordering. If you enable/disable any repo in the "Fedora Linux 35" section, that repo, together will all other repos defined in that same file, is moved to the very bottom of the list (so e.g. "F35 Updates + Updates Debug + Updates Source" are moved to the bottom). If you don't pay close attention to this, you might get confused. For example if the 'updates' triplet jumps away and on the same place appears the 'fedora' triplet with the same selection as originally (the first item enabled, the other two disabled), you might not re-read the item again carefully and just assume that your click wasn't registered, and click again (and then it disappears from the view and you'll not realize you've just disabled the 'fedora' repo). Additionally, each time you perform the change, all items in the "Firmware Updates" and "Flatpak" sections get renamed to "undefined". For some items, scrolling up and down is enough the redraw them into proper names, for other items, you need to change the current tab to some other one and back. See the attached video. Version-Release number of selected component (if applicable): plasma-discover-5.22.90-3.fc35 How reproducible: always Steps to Reproduce: 1. go to Discover -> Settings 2. click an RPM repo to enable/disable it 3. see the repo (and related ones) disappear, find them at the bottom 4. see other items in other sections renamed to "undefined"
Created attachment 1830328 [details] repo jump and redraw issue (video)
Created attachment 1830329 [details] rpm -qa
Please report upstream. I saw the undefinted thing too, but appeared to be temporary while config is re-read.
Tested with plasma-discover-5.23.0-1.fc35 and the bug is still there. Please note that the reshuffled rpm repo order survives reboots, i.e. the order change is permanent. The "undefined" glitch is temporary, until the page is forced to be redrawn.
Upstream bug report: https://bugs.kde.org/show_bug.cgi?id=443583
Since bug 2011305 is an accepted blocker now, and the proposed update for it [1] introduces/uncovers this bug, I'm going to mark this for a blocker discussion as well. It's not fully technically correct (this bug can't be a blocker before that update is pushed stable), but a) I want others to be aware of it, and b) it's very likely that this bug has been already present in Discover for some time, it just couldn't be tested due to bug 2011305. [1] https://bodhi.fedoraproject.org/updates/FEDORA-2021-a32a5c05d4
Discussed during the 2021-10-11 blocker review meeting: [0] The decision to classify this bug as a "RejectedBlocker (Final)" and an "AcceptedFreezeException (Final)" was made as we agreed that while this looks bad, the operation does work, so critical functionality is maintained. It's accepted as an FE issue if it can be fixed relatively safely, as it does look pretty bad. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-10-11/f35-blocker-review.2021-10-11-16.00.txt
FEDORA-2021-4f68774f07 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-4f68774f07
https://bodhi.fedoraproject.org/updates/FEDORA-2021-4f68774f07 should fix the "other repos go to 'undefined'" part of this. It doesn't solve the order changing part, though. Aleix is working on a bigger fix that would avoid the whole "refresh the entire interface whenever you touch a PK repo" thing, but we don't think that's likely safe to rush in for Final.
Tested it and just like @awilliam said: no more the "undefined" problem, thats fixed.
https://invent.kde.org/plasma/discover/-/merge_requests/192 is the PR that would address the rest of this, probably.
(In reply to Geraldo Simião from comment #10) > Tested it and just like @awilliam said: no more the "undefined" > problem, thats fixed. Confirmed.
FEDORA-2021-4f68774f07 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-4f68774f07` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-4f68774f07 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-4f68774f07 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
The remaining issue is that the toggled repos jump around in the list.
https://koji.fedoraproject.org/koji/taskinfo?taskID=77634062 is a scratch build with the fix for this. Please test it quite hard as it changes the logic of how the PK source list gets refreshed, so see if you can break that...enable and disable a bunch of sources, add sources, remove them, leave and re-enter the page, stuff like that.
Adam, the repo jumping is fixed. I only found one problem in my testing. If you quickly click twice on a repo checkbox, you can make it not reflect the actual state. So e.g. if updates-testing is disabled (unchecked), and you quickly click twice on its checkbox, it gets checked and unchecked again, i.e. it looks as disabled. But in fact, only the first action got performed in the code beneath, and updates-testing is currently enabled. Switching the tab to e.g. About and back to Settings redraws the checkbox into a proper (checked) state. I'm not able to verify whether this is a new bug or it existed before, because it couldn't be triggered before (the repos jumped around, and if you tried this with the bottom-most repo, the whole page scrolled up, preventing you from doing a double click).
thanks. yeah, I've managed to trigger bugs in the other backends by doing the same thing, but it strikes me as a fairly unlikely 'real world' thing, it's more something you and me would do because we like breaking stuff. :P So if that's the only problem, I think the fix is good, but...on the whole, since it's Monday, it might be best to hold off pulling the fix into the final compose. I think I'll submit it but leave it to be a 0-day update.
FEDORA-2021-35e9884fd8 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-35e9884fd8
FEDORA-2021-f7d19c8901 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-f7d19c8901` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-f7d19c8901 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
seems to be fixed here after the update https://bodhi.fedoraproject.org/updates/FEDORA-2021-f7d19c8901
FEDORA-2021-f7d19c8901 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.