GUI audio settings silently reverted if user is not a member of 'audio'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
New
|
Undecided
|
Unassigned |
Bug Description
Hi,
Trying to connect a JBL-450BT heeadset to my system has resulted in several bugs. The particular one I have encountered is that audio settings are silently discarded if the user is not a member of the audio group. the particular settings I was trying to fiddle with were the headset profile (A2DP -> HSP/HFP) and the mic input.
Steps to reproduce:
1. Install ubuntu 20.04 desktop, making no particular add-on or configuration actions.
2. Connect a bluetooth headset using the system UI.
3. Go to sound settings, change the connection profile from A2DP to HSP/HFP.
Expected result:
Upon closing the settings app, the settings activate and the profile switches to HSP/HFP. upon reopening the settings app, settings are preserved.
Observed result:
Upon closing the settings app, the settings do not activate and the headset remains on A2DP profile. upon reopening the settings app, settings have been reverted / not been saved.
Observed result 2:
Adding the user to the audio group and rebooting the machine has caused the problem to disappear and behaviour now matches 'expected result'. this is apparently against https:/
I have to say I'm stymied about which package this needs to be reported against.
System information:
gilbahat@meadow:~$ lsb_release -rd
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04
root@meadow:~# hcitool info 78:44:05:B3:C2:2D
Requesting information ...
BD Address: 78:44:05:B3:C2:2D
OUI Company: FUJITU(HONG KONG) ELECTRONIC Co.,LTD. (78-44-05)
Device Name: JBL T450BT
LMP Version: 4.1 (0x7) LMP Subversion: 0x13b3
Manufacturer: WuXi Vimicro (129)
Features page 0: 0xbf 0xfe 0x8d 0xfe 0x9b 0xfd 0x79 0x83
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <sniff mode> <RSSI>
<channel quality> <SCO link> <HV2 packets> <HV3 packets>
<u-law log> <A-law log> <CVSD> <power control>
<transparent SCO> <broadcast encrypt> <EDR ACL 2 Mbps>
<EDR ACL 3 Mbps> <enhanced iscan> <interlaced iscan>
<interlaced pscan> <inquiry with RSSI> <extended SCO>
<EV4 packets> <EV5 packets> <AFH cap. slave>
<AFH class. slave> <3-slot EDR ACL> <5-slot EDR ACL>
<pause encryption> <AFH cap. master> <AFH class. master>
<EDR eSCO 2 Mbps> <EDR eSCO 3 Mbps> <3-slot EDR eSCO>
<extended inquiry> <simple pairing> <encapsulated PDU>
<err. data report> <non-flush flag> <LSTO> <inquiry TX power>
<extended features>
Features page 1: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1869313/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]