Bug 468313

Summary:	zypper segfaults
Product:	[openSUSE] openSUSE 11.1	Reporter:	Andreas Vetter <vetter>
Component:	libzypp	Assignee:	E-mail List <zypp-maintainers>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	asklein, meissner, mls
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 11.1
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	gdb output (created without debuginfo) solverTestCase zypper.segfault.log zypper.ZYPP_FULLLOG=1.log zypper.ZYPP_FULLLOG=1.segfault.log zypper.normal.log

Description Andreas Vetter 2009-01-22 10:20:25 UTC

Created attachment 266808 [details]
gdb output (created without debuginfo)

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-0.1 Firefox/3.0.5

zypper rm, zypper in, zypper up, zypper se segfault. 
zypper lr still works. zypper clean -a works, but does not help.

Reproducible: Always

Steps to Reproduce:
zypper search zypper

Actual Results:  
zypper segfaults

Expected Results:  
zypper should not segfault ;-)

yast2 sw_single also segfaults

Comment 1 Marcus Meissner 2009-01-23 08:35:44 UTC

Can you install libzypp-debuginfo (via rpm commandline ;) to capture a better backtrace?

seems like the db state is corrupted somewhere. try: "zypper refresh -f"

Comment 2 Andreas Vetter 2009-01-23 14:25:46 UTC

JFYI: All my repos are on NFS.

Maybe it's a timing problem. After installing libzypp-debuginfo, I had one working attempt in gdb, the next one was segfaulting again. 

wpyc001:~ # rpm -ivh libzypp-debuginfo-5.24.5-1.1.x86_64.rpm
Preparing...                ########################################### [100%]
   1:libzypp-debuginfo      ########################################### [100%]
wpyc001:~ # zypper se zypper
Loading repository data...
Reading installed packages...
Segmentation fault
wpyc001:~ # gdb zypper
GNU gdb (GDB; openSUSE 11.1) 6.8.50.20081120-cvs
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
For bug reporting instructions, please see:
<http://bugs.opensuse.org/>...
(no debugging symbols found)
(gdb) run se zypper
Starting program: /usr/bin/zypper se zypper
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
Loading repository data...
Reading installed packages...

S | Name                  | Summary                                       | Type
--+-----------------------+-----------------------------------------------+--------
i | nagios-plugins-zypper | Nagios plugin for checking software updates   | package
i | zypper                | Command Line Package Management Using Libzypp | package

Program exited normally.
(gdb) se zypper
Ambiguous command "se zypper": search, section, select-frame, set.
(gdb) run se zypper
Starting program: /usr/bin/zypper se zypper
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
Loading repository data...
Reading installed packages...

Program received signal SIGSEGV, Segmentation fault.
solver_solve (solv=0x13d3800, job=0x77f830)
    at /usr/src/debug/satsolver-0.13.0/src/solver.h:304
304     /usr/src/debug/satsolver-0.13.0/src/solver.h: No such file or directory.
        in /usr/src/debug/satsolver-0.13.0/src/solver.h
(gdb) bt
#0  solver_solve (solv=0x13d3800, job=0x77f830)
    at /usr/src/debug/satsolver-0.13.0/src/solver.h:304
#1  0x00007ffff79f4597 in zypp::solver::detail::SATResolver::solving (this=0x77f800,
    requires_caps=@0x77f5b0, conflict_caps=@0x77f5e0)
    at /usr/src/debug/libzypp-5.24.5/zypp/solver/detail/SATResolver.cc:456
#2  0x00007ffff79f8c4a in zypp::solver::detail::SATResolver::resolvePool (this=0x77f800,
    requires_caps=@0x77f5b0, conflict_caps=@0x77f5e0, weakItems=<value optimized out>)
    at /usr/src/debug/libzypp-5.24.5/zypp/solver/detail/SATResolver.cc:726
#3  0x00000000004be80c in resolve(Zypper&) ()
#4  0x000000000043b7cd in Zypper::doCommand() ()
#5  0x0000000000441db8 in Zypper::safeDoCommand() ()
#6  0x0000000000446faa in Zypper::main(int, char**) ()
#7  0x000000000045791c in main ()
(gdb)

Comment 3 Michael Schröder 2009-01-23 14:49:02 UTC

Whoa, a crash in the solver! (Though why zypper needs to run the solver when searching for a package is a mystery to me)

Please do as root:
rm -f /var/log/zypper.log
ZYPP_FULLLOG=1 zypper se zypper

and attach the resulting /var/log/zypper.log file

Also please run
zypper in --debug-solver xxx

