From: Ricardo Wurmus <rekado@elephly.net>
To: 35591@debbugs.gnu.org
Cc: Jonathan Frederickson <jonathan@terracrypt.net>
Subject: bug#35591: Segfault on flatpak remote-add
Date: Mon, 11 May 2020 23:38:05 +0200 [thread overview]
Message-ID: <87r1vq17b6.fsf@elephly.net> (raw)
In-Reply-To: <87tv0m1ar8.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> Ben Sturmfels <ben@sturm.com.au> writes:
>
>> On Sun, 05 May 2019, Jonathan Frederickson wrote:
>>
>>> I'm attempting to use Flatpak on my Guix system, and I'm experiencing
>>> segfaults when attempting to add a remote repo. Provided below are the
>>> output of the command I'm attempting to run, as well as some info
>>> about my system.
>>
>> I learnt on #guix IRC that flatpak works when run with the --user flag:
>>
>> $ flatpak --user remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
>> $ flatpak install flathub org.gnome.Builder
>> $ flatpak run org.gnome.Builder
>>
>> The segfaulting behaviour is still a bug in my opinion, because it's
>> extremely user un-friendly, and the requirement for --user is not
>> obvious.
>
> Yes, segfaults are always bugs, unless you forced the program to
> load garbage.
>
> I traced the execution of flatpak and saw that it segfaults right after
> failing to created /var/lib/flatpak. Sure enough, after creating it
> manually the program no longer segfaults.
I reported this here:
https://github.com/flatpak/flatpak/issues/3612
I’d say we close this issue here, because the segfault isn’t our fault.
Thoughts?
--
Ricardo
next prev parent reply other threads:[~2020-05-11 21:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 20:05 bug#35591: Segfault on flatpak remote-add Jonathan Frederickson
2019-05-05 22:36 ` Mark H Weaver
2019-05-05 22:47 ` Jonathan Frederickson
2019-10-31 10:50 ` Ben Sturmfels
2020-05-11 20:23 ` Ricardo Wurmus
2020-05-11 21:38 ` Ricardo Wurmus [this message]
2020-05-14 5:26 ` Ricardo Wurmus
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=87r1vq17b6.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=35591@debbugs.gnu.org \
--cc=jonathan@terracrypt.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.