From: Eluminae <Eluminae@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Issue with pipewire bluetooth (cant connect to paired device)
Date: Thu, 18 Mar 2021 20:04:00 +0100 [thread overview]
Message-ID: <20210318190400.aCgKQtmFPyhte1mIeUbDOpBnd2mYlt-YLcaRzqAnK3c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29570@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1769 bytes --]
Closed issue by Eluminae on void-packages repository
https://github.com/void-linux/void-packages/issues/29570
Description:
### System
An up to date voidlinux
* xuname:
*Void 5.10.23_1 x86_64 GenuineIntel uptodate rrrmFFFF*
* package:
*pipewire-0.3.23_1*
*bluez-5.55_1*
### Expected behavior
Having pipewire + bluez setup, I should be able to connect my bluetooth headphone and use it
### Actual behavior
```
[bluetooth]# connect 98:xx:3D:A6:xx:1C
Attempting to connect to 98:xx:3D:A6:xx:1C
Failed to connect: org.bluez.Error.Failed
```
The exact same command with pulseaudio instead of pipewire works like a charm.
### Steps to reproduce the behavior
```
$ sudo xbps-install pipewire bluez
$ sudo ln -s /etc/sv/bluetoothd /var/service/
$ pulseaudio -k # make sure pulseaudio is stopped
$ sudo vim /etc/pipewire/pipewire.conf # make sure to uncomment both context.exec at the end
$ pipewire & # or in another terminal
$ bluetoothctl
[bluetooth]# power on
[bluetooth]# scan on
...
[bluetooth]# pair xx:xx:xx:xx:xx:xx
...
# here you will be connected a very short time then disconnected
[bluetooth]# connect xx:xx:xx:xx:xx:xx
Attempting to connect to xx:xx:xx:xx:xx:xx
Failed to connect: org.bluez.Error.Failed
```
I already tries to remove then re-pair the bluetooth device, or make any kind of combinaison. I got two devices that got the exact same issue. I got the issue with two different machines. Anyway, it works very well with pulseaudio.
Pipewire log this line very early
```
[E][000000903.740297][bluez-monitor.c:572 sm_bluez5_monitor_start()] can't load api.bluez5.enum.dbus: No such file or directory
```
I think maybe it miss something to works correctly with bluez through dbus.
prev parent reply other threads:[~2021-03-18 19:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 17:52 [ISSUE] " Eluminae
2021-03-18 18:12 ` ericonr
2021-03-18 18:43 ` st3r4g
2021-03-18 18:50 ` st3r4g
2021-03-18 19:03 ` Eluminae
2021-03-18 19:04 ` Eluminae [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210318190400.aCgKQtmFPyhte1mIeUbDOpBnd2mYlt-YLcaRzqAnK3c@z \
--to=eluminae@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).