Year: 2020

Archduke Wilhelm of Austria

Jovan Stosic August 28, 2020

Archduke Wilhelm Franz of Austria, later Wilhelm Franz von Habsburg-Lothringen (10 February 1895 – 18 August 1948), also known as Vasyl Vyshyvani (Ukrainian: Василь Вишиваний, romanized: Vasyl Vyshyvani), was an Austrian archduke, a colonel of the Ukrainian Sich Riflemen,[citation needed] and a poet.

https://en.m.wikipedia.org/wiki/Archduke_Wilhelm_of_Austria

Archduke Wilhelm of Austria was last modified: August 28th, 2020 by Jovan Stosic

ESP8266 Pinout Reference: Which GPIO pins should you use?

Jovan Stosic August 26, 2020
Label GPIO Input Output Notes
D0 GPIO16 no interrupt no PWM or I2C support HIGH at boot
used to wake up from deep sleep
D1 GPIO5 OK OK often used as SCL (I2C)
D2 GPIO4 OK OK often used as SDA (I2C)
D3 GPIO0 pulled up OK connected to FLASH button, boot fails if pulled LOW
D4 GPIO2 pulled up OK HIGH at boot
connected to on-board LED, boot fails if pulled LOW
D5 GPIO14 OK OK SPI (SCLK)
D6 GPIO12 OK OK SPI (MISO)
D7 GPIO13 OK OK SPI (MOSI)
D8 GPIO15 pulled to GND OK SPI (CS)
Boot fails if pulled HIGH
RX GPIO3 OK RX pin HIGH at boot
TX GPIO1 TX pin OK HIGH at boot
debug output at boot, boot fails if pulled LOW
A0 ADC0 Analog Input X

Source: ESP8266 Pinout Reference: Which GPIO pins should you use? | Random Nerd Tutorials

ESP8266 Pinout Reference: Which GPIO pins should you use? was last modified: August 26th, 2020 by Jovan Stosic

Crimean War

Jovan Stosic August 25, 2020

The Crimean War was a military conflict fought from October 1853 to February 1856 in which Russia lost to an alliance made up of the Ottoman Empire, the United Kingdom, Sardinia and France. The immediate cause of the war involved the rights of Christian minorities in the Holy Land, which was a part of the Ottoman Empire. The French promoted the rights of Roman Catholics, while Russia promoted those of the Eastern Orthodox Church. The longer-term causes involved the decline of the Ottoman Empire and the unwillingness of Britain and France to allow Russia to gain territory and power at the Ottoman Empire’s expense. It has widely been noted that the causes, in one case involving an argument over the keys to the Church of the Nativity, revealed a “great confusion of purpose”, yet they led to a war noted for its “notoriously incompetent international butchery”.

https://en.m.wikipedia.org/wiki/Crimean_War

Crimean War was last modified: August 25th, 2020 by Jovan Stosic

18.04 – Blueman Protocol not available

Jovan Stosic August 23, 2020

Today my bluetooth headset stopped working. I haven’t modified anything recently (although a few days ago I was trying to get a bluetooth headset to automatically connect in a2dp mode, which involved installing blueman and re-pairing with it, but I’ve connected and rebooted several times since making that change and everything was working).

Now when I try to connect the headset I get:

Connection Failed: blueman.bluez.errors.DBusFailedError: Protocol Not available

Based on a few things from here (Bluetooth – Connection Failed: blueman.bluez.errors.DBusFailedError: Protocol Not available) and other Internet searches, I’ve tried:

$ sudo apt-get install pulseaudio-module-bluetooth
$ pactl load-module module-bluetooth-discover

And I’ve tried reinstalling things:

$ sudo apt-get --purge --reinstall install bluetooth bluez blueman pulseaudio pulseaudio-module-bluetooth
$ sudo /etc/init.d/networking restart
    [ ok ] Restarting networking (via systemctl): networking.service.
$ sudo /etc/init.d/bluetooth restart
    [ ok ] Restarting bluetooth (via systemctl): bluetooth.service.

And of course rebooting, but nothing seems to help, and I can’t figure out what protocol it’s talking about, since I can see the headset and pair with it, but not make an audio connection.

I’m running Ubuntu 18.04.1. Some other details:

$ dpkg -l | grep blue
    blueman                            2.0.5-1ubuntu1    
    bluetooth                          5.48-0ubuntu3.1
    bluez                              5.48-0ubuntu3.1
    bluez-cups                         5.48-0ubuntu3.1
    bluez-obexd                        5.48-0ubuntu3.1
    gir1.2-gnomebluetooth-1.0:amd64    3.28.0-2ubuntu0.1
    gnome-bluetooth                    3.28.0-2ubuntu0.1
    indicator-bluetooth                0.0.6+17.10.20170605-0ubuntu3                
    libbluetooth3:amd64                5.48-0ubuntu3.1                              
    libgnome-bluetooth13:amd64         3.28.0-2ubuntu0.1
    pulseaudio-module-bluetooth        1:11.1-1ubuntu7.1

