Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#58939 - flatpak build seg faults in 0.11.8/0.11.8.1

Attached to Project: Arch Linux
Opened by Fernando Fernandez (bereltarmaciltur) - Saturday, 09 June 2018, 04:36 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Monday, 11 June 2018, 08:10 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

flatpak build seg faults (killed by signal 11) in version 0.11.8 and 0.11.8.1
works well after downgrade to flatpak 0.11.7

log:
jun 09 01:17:24 alsius kernel: flatpak[4976]: segfault at 18 ip 000055cd02af4790 sp 00007fffe0657518 error 4 in flatpak[55cd02a86000+c1000]
jun 09 01:17:24 alsius systemd[1]: Started Process Core Dump (PID 4977/UID 0).
jun 09 01:17:25 alsius systemd-coredump[4978]: Process 4976 (flatpak) of user 1000 dumped core.

Stack trace of thread 4976:
#0 0x000055cd02af4790 n/a (flatpak)
#1 0x000055cd02ab246f n/a (flatpak)
#2 0x000055cd02aa1a6a n/a (flatpak)
#3 0x00007fb44907306b __libc_start_main (libc.so.6)
#4 0x000055cd02aa1e2a n/a (flatpak)

Steps to reproduce:
* install flatpak 0.11.8.1
* try to build an app with flatpak build (flatpak-builder gnome-builder)
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Monday, 11 June 2018, 08:10 GMT
Reason for closing:  Upstream
Additional comments about closing:  https://github.com/flatpak/flatpak/issue s/1770
Comment by Bartłomiej Piotrowski (Barthalion) - Sunday, 10 June 2018, 20:12 GMT
http://pkgbuild.com/~bpiotrowski/.fs58939/flatpak-0.11.8.1-1.1-x86_64.pkg.tar.xz

Please install it (with -U <url> for signature verification) and trigger the problem again, it will print a more useful trace.
Comment by Bartłomiej Piotrowski (Barthalion) - Sunday, 10 June 2018, 20:18 GMT
Okay, so actual trace is:

Stack trace of thread 8364:
#0 0x0000564686d50790 flatpak_context_allows_features (flatpak)
#1 0x0000564686d0e46f flatpak_builtin_build (flatpak)
#2 0x0000564686cfda6a flatpak_run (flatpak)
#3 0x00007fcda222106b __libc_start_main (libc.so.6)
#4 0x0000564686cfde2a _start (flatpak)
Comment by Bartłomiej Piotrowski (Barthalion) - Sunday, 10 June 2018, 20:19 GMT
I will try to debug it further tomorrow morning but most likely it's upstream issue.

Loading...