Open Teascade opened 3 weeks ago
pipewire is unsupported, please replicate with a real jack backend.
I'm unable to do that, because my entire desktop linux environment relies on me using pipewire specifically. If this is not a complaint for OBS then, then who shall I make this issue to?
If you cannot test if the issue occurs in jack then its unlikely anyone will be interested in your report, since pipewire will probably just tell you its an obs issue if you cannot prove they diverge from jack's implementation, and im telling you we dont support pipewire since I'm not aware of anyone on our team interested in debugging pipewire's translation layers.
Operating System Info
Other
Other OS
ArchLinux (6.10.4-arch2-1)
OBS Studio Version
Other
OBS Studio Version (Other)
30.2.1-1 (latest from ArchLinux official repos)
OBS Studio Log URL
https://obsproject.com/logs/xydLjSF8jOVzXOML
OBS Studio Crash Log URL
https://obsproject.com/logs/xydLjSF8jOVzXOML
Expected Behavior
Sometime earlier this year, obs was working as intended, by which I mean that obs never segfaulted regardless of how I started or stopped playbacks during the program running (YouTube/Spotify/Netflix/etc.).
Current Behavior
OBS segfaults either when starting playback or stopping it. It seems to be random which causes it, and sometimes it seems to be source-specific. Unclear.
Steps to Reproduce
Anything else we should know?
Full GDB logs and
backtrace -full
after segmentation fault, which causes me to believe the issue is related to pipewire/pipewire-jack.Other related versions are:
The GDB logs in their entirety: