On 31/01/2019 06.30, David C. Rankin wrote:
On 01/30/2019 11:15 PM, Basil Chupin wrote:
> I am trying to update my wife's Leap 15.0 system and get this error when
> using either zypper or Yast2.
> I am using the kernel from the ../Kernel:/stable/standard/ repository on
> my Leap 15.0 as well as hers but I am not having this hassle.
> When using zypper to update I get this error msg (pls see attached
> zypper_error-31.png) and when using Yast I get the error msg in the
> attached Yast_error-31.png.
> Yesterday when I tried to do same, the 'zypper up' got a lot further in
> the installation - pls see attached zypper_error.png.
Do "dmesg" just after the error. There should be an entry in the last
line about the segmentation fault.
Or just peruse the log now and search back for it (word "segmentation"
or perhaps "coredump").
> I have run 'zypper clean -a' and 'zypper refresh -fdb' but this
> Anyone please suggest what is causing this problem and how to how to get
> rid of the cause of this problem?
I would try "rpmdb --rebuilddb".
This is more a calculated guess than a silver bullet,
but it looks like the
4.20.5 kernel (brand new) is not playing well with the 20181218
kernel-firmware patch. I do know I got new firmware with 4.20.5 on Arch, so I
suspect the same would be needed with openSuSE.
From a recent thread in factory mail list, I understand it is better to
try the tumbleweed kernel. I can search the explanation if you want.
Cheers / Saludos,
Carlos E. R.
(from 15.0 x86_64 at Telcontar)