LabWC - Revision history

Prabuanand: removed :Category:Desktop as per Help_talk:Style

2025-05-25T15:26:59Z

removed Category:Desktop as per Help_talk:Style

← Older revision		Revision as of 15:26, 25 May 2025
Line 48:		Line 48:
	== See also ==		== See also ==

	[https://labwc.github.io LabWC Official website]		* [https://labwc.github.io LabWC Official website]


	~~[[Category:Desktop]]~~
	~~[[Category:Wayland]]~~
	[[Category:compositor]]		[[Category:compositor]]

Prabuanand: added heading Prerequisites and made some changes related to seat manager and others

2025-03-17T10:35:57Z

added heading Prerequisites and made some changes related to seat manager and others

← Older revision		Revision as of 10:35, 17 March 2025
Line 1:		Line 1:
	[https://labwc.github.io LabWC] is a stacking [[Wayland]] compositor. LabWC can serve as a drop-in replacement for the [[Openbox]] window manager.		[https://labwc.github.io LabWC] is a stacking [[Wayland]] compositor. LabWC can serve as a drop-in replacement for the [[Openbox]] window manager.

	== ~~Installation~~ ==		== Prerequisites ==
	{{:Include:Desktop prerequisites}}		{{:Include:Desktop prerequisites}}
			* Wayland compositors need raw access to input and output devices, typically mediated by a [[seat manager]]. Either [[seatd]] or [[elogind]] work fine, but installing both leads to conflicts.
			* Setting up [[Alpine_setup_scripts#setup-wayland-base\|Wayland-base]] enables [[elogind]] as [[Seat manager\|seat manager]], enables [[Repositories#Community\|community repository]] and enables [[eudev]].

	The <Code>setup-wayland-base</Code> script installs and enables [[elogind]] as [[Seat manager\|seat manager]], enables [[Repositories#Community\|community repository]] and enables [[eudev]] automatically as these are required for Wayland to work.		== Installation ==

	=== ~~Set up eudev~~ ===
	~~{{:Include:Setup Device Manager}}~~

	~~=== Setup up a seat manager ===~~

	~~Wayland compositors need raw access to input and output devices. This is mediated by a [[seat manager]].~~

	~~Configure either [[seatd]] or [[elogind]] as both are supported. However using both may lead to conflicts.~~

	~~=== Install fonts ===~~

	~~Install DejaVu fonts, which has good Unicode coverage:~~
	~~{{cmd\|# apk add font-dejavu}}~~

	~~===~~ Install ~~labwc ===~~		Install labwc:
	~~We can now install~~ labwc:
	{{Cmd\|# apk add labwc labwc-doc		{{Cmd\|# apk add labwc labwc-doc
	# apk add \ # Install optional dependencies:		# apk add \ # Install optional dependencies:
Line 30:		Line 17:
	swaybg \ # wallpaper daemon		swaybg \ # wallpaper daemon
	swayidle \ # idle management (DPMS) daemon		swayidle \ # idle management (DPMS) daemon
	dbus-x11		dbus-x11 \
			font-dejavu
	}}		}}

Prabuanand: rearranged headings and added Include:Desktop prerequisites

2025-01-09T07:07:13Z

rearranged headings and added Include:Desktop prerequisites

← Older revision		Revision as of 07:07, 9 January 2025
Line 1:		Line 1:
	[https://labwc.github.io LabWC] is a stacking [[Wayland]] compositor. ~~Although [https://github.com/labwc/labwc#1-what-is-this it wasn't intended like that], it~~ can serve as a drop-in replacement for the [[Openbox]] window manager ~~(the same way [[Sway]] is for [[I3wm]])~~.		[https://labwc.github.io LabWC] is a stacking [[Wayland]] compositor. LabWC can serve as a drop-in replacement for the [[Openbox]] window manager.

	~~This wiki was written starting from a fresh install using the Alpine 3.16 x86 extended .iso. The steps begin from the first reboot after running setup-alpine and performing a sys install to disk.~~		== Installation ==
			{{:Include:Desktop prerequisites}}
	Many steps below were taken from the [[Sway\|wiki entry for installing Sway]], as both are wlroots-based Wayland compositors. Another interesting page, because of the same reasons, is the [[River]] compositor's.

	== ~~Prerequisites~~ ==
	~~{{Note\|These steps posted as both Sway and LabWC prerequisites could be applied to almost all wlroots-based Wayland compositors.}}~~

	{{:Include:~~Setup_Device_Manager~~}}

	~~Then install the mesa gallium drivers:~~		The <Code>setup-wayland-base</Code> script installs and enables [[elogind]] as [[Seat manager\|seat manager]], enables [[Repositories#Community\|community repository]] and enables [[eudev]] automatically as these are required for Wayland to work.

	{{~~Cmd\|# apk add mesa-dri-gallium~~}}		=== Set up eudev ===
			{{:Include:Setup Device Manager}}

	~~The following links contain guides for setting~~ up ~~the video stack.~~		=== Setup up a seat manager ===

	* [[~~Intel Video]]~~		Wayland compositors need raw access to input and output devices. This is mediated by a [[seat manager]].
	* [[Radeon Video]]

	~~Add yourself~~ to ~~the input and video groups:~~		Configure either [[seatd]] or [[elogind]] as both are supported. However using both may lead to conflicts.

			=== Install fonts ===

	~~{{Cmd\|# adduser $USER input~~		Install DejaVu fonts, which has good Unicode coverage:
	~~# adduser $USER video~~		{{cmd\|# apk add font-dejavu}}
	}}

	~~You have to log out and back in for this to take effect.~~

	Install ~~some TTF~~ fonts:

	{{~~Cmd~~\|# apk add font-dejavu}}

	Since wlroots 0.14, you need to set up libseat backend if you wish to run labwc directly (without nesting it in another wayland compositor). To do that, [[Repositories#Enabling_the_community_repository\|enable the community repository]] and choose one of the following methods:

	~~=== Option 1: seatd daemon (recommended) ===~~
	~~See [[Seatd]].~~

	~~=== Option 2: seatd-launch ===~~

	~~{{Cmd\|# apk add seatd-launch}}~~

	~~When starting labwc, you will need to prefix invocation with <code>seatd-launch</code>.~~
	~~Note: <code>seatd-launch</code> is a suid binary, so it might be wise to use one of the other methods from a security perspective.~~

	~~=== Option 3: elogind daemon ===~~

	~~See [[Elogind]].~~

	~~== Installation ==~~

			=== Install labwc ===
	We can now install labwc:		We can now install labwc:
	{{Cmd\|# apk add labwc labwc-doc		{{Cmd\|# apk add labwc labwc-doc
Line 61:		Line 32:
	dbus-x11		dbus-x11
	}}		}}

	~~Note that almost all optional dependencies are the same as Sway's.~~

	== Running LabWC ==		== Running LabWC ==

	To ~~run labwc, first set up [[XDG_RUNTIME_DIR]] Then~~ run labwc from ~~the Linux~~ console (dbus-launch ~~is used because pipewire needs it, it is included in dbus-x11 and you may omit it):~~		To run labwc from console:{{Cmd\|$ dbus-launch labwc}}

	~~{{Cmd\|$~~ dbus-launch labwc}}		'''dbus-launch labwc''' is used because pipewire needs it, it is included in dbus-x11 and you may omit it.

	(if you run labwc with seatd-launch, you will need to use <code>$ dbus-launch seatd-launch labwc</code>)		(if you run labwc with seatd-launch, you will need to use <code>$ dbus-launch seatd-launch labwc</code>)
Line 79:		Line 48:
	}}		}}

	== Configuration ~~and Usage~~ ==		== Configuration ==

	LabWC aims to implement the [http://openbox.org/wiki/Help:Contents openbox 3.4] specification, so many things working in OpenBox should be compatible.		LabWC aims to implement the [http://openbox.org/wiki/Help:Contents openbox 3.4] specification, so many things working in OpenBox should be compatible.
Line 86:		Line 55:

	For additional information, labwc [https://labwc.github.io/manual.html manpages] and [https://github.com/labwc/labwc/wiki wiki] can be consulted.		For additional information, labwc [https://labwc.github.io/manual.html manpages] and [https://github.com/labwc/labwc/wiki wiki] can be consulted.

			== Troubleshooting ==

			== See also ==

			[https://labwc.github.io LabWC Official website]

	[[Category:Desktop]]		[[Category:Desktop]]
	[[Category:Wayland]]		[[Category:Wayland]]
	[[Category:compositor]]		[[Category:compositor]]

Arnaudv6 at 08:03, 19 December 2024

2024-12-19T08:03:34Z

← Older revision		Revision as of 08:03, 19 December 2024
Line 89:		Line 89:
	[[Category:Desktop]]		[[Category:Desktop]]
	[[Category:Wayland]]		[[Category:Wayland]]
			[[Category:compositor]]

WhyNotHugo: /* Running LabWC */ Link to XDG_RUNTIME_DIR

2024-05-18T19:06:43Z

Running LabWC: Link to XDG_RUNTIME_DIR

← Older revision		Revision as of 19:06, 18 May 2024
Line 66:		Line 66:
	== Running LabWC ==		== Running LabWC ==

	To run labwc, first set XDG_RUNTIME_DIR ~~to a suitable location (e.g. create a .run folder in your home directory and set it to ~/.run).~~ Then run labwc from the Linux console (dbus-launch is used because pipewire needs it, it is included in dbus-x11 and you may omit it):		To run labwc, first set up [[XDG_RUNTIME_DIR]] Then run labwc from the Linux console (dbus-launch is used because pipewire needs it, it is included in dbus-x11 and you may omit it):

	{{Cmd\|$ ~~XDG_RUNTIME_DIR=~/.run~~ dbus-launch labwc}}		{{Cmd\|$ dbus-launch labwc}}

	(if you run labwc with seatd-launch, you will need to use <code>$ ~~XDG_RUNTIME_DIR=~/.run~~ dbus-launch seatd-launch labwc</code>)		(if you run labwc with seatd-launch, you will need to use <code>$ dbus-launch seatd-launch labwc</code>)

	You can also create a simple alias in your shell rc file (e.g. .zshrc), like:		You can also create a simple alias in your shell rc file (e.g. .zshrc), like:
	{{Cmd\|alias labwcinit="~~XDG_RUNTIME_DIR=~/.run~~ dbus-launch seatd-launch labwc"}}		{{Cmd\|alias labwcinit="dbus-launch seatd-launch labwc"}}

	~~See the [https://wiki.alpinelinux.org/wiki/Wayland Wayland] page for a permanent configuration (recommended).~~

	{{Note\|		{{Note\|

WhyNotHugo: /* Prerequisites */ use subtitles (so we get proper anchors)

2024-03-03T10:10:16Z

Prerequisites: use subtitles (so we get proper anchors)

← Older revision		Revision as of 10:10, 3 March 2024
Line 34:		Line 34:
	Since wlroots 0.14, you need to set up libseat backend if you wish to run labwc directly (without nesting it in another wayland compositor). To do that, [[Repositories#Enabling_the_community_repository\|enable the community repository]] and choose one of the following methods:		Since wlroots 0.14, you need to set up libseat backend if you wish to run labwc directly (without nesting it in another wayland compositor). To do that, [[Repositories#Enabling_the_community_repository\|enable the community repository]] and choose one of the following methods:

	~~<dl>~~		=== Option 1: seatd daemon (recommended) ===
			See [[Seatd]].

	~~<dt>~~Option 1: seatd ~~daemon (recommended)</dt>~~		=== Option 2: seatd-launch ===
	~~<dd>~~
	~~See [[Seatd]].~~

	~~<dt>Option 2: seatd-launch</dt>~~
	~~<dd>~~
	{{Cmd\|# apk add seatd-launch}}		{{Cmd\|# apk add seatd-launch}}

	When starting labwc, you will need to prefix invocation with <code>seatd-launch</code>.		When starting labwc, you will need to prefix invocation with <code>seatd-launch</code>.
	Note: <code>seatd-launch</code> is a suid binary, so it might be wise to use one of the other methods from a security perspective.		Note: <code>seatd-launch</code> is a suid binary, so it might be wise to use one of the other methods from a security perspective.
	~~</dd>~~

	~~<dt>~~Option 3: elogind daemon~~</dt>~~		=== Option 3: elogind daemon ===
	~~<dd>~~

	See [[Elogind]].		See [[Elogind]].

	~~</dd>~~

	~~</dl>~~

	== Installation ==		== Installation ==

WhyNotHugo: /* Prerequisites */ link to elogind

2024-03-03T10:08:29Z

Prerequisites: link to elogind

← Older revision		Revision as of 10:08, 3 March 2024
Line 51:		Line 51:
	<dd>		<dd>

	~~{{Cmd\|# apk add elogind polkit-elogind~~		See [[Elogind]].
	~~# rc-update add elogind~~
	~~# rc-service elogind start~~
	}}

	~~Using <code>elogind</code> will automatically set the necessary permissions, so you can skip adding groups like <code>seat</code> and <code>video</code>~~

	</dd>		</dd>

WhyNotHugo: /* Prerequisites */ link to seatd article

2024-03-03T10:07:51Z

Prerequisites: link to seatd article

← Older revision		Revision as of 10:07, 3 March 2024
Line 38:		Line 38:
	<dt>Option 1: seatd daemon (recommended)</dt>		<dt>Option 1: seatd daemon (recommended)</dt>
	<dd>		<dd>
	~~{{Cmd\|# apk add seatd~~		See [[Seatd]].
	~~# rc-update add seatd~~
	~~# rc-service seatd start~~
	~~# adduser $USER seat~~
	}}

	~~If you are already logged in as a $USER, you will need to relogin~~.
	~~</dd>~~

	<dt>Option 2: seatd-launch</dt>		<dt>Option 2: seatd-launch</dt>

Hyphae at 18:13, 1 February 2024

2024-02-01T18:13:50Z

← Older revision		Revision as of 18:13, 1 February 2024
Line 83:		Line 83:
	}}		}}

	Note that almost all optional dependencies are the same ~~than~~ Sway's. Another interesting packages are specified into the [https://github.com/labwc/labwc#6-integrate project's README], as it can be [https://labwc.github.io/integration.html#waybar waybar] (included into the Alpine's repository) as navigation bar.		Note that almost all optional dependencies are the same as Sway's.

	== Running LabWC ==		== Running LabWC ==

Zcrayfish: /* Installation */ dbus-x11 is needed.

2024-01-15T09:09:27Z

Installation: dbus-x11 is needed.

← Older revision		Revision as of 09:09, 15 January 2024
Line 76:		Line 76:
	xwayland \ # recommended for compatibility reasons		xwayland \ # recommended for compatibility reasons
	foot \ # default terminal emulator		foot \ # default terminal emulator
	rofi \ # default application launcher (dmenu could be used instead)		rofi \ # default application launcher (dmenu could be used instead)
	swaylock \ # lockscreen tool		swaylock \ # lockscreen tool
	swaybg \ # wallpaper daemon		swaybg \ # wallpaper daemon
	swayidle # idle management (DPMS) daemon		swayidle \ # idle management (DPMS) daemon
			dbus-x11
	}}		}}