Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

One can't proceed from the informal to the formal by formal means.

computers / alt.os.linux.mint / Re: Terminal issues and Bluetooth

SubjectAuthor
* Terminal issues and BluetoothJeff Layman
`* Re: Terminal issues and BluetoothPaul
 `- Re: Terminal issues and BluetoothJeff Layman

1
Terminal issues and Bluetooth

<t3jd6v$ngs$1@dont-email.me>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=3461&group=alt.os.linux.mint#3461

  copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: jmlay...@invalid.invalid (Jeff Layman)
Newsgroups: alt.os.linux.mint
Subject: Terminal issues and Bluetooth
Date: Mon, 18 Apr 2022 11:06:23 +0100
Organization: A noiseless patient Spider
Lines: 132
Message-ID: <t3jd6v$ngs$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 18 Apr 2022 10:06:23 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="a2e0faf28e30532696ef6b7627bc76f3";
logging-data="24092"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+Sn39XfJ+8Z6nPyatPtcAj1zYA18k22LE="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Thunderbird/91.7.0
Cancel-Lock: sha1:OM1JTfDpvavn71z9KAaGeSLjGjY=
Content-Language: en-GB
 by: Jeff Layman - Mon, 18 Apr 2022 10:06 UTC

20.3 Cinnamon 5.2.7

As I might have a need for Bluetooth in future, I decided to have a look
at it. Running "Bluetooth" from the menu showed that my laptop
(jeff-P15xEMx - see below) was available for file transfers. But it also
showed a device as "Not set up" under devices. This appears to be a Sony
TV which I don't have! I searched on 'mint Bluetooth device unknown',
and found a hit at <https://forums.linuxmint.com/viewtopic.php?t=330340>
which wasn't "SOVLED" (sic)!

A bit more searching led me to try sudo systemctl status Bluetooth in a
terminal. This is the result (sorry about the length):

============================================
jeff@jeff-P15xEMx:~$ sudo systemctl status bluetooth
[sudo] password for jeff:
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled;
vendor pre>
Active: active (running) since Mon 2022-04-18 08:27:22 BST; 36min ago
Docs: man:bluetoothd(8)
Main PID: 709 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 9310)
Memory: 2.4M
CGroup: /system.slice/bluetooth.service
└─709 /usr/lib/bluetooth/bluetoothd

Apr 18 08:27:22 jeff-P15xEMx systemd[1]: Started Bluetooth service.
Apr 18 08:27:22 jeff-P15xEMx bluetoothd[709]: Bluetooth management
interface 1.>
Apr 18 08:27:26 jeff-P15xEMx bluetoothd[709]: Failed to set mode:
Blocked throu>
Apr 18 08:27:52 jeff-P15xEMx bluetoothd[709]: Endpoint registered:
sender=:1.35>
Apr 18 08:27:52 jeff-P15xEMx bluetoothd[709]: Endpoint registered:
sender=:1.35>
Apr 18 08:31:22 jeff-P15xEMx bluetoothd[709]: Endpoint unregistered:
sender=:1.>
Apr 18 08:31:22 jeff-P15xEMx bluetoothd[709]: Endpoint unregistered:
sender=:1.>
Apr 18 08:31:23 jeff-P15xEMx bluetoothd[709]: Endpoint registered:
sender=:1.48>
Apr 18 08:31:23 jeff-P15xEMx bluetoothd[709]: Endpoint registered:
sender=:1.48>
Apr 18 08:50:22 jeff-P15xEMx bluetoothd[709]: Failed to set mode:
Blocked throu>
lines 1-21/21 (END)...skipping...
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled;
vendor preset: enabled)
Active: active (running) since Mon 2022-04-18 08:27:22 BST; 36min ago
Docs: man:bluetoothd(8)
Main PID: 709 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 9310)
Memory: 2.4M
CGroup: /system.slice/bluetooth.service
└─709 /usr/lib/bluetooth/bluetoothd

