Bluetooth not working on Dell XPS 15 (Qualcomm Atheros QCA6174)

Bug #1782893 reported by Ákos Maróy
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Undecided
Unassigned
gnome-bluetooth (Ubuntu)
Undecided
Unassigned
linux (Ubuntu)
Medium
Unassigned

Bug Description

Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04.

expected behavior:

in Settings, one goes to the Bluetooth tab, slides the 'ON' button to 'ON', and then Bluetooth is enabled, and one can pair devices

what is happening:

in Settings, when clicking on the 'ON' button in the Bluetooth tab, it seems to turn on, that falls back to off

some relevant output:

$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetoothLinux
Linux dell-xps15 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
 Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter [1a56:1535]
 Kernel driver in use: ath10k_pci
 Kernel modules: ath10k_pci
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 138a:0091 Validity Sensors, Inc.
Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc.
Bus 001 Device 005: ID 0c45:6713 Microdia
Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 3.905518] Bluetooth: Core ver 2.22
[ 3.905532] Bluetooth: HCI device and connection manager initialized
[ 3.905534] Bluetooth: HCI socket layer initialized
[ 3.905536] Bluetooth: L2CAP socket layer initialized
[ 3.905539] Bluetooth: SCO socket layer initialized
[ 0.028000] Spectre V2 : Enabling Restricted Speculation for firmware calls
[ 0.068684] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 1.460567] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1)
[ 3.857792] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
[ 3.857799] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2
[ 3.860582] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: am 5501 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=2e64cf71-cb2d-491f-b8cd-fef8c3aeb582
InstallationDate: Installed on 2017-10-23 (272 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Dell Inc. XPS 15 9560
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=a991df19-cc0a-4108-b718-c90ef7113f52 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-23-generic N/A
 linux-backports-modules-4.15.0-23-generic N/A
 linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-06-20 (32 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/23/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.9.4
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please run this command to send us more information about the system:

  apport-collect 1782893

affects: bluez (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
Changed in bluez (Ubuntu):
status: New → Incomplete
Revision history for this message
Ákos Maróy (akos-maroy) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected bionic
description: updated
Revision history for this message
Ákos Maróy (akos-maroy) wrote : CRDA.txt

apport information

Revision history for this message
Ákos Maróy (akos-maroy) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Ákos Maróy (akos-maroy) wrote : IwConfig.txt

apport information

Revision history for this message
Ákos Maróy (akos-maroy) wrote : Lspci.txt

apport information

Revision history for this message
Ákos Maróy (akos-maroy) wrote : Lsusb.txt

apport information

Revision history for this message
Ákos Maróy (akos-maroy) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Ákos Maróy (akos-maroy) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Ákos Maróy (akos-maroy) wrote : ProcEnviron.txt

apport information

Revision history for this message
Ákos Maróy (akos-maroy) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Ákos Maróy (akos-maroy) wrote : ProcModules.txt

apport information

Revision history for this message
Ákos Maróy (akos-maroy) wrote : PulseList.txt

apport information

Revision history for this message
Ákos Maróy (akos-maroy) wrote : RfKill.txt

apport information

Revision history for this message
Ákos Maróy (akos-maroy) wrote : UdevDb.txt

apport information

Revision history for this message
Ákos Maróy (akos-maroy) wrote : WifiSyslog.txt

apport information

Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: Bluetooth not working on Dell XPS 15

Thanks. It appears you have a Qualcomm/Atheros Bluetooth adapter connected internally via USB.

The kernel has apparently found the adapter and loaded firmware for it. However the kernel also has it set to disabled:

0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
3: hci0: Bluetooth
 Soft blocked: yes <-------------
 Hard blocked: no

In a terminal please try running: rfkill unblock 3
Does that fix the problem?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

After running "rfkill unblock 3" please then run:

  rfkill list

and send us the output.

Changed in gnome-bluetooth (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Also, does the problem only occur after suspend/resume? Does it work on a fresh reboot?

Revision history for this message
Ákos Maróy (akos-maroy) wrote :

$ rfkill unblock 3
$ rfkill list
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
3: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

but the result is the same. I open the settings panel, go to the Bluetooth tab, try to turn it on, the switch shows 'ON', but nothing changes. going away from this tab and back will show the switch 'OFF'

is there a command line tool I can turn on & off?

yes, this is the effect on clean boot as well, not just after a reboot

Revision history for this message
Ákos Maróy (akos-maroy) wrote :

output after a clean boot:

$ rfkill list
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
1: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no
$ rfkill unblock 1
$ rfkill list
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
1: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

the effect with the settings panel is the same

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

"rfkill" is the command line tool and it is now enabled:

1: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

So if it's still not working for you then that sounds like a GUI bug, or a subtle driver/firmware bug.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Next, please try running "bluetoothctl" and then:

 list
 power on
 scan on

what output do you see?

Revision history for this message
Ákos Maróy (akos-maroy) wrote :
Download full text (3.9 KiB)

interestingly, bluez was not yet installed. after installing, I see:

$ bluetoothctl
[NEW] Controller 9C:B6:D0:FE:37:CA dell-xps15 [default]
Agent registered
[bluetooth]# list
Controller 9C:B6:D0:FE:37:CA dell-xps15 [default]
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller 9C:B6:D0:FE:37:CA Discovering: yes
[NEW] Device 48:22:B7:D2:B1:52 48-22-B7-D2-B1-52
[NEW] Device 6A:D9:FF:E8:DF:F9 6A-D9-FF-E8-DF-F9
[NEW] Device 44:CA:BD:00:6B:53 44-CA-BD-00-6B-53
[NEW] Device 4A:75:85:93:D4:F6 4A-75-85-93-D4-F6
...

and then it also shows devices on the Bluetooth tab in Settings. so this is great progress.

but not all is right. if I pair it with for example a Bluetooth headset, it seems to pair, the it's 'Connected' for a second, and then it won't ever connect.

this is the log:

[CHG] Device 70:26:05:87:EC:01 TxPower: 4
[CHG] Device 70:26:05:87:EC:01 Name: WH-1000XM2
[CHG] Device 70:26:05:87:EC:01 Alias: WH-1000XM2
[CHG] Device 70:26:05:87:EC:01 Class: 0x00240404
[CHG] Device 70:26:05:87:EC:01 Icon: audio-card
[CHG] Device 70:26:05:87:EC:01 Modalias: usb:v054Cp0C67d0105
[CHG] Device 70:26:05:87:EC:01 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 0000110d-0000-1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 00001131-0000-1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 0000110f-0000-1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 00000000-deca-fade-deca-deafdecacaff
[CHG] Device 48:22:B7:D2:B1:52 RSSI: -68
[CHG] Device 48:22:B7:D2:B1:52 ManufacturerData Key: 0x004c
[CHG] Device 48:22:B7:D2:B1:52 ManufacturerData Value:
  10 02 07 00 ....
[CHG] Device 7C:58:67:01:4A:D2 RSSI: -75
[CHG] Device 7C:58:67:01:4A:D2 ManufacturerData Key: 0x004c
[CHG] Device 7C:58:67:01:4A:D2 ManufacturerData Value:
  0c 0e 08 6b c0 31 b0 2f e1 f1 ca 34 92 c6 17 b5 ...k.1./...4....
[CHG] Device 48:22:B7:D2:B1:52 RSSI: -60
[CHG] Device 6A:D9:FF:E8:DF:F9 RSSI: -60
[CHG] Device 70:26:05:87:EC:01 TxPower: -13
[CHG] Device 70:26:05:87:EC:01 Name: LE_WH-1000XM2
[CHG] Device 70:26:05:87:EC:01 Alias: LE_WH-1000XM2
[CHG] Device 44:CA:BD:00:6B:53 RSSI: -76
[CHG] Device 70:26:05:87:EC:01 RSSI: -56
[CHG] Device 70:26:05:87:EC:01 TxPower: 4
[CHG] Device 70:26:05:87:EC:01 Name: WH-1000XM2
[CHG] Device 70:26:05:87:EC:01 Alias: WH-1000XM2
[CHG] Device 70:26:05:87:EC:01 Connected: yes
[CHG] Device 70:26:05:87:EC:01 Modalias: usb:v054Cp0C67d0201
[CHG] Device 70:26:05:87:EC:01 UUIDs: 00000000-deca-fade-deca-deafdecacaff
[CHG] Device 70:26:05:87:EC:01 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] D...

Read more...

Revision history for this message
Ákos Maróy (akos-maroy) wrote :

doing the pairing from bluetoothctl gets the same result:

# pair 70:26:05:87:EC:01
Attempting to pair with 70:26:05:87:EC:01
[CHG] Device 70:26:05:87:EC:01 Connected: yes
[CHG] Device 70:26:05:87:EC:01 Name: WH-1000XM2
[CHG] Device 70:26:05:87:EC:01 Alias: WH-1000XM2
[CHG] Device 70:26:05:87:EC:01 Modalias: usb:v054Cp0C67d0201
[CHG] Device 70:26:05:87:EC:01 UUIDs: 00000000-deca-fade-deca-deafdecacaff
[CHG] Device 70:26:05:87:EC:01 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 7b265b0e-2232-4d45-bef4-bb8ae62f813d
[CHG] Device 70:26:05:87:EC:01 UUIDs: 81c2e72a-0591-443e-a1ff-05f988593351
[CHG] Device 70:26:05:87:EC:01 UUIDs: 96cc203e-5068-46ad-b32d-e316f5e069ba
[CHG] Device 70:26:05:87:EC:01 UUIDs: b9b213ce-eeab-49e4-8fd9-aa478ed1b26b
[CHG] Device 70:26:05:87:EC:01 UUIDs: f8d1fbe4-7966-4334-8024-ff96c9330e15
[CHG] Device 70:26:05:87:EC:01 ServicesResolved: yes
[CHG] Device 70:26:05:87:EC:01 Paired: yes
Pairing successful
[CHG] Device 7C:58:67:01:4A:D2 ManufacturerData Key: 0x004c
[CHG] Device 7C:58:67:01:4A:D2 ManufacturerData Value:
  0c 0e 08 77 c0 24 1e a5 80 d6 8e f5 7b f3 0e b6 ...w.$......{...
[CHG] Device 70:26:05:87:EC:01 RSSI: -67
[CHG] Device 70:26:05:87:EC:01 Name: LE_WH-1000XM2
[CHG] Device 70:26:05:87:EC:01 Alias: LE_WH-1000XM2
[CHG] Device 4C:47:D2:36:C9:32 RSSI: -50
[CHG] Device 70:26:05:87:EC:01 ServicesResolved: no
[CHG] Device 70:26:05:87:EC:01 Connected: no

trying to connect manually:

# connect 70:26:05:87:EC:01
Attempting to connect to 70:26:05:87:EC:01
Failed to connect: org.bluez.Error.Failed

might it be that the Settings panel Bluetooth thing interferes with the bluetoothctl stack?

Revision history for this message
Ákos Maróy (akos-maroy) wrote :
Download full text (5.5 KiB)

on a second try pairing, this is what I get:

# pair 70:26:05:87:EC:01
Attempting to pair with 70:26:05:87:EC:01
[CHG] Device 70:26:05:87:EC:01 Connected: yes
[NEW] Primary Service
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service0001
 00001801-0000-1000-8000-00805f9b34fb
 Generic Attribute Profile
[NEW] Characteristic
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service0001/char0002
 00002a05-0000-1000-8000-00805f9b34fb
 Service Changed
[NEW] Descriptor
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service0001/char0002/desc0004
 00002902-0000-1000-8000-00805f9b34fb
 Client Characteristic Configuration
[NEW] Primary Service
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service000a
 69a7f243-e52f-4443-a7f9-cb4d053c74d6
 Vendor specific
[NEW] Characteristic
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service000a/char000b
 be8692b1-3b29-410d-94d3-50281940553e
 Vendor specific
[NEW] Characteristic
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service000a/char000d
 3f92019d-ac1d-48dc-9d94-86a0fb507591
 Vendor specific
[NEW] Descriptor
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service000a/char000d/desc000f
 00002902-0000-1000-8000-00805f9b34fb
 Client Characteristic Configuration
[NEW] Characteristic
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service000a/char0010
 5bc06a57-f84d-4086-a65a-2a238cb39cdb
 Vendor specific
[NEW] Descriptor
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service000a/char0010/desc0012
 00002902-0000-1000-8000-00805f9b34fb
 Client Characteristic Configuration
[NEW] Characteristic
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service000a/char0013
 99c3f043-8431-40e9-9802-850114e4c0d1
 Vendor specific
[NEW] Primary Service
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service0015
 fe59bfa8-7fe3-4a05-9d94-99fadc69faff
 Vendor specific
[NEW] Characteristic
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service0015/char0016
 104c022e-48d6-4dd2-8737-f8ac5489c5d4
 Vendor specific
[NEW] Characteristic
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service0015/char0018
 69745240-ec29-4899-a2a8-cf78fd214303
 Vendor specific
[NEW] Descriptor
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service0015/char0018/desc001a
 00002902-0000-1000-8000-00805f9b34fb
 Client Characteristic Configuration
[NEW] Characteristic
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service0015/char001b
 70efdf00-4375-4a9e-912d-63522566d947
 Vendor specific
[NEW] Descriptor
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service0015/char001b/desc001d
 00002902-0000-1000-8000-00805f9b34fb
 Client Characteristic Configuration
[NEW] Characteristic
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service0015/char001e
 eea2e8a0-89f0-4985-a1e2-d91dc4a52632
 Vendor specific
[NEW] Characteristic
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service0015/char0020
 a79e2bd1-d6e4-4d1e-8b4f-141d69011cbb
 Vendor specific
[NEW] Primary Service
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service0022
 91c10d9c-aaef-42bd-b6d6-8a648c19213d
 Vendor specific
[NEW] Characteristic
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service0022/char0023
 99d1064e-4517-46aa-8fb4-6be64dd1a1f1
 Vendor specific
[NEW] Descriptor
 /org/bluez/hci0/dev_70_26_05_87_EC_01/service0022/char0023/desc0025
 00002902-0000-1000-8000-00805f9b34fb
 Client Characteristic Configuration
[NEW] Characteristic
 /org/bluez/hci0/dev_70_26_05_87_EC...

Read more...

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Did it ever work at all in 18.04? Do you suppose a recent update broke it?

Next, maybe try installing a very new kernel to see if that makes it more stable:
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

Or even try older kernels if that doesn't work.

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key
Revision history for this message
Jeremy (wa113y3s) wrote :

Try
sudo apt install pulseaudio-module-bluetooth
pactl load-module module-bluetooth-discover

Then see if you can connect to the headset

Revision history for this message
Ákos Maróy (akos-maroy) wrote :

thanks, this seems to make it work

now the only strange thing seems to be that the volume control doesn't work, but I guess that's a different issue / topic

so: why did this not work out of the box?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Ubuntu does those steps out-of-the-box already. You will find pulseaudio-module-bluetooth installed by default, and module-bluetooth-discover is loaded by default.

So if the steps in comment #28 helped then I imagine that maybe module-bluetooth-discover is not searching often enough. That may be a bug in PulseAudio (module-bluetooth-discover), or it may be a bug in BlueZ.

Revision history for this message
Jeremy (wa113y3s) wrote :

Daniel, I have to think something failed during install as I have never had to install Bluez

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Yes the original reporter appears to have upgraded from 16.04 to 18.04. Maybe the required packages didn't get installed with the upgrade.

summary: - Bluetooth not working on Dell XPS 15
+ Bluetooth not working on Dell XPS 15 (Qualcomm Atheros QCA6174)
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for bluez (Ubuntu) because there has been no activity for 60 days.]

Changed in bluez (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-bluetooth (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-bluetooth (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers