Github messages for voidlinux
 help / color / mirror / Atom feed
From: SpidFightFR <SpidFightFR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Flatpak displays an error since curl update
Date: Thu, 19 Sep 2024 12:24:32 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52273@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 772 bytes --]

New issue by SpidFightFR on void-packages repository

https://github.com/void-linux/void-packages/issues/52273

Description:
### 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`

             reply	other threads:[~2024-09-19 10:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 10:24 SpidFightFR [this message]
2024-09-19 10:24 ` Felipe-Rafael-Rosa
2024-09-19 10:29 ` Clos3y
2024-09-19 10:56 ` SpidFightFR
2024-09-19 10:56 ` SpidFightFR
2024-09-19 11:05 ` SpidFightFR
2024-09-19 11:38 ` classabbyamp
2024-09-19 11:50 ` SpidFightFR
2024-09-19 11:52 ` SpidFightFR
2024-09-19 11:54 ` SpidFightFR
2024-09-19 12:24 ` SpidFightFR
2024-09-19 12:24 ` chrysos349
2024-09-19 14:54 ` TeusLollo
2024-09-19 15:57 ` SpidFightFR
2024-09-19 15:58 ` SpidFightFR
2024-09-19 16:03 ` [ISSUE] [CLOSED] " Duncaen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52273@inbox.vuxu.org \
    --to=spidfightfr@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).