# Failing to connect to DBus

**URL:** <https://hub.mender.io/t/failing-to-connect-to-dbus/4986>\
**Category:** Other\
**Created:** [May 25, 2022, 3:27pm UTC](https://hub.mender.io/t/failing-to-connect-to-dbus/4986 "2022-05-25T15:27:26Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![uishon](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/uishon/32/1326_2.png) [@uishon](https://hub.mender.io/u/uishon)\
**Post date:** [May 25, 2022, 3:27pm UTC](https://hub.mender.io/t/failing-to-connect-to-dbus/4986/1 "2022-05-25T15:27:26Z")

</div>

Trying to get mender running on an ARMv7 (v7l).  
Cross compiled mender (as well as mender-connect) and it’s working.  
However, I cannot get it to connect to DBus. Had to cross compile dbus as well (not available on my box) but dbus seems to be working - e.g., I am able to `dbus-send` messages to org.desktop.DBus (using the dbus CLI). Mender, however, outputs this error message on startup:

```auto
(process:1711): GLib-GIO-CRITICAL **: 16:47:20.917: g_dbus_connection_emit_signal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

```

Any idea?

---

<div class="post-metadata">

**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\
**Post date:** [May 27, 2022, 6:10am UTC](https://hub.mender.io/t/failing-to-connect-to-dbus/4986/2 "2022-05-27T06:10:37Z")

</div>

When you use `dbus-send`, are you using the `--system` argument? Mender needs to connect to the system bus, which is distinct from the (default) session bus. [This stackoverflow post](https://stackoverflow.com/questions/71251908/dbus-difference-between-system-bus-and-session-bus) gives a decent description of the two.

---

<div class="post-metadata">

**Author:** ![uishon](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/uishon/32/1326_2.png) [@uishon](https://hub.mender.io/u/uishon)\
**Post date:** [May 27, 2022, 10:25am UTC](https://hub.mender.io/t/failing-to-connect-to-dbus/4986/3 "2022-05-27T10:25:50Z")

</div>

Thanks. I am using --system.

---

<div class="post-metadata">

**Author:** ![uishon](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/uishon/32/1326_2.png) [@uishon](https://hub.mender.io/u/uishon)\
**Post date:** [May 30, 2022, 9:24am UTC](https://hub.mender.io/t/failing-to-connect-to-dbus/4986/4 "2022-05-30T09:24:35Z")

</div>

I’ve figured this one out 🙂  
Looks like `mender` wasn’t able to find the dbus daemon even though I was using `--system`.  
I guess it’s related to the fact that I had to build dbus that does NOT use the stand system folders but only folders under `/usr/local` and not the standard folders (since, on my target system, the default system folders are all read-only). Anyway, when I set `DBUS_SYSTEM_BUS_ADDRESS` to the correct address (as printed by `dbus-daemon` when using the `--print-address` option) it works. Both `mender` and `mender-connect` are now able to connect to dbus and remote terminal works.

---

<div class="post-metadata">

**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\
**Post date:** [May 31, 2022, 5:57am UTC](https://hub.mender.io/t/failing-to-connect-to-dbus/4986/5 "2022-05-31T05:57:19Z")

</div>

Great that you figured it out!

---

<div class="post-metadata">

**Author:** ![christian](https://avatars.discourse-cdn.com/v4/letter/c/b2d939/32.png) [@christian](https://hub.mender.io/u/christian)\
**Post date:** [February 28, 2024, 9:52pm UTC](https://hub.mender.io/t/failing-to-connect-to-dbus/4986/6 "2024-02-28T21:52:15Z")

</div>

Hi uishon,  
I think I’m having the same issue (dbus on readonly rootfs) and same error message.  
Could you explicit what your solution was? Especially, _where_ did you set DBUS\_SYSTEM\_BUS\_ADDRESS (I’ve tried setting it in all the systemd service files) and an example of what you set it to would be useful.  
Thanks a lot.
