9:50 p.m.
Hi All
Fedora 35
Xfce
Xfce's bluetooth manager find my Jabra 85h but
when I try to pair with it, I get "Disconnected"
https://imgur.com/VsnXOSK.png
# rpm -qa | grep -i blue | grep -v fish | grep -v bird
bluez-tools-0.2.0-0.17.git20170912.7cb788c.fc35.x86_64
gnome-bluetooth-libs-3.34.5-2.fc35.x86_64
gnome-bluetooth-3.34.5-2.fc35.x86_64
bluez-5.64-1.fc35.x86_64
bluez-libs-5.64-1.fc35.x86_64
bluez-cups-5.64-1.fc35.x86_64
bluez-obexd-5.64-1.fc35.x86_64
# dnf install pulseaudio-module-bluetooth
Error:
Problem: problem with installed package
pipewire-pulseaudio-0.3.50-1.fc35.x86_64
- package pipewire-pulseaudio-0.3.50-1.fc35.x86_64 conflicts with
pulseaudio provided by pulseaudio-15.0-2.fc35.x86_64
When I try to pair, journal give me:
bluetoothd[1182]: src/device.c:load_gatt_db() Unable to load key file
from /var/lib/bluetooth/00:19:0E:19:3F:C4/cache/7F:A5:9F:E8:AA:26: (No
such file)
And there really is no file of that name:
# ls -al /var/lib/bluetooth/00\:19\:0E\:19\:3F\:C4/cache/
total 16
drwx------. 2 root root 4096 Apr 22 19:15 .
drwx------. 4 root root 4096 Apr 22 19:15 ..
-rw-------. 1 root root 1078 Apr 22 19:15 30:50:75:48:88:97
-rw-------. 1 root root 29 Mar 21 20:31 CC:82:EB:4C:D5:D5
What is interesting is that 30:50:75:48:88:97 says it is
my Jabra 85H
[General]
Name=Jabra Elite 85h
If I erase the cache and start over, the same thing
happens. A new file is created but the error log
says it can't find a different file.
Yours in frustration,
-T
10:56 a.m.
On Fri, 22 Apr 2022 19:50:47 -0700
ToddAndMargo via users <users(a)lists.fedoraproject.org> wrote:
Hi All
Fedora 35
Xfce
Xfce's bluetooth manager find my Jabra 85h but
when I try to pair with it, I get "Disconnected"
# dnf install pulseaudio-module-bluetooth
Error:
Problem: problem with installed package
pipewire-pulseaudio-0.3.50-1.fc35.x86_64
- package pipewire-pulseaudio-0.3.50-1.fc35.x86_64 conflicts with
pulseaudio provided by pulseaudio-15.0-2.fc35.x86_64
Don't know if this will solve your problem, but the error says it all.
Pipewire and pulseaudio cannot co-exist. Because you are on f35 where
pipewire became default, you should remove all pulseaudio packages and
replace them with the appropriate pipewire packages. You can try
dnf swap pulseaudio pipewire
but it might not work because you have both already installed. Then it
becomes a manual process of listing the pulseaudio packages you have
installed, the corresponding pipewire packages available, and
installing the pipewire packages and removing the pulseaudio packages.
The issue will be if removing a package wants to take things that
depend on it away.
If the error is occurring because you are trying to install a
pulseaudio package with pipewire the default, and there is not an
equivalent bluetooth package for pipewire, you will have to open a
bugzilla requesting such a package.
11:56 a.m.
On 4/23/22 09:56, stan via users wrote:
Then it
becomes a manual process of listing the pulseaudio packages you have
installed, the corresponding pipewire packages available, and
installing the pipewire packages and removing the pulseaudio packages.
Wouldn't "dnf erase *pulseaudio*" work?
9:31 p.m.
On 4/23/22 09:56, Joe Zeff wrote:
On 4/23/22 09:56, stan via users wrote:
> Then it
> becomes a manual process of listing the pulseaudio packages you have
> installed, the corresponding pipewire packages available, and
> installing the pipewire packages and removing the pulseaudio packages.
Wouldn't "dnf erase *pulseaudio*" work?
# dnf erase pulseaudio*
want to erase 435 packages (2.6 GB). It would be a disaster
# dnf swap pulseaudio pipewire
Package pipewire-0.3.50-1.fc35.x86_64 is already installed.
No match for argument: pulseaudio
No packages marked for removal.
# rpm -qa pulse*
pulseaudio-libs-15.0-2.fc35.x86_64
pulseaudio-libs-glib2-15.0-2.fc35.x86_64
pulseaudio-utils-15.0-2.fc35.x86_64
pulseaudio-libs-15.0-2.fc35.i686
What next?
7:19 a.m.
On 24/04/2022 10:31, ToddAndMargo via users wrote:
# dnf swap pulseaudio pipewire
Package pipewire-0.3.50-1.fc35.x86_64 is already installed.
No match for argument: pulseaudio
No packages marked for removal.
# rpm -qa pulse*
pulseaudio-libs-15.0-2.fc35.x86_64
pulseaudio-libs-glib2-15.0-2.fc35.x86_64
pulseaudio-utils-15.0-2.fc35.x86_64
pulseaudio-libs-15.0-2.fc35.i686
What next?
Just a bit of advice. Dpm't put the cart before the horse.
Pulseaudio and pipewire are irrelevant until the device is paired and connected.
Instead of using the GUI, use a terminal and the bluetoothctl command.
Put the speakers in pairing mode and issue the devices command under bluetoothctl use the
"pair" command to get some info
along with the journal to see why pairing fails.
Small example, but I don't have time to disconnect and upair my speakers.
[egreshko@meimei ~]$ bluetoothctl
Agent registered
[SRS-XB43]#
[SRS-XB43]# devices
Device 6C:47:60:43:6B:49 SRS-XB43
[SRS-XB43]# info 6C:47:60:43:6B:49
Device 6C:47:60:43:6B:49 (public)
Name: SRS-XB43
Alias: SRS-XB43
Class: 0x00240414
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Vendor specific (00000000-deca-fade-deca-deafdecacaff)
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (0000ff01-0000-1000-8000-00805f9b34ff)
UUID: Vendor specific (8901dfa8-5c7e-4d8f-9f0c-c2b70683f5f0)
UUID: Vendor specific (b9b213ce-eeab-49e4-8fd9-aa478ed1b26b)
Modalias: bluetooth:v0094p0004d0100
--
Did 황준호 die?
1:06 a.m.
On 4/24/22 05:19, Ed Greshko wrote:
On 24/04/2022 10:31, ToddAndMargo via users wrote:
> # dnf swap pulseaudio pipewire
> Package pipewire-0.3.50-1.fc35.x86_64 is already installed.
> No match for argument: pulseaudio
> No packages marked for removal.
>
> # rpm -qa pulse*
> pulseaudio-libs-15.0-2.fc35.x86_64
> pulseaudio-libs-glib2-15.0-2.fc35.x86_64
> pulseaudio-utils-15.0-2.fc35.x86_64
> pulseaudio-libs-15.0-2.fc35.i686
>
>
> What next?
Just a bit of advice. Dpm't put the cart before the horse.
Pulseaudio and pipewire are irrelevant until the device is paired and
connected.
Instead of using the GUI, use a terminal and the bluetoothctl command.
Put the speakers in pairing mode and issue the devices command under
bluetoothctl use the "pair" command to get some info
along with the journal to see why pairing fails.
Small example, but I don't have time to disconnect and upair my speakers.
[egreshko@meimei ~]$ bluetoothctl
Agent registered
[SRS-XB43]#
[SRS-XB43]# devices
Device 6C:47:60:43:6B:49 SRS-XB43
[SRS-XB43]# info 6C:47:60:43:6B:49
Device 6C:47:60:43:6B:49 (public)
Name: SRS-XB43
Alias: SRS-XB43
Class: 0x00240414
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Vendor specific (00000000-deca-fade-deca-deafdecacaff)
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target
(0000110c-0000-1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu..
(0000110d-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (0000ff01-0000-1000-8000-00805f9b34ff)
UUID: Vendor specific (8901dfa8-5c7e-4d8f-9f0c-c2b70683f5f0)
UUID: Vendor specific (b9b213ce-eeab-49e4-8fd9-aa478ed1b26b)
Modalias: bluetooth:v0094p0004d0100
Hi Ed,
I got to this point:
# connect 30:50:75:48:88:97
Attempting to connect to 30:50:75:48:88:97
[CHG] Device 30:50:75:48:88:97 Connected: yes
[CHG] Device 30:50:75:48:88:97 Connected: no
As soon as it connects, it disconnects.
:'(
-T
9:32 a.m.
On Sat, 23 Apr 2022 19:31:57 -0700
ToddAndMargo via users <users(a)lists.fedoraproject.org> wrote:
On 4/23/22 09:56, Joe Zeff wrote:
> On 4/23/22 09:56, stan via users wrote:
>> Then it
>> becomes a manual process of listing the pulseaudio packages you
>> have installed, the corresponding pipewire packages available, and
>> installing the pipewire packages and removing the pulseaudio
>> packages.
>
> Wouldn't "dnf erase *pulseaudio*" work?
# dnf erase pulseaudio*
want to erase 435 packages (2.6 GB). It would be a disaster
# dnf swap pulseaudio pipewire
Package pipewire-0.3.50-1.fc35.x86_64 is already installed.
No match for argument: pulseaudio
No packages marked for removal.
# rpm -qa pulse*
pulseaudio-libs-15.0-2.fc35.x86_64
pulseaudio-libs-glib2-15.0-2.fc35.x86_64
pulseaudio-utils-15.0-2.fc35.x86_64
pulseaudio-libs-15.0-2.fc35.i686
What next?
If Ed's idea doesn't solve the problem, here are a couple of
suggestions.
Try
dnf swap pulseaudio\* pipewire\*
so that everything is considered in the swap.
If that doesn't work, you should try the opposite, reverting your
system to pulseaudio only, by removing all of pipewire. If everything
on your system still has dependencies on pulseaudio, it might work to do
dnf remove pipewire\*
without the huge dependency erase. Then, run the swap command, the
inclusive one, and it should work. Or, once pipewire is removed, just
continue using pulseaudio, as either will work, they just conflict if
both are installed (in my experience). You won't face the problem
again until f36 or f37.
12:15 a.m.
On 4/24/22 07:32, stan via users wrote:
On Sat, 23 Apr 2022 19:31:57 -0700
ToddAndMargo via users <users(a)lists.fedoraproject.org> wrote:
> On 4/23/22 09:56, Joe Zeff wrote:
>> On 4/23/22 09:56, stan via users wrote:
>>> Then it
>>> becomes a manual process of listing the pulseaudio packages you
>>> have installed, the corresponding pipewire packages available, and
>>> installing the pipewire packages and removing the pulseaudio
>>> packages.
>>
>> Wouldn't "dnf erase *pulseaudio*" work?
>
> # dnf erase pulseaudio*
> want to erase 435 packages (2.6 GB). It would be a disaster
>
>
> # dnf swap pulseaudio pipewire
> Package pipewire-0.3.50-1.fc35.x86_64 is already installed.
> No match for argument: pulseaudio
> No packages marked for removal.
>
> # rpm -qa pulse*
> pulseaudio-libs-15.0-2.fc35.x86_64
> pulseaudio-libs-glib2-15.0-2.fc35.x86_64
> pulseaudio-utils-15.0-2.fc35.x86_64
> pulseaudio-libs-15.0-2.fc35.i686
>
>
> What next?
If Ed's idea doesn't solve the problem, here are a couple of
suggestions.
Try
dnf swap pulseaudio\* pipewire\*
so that everything is considered in the swap.
If that doesn't work, you should try the opposite, reverting your
system to pulseaudio only, by removing all of pipewire. If everything
on your system still has dependencies on pulseaudio, it might work to do
dnf remove pipewire\*
without the huge dependency erase. Then, run the swap command, the
inclusive one, and it should work. Or, once pipewire is removed, just
continue using pulseaudio, as either will work, they just conflict if
both are installed (in my experience). You won't face the problem
again until f36 or f37.
Ed it right about the cart and the horse. Without
the pair, sound and file sharing are a moot point.
And from this:
$ rpm -qa pulse*
pulseaudio-libs-15.0-2.fc35.x86_64
pulseaudio-libs-glib2-15.0-2.fc35.x86_64
pulseaudio-utils-15.0-2.fc35.x86_64
pulseaudio-libs-15.0-2.fc35.i686
I believe I am already on pipewire and am just
looking
at pipewire's pulse plugins
1:38 a.m.
On 4/24/22 22:15, ToddAndMargo via users wrote:
On 4/24/22 07:32, stan via users wrote:
> On Sat, 23 Apr 2022 19:31:57 -0700
> ToddAndMargo via users <users(a)lists.fedoraproject.org> wrote:
>
>> On 4/23/22 09:56, Joe Zeff wrote:
>>> On 4/23/22 09:56, stan via users wrote:
>>>> Then it
>>>> becomes a manual process of listing the pulseaudio packages you
>>>> have installed, the corresponding pipewire packages available, and
>>>> installing the pipewire packages and removing the pulseaudio
>>>> packages.
>>>
>>> Wouldn't "dnf erase *pulseaudio*" work?
>>
>> # dnf erase pulseaudio*
>> want to erase 435 packages (2.6 GB). It would be a disaster
>>
>>
>> # dnf swap pulseaudio pipewire
>> Package pipewire-0.3.50-1.fc35.x86_64 is already installed.
>> No match for argument: pulseaudio
>> No packages marked for removal.
>>
>> # rpm -qa pulse*
>> pulseaudio-libs-15.0-2.fc35.x86_64
>> pulseaudio-libs-glib2-15.0-2.fc35.x86_64
>> pulseaudio-utils-15.0-2.fc35.x86_64
>> pulseaudio-libs-15.0-2.fc35.i686
>>
>>
>> What next?
>
> If Ed's idea doesn't solve the problem, here are a couple of
> suggestions.
>
> Try
> dnf swap pulseaudio\* pipewire\*
> so that everything is considered in the swap.
>
> If that doesn't work, you should try the opposite, reverting your
> system to pulseaudio only, by removing all of pipewire. If everything
> on your system still has dependencies on pulseaudio, it might work to do
> dnf remove pipewire\*
> without the huge dependency erase. Then, run the swap command, the
> inclusive one, and it should work. Or, once pipewire is removed, just
> continue using pulseaudio, as either will work, they just conflict if
> both are installed (in my experience). You won't face the problem
> again until f36 or f37.
Ed it right about the cart and the horse. Without
the pair, sound and file sharing are a moot point.
And from this:
$ rpm -qa pulse*
pulseaudio-libs-15.0-2.fc35.x86_64
pulseaudio-libs-glib2-15.0-2.fc35.x86_64
pulseaudio-utils-15.0-2.fc35.x86_64
pulseaudio-libs-15.0-2.fc35.i686
I believe I am already on pipewire and am just
looking
at pipewire's pulse plugins
Jabra confirmed that my 854H headset won't work
with a computer. So that is out
Now, how do I share files with my cell phone?
4:51 a.m.
On 25/04/2022 14:38, ToddAndMargo via users wrote:
Jabra confirmed that my 854H headset won't work
with a computer. So that is out
That doesn't surprise me. I've had several of their products years ago. They
never impressed me.
I stick with Bose, Sony, and Panasonic.
Now, how do I share files with my cell phone?
Must be the subject of a different thread. As a KDE user I prefer KDE Connect.
--
Did 황준호 die?
8:54 p.m.
On Mon, Apr 25, 2022 at 4:42 AM Ed Greshko <ed.greshko(a)greshko.com> wrote:
I stick with Bose, Sony, and Panasonic.
However, it does matter which exact product you have, not just whether it
is a quality product or not. For instance, I have a really nice pair of
Bose bluetooth headphones. They sound great, but unfortunately they only
work on my Android devices, because they require use of an app to properly
connect. They will not reliably pair with Linux or Windows. (There is
probably an iPhone version of the app too). Same holds for my pair of Sony
"true wireless" earbuds. Sound great, but will not pair with a computer,
require an app.
--Greg
9:05 p.m.
On 26/04/2022 09:54, Greg Woods wrote:
On Mon, Apr 25, 2022 at 4:42 AM Ed Greshko <ed.greshko(a)greshko.com> wrote:
I stick with Bose, Sony, and Panasonic.
However, it does matter which exact product you have, not just whether it is a quality
product or not. For instance, I have a really nice pair of Bose bluetooth headphones. They
sound great, but unfortunately they only work on my Android devices, because they require
use of an app to properly connect. They will not reliably pair with Linux or Windows.
(There is probably an iPhone version of the app too). Same holds for my pair of Sony
"true wireless" earbuds. Sound great, but will not pair with a computer, require
an app.
I did name the product in a subsequent email. Bose Quiet Comfort.
--
Did 황준호 die?
730
days inactive
733
days old
13 comments
5 participants
participants (5)
-
Ed Greshko -
Greg Woods -
Joe Zeff -
stan -
ToddAndMargo