From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [SOLVED]Re: [gentoo-user] Bluetooth speakers
Date: Wed, 18 May 2022 15:22:07 +0100 [thread overview]
Message-ID: <5570276.DvuYhMxLoT@wstn> (raw)
In-Reply-To: <8067451.T7Z3S40VBb@lenovo.localdomain>
On Wednesday, 18 May 2022 11:02:21 BST Michael wrote:
> On Wednesday, 18 May 2022 09:51:57 BST Peter Humphrey wrote:
> > On Saturday, 14 May 2022 17:34:58 BST Peter Humphrey wrote:
> > > On Thursday, 5 May 2022 16:22:56 BST Peter Humphrey wrote:
> > > > Is there a knack to getting my plasma desktop to operate happily with
> > > > my
> > > > new Bluetooth speakers? I can get a connection using the Bluetooth
> > > > control panel, and the sound device appears in the Audio control
> > > > panel,
> > > > but testing either speaker produces no sound.
> > >
> > > I think I've solved the problem. No, not BT but with a wired connection
> > > I
> > > do now have sound. BT can wait until I need it.
> >
> > Wrong again. In fact, the problem was that pulseaudio was not running. A
> > simple 'pulseaudio start' - et voila! Sound.
> >
> > I found this along the way:
> >
> > # pulseaudio --dump-conf
> > ### Read from configuration file: /etc/pulse/daemon.conf ###
> > daemonize = no
> > [...]
> >
> > Why is it set to No by default? Isn't PA deaf without the daemon running?
>
> Pulseaudio is currently set to "daemonize = no" by default and it should
> also be set "autospawn = no", in order for Plasma to use pipewire instead
> of pulseaudio. Pipewire is the new audio solution, which is meant to
> satisfy use cases previously addressed with pulseaudio and/or jack,
> although it should co-exist and work with both regardless.
>
> As I understand it originally udev would probe, auto-detect and hotplug
> devices, calling pulseaudio to process audio. I am not up to speed how
> pipewire now interacts with pulseaudio in depth, but I can see on a Plasma
> system which has pulseaudio installed, pipewire is launched and uses
> pipewire- pulse.conf:
>
> \_ /usr/bin/wireplumber
> \_ /usr/bin/pipewire
> \_ /usr/bin/pipewire -c pipewire-pulse.conf
>
> I have audio working, but no pulseaudio process shows up.
Somewhere around here I said I had too many USE flag staatements under /etc/
portage, so I removed package.use and just set whatever flags were needed to
install all my packages. That was fine, but it meant that USE=pulseaudio was
only set on alsa-plugins, which was fine as far as it went, but nothing else
could use PA. Now that I've put pulseaudio back into make.conf and recompiled,
I hope for a quieter life, if you see what I mean...
Thanks again for everyone's patience.
--
Regards,
Peter.
next prev parent reply other threads:[~2022-05-18 14:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 15:22 [gentoo-user] Bluetooth speakers Peter Humphrey
2022-05-05 16:21 ` Jack
2022-05-05 20:37 ` Michael
2022-05-06 7:59 ` Peter Humphrey
2022-05-06 12:24 ` [gentoo-user] " Grant Edwards
2022-05-06 12:41 ` Peter Humphrey
2022-05-06 14:40 ` Daniel Frey
2022-05-07 17:02 ` [gentoo-user] " Peter Humphrey
2022-05-07 19:32 ` Jack
2022-05-08 18:02 ` Peter Humphrey
2022-05-09 13:56 ` karl
2022-05-09 14:38 ` Michael
2022-05-10 8:17 ` Peter Humphrey
2022-05-10 9:26 ` Michael
2022-05-10 10:29 ` 3.5mm jacks (was Re: [gentoo-user] Bluetooth speakers) karl
2022-05-10 10:59 ` Michael
2022-05-10 12:00 ` [gentoo-user] Bluetooth speakers Peter Humphrey
2022-05-10 19:06 ` Michael
2022-05-11 10:54 ` Peter Humphrey
2022-05-12 10:01 ` Peter Humphrey
2022-05-12 13:49 ` Neil Bothwick
2022-05-12 14:50 ` Peter Humphrey
2022-05-12 9:44 ` Peter Humphrey
2022-05-14 16:34 ` [SOLVED]Re: " Peter Humphrey
2022-05-18 8:51 ` Peter Humphrey
2022-05-18 10:02 ` Michael
2022-05-18 14:22 ` Peter Humphrey [this message]
2022-05-18 14:47 ` Michael
2022-05-18 21:26 ` Wol
2022-05-19 8:36 ` Peter Humphrey
2022-06-12 7:38 ` FIXED " Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5570276.DvuYhMxLoT@wstn \
--to=peter@prh.myzen.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox