FS#52570 - [boost-libs]
Attached to Project:
Arch Linux
Opened by Juan Antonio Clavero (jaclaverogarcia) - Monday, 16 January 2017, 10:04 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 28 January 2017, 14:38 GMT
Opened by Juan Antonio Clavero (jaclaverogarcia) - Monday, 16 January 2017, 10:04 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 28 January 2017, 14:38 GMT
|
Details
Description: Since updating the boost-libs package 1.62.0 to
1.63.0 it is not possible to connect to libvirtd from
virt-manager.
Additional info: boost-libs 1.63.0-1 libvirt 2.4.0-2 libvirt-glib 0.2.3-1 libvirt-python 2.2.0-2 libvirt-python3 2.2.0-2 qemu 2.8.0-1 virt-manager 1.4.0-2 Log error of libvirtd (the output is in spanish, I did not translate it): ene 16 10:46:38 portatiljuan libvirtd[7387]: no existe disponible un controlador de conexión para qemu:///system ene 16 10:46:38 portatiljuan libvirtd[7387]: Fin de archivo al leer datos: Error de entrada/salida Steps to reproduce: When virt-manager attempts to connect to libvirt via the local qemu connection, the error occurs: libvirtError: There is no connection driver available for qemu: /// system |
This task depends upon
Closed by Doug Newgard (Scimmia)
Saturday, 28 January 2017, 14:38 GMT
Reason for closing: No response
Saturday, 28 January 2017, 14:38 GMT
Reason for closing: No response
No connection driver available for qemu:///system
End of file when reading data: Input / output error
Suspect that it is an error derived from something else.
If I downgrade boost-libs to 1.62.0-x it works fine (however Evolution 3.22.3-1 does not start).
I think it can be by the python package or another dependency/required.
Things like this are usually caused by partial updates or AUR packgaes.