Description of problem: flatpack crashes every time I run "flatpak install --from https://firefox-flatpak.mojefedora.cz/org.mozilla.FirefoxNightly.flatpakref" Version-Release number of selected component: flatpak-1.2.4-3.fc30 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: flatpak install --from https://firefox-flatpak.mojefedora.cz/org.mozilla.FirefoxNightly.flatpakref crash_function: multi_socket executable: /usr/bin/flatpak journald_cursor: s=2b38e6c3122a4bd9a8bfd163f91d0c3b;i=1b10ce;b=5fbc9768b7b1408086c30301f30cb0a4;m=51e0f9fb3;t=589ed301d7f14;x=74d0074d253cac8c kernel: 5.0.17-300.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 multi_socket at ../../lib/multi.c:2652 #1 curl_multi_socket_action at ../../lib/multi.c:2838 #2 event_cb at src/libostree/ostree-fetcher-curl.c:451 #6 g_main_context_iteration at ../glib/gmain.c:3988 #7 ostree_repo_pull_with_options at src/libostree/ostree-repo-pull.c:4491 #8 repo_pull at common/flatpak-dir.c:4030 #9 flatpak_dir_pull at common/flatpak-dir.c:4771 #10 flatpak_dir_install at common/flatpak-dir.c:7810 #11 flatpak_transaction_real_run at common/flatpak-transaction.c:2892 #12 flatpak_cli_transaction_run at ./common/flatpak-transaction.h:92
Created attachment 1574223 [details] File: backtrace
Created attachment 1574224 [details] File: cgroup
Created attachment 1574225 [details] File: core_backtrace
Created attachment 1574226 [details] File: cpuinfo
Created attachment 1574227 [details] File: dso_list
Created attachment 1574228 [details] File: environ
Created attachment 1574229 [details] File: exploitable
Created attachment 1574230 [details] File: limits
Created attachment 1574231 [details] File: maps
Created attachment 1574232 [details] File: mountinfo
Created attachment 1574233 [details] File: open_fds
Created attachment 1574234 [details] File: proc_pid_status
Created attachment 1574235 [details] File: var_log_messages
Oops, didn't mean to make the bug restricted - there's nothing sensitive here. But I can't figure out how to make it public.
*** This bug has been marked as a duplicate of bug 1697566 ***