and attach a tar of the /var/log/zypper.solverTestCase directory.

Plus, please install valgrind and do
valgrind zypper se zypper

to locate the problem a bit better.

Comment 4 Andreas Vetter 2009-01-23 15:04:03 UTC

With ZYPP_FULLLOG=1 the segfault does not occur, without ZYPP_FULLLOG=1 it segfaults approx. every second try.

wpyc001:~ # ZYPP_FULLLOG=1 zypper se zypper
Loading repository data...
Reading installed packages...

S | Name                  | Summary                                       | Type
--+-----------------------+-----------------------------------------------+--------
i | nagios-plugins-zypper | Nagios plugin for checking software updates   | package
i | zypper                | Command Line Package Management Using Libzypp | package
wpyc001:~ # zypper se zypper
Loading repository data...
Reading installed packages...
Segmentation fault

Comment 5 Andreas Vetter 2009-01-23 15:08:29 UTC

Created attachment 267276 [details]
solverTestCase

wpyc001:~ # zypper in --debug-solver xxx
Loading repository data...
Reading installed packages...
Segmentation fault
wpyc001:~ # rm /var/log/zypper.log; ZYPP_FULLLOG=1 zypper in --debug-solver xxx
Loading repository data...
Reading installed packages...
'xxx' not found.
Resolving package dependencies...
Generating solver test case...
Solver test case generated successfully at /var/log/zypper.solverTestCase.

Comment 6 Andreas Vetter 2009-01-23 15:31:10 UTC

valgrind is killed by the oom-killer, the system has 2 GB RAM. (I disabled swap, since the swap partition is 32GB by accident and valgrind ran for several minutes swapping and swapping.)

wpyc001:~ # valgrind zypper se zypper
==18482== Memcheck, a memory error detector.
==18482== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==18482== Using LibVEX rev 1854, a library for dynamic binary translation.
==18482== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==18482== Using valgrind-3.3.1, a dynamic binary instrumentation framework.
==18482== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==18482== For more details, rerun with: -v
==18482==
Loading repository data...
Reading installed packages...
Killed

Jan 23 16:27:51 wpyc001 kernel: Out of memory: kill process 18220 (bash) score 14680 or a child
Jan 23 16:27:51 wpyc001 kernel: Killed process 18482 (memcheck)

Comment 7 Michael Schröder 2009-01-23 15:52:08 UTC

It segfaults every second try? Hmm, are you sure that your computer's memory is good? Could you please boot memtest and check your memory to rule out a flaky chip?

Comment 8 Andreas Vetter 2009-01-23 15:58:42 UTC

mcelog says ok. and i have that on several machines of the same make. all are autoyast installed. do you really think a memtest helps?

Comment 9 Jan Kupec 2009-01-23 16:00:50 UTC

