From: runrin <runrin@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
Date: Thu, 27 Oct 2022 01:11:54 +0200 [thread overview]
Message-ID: <20221026231154.1_FZU10glDLJ-FaSZZ3x2jEPyq0WSVOPjlM5Au5Rn1A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40018@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
New comment by runrin on void-packages repository
https://github.com/void-linux/void-packages/issues/40018#issuecomment-1292761848
Comment:
i have had some form of this issue (intermittently) when attempting to connect my headphones and bluetooth speakers for a while now. i'm on `Void 5.19.10_1 x86_64 AuthenticAMD`.
today i'm getting `Failed to connect: org.bluez.Error.Failed br-connection-unknown`.
i suspect this isn't an issue with the void package, and is more an issue with bluez itself. i've seen the same errors on my debian machines as well, along with other similarly inscrutable errors. my experience for years with bluetooth on multiple linux boxes has been that it only works correctly about 65% of the time.
sometimes it just doesn't feel like working, sometimes the service won't even restart with `sv restart` and i have to use `sv stop` instead.
the only thing that ever resolves this issue for me is rebooting my machine (and this only occasionally works, rebooting multiple times sometimes gets it to work again).
restarting pulseaudio and/or the bluetooth service have never worked for me.
next prev parent reply other threads:[~2022-10-26 23:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 8:30 [ISSUE] " LinArcX
2022-10-18 12:05 ` Duncaen
2022-10-18 12:27 ` LinArcX
2022-10-18 13:06 ` paper42
2022-10-18 15:55 ` LinArcX
2022-10-18 16:03 ` LinArcX
2022-10-18 16:14 ` LinArcX
2022-10-18 16:27 ` LinArcX
2022-10-26 23:11 ` runrin [this message]
2022-12-10 8:20 ` eoli3n
2022-12-10 8:24 ` eoli3n
2023-01-20 18:48 ` cybergsus
2023-01-20 18:49 ` cybergsus
2023-01-20 20:34 ` paper42
2023-01-24 9:38 ` cybergsus
2023-01-24 9:39 ` cybergsus
2023-01-24 9:39 ` cybergsus
2023-01-24 9:43 ` cybergsus
2023-01-24 9:43 ` cybergsus
2023-02-20 21:18 ` dwhughes
2023-02-20 21:22 ` dwhughes
2023-08-21 5:46 ` GrubBox
2023-08-21 5:48 ` GrubBox
2023-08-21 5:48 ` GrubBox
2023-08-21 5:48 ` GrubBox
2023-08-21 5:49 ` GrubBox
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=20221026231154.1_FZU10glDLJ-FaSZZ3x2jEPyq0WSVOPjlM5Au5Rn1A@z \
--to=runrin@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).