Bugzilla – Bug 1084796
Segmentation fault with zypper after zypper dup to TW20180305 and reboot on aarch64 (Raspberry Pi 3B)
Last modified: 2018-03-19 03:26:47 UTC
I used the image file openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.aarch64-2018.02.02-Build1.2.raw.xz to build a system om a Raspberry Pi 3B. After that I did a "zypper dup --no-recommends" to TW20180305 and installed a few other packages. After a reboot using zypper I get a Segmentation fault. I also use "git clone" which does not give a clear error message, instead gives Cloning into 'xxxxx'..., however not even the folder xxxxx has been created. I have a number of coredumps from git, a.o.: /var/lib/systemd/coredump/core.git-remote-http.0.5701e233682d45d296fb928e88862f6c.1448.1520718889000000.lz4
Can you try what is describe in this link: https://bugzilla.opensuse.org/show_bug.cgi?id=1084812#c5
Added "195.135.221.134 download.opensuse.org" to /etc/hosts and the problem with zypper is gone.
(In reply to Freek de Kruijf from comment #2) > Added "195.135.221.134 download.opensuse.org" to /etc/hosts and the problem > with zypper is gone. Al least when doing "zypper se git". I got the 4 mentioned files in comment #5. Installation succeeded after ignoring Signature verification. Also only two got installed from the rpm files, 3 others were downloaded.
(In reply to Freek de Kruijf from comment #3) > (In reply to Freek de Kruijf from comment #2) > > Added "195.135.221.134 download.opensuse.org" to /etc/hosts and the problem > > with zypper is gone. > > Al least when doing "zypper se git". > > I got the 4 mentioned files in comment #5. > Installation succeeded after ignoring Signature verification. Also only two > got installed from the rpm files, 3 others were downloaded. Apparently the downloaded ones did not get installed. After a reboot 4 packages came from obs://build.opensuse.org/home:StefanBruens
I installed python2-pip, but the command "pip > /dev/null" segfaults.
Let's consolidate the information where the most details are. *** This bug has been marked as a duplicate of bug 1084812 ***