Blutooth doesnt work

[sisqonrw]

Hi have used some month Emmabuntüs Debian Edition 4. The Bluetooth dongle and bluetooth has worked direcly and where fine.
now i have installed Edition 5 now Bluetooth does not work. what can i do? thanks

[alain-tux]

Hello Sysqonrw.
What does the following codes return?

Code: [Sélectionner]

rfkill listand:

Code: [Sélectionner]

inxi -nzIs wifi OK?

[sisqonrw]

Hi
WLAN works fine.

Code: [Sélectionner]

rfkill list
0: acer-wireless: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
5: hci1: Bluetooth
        Soft blocked: no
        Hard blocked: no


Code: [Sélectionner]

inxi -nz
Network:
  Device-1: Intel PRO/Wireless 3945ABG [Golan] Network
    driver: iwl3945
  IF: wlp3s0 state: up mac: <filter>
  Device-2: Broadcom NetLink BCM5789 Gigabit Ethernet PCI
    Express driver: tg3
  IF: enp4s0 state: down mac: <filter>


[sisqonrw]

did you see something? What could be wrong? thanks

[alain-tux]

There is nothing wrong in your feedback.
 What happens when you try to start the bluetooth?
Can you describe what is going on, if there are error messages or other information. Thanks.

[sisqonrw]

on the Edition 4 there was a symbol of my headphone after search. i could connect it and trust it, etc.
but on the Edition 5 he can not find the same bluetooth headphone.
it is the same notebook, headphone, bluetooth dongle, etc.
i want to use bluetooth with my headphone. it is important for me.
what can i do?

[alain-tux]

Did you put your headphones in search of Bluetooth before pressing search (Suche)?
I don't know your headphones, but on mine, a Sony, after going from Emmade4 to 5,
I had to pair it again by pressing the button on for 7s then when I heard "pairing" Do "search" (suche) and it appeared.
It can be long and even exceed the time or headphones is in pairing mode. In this case you have to start the operation
again until the headphones appear in the window.
Then right click on the headphones and "connect".

If you've already done this procedure, then there is a problem either on your Dongle BT or on the headphones.
The dongle seems to work according to your feedback.
But we can make sure with: Bluetoothctl

[sisqonrw]

I always look for the headphones from the notebook and not the other way around.
I've done that 100 times. As I said, it always worked that way with Edition 4.

i am getting this error report:

Code: [Sélectionner]

Bluetoothctl
bash: /usr/bin/python: Datei oder Verzeichnis nicht gefunden

[alain-tux]

Sorry    It's not Bluetoothctl, but bluetoothctl.

Code: [Sélectionner]

bluetoothctl
Then you get this:

Code: [Sélectionner]

alain@helene-victus:~$ bluetoothctl
Agent registered
[bluetooth]#
Next just after # do:

Code: [Sélectionner]

list
If there is a Bluetooth Operationel controller you will have a feedback like this:

Code: [Sélectionner]

[bluetooth]# list
Controller 14:13:33:23:47:20 helene-victus [default]
Notes the number and write this:

Code: [Sélectionner]

show "your number"
without the ""


And give us the complete return of command .

[sisqonrw]

that is no problem.

Code: [Sélectionner]

bluetoothctl
Agent registered
[bluetooth]# list
Controller 00:0C:78:30:3C:9F salseroo [default]
[bluetooth]# show your number
Too many arguments: 2 > 1


[alain-tux]

There is a problem. Your number is 00: 0C: 78: 30: 3C: 9F and not "your number".
So the command is:

Code: [Sélectionner]

show 00: 0C: 78: 30: 3C: 9Fexplaination:
list : to know the number of BT adaptator
show :  (the number of adaptator) to show information about it

[sisqonrw]

is this now correct?

Code: [Sélectionner]

bluetoothctl
Agent registered
[bluetooth]# list
Controller 00:0C:78:30:3C:9F salseroo [default]
[bluetooth]# show 00:0C:78:30:3C:9F
Controller 00:0C:78:30:3C:9F (public)
        Name: salseroo-aspire5670
        Alias: salseroo
        Class: 0x00000000
        Powered: no
        Discoverable: yes
        DiscoverableTimeout: 0x00000000
        Pairable: yes
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
        UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
        UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
        UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
        UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v1D6Bp0246d0542
        Discovering: no


Code: [Sélectionner]

bluetoothctl
Agent registered
[bluetooth]# list
Controller 00:0C:78:30:3C:9F salseroo [default]
[bluetooth]# show 00:0C:78:30:3C:9F
Controller 00:0C:78:30:3C:9F (public)
        Name: salseroo-aspire5670
        Alias: salseroo
        Class: 0x007c0000
        Powered: yes
        Discoverable: yes
        DiscoverableTimeout: 0x00000000
        Pairable: yes
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
        UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
        UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
        UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
        UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v1D6Bp0246d0542
        Discovering: no

[alain-tux]

Yes it's correct 
Your Bluetooth controller (adaptator) is correct too. it's run well.

Maybe there is a problem with the headphones? But there I cannot help you ...

Always after:
[Bluetooth]#
What return:

Code: [Sélectionner]

devices
like this :

Code: [Sélectionner]

[bluetooth]# devices
Device 30:53:C1:06:96:EA WH-CH510
[bluetooth]#

[sisqonrw]

Hi i can connet the headphone with an windows notebook and mobile phone. the headphone is working.

Code: [Sélectionner]

bluetoothctl
Agent registered
[CHG] Controller 00:0C:78:30:3C:9F Pairable: yes
[bluetooth]# devices
Device A0:E9:DB:53:51:70 A0-E9-DB-53-51-70


[alain-tux]

All right.
headphone is well seen by Bluetooth so everything works well.

But your answer: "i can connet the headphone with a windows notebook and mobile phone. the headset is working."
Made me think that if your headphone is paired to another device, it does not allow pairing on the Linux device. It is certainly occupied by another device(s) and cannot be used by EmmaDE.

Stops all Bluetooth, Windows, notebook and mobile phones.
Then try pairing again on Linux.