On Do, 01.04.21 13:32, Carlo Wood (carlo@xxxxxxxxxx) wrote: > I am getting all kinds of unlisted errors from > sd_bus_get_unique_name. > > EBADMSG and EBUSY are not listed on the manual page of > sd_bus_get_unique_name. We only document prominent errors directly, but the list is by no means complete. > What is the cause of these errors, and how should I deal with > them? I don#t know. Provide a minimal reproducer? EBADMSG usually means that somehow an invalid dbus packet we couldn't parse entered the stream. maybe some memory corruption thing? or maybe you are using this in a threaded env without locking? Lennart -- Lennart Poettering, Berlin _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel