Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failed assertion in adapter_get_dbus_object_path (self=0x0) at lib/bluez/adapter.c:165 #23

Open
rathann opened this issue Jan 17, 2018 · 7 comments

Comments

@rathann
Copy link

rathann commented Jan 17, 2018

bt-adapter is consistently crashing after disabling Bluetooth using rfkill. This was originally reported in Fedora by multiple users.

@leigh123linux
Copy link
Contributor

Issue also present in Ubuntu

https://bugs.launchpad.net/ubuntu/+source/bluez-tools/+bug/1621669

@rathann
Copy link
Author

rathann commented Sep 10, 2019

Reproducer:

$ rfkill block bluetooth
$ bt-adapter -i
**
ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self))
Aborted (core dumped)

@bitnom
Copy link

bitnom commented Oct 12, 2019

I'm getting this now. bluetooth not working and this is what I see when I run bt-device -l

@osousa
Copy link

osousa commented Dec 5, 2019

Same here, after updating to latest kernel

@vdegenne
Copy link

Same here, and when that happens I usually can't active or deactivate the bluetooth from the gnome desktop settings GUI.

@orzechow
Copy link

Had the same issue suddenly appearing during runtime on Linux Mint 19.3, although bluetooth had been working before without issues (I have my mouse connected via Bluetooth, thus I realized the issue right away).
I could not find any hints in the kernel logs and neither restarting the bluetooth kernel module, nor rebooting the system helped.

But one thing "fixed" it: shutting down the system completely, unplugging from power source, waiting for a minute and then replugging and booting again. Strange...

@Wunkolo
Copy link

Wunkolo commented Jul 24, 2021

I'm getting this issue too

But one thing "fixed" it: shutting down the system completely, unplugging from power source, waiting for a minute and then replugging and booting again. Strange...

For some reason this "fixed" it for me too... Likely some kind of interaction with power options or USB autosuspend or something?
I'm archlinux on an Z590 Taichi, using the Killer AX1675x.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants