Description of problem: après avoir effectué les mises à jour avec pup, quand je lance yumex j'ai le message "erreur dans l'installation de yum". pour relancer yum, il faut redémarré le pc Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: yum update Loading "fastestmirror" plugin Loading "installonlyn" plugin rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbenv->open: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db3 - (-30977) error: cannot open Packages database in /var/lib/rpm Traceback (most recent call last): File "/usr/bin/yum", line 29, in ? yummain.main(sys.argv[1:]) File "/usr/share/yum-cli/yummain.py", line 85, in main base.getOptionsConfig(args) File "/usr/share/yum-cli/cli.py", line 199, in getOptionsConfig errorlevel=opts.errorlevel) File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 125, in doConfigSetup self.conf = config.readMainConfig(startupconf) File "/usr/lib/python2.4/site-packages/yum/config.py", line 597, in readMainConfig vars['releasever'] = _getsysver(startupconf.installroot, startupconf.distroverpkg) File "/usr/lib/python2.4/site-packages/yum/config.py", line 656, in _getsysver idx = ts.dbMatch('provides', distroverpkg) TypeError: rpmdb open failed
Created attachment 141410 [details] erreur yum
Segafualts and loss of data are likely due to removing an rpmdb environment without correcting other problems in the rpmdb. FYI: Most rpmdb "hangs" are now definitely fixed by purging stale read locks when opening a database environment in rpm-4.4.8-0.4. There's more todo, but I'm quite sure that a large class of problems with symptoms of "hang" are now corrected. Detecting damaged by verifying when needed is well automated in rpm-4.4.8-0.4. Automatically correcting all possible damage is going to take more work, but a large class of problems is likely already fixed in rpm-4.4.8-0.8 as well. UPSTREAM
*** This bug has been marked as a duplicate of 213963 ***