Description of problem: In Discover, if you install an app, you can't uninstall it shortly afterwards, you'll only see "Package not found" error. Similarly, if you uninstall an app, you can't install it again, because of the same error. This prevents people from: 1. Quickly trying out different apps, e.g. when looking for a good image editor. "This one? No. This one? No. This one? Yes, I like it, I'll keep it." 2. Reinstalling an app if they experience some troubles with it. Closing and reopening Discover makes Discover recover from the problem, and you can then remove or install the app that previously was producing the errors. Version-Release number of selected component (if applicable): plasma-discover-5.23.0-3.fc35 PackageKit-1.2.4-2.fc35 How reproducible: always Steps to Reproduce: 1. install an RPM app 2. try to remove it, it fails with "Package not found" 3. restart Discover 4. remove the app, now it works 5. try to install the app again, it fails again with "Package not found"
Created attachment 1834970 [details] bug demonstration video
Created attachment 1834971 [details] journal The relevant journal error seems to be: Oct 20 09:29:22 fedora PackageKit[2169]: new remove-packages transaction /203_dcbeeeeb scheduled from uid 1000 Oct 20 09:29:22 fedora plasma-discover[2378]: percentage cannot be calculated Oct 20 09:29:22 fedora plasma-discover[2378]: percentage cannot be calculated Oct 20 09:29:22 fedora plasma-discover[2378]: percentage cannot be calculated Oct 20 09:29:22 fedora plasma-discover[2378]: percentage cannot be calculated Oct 20 09:29:22 fedora PackageKit[2169]: remove-packages transaction /203_dcbeeeeb from uid 1000 finished with failed after 137ms Oct 20 09:29:22 fedora plasma-discover[2378]: PackageKit error: PackageKit::Transaction::ErrorPackageNotFound "Package not found" "Failed to find kmymoney;5.1.2-2.fc35;x86_64;fedora"
Created attachment 1834972 [details] rpm-qa
Proposing for a blocker discussion.
This doesn't seem to be a recent regression in the last-minute fixes we did for plasma-discover, because 5.23.0-1.fc35 also exhibits this bug.
Does F34 behave the same?
(In reply to Adam Williamson from comment #6) > Does F34 behave the same? Yes, F34 clean KDE Live install behaves the same.
In today's Go/No-Go meeting we agreed: It is functional enough to ship and fix in an update, but we'd like to have it in the release if a fix is available and we slip https://meetbot.fedoraproject.org/fedora-meeting/2021-10-21/f35-final-go_no_go-meeting.2021-10-21-17.00.log.html#l-130
Known upstream bug: https://bugs.kde.org/show_bug.cgi?id=443615
I spent some time looking into this one yesterday. It's not clear to me if it's a packagekit dnf backend but or Discover's, I guess I better see if we can workaround it from within Discover anyway. Problem is that we are using the package id that the install transaction gives us as the new pkgid, I can change it to issue a new resolve query instead.
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.
The update https://bodhi.fedoraproject.org/updates/FEDORA-2021-f7d19c8901 seems to fix this bug, tested here: installed and removed software without errors, and without discover restart.
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.