dbus_1.10.20 arch64

[alejandrolozano2]

Hi,

It is a great library I was able to get something up and running on my PC.
But when I try it with a aarch64 I get the below:

arguments to dbus_connection_add_filter() were incorrect, assertion "connection != NULL" failed in file ../../dbus-1.10.20/dbus/dbus-connection.c line 5577.
This is normally a bug in some application using the D-Bus library.

Do you know what could be the issue?

Thanks,
Alejandro

[martinhaefner1]

Hi Alejandro, I admit that I did not pay much attention on error handling during initialization, i.e. dispatcher construction. Are you familiar with DBus? Have a look into the method Dispatcher::init. I think you did not get a DBusConnection instance due to e.g. no dbus-daemon running on your system or connecting to the wrong bus (system vs. session bus)? We use the library on an embedded ARM32 platform only running a system bus so we construct the Dispatcher with "bus:system" as argument. Regards, Martin Am Mi., 9. Jan. 2019 um 23:27 Uhr schrieb alejandrolozano2 < [email protected]>:

…

Hi, It is a great library I was able to get something up and running on my PC. But when I try it with a aarch64 I get the below: arguments to dbus_connection_add_filter() were incorrect, assertion "connection != NULL" failed in file ../../dbus-1.10.20/dbus/dbus-connection.c line 5577. This is normally a bug in some application using the D-Bus library. Do you know what could be the issue? Thanks, Alejandro — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#11>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABM5jHmGN5ddAYzUVBOpP2tU-bazU0MCks5vBmy6gaJpZM4Z4bMU> .

[chardin-cpi]

strace your application - likely you are trying to do a dbus_launch if the bus service is not there, and on most systems you need to be root or the proper user to do that. This was on stripped own ubuntu 18.04 system when I tracked this down.

There could be multiple reasons that the connection is null because it is relying on the internal dbus lib to create and establish the connection - the dbus_launch was the case I hit, but hopefully the strace (or strace -f to follow the child) can give you a notion.