Description of problem: Fedora 8 is unusable. Xorg exits immediately after start (no EE in log however). And when I tried to update it with yum, rpm said 'fatal error, run db rebuild' or something like that. I don't want to here anything about hardware problems - I don't have them. My system is rock stable. Great job, guys! Continue doing such things and your project will die. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Flaming isn't the best way to get people to look at your problems you know. Try this as the first step: http://wiki.rpm.org/Docs/RpmRecovery
Yes, rpm --rebuilddb helped. rpm now shows installed packages properly. I will try to update now. I just don't understand why this problem appeared in the first place. Did the installer do something wrong, I went to forum to ask about Xorg problem and found HUGE amount of threads about Fedora 8 problems. Perhaps you, guys, were to hurry to release. Obviously much more testing was needed.
Was this a fresh installation of F8 or upgrade from some earlier version (F7, F8-test-something, rawhide...) and what kind of system is it (architecture etc)?
This is fresh installation. My system: ASUS P5B Plus Vista Edition motherboard Core 2 Duo E6600 2.4 GHz 2GB ram 800MHz Dual NVIDIA GeForce 8800 GTX Creative Audigy 4 I installed i386 (32 bit intel) version of Fedora 8.
I was able to finally start fedora 8 after installing it in text mode (which didn't download anything additional even when I set to do it by the way). But when I tried to update system with pup it showed many unresolved dependencies (what the...?). I closed pup and launched it again. It said that rpm db is corrupt. I tried rpm --rebuilddb but no luck - message about fatal error instead of db rebuilding. Rpm is MEGA-UNSTABLE. Fedora 8 is unusable.
That rpmdb corruption happens on your system doesn't mean it happens everywhere. This looks fairly similar to bug 230362, but so far there aren't really any clues what's so different on these systems to everything else. These kind of problems are usually due to the mmap()'ed db environment getting somehow screwed up, which can happen due to kernel (driver and otherwise) and glibc bugs: there was a huge amount of "rpmdb is corrupted" troubles about a year ago where the real bug turned out to be in kernel (2.6.18 and thereabouts) mmap implementation. The point: it's not as simple as "rpm is unstable and buggy". One thing you could try is installing x86_64 version and see if the corruption happens there too. If not, that'd be a valuable data point.
I'll try that
The system starts normally but I can't update kernel even from local file using rpm -U. Db becomes corrupt on this attempt but after system restart db works fine again. Looks like the actual error is somewhere in memory, not on disk. I will compile and install new kernel from source and try to update system with it and say if it makes any difference.
No, compiling and installing updated kernel from fedora 8 repo does not help. I can't update any package - rpm says db is corrupt. Then again after reboot db is fine and I can make query operations on it.
If you check the filesystem (boot the install cd with "linux rescue" at the boot prompt, then fsck) does anything show up? -Eric
No, no errors were found.
I was able to get rid of the problem by running rpm --rebuilddb right after system start before anything bad happens. Now rpm works fine. Perhaps updating the kernel helped. I'll leave this issue open for a few days in case of something else shows up.
Closing due to inactivity, comment #12 indicates this was some sort of temporary issue possibly with kernel or whatever.