Apr 18 08:27:22 jeff-P15xEMx systemd[1]: Started Bluetooth service.
Apr 18 08:27:22 jeff-P15xEMx bluetoothd[709]: Bluetooth management
interface 1.14 initialized
Apr 18 08:27:26 jeff-P15xEMx bluetoothd[709]: Failed to set mode:
Blocked through rfkill (0x12)
Apr 18 08:27:52 jeff-P15xEMx bluetoothd[709]: Endpoint registered:
sender=:1.35 path=/MediaEndpoint/A2DPSink/sbc
Apr 18 08:27:52 jeff-P15xEMx bluetoothd[709]: Endpoint registered:
sender=:1.35 path=/MediaEndpoint/A2DPSource/sbc
Apr 18 08:31:22 jeff-P15xEMx bluetoothd[709]: Endpoint unregistered:
sender=:1.35 path=/MediaEndpoint/A2DPSink/sbc
Apr 18 08:31:22 jeff-P15xEMx bluetoothd[709]: Endpoint unregistered:
sender=:1.35 path=/MediaEndpoint/A2DPSource/sbc
Apr 18 08:31:23 jeff-P15xEMx bluetoothd[709]: Endpoint registered:
sender=:1.48 path=/MediaEndpoint/A2DPSink/sbc
Apr 18 08:31:23 jeff-P15xEMx bluetoothd[709]: Endpoint registered:
sender=:1.48 path=/MediaEndpoint/A2DPSource/sbc
Apr 18 08:50:22 jeff-P15xEMx bluetoothd[709]: Failed to set mode:
Blocked through rfkill (0x12)
~ ~
~ ~
~ ~
~ ~
~ ~
~ ~
~ ~
~ ~
~ ~
lines 1-21/21 (END)

============================================

I then tried the following:

Typing "exit" shows "No next tag (press RETURN)". Pressing RETURN cycles
back to the "lines 1-21/21 (END)"

Typing Ctrl-C gets back to the prompt.

Typing Shift-ctrl-Q gets:
"Close this terminal?
There is still a process running in this terminal. Closing the terminal
will kill it
(Cancel/Close terminal)"

I am very ignorant when it comes to a terminal, so can someone please
explain what's going on here?
Why is the command apparently executed twice, with the first 10 lines
starting with "Apr 18 08:27:22 jeff-P15xEMx" incomplete and truncated
with a > the first time they appear?
Why are they apparently complete the second time they appear? The line
ending "Failed to set mode: Blocked through rfkill (0x12)" is in red
each time it appears.
Why the 18 lines of tildes (~)?

What next to try? In the Mint Forum there seem to be lots of questions
about Bluetooth. Would it make sense to wait for 21.0 as there's no
urgency for me to use it now:
<https://www.omgubuntu.co.uk/2022/03/linux-mint-is-making-a-major-bluetooth-change>

--

Jeff

Re: Terminal issues and Bluetooth

<t3ppa0$qle$1@gioia.aioe.org>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=3512&group=alt.os.linux.mint#3512

  copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!aioe.org!YpgQ0RW05rxPQLn9OTMxZA.user.46.165.242.75.POSTED!not-for-mail
From: nos...@needed.invalid (Paul)
Newsgroups: alt.os.linux.mint
Subject: Re: Terminal issues and Bluetooth
Date: Wed, 20 Apr 2022 16:09:37 -0400
Organization: Aioe.org NNTP Server
Message-ID: <t3ppa0$qle$1@gioia.aioe.org>
References: <t3jd6v$ngs$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: gioia.aioe.org; logging-data="27310"; posting-host="YpgQ0RW05rxPQLn9OTMxZA.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
X-Notice: Filtered by postfilter v. 0.9.2
Content-Language: en-US
 by: Paul - Wed, 20 Apr 2022 20:09 UTC

