D-Bus - Revision history

Prabuanand: added wikilink

2025-07-28T07:01:30Z

added wikilink

← Older revision		Revision as of 07:01, 28 July 2025
Line 5:		Line 5:
	Install the dbus package: {{cmd\|# apk add {{pkg\|dbus}}}}		Install the dbus package: {{cmd\|# apk add {{pkg\|dbus}}}}

	If ~~X11~~ is used, install the {{pkg\|dbus-x11}} package which provides the {{ic\|dbus-launch}} command needed for [[#D-Bus session bus\|D-Bus session bus]] as follows:{{cmd\|# apk add {{pkg\|dbus-x11}}}}		If [[Xorg]] is used, install the {{pkg\|dbus-x11}} package which provides the {{ic\|dbus-launch}} command needed for [[#D-Bus session bus\|D-Bus session bus]] as follows:{{cmd\|# apk add {{pkg\|dbus-x11}}}}

	== Configuration ==		== Configuration ==

Prabuanand: fixed typo

2025-06-01T03:15:49Z

fixed typo

← Older revision		Revision as of 03:15, 1 June 2025
Line 27:		Line 27:
	Running <code>dbus-launch</code> in a terminal requires {{ic\|export $(dbus-launch)}}. If not, other running process won't find the socket of D-Bus session Bus.		Running <code>dbus-launch</code> in a terminal requires {{ic\|export $(dbus-launch)}}. If not, other running process won't find the socket of D-Bus session Bus.

	{{Tip\| If D-Bus session bus is properly configured, the command:{{ic\|$ echo $DBUS_SESSION_BUS_ADDRESS}} must provide a output.}}		{{Tip\|If D-Bus session bus is properly configured, the command:{{ic\|$ echo $DBUS_SESSION_BUS_ADDRESS}} must provide an output.}}

	If <code>$DBUS_SESSION_BUS_ADDRESS</code> is undefined, many applications will attempt to use the standard path:{{ic\|$XDG_RUNTIME_DIR/bus}}		If <code>$DBUS_SESSION_BUS_ADDRESS</code> is undefined, many applications will attempt to use the standard path:{{ic\|$XDG_RUNTIME_DIR/bus}}

Prabuanand: redone the page to clarify the difference between System D-Bus and D-Bus session bus

2025-06-01T03:13:19Z

redone the page to clarify the difference between System D-Bus and D-Bus session bus

← Older revision		Revision as of 03:13, 1 June 2025
Line 4:		Line 4:

	Install the dbus package: {{cmd\|# apk add {{pkg\|dbus}}}}		Install the dbus package: {{cmd\|# apk add {{pkg\|dbus}}}}
	~~If you are using x11 you might also want to install the X11 add-ons which provide the <code>dbus-launch</code> command:{{cmd\|# apk add {{pkg\|dbus-x11}}}}~~
	~~If you want dbus to be started at system startup enable the [[OpenRC]] service: {{cmd\|# rc-update add dbus}}~~
	~~To start the service immediately, use service '''start\|stop\|restart''' commands as follows: {{cmd\|# rc-service dbus start}}~~

	{{~~Tip~~\|~~If system D~~-~~Bus is running,~~ the ~~command:~~{{ic\|~~$ rc~~-~~service dbus status~~}} ~~will output~~ {{ic\|* status: started}}.}}		If X11 is used, install the {{pkg\|dbus-x11}} package which provides the {{ic\|dbus-launch}} command needed for [[#D-Bus session bus\|D-Bus session bus]] as follows:{{cmd\|# apk add {{pkg\|dbus-x11}}}}

	== ~~D-Bus session~~ ==		== Configuration ==

	System D-Bus service needs to be installed and running before launching a D-Bus session instance. You can start a {{ic\|dbus session}} using the command like this: {{ic\|dbus-run-session -- sh}}, by replacing '''sh''' with your shell or a window manager.		=== System D-Bus ===

	If ~~you are~~ running ~~a X11 based window manager using~~ {{~~Path~~\|.~~xinitrc~~}}, use : {{ic\|~~exec~~ dbus-~~launch~~ --~~exit~~-with~~-session your_favourite_wm~~}} so that D-Bus passes the environment variable <code>$DBUS_SESSION_BUS_ADDRESS</code> ~~to its children~~. Running <code>dbus-launch</code> in a terminal ~~means that~~ other running process won't find ~~this~~ D-Bus~~'s socket without a <code>export $(dbus-launch)</code>~~.		To start system D-Bus service {{ic\|dbus}} at startup, enable it as follows: {{cmd\|# rc-update add dbus}}

			To start the system D-Bus service immediately, use [[OpenRC]] service '''start\|stop\|restart''' commands as follows: {{cmd\|# rc-service dbus start}}

			{{Tip\|If System D-Bus is running, the command:{{ic\|$ rc-service dbus status}} will output {{ic\|* status: started}}.}}

			=== D-Bus session bus===

			{{Note\|System D-Bus service needs to be running before launching an instance of D-Bus session bus.}}

			To start a window manager along with D-bus session bus, use the command: {{ic\|$ dbus-run-session -- <your_wm>}} by replacing '''<your_wm>''' with your shell or a window manager.

			If X11 based window manager is started using {{Path\|.xinitrc}}, to ensure that D-Bus session bus passes the environment variable <code>$DBUS_SESSION_BUS_ADDRESS</code>, add an entry as follows {{Cat\|.xinitrc\|exec dbus-launch --exit-with-session <your_wm>}}

			Running <code>dbus-launch</code> in a terminal requires {{ic\|export $(dbus-launch)}}. If not, other running process won't find the socket of D-Bus session Bus.

	{{Tip\| If D-Bus session bus is properly configured, the command:{{ic\|$ echo $DBUS_SESSION_BUS_ADDRESS}} must provide a output.}}		{{Tip\| If D-Bus session bus is properly configured, the command:{{ic\|$ echo $DBUS_SESSION_BUS_ADDRESS}} must provide a output.}}

Prabuanand: rephrased sentence and links that might cause ambiguity

2025-05-31T16:10:13Z

rephrased sentence and links that might cause ambiguity

← Older revision		Revision as of 16:10, 31 May 2025
Line 1:		Line 1:
	[https://en.wikipedia.org/wiki/D-Bus D-Bus] is a message bus system that provides a mechanism for inter-process communication~~. System D-Bus service needs to be [[#Installation\|installed]] before launching a [[#D-Bus session\|D-Bus session]] instance.~~		[https://en.wikipedia.org/wiki/D-Bus D-Bus] is a message bus system that provides a mechanism for inter-process communication.

	Some services like [[PipeWire#D-Bus\|Pipewire]] rely on a [[#D-Bus session\|D-Bus session]] instance or expect it by default. Other processes will only be able to communicate with these services if D-Bus is running.

	== Installation ==		== Installation ==

	~~{{Tip\|Check if system D-Bus service is already installed and running:{{ic\|$ rc-service dbus status}}, before proceeding futher.}}~~

	Install the dbus package: {{cmd\|# apk add {{pkg\|dbus}}}}		Install the dbus package: {{cmd\|# apk add {{pkg\|dbus}}}}
Line 11:		Line 7:
	If you want dbus to be started at system startup enable the [[OpenRC]] service: {{cmd\|# rc-update add dbus}}		If you want dbus to be started at system startup enable the [[OpenRC]] service: {{cmd\|# rc-update add dbus}}
	To start the service immediately, use service '''start\|stop\|restart''' commands as follows: {{cmd\|# rc-service dbus start}}		To start the service immediately, use service '''start\|stop\|restart''' commands as follows: {{cmd\|# rc-service dbus start}}

			{{Tip\|If system D-Bus is running, the command:{{ic\|$ rc-service dbus status}} will output {{ic\|* status: started}}.}}

	== D-Bus session ==		== D-Bus session ==

	{{~~Tip~~\| ~~If D-Bus~~ session ~~bus is properly configured,~~ the command:{{ic\|~~$ echo $DBUS_SESSION_BUS_ADDRESS~~}} ~~must provide~~ a ~~output~~.}}		System D-Bus service needs to be installed and running before launching a D-Bus session instance. You can start a {{ic\|dbus session}} using the command like this: {{ic\|dbus-run-session -- sh}}, by replacing '''sh''' with your shell or a window manager.

	~~You can start~~ a {{ic\|~~dbus session~~}} ~~using the command like this~~: {{ic\|dbus-~~run~~-~~session~~ -- sh}}~~, by replacing '~~''~~sh''' with your shell or~~ a ~~window manager~~.		If you are running a X11 based window manager using {{Path\|.xinitrc}}, use : {{ic\|exec dbus-launch --exit-with-session your_favourite_wm}} so that D-Bus passes the environment variable <code>$DBUS_SESSION_BUS_ADDRESS</code> to its children. Running <code>dbus-launch</code> in a terminal means that other running process won't find this D-Bus's socket without a <code>export $(dbus-launch)</code>.

	~~If you are running a X11 based window manager using~~ {{~~Path~~\|~~.xinitrc}}~~, ~~use~~ : {{ic\|~~exec dbus-launch --exit-with-session your_favourite_wm~~}} ~~so that D-Bus passes the environment variable <code>$DBUS_SESSION_BUS_ADDRESS</code> to its children. Running <code>dbus-launch</code> in~~ a ~~terminal means that other running process won't find this D-Bus's socket without a <code>export $(dbus-launch)</code>~~.		{{Tip\| If D-Bus session bus is properly configured, the command:{{ic\|$ echo $DBUS_SESSION_BUS_ADDRESS}} must provide a output.}}

	If <code>$DBUS_SESSION_BUS_ADDRESS</code> is undefined, many applications will attempt to use the standard path:{{ic\|$XDG_RUNTIME_DIR/bus}}		If <code>$DBUS_SESSION_BUS_ADDRESS</code> is undefined, many applications will attempt to use the standard path:{{ic\|$XDG_RUNTIME_DIR/bus}}
Line 43:		Line 41:
	== See also ==		== See also ==

	* [[PipeWire#D-Bus\|Pipewire and D-Bus]]
	* [https://wiki.archlinux.org/title/D-Bus Archwiki]		* [https://wiki.archlinux.org/title/D-Bus Archwiki]
	* [https://wiki.gentoo.org/wiki/D-Bus Gentoo Wiki]		* [https://wiki.gentoo.org/wiki/D-Bus Gentoo Wiki]

	[[Category:System Administration]]		[[Category:System Administration]]

Prabuanand: added back a tip to check the service and changed introduction paragraph

2025-05-24T10:17:50Z

added back a tip to check the service and changed introduction paragraph

← Older revision		Revision as of 10:17, 24 May 2025
Line 1:		Line 1:
	[https://en.wikipedia.org/wiki/D-Bus D-Bus] is a message bus system that provides a mechanism for inter-process communication.		[https://en.wikipedia.org/wiki/D-Bus D-Bus] is a message bus system that provides a mechanism for inter-process communication. System D-Bus service needs to be [[#Installation\|installed]] before launching a [[#D-Bus session\|D-Bus session]] instance.

	Some services rely on a D-Bus session instance or expect it by default ~~(including [[PipeWire#D-Bus\|Pipewire]])~~. Other processes will only be able to communicate with these services if d-~~bus~~ is running.		Some services like [[PipeWire#D-Bus\|Pipewire]] rely on a [[#D-Bus session\|D-Bus session]] instance or expect it by default. Other processes will only be able to communicate with these services if D-Bus is running.

	== Installation ==		== Installation ==

			{{Tip\|Check if system D-Bus service is already installed and running:{{ic\|$ rc-service dbus status}}, before proceeding futher.}}

	Install the dbus package: {{cmd\|# apk add {{pkg\|dbus}}}}		Install the dbus package: {{cmd\|# apk add {{pkg\|dbus}}}}
	If you are using x11 you might also want to install the X11 add-ons which provide the <code>dbus-launch</code> command:{{cmd\|# apk add {{pkg\|dbus-x11}}}}		If you are using x11 you might also want to install the X11 add-ons which provide the <code>dbus-launch</code> command:{{cmd\|# apk add {{pkg\|dbus-x11}}}}
	If you want dbus to be started at system startup enable the [[OpenRC]] service: {{cmd\|# rc-update add dbus}}		If you want dbus to be started at system startup enable the [[OpenRC]] service: {{cmd\|# rc-update add dbus}}
	To ~~use~~ the service immediately ~~without restarting~~, start ~~it manually~~: {{cmd\|# rc-service dbus start}}		To start the service immediately, use service '''start\|stop\|restart''' commands as follows: {{cmd\|# rc-service dbus start}}

	~~The above commands related to {{ic\|dbus service}} only starts the system D-bus. The [[#D-Bus session\|~~D-Bus session~~]] needs to be started separately for each user.~~		== D-Bus session ==

	== D-Bus session ==		{{Tip\| If D-Bus session bus is properly configured, the command:{{ic\|$ echo $DBUS_SESSION_BUS_ADDRESS}} must provide a output.}}

	You can start a {{ic\|dbus session}} using the command like this: {{ic\|dbus-run-session -- sh}}, by replacing '''sh''' with your shell or a window manager.		You can start a {{ic\|dbus session}} using the command like this: {{ic\|dbus-run-session -- sh}}, by replacing '''sh''' with your shell or a window manager.

Prabuanand: Reworded sentence and updated wikitags

2025-05-07T07:05:24Z

Reworded sentence and updated wikitags

← Older revision		Revision as of 07:05, 7 May 2025
Line 5:		Line 5:
	== Installation ==		== Installation ==

	Install the dbus package:		Install the dbus package: {{cmd\|# apk add {{pkg\|dbus}}}}
	{{cmd\|# apk add {{pkg\|dbus}}}}		If you are using x11 you might also want to install the X11 add-ons which provide the <code>dbus-launch</code> command:{{cmd\|# apk add {{pkg\|dbus-x11}}}}
	If you are using x11 you might also want to install the X11 add-ons which provide the <code>dbus-launch</code> command:		If you want dbus to be started at system startup enable the [[OpenRC]] service: {{cmd\|# rc-update add dbus}}
	{{cmd\|# apk add {{pkg\|dbus-x11}}}}		To use the service immediately without restarting, start it manually: {{cmd\|# rc-service dbus start}}
	If you want dbus to be started at system startup enable the service:
	{{cmd\|# rc-update add dbus}}		The above commands related to {{ic\|dbus service}} only starts the system D-bus. The [[#D-Bus session\|D-Bus session]] needs to be started separately for each user.
	To use the service without restarting ~~you need to~~ start it manually:
	{{cmd\|# rc-service dbus start}}
	{{~~note~~\|~~This~~ only starts the system ~~dbus~~. The ~~dbus~~ session is started ~~separatly~~ for each user.}}

	== D-Bus session ==		== D-Bus session ==

	You can start a dbus session like this: ~~<code>~~dbus-run-session -- sh~~</code>(~~replacing sh with your shell or a window manager~~), or, <code>export $(dbus-launch)</code>~~.		You can start a {{ic\|dbus session}} using the command like this: {{ic\|dbus-run-session -- sh}}, by replacing '''sh''' with your shell or a window manager.

	D-Bus passes the environment variable <code>$DBUS_SESSION_BUS_ADDRESS</code> to its children. Running <code>dbus-launch</code> in a terminal means that other running process won't find this D-Bus's socket.		If you are running a X11 based window manager using {{Path\|.xinitrc}}, use : {{ic\|exec dbus-launch --exit-with-session your_favourite_wm}} so that D-Bus passes the environment variable <code>$DBUS_SESSION_BUS_ADDRESS</code> to its children. Running <code>dbus-launch</code> in a terminal means that other running process won't find this D-Bus's socket without a <code>export $(dbus-launch)</code>.

	If <code>$DBUS_SESSION_BUS_ADDRESS</code> is undefined, many applications will attempt to use the standard path:		If <code>$DBUS_SESSION_BUS_ADDRESS</code> is undefined, many applications will attempt to use the standard path:{{ic\|$XDG_RUNTIME_DIR/bus}}

	~~$XDG_RUNTIME_DIR/bus~~

	~~Running D-Bus like so should work for many applications:~~

	{{~~Cmd~~\|~~dbus-daemon --nofork --address unix:path{{=}}~~$XDG_RUNTIME_DIR/bus ~~--session~~}}

			Running D-Bus like so should work for many applications: {{Cmd\|dbus-daemon --nofork --address unix:path{{=}}$XDG_RUNTIME_DIR/bus --session}}

	For applications that dont work without <code>$DBUS_SESSION_BUS_ADDRESS</code> you can prepend your program with the follow workaround script which avoid launching multiple user dbus sessions:		For applications that dont work without <code>$DBUS_SESSION_BUS_ADDRESS</code> you can prepend your program with the follow workaround script which avoid launching multiple user dbus sessions:
Line 48:		Line 40:

	== See also ==		== See also ==

	* [[PipeWire#D-Bus\|Pipewire and D-Bus]]		* [[PipeWire#D-Bus\|Pipewire and D-Bus]]
	* [https://wiki.archlinux.org/title/D-Bus Archwiki]		* [https://wiki.archlinux.org/title/D-Bus Archwiki]

Sertonix: add actual installation instructions

2023-10-27T19:05:45Z

add actual installation instructions

@@ Line 3: / Line 3: @@
 Some services rely on a D-Bus session instance or expect it by default (including [[PipeWire#D-Bus|Pipewire]]). Other processes will only be able to communicate with these services if d-bus is running.
-You can start a dbus session like this: <code>dbus-run-session -- sh</code>(replacing sh with your shell or a window manager), or, <code>export $(dbus-launch)</code>. This is distinct from running dbus system-wide: <code>rc-service dbus start</code>, which is a prerequisite to run a user dbus session.
+== Installation ==
 D-Bus passes the environment variable <code>$DBUS_SESSION_BUS_ADDRESS</code> to its children. Running <code>dbus-launch</code> in a terminal means that other running process won't find this  D-Bus's socket.

Sertonix: link to arch and gentoo wiki in "See also"

2023-10-27T18:42:32Z

link to arch and gentoo wiki in "See also"

← Older revision		Revision as of 18:42, 27 October 2023
Line 35:		Line 35:
	== See also ==		== See also ==
	* [[PipeWire#D-Bus\|Pipewire and D-Bus]]		* [[PipeWire#D-Bus\|Pipewire and D-Bus]]
			* [https://wiki.archlinux.org/title/D-Bus Archwiki]
			* [https://wiki.gentoo.org/wiki/D-Bus Gentoo Wiki]

	[[Category:System Administration]]		[[Category:System Administration]]

Sertonix: pipewire only needs to be configured to run without dbus

2023-10-27T17:32:27Z

pipewire only needs to be configured to run without dbus

← Older revision		Revision as of 17:32, 27 October 2023
Line 1:		Line 1:
	[https://en.wikipedia.org/wiki/D-Bus D-Bus] is a message bus system that provides a mechanism for inter-process communication.		[https://en.wikipedia.org/wiki/D-Bus D-Bus] is a message bus system that provides a mechanism for inter-process communication.

	Some services (including [[PipeWire]]) ~~rely on a D-Bus session instance~~. Other processes will only be able to communicate with these services if d-bus is running.		Some services rely on a D-Bus session instance or expect it by default (including [[PipeWire#D-Bus\|Pipewire]]). Other processes will only be able to communicate with these services if d-bus is running.

	You can start a dbus session like this: <code>dbus-run-session -- sh</code>(replacing sh with your shell or a window manager), or, <code>export $(dbus-launch)</code>. This is distinct from running dbus system-wide: <code>rc-service dbus start</code>, which is a prerequisite to run a user dbus session.		You can start a dbus session like this: <code>dbus-run-session -- sh</code>(replacing sh with your shell or a window manager), or, <code>export $(dbus-launch)</code>. This is distinct from running dbus system-wide: <code>rc-service dbus start</code>, which is a prerequisite to run a user dbus session.
Line 32:		Line 32:
	$@		$@
	fi		fi

			== See also ==
			* [[PipeWire#D-Bus\|Pipewire and D-Bus]]

	[[Category:System Administration]]		[[Category:System Administration]]

Sertonix: link to PipeWire page

2023-07-04T18:02:42Z

link to PipeWire page

← Older revision		Revision as of 18:02, 4 July 2023
Line 1:		Line 1:
	[https://en.wikipedia.org/wiki/D-Bus D-Bus] is a message bus system that provides a mechanism for inter-process communication.		[https://en.wikipedia.org/wiki/D-Bus D-Bus] is a message bus system that provides a mechanism for inter-process communication.

	Some services (including ~~Pipewire~~) rely on a D-Bus session instance. Other processes will only be able to communicate with these services if d-bus is running.		Some services (including [[PipeWire]]) rely on a D-Bus session instance. Other processes will only be able to communicate with these services if d-bus is running.

	You can start a dbus session like this: <code>dbus-run-session -- sh</code>(replacing sh with your shell or a window manager), or, <code>export $(dbus-launch)</code>. This is distinct from running dbus system-wide: <code>rc-service dbus start</code>, which is a prerequisite to run a user dbus session.		You can start a dbus session like this: <code>dbus-run-session -- sh</code>(replacing sh with your shell or a window manager), or, <code>export $(dbus-launch)</code>. This is distinct from running dbus system-wide: <code>rc-service dbus start</code>, which is a prerequisite to run a user dbus session.

← Older revision		Revision as of 03:15, 1 June 2025
Line 27:		Line 27:
	Running <code>dbus-launch</code> in a terminal requires {{ic\|export $(dbus-launch)}}. If not, other running process won't find the socket of D-Bus session Bus.		Running <code>dbus-launch</code> in a terminal requires {{ic\|export $(dbus-launch)}}. If not, other running process won't find the socket of D-Bus session Bus.

	{{Tip\| If D-Bus session bus is properly configured, the command:{{ic\|$ echo $DBUS_SESSION_BUS_ADDRESS}} must provide a output.}}		{{Tip\|If D-Bus session bus is properly configured, the command:{{ic\|$ echo $DBUS_SESSION_BUS_ADDRESS}} must provide an output.}}

	If <code>$DBUS_SESSION_BUS_ADDRESS</code> is undefined, many applications will attempt to use the standard path:{{ic\|$XDG_RUNTIME_DIR/bus}}		If <code>$DBUS_SESSION_BUS_ADDRESS</code> is undefined, many applications will attempt to use the standard path:{{ic\|$XDG_RUNTIME_DIR/bus}}

← Older revision		Revision as of 03:13, 1 June 2025
Line 4:		Line 4:

	Install the dbus package: {{cmd\|# apk add {{pkg\|dbus}}}}		Install the dbus package: {{cmd\|# apk add {{pkg\|dbus}}}}
	~~If you are using x11 you might also want to install the X11 add-ons which provide the <code>dbus-launch</code> command:{{cmd\|# apk add {{pkg\|dbus-x11}}}}~~
	~~If you want dbus to be started at system startup enable the [[OpenRC]] service: {{cmd\|# rc-update add dbus}}~~
	~~To start the service immediately, use service '''start\|stop\|restart''' commands as follows: {{cmd\|# rc-service dbus start}}~~

	{{~~Tip~~\|~~If system D~~-~~Bus is running,~~ the ~~command:~~{{ic\|~~$ rc~~-~~service dbus status~~}} ~~will output~~ {{ic\|* status: started}}.}}		If X11 is used, install the {{pkg\|dbus-x11}} package which provides the {{ic\|dbus-launch}} command needed for [[#D-Bus session bus\|D-Bus session bus]] as follows:{{cmd\|# apk add {{pkg\|dbus-x11}}}}

	== ~~D-Bus session~~ ==		== Configuration ==

	System D-Bus service needs to be installed and running before launching a D-Bus session instance. You can start a {{ic\|dbus session}} using the command like this: {{ic\|dbus-run-session -- sh}}, by replacing '''sh''' with your shell or a window manager.		=== System D-Bus ===

	If ~~you are~~ running ~~a X11 based window manager using~~ {{~~Path~~\|.~~xinitrc~~}}, use : {{ic\|~~exec~~ dbus-~~launch~~ --~~exit~~-with~~-session your_favourite_wm~~}} so that D-Bus passes the environment variable <code>$DBUS_SESSION_BUS_ADDRESS</code> ~~to its children~~. Running <code>dbus-launch</code> in a terminal ~~means that~~ other running process won't find ~~this~~ D-Bus~~'s socket without a <code>export $(dbus-launch)</code>~~.		To start system D-Bus service {{ic\|dbus}} at startup, enable it as follows: {{cmd\|# rc-update add dbus}}

			To start the system D-Bus service immediately, use [[OpenRC]] service '''start\|stop\|restart''' commands as follows: {{cmd\|# rc-service dbus start}}

			{{Tip\|If System D-Bus is running, the command:{{ic\|$ rc-service dbus status}} will output {{ic\|* status: started}}.}}

			=== D-Bus session bus===

			{{Note\|System D-Bus service needs to be running before launching an instance of D-Bus session bus.}}

			To start a window manager along with D-bus session bus, use the command: {{ic\|$ dbus-run-session -- <your_wm>}} by replacing '''<your_wm>''' with your shell or a window manager.

			If X11 based window manager is started using {{Path\|.xinitrc}}, to ensure that D-Bus session bus passes the environment variable <code>$DBUS_SESSION_BUS_ADDRESS</code>, add an entry as follows {{Cat\|.xinitrc\|exec dbus-launch --exit-with-session <your_wm>}}

			Running <code>dbus-launch</code> in a terminal requires {{ic\|export $(dbus-launch)}}. If not, other running process won't find the socket of D-Bus session Bus.

	{{Tip\| If D-Bus session bus is properly configured, the command:{{ic\|$ echo $DBUS_SESSION_BUS_ADDRESS}} must provide a output.}}		{{Tip\| If D-Bus session bus is properly configured, the command:{{ic\|$ echo $DBUS_SESSION_BUS_ADDRESS}} must provide a output.}}

← Older revision		Revision as of 10:17, 24 May 2025
Line 1:		Line 1:
	[https://en.wikipedia.org/wiki/D-Bus D-Bus] is a message bus system that provides a mechanism for inter-process communication.		[https://en.wikipedia.org/wiki/D-Bus D-Bus] is a message bus system that provides a mechanism for inter-process communication. System D-Bus service needs to be [[#Installation\|installed]] before launching a [[#D-Bus session\|D-Bus session]] instance.

	Some services rely on a D-Bus session instance or expect it by default ~~(including [[PipeWire#D-Bus\|Pipewire]])~~. Other processes will only be able to communicate with these services if d-~~bus~~ is running.		Some services like [[PipeWire#D-Bus\|Pipewire]] rely on a [[#D-Bus session\|D-Bus session]] instance or expect it by default. Other processes will only be able to communicate with these services if D-Bus is running.

	== Installation ==		== Installation ==

			{{Tip\|Check if system D-Bus service is already installed and running:{{ic\|$ rc-service dbus status}}, before proceeding futher.}}

	Install the dbus package: {{cmd\|# apk add {{pkg\|dbus}}}}		Install the dbus package: {{cmd\|# apk add {{pkg\|dbus}}}}
	If you are using x11 you might also want to install the X11 add-ons which provide the <code>dbus-launch</code> command:{{cmd\|# apk add {{pkg\|dbus-x11}}}}		If you are using x11 you might also want to install the X11 add-ons which provide the <code>dbus-launch</code> command:{{cmd\|# apk add {{pkg\|dbus-x11}}}}
	If you want dbus to be started at system startup enable the [[OpenRC]] service: {{cmd\|# rc-update add dbus}}		If you want dbus to be started at system startup enable the [[OpenRC]] service: {{cmd\|# rc-update add dbus}}
	To ~~use~~ the service immediately ~~without restarting~~, start ~~it manually~~: {{cmd\|# rc-service dbus start}}		To start the service immediately, use service '''start\|stop\|restart''' commands as follows: {{cmd\|# rc-service dbus start}}

	~~The above commands related to {{ic\|dbus service}} only starts the system D-bus. The [[#D-Bus session\|~~D-Bus session~~]] needs to be started separately for each user.~~		== D-Bus session ==

	== D-Bus session ==		{{Tip\| If D-Bus session bus is properly configured, the command:{{ic\|$ echo $DBUS_SESSION_BUS_ADDRESS}} must provide a output.}}

	You can start a {{ic\|dbus session}} using the command like this: {{ic\|dbus-run-session -- sh}}, by replacing '''sh''' with your shell or a window manager.		You can start a {{ic\|dbus session}} using the command like this: {{ic\|dbus-run-session -- sh}}, by replacing '''sh''' with your shell or a window manager.