(In reply to comment #3)
> Whoa, a crash in the solver! (Though why zypper needs to run the solver when
> searching for a package is a mystery to me)

It neeeds the installed status of patches and patterns.

Comment 10 Michael Schröder 2009-01-23 16:01:50 UTC

And could you please also attach /var/log/zypper.log (both without ZYPP_FULLLOG=1 so there will be a segfault and with ZYPP_FULLLOG=1)

Comment 11 Michael Schröder 2009-01-23 16:03:00 UTC

#8: if you see that on multiple machines we can rule out bad memory.

#9: you don't need to run the solver to get that information.

Comment 12 Andreas Vetter 2009-01-23 18:11:10 UTC

(In reply to comment #7)
> It segfaults every second try? 

At the moment it segfaults every try. I cannot give you a zypper.log without ZYPP_FULLLOG=1.

Comment 13 Andreas Vetter 2009-01-23 18:12:38 UTC

Created attachment 267359 [details]
zypper.segfault.log

This is from a segfaulted
zypper se zypper

Comment 14 Andreas Vetter 2009-01-23 18:14:54 UTC

Created attachment 267361 [details]
zypper.ZYPP_FULLLOG=1.log

This is from a working
ZYPP_FULLLOG=1 zypper se zypper

Comment 15 Andreas Vetter 2009-01-26 10:10:31 UTC

Created attachment 267549 [details]
zypper.ZYPP_FULLLOG=1.segfault.log

On another machine (same hardware, same autoyast installation), the ZYPP_FULLLOG=1 variable does not prevent the segfault:

wpyc013:~ # ZYPP_FULLLOG=1  zypper rm logdigest
Loading repository data...
Reading installed packages...
Segmentation fault

Comment 16 Michael Schröder 2009-01-26 11:54:08 UTC

I think I found something: The code contains
"pp = pool->whatprovidesdata + pool_whatprovides(pool, name)"
in some places. This is undefined behaviour, as pool_whatprovides()
may change pool->whatprovidesdata. So we need to do it in two steps:

off = pool_whatprovides(pool, name);
pp = pool->whatprovidesdata + off;

Comment 17 Michael Schröder 2009-01-26 13:04:28 UTC

(hopefully) fixed in satsolver-0.13.1.

It should show up in
http://download.opensuse.org/repositories/zypp:/Head/openSUSE_11.1/repodata/

in a couple of minutes. Note that you need to update libzypp as well, as it is statically linked against the sat solver.

Unfortunately we just missed the current update stack maintenance update, so the fix will be out with the next one.

Comment 18 Andreas Vetter 2009-01-26 19:06:41 UTC

Hmm, somehow the addition of the new repo repaired it. In detail:
I added the repo 
http://download.opensuse.org/repositories/zypp:Head/openSUSE_11.1 .
I did a zypper up, which worked (no need for ZYPP_FULLLOG=1 !),
this installed the patches from update and brought the packages 
perl-satsolver python-satsolver ruby-satsolver to the version from the 
zypp:Head repo.
libzypp and satsolver-tools were not updated, but
zypper se zypper works now.

Here is what I did:
wpyc001:~ # zypper ar http://download.opensuse.org/repositories/zypp:/Head/openSUSE_11.1 zypphead
Adding repository 'zypphead' [done]
Repository 'zypphead' successfully added
Enabled: Yes
Autorefresh: No
URI: http://download.opensuse.org/repositories/zypp:/Head/openSUSE_11.1

wpyc001:~ # zypper ref
Repository 'openSUSE-NonOSS-Add-on 11.1-0' is up to date.
Repository 'openSUSE 11.1-0' is up to date.
Repository 'openSUSE 11.1-0' is up to date.
Repository 'Main Update Repository' is up to date.
Repository 'update' is up to date.
New repository or package signing key received:
Key ID: 33D38EBC7FB7F464
Key Name: zypp OBS Project <zypp@build.opensuse.org>
Key Fingerprint: 47D7CE1DD600935B3B90365733D38EBC7FB7F464
Repository: zypphead

Do you want to reject the key, trust temporarily, or trust always? [R/t/a/?]: t
Retrieving repository 'zypphead' metadata [done]
Building repository 'zypphead' cache [done]
All repositories have been refreshed.
wpyc001:~ # zypper up
Loading repository data...
Reading installed packages...

The following packages are going to be upgraded:
  attr gnome-main-menu libattr libattr-32bit libattr-devel perl-satsolver plotutils
python-satsolver release-notes-openSUSE ruby-satsolver


The following packages are going to change vendor:
  perl-satsolver python-satsolver ruby-satsolver


Overall download size: 7.1 M. After the operation, additional 7.2 M will be used.
Continue? [YES/no]:
Retrieving package ruby-satsolver-0.13.1-1.1.x86_64 (1/10), 447.0 K (1.5 M unpacked)
Retrieving: ruby-satsolver-0.13.1-1.1.x86_64.rpm [done]
Installing: ruby-satsolver-0.13.1-1.1 [done]
Retrieving package python-satsolver-0.13.1-1.1.x86_64 (2/10), 1.8 M (6.6 M unpacked)
Retrieving: python-satsolver-0.13.1-1.1.x86_64.rpm [done]
Installing: python-satsolver-0.13.1-1.1 [done]
Retrieving package perl-satsolver-0.13.1-1.1.x86_64 (3/10), 552.0 K (2.0 M unpacked)
Retrieving: perl-satsolver-0.13.1-1.1.x86_64.rpm [done]
Installing: perl-satsolver-0.13.1-1.1 [done]
Retrieving package libattr-32bit-2.4.43-2.1.1.x86_64 (4/10), 11.0 K (18.0 K unpacked)
Retrieving delta: ./rpm/x86_64/libattr-32bit-2.4.39_2.4.43-67.5_2.1.1.x86_64.delta.rpm, 5.0 K
Retrieving: libattr-32bit-2.4.39_2.4.43-67.5_2.1.1.x86_64.delta.rpm [done]
Applying delta: ./libattr-32bit-2.4.39_2.4.43-67.5_2.1.1.x86_64.delta.rpm [done]
Installing: libattr-32bit-2.4.43-2.1.1 [done]
Retrieving package libattr-2.4.43-2.1.1.x86_64 (5/10), 12.0 K (20.0 K unpacked)
Retrieving delta: ./rpm/x86_64/libattr-2.4.39_2.4.43-67.11_2.1.1.x86_64.delta.rpm, 6.0 K
Retrieving: libattr-2.4.39_2.4.43-67.11_2.1.1.x86_64.delta.rpm [done]
Applying delta: ./libattr-2.4.39_2.4.43-67.11_2.1.1.x86_64.delta.rpm [done]
Installing: libattr-2.4.43-2.1.1 [done]
Retrieving package plotutils-2.5-197.10.1.x86_64 (6/10), 3.9 M (28.0 M unpacked)
Retrieving delta: ./rpm/x86_64/plotutils-2.5-197.8_197.10.1.x86_64.delta.rpm, 21.0 K
Retrieving: plotutils-2.5-197.8_197.10.1.x86_64.delta.rpm [done]
Applying delta: ./plotutils-2.5-197.8_197.10.1.x86_64.delta.rpm [done]
Installing: plotutils-2.5-197.10.1 [done]
Retrieving package gnome-main-menu-0.9.11-22.9.1.x86_64 (7/10), 185.0 K (727.0 K unpacked)
Retrieving delta: ./rpm/x86_64/gnome-main-menu-0.9.11-22.6_22.9.1.x86_64.delta.rpm, 41.0 K
Retrieving: gnome-main-menu-0.9.11-22.6_22.9.1.x86_64.delta.rpm [done]
Applying delta: ./gnome-main-menu-0.9.11-22.6_22.9.1.x86_64.delta.rpm [done]
Installing: gnome-main-menu-0.9.11-22.9.1 [done]
Retrieving package release-notes-openSUSE-11.1.9-1.1.1.noarch (8/10), 64.0 K (327.0 K unpacked)
Retrieving delta: ./rpm/noarch/release-notes-openSUSE-11.1.7_11.1.9-1.7_1.1.1.noarch.delta.rpm, 49.0 K
Retrieving: release-notes-openSUSE-11.1.7_11.1.9-1.7_1.1.1.noarch.delta.rpm [24% (11.8 K/sRetrieving: release-notes-openSUSE-11.1.7_11.1.9-1.7_1.1.1.noarch.delta.rpm [done]
Applying delta: ./release-notes-openSUSE-11.1.7_11.1.9-1.7_1.1.1.noarch.delta.rpm [done]
Installing: release-notes-openSUSE-11.1.9-1.1.1 [done]
Retrieving package libattr-devel-2.4.43-2.1.1.x86_64 (9/10), 36.0 K (110.0 K unpacked)
Retrieving delta: ./rpm/x86_64/libattr-devel-2.4.39_2.4.43-67.11_2.1.1.x86_64.delta.rpm, 10.0 K
Retrieving: libattr-devel-2.4.39_2.4.43-67.11_2.1.1.x86_64.delta.rpm [done]
Applying delta: ./libattr-devel-2.4.39_2.4.43-67.11_2.1.1.x86_64.delta.rpm [done]
Installing: libattr-devel-2.4.43-2.1.1 [done]
Retrieving package attr-2.4.43-2.1.1.x86_64 (10/10), 52.0 K (149.0 K unpacked)
Retrieving delta: ./rpm/x86_64/attr-2.4.39_2.4.43-67.11_2.1.1.x86_64.delta.rpm, 17.0 K
Retrieving: attr-2.4.39_2.4.43-67.11_2.1.1.x86_64.delta.rpm [done]
Applying delta: ./attr-2.4.39_2.4.43-67.11_2.1.1.x86_64.delta.rpm [done]
Installing: attr-2.4.43-2.1.1 [done]
wpyc001:~ # rpm -q satsolver-tools
satsolver-tools-0.13.0-3.3
wpyc001:~ # zypper up satsolver-tools
Retrieving repository 'Main Update Repository' metadata [done]
Building repository 'Main Update Repository' cache [done]
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: libzypp-5.24.5-1.1.x86_64 requires satsolver-tools = 0.13.0, but this requirement cannot be provided
 Solution 1: Following actions will be done:
  deinstallation of yast2-qt-pkg-2.17.25-1.1.x86_64
  deinstallation of yast2-gtk-2.17.8-1.5.x86_64
  deinstallation of yast2-ncurses-pkg-2.17.10-1.20.x86_64
  deinstallation of yast2-pkg-bindings-2.17.29-1.7.x86_64
  deinstallation of libzypp-testsuite-tools-4.2.6-6.7.x86_64
  deinstallation of yast2-online-update-2.17.10-1.37.noarch
  deinstallation of yast2-2.17.54-1.1.x86_64
  deinstallation of yast2-bootloader-2.17.44-1.1.x86_64
  deinstallation of yast2-country-2.17.29-1.6.x86_64
  deinstallation of yast2-packager-2.17.50-1.4.x86_64
  deinstallation of libzypp-testsuite-tools-data-4.2.6-6.7.x86_64
  deinstallation of yast2-registration-2.17.17-1.1.noarch
  deinstallation of yast2-product-creator-2.17.13-1.20.noarch
  deinstallation of yast2-pkg-bindings-devel-doc-2.17.29-1.9.noarch
  deinstallation of gnome-applets-2.24.1-2.21.x86_64
  deinstallation of autoyast2-installation-2.17.23-1.6.noarch
  deinstallation of autoyast2-2.17.23-1.6.noarch
  deinstallation of yast2-add-on-2.17.11-1.22.noarch
  deinstallation of yast2-dirinstall-2.17.2-1.15.noarch
  deinstallation of yast2-metapackage-handler-0.8.7-1.72.noarch
  deinstallation of yast2-iscsi-client-2.17.5-1.2.noarch
  deinstallation of yast2-installation-2.17.43-1.2.noarch
  deinstallation of yast2-inetd-2.17.3-1.4.noarch
  deinstallation of yast2-update-2.17.14-1.5.x86_64
  deinstallation of yast2-registration-branding-openSUSE-2.17.17-1.1.noarch
  deinstallation of yast2-add-on-creator-2.17.8-2.1.noarch
  deinstallation of yast2-apparmor-2.17.4-1.5.noarch
  deinstallation of yast2-autofs-2.15.4-14.122.noarch
  deinstallation of yast2-backup-2.17.3-1.1.noarch
  deinstallation of yast2-ca-management-2.17.6-1.13.noarch
  deinstallation of yast2-dhcp-server-2.17.2-1.33.noarch
  deinstallation of yast2-dns-server-2.17.9-1.22.noarch
  deinstallation of yast2-drbd-2.13.1-215.21.noarch
  deinstallation of yast2-firewall-2.17.6-1.1.noarch
  deinstallation of yast2-firstboot-2.17.4-1.64.noarch
  deinstallation of yast2-ftp-server-2.17.3-1.19.noarch
  deinstallation of yast2-http-server-2.17.5-1.20.noarch
  deinstallation of yast2-instserver-2.17.3-1.43.noarch
  deinstallation of yast2-irda-2.17.2-1.43.noarch
  deinstallation of yast2-iscsi-server-2.17.3-1.25.noarch
  deinstallation of yast2-isns-1.0.4-1.210.noarch
  deinstallation of yast2-kerberos-client-2.17.5-1.31.noarch
  deinstallation of yast2-ldap-client-2.17.16-1.33.noarch
  deinstallation of yast2-live-installer-2.17.2-1.21.noarch
  deinstallation of yast2-mail-2.17.1-1.19.noarch
  deinstallation of yast2-multipath-2.17.1-3.15.noarch
  deinstallation of yast2-nfs-client-2.17.9-1.15.noarch
  deinstallation of yast2-nfs-server-2.17.4-1.19.noarch
  deinstallation of yast2-nis-server-2.17.2-1.77.noarch
  deinstallation of yast2-ntp-client-2.17.7-1.28.noarch
  deinstallation of yast2-pam-2.17.1-1.25.noarch
  deinstallation of yast2-phone-services-2.16.0-19.117.noarch
  deinstallation of yast2-repair-2.17.7-1.29.noarch
  deinstallation of yast2-restore-2.16.2-19.123.noarch
  deinstallation of yast2-runlevel-2.17.4-1.33.noarch
  deinstallation of yast2-samba-client-2.17.11-1.30.noarch
  deinstallation of yast2-samba-server-2.17.6-1.2.noarch
  deinstallation of yast2-security-2.17.12-1.9.noarch
  deinstallation of yast2-slp-server-2.17.1-1.60.noarch
  deinstallation of yast2-sudo-2.17.2-1.2.noarch
  deinstallation of yast2-sysconfig-2.17.0-1.145.noarch
  deinstallation of yast2-tftp-server-2.17.1-1.28.noarch
  deinstallation of yast2-tv-2.17.2-1.56.noarch
  deinstallation of yast2-x11-2.17.10-1.9.noarch
  deinstallation of yast2-control-center-2.17.3-1.8.x86_64
  deinstallation of yast2-fingerprint-reader-2.17.6-1.42.x86_64
  deinstallation of yast2-kdump-2.17.14-1.6.x86_64
  deinstallation of yast2-ldap-2.17.3-1.66.x86_64
  deinstallation of yast2-ldap-server-2.17.17-1.1.x86_64
  deinstallation of yast2-mouse-2.16.1-19.119.x86_64
  deinstallation of yast2-network-2.17.60-1.4.x86_64
  deinstallation of yast2-nis-client-2.17.7-1.15.x86_64
  deinstallation of yast2-printer-2.17.48-2.5.x86_64
  deinstallation of yast2-profile-manager-2.17.1-1.99.x86_64
  deinstallation of yast2-scanner-2.17.5-2.1.x86_64
  deinstallation of yast2-sound-2.17.13-1.1.x86_64
  deinstallation of yast2-squid-2.17.5-1.7.x86_64
  deinstallation of yast2-storage-2.17.61-2.1.x86_64
  deinstallation of yast2-tune-2.17.6-1.42.x86_64
  deinstallation of yast2-users-2.17.27-1.2.x86_64
  deinstallation of yast2-vm-2.16.8-1.17.x86_64
  deinstallation of yast2-audit-laf-2.17.7-1.21.noarch
  deinstallation of yast2-casa-ats-1.7.1575-1.25.noarch
  deinstallation of yast2-kerberos-server-2.17.5-1.2.noarch
  deinstallation of yast2-power-management-2.17.6-1.11.noarch
  deinstallation of yast2-reipl-2.17.2-1.36.noarch
  deinstallation of yast2-sshd-2.16.2-17.125.noarch
  deinstallation of yast2-support-2.17.18-1.11.noarch
  deinstallation of yast2-system-profile-2.17.2-1.59.noarch
  deinstallation of yast2-wagon-2.17.6-1.7.noarch
  deinstallation of yast2-CASA-1.7.1535-1.101.x86_64
  deinstallation of yast2-devel-doc-2.17.54-1.1.x86_64
  deinstallation of yast2-s390-2.15.1-2.41.x86_64
  deinstallation of yast2-update-FACTORY-2.17.14-1.5.x86_64
  deinstallation of yast2-online-update-frontend-2.17.10-1.37.noarch
  deinstallation of gscpm-0.1-216.158.x86_64
  deinstallation of kscpm-0.5.4-143.25.x86_64
  deinstallation of yast2-inetd-doc-2.17.3-1.4.noarch
  deinstallation of yast2-installation-devel-doc-2.17.43-1.2.noarch
  deinstallation of yast2-control-center-gnome-2.13.3-75.17.x86_64
  deinstallation of yast2-control-center-qt-2.17.3-1.8.x86_64
  deinstallation of yast2-mcs-plugin-0.1.0-55.101.x86_64
  deinstallation of yast2-nis-server-devel-doc-2.17.2-1.77.noarch
  deinstallation of yast2-storage-devel-2.17.61-2.1.x86_64
  deinstallation of xfce4-panel-plugin-xfapplet-0.1.0-1.13.x86_64
  deinstallation of gnome-applets-invest-2.24.1-2.21.x86_64
  deinstallation of gnome-applets-lang-2.24.1-2.21.x86_64
  deinstallation of gscpm-lang-0.1-216.158.x86_64
 Solution 2: do not ask to install a solvable providing satsolver-tools > 0.13.0-3.3
 Solution 3: Ignore some dependencies of libzypp

Choose from above solutions by number or cancel [1/2/3/C]: c
wpyc001:~ # zypper up satsolver-tools libzypp
Loading repository data...
Reading installed packages...
Resolving package dependencies...
2 Problems:
Problem: libzypp-5.24.5-1.1.x86_64 requires satsolver-tools = 0.13.0, but this requirement cannot be provided
Problem: yast2-pkg-bindings-2.17.29-1.7.x86_64 requires libzypp.so.523()(64bit), but this requirement cannot be provided

Problem: libzypp-5.24.5-1.1.x86_64 requires satsolver-tools = 0.13.0, but this requirement cannot be provided
 Solution 1: Following actions will be done:
  deinstallation of yast2-qt-pkg-2.17.25-1.1.x86_64
  deinstallation of yast2-gtk-2.17.8-1.5.x86_64
  deinstallation of yast2-ncurses-pkg-2.17.10-1.20.x86_64
  deinstallation of libzypp-testsuite-tools-4.2.6-6.7.x86_64
  deinstallation of yast2-online-update-2.17.10-1.37.noarch
  deinstallation of yast2-2.17.54-1.1.x86_64
  deinstallation of yast2-bootloader-2.17.44-1.1.x86_64
  deinstallation of yast2-country-2.17.29-1.6.x86_64
  deinstallation of yast2-packager-2.17.50-1.4.x86_64
  deinstallation of libzypp-testsuite-tools-data-4.2.6-6.7.x86_64
  deinstallation of yast2-registration-2.17.17-1.1.noarch
  deinstallation of yast2-product-creator-2.17.13-1.20.noarch
  deinstallation of yast2-pkg-bindings-devel-doc-2.17.29-1.9.noarch
  deinstallation of gnome-applets-2.24.1-2.21.x86_64
  deinstallation of autoyast2-installation-2.17.23-1.6.noarch
  deinstallation of autoyast2-2.17.23-1.6.noarch
  deinstallation of yast2-add-on-2.17.11-1.22.noarch
  deinstallation of yast2-dirinstall-2.17.2-1.15.noarch
  deinstallation of yast2-metapackage-handler-0.8.7-1.72.noarch
  deinstallation of yast2-iscsi-client-2.17.5-1.2.noarch
  deinstallation of yast2-installation-2.17.43-1.2.noarch
  deinstallation of yast2-inetd-2.17.3-1.4.noarch
  deinstallation of yast2-update-2.17.14-1.5.x86_64
  deinstallation of yast2-registration-branding-openSUSE-2.17.17-1.1.noarch
  deinstallation of yast2-add-on-creator-2.17.8-2.1.noarch
  deinstallation of yast2-apparmor-2.17.4-1.5.noarch
  deinstallation of yast2-autofs-2.15.4-14.122.noarch
  deinstallation of yast2-backup-2.17.3-1.1.noarch
  deinstallation of yast2-ca-management-2.17.6-1.13.noarch
  deinstallation of yast2-dhcp-server-2.17.2-1.33.noarch
  deinstallation of yast2-dns-server-2.17.9-1.22.noarch
  deinstallation of yast2-drbd-2.13.1-215.21.noarch
  deinstallation of yast2-firewall-2.17.6-1.1.noarch
  deinstallation of yast2-firstboot-2.17.4-1.64.noarch
  deinstallation of yast2-ftp-server-2.17.3-1.19.noarch
  deinstallation of yast2-http-server-2.17.5-1.20.noarch
  deinstallation of yast2-instserver-2.17.3-1.43.noarch
  deinstallation of yast2-irda-2.17.2-1.43.noarch
  deinstallation of yast2-iscsi-server-2.17.3-1.25.noarch
  deinstallation of yast2-isns-1.0.4-1.210.noarch
  deinstallation of yast2-kerberos-client-2.17.5-1.31.noarch
  deinstallation of yast2-ldap-client-2.17.16-1.33.noarch
  deinstallation of yast2-live-installer-2.17.2-1.21.noarch
  deinstallation of yast2-mail-2.17.1-1.19.noarch
  deinstallation of yast2-multipath-2.17.1-3.15.noarch
  deinstallation of yast2-nfs-client-2.17.9-1.15.noarch
  deinstallation of yast2-nfs-server-2.17.4-1.19.noarch
  deinstallation of yast2-nis-server-2.17.2-1.77.noarch
  deinstallation of yast2-ntp-client-2.17.7-1.28.noarch
  deinstallation of yast2-pam-2.17.1-1.25.noarch
  deinstallation of yast2-phone-services-2.16.0-19.117.noarch
  deinstallation of yast2-repair-2.17.7-1.29.noarch
  deinstallation of yast2-restore-2.16.2-19.123.noarch
  deinstallation of yast2-runlevel-2.17.4-1.33.noarch
  deinstallation of yast2-samba-client-2.17.11-1.30.noarch
  deinstallation of yast2-samba-server-2.17.6-1.2.noarch
  deinstallation of yast2-security-2.17.12-1.9.noarch
  deinstallation of yast2-slp-server-2.17.1-1.60.noarch
  deinstallation of yast2-sudo-2.17.2-1.2.noarch
  deinstallation of yast2-sysconfig-2.17.0-1.145.noarch
  deinstallation of yast2-tftp-server-2.17.1-1.28.noarch
  deinstallation of yast2-tv-2.17.2-1.56.noarch
  deinstallation of yast2-x11-2.17.10-1.9.noarch
  deinstallation of yast2-control-center-2.17.3-1.8.x86_64
  deinstallation of yast2-fingerprint-reader-2.17.6-1.42.x86_64
  deinstallation of yast2-kdump-2.17.14-1.6.x86_64
  deinstallation of yast2-ldap-2.17.3-1.66.x86_64
  deinstallation of yast2-ldap-server-2.17.17-1.1.x86_64
  deinstallation of yast2-mouse-2.16.1-19.119.x86_64
  deinstallation of yast2-network-2.17.60-1.4.x86_64
  deinstallation of yast2-nis-client-2.17.7-1.15.x86_64
  deinstallation of yast2-printer-2.17.48-2.5.x86_64
  deinstallation of yast2-profile-manager-2.17.1-1.99.x86_64
  deinstallation of yast2-scanner-2.17.5-2.1.x86_64
  deinstallation of yast2-sound-2.17.13-1.1.x86_64
  deinstallation of yast2-squid-2.17.5-1.7.x86_64
  deinstallation of yast2-storage-2.17.61-2.1.x86_64
  deinstallation of yast2-tune-2.17.6-1.42.x86_64
  deinstallation of yast2-users-2.17.27-1.2.x86_64
  deinstallation of yast2-vm-2.16.8-1.17.x86_64
  deinstallation of yast2-audit-laf-2.17.7-1.21.noarch
  deinstallation of yast2-casa-ats-1.7.1575-1.25.noarch
  deinstallation of yast2-kerberos-server-2.17.5-1.2.noarch
  deinstallation of yast2-power-management-2.17.6-1.11.noarch
  deinstallation of yast2-reipl-2.17.2-1.36.noarch
  deinstallation of yast2-sshd-2.16.2-17.125.noarch
  deinstallation of yast2-support-2.17.18-1.11.noarch
  deinstallation of yast2-system-profile-2.17.2-1.59.noarch
  deinstallation of yast2-wagon-2.17.6-1.7.noarch
  deinstallation of yast2-CASA-1.7.1535-1.101.x86_64
  deinstallation of yast2-devel-doc-2.17.54-1.1.x86_64
  deinstallation of yast2-s390-2.15.1-2.41.x86_64
  deinstallation of yast2-update-FACTORY-2.17.14-1.5.x86_64
  deinstallation of yast2-online-update-frontend-2.17.10-1.37.noarch
  deinstallation of gscpm-0.1-216.158.x86_64
  deinstallation of kscpm-0.5.4-143.25.x86_64
  deinstallation of yast2-inetd-doc-2.17.3-1.4.noarch
  deinstallation of yast2-installation-devel-doc-2.17.43-1.2.noarch
  deinstallation of yast2-control-center-gnome-2.13.3-75.17.x86_64
  deinstallation of yast2-control-center-qt-2.17.3-1.8.x86_64
  deinstallation of yast2-mcs-plugin-0.1.0-55.101.x86_64
  deinstallation of yast2-nis-server-devel-doc-2.17.2-1.77.noarch
  deinstallation of yast2-storage-devel-2.17.61-2.1.x86_64
  deinstallation of xfce4-panel-plugin-xfapplet-0.1.0-1.13.x86_64
  deinstallation of gnome-applets-invest-2.24.1-2.21.x86_64
  deinstallation of gnome-applets-lang-2.24.1-2.21.x86_64
  deinstallation of gscpm-lang-0.1-216.158.x86_64
 Solution 2: do not ask to install a solvable providing satsolver-tools > 0.13.0-3.3
 Solution 3: Ignore some dependencies of libzypp

Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/C]: c
wpyc001:~ # zypper se zypper
Loading repository data...
Reading installed packages...

S | Name                  | Summary                                           | Type
--+-----------------------+---------------------------------------------------+-----------
i | nagios-plugins-zypper | Nagios plugin for checking software updates       | package
i | zypper                | Command line package management tool using libz-> | package
  | zypper                | Command line package management tool using libz-> | srcpackage
wpyc001:~ # zypper se zypper
Loading repository data...
Reading installed packages...

S | Name                  | Summary                                           | Type
--+-----------------------+---------------------------------------------------+-----------
i | nagios-plugins-zypper | Nagios plugin for checking software updates       | package
i | zypper                | Command line package management tool using libz-> | package
  | zypper                | Command line package management tool using libz-> | srcpackage
wpyc001:~ # rpm -q libzypp
libzypp-5.24.5-1.1

Comment 19 Andreas Vetter 2009-01-26 19:22:58 UTC

Created attachment 267745 [details]
zypper.normal.log

On another machine, where I did not change any package, it suddenly works.

I think you fixed another bug ;-)

Can this be a problem with NFS locking? All our repos are on NFS (SLES10 SP2). 

We already saw problems with NFS locking: 
a kwrite process was hanging in the kernel lockd, unkillable, and the kernel complained: NFS server not responding. Some machines freeze without any hint, what happened. I also suspect NFS problems in that case.

So my suspicion is: There might be a problem when the repo does not work properly.