Created attachment 1235082 [details] /var/lib/rpm database Well, for an unknown reason, “dnf upgrade -y” crashed when trying to import a ɢᴘɢ key : (33/34): libwebp-0.5.2-1.fc25.x86_64.rpm 90 kB/s | 244 kB 00:02 (34/34): perl-5.24.0-380.fc25.x86_64.rpm 184 kB/s | 6.0 MB 00:33 --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 112 kB/s | 6.3 MB 00:57 attention : /var/cache/dnf/rpmfusion-free-updates-8b261166f7b8f005/packages/ffmpeg-3.1.6-1.fc25.x86_64.rpm: Entête V4 RSA/SHA1 Signature, clé ID 6806a9cb: NOKEY Importation de la clé GPG 0x6806A9CB : Utilisateur : « RPM Fusion free repository for Fedora (25) <rpmfusion-buildsys.org> » Empreinte : 286F 52F7 E9D4 7B46 3EAD D8AB A1E5 4A0F 6806 A9CB Provenance : /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-25 La clé a été importée avec succès Test de la transaction en cours La vérification de la transaction a réussi. Lancement de la transaction de test Erreur de segmentation (core dump) example@WINDOWS81:/mnt/c$ example@WINDOWS81:/mnt/c$ su -c "dnf upgrade" erreur : rpmdb: BDB0113 Thread/process 21/140311634183936 failed: BDB1507 Thread died in Berkeley DB library erreur : db5 erreur(-30973) de dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery erreur : impossible d'ouvrir l'index Packages en utilisant db5 - (-30973) erreur : impossible d'ouvrir la base de données paquet dans /var/lib/rpm Erreur : Error: rpmdb open failed I tried to repair it, but it had no effect : example@WINDOWS81:/mnt/c/Net/iso$ su -c "rpm --rebuilddb" example@WINDOWS81:/mnt/c/Net/iso$ Now, if I try to run any dnf or rpm (standalone) command, the process hang immediately with even printing a new line. It ignores all signals except sigkill. I also can’t look more in depth into the issue https://github.com/Microsoft/BashOnWindows/issues/1148. So here’s the ʀᴘᴍ database, I think if you use it will retrigger the problem.
Please note you can remove the default ubuntu Linux distribution on bashonwindows in order to install any rootfs you want. I imported the database in order to run it with a real Linux kernel, and I confirm it is not bash on Windows related.
of course, this was done from a fedora virtual machine. with a fedora kernel
I experienced this just now while updating Fedora 25, and seems to be related to updating libdb-* packages. See also: * #1175961 - fedora 21
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.