I have been using Fedora for few months without any issues so far. Then I haven’t touched my computer for few weeks and when I am trying to use him and boot on Fedora, I am getting a white screen asking me to contact my administrator…
I managed to get into the CLI mode and it seems that everytime I am trying to use DNF, it is prompting me the error
/lib64/libassuan.so.0 file too short
but this file is not existing on my drive. After checking google, it seems that this library would be linked to “pacman” which doesn’t seem to be installed on my system (command not found).
the system is running Fedora38
Does anyone has a clue about how to get my system back working?
That message seems to indicate there is something wrong with that particular file. You could try reinstalling the package that provides that file. Since DNF isn’t working, download the file manually from here: libassuan-2.5.6-1.fc38 | Build Info | koji
After it is downloaded, use rpm to reinstall: sudo rpm -Uvh full_file_name
On my system it seems that the libassuan package does not install the noted library file. In fact, the file /usr/lib64/libassuan.so.0 file is only provided by the libassuan-devel package according to dnf.
pacman is not installed on my system (and should not be on most fedora systems) since it appears to be the package manager for Arch Linux.
It would seem that something has happened to the dnf command since it should not be trying to access that particular library file with a normal workstation installed system.
That’s weird. Here is what my command showed:
sudo dnf provides libassuan
Last metadata expiration check: 1:50:34 ago on Mon Aug 28 06:42:06 2023.
libassuan-2.5.5-6.fc38.i686 : GnuPG IPC library
Repo : fedora
Matched from:
Provide : libassuan = 2.5.5-6.fc38
I have installed libassuan, but I still have the same error.
And I tried to install the devel version but I have some dépendances issues (pkgconfig missing)
I used sudo dnf provides */libassuan.so and was given the libassuan-devel package only. sudo dnf provides */libassuan.so.0 (which is the file that was deemed missing) gives the libassuan package.
Wierd!
Assuan was developed for use by the GNU Privacy Guard, GnuPG,[…]
Assuan is not, however, limited to use with GnuPG servers and clients: it was design to be flexible enough to meet the demands of almost any transaction based environment with non-persistent servers.
dnf is a python script, so libassuan is probably required by one the the python libraries used by dnf. Since dnf isn’t working for you, I’ll provide
some details that maight be helpful. In my experience, a truncated system file is often a sign of deeper issues like a failing storage device or full filesystem.
As a minimum, I suggest check the S.M.A.R.T status of the drive using Gnome Disks.
Here:
% dnf info libassuan.x86_64`
[...]
Installed Packages
Name : libassuan
Epoch : 0
Version : 2.5.6
Release : 1.fc38
Architecture : x86_64
Installed size : 167.3 KiB
Source : libassuan-2.5.6-1.fc38.src.rpm
From repository : updates
Summary : GnuPG IPC library
URL : https://www.gnupg.org/
License : GPL-3.0-or-later AND LGPL-2.1-or-later AND LGPL-3.0-or-later
Description : This is the IPC library used by GnuPG 2, GPGME and a few other
: packages.
Actually the release of F38 in April was libassuan package version 2.5.5-6 and it was updated to 2.5.6-1 in early July according to my dnf history. Of course that means any system upgraded from F37 to F38 or installed from an updated respin of F38 after the package update would not see that change because they would already have the newer version.
