dbus | Native Go bindings for D-Bus | Messaging library

Highly doubt that anyone would have the same scenario, but I solved it by just using a separate docker container for memcached and connecting my application to that instead.

Further research shows that dbus itself is an SELinux aware application. It is checking the SELinux configuration, and taking enforcement actions within dbus itself. This accounts for why the denials from dbus do not appear in the audit log, even when silent denials are turned off.

My particular issue was solved by adding some allow rules for 'send_msg' as follows:

Try doing pip install dbus-python. It worked for me on fedora 34.

std::async returns a future that completes with the return value of the function passed to std::async.

The second assignment to the future will block until the call to sendRequestA completes (it blocks because of the destructor of the previous std::future instance). It does not wait until the reply callback is received (unless you are blocking in sendRequestA but that would be strange).

m_future.get() in your reply callbacks will block until the future is resolved (sendRequestA returns). However, it will have been sent already (because that is the only way you would get a reply) and so the .get() call would return immediately.

I think you want to be using something more like std::promise. In your reply callback you would call std::promise::set_value to resolve the future. Calls to the destructor of the future associated with the std::promise or to std::future::get will block until std::promise::set_value is called (or the promise is destroyed).

At the bottom of https://www.freedesktop.org/wiki/Software/DBusBindings/ it suggests that dbus-python should not be used for new projects.

With pydbus your example would look like:

You can use -o /dev/null to discard the output altogether, or you could send it to a temporary file which you then delete. If you're concerned with compile times, you can add -E in order to only run the preprocessor, which is the minimum in order for -H to work. That works because if you tell gcc to stop after preprocessing (-H), it doesn't matter if you also tell it to stop after creating an object file (-c). (That's an exception to the general rule that gcc uses the last of a set of conflicting options, which is designed to let you override options by adding to the end of a command-line.)

However, I can't help thinking that this is not really the best solution to your problem. It seems like you've hand-crafted a compiler invocation with a number of options, and then put it somewhere where it's difficult to modify. A better solution would be to use a makefile and set the value of the various standard makefile variables -- such as CFLAGS, CPPFLAGS, LDFLAGS, LDLIBS -- which are documented in the Gnu make manual. In simple cases, your Makefile might consist only of lines which set these variables, since Gnu make has built-in rules for common targets.

Here is an illustration of how two sibling child processes are linked into their parent process's list of children:

I extended the dbus-python example service to have a list of dictionaries like you were trying to do.

I think you were missing an a for the array and then a second a for the dictionary.

The following worked for me:

You need to add -DGWEATHER_I_KNOW_THIS_IS_UNSTABLE to your C compilation arguments. If you're using Meson, GNOME Clocks has a good example.

Be sure you understand why the library authors make you do this. The library API/ABI might still change in the future, and you may have to update your code accordingly if that happens. (For example, there's an open merge request to remove all the GTK widgets so the rest of the library can link with GTK4 apps).