This is a believed to be an application issue
https://webcompat.com/issues/53808
** Bug watch added: webcompat.com/issues #53808
https://webcompat.com/issues/53808
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio
Changing codec via gnome-control-center would probably need a feature
request to gnome-control-center to support new functionality in
>=pulseaudio-15.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubun
Whether your headset cannot be switched from HFP to A2DP is a separate
issue anyway. You can try pairing and trusting the device again, also
please check if you have pipewire audio enabled which could seldom take
over bluetooth a2dp, and see if bluetoothd log has anything related.
--
You received
It's in the 15.0 release notes,
https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/15.0/#supportforldacandaptxbluetoothcodecsplussbcxqsbcwithhigher-
qualityparameters
pactl send-message /card/bluez_card.XX_XX_XX_XX_XX_XX/bluez list-
codecs
You should also be able to find codec selection
Almost positive this is due to pipewire audio part is running, see alsa
info:
PipeWire:
Installed - Yes (/usr/bin/pipewire)
Running - Yes
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https
Corrado, this is still not ideal - while it appears to work at the
moment, having two audio servers with their own idea of volumes would
probably cause trouble going on.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaud
OK that matches what we have observed elsewhere. In theory there is an
audio device reservation protocol which is obeyed by both pulseaudio and
pipewire, but in practice it looks like at least some versions of
pipewire media server component do not obey the protocol in full (i.e.
are still using co
Please have a look which apps are using audio devices: 'lsof /dev/snd/*
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1953052
Title:
In Jammy sound level reset after r
Sebastien, if distribution is intended to provide pipewire function for
video only, there is no need to install audio parts. At very least
'with-pulse' 'with-jack' and other files directly or transitively
enabling 'with-audio' pipewire parts should not be installed so pipewire
media session daemon
Do you have both pulseaudio and pipewire audio enabled simultaneously?
At least system log suggests pipewire with session manager is also being
activated, this could cause issues if both attempt to restore volumes
for some reason.
--
You received this bug notification because you are a member of
I believe there is no defined order in which audio devices are resuming,
which makes them appear to pulseaudio in random order. This is probably
causing pulseaudio module-switch-on-connect to flip user preference to
each appearing device in same (random) order. If you do not use this
function you c
Just a heads-up, fix for libx11 issue 139 is now merged upstream
https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/84
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.n
This could be a problem in pulseaudio native backend, provoked by
numerous reconnections between bluez and headset.
If verbose log from pulseaudio daemon can be collected for this crash, I
think it is worth to file an issue in pulseaudio tracker here
https://gitlab.freedesktop.org/pulseaudio/pulse
Hi Brian, would you mind filing an issue on bluez tracker for this
analysis here https://github.com/bluez/bluez/issues
To me it looks valid, but still running this through bluez maintainers
is a good idea.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
I cannot reproduce this yet. Could someone who can please collect
pulseaudio daemon verbose log for this crash?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1942685
Tit
I believe this crash is caused by this libx11 issue
https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/139
** Bug watch added: gitlab.freedesktop.org/xorg/lib/libx11/-/issues #139
https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/139
--
You received this bug notification because y
16 matches
Mail list logo
