kdelibs update failure
List, I have run into a problem installing one of the latest KDE rpms. When trying to update kdelibs3-3.5.1-15 from kdelibs3-3.5.0-31, Yast fails with: 'ERROR(InstTarget:E_RpmDB_subprocess_failed)'. If I download and try the same rpm with 'rpm -Uvv', it fails with a seg fault. Here is the end of the output: <snip> D: ========== tsorting packages (order, #predecessors, #succesors, tree, depth) D: 0 0 1 0 0 +kdelibs3-3.5.1-15 D: ========== successors only (15957491 bytes) D: 1 1 0 0 1 -kdelibs3-3.5.0-31 D: installing binary packages D: closed db index /var/lib/rpm/Pubkeys D: closed db index /var/lib/rpm/Providename D: closed db index /var/lib/rpm/Requirename D: closed db index /var/lib/rpm/Basenames D: closed db index /var/lib/rpm/Packages D: closed db environment /var/lib/rpm/Packages D: shared posix mutexes found(0), anyway adding DB_PRIVATE, using fcntl lock D: opening db environment /var/lib/rpm/Packages create:cdb:mpool:private D: opening db index /var/lib/rpm/Packages create mode=0x42 D: locked db index /var/lib/rpm/Packages D: mounted filesystems: D: i dev bsize bavail iavail mount point D: 0 0x0344 4096 6564454 -1 / D: 1 0x0003 4096 0 -1 /proc D: 2 0x0000 4096 0 -1 /sys D: 3 0x000f 4096 64469 64470 /dev/shm D: 4 0x000a 4096 0 -1 /dev/pts D: 5 0x0301 4096 5130594 2045 /windows/C D: 6 0x0341 16384 1060264 -1 /windows/D D: 7 0x0305 4096 485587 -1 /windows/E D: 8 0x0010 4096 0 -1 /proc/bus/usb D: sanity checking 2 elements D: opening db index /var/lib/rpm/Name create:nofsync mode=0x42 D: read h# 1364 Header SHA1 digest: OK (235d6272d7db640a523fba109c73d17c905119ba) D: computing 7271 file fingerprints D: opening db index /var/lib/rpm/Basenames create:nofsync mode=0x42 D: opening db index /var/lib/rpm/Group create:nofsync mode=0x42 D: opening db index /var/lib/rpm/Requirename create:nofsync mode=0x42 D: opening db index /var/lib/rpm/Providename create:nofsync mode=0x42 D: opening db index /var/lib/rpm/Conflictname create:nofsync mode=0x42 D: opening db index /var/lib/rpm/Triggername create:nofsync mode=0x42 D: opening db index /var/lib/rpm/Dirnames create:nofsync mode=0x42 D: opening db index /var/lib/rpm/Requireversion create:nofsync mode=0x42 D: opening db index /var/lib/rpm/Provideversion create:nofsync mode=0x42 D: opening db index /var/lib/rpm/Installtid create:nofsync mode=0x42 D: opening db index /var/lib/rpm/Sigmd5 create:nofsync mode=0x42 D: opening db index /var/lib/rpm/Sha1header create:nofsync mode=0x42 D: opening db index /var/lib/rpm/Filemd5s create:nofsync mode=0x42 D: opening db index /var/lib/rpm/Pubkeys create:nofsync mode=0x42 Preparing packages for installation... D: computing file dispositions D: read h# 303 Header SHA1 digest: OK (eba8317e6056bdf12077e0d398d45afd0da4da60) D: read h# 346 Header SHA1 digest: OK (4a70dca751b598610fe62d695d5900174a9f24f9) D: read h# 381 Header SHA1 digest: OK (21e269097fea5ffd798d9b988d0f58c6834ab83d) D: read h# 508 Header SHA1 digest: OK (cef430b2bc7464b802fa4643fd48b9253d3b7aea) D: read h# 534 Header SHA1 digest: OK (2217507fc2839ab6dabc9a7d9d4c323151a84cff) D: read h# 555 Header SHA1 digest: OK (25bd377ad49025231ab10d898062a426bb03bbcf) D: read h# 572 Header SHA1 digest: OK (38a1135a08ba1bb3c5450f46f4c04c08351e0365) D: read h# 622 Header SHA1 digest: OK (7f0721f180e3dbacc6f99754f43568669d2f251d) D: read h# 634 Header SHA1 digest: OK (c75d973764b34a9bbff948dfdf77389dadfca654) D: read h# 744 Header sanity check: OK D: read h# 830 Header SHA1 digest: OK (9378ac2da125d4e58f07c9f193c4e230b097692a) D: read h# 925 Header SHA1 digest: OK (32fa1da339b9d8592c1063f8ebf9803b4907d8a4) D: read h# 1026 Header SHA1 digest: OK (eaccf3cdb1d56af8ceb473b7d07d41b75f6624f1) D: read h# 1074 Header SHA1 digest: OK (ee74b4f017a01ddf3bb9f484be440887d85f3494) D: read h# 1126 Header SHA1 digest: OK (ed91443c701b14c45c0267633f1d97c79f7beb27) D: read h# 1169 Header SHA1 digest: OK (5c4082d0742ea5725677b80e131eb6685b782194) D: read h# 1172 Header SHA1 digest: OK (7a93a507d523f54f3bfe411028201405e33eccd5) D: read h# 1233 Header SHA1 digest: OK (d1af538fe8e5b775961c38991fb1e2fa171b56a2) D: read h# 1244 Header V3 DSA signature: NOKEY, key ID 27db6f5b D: read h# 1246 Header SHA1 digest: OK (bd1a78499f2825885a89b6718994d6f98e5fc7c5) D: read h# 1250 Header SHA1 digest: OK (ced1a01c2550eaa7ddbe8822dab4278fed7d04f6) D: read h# 1270 Header SHA1 digest: OK (179134bbf4cad8ef0b121e8229b3c59bf38e5e21) D: read h# 1272 Header SHA1 digest: OK (6db4f8b7d2df59020d4581de5dd18d28a88d9205) D: read h# 1373 Header SHA1 digest: OK (06d4aa660849da4edc516cca8333bd10d1ac4350) D: read h# 1385 Header SHA1 digest: OK (085a66433c262c3a89ccea7aa7b403afafad0f0c) D: read h# 1388 Header SHA1 digest: OK (2b27c064dcca6b8852bd3354d2b23ca355b3f09c) D: read h# 1391 Header SHA1 digest: OK (b3722eea781bc428cb8df12d9806bbc1cd6de084) D: read h# 1392 Header SHA1 digest: OK (212cb183728392c8e3a77922115ff38f2eef2311) D: read h# 1393 Header SHA1 digest: OK (7c3bb587adcc23a741d05264b10fe34fbdd578c8) D: read h# 1394 Header SHA1 digest: OK (d854e87ff7d8515a7c0931f4c80f41ce0f9cdff2) D: read h# 1401 Header SHA1 digest: OK (9f3731600e0b912110b19b36d9d759863c4b8e01) D: read h# 1403 Header SHA1 digest: OK (0f86caeacd643d911c2b77ac9ab3e7ea98e54401) D: read h# 1429 Header SHA1 digest: OK (75f5ffad67eb74322a18a581950204e183f7315b) D: read h# 1447 Header V3 DSA signature: NOKEY, key ID 1be4d89e D: read h# 1465 Header SHA1 digest: OK (a596d7a8383284d0423b0d6d134870cdf5123e69) D: read h# 1469 Header V3 DSA signature: NOKEY, key ID cd3140cd D: read h# 1620 Header V3 DSA signature: NOKEY, key ID 27db6f5b D: read h# 1654 Header SHA1 digest: OK (5191ab26d5d94b32eca5a50b31a8fb960226631a) D: read h# 1670 Header SHA1 digest: OK (59efb14285ef95d41d7152f9e9c0673718e51c0c) D: read h# 1671 Header SHA1 digest: OK (37cab0044b77321a1f46183813e8e2304f7ab1cb) Segmentation fault I am running SuSE 10.0 with the latest x.org updates (6.9) Thanks for any help, Brian Mazari
Brian Mazari wrote:
Segmentation fault
I am running SuSE 10.0 with the latest x.org updates (6.9)
Thanks for any help,
The first thing to try when this happens, which works in most cases that I've seen, is to run rpm --rebuilddb It seems rpm isn't very fault tolerant, and can easily crash when it encounters bad data in the database If this doesn't work then we'll have to dig deeper, but try this first
Anders Johansson wrote:
The first thing to try when this happens, which works in most cases that I've seen, is to run
rpm --rebuilddb
It seems rpm isn't very fault tolerant, and can easily crash when it encounters bad data in the database
Worked like a charm. I'll have to write this one down! Thanks Anders! Thanks, Brian Mazari
participants (2)
-
Anders Johansson
-
Brian Mazari