This post discusses the differences between the DBus interface in GNOME Shell 3.6 and GNOME Shell 3.4. I also demonstrate how to use some of the new methods provided to remove an installed extension, to download and install an extension from extensions.gnome.org, and how to flash your screen.
Many people are unaware that the GNOME Shell has a DBus interface which can be used to programmatically interact with the GNOME Shell. This post shows you a number of ways to use DBus to interact with the GNOME 3.4 Shell.
In this post, I demonstrate how you can add D-Bus support to a GNOME Shell or Cinnamon extension and allow a command line utility to control the operating characteristics of the extension via a command line utility.
This post discusses the D-Bus interface to the GNOME Shell and Cinnamon and shows you how a simple command line tool called cinnamon-tool can be used to enable or disable Cinnamon extensions via D-Bus.
The documentation on retrieving or setting an D-Bus object’s properties using Python is pityful and mostly inaccurate. Recently GDBus has replaced dbus-glib as the preferred way to interface with D-Bus on GNOME platforms. The central concepts of D-Bus are modelled in a very similar way in dbus-glib and GDBus. Both have objects representing connections, proxies and method invocations. However there are some important differences: dbus-glib uses the D-Bus libdbus reference implementation, GDBus does not. Instead, it relies on GIO streams as transport layer, and has its own implementation for the the D-Bus connection setup and authentication. dbus-glib uses the GObject