On 4/18/2022 6:06 AM, Jeff Layman wrote:
> 20.3 Cinnamon 5.2.7
>
> As I might have a need for Bluetooth in future, I decided to have a look at it. Running "Bluetooth" from the menu showed that my laptop (jeff-P15xEMx - see below) was available for file transfers. But it also showed a device as "Not set up" under devices. This appears to be a Sony TV which I don't have! I searched on 'mint Bluetooth device unknown', and found a hit at <https://forums.linuxmint.com/viewtopic.php?t=330340> which wasn't "SOVLED" (sic)!
>
> A bit more searching led me to try sudo systemctl status Bluetooth in a terminal. This is the result (sorry about the length):
>
> ============================================
> jeff@jeff-P15xEMx:~$ sudo systemctl status bluetooth
> [sudo] password for jeff:
> ● bluetooth.service - Bluetooth service
>      Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre>
>      Active: active (running) since Mon 2022-04-18 08:27:22 BST; 36min ago
>        Docs: man:bluetoothd(8)
>    Main PID: 709 (bluetoothd)
>      Status: "Running"
>       Tasks: 1 (limit: 9310)
>      Memory: 2.4M
>      CGroup: /system.slice/bluetooth.service
>              └─709 /usr/lib/bluetooth/bluetoothd
>
> Apr 18 08:27:22 jeff-P15xEMx systemd[1]: Started Bluetooth service.
> Apr 18 08:27:22 jeff-P15xEMx bluetoothd[709]: Bluetooth management interface 1.>
> Apr 18 08:27:26 jeff-P15xEMx bluetoothd[709]: Failed to set mode: Blocked throu>
> Apr 18 08:27:52 jeff-P15xEMx bluetoothd[709]: Endpoint registered: sender=:1.35>
> Apr 18 08:27:52 jeff-P15xEMx bluetoothd[709]: Endpoint registered: sender=:1.35>
> Apr 18 08:31:22 jeff-P15xEMx bluetoothd[709]: Endpoint unregistered: sender=:1.>
> Apr 18 08:31:22 jeff-P15xEMx bluetoothd[709]: Endpoint unregistered: sender=:1.>
> Apr 18 08:31:23 jeff-P15xEMx bluetoothd[709]: Endpoint registered: sender=:1.48>
> Apr 18 08:31:23 jeff-P15xEMx bluetoothd[709]: Endpoint registered: sender=:1.48>
> Apr 18 08:50:22 jeff-P15xEMx bluetoothd[709]: Failed to set mode: Blocked throu>
> lines 1-21/21 (END)...skipping...
> ● bluetooth.service - Bluetooth service
>      Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
>      Active: active (running) since Mon 2022-04-18 08:27:22 BST; 36min ago
>        Docs: man:bluetoothd(8)
>    Main PID: 709 (bluetoothd)
>      Status: "Running"
>       Tasks: 1 (limit: 9310)
>      Memory: 2.4M
>      CGroup: /system.slice/bluetooth.service
>              └─709 /usr/lib/bluetooth/bluetoothd
>
> Apr 18 08:27:22 jeff-P15xEMx systemd[1]: Started Bluetooth service.
> Apr 18 08:27:22 jeff-P15xEMx bluetoothd[709]: Bluetooth management interface 1.14 initialized
> Apr 18 08:27:26 jeff-P15xEMx bluetoothd[709]: Failed to set mode: Blocked through rfkill (0x12)
> Apr 18 08:27:52 jeff-P15xEMx bluetoothd[709]: Endpoint registered: sender=:1.35 path=/MediaEndpoint/A2DPSink/sbc
> Apr 18 08:27:52 jeff-P15xEMx bluetoothd[709]: Endpoint registered: sender=:1.35 path=/MediaEndpoint/A2DPSource/sbc
> Apr 18 08:31:22 jeff-P15xEMx bluetoothd[709]: Endpoint unregistered: sender=:1.35 path=/MediaEndpoint/A2DPSink/sbc
> Apr 18 08:31:22 jeff-P15xEMx bluetoothd[709]: Endpoint unregistered: sender=:1.35 path=/MediaEndpoint/A2DPSource/sbc
> Apr 18 08:31:23 jeff-P15xEMx bluetoothd[709]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSink/sbc
> Apr 18 08:31:23 jeff-P15xEMx bluetoothd[709]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSource/sbc
> Apr 18 08:50:22 jeff-P15xEMx bluetoothd[709]: Failed to set mode: Blocked through rfkill (0x12)
> ~
> ~
> lines 1-21/21 (END)
>
> ============================================
>
> I then tried the following:
>
> Typing "exit" shows "No next tag (press RETURN)". Pressing RETURN cycles back to the "lines 1-21/21 (END)"
>
> Typing Ctrl-C gets back to the prompt.
>
> Typing Shift-ctrl-Q gets:
> "Close this terminal?
> There is still a process running in this terminal. Closing the terminal will kill it
> (Cancel/Close terminal)"
>
> I am very ignorant when it comes to a terminal, so can someone please explain what's going on here?
> Why is the command apparently executed twice, with the first 10  lines starting with "Apr 18 08:27:22 jeff-P15xEMx" incomplete and truncated with a > the first time they appear?
> Why are they apparently complete the second time they appear? The line ending "Failed to set mode: Blocked through rfkill (0x12)" is in red each time it appears.
> Why the 18 lines of tildes (~)?
>
> What next to try? In the Mint Forum there seem to be lots of questions about Bluetooth. Would it make sense to wait for 21.0 as there's no urgency for me to use it now:
> <https://www.omgubuntu.co.uk/2022/03/linux-mint-is-making-a-major-bluetooth-change>
>

