Thanks Sergeev, that is an interesting insight. $ mkdir /tmp/service # works $ qemu-system-x86_64 -enable-kvm -vnc unix:/tmp/service/vnc-sock # fails $ qemu-system-x86_64 -enable-kvm -vnc unix:/tmp/service/../service/../service/../service/vnc-sock
And while these are running in another shell run: $ socat - UNIX:/tmp/service/vnc-sock Checked a few versions: Qemu 2.10.1 works Qemu 2.8.0 fails. Qemu 2.5.0 fails. A few potential fixes that come to mind, but unfortunately in Summer 2016 there were quite some rewrites int the area. So for the regression risk we should really only identify those needed and carefully review that (instead of picking more fixes along). Iused gdb on a crashing qemu and found it really is exactly what this fixes: 3e7f136d vnc: fix crash when vnc_server_info_get has an error This change is nice and clean and should address the issue. I build a test ppa at [1] which we can check later if it fixes the issue. [1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3245 ** Changed in: qemu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705743 Title: qemu-system-x86 crashes when VNC connection is established To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1705743/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
