See https://www.openwall.com/lists/musl/2020/08/14/3 Please consider reverting the musl-1.2.1 stabilization.
I am not one to follow mailing lists for another project. Can you actually explain how things like pulseaudio are broken? I currently use pulseaudio with all my machines and none of them are having an issue with musl-1.2.1
I can confirm app-emulation/libvirt is broken on musl 1.2.1, app-emulation/virt-manager can't connect to the server. upstream report: https://gitlab.com/libvirt/libvirt/-/issues/52#note_377144096 patch: https://www.redhat.com/archives/libvir-list/2020-August/msg00597.html
(In reply to Jory A. Pratt from comment #1) > I am not one to follow mailing lists for another project. Can you actually > explain how things like pulseaudio are broken? I currently use pulseaudio > with all my machines and none of them are having an issue with musl-1.2.1 I'm not using pulseaudio on my musl systems. However, I am experiencing the same problem as https://bugs.gentoo.org/738910#c2. The workaround for this is to kill the 2nd /usr/sbin/libvirtd process after starting libvirtd. Maybe we should carry the libvirt patches instead. Unfortunately upstream seems to be ignoring them so far.
(In reply to 12101111 from comment #2) > I can confirm app-emulation/libvirt is broken on musl 1.2.1, > app-emulation/virt-manager can't connect to the server. > > upstream report: > https://gitlab.com/libvirt/libvirt/-/issues/52#note_377144096 > > patch: https://www.redhat.com/archives/libvir-list/2020-August/msg00597.html This patches can not fully resolve the issue. Such command hangs and other, because libvirtd fork process deadlock'ed: virsh # list
The issue completely resolved for libvirt with above patches and sys-libs/libcap-ng-0.8.2-r1 sys-libs/musl-1.2.2-r1
(In reply to Alexander Miroshnichenko from comment #5) > The issue completely resolved for libvirt with above patches and > sys-libs/libcap-ng-0.8.2-r1 > sys-libs/musl-1.2.2-r1 Thanks.