VladimirMrzv
VladimirMrzv
I am on Ubuntu 22.04 pipewire 0.3.55 from https://launchpad.net/~pipewire-debian/+archive/ubuntu/pipewire-upstream
I can help to reproduce it and save log. Write please how to do it.
my files [pw-dump.log](https://github.com/dimtpap/obs-pipewire-audio-capture/files/9132920/pw-dump.log) [pwlog1.txt](https://github.com/dimtpap/obs-pipewire-audio-capture/files/9132921/pwlog1.txt) [pwlog2.txt](https://github.com/dimtpap/obs-pipewire-audio-capture/files/9132922/pwlog2.txt) I run game from steam in proton. Reproducing in Dying Light 2.
sad, but not helped New logs [pw-dump2.log](https://github.com/dimtpap/obs-pipewire-audio-capture/files/9142328/pw-dump2.log) [pwlog6.txt](https://github.com/dimtpap/obs-pipewire-audio-capture/files/9142329/pwlog6.txt) [pwlog5.txt](https://github.com/dimtpap/obs-pipewire-audio-capture/files/9142338/pwlog5.txt) in file 5, after start no sound and plugin not work
Try on another game and it works 3-4 hours. Maybe something go wrong with Dying Light 2.
After update pipewire and today plugin it works better, but sound continue disappearing in DayingLight2. Now disappear after 1 hour and 25 minutes, it happened two times - 5 days...
My system crashes too, but after start streaming. https://obsproject.com/logs/z5sKa9lIBgLOTywU
before works fine. I got updates for cmake (3.22.1-1ubuntu1) to 3.22.1-1ubuntu1.22.04.1 cmake-data (3.22.1-1ubuntu1) to 3.22.1-1ubuntu1.22.04.1 gnome-control-center (1:41.7-0ubuntu0.22.04.4) to 1:41.7-0ubuntu0.22.04.5 gnome-control-center-data (1:41.7-0ubuntu0.22.04.4) to 1:41.7-0ubuntu0.22.04.5 gnome-control-center-faces (1:41.7-0ubuntu0.22.04.4) to 1:41.7-0ubuntu0.22.04.5 libpoppler-cpp0v5 (22.02.0-2) to...
also update mesa today test old build and no crashes. problem begin from update with commit https://gitlab.freedesktop.org/mesa/mesa/-/commit/eec1e728c5cde99e8cd61a49791dfd96e383a902 and works fine with https://gitlab.freedesktop.org/mesa/mesa/-/commit/e612f32e1ad20789441057b0de131fa04466e55e Open bug report https://gitlab.freedesktop.org/mesa/mesa/-/issues/7290
My problem was fixed with latest mesa