[Bug 1163486] New: Pulseaudo Bluetooth profile setting broken in plasma 5

older
[Bug 1173185] Latest Mesa Update...

bugzilla_noreply＠novell.com

12 Feb 2020 12 Feb '20

12:12

http://bugzilla.opensuse.org/show_bug.cgi?id=1163486 Bug ID: 1163486 Summary: Pulseaudo Bluetooth profile setting broken in plasma 5 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai@suse.com Reporter: stakanov@freenet.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- This is true since the first version of plasma 5 (about 5 years now). Use any BT adapter and Leap 15.1. KDE Plasma session. Connect any BT headset that supports both(!) profiles HSF/HFP and "sink A2DP". What does work correctly: The headset is paired in automatic if given trust. The source is changed to the new available one if set accordingly, BUT a) the source is not selected at appearance if the application is already open. E.g. in VLC audio sources the BT set is not electable. If closed down and restarted it appears. Some of the VOIP apps do not see it at all and if, do not change the source (e.g. Linphone). b) The profile selection of pulseaudio is not working. It seams broken insofar that when you use a device that is capable of HSF/HFP this profile is ALWAYS selected, although the settings menu senses and offers the A2DP profile. Once set A2DP (and no matter were, in the tray or in system settings) the profile jumps back to HSF/HFP headset function. The audio capacity of this protocol is to say the minor limited, thus BT headsets and pulseaudio in combination are not usable in 15.1. I can exclude a BT hardware problem as e.g. the very headset of SE-CL761 BT do connect flawlessly with a Nokia 8110 4G and full sound capacities. The problem was verified with several BT adapters. For this report I do reference to: Bus 004 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) However trying other brands and chipsets, other BTversions (2, 3, 4) do not add anything to the solution. This problem presents alike with JBC BT boxes that bring both profiles. Quality is actually voiding the function of external boxes for reproduction of music. What the software does: profile selection in pulseaudio are not honored in BT devices when selected and the device is capable of both protocols. BT device is electable only after restart of the respective program. What the software should do: leave the choice to the user if the usage is music (A2DP) or headset (HSF/HFP) when using a BT device. Honor the setting of the user. -- You are receiving this mail because: You are on the CC list for the bug.

Attachments:

attachment.htm (text/html — 4.2 KB)

Show replies by date

bugzilla_noreply＠novell.com

12 Feb 12 Feb

12:28

New subject: [Bug 1163486] Pulseaudo Bluetooth profile setting broken in plasma 5

http://bugzilla.opensuse.org/show_bug.cgi?id=1163486 http://bugzilla.opensuse.org/show_bug.cgi?id=1163486#c1 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seife@novell.slipkontur.de --- Comment #1 from Takashi Iwai --- Is it a problem of pulseaudio, bluez or KDE-specific issue? I vaguely remember of the HFS/A2DP profile issue. Adding Seife to Cc, who should know of the mess better. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

12:28

New subject: [Bug 1163486] Pulseaudo Bluetooth profile setting broken in plasma 5

http://bugzilla.opensuse.org/show_bug.cgi?id=1163486 http://bugzilla.opensuse.org/show_bug.cgi?id=1163486#c2 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |acho@suse.com --- Comment #2 from Takashi Iwai --- ... and Al to Cc for SLE15 stuff, too. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

12:48

New subject: [Bug 1163486] Pulseaudo Bluetooth profile setting broken in plasma 5

http://bugzilla.opensuse.org/show_bug.cgi?id=1163486 http://bugzilla.opensuse.org/show_bug.cgi?id=1163486#c3 --- Comment #3 from Stakanov Schufter --- (In reply to Takashi Iwai from comment #1)

...

Is it a problem of pulseaudio, bluez or KDE-specific issue?

I vaguely remember of the HFS/A2DP profile issue. Adding Seife to Cc, who should know of the mess better.

FYI Well, without giving responsibilities to anybody. When we (several users) filed during the years (yes, this one is a historic one, AFAIR, since 42.x) we were told finally, it is a pulseaudio based problem, as the BT function itself now works and pairing IS possible. Also the selection of new hardwaresource when it becomes available works ...limited to the plasma desktop, it seems not honored by applications. And in the settings the issue concerns settings in "multimedia". AFAIU the settings in the tray are only a link to the settings in the "system settings". The profiles are actually sensed correctly by BT, hardware capacities are shown correctly. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

30 Mar 30 Mar

20:28

New subject: [Bug 1163486] Pulseaudo Bluetooth profile setting broken in plasma 5

http://bugzilla.opensuse.org/show_bug.cgi?id=1163486 http://bugzilla.opensuse.org/show_bug.cgi?id=1163486#c8 --- Comment #8 from Stakanov Schufter --- OK, I tried. Issues: 1) the first time you pair the BT headset, the set is not seen in the list of audio devices. If you disconnect it and reconnect it again it reappears. This is reproducible on this machine. 2) when opening in settings the BT profiles of the headset, the A2DP is electable but the indicator below stays on "mono". Once you start VLC the setting is not honored, drops back to HSP. Sound quality is not adapted to consumption of music. 3) I have yet to do a call with voip to check the HSP microphone function. The microphone is listed, but that does not mean it works. Will report back on this later. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

31 Mar 31 Mar

07:59

New subject: [Bug 1163486] Pulseaudo Bluetooth profile setting broken in plasma 5

http://bugzilla.opensuse.org/show_bug.cgi?id=1163486 http://bugzilla.opensuse.org/show_bug.cgi?id=1163486#c9 --- Comment #9 from Stakanov Schufter --- Update: after the installation I am getting also a complaint in the dmesg. As it might be related, I think it will be of interest (so this is with the fixes I installed as of indication): sudo dmesg -r (excerpt) <4>[ 1338.404968] ------------[ cut here ]------------ <4>[ 1338.404980] WARNING: CPU: 2 PID: 934 at ../kernel/workqueue.c:2458 check_flush_dependency+0xad/0x120 <4>[ 1338.404981] Modules linked in: uinput fuse ip6t_MASQUERADE nf_nat_masquerade_ipv6 ipt_MASQUERADE nf_nat_masquerade_ipv4 ccm nf_nat_sip nf_conntrack_sip xt_CT xt_tcpudp ip6t_rpfilter af_packet ip6t_REJECT nf_log_ipv6 ipt_REJECT nf_log_ipv4 nf_log_common xt_LOG xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute br_netfilter bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle scsi_transport_iscsi iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables rfcomm cmac algif_hash bnep rtl8xxxu dmi_sysfs arc4 btusb btrtl btbcm btintel bluetooth ecdh_generic rtl8192cu rtl_usb rtl8192c_common <4>[ 1338.405028] rtlwifi mac80211 cfg80211 msr snd_hda_codec_hdmi iTCO_wdt iTCO_vendor_support snd_hda_codec_conexant wmi_bmof snd_hda_codec_generic intel_powerclamp mei_wdt coretemp snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep joydev snd_pcm pcspkr i2c_i801 intel_ips thinkpad_acpi lpc_ich wmi thermal ledtrig_audio snd_timer snd rfkill battery ac e1000e mei_me pcc_cpufreq mei ptp pps_core soundcore acpi_cpufreq button dm_crypt algif_skcipher af_alg crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel i915 i2c_algo_bit kvmgt vfio_mdev mdev vfio_iommu_type1 aes_x86_64 crypto_simd vfio cryptd glue_helper xhci_pci kvm serio_raw irqbypass ahci libahci xhci_hcd ehci_pci drm_kms_helper syscopyarea ehci_hcd sysfillrect sysimgblt fb_sys_fops usbcore drm drm_panel_orientation_quirks video dm_mirror <4>[ 1338.405082] dm_region_hash dm_log l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox ppp_generic slhc sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua <4>[ 1338.405098] CPU: 2 PID: 934 Comm: kworker/u9:4 Not tainted 4.12.14-lp151.28.44-default #1 openSUSE Leap 15.1 <4>[ 1338.405099] Hardware name: LENOVO 3680W1J/3680W1J, BIOS 6QET70WW (1.40 ) 10/11/2012 <4>[ 1338.405112] Workqueue: hci0 hci_power_off [bluetooth] <4>[ 1338.405113] task: ffff88022d5d6240 task.stack: ffffc900012bc000 <4>[ 1338.405116] RIP: 0010:check_flush_dependency+0xad/0x120 <4>[ 1338.405117] RSP: 0000:ffffc900012bfd30 EFLAGS: 00010086 <4>[ 1338.405119] RAX: 000000000000006e RBX: ffff880187c06a00 RCX: ffffffff8205fce8 <4>[ 1338.405120] RDX: 0000000000000001 RSI: 0000000000000086 RDI: 0000000000000097 <4>[ 1338.405120] RBP: ffffffffa0a1d1f0 R08: 0000000000000415 R09: ffffffff82728ee0 <4>[ 1338.405121] R10: 0000000000000000 R11: 0000000000000000 R12: ffff88022d5d6240 <4>[ 1338.405122] R13: ffff88022f428180 R14: ffffffff810a4470 R15: ffff88022a668bc8 <4>[ 1338.405124] FS: 0000000000000000(0000) GS:ffff88023bd00000(0000) knlGS:0000000000000000 <4>[ 1338.405125] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <4>[ 1338.405126] CR2: 00007f9c30394f80 CR3: 00000000964ae000 CR4: 00000000000006e0 <4>[ 1338.405127] Call Trace: <4>[ 1338.405137] flush_work+0x7c/0x1c0 <4>[ 1338.405140] ? flush_work+0x33/0x1c0 <4>[ 1338.405142] __cancel_work_timer+0xfa/0x170 <4>[ 1338.405147] ? kfree_skb+0x2e/0x90 <4>[ 1338.405150] btusb_close+0x1e/0xf0 [btusb] <4>[ 1338.405167] hci_dev_do_close+0x2ce/0x4e0 [bluetooth] <4>[ 1338.405186] ? hci_rx_work+0x36/0x360 [bluetooth] <4>[ 1338.405189] process_one_work+0x1da/0x400 <4>[ 1338.405192] worker_thread+0x2b/0x3f0 <4>[ 1338.405194] ? process_one_work+0x400/0x400 <4>[ 1338.405197] kthread+0x10d/0x130 <4>[ 1338.405199] ? kthread_create_worker_on_cpu+0x50/0x50 <4>[ 1338.405202] ret_from_fork+0x35/0x40 <4>[ 1338.405205] Code: 00 75 9a 49 8b 55 18 48 8d 8b b0 00 00 00 48 81 c6 b0 00 00 00 49 89 e8 48 c7 c7 b0 97 e3 81 c6 05 96 9f 08 01 01 e8 e3 bb 11 00 <0f> 0b e9 6b ff ff ff 65 48 8b 04 25 40 6c 01 00 f6 40 25 08 0f <4>[ 1338.405235] ---[ end trace 9266f8ffbf982a09 ]--- BT hardware and other dongles I use on this system: entropia@roadrunner:~> lsusb Bus 004 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 004 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0b05:17ba ASUSTek Computer, Inc. N10 Nano 802.11n Network Adapter [Realtek RTL8192CU] Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

