Could you include the journalctl log from around the time of the issue?
Also start 'G_DEBUG_MESSAGES=all gnome-control-center bluetooth' from a
command line and see what info are printed?
** Changed in: gnome-control-center (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1776000
Title:
gnome-control-center says "no bluetooth found" even though bluetooth
is present and somewhat usable
Status in gnome-control-center package in Ubuntu:
Incomplete
Bug description:
I am running bionic and the gnome-control-center on the bluetooth tab
tells me that "no bluetooth found" and that I should plug in a dongle
to use bluetooth. My computer has built-in bluetooth.
I believe I am seeing what's being discussed at http://gnome-
apps.13852.n7.nabble.com/No-Bluetooth-Found-Plug-in-a-dongle-to-use-
Bluetooth-td68467.html especially the message by Bjørn Forsman, dated
Dec 31 2016.
$ 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
Discoverable: yes
Pairable: yes
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: IrMC Sync (00001104-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00005005-0000-1000-8000-0002ee000001)
UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0530
Discovering: yes
$ rfkill list all
0: tpacpi_bluetooth_sw: Bluetooth
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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1776000/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
