Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 105350 - emerge crashes: segmentation fault
Summary: emerge crashes: segmentation fault
Status: RESOLVED DUPLICATE of bug 20600
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High blocker (vote)
Assignee: Gentoo Linux bug wranglers
Depends on:
Reported: 2005-09-09 01:55 UTC by Borja Pacheco
Modified: 2005-09-09 05:59 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Borja Pacheco 2005-09-09 01:55:34 UTC
I'll describe facts, although I don't find any direct relation among them

1. Since yesterday, my system was updating itself with the masked version of
gnome 2.12 (I use to do this) -> [emerge gnome]
2. My update failed, because one packet of gnome didn't compile properly
(nothing extrange at all)
3. Before, analyzing the fail and trying to keep on the update. I decided to
sync portage tree -> [emerge --sync]
This update was ok, and the system commited me to update portage because there
was a newest release.
4. Then, I tryed to execute the update [emerge --update world], and I started to
see exception about some gnome packets. The message something like this (auxdb
exception: [/usr/portage::xxx]: "Corruption detected when reading key 'xxxx':
Key count mistmat")
5. My system reached a load near 8, and I had to shutdown it (it didn't response
to any event, nor power-button)
6. After this, the BIOS warms me with a prefail disk (SMART)
7. I executed smartctl and it informs me about a possible future fail into disk.
8. My system starts ok (repairing filesystems...), and I try to execute emerge
--sync in order to reapir portage tree. It didn't work and again it becomes
hanged-up, when updating portage cache (at 52%).
9. Once booted again, I try to execute emerge --metadata and here it's the

# emerge --metadata
skipping sync

>>> Updating Portage cache:   52%auxdb exception: [/usr/portage::kde-base/kstars
-3.4.1]: "Corruption detected when reading key 'kstars-3.4.1': Key count mistmat ch"
Segmentation fault

Current status:
a) gnome is broken, not too bad.
b) worst thing, emerge does not work!

Any suggestion?

Reproducible: Always
Steps to Reproduce:
1. execute 
emerge --sync or emerge package-name

Actual Results:  
segmentation fault, some pyhton errors or just huge load into the system

emerge --info, does not work. Again load tends to infinite
Comment 1 SpanKY gentoo-dev 2005-09-09 05:54:52 UTC
6. After this, the BIOS warms me with a prefail disk (SMART)

you should most def NOT ignore that warning ... grab another hard drive and
start backing up your data because that drive is going to die soon
Comment 2 Jakub Moc (RETIRED) gentoo-dev 2005-09-09 05:59:04 UTC
Sorry, we cannot fix hardware problems.

*** This bug has been marked as a duplicate of 20600 ***