$ sudo service bluetooth status
* bluetooth.service - Bluetooth service    Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset    Active: active (running) since Mon 2019-02-04 14:36:47 PST; 1min 13s ago
     Docs: man:bluetoothd(8)  Main PID: 6912 (bluetoothd)    Status: "Running"
    Tasks: 1 (limit: 4915)    CGroup: /system.slice/bluetooth.service
           └─6912 /usr/lib/bluetooth/bluetoothd

Feb 04 14:36:47 AVB systemd[1]: Starting Bluetooth service... Feb 04 14:36:47 AVB bluetoothd[6912]: Bluetooth daemon 5.48 Feb 04 14:36:47 AVB systemd[1]: Started Bluetooth service. Feb 04 14:36:47 AVB bluetoothd[6912]: Starting SDP server Feb 04 14:36:47 AVB bluetoothd[6912]: Bluetooth management interface 1.14 initialized

$ dmesg | grep Bluetooth
    [    5.197632] Bluetooth: Core ver 2.22
    [    5.197654] Bluetooth: HCI device and connection manager initialized
    [    5.197657] Bluetooth: HCI socket layer initialized
    [    5.197660] Bluetooth: L2CAP socket layer initialized
    [    5.197664] Bluetooth: SCO socket layer initialized
    [    5.349217] Bluetooth: hci0: Firmware revision 0.1 build 185 week 49 2017
    [    5.492623] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [    5.492625] Bluetooth: BNEP filters: protocol multicast
    [    5.492628] Bluetooth: BNEP socket layer initialized
    [   16.972106] Bluetooth: RFCOMM TTY layer initialized
    [   16.972113] Bluetooth: RFCOMM socket layer initialized
    [   16.972117] Bluetooth: RFCOMM ver 1.11
    [   84.672241] Bluetooth: hci0: last event is not cmd complete (0x0f)

$ hciconfig
    hci0:    Type: Primary  Bus: USB
    BD Address: 74:70:FD:B6:73:0C  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN ISCAN INQUIRY
    RX bytes:18753 acl:61 sco:0 events:738 errors:0
    TX bytes:14257 acl:60 sco:0 commands:267 errors:0

$ lspci -knn | grep Net -A3
    02:00.0 Network controller [0280]: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
    Subsystem: Intel Corporation Dual Band Wireless-AC 8265 [8086:0010]
    Kernel driver in use: iwlwifi
    Kernel modules: iwlwifi

$ lsusb
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 003: ID 8087:0a2b Intel Corp.
    Bus 001 Device 002: ID 13d3:5a07 IMC Networks
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ ps aux | grep blue
    me        2032  0.0  0.6 694048 54240 tty2     Sl+  14:19   0:01 /usr/bin/python3 /usr/bin/blueman-applet
    me        2091  0.0  0.0  82728  6832 ?        Ss   14:19   0:00 /usr/lib/bluetooth/obexd
    root      6912  0.0  0.0  37992  6096 ?        Ss   14:36   0:02 /usr/lib/bluetooth/bluetoothd

Any suggestions on where to look next? Thanks.

 
share  improve this question  
  • 3
    I might have solved this myself. “sudo apt install pulseaudio-module-bluetooth” and then restarting pulse audio (“pulseaudio -k” “pulseaudio –start”) and the error goes away. I still have no idea why this is necessary or what the error originally meant. – M. P. Feb 5 ’19 at 17:53

2 Answers

ActiveOldestVotes

20

For me just reloading the module by executing:

pactl unload-module module-bluetooth-discover
pactl load-module module-bluetooth-discover

helped solving the issue.

share  improve this answer  
  • 4
    Works with 19.04 too. The module must be unloaded first pactl unload-module module-bluetooth-discover. – Vladimir Botka Oct 4 ’19 at 14:59
  • This is the only thing that worked for me with my Bose 700 headphones using blueman on cinnamon. Didn’t even have to restart bluetooth service and didn’t have to run the commands above as root. – Plasty Grove Jul 28 at 2:56

1

Just delete the device on bluetooth manager and pair again. Works for me.

share  improve this answer  

Source: 18.04 – Blueman Protocol not available – Ask Ubuntu

18.04 – Blueman Protocol not available was last modified: August 23rd, 2020 by Jovan Stosic