Cannot install software with dnf after dnf update #46
Comments
|
I had the same problem. Running |
|
Is this occurring on a fresh install? |
yes. |
This method did not solve the problem [lzy@DESKTOP-GLN7DSM ~]$ sudo rm -f /var/lib/rpm/__db*
[sudo] password for lzy:
[lzy@DESKTOP-GLN7DSM ~]$ sudo yum update
Segmentation fault (core dumped)
[lzy@DESKTOP-GLN7DSM ~]$ |
|
I'm experiencing same issue on my fresh installation |
My fault... |
This update contains rpm, dnf, it should be a problem with these two packages, I have excluded these two packages in /etc/dnf/dnf.conf and then update. |
dnf is also the same error |
|
Can confirm the issue on a fresh installation. The first dnf update detailNo success with $ sudo rpm --rebuilddb
error: failed to replace old database with new database!
error: replace files in /var/lib/rpm with files from /var/lib/rpmrebuilddb.464 to recover |
|
What builds of Windows 10 are you on? I wonder if you are running into this WhitewaterFoundry/Pengwin-Enterprise#20 |
|
Oldish, 10.0.17763 It looks like that issue indeed. |
Both issues are still present on Microsoft Windows [Version 10.0.18362.356] |
|
I could avoid this problem on a new installation by doing the following steps: then we can now proceed on upgrading the rest of the packages or installing new ones. |
|
Thank you for the solution. If it works in all cases, we can put it in our init scripts |
|
I had struggled with this problem as well, and @ealap's solution worked for me. Thanks! |
|
It works! |
|
Marcin Kielar
It does on fersh install even without -v.
it's |
|
I just ran into this, and the key is to remove the rpm lock after you get the problem. Apparently, once the db system barfs, the rpm lock stays on. sudo rm /var/lib/rpm/.rpm.lock is the key. |
|
A fix was uploaded to the store with the version 1.30.5.0 if someone can check if the error is gone away. |
|
Works fine for me. Full log no edits of actions identical to first post. |
|
Excellent thank you for the report. I will close it in a couple of days |
|
I have clean installed the 1.30.5.0 version but still runned into this problem... |
|
Tested it. It break after dnf update, and then multiple dnf installs now. |
|
Hello @YRTV, What version did you test? And which Windows version? Regards |
|
winver Version 10.0.18362.476 |
|
I can confirm the issue on a fresh installation (1.31.6.0). The first dnf update runs to completion, but every other update/install will show the following error: Winver = 1909 (OS Build 18363.476) |
|
Same here. Latest Win 10 Pro version. Solution was to remove the lock file ( |
Solution confirmed ! |
|
Verified and blogged about it too. https://divby0.blogspot.com/2020/02/fedora-31-rawhide-in-windows-subsystem.html |
|
issue is solved by installing Windows 1903 (OS Build 18362.1049) or later before installing Fedora Remix for WSL 31.5.0.0 |
|
@mi-hol the error is completely erratic, please use the upgrade.sh script included. It will ensure that dnf will always work. |
|
Should script also be used on WSL2? Problem doesn't exist yet on my WSL2 installation. |
|
Hello, Yes, use it even in WSL2 because this script takes care of updating any customization made like the file /etc/profile.d/00-remix.sh. We are planning to make some Message of the Day (MOTD) telling that. Regards |
I really hope that this update solves the issue (at least this solves the glibc 2.31 so now it is safe to upgrade to Fedora 32). It has bugged us so much time and it has been the headache of many users. |
The text was updated successfully, but these errors were encountered: