Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] Waiting to connect to bluetoothd...dbus
@ 2022-10-17 21:15 LinArcX
  2022-10-18  0:52 ` sgn
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: LinArcX @ 2022-10-17 21:15 UTC (permalink / raw)
  To: ml

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

New 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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Waiting to connect to bluetoothd...dbus
  2022-10-17 21:15 [ISSUE] Waiting to connect to bluetoothd...dbus LinArcX
@ 2022-10-18  0:52 ` sgn
  2022-10-18  0:52 ` sgn
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: sgn @ 2022-10-18  0:52 UTC (permalink / raw)
  To: ml

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

New comment by sgn on void-packages repository

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

Comment:
Just want to check, are both bluetoothd and dbus service up?
```
sv status dbus bluetoothd
```
Is there any errors in dmesg?

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Waiting to connect to bluetoothd...dbus
  2022-10-17 21:15 [ISSUE] Waiting to connect to bluetoothd...dbus LinArcX
  2022-10-18  0:52 ` sgn
@ 2022-10-18  0:52 ` sgn
  2022-10-18  7:21 ` LinArcX
  2022-10-18  7:21 ` [ISSUE] [CLOSED] " LinArcX
  3 siblings, 0 replies; 5+ messages in thread
From: sgn @ 2022-10-18  0:52 UTC (permalink / raw)
  To: ml

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

New comment by sgn on void-packages repository

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

Comment:
Just want to check, are both bluetoothd and dbus service up?
```
sv status dbus bluetoothd
```
Is there any errors in syslog?

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Waiting to connect to bluetoothd...dbus
  2022-10-17 21:15 [ISSUE] Waiting to connect to bluetoothd...dbus LinArcX
  2022-10-18  0:52 ` sgn
  2022-10-18  0:52 ` sgn
@ 2022-10-18  7:21 ` LinArcX
  2022-10-18  7:21 ` [ISSUE] [CLOSED] " LinArcX
  3 siblings, 0 replies; 5+ messages in thread
From: LinArcX @ 2022-10-18  7:21 UTC (permalink / raw)
  To: ml

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

New comment by LinArcX on void-packages repository

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

Comment:
Oh, I don't know why this happened. Just reinstalled dbus and bluez, and everything now works.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [ISSUE] [CLOSED] Waiting to connect to bluetoothd...dbus
  2022-10-17 21:15 [ISSUE] Waiting to connect to bluetoothd...dbus LinArcX
                   ` (2 preceding siblings ...)
  2022-10-18  7:21 ` LinArcX
@ 2022-10-18  7:21 ` LinArcX
  3 siblings, 0 replies; 5+ messages in thread
From: LinArcX @ 2022-10-18  7:21 UTC (permalink / raw)
  To: ml

[-- 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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2022-10-18  7:21 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-10-17 21:15 [ISSUE] Waiting to connect to bluetoothd...dbus LinArcX
2022-10-18  0:52 ` sgn
2022-10-18  0:52 ` sgn
2022-10-18  7:21 ` LinArcX
2022-10-18  7:21 ` [ISSUE] [CLOSED] " LinArcX

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).