If I do rfkill here, I get

ID TYPE DEVICE SOFT HARD
0 bluetooth hci0 unblocked unblocked

*******

Then bluetoothctl:

Agent registered
[CHG] Controller 88:99:AA:BB:CC:DD Pairable: yes

help
exit

*******

sudo systemctl status bluetooth # No funny block io type responses seen here...
# Output does not leave me in an editor, or in "less"
# In another terminal, you could try ps aguwwwx and list
# the processes running perhaps.

[sudo] password for bullwinkle:
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-04-20 11:27:04 EDT; 4h 18min ago
Docs: man:bluetoothd(8)
Main PID: 966 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 77035)
Memory: 2.2M
CGroup: /system.slice/bluetooth.service
└─966 /usr/lib/bluetooth/bluetoothd

Apr 20 11:27:04 TUNAFISH systemd[1]: Starting Bluetooth service...
Apr 20 11:27:04 TUNAFISH bluetoothd[966]: Bluetooth daemon 5.53
Apr 20 11:27:04 TUNAFISH bluetoothd[966]: Starting SDP server
Apr 20 11:27:04 TUNAFISH bluetoothd[966]: Bluetooth management interface 1.14 initialized
Apr 20 11:27:04 TUNAFISH systemd[1]: Started Bluetooth service.
Apr 20 15:27:36 TUNAFISH bluetoothd[966]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSink/sbc
Apr 20 15:27:36 TUNAFISH bluetoothd[966]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/sbc

# The clock change is due to automatic time synchronization.

*******

I was able to use bluetooth-sendto to a Windows machine,
but... the process wasn't exactly well-greased. You have to
pair and connect, to avoid error 111 (Connection refused).
The sendto then jams up at the end of file transfer.
Closing the dialog at the Ubuntu end, allowed the Save As
to appear at the Windows end.

And multibooting, or moving BT nano dongles around, these
will cause hairloss at some future date, when stuff no longer
works. Entirely too much "history" is recorded for later,
to make Bluetooth a "stateless" protocol. Now, my Windows will
likely see that "the hostname changed on the other machine" and
deny all sorts of stuff. But, that's how it works. Where would
the fun be, if every interface on a computer did not have
barriers.

Paul

Re: Terminal issues and Bluetooth

<t3u6km$j3p$1@dont-email.me>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=3538&group=alt.os.linux.mint#3538

  copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: jmlay...@invalid.invalid (Jeff Layman)
Newsgroups: alt.os.linux.mint
Subject: Re: Terminal issues and Bluetooth
Date: Fri, 22 Apr 2022 13:21:41 +0100
Organization: A noiseless patient Spider
Lines: 151
Message-ID: <t3u6km$j3p$1@dont-email.me>
References: <t3jd6v$ngs$1@dont-email.me> <t3ppa0$qle$1@gioia.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 22 Apr 2022 12:21:42 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="27a7ed7677adaf218e62c88af39458e2";
logging-data="19577"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/L9I44jlGMDVaKeU7zEWxXMRjFz9c9NdI="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Thunderbird/91.7.0
Cancel-Lock: sha1:A+QfwfY2Rzy8tGJQW5+hNmQdvqg=
In-Reply-To: <t3ppa0$qle$1@gioia.aioe.org>
Content-Language: en-GB
 by: Jeff Layman - Fri, 22 Apr 2022 12:21 UTC

