libvirt error: libidn.so.11 (caused by upgrading to Current64)

Hi Slackware community,

I recently upgraded from Slackware stable 14.2 x64 to Current64. I have been able to get the programs up and running as I use them, however with KVM, I was able to install libvirt but having issues with virt-manager. I get the following error:

Error starting Virtual Machine Manager: g-invoke-error-quark: Could not locate gvir_init: libidn.so.11: cannot open shared object file: No such file or directory (1)

Traceback (most recent call last):
File "/usr/share/virt-manager/virt-manager", line 291, in <module>
main()
File "/usr/share/virt-manager/virt-manager", line 272, in main
LibvirtGLib.init(None)
Error: g-invoke-error-quark: Could not locate gvir_init: libidn.so.11: cannot open shared object file: No such file or directory (1)

I have /usr/lib64/libidn.so.12
This has been happening with a couple of other applications but got them fixed. I found a solution (http://tiny.cc/3c5pbz)but I am not sure if this is the best solution.

To prevent this in the future, how do I go about upgrading the libraries correctly? Please feel free to impart other useful advice.

Thank you in advance for any help provided and the patience.

did you run this command?

slackpkg install-new

I did. I later realized that I was to run the command before

slackpkg upgrade-all

because I ran it afterward.

Should I run it again, just in case? I have tried some commands like

upgradepkg --install-new --reinstall *.txz

where I did not run

slackpkg install-new

Originally Posted by ernie young This has been happening with a couple of other applications but got them fixed. I found a solution (http://tiny.cc/3c5pbz)but I am not sure if this is the best solution.

no, creating random symlink is not a solution and it will surely break things in the long run.

To prevent this in the future, how do I go about upgrading the libraries correctly? Please feel free to impart other useful advice.

if you upgrade from 14.2 to current (and often also after applying some current updates) you better rebuild your third party packages that link to libraries not on your system anymore: if you don't know how to find what libraries links to whatever else, you can in alternative rebuild all of your third party packages.
also, don't do this on the same machine that you have upgraded: create a slackware current full installation in a virtual machine and build your packages there, then move them where you need them.

Since I am trying to get my virtual machine up, I was rebuilding the virt-manager package from Ponce's Current sbopkg, however I see your point very clear with this infinite loop:

Vte-2.91.gir:5384.1-5384.0: error: unexpected end of file Vte-2.91.gir:5384.1-5384.0: warning: expected end element of `type' Vte-2.91.gir:5384.1-5384.0: error: unexpected end of file Vte-2.91.gir:5384.1-5384.0: warning: expected end element of `type' Vte-2.91.gir:5384.1-5384.0: error: unexpected end of file Vte-2.91.gir:5384.1-5384.0: warning: expected end element of `type' Vte-2.91.gir:5384.1-5384.0: error: unexpected end of file Vte-2.91.gir:5384.1-5384.0: warning: expected end element of `type' Vte-2.91.gir:5384.1-5384.0: error: unexpected end of file Vte-2.91.gir:5384.1-5384.0: warning: expected end element of `type' Vte-2.91.gir:5384.1-5384.0: error: unexpected end of file

I tried rebuilding virt-manager by running sbopkg and reinstalling all the dependencies of virt-manager by creating sqg. The results above are from vte3. Does someone know what I am doing wrong?

No idea, as this appears to be some kind of vala-related issue which I have very limited knowledge of.

I have read some reports online of people fixing similar errors by uninstalling dependencies and rebuilding, and installing each rebuilt dependency one by one, like a link in the chain.

Best of luck...

Originally Posted by ernie young Since I am trying to get my virtual machine up, I was rebuilding the virt-manager package from Ponce's Current sbopkg, however I see your point very clear with this infinite loop: I tried rebuilding virt-manager by running sbopkg and reinstalling all the dependencies of virt-manager by creating sqg. The results above are from vte3. Does someone know what I am doing wrong?

there should be no vte3 package in slackware current (is called just "vte" there and is provided by Slackware, while vte in 14.2 has been moved to the unofficial repositoy for current and it's called "vte2"): most probably when you upgraded you haven't issued the command

slackpkg clean-system

that should have taken care to uninstall whatever has been removed from current.
be aware that then you will run it, it will also try to remove any third party package you have installed, but that could not be necessarily a bad thing as you could create a list of what it is removing and rebuild the third party stuff later... you are in charge of handling this, deselecting from slackpkg's dialog interface what you prefer too keep.

also, if you have vte3 in a sqg queue, most probably sqg and/or sbopkg point to the wrong repository (14.2 and not current).

to fix that see here for sbopkg and edit the pointers to repository directly the sqg script in a similar way (you can find it with the command "which sqg").

Thank you for the help provided willysr, Rockpops, and ponce.

Concerning

slackpkg clean-system

when I run it, only SBo-git packages appear and are the ones I got working before virt-manager, should I still run it?

I checked /etc/sbopkg/sbopkg.conf and the file was reset. I updated the .conf file but the sqf still generates the Stable packages even though I deleted the previous queue. I say this because the vte3 dependency is there. I have uploaded the file.

I have deleted

rm -fR /var/lib/sbopkg/SBo-git

and have run

sbopkg -r

but no luck.

I ran this command from this thread http://tiny.cc/wbbubz:

rm -rf /var/lib/sbopkg/*

and removed the queues, 14.2, and SBo-git folders. But now I am getting this

ERROR: /var/lib/sbopkg/queues or /var/lib/sbopkg/SBo/14.2 do not exist or are not writable. Check the configurable variables at the top of the script.

when I run:

sqg -p virt-manager

you delete the whole SBo repository used by sbopkg, so it's normal that you receive the error message
try running sbopkg -r again to re-download the whole repository.

you delete the whole SBo repository used by sbopkg, so it's normal that you receive the error message try running sbopkg -r again to re-download the whole repository.

I ran the command prior to my previous post and again after the suggestion but I still get the error. The folders in /var/lib/sbopkg are "queues" & "SBo-git".
This is the output after running the command:

bopkg -r Syncing with the remote repository into /var/lib/sbopkg/SBo-git. From git://github.com/Ponce/slackbuilds * branch current -> FETCH_HEAD Already up to date. HEAD is now at e153103edc 20190824.2 global branch merge. Repository update complete.

These past few days have been busy but I was finally able to look into this again and I found the solution in this thread, Ponce's answer: https://www.linuxquestions.org/quest...po-4175639249/
I am going to see if virt-manager installs like it should, wish me luck.

Originally Posted by Poprocks I have read some reports online of people fixing similar errors by uninstalling dependencies and rebuilding, and installing each rebuilt dependency one by one, like a link in the chain.

I have the following example,

slackpkg search pyparsing

Looking for pyparsing in package list. Please wait... DONE

The list below shows all packages with name matching "pyparsing".

[ Status           ] [ Repository               ] [ Package                                  ]
  upgrade                  slackware64                  pyparsing-2.3.1-x86_64-1_SBo --> pyparsing-2.4.0-x86_64-1

Is there something to update all the packages that have an upgrade available collectively instead of one by one? I ran

slackpkg update  

slackpkg install-new  

slackpkg upgrade-all

but an update like the one in the example was not picked up. So I ran

slackpkg download pyparsing-2.4.0-x86_64-1

upgradepkg --install-new --reinstall pyparsing-2.4.0-x86_64-1

I ask because I am sure there's an efficient way but I don't know how to do it.

In installing every package individually to install virt-manager, I have arrived to installing the libvirt package which is giving me the following output:

/usr/bin/grep: /usr/lib64/libgcrypt.la: No such file or directory /usr/bin/sed: can't read /usr/lib64/libgcrypt.la: No such file or directory libtool: error: '/usr/lib64/libgcrypt.la' is not a valid libtool archive make[3]: *** [Makefile:8313: libvirt_storage_backend_iscsi-direct.la] Error 1 make[3]: Leaving directory '/tmp/SBo/libvirt-5.6.0/src' make[2]: *** [Makefile:7086: all] Error 2 make[2]: Leaving directory '/tmp/SBo/libvirt-5.6.0/src' make[1]: *** [Makefile:2129: all-recursive] Error 1 make[1]: Leaving directory '/tmp/SBo/libvirt-5.6.0' make: *** [Makefile:2022: all] Error 2

Has someone faced something like this before?
Btw, happy Labor Day!