Github messages for voidlinux
 help / color / mirror / Atom feed
From: LinArcX <LinArcX@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Waiting to connect to bluetoothd...dbus
Date: Tue, 18 Oct 2022 09:21:43 +0200	[thread overview]
Message-ID: <20221018072143.vg8EJ6_5L4XIR6GvBo2on_FyyynrA-KWkv7wPz5mNxA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40011@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]

Closed issue by LinArcX on void-packages repository

https://github.com/void-linux/void-packages/issues/40011

Description:
### Is this a new report?

Yes

### System Info

Void 5.19.16_1 x86_64 GenuineIntel notuptodate hold rFF

### Package(s) Affected

bluez, dbus

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

`bluetoothctl` should work properly.

### Actual behaviour

Whenever i wanted to run `bluetoothctl`, it throws this error:
```
↳ bluetoothctl
Waiting to connect to bluetoothd...dbus[18807]: arguments to dbus_connection_get_object_path_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5921.
This is normally a bug in some application using the D-Bus library.

  D-Bus not built with -rdynamic so unable to print a backtrace
Aborted
```

### Steps to reproduce

I wanted to enable Bluetooth on my void Linux, there are the steps that I followed:
https://docs.voidlinux.org/config/bluetooth.html

      parent reply	other threads:[~2022-10-18  7:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 21:15 [ISSUE] " LinArcX
2022-10-18  0:52 ` sgn
2022-10-18  0:52 ` sgn
2022-10-18  7:21 ` LinArcX
2022-10-18  7:21 ` LinArcX [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=20221018072143.vg8EJ6_5L4XIR6GvBo2on_FyyynrA-KWkv7wPz5mNxA@z \
    --to=linarcx@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).