The officially official Devuan Forum!

chomwitt

Member

Registered: 2019-09-24

Posts: 130  

virt-manager 1:4.1.0-1 is broken in daedalus

Devuan GNU/Linux 5 (daedalus/ceres)
After  doing :

$ sudo apt-get update
$ sudo apt-get upgrade

$ virt-manager --debug
--if i try to 'open' the window of a virtual machine virt-manager
crashes with the following message:
(virt-manager:19736): libsoup-ERROR **: 08:54:50.904:
libsoup3 symbols detected. Using libsoup2 and libsoup3
in the same process is not supported.

$ sudo apt-cache policy virt-manager
virt-manager:
  Installed: 1:4.1.0-1
  Candidate: 1:4.1.0-1

how can i correct this?

I've checked https://tracker.debian.org/pkg/virt-manager
and bug reports upstream at the project's bug tracker
but i havent found something.
But in searching the interent i found arch related opened issues FS#75823 where the cause is said to be  libgovirt on which many applications depend

I've managed to connect to a running vm from the command line:
$ sudo virsh list --all
Id   Name               State
-----------------------------------
6    Hyperbola_min_vm   running
-    Devuan_vm          shut off

$ virt-viewer --connect qemu:///system 6

So the issue in my case dont seem related to virt-viewer

Last edited by chomwitt (2022-10-13 09:50:30)

---

Devuan(Chimaera)(Daedalus)  DS+WM: XorgX11server+StumpVM

andyprough

Member

Registered: 2019-10-19

Posts: 327  

Re: virt-manager 1:4.1.0-1 is broken in daedalus

Thanks for posting this, I won't update to this version. Please let us know if you get a point update that fixes it or if there's some obvious config change that's needed to fix it.

xinomilo

Unknown

Registered: 2017-07-02

Posts: 315  

Re: virt-manager 1:4.1.0-1 is broken in daedalus

no such problem here (same version - testing/ceres). not a single libsoup message in virt-manager --debug. vms window open/work normally as always.
i would say problem is on some virt-manager installed recommendation, and not on actual virt-manager. eg. check this bug, it's similar :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019339
maybe some gnome thingy(?)