"Unix socket path too long" is not reported to the user
Affected version
- Boxes version: 46.0-2e4e714e
- Flatpak: Yes
- Operating system name and version: Debian 12
Steps to reproduce
- Have a long username
- Choose an OS with a long name
- Start a virtual machine
Seen behavior
The VM fails to start. Boxes suggests to look at the "troubleshooting log" which contains no relevant info.
Starting Boxes from the command line, I see a more relevant error message:
(org.gnome.Boxes:2): Boxes-WARNING **: 20:19:52.929: machine.vala:611: Failed to start GNOME OS Nightly: Unable to start domain: internal error: UNIX socket path '/home/abderrahimkitouni/.var/app/org.gnome.Boxes/config/libvirt/qemu/lib/domain-1-gnomenightly-2/monitor.sock' too long
So the root cause is that the socket path is too long (and I can work around it by having a single virtual machine to avoid the -2 prefix). The secondary issue is that it doesn't end up in the "troubleshooting log".
I'm not sure what's the best way to deal with this, but trying to avoid a lot of nested directories could probably help.