Created attachment 1626474 [details] The error message Description of problem: When I install (or remove) an application using Discover on KDE, I cannot reverse the operation just after it has finished. Such attempt results in an error message saying "Package not found." When I refresh the application list (by conducting a new search for example), the application can be worked with normally and it does not complain any more. It seems to me, however, that this functionality should be possible. Version-Release number of selected component (if applicable): plasma-discover-5.16.5-1 How reproducible: Always Steps to Reproduce: 1. Run Discover. 2. Search for application to install, for example gvim. 3. Install it using the Install button. 4. After the installation, the button changes to Remove. 5. Click on Remove. Actual results: The application cannot be installed or removed right after it has been removed or installed. Expected results: Flawless handling of such application. Additional info: This is reported by PackageKit: Oct 16 14:29:41 localhost-live PackageKit[1448]: in /108_cbaeeebd for remove-packages package vim-X11;2:8.1.2102-1.fc31;x86_64;installed was removing for uid 1000 Oct 16 14:29:41 localhost-live PackageKit[1448]: remove-packages transaction /108_cbaeeebd from uid 1000 finished with success after 713ms Oct 16 14:29:41 localhost-live audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=man-db-cache-update comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Oct 16 14:29:41 localhost-live audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=man-db-cache-update comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Oct 16 14:29:41 localhost-live systemd[1]: man-db-cache-update.service: Succeeded. Oct 16 14:29:41 localhost-live systemd[1]: Started man-db-cache-update.service. Oct 16 14:29:41 localhost-live systemd[1]: run-r5709ee8948304c63abd293641d364edd.service: Succeeded. Oct 16 14:29:41 localhost-live audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=run-r5709ee8948304c63abd293641d364edd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Oct 16 14:29:43 localhost-live PackageKit[1448]: get-updates transaction /109_acbdeeae from uid 1000 finished with success after 2027ms Oct 16 14:29:43 localhost-live PackageKit[1448]: get-updates transaction /110_debdbeba from uid 1000 finished with success after 32ms Oct 16 14:29:45 localhost-live PackageKit[1448]: new install-packages transaction /111_bdbecdab scheduled from uid 1000 Oct 16 14:29:45 localhost-live PackageKit[1448]: install-packages transaction /111_bdbecdab from uid 1000 finished with failed after 8ms Oct 16 14:29:45 localhost-live plasma-discover[1515]: PackageKit error: PackageKit::Transaction::ErrorPackageNotFound "Package not found" "Failed to find vim-X11;2:8.1.2102-1.fc31;x86_64;installed" Oct 16 14:30:01 localhost-live PackageKit[1448]: new install-packages transaction /112_aadddedc scheduled from uid 1000 Oct 16 14:30:01 localhost-live PackageKit[1448]: install-packages transaction /112_aadddedc from uid 1000 finished with failed after 3ms Oct 16 14:30:01 localhost-live plasma-discover[1515]: PackageKit error: PackageKit::Transaction::ErrorPackageNotFound "Package not found" "Failed to find vim-X11;2:8.1.2102-1.fc31;x86_64;installed" Oct 16 14:30:07 localhost-live systemd[1]: fprintd.service: Succeeded. Oct 16 14:30:07 localhost-live audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Proposed as a Blocker for 31-final by Fedora user lruzicka using the blocker tracking app because: I am proposing this as a blocker because it violates the "Application criterion", because this the main software manipulating application for KDE Plasma and it should work flawlessly. Although, package installation and package removal are still possible, the behaviour is quite confusing.
is this new in F31? I'm sorta inclined to -1 blocker because I don't think doing this is very common in normal use, though it certainly *is* common in testing :)
Yeah, I feel like -1 too.
I can confirm the problem on F31 KDE. It's very unclear how to make Discover refresh the information (even if the user knew about this), I had cases where the bug still occurred even after changing screens or searching again. Sometimes the information gets refreshed by accident due to a background updates check. Overall we can make a simplified statement that an installed (or removed) package can't be removed (or installed) again until you close and restart Discover. I tested F30 clean installed from Live and also latest version from netinst. In both cases the same problem is present.
Discussed at 2019-10-17 Fedora 31 go/no-go meeting, acting as a blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2019-10-17/f31-final-go_no_go-meeting.2019-10-17-17.00.html . We decided that this doesn't seem like a common enough use case to merit blocker status, so it is rejected as a blocker. The fact that the bug exists in F30 but we haven't really had super loud complaints about it backs that up. It is accepted as a freeze exception issue, though, as it would be nice to fix this for the OOTB experience if a safe enough fix is found quickly.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.