08:16

New subject: [Bug 1163486] Pulseaudo Bluetooth profile setting broken in plasma 5

http://bugzilla.opensuse.org/show_bug.cgi?id=1163486 http://bugzilla.opensuse.org/show_bug.cgi?id=1163486#c11 --- Comment #11 from Stakanov Schufter --- (In reply to Takashi Iwai from comment #10)

...

(In reply to Stakanov Schufter from comment #9)

...
Update: after the installation I am getting also a complaint in the dmesg. As it might be related, I think it will be of interest (so this is with the fixes I installed as of indication): sudo dmesg -r (excerpt)

<4>[ 1338.404968] ------------[ cut here ]------------ <4>[ 1338.404980] WARNING: CPU: 2 PID: 934 at ../kernel/workqueue.c:2458 check_flush_dependency+0xad/0x120

This looks like a long-standing bug in btusb driver.

Can you trigger the bug at your will, or is it just intermittent?

For what I know (...and I know little, as I catch these things when I check and, of course, I have to admit I do not check always) it is more frequently presenting when suspending to disc. However it seems also randomly there so I wouldn't wager my boots on it, if you know what I mean. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

3 Apr 3 Apr

16:19

New subject: [Bug 1163486] Pulseaudo Bluetooth profile setting broken in plasma 5

http://bugzilla.opensuse.org/show_bug.cgi?id=1163486 http://bugzilla.opensuse.org/show_bug.cgi?id=1163486#c12 --- Comment #12 from Takashi Iwai --- OK, if you can trigger the problem at your will, it'd be great, we can have a better chance to fix it. Other than that, you can ignore it; this doesn't look too serious but rather a warning. Did you also update bluez-related packages from that repo, too? The connection and device enumeration issue might be rather a bluez problem. Also please check the setup rather with pavucontrol program (the package is the same name). In Configuration tab, you should be able to choose the BT device profile. FWIW, I created a repo containing a downstream version of pulseaudio BT module that supports more codecs like aptX, and also applied the downstream patches for HFP support. They are in OBS home:tiwai:bluetooth repo. If you're interested, give it a try. https://build.opensuse.org/project/show/home:tiwai:bluetooth -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16:27

New subject: [Bug 1163486] Pulseaudo Bluetooth profile setting broken in plasma 5

http://bugzilla.opensuse.org/show_bug.cgi?id=1163486 http://bugzilla.opensuse.org/show_bug.cgi?id=1163486#c13 --- Comment #13 from Stakanov Schufter --- (In reply to Takashi Iwai from comment #12)

...

OK, if you can trigger the problem at your will, it'd be great, we can have a better chance to fix it. Other than that, you can ignore it; this doesn't look too serious but rather a warning.

Did you also update bluez-related packages from that repo, too? The connection and device enumeration issue might be rather a bluez problem.

Also please check the setup rather with pavucontrol program (the package is the same name). In Configuration tab, you should be able to choose the BT device profile.

FWIW, I created a repo containing a downstream version of pulseaudio BT module that supports more codecs like aptX, and also applied the downstream patches for HFP support. They are in OBS home:tiwai:bluetooth repo. If you're interested, give it a try. https://build.opensuse.org/project/show/home:tiwai:bluetooth

I did update also the BT stack, but I will now change the repo to the one you indicated and try. I will also see that I have pavucontrol installed and use it. I will report then back here about the results. I will then try if I can trigger the bug. A word to all people here. I would like to take the occasion to thank everybody that continues to work on software bugs while real "bugs" make our life quite difficult currently. This is noted, noteworthy and I thank you all sincerely for this. Stay healthy. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

18:35

New subject: [Bug 1163486] Pulseaudo Bluetooth profile setting broken in plasma 5

http://bugzilla.opensuse.org/show_bug.cgi?id=1163486 http://bugzilla.opensuse.org/show_bug.cgi?id=1163486#c14 --- Comment #14 from Stakanov Schufter --- Ok, did change the BT stack. So the A2DP profile is really badly broken, the BT connects nicely but there is no way to get the profile to work. Either it jumps back to HSF. The sound quality is unusable. Now I get some error in dmesg while trying to set the profile that may be of interest.

...

From sudo dmesg:

[ 17.362046] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 17.362298] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt [ 17.365807] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 17.371776] kvm: disable TXT in the BIOS or activate TXT before enabling KVM [ 17.371779] kvm: disabled by bios [ 17.422365] kvm: disable TXT in the BIOS or activate TXT before enabling KVM [ 17.422367] kvm: disabled by bios [ 17.425011] snd_hda_codec_conexant hdaudioC0D0: CX20585: BIOS auto-probing. [ 17.425533] snd_hda_codec_conexant hdaudioC0D0: autoconfig for CX20585: line_outs=1 (0x1f/0x0/0x0/0x0/0x0) type:speaker [ 17.425536] snd_hda_codec_conexant hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 17.425538] snd_hda_codec_conexant hdaudioC0D0: hp_outs=2 (0x1c/0x19/0x0/0x0/0x0) [ 17.425539] snd_hda_codec_conexant hdaudioC0D0: mono: mono_out=0x0 [ 17.425540] snd_hda_codec_conexant hdaudioC0D0: inputs: [ 17.425542] snd_hda_codec_conexant hdaudioC0D0: Internal Mic=0x23 [ 17.425544] snd_hda_codec_conexant hdaudioC0D0: Mic=0x1b [ 17.425546] snd_hda_codec_conexant hdaudioC0D0: Dock Mic=0x1a [ 17.442989] input: HDA Intel MID Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10 [ 17.443073] input: HDA Intel MID Dock Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11 [ 17.443147] input: HDA Intel MID Dock Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12 [ 17.443223] input: HDA Intel MID Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13 [ 17.443294] input: HDA Intel MID HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14 [ 17.446315] iTCO_vendor_support: vendor-support=0 [ 17.447066] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [ 17.447131] iTCO_wdt: Found a QM57 TCO device (Version=2, TCOBASE=0x1060) [ 17.447218] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 17.448203] e1000e 0000:00:19.0 eth1: renamed from eth0 [ 17.635148] Adding 7950332k swap on /dev/mapper/system-swap. Priority:-1 extents:1 across:7950332k SSFS [ 17.740356] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: acl,user_xattr,data=ordered [ 18.262829] Bluetooth: Core ver 2.22 [ 18.262856] NET: Registered protocol family 31 [ 18.262858] Bluetooth: HCI device and connection manager initialized [ 18.262863] Bluetooth: HCI socket layer initialized [ 18.262867] Bluetooth: L2CAP socket layer initialized [ 18.262875] Bluetooth: SCO socket layer initialized [ 19.088827] usbcore: registered new interface driver btusb [ 19.102888] ip_tables: (C) 2000-2006 Netfilter Core Team [ 19.123628] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 19.157670] Ebtables v2.0 registered [ 19.197336] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 19.197338] Bluetooth: BNEP filters: protocol multicast [ 19.197343] Bluetooth: BNEP socket layer initialized [ 19.221623] nf_conntrack version 0.5.0 (65536 buckets, 262144 max) [ 19.224410] rtl8192cu: Chip version 0x10 [ 19.315112] Loading iSCSI transport class v2.0-870. [ 19.361924] rtl8192cu: Board Type 0 [ 19.362164] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1 [ 19.362236] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin [ 19.369772] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 19.371979] Bluetooth: RFCOMM TTY layer initialized [ 19.371985] Bluetooth: RFCOMM socket layer initialized [ 19.371992] Bluetooth: RFCOMM ver 1.11 [ 19.375032] ieee80211 phy0: Selected rate control algorithm 'rtl_rc' [ 19.375396] usbcore: registered new interface driver rtl8192cu [ 19.378715] Bridge firewalling registered [ 19.382444] usbcore: registered new interface driver rtl8xxxu [ 19.492772] Netfilter messages via NETLINK v0.30. [ 19.507675] ip_set: protocol 6 [ 19.963433] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [ 20.188275] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [ 20.225722] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 20.247914] rtl8192cu: MAC auto ON okay! [ 20.288794] rtl8192cu: Tx queue select: 0x05 [ 20.896269] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 20.926922] rtl8192cu: MAC auto ON okay! [ 20.960167] rtl8192cu: Tx queue select: 0x05 [ 21.611567] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 21.737498] NET: Registered protocol family 17 [ 21.779894] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 38.181815] rtl8192cu: MAC auto ON okay! [ 38.217183] rtl8192cu: Tx queue select: 0x05 [ 38.829766] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 69.003228] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 69.045574] rtl8192cu: MAC auto ON okay! [ 69.078311] rtl8192cu: Tx queue select: 0x05 [ 69.715295] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 70.755082] rtl8192cu: MAC auto ON okay! [ 70.788853] rtl8192cu: Tx queue select: 0x05 [ 71.429764] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 77.566809] wlan0: authenticate with 00:0b:3b:d1:30:4f [ 77.578512] wlan0: send auth to 00:0b:3b:d1:30:4f (try 1/3) [ 77.583100] wlan0: authenticated [ 77.583584] wlan0: associate with 00:0b:3b:d1:30:4f (try 1/3) [ 77.593860] wlan0: RX AssocResp from 00:0b:3b:d1:30:4f (capab=0x431 status=0 aid=1) [ 77.596104] wlan0: associated [ 77.596159] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 169.263692] fuse init (API version 7.26) [ 342.237633] input: SE-CL761BT (AVRCP) as /devices/virtual/input/input15 [ 429.694891] input: SE-CL761BT (AVRCP) as /devices/virtual/input/input16 [ 666.986664] Bluetooth: hci0: SCO packet for unknown connection handle 65 [ 666.986669] Bluetooth: hci0: SCO packet for unknown connection handle 65 [ 874.628375] input: SE-CL761BT (AVRCP) as /devices/virtual/input/input17 [ 973.794244] Bluetooth: hci0: SCO packet for unknown connection handle 63 [ 973.794248] Bluetooth: hci0: SCO packet for unknown connection handle 63 And from sudo journalctl -r apr 03 20:18:24 roadrunner.suse bluetoothd[1525]: Unable to get io data for Hands-Free Voice gateway: getpeernam> apr 03 20:18:24 roadrunner.suse rtkit-daemon[2164]: Supervising 0 threads of 0 processes of 1 users. apr 03 20:18:24 roadrunner.suse rtkit-daemon[2164]: Supervising 0 threads of 0 processes of 1 users. apr 03 20:18:24 roadrunner.suse rtkit-daemon[2164]: Supervising 0 threads of 0 processes of 1 users. apr 03 20:18:24 roadrunner.suse rtkit-daemon[2164]: Supervising 0 threads of 0 processes of 1 users. apr 03 20:18:24 roadrunner.suse rtkit-daemon[2164]: Supervising 0 threads of 0 processes of 0 users. apr 03 20:18:24 roadrunner.suse kernel: Bluetooth: hci0: SCO packet for unknown connection handle 63 apr 03 20:18:24 roadrunner.suse kernel: Bluetooth: hci0: SCO packet for unknown connection handle 63 -- You are receiving this mail because: You are on the CC list for the bug.