New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Gnome software stuck due to flatpak #5519
Comments
Not sure if this is helpful, here's what thread 11 returns:
|
There was already a timeout set using `CURLOPT_CONNECTTIMEOUT`, but that only affects the initial connection. Once a HTTP connection is established, the timeout is ineffective. That means that once a HTTP connection is established, there is no bound on the length of time a download can take. Sometimes, downloads drop to very low speeds (for Networking Reasons) and we need a way to give up on a download if that happens. So, set a low speed limit of 10KB/s for 60s. If a curl download goes more slowly than this, it will be considered timed out, and the `CURLE_OPERATION_TIMEDOUT` code path will be taken. Signed-off-by: Philip Withnall <[email protected]> Fixes: flatpak#5519
#5520 might fix this, but it’s a guess. I cannot reproduce the issue. From Adding a low-speed timeout should help with that. I’m guessing it’s fallen over for misc Networking Reasons, rather than any bugs in the client side (libcurl should be pretty robust as a HTTP implementation!). |
There was already a timeout set using `CURLOPT_CONNECTTIMEOUT`, but that only affects the initial connection. Once a HTTP connection is established, the timeout is ineffective. That means that once a HTTP connection is established, there is no bound on the length of time a download can take. Sometimes, downloads drop to very low speeds (for Networking Reasons) and we need a way to give up on a download if that happens. So, set a low speed limit of 10KB/s for 60s. If a curl download goes more slowly than this, it will be considered timed out, and the `CURLE_OPERATION_TIMEDOUT` code path will be taken. Signed-off-by: Philip Withnall <[email protected]> Fixes: #5519
I think I am affected by this issue as well. Is there a way for me to update flatpak to #5520 and try out the fix? When trying to install an app via flatpak (i.e. Using The Secondly (and I guess that's the bigger issue) the |
There was already a timeout set using `CURLOPT_CONNECTTIMEOUT`, but that only affects the initial connection. Once a HTTP connection is established, the timeout is ineffective. That means that once a HTTP connection is established, there is no bound on the length of time a download can take. Sometimes, downloads drop to very low speeds (for Networking Reasons) and we need a way to give up on a download if that happens. So, set a low speed limit of 10KB/s for 60s. If a curl download goes more slowly than this, it will be considered timed out, and the `CURLE_OPERATION_TIMEDOUT` code path will be taken. Signed-off-by: Philip Withnall <[email protected]> Fixes: flatpak#5519 (cherry picked from commit d6b10c2)
Checklist
Flatpak version
1.15.4
What Linux distribution are you using?
Fedora Linux
Linux distribution version
38
What architecture are you using?
x86_64
How to reproduce
Not sure it can be reproduced without problems
Expected Behavior
It should fetch updates and show them
Actual Behavior
It keeps spinning forever. According to a gnome software dev due to flatpak not returning/timing out from a download in thread 11.
Additional Information
The text was updated successfully, but these errors were encountered: