[Bug 1875369] Re: recording device won't change

2022-05-20 Thread Igor V. Kovalenko
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 Bugs, which is subscribed to Ubuntu.

[Bug 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices

2022-04-03 Thread Igor V. Kovalenko
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 Bugs, which is subscribed to Ubuntu.

[Bug 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices

2022-04-02 Thread Igor V. Kovalenko
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

[Bug 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices

2022-03-23 Thread Igor V. Kovalenko
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

[Bug 1964579] Re: Pulseaudio fails to detect /enable Intel SST sound card

2022-03-11 Thread Igor V. Kovalenko
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 Bugs, which is subscribed to Ubuntu.

[Bug 1953052] Re: In Jammy sound level reset after reboot

2022-02-20 Thread Igor V. Kovalenko
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 Bugs, which is subscribed to Ubuntu.

[Bug 1953052] Re: In Jammy sound level reset after reboot

2022-02-19 Thread Igor V. Kovalenko
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

[Bug 1953052] Re: In Jammy sound level reset after reboot

2022-02-18 Thread Igor V. Kovalenko
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953052 Title: In Jammy sound level reset after reboot To manage notifications

[Bug 1953052] Re: In Jammy sound level reset after reboot

2022-02-17 Thread Igor V. Kovalenko
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

[Bug 1953052] Re: In Jammy sound level reset after reboot

2022-02-17 Thread Igor V. Kovalenko
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

[Bug 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake

2021-11-09 Thread Igor V. Kovalenko
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

[Bug 1941962] Re: pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from pa_x11_wrapper_unref()

2021-10-22 Thread Igor V. Kovalenko
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941962 Title:

[Bug 1945235] Re: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put() from transport_put() from hfp_rfcomm_handle()

2021-09-28 Thread Igor V. Kovalenko
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

[Bug 1941977] Re: PC streams music over low-quality HFP/SCO connection, instead of A2DP/AVDTP

2021-09-11 Thread Igor V. Kovalenko
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 Bugs, which is

[Bug 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()

2021-09-07 Thread Igor V. Kovalenko
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942685 Title: pulseaudio crashed with

[Bug 1941962] Re: pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from pa_x11_wrapper_unref()

2021-09-05 Thread Igor V. Kovalenko
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