On 20/04/2022 21:09, Paul wrote:
> On 4/18/2022 6:06 AM, Jeff Layman wrote:
>> 20.3 Cinnamon 5.2.7
>>
>> As I might have a need for Bluetooth in future, I decided to have a look at it. Running "Bluetooth" from the menu showed that my laptop (jeff-P15xEMx - see below) was available for file transfers. But it also showed a device as "Not set up" under devices. This appears to be a Sony TV which I don't have! I searched on 'mint Bluetooth device unknown', and found a hit at <https://forums.linuxmint.com/viewtopic.php?t=330340> which wasn't "SOVLED" (sic)!
>>
>> A bit more searching led me to try sudo systemctl status Bluetooth in a terminal. This is the result (sorry about the length):
>>
>> ============================================
>> jeff@jeff-P15xEMx:~$ sudo systemctl status bluetooth
>> [sudo] password for jeff:
>> ● bluetooth.service - Bluetooth service
>>      Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre>
>>      Active: active (running) since Mon 2022-04-18 08:27:22 BST; 36min ago
>>        Docs: man:bluetoothd(8)
>>    Main PID: 709 (bluetoothd)
>>      Status: "Running"
>>       Tasks: 1 (limit: 9310)
>>      Memory: 2.4M
>>      CGroup: /system.slice/bluetooth.service
>>              └─709 /usr/lib/bluetooth/bluetoothd
>>
>> Apr 18 08:27:22 jeff-P15xEMx systemd[1]: Started Bluetooth service.
>> Apr 18 08:27:22 jeff-P15xEMx bluetoothd[709]: Bluetooth management interface 1.>
>> Apr 18 08:27:26 jeff-P15xEMx bluetoothd[709]: Failed to set mode: Blocked throu>
>> Apr 18 08:27:52 jeff-P15xEMx bluetoothd[709]: Endpoint registered: sender=:1.35>
>> Apr 18 08:27:52 jeff-P15xEMx bluetoothd[709]: Endpoint registered: sender=:1.35>
>> Apr 18 08:31:22 jeff-P15xEMx bluetoothd[709]: Endpoint unregistered: sender=:1.>
>> Apr 18 08:31:22 jeff-P15xEMx bluetoothd[709]: Endpoint unregistered: sender=:1.>
>> Apr 18 08:31:23 jeff-P15xEMx bluetoothd[709]: Endpoint registered: sender=:1.48>
>> Apr 18 08:31:23 jeff-P15xEMx bluetoothd[709]: Endpoint registered: sender=:1.48>
>> Apr 18 08:50:22 jeff-P15xEMx bluetoothd[709]: Failed to set mode: Blocked throu>
>> lines 1-21/21 (END)...skipping...
>> ● bluetooth.service - Bluetooth service
>>      Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
>>      Active: active (running) since Mon 2022-04-18 08:27:22 BST; 36min ago
>>        Docs: man:bluetoothd(8)
>>    Main PID: 709 (bluetoothd)
>>      Status: "Running"
>>       Tasks: 1 (limit: 9310)
>>      Memory: 2.4M
>>      CGroup: /system.slice/bluetooth.service
>>              └─709 /usr/lib/bluetooth/bluetoothd
>>
>> Apr 18 08:27:22 jeff-P15xEMx systemd[1]: Started Bluetooth service.
>> Apr 18 08:27:22 jeff-P15xEMx bluetoothd[709]: Bluetooth management interface 1.14 initialized
>> Apr 18 08:27:26 jeff-P15xEMx bluetoothd[709]: Failed to set mode: Blocked through rfkill (0x12)
>> Apr 18 08:27:52 jeff-P15xEMx bluetoothd[709]: Endpoint registered: sender=:1.35 path=/MediaEndpoint/A2DPSink/sbc
>> Apr 18 08:27:52 jeff-P15xEMx bluetoothd[709]: Endpoint registered: sender=:1.35 path=/MediaEndpoint/A2DPSource/sbc
>> Apr 18 08:31:22 jeff-P15xEMx bluetoothd[709]: Endpoint unregistered: sender=:1.35 path=/MediaEndpoint/A2DPSink/sbc
>> Apr 18 08:31:22 jeff-P15xEMx bluetoothd[709]: Endpoint unregistered: sender=:1.35 path=/MediaEndpoint/A2DPSource/sbc
>> Apr 18 08:31:23 jeff-P15xEMx bluetoothd[709]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSink/sbc
>> Apr 18 08:31:23 jeff-P15xEMx bluetoothd[709]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSource/sbc
>> Apr 18 08:50:22 jeff-P15xEMx bluetoothd[709]: Failed to set mode: Blocked through rfkill (0x12)
>> ~
>> ~
>> lines 1-21/21 (END)
>>
>> ============================================
>>
>> I then tried the following:
>>
>> Typing "exit" shows "No next tag (press RETURN)". Pressing RETURN cycles back to the "lines 1-21/21 (END)"
>>
>> Typing Ctrl-C gets back to the prompt.
>>
>> Typing Shift-ctrl-Q gets:
>> "Close this terminal?
>> There is still a process running in this terminal. Closing the terminal will kill it
>> (Cancel/Close terminal)"
>>
>> I am very ignorant when it comes to a terminal, so can someone please explain what's going on here?
>> Why is the command apparently executed twice, with the first 10  lines starting with "Apr 18 08:27:22 jeff-P15xEMx" incomplete and truncated with a > the first time they appear?
>> Why are they apparently complete the second time they appear? The line ending "Failed to set mode: Blocked through rfkill (0x12)" is in red each time it appears.
>> Why the 18 lines of tildes (~)?
>>
>> What next to try? In the Mint Forum there seem to be lots of questions about Bluetooth. Would it make sense to wait for 21.0 as there's no urgency for me to use it now:
>> <https://www.omgubuntu.co.uk/2022/03/linux-mint-is-making-a-major-bluetooth-change>
>>
>
> If I do rfkill here, I get
>
> ID TYPE DEVICE SOFT HARD
> 0 bluetooth hci0 unblocked unblocked
>
> *******
>
> Then bluetoothctl:
>
> Agent registered
> [CHG] Controller 88:99:AA:BB:CC:DD Pairable: yes
>
> help
> exit
>
> *******
>
> sudo systemctl status bluetooth # No funny block io type responses seen here...
> # Output does not leave me in an editor, or in "less"
> # In another terminal, you could try ps aguwwwx and list
> # the processes running perhaps.
>
> [sudo] password for bullwinkle:
> ● bluetooth.service - Bluetooth service
> Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
> Active: active (running) since Wed 2022-04-20 11:27:04 EDT; 4h 18min ago
> Docs: man:bluetoothd(8)
> Main PID: 966 (bluetoothd)
> Status: "Running"
> Tasks: 1 (limit: 77035)
> Memory: 2.2M
> CGroup: /system.slice/bluetooth.service
> └─966 /usr/lib/bluetooth/bluetoothd
>
> Apr 20 11:27:04 TUNAFISH systemd[1]: Starting Bluetooth service...
> Apr 20 11:27:04 TUNAFISH bluetoothd[966]: Bluetooth daemon 5.53
> Apr 20 11:27:04 TUNAFISH bluetoothd[966]: Starting SDP server
> Apr 20 11:27:04 TUNAFISH bluetoothd[966]: Bluetooth management interface 1.14 initialized
> Apr 20 11:27:04 TUNAFISH systemd[1]: Started Bluetooth service.
> Apr 20 15:27:36 TUNAFISH bluetoothd[966]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSink/sbc
> Apr 20 15:27:36 TUNAFISH bluetoothd[966]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/sbc
>
> # The clock change is due to automatic time synchronization.
>
> *******
>
> I was able to use bluetooth-sendto to a Windows machine,
> but... the process wasn't exactly well-greased. You have to
> pair and connect, to avoid error 111 (Connection refused).
> The sendto then jams up at the end of file transfer.
> Closing the dialog at the Ubuntu end, allowed the Save As
> to appear at the Windows end.
>
> And multibooting, or moving BT nano dongles around, these
> will cause hairloss at some future date, when stuff no longer
> works. Entirely too much "history" is recorded for later,
> to make Bluetooth a "stateless" protocol. Now, my Windows will
> likely see that "the hostname changed on the other machine" and
> deny all sorts of stuff. But, that's how it works. Where would
> the fun be, if every interface on a computer did not have
> barriers.

Thanks for the detailed comments. I'll see how easily - or not - my
cellphone connects to the laptop via Bluetooth. If it doesn't, I'll take
the simple solution by getting out the USB-A to USB-C lead and plugging
it in to both devices!

--

Jeff

1
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor