You are not logged in.

#1 2021-11-26 21:58:03

nicocot
Member
Registered: 2018-02-04
Posts: 29

Issue with dbus

Hi,

I've got the following issue with dbus:

$ dbus-monitor
signal time=1637963284.556664 sender=org.freedesktop.DBus -> destination=:1.0 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
   string ":1.0"
signal time=1637963284.556731 sender=org.freedesktop.DBus -> destination=:1.0 serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
   string ":1.0"

Any ideas would be appreciated.

Many thanks

Offline

#2 2021-11-26 22:28:22

seth
Member
Registered: 2012-09-03
Posts: 50,012

Re: Issue with dbus

The destination should probably not be ":1.0" - depending on the context.
However, your post does not directly indicate issues w/ dbus - so maybe elaborate on the acutal issue you face.

Offline

#3 2021-11-26 23:58:01

nicocot
Member
Registered: 2018-02-04
Posts: 29

Re: Issue with dbus

seth wrote:

The destination should probably not be ":1.0" - depending on the context.
However, your post does not directly indicate issues w/ dbus - so maybe elaborate on the acutal issue you face.

I had lots of issue with Jack / Pipewire / a2jmidid which seemed to be linked to dbus / X11. However I've solved them and pipewire works fine now.
I haven't kept the error messages but I had something like: 'Freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.gna.home.a2jmidid': no such name'

I just thought there might be something wrong my dbus config but maybe there is nothing wrong after all?

Thanks

Offline

#4 2021-11-27 08:13:56

seth
Member
Registered: 2012-09-03
Posts: 50,012

Re: Issue with dbus

I haven't kept the error messages

But the journal has?
https://wiki.archlinux.org/title/Systemd/Journal

there might be something wrong my dbus config

Impossible to say from here, however

linked to dbus / X11. However I've solved them

If we ignore that X11 and dbus are vastly different things: since you solved *something*, something™ must have been wrong and you're the on who knows what that might have been…

The usual suspect is a misconfigured xinitrc (if you're using startx/xinit) and you've a compromised session bus, but again: impossible to say from here.

The messages in dbus-monitor are normal-ish.

Offline

Board footer

Powered by FluxBB