[ISSUE] flatpak segfaults on remote-add

[ISSUE] flatpak segfaults on remote-add

[duncancmt]

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

New 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_2 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).

Re: flatpak segfaults on remote-add on aarch64 musl

[ericonr]

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

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/24783#issuecomment-689618962

Comment:
You can also download the `flatpak-dbg` package from the `void-repo-debug` repository.

Did this drop a core dump or anything of the sort?

Re: flatpak segfaults on remote-add on aarch64 musl

[duncancmt]

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

New comment by duncancmt on void-packages repository

https://github.com/void-linux/void-packages/issues/24783#issuecomment-689663684

Comment:
Where would be the appropriate place to submit a coredump?

Re: flatpak segfaults on remote-add on aarch64 musl

[ericonr]

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

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/24783#issuecomment-689670527

Comment:
`xbps-install $(xdbg flatpak)` -> installs all debug packages related to flatpak, then you can generate a backtrace from the core dump. Otherwise you'd need to upload the coredump and hope someone is invested enough to assemble the backtrace for you.

Re: flatpak segfaults on remote-add on aarch64 musl

[duncancmt]

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

New comment by duncancmt on void-packages repository

https://github.com/void-linux/void-packages/issues/24783#issuecomment-689674628

Comment:
Thanks for the help. I have a coredump and all the `*-dbg` packages installed. However `gdb` _itself_ aborts when running `flatpak` or when analyzing the coredump:

```
$ gdb `which flatpak` core.12507
GNU gdb (GDB) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "aarch64-linux-musl".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /bin/flatpak...
Reading symbols from /usr/lib/debug//usr/bin/flatpak...
[New LWP 12512]
[New LWP 12507]
[New LWP 12511]
[New LWP 12509]

warning: Can't read pathname for load map: No error information.
Core was generated by `/usr/bin/flatpak remote-add --if-not-exists flathub https://flathub.org/repo/fl'.
Program terminated with signal SIGSEGV, Segmentation fault.
Aborted
$ echo $?
134
```

Re: flatpak segfaults on remote-add on aarch64 musl

[ericonr]

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

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/24783#issuecomment-689676839

Comment:
Very long shot, can you try `gdb -c core.12507` ?

Re: flatpak segfaults on remote-add on aarch64 musl

[duncancmt]

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

New comment by duncancmt on void-packages repository

https://github.com/void-linux/void-packages/issues/24783#issuecomment-689677430

Comment:
That does give me something! Probably not very useful, though:
```
$ gdb -c core.12507
GNU gdb (GDB) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "aarch64-linux-musl".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word".
[New LWP 12512]
[New LWP 12507]
[New LWP 12511]
[New LWP 12509]
Core was generated by `/usr/bin/flatpak remote-add --if-not-exists flathub https://flathub.org/repo/fl'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000ffffae3497dc in ?? ()
[Current thread is 1 (LWP 12512)]
(gdb) bt
#0  0x0000ffffae3497dc in ?? ()
#1  0x0000ffffac9c171c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)
```

Re: flatpak segfaults on remote-add on aarch64 musl

[duncancmt]

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

New comment by duncancmt on void-packages repository

https://github.com/void-linux/void-packages/issues/24783#issuecomment-689731176

Comment:
Maybe the bigger issue is that `gdb` doesn't work:
```
$ gdb
GNU gdb (GDB) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "aarch64-linux-musl".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) help symbol
Load symbol table from executable file FILE.
Usage: symbol-file [-readnow | -readnever] [-o OFF] FILE
OFF is an optional offset which is added to each section address.
The `file' command can also load symbol tables, as well as setting the file
to execute.
The '-readnow' option will cause GDB to read the entire symbol file
immediately.  This makes the command slower, but may make future operations
faster.
The '-readnever' option will prevent GDB from reading the symbol file's
symbolic debug information.
(gdb) help symbols
Aborted
$ echo $?
134
```

Re: flatpak segfaults on remote-add on aarch64 musl

[duncancmt]

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

New comment by duncancmt on void-packages repository

https://github.com/void-linux/void-packages/issues/24783#issuecomment-689731176

Comment:
Maybe the bigger issue is that `gdb` doesn't work:
```
$ gdb
GNU gdb (GDB) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "aarch64-linux-musl".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) help symbol
Load symbol table from executable file FILE.
Usage: symbol-file [-readnow | -readnever] [-o OFF] FILE
OFF is an optional offset which is added to each section address.
The `file' command can also load symbol tables, as well as setting the file
to execute.
The '-readnow' option will cause GDB to read the entire symbol file
immediately.  This makes the command slower, but may make future operations
faster.
The '-readnever' option will prevent GDB from reading the symbol file's
symbolic debug information.
(gdb) help symbols
Aborted
$ echo $?
134
```

```
$ gdb gdb
GNU gdb (GDB) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "aarch64-linux-musl".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gdb...
(No debugging symbols found in gdb)
(gdb) run
Starting program: /usr/bin/gdb
[Detaching after fork from child process 5230]
GNU gdb (GDB) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "aarch64-linux-musl".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) help symbols

Program received signal SIGSEGV, Segmentation fault.
Aborted
$ echo $?
134
```

Re: flatpak segfaults on remote-add on aarch64 musl

[ericonr]

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

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/24783#issuecomment-689733855

Comment:
Ohh boy, that could have been caused by some cross compile issue. Last I remember, I could use gdb fine on armv6l-musl, at least.

Re: flatpak segfaults on remote-add on aarch64 musl

[ericonr]

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

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/24783#issuecomment-689734291

Comment:
Can you check if all your files are fine? `xbps-pkgdb -a`

Re: flatpak segfaults on remote-add on aarch64 musl

[duncancmt]

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

New comment by duncancmt on void-packages repository

https://github.com/void-linux/void-packages/issues/24783#issuecomment-689741746

Comment:
```
$ sudo xbps-pkgdb -a
ERROR: device-mapper: hash mismatch for /etc/sv/dmeventd/run.
ERROR: device-mapper: files check FAILED.
ERROR: mdocml: hash mismatch for /etc/cron.daily/makewhatis.
ERROR: mdocml: files check FAILED.
ERROR: pinebookpro-base: hash mismatch for /var/lib/alsa/asound.state.
ERROR: pinebookpro-base: files check FAILED.
ERROR: linux-firmware: /usr/lib/firmware/rockchip/dptx.bin mtime mismatch (current: 1598729144, stored 1590307167)
ERROR: linux-firmware: files check FAILED.
```
Those are all files I manually edited as part of installing my system.

Re: flatpak segfaults on remote-add on aarch64 musl

[ericonr]

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

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/24783#issuecomment-689756083

Comment:
As a tip, you might want to configure xbps so those files aren't overwritten on updates. (see `xbps.d(5)`)

Re: flatpak segfaults on remote-add on aarch64 musl

[ericonr]

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

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/24783#issuecomment-689756288

Comment:
Still, none of that should influence flatpak, afaik.

Re: flatpak segfaults on remote-add on aarch64 musl

[duncancmt]

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

New comment by duncancmt on void-packages repository

https://github.com/void-linux/void-packages/issues/24783#issuecomment-706802144

Comment:
duplicates #25535

Re: [ISSUE] [CLOSED] flatpak segfaults on remote-add on aarch64 musl

[duncancmt]

[-- 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).