internal error path to monitor.sock too long when I reinstall QEMU flatpak extension after making VM

[alexsch01]

I tried importing the qcow2 file into a new VM install and I get a similar error

(I made 2 extra new lines so it would wrap around)

Unable to complete install: 'internal error: UNIX socket path '/home/deck/.var/app/org.virt_manager.virt-
manager/config/libvirt/qemu/lib/domain-2-silverblue41/monitor.sock' too long'

Traceback (most recent call last):
  File "/app/share/virt-manager/virtManager/asyncjob.py", line 71, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/app/share/virt-manager/virtManager/createvm.py", line 2008, in _do_async_install
    installer.start_install(guest, meter=meter)
  File "/app/share/virt-manager/virtinst/install/installer.py", line 726, in start_install
    domain = self._create_guest(
             ^^^^^^^^^^^^^^^^^^^
  File "/app/share/virt-manager/virtinst/install/installer.py", line 667, in _create_guest
    domain = self.conn.createXML(initial_xml or final_xml, 0)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/lib/python3.12/site-packages/libvirt.py", line 4545, in createXML
    raise libvirtError('virDomainCreateXML() failed')
libvirt.libvirtError: internal error: UNIX socket path '/home/deck/.var/app/org.virt_manager.virt-
manager/config/libvirt/qemu/lib/domain-2-silverblue41/monitor.sock' too long

[travier]

Can you try again with a shorter name for the VM (a) to confirm that's the issue?

[alexsch01]

I used "silverblue41" (Fedora Kinoite 41 so I picked the closest thing and kept the default name) for the VM name
I deleted and reinstalled the flatpak and the VM with the exact same name and that's working so far
really strange

[alexsch01]

Issue still happens after going through install process of Fedora Kinoite 41 (silverblue41) [on Steam Deck]

[alexsch01]

Everytime I click the start button, the count on domain-${count}-silverblue41 goes up by 1

(I made 2 extra new lines so it would wrap around)

Error starting domain: internal error: UNIX socket path '/home/deck/.var/app/org.virt_manager.virt-
manager/config/libvirt/qemu/lib/domain-3-silverblue41/monitor.sock' too long

Traceback (most recent call last):
  File "/app/share/virt-manager/virtManager/asyncjob.py", line 71, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/app/share/virt-manager/virtManager/asyncjob.py", line 107, in tmpcb
    callback(*args, **kwargs)
  File "/app/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn
    ret = fn(self, *args, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/share/virt-manager/virtManager/object/domain.py", line 1384, in startup
    self._backend.create()
  File "/app/lib/python3.12/site-packages/libvirt.py", line 1379, in create
    raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: internal error: UNIX socket path '/home/deck/.var/app/org.virt_manager.virt-
manager/config/libvirt/qemu/lib/domain-3-silverblue41/monitor.sock' too long

[matheuswillder]

Error starting domain: internal error: UNIX socket path '/home/deck/.var/app/org.virt_manager.virt-
manager/config/libvirt/qemu/lib/domain-3-silverblue41/monitor.sock' too long

I was just reading the issues but.. isn't this error the same or related to this one below?

flathub/org.virt_manager.virt_manager.Extension.Qemu#11 (comment)

[alexsch01]

Yeah seems similar