Alpine Linux - User contributions [en]

User:Gopherbot

2025-03-16T14:39:57Z

Zcrayfish: added retired template.

{{retired}}

Gopherbot is a retired MediWiki maintenance bot formerly used on the Alpine Linux wiki by [[User:zcrayfish|zcrayfish]]. 

=Former bot tasks=
* Checks for dead hyperlinks, and certain dead wikilinks as well.
** After seeing a link fail to work for a minimum of a week, a comment will be added on the associated talk page.
* On a semi-automated basis: Removes unwanted categories.

= Dead link blacklist =
Links from the following domains were NOT checked, usually because the servers either do dumb things (every response is a 200?) or block the bot:

* [https://datatracker.ietf.org/doc/html/rfc2606#page-2 RFC2606 test domains] (e.g. example.com, example.net, example.org, etc)
* berlinonline.de* (incompatible)
* web.archive.org* (rejects bots)
* archive.is* (rejects bots, and is an EXTREMELY slow site in general)
* cloudflare.com* (intermittently rejects bots... and humans too...)
* cyberciti.biz* (rejects bots)
* linuxconfig.org* (rejects bots)
* openvpn.net* (rejects bots)
* gitlab.com/lramage94* (requires login)
* www.voip-info.org* (rejects bots)

User talk:Zcrayfish

2025-03-16T14:36:57Z

Zcrayfish: retired template.

{{retired}}
Any additional comments on this talk page will be ignored.

=== thanks for the help ===
thanks for the formatting help [https://wiki.alpinelinux.org/w/index.php?title=Setting_up_disks_manually&diff=prev&oldid=26562]
[[User:Alpinetony|Alpinetony]] [[User talk:Alpinetony|💬]] 22:24, 4 March 2024 (UTC)
:any time! \o/ –[[User:zcrayfish|zcrayfish]] ([[User talk:zcrayfish|talk]]•[[Special:Contributions/zcrayfish|contribs]]•[[Special:EmailUser/zcrayfish|send email]]) 08:43, 7 March 2024 (UTC)

== About "undo revision 26759" ==

:Revision comment does not match what was done with the page. Most content removed. Accident?

Yes, thanks for fixing that. Damn... I pressed the "edit section" button instead of "edit page". I thought I was editing just the section, and that the rest of the page would be untouched.

— Preceding [[Help:Signature|unsigned]] comment added by [[User:Harpia|Harpia]] ([[User talk:Harpia|{{int:talkpagelinktext}}]] • [[Special:Contributions/Harpia|{{int:contribslink}}]]) 22:25, 28 May 2024‎

:No problem!! :) –[[User:zcrayfish|zcrayfish]] ([[User talk:zcrayfish|talk]]•[[Special:Contributions/zcrayfish|contribs]]•[[Special:EmailUser/zcrayfish|send email]]) 02:34, 3 June 2024 (UTC)

User:Zcrayfish

2025-03-16T14:36:12Z

Zcrayfish: added retired template.

{{DISPLAYTITLE:User:zcrayfish}}
{{retired}}
=Stuff to watch=
[[Special:Patroller|Unpatrolled edits]]
Most recent unpatrolled new pages (ideally there should be none): {{Special:NewPages/limit=50,hidepatrolled}}

[[Special:BrokenRedirects|List of broken redirects]] (there should be none)

[[Special:DoubleRedirects|List of double redirects]] (there should be none)

[[Special:ListDuplicatedFiles|List of duplicate files]] (there should be none)

[https://wiki.alpinelinux.org/w/index.php?target=irc%3A%2F%2F*&title=Special%3ALinkSearch All irc:// hyperlinks]. (there should be none)

[[Special:TrackingCategories|Pages that mediawiki has marked as broken in some way]] (there should be none)

[[Special:RecentChanges|250 most recent wiki edits]]

=To-do=

[[Special:WhatLinksHere/Template:Dead_link|Pages which contain dead links]]

[[Special:WhatLinksHere/Template:Obsolete|Obsolete pages]] (Need to go through and RfD some of these)

[[Special:WhatLinksHere/Template:Insecure_url|Pages which contain links to unencrypted content]] (Some sites stubbornly refuse to join the current century)

[[Special:WhatLinksHere/Template:Delete|RfDs]] (I don't have access to deal with these)

[[Special:WantedPages|List of non-existing pages that are linked to]]

[https://wiki.alpinelinux.org/w/index.php?target=http%3A%2F%2F*&title=Special%3ALinkSearch All http:// hyperlinks]. All of these need to be checked to see if they can be rewritten to https://

[https://wiki.alpinelinux.org/w/index.php?target=ftp%3A%2F%2F*&title=Special%3ALinkSearch All ftp:// hyperlinks]. All of these need to be check to see if an sftp:// or https:// version is available.

[https://wiki.alpinelinux.org/w/index.php?target=svn%3A%2F%2F*&title=Special%3ALinkSearch All svn:// hyperlinks]. Old Alpine SVN links have gotta go!

=Tools=

[[Special:LinkSearch|External link seach]]

[[Special:AllPages/Template:|List of all templates]]

[[Special:ExpandTemplates|Template wikimarkup expansion tool]]

[[Special:Redirect|Redirect by file, user, page, revision, or log ID]]

[[Special:AbuseFilter|Description of automatic abuse filtering]] (because I always forget, and it would be nice to be able to explain to new wiki users why exactly their posts are getting denied)

[[Special:Random|Go to a completely random page.]] This is both fun and useful!

=Logs/Stats=

[[Special:BlockList]]

[[Special:AbuseLog]]

[[Special:Statistics]]

Setting up encrypted volumes with LUKS

2025-03-09T20:56:16Z

Zcrayfish: /* mkinitfs and LUKS */ use path template

[https://en.wikipedia.org/wiki/Linux%20Unified%20Key%20Setup LUKS] allows encrypting a partition and mapping it as a virtual block device, which can then be used as a normal partition. Guides for other Linux distributions should serve as a general references for installing Alpine onto a LUKS encrypted disk.

The installer has built-in support for encryption. The default installer will not encrypt the swap partition and the boot partition. To setup Alpine Linux with an encrypted swap partition, refer to [[LVM on LUKS]]. The GRUB bootloader supports BIOS and EFI boot with an encrypted boot partition.

== mkinitfs and LUKS ==

For those familiar with setting up FDE on other Linux distributions, this section contains only Alpine-specific knowledge required is understanding [[mkinitfs]].

First of all, the <code>cryptsetup</code> feature needs to be added to {{path|/etc/mkinitfs/mkinitfs.conf}}. Additionally, the following kernel parameters are required:

* <code>cryptroot</code> kernel parameter should point to the encrypted block device.
* <code>cryptdm</code>: the name that will be given to the device.
* <code>root</code> kernel parameter should point to the mapped block device: <code>/dev/mapper/<name used in cryptdm></code>.
* <code>rootfstype</code>: the filesystem type of the root partition (e.g.: <code>btrfs</code>).

For example if you use grub with GPT partition table, no LVM and ext4 you will have in {{path|/etc/default/grub}}:
<pre>
GRUB_TIMEOUT=2
GRUB_DISABLE_SUBMENU=y
GRUB_DISABLE_RECOVERY=true
GRUB_CMDLINE_LINUX_DEFAULT="modules=sd-mod,usb-storage,ext4 quiet rootfstype=ext4 cryptroot=UUID=a7dc90c4-6746-417e-b25b-cb8769ee6334 cryptdm=alpine-rootfs root=/dev/mapper/alpine-rootfs"
GRUB_PRELOAD_MODULES="luks cryptodisk part_gpt"
GRUB_ENABLE_CRYPTODISK=y
</pre>

== See also ==

* [[LVM on LUKS]]
* [[mkinitfs|Initramfs init]]
* [[Full disk encryption secure boot]]
* [https://wiki.archlinux.org/index.php/Dm-crypt dm-crypt on ArchWiki]

[[Category:Storage]]
[[Category:Security]]

Talk:Support

2025-03-05T03:06:53Z

Zcrayfish: reply

Hi Zcrayfish, when a user types support, wiki will land in this page. The actual support page [[Alpine Linux:Support]] page will not be displayed since that page is in "Alpine Linux" namespace and not in the Main namespace. Reverting back the old redirect will help wiki users to reach [[Alpine Linux:Support|Support]] page, on searching support in the search box. [[User:Prabuanand|Prabuanand]] ([[User talk:Prabuanand|talk]]) 03:49, 21 February 2025 (UTC)

:Good catch, thanks for fixing that.
:–[[User:zcrayfish|zcrayfish]] ([[User talk:zcrayfish|talk]]•[[Special:Contributions/zcrayfish|contribs]]•[[Special:EmailUser/zcrayfish|send email]]) 03:06, 5 March 2025 (UTC)

Installing Oracle Java

2025-03-05T02:59:32Z

Zcrayfish: Reverting: Completely blanking pages is not acceptable.

{{Obsolete|Alpine has not used grsec for a while now...}}

Using java requires having grsec play nice with the binaries. You may also want to install the JDK instead of the JRE depending on your needs.

This guide assumes you're running as root.

Download XXX-XXX-linux-x64.tar.gz from either the JRE or JDK section here:
https://www.oracle.com/technetwork/java/javase/downloads/index.html

mkdir -p /opt/java
cd /opt/java
sudo tar -zxvf XXX-XXX-linux-x64.tar.gz

Take note of the directory, e.g. /opt/java/jdk1.8.0_121, create a symbolic link as the current version:

ln -s /opt/java/jdk1.8.0_121 /opt/java/current

Create a file in '''/etc/profile.d/java.sh''':
export JAVA_HOME=/opt/java/current
export PATH=$PATH:$JAVA_HOME/bin

Execute this script or restart your shell:
sh /etc/profile.d/java.sh

Now we need manage grsec with paxctl. Use this command to check if its installed:
which paxctl

If nothing comes up install it:

apk add paxctl

Now in your /opt/java/XXX/bin folder, execute:
paxctl -c java
paxctl -m java

If you have the JDK, you need to do the same to javac:
paxctl -c javac
paxctl -m javac

You can do this for any other binary you need to use.

NOTE: some users have reported they had to use this command to get it working:

setfattr -n user.pax.flags -v "mr" java
setfattr -n user.pax.flags -v "mr" javac

'''Alternative installation of Oracle Java on Linux Alpine'''

1. Run apk update && apk upgrade
2. Edit vim /etc/profile, add the value before the string: append_path "/user/local/sbin", value: append_path "/opt/java/current/bin"
3. Download XXX-XXX-linux-x64.tar.gz and jce_policy-8.zip from official oracle suite.
4. Сreate a directory in the root: mkdir -p /opt/java
5. Copy XXX-XXX-linux-x64.tar.gz in the java directory: scp /home/username/XXX-XXX-linux-x64.tar.gz /opt/java/
6. Let's go to the catalog java: cd /opt/java and unpack the file: XXX-XXX-linux-x64.tar.gz, tar -zxvf XXX-XXX-linux-x64.tar.gz
7. Create simlink: ln -s /opt/java/jdkX.X.X_XXX /opt/java/current
8. Download and install the certificate: wget -q -O /etc/apk/keys/sgerrand.rsa.pub https://alpine-pkgs.sgerrand.com/sgerrand.rsa.pub
9. Download glibc: wget https://github.com/sgerrand/alpine-pkg-glibc/releases/download/2.34-r0/glibc-2.34-r0.apk
10. Install glibc: apk add glibc-2.34-r0.apk
11. Download glibc-bin: wget https://github.com/sgerrand/alpine-pkg-glibc/releases/download/2.34-r0/glibc-bin-2.34-r0.apk
12. Install glibc-bin: apk add glibc-bin-2.34-r0.apk
13. Install the license jce_policy-8.zip, сopy the file: scp /home/username/jce_policy-8.zip /opt/java/current/jre/lib/security/
14. Let's go to the folder /opt/java/current/jre/lib/security/: cd /opt/java/current/jre/lib/security/ and unpack it: unzip -o -j jce_policy-8.zip UnlimitedJCEPolicyJDK8/*.jar
15. Delete the archive file: rm -f jce_policy-8.zip
16. Restart the computer or virtual machine: reboot
17. Let's check the version of Java installed: java -version
18. If it displays: java version "X.X.X_XXX", then we did everything correctly.
= =
* [https://blog.overops.com/author/shahar_valiano/ Native Java Debugging on Alpine Linux: GDB, OpenJDK and the Mysterious Unknown Signal] Shahar Valiano 2019

[[Category:Programming]]

Talk:Local APK cache

2025-02-09T22:34:10Z

Zcrayfish: Article improvement idea.

==Instructions on how to share the APK cache on the local network are needed==
With the infrastructure crisis that Alpine Linux is currently experiencing, it might be prudent for us to add directions here on the wiki on how to share the APK cache on the local network; if many users do this, it could help achieve a modest reduction in usage on the Alpine mirrors. (not to mention it is MUCH faster under most circumstances to download files locally rather than through the internet)...
–[[User:zcrayfish|zcrayfish]] ([[User talk:zcrayfish|talk]]•[[Special:Contributions/zcrayfish|contribs]]•[[Special:EmailUser/zcrayfish|send email]]) 22:34, 9 February 2025 (UTC)

User:Zcrayfish

2025-02-04T20:18:26Z

Zcrayfish: I am away.

{{DISPLAYTITLE:User:zcrayfish}}
{{note|This user is on hiatus until the MR backlog and [https://www.phoronix.com/forums/forum/phoronix/latest-phoronix-articles/1523664-alpine-linux-in-an-infrastructure-crisis-with-equinix-metal-sunsetting infrastructure crisis] is dealt with.}}
=Stuff to watch=
[[Special:Patroller|Unpatrolled edits]]
Most recent unpatrolled new pages (ideally there should be none): {{Special:NewPages/limit=50,hidepatrolled}}

[[Special:BrokenRedirects|List of broken redirects]] (there should be none)

[[Special:DoubleRedirects|List of double redirects]] (there should be none)

[[Special:ListDuplicatedFiles|List of duplicate files]] (there should be none)

[https://wiki.alpinelinux.org/w/index.php?target=irc%3A%2F%2F*&title=Special%3ALinkSearch All irc:// hyperlinks]. (there should be none)

[[Special:TrackingCategories|Pages that mediawiki has marked as broken in some way]] (there should be none)

[[Special:RecentChanges|250 most recent wiki edits]]

=To-do=

[[Special:WhatLinksHere/Template:Dead_link|Pages which contain dead links]]

[[Special:WhatLinksHere/Template:Obsolete|Obsolete pages]] (Need to go through and RfD some of these)

[[Special:WhatLinksHere/Template:Insecure_url|Pages which contain links to unencrypted content]] (Some sites stubbornly refuse to join the current century)

[[Special:WhatLinksHere/Template:Delete|RfDs]] (I don't have access to deal with these)

[[Special:WantedPages|List of non-existing pages that are linked to]]

[https://wiki.alpinelinux.org/w/index.php?target=http%3A%2F%2F*&title=Special%3ALinkSearch All http:// hyperlinks]. All of these need to be checked to see if they can be rewritten to https://

[https://wiki.alpinelinux.org/w/index.php?target=ftp%3A%2F%2F*&title=Special%3ALinkSearch All ftp:// hyperlinks]. All of these need to be check to see if an sftp:// or https:// version is available.

[https://wiki.alpinelinux.org/w/index.php?target=svn%3A%2F%2F*&title=Special%3ALinkSearch All svn:// hyperlinks]. Old Alpine SVN links have gotta go!

=Tools=

[[Special:LinkSearch|External link seach]]

[[Special:AllPages/Template:|List of all templates]]

[[Special:ExpandTemplates|Template wikimarkup expansion tool]]

[[Special:Redirect|Redirect by file, user, page, revision, or log ID]]

[[Special:AbuseFilter|Description of automatic abuse filtering]] (because I always forget, and it would be nice to be able to explain to new wiki users why exactly their posts are getting denied)

[[Special:Random|Go to a completely random page.]] This is both fun and useful!

=Logs/Stats=

[[Special:BlockList]]

[[Special:AbuseLog]]

[[Special:Statistics]]

Hardened malloc

2025-01-22T01:05:26Z

Zcrayfish: /* How to use */ Use pkg template.

=== What is it? ===
An excerpt on [https://github.com/GrapheneOS/hardened_malloc github] [1]:

''This is a security-focused general purpose memory allocator providing the malloc API along with various extensions. It provides substantial hardening against heap corruption vulnerabilities.''

=== How to use ===
{{note| Need Alpine Linux Edge with testing repo in {{path|/etc/apk/repositories}}}}
{{cmd| $ doas apk add {{pkg|hardened-malloc|arch=}}}}

Then you can set <code>LD_PRELOAD="/usr/lib/libhardened_malloc.so"</code> while launching individual applications or before your window manager starts if you prefer. For a more global setting placing the LD_PRELOAD reference into {{path|/etc/profile}} or {{path|/etc/profile.d/}} might help, as well as {{path|/etc/environment}} for PAM-based systems.

=== External sources ===
Hardened malloc github
* [https://github.com/GrapheneOS/hardened_malloc https://github.com/GrapheneOS/hardened_malloc] [1]

[[Category:Security]]

Hardened malloc

2025-01-22T01:04:40Z

Zcrayfish: /* How to use */ Use path template.

=== What is it? ===
An excerpt on [https://github.com/GrapheneOS/hardened_malloc github] [1]:

''This is a security-focused general purpose memory allocator providing the malloc API along with various extensions. It provides substantial hardening against heap corruption vulnerabilities.''

=== How to use ===
{{note| Need Alpine Linux Edge with testing repo in {{path|/etc/apk/repositories}}}}
{{cmd| $ doas apk add hardened-malloc}}

Then you can set <code>LD_PRELOAD="/usr/lib/libhardened_malloc.so"</code> while launching individual applications or before your window manager starts if you prefer. For a more global setting placing the LD_PRELOAD reference into {{path|/etc/profile}} or {{path|/etc/profile.d/}} might help, as well as {{path|/etc/environment}} for PAM-based systems.

=== External sources ===
Hardened malloc github
* [https://github.com/GrapheneOS/hardened_malloc https://github.com/GrapheneOS/hardened_malloc] [1]

[[Category:Security]]

LXQt

2025-01-12T18:58:28Z

Zcrayfish: /* Basic Configuration */ more wayland additions.

{{TOC right}}

[[File:LXQt Minimal Installation.png | thumb | LXQt 1.3.0 Basic Install with Papirus icons]]

'''[https://lxqt-project.org/ LXQt]''' is a lightweight QT based desktop environment. LXQt was originally a port of LXDE to QT (called LXDE-Qt), it was created due to LXDE maintainer Hong Jen Yee being dissatisfied with GTK 3. On 21 July 2013 the LXDE(-Qt) and [https://en.wikipedia.org/wiki/Razor-qt Razor-qt] projects merged creating LXQt.

{{:Include:Setup-desktop}}

When lxqt is chosen, the {{ic|Setup-desktop}} script installs [[SDDM]] as display manager and completes all the steps listed below in the [[#Manual installation|Manual installation]] and [[#Basic Configuration|Basic Configuration]] sections.

== Manual installation ==

=== Prerequisites ===

* [[Alpine_setup_scripts#setup-xorg-base|Install Xorg]]
* [[D-Bus#Installation|Install and configure D-Bus]] (without D-Bus icons and keyboard shortcuts may be missing)
* Install a [[Fonts|font]] by issuing the command {{ic|# apk add font-dejavu}}

== Basic Configuration ==

Begin the LXQt installation by adding basic packages:
{{Cmd|# apk add {{Pkg|lxqt-desktop}} {{Pkg|lximage-qt}} {{Pkg|pavucontrol-qt}}}}
If using Xorg, the following packages are also suggested: 
{{Cmd|# apk add {{Pkg|arandr}} {{Pkg|obconf-qt}} {{Pkg|screengrab}} {{Pkg|sddm}}}}
{{Note|By default LXQt on Xorg uses [[Openbox]] as its window manager (it is a dependency of the {{Pkg|lxqt-desktop}} package). LXQt supports many different window managers and wayland compositors. Openbox has not been maintained for 9 years. Similar window managers are JWM and PeKWM. For additional Window Manager options see: [https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers Window Managers Configuration on the LXQt GitHub wiki]}}

If using wayland, the following packages are suggested: 
{{cmd|# apk add {{Pkg|lxqt-wayland-session}} {{Pkg|swayidle}} {{Pkg|swaybg}} {{Pkg|wlopm}} {{Pkg|labwc}}}}
{{Note|labwc is used for the initial configuration (e.g. picking compositor and screen locker) on wayland, but can safely be uninstalled afterwards if a different compositor is installed and selected. For additional compositor options see: [https://github.com/lxqt/lxqt/wiki/ConfigWaylandSettings LXQt Wayland Session on the LXQt GitHub wiki]}}

=== Set up eudev ===
{{:Include:Setup_Device_Manager}}

=== Allowing shut down and reboot ===

To enable users to shut down the machine or reboot, the packages {{Pkg|elogind}} and {{Pkg|polkit-elogind}} need to be installed.
{{Cmd|# apk add elogind polkit-elogind}}

A reboot is required to let it take effect.

=== Auto-mounting USB drives ===

To enable automatic mounting of USB drives, install these packages:
{{Cmd|# apk add {{pkg|gvfs|arch=}} {{pkg|udisks2|arch=}}}}

Depending on what devices you intend to mount, some additional packages may be needed:
{{Cmd|{{pkg|ntfs-3g|arch=}} Stable, full-featured, read-write NTFS (driver)
{{pkg|gvfs-cdda|arch=}} CDDA support for gvfs
{{pkg|gvfs-afp|arch=}} AFP support for gvfs
{{pkg|gvfs-goa|arch=}} GNOME Online Accounts support for gvfs
{{pkg|gvfs-mtp|arch=}} MTP support for gvfs
{{pkg|gvfs-smb|arch=}} Windows fileshare support for gvfs
{{pkg|gvfs-lang|arch=}} Languages for package gvfs
{{pkg|gvfs-afc|arch=}} Apple mobile devices support for gvfs
{{pkg|gvfs-nfs|arch=}} NFS support for gvfs
{{pkg|gvfs-dev|arch=}} Backends for the gio framework in GLib (development files)
{{pkg|gvfs-archive|arch=}} Archiving support for gvfs
{{pkg|gvfs-dav|arch=}} WebDAV support for gvfs
{{pkg|gvfs-fuse|arch=}} FUSE support for gvfs
{{pkg|gvfs-gphoto2|arch=}} gphoto2 support for gvfs
{{pkg|gvfs-avahi|arch=}} DNS-SD support for gvfs}}

To list descriptions of all gvfs- packages:
{{cmd|# apk info -d {{pkg|gvfs-*|arch=x86_64}}}}

=== Enabling privilege escalation GUI ===

To enable the privilege escalation GUI for a doas/sudo user, you need to install {{Pkg|elogind}}, {{Pkg|polkit-elogind}}, and {{Pkg|sddm}}.

To have elogind run, either make them start automatically at system start:
{{Cmd|# rc-update add elogind}}

or start them manually for this time only:
{{Cmd|# rc-service elogind start }}

== Starting LXQt ==

=== With a display manager (DM) ===

If the package {{Pkg|sddm}} has been installed, SDDM may be started to log in graphically with your new user.
{{Cmd|# rc-service sddm start}}

After correct operation is verified, sddm can be enabled to start up during boot:
{{Cmd|# rc-update add sddm}}

=== From the command line ===

LXQt for X11 may be started with:
{{cmd|$ startlxqt}}

LXQt for Wayland may be started with:
{{cmd|$ startlxqtwayland}}

== Localized keyboard layout ==

Preferences → LXQt Settings → Keyboard and Mouse → Keyboard Layout

== Optional Configuration ==
=== Network browsing ===

For browsing of network shares within LXQt that works with file associations, you can install the gvfs packages for the network protocols you use.

For example, to browse in a SMB/cifs windows network:
{{Cmd|# apk add gvfs-smb}}

(Check: If the above may already be sufficient for gvfs to initiate the fuse kernel module. Else, try to identify if there are necessary steps in:)
{{Cmd|# apk add gvfs-fuse}}

The OpenRC script for fuse is in a separate package.
{{Cmd|# apk add {{pkg|fuse-openrc|arch=}}}}

Then the fuse service can be started manually.
{{Cmd|# rc-service fuse start}}

If it works, the fuse service can be added to start up automatically at boot time:
{{Cmd|# rc-update add fuse}}

=== Screen Compositor ===

To enable different effects (transparency, for example) {{Pkg|picom}} can be used.

After installation, add it to the ''Autostart'' section of the '''LXQt Session Settings'''.

The default configuration is available in {{Path|/etc/xdg/picom.conf.example}}. For modifications, it can be copied to {{Path|~/.config/picom/picom.conf}} or {{Path|~/.config/picom.conf}}.

Either modify the config file to your taste, or change the Autostart command line options. For example, <code>picom --vsync -r 12 --no-fading-openclose -b</code>.

=== Panel Widgets ===

If you cannot add the CPU and System Statistics widgets to the panel, make sure {{Pkg|libstatgrab}} and {{Pkg|libsysstat}} are installed.

=== Appearance Tweaking ===

==== Location of appearance-related configuration files ====

User-specific configuration is stored in {{Path|~/.config/lxqt/}}.

LXQt themes are [https://doc.qt.io/qt-6/stylesheet.html qss stylesheets]. They are located in {{Path|/usr/share/lxqt/themes/}} or {{Path|~/.local/share/lxqt/themes}}.

Qt Palette colors can be modified in lxqt-config-appearence > Widget Style > Qt Palette. Custom palettes are saved in {{Path|~/.local/share/lxqt/palettes/}}.

==== Additional QT Styles ====

Several packages provide additional QT Styles:
{{Cmd|# apk add {{Pkg|adwaita-qt}} {{Pkg|breeze}} {{Pkg|oxygen}}}}

They also provide additional cursors.

==== Consistant Theming ====

Adding the KEY=VAL <code>QT_QPA_PLATFORMTHEME=lxqt</code> to the Environment section of the Session Settings [https://github.com/lxqt/lxqt-qtplugin#configuration-usage is suggested by the LXQt developers]. Then every Qt5 program can load the theme plugin.

Another option, however, is to to install the package {{Pkg|qt5ct}} (from [[Repositories | Testing]]) and appending the line <code>QT_QPA_PLATFORMTHEME=qt5ct</code> to the environmental settings in the Environment section of the Session Settings will allow you to achieve a unified appearance between apps. Then, in the LXQt Appearance Configuration, under Widget Style, set Qt Style to <code>qt5ct-style</code>.

==== Additional Packages ====

When using themes found around the web, it is possible that they are dependant on different packages. Consider using {{Pkg|qt5-qtgraphicaleffects}}, {{Pkg|qt5-qtquickcontrols}}, and {{Pkg|qt5-qtquickcontrols2}}.

== Documentation packages ==
* {{Pkg|lxqt-config-doc}}
* {{Pkg|lxqt-openssh-askpass-doc}}
* {{Pkg|lxqt-panel-doc}}
* {{Pkg|lxqt-policykit-doc}}
* {{Pkg|lxqt-runner-doc}}
* {{Pkg|lxqt-session-doc}}
* {{Pkg|lxqt-sudo-doc}}
* {{Pkg|lxqt-wayland-session-doc}}

== Development files ==

* {{Pkg|libdbusmenu-lxqt-dev}}
* {{Pkg|liblxqt-dev}}
* {{Pkg|lxqt-globalkeys-dev}}
* {{Pkg|lxqt-panel-dev}}
* {{Pkg|lxqt-build-tools}}

== Help wanted ==

The following LXQt components are not yet packaged in Alpine Linux:
* lxqt_wallet

The following LXQt components are out-of-date:
* obconf-qt (need an X11+openbox user to build the latest version and test it)

== Troubleshooting ==

=== Missing Icons and Fonts ===

By default a Desktop Environment needs icons. {{Pkg|adwaita-icon-theme}} is a good start.
{{Cmd|# apk add adwaita-icon-theme}}

See [[Fonts]] for more information on fonts.

== See Also ==

* [[Installation#Post-Installation|Post Install]]
* [[Desktop environments and Window managers]]
=== External Resources ===
* [https://lxqt.github.io/ LXQt Homepage]
* [https://github.com/lxqt/lxqt LXQt on GitHub]
* [https://wiki.archlinux.org/title/LXQt LXQt entry on ArchWiki]
* [https://github.com/sddm/sddm SDDM Project on GitHub]

[[Category:Desktop]]
[[Category:Desktop Environments]]

LXQt

2025-01-12T18:54:38Z

Zcrayfish: /* Basic Configuration */ wayland

{{TOC right}}

[[File:LXQt Minimal Installation.png | thumb | LXQt 1.3.0 Basic Install with Papirus icons]]

'''[https://lxqt-project.org/ LXQt]''' is a lightweight QT based desktop environment. LXQt was originally a port of LXDE to QT (called LXDE-Qt), it was created due to LXDE maintainer Hong Jen Yee being dissatisfied with GTK 3. On 21 July 2013 the LXDE(-Qt) and [https://en.wikipedia.org/wiki/Razor-qt Razor-qt] projects merged creating LXQt.

{{:Include:Setup-desktop}}

When lxqt is chosen, the {{ic|Setup-desktop}} script installs [[SDDM]] as display manager and completes all the steps listed below in the [[#Manual installation|Manual installation]] and [[#Basic Configuration|Basic Configuration]] sections.

== Manual installation ==

=== Prerequisites ===

* [[Alpine_setup_scripts#setup-xorg-base|Install Xorg]]
* [[D-Bus#Installation|Install and configure D-Bus]] (without D-Bus icons and keyboard shortcuts may be missing)
* Install a [[Fonts|font]] by issuing the command {{ic|# apk add font-dejavu}}

== Basic Configuration ==

Begin the LXQt installation by adding basic packages:
{{Cmd|# apk add {{Pkg|lxqt-desktop}} {{Pkg|lximage-qt}} {{Pkg|pavucontrol-qt}}}}
If using Xorg, the following packages are also suggested: 
{{Cmd|# apk add {{Pkg|arandr}} {{Pkg|obconf-qt}} {{Pkg|screengrab}} {{Pkg|sddm}}}}
{{Note|By default LXQt on Xorg uses [[Openbox]] as its window manager (it is a dependency of the {{Pkg|lxqt-desktop}} package). LXQt supports many different window managers and wayland compositors. Openbox has not been maintained for 9 years. Similar window managers are JWM and PeKWM. For additional Window Manager options See: [https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers Window Managers Configuration on the LXQt GitHub wiki]}}

If using wayland, the following packages are suggested: 
{{cmd|# apk add {{Pkg|lxqt-wayland-session}} {{Pkg|swayidle}} {{Pkg|swaybg}} {{Pkg|wlopm}} {{Pkg|labwc}}}}
{{Note|labwc is used for the initial configuration (e.g. picking compositor and screen locker) on wayland, but can safely be uninstalled afterwards if a different compositor is installed and selected.}}

=== Set up eudev ===
{{:Include:Setup_Device_Manager}}

=== Allowing shut down and reboot ===

To enable users to shut down the machine or reboot, the packages {{Pkg|elogind}} and {{Pkg|polkit-elogind}} need to be installed.
{{Cmd|# apk add elogind polkit-elogind}}

A reboot is required to let it take effect.

=== Auto-mounting USB drives ===

To enable automatic mounting of USB drives, install these packages:
{{Cmd|# apk add {{pkg|gvfs|arch=}} {{pkg|udisks2|arch=}}}}

Depending on what devices you intend to mount, some additional packages may be needed:
{{Cmd|{{pkg|ntfs-3g|arch=}} Stable, full-featured, read-write NTFS (driver)
{{pkg|gvfs-cdda|arch=}} CDDA support for gvfs
{{pkg|gvfs-afp|arch=}} AFP support for gvfs
{{pkg|gvfs-goa|arch=}} GNOME Online Accounts support for gvfs
{{pkg|gvfs-mtp|arch=}} MTP support for gvfs
{{pkg|gvfs-smb|arch=}} Windows fileshare support for gvfs
{{pkg|gvfs-lang|arch=}} Languages for package gvfs
{{pkg|gvfs-afc|arch=}} Apple mobile devices support for gvfs
{{pkg|gvfs-nfs|arch=}} NFS support for gvfs
{{pkg|gvfs-dev|arch=}} Backends for the gio framework in GLib (development files)
{{pkg|gvfs-archive|arch=}} Archiving support for gvfs
{{pkg|gvfs-dav|arch=}} WebDAV support for gvfs
{{pkg|gvfs-fuse|arch=}} FUSE support for gvfs
{{pkg|gvfs-gphoto2|arch=}} gphoto2 support for gvfs
{{pkg|gvfs-avahi|arch=}} DNS-SD support for gvfs}}

To list descriptions of all gvfs- packages:
{{cmd|# apk info -d {{pkg|gvfs-*|arch=x86_64}}}}

=== Enabling privilege escalation GUI ===

To enable the privilege escalation GUI for a doas/sudo user, you need to install {{Pkg|elogind}}, {{Pkg|polkit-elogind}}, and {{Pkg|sddm}}.

To have elogind run, either make them start automatically at system start:
{{Cmd|# rc-update add elogind}}

or start them manually for this time only:
{{Cmd|# rc-service elogind start }}

== Starting LXQt ==

=== With a display manager (DM) ===

If the package {{Pkg|sddm}} has been installed, SDDM may be started to log in graphically with your new user.
{{Cmd|# rc-service sddm start}}

After correct operation is verified, sddm can be enabled to start up during boot:
{{Cmd|# rc-update add sddm}}

=== From the command line ===

LXQt for X11 may be started with:
{{cmd|$ startlxqt}}

LXQt for Wayland may be started with:
{{cmd|$ startlxqtwayland}}

== Localized keyboard layout ==

Preferences → LXQt Settings → Keyboard and Mouse → Keyboard Layout

== Optional Configuration ==
=== Network browsing ===

For browsing of network shares within LXQt that works with file associations, you can install the gvfs packages for the network protocols you use.

For example, to browse in a SMB/cifs windows network:
{{Cmd|# apk add gvfs-smb}}

(Check: If the above may already be sufficient for gvfs to initiate the fuse kernel module. Else, try to identify if there are necessary steps in:)
{{Cmd|# apk add gvfs-fuse}}

The OpenRC script for fuse is in a separate package.
{{Cmd|# apk add {{pkg|fuse-openrc|arch=}}}}

Then the fuse service can be started manually.
{{Cmd|# rc-service fuse start}}

If it works, the fuse service can be added to start up automatically at boot time:
{{Cmd|# rc-update add fuse}}

=== Screen Compositor ===

To enable different effects (transparency, for example) {{Pkg|picom}} can be used.

After installation, add it to the ''Autostart'' section of the '''LXQt Session Settings'''.

The default configuration is available in {{Path|/etc/xdg/picom.conf.example}}. For modifications, it can be copied to {{Path|~/.config/picom/picom.conf}} or {{Path|~/.config/picom.conf}}.

Either modify the config file to your taste, or change the Autostart command line options. For example, <code>picom --vsync -r 12 --no-fading-openclose -b</code>.

=== Panel Widgets ===

If you cannot add the CPU and System Statistics widgets to the panel, make sure {{Pkg|libstatgrab}} and {{Pkg|libsysstat}} are installed.

=== Appearance Tweaking ===

==== Location of appearance-related configuration files ====

User-specific configuration is stored in {{Path|~/.config/lxqt/}}.

LXQt themes are [https://doc.qt.io/qt-6/stylesheet.html qss stylesheets]. They are located in {{Path|/usr/share/lxqt/themes/}} or {{Path|~/.local/share/lxqt/themes}}.

Qt Palette colors can be modified in lxqt-config-appearence > Widget Style > Qt Palette. Custom palettes are saved in {{Path|~/.local/share/lxqt/palettes/}}.

==== Additional QT Styles ====

Several packages provide additional QT Styles:
{{Cmd|# apk add {{Pkg|adwaita-qt}} {{Pkg|breeze}} {{Pkg|oxygen}}}}

They also provide additional cursors.

==== Consistant Theming ====

Adding the KEY=VAL <code>QT_QPA_PLATFORMTHEME=lxqt</code> to the Environment section of the Session Settings [https://github.com/lxqt/lxqt-qtplugin#configuration-usage is suggested by the LXQt developers]. Then every Qt5 program can load the theme plugin.

Another option, however, is to to install the package {{Pkg|qt5ct}} (from [[Repositories | Testing]]) and appending the line <code>QT_QPA_PLATFORMTHEME=qt5ct</code> to the environmental settings in the Environment section of the Session Settings will allow you to achieve a unified appearance between apps. Then, in the LXQt Appearance Configuration, under Widget Style, set Qt Style to <code>qt5ct-style</code>.

==== Additional Packages ====

When using themes found around the web, it is possible that they are dependant on different packages. Consider using {{Pkg|qt5-qtgraphicaleffects}}, {{Pkg|qt5-qtquickcontrols}}, and {{Pkg|qt5-qtquickcontrols2}}.

== Documentation packages ==
* {{Pkg|lxqt-config-doc}}
* {{Pkg|lxqt-openssh-askpass-doc}}
* {{Pkg|lxqt-panel-doc}}
* {{Pkg|lxqt-policykit-doc}}
* {{Pkg|lxqt-runner-doc}}
* {{Pkg|lxqt-session-doc}}
* {{Pkg|lxqt-sudo-doc}}
* {{Pkg|lxqt-wayland-session-doc}}

== Development files ==

* {{Pkg|libdbusmenu-lxqt-dev}}
* {{Pkg|liblxqt-dev}}
* {{Pkg|lxqt-globalkeys-dev}}
* {{Pkg|lxqt-panel-dev}}
* {{Pkg|lxqt-build-tools}}

== Help wanted ==

The following LXQt components are not yet packaged in Alpine Linux:
* lxqt_wallet

The following LXQt components are out-of-date:
* obconf-qt (need an X11+openbox user to build the latest version and test it)

== Troubleshooting ==

=== Missing Icons and Fonts ===

By default a Desktop Environment needs icons. {{Pkg|adwaita-icon-theme}} is a good start.
{{Cmd|# apk add adwaita-icon-theme}}

See [[Fonts]] for more information on fonts.

== See Also ==

* [[Installation#Post-Installation|Post Install]]
* [[Desktop environments and Window managers]]
=== External Resources ===
* [https://lxqt.github.io/ LXQt Homepage]
* [https://github.com/lxqt/lxqt LXQt on GitHub]
* [https://wiki.archlinux.org/title/LXQt LXQt entry on ArchWiki]
* [https://github.com/sddm/sddm SDDM Project on GitHub]

[[Category:Desktop]]
[[Category:Desktop Environments]]

LXQt

2025-01-12T18:50:33Z

Zcrayfish: /* Basic Configuration */ wayland

{{TOC right}}

[[File:LXQt Minimal Installation.png | thumb | LXQt 1.3.0 Basic Install with Papirus icons]]

'''[https://lxqt-project.org/ LXQt]''' is a lightweight QT based desktop environment. LXQt was originally a port of LXDE to QT (called LXDE-Qt), it was created due to LXDE maintainer Hong Jen Yee being dissatisfied with GTK 3. On 21 July 2013 the LXDE(-Qt) and [https://en.wikipedia.org/wiki/Razor-qt Razor-qt] projects merged creating LXQt.

{{:Include:Setup-desktop}}

When lxqt is chosen, the {{ic|Setup-desktop}} script installs [[SDDM]] as display manager and completes all the steps listed below in the [[#Manual installation|Manual installation]] and [[#Basic Configuration|Basic Configuration]] sections.

== Manual installation ==

=== Prerequisites ===

* [[Alpine_setup_scripts#setup-xorg-base|Install Xorg]]
* [[D-Bus#Installation|Install and configure D-Bus]] (without D-Bus icons and keyboard shortcuts may be missing)
* Install a [[Fonts|font]] by issuing the command {{ic|# apk add font-dejavu}}

== Basic Configuration ==

Begin the LXQt installation by adding basic packages:
{{Cmd|# apk add {{Pkg|lxqt-desktop}} {{Pkg|lximage-qt}} {{Pkg|obconf-qt}} {{Pkg|pavucontrol-qt}}}}
If using Xorg, the following packages are also suggested: 
{{Cmd|# apk add {{Pkg|arandr}} {{Pkg|screengrab}} {{Pkg|sddm}}}}

If using wayland, the following packages are suggested: 
{{cmd|# apk add {{Pkg|lxqt-wayland-session}} {{Pkg|swayidle}} {{Pkg|swaybg}} {{Pkg|wlopm}} {{Pkg|labwc}}}}

{{Note|By default LXQt on Xorg uses [[Openbox]] as its window manager (it is a dependency of the {{Pkg|lxqt-desktop}} package). LXQt supports many different window managers and wayland compositors. Openbox has not been maintained for 9 years. Similar window managers are JWM and PeKWM. For additional Window Manager options See: [https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers Window Managers Configuration on the LXQt GitHub wiki]}}

=== Set up eudev ===
{{:Include:Setup_Device_Manager}}

=== Allowing shut down and reboot ===

To enable users to shut down the machine or reboot, the packages {{Pkg|elogind}} and {{Pkg|polkit-elogind}} need to be installed.
{{Cmd|# apk add elogind polkit-elogind}}

A reboot is required to let it take effect.

=== Auto-mounting USB drives ===

To enable automatic mounting of USB drives, install these packages:
{{Cmd|# apk add {{pkg|gvfs|arch=}} {{pkg|udisks2|arch=}}}}

Depending on what devices you intend to mount, some additional packages may be needed:
{{Cmd|{{pkg|ntfs-3g|arch=}} Stable, full-featured, read-write NTFS (driver)
{{pkg|gvfs-cdda|arch=}} CDDA support for gvfs
{{pkg|gvfs-afp|arch=}} AFP support for gvfs
{{pkg|gvfs-goa|arch=}} GNOME Online Accounts support for gvfs
{{pkg|gvfs-mtp|arch=}} MTP support for gvfs
{{pkg|gvfs-smb|arch=}} Windows fileshare support for gvfs
{{pkg|gvfs-lang|arch=}} Languages for package gvfs
{{pkg|gvfs-afc|arch=}} Apple mobile devices support for gvfs
{{pkg|gvfs-nfs|arch=}} NFS support for gvfs
{{pkg|gvfs-dev|arch=}} Backends for the gio framework in GLib (development files)
{{pkg|gvfs-archive|arch=}} Archiving support for gvfs
{{pkg|gvfs-dav|arch=}} WebDAV support for gvfs
{{pkg|gvfs-fuse|arch=}} FUSE support for gvfs
{{pkg|gvfs-gphoto2|arch=}} gphoto2 support for gvfs
{{pkg|gvfs-avahi|arch=}} DNS-SD support for gvfs}}

To list descriptions of all gvfs- packages:
{{cmd|# apk info -d {{pkg|gvfs-*|arch=x86_64}}}}

=== Enabling privilege escalation GUI ===

To enable the privilege escalation GUI for a doas/sudo user, you need to install {{Pkg|elogind}}, {{Pkg|polkit-elogind}}, and {{Pkg|sddm}}.

To have elogind run, either make them start automatically at system start:
{{Cmd|# rc-update add elogind}}

or start them manually for this time only:
{{Cmd|# rc-service elogind start }}

== Starting LXQt ==

=== With a display manager (DM) ===

If the package {{Pkg|sddm}} has been installed, SDDM may be started to log in graphically with your new user.
{{Cmd|# rc-service sddm start}}

After correct operation is verified, sddm can be enabled to start up during boot:
{{Cmd|# rc-update add sddm}}

=== From the command line ===

LXQt for X11 may be started with:
{{cmd|$ startlxqt}}

LXQt for Wayland may be started with:
{{cmd|$ startlxqtwayland}}

== Localized keyboard layout ==

Preferences → LXQt Settings → Keyboard and Mouse → Keyboard Layout

== Optional Configuration ==
=== Network browsing ===

For browsing of network shares within LXQt that works with file associations, you can install the gvfs packages for the network protocols you use.

For example, to browse in a SMB/cifs windows network:
{{Cmd|# apk add gvfs-smb}}

(Check: If the above may already be sufficient for gvfs to initiate the fuse kernel module. Else, try to identify if there are necessary steps in:)
{{Cmd|# apk add gvfs-fuse}}

The OpenRC script for fuse is in a separate package.
{{Cmd|# apk add {{pkg|fuse-openrc|arch=}}}}

Then the fuse service can be started manually.
{{Cmd|# rc-service fuse start}}

If it works, the fuse service can be added to start up automatically at boot time:
{{Cmd|# rc-update add fuse}}

=== Screen Compositor ===

To enable different effects (transparency, for example) {{Pkg|picom}} can be used.

After installation, add it to the ''Autostart'' section of the '''LXQt Session Settings'''.

The default configuration is available in {{Path|/etc/xdg/picom.conf.example}}. For modifications, it can be copied to {{Path|~/.config/picom/picom.conf}} or {{Path|~/.config/picom.conf}}.

Either modify the config file to your taste, or change the Autostart command line options. For example, <code>picom --vsync -r 12 --no-fading-openclose -b</code>.

=== Panel Widgets ===

If you cannot add the CPU and System Statistics widgets to the panel, make sure {{Pkg|libstatgrab}} and {{Pkg|libsysstat}} are installed.

=== Appearance Tweaking ===

==== Location of appearance-related configuration files ====

User-specific configuration is stored in {{Path|~/.config/lxqt/}}.

LXQt themes are [https://doc.qt.io/qt-6/stylesheet.html qss stylesheets]. They are located in {{Path|/usr/share/lxqt/themes/}} or {{Path|~/.local/share/lxqt/themes}}.

Qt Palette colors can be modified in lxqt-config-appearence > Widget Style > Qt Palette. Custom palettes are saved in {{Path|~/.local/share/lxqt/palettes/}}.

==== Additional QT Styles ====

Several packages provide additional QT Styles:
{{Cmd|# apk add {{Pkg|adwaita-qt}} {{Pkg|breeze}} {{Pkg|oxygen}}}}

They also provide additional cursors.

==== Consistant Theming ====

Adding the KEY=VAL <code>QT_QPA_PLATFORMTHEME=lxqt</code> to the Environment section of the Session Settings [https://github.com/lxqt/lxqt-qtplugin#configuration-usage is suggested by the LXQt developers]. Then every Qt5 program can load the theme plugin.

Another option, however, is to to install the package {{Pkg|qt5ct}} (from [[Repositories | Testing]]) and appending the line <code>QT_QPA_PLATFORMTHEME=qt5ct</code> to the environmental settings in the Environment section of the Session Settings will allow you to achieve a unified appearance between apps. Then, in the LXQt Appearance Configuration, under Widget Style, set Qt Style to <code>qt5ct-style</code>.

==== Additional Packages ====

When using themes found around the web, it is possible that they are dependant on different packages. Consider using {{Pkg|qt5-qtgraphicaleffects}}, {{Pkg|qt5-qtquickcontrols}}, and {{Pkg|qt5-qtquickcontrols2}}.

== Documentation packages ==
* {{Pkg|lxqt-config-doc}}
* {{Pkg|lxqt-openssh-askpass-doc}}
* {{Pkg|lxqt-panel-doc}}
* {{Pkg|lxqt-policykit-doc}}
* {{Pkg|lxqt-runner-doc}}
* {{Pkg|lxqt-session-doc}}
* {{Pkg|lxqt-sudo-doc}}
* {{Pkg|lxqt-wayland-session-doc}}

== Development files ==

* {{Pkg|libdbusmenu-lxqt-dev}}
* {{Pkg|liblxqt-dev}}
* {{Pkg|lxqt-globalkeys-dev}}
* {{Pkg|lxqt-panel-dev}}
* {{Pkg|lxqt-build-tools}}

== Help wanted ==

The following LXQt components are not yet packaged in Alpine Linux:
* lxqt_wallet

The following LXQt components are out-of-date:
* obconf-qt (need an X11+openbox user to build the latest version and test it)

== Troubleshooting ==

=== Missing Icons and Fonts ===

By default a Desktop Environment needs icons. {{Pkg|adwaita-icon-theme}} is a good start.
{{Cmd|# apk add adwaita-icon-theme}}

See [[Fonts]] for more information on fonts.

== See Also ==

* [[Installation#Post-Installation|Post Install]]
* [[Desktop environments and Window managers]]
=== External Resources ===
* [https://lxqt.github.io/ LXQt Homepage]
* [https://github.com/lxqt/lxqt LXQt on GitHub]
* [https://wiki.archlinux.org/title/LXQt LXQt entry on ArchWiki]
* [https://github.com/sddm/sddm SDDM Project on GitHub]

[[Category:Desktop]]
[[Category:Desktop Environments]]

Intel Video

2025-01-12T18:47:30Z

Zcrayfish: Added blurb about PowerVR-based GMA... which use a different set of drivers.

This page documents the graphics driver for Intel GMA on-board graphics cards and Intel iGPU and dedicated graphics cards (excluding [https://en.wikipedia.org/wiki/List_of_Intel_graphics_processing_units#PowerVR_based PowerVR-based models]). Install the following packages as needed:

* {{Pkg|mesa-dri-gallium}}: '''necessary''' Mesa drivers for all Intel Graphics.
* {{Pkg|mesa-va-gallium}}: Mesa vaapi drivers for all Intel video decoding acceleration. You want one of the below too.
* {{Pkg|intel-media-driver}}: VAAPI driver, for hardware accelerated video encoding and decoding. What you want since Intel Broadwell.
* {{Pkg|libva-intel-driver}}: VAAPI driver, for processors older than Broadwell.
* {{Pkg|linux-firmware-i915}}: Needed if the i915 driver complains about firmware being missing in dmesg

== Use environment variables ==

For all Intel Graphics up to Haswell, the user must manually select '''crocus''' Mesa driver in order to let the graphics work properly:

<pre>
export MESA_LOADER_DRIVER_OVERRIDE=crocus
</pre>

For newer Intel Graphics, if automatic driver selection does not work and bugs such as missing mouse cursor under [[Sway]] occur (no hardware graphics acceleration), the user can manually select '''iris''' driver:

<pre>
export MESA_LOADER_DRIVER_OVERRIDE=iris
</pre>

== Legacy drivers ==
{{Main|Xorg}}
Legacy drivers like {{Pkg|xf86-video-intel}} which have [https://wiki.archlinux.org/title/Intel_graphics#Installation known Issues]. Use these, only if nothing else works.

[[Category:Hardware]]
[[Category:Drivers]]
[[Category:Graphics]]

LXQt

2025-01-12T18:34:34Z

Zcrayfish: /* From the command line */ +startlxqtwayland

{{TOC right}}

[[File:LXQt Minimal Installation.png | thumb | LXQt 1.3.0 Basic Install with Papirus icons]]

'''[https://lxqt-project.org/ LXQt]''' is a lightweight QT based desktop environment. LXQt was originally a port of LXDE to QT (called LXDE-Qt), it was created due to LXDE maintainer Hong Jen Yee being dissatisfied with GTK 3. On 21 July 2013 the LXDE(-Qt) and [https://en.wikipedia.org/wiki/Razor-qt Razor-qt] projects merged creating LXQt.

{{:Include:Setup-desktop}}

When lxqt is chosen, the {{ic|Setup-desktop}} script installs [[SDDM]] as display manager and completes all the steps listed below in the [[#Manual installation|Manual installation]] and [[#Basic Configuration|Basic Configuration]] sections.

== Manual installation ==

=== Prerequisites ===

* [[Alpine_setup_scripts#setup-xorg-base|Install Xorg]]
* [[D-Bus#Installation|Install and configure D-Bus]] (without D-Bus icons and keyboard shortcuts may be missing)
* Install a [[Fonts|font]] by issuing the command {{ic|# apk add font-dejavu}}

== Basic Configuration ==

Begin the LXQt installation by adding basic packages:
{{Cmd|# apk add {{Pkg|lxqt-desktop}} {{Pkg|lximage-qt}} {{Pkg|obconf-qt}} {{Pkg|pavucontrol-qt}}}}
If using Xorg, the following packages are also suggested: 
{{Cmd|# apk add {{Pkg|arandr}} {{Pkg|screengrab}} {{Pkg|sddm}}}}

{{Note|By default LXQt on Xorg uses [[Openbox]] as its window manager (it is a dependency of the {{Pkg|lxqt-desktop}} package). LXQt supports many different window managers and wayland compositors. Openbox has not been maintained for 9 years. Similar window managers are JWM and PeKWM. For additional Window Manager options See: [https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers Window Managers Configuration on the LXQt GitHub wiki]}}

=== Set up eudev ===
{{:Include:Setup_Device_Manager}}

=== Allowing shut down and reboot ===

To enable users to shut down the machine or reboot, the packages {{Pkg|elogind}} and {{Pkg|polkit-elogind}} need to be installed.
{{Cmd|# apk add elogind polkit-elogind}}

A reboot is required to let it take effect.

=== Auto-mounting USB drives ===

To enable automatic mounting of USB drives, install these packages:
{{Cmd|# apk add {{pkg|gvfs|arch=}} {{pkg|udisks2|arch=}}}}

Depending on what devices you intend to mount, some additional packages may be needed:
{{Cmd|{{pkg|ntfs-3g|arch=}} Stable, full-featured, read-write NTFS (driver)
{{pkg|gvfs-cdda|arch=}} CDDA support for gvfs
{{pkg|gvfs-afp|arch=}} AFP support for gvfs
{{pkg|gvfs-goa|arch=}} GNOME Online Accounts support for gvfs
{{pkg|gvfs-mtp|arch=}} MTP support for gvfs
{{pkg|gvfs-smb|arch=}} Windows fileshare support for gvfs
{{pkg|gvfs-lang|arch=}} Languages for package gvfs
{{pkg|gvfs-afc|arch=}} Apple mobile devices support for gvfs
{{pkg|gvfs-nfs|arch=}} NFS support for gvfs
{{pkg|gvfs-dev|arch=}} Backends for the gio framework in GLib (development files)
{{pkg|gvfs-archive|arch=}} Archiving support for gvfs
{{pkg|gvfs-dav|arch=}} WebDAV support for gvfs
{{pkg|gvfs-fuse|arch=}} FUSE support for gvfs
{{pkg|gvfs-gphoto2|arch=}} gphoto2 support for gvfs
{{pkg|gvfs-avahi|arch=}} DNS-SD support for gvfs}}

To list descriptions of all gvfs- packages:
{{cmd|# apk info -d {{pkg|gvfs-*|arch=x86_64}}}}

=== Enabling privilege escalation GUI ===

To enable the privilege escalation GUI for a doas/sudo user, you need to install {{Pkg|elogind}}, {{Pkg|polkit-elogind}}, and {{Pkg|sddm}}.

To have elogind run, either make them start automatically at system start:
{{Cmd|# rc-update add elogind}}

or start them manually for this time only:
{{Cmd|# rc-service elogind start }}

== Starting LXQt ==

=== With a display manager (DM) ===

If the package {{Pkg|sddm}} has been installed, SDDM may be started to log in graphically with your new user.
{{Cmd|# rc-service sddm start}}

After correct operation is verified, sddm can be enabled to start up during boot:
{{Cmd|# rc-update add sddm}}

=== From the command line ===

LXQt for X11 may be started with:
{{cmd|$ startlxqt}}

LXQt for Wayland may be started with:
{{cmd|$ startlxqtwayland}}

== Localized keyboard layout ==

Preferences → LXQt Settings → Keyboard and Mouse → Keyboard Layout

== Optional Configuration ==
=== Network browsing ===

For browsing of network shares within LXQt that works with file associations, you can install the gvfs packages for the network protocols you use.

For example, to browse in a SMB/cifs windows network:
{{Cmd|# apk add gvfs-smb}}

(Check: If the above may already be sufficient for gvfs to initiate the fuse kernel module. Else, try to identify if there are necessary steps in:)
{{Cmd|# apk add gvfs-fuse}}

The OpenRC script for fuse is in a separate package.
{{Cmd|# apk add {{pkg|fuse-openrc|arch=}}}}

Then the fuse service can be started manually.
{{Cmd|# rc-service fuse start}}

If it works, the fuse service can be added to start up automatically at boot time:
{{Cmd|# rc-update add fuse}}

=== Screen Compositor ===

To enable different effects (transparency, for example) {{Pkg|picom}} can be used.

After installation, add it to the ''Autostart'' section of the '''LXQt Session Settings'''.

The default configuration is available in {{Path|/etc/xdg/picom.conf.example}}. For modifications, it can be copied to {{Path|~/.config/picom/picom.conf}} or {{Path|~/.config/picom.conf}}.

Either modify the config file to your taste, or change the Autostart command line options. For example, <code>picom --vsync -r 12 --no-fading-openclose -b</code>.

=== Panel Widgets ===

If you cannot add the CPU and System Statistics widgets to the panel, make sure {{Pkg|libstatgrab}} and {{Pkg|libsysstat}} are installed.

=== Appearance Tweaking ===

==== Location of appearance-related configuration files ====

User-specific configuration is stored in {{Path|~/.config/lxqt/}}.

LXQt themes are [https://doc.qt.io/qt-6/stylesheet.html qss stylesheets]. They are located in {{Path|/usr/share/lxqt/themes/}} or {{Path|~/.local/share/lxqt/themes}}.

Qt Palette colors can be modified in lxqt-config-appearence > Widget Style > Qt Palette. Custom palettes are saved in {{Path|~/.local/share/lxqt/palettes/}}.

==== Additional QT Styles ====

Several packages provide additional QT Styles:
{{Cmd|# apk add {{Pkg|adwaita-qt}} {{Pkg|breeze}} {{Pkg|oxygen}}}}

They also provide additional cursors.

==== Consistant Theming ====

Adding the KEY=VAL <code>QT_QPA_PLATFORMTHEME=lxqt</code> to the Environment section of the Session Settings [https://github.com/lxqt/lxqt-qtplugin#configuration-usage is suggested by the LXQt developers]. Then every Qt5 program can load the theme plugin.

Another option, however, is to to install the package {{Pkg|qt5ct}} (from [[Repositories | Testing]]) and appending the line <code>QT_QPA_PLATFORMTHEME=qt5ct</code> to the environmental settings in the Environment section of the Session Settings will allow you to achieve a unified appearance between apps. Then, in the LXQt Appearance Configuration, under Widget Style, set Qt Style to <code>qt5ct-style</code>.

==== Additional Packages ====

When using themes found around the web, it is possible that they are dependant on different packages. Consider using {{Pkg|qt5-qtgraphicaleffects}}, {{Pkg|qt5-qtquickcontrols}}, and {{Pkg|qt5-qtquickcontrols2}}.

== Documentation packages ==
* {{Pkg|lxqt-config-doc}}
* {{Pkg|lxqt-openssh-askpass-doc}}
* {{Pkg|lxqt-panel-doc}}
* {{Pkg|lxqt-policykit-doc}}
* {{Pkg|lxqt-runner-doc}}
* {{Pkg|lxqt-session-doc}}
* {{Pkg|lxqt-sudo-doc}}
* {{Pkg|lxqt-wayland-session-doc}}

== Development files ==

* {{Pkg|libdbusmenu-lxqt-dev}}
* {{Pkg|liblxqt-dev}}
* {{Pkg|lxqt-globalkeys-dev}}
* {{Pkg|lxqt-panel-dev}}
* {{Pkg|lxqt-build-tools}}

== Help wanted ==

The following LXQt components are not yet packaged in Alpine Linux:
* lxqt_wallet

The following LXQt components are out-of-date:
* obconf-qt (need an X11+openbox user to build the latest version and test it)

== Troubleshooting ==

=== Missing Icons and Fonts ===

By default a Desktop Environment needs icons. {{Pkg|adwaita-icon-theme}} is a good start.
{{Cmd|# apk add adwaita-icon-theme}}

See [[Fonts]] for more information on fonts.

== See Also ==

* [[Installation#Post-Installation|Post Install]]
* [[Desktop environments and Window managers]]
=== External Resources ===
* [https://lxqt.github.io/ LXQt Homepage]
* [https://github.com/lxqt/lxqt LXQt on GitHub]
* [https://wiki.archlinux.org/title/LXQt LXQt entry on ArchWiki]
* [https://github.com/sddm/sddm SDDM Project on GitHub]

[[Category:Desktop]]
[[Category:Desktop Environments]]

LXQt

2025-01-12T18:32:31Z

Zcrayfish: /* Development files */ +libdbusmenu-lxqt-dev, +liblxqt-dev

{{TOC right}}

[[File:LXQt Minimal Installation.png | thumb | LXQt 1.3.0 Basic Install with Papirus icons]]

'''[https://lxqt-project.org/ LXQt]''' is a lightweight QT based desktop environment. LXQt was originally a port of LXDE to QT (called LXDE-Qt), it was created due to LXDE maintainer Hong Jen Yee being dissatisfied with GTK 3. On 21 July 2013 the LXDE(-Qt) and [https://en.wikipedia.org/wiki/Razor-qt Razor-qt] projects merged creating LXQt.

{{:Include:Setup-desktop}}

When lxqt is chosen, the {{ic|Setup-desktop}} script installs [[SDDM]] as display manager and completes all the steps listed below in the [[#Manual installation|Manual installation]] and [[#Basic Configuration|Basic Configuration]] sections.

== Manual installation ==

=== Prerequisites ===

* [[Alpine_setup_scripts#setup-xorg-base|Install Xorg]]
* [[D-Bus#Installation|Install and configure D-Bus]] (without D-Bus icons and keyboard shortcuts may be missing)
* Install a [[Fonts|font]] by issuing the command {{ic|# apk add font-dejavu}}

== Basic Configuration ==

Begin the LXQt installation by adding basic packages:
{{Cmd|# apk add {{Pkg|lxqt-desktop}} {{Pkg|lximage-qt}} {{Pkg|obconf-qt}} {{Pkg|pavucontrol-qt}}}}
If using Xorg, the following packages are also suggested: 
{{Cmd|# apk add {{Pkg|arandr}} {{Pkg|screengrab}} {{Pkg|sddm}}}}

{{Note|By default LXQt on Xorg uses [[Openbox]] as its window manager (it is a dependency of the {{Pkg|lxqt-desktop}} package). LXQt supports many different window managers and wayland compositors. Openbox has not been maintained for 9 years. Similar window managers are JWM and PeKWM. For additional Window Manager options See: [https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers Window Managers Configuration on the LXQt GitHub wiki]}}

=== Set up eudev ===
{{:Include:Setup_Device_Manager}}

=== Allowing shut down and reboot ===

To enable users to shut down the machine or reboot, the packages {{Pkg|elogind}} and {{Pkg|polkit-elogind}} need to be installed.
{{Cmd|# apk add elogind polkit-elogind}}

A reboot is required to let it take effect.

=== Auto-mounting USB drives ===

To enable automatic mounting of USB drives, install these packages:
{{Cmd|# apk add {{pkg|gvfs|arch=}} {{pkg|udisks2|arch=}}}}

Depending on what devices you intend to mount, some additional packages may be needed:
{{Cmd|{{pkg|ntfs-3g|arch=}} Stable, full-featured, read-write NTFS (driver)
{{pkg|gvfs-cdda|arch=}} CDDA support for gvfs
{{pkg|gvfs-afp|arch=}} AFP support for gvfs
{{pkg|gvfs-goa|arch=}} GNOME Online Accounts support for gvfs
{{pkg|gvfs-mtp|arch=}} MTP support for gvfs
{{pkg|gvfs-smb|arch=}} Windows fileshare support for gvfs
{{pkg|gvfs-lang|arch=}} Languages for package gvfs
{{pkg|gvfs-afc|arch=}} Apple mobile devices support for gvfs
{{pkg|gvfs-nfs|arch=}} NFS support for gvfs
{{pkg|gvfs-dev|arch=}} Backends for the gio framework in GLib (development files)
{{pkg|gvfs-archive|arch=}} Archiving support for gvfs
{{pkg|gvfs-dav|arch=}} WebDAV support for gvfs
{{pkg|gvfs-fuse|arch=}} FUSE support for gvfs
{{pkg|gvfs-gphoto2|arch=}} gphoto2 support for gvfs
{{pkg|gvfs-avahi|arch=}} DNS-SD support for gvfs}}

To list descriptions of all gvfs- packages:
{{cmd|# apk info -d {{pkg|gvfs-*|arch=x86_64}}}}

=== Enabling privilege escalation GUI ===

To enable the privilege escalation GUI for a doas/sudo user, you need to install {{Pkg|elogind}}, {{Pkg|polkit-elogind}}, and {{Pkg|sddm}}.

To have elogind run, either make them start automatically at system start:
{{Cmd|# rc-update add elogind}}

or start them manually for this time only:
{{Cmd|# rc-service elogind start }}

== Starting LXQt ==

=== With a display manager (DM) ===

If the package {{Pkg|sddm}} has been installed, SDDM may be started to log in graphically with your new user.
{{Cmd|# rc-service sddm start}}

After correct operation is verified, sddm can be enabled to start up during boot:
{{Cmd|# rc-update add sddm}}

=== From the command line ===

LXQt for X11 may be started with:
{{cmd|# startlxqt}}

== Localized keyboard layout ==

Preferences → LXQt Settings → Keyboard and Mouse → Keyboard Layout

== Optional Configuration ==
=== Network browsing ===

For browsing of network shares within LXQt that works with file associations, you can install the gvfs packages for the network protocols you use.

For example, to browse in a SMB/cifs windows network:
{{Cmd|# apk add gvfs-smb}}

(Check: If the above may already be sufficient for gvfs to initiate the fuse kernel module. Else, try to identify if there are necessary steps in:)
{{Cmd|# apk add gvfs-fuse}}

The OpenRC script for fuse is in a separate package.
{{Cmd|# apk add {{pkg|fuse-openrc|arch=}}}}

Then the fuse service can be started manually.
{{Cmd|# rc-service fuse start}}

If it works, the fuse service can be added to start up automatically at boot time:
{{Cmd|# rc-update add fuse}}

=== Screen Compositor ===

To enable different effects (transparency, for example) {{Pkg|picom}} can be used.

After installation, add it to the ''Autostart'' section of the '''LXQt Session Settings'''.

The default configuration is available in {{Path|/etc/xdg/picom.conf.example}}. For modifications, it can be copied to {{Path|~/.config/picom/picom.conf}} or {{Path|~/.config/picom.conf}}.

Either modify the config file to your taste, or change the Autostart command line options. For example, <code>picom --vsync -r 12 --no-fading-openclose -b</code>.

=== Panel Widgets ===

If you cannot add the CPU and System Statistics widgets to the panel, make sure {{Pkg|libstatgrab}} and {{Pkg|libsysstat}} are installed.

=== Appearance Tweaking ===

==== Location of appearance-related configuration files ====

User-specific configuration is stored in {{Path|~/.config/lxqt/}}.

LXQt themes are [https://doc.qt.io/qt-6/stylesheet.html qss stylesheets]. They are located in {{Path|/usr/share/lxqt/themes/}} or {{Path|~/.local/share/lxqt/themes}}.

Qt Palette colors can be modified in lxqt-config-appearence > Widget Style > Qt Palette. Custom palettes are saved in {{Path|~/.local/share/lxqt/palettes/}}.

==== Additional QT Styles ====

Several packages provide additional QT Styles:
{{Cmd|# apk add {{Pkg|adwaita-qt}} {{Pkg|breeze}} {{Pkg|oxygen}}}}

They also provide additional cursors.

==== Consistant Theming ====

Adding the KEY=VAL <code>QT_QPA_PLATFORMTHEME=lxqt</code> to the Environment section of the Session Settings [https://github.com/lxqt/lxqt-qtplugin#configuration-usage is suggested by the LXQt developers]. Then every Qt5 program can load the theme plugin.

Another option, however, is to to install the package {{Pkg|qt5ct}} (from [[Repositories | Testing]]) and appending the line <code>QT_QPA_PLATFORMTHEME=qt5ct</code> to the environmental settings in the Environment section of the Session Settings will allow you to achieve a unified appearance between apps. Then, in the LXQt Appearance Configuration, under Widget Style, set Qt Style to <code>qt5ct-style</code>.

==== Additional Packages ====

When using themes found around the web, it is possible that they are dependant on different packages. Consider using {{Pkg|qt5-qtgraphicaleffects}}, {{Pkg|qt5-qtquickcontrols}}, and {{Pkg|qt5-qtquickcontrols2}}.

== Documentation packages ==
* {{Pkg|lxqt-config-doc}}
* {{Pkg|lxqt-openssh-askpass-doc}}
* {{Pkg|lxqt-panel-doc}}
* {{Pkg|lxqt-policykit-doc}}
* {{Pkg|lxqt-runner-doc}}
* {{Pkg|lxqt-session-doc}}
* {{Pkg|lxqt-sudo-doc}}
* {{Pkg|lxqt-wayland-session-doc}}

== Development files ==

* {{Pkg|libdbusmenu-lxqt-dev}}
* {{Pkg|liblxqt-dev}}
* {{Pkg|lxqt-globalkeys-dev}}
* {{Pkg|lxqt-panel-dev}}
* {{Pkg|lxqt-build-tools}}

== Help wanted ==

The following LXQt components are not yet packaged in Alpine Linux:
* lxqt_wallet

The following LXQt components are out-of-date:
* obconf-qt (need an X11+openbox user to build the latest version and test it)

== Troubleshooting ==

=== Missing Icons and Fonts ===

By default a Desktop Environment needs icons. {{Pkg|adwaita-icon-theme}} is a good start.
{{Cmd|# apk add adwaita-icon-theme}}

See [[Fonts]] for more information on fonts.

== See Also ==

* [[Installation#Post-Installation|Post Install]]
* [[Desktop environments and Window managers]]
=== External Resources ===
* [https://lxqt.github.io/ LXQt Homepage]
* [https://github.com/lxqt/lxqt LXQt on GitHub]
* [https://wiki.archlinux.org/title/LXQt LXQt entry on ArchWiki]
* [https://github.com/sddm/sddm SDDM Project on GitHub]

[[Category:Desktop]]
[[Category:Desktop Environments]]

LXQt

2025-01-12T18:31:24Z

Zcrayfish: /* Documentation packages */ +lxqt-wayland-session-doc

{{TOC right}}

[[File:LXQt Minimal Installation.png | thumb | LXQt 1.3.0 Basic Install with Papirus icons]]

'''[https://lxqt-project.org/ LXQt]''' is a lightweight QT based desktop environment. LXQt was originally a port of LXDE to QT (called LXDE-Qt), it was created due to LXDE maintainer Hong Jen Yee being dissatisfied with GTK 3. On 21 July 2013 the LXDE(-Qt) and [https://en.wikipedia.org/wiki/Razor-qt Razor-qt] projects merged creating LXQt.

{{:Include:Setup-desktop}}

When lxqt is chosen, the {{ic|Setup-desktop}} script installs [[SDDM]] as display manager and completes all the steps listed below in the [[#Manual installation|Manual installation]] and [[#Basic Configuration|Basic Configuration]] sections.

== Manual installation ==

=== Prerequisites ===

* [[Alpine_setup_scripts#setup-xorg-base|Install Xorg]]
* [[D-Bus#Installation|Install and configure D-Bus]] (without D-Bus icons and keyboard shortcuts may be missing)
* Install a [[Fonts|font]] by issuing the command {{ic|# apk add font-dejavu}}

== Basic Configuration ==

Begin the LXQt installation by adding basic packages:
{{Cmd|# apk add {{Pkg|lxqt-desktop}} {{Pkg|lximage-qt}} {{Pkg|obconf-qt}} {{Pkg|pavucontrol-qt}}}}
If using Xorg, the following packages are also suggested: 
{{Cmd|# apk add {{Pkg|arandr}} {{Pkg|screengrab}} {{Pkg|sddm}}}}

{{Note|By default LXQt on Xorg uses [[Openbox]] as its window manager (it is a dependency of the {{Pkg|lxqt-desktop}} package). LXQt supports many different window managers and wayland compositors. Openbox has not been maintained for 9 years. Similar window managers are JWM and PeKWM. For additional Window Manager options See: [https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers Window Managers Configuration on the LXQt GitHub wiki]}}

=== Set up eudev ===
{{:Include:Setup_Device_Manager}}

=== Allowing shut down and reboot ===

To enable users to shut down the machine or reboot, the packages {{Pkg|elogind}} and {{Pkg|polkit-elogind}} need to be installed.
{{Cmd|# apk add elogind polkit-elogind}}

A reboot is required to let it take effect.

=== Auto-mounting USB drives ===

To enable automatic mounting of USB drives, install these packages:
{{Cmd|# apk add {{pkg|gvfs|arch=}} {{pkg|udisks2|arch=}}}}

Depending on what devices you intend to mount, some additional packages may be needed:
{{Cmd|{{pkg|ntfs-3g|arch=}} Stable, full-featured, read-write NTFS (driver)
{{pkg|gvfs-cdda|arch=}} CDDA support for gvfs
{{pkg|gvfs-afp|arch=}} AFP support for gvfs
{{pkg|gvfs-goa|arch=}} GNOME Online Accounts support for gvfs
{{pkg|gvfs-mtp|arch=}} MTP support for gvfs
{{pkg|gvfs-smb|arch=}} Windows fileshare support for gvfs
{{pkg|gvfs-lang|arch=}} Languages for package gvfs
{{pkg|gvfs-afc|arch=}} Apple mobile devices support for gvfs
{{pkg|gvfs-nfs|arch=}} NFS support for gvfs
{{pkg|gvfs-dev|arch=}} Backends for the gio framework in GLib (development files)
{{pkg|gvfs-archive|arch=}} Archiving support for gvfs
{{pkg|gvfs-dav|arch=}} WebDAV support for gvfs
{{pkg|gvfs-fuse|arch=}} FUSE support for gvfs
{{pkg|gvfs-gphoto2|arch=}} gphoto2 support for gvfs
{{pkg|gvfs-avahi|arch=}} DNS-SD support for gvfs}}

To list descriptions of all gvfs- packages:
{{cmd|# apk info -d {{pkg|gvfs-*|arch=x86_64}}}}

=== Enabling privilege escalation GUI ===

To enable the privilege escalation GUI for a doas/sudo user, you need to install {{Pkg|elogind}}, {{Pkg|polkit-elogind}}, and {{Pkg|sddm}}.

To have elogind run, either make them start automatically at system start:
{{Cmd|# rc-update add elogind}}

or start them manually for this time only:
{{Cmd|# rc-service elogind start }}

== Starting LXQt ==

=== With a display manager (DM) ===

If the package {{Pkg|sddm}} has been installed, SDDM may be started to log in graphically with your new user.
{{Cmd|# rc-service sddm start}}

After correct operation is verified, sddm can be enabled to start up during boot:
{{Cmd|# rc-update add sddm}}

=== From the command line ===

LXQt for X11 may be started with:
{{cmd|# startlxqt}}

== Localized keyboard layout ==

Preferences → LXQt Settings → Keyboard and Mouse → Keyboard Layout

== Optional Configuration ==
=== Network browsing ===

For browsing of network shares within LXQt that works with file associations, you can install the gvfs packages for the network protocols you use.

For example, to browse in a SMB/cifs windows network:
{{Cmd|# apk add gvfs-smb}}

(Check: If the above may already be sufficient for gvfs to initiate the fuse kernel module. Else, try to identify if there are necessary steps in:)
{{Cmd|# apk add gvfs-fuse}}

The OpenRC script for fuse is in a separate package.
{{Cmd|# apk add {{pkg|fuse-openrc|arch=}}}}

Then the fuse service can be started manually.
{{Cmd|# rc-service fuse start}}

If it works, the fuse service can be added to start up automatically at boot time:
{{Cmd|# rc-update add fuse}}

=== Screen Compositor ===

To enable different effects (transparency, for example) {{Pkg|picom}} can be used.

After installation, add it to the ''Autostart'' section of the '''LXQt Session Settings'''.

The default configuration is available in {{Path|/etc/xdg/picom.conf.example}}. For modifications, it can be copied to {{Path|~/.config/picom/picom.conf}} or {{Path|~/.config/picom.conf}}.

Either modify the config file to your taste, or change the Autostart command line options. For example, <code>picom --vsync -r 12 --no-fading-openclose -b</code>.

=== Panel Widgets ===

If you cannot add the CPU and System Statistics widgets to the panel, make sure {{Pkg|libstatgrab}} and {{Pkg|libsysstat}} are installed.

=== Appearance Tweaking ===

==== Location of appearance-related configuration files ====

User-specific configuration is stored in {{Path|~/.config/lxqt/}}.

LXQt themes are [https://doc.qt.io/qt-6/stylesheet.html qss stylesheets]. They are located in {{Path|/usr/share/lxqt/themes/}} or {{Path|~/.local/share/lxqt/themes}}.

Qt Palette colors can be modified in lxqt-config-appearence > Widget Style > Qt Palette. Custom palettes are saved in {{Path|~/.local/share/lxqt/palettes/}}.

==== Additional QT Styles ====

Several packages provide additional QT Styles:
{{Cmd|# apk add {{Pkg|adwaita-qt}} {{Pkg|breeze}} {{Pkg|oxygen}}}}

They also provide additional cursors.

==== Consistant Theming ====

Adding the KEY=VAL <code>QT_QPA_PLATFORMTHEME=lxqt</code> to the Environment section of the Session Settings [https://github.com/lxqt/lxqt-qtplugin#configuration-usage is suggested by the LXQt developers]. Then every Qt5 program can load the theme plugin.

Another option, however, is to to install the package {{Pkg|qt5ct}} (from [[Repositories | Testing]]) and appending the line <code>QT_QPA_PLATFORMTHEME=qt5ct</code> to the environmental settings in the Environment section of the Session Settings will allow you to achieve a unified appearance between apps. Then, in the LXQt Appearance Configuration, under Widget Style, set Qt Style to <code>qt5ct-style</code>.

==== Additional Packages ====

When using themes found around the web, it is possible that they are dependant on different packages. Consider using {{Pkg|qt5-qtgraphicaleffects}}, {{Pkg|qt5-qtquickcontrols}}, and {{Pkg|qt5-qtquickcontrols2}}.

== Documentation packages ==
* {{Pkg|lxqt-config-doc}}
* {{Pkg|lxqt-openssh-askpass-doc}}
* {{Pkg|lxqt-panel-doc}}
* {{Pkg|lxqt-policykit-doc}}
* {{Pkg|lxqt-runner-doc}}
* {{Pkg|lxqt-session-doc}}
* {{Pkg|lxqt-sudo-doc}}
* {{Pkg|lxqt-wayland-session-doc}}

== Development files ==

* {{Pkg|lxqt-globalkeys-dev}}
* {{Pkg|lxqt-panel-dev}}
* {{Pkg|lxqt-build-tools}}

== Help wanted ==

The following LXQt components are not yet packaged in Alpine Linux:
* lxqt_wallet

The following LXQt components are out-of-date:
* obconf-qt (need an X11+openbox user to build the latest version and test it)

== Troubleshooting ==

=== Missing Icons and Fonts ===

By default a Desktop Environment needs icons. {{Pkg|adwaita-icon-theme}} is a good start.
{{Cmd|# apk add adwaita-icon-theme}}

See [[Fonts]] for more information on fonts.

== See Also ==

* [[Installation#Post-Installation|Post Install]]
* [[Desktop environments and Window managers]]
=== External Resources ===
* [https://lxqt.github.io/ LXQt Homepage]
* [https://github.com/lxqt/lxqt LXQt on GitHub]
* [https://wiki.archlinux.org/title/LXQt LXQt entry on ArchWiki]
* [https://github.com/sddm/sddm SDDM Project on GitHub]

[[Category:Desktop]]
[[Category:Desktop Environments]]

LXQt

2025-01-12T18:30:00Z

Zcrayfish: /* Missing Icons and Fonts */ grammar

{{TOC right}}

[[File:LXQt Minimal Installation.png | thumb | LXQt 1.3.0 Basic Install with Papirus icons]]

'''[https://lxqt-project.org/ LXQt]''' is a lightweight QT based desktop environment. LXQt was originally a port of LXDE to QT (called LXDE-Qt), it was created due to LXDE maintainer Hong Jen Yee being dissatisfied with GTK 3. On 21 July 2013 the LXDE(-Qt) and [https://en.wikipedia.org/wiki/Razor-qt Razor-qt] projects merged creating LXQt.

{{:Include:Setup-desktop}}

When lxqt is chosen, the {{ic|Setup-desktop}} script installs [[SDDM]] as display manager and completes all the steps listed below in the [[#Manual installation|Manual installation]] and [[#Basic Configuration|Basic Configuration]] sections.

== Manual installation ==

=== Prerequisites ===

* [[Alpine_setup_scripts#setup-xorg-base|Install Xorg]]
* [[D-Bus#Installation|Install and configure D-Bus]] (without D-Bus icons and keyboard shortcuts may be missing)
* Install a [[Fonts|font]] by issuing the command {{ic|# apk add font-dejavu}}

== Basic Configuration ==

Begin the LXQt installation by adding basic packages:
{{Cmd|# apk add {{Pkg|lxqt-desktop}} {{Pkg|lximage-qt}} {{Pkg|obconf-qt}} {{Pkg|pavucontrol-qt}}}}
If using Xorg, the following packages are also suggested: 
{{Cmd|# apk add {{Pkg|arandr}} {{Pkg|screengrab}} {{Pkg|sddm}}}}

{{Note|By default LXQt on Xorg uses [[Openbox]] as its window manager (it is a dependency of the {{Pkg|lxqt-desktop}} package). LXQt supports many different window managers and wayland compositors. Openbox has not been maintained for 9 years. Similar window managers are JWM and PeKWM. For additional Window Manager options See: [https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers Window Managers Configuration on the LXQt GitHub wiki]}}

=== Set up eudev ===
{{:Include:Setup_Device_Manager}}

=== Allowing shut down and reboot ===

To enable users to shut down the machine or reboot, the packages {{Pkg|elogind}} and {{Pkg|polkit-elogind}} need to be installed.
{{Cmd|# apk add elogind polkit-elogind}}

A reboot is required to let it take effect.

=== Auto-mounting USB drives ===

To enable automatic mounting of USB drives, install these packages:
{{Cmd|# apk add {{pkg|gvfs|arch=}} {{pkg|udisks2|arch=}}}}

Depending on what devices you intend to mount, some additional packages may be needed:
{{Cmd|{{pkg|ntfs-3g|arch=}} Stable, full-featured, read-write NTFS (driver)
{{pkg|gvfs-cdda|arch=}} CDDA support for gvfs
{{pkg|gvfs-afp|arch=}} AFP support for gvfs
{{pkg|gvfs-goa|arch=}} GNOME Online Accounts support for gvfs
{{pkg|gvfs-mtp|arch=}} MTP support for gvfs
{{pkg|gvfs-smb|arch=}} Windows fileshare support for gvfs
{{pkg|gvfs-lang|arch=}} Languages for package gvfs
{{pkg|gvfs-afc|arch=}} Apple mobile devices support for gvfs
{{pkg|gvfs-nfs|arch=}} NFS support for gvfs
{{pkg|gvfs-dev|arch=}} Backends for the gio framework in GLib (development files)
{{pkg|gvfs-archive|arch=}} Archiving support for gvfs
{{pkg|gvfs-dav|arch=}} WebDAV support for gvfs
{{pkg|gvfs-fuse|arch=}} FUSE support for gvfs
{{pkg|gvfs-gphoto2|arch=}} gphoto2 support for gvfs
{{pkg|gvfs-avahi|arch=}} DNS-SD support for gvfs}}

To list descriptions of all gvfs- packages:
{{cmd|# apk info -d {{pkg|gvfs-*|arch=x86_64}}}}

=== Enabling privilege escalation GUI ===

To enable the privilege escalation GUI for a doas/sudo user, you need to install {{Pkg|elogind}}, {{Pkg|polkit-elogind}}, and {{Pkg|sddm}}.

To have elogind run, either make them start automatically at system start:
{{Cmd|# rc-update add elogind}}

or start them manually for this time only:
{{Cmd|# rc-service elogind start }}

== Starting LXQt ==

=== With a display manager (DM) ===

If the package {{Pkg|sddm}} has been installed, SDDM may be started to log in graphically with your new user.
{{Cmd|# rc-service sddm start}}

After correct operation is verified, sddm can be enabled to start up during boot:
{{Cmd|# rc-update add sddm}}

=== From the command line ===

LXQt for X11 may be started with:
{{cmd|# startlxqt}}

== Localized keyboard layout ==

Preferences → LXQt Settings → Keyboard and Mouse → Keyboard Layout

== Optional Configuration ==
=== Network browsing ===

For browsing of network shares within LXQt that works with file associations, you can install the gvfs packages for the network protocols you use.

For example, to browse in a SMB/cifs windows network:
{{Cmd|# apk add gvfs-smb}}

(Check: If the above may already be sufficient for gvfs to initiate the fuse kernel module. Else, try to identify if there are necessary steps in:)
{{Cmd|# apk add gvfs-fuse}}

The OpenRC script for fuse is in a separate package.
{{Cmd|# apk add {{pkg|fuse-openrc|arch=}}}}

Then the fuse service can be started manually.
{{Cmd|# rc-service fuse start}}

If it works, the fuse service can be added to start up automatically at boot time:
{{Cmd|# rc-update add fuse}}

=== Screen Compositor ===

To enable different effects (transparency, for example) {{Pkg|picom}} can be used.

After installation, add it to the ''Autostart'' section of the '''LXQt Session Settings'''.

The default configuration is available in {{Path|/etc/xdg/picom.conf.example}}. For modifications, it can be copied to {{Path|~/.config/picom/picom.conf}} or {{Path|~/.config/picom.conf}}.

Either modify the config file to your taste, or change the Autostart command line options. For example, <code>picom --vsync -r 12 --no-fading-openclose -b</code>.

=== Panel Widgets ===

If you cannot add the CPU and System Statistics widgets to the panel, make sure {{Pkg|libstatgrab}} and {{Pkg|libsysstat}} are installed.

=== Appearance Tweaking ===

==== Location of appearance-related configuration files ====

User-specific configuration is stored in {{Path|~/.config/lxqt/}}.

LXQt themes are [https://doc.qt.io/qt-6/stylesheet.html qss stylesheets]. They are located in {{Path|/usr/share/lxqt/themes/}} or {{Path|~/.local/share/lxqt/themes}}.

Qt Palette colors can be modified in lxqt-config-appearence > Widget Style > Qt Palette. Custom palettes are saved in {{Path|~/.local/share/lxqt/palettes/}}.

==== Additional QT Styles ====

Several packages provide additional QT Styles:
{{Cmd|# apk add {{Pkg|adwaita-qt}} {{Pkg|breeze}} {{Pkg|oxygen}}}}

They also provide additional cursors.

==== Consistant Theming ====

Adding the KEY=VAL <code>QT_QPA_PLATFORMTHEME=lxqt</code> to the Environment section of the Session Settings [https://github.com/lxqt/lxqt-qtplugin#configuration-usage is suggested by the LXQt developers]. Then every Qt5 program can load the theme plugin.

Another option, however, is to to install the package {{Pkg|qt5ct}} (from [[Repositories | Testing]]) and appending the line <code>QT_QPA_PLATFORMTHEME=qt5ct</code> to the environmental settings in the Environment section of the Session Settings will allow you to achieve a unified appearance between apps. Then, in the LXQt Appearance Configuration, under Widget Style, set Qt Style to <code>qt5ct-style</code>.

==== Additional Packages ====

When using themes found around the web, it is possible that they are dependant on different packages. Consider using {{Pkg|qt5-qtgraphicaleffects}}, {{Pkg|qt5-qtquickcontrols}}, and {{Pkg|qt5-qtquickcontrols2}}.

== Documentation packages ==
* {{Pkg|lxqt-config-doc}}
* {{Pkg|lxqt-openssh-askpass-doc}}
* {{Pkg|lxqt-panel-doc}}
* {{Pkg|lxqt-policykit-doc}}
* {{Pkg|lxqt-runner-doc}}
* {{Pkg|lxqt-session-doc}}
* {{Pkg|lxqt-sudo-doc}}

== Development files ==

* {{Pkg|lxqt-globalkeys-dev}}
* {{Pkg|lxqt-panel-dev}}
* {{Pkg|lxqt-build-tools}}

== Help wanted ==

The following LXQt components are not yet packaged in Alpine Linux:
* lxqt_wallet

The following LXQt components are out-of-date:
* obconf-qt (need an X11+openbox user to build the latest version and test it)

== Troubleshooting ==

=== Missing Icons and Fonts ===

By default a Desktop Environment needs icons. {{Pkg|adwaita-icon-theme}} is a good start.
{{Cmd|# apk add adwaita-icon-theme}}

See [[Fonts]] for more information on fonts.

== See Also ==

* [[Installation#Post-Installation|Post Install]]
* [[Desktop environments and Window managers]]
=== External Resources ===
* [https://lxqt.github.io/ LXQt Homepage]
* [https://github.com/lxqt/lxqt LXQt on GitHub]
* [https://wiki.archlinux.org/title/LXQt LXQt entry on ArchWiki]
* [https://github.com/sddm/sddm SDDM Project on GitHub]

[[Category:Desktop]]
[[Category:Desktop Environments]]

LXQt

2025-01-12T18:29:40Z

Zcrayfish: /* Help wanted */ lxqt-wayland-session is now part of the testing repo on edge.

{{TOC right}}

[[File:LXQt Minimal Installation.png | thumb | LXQt 1.3.0 Basic Install with Papirus icons]]

'''[https://lxqt-project.org/ LXQt]''' is a lightweight QT based desktop environment. LXQt was originally a port of LXDE to QT (called LXDE-Qt), it was created due to LXDE maintainer Hong Jen Yee being dissatisfied with GTK 3. On 21 July 2013 the LXDE(-Qt) and [https://en.wikipedia.org/wiki/Razor-qt Razor-qt] projects merged creating LXQt.

{{:Include:Setup-desktop}}

When lxqt is chosen, the {{ic|Setup-desktop}} script installs [[SDDM]] as display manager and completes all the steps listed below in the [[#Manual installation|Manual installation]] and [[#Basic Configuration|Basic Configuration]] sections.

== Manual installation ==

=== Prerequisites ===

* [[Alpine_setup_scripts#setup-xorg-base|Install Xorg]]
* [[D-Bus#Installation|Install and configure D-Bus]] (without D-Bus icons and keyboard shortcuts may be missing)
* Install a [[Fonts|font]] by issuing the command {{ic|# apk add font-dejavu}}

== Basic Configuration ==

Begin the LXQt installation by adding basic packages:
{{Cmd|# apk add {{Pkg|lxqt-desktop}} {{Pkg|lximage-qt}} {{Pkg|obconf-qt}} {{Pkg|pavucontrol-qt}}}}
If using Xorg, the following packages are also suggested: 
{{Cmd|# apk add {{Pkg|arandr}} {{Pkg|screengrab}} {{Pkg|sddm}}}}

{{Note|By default LXQt on Xorg uses [[Openbox]] as its window manager (it is a dependency of the {{Pkg|lxqt-desktop}} package). LXQt supports many different window managers and wayland compositors. Openbox has not been maintained for 9 years. Similar window managers are JWM and PeKWM. For additional Window Manager options See: [https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers Window Managers Configuration on the LXQt GitHub wiki]}}

=== Set up eudev ===
{{:Include:Setup_Device_Manager}}

=== Allowing shut down and reboot ===

To enable users to shut down the machine or reboot, the packages {{Pkg|elogind}} and {{Pkg|polkit-elogind}} need to be installed.
{{Cmd|# apk add elogind polkit-elogind}}

A reboot is required to let it take effect.

=== Auto-mounting USB drives ===

To enable automatic mounting of USB drives, install these packages:
{{Cmd|# apk add {{pkg|gvfs|arch=}} {{pkg|udisks2|arch=}}}}

Depending on what devices you intend to mount, some additional packages may be needed:
{{Cmd|{{pkg|ntfs-3g|arch=}} Stable, full-featured, read-write NTFS (driver)
{{pkg|gvfs-cdda|arch=}} CDDA support for gvfs
{{pkg|gvfs-afp|arch=}} AFP support for gvfs
{{pkg|gvfs-goa|arch=}} GNOME Online Accounts support for gvfs
{{pkg|gvfs-mtp|arch=}} MTP support for gvfs
{{pkg|gvfs-smb|arch=}} Windows fileshare support for gvfs
{{pkg|gvfs-lang|arch=}} Languages for package gvfs
{{pkg|gvfs-afc|arch=}} Apple mobile devices support for gvfs
{{pkg|gvfs-nfs|arch=}} NFS support for gvfs
{{pkg|gvfs-dev|arch=}} Backends for the gio framework in GLib (development files)
{{pkg|gvfs-archive|arch=}} Archiving support for gvfs
{{pkg|gvfs-dav|arch=}} WebDAV support for gvfs
{{pkg|gvfs-fuse|arch=}} FUSE support for gvfs
{{pkg|gvfs-gphoto2|arch=}} gphoto2 support for gvfs
{{pkg|gvfs-avahi|arch=}} DNS-SD support for gvfs}}

To list descriptions of all gvfs- packages:
{{cmd|# apk info -d {{pkg|gvfs-*|arch=x86_64}}}}

=== Enabling privilege escalation GUI ===

To enable the privilege escalation GUI for a doas/sudo user, you need to install {{Pkg|elogind}}, {{Pkg|polkit-elogind}}, and {{Pkg|sddm}}.

To have elogind run, either make them start automatically at system start:
{{Cmd|# rc-update add elogind}}

or start them manually for this time only:
{{Cmd|# rc-service elogind start }}

== Starting LXQt ==

=== With a display manager (DM) ===

If the package {{Pkg|sddm}} has been installed, SDDM may be started to log in graphically with your new user.
{{Cmd|# rc-service sddm start}}

After correct operation is verified, sddm can be enabled to start up during boot:
{{Cmd|# rc-update add sddm}}

=== From the command line ===

LXQt for X11 may be started with:
{{cmd|# startlxqt}}

== Localized keyboard layout ==

Preferences → LXQt Settings → Keyboard and Mouse → Keyboard Layout

== Optional Configuration ==
=== Network browsing ===

For browsing of network shares within LXQt that works with file associations, you can install the gvfs packages for the network protocols you use.

For example, to browse in a SMB/cifs windows network:
{{Cmd|# apk add gvfs-smb}}

(Check: If the above may already be sufficient for gvfs to initiate the fuse kernel module. Else, try to identify if there are necessary steps in:)
{{Cmd|# apk add gvfs-fuse}}

The OpenRC script for fuse is in a separate package.
{{Cmd|# apk add {{pkg|fuse-openrc|arch=}}}}

Then the fuse service can be started manually.
{{Cmd|# rc-service fuse start}}

If it works, the fuse service can be added to start up automatically at boot time:
{{Cmd|# rc-update add fuse}}

=== Screen Compositor ===

To enable different effects (transparency, for example) {{Pkg|picom}} can be used.

After installation, add it to the ''Autostart'' section of the '''LXQt Session Settings'''.

The default configuration is available in {{Path|/etc/xdg/picom.conf.example}}. For modifications, it can be copied to {{Path|~/.config/picom/picom.conf}} or {{Path|~/.config/picom.conf}}.

Either modify the config file to your taste, or change the Autostart command line options. For example, <code>picom --vsync -r 12 --no-fading-openclose -b</code>.

=== Panel Widgets ===

If you cannot add the CPU and System Statistics widgets to the panel, make sure {{Pkg|libstatgrab}} and {{Pkg|libsysstat}} are installed.

=== Appearance Tweaking ===

==== Location of appearance-related configuration files ====

User-specific configuration is stored in {{Path|~/.config/lxqt/}}.

LXQt themes are [https://doc.qt.io/qt-6/stylesheet.html qss stylesheets]. They are located in {{Path|/usr/share/lxqt/themes/}} or {{Path|~/.local/share/lxqt/themes}}.

Qt Palette colors can be modified in lxqt-config-appearence > Widget Style > Qt Palette. Custom palettes are saved in {{Path|~/.local/share/lxqt/palettes/}}.

==== Additional QT Styles ====

Several packages provide additional QT Styles:
{{Cmd|# apk add {{Pkg|adwaita-qt}} {{Pkg|breeze}} {{Pkg|oxygen}}}}

They also provide additional cursors.

==== Consistant Theming ====

Adding the KEY=VAL <code>QT_QPA_PLATFORMTHEME=lxqt</code> to the Environment section of the Session Settings [https://github.com/lxqt/lxqt-qtplugin#configuration-usage is suggested by the LXQt developers]. Then every Qt5 program can load the theme plugin.

Another option, however, is to to install the package {{Pkg|qt5ct}} (from [[Repositories | Testing]]) and appending the line <code>QT_QPA_PLATFORMTHEME=qt5ct</code> to the environmental settings in the Environment section of the Session Settings will allow you to achieve a unified appearance between apps. Then, in the LXQt Appearance Configuration, under Widget Style, set Qt Style to <code>qt5ct-style</code>.

==== Additional Packages ====

When using themes found around the web, it is possible that they are dependant on different packages. Consider using {{Pkg|qt5-qtgraphicaleffects}}, {{Pkg|qt5-qtquickcontrols}}, and {{Pkg|qt5-qtquickcontrols2}}.

== Documentation packages ==
* {{Pkg|lxqt-config-doc}}
* {{Pkg|lxqt-openssh-askpass-doc}}
* {{Pkg|lxqt-panel-doc}}
* {{Pkg|lxqt-policykit-doc}}
* {{Pkg|lxqt-runner-doc}}
* {{Pkg|lxqt-session-doc}}
* {{Pkg|lxqt-sudo-doc}}

== Development files ==

* {{Pkg|lxqt-globalkeys-dev}}
* {{Pkg|lxqt-panel-dev}}
* {{Pkg|lxqt-build-tools}}

== Help wanted ==

The following LXQt components are not yet packaged in Alpine Linux:
* lxqt_wallet

The following LXQt components are out-of-date:
* obconf-qt (need an X11+openbox user to build the latest version and test it)

== Troubleshooting ==

=== Missing Icons and Fonts ===

By default a Desktop Environments needs icons. {{Pkg|adwaita-icon-theme}} is a good start.
{{Cmd|# apk add adwaita-icon-theme}}

See [[Fonts]] for more information on fonts.

== See Also ==

* [[Installation#Post-Installation|Post Install]]
* [[Desktop environments and Window managers]]
=== External Resources ===
* [https://lxqt.github.io/ LXQt Homepage]
* [https://github.com/lxqt/lxqt LXQt on GitHub]
* [https://wiki.archlinux.org/title/LXQt LXQt entry on ArchWiki]
* [https://github.com/sddm/sddm SDDM Project on GitHub]

[[Category:Desktop]]
[[Category:Desktop Environments]]

User talk:Pursuable1652

2025-01-05T20:46:09Z

Zcrayfish: Talk page comments

=Talk page comment signature=
Hi there, you can sign your talk page comments with <nowiki>~~~~</nowiki> 
Best regards –[[User:zcrayfish|zcrayfish]] ([[User talk:zcrayfish|talk]]•[[Special:Contributions/zcrayfish|contribs]]•[[Special:EmailUser/zcrayfish|send email]]) 20:46, 5 January 2025 (UTC)

AppArmor

2024-12-21T02:28:04Z

Zcrayfish: Use path template. Remove HTML fluff.

{{TOC right}}

AppArmor is a kernel security module that restricts individual programs' capabilities. This can allow administrators to prevent programs accessing system resources in malicious ways according to per-applications specifications. AppArmor works by following profiles, which dictate what each application is and is not allowed to do.

== Installation ==

{{Cmd|# apk add {{Pkg|apparmor}}}}

You should also install <code>apparmor-utils</code> if you want to use the <code>aa</code> command to interact with AppArmor.

{{Cmd|# apk add {{Pkg|apparmor-utils}}}}

==Setup==

Run the command {{Cmd|# cat /sys/kernel/security/lsm}} to see what linux security modules are currently setup.

=== With SYSLINUX ===

Use a text editor of your choice (preferably a TUI based one since some GUI setups don't work with privilege escalation, unless you use sudo -e) to edit {{path|/boot/extlinux.conf}} such that the <code>'''APPEND'''</code> line ends with the following:

<pre>
lsm=landlock,yama,apparmor
</pre>

Note that because you're including lsm in this .conf file you are overriding the default lsm. Thus, you should include any lsm that you saw previously running in the above cat command. Additionally, lsm initializes these modules in order, so their position is important in regards to major/minor modules. Ensure that apparmor is placed first among major modules. Note for convenience that yama, capability, and landlock, which come with Alpine Linux, are not major modules, and apparmor can be placed after them. The module called capability is automatically included and does not need to be written in.

To persist your changes between kernel updates (which overwrite {{path|/boot/extlinux.conf}}), edit {{path|/etc/update-extlinux.conf}}, and append your <code>lsm=landlock,yama,apparmor</code> parameter to <code>default_kernel_opts</code>.

=== With GRUB ===

Add the following at the end of the value for key <code>'''GRUB_CMDLINE_LINUX_DEFAULT'''</code> to {{path|/etc/default/grub}}:

<pre>
apparmor=1 security=apparmor
</pre>

Then apply with:

{{Cmd|# grub-mkconfig -o /boot/grub/grub.cfg}}

== Running ==

Next, start AppArmor and tell [[OpenRC]] to start it on boot.

{{Cmd|# rc-service apparmor start}}

{{Cmd|# rc-update add apparmor boot}}

You can check if AppArmor is running with the command <code>aa-enabled</code>

{{Cmd|# aa-enabled}}

== Configuration ==

AppArmor works using rules established in profiles. A set of pre-made profiles is available for ease of use:

{{Cmd|# apk add {{Pkg|apparmor-profiles}}}}

Reboot following installation

=== Enabling Extra Profiles ===

Extra profiles reside in {{Path|/usr/share/apparmor/extra-profiles/}}. In order to enable to profile, it needs to be copied to {{Path|/etc/apparmor.d/}}:

If you want to enable the profile for <code>usr.bin.chromium-browser</code>, for example:

{{Cmd|# cp /usr/share/apparmor/extra-profiles/usr.bin.chromium-browser /etc/apparmor.d/}}

This will ''install'' the profile, it then needs to be set to '''complain''' or '''enforce''' mode:

{{Cmd|# aa-complain /etc/apparmor.d/usr.bin.chromium-browser}}

{{Note|Use <code>aa-enforce</code> to set it to enforce mode, '''but beware that this could break functionality'''.}}

=== Creating additional profiles ===

The profiles provided by the apparmor-profiles package are just a starter. You can create your own profiles, but first you must install and start <code>audit</code>

{{Cmd|# apk add {{Pkg|audit}}}}

{{Cmd|# rc-service auditd start}}

{{Cmd|# rc-update add auditd}}

Now you can generate your own profiles with

{{Cmd|# aa-easyprof /path/to/binary}}

or

{{Cmd|# aa-genprof /path/to/binary}}

Note that for this to work you'll probably need to set a more verbose [https://linuxconfig.org/introduction-to-the-linux-kernel-log-levels kernel log level]. For improved security, set it back to a higher level afterwards.

== Use ==

View AppArmor's report:

{{Cmd|# aa-status}}

This details how many and what profiles are in use as well as relevant findings, such as how many profiles are in complain mode or in kill mode.

== Troubleshooting ==

If you notice a bunch of AppArmor errors on boot, try running <code>aa-status</code> and <code>aa-enabled</code> in the terminal. If the output mentions AppArmor being disabled at boot, re-open your {{path|/boot/extlinux.conf}} file and make sure the '''APPEND''' line still ends with <code>lsm=landlock,yama,apparmor</code>

== See Also ==

* [https://wiki.apparmor.net/ AppArmor Wiki]
* [https://wiki.debian.org/AppArmor/HowToUse Debian Wiki: How to use AppArmor]
* [https://wiki.archlinux.org/title/AppArmor AppArmor entry on ArchWiki]

[[Category:Security]]
[[Category:Kernel]]

Release Notes for Alpine 3.22.0

2024-12-17T02:41:50Z

Zcrayfish: Use appropriate templates, correct typos, and nitpicky grammar improvements that nobody cares about. :)

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

== Significant changes ==

The X11 session for KDE Plasma has been removed. If you had {{pkg|plasma-workspace-x11|branch=v3.21|arch=}} installed make sure to remove it from {{path|/etc/apk/world}}. Wayland is the only available option now.

== Note-worthy updates ==

As always, many packages were upgraded. Make sure to read the individual release notes of the projects you use.

* Linux TODO
* busybox TODO
* GCC TODO
* LLVM TODO
* Go TODO
* Rust TODO
* PHP TODO
* GNOME TODO
* KDE Plasma TODO
* LXQt TODO
* Qt TODO
* wlroots TODO

== Significant removals ==

Talk:Custom Kernel

2024-12-03T02:06:10Z

Zcrayfish: Unsigned comment attribution.

Needs to be adjusted for other archs

— Preceding [[Help:Signature|unsigned]] comment added by [[User:Orson Teodoro|Orson Teodoro]] ([[User talk:Orson Teodoro|{{int:talkpagelinktext}}]] • [[Special:Contributions/Orson Teodoro|{{int:contribslink}}]]) 03:36, 4 March 2018‎

== Locations/paths of build config files ==

My goal is to build the Virt (not Standard/LTS) kernel using the defaults for Virt, and I don't understand which files are needed in exactly which paths.

I had difficulty understanding the excerpt below. Is anyone willing to assist me in understanding it? For example, where/what is the "linux-4.15" folder?

:''When you are done with your edits either by editing directly the APKBUILD and copying the lts.ARCH.config as .config in the linux-4.15 folder. You will then move the .config back overriding the lts.ARCH.config generated by make menuconfig.''

— Preceding [[Help:Signature|unsigned]] comment added by [[User:-anthumchris-|-anthumchris-]] ([[User talk:-anthumchris-|{{int:talkpagelinktext}}]] • [[Special:Contributions/-anthumchris-|{{int:contribslink}}]]) 17:34, 23 November 2024‎

Release Notes for Alpine 3.21.0

2024-11-17T22:28:54Z

Zcrayfish: /* LXQt 2.1 */ updated LXQt information.

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH requires restart ===

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preperations went into this release to ensure that the merge happens as smoothly as possible.

{{Note|TODO: replace with actual blog post}}

For more information, the timeline and the effects, read the blog post: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/88/diffs

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ([https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/69924 !69924])

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: https://gitlab.alpinelinux.org/alpine/aports/-/issues/16613

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* GCC 14.2.0
* LLVM 19
* Go 1.23.3
* Rust 1.82
* GNOME 47.1
* KDE Plasma 6.2.3
* LXQt 2.1.0

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== ISC DHCP ===

{{Note|TODO: Write something cool if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ([https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/75304 !75304])

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

LXQt

2024-11-10T07:01:59Z

Zcrayfish: /* Help wanted */ obconf-qt

{{TOC right}}

[[File:LXQt Minimal Installation.png | thumb | LXQt 1.3.0 Basic Install with Papirus icons]]

'''[https://lxqt-project.org/ LXQt]''' is a lightweight QT based desktop environment. LXQt was originally a port of LXDE to QT (called LXDE-Qt), it was created due to LXDE maintainer Hong Jen Yee being dissatisfied with GTK 3. On 21 July 2013 the LXDE(-Qt) and [https://en.wikipedia.org/wiki/Razor-qt Razor-qt] projects merged creating LXQt.

== Prerequisites ==

* [[Installation|Install]] Alpine Linux
* [[Setting_up_a_new_user#Creating_a_new_user|Create a user account]] (optional but recommended)
* [[Repositories#Enabling_the_community_repository|Enable the Community repository]]
* [[Alpine_setup_scripts#setup-xorg-base|Install Xorg]] (running {{ic|setup-xorg-base}} is still a requirement even if using wayland)

== Basic LXQt Desktop Installation ==
Begin the installation by adding basic packages:
{{Cmd|# apk add {{Pkg|lxqt-desktop}} {{Pkg|lximage-qt}} {{Pkg|obconf-qt}} {{Pkg|pavucontrol-qt}}}}
If using Xorg, the following packages are also suggested: 
{{Cmd|# apk add {{Pkg|arandr}} {{Pkg|screengrab}} {{Pkg|sddm}}}}

{{Note|By default LXQt on Xorg uses [[Openbox]] as its window manager (it is a dependency of the {{Pkg|lxqt-desktop}} package). LXQt supports many different window managers and wayland compositors. Openbox has not been maintained for 9 years. Similar window managers are JWM and PeKWM. For additional Window Manager options See: [https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers Window Managers Configuration on the LXQt GitHub wiki]}}

Starting dbus (desktop bus) service:
{{Cmd|# rc-service dbus start}}

Enabling dbus to start on boot:
{{Cmd|# rc-update add dbus}}

If dbus is not running it leads to issues like missing icons and keyboard shortcuts.

{{:Include:Setup_Device_Manager}}

== Starting LXQt ==

=== With a display manager (DM) ===

If the package {{Pkg|sddm}} has been installed, SDDM may be started to log in graphically with your new user.
{{Cmd|# rc-service sddm start}}

After correct operation is verified, sddm can be enabled to start up during boot:
{{Cmd|# rc-update add sddm}}

=== From the command line ===

LXQt for X11 may be started with:
{{cmd|# startlxqt}}

== Localized keyboard layout ==

Preferences → LXQt Settings → Keyboard and Mouse → Keyboard Layout

== Allowing shut down and reboot ==

To enable users to shut down the machine or reboot, the packages {{Pkg|elogind}} and {{Pkg|polkit-elogind}} need to be installed.
{{Cmd|# apk add elogind polkit-elogind}}

A reboot is required to let it take effect.

== Auto-mounting USB drives ==

To enable automatic mounting of USB drives, install these packages:
{{Cmd|# apk add {{pkg|gvfs|arch=}} {{pkg|udisks2|arch=}}}}

Depending on what devices you intend to mount, some additional packages may be needed:
{{Cmd|{{pkg|ntfs-3g|arch=}} Stable, full-featured, read-write NTFS (driver)
{{pkg|gvfs-cdda|arch=}} CDDA support for gvfs
{{pkg|gvfs-afp|arch=}} AFP support for gvfs
{{pkg|gvfs-goa|arch=}} GNOME Online Accounts support for gvfs
{{pkg|gvfs-mtp|arch=}} MTP support for gvfs
{{pkg|gvfs-smb|arch=}} Windows fileshare support for gvfs
{{pkg|gvfs-lang|arch=}} Languages for package gvfs
{{pkg|gvfs-afc|arch=}} Apple mobile devices support for gvfs
{{pkg|gvfs-nfs|arch=}} NFS support for gvfs
{{pkg|gvfs-dev|arch=}} Backends for the gio framework in GLib (development files)
{{pkg|gvfs-archive|arch=}} Archiving support for gvfs
{{pkg|gvfs-dav|arch=}} WebDAV support for gvfs
{{pkg|gvfs-fuse|arch=}} FUSE support for gvfs
{{pkg|gvfs-gphoto2|arch=}} gphoto2 support for gvfs
{{pkg|gvfs-avahi|arch=}} DNS-SD support for gvfs}}

To list descriptions of all gvfs- packages:

{{cmd|# apk info -d {{pkg|gvfs-*|arch=x86_64}}}}

== Network browsing ==

For browsing of network shares within LXQt that works with file associations, you can install the gvfs packages for the network protocols you use.

For example, to browse in a SMB/cifs windows network:

{{Cmd|# apk add gvfs-smb}}

(Check: If the above may already be sufficient for gvfs to initiate the fuse kernel module. Else, try to identify if there are necessary steps in:)

{{Cmd|# apk add gvfs-fuse}}

The OpenRC script for fuse is in a separate package.

{{Cmd|# apk add {{pkg|fuse-openrc|arch=}}}}

Then the fuse service can be started manually.

{{Cmd|# rc-service fuse start}}

If it works, the fuse service can be added to start up automatically at boot time:

{{Cmd|# rc-update add fuse}}

== Enabling privilege escalation GUI ==

To enable the privilege escalation GUI for a doas/sudo user, you need to install {{Pkg|elogind}}, {{Pkg|polkit-elogind}}, and {{Pkg|sddm}}.

To have elogind run, either make them start automatically at system start:

{{Cmd|# rc-update add elogind}}

or start them manually for this time only:

{{Cmd|# rc-service elogind start }}

== Panel Widgets ==

If you cannot add the CPU and System Statistics widgets to the panel, make sure {{Pkg|libstatgrab}} and {{Pkg|libsysstat}} are installed.

== Troubleshooting ==

=== Missing Icons and Fonts ===

By default a Desktop Environments needs icons. {{Pkg|adwaita-icon-theme}} is a good start.
{{Cmd|# apk add adwaita-icon-theme}}

See [[Fonts]] for more information on fonts.

== Optional Configuration ==

=== Screen Compositor ===

To enable different effects (transparency, for example) {{Pkg|picom}} can be used.

After installation, add it to the ''Autostart'' section of the '''LXQt Session Settings'''.

The default configuration is available in {{Path|/etc/xdg/picom.conf.example}}. For modifications, it can be copied to {{Path|~/.config/picom/picom.conf}} or {{Path|~/.config/picom.conf}}.

Either modify the config file to your taste, or change the Autostart command line options. For example, <code>picom --vsync -r 12 --no-fading-openclose -b</code>.

=== Appearance Tweaking ===

==== Location of appearance-related configuration files ====

User-specific configuration is stored in {{Path|~/.config/lxqt/}}.

LXQt themes are [https://doc.qt.io/qt-6/stylesheet.html qss stylesheets]. They are located in {{Path|/usr/share/lxqt/themes/}} or {{Path|~/.local/share/lxqt/themes}}.

Qt Palette colors can be modified in lxqt-config-appearence > Widget Style > Qt Palette. Custom palettes are saved in {{Path|~/.local/share/lxqt/palettes/}}.

==== Additional QT Styles ====

Several packages provide additional QT Styles:

{{Cmd|# apk add {{Pkg|adwaita-qt}} {{Pkg|breeze}} {{Pkg|oxygen}}}}

They also provide additional cursors.

==== Consistant Theming ====

Adding the KEY=VAL <code>QT_QPA_PLATFORMTHEME=lxqt</code> to the Environment section of the Session Settings [https://github.com/lxqt/lxqt-qtplugin#configuration-usage is suggested by the LXQt developers]. Then every Qt5 program can load the theme plugin.

Another option, however, is to to install the package {{Pkg|qt5ct}} (from [[Repositories | Testing]]) and appending the line <code>QT_QPA_PLATFORMTHEME=qt5ct</code> to the environmental settings in the Environment section of the Session Settings will allow you to achieve a unified appearance between apps. Then, in the LXQt Appearance Configuration, under Widget Style, set Qt Style to <code>qt5ct-style</code>.

==== Additional Packages ====

When using themes found around the web, it is possible that they are dependant on different packages. Consider using {{Pkg|qt5-qtgraphicaleffects}}, {{Pkg|qt5-qtquickcontrols}}, and {{Pkg|qt5-qtquickcontrols2}}.

== Documentation ==

* {{Pkg|lxqt-config-doc}}
* {{Pkg|lxqt-openssh-askpass-doc}}
* {{Pkg|lxqt-panel-doc}}
* {{Pkg|lxqt-policykit-doc}}
* {{Pkg|lxqt-runner-doc}}
* {{Pkg|lxqt-session-doc}}
* {{Pkg|lxqt-sudo-doc}}

== Development files ==

* {{Pkg|lxqt-globalkeys-dev}}
* {{Pkg|lxqt-panel-dev}}

== Misc ==

* {{Pkg|lxqt-build-tools}}

== Help wanted ==

The following LXQt components are not yet packaged in Alpine Linux:
* lxqt_wallet
* lxqt-wayland-session (will be added to testing repo after LXQt 2.1 is packaged)

The following LXQt components are out-of-date:
* obconf-qt (need an X11+openbox user to build the latest version and test it)

== See Also ==

* [[Installation#Post-Installation|Post Install]]
* [[Desktop environments and Window managers]]

= External Resources =

* [https://lxqt.github.io/ LXQt Homepage]
* [https://github.com/lxqt/lxqt LXQt on GitHub]
* [https://wiki.archlinux.org/title/LXQt LXQt entry on ArchWiki]
* [https://github.com/sddm/sddm SDDM Project on GitHub]

[[Category:Desktop]]
[[Category:Desktop Environments]]

LXQt

2024-11-07T01:54:27Z

Zcrayfish: /* Help wanted */ Adjusted subtext for lxqt-wayland-session

{{TOC right}}

[[File:LXQt Minimal Installation.png | thumb | LXQt 1.3.0 Basic Install with Papirus icons]]

'''[https://lxqt-project.org/ LXQt]''' is a lightweight QT based desktop environment. LXQt was originally a port of LXDE to QT (called LXDE-Qt), it was created due to LXDE maintainer Hong Jen Yee being dissatisfied with GTK 3. On 21 July 2013 the LXDE(-Qt) and [https://en.wikipedia.org/wiki/Razor-qt Razor-qt] projects merged creating LXQt.

== Prerequisites ==

* [[Installation|Install]] Alpine Linux
* [[Setting_up_a_new_user#Creating_a_new_user|Create a user account]] (optional but recommended)
* [[Repositories#Enabling_the_community_repository|Enable the Community repository]]
* [[Alpine_setup_scripts#setup-xorg-base|Install Xorg]] (running {{ic|setup-xorg-base}} is still a requirement even if using wayland)

== Basic LXQt Desktop Installation ==
Begin the installation by adding basic packages:
{{Cmd|# apk add {{Pkg|lxqt-desktop}} {{Pkg|lximage-qt}} {{Pkg|obconf-qt}} {{Pkg|pavucontrol-qt}}}}
If using Xorg, the following packages are also suggested: 
{{Cmd|# apk add {{Pkg|arandr}} {{Pkg|screengrab}} {{Pkg|sddm}}}}

{{Note|By default LXQt on Xorg uses [[Openbox]] as its window manager (it is a dependency of the {{Pkg|lxqt-desktop}} package). LXQt supports many different window managers and wayland compositors. Openbox has not been maintained for 9 years. Similar window managers are JWM and PeKWM. For additional Window Manager options See: [https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers Window Managers Configuration on the LXQt GitHub wiki]}}

Starting dbus (desktop bus) service:
{{Cmd|# rc-service dbus start}}

Enabling dbus to start on boot:
{{Cmd|# rc-update add dbus}}

If dbus is not running it leads to issues like missing icons and keyboard shortcuts.

{{:Include:Setup_Device_Manager}}

== Starting LXQt ==

=== With a display manager (DM) ===

If the package {{Pkg|sddm}} has been installed, SDDM may be started to log in graphically with your new user.
{{Cmd|# rc-service sddm start}}

After correct operation is verified, sddm can be enabled to start up during boot:
{{Cmd|# rc-update add sddm}}

=== From the command line ===

LXQt for X11 may be started with:
{{cmd|# startlxqt}}

== Localized keyboard layout ==

Preferences → LXQt Settings → Keyboard and Mouse → Keyboard Layout

== Allowing shut down and reboot ==

To enable users to shut down the machine or reboot, the packages {{Pkg|elogind}} and {{Pkg|polkit-elogind}} need to be installed.
{{Cmd|# apk add elogind polkit-elogind}}

A reboot is required to let it take effect.

== Auto-mounting USB drives ==

To enable automatic mounting of USB drives, install these packages:
{{Cmd|# apk add {{pkg|gvfs|arch=}} {{pkg|udisks2|arch=}}}}

Depending on what devices you intend to mount, some additional packages may be needed:
{{Cmd|{{pkg|ntfs-3g|arch=}} Stable, full-featured, read-write NTFS (driver)
{{pkg|gvfs-cdda|arch=}} CDDA support for gvfs
{{pkg|gvfs-afp|arch=}} AFP support for gvfs
{{pkg|gvfs-goa|arch=}} GNOME Online Accounts support for gvfs
{{pkg|gvfs-mtp|arch=}} MTP support for gvfs
{{pkg|gvfs-smb|arch=}} Windows fileshare support for gvfs
{{pkg|gvfs-lang|arch=}} Languages for package gvfs
{{pkg|gvfs-afc|arch=}} Apple mobile devices support for gvfs
{{pkg|gvfs-nfs|arch=}} NFS support for gvfs
{{pkg|gvfs-dev|arch=}} Backends for the gio framework in GLib (development files)
{{pkg|gvfs-archive|arch=}} Archiving support for gvfs
{{pkg|gvfs-dav|arch=}} WebDAV support for gvfs
{{pkg|gvfs-fuse|arch=}} FUSE support for gvfs
{{pkg|gvfs-gphoto2|arch=}} gphoto2 support for gvfs
{{pkg|gvfs-avahi|arch=}} DNS-SD support for gvfs}}

To list descriptions of all gvfs- packages:

{{cmd|# apk info -d {{pkg|gvfs-*|arch=x86_64}}}}

== Network browsing ==

For browsing of network shares within LXQt that works with file associations, you can install the gvfs packages for the network protocols you use.

For example, to browse in a SMB/cifs windows network:

{{Cmd|# apk add gvfs-smb}}

(Check: If the above may already be sufficient for gvfs to initiate the fuse kernel module. Else, try to identify if there are necessary steps in:)

{{Cmd|# apk add gvfs-fuse}}

The OpenRC script for fuse is in a separate package.

{{Cmd|# apk add {{pkg|fuse-openrc|arch=}}}}

Then the fuse service can be started manually.

{{Cmd|# rc-service fuse start}}

If it works, the fuse service can be added to start up automatically at boot time:

{{Cmd|# rc-update add fuse}}

== Enabling privilege escalation GUI ==

To enable the privilege escalation GUI for a doas/sudo user, you need to install {{Pkg|elogind}}, {{Pkg|polkit-elogind}}, and {{Pkg|sddm}}.

To have elogind run, either make them start automatically at system start:

{{Cmd|# rc-update add elogind}}

or start them manually for this time only:

{{Cmd|# rc-service elogind start }}

== Panel Widgets ==

If you cannot add the CPU and System Statistics widgets to the panel, make sure {{Pkg|libstatgrab}} and {{Pkg|libsysstat}} are installed.

== Troubleshooting ==

=== Missing Icons and Fonts ===

By default a Desktop Environments needs icons. {{Pkg|adwaita-icon-theme}} is a good start.
{{Cmd|# apk add adwaita-icon-theme}}

See [[Fonts]] for more information on fonts.

== Optional Configuration ==

=== Screen Compositor ===

To enable different effects (transparency, for example) {{Pkg|picom}} can be used.

After installation, add it to the ''Autostart'' section of the '''LXQt Session Settings'''.

The default configuration is available in {{Path|/etc/xdg/picom.conf.example}}. For modifications, it can be copied to {{Path|~/.config/picom/picom.conf}} or {{Path|~/.config/picom.conf}}.

Either modify the config file to your taste, or change the Autostart command line options. For example, <code>picom --vsync -r 12 --no-fading-openclose -b</code>.

=== Appearance Tweaking ===

==== Location of appearance-related configuration files ====

User-specific configuration is stored in {{Path|~/.config/lxqt/}}.

LXQt themes are [https://doc.qt.io/qt-6/stylesheet.html qss stylesheets]. They are located in {{Path|/usr/share/lxqt/themes/}} or {{Path|~/.local/share/lxqt/themes}}.

Qt Palette colors can be modified in lxqt-config-appearence > Widget Style > Qt Palette. Custom palettes are saved in {{Path|~/.local/share/lxqt/palettes/}}.

==== Additional QT Styles ====

Several packages provide additional QT Styles:

{{Cmd|# apk add {{Pkg|adwaita-qt}} {{Pkg|breeze}} {{Pkg|oxygen}}}}

They also provide additional cursors.

==== Consistant Theming ====

Adding the KEY=VAL <code>QT_QPA_PLATFORMTHEME=lxqt</code> to the Environment section of the Session Settings [https://github.com/lxqt/lxqt-qtplugin#configuration-usage is suggested by the LXQt developers]. Then every Qt5 program can load the theme plugin.

Another option, however, is to to install the package {{Pkg|qt5ct}} (from [[Repositories | Testing]]) and appending the line <code>QT_QPA_PLATFORMTHEME=qt5ct</code> to the environmental settings in the Environment section of the Session Settings will allow you to achieve a unified appearance between apps. Then, in the LXQt Appearance Configuration, under Widget Style, set Qt Style to <code>qt5ct-style</code>.

==== Additional Packages ====

When using themes found around the web, it is possible that they are dependant on different packages. Consider using {{Pkg|qt5-qtgraphicaleffects}}, {{Pkg|qt5-qtquickcontrols}}, and {{Pkg|qt5-qtquickcontrols2}}.

== Documentation ==

* {{Pkg|lxqt-config-doc}}
* {{Pkg|lxqt-openssh-askpass-doc}}
* {{Pkg|lxqt-panel-doc}}
* {{Pkg|lxqt-policykit-doc}}
* {{Pkg|lxqt-runner-doc}}
* {{Pkg|lxqt-session-doc}}
* {{Pkg|lxqt-sudo-doc}}

== Development files ==

* {{Pkg|lxqt-globalkeys-dev}}
* {{Pkg|lxqt-panel-dev}}

== Misc ==

* {{Pkg|lxqt-build-tools}}

== Help wanted ==

The following LXQt components are not yet packaged in Alpine Linux:
* lxqt_wallet
* lxqt-wayland-session (will be added to testing repo after LXQt 2.1 is packaged)

== See Also ==

* [[Installation#Post-Installation|Post Install]]
* [[Desktop environments and Window managers]]

= External Resources =

* [https://lxqt.github.io/ LXQt Homepage]
* [https://github.com/lxqt/lxqt LXQt on GitHub]
* [https://wiki.archlinux.org/title/LXQt LXQt entry on ArchWiki]
* [https://github.com/sddm/sddm SDDM Project on GitHub]

[[Category:Desktop]]
[[Category:Desktop Environments]]

LXQt

2024-11-01T22:29:36Z

Zcrayfish: Added note about help wanted for some LXQt packages that are not part of Alpine Linux, yet...

{{TOC right}}

[[File:LXQt Minimal Installation.png | thumb | LXQt 1.3.0 Basic Install with Papirus icons]]

'''[https://lxqt-project.org/ LXQt]''' is a lightweight QT based desktop environment. LXQt was originally a port of LXDE to QT (called LXDE-Qt), it was created due to LXDE maintainer Hong Jen Yee being dissatisfied with GTK 3. On 21 July 2013 the LXDE(-Qt) and [https://en.wikipedia.org/wiki/Razor-qt Razor-qt] projects merged creating LXQt.

== Prerequisites ==

* [[Installation|Install]] Alpine Linux
* [[Setting_up_a_new_user#Creating_a_new_user|Create a user account]] (optional but recommended)
* [[Repositories#Enabling_the_community_repository|Enable the Community repository]]
* [[Alpine_setup_scripts#setup-xorg-base|Install Xorg]] (running {{ic|setup-xorg-base}} is still a requirement even if using wayland)

== Basic LXQt Desktop Installation ==
Begin the installation by adding basic packages:
{{Cmd|# apk add {{Pkg|lxqt-desktop}} {{Pkg|lximage-qt}} {{Pkg|obconf-qt}} {{Pkg|pavucontrol-qt}}}}
If using Xorg, the following packages are also suggested: 
{{Cmd|# apk add {{Pkg|arandr}} {{Pkg|screengrab}} {{Pkg|sddm}}}}

{{Note|By default LXQt on Xorg uses [[Openbox]] as its window manager (it is a dependency of the {{Pkg|lxqt-desktop}} package). LXQt supports many different window managers and wayland compositors. Openbox has not been maintained for 9 years. Similar window managers are JWM and PeKWM. For additional Window Manager options See: [https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers Window Managers Configuration on the LXQt GitHub wiki]}}

Starting dbus (desktop bus) service:
{{Cmd|# rc-service dbus start}}

Enabling dbus to start on boot:
{{Cmd|# rc-update add dbus}}

If dbus is not running it leads to issues like missing icons and keyboard shortcuts.

{{:Include:Setup_Device_Manager}}

== Starting LXQt ==

=== With a display manager (DM) ===

If the package {{Pkg|sddm}} has been installed, SDDM may be started to log in graphically with your new user.
{{Cmd|# rc-service sddm start}}

After correct operation is verified, sddm can be enabled to start up during boot:
{{Cmd|# rc-update add sddm}}

=== From the command line ===

LXQt for X11 may be started with:
{{cmd|# startlxqt}}

== Localized keyboard layout ==

Preferences → LXQt Settings → Keyboard and Mouse → Keyboard Layout

== Allowing shut down and reboot ==

To enable users to shut down the machine or reboot, the packages {{Pkg|elogind}} and {{Pkg|polkit-elogind}} need to be installed.
{{Cmd|# apk add elogind polkit-elogind}}

A reboot is required to let it take effect.

== Auto-mounting USB drives ==

To enable automatic mounting of USB drives, install these packages:
{{Cmd|# apk add {{pkg|gvfs|arch=}} {{pkg|udisks2|arch=}}}}

Depending on what devices you intend to mount, some additional packages may be needed:
{{Cmd|{{pkg|ntfs-3g|arch=}} Stable, full-featured, read-write NTFS (driver)
{{pkg|gvfs-cdda|arch=}} CDDA support for gvfs
{{pkg|gvfs-afp|arch=}} AFP support for gvfs
{{pkg|gvfs-goa|arch=}} GNOME Online Accounts support for gvfs
{{pkg|gvfs-mtp|arch=}} MTP support for gvfs
{{pkg|gvfs-smb|arch=}} Windows fileshare support for gvfs
{{pkg|gvfs-lang|arch=}} Languages for package gvfs
{{pkg|gvfs-afc|arch=}} Apple mobile devices support for gvfs
{{pkg|gvfs-nfs|arch=}} NFS support for gvfs
{{pkg|gvfs-dev|arch=}} Backends for the gio framework in GLib (development files)
{{pkg|gvfs-archive|arch=}} Archiving support for gvfs
{{pkg|gvfs-dav|arch=}} WebDAV support for gvfs
{{pkg|gvfs-fuse|arch=}} FUSE support for gvfs
{{pkg|gvfs-gphoto2|arch=}} gphoto2 support for gvfs
{{pkg|gvfs-avahi|arch=}} DNS-SD support for gvfs}}

To list descriptions of all gvfs- packages:

{{cmd|# apk info -d {{pkg|gvfs-*|arch=x86_64}}}}

== Network browsing ==

For browsing of network shares within LXQt that works with file associations, you can install the gvfs packages for the network protocols you use.

For example, to browse in a SMB/cifs windows network:

{{Cmd|# apk add gvfs-smb}}

(Check: If the above may already be sufficient for gvfs to initiate the fuse kernel module. Else, try to identify if there are necessary steps in:)

{{Cmd|# apk add gvfs-fuse}}

The OpenRC script for fuse is in a separate package.

{{Cmd|# apk add {{pkg|fuse-openrc|arch=}}}}

Then the fuse service can be started manually.

{{Cmd|# rc-service fuse start}}

If it works, the fuse service can be added to start up automatically at boot time:

{{Cmd|# rc-update add fuse}}

== Enabling privilege escalation GUI ==

To enable the privilege escalation GUI for a doas/sudo user, you need to install {{Pkg|elogind}}, {{Pkg|polkit-elogind}}, and {{Pkg|sddm}}.

To have elogind run, either make them start automatically at system start:

{{Cmd|# rc-update add elogind}}

or start them manually for this time only:

{{Cmd|# rc-service elogind start }}

== Panel Widgets ==

If you cannot add the CPU and System Statistics widgets to the panel, make sure {{Pkg|libstatgrab}} and {{Pkg|libsysstat}} are installed.

== Troubleshooting ==

=== Missing Icons and Fonts ===

By default a Desktop Environments needs icons. {{Pkg|adwaita-icon-theme}} is a good start.
{{Cmd|# apk add adwaita-icon-theme}}

See [[Fonts]] for more information on fonts.

== Optional Configuration ==

=== Screen Compositor ===

To enable different effects (transparency, for example) {{Pkg|picom}} can be used.

After installation, add it to the ''Autostart'' section of the '''LXQt Session Settings'''.

The default configuration is available in {{Path|/etc/xdg/picom.conf.example}}. For modifications, it can be copied to {{Path|~/.config/picom/picom.conf}} or {{Path|~/.config/picom.conf}}.

Either modify the config file to your taste, or change the Autostart command line options. For example, <code>picom --vsync -r 12 --no-fading-openclose -b</code>.

=== Appearance Tweaking ===

==== Location of appearance-related configuration files ====

User-specific configuration is stored in {{Path|~/.config/lxqt/}}.

LXQt themes are [https://doc.qt.io/qt-6/stylesheet.html qss stylesheets]. They are located in {{Path|/usr/share/lxqt/themes/}} or {{Path|~/.local/share/lxqt/themes}}.

Qt Palette colors can be modified in lxqt-config-appearence > Widget Style > Qt Palette. Custom palettes are saved in {{Path|~/.local/share/lxqt/palettes/}}.

==== Additional QT Styles ====

Several packages provide additional QT Styles:

{{Cmd|# apk add {{Pkg|adwaita-qt}} {{Pkg|breeze}} {{Pkg|oxygen}}}}

They also provide additional cursors.

==== Consistant Theming ====

Adding the KEY=VAL <code>QT_QPA_PLATFORMTHEME=lxqt</code> to the Environment section of the Session Settings [https://github.com/lxqt/lxqt-qtplugin#configuration-usage is suggested by the LXQt developers]. Then every Qt5 program can load the theme plugin.

Another option, however, is to to install the package {{Pkg|qt5ct}} (from [[Repositories | Testing]]) and appending the line <code>QT_QPA_PLATFORMTHEME=qt5ct</code> to the environmental settings in the Environment section of the Session Settings will allow you to achieve a unified appearance between apps. Then, in the LXQt Appearance Configuration, under Widget Style, set Qt Style to <code>qt5ct-style</code>.

==== Additional Packages ====

When using themes found around the web, it is possible that they are dependant on different packages. Consider using {{Pkg|qt5-qtgraphicaleffects}}, {{Pkg|qt5-qtquickcontrols}}, and {{Pkg|qt5-qtquickcontrols2}}.

== Documentation ==

* {{Pkg|lxqt-config-doc}}
* {{Pkg|lxqt-openssh-askpass-doc}}
* {{Pkg|lxqt-panel-doc}}
* {{Pkg|lxqt-policykit-doc}}
* {{Pkg|lxqt-runner-doc}}
* {{Pkg|lxqt-session-doc}}
* {{Pkg|lxqt-sudo-doc}}

== Development files ==

* {{Pkg|lxqt-globalkeys-dev}}
* {{Pkg|lxqt-panel-dev}}

== Misc ==

* {{Pkg|lxqt-build-tools}}

== Help wanted ==

The following LXQt components are not yet packaged in Alpine Linux:
* lxqt_wallet
* lxqt-wayland-session (awaiting release)

== See Also ==

* [[Installation#Post-Installation|Post Install]]
* [[Desktop environments and Window managers]]

= External Resources =

* [https://lxqt.github.io/ LXQt Homepage]
* [https://github.com/lxqt/lxqt LXQt on GitHub]
* [https://wiki.archlinux.org/title/LXQt LXQt entry on ArchWiki]
* [https://github.com/sddm/sddm SDDM Project on GitHub]

[[Category:Desktop]]
[[Category:Desktop Environments]]

Software management

2024-10-30T14:11:48Z

Zcrayfish: Undo revision 27139 by Manoel (talk) remove self-promotion because people are complaining.

If you want to run [https://www.gnu.org/software/libc/ glibc] programs in Alpine Linux, there are a few ways of doing so. You can install the [https://git.adelielinux.org/adelie/gcompat gcompat] compatibility layer, you can install glibc alongside [https://musl.libc.org/ musl] (manually, as it isn't packaged), or you could do it the easy way and use either Flatpak (the easiest), containers or a chroot. 

Because there are different use cases, this is just a slight overview about what's possible and what's sensible. 

= Your options =

== gcompat ==

gcompat is the go-to compatibility layer for Alpine users.

{{cmd|apk add {{pkg|gcompat}}}}

After that you run your binaries as normal.

== Flatpak ==

Flatpak is by far the easiest method of running any graphical glibc program on Alpine.
Firstly install it.

{{cmd|apk add {{pkg|flatpak}}}}

Then you can run any Flatpak application:

{{cmd|flatpak run <flatpak name>}}

It is recommended to enable [https://flathub.org Flathub] using its instructions [https://flatpak.org/setup/Alpine/ here], as most glibc programs you might need will be packaged there.

You can then install applications from it, for example:

{{cmd|flatpak install com.valvesoftware.Steam}}

== Chroot ==

An option that's easier to generalize to other glibc applications is installing a glibc-based distribution into a chroot. You can then either chroot into it, or use a symlink and some configuration to make its glibc (and associated libraries) usable from Alpine.

After setting up a chroot using any of the methods described below, the loader can be set up in Alpine like so (these instructions are for a Debian chroot in /var/chroots/debian, on x86_64, but can be adapted to other systems by using the appropriate paths):

{{cmd|mkdir -p /lib64
ln -s /var/chroots/debian/lib/x86_64-linux-gnu/ld-2.33.so /lib64
printf '/var/chroots/debian/lib/x86_64-linux-gnu\n/var/chroots/debian/usr/lib/x86_64-linux-gnu\n' > /etc/ld.so.conf
/var/chroots/debian/sbin/ldconfig}}

=== Gentoo Linux ===

Select a stage3 from [https://www.gentoo.org/downloads/ here] and portage latest from [https://www.gentoo.org/downloads/mirrors/ here] at gentoo/snapshots/portage-latest.tar.xz.

First,

{{cmd|doas apk add {{pkg|xz}}}}

Enter the chroot:
{{cmd|mkdir ~/chroot
cd ~/chroot
tar -xvf stage3-*.tar.xz
tar -xvf portage-latest.tar.xz
mv portage usr
doas mount --bind /dev dev
doas mount --bind /sys sys
doas mount -t proc proc proc
cp /etc/resolv.conf etc
doas chroot . /bin/bash}}

And voilà, you have your working Gentoo chroot! 

You can now take a look at [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo's Handbook] to find out how you can configure and install your system, or simply extract/copy the program you need to run in your chroot enviroment and execute it.

Here is a wrapper script that is similar to <code>arch-chroot</code> when you frequently reuse this chroot:

Also, create an account with the same user name as host current user to the chroot or make changes to the userspec option to chroot line.

{{Cat|gentoo-chroot.sh|<nowiki>!/bin/bash
CHROOT_PATH="/home/$USER/chroot"
cd $CHROOT_PATH
mount | grep $CHROOT_PATH/dev || doas mount --bind /dev dev
mount | grep $CHROOT_PATH/sys || doas mount --bind /sys sys
mount | grep $CHROOT_PATH/proc || doas mount -t proc proc proc
cp /etc/resolv.conf etc
doas chroot --userspec=$USER:users . /bin/bash
echo "You must manually unmount $CHROOT_PATH/dev, $CHROOT_PATH/sys, $CHROOT_PATH/proc."
</nowiki>
}}

Do at <code>chmod +x gentoo-chroot.sh</code> to get it to work.

=== Arch Linux ===

Either use '''pacstrap''' (included with the arch-install-scripts package) or an Arch bootstrap image:

{{cmd|doas apk add {{pkg|arch-install-scripts}}
mkdir ~/chroot && cd ~/chroot
curl -O https://mirrors.edge.kernel.org/archlinux/iso/latest/archlinux-bootstrap-x86_64.tar.gz
doas tar xzf archlinux-bootstrap-x86_64.tar.gz && rm archlinux-bootstrap-x86_64.tar.gz
doas sed -i '/evowise/s/^#//' root.x86_64/etc/pacman.d/mirrorlist
doas sed -i '/CheckSpace/s/^/#/' root.x86_64/etc/pacman.conf
doas arch-chroot root.x86_64
[chroot]# pacman-key --init
[chroot]# pacman-key --populate archlinux}}

Once that is done, update the system and install the desired package(s) (denoted by ''"foo"'' in this example):

{{cmd|[chroot]# pacman -Syu ''foo''}}

=== Debian ===
{{todo|gresec referencs need to be cleanly removed from this section.}}
Use the provided debootstrap package to create the Debian chroot. <code>--arch</code> is optional, depending of your needs.

On the '''linux-grsec''' kernel, you will need to relax chroot limitations:

sudo apk add debootstrap
for i in /proc/sys/kernel/grsecurity/chroot_*; do echo 0 | sudo tee $i; done
mkdir ~/chroot
sudo debootstrap --arch=i386 wheezy ~/chroot https://deb.debian.org/debian/
for i in /proc/sys/kernel/grsecurity/chroot_*; do echo 1 | sudo tee $i; done
sudo chroot ~/chroot /bin/bash

You can now use <code>apt-get</code> to install needed packages.

== Containers ==

It's also possible to use Docker or Podman containers with a helper like Distrobox. This allows using graphical programs easily and doesn't require root privileges once set up.

{{cmd|# apk add {{pkg|distrobox}}}}

=== Distrobox + Podman ===

{{cmd|# apk add {{pkg|podman}}}}

Then set up rootless Podman, following [[Podman|these steps]].
You'll need to mount your root as shared for Distrobox to function.

Fill in {{path|/etc/local.d/mount-rshared.start}} like so:

{{cmd|#!/bin/sh
mount --make-rshared /}}

Mark it as executable.

{{cmd|# chmod +x /etc/local.d/mount-rshared.start}}

Then autostart its service.

{{cmd|# rc-update add local default
# rc-service local start}}

Finally you can create a container using your chosen image.

{{cmd|$ distrobox create --image debian --name debian
$ distrobox enter debian}}

It may also be necessary to allow X authorization for GUI programs to work.

{{cmd|$ xhost +si:localuser:$USER}}

== Chroot + Bubblewrap ==

It's also possible to use a Debian system chroot with Bubblewrap. This allows running programs without root.

{{cmd|# apk add bubblewrap debootstrap
# mkdir -p /var/chroots/debian
# debootstrap --arch amd64 stable /var/chroots/debian/ https://deb.debian.org/debian}}

Finally we can make an alias for bwrap.

{{cmd|$ alias glibc{{=}}"LANG{{=}}en_US.UTF-8 bwrap --bind /var/chroots/debian / --dev-bind /dev /dev --proc /proc --bind /sys /sys --bind /run /run --bind /home /home --ro-bind /etc/resolv.conf /etc/resolv.conf --ro-bind /etc/passwd /etc/passwd --ro-bind /etc/group /etc/group"}}

To run programs that use X11/Xorg you can use:
{{cmd|$ alias glibcX11{{=}}"LANG{{=}}en_US.UTF-8 bwrap --bind /var/chroots/debian / --dev-bind /dev /dev --proc /proc --bind /sys /sys --bind /run /run --bind /home /home --ro-bind /etc/resolv.conf /etc/resolv.conf --ro-bind /etc/passwd /etc/passwd --ro-bind /etc/group /etc/group --bind /tmp/.X11-unix/X0 /tmp/.X11-unix/X0 --setenv DISPLAY :0"}}

In this case you might need to use xhost to allow local connections, e.g.:
{{cmd|# xhost + local:}}

Now we can invoke glibc-built binaries like so:
{{cmd|$ glibc ./binary}} or {{cmd|$ glibcX11 ./binary}}

For updating the Chroot or installing dependencies we can mount it and then login as root:
{{cmd|# mount --bind /dev /var/chroots/debian/dev
# mount --bind /proc /var/chroots/debian/proc
# chroot /var/chroots/debian /bin/bash
# apt update && apt upgrade}}

After installing what you might want to umount the binds for dev and proc to avoid issues.
{{cmd|# umount /var/chroots/debian/dev}}
{{cmd|# umount /var/chroots/debian/proc}}

[[Category:Development]]
[[Category:Installation]]

Apk spec

2024-10-14T22:34:37Z

Zcrayfish: Fix a wikilink... Use path template in a few places, as appropriate.

{{Draft}}

For end-user facing documentation about apk, check out the [[Alpine Package Keeper]] page.

This page is an attempt to document the internal data structures of the apk package manager. The canonical implementation of the apk format is [https://gitlab.alpinelinux.org/alpine/apk-tools apk-tools] and much of this information is gleaned from reading the source code.

There are three generations of the APK data formats. Version 1 is deprecated and no longer used, version 2 is currently the main version in use by apk-tools, and version 3 is under development. This page mostly describes the data formats used in version 2.

= Background =
== Tar Segments ==
Tar segments are a set of tar records. Normal tar files contain two null records at the end of the tar file to signal the end of the tarball. Tar segments are lacking these two records and can thus be concatenated before other tar files and will behave as one continuous tar file. The APK v2 package format makes use of both tar segments and tarballs.

Tar segments can be compressed using gzip compression. Gzip is a stream-based file format and multiple streams can be concatenated together. Most tooling will treat multiple gzip streams within a file as if it were a single stream. APK v2 files are aware of gzip streams and use them for file segmentation.

= Package Format V2 =
== Binary Format ==
APK v2 packages contain two tar segments followed by a tarball each in their own gzip stream (3 streams total). These streams contain the package signature, control data, and package data. The package data is a tarball of the files contained in a package laid out in a way that allows it to be unpacked at the filesystem root such that all files are placed in the correct location on the system. The control tar segment contains the package metadata along with any install scripts. The signature tar segment contains a single file that is a binary signature over the control segment.

The signature file is a DER encoded PKCS1v15 RSA signature of the SHA1 hash of the control tar segment gzip stream. The filename has the format <tt>.SIGN.RSA.<key_name>.rsa.pub</tt> (for example <tt>.SIGN.RSA.alpine-devel@lists.alpinelinux.org-5261cecb.rsa.pub</tt>). This file is placed inside of a tar record with permissions 0644, uid 0, and gid 0. This tar record (lacking end-of-tar records) is gzip compressed, forming a signature tar segment, and is concatenated onto the front of the combined control and data segments. [https://gitlab.alpinelinux.org/alpine/abuild/-/blob/master/abuild-sign.in abuild-sign] is responsible for generating these signature segments.

Apk will verify a signature by looking in {{path|/etc/apk/keys}} for a file called ''exactly'' {{path|<key_name>.rsa.pub}} in {{path|/etc/apk/keys}}. If no such file is found, verification fails.

The control segment contains the package metadata in a {{path|.PKGINFO}} file as well as all of the scripts (if any) that are used by apk during installation and removal of the package. For historical reasons all files in the control tar segment are prefixed with a dot (<tt>.</tt>). The control segment is constructed by placing each file for the package into a tar record, concatenating those tar records, gzipping the tar records, and concatenating them onto the front of the data tarball. The SHA1 hash of this gzip stream is used as the checksum <tt>C:</tt> field in the APKINDEX file.

The data tarball is a standard gzipped tarball with extra PAX headers that contain the SHA1 hash of each file in the tar header for that file. The hash is contained in a header called {{path|APK-TOOLS.checksum.SHA1}}. Unlike the other tar streams this tarball does contain the two end-of-tar null records. It is always the final segment of an APK package. Hashes are added with the [https://gitlab.alpinelinux.org/alpine/abuild/-/blob/master/abuild-tar.c abuild-tar] tool.

== PKGINFO Format ==
The PKGINFO file contains the package metadata. This is a plain-text file similar to INI files. Lines that begin with <tt>#</tt> are comments and ignored. Unlike INI files the parsing format of this file is very strict. Each key-value pair must be separated by exactly one space, one equal sign, and one more space (<tt> = </tt>). Keys may be repeated in this file and should be treated as a list of values if repetitions are found.

The specification for what fields are valid in PKGINFO is largely defined by [https://gitlab.alpinelinux.org/alpine/abuild/-/blob/master/abuild.in abuild]. As of July 2022 the following fields are supported:

* <tt>pkgname</tt> - package name
* <tt>pkgver</tt> - package version
* <tt>pkgdesc</tt> - package description
* <tt>url</tt> - package url
* <tt>builddate</tt> - unix timestamp of the package build date/time
* <tt>packager</tt> - name (and typically email) of person who built the package
* <tt>size</tt> - the installed-size of the package
* <tt>arch</tt> - the architecture of the package (ex: x86_64)
* <tt>origin</tt> - the origin name of the package
* <tt>commit</tt> - the commit hash from which the package was built
* <tt>maintainer</tt> - name (and typically email) of the package maintainer
* <tt>replaces_priority</tt> - replaces priority field for package (integer)
* <tt>provider_priority</tt> - provider priority for the package (integer)
* <tt>license</tt> - license string for the package
* <tt>depend</tt> - dependencies for the package (repeated)
* <tt>replaces</tt> - packages this package replaces (repeated)
* <tt>provides</tt> - what this package provides (repeated)
* <tt>triggers</tt> - what packages this package triggers on (repeated)
* <tt>install_if</tt> - install this package if these packages are present (repeated)
* <tt>datahash</tt> - hex-encoded sha256 checksum of the data tarball

== Example of PKGINFO ==
<pre>
# Generated by abuild 3.9.0-r2
# using fakeroot version 1.25.3
# Wed Jul 6 19:09:49 UTC 2022
pkgname = busybox
pkgver = 1.35.0-r18
pkgdesc = Size optimized toolbox of many common UNIX utilities
url = https://busybox.net/
builddate = 1657134589
packager = Buildozer <alpine-devel@lists.alpinelinux.org>
size = 958464
arch = x86_64
origin = busybox
commit = 332d2fff53cd4537d415e15e55e8ceb6fe6eaedb
maintainer = Sören Tempel <soeren+alpine@soeren-tempel.net>
provider_priority = 100
license = GPL-2.0-only
replaces = busybox-initscripts
provides = /bin/sh
triggers = /bin /usr/bin /sbin /usr/sbin /lib/modules/*
# automatically detected:
provides = cmd:busybox=1.35.0-r18
provides = cmd:sh=1.35.0-r18
depend = so:libc.musl-x86_64.so.1
datahash = 7d3351ac6c3ebaf18182efb5390061f50d077ce5ade60a15909d91278f70ada7
</pre>

== Package Building Example ==
This is a set of commands to partially build a package. '''DO NOT DO THIS''', it's mainly an example to see how this all fits together. Use the official build tools to build packages.

<pre>
tar -c .PKGNIFO .pre-install | abuild-tar --cut | gzip -9 > $controldir/control.tar.gz
cd $pkgdir; tar -c * | abuild-tar --hash | gzip -9 > $controldir/data.tar.gz
cat $controldir/control.tar.gz $controldir/data.tar.gz > mypackage-1.0-r0.apk
</pre>

= Index Format V2 =
== Binary Format ==
The index is served as [https://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz APKINDEX.tar.gz] and is downloaded by apk to power the package database. The index is signed similarly to packages. The main difference between the index and packages is that the index file contains only two segments.

The signature segment is identical to a package segment and is concatenated, in its own gzip stream, to the beginning of the APKINDEX tarball.

The APKINDEX tarball contains two files: a DESCRIPTION file and an APKINDEX file. Each of these files is in their own tar record and the final record is followed by the standard end-of-tar null records. The DESCRIPTION file is a simple text file containing a description of the index (ex: <tt>community v20210212-7170-g5c9853dc69</tt>). The APKINDEX file is a text file containing records for each package in the repository in a text-based format. Each record is separated by a newline.

== APKINDEX Format ==
The APKINDEX file contains a set of records extracted from the PKGINFO file of each package in the repository. Each line is prefixed with a letter, colon, and is followed by the value of the field. Lines are newline (<tt>\n</tt>) terminated and there is one blank line between records for a package.

The <tt>apk_pkg_write_index_entry</tt> function of [https://gitlab.alpinelinux.org/alpine/apk-tools/-/blob/ff7c8f6ee9dfa2add57b88dc271f6711030e72a0/src/package.c#L905 package.c] defines the currently accepted fields. As of July 2022, these are:

* <tt>C:</tt> - file checksum, see below
* <tt>P:</tt> - package name (corresponds to <tt>pkgname</tt> in PKGINFO)
* <tt>V:</tt> - package version (corresponds to <tt>pkgver</tt> in PKGINFO)
* <tt>A:</tt> - architecture (corresponds to <tt>arch</tt> in PKGINFO), optional
* <tt>S:</tt> - size of entire package, integer
* <tt>I:</tt> - installed size, integer (corresponds to <tt>size</tt> in PKGINFO)
* <tt>T:</tt> - description (corresponds to <tt>pkgdesc</tt> in PKGINFO)
* <tt>U:</tt> - url (corresponds to <tt>url</tt> in PKGINFO)
* <tt>L:</tt> - license (corresponds to <tt>license</tt> in PKGINFO)
* <tt>o:</tt> - origin (corresponds to <tt>origin</tt> in PKGINFO), optional
* <tt>m:</tt> - maintainer (corresponds to <tt>maintainer</tt> in PKGINFO), optional
* <tt>t:</tt> - build time (corresponds to <tt>builddate</tt> in PKGINFO), optional
* <tt>c:</tt> - commit (corresponds to <tt>commit</tt> in PKGINFO), optional
* <tt>k:</tt> - provider priority, integer (corresponds to <tt>provider_priority</tt> in PKGINFO), optional
* <tt>D:</tt> - dependencies (corresponds to <tt>depend</tt> in PKGINFO, concatenated by spaces into a single line)
* <tt>p:</tt> - provides (corresponds to <tt>provides</tt> in PKGINFO, concatenated by spaces into a single line)
* <tt>i:</tt> - install if (corresponds to <tt>install_if</tt> in PKGINFO, concatenated by spaces into a single line)

== Package Checksum Field ==
The package checksum field is the SHA1 hash of the second gzip stream (control stream) in the package. The binary hash digest is base64 encoded. This is prefixed with <tt>Q1</tt> to differentiate it from the MD5 hashes used in older index formats. It is not possible to compute this checksum with standard command line tools but the apk-tools can compute it in their <tt>index</tt> operation.

== Example APKINDEX Record ==
<pre>
C:Q1P4IRU/u5yB4CSnUEBRD1WWwajrY=
P:jool-tools
V:4.1.5-r0
A:x86_64
S:140605
I:434176
T:Userspace control tools for SIIT / NAT64 Jool
U:https://www.jool.mx
L:GPL-2.0-only
o:jool-tools
m:Jakub Jirutka <jakub@jirutka.cz>
t:1620480809
c:771b3b0910ea9c7736db6ca4ff5c37ca9cf9af0d
D:so:libc.musl-x86_64.so.1 so:libnl-3.so.200 so:libnl-genl-3.so.200
p:cmd:jool=4.1.5-r0 cmd:jool_siit=4.1.5-r0 cmd:joold=4.1.5-r0
</pre>

= Installed Database V2 =
The installed database is used by apk to track which packages are installed and what modifications those packages have made to the system. This file is located at {{path|/lib/apk/db/installed}}. The installed file is a plaintext file of the same format as APKINDEX (contained in APKINDEX.tar.gz). It is neither compressed nor signed. Each record in the installed file starts with a package index record with the same fields as the APKINDEX file. The installed file adds some additional fields that are defined in [https://gitlab.alpinelinux.org/alpine/apk-tools/-/blob/ff7c8f6ee9dfa2add57b88dc271f6711030e72a0/src/database.c#L937 database.c]. As of July 2022 these additional fields are:

* <tt>r:</tt> - packages which this package replaces, space separated list
* <tt>q:</tt> - replaces priority, integer, optional
* <tt>s:</tt> - repository tag, optional, this will be set if the package is tagged to a repository in the world file (ex: linux@testing)
* <tt>f:</tt> - indicates broken items, space separated (f=files, s=scripts, x=xattrs, S=file hashes)

The following fields are repeated and in groups consist of a set of mutations made to the system to install the package.

ACL lines are specified as uid, colon, gid, colon, and mode.

* <tt>F:</tt> - directory name that was created by package, repeated
* <tt>M:</tt> - directory ACL, only if different than the default of 0:0:0755
* <tt>R:</tt> - file name, relative to preceding directory name
* <tt>a:</tt> - file ACL
* <tt>Z:</tt> - file checksum, if the checksum in the package is not none, a <tt>Q1</tt> prefix indicates this will be a SHA1 hash in base64 format

[[Category:Package Manager]] [[Category:Development]]

Apcupsd

2024-10-14T22:29:28Z

Zcrayfish: /* Configuring and Testing Email Alerts */ Use path and cmd templates as appropriate.

== Using apcupsd to Monitor a USB-Attached APC UPS ==

This wiki page shows how to install and configure the apcupsd package to monitor and report the statistics for an APC branded USB attached Uninterruptible Power Supply (UPS). The UPS model used in the examples is an APC SmartUPS 1000, but any APC or compatible model should work.

The end goal is to make the UPS status available over the network so it can be monitored and used to trigger actions in a home automation system like [https://www.home-assistant.io/ Home Assistant].

=== Installing and Configuring apcupsd ===

The first step is to add the alpine package for apcupsd. After that, we'll rename the default configuration file and replace them with the parameters needed for our example USB attached APC Smart-UPS.

Installation is by an APK package:

{{cmd|# apk add {{pkg|apcupsd}}}}

There is one main configuration file called ''/etc/apcupsd/apcupsd.conf'' that has all the tunable parameters along with many comments. We'll keep the original as a reference and then edit the parameters to suit.

{{cmd|<nowiki># mv /etc/apcupsd/apcupsd.conf /etc/apcupsd/apcupsd.conf~
# grep -v '^\s*$\|^\s*\#' /etc/apcupsd/apcupsd.conf~ >/etc/apcupsd/apcupsd.conf</nowiki>}}

Now, edit the parameters in {{path|/etc/apcupsd/apcupsd.conf}} using the backup copy of the original file as a reference for comments. Some of the important parameters are listed below in order of appearance.

* UPSNAME - This is to identify your UPS. Exact format is not important, but keep it short and don't use spaces.
* UPSCABLE - For a USB attached UPS, use the value ''usb''
* USBTYPE - Similar to USBCABLE, use ''usb''
* DEVICE - For a USB attached UPS, the parameter is not needed. Comment this line by using a # at the beginning.

These four changes are enough to get started. Everything else can be left as default. Read the comments in the original {{path|apcupsd.conf~}} file to find out what the other parameters do and if you want to use them.

{{Note|The comments in the config file say UPSNAME should be eight characters or less. This appears to be a limitation of using the parameter for storing the name in the UPS's EPROM. If you're not planning to update EPROM, longer names do not appear to cause problems. See the config section after ''Configuration statements used in updating the UPS EPROM'' for more detail. }}

== Starting apcupsd ==

The apcupsd package installs a service that allows you to control apcupsd using the standard tools. The following example shows how to start it and ensure it starts each time the system boots.

<nowiki>
alpine:/# rc-service apcupsd start
* Starting APC UPS daemon ...

alpine:/# rc-update add apcupsd
* service apcupsd added to runlevel default</nowiki>

== Checking the Configuration ==

The '''apcaccess''' command will communicate with the UPS via the apcupsd daemon's network port and report back what it finds. This is a good way to test your connection and configuration.

A successful test will look similar to what's shown below.
<nowiki>
alpine:/# apcaccess
APC : 001,043,1022
DATE : 2024-10-12 15:31:10 +0000
HOSTNAME : alpine.home
VERSION : 3.14.14 (31 May 2016) unknown
UPSNAME : SmartUPS_1000
CABLE : USB Cable
DRIVER : USB UPS Driver
UPSMODE : Stand Alone</nowiki>
...

The actual list of reported parameters is much longer, but the first few lines show the ones that have been customized in the configuration thus far. If you see the message ''Error contacting apcupsd @ localhost:3551: Connection refused'', check to ensure the apcupsd service is running.

== Configuring and Testing Email Alerts ==

{{Note|In order to receive notifications, you must have mail delivery setup and working on your Alpine host. In addition, you should have an alias that sends email intended for root to a regular user. See the Alpine HOWTO [[Small-Time_Email_with_Exim_and_Dovecot]] for help with that.}}

apcupsd will send alerts for important events using shell scripts in the {{path|/etc/apcupsd}} directory. These scripts and their alert functions are listed below.

* changeme - sends an alert when batteries have reached the end of their useful life
* commfailure - apcupsd cannot communicate with the UPS
* commok - communication with the UPS has been restored after a failure
* offbattery - the UPS is back to running on mains power after running on battery
* onbattery - the ups has switched to battery power

All of the scripts have a similar setup and rely on two environment variables, SYSADMIN and APCUPSD_MAIL, to deliver email alerts. To test the alerts, temporarily export these two variables and run one of the scripts from the command-line. The example below shows how to send a test alert for battery change.

{{cmd|<nowiki># export SYSADMIN=root
# export APCUPSD_MAIL=mail
# sh /etc/apcupsd/changeme</nowiki>}}

If all goes well, you should receive an email telling you the UPS battery needs changing NOW. If you find you need to use different values for SYSADMIN or APCUPSD_MAIL, be sure to make those changes in {{path|/etc/apcupsd/apccontrol}}. The exported variables used in the test are temporary and will lost after you log out.

== Next Steps ==

Further configuration can be done to initiate automatic shutdown using the parameters in apcupsd.conf (see the original commented file apcupsd.conf~ for details.) You may also monitor the UPS via home automation using Home Assistant and the [https://www.home-assistant.io/integrations/apcupsd/ APC UPS Daemon integration].

Apcupsd

2024-10-14T22:26:40Z

Zcrayfish: /* Installing and Configuring apcupsd */ Use cmd, path, and pkg templates, ass appropriate.

== Using apcupsd to Monitor a USB-Attached APC UPS ==

This wiki page shows how to install and configure the apcupsd package to monitor and report the statistics for an APC branded USB attached Uninterruptible Power Supply (UPS). The UPS model used in the examples is an APC SmartUPS 1000, but any APC or compatible model should work.

The end goal is to make the UPS status available over the network so it can be monitored and used to trigger actions in a home automation system like [https://www.home-assistant.io/ Home Assistant].

=== Installing and Configuring apcupsd ===

The first step is to add the alpine package for apcupsd. After that, we'll rename the default configuration file and replace them with the parameters needed for our example USB attached APC Smart-UPS.

Installation is by an APK package:

{{cmd|# apk add {{pkg|apcupsd}}}}

There is one main configuration file called ''/etc/apcupsd/apcupsd.conf'' that has all the tunable parameters along with many comments. We'll keep the original as a reference and then edit the parameters to suit.

{{cmd|<nowiki># mv /etc/apcupsd/apcupsd.conf /etc/apcupsd/apcupsd.conf~
# grep -v '^\s*$\|^\s*\#' /etc/apcupsd/apcupsd.conf~ >/etc/apcupsd/apcupsd.conf</nowiki>}}

Now, edit the parameters in {{path|/etc/apcupsd/apcupsd.conf}} using the backup copy of the original file as a reference for comments. Some of the important parameters are listed below in order of appearance.

* UPSNAME - This is to identify your UPS. Exact format is not important, but keep it short and don't use spaces.
* UPSCABLE - For a USB attached UPS, use the value ''usb''
* USBTYPE - Similar to USBCABLE, use ''usb''
* DEVICE - For a USB attached UPS, the parameter is not needed. Comment this line by using a # at the beginning.

These four changes are enough to get started. Everything else can be left as default. Read the comments in the original {{path|apcupsd.conf~}} file to find out what the other parameters do and if you want to use them.

{{Note|The comments in the config file say UPSNAME should be eight characters or less. This appears to be a limitation of using the parameter for storing the name in the UPS's EPROM. If you're not planning to update EPROM, longer names do not appear to cause problems. See the config section after ''Configuration statements used in updating the UPS EPROM'' for more detail. }}

== Starting apcupsd ==

The apcupsd package installs a service that allows you to control apcupsd using the standard tools. The following example shows how to start it and ensure it starts each time the system boots.

<nowiki>
alpine:/# rc-service apcupsd start
* Starting APC UPS daemon ...

alpine:/# rc-update add apcupsd
* service apcupsd added to runlevel default</nowiki>

== Checking the Configuration ==

The '''apcaccess''' command will communicate with the UPS via the apcupsd daemon's network port and report back what it finds. This is a good way to test your connection and configuration.

A successful test will look similar to what's shown below.
<nowiki>
alpine:/# apcaccess
APC : 001,043,1022
DATE : 2024-10-12 15:31:10 +0000
HOSTNAME : alpine.home
VERSION : 3.14.14 (31 May 2016) unknown
UPSNAME : SmartUPS_1000
CABLE : USB Cable
DRIVER : USB UPS Driver
UPSMODE : Stand Alone</nowiki>
...

The actual list of reported parameters is much longer, but the first few lines show the ones that have been customized in the configuration thus far. If you see the message ''Error contacting apcupsd @ localhost:3551: Connection refused'', check to ensure the apcupsd service is running.

== Configuring and Testing Email Alerts ==

{{Note|In order to receive notifications, you must have mail delivery setup and working on your Alpine host. In addition, you should have an alias that sends email intended for root to a regular user. See the Alpine HOWTO [[Small-Time_Email_with_Exim_and_Dovecot]] for help with that.}}

apcupsd will send alerts for important events using shell scripts in the /etc/apcupsd directory. These scripts and their alert functions are listed below.

* changeme - sends an alert when batteries have reached the end of their useful life
* commfailure - apcupsd cannot communicate with the UPS
* commok - communication with the UPS has been restored after a failure
* offbattery - the UPS is back to running on mains power after running on battery
* onbattery - the ups has switched to battery power

All of the scripts have a similar setup and rely on two environment variables, SYSADMIN and APCUPSD_MAIL, to deliver email alerts. To test the alerts, temporarily export these two variables and run one of the scripts from the command-line. The example below shows how to send a test alert for battery change.

alpine:/# export SYSADMIN=root
alpine:/# export APCUPSD_MAIL=mail
alpine:/# sh /etc/apcupsd/changeme</nowiki>

If all goes well, you should receive an email telling you the UPS battery needs changing NOW. If you find you need to use different values for SYSADMIN or APCUPSD_MAIL, be sure to make those changes in ''/etc/apcupsd/apccontrol''. The exported variables used in the test are temporary and will lost after you log out.

== Next Steps ==

Further configuration can be done to initiate automatic shutdown using the parameters in apcupsd.conf (see the original commented file apcupsd.conf~ for details.) You may also monitor the UPS via home automation using Home Assistant and the [https://www.home-assistant.io/integrations/apcupsd/ APC UPS Daemon integration].

Setting up a LLDAP server

2024-10-04T02:08:14Z

Zcrayfish: /* Configure */ Use path template; typo fix.

= General =
LLDAP is a small LDAP server designed for directory services without the overhead of a full blown OpenLDAP server. LLDAP server is designed for easy management using a simple web gui. It lacks some of the features found in other directory servers, because its specificly designed for easy use.

= Install =
Installing LLDAP is fairly simple and can be done in less then 5 minutes. start by logging in as root:
{{Cmd|doas su -}}
Then we make sure the system is up to date and install wget:
{{Cmd|apk update && apk upgrade && apk add wget}}
Then we make the directory for LLDAP to live in and install the software:
{{Cmd|mkdir /opt/lldap && cd /opt/lldap}}
{{Cmd|wget https://github.com/lldap/lldap/releases/download/v0.5.0/amd64-lldap.tar.gz && tar xzf amd64-lldap.tar.gz && mv amd64-lldap/* . && rm -rf amd64-lldap}}

= Configure =
To configure LLDAP we have to create a config file, and an rc file to start it automaticly upon boot. First we generate 2 random strings to use in the configuration as jwt_secret and key_seed:
{{Cmd| openssl rand -base64 15 && openssl rand -base64 15}}

Then we paste the following configuration into {{path|/opt/lldap/lldap_config.toml}} and replace the jwt_secret and key_seed with the random generated value's:
{{Cmd|<nowiki>
ldap_port = 3890
http_port = 17170
http_url = "https://domain.tld"
jwt_secret = "very-long-string"
ldap_base_dn = "dc=domain,dc=tld"
ldap_user_dn = "admin"
ldap_user_email = "admin@domain.tld"
ldap_user_pass = "very-strong-password"
database_url = "sqlite:///opt/lldap/users.db?mode=rwc"
key_seed = "random-string-again"

[smtp_options]
#enable_password_reset=true
#server="smtp.gmail.com"
#port=587
#smtp_encryption = "TLS"
#user="sender@gmail.com"
#password="password"
#from="LLDAP Admin <sender@gmail.com>"
#reply_to="Do not reply <noreply@localhost>"

[ldaps_options]
#enabled=true
#port=6360
## Certificate file.
#cert_file="/data/cert.pem"
## Certificate key file.
#key_file="/data/key.pem"
</nowiki>}}

Replace domain.tld with your chose domain name.
Next we need to create an openrc file so we can automatically start lldap:

{{Cmd|<nowiki>cat <<EOF > /etc/init.d/lldap
#!/sbin/openrc-run

name=lldap
command="/opt/lldap/lldap"
command_args="run"
command_background="yes"
pidfile="/run/lldap.pid"

depend() {
need net
}

start_pre()
{
cd /opt/lldap
}
EOF
</nowiki>}}

This is not an extensive file, but it gets you running and ensures lldap starts and works correctly.
Now we need to add it to the default runlevel and start the service
{{Cmd|chmod +x /etc/init.d/lldap && rc-update add lldap}}

= Use =
To use LLDAP we can browse to http://<ip>:17170 and login with the credentials we specified in the config file.

This is a basic configuration. You can now connect other services that support ldap logins to LLDAP.

= Troubleshooting =
* Some troubleshooting information

= Resources =
* https://github.com/lldap/lldap

[[Category:Server]]

Release Notes for Alpine 3.21.0

2024-09-30T18:47:54Z

Zcrayfish: LXQt 2.0.0

== Highlights ==

* Go 1.23.1
* Rust 1.81
* GNOME 47
* KDE Plasma 6.1.5
* LXQt 2.0.0

== OpenSSH ==

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

== GNOME 47 ==

GNOME 47 made it into Alpine 3.21. Everything should work as expected. Make sure you read the GNOME 47 release notes: https://release.gnome.org/47/

== LXQt 2.0.0 ==

LXQt has been updated to release 2.0.
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, LXQt Panel's task-bar² and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been released or packaged yet, but most folks wanting to test on wayland will want to use it. 
² Most folks testing LXQt on wayland are using {{pkg|waybar}} temporarily until the task-bar is ported.

== Jellyfin ==

Jellyfin now uses the recommended fork of ffmpeg called <code>jellyfin-ffmpeg</code> by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ([https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/69924 !69924])

== Bats ==

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

HAProxy

2024-09-19T23:58:32Z

Zcrayfish: SSL support in HAProxy is deprecated, as it should be, replaced those references with TLS. Linked to packages.

[https://www.haproxy.org/ HAProxy] is a free, very fast, and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications.

A unique feature is that HAProxy can be configured for TLS termination to occur locally on the HAProxy server or it can be configured to pass through TLS termination at the backend via SNI.

== Installation ==
HAProxy package is available in the Alpine Linux repositories. To install it run:

{{Cmd|apk update
apk add {{pkg|haproxy}}}}

=== System scripts ===
If you are running OpenRC, then you can install with:

{{Cmd|apk update
apk add {{pkg|haproxy-openrc}}}}

If you are running runit, s6, or dinit, (or other), then there are no scripts packaged for your init systems yet. Please feel free to contribute a package with them.

=== Local Documentation ===
If you want local documenation, then you can install that with:

{{Cmd|apk add {{pkg|haproxy-doc}}}}

== See Also ==

* [https://www.haproxy.org/ HAProxy Homepage]

[[Category:Web Server]]

APKBUILD examples:Neovim

2024-09-16T20:15:47Z

Zcrayfish: /* [Draft] Neovim plugin packaging policy */ Use issue template.

== [Draft] Neovim plugin packaging policy ==

See {{issue|16021}}.

=== Name ===

* Must be prefixed with '''nvim-'''
* Only have a single '''nvim-''' prefix:
** Use '''nvim-treesitter''', instead of '''nvim-nvim-treesitter'''
* Omit '''.nvim''' suffix:
** Use '''nvim-telescope''', instead of '''nvim-telescope.nvim'''

=== Version ===

If there are no tags, upstream should be requested to release.

=== Site ===

Plugins must be installed in '''"$pkgdir"/usr/share/nvim/site/pack/dist/opt/$pkgname/'''. This allows users to lazy load apk managed neovim packages using: ''':packadd $pkgname''', or '''vim.cmd.packadd('$pkgname')'''.

=== Doc ===

If upstream doesn't contain generated [https://neovim.io/doc/user/helphelp.html#%3Ahelptags helptags], do so in '''build''':
build() {
nvim -u NONE -i NONE -e --headless -c "helptags doc" -c quit
}
'''amove''' neovim help files and tags in '''doc''':
doc() {
default_doc
amove usr/share/nvim/site/pack/dist/opt/$pkgname/doc
}

=== Tests ===

Skipping '''check''' is fine if testing a plugin requires vusted (which is not yet packaged):
options="!check" # requires vusted

=== Example ===

See [https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/community/nvim-lspconfig/APKBUILD?ref_type=heads community/nvim-lspconfig] for a complete example.

Template talk:AlpineLatest

2024-09-08T01:02:58Z

Zcrayfish: Indent replies; reply to Prabuanand.

This needs to be updated to the latest version (currently 3.18), but I can't do so as it is protected. [[User:Arrogance|Arrogance]] ([[User talk:Arrogance|talk]]) 11:24, 7 June 2023 (UTC)
:<s>Needs to be bumped again as we're now at 3.18.2</s> [[User:Zcrayfish|zcrayfish]] ([[User talk:Zcrayfish|talk]]) 19:48, 26 July 2023 (UTC)

== There is a need for fixing AlpineLatest Template ==

There is a need for fixing '''AlpineLatest''' Template. This template currently makes the truncation for 3.20.2 to appear as 3.2. The correct truncation should be 3.20 and not 3.2.

When the following is used <nowiki> {{#expr:{{AlpineLatest}}}} </nowiki>, it evaluates to 3.2 and when used like <nowiki>{{AlpineLatest}}</nowiki> it evaluates to 3.20.2.

This affects wiki documentation pages . For example, https://wiki.alpinelinux.org/wiki/Upgrading_Alpine#Upgrading_to_latest_release, appears as follows:

To upgrade, in this example, from version 3.3 to 3.2, simply change:
http://dl-3.alpinelinux.org/alpine/v3.3/main
to
http://dl-3.alpinelinux.org/alpine/v3.2/main

Please fix this asap, as this issue affects [[Special:WhatLinksHere/Template:AlpineLatest|multiple pages]]

[[User:Prabuanand|Prabuanand]] ([[User talk:Prabuanand|talk]]) 17:45, 5 September 2024 (UTC)

:It's not an issue with the template, but it is my fault because I was the one who inserted <nowiki> {{#expr:{{AlpineLatest}}}} </nowiki> all over the place in a lame effort to automatically update pages upon version changes... I gotta think about how best to fix this... Might be best to make the template smarter though. –[[User:zcrayfish|zcrayfish]] ([[User talk:zcrayfish|talk]]•[[Special:Contributions/zcrayfish|contribs]]•[[Special:EmailUser/zcrayfish|send email]]) 16:06, 6 September 2024 (UTC)

:My proposal is to change Template:AlpineLatest to what I currently have at [[Special:PermanentLink/27221|Template:Sandbox]], and then change all instances of <nowiki> {{#expr:{{AlpineLatest}}}} </nowiki> to <nowiki> {{AlpineLatest|v}} </nowiki> or <nowiki> {{AlpineLatest|short}} </nowiki> as appropriate. –[[User:zcrayfish|zcrayfish]] ([[User talk:zcrayfish|talk]]•[[Special:Contributions/zcrayfish|contribs]]•[[Special:EmailUser/zcrayfish|send email]]) 18:32, 6 September 2024 (UTC)

::Has the work been completed? The output in the sandbox still shows the same for both {{AlpineLatest|v}} and {{AlpineLatest|short}}. Refer [[Media:Template AlpineLatest.png|screenshot]] of what i see. Am i missing something?
::[[User:Prabuanand|Prabuanand]] ([[User talk:Prabuanand|talk]]) 08:54, 7 September 2024 (UTC)

:::Not yet –[[User:zcrayfish|zcrayfish]] ([[User talk:zcrayfish|talk]]•[[Special:Contributions/zcrayfish|contribs]]•[[Special:EmailUser/zcrayfish|send email]]) 01:02, 8 September 2024 (UTC)

Template talk:AlpineLatest

2024-09-06T18:32:38Z

Zcrayfish: Additional commentary

Template:Sandbox

2024-09-06T17:44:27Z

Zcrayfish: Add documentation...

<includeonly>{{#switch: {{{1}}} | short = 3.20 | v = v3.20 | 3.20.3 }}</includeonly>
<noinclude></noinclude>
<noinclude>{{Template}}
This template produces a string containing the latest version of Alpine Linux

=== Usage ===
<pre>{{AlpineLatest|short|v}}</pre>

{{define|short|The string produced will only contain the minor and major version}}
{{define|v|The string produced will only contain the minor and major version prefixed with a v}}

This template will only accept one parameter at a time, all parameters are optional. 
If no parameters are supplied, or the parameters which are supplied are invalid, the full version string (minor.major.patchlevel) will be produced.

=== Examples ===
Display the full version string of the latest Alpine Linux stable:
<pre>{{AlpineLatest}}</pre>
will produce:
{{AlpineLatest}}

Display the short version string of the latest Alpine Linux stable:
<pre>{{AlpineLatest|short}}</pre>
will produce:
{{AlpineLatest|short}}

Display the short version string of the latest Alpine Linux stable, prefixed with v:
<pre>{{AlpineLatest|v}}</pre>
will produce:
{{AlpineLatest|v}}
</noinclude>

Template:Sandbox

2024-09-06T17:15:00Z

Zcrayfish:

<noinclude>This is a test</noinclude>
<includeonly>
{{#switch: {{{1}}} | v = v3.20 | short = 3.20 | 3.20.3 }}
</includeonly>

Template:Sandbox

2024-09-06T17:04:55Z

Zcrayfish:

Template:Sandbox

2024-09-06T17:01:42Z

Zcrayfish:

Template:Sandbox

2024-09-06T17:00:03Z

Zcrayfish: Testing AlpineLatest template...

Sandbox

2024-09-06T16:58:47Z

Zcrayfish: working on AlpineLatest template...

Template talk:AlpineLatest

2024-09-06T16:06:38Z

Zcrayfish: /* There is a need for fixing AlpineLatest Template */ Commentary added

Talk:Alpine configuration management scripts

2024-08-18T04:42:00Z

Zcrayfish: Unsigned comment attribution. Separate topics with HR

== Automate Alpine Linux installation ==

I am trying to achieve unattended Alpine Linux installation. I went through the Alpine automatic installation guide via setup-alpine script, but when I follow this guide there are many manual interventions are needed during the installation!
one during writing the root user name, another time when creating the answer file (setup-alpine -c answerfileName), editing the answer file, calling the actual installation command (setup-alpine -f answerfileName) and reset the root password. Is there any way to include the answer file inside the ISO image and select the root user by default before starting the installation and set its password as well after the installation is done (something similar to the kickstart file in the debian distros) ? 
— Preceding unsigned comments added by [[User:Khaled.elgohary|Khaled.elgohary ]] ([[User talk:Khaled.elgohary #top|talk]] • [[Special:Contributions/Khaled.elgohary |contribs]]) 12:20, 7 February 2022‎

----

The [[https://wiki.alpinelinux.org/wiki/Alpine_setup_scripts#setup-alpine| setup-alpine]] section currently gives instructions that may appear to be contradictory:

"17. if installation mode selected during setup-disk was "data" instead of "sys", then: setup-lbu [/media/sdb1]

18. if installation mode selected during setup-disk was "data" instead of "sys", then: setup-apkcache [/media/sdb1/cache | none]"

One of these presumably refers to the case for "sys", but which?

— Preceding [[Help:Signature|unsigned]] comment added by [[User:John3-16|John3-16]] ([[User talk:John3-16|{{int:talkpagelinktext}}]] • [[Special:Contributions/John3-16|{{int:contribslink}}]]) 09:56, 15 August 2024‎

Install Alpine on a btrfs filesystem with refind as boot manager

2024-08-03T20:52:02Z

Zcrayfish: Use pkg template instead of external link to the package oracle.

It is assumed that your other OS is already installed and working with <code>[[#rEFInd|rEFInd]]</code> as boot manager and your filesystem is [[btrfs]]. Currently <code>[[#rEFInd|rEFInd]]</code> is available as the package {{pkg|refind|branch=edge|repo=testing}} in the testing repository.

Boot your PC from the Alpine Linux USB. Once booted, log in as root (no password required).
Identify your partitions by using the command.

{{cmd|# blkid}}
<pre>
/dev/nvme0n1p1: UUID="55C3-8AB4" TYPE="vfat"
/dev/nvme0n1p2: UUID="dab64e31-fb89-4364-b90f-b79400f73304" TYPE="swap"
/dev/nvme0n1p3: LABEL="BTRFSVOL" UUID="823a3283-30a7-4fef-b50b-8a2230c71b5b" TYPE="btrfs"
</pre>

Mount the btrfs partition to /mnt.

{{cmd|# mount /dev/nvme0n1p3 /mnt -t btrfs}}

Run the setup script:

{{cmd|# setup-alpine }}

This will guide you through basic system configuration. Follow the prompts to:

* Select keyboard layout
* Set hostname
* Configure network (choose your WiFi interface and enter your WiFi credentials)
* Set root password
* Choose timezone
* Choose NTP client (chronyd)
* Choose a mirror for packages
* Create a new user (optional but recommended)
* After this accept the remaining choices, if any.

Once basic setup is complete, prepare your disk for installation of Alpine as a subvolume in the [[btrfs]] filesystem:

Create a new [[Btrfs]] subvolume for Alpine and you need {{Pkg|btrfs-progs}} package

{{cmd|# apk add btrfs-progs }}
Create a new Btrfs subvolume for Alpine:
{{cmd|# btrfs subvolume create /mnt/@alpine}}

Create a new mountpoint and mount the newly created subvolume:
{{cmd|# mkdir /mnt/os}}
<pre># mount -o subvol=@alpine /dev/nvme0n1p3 /mnt/os</pre>

Install the base system using the below command:
{{cmd|# setup-disk -m sys /mnt/os}}

This will install the base system to the mounted subvolume. Once the base system is installed, chroot into the new system:
{{cmd|# chroot /mnt/os}}

Edit /etc/fstab to use the correct subvolume. Ensure that root entry looks like below. Mounting the efi partition is optional. If you want to share your @home subvolume between both the operating systems, you can also add an entry for it now.

{{Cat|/etc/fstab |<nowiki>
UUID=823a3283-30a7-4fef-b50b-8a2230c71b5b / btrfs rw,relatime,compress=zlib:3,ssd,discard=async,space_cache=v2,subvol=/@alpine 0 1
UUID=55C3-8AB4 /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro 0 2
</nowiki>}}

Verify linux kernel is installed successfully.
{{cmd|# apk list --installed |grep linux}}

If your other OS is already installed and working with refind as boot manager, then there is no need to install refind here.
You may want to remove the grub and grub-efi packages
{{cmd|# apk del grub grub-efi}}

Exit the chroot:
{{cmd|# exit}}

Mount the EFI partition to edit the refind.conf file
{{cmd|# mkdir /mnt/os/boot/efi}}

{{cmd|# mount dev/nvme0n1p1 /mnt/os/boot/efi}}

Edit /mnt/os/boot/efi/EFI/refind/refind.conf to boot alpine by adding an entry for Alpine Linux as shown below:

{{Cat|/boot/efi/EFI/refind/refind.conf|<nowiki>
menuentry "Alpine Linux" {
volume "BTRFSVOL"
loader @alpine/boot/vmlinuz-lts
initrd @alpine/boot/initramfs-lts
options "root=UUID=823a3283-30a7-4fef-b50b-8a2230c71b5b rw rootflags=subvol=@alpine rootfstype=btrfs"

}
</nowiki>}}

Do not use PARTUUID in refind.conf as it does not work for booting alpine.

Unmount everything:
{{cmd|# umount -R /mnt}}

Reboot your system.
{{cmd|# reboot}}

Now, you should now see an option to boot into Alpine Linux in the rEFInd boot menu.

* [https://wiki.archlinux.org/title/REFInd#For_manual_boot_stanzas Refind in Arch Wiki]

Matrix

2024-07-26T17:24:40Z

Zcrayfish: Convert weblinks to wikilinks. Remove fluff.

[https://matrix.org/ Matrix] is an ambitious new ecosystem and protocol for open federated instant messaging and VoIP. It consists of servers, [https://matrix.org/clients/ various clients] and [https://matrix.org/bridges/ bridge] software to connect to existing messaging solutions such as IRC (Internet Relay Chat).

The [[Alpine Linux:IRC|Alpine Linux IRC chatrooms]] are bridged to Matrix. The General Alpine Linux room can be found on Matrix here [https://matrix.to/#/#_oftc_#alpine-linux:matrix.org #_oftc_#alpine-linux:matrix.org]. If you want to access any of the other Alpine Linux chats from Matrix, then substitute the IRC channel name accordingly.

= Installation =
The Matrix Protocol has multiple server implementations which are available on Alpine Linux.

The reference server implementation Synapse, which is the most commonly used server, is available as the {{pkg|synapse}} package. It has been available since Alpine 3.11.

There is also a second-generation Matrix homeserver written in Go, which is available as the {{pkg|dendrite}} package. It intends to provide an efficient, reliable and scalable alternative to Synapse, but it is not as feature complete as Synapse is at this time. It has been available since Alpine 3.15.

There is also another Matrix homeserver, written in Rust, which is available as the {{pkg|conduit}} package and is only currently available in the Alpine Edge at this time.

Before you start installing anything, make sure you have the latest packages available.
{{tip|Detailed information is found in [[Include:Upgrading_to_latest_release|this]] doc.}}

= Matrix Synapse server =

This Wiki will cover the installation, configuration, and setup of the '''Matrix Synapse server''', as this is the most commonly used and feature complete Matrix Protocol server at this time.

== Install Matrix Synapse server ==

Synapse package is available in the Alpine Linux repositories. To install it run:

{{Cmd|apk update
apk add synapse}}

When installing the Alpine Linux synapse package, it will create a user called ''synapse''.

== Configuration and Setup ==

During installation, the Alpine Linux synapse package will create a default synapse configuration file which will be located at {{path|/etc/synapse/homeserver.conf}}.

You will want to refer to the [https://element-hq.github.io/synapse/latest/usage/configuration/config_documentation.html Matrix Synapse Configuration Manual] to configure the various options.

If you want your Matrix Synapse server to be accessed over the internet, then it is highly recommended to configure a [https://element-hq.github.io/synapse/latest/reverse_proxy.html reverse proxy] to do that. You are free to choose your reverse proxy of choice, as the Matrix Synapse documentation has examples for each one. I recommend [[nginx]].

=== Database ===

Once synapse is installed, you will need to select which database to use with it. By default, Synapse uses a SQLite database, which is only acceptable for testing purposes & should not be used a production environment.

The Matrix Synapse developers recommend using PostgresSQL as your database backend. For more details on installing PostgresSQL, refer to the [[Postgresql|PostgreSQL article]]. It is recommended that you install the latest PostgreSQL release available, which at this time is PostgreSQL 16.

== See also ==
* [https://wiki.archlinux.org/title/Matrix Matrix - Archwiki]
* [https://element-hq.github.io/synapse/ Matrix Synapse Documentation]
* [https://github.com/element-hq/synapse Matrix Synapse Github]
* [https://github.com/matrix-org/dendrite Matrix Dendrite Github]
* [https://conduit.rs/ Matrix Conduit Website]

[[Category:Server]]

Postgresql 16

2024-07-26T17:19:41Z

Zcrayfish: /* Install */ Use pkg template.

= General =
PostgreSQL is a well known opensource database that scales well and is easy to use. In Alpine v3.20 we can install the latest version using the package postgresql16

= Install =
{{Cmd|apk add {{pkg|postgresql16|arch=}} {{pkg|postgresql16-contrib|arch=}} {{pkg|postgresql16-openrc|arch=}}}}
{{Cmd|rc-update add postgresql}}
{{Cmd|rc-service postgresql start}}

This will start the postgresql 16 server and perform some initial configuration.

= Configure =
Login as the postgres user and start psql to create a new user and database:
{{Cmd|su postgres}}
{{Cmd|psql}}
{{Cmd|create user user with encrypted password 'password';}}
{{Cmd|create database database;}}
{{Cmd|grant all privileges on database database to user;}}

= Use =
By default only local access is allowed to PostgreSQL. To allow other networked services to access the database we need to configure PostgreSQL to allow external connections.

== modify the postgresql.conf file ==
{{Cmd|nano /etc/postgresql16/postgresql.conf}}
Find the line that starts with <pre>#listen_addresses = 'localhost'</pre>
Uncomment it and change it to the following:
<pre>listen_addresses = '*'</pre>
If you want it to listen on a specific ip you can change * to 192.168.1.2/24.
Save the file and change the next config file.

== modify the pg_hba.conf file ==
{{Cmd|nano /etc/postgresql16/pg_hba.conf}}
Look for the line: <pre>host all all 127.0.0.1/32 md5</pre>
And change it to: <pre>host all all 0.0.0.0/0 md5</pre>
This line allows connections from any IP address and requires a password for authentication (md5).
Restart the server to allow incoming connections from other hosts.
{{Cmd|rc-service postgresql start}}

Besure to allow the port through the firewall. For UFW type:
{{Cmd|ufw allow 5432}}

This is a basic configuration. You can configure the PostgreSQL server to only allow certain networks or IP's to connect but thats beyond the scope of this documentation.

= Troubleshooting =
* Some troubleshooting information

= Upgrading PostgreSQL =
* Notes on upgrading PostgreSQL 16 to 17

= Resources =
* https://blog.devart.com/configure-postgresql-to-allow-remote-connection.html

[[Category:Server]]

Securing Alpine Linux

2024-07-04T00:07:03Z

Zcrayfish: Begin to use some of the styling templates (path, cmd)

Securing Alpine Linux using Security Technical Implementation Guides (STIGs) involves several steps. STIGs are a series of security requirements and configurations that help to secure systems. While there might not be a specific STIG for Alpine Linux, you can follow general Linux hardening guidelines and apply the principles from other Linux STIGs. Here’s a step-by-step process:

Step 1: Update and Upgrade System

1. Update package lists:

{{cmd|doas apk update}}

2. Upgrade installed packages:

{{cmd|doas apk upgrade}}

Step 2: Install Necessary Security Tools

1. Install {{pkg|audit|arch=}} package:

{{cmd|doas apk add audit}}

2. Install other necessary security packages:

{{cmd|doas apk add doas logrotate bash-completion openssh-server}}

Step 3: User and Access Management

1. Disable root login over SSH:

Edit {{path|/etc/ssh/sshd_config}}:

{{cmd|doas vi /etc/ssh/sshd_config}}

Set the following parameter:

PermitRootLogin no

2. Ensure password complexity:

Edit {{path|/etc/security/pwquality.conf}}:

{{cmd|doas vi /etc/security/pwquality.conf}}

Add or update the following lines:

minlen = 14
dcredit = -1
ucredit = -1
ocredit = -1
lcredit = -1

3. Lock unused system accounts:

for user in `awk -F: '($3 < 1000) {print $1}' /etc/passwd`; do
if [ $user !{{=}} "root" ]; then
doas passwd -l $user
doas chage -E 0 $user
fi
done

Step 4: File System and Directory Permissions

1. Set appropriate permissions on important directories:

doas chmod 700 /root
doas chmod 600 /boot/grub/grub.cfg
doas chmod 600 /etc/ssh/sshd_config

2. Configure mount options:

Edit {{path|/etc/fstab}}:

{{cmd|doas vi /etc/fstab}}

Add `nosuid`, `nodev`, and `noexec` options to non-root partitions:

/dev/sda1 /home ext4 defaults,nosuid,nodev,noexec 0 2

Step 5: Network Security

1. Disable unnecessary services:

{{cmd|doas rc-update del <service_name>
doas rc-service <service_name> stop}}

2. Configure firewall (iptables):

{{cmd|doas apk add iptables
doas rc-service iptables start
doas rc-update add iptables}}

Create a basic firewall ruleset:

{{cmd|doas vi /etc/iptables/rules.v4}}

Example rules:

*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p tcp --dport 22 -j ACCEPT
COMMIT

Step 6: Logging and Auditing

1. Configure system logging:

Edit {{path|/etc/rsyslog.conf}} to ensure all log files are being captured:

{{cmd|doas vi /etc/rsyslog.conf}}

Example configuration:

*.info;mail.none;authpriv.none;cron.none /var/log/messages
authpriv.* /var/log/secure
mail.* -/var/log/maillog
cron.* /var/log/cron

2. Set up audit rules:

Edit {{path|/etc/audit/rules.d/audit.rules}}:

{{cmd|doas vi /etc/audit/rules.d/audit.rules}}

Example rules:

-w /etc/passwd -p wa -k passwd_changes
-w /etc/shadow -p wa -k shadow_changes
-w /etc/group -p wa -k group_changes

Step 7: Apply Kernel and Service Hardening

1. Disable unused filesystems:

Edit {{path|/etc/modprobe.d/disable-filesystems.conf}}:

{{cmd|doas vi /etc/modprobe.d/disable-filesystems.conf}}

Add the following lines:

install cramfs /bin/true
install freevxfs /bin/true
install jffs2 /bin/true
install hfs /bin/true
install hfsplus /bin/true
install squashfs /bin/true
install udf /bin/true
install vfat /bin/true

2. Configure kernel parameters:

Edit {{path|/etc/sysctl.conf}}:

{{cmd|doas vi /etc/sysctl.conf}}

Add or update the following parameters:

net.ipv4.ip_forward = 0
net.ipv4.conf.all.accept_source_route = 0
net.ipv4.conf.all.accept_redirects = 0
net.ipv4.conf.all.secure_redirects = 0
net.ipv4.conf.all.log_martians = 1
net.ipv4.conf.default.log_martians = 1
net.ipv4.icmp_echo_ignore_broadcasts = 1
net.ipv4.icmp_ignore_bogus_error_responses = 1
net.ipv4.tcp_syncookies = 1
net.ipv4.conf.all.send_redirects = 0
net.ipv4.conf.default.send_redirects = 0

Step 8: Regular Maintenance

1. Set up regular updates:

Create a cron job for regular updates:

{{cmd|doas crontab -e}}

Add the following line to update daily at 2 AM:

0 2 * * * apk update && apk upgrade

2. Review and monitor logs regularly:

Ensure logs are rotated and reviewed frequently:

{{cmd|doas logrotate /etc/logrotate.conf}}

Conclusion

This process provides a foundation for securing an Alpine Linux system. Regular reviews and updates, along with compliance with the latest security guidelines, are essential to maintaining a secure environment.

Securing Alpine Linux

2024-07-03T23:53:50Z

Zcrayfish: Bulk replace sudo with doas.

Securing Alpine Linux using Security Technical Implementation Guides (STIGs) involves several steps. STIGs are a series of security requirements and configurations that help to secure systems. While there might not be a specific STIG for Alpine Linux, you can follow general Linux hardening guidelines and apply the principles from other Linux STIGs. Here’s a step-by-step process:

Step 1: Update and Upgrade System

1. Update package lists:

doas apk update

2. Upgrade installed packages:

doas apk upgrade

Step 2: Install Necessary Security Tools

1. Install `audit` package:

doas apk add audit

2. Install other necessary security packages:

doas apk add doas logrotate bash-completion openssh-server

Step 3: User and Access Management

1. Disable root login over SSH:

Edit `/etc/ssh/sshd_config`:

doas vi /etc/ssh/sshd_config

Set the following parameter:

PermitRootLogin no

2. Ensure password complexity:

Edit `/etc/security/pwquality.conf`:

doas vi /etc/security/pwquality.conf

Add or update the following lines:

minlen = 14
dcredit = -1
ucredit = -1
ocredit = -1
lcredit = -1

3. Lock unused system accounts:

for user in `awk -F: '($3 < 1000) {print $1}' /etc/passwd`; do
if [ $user != "root" ]; then
doas passwd -l $user
doas chage -E 0 $user
fi
done

Step 4: File System and Directory Permissions

1. Set appropriate permissions on important directories:

doas chmod 700 /root
doas chmod 600 /boot/grub/grub.cfg
doas chmod 600 /etc/ssh/sshd_config

2. Configure mount options:

Edit `/etc/fstab`:

doas vi /etc/fstab

Add `nosuid`, `nodev`, and `noexec` options to non-root partitions:

/dev/sda1 /home ext4 defaults,nosuid,nodev,noexec 0 2

Step 5: Network Security

1. Disable unnecessary services:

doas rc-update del <service_name>
doas rc-service <service_name> stop

2. Configure firewall (iptables):

doas apk add iptables
doas rc-service iptables start
doas rc-update add iptables

Create a basic firewall ruleset:

doas vi /etc/iptables/rules.v4

Example rules:

*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p tcp --dport 22 -j ACCEPT
COMMIT

Step 6: Logging and Auditing

1. Configure system logging:

Edit `/etc/rsyslog.conf` to ensure all log files are being captured:

doas vi /etc/rsyslog.conf

Example configuration:

*.info;mail.none;authpriv.none;cron.none /var/log/messages
authpriv.* /var/log/secure
mail.* -/var/log/maillog
cron.* /var/log/cron

2. Set up audit rules:

Edit `/etc/audit/rules.d/audit.rules`:

doas vi /etc/audit/rules.d/audit.rules

Example rules:

-w /etc/passwd -p wa -k passwd_changes
-w /etc/shadow -p wa -k shadow_changes
-w /etc/group -p wa -k group_changes

Step 7: Apply Kernel and Service Hardening

1. Disable unused filesystems:

Edit `/etc/modprobe.d/disable-filesystems.conf`:

doas vi /etc/modprobe.d/disable-filesystems.conf

Add the following lines:

install cramfs /bin/true
install freevxfs /bin/true
install jffs2 /bin/true
install hfs /bin/true
install hfsplus /bin/true
install squashfs /bin/true
install udf /bin/true
install vfat /bin/true

2. Configure kernel parameters:

Edit `/etc/sysctl.conf`:

doas vi /etc/sysctl.conf

Add or update the following parameters:

net.ipv4.ip_forward = 0
net.ipv4.conf.all.accept_source_route = 0
net.ipv4.conf.all.accept_redirects = 0
net.ipv4.conf.all.secure_redirects = 0
net.ipv4.conf.all.log_martians = 1
net.ipv4.conf.default.log_martians = 1
net.ipv4.icmp_echo_ignore_broadcasts = 1
net.ipv4.icmp_ignore_bogus_error_responses = 1
net.ipv4.tcp_syncookies = 1
net.ipv4.conf.all.send_redirects = 0
net.ipv4.conf.default.send_redirects = 0

Step 8: Regular Maintenance

1. Set up regular updates:

Create a cron job for regular updates:

doas crontab -e

Add the following line to update daily at 2 AM:

0 2 * * * apk update && apk upgrade

2. Review and monitor logs regularly:

Ensure logs are rotated and reviewed frequently:

doas logrotate /etc/logrotate.conf

Conclusion

This process provides a foundation for securing an Alpine Linux system. Regular reviews and updates, along with compliance with the latest security guidelines, are essential to maintaining a secure environment.