-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segfault if Pipewire not available #10859
Comments
For what it's worth, if I don't have the pipewire user service running on my system (s6-rc service not systemd), I don't get this; the AO just errors out normally. No clue why masking the socket would result in anything different though (presumably this has the same effect as preventing the daemon from running at all). |
Ouch. I can only look at this in a few hours. |
[ao/pipewire] Headers version: 0.3.59 [ao/pipewire] Library version: 0.3.59 More exact: the package built from https://github.com/archlinux/svntogit-packages/tree/5dcef66c656839c179ddcd4dcdc279b8dcf9f483/trunk |
Is it reliably reproducible for you? Can you create some logs with the env variable PIPEWIRE_DEBUG? Does it reproduce with the Arch binary package? |
FYI you can use debuginfod to get automatic debug symbols for all repo packages. |
Yes, it's 100% reliable. Updated my entire system just now too, didn't help. Didn't try the upstream pkg but here's a fresh log https://0x0.st/o6hD.txt |
You're right though that is must be something about my system because I can't reproduce it in a clean container with mpv & pipewire from testing or from extra or self-compiled. |
I would really like to have a test with the Arch package. It would show us if it's an issue with the system or the build. |
I ran into the same issue earlier on arch. Update to pipewire 0.3.60 fixed it. |
@suicide In 0.3.60 the assert() was removed so this issue is maybe just hidden. |
@t-8ch I just tried downgrading pipewire again but I could not reproduce the error with mpv 0.35 |
Still happens, https://0x0.st/oIq2.txt
Well not really, I run ffmpeg-git on my system which shouldn't but could play a part. |
In any case upgrading to pipewire 1:0.3.60-1 fixed this which is good enough. |
Thoughts:
seriously
Backtrace:
Possible environment peculiarities:
I have the
pipewire.socket
user unit masked to avoid pipewire from even doing anything at all on my system (this might be a bad idea, who knows?).The text was updated successfully, but these errors were encountered: