Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 906070 - media-video/pipewire-0.3.70-r1: No more sound in any app
Summary: media-video/pipewire-0.3.70-r1: No more sound in any app
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Sam James
URL:
Whiteboard:
Keywords: PATCH
Depends on:
Blocks:
 
Reported: 2023-05-10 15:03 UTC by Andrei Slavoiu
Modified: 2023-05-11 01:21 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge.info,9.16 KB, text/plain)
2023-05-10 15:04 UTC, Andrei Slavoiu
Details
Patch that redirects error messages to stderr (gentoo-pipewire-launcher.in-r1.patch,779 bytes, patch)
2023-05-10 17:10 UTC, Andrei Slavoiu
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Andrei Slavoiu 2023-05-10 15:03:51 UTC
Upgrading to the -r1 revision removed the ability to play any sound. I couldn't identify exactly what's wrong, but Plasma's sound applet shows no sound cards and aplay seems to block trying to play anything. Couldn't find any useful error mesages in any log files.

Reverting to media-video/pipewire-0.3.70 restores things to normal.

Reproducible: Always
Comment 1 Andrei Slavoiu 2023-05-10 15:04:43 UTC
Created attachment 861434 [details]
emerge --info
Comment 2 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2023-05-10 15:08:59 UTC
flexibeast, can you take a look? thanks
Comment 3 Andrei Slavoiu 2023-05-10 16:02:37 UTC
Well, looking in the changes made for #904851 I found the issue: only pipewire is running, no wireplumber. Looking further into what might start pipewire alone before the script is run.
Comment 4 Andrei Slavoiu 2023-05-10 17:06:07 UTC
Turns out I had a $HOME/.xprofile that started pipewire, probably some leftover from my early experiments with pipewire.

So, what could be considered a bug in the Gentoo scripts is that the error messages are not redirected to stderr. That made them not appear in the session log.
Comment 5 Andrei Slavoiu 2023-05-10 17:10:39 UTC
Created attachment 861457 [details, diff]
Patch that redirects error messages to stderr
Comment 6 Alexis 2023-05-11 00:40:27 UTC
(In reply to Andrei Slavoiu from comment #4)
> Turns out I had a $HOME/.xprofile that started pipewire, probably some
> leftover from my early experiments with pipewire.
> 
> So, what could be considered a bug in the Gentoo scripts is that the error
> messages are not redirected to stderr. That made them not appear in the
> session log.

Sorry for the hassle! Thanks for tracking down the issue, and for the patch; yes, i think directing the error messages to stderr is the way to go, as i feel the pre-r1 behaviour of unconditionally terminating existing PW/WP sessions (and thus perhaps unnecessarily disrupting one or more active audio streams) was incorrect.
Comment 7 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2023-05-11 00:48:46 UTC
Thanks both.
Comment 8 Larry the Git Cow gentoo-dev 2023-05-11 01:21:51 UTC
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5fa782429b4f607f8a1dc0e41e5cbe1bd94b35c3

commit 5fa782429b4f607f8a1dc0e41e5cbe1bd94b35c3
Author:     Sam James <sam@gentoo.org>
AuthorDate: 2023-05-11 00:48:00 +0000
Commit:     Sam James <sam@gentoo.org>
CommitDate: 2023-05-11 00:48:00 +0000

    media-video/pipewire: write error messages from gentoo-pipewire-launcher to stderr
    
    Thanks to Andrei Slavoiu and flexibeast.
    
    Bug: https://bugs.gentoo.org/904851
    Closes: https://bugs.gentoo.org/906070
    Signed-off-by: Sam James <sam@gentoo.org>

 media-video/pipewire/files/gentoo-pipewire-launcher.in-r1         | 8 ++++----
 .../{pipewire-0.3.70-r1.ebuild => pipewire-0.3.70-r2.ebuild}      | 0
 2 files changed, 4 insertions(+), 4 deletions(-)