I have run into this issue as well trying to upgrade from Leap 15.0 to Leap 15.1. Ended up using the bruit force script that Reg_gie made. Hopefully this works. The other workaround was to use the upgrade option on the Leap 15.1 DVD image.
I have run into this issue as well trying to upgrade from Leap 15.0 to Leap 15.1. Ended up using the bruit force script that Reg_gie made. Hopefully this works. The other workaround was to use the upgrade option on the Leap 15.1 DVD image.
Experiencing this problem mid-November 2019, either segfault or silent exit. Thanks for the folks upsthread who pointed me to curl and libcurl, updated those and now working fine.
et al:
Had this problem in my TW install, now running only in TTY . . . got the "segmentation fault" after pulling three lines of the Main repository . . . I thought it was a sure sign that my broken non-booting TW install had finally gone completely "belly up" . . . .
Nope, just a bug that's been around since March . . . glad I found this thread.
It doesn't seem like the fix has been ported to Leap 15.0. Even after updating libcurl and curl, I still have this issue.
Hi and welcome to the Forum
I doubt there would be a fix forthcoming as Leap 15.0 went EOL at the end of November (2 days ago).....
https://en.opensuse.org/Lifetime
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below... Thanks!
No segfaults occurring with Leap 15.1 or Tumbleweed:
Code:erlangen:~ # grep libcurl4 /mnt/var/log/zypp/history 2019-11-21 21:43:34|install|libcurl4|7.60.0-lp151.4.2|x86_64||openSUSE-Leap-15.1-1|5371f05e700ec048308d8e44723c7fd7eb9eb14b57e81b3de4b67241db0bab5c| 2019-11-21 22:16:57|install|libcurl4|7.60.0-lp151.5.9.1|x86_64||repo-update|0bba135ddc2b494adbdf2b32e340b06f81e4ca0eb1eb147053ffe7e13c0a2385| erlangen:~ # grep libcurl4 /var/log/zypp/history 2019-11-08 18:58:47|install|libcurl4|7.66.0-1.1|x86_64||openSUSE-20191106-0|e5007389397247224da618b59c00cfb0d3b3c8ed367768903bb464adde52702a| 2019-11-12 23:15:07|install|libcurl4|7.67.0-1.1|x86_64||openSUSE-20191106-0|9bbf14a2c6057ecabac3a7a16f8e080bc37e29d7a395e5e1ac0d50ec5d52d5bd| 2019-11-18 10:23:17|install|libcurl4|7.67.0-3.1|x86_64||repo-update|a42bf6d3053994544583fb11c49aebca7060809f759f6108e46a4c618f0b3edf| 2019-11-21 14:07:15|install|libcurl4|7.67.0-2.1|x86_64||openSUSE-20191106-0|6be48b0fd04e61a5b33c38751c81806230685de9ce8a6ba82467e111ad777c92| erlangen:~ #
AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5
https://bugzilla.opensuse.org/show_bug.cgi?id=1146027 fix for 15.0 is 2 months old in 17.14.1 libzypp. TW's https://bugzilla.opensuse.org/show_bug.cgi?id=1156481 remains open. I suppose you could try backleveling from 17.15.0 to 17.14.1.
Reg. Linux User #211409 *** multibooting since 1992
Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
Secondary: eComStation (OS/2)&42.3 on 965P/Radeon
Tertiary: TW,15.0,42.3,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&
Bookmarks