Merge branch 'master' of github:/tiyn/wiki

wiki/linux/easyeffects.md

@@ -13,6 +13,53 @@ An installation via [Flatpak](./flatpak.md) is also possible.
 
 Easyeffects can apply `Effects` to input and output sound.
 
+### Autostart
+
+Easyeffects can be started in various ways.
+
+The service can be started including the window with the following.
+It will have to be called each startup.
+
+```sh
+easyeffects
+```
+
+Alternatively it can be started in the background with the following command.
+This command also has to be called each time the system starts.
+
+```sh
+easyeffects --gapplication-service
+```
+
+The two former commands will only work if called on each startup.
+The easiest way to do this is by using [SystemD](/wiki/linux/systemd.md).
+The following will work analogously to the path explained in
+[the corresponding section of the SystemD entry](/wiki/linux/systemd.md#run-command-on-boot).
+
+Run the following command to edit the configuration file for the newly created EasyEffect service.
+
+```sh
+systemctl --user edit --force -full easyeffects.service
+```
+
+Afterward set the contents of this file to the following.
+Due to EasyEffect working together with [Pipewire and Wireplumber](/wiki/linux/pipewire.md) some
+precautions have to be taken to start it before these two.
+
+```sh
+[Unit]
+Description=EasyEffects (GApplication Service)
+After=pipewire.service wireplumber.service
+PartOf=graphical-session.target
+
+[Service]
+ExecStart=/usr/bin/easyeffects --gapplication-service
+Restart=on-failure
+
+[Install]
+WantedBy=graphical-session.target
+```
+
 ### Noise cancellation
 
 Setup

wiki/linux/proxmox.md

@@ -202,7 +202,7 @@ be hidden.
 It is then more difficult to find the out-of-memory error that makes a program crash.
 Problems with balooning RAM can be found using the following command.
 
-```sh 
+```sh
 journalctl -k
 ```
 

wiki/linux/swayidle.md

@@ -10,7 +10,7 @@ On most Linux distributions swayidle can be installed with the `swayidle` packag
 
 To run swayidle it has to be called - preferably after the boot process.
 An example of this will look like the following.
-This will [suspend-then-hibernate](/wiki/linux/systemd.md#change-suspend-and-hibernate-behaviour)
+This will [suspend-then-hibernate](/wiki/linux/systemd.md#change-suspend-and-hibernate-behavior)
 the system after 30 seconds.
 Additionally a program [xss-lock](/wiki/linux/xss-lock.md) has to be used to let swayidle know to
 use a specific lock command.

wiki/linux/systemd.md

@@ -10,6 +10,15 @@ It is used for service configuration and startup.
 To run a command (in this case `/bin/bash /root/run.sh`) create the following
 file at `/etc/systemd/system/` with a name ending on `.service`.
 In this case it is called `unturned.service`.
+Alternatively to creating the command manually the following command can be used.
+The `--user` flag may be useful as explained in the
+[corresponding section](#startstopenabledisable-a-service-and-retrieve-its-logs).
+
+```sh
+systemctl edit --force --full unturned.service
+```
+
+And set the contents to the following.
 
 ```txt
 [Unit]
@@ -31,17 +40,8 @@ initializing.
 After=pve-guests.service
 ```
 
-Such a service can be started by running:
+A service that was created this way can then be started as explained in
-
+[the corresponding section](#startstopenabledisable-a-service-and-retrieve-its-logs).
-```sh
-sudo systemctl start unturned
-```
-
-Alternatively it can be enabled to start at every boot by running:
-
-```sh
-sudo systemctl enable unturned
-```
 
 ### Start/Stop/Enable/Disable a service and Retrieve its Logs
 
@@ -54,6 +54,8 @@ The `disable` keyword stops the service from starting automatically.
 
 Logs of the last start of the service can be found by running `systemctl status <service-name>`.
 
+Additionally, the `--user` flag can be set to start the service only for the current user.
+
 ### Retrieving the SystemD Logs
 
 SystemD logs can easily be found using the `journalctl` command.
@@ -64,9 +66,9 @@ This can be achieved by running the following command.
 journalctl -b-1
 ```
 
-### Change Suspend and Hibernate Behaviour
+### Change Suspend and Hibernate Behavior
 
-The behaviour of suspend and hibernation can be changed in the file `/etc/systemd/sleep.conf`.
+The behavior of suspend and hibernation can be changed in the file `/etc/systemd/sleep.conf`.
 One of the most important variables is the one to set the hibernation delay time.
 This time will be used to determine the time that is taken from suspend to hibernation if
 suspend-to-hibernate is called.
@@ -79,7 +81,7 @@ HibernateDelaySec=10min
 ### Handle Power Key and Lid Switching
 
 The management of power keys and lid switches is handled in the file `/etc/systemd/logind.conf`.
-The following line will set the behaviour of the power key to hibernate. The default for this would
+The following line will set the behavior of the power key to hibernate. The default for this would
 be to shutdown the system.
 
 ```txt
@@ -94,8 +96,8 @@ The following lines will change this to suspend-then-hibernate.
 HandleLidSwitch=suspend-then-hibernate
 ```
 
-For further behaviour of the suspend and hibernate actions check the
+For further behavior of the suspend and hibernate actions check the
-[corresponding section](#change-suspend-and-hibernate-behaviour).
+[corresponding section](#change-suspend-and-hibernate-behavior).
 
 When wanting to work with a closed lid some of the settings in the config file have to be set to
 ignore.

wiki/linux/xss-lock.md

@@ -12,7 +12,7 @@ On most Linux distributions swayidle can be installed with the `xss-lock` packag
 To run xss-lock it has to be called - preferably after the boot process.
 An example of this will look like the following.
 This command makes the system use `swaylock` if the system is put to
-[sleep](/wiki/linux/systemd.md#change-suspend-and-hibernate-behaviour).
+[sleep](/wiki/linux/systemd.md#change-suspend-and-hibernate-behavior).
 
 ```sh
 xss-lock -- swaylock