From: duncancmt <duncancmt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] flatpak segfaults on remote-add on aarch64 musl
Date: Mon, 12 Oct 2020 03:03:30 +0200 [thread overview]
Message-ID: <20201012010330.ZmJS_jogW9wDaQPz0L1feqs0V8xgVNm-xEpu0FzBKVw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24783@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
Closed issue by duncancmt on void-packages repository
https://github.com/void-linux/void-packages/issues/24783
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
`Void 5.7.0_1 aarch64-musl Unknown uptodate rFFF`
* package:
`flatpak-1.6.3_1`
### Expected behavior
```
$ flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
<something>
```
### Actual behavior
```
$ flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
Segmentation fault
$ echo $?
139
```
### Steps to reproduce the behavior
see above
I have tried building from source with debugging symbols and running it under `gdb`, but `gdb` itself aborts (and running `flatpak` under `gdb` under `gdb` similarly crashes).
prev parent reply other threads:[~2020-10-12 1:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 14:56 [ISSUE] flatpak segfaults on remote-add duncancmt
2020-09-09 14:58 ` flatpak segfaults on remote-add on aarch64 musl ericonr
2020-09-09 16:09 ` duncancmt
2020-09-09 16:21 ` ericonr
2020-09-09 16:28 ` duncancmt
2020-09-09 16:32 ` ericonr
2020-09-09 16:33 ` duncancmt
2020-09-09 18:13 ` duncancmt
2020-09-09 18:17 ` duncancmt
2020-09-09 18:18 ` ericonr
2020-09-09 18:19 ` ericonr
2020-09-09 18:34 ` duncancmt
2020-09-09 19:03 ` ericonr
2020-09-09 19:03 ` ericonr
2020-10-12 1:03 ` duncancmt
2020-10-12 1:03 ` duncancmt [this message]
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=20201012010330.ZmJS_jogW9wDaQPz0L1feqs0V8xgVNm-xEpu0FzBKVw@z \
--to=duncancmt@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).