diff --git a/technology/applications/Applications.md b/technology/applications/Applications.md index 9b556b4..010685c 100644 --- a/technology/applications/Applications.md +++ b/technology/applications/Applications.md @@ -38,6 +38,7 @@ rev: 2024-12-10 ## Desktop - [KDE Plasma](./desktops/KDE%20Plasma.md) +- [SDDM](./desktops/SDDM.md) - [dwm](./desktops/dwm.md) - [picom](./desktops/picom.md) - [Hyprland](./desktops/hyprland.md) diff --git a/technology/applications/desktops/SDDM.md b/technology/applications/desktops/SDDM.md new file mode 100644 index 0000000..aeb1cd4 --- /dev/null +++ b/technology/applications/desktops/SDDM.md @@ -0,0 +1,71 @@ +--- +obj: application +arch-wiki: https://wiki.archlinux.org/title/SDDM +wiki: https://en.wikipedia.org/wiki/Simple_Desktop_Display_Manager +repo: https://github.com/sddm/sddm +rev: 2024-12-17 +--- + +# SDDM +The Simple Desktop Display Manager (SDDM) is a display manager. It is the recommended display manager for the KDE Plasma and LXQt desktop environments. + +## Configuration +The default configuration file for SDDM can be found at `/usr/lib/sddm/sddm.conf.d/default.conf`. For any changes, create configuration file(s) in `/etc/sddm.conf.d/`. + +Everything should work out of the box, since Arch Linux uses systemd and SDDM defaults to using `systemd-logind` for session management. + +### Autologin +SDDM supports automatic login through its configuration file, for example (`/etc/sddm.conf.d/autologin.conf`): + +```ini +[Autologin] +User=john +Session=plasma + +# Optionally always relogin the user on logout +Relogin=true +``` + +This configuration causes a KDE Plasma session to be started for user `john` when the system is booted. Available session types can be found in `/usr/share/xsessions/` for X and in `/usr/share/wayland-sessions/` for Wayland. + +To autologin into KDE Plasma while simultaneously locking the session (e.g. to allow autostarted apps to warm up), create a systemd user unit drop in to pass `--lockscreen` in `plasma-ksmserver.service` (`~/.config/systemd/user/plasma-ksmserver.service.d/override.conf`): + +```ini +[Service] +ExecStart= +ExecStart=/usr/bin/ksmserver --lockscreen +``` + +### Theme settings +Theme settings can be changed in the `[Theme]` section. If you use Plasma's system settings, themes may show previews. + +Set to `breeze` for the default Plasma theme. + +#### Current theme + +Set the current theme through the Current value, e.g. `Current=archlinux-simplyblack`. + +#### Editing themes +The default SDDM theme directory is `/usr/share/sddm/themes/`. You can add your custom made themes to that directory under a separate subdirectory. Note that SDDM requires these subdirectory names to be the same as the theme names. Study the files installed to modify or create your own theme. + +#### Customizing a theme +To override settings in the `theme.conf` configuration file, create a custom `theme.conf.user` file in the same directory. For example, to change the theme's background (`/usr/share/sddm/themes/name/theme.conf.user`): + +```ini +[General] +background=/path/to/background.png +``` + +#### Testing (previewing) a theme +You can preview an SDDM theme if needed. This is especially helpful if you are not sure how the theme would look if selected or just edited a theme and want to see how it would look without logging out. You can run something like this: + +```sh +sddm-greeter-qt6 --test-mode --theme /usr/share/sddm/themes/breeze +``` + +This should open a new window for every monitor you have connected and show a preview of the theme. + +#### Mouse cursor +To set the mouse cursor theme, set `CursorTheme` to your preferred cursor theme. + +Valid Plasma mouse cursor theme names are `breeze_cursors`, `Breeze_Snow` and `breeze-dark`. diff --git a/technology/linux/systemd/Systemd.md b/technology/linux/systemd/Systemd.md index 8442c8b..c508346 100644 --- a/technology/linux/systemd/Systemd.md +++ b/technology/linux/systemd/Systemd.md @@ -12,6 +12,7 @@ systemd is a suite of basic building blocks for a [Linux](../Linux.md) system. I See also: - [Systemd-Timers](Systemd-Timers.md) - [systemd-boot](systemd-boot.md) +- [systemd-cryptenroll](systemd-cryptenroll.md) ## Using Units Units commonly include, but are not limited to, services (_.service_), mount points (_.mount_), devices (_.device_) and sockets (_.socket_). diff --git a/technology/linux/systemd/systemd-boot.md b/technology/linux/systemd/systemd-boot.md index f769da2..9b54efa 100644 --- a/technology/linux/systemd/systemd-boot.md +++ b/technology/linux/systemd/systemd-boot.md @@ -1,6 +1,7 @@ --- obj: application arch-wiki: https://wiki.archlinux.org/title/Systemd-boot +rev: 2024-12-17 --- # Systemd Boot @@ -20,7 +21,8 @@ bootctl update ``` ## Configuration -The loader configuration is stored in the file `_esp_/loader/loader.conf` +The loader configuration is stored in the file `_esp_/loader/loader.conf`. + Example: ``` default arch.conf @@ -30,7 +32,7 @@ editor no ``` ### Adding loaders -_systemd-boot_ will search for boot menu items in `_esp_/loader/entries/*.conf` +_systemd-boot_ will search for boot menu items in `_esp_/loader/entries/*.conf`. Values: - `title` : Name @@ -57,4 +59,18 @@ systemctl reboot --boot-loader-entry=arch-custom.conf Firmware Setup: ```shell systemctl reboot --firmware-setup -``` \ No newline at end of file +``` + +## Keybindings +While the menu is shown, the following keys are active: + +| Key | Description | +| ------------- | ----------------------------------------------------------------------------------- | +| `Up` / `Down` | Select menu entry | +| `Enter` | Boot the selected entry | +| `d` | select the default entry to boot (stored in a non-volatile EFI variable) | +| `t` / `T` | adjust the timeout (stored in a non-volatile EFI variable) | +| `e` | edit the option line (kernel command line) for this bootup to pass to the EFI image | +| `Q` | quit | +| `v` | show the systemd-boot and UEFI version | +| `P` | print the current configuration to the console |