Skip to content
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

Flatpak displays an error since curl update #52273

Closed
SpidFightFR opened this issue Sep 19, 2024 · 12 comments · Fixed by #52276
Closed

Flatpak displays an error since curl update #52273

SpidFightFR opened this issue Sep 19, 2024 · 12 comments · Fixed by #52276
Labels
bug Something isn't working needs-testing Testing a PR or reproducing an issue needed

Comments

@SpidFightFR
Copy link
Contributor

Is this a new report?

Yes

System Info

Void 6.10.10_1 x86_64 AuthenticAMD uptodate rrmFFFFFFFF

Package(s) Affected

flatpak-1.15.10_1, curl-8.10.1_1

Does a report exist for this bug with the project's home (upstream) and/or another distro?

N.A

Expected behaviour

  1. flatpak update --user
  2. [Updates user-wide flatpaks]

Actual behaviour

Installing 1/X…**
OSTree:ERROR:src/libostree/ostree-fetcher-curl.c:534:sock_cb: code should not be reached
Bail out! OSTree:ERROR:src/libostree/ostree-fetcher-curl.c:534:sock_cb: code should not be reached
Abandon

Steps to reproduce

  1. flatpak update --user
@SpidFightFR SpidFightFR added bug Something isn't working needs-testing Testing a PR or reproducing an issue needed labels Sep 19, 2024
@Clos3y
Copy link
Contributor

Clos3y commented Sep 19, 2024

Am getting the same error.

@SpidFightFR
Copy link
Contributor Author

SpidFightFR commented Sep 19, 2024

This might help:This file might fix it

[REDACTED - Suspicious link] If you don't have the c compliator, install it.(gcc or clang)

sorry but...
That's weird as hell.

Posting a random mega link with a "fix" in a zip...
Could be literally anything else but a fix. Do you have sources ?

@SpidFightFR
Copy link
Contributor Author

ain't no way i'm downloading this zip file, lad.

@classabbyamp
Copy link
Member

that was spam

@SpidFightFR
Copy link
Contributor Author

that was spam

indeed. About the issue though...
Flatpak is currently broken.

@SpidFightFR
Copy link
Contributor Author

i'm unable to tell if a recompilation of flatpak (perhaps in an attempt to take into consideration the libcurl (thus curl) update) could fix the issue...

@SpidFightFR
Copy link
Contributor Author

SpidFightFR added a commit to SpidFightFR/void-packages that referenced this issue Sep 19, 2024
@SpidFightFR
Copy link
Contributor Author

I opened a pr with a fix. A true one this time: #52276 .
Apparently it started with Alpine and Gentoo as well.

Anyways i tested on my laptop the fix, it indeed fixes the flatpak issue.

@chrysos349
Copy link
Contributor

ostreedev/ostree#3299

@TeusLollo
Copy link

This time you beat me to it :)

Updating 1/3…**
OSTree:ERROR:src/libostree/ostree-fetcher-curl.c:534:sock_cb: code should not be reached
Bail out! OSTree:ERROR:src/libostree/ostree-fetcher-curl.c:534:sock_cb: code should not be reached
zsh: IOT instruction sudo flatpak update

Anyway, they're saying that this fixes it: ostreedev/ostree#3299 (comment)

@SpidFightFR
Copy link
Contributor Author

This time you beat me to it :)

Updating 1/3…** OSTree:ERROR:src/libostree/ostree-fetcher-curl.c:534:sock_cb: code should not be reached Bail out! OSTree:ERROR:src/libostree/ostree-fetcher-curl.c:534:sock_cb: code should not be reached zsh: IOT instruction sudo flatpak update

Anyway, they're saying that this fixes it: ostreedev/ostree#3299 (comment)

yep, it's in the PR. I can confirm this PR works on my laptop. 👍

@SpidFightFR
Copy link
Contributor Author

sidenote: we'll be able to remove this patch at the next release of ostree.

Duncaen pushed a commit that referenced this issue Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-testing Testing a PR or reproducing an issue needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants
@classabbyamp @Clos3y @SpidFightFR @chrysos349 @TeusLollo and others