For what it’s worth, once that libcurl update was available the other day (I saw it on 3/11) I installed just it in one zypper run and since then have not had any of the segfaults as before.
Oh thanks. That is a good command to know though.
Ugh, this was a nasty one. Had 940 packages to upgrade and kept segfaulting after downloading a few. Glad I found this thread and
zypper in libcurl4
fixed it up. Was going to take ages to fix by just running dup over and over.
I know some people will still be experiencing this as not everyone has updated to certain snapshots yet but … I updated (I think using the “download a little, then re dup, then redup again” method to get all the packages) to the March 10th snapshot and just booted the TW install today and dup’ed again … NO PROBLEMS at all … this issues has been fixed as of the March 10th snapshot, if you ask me… and yes i had seen a libcurl update which is what i am sure it was.
I had/have another thread here related to (during March 01 to March 07 2019) related to my installer just crashing for no reason (the y2*.log … i forgot the exact name)did show a libcurl error … and i never saw a specific error but the live DVD installer (the 4.x GB ISO) would crash too … I am 99.999% it was all due to the same libcurl issue
Yes, that’s entirely possible. I have heard of other people having install problems due to this.
I just updated a system today – previously at 20190301 level. And it segfaulted during update.
After the first segfault, I did:
zypper update libcurl4
The I resumed the interrupted “zypper dup” with no further problems.
I went through the updates and it failed when it got to a GIMP file. It could not find it on the repo. So, I just let it go over night.
Then yesterday I did a dup and it finished up fairly quickly and never got another error. It said to reboot for some process, plus that kernel.
cavsfan@openSUSE:~> uname -r
5.0.1-1-default
Information for package libcurl4:
---------------------------------
Repository : openSUSE-Tumbleweed-Update
Name : libcurl4
Version : 7.64.0-3.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 646.1 KiB
Installed : Yes (automatically)
Status : up-to-date
Source package : curl-7.64.0-3.1.src
Summary : Library for transferring data from URLs
Description :
The cURL shared library for accessing data using different
network protocols.
zypper update libcurl4
I was having this problem doing a dup from Leap 15 to Leap 15.1 and libcurl was already up to date. I even tried downgrading it to the version I had available without success.
The symptom, it would download a random number of files and then get that segment fault. Finally I just brute forced the downloading with the following little bash script:
echo
echo "zypper dup --auto-agree-with-licenses --allow-vendor-change -y --download-only"
echo
iteration=0
rc=-1
while $rc -ne 0 ]; do
zypper dup --auto-agree-with-licenses --allow-vendor-change -y --download-only
rc=$?
echo
echo " Count: $iteration"
echo "Ret Code: $rc"
echo
sleep 2
((iteration++))
done
echo
It took a while but worked like a charm and with a little luck that curl library would have gotten an upgrade when I finished the dup and fixed the problem.
Anyway I hope this helps someone when all else fails, it’s definitely meant only as a “last resort” solution.
BTW, that “iteration count” ended up begin almost 400! …not something you would ever want to do interactively.
Just yesterday I loaded Leap 15.0 fresh on this system from flash drive, and trying to run the update, began having issues with running zypper. Downloads are dying with a seg fault. I ran a zypper clean -a and then attempted a full refresh 3 times and still the downloads are dying with seg fault:
my_pc:~ # zypper clean -a
All repositories have been cleaned up.
my_pc:~ # zypper refresh
Retrieving repository ‘openSUSE-Leap-15.0-Non-Oss’ metadata …[done]
Building repository ‘openSUSE-Leap-15.0-Non-Oss’ cache …[done]
Retrieving repository ‘openSUSE-Leap-15.0-Oss’ metadata ------------------------------------------------------------------------------------------------------------]Segmentation fault (core dumped)
my_pc:~ # zypper refresh
Repository ‘openSUSE-Leap-15.0-Non-Oss’ is up to date.
Retrieving repository ‘openSUSE-Leap-15.0-Oss’ metadata ------------------------------------------------------------------------------------------------------------]Segmentation fault (core dumped)
my_pc:~ # zypper refresh
Repository ‘openSUSE-Leap-15.0-Non-Oss’ is up to date.
Retrieving repository ‘openSUSE-Leap-15.0-Oss’ metadata ------------------------------------------------------------------------------------------------------------]Segmentation fault (core dumped)
After additional attempts at the zupper refresh, I ran into an abort from glibc!
linux-xjhf:~ # zypper refresh
Repository ‘openSUSE-Leap-15.0-Non-Oss’ is up to date.
Retrieving repository ‘openSUSE-Leap-15.0-Oss’ metadata ------------------------------------------------------------------------------------------------------------/]Segmentation fault (core dumped)
linux-xjhf:~ # zypper refresh
Repository ‘openSUSE-Leap-15.0-Non-Oss’ is up to date.
Retrieving repository ‘openSUSE-Leap-15.0-Oss’ metadata ------------------------------------------------------------------------------------------------------------]Fatal error: glibc detected an invalid stdio handle
Aborted (core dumped)
/var/log/messages shows the following after each seg fault, but nothing for the glibc abort:
2019-09-02T11:06:11.901171-05:00 my_pc kernel: 7454.144447] traps: zypper[14955] general protection ip:7efe26e5ea3c sp:7ffec5cb3518 error:0 in libcurl.so.4.5.0[7efe26e25000+85000]
2019-09-02T11:07:00.861268-05:00 my_pc kernel: 7503.102573] traps: zypper[15029] general protection ip:7facba95ea3c sp:7ffcfc0d5e18 error:0 in libcurl.so.4.5.0[7facba925000+85000]
2019-09-02T11:21:57.057131-05:00 my_pc kernel: 8399.281026] zypper[15388]: segfault at 74737190 ip 00007fad6666ffe1 sp 00007ffdd08c5260 error 4 in libcurl.so.4.5.0[7fad6661d000+85000]
Please start a new thread, this one is about Tumbleweed. And use CODE tags, the # in the editor to make output more readable, please. Also, in the new thread show
zypper lr -d
More zypper segfaulting, also not TW:
https://lists.opensuse.org/opensuse-kde3/2019-08/msg00002.html
rest of thread:
https://lists.opensuse.org/opensuse-kde3/2019-09/msg00000.html
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)…
No segfaults occurring with Leap 15.1 or Tumbleweed:
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:~ #
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.
Still happening today.
I had not been on TW in a couple of weeks. So, there were a lot of updates doing a dup. I got so many segfaults it was crazy.
I had to keep re-entering dup, etc. over and over again. It would get further and segfault. It finally finished but, that was hard to endure.
I thought I saw that you had done upgrade on “libcurl” . . . but was that specifically “libcurl4”??? as per the karlmistelberger post above?? I had this problem couple weeks back but just upgrading the “libcurl4” package fixed that problem . . . might be I did
sudo zypper install libcurl4
?? to get zypper to find and upgrade it??