[Bug 1178310] New: inconsistent pipewire stack trace resulting in no sound
http://bugzilla.opensuse.org/show_bug.cgi?id=1178310 Bug ID: 1178310 Summary: inconsistent pipewire stack trace resulting in no sound Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai@suse.com Reporter: pablo@blueoakdb.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 843176 --> http://bugzilla.opensuse.org/attachment.cgi?id=843176&action=edit pipewire stack trace Hi, I've been working-around[1] a sound issue for a while. I apologize for not reporting it when I first noticed it. I narrowed the issue to a pipewire stack trace[2]. The stack trace is inconsistent. Perhaps there's a timing and/or race-condition. I have captured `alsa-info' with sound working[3] and no sound[4]. As expected, when there is no sound, `alsa-info' writes to stderr that no sound cards were found[5]. Please let me know if there is more data that I can provide. ::: References ::: 1 - My work-around is to suspend and resume my laptop. 2 - messages.snip.1 - a snip from /var/log/messages with the pipewire stack trace 3 - alsa-info.with-sound 4 - alsa-info.with-no-sound.1 5 - errors.1 - alsa-info errors when pipewire stack traces -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1178310 http://bugzilla.opensuse.org/show_bug.cgi?id=1178310#c1 --- Comment #1 from Pablo Sanchez <pablo@blueoakdb.com> --- Created attachment 843177 --> http://bugzilla.opensuse.org/attachment.cgi?id=843177&action=edit alsa-info when sound is working (no stack trace) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1178310 http://bugzilla.opensuse.org/show_bug.cgi?id=1178310#c2 --- Comment #2 from Pablo Sanchez <pablo@blueoakdb.com> --- Created attachment 843178 --> http://bugzilla.opensuse.org/attachment.cgi?id=843178&action=edit alsa-info with no sound working (pipewire stack trace) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1178310 http://bugzilla.opensuse.org/show_bug.cgi?id=1178310#c3 --- Comment #3 from Pablo Sanchez <pablo@blueoakdb.com> --- Created attachment 843179 --> http://bugzilla.opensuse.org/attachment.cgi?id=843179&action=edit alsa-info stderr errors when no sound -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1178310 http://bugzilla.opensuse.org/show_bug.cgi?id=1178310#c5 --- Comment #5 from Pablo Sanchez <pablo@blueoakdb.com> --- Hi Takashi, I did not know that pipewire was not needed. :] I've uninstalled the bits and I did two reboot tests: audio works. \o/ Thank you so much! I detailed below what I've done with the hopes that it may help others. Given pipewire is version 0.X, I'm going to assume it'll become more stable. I'm happy to do more testing to try to get to the root-cause or just call it done (RESOLVED). Please let me know. ::: Strategy ::: Generally I try minimally invasive tactics first. Below is the order in which I tried to resolve the issue. ::: 1 - User-level service disable ::: Stop and disable the pipewire.socket/.service for my user. On reboot, I saw the stack trace in /var/log/messages and no sound. The service was still started for my user. ::: 2 - Globally disable the service ::: I globally disabled the service, rebooted and still no sound. /var/log/messages showed the stack trace. I confirmed that the service was disabled: # user-level status check systemctl --user status pipewire.socket systemctl --user status pipewire.service # globally disable the service systemctl disable --global pipewire ::: 3 - Uninstall pipewire ::: I removed pipewire. I probably should set up zypper to not install it. No more stack trace and after two reboot tests, I confirmed audio is working. # Drop the hammer on pipewire rpm --erase pipewire pipewire-modules pipewire-spa-plugins-0_2 plasma5-session-wayland -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1178310 http://bugzilla.opensuse.org/show_bug.cgi?id=1178310#c6 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(pablo@blueoakdb.c | |om) | --- Comment #6 from Takashi Iwai <tiwai@suse.com> --- OK, good to hear :) The fix is on its way to TW now. It might take a bit more time until the fix reaches to TW snapshot. Until then, you can keep pipewire uninstalled, or you can just remove the file /etc/alsa/conf.d/99-pipewire-default.conf. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1178310 http://bugzilla.opensuse.org/show_bug.cgi?id=1178310#c7 --- Comment #7 from Pablo Sanchez <pablo@blueoakdb.com> --- Thanks again for your help and the .conf pro-tip. I'll leave it uninstalled and when the updated bits drop on TW, it'll be re-installed. If I have the same issues, I'll open a new bug and reference this one. Have a good day! -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com