Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1714533[details]
Screenshot of `flatpak update`
Description of problem:
When invoking a command `flatpak update` I get quite often a weird progressbar which goes highly above 100% (image attached).
Version-Release number of selected component (if applicable):
Flatpak 1.6.2
How reproducible:
The weird behavior does not occur for all update items, I have not found out any pattern in it.
Additional info:
What I remember this issue was not happening in 1.0.x version.
Note: This linked PR is for ostree based Flatpaks (ie. Flathub ones). The OCI Flatpaks (RHEL, Fedora) had the progress broken as well and it was fixed with https://github.com/flatpak/flatpak/pull/3850
https://github.com/flatpak/flatpak/pull/3850 fixed OCI progress not working at all in flatpak 1.8.x (it had regressed compared to 1.6.x). I don't think it changed anything related to the 100% issue.
True, I just wanted to mention the OCI issue there as well so when the 1.8 rebase will be tested we check both OCI and ostree (as the OCI change wasn't backported to 1.8 - it might be in some of the future 1.8.x release)
(In reply to Tomas Popela from comment #3)
> True, I just wanted to mention the OCI issue there as well so when the 1.8
> rebase will be tested we check both OCI and ostree (as the OCI change wasn't
> backported to 1.8 - it might be in some of the future 1.8.x release)https://github.com/flatpak/flatpak/pull/3850 was backported to flatpak-1.8.3:
https://github.com/flatpak/flatpak/commit/4e47dba3b3ae095abd0cb2d53ec99c1d68d0d4b7
It has been in RHEL 8 since 8.4.
Maybe Martin knows if we have tests for it - do we? It would be ideal if the upstream test suite covered this. I don't know if it does.
I am marking this as a duplicate of the rebase to 1.8.x
I am still curious about the tests, though. If we don't have anything, I can look into adding some to the upstream test suite.
*** This bug has been marked as a duplicate of bug 1851958 ***
Created attachment 1714533 [details] Screenshot of `flatpak update` Description of problem: When invoking a command `flatpak update` I get quite often a weird progressbar which goes highly above 100% (image attached). Version-Release number of selected component (if applicable): Flatpak 1.6.2 How reproducible: The weird behavior does not occur for all update items, I have not found out any pattern in it. Additional info: What I remember this issue was not happening in 1.0.x version.