gnome-control-center says "no bluetooth found" even though bluetooth is present and somewhat usable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center (Ubuntu) |
New
|
Low
|
Unassigned |
Bug Description
I am running bionic and the gnome-control-
I believe I am seeing what's being discussed at http://
$ ll /dev/rfkill
crw-rw-r--+ 1 root root 10, 62 Mai 29 17:19 /dev/rfkill
$ bluetoothctl
[NEW] Controller 3C:77:E6:EC:91:4E work [default]
[NEW] Device 20:A9:0E:1B:1B:84 alcatel POP 4
Agent registered
[bluetooth]# show
Controller 3C:77:E6:EC:91:4E (public)
Name: work
Alias: work
Class: 0x0010010c
Powered: yes
Pairable: yes
UUID: Generic Attribute Profile (00001801-
UUID: A/V Remote Control (0000110e-
UUID: OBEX File Transfer (00001106-
UUID: Generic Access Profile (00001800-
UUID: OBEX Object Push (00001105-
UUID: PnP Information (00001200-
UUID: IrMC Sync (00001104-
UUID: A/V Remote Control Target (0000110c-
UUID: Vendor specific (00005005-
UUID: Message Notification Se.. (00001133-
UUID: Phonebook Access Server (0000112f-
UUID: Message Access Server (00001132-
Modalias: usb:v1D6Bp0246d0530
$ rfkill list all
0: tpacpi_
Soft blocked: no
Hard blocked: no
1: tpacpi_wwan_sw: Wireless WAN
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
30: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
This is what I see in /var/log/syslog when trying to send a file from a paired phone.
Jun 9 22:01:24 work obexd[18062]: CONNECT(0x0), (null)(0xffffffff)
Jun 9 22:01:24 work obexd[18062]: CONNECT(0x0), (null)(0x0)
Jun 9 22:01:24 work obexd[18062]: PUT(0x2), (null)(0xffffffff)
Jun 9 22:01:24 work obexd[18062]: PUT(0x2), FORBIDDEN(0x43)
Jun 9 22:01:24 work obexd[18062]: DISCONNECT(0x1), (null)(0xffffffff)
Jun 9 22:01:24 work obexd[18062]: DISCONNECT(0x1), SUCCESS(0x20)
Jun 9 22:01:24 work obexd[18062]: disconnected: Transport got disconnected
Jun 9 22:01:24 work bluetoothd[17556]: Unable to get io data for Object Push: getpeername: Transport endpoint is not connected (107)
Thank you for your bug report, what's the output of 'bluetoothctl'