Why use dbus

Join our community today! Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions. If you need to reset your password, click here. Having a problem logging in?

Please visit this page to clear all LQ-related cookies. Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use. Click here for more info. I wonder, what are advantages of using dbus.

From the same developers as systemd Dbus originally was just another inter-process communication method that allowed addressing like rpc services do, but using a different addressing scheme.

The developers wormed it into being used for anything and everything. It is embedded in systemd as well. It has been used to pass audio around, configuration options, system daemon to user notifications Personally, I prefer simple text files even XML is overkill, and hard to read as well; so suddenly you get yet another GUI editor for those files One of the issues dbus does address is to separate the X resource database portion of the X server which still exists from the X server. Ideally, include test suite coverage with your patch; or if you report a bug, it's good to add a test that fails even if you don't have a patch otherwise.

Patches to improve test coverage are very welcome, though D-Bus is already among the best-covered codebases around. If you're new to D-Bus, the tutorial is probably the best place to start even though it is very incomplete, the basics are covered. Released versions can be downloaded from the releases directory on dbus.

If in doubt, use your distribution's packages. The current stable branch is dbus 1. This is the recommended version for most purposes. The current legacy branch is dbus 1. Older branches such as 1. Please contact the maintainers for more information. It's only purpose, as far as I can see, is keeping bloatware connected in run time, to do absolutely nothing.

D-Bus is usually used for things like telling a DE panel to display a tray icon and similarly peripheral stuff.

There is some overlap with X11 there. Never see a application launching dbus itself, but like many users says here ,there are applications that need it for example, lilyterm writen in gkt2 and is not way to get out dbus in that application. Jose said:. I thought of a daemon that requires Dbus: Avahi. Sometimes worrying about it isn't worth the time. Years ago on my Gentoo desktop I turned off dbus and did a rebuild, could not tell any difference for a few days Matlib Member Reaction score: 34 Messages: Gimp used to work without dbus back in the day, so it should be possible to reverse that code sabotage.

PMc said:. It is a good thing I hate gnome 3 and programs that force gtk3 on me, and now I see my annoyance and hatred of d-bus is now justified. I want it gone. But too bad, I just moved my desktop to openbsd since the freebsd installer doesn't want to work on my new laptop.

Is there some flag I can set to get programs to build with gtk2 instead in my make. Yes, that's one of them. ServiceUnknown: The name org. Bus was not provided by any. Some allow to be started without dbus , ie: terminator --no-dbus I see no difference in behavior.

What was the purpose of the above script? Are there applications that don't work without dbus? Improve this question. Add a comment. Active Oldest Votes. From terminator's man page , we see: --new-tab If this is specified and Terminator is already running, DBus will be used to spawn a new tab in the first Terminator window.

Introspectable interface - - -. Introspect method - s - org. Peer interface - - -. GetMachineId method - s -. Ping method - - - org. Properties interface - - -.

Get method ss v -. Set method ssv - -. Service interface - - -. AttachProcesses method sau - -. GetProcesses method - a sus -. AllowedCPUs property ay 0 -. AllowedMemoryNodes property ay 0 -. AmbientCapabilities property t 0 const.

AppArmorProfile property bs false "" const. BindPaths property a ssbt 0 const. BindReadOnlyPaths property a ssbt 0 const. BlockIOAccounting property b false -.

BlockIODeviceWeight property a st 0 -. BlockIOReadBandwidth property a st 0 -. BlockIOWeight property t -. BlockIOWriteBandwidth property a st 0 -. BusName property s "" const. CPUAccounting property b false -. CPUAffinity property ay 0 const. CPUSchedulingPolicy property i 0 const. CPUSchedulingPriority property i 0 const. CPUShares property t -. CPUWeight property t -. CacheDirectory property as 0 const.

CacheDirectoryMode property u const. CapabilityBoundingSet property t const. CleanResult property s "success" emits-change. ConfigurationDirectory property as 0 const. ConfigurationDirectoryMode property u const.

ControlPID property u 0 emits-change. CoredumpFilter property t 51 const. DefaultMemoryLow property t 0 -. DefaultMemoryMin property t 0 -. Delegate property b false -. DelegateControllers property as 0 -. DeviceAllow property a ss 0 -. DevicePolicy property s "auto" -. DisableControllers property as 0 -. DynamicUser property b false const. EffectiveCPUs property ay 0 -. EffectiveMemoryNodes property ay 0 -.

Environment property as 0 const. ExecCondition property a sasbttttuii 0 emits-invalidation. ExecConditionEx property a sasasttttuii 0 emits-invalidation. ExecMainCode property i 0 emits-change. ExecMainExitTimestamp property t 0 emits-change. ExecMainExitTimestampMonotonic property t 0 emits-change. ExecMainPID property u emits-change. ExecMainStartTimestamp property t emits-change.

ExecMainStartTimestampMonotonic property t emits-change. ExecMainStatus property i 0 emits-change. ExecStartPost property a sasbttttuii 0 emits-invalidation. ExecStartPostEx property a sasasttttuii 0 emits-invalidation.

ExecStop property a sasbttttuii 0 emits-invalidation. ExecStopEx property a sasasttttuii 0 emits-invalidation.