-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
segfault when encountering WAL error in /var/lib/dnf/history.sqlite #1603
Comments
If I do |
I ran into this while running tests in osbuild-composer with up-to-date packages (with sqlite 3.42.0). Is this an issue in libdnf or sqlite? If it's in sqlite, is there a ticket I can follow for that? |
I am not sure is this libdnf, sqlite, or rpm (see frame #5) bug, as I spent only a couple of minutes troubleshooting this. |
I don't see any official sqlite 3.42 package for Fedora. Is it something manually built? I cannot reproduce it using the latest versions from Fedora 38: libdnf 0.70.1 rpm 4.18.1 dnf 4.15.1 sqlite 3.40.1. |
It's manually built. After I upgrade a package (history.sqlite is modified), segfaulting starts again. |
If it's working for you with the current official version of sqlite for Fedora, I would suggest to wait until the new version is released. It might be already fixed by then. |
|
I guess if there has been already some operation involved using the manually built sqlite, the db could be broken. Could you check the |
Related issue in rpm — rpm-software-management/rpm#2553 |
Looks like sqlite 3.42.0 triggers some error which causes segfault when it is being logged. Running on Fedora 37 which comes with sqlite 3.40.0 by default.
libdnf 0.70.1, rpm 4.18.1, dnf 4.15.1.
Running command "dnf upgrade".
The text was updated successfully, but these errors were encountered: