Running zypper ref segfaults. The last time I ran zypper ref successfully was on 02 Jan 2012. Since that time I have not changed repos nor installed anything.
To narrow down the case I’ve disabled all non-standard repositories.
Thanks for advice but trying to remove libzypp and zypper as suggested (rpm -e libzypp zypper) gives a dependency error:
error: Failed dependencies:
libzypp.so.1003()(64bit) is needed by (installed) PackageKit-0.6.19-2.6.3.x86_64
libzypp.so.1003()(64bit) is needed by (installed) libqdialogsolver1-1.3.0-12.1.3.x86_64
libzypp.so.1003()(64bit) is needed by (installed) yast2-ncurses-pkg-2.21.2-1.1.2.x86_64
libzypp.so.1003()(64bit) is needed by (installed) yast2-qt-pkg-2.21.13-1.2.x86_64
libzypp.so.1003()(64bit) is needed by (installed) yast2-pkg-bindings-2.21.11-2.1.3.x86_64
libzypp >= 10.3.1-2.2 is needed by (installed) libqdialogsolver1-1.3.0-12.1.3.x86_64
libzypp >= 7.4.0 is needed by (installed) yast2-ncurses-pkg-2.21.2-1.1.2.x86_64
libzypp >= 7.4.0 is needed by (installed) yast2-qt-pkg-2.21.13-1.2.x86_64
libzypp >= 6.6.0 is needed by (installed) yast2-pkg-bindings-2.21.11-2.1.3.x86_64
zypper >= 0.12.6 is needed by (installed) suseRegister-1.4-13.1.3.noarch
zypper is needed by (installed) libksuseinstall1-4.7.2-5.2.2.x86_64
Not if it’s a 64bit system. I just guessed from the only enabled repository URL. Because I was guessing I said “something like”, leaving you to modify accordingly.
I found /var/cache/zypp and /var/cache/zypper (the latter one seems to be pretty old). I moved them away to “clear cache”. When running “zypper -v ref” the output is the same but the last line which now says:
The problem seems to be in libproxy. When running wget from behind a proxy and http_proxy variable is defined, everything works. But when running wget from beheind a proxy and http_proxy variable is NOT defined, it segfaults:
On 01/05/2012 10:36 AM, pahlo wrote:
> I’ve run out of ideas, I’m going to reinstall the
> box.
if you have not yet reinstalled (or if you have and find the same
problem before you add all of those repos again) then at the first
green screen during boot, press F5 and select systemv (instead of
systemd) and see if that has an impact on your problem…
note: i always suggest following the excellent advice found in the
paragraph beginning with “IMPORTANT” here http://tinyurl.com/33qc9vu
and, as your needs require other repos be drawn from, just be aware
that it is possible to update your system with conflicting packages
until all sorts of little problems pop up…
there is nothing inherently wrong with having hundreds of repos
available…the problem comes when one has a huge group enabled,
refreshed and then run “zypper up” or “zypper dup” (either of which is
kinda like putting in one bullet, spinning the cylinder, taking careful
aim at your own foot and pressing enter!)
On 01/05/2012 11:46 AM, pahlo wrote:
>
> I did a clean install from our mirror. Everything went OK until running
> “you” which upgraded zypper. During upgrade: segfault as before.
very strange!
perhaps you have discovered a bug in
zypper-1.6.18-5.8.1.x86_64.rpm
perhaps you can go back to the previous
zypper-1.6.16-5.3.1.x86_64.rpm
The problem is in NO_PROXY in /etc/sysconfig/proxy. If it contains network definition like 10.0.0.0/8, the segfault appears. Once the network definition is removed, the segfault disappears.
pahlo wrote:
> It seems I’m not the first one:
>
> https://bugzilla.novell.com/show_bug.cgi?id=739069
>
> The problem is in NO_PROXY in /etc/sysconfig/proxy. If it contains
> network definition like 10.0.0.0/8, the segfault appears. Once the
> network definition is removed, the segfault disappears.
Are you the person who posted comment #1? If not, I suggest you add a
“me too” posting with your segfault and system details. The more people
report it, the sooner it might get fixed.
On 2012-01-05 14:06, pahlo wrote:
>
> It seems I’m not the first one:
>
> https://bugzilla.novell.com/show_bug.cgi?id=739069
>
> The problem is in NO_PROXY in /etc/sysconfig/proxy. If it contains
> network definition like 10.0.0.0/8, the segfault appears. Once the
> network definition is removed, the segfault disappears.
A segfault is always a programming error, thus a bug somewhere.
You must add a “meetoo” to the bugzilla report, it is very important.
CRUCIAL, in fact. You are guilty if you don’t fill it.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)