David C. Rankin composed on 2019-09-02 02:17 (UTC-0500):
There is nothing above that jumps out as remotely a cause of the problem you are experiencing. The only thing I can think of is that there were several complete and partial rebuilds of the KDE3 repo that took place in the timeframe of your failed update. And while it should not happen, I wonder if the repo you were pulling from somehow was in a partial update state when you did the update. I can't explain how that would effect libzypp, glibc or libcurl, but the kde-yast package and a slew of osc/zypp packages also had updates at that same time.
Are you able to do a full zypper up now and see if it straightens itself out? The only other guess I have is to use rpmdb --rebuilddb to check and rebuild the rpm database to determine if there is any inconsistency there.
Thread was started based upon host big41. There before I started this thread I just continued to repeat zypper -v up until there were no more updates left to install. IIRC, somewhere along the way I did rebuilddb, but it didn't stop the segfaulting. Now the problem returned on a different host, big31, which had last been updated about 7 weeks ago. Segfaults were 4 on this one. None happened until after I ran my package management update script, which downloads in advance. Segfaults didn't start until having answered N several times to zypper -v up, which I did because of seeing this on responding g: # zypper -v up ... ( 6 new packages will be installed ) ... l | libBasicUsageEnvironment1 | package | 2019.06.28-lp150.12.1 | x86_64 | Update l | libUsageEnvironment3 | package | 2019.06.28-lp150.12.1 | x86_64 | Update ( and 4 others ) ...continue Y/N? n It took me 20 minutes to dig these lines out of zypp history, so I quit trying before finding the other 4. Zypper.log is so huge I didn't find anything useful in it. My Ns only resulted after seeing 6 *new* packages proposed to be included in the 'zypper -v update'. I started KDE to make it easier to capture the activity, then added a lock to account for a few, and on seeing names of those remaining, tried more locking before another attempt, and repeat until proposed new packages ceased showing up. After all zypper updates completed, I removed the locks and repeated up only to *again* find no packages to update - no sign of any of those proposed on the screen, or in history. If they're in zypper.log, they're well obfuscated by the volume and not knowing the names of the other 4. How is it that a zypper up can cause any new packages to be installed; and *then* *forget* everything about them after refusing to allow their installation via locks? What are these new *Environment* packages and probable deps about? -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org