Bug ID 1206780
Summary "zypper refresh" segfaults in ARM64 container
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Major
Priority P5 - None
Component libzypp
Assignee zypp-maintainers@suse.de
Reporter martin.wilck@suse.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Happening on latest TW. I'm running TW/aarch64 in a container with
qemu-linux-user.

> podman run --arch arm64 -it --rm registry.opensuse.org/opensuse/tumbleweed:latest
> :/ # zypper refresh
> Segmentation fault (core dumped)

I don't think this is a qemu problem because it happens both on TW/x86_64 with
native qemu-linux-user and on Leap 15.34 with
https://github.com/multiarch/qemu-user-static, and even on an Ubuntu system in
GitHub actions
(https://github.com/mwilck/build-multipath/actions/runs/3820271701/jobs/6500701743#step:11:230).

I can't test this on native TW/aarch64 because I don't have a suitable test
system.

I can provide core dumps, but I am unsure if they'll be helpful or easily
debuggable, as they are formally core dumps from qemu-aarch64.

> > coredumpctl list
> TIME                          PID   UID GID SIG     COREFILE EXE                        SIZE
> Mon 2023-01-02 10:51:06 CET 26071 17326  50 SIGSEGV present  /usr/bin/qemu-aarch64      6.6M


You are receiving this mail because: