Description of problem: When installing an application from RPMs, Software reports that it has been installed, but when I look into the Installed applications, the application is listed as In Progress. This lasts until the background process is killed with gnome-software --quit. Then, when restarted, the application is correctly placed in the Installed applications. This only happens when the installation source is RPM. When installing from Flatpaks, the lists are updated correctly immediately. Version-Release number of selected component (if applicable): gnome-software-41.0-5.fc35.x86_64 How reproducible: Always Steps to Reproduce: 1. Install an application from the RPMs (make sure, you select the correct source with the source selector). 2. Wait until Software reports that the installation has finished. 3. Navigate to the list of Installed applications. Actual results: The installed application is listed as "In progress". Expected results: The installed application should be listed as Installed immediately. Additional info: This is also filed upstream: https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1492. This bug is for tracking the blocker discussion.
Proposed as a Blocker for 35-final by Fedora user lruzicka using the blocker tracking app because: Hello, I am proposing this for a blocker discussion as it might break the "application basic functionality criterion".
Lukas, have you found any negative effect of this bug? E.g. is there a problem to uninstall the app while it is in the "pending" state? Or is this just a minor glitch that places the app into an incorrect category, but nothing else?
It seems to be a minor glitch but it creates some confusion for the user, if anybody arrives at that page right after the installation.
Discussed during the 2021-10-11 blocker review meeting: [0] The decision to classify this bug as a "RejectedBlocker (Final)" was made as no practical consequences of this have been identified, we agreed it's not really significant enough to count as a failure of "basic functionality", and so it does not meet the blocker criteria. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-10-11/f35-blocker-review.2021-10-11-16.00.txt
Proposed as a Freeze Exception for 35-final by Fedora user lruzicka using the blocker tracking app because: I am reproposing this bug (already rejected as a blocker) for at least a freeze exception based on @mcatanzaro's upstream comment in which he states that "this one is pretty serious", see https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1492#note_1290448.
I reproduced this on a VM and it behaves exactly as Lukas described. It does have any other negative effect. User can start the program installed and can remove it without problems.
Discussed during the 2021-10-18 blocker review meeting: [0] The decision to classify this bug as an "AcceptedFreezeException (Final)" was made as it is a noticeable issue that cannot be fixed with an update. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-10-18/f35-blocker-review.2021-10-18-16.00.txt
FEDORA-2021-616f1be2c0 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-616f1be2c0
(In reply to Fedora Update System from comment #8) > FEDORA-2021-616f1be2c0 has been submitted as an update to Fedora 35. > https://bodhi.fedoraproject.org/updates/FEDORA-2021-616f1be2c0 Fixes the problem.
FEDORA-2021-616f1be2c0 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.