Mailinglist Archive: opensuse-bugs (5385 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=683582

https://bugzilla.novell.com/show_bug.cgi?id=683582#c2


--- Comment #2 from Bakos Ludvig <ludvigbakos@xxxxxxxxx> 2011-04-01 12:01:04 
UTC ---
(In reply to comment #0)
> Yast was not able to install it the fresh packages!
>
> ---------------------------------------------------
>
>
> Subprocess failed. Error: RPM sikertelen: rpmdb: PANIC: Invalid argument
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from dbcursor->c_put: DB_RUNRECOVERY: Fatal error, 
> run
> database recovery
> error: error(-30977) storing record libc.so.6(GLIBC_2.2) into Requirename
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, 
> run
> database recovery
> error: error(-30977) getting "libc.so.6(GLIBC_2.3.4)" records from Requirename
> index
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, 
> run
> database recovery
> error: error(-30977) getting "libc.so.6(GLIBC_2.4)" records from Requirename
> index
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, 
> run
> database recovery
> error: error(-30977) getting "libgdk-x11-2.0.so.0" records from Requirename
> index
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, 
> run
> database recovery
> error: error(-30977) getting "libgdk_pixbuf-2.0.so.0" records from Requirename
> index
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, 
> run
> database recovery
> error: error(-30977) getting "libglib-2.0.so.0" records from Requirename index
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, 
> run
> database recovery
> error: error(-30977) getting "libgobject-2.0.so.0" records from Requirename
> index
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, 
> run
> database recovery
> error: error(-30977) getting "libgtk-x11-2.0.so.0" records from Requirename
> index
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, 
> run
> database recovery
> error: error(-30977) getting "liblcms.so.1" records from Requirename index
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, 
> run
> database recovery
> error: error(-30977) getting "libm.so.6" records from Requirename index
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, 
> run
> database recovery
> error: error(-30977) getting "libm.so.6(GLIBC_2.0)" records from Requirename
> index
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, 
> run
> database recovery
> error: error(-30977) getting "libm.so.6(GLIBC_2.1)" records from Requirename
> index
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, 
> run
> database recovery
> error: error(-30977) getting "libpango-1.0.so.0" records from Requirename 
> index
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, 
> run
> database recovery
> error: error(-30977) getting "libpthread.so.0" records from Requirename index
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, 
> run
> database recovery
> error: error(-30977) getting "libpthread.so.0(GLIBC_2.0)" records from
> Requirename index
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
> database recovery
> error: cannot open Providename index using db3 -  (-30977)
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
> database recovery
> error: cannot open Dirnames index using db3 -  (-30977)
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
> database recovery
> error: cannot open Requireversion index using db3 -  (-30977)
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
> database recovery
> error: cannot open Provideversion index using db3 -  (-30977)
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
> database recovery
> error: cannot open Installtid index using db3 -  (-30977)
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
> database recovery
> error: cannot open Sigmd5 index using db3 -  (-30977)
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
> database recovery
> error: cannot open Sha1header index using db3 -  (-30977)
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
> database recovery
> error: cannot open Filedigests index using db3 -  (-30977)
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
> database recovery
> rpmdb: PANIC: fatal region error detected; run recovery
> error: db3 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run
> database recovery

(In reply to comment #1)
> Please run 'rpm --rebuilddb', after that package management should work again.
> (It's not really a rpm problem, but some problem in the berkeley db
> implementation.)
> Please reopen if you still have problems after the database is rebuilt.



Thank you! Now already it's okay!

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.