Re: Bluetooth Issue.
If it's paired it should appear in that list, even if it's not connected at
the moment. If you run the command it'll bypass gnome-settings and we'll be
able to see if the sound issue goes away; if it does, we know it's
something with gnome, if not, something else.
Geoff Marr
IRC: coremodule
On Wed, Apr 3, 2019 at 11:18 AM Geoffrey Marr wrote:
> Whoops.
>
> [0] https://wiki.archlinux.org/index.php/Bluetooth_headset
>
> Geoff Marr
> IRC: coremodule
>
>
> On Wed, Apr 3, 2019 at 11:16 AM Geoffrey Marr wrote:
>
>> Hmmm, it doesn't look like the device you're trying to connect to is in
>> the "paired" list of devices. Can you try to pair to it manually?
>>
>> Use "sudo bluetoothctl" then "scan on" to start scanning the area for
>> available bluetooth devices (make sure the device you're trying to pair is
>> in discoverable mode). Then, once you have found the device you're trying
>> to connect to, use "pair MAC" where MAC is the MAC address of the device
>> you're trying to connect to (you can use tab completion for this). If it
>> successfully pairs, run "trust MAC" and then finally "connect MAC". If this
>> all works, it *should* connect to the device and you should be able to
>> output sound to it using the Sound configuration page in Gnome.
>>
>> See this for more details if you get stuck [0]
>>
>> If this all works, then check the Bluetooth config page in Gnome to see
>> if it recognizes your paired device. You can also run the command from my
>> first post to see if "bluetoothctl" recognizes the device still. This will
>> tell us what is causing the problem you're having.
>>
>> Geoff Marr
>> IRC: coremodule
>>
>>
>> On Wed, Apr 3, 2019 at 11:06 AM Andrew J Hutton <
>> andrew.john.hut...@gmail.com> wrote:
>>
>>> Here you go.
>>>
>>> On 2019-04-03 12:52 p.m., Geoffrey Marr wrote:
>>> > for i in 'list' 'show' 'devices' ; do sudo bluetoothctl ${i};done
>>>
>>> Controller 00:1A:7D:DA:71:13 Odin [default]
>>> Controller 00:1A:7D:DA:71:13 (public)
>>> Name: Odin
>>> Alias: Odin
>>> Class: 0x001c
>>> Powered: yes
>>> Discoverable: no
>>> Pairable: yes
>>> UUID: Headset AG
>>> (1112--1000-8000-00805f9b34fb)
>>> UUID: Generic Attribute Profile
>>> (1801--1000-8000-00805f9b34fb)
>>> UUID: A/V Remote Control
>>> (110e--1000-8000-00805f9b34fb)
>>> UUID: OBEX File Transfer
>>> (1106--1000-8000-00805f9b34fb)
>>> UUID: Generic Access Profile
>>> (1800--1000-8000-00805f9b34fb)
>>> UUID: OBEX Object Push
>>> (1105--1000-8000-00805f9b34fb)
>>> UUID: PnP Information
>>> (1200--1000-8000-00805f9b34fb)
>>> UUID: IrMC Sync
>>> (1104--1000-8000-00805f9b34fb)
>>> UUID: A/V Remote Control Target
>>> (110c--1000-8000-00805f9b34fb)
>>> UUID: Audio Source
>>> (110a--1000-8000-00805f9b34fb)
>>> UUID: Audio Sink
>>> (110b--1000-8000-00805f9b34fb)
>>> UUID: Message Notification Se..
>>> (1133--1000-8000-00805f9b34fb)
>>> UUID: Phonebook Access Server
>>> (112f--1000-8000-00805f9b34fb)
>>> UUID: Message Access Server
>>> (1132--1000-8000-00805f9b34fb)
>>> UUID: Headset
>>> (1108--1000-8000-00805f9b34fb)
>>> Modalias: usb:v1D6Bp0246d0532
>>> Discovering: yes
>>> Device B4:F1:DA:98:AD:AD Pixel 2 XL
>>>
>>> ___
>>> test mailing list -- test@lists.fedoraproject.org
>>> To unsubscribe send an email to test-le...@lists.fedoraproject.org
>>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>>> List Archives:
>>> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>>>
>>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Bluetooth Issue.
Whoops.
[0] https://wiki.archlinux.org/index.php/Bluetooth_headset
Geoff Marr
IRC: coremodule
On Wed, Apr 3, 2019 at 11:16 AM Geoffrey Marr wrote:
> Hmmm, it doesn't look like the device you're trying to connect to is in
> the "paired" list of devices. Can you try to pair to it manually?
>
> Use "sudo bluetoothctl" then "scan on" to start scanning the area for
> available bluetooth devices (make sure the device you're trying to pair is
> in discoverable mode). Then, once you have found the device you're trying
> to connect to, use "pair MAC" where MAC is the MAC address of the device
> you're trying to connect to (you can use tab completion for this). If it
> successfully pairs, run "trust MAC" and then finally "connect MAC". If this
> all works, it *should* connect to the device and you should be able to
> output sound to it using the Sound configuration page in Gnome.
>
> See this for more details if you get stuck [0]
>
> If this all works, then check the Bluetooth config page in Gnome to see if
> it recognizes your paired device. You can also run the command from my
> first post to see if "bluetoothctl" recognizes the device still. This will
> tell us what is causing the problem you're having.
>
> Geoff Marr
> IRC: coremodule
>
>
> On Wed, Apr 3, 2019 at 11:06 AM Andrew J Hutton <
> andrew.john.hut...@gmail.com> wrote:
>
>> Here you go.
>>
>> On 2019-04-03 12:52 p.m., Geoffrey Marr wrote:
>> > for i in 'list' 'show' 'devices' ; do sudo bluetoothctl ${i};done
>>
>> Controller 00:1A:7D:DA:71:13 Odin [default]
>> Controller 00:1A:7D:DA:71:13 (public)
>> Name: Odin
>> Alias: Odin
>> Class: 0x001c
>> Powered: yes
>> Discoverable: no
>> Pairable: yes
>> UUID: Headset AG(1112--1000-8000-00805f9b34fb)
>> UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
>> UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
>> UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
>> UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
>> UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb)
>> UUID: PnP Information (1200--1000-8000-00805f9b34fb)
>> UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
>> UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
>> UUID: Audio Source (110a--1000-8000-00805f9b34fb)
>> UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
>> UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
>> UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb)
>> UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
>> UUID: Headset (1108--1000-8000-00805f9b34fb)
>> Modalias: usb:v1D6Bp0246d0532
>> Discovering: yes
>> Device B4:F1:DA:98:AD:AD Pixel 2 XL
>>
>> ___
>> test mailing list -- test@lists.fedoraproject.org
>> To unsubscribe send an email to test-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>>
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Bluetooth Issue.
Hmmm, it doesn't look like the device you're trying to connect to is in the
"paired" list of devices. Can you try to pair to it manually?
Use "sudo bluetoothctl" then "scan on" to start scanning the area for
available bluetooth devices (make sure the device you're trying to pair is
in discoverable mode). Then, once you have found the device you're trying
to connect to, use "pair MAC" where MAC is the MAC address of the device
you're trying to connect to (you can use tab completion for this). If it
successfully pairs, run "trust MAC" and then finally "connect MAC". If this
all works, it *should* connect to the device and you should be able to
output sound to it using the Sound configuration page in Gnome.
See this for more details if you get stuck [0]
If this all works, then check the Bluetooth config page in Gnome to see if
it recognizes your paired device. You can also run the command from my
first post to see if "bluetoothctl" recognizes the device still. This will
tell us what is causing the problem you're having.
Geoff Marr
IRC: coremodule
On Wed, Apr 3, 2019 at 11:06 AM Andrew J Hutton <
andrew.john.hut...@gmail.com> wrote:
> Here you go.
>
> On 2019-04-03 12:52 p.m., Geoffrey Marr wrote:
> > for i in 'list' 'show' 'devices' ; do sudo bluetoothctl ${i};done
>
> Controller 00:1A:7D:DA:71:13 Odin [default]
> Controller 00:1A:7D:DA:71:13 (public)
> Name: Odin
> Alias: Odin
> Class: 0x001c
> Powered: yes
> Discoverable: no
> Pairable: yes
> UUID: Headset AG(1112--1000-8000-00805f9b34fb)
> UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
> UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
> UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
> UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
> UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb)
> UUID: PnP Information (1200--1000-8000-00805f9b34fb)
> UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
> UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
> UUID: Audio Source (110a--1000-8000-00805f9b34fb)
> UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
> UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
> UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb)
> UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
> UUID: Headset (1108--1000-8000-00805f9b34fb)
> Modalias: usb:v1D6Bp0246d0532
> Discovering: yes
> Device B4:F1:DA:98:AD:AD Pixel 2 XL
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Bluetooth Issue.
Here you go.
On 2019-04-03 12:52 p.m., Geoffrey Marr wrote:
> for i in 'list' 'show' 'devices' ; do sudo bluetoothctl ${i};done
Controller 00:1A:7D:DA:71:13 Odin [default]
Controller 00:1A:7D:DA:71:13 (public)
Name: Odin
Alias: Odin
Class: 0x001c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG (1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control (110e--1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (1106--1000-8000-00805f9b34fb)
UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb)
UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb)
UUID: PnP Information (1200--1000-8000-00805f9b34fb)
UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink (110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb)
UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
UUID: Headset (1108--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0532
Discovering: yes
Device B4:F1:DA:98:AD:AD Pixel 2 XL
pEpkey.asc
Description: application/pgp-keys
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Bluetooth Issue.
HI Andrew,
Can you please post the result of running "for i in 'list' 'show'
'devices' ; do sudo bluetoothctl ${i};done"?
Geoff Marr
IRC: coremodule
On Wed, Apr 3, 2019 at 9:49 AM Andrew J. Hutton <
andrew.john.hut...@gmail.com> wrote:
> I just added a bluetooth dongle to my desktop cluster for audio on F29
> and there are some bugs; what exactly they are and who is responsible
> for them is where I'm a bit fuzzy. The kernel detects the device fine;
> and I can pair to it. If I output audio to it the sound comes out of the
> local built-in speaker vs the PulseAudio sink that is configured to send
> it to the correct device.
>
> The most obvious issue is that when the Gnome Settings is accessed, the
> Bluetooth section still shows 'No Bluetooth Found'; since I don't have
> access to it I can't tell if that would allow me to fix the audio
> routing issue, or set-up the other features. The default panel plugin
> that provides the volume, current network state, etc does show 1
> Connected however the only options there are Turn Off, and Bluetooth
> Settings, which as stated does not work.
>
> So, my question is, is this a failure of one gnome component to notify
> another, a missing dependency (though I think that I have everything
> even related to Bluetooth installed), or some other kind of bug? I do
> recall this working correctly on one of the laptops also on F29, though
> I'm unsure which one and would have to find the right one to confirm.
>
> Ideas?
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
