Results 1 to 6 of 6

Thread: Problem with RPM's and the YaST-Softwareinstaller

  1. #1
    xVerteXx NNTP User

    Red face Problem with RPM's and the YaST-Softwareinstaller

    hi

    i installed opensuse 11.2 on a usb-stick and it works fine.

    or better said, it worked fine till i broke anything again (i'm quite new to linux).

    my problems:
    1: when i try to install the flashplayer by using the rpm-package that i downloaded from adobe.com, i get this failure:
    "internal system error", detailed info says: "[PK_TMP_DIR|dir:///var/tmp/TmpDir.R3BQAg] Repository already exists.".
    2: when i try to install new software with the yast-software-installer i get a failure like this, no matter what packet i try to install:
    Code:
    Subprocess failed. Error: RPM fehlgeschlagen: rpmdb: PANIC: Invalid argument
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) storing record 4.0-1 into Requireversion
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "3.0.4-1" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30977) getting "4.4.6-1" records from Requireversion index
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 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: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 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: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 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: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 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: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 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: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery
    now i don't know which recovery is meant and how i can fix all this in general

  2. #2
    xVerteXx NNTP User

    Default Re: Problem with RPM's and the YaST-Softwareinstaller

    update of my problem:
    when i try to install the flashplayer-rpm now, i get this message:
    "failed to get supported types for the backend: Launch helper exited with unknown return code 1"
    instead of the message before

  3. #3
    Join Date
    Jan 2009
    Location
    Hungary
    Posts
    40

    Default Re: Problem with RPM's and the YaST-Softwareinstaller

    I have the same issue. Is there still a solution already? :S

    linux-8j1v:/home/bigb/downloads # rpm -Uvh ifuse-1.0.0-3.2.x86_64.rpm
    Preparing... ########################################### [100%]
    package ifuse-1.0.0-3.2.x86_64 is already installed

  4. #4
    Join Date
    Feb 2009
    Location
    Burgas, Bulgaria
    Posts
    148

    Default Re: Problem with RPM's and the YaST-Softwareinstaller

    You need to rebuild your database. First you should create a backup to your database ( /var/lib/rpm/ ). You can use YaST's tool or comand line:
    Code:
    cd /var/lib
    mkdir rpm-backup
    rsync -av ./rpm/. ./rpm-backup/.
    I prefer YaST. Then make sure you are not accessing the database( if you are running zypper or yast stop them or better wait for them to finish).
    After that run:
    Code:
    rpm -vv --rebuilddb
    You should have no problems after this. If you have problems or just want to learn some techie stuff read this Repair an RPM database safely.
    Let us know how the operation ended
    openSUSE 11.4 | KDE 4.6
    AMD Athlon64 X2 5000+ | 2GB RAM | ATI Radeon HD 3450 | Gigabyte M68SM-S2L | 320 GB HDD

  5. #5

    Default Re: Problem with RPM's and the YaST-Softwareinstaller

    well, i have the same problem, followed the instructions and it made no difference. whenever i try to install an RPM package using the installer i get the error:

    failed to get supported types for the backend: Launch helper exited with unknown return code 1

    tried with skype, flash player and opera - no luck
    all 3 went fine when using rpm from the terminal window.

    any ideas?
    thanks

  6. #6

    Default Re: Problem with RPM's and the YaST-Softwareinstaller

    Quote Originally Posted by esiu69 View Post
    well, i have the same problem, followed the instructions and it made no difference. whenever i try to install an RPM package using the installer i get the error:

    failed to get supported types for the backend: Launch helper exited with unknown return code 1

    tried with skype, flash player and opera - no luck
    all 3 went fine when using rpm from the terminal window.

    any ideas?
    thanks
    I'm confused, can you clarify?
    You followed the rpm database rebuild instructions suggested by Siminin?
    And you are still receiving the DB4 error messages?

    Which package installer are you using?
    When you use the rpm command line rpm packages install without problem?

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •