ArchWiki - User contributions [en]

Display server

2026-04-28T17:09:51Z

Alad: update redirect

#REDIRECT: [[List of applications/Other#Display_servers]]

General recommendations

2026-04-28T17:06:34Z

Alad: /* Display server */ remove section per template

[[Category:System administration]]
[[bs:General recommendations]]
[[ca:General recommendations]]
[[cs:General recommendations]]
[[el:General recommendations]]
[[es:General recommendations]]
[[fr:General recommendations]]
[[hu:General recommendations]]
[[it:General recommendations]]
[[ja:一般的な推奨事項]]
[[lv:General recommendations]]
[[pl:General recommendations]]
[[pt:General recommendations]]
[[ru:General recommendations]]
[[tr:General recommendations]]
[[zh-hans:建议阅读]]
[[zh-hant:General recommendations]]
{{Related articles start}}
{{Related|Frequently asked questions}}
{{Related|List of applications}}
{{Related|System maintenance}}
{{Related articles end}}

This document is an annotated index of popular articles and important information for improving and adding functionalities to the installed Arch system. Readers are assumed to have read and followed the [[Installation guide]] to obtain a basic Arch Linux installation. Having read and understood the concepts explained in [[#System administration]] and [[#Package management]] is ''required'' for following the other sections of this page and the other articles in the wiki.

== System administration ==

This section deals with administrative tasks and system management. See [[Core utilities]] and [[:Category:System administration]] for more.

=== Users and groups ===

A new installation leaves you with only the [[Wikipedia:Superuser|superuser]] account, better known as "root". Logging in as root for prolonged periods of time, possibly even exposing it via [[SSH]] on a server, [https://apple.stackexchange.com/questions/192365/is-it-ok-to-use-the-root-user-as-a-normal-user/192422#192422 is insecure]. Instead, you should create and use unprivileged user account(s) for most tasks, only using the root account for system administration. See [[Users and groups#User management]] for details.

Users and groups are a mechanism for ''access control''; administrators may fine-tune group membership and ownership to grant or deny users and services access to system resources. Read the [[Users and groups]] article for details and potential security risks.

=== Security ===

Read [[Security]] for recommendations and best practices on hardening the system.

For a list of applications to allow running commands or starting an interactive shell as another user (e.g. root), see [[List of applications/Security#Privilege elevation]]. For graphical equivalents (and how to avoid them), see [[Privilege elevation for graphical applications]].

{{Tip|More fine-grained privilege elevation is provided by [[polkit]], which requires additional setup for graphical environments.}}

=== Service management ===

Arch Linux uses [[systemd]] as the [[init]] process, which is a system and service manager for Linux. For maintaining your Arch Linux installation, it is a good idea to learn the basics about it.

Interaction with ''systemd'' is done through the ''systemctl'' command. See [[systemd#Basic systemctl usage]] for more information.

A logging system is also provided, with the command ''journalctl''. See [[journal]] for more information.

=== System maintenance ===

Arch is a rolling release system and has rapid package turnover, so users have to take some time to do [[system maintenance]].

== Package management ==

This section contains helpful information related to package management. See [[FAQ#Package management]] and [[:Category:Package management]] for more.

{{Note|It is imperative to keep up to date with changes in Arch Linux that require manual intervention '''before''' upgrading your system. Subscribe to the [https://lists.archlinux.org/mailman3/lists/arch-announce.lists.archlinux.org/ arch-announce mailing list] or the [https://archlinux.org/feeds/news/ recent news RSS feed]. Alternatively, check the front page [https://archlinux.org/ Arch news] every time before you update.}}

=== pacman ===

[[pacman]] is the Arch Linux ''pac''kage ''man''ager: it is highly encouraged to become familiar with it before reading any other articles.

For long term handling of cached packages, see [[pacman#Cleaning the package cache]].

See [[pacman/Tips and tricks]] for suggestions on how to improve your interaction with ''pacman'' and package management in general.

=== Repositories ===

See the [[Official repositories]] article for details about the purpose of each officially maintained repository.

If you plan on using 32-bit applications, you will want to enable the [[multilib]] repository.

The [[Unofficial user repositories]] article lists several other unsupported repositories.

You may consider installing the [[pkgstats]] service.

=== Mirrors ===

Visit the [[Mirrors]] article for steps on taking full advantage of using the fastest and most up to date mirrors of the official repositories. As explained in the article, a particularly good advice is to routinely check the [https://archlinux.org/mirrors/status/ Mirror Status] page for a list of mirrors that have been recently synced. This can be automated with [[Reflector]].

=== Arch Build System ===

''Ports'' is a system initially used by BSD distributions consisting of build scripts that reside in a directory tree on the local system. Simply put, each port contains a script within a directory intuitively named after the installable third-party application.

The [[Arch build system]] offers the same functionality by providing build scripts called [[PKGBUILD]]s, which are populated with information for a given piece of software: integrity hashes, project URL, version, license and build instructions. These PKGBUILDs are parsed by [[makepkg]], the actual program that generates packages that are cleanly manageable by ''pacman''.

Every package in the repositories along with those present in the AUR are subject to recompilation with ''makepkg''.

=== Arch User Repository ===

While the Arch Build System allows the ability of building software available in the official repositories, the [[Arch User Repository]] (AUR) is the equivalent for user submitted packages. It is an unsupported repository of build scripts accessible through the [https://aur.archlinux.org/ web interface] or through the [[Aurweb RPC interface]].

== Booting ==

This section contains information pertaining to the boot process. An overview of the Arch boot process can be found at [[Arch boot process]]. See [[:Category:Boot process]] for more.

=== Hardware auto-recognition ===

Hardware should be auto-detected by [[udev]] during the boot process by default. A potential improvement in boot time can be achieved by disabling module auto-loading and specifying required modules manually, as described in [[Kernel modules]]. Additionally, [[Xorg]] should be able to auto-detect required drivers using {{ic|udev}}, but users have the option to configure the X server manually too.

=== Microcode ===

Processors may have [https://www.anandtech.com/show/8376/intel-disables-tsx-instructions-erratum-found-in-haswell-haswelleep-broadwelly faulty behaviour], which the kernel can correct by updating the ''microcode'' on startup. See [[Microcode]] for details.

=== Retaining boot messages ===

Once the login prompt appears, the messages from boot are cleared, leaving users unable to gather feedback from them. [[Disable clearing of boot messages]] to overcome this limitation.

=== Num Lock activation ===

[[Wikipedia:Num Lock|Num Lock]] is a toggle key found in most keyboards. For activating Num Lock's number key-assignment during startup, see [[Activating numlock on bootup]].

== Graphical user interface ==

This section provides orientation for users wishing to run graphical applications on their system. See [[:Category:Graphical user interfaces]] for additional resources.

=== Xorg DDX drivers ===

[[Xorg]]'s default ''modesetting'' DDX driver will work with most video cards, but performance may be improved and additional features harnessed by installing the [[Graphics processing unit#Installation|appropriate DDX driver]] for [[AMD]], [[Intel]] or [[NVIDIA]] products.

=== Desktop environments ===

Although the display server provides the basic framework for building a graphical environment, additional components may be considered necessary for a complete user experience. [[Desktop environment]]s such as [[KDE]], [[GNOME]], [[COSMIC]], [[Xfce]], [[Cinnamon]], [[LXDE]], bundle together a wide range of well-integrated applications, such as a window manager or compositor, panel/taskbar, file manager, terminal emulator, text editor, icons, and other utilities. Users with less experience may wish to install a desktop environment for a more familiar environment. See [[:Category:Desktop environments]] for additional resources.

=== Window managers or compositors ===

A full-fledged desktop environment provides a complete and consistent graphical user interface, but tends to consume a good amount of system resources. Users seeking to maximize performance or otherwise simplify their environment may opt to install a [[window manager]] or [[Wayland#Compositors|compositor]] alone and hand-pick desired extras. Using [[Xorg]], most desktop environments allow use of an alternative window manager as well. [[:Category:Dynamic window managers|Dynamic]], [[:Category:Stacking window managers|stacking]], and [[:Category:Tiling window managers|tiling]] window managers differ in their handling of window placement.

=== Display manager ===

Most desktop environments include a [[display manager]] for automatically starting the graphical environment and managing user logins. Users without a desktop environment can install one separately. Alternatively you may [[start X at login]] as a simple alternative to a display manager.

=== User directories ===

Well-known user directories like Downloads or Music are created by the {{ic|xdg-user-dirs-update.service}} user service, that is provided by {{Pkg|xdg-user-dirs}} and enabled by default upon install. If your desktop environment or window manager does not pull in the package, you can [[install]] it and run {{ic|xdg-user-dirs-update}} manually as per [[XDG user directories#Creating default directories]].

== Power management ==

This section may be of use to laptop owners or users otherwise seeking power management controls. See [[:Category:Power management]] for more.

See [[Power management]] for more general overview.

=== ACPI events ===

Users can configure how the system reacts to ACPI events such as pressing the power button or closing a laptop's lid. For the recommended method using [[systemd]], see [[Power management#ACPI events]]. For the old method, see [[acpid]].

=== CPU frequency scaling ===

Modern processors can decrease their frequency and voltage to reduce heat and power consumption. Less heat leads to more quiet system and prolongs the life of hardware. See [[CPU frequency scaling]] for details.

=== Laptops ===

For articles related to portable computing along with model-specific installation guides, please see [[:Category:Laptops]]. For a general overview of laptop-related articles and recommendations, see [[Laptop]].

=== Suspend and hibernate ===

See the main article: [[Power management/Suspend and hibernate]].

== Multimedia ==

[[:Category:Multimedia]] includes additional resources.

=== Sound system ===

[[ALSA]] is a kernel [[sound system]] that should work out the box (it just needs to be [[Advanced Linux Sound Architecture#Unmuting the channels|unmuted]]). [[Sound server]]s such as [[PipeWire]] and [[PulseAudio]] can offer additional features and support more complex audio configuration.

See [[Professional audio]] for advanced audio requirements.

== Networking ==

This section is confined to small networking procedures. See [[Network configuration]] for a full configuration guide and [[:Category:Networking]] for related articles.

=== DNS security ===

For better security while browsing the web, paying online, connecting to [[SSH]] services and similar tasks consider using [[DNSSEC]]-enabled [[DNS resolver]] that can validate signed [[Wikipedia:Domain Name System|DNS]] records, and an encrypted protocol such as [[Wikipedia:DNS over TLS|DNS over TLS]], [[Wikipedia:DNS over HTTPS|DNS over HTTPS]] or [[Wikipedia:DNSCrypt|DNSCrypt]]. See [[Domain name resolution]] for details.

=== Setting up a firewall ===

A firewall can provide an extra layer of protection on top of the Linux networking stack. While the stock Arch kernel is capable of using [[Wikipedia:Netfilter|Netfilter]]'s [[iptables]] and [[nftables]], neither are enabled by default. It is highly recommended to set up some form of firewall. See [[:Category:Firewalls]] for available guides.

=== Network shares ===

To share files among the machines in a network, follow the [[NFS]] or the [[SSHFS]] article.

Use [[Samba]] to join a Windows network. To configure the machine to use Active Directory for authentication, read [[Active Directory integration]].

See also [[:Category:Network sharing]].

== Input devices ==

This section contains popular input device configuration tips. See [[:Category:Input devices]] for more.

=== Keyboard layouts ===

Non-English or otherwise non-standard keyboards may not function as expected by default. The necessary steps to configure the keymap are different for virtual console and [[Xorg]], they are described in [[Keyboard configuration in console]] and [[Keyboard configuration in Xorg]] respectively.

=== Mouse buttons ===

Owners of advanced or unusual mice may find that not all mouse buttons are recognized by default, or may wish to assign different actions for extra buttons. Instructions can be found in [[Mouse buttons]].

=== Laptop touchpads ===

Many laptops use [[Wikipedia:Synaptics|Synaptics]] or [[Wikipedia:Alps Electric|ALPS]] "touchpad" pointing devices. For these, and several other touchpad models, you can use either the Synaptics input driver or libinput; see [[Touchpad Synaptics]] and [[libinput]] for installation and configuration details.

=== TrackPoints ===

See the [[TrackPoint]] article to configure your TrackPoint device.

== Optimization ==

This section aims to summarize tweaks, tools and available options useful to improve system and application performance.

=== Benchmarking ===

[[Benchmarking]] is the act of measuring performance and comparing the results to another system's results or a widely accepted standard through a unified procedure.

=== Improving performance ===

The [[Improving performance]] article gathers information and is a basic rundown about gaining performance in Arch Linux.

=== Solid state drives ===

The [[Solid state drive]] article covers many aspects of solid state drives, including configuring them to maximize their lifetimes, e.g. with [[TRIM]].

== System services ==

This section relates to [[daemons]].

=== File index and search ===

Most distributions have a ''locate'' command available to be able to quickly search files. Arch Linux provides several alternatives, see [[locate]] for details.

[[List of applications/Utilities#File searching|Desktop search engines]] provide a similar service, while better integrated into [[desktop environment]]s.

=== Local mail delivery ===

A default setup does not provide a way to synchronize mail. A list of mail delivery agents is available in the [[Mail server]] article.

=== Printing ===

[[CUPS]] is a standards-based, open source printing system developed by OpenPrinting for Linux. See [[:Category:Printers]] for printer-specific articles.

== Appearance ==

This section contains frequently-sought "eye candy" tweaks for an aesthetically pleasing Arch experience. See [[:Category:Eye candy]] for more.

=== Fonts ===

You may wish to install a set of TrueType fonts, as only unscalable bitmap fonts are included in a basic Arch system. There are several general-purpose [[Fonts#Families|font families]] providing large [[Wikipedia:Unicode|Unicode]] coverage and even [[Metric-compatible fonts|metric compatibility]] with fonts from other operating systems.

A plethora of information on the subject can be found in the [[Fonts]] and [[Font configuration]] articles.

If spending a significant amount of time working from the virtual console (i.e. outside an X server), users may wish to change the console font to improve readability; see [[Linux console#Fonts]].

=== GTK and Qt themes ===

A big part of the applications with a graphical interface for Linux systems are based on the [[GTK]] or the [[Qt]] toolkits. See those articles and [[Uniform look for Qt and GTK applications]] for ideas to improve the appearance of your installed programs and adapt it to your liking.

== Console improvements ==

This section applies to small modifications that improve console programs' practicality. See [[:Category:Command-line shells]] for more.

=== Tab-completion enhancements ===

It is recommended to properly set up extended [[Wikipedia:Command-line_completion|tab completion]] right away, as instructed in the article of your chosen [[shell]].

=== Aliases ===

Aliasing a command, or a group thereof, is a way of saving time when using the console. This is especially helpful for repetitive tasks that do not need significant alteration to their parameters between executions. Common time-saving aliases can be found in [[Bash#Aliases]], which are easily portable to [[zsh]] as well.

=== Alternative shells ===

[[Bash]] is the shell installed by default in an Arch system. The live installation media, however, uses [[zsh]] with the {{Pkg|grml-zsh-config}} addon package. See [[Command-line shell#List of shells]] for more alternatives.

=== Bash additions ===

A list of miscellaneous Bash settings, history search and [[Readline]] macros is available in [[Bash#Tips and tricks]].

=== Colored output ===

This section is covered in [[Color output in console]].

=== Compressed files ===

Compressed files, or archives, are frequently encountered on a GNU/Linux system. [[Tar]] is one of the most commonly used archiving tools, and users should be familiar with its syntax (Arch Linux packages, for example, are simply {{Pkg|zstd}} compressed tarballs). See [[Archiving and compression]].

=== Console prompt ===

The console prompt ({{ic|PS1}}) can be customized to a great extent. See [[Bash/Prompt customization]] or [[Zsh#Prompts]] if using Bash or Zsh, respectively.

=== Emacs shell ===

Emacs is known for featuring options beyond the duties of regular text editing, one of these being a full shell replacement. Consult [[Emacs#Colored output issues]] for a fix regarding garbled characters that may result from enabling colored output.

=== Mouse support ===

Using a mouse with the console for copy-paste operations can be preferred over [[GNU Screen]]'s traditional copy mode. Refer to [[General purpose mouse]] for comprehensive directions. Note that you can already do this in [[terminal emulator]]s with the [[clipboard]].

=== Session management ===

Using terminal multiplexers like [[tmux]] or [[GNU Screen]], programs may be run under sessions composed of tabs and panes that can be detached at will, so when the user either kills the terminal emulator, terminates [[X]], or logs off, the programs associated with the session will continue to run in the background as long as the terminal multiplexer server is active. Interacting with the programs requires reattaching to the session.

Talk:AUR helpers

2026-04-26T22:00:17Z

Alad: /* Add reference to Pacman/Tips and tricks#Graphical */ new section

== Add table column for [[AUR helpers#Pacman wrappers]] ==

We have a note right above the table, would it not be better to create a new column for the information it contains? --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 08:26, 20 March 2022 (UTC)

:The article went back and forth on this, the main issue being to define "batch operations" in the first place. This term was originally introduced by {{AUR|pacaur}} and comes down to 1. guessing which packages need to be replaced beforehand 2. using {{ic|pacman --ask}} (undocumented feature) to invert {{ic|pacman --noconfirm}} prompts from {{ic|N}} to {{ic|Y}} during the build process.
:Making this a column with Yes/No implies this is a desirable feature. I argue that depending on undocumented features with a bug-prone implementation (what if the wrong package is replaced on the user's system?) can not be classified as such. Furthermore, it gives the impression this somehow leads to ''less'' interaction on the user's behalf, which is false (in fact, the vast majority of pacman wrappers play a game of whack-a-mole with {{ic|y/N}} prompts). A Note is more neutral, and leaves out whether a feature is wanted or not in the middle.
:In any case, the other columns, Shell completion excepted, are better suited as basic requirements for a reliable AUR helper. And as far as basic requirements go, they are relatively simple to implement for AUR helper authors looking at this article - unlike a "batch operation" mechanism. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 15:47, 20 March 2022 (UTC)

:: Thank you ! I better understand now the reason why this is not already done. --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 16:26, 20 March 2022 (UTC)

== Auxiliary files for File review ==

Auxiliary files in an AUR repository also lead to arbitrary code execution, namely .install files which are run by [[pacman]] as root. As such it makes sense for the file review column to include them. For a helper that only supports viewing the [[PKGBUILD]], I suggest a Partial entry (after all, when noticing there is an .install file, the user can manually view it with some effort). -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 03:10, 8 October 2023 (UTC)

:Sounds good to me :) [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 15:37, 15 May 2024 (UTC)

== Add warning about reading diffs ==

In the light of the recent RAT malware found on the AUR, we may want to add a reminder in the warning up top, with either a link to or a rewording of the warning in [[Arch User Repository#Build the package]]? 
-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 09:48, 7 August 2025 (UTC)

== Paru/Yay Unsafe Flags are Wrong ==

Yay and Paru both have the option to use --ask although it is opt in and is a flag that needs to be
explicitly Passed.

Yay and Paru both have the --combinedupgrade flag (which causes a -Sy), although it's on by default
in Yay and off in Paru.

I'm not sure if yellow is meant to mean the flag is optional or --ask is coloured yellow and -Sy always red. I don't
seem to have the perms to edit it anyway so I'll leave the formatting to you. --[[User:Morganamilo|Morganamilo]] ([[User talk:Morganamilo|talk]]) 08:11, 7 October 2025 (UTC)

:So if I get it right, yay should have a red entry for default -Sy, and paru no entry?
:The only definition for yellow in the article is "optional", but since every wrapper supports -Sy as an option, that doesn't make sense for the Unsafe flags column. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 05:54, 5 January 2026 (UTC)

== <s>Spring cleaning</s> ==

Time for another spring cleaning? Most of the helpers in this article haven't been updated in years:

* {{AUR|pbget}}: last update in 2021, reported to no longer work: https://aur.archlinux.org/packages/pbget
* {{AUR|yaah}}: last update in 2021
* {{AUR|rua}}: last update in 2024, multiple security issues ignored: https://github.com/vn971/rua/issues
* {{AUR|aurman}}: last update in 2023, no github activity
* {{AUR|pacaur}}: last update in 2021, no github activity

If no objections are raised within 2 weeks of this post, I will remove the entries. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 12:21, 27 March 2026 (UTC)

:Make sense, go for it, [[User:Spyhawk|Spyhawk]] ([[User talk:Spyhawk|talk]]) 13:43, 6 April 2026 (UTC)

::[[Special:Diff/872262]] -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 21:53, 26 April 2026 (UTC)

== adding cockpit-pacman to GUI tools section ==

would it make sense to add cockpit-pacman [1][2] to the GUI tools section?

[1] https://gitlab.archlinux.org/pfeifferj/cockpit-pacman

[2] https://aur.archlinux.org/packages/cockpit-pacman [[User:Pfeifferj|Pfeifferj]] ([[User talk:Pfeifferj|talk]]) 16:13, 27 March 2026 (UTC)

:Wouldn't this belong to [[Pacman/Tips_and_tricks#Graphical]]? I don't see AUR support in cockpit-pacman. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 21:56, 26 April 2026 (UTC)

== Add reference to [[Pacman/Tips and tricks#Graphical]] ==

Since graphical AUR and pacman helpers are intimately related, it would make sense to reference [[Pacman/Tips and tricks#Graphical]] in [[AUR helpers#Graphical]]. Conversely, [[Pacman/Tips and tricks]] already links to [[AUR helpers]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 22:00, 26 April 2026 (UTC)

Talk:AUR helpers

2026-04-26T21:56:20Z

Alad: /* adding cockpit-pacman to GUI tools section */ re

Talk:AUR helpers

2026-04-26T21:53:18Z

Alad: /* Spring cleaning */ re, close

AUR helpers

2026-04-26T21:51:50Z

Alad: /* Search and build */ attempt to make the pat-aur-* entries look less bad

[[Category:Package management]]
[[Category:Software comparisons]]
[[de:AUR Hilfsprogramme]]
[[fr:AUR helpers]]
[[it:AUR helpers]]
[[ja:AUR ヘルパー]]
[[pt:AUR helpers]]
[[ru:AUR helpers]]
[[uk:AUR helpers]]
[[zh-hans:AUR 助手]]
{{Warning|1=AUR helpers are '''not supported''' by Arch Linux. You should become familiar with the [[Arch User Repository#Installing and upgrading packages|manual build process]] in order to be prepared to troubleshoot problems.}}

{{Notice|Please use the discussion page prior to making edits to this article: [[Talk:AUR helpers]].}}

AUR helpers automate usage of the [[Arch User Repository]]. In particular, they may automate the following tasks:

* searching for packages published on the AUR,
* resolving of dependencies between AUR packages,
* retrieve and build AUR packages,
* retrieve web content, such as user comments,
* submission of AUR packages.

[[Pacman]] only handles updates for pre-built packages in its repositories. AUR packages are redistributed in form of [[PKGBUILD]]s and need an AUR helper to automate the rebuild process. However, keep in mind that a rebuild of a package may be required when its shared library dependencies are updated, not only when the package itself is updated.

== Legend ==

The [[#Comparison tables]] columns have the following meaning:

;File review: Does not [[source]] the [[PKGBUILD]] file at all ''by default''; or alerts the user and offers the opportunity to inspect the {{ic|PKGBUILD}} file manually before it is sourced. Some helpers are known to source {{ic|PKGBUILD}}s before the user can inspect them, '''allowing malicious code to be executed'''.
;Diff view: Ability to view package differences on inspection. Besides the {{ic|PKGBUILD}} file, this includes changes to files such as {{ic|.install}} or {{ic|.patch}} files.
;Git clone: Uses {{man|1|git-clone}} by default to retrieve build files from the AUR.
;Reliable parser: Ability to handle complex packages by using the provided metadata ([[Aurweb RPC interface|RPC]]/{{ic|.SRCINFO}}) instead of the {{ic|PKGBUILD}} file [[w:Parsing#Parser|parsing]], such as {{AUR|aws-cli-git}}.
;Reliable solver: Ability to correctly solve and build complex dependency chains, such as {{AUR|liri-git-meta}}.
;Split packages: Ability to correctly build and install:
:* Multiple packages from the same package base, without rebuilding or reinstalling multiple times, such as {{AUR|clion}}.
:* Split packages which depend on a package from the same package base, such as {{AUR|samsung-unified-driver}}.
:* Split packages independently, such as {{AUR|nxproxy}} and {{AUR|nxagent}}.
;Shell completion: [[w:Command-line_completion|Tab completion]] is available for the listed [[shell]]s.

{{Note|
* ''Optional'' means that a feature is available, but only through a command-line argument or configuration option.
* ''Partial'' means that a feature is not fully implemented, or that it partially deviates from the given criteria.
}}

== Comparison tables ==

=== Search and download ===

{| class="wikitable sortable" style="text-align: center;"
! Name !! Written in !! File review !! Diff view !! Git clone !! Reliable parser !! Reliable solver !! Shell completion !! Specificity
|-
! {{AUR|auracle-git}}
| C++ || {{Yes}} || {{No}} || {{Yes|https://github.com/falconindy/auracle/commit/c73bbee}} || {{Yes}} || {{Yes}} || bash || {{L|print build order}}
|-
! {{AUR|repoctl}}
| Go || {{Yes}} || {{No}} || {{No}} || {{Yes|https://github.com/goulash/pacman/blob/master/aur/aur.go}} || {{-}} || bash, zsh, fish || {{L|[[local repository]]}}
|}

=== Search and build ===

{| class="wikitable sortable" style="text-align: center;"
! Name !! Written in !! File review !! Diff view !! Git clone !! Reliable parser !! Reliable solver !! Split packages !! Shell completion !! Specificity
|-
! {{AUR|aurutils}}
| Bash || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || bash, zsh || {{L|[[local repository]], local patch application, [[package signing]], [[clean chroot]] (via [[systemd-nspawn]])}}
|-
! {{AUR|pat-aur-host-git}} {{AUR|pat-aur-client-git}}
| Elvish || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || bash, zsh, elvish || {{L|[[local repository]], local patch application, [[package signing]], [[clean chroot]] (via [[bubblewrap]]), [[Wikipedia:Cross compiler|cross-compilation]]}}
|}

=== Pacman wrappers ===

{{Warning|{{man|8|pacman}} wrappers abstract the work of the package manager. They may (optionally or by default) introduce [[System maintenance#Avoid certain pacman commands|unsafe flags]], or other unexpected behavior leading to a defective system.}}

{{Note|The following pacman wrappers support batch (rather than on-demand) operations: {{AUR|pikaur}}, {{AUR|yay}}, {{AUR|aura}}, {{AUR|paru}}
}}

{| class="wikitable sortable" style="text-align: center;"
! Name !! Written in !! File review !! Diff view !! Git clone !! Reliable parser !! Reliable solver !! Split packages !! Unsafe flags !! Shell completion !! Specificity
|-
! {{AUR|aura}}
| Rust || {{No}} || {{Y|[https://github.com/aurapm/aura/blob/89bf702/aura/src/Aura/Pkgbuild/Records.hs Partial]}} || {{Yes|https://github.com/fosskers/aura/commit/ca9c38d}} || {{Yes|https://github.com/aurapm/aura/commit/7848e98}} || {{Yes|https://github.com/fosskers/aura/pull/479}} || {{Yes|https://github.com/fosskers/aura/pull/479}} || {{-}} || bash, fish, zsh || {{L|[[clean chroot]]}}
|-
! {{AUR|pakku}}
| Nim || {{Yes}} || {{Yes|https://github.com/kitsunyan/pakku/commit/396e9f4}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|[https://github.com/kitsunyan/pakku/wiki/Native-Pacman-Explanation -Sy]}} || bash, zsh || {{-}}
|-
! {{AUR|paru}}
| Rust|| {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|[https://github.com/Morganamilo/paru/blob/15394a7db80d045f038ea4d0ee94d00211070c96/man/paru.8#L543-L552 -Sy] [https://github.com/Morganamilo/paru/blob/32b75ac1cb7e0fccd21a0f795f25fd9fb1a14d8a/man/paru.conf.5#L110-L116 --ask]}} || bash, fish, zsh || {{L|[[local repository]], [[clean chroot]]}}
|-
! {{AUR|pikaur}}
| Python || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|[https://github.com/actionless/pikaur#pikaur -Sy]}} || bash, fish, zsh || {{L|[https://0pointer.net/blog/dynamic-users-with-systemd.html dynamic users]}}
|-
! {{AUR|trizen}}
| Perl || {{Yes}} || {{Yes}} ||{{Yes|https://github.com/trizen/trizen/commit/6fb0cc9}} || {{Yes|https://github.com/trizen/trizen/commit/7ab7ee5f}} || {{Yes}} || {{Y|[https://github.com/trizen/trizen/issues/46 Partial]}} || {{-}} || bash, fish, zsh || {{-}}
|-
! {{AUR|yay}}
| Go || {{Yes}} || {{Yes|https://github.com/Jguer/yay/pull/447}} || {{Yes|https://github.com/Jguer/yay/pull/297}} || {{Yes}} || {{Yes|https://github.com/Jguer/yay/pull/866}} || {{Yes}} || {{Y|[https://github.com/Jguer/yay/commit/ea5a94e --ask]}} || bash, fish, zsh || {{-}}
|}

== Graphical ==

{{Warning|Usage of graphical AUR helpers may lead to a defective system, for example through unattended [[partial upgrade]]s.}}
* {{App|Argon|GTK 3 pacman wrapper written in Python.|https://github.com/14mRh4X0r/arch-argon|{{AUR|argon}}}}
* {{App|Bauh|Qt5 Python application supporting AppImage, Debian and Arch packages (including AUR), Flatpak, Snap and native Web applications.|https://github.com/vinifmor/bauh|{{AUR|bauh}}}}
* {{App|Cylon|TUI pacman wrapper written in Bash.|https://github.com/gavinlyonsrepo/cylon|{{AUR|cylon}}}}
* {{App|Kalu|Systray notification icon using libalpm and [[PolicyKit]], with optional updater|https://github.com/Thulinma/kalu|{{AUR|kalu}}}}
* {{App|Octopi|Qt 5 pacman wrapper written in C++.|https://tintaescura.com/projects/octopi|{{AUR|octopi}}}}
* {{App|Pacsea|A fast, keyboard-friendly TUI for browsing and installing Arch and AUR packages written in Rust.|https://github.com/Firstp1ck/Pacsea|{{AUR|pacsea-bin}}}}
* {{App|Pacseek|A terminal user interface for searching and installing Arch Linux packages.|https://github.com/moson-mo/pacseek|{{AUR|pacseek}}}}
* {{App|Pamac|Standalone GTK 4 (or terminal) package manager written for Manjaro using {{man|3|libalpm}} with tray integration.|https://wiki.manjaro.org/index.php/Pamac|{{AUR|pamac-aur}}}}
* {{App|Pakku GUI|GTK 3 frontend for pakku written in Python.|https://gitlab.com/mrvik/pakku-gui|{{AUR|pakku-gui}}}}
* {{App|PkgBrowser|Qt 5 read-only browser for repository packages and AUR written in Python.|https://osdn.net/projects/pkgbrowser/|{{AUR|pkgbrowser}}}}
* {{App|SPM|A TUI wrapper for pacman and yay that makes package management visual and interactive.|https://github.com/adelmonte/Simple_Package_Manager|{{AUR|spm-arch}}}}
* {{App|Yup|Ncurses TUI pacman wrapper written in Go.|https://github.com/ericm/yup|{{AUR|yup}}}}

== Maintenance ==

* {{App|aur-out-of-date|Uses hoster APIs to check AUR packages for upstream changes.|https://github.com/simon04/aur-out-of-date|{{AUR|aur-out-of-date}}}}
* {{App|aurpublish|Helper script to manage and upload AUR packages using {{man|1|git-subtree}}. Uses {{man|5|githooks}} to verify the {{ic|PKGBUILD}} file integrity, generate the {{ic|.SRCINFO}} file automatically, and create a commit message template.|https://github.com/eli-schwartz/aurpublish|{{Pkg|aurpublish}}}}
* {{App|[[DeveloperWiki:Building in a clean chroot|devtools]]|Build packages in a clean environment ([[systemd-nspawn]] container) to ensure their correctness. Wrapped by {{AUR|aura}}, {{AUR|aurutils}}, {{AUR|clean-chroot-manager}} and {{AUR|paru}}.|https://gitlab.archlinux.org/archlinux/devtools|{{Pkg|devtools}}}}
* {{App|pkgoutofdate|Parses the source URL from {{ic|PKGBUILD}}s and tries to find new versions of packages by incrementing the version number and sending requests to the web server.|https://github.com/anatol/pkgoutofdate|{{AUR|pkgoutofdate-git}}}}
* {{App|repman|Command line tool to manage local and remote repositories.|https://gitlab.com/mipimipi/repman|{{AUR|repman-git}}}}

== Other ==

* {{App|aur-talk|Fetch and display AUR comments.|https://github.com/GermainZ/aur-talk|{{AUR|aur-talk-git}}}}
* {{App|aurvote-utils|A set of utilities for managing AUR votes.|https://github.com/jadenPete/aurvote-utils|{{AUR|aurvote-utils}}}}
* {{App|haskell-aur|[[Haskell]] library for accessing [[Aurweb RPC interface]].|https://hackage.haskell.org/package/aur|{{AUR|haskell-aur}}}}
* {{App|package-query|Tool for querying {{man|3|libalpm}} and the AUR.|https://github.com/archlinuxfr/package-query|{{AUR|package-query}}}}
* {{App|python3-aur|[[Python]] modules and helper utilities for accessing AUR package information and automating AUR interactions.|https://xyne.dev/projects/python3-aur|{{AUR|python3-aur}}}}
* {{App|raur|Rust library for accessing Aurweb RPC interface.|https://gitlab.com/davidbittner/raur||}}

== See also ==

* [https://www.debugpoint.com/arch-linux-gui-package-managers/ GUI Package Managers for Arch Linux] (DebugPoint, 2023) offers some screenshots and simple information about a few of the options mentioned in [[#Graphical]]

AUR helpers

2026-04-26T21:51:04Z

Alad: remove unmaintained/stale AUR helpers, see Talk:AUR helpers#Spring cleaning

[[Category:Package management]]
[[Category:Software comparisons]]
[[de:AUR Hilfsprogramme]]
[[fr:AUR helpers]]
[[it:AUR helpers]]
[[ja:AUR ヘルパー]]
[[pt:AUR helpers]]
[[ru:AUR helpers]]
[[uk:AUR helpers]]
[[zh-hans:AUR 助手]]
{{Warning|1=AUR helpers are '''not supported''' by Arch Linux. You should become familiar with the [[Arch User Repository#Installing and upgrading packages|manual build process]] in order to be prepared to troubleshoot problems.}}

{{Notice|Please use the discussion page prior to making edits to this article: [[Talk:AUR helpers]].}}

AUR helpers automate usage of the [[Arch User Repository]]. In particular, they may automate the following tasks:

* searching for packages published on the AUR,
* resolving of dependencies between AUR packages,
* retrieve and build AUR packages,
* retrieve web content, such as user comments,
* submission of AUR packages.

[[Pacman]] only handles updates for pre-built packages in its repositories. AUR packages are redistributed in form of [[PKGBUILD]]s and need an AUR helper to automate the rebuild process. However, keep in mind that a rebuild of a package may be required when its shared library dependencies are updated, not only when the package itself is updated.

== Legend ==

The [[#Comparison tables]] columns have the following meaning:

;File review: Does not [[source]] the [[PKGBUILD]] file at all ''by default''; or alerts the user and offers the opportunity to inspect the {{ic|PKGBUILD}} file manually before it is sourced. Some helpers are known to source {{ic|PKGBUILD}}s before the user can inspect them, '''allowing malicious code to be executed'''.
;Diff view: Ability to view package differences on inspection. Besides the {{ic|PKGBUILD}} file, this includes changes to files such as {{ic|.install}} or {{ic|.patch}} files.
;Git clone: Uses {{man|1|git-clone}} by default to retrieve build files from the AUR.
;Reliable parser: Ability to handle complex packages by using the provided metadata ([[Aurweb RPC interface|RPC]]/{{ic|.SRCINFO}}) instead of the {{ic|PKGBUILD}} file [[w:Parsing#Parser|parsing]], such as {{AUR|aws-cli-git}}.
;Reliable solver: Ability to correctly solve and build complex dependency chains, such as {{AUR|liri-git-meta}}.
;Split packages: Ability to correctly build and install:
:* Multiple packages from the same package base, without rebuilding or reinstalling multiple times, such as {{AUR|clion}}.
:* Split packages which depend on a package from the same package base, such as {{AUR|samsung-unified-driver}}.
:* Split packages independently, such as {{AUR|nxproxy}} and {{AUR|nxagent}}.
;Shell completion: [[w:Command-line_completion|Tab completion]] is available for the listed [[shell]]s.

{{Note|
* ''Optional'' means that a feature is available, but only through a command-line argument or configuration option.
* ''Partial'' means that a feature is not fully implemented, or that it partially deviates from the given criteria.
}}

== Comparison tables ==

=== Search and download ===

{| class="wikitable sortable" style="text-align: center;"
! Name !! Written in !! File review !! Diff view !! Git clone !! Reliable parser !! Reliable solver !! Shell completion !! Specificity
|-
! {{AUR|auracle-git}}
| C++ || {{Yes}} || {{No}} || {{Yes|https://github.com/falconindy/auracle/commit/c73bbee}} || {{Yes}} || {{Yes}} || bash || {{L|print build order}}
|-
! {{AUR|repoctl}}
| Go || {{Yes}} || {{No}} || {{No}} || {{Yes|https://github.com/goulash/pacman/blob/master/aur/aur.go}} || {{-}} || bash, zsh, fish || {{L|[[local repository]]}}
|}

=== Search and build ===

{| class="wikitable sortable" style="text-align: center;"
! Name !! Written in !! File review !! Diff view !! Git clone !! Reliable parser !! Reliable solver !! Split packages !! Shell completion !! Specificity
|-
! {{AUR|aurutils}}
| Bash || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || bash, zsh || {{L|[[local repository]], local patch application, [[package signing]], [[clean chroot]] (via [[systemd-nspawn]])}}
|-
! {{AUR|pat-aur-host-git}}/{{AUR|pat-aur-client-git}}
| Elvish || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || bash, zsh, elvish || {{L|[[local repository]], local patch application, [[package signing]], [[clean chroot]] (via [[bubblewrap]]), [[Wikipedia:Cross compiler|cross-compilation]]}}
|}

=== Pacman wrappers ===

{{Warning|{{man|8|pacman}} wrappers abstract the work of the package manager. They may (optionally or by default) introduce [[System maintenance#Avoid certain pacman commands|unsafe flags]], or other unexpected behavior leading to a defective system.}}

{{Note|The following pacman wrappers support batch (rather than on-demand) operations: {{AUR|pikaur}}, {{AUR|yay}}, {{AUR|aura}}, {{AUR|paru}}
}}

{| class="wikitable sortable" style="text-align: center;"
! Name !! Written in !! File review !! Diff view !! Git clone !! Reliable parser !! Reliable solver !! Split packages !! Unsafe flags !! Shell completion !! Specificity
|-
! {{AUR|aura}}
| Rust || {{No}} || {{Y|[https://github.com/aurapm/aura/blob/89bf702/aura/src/Aura/Pkgbuild/Records.hs Partial]}} || {{Yes|https://github.com/fosskers/aura/commit/ca9c38d}} || {{Yes|https://github.com/aurapm/aura/commit/7848e98}} || {{Yes|https://github.com/fosskers/aura/pull/479}} || {{Yes|https://github.com/fosskers/aura/pull/479}} || {{-}} || bash, fish, zsh || {{L|[[clean chroot]]}}
|-
! {{AUR|pakku}}
| Nim || {{Yes}} || {{Yes|https://github.com/kitsunyan/pakku/commit/396e9f4}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|[https://github.com/kitsunyan/pakku/wiki/Native-Pacman-Explanation -Sy]}} || bash, zsh || {{-}}
|-
! {{AUR|paru}}
| Rust|| {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|[https://github.com/Morganamilo/paru/blob/15394a7db80d045f038ea4d0ee94d00211070c96/man/paru.8#L543-L552 -Sy] [https://github.com/Morganamilo/paru/blob/32b75ac1cb7e0fccd21a0f795f25fd9fb1a14d8a/man/paru.conf.5#L110-L116 --ask]}} || bash, fish, zsh || {{L|[[local repository]], [[clean chroot]]}}
|-
! {{AUR|pikaur}}
| Python || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|[https://github.com/actionless/pikaur#pikaur -Sy]}} || bash, fish, zsh || {{L|[https://0pointer.net/blog/dynamic-users-with-systemd.html dynamic users]}}
|-
! {{AUR|trizen}}
| Perl || {{Yes}} || {{Yes}} ||{{Yes|https://github.com/trizen/trizen/commit/6fb0cc9}} || {{Yes|https://github.com/trizen/trizen/commit/7ab7ee5f}} || {{Yes}} || {{Y|[https://github.com/trizen/trizen/issues/46 Partial]}} || {{-}} || bash, fish, zsh || {{-}}
|-
! {{AUR|yay}}
| Go || {{Yes}} || {{Yes|https://github.com/Jguer/yay/pull/447}} || {{Yes|https://github.com/Jguer/yay/pull/297}} || {{Yes}} || {{Yes|https://github.com/Jguer/yay/pull/866}} || {{Yes}} || {{Y|[https://github.com/Jguer/yay/commit/ea5a94e --ask]}} || bash, fish, zsh || {{-}}
|}

== Graphical ==

{{Warning|Usage of graphical AUR helpers may lead to a defective system, for example through unattended [[partial upgrade]]s.}}
* {{App|Argon|GTK 3 pacman wrapper written in Python.|https://github.com/14mRh4X0r/arch-argon|{{AUR|argon}}}}
* {{App|Bauh|Qt5 Python application supporting AppImage, Debian and Arch packages (including AUR), Flatpak, Snap and native Web applications.|https://github.com/vinifmor/bauh|{{AUR|bauh}}}}
* {{App|Cylon|TUI pacman wrapper written in Bash.|https://github.com/gavinlyonsrepo/cylon|{{AUR|cylon}}}}
* {{App|Kalu|Systray notification icon using libalpm and [[PolicyKit]], with optional updater|https://github.com/Thulinma/kalu|{{AUR|kalu}}}}
* {{App|Octopi|Qt 5 pacman wrapper written in C++.|https://tintaescura.com/projects/octopi|{{AUR|octopi}}}}
* {{App|Pacsea|A fast, keyboard-friendly TUI for browsing and installing Arch and AUR packages written in Rust.|https://github.com/Firstp1ck/Pacsea|{{AUR|pacsea-bin}}}}
* {{App|Pacseek|A terminal user interface for searching and installing Arch Linux packages.|https://github.com/moson-mo/pacseek|{{AUR|pacseek}}}}
* {{App|Pamac|Standalone GTK 4 (or terminal) package manager written for Manjaro using {{man|3|libalpm}} with tray integration.|https://wiki.manjaro.org/index.php/Pamac|{{AUR|pamac-aur}}}}
* {{App|Pakku GUI|GTK 3 frontend for pakku written in Python.|https://gitlab.com/mrvik/pakku-gui|{{AUR|pakku-gui}}}}
* {{App|PkgBrowser|Qt 5 read-only browser for repository packages and AUR written in Python.|https://osdn.net/projects/pkgbrowser/|{{AUR|pkgbrowser}}}}
* {{App|SPM|A TUI wrapper for pacman and yay that makes package management visual and interactive.|https://github.com/adelmonte/Simple_Package_Manager|{{AUR|spm-arch}}}}
* {{App|Yup|Ncurses TUI pacman wrapper written in Go.|https://github.com/ericm/yup|{{AUR|yup}}}}

== Maintenance ==

* {{App|aur-out-of-date|Uses hoster APIs to check AUR packages for upstream changes.|https://github.com/simon04/aur-out-of-date|{{AUR|aur-out-of-date}}}}
* {{App|aurpublish|Helper script to manage and upload AUR packages using {{man|1|git-subtree}}. Uses {{man|5|githooks}} to verify the {{ic|PKGBUILD}} file integrity, generate the {{ic|.SRCINFO}} file automatically, and create a commit message template.|https://github.com/eli-schwartz/aurpublish|{{Pkg|aurpublish}}}}
* {{App|[[DeveloperWiki:Building in a clean chroot|devtools]]|Build packages in a clean environment ([[systemd-nspawn]] container) to ensure their correctness. Wrapped by {{AUR|aura}}, {{AUR|aurutils}}, {{AUR|clean-chroot-manager}} and {{AUR|paru}}.|https://gitlab.archlinux.org/archlinux/devtools|{{Pkg|devtools}}}}
* {{App|pkgoutofdate|Parses the source URL from {{ic|PKGBUILD}}s and tries to find new versions of packages by incrementing the version number and sending requests to the web server.|https://github.com/anatol/pkgoutofdate|{{AUR|pkgoutofdate-git}}}}
* {{App|repman|Command line tool to manage local and remote repositories.|https://gitlab.com/mipimipi/repman|{{AUR|repman-git}}}}

== Other ==

* {{App|aur-talk|Fetch and display AUR comments.|https://github.com/GermainZ/aur-talk|{{AUR|aur-talk-git}}}}
* {{App|aurvote-utils|A set of utilities for managing AUR votes.|https://github.com/jadenPete/aurvote-utils|{{AUR|aurvote-utils}}}}
* {{App|haskell-aur|[[Haskell]] library for accessing [[Aurweb RPC interface]].|https://hackage.haskell.org/package/aur|{{AUR|haskell-aur}}}}
* {{App|package-query|Tool for querying {{man|3|libalpm}} and the AUR.|https://github.com/archlinuxfr/package-query|{{AUR|package-query}}}}
* {{App|python3-aur|[[Python]] modules and helper utilities for accessing AUR package information and automating AUR interactions.|https://xyne.dev/projects/python3-aur|{{AUR|python3-aur}}}}
* {{App|raur|Rust library for accessing Aurweb RPC interface.|https://gitlab.com/davidbittner/raur||}}

== See also ==

* [https://www.debugpoint.com/arch-linux-gui-package-managers/ GUI Package Managers for Arch Linux] (DebugPoint, 2023) offers some screenshots and simple information about a few of the options mentioned in [[#Graphical]]

List of applications/Other

2026-04-26T21:43:36Z

Alad: /* Display servers */ add Xephyr

[[Category:Applications]]
[[Category:Lists of software]]
[[es:List of applications (Español)/Other]]
[[hu:List of applications (Magyar)/Other]]
[[ja:アプリケーション一覧/その他]]
[[pl:List of applications (Polski)/Other]]
[[zh-hans:List of applications/Other]]
{{List of applications navigation}}

== Organization ==

=== CalDAV/CardDAV servers ===

* {{App|Baïkal|A lightweight CalDAV+CardDAV server.|https://sabre.io/baikal/|{{AUR|baikal}}}}
* {{App|kcaldav|Simple, safe, minimal CalDAV server.|https://kristaps.bsd.lv/kcaldav|{{AUR|kcaldav}}}}
* {{App|[[Radicale]]|Free and Open-Source CalDAV and CardDAV Server.|https://radicale.org|{{Pkg|radicale}}}}
* {{App|xandikos|A lightweight yet complete CardDAV/CalDAV server that backs onto a Git repository.|https://www.xandikos.org|{{Pkg|xandikos}}}}

=== Personal information managers ===

These applications support time, task and contacts management.

* {{App|[[Evolution]]|Personal information management application that provides integrated mail, calendaring and address book functionality. Part of {{Grp|gnome-extra}}.|https://gitlab.gnome.org/GNOME/evolution/-/wikis/home|{{Pkg|evolution}}}}
* {{App|[[Wikipedia:Kontact|Kontact]]|Integrated solution to your personal information management. Part of {{Grp|kde-pim}}.|https://kontact.kde.org/|{{Pkg|kontact}}}}
* {{App|Merkuro|Calendar and contact application that allows you to manage your tasks, events and contacts. Part of {{Grp|kde-pim}}.|https://apps.kde.org/merkuro/|{{Pkg|merkuro}}}}
* {{App|Osmo|GTK personal organizer, which includes calendar, tasks manager and address book modules.|https://osmo-pim.sourceforge.net|{{Pkg|osmo}}}}
* {{App|[[Wikipedia:SeaMonkey#Mail|SeaMonkey Mail & Newsgroups]] with [[Wikipedia:Lightning (software)|Lightning]]|Extension to SeaMonkey that provides calendar and task support.|https://www.seamonkey-project.org/|{{AUR|seamonkey}}}}
* {{App|[[Thunderbird]]|A fully featured E-mail client formerly developed by Mozilla.|https://www.thunderbird.net|{{Pkg|thunderbird}}}}

=== Time management ===

==== Console ====

* {{App|Calcurse|Text-based ncurses calendar and scheduling system (supports CalDAV)|https://calcurse.org|{{Pkg|calcurse}}}}
* {{App|ccal|A console program which writes a calendar together with Chinese calendar to standard output.|https://ccal.chinesebay.com/ccal/ccal.htm|{{AUR|ccal}}}}
* {{App|khal|Command-line (non-interactive) and ncurses (interactive) calendar system (supports CalDAV)|https://github.com/pimutils/khal|{{Pkg|khal}}}}
* {{App|gcalcli|Command-line (non-interactive) Google Calendar for event management and agendas.|https://github.com/insanum/gcalcli|{{AUR|gcalcli}}}}
* {{App|mail2rem|Small script for importing ''.ics'' calendars from Maildir to Remind calendar.|https://github.com/esovetkin/mail2rem|{{AUR|mail2rem-git}}}}
* {{App|Pal|Very lightweight calendar with both interactive and non-interactive interfaces.|https://palcal.sourceforge.net/|{{AUR|pal}}}}
* {{App|pcal|A tool to create pdf calendars from pcal input which can be exported by some calendar programs.|https://sourceforge.net/projects/pcal/|{{AUR|pcal}}}}
* {{App|[[Remind]]|Highly sophisticated text-based calendaring and notification system.|https://dianne.skoll.ca/projects/remind/|{{Pkg|remind}}}}
* {{App|When|Simple personal calendar program.|http://lightandmatter.com/when/when.html|{{Pkg|when}}}}
* {{App|Wyrd|Text-based front-end to Remind, a calendar and alarm program used on UNIX and Linux computers.|https://gitlab.com/wyrd-calendar/wyrd|{{AUR|wyrd}}}}

==== Graphical ====

* {{App|Agenda|Calendar application built with MauiKit. Part of {{Grp|maui}}.|https://mauikit.org/apps/|{{Pkg|maui-agenda}}}}
* {{App|Calindori|Calendar application for Plasma Mobile.|https://apps.kde.org/calindori/|{{Pkg|calindori}}}}
* {{App|chinese-calendar|Chinese traditional calendar for Ubuntu Kylin.|https://launchpad.net/chinese-calendar/|{{Pkg|chinese-calendar}}}}
* {{App|CoreTime|Very simple Clock/Calendar application which shows a clock, supports alarms, reminders, a stop watch and a timer. Part of C-Suite.|https://cubocore.gitlab.io/|{{AUR|coretime}}}}
* {{App|Deepin Calendar|Calendar application for Deepin.|https://www.deepin.org/en/original/dde-calendar/|{{Pkg|deepin-calendar}}}}
* {{App|etmtk (Event and Task Manager)|Simple application with a "Getting Things Done!" approach to handling events, tasks, activities, reminders and projects.|https://people.duke.edu/~dgraham/ETMtk/|{{AUR|etmtk}}}}
* {{App|Gahshomar|Persian (Jalali/Farsi) calendar.|https://gahshomar.github.io/gahshomar/|{{AUR|gahshomar}}}}
* {{App|GNOME Calendar|Calendar application for GNOME. Part of {{Grp|gnome}}.|https://apps.gnome.org/Calendar/|{{Pkg|gnome-calendar}}}}
* {{App|[[Wikipedia:KAlarm|KAlarm]]|Personal alarm message, command and email scheduler, part of {{Grp|kde-pim}}.|https://apps.kde.org/kalarm/|{{Pkg|kalarm}}}}
* {{App|Kongress|Companion application for conferences made by KDE. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/kongress/|{{Pkg|kongress}}}}
* {{App|[[Wikipedia:Kontact#Organizer|KOrganizer]]|Calendar and scheduling program, part of {{Grp|kde-pim}}.|https://kontact.kde.org/components/korganizer|{{Pkg|korganizer}}}}
* {{App|Merkuro Calendar|Calendar application using Akonadi that supports both local and online calendars: Nextcloud, Google Calendar, Outlook, Caldav and more. Part of {{Grp|kde-pim}}.|https://apps.kde.org/merkuro.calendar/|{{Pkg|merkuro}}}}
* {{App|[[Nextcloud]] Calendar|Calendar app for Nextcloud.|https://github.com/nextcloud/calendar|{{Pkg|nextcloud-app-calendar}}}}
* {{App|Outspline|Extensible outliner with advanced time management features, supporting events with complex recurrence schemes.|https://kynikos.github.io/outspline/|{{AUR|outspline}}}}
* {{App|TkRemind|Sophisticated calendar and alarm program.|https://dianne.skoll.ca/projects/remind/|{{Pkg|remind}}}}

=== Timers ===

==== Countdown timers and stopwatch ====

* {{App|arttime|Clock, timer, pattern-based time manager, ASCII art viewer. Set a one-off, multiple, repeating, pattern-based timers.|https://github.com/poetaman/arttime|{{AUR|arttime-git}}}}
* {{App|Chess Clock|Simple application to provide time control for over-the-board chess games.|https://apps.gnome.org/Chessclock/|{{Pkg|chess-clock}}}}
* {{App|GNOME Clocks|Clocks application for GNOME, including alarm, stopwatch and timer functionality. Part of {{Grp|gnome}}.|https://apps.gnome.org/Clocks/|{{Pkg|gnome-clocks}}}}
* {{App|Hourglass|Simple time keeping application designed for elementary OS.|https://github.com/sgpthomas/hourglass|{{AUR|hourglass}}}}
* {{App|KClock|A convergent clock application for Plasma. It contains alarm, timer, stopwatch and timezone functionalities. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/kclock/|{{Pkg|kclock}}}}
* {{App|Kronometer|Stopwatch application for KDE.|https://apps.kde.org/kronometer/|{{Pkg|kronometer}}}}
* {{App|KTeaTime|Handy timer for steeping tea. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/kteatime/|{{Pkg|kteatime}}}}
* {{App|pystopwatch|Stopwatch written in Python with a clock and two countdown functions that can minimize to the tray.|https://xyne.dev/projects/pystopwatch/|{{AUR|pystopwatch}}}}
* {{App|snore|A program like sleep, but with feedback.|https://github.com/clamiax/snore|{{AUR|snore-git}}}}
* {{App|termdown|Countdown timer and stopwatch in your terminal.|https://github.com/trehn/termdown|{{Pkg|termdown}}}}

==== Break timers ====

* {{App|Break Timer|Keeps track of how much you are using the computer, and it reminds you to take regular breaks. Works only in GNOME.|https://wiki.gnome.org/Apps/BreakTimer|{{Pkg|gnome-break-timer}}}}
* {{App|RSI Break|Takes care of your health and regularly breaks your work to avoid repetitive strain injury (RSI) [https://bugs.kde.org/show_bug.cgi?id{{=}}422033 on Xorg].|https://apps.kde.org/rsibreak/|{{Pkg|rsibreak}}}}
* {{App|Safe Eyes|Tool to reduce and prevent repetitive strain injury (RSI).|https://slgobinath.github.io/SafeEyes/|{{AUR|safeeyes}}}}
* {{App|Work-break|Work and rest time balancer taking into account your current and today strain.|https://github.com/ShadoySV/work-break/|{{AUR|work-break}}}}
* {{App|[[Wikipedia:Workrave|Workrave]]|Program that assists in the recovery and prevention of RSI [https://bbs.archlinux.org/viewtopic.php?id{{=}}285701 on Xorg].|https://workrave.org/|{{Pkg|workrave}}}}

==== Pomodoro timers ====

See [[Wikipedia:Pomodoro Technique]] for an introduction.

* {{App|flow|Pomodoro app that blocks distractions while you work.|https://github.com/iamsergio/flow-pomodoro|{{AUR|flow-pomodoro}}}}
* {{App|Francis|App that uses the well-known pomodoro technique to help you get more productive. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/francis/|{{Pkg|francis}}}}
* {{App|Gnomato|Timer for the Pomodoro Technique.|https://github.com/diegorubin/gnomato|{{AUR|gnomato}}}}
* {{App|Pilorama|Eye-candy timeboxing tool written in QML|https://github.com/eplatonoff/pilorama|{{AUR|pilorama-git}}}}
* {{App|Pomodoro|Time management utility for GNOME based on the Pomodoro Technique.|https://gnomepomodoro.org/|{{AUR|gnome-shell-pomodoro}}}}
* {{App|Pomodoro-Logger|Pomodoro timer and logger with [[Wikipedia:Kanban board|Kanban board]] for task management and tracking.|https://github.com/zxch3n/PomodoroLogger|{{AUR|pomodoro-logger}}}}
* {{App|potato-c|A minimal and efficient pomodoro timer with server-client structure.|https://github.com/nimaaskarian/potato-c|{{AUR|potato-c}}}}
* {{App|Solanum|Pomodoro timer for the GNOME desktop.|https://apps.gnome.org/Solanum/|{{Pkg|solanum}}}}
* {{App|Tomate|Timer for the Pomodoro Technique.|https://github.com/eliostvs/tomate-gtk|{{AUR|tomate-gtk}}}}
* {{App|Tomighty|Desktop timer for the Pomodoro Technique.|https://tomighty.github.io|{{AUR|tomighty}}}}

=== Time trackers ===

* {{App|ActivityWatch|A self/local-hosted, cross-platform, client-server, privacy-focused active window tracker.|https://github.com/ActivityWatch/activitywatch|{{AUR|activitywatch-bin}}}}
* {{App|Hamster|Time tracking application that helps you to keep track on how much time you have spent during the day on activities you choose to track.|http://projecthamster.org/|{{Pkg|hamster-time-tracker}}}}
* {{App|Kapow|Punch clock to track time spent on projects.|https://gottcode.org/kapow/|{{AUR|kapow}}}}
* {{App|KTimeTracker|Todo management and time tracking application.|https://apps.kde.org/ktimetracker/|{{Pkg|ktimetracker}}}}
* {{App|Tider|Lightweight time tracking application (GTK)|https://github.com/naspeh/tider|{{AUR|tider-git}}}}
* {{App|Timenaut|Time tracker that tracks active windows and lets you sort them into categories. Based on the [https://electronjs.org/ Electron] platform.|https://timenaut.app/|{{AUR|timenaut-appimage}}}}
* {{App|Timetrack|Simple time-tracking app for GNOME.|https://gitlab.gnome.org/danigm/timetrack|{{AUR|timetrack}}}}
* {{App|Timewarrior|A command-line time-tracking application.|https://timewarrior.net/|{{Pkg|timew}}}}
* {{App|Wakatime|Open source plugins for metrics about your programming with intuitive web-interface.|https://wakatime.com/|{{AUR|wakatime}}}}

=== Task management ===

==== Console ====

* {{App|c3|A multi-platform TUI todo manager that extends calcurse's todo format to have a tree-like dependency structure, and even more! |https://github.com/nimaaskarian/c3|{{AUR|c3}}}}
* {{App|Cfait|Powerful, simple, elegant, and lightweight CalDAV task manager (TUI & GUI).|https://codeberg.org/trougnouf/cfait|{{AUR|cfait}}}}
* {{App|dijo|Scriptable, curses-based, digital habit tracker |https://github.com/nerdypepper/dijo|{{AUR|dijo}}}}
* {{App|Taskbook|Tasks, boards and notes for the command-line habitat.|https://github.com/klauscfhq/taskbook|{{AUR|taskbook}}}}
* {{App|Taskell|A command-line kanban board/task manager.|https://github.com/smallhadroncollider/taskell|{{AUR|taskell}}}}
* {{App|[[Wikipedia:Taskwarrior|Taskwarrior]]|Command-line To-do list application with support for lua customization and more.|https://taskwarrior.org/|{{Pkg|task}}}}
* {{App|todoman|Command-line To-do list manager (supports CalDAV)|https://github.com/pimutils/todoman|{{Pkg|todoman}}}}
* {{App|Todo.txt|Small command-line To-do manager.|https://github.com/todotxt/todo.txt-cli/|{{AUR|todotxt}}}}
* {{App|TuDu|Ncurses-based hierarchical To-do list manager with vim-like keybindings.|https://code.meskio.net/tudu/|{{AUR|tudu}}}}

==== Graphical ====

* {{App|Agenda|Simple, fast, no-nonsense to-do (task) list for elementary OS.|https://github.com/dahenson/agenda|{{AUR|agenda}}}}
* {{App|Cfait|Powerful, simple, elegant, and lightweight CalDAV task manager (TUI & GUI).|https://codeberg.org/trougnouf/cfait|{{AUR|cfait}}}}
* {{App|Effitask|Graphical task manager, based on the [http://todotxt.com/ Todo.txt] format.|https://github.com/sanpii/effitask|{{AUR|effitask}}}}
* {{App|Endeavour|Personal task manager for GNOME. Part of {{Grp|gnome-extra}}.|https://wiki.gnome.org/Apps/Todo|{{Pkg|endeavour}}}}
* {{App|Errands|Todo application for those who prefer simplicity.|https://apps.gnome.org/List/|{{Pkg|errands}}}}
* {{App|Go For It!|Simple and stylish productivity app, featuring a to-do list, merged with a timer that keeps your focus on the current task. To-do lists are stored in the [http://todotxt.com/ Todo.txt] format.|https://manuelkehl.de/projects/go-for-it/|{{AUR|go-for-it}}}}
* {{App|GTG|Personal tasks and TODO list items organizer for GNOME inspired by the [[Wikipedia:Getting Things Done|Getting Things Done (GTD)]] methodology.|https://github.com/getting-things-gnome/gtg|{{AUR|gtg}}}}
* {{App|KomoDo|Todo manager that uses todo.txt specification.|https://apps.kde.org/komodo/|{{Pkg|komodo}}}}
* {{App|[[Nextcloud]] Tasks|Tasks app for Nextcloud.|https://github.com/nextcloud/tasks|{{Pkg|nextcloud-app-tasks}}}}
* {{App|Planner|Task manager with Todoist support.|https://useplanner.com/|{{AUR|planify}}}}
* {{App|ptask|GTK task manager based on [[Wikipedia:Taskwarrior|Taskwarrior]].|https://wpitchoune.net/ptask/|{{AUR|ptask}}}}
* {{App|sleek|todo.txt app with modern GUI. Based on the [https://electronjs.org/ Electron] platform.|https://github.com/ransome1/sleek/|{{AUR|sleek}}}}
* {{App|TickTick|Is a simple and effective to-do list and task manager app with seamless cloud synchronization across all your devices|https://ticktick.com/|{{AUR|ticktick}}}}
* {{App|Zanshin|To-do management application for KDE. Part of {{Grp|kde-pim}}.|https://apps.kde.org/zanshin/|{{Pkg|zanshin}}}}

=== Contacts management ===

==== Console ====

* {{App|Abook|Text-based contacts manager designed for use with mutt.|https://abook.sourceforge.net/|{{AUR|abook}}}}
* {{App|Khard|Command-line addressbook that is able to sync with CardDAV-servers.|https://github.com/scheibler/khard|{{Pkg|khard}}}}

==== Graphical ====

* {{App|Addresses|Address book application for GNUstep.|https://www.nongnu.org/gap/addresses/|{{AUR|addresses.app}}}}
* {{App|Communicator|Integrated address book and dialer application features the search for and view of contacts, edit contact details, and make new contacts, favorites, and dialer pad. Part of {{Grp|maui}}.|https://mauikit.org/apps/communicator/|{{Pkg|communicator}}}}
* {{App|GNOME Contacts|Contacts manager for GNOME. Part of {{Grp|gnome}}.|https://apps.gnome.org/Contacts/|{{Pkg|gnome-contacts}}}}
* {{App|KAddressBook|Address book manager for KDE. Part of {{Grp|kde-pim}}.|https://kontact.kde.org/components/kaddressbook|{{Pkg|kaddressbook}}}}
* {{App|LDAP Administration Tool|Browse LDAP-based directories and add/edit/delete entries contained within.|https://sourceforge.net/projects/ldap-at/|{{AUR|lat}}}}
* {{App|Merkuro Contacts|Address book using Akonadi. Part of {{Grp|kde-pim}}.|https://apps.kde.org/merkuro.contact/|{{Pkg|merkuro}}}}
* {{App|[[Nextcloud]] Contacts|Contacts app for Nextcloud.|https://github.com/nextcloud/contacts|{{Pkg|nextcloud-app-contacts}}}}
* {{App|[[phpLDAPadmin]]|LDAP client webapp. Its hierarchical tree-viewer and advanced search functionality make it intuitive to browse and administer your LDAP directory.|https://phpldapadmin.sourceforge.net/|{{Pkg|phpldapadmin}}}}
* {{App|[[Thunderbird]] with [https://gitlab.com/CardBook/CardBook CardBook] extension|address book based on the CardDAV and vCard standards.|https://gitlab.com/CardBook/CardBook|{{Pkg|thunderbird}}}}

=== Financial management ===

See also [[Wikipedia:Comparison of accounting software]].

==== Console ====

* {{App|Beancount|A double-entry bookkeeping computer language that lets you define financial transaction records in a text file, read them in memory, generate a variety of reports from them, and provides a web interface.|https://beancount.github.io/|{{AUR|beancount}}}}
* {{App|hledger|An accounting program for tracking money, time, or any other commodity, using double-entry accounting and a simple, editable file format. hledger is inspired by and largely compatible with ledger.|https://hledger.org/|{{Pkg|hledger}}}}
* {{App|[[Ledger]]|Ledger is a powerful, double-entry accounting system that is accessed from the UNIX command-line.|https://www.ledger-cli.org/|{{Pkg|ledger}}}}

==== Graphical ====

* {{App|Eqonomize!|Cross-platform personal accounting software, with focus on efficiency and ease of use for the small household economy.|https://eqonomize.github.io/|{{AUR|eqonomize}}}}
* {{App|[[ERPNext]]|Free and open source Enterprise Resource Planning (ERP).|https://github.com/frappe/erpnext|{{AUR|erpnext}}}}
* {{App|[[Wikipedia:GnuCash|GnuCash]]|Financial application that implements a double-entry book-keeping system with features for small business accounting.|https://www.gnucash.org/|{{Pkg|gnucash}}}}
* {{App|Grisbi|Personal finance system which manages third party, expenditure and receipt categories, as well as budgetary lines, financial years, and other information that makes it suitable for associations.|https://www.grisbi.org/|{{AUR|grisbi}}}}
* {{App|[[Wikipedia:HomeBank|HomeBank]]|Easy to use finance manager that can analyse your personal finance in detail using powerful filtering tools and graphs.|http://homebank.free.fr/|{{Pkg|homebank}}}}
* {{App|[[Wikipedia:KMyMoney|KMyMoney]]|Personal finance manager that operates in a similar way to [[Wikipedia:Microsoft Money|Microsoft Money]]. It supports different account types, categorisation of expenses and incomes, reconciliation of bank accounts and import/export to the “QIF” file format.|https://kmymoney.org/|{{Pkg|kmymoney}}}}
* {{App|Kresus|Self-hosted personal finance management software. It automatically retrieves every day all your new bank transactions and lets you categorize them, study them through charts and establish a budget.|https://kresus.org/en/|{{Pkg|kresus}}}}
* {{App|Manager|Proprietary accounting software for small business.|https://www.manager.io/|{{AUR|manager-accounting}}}}
* {{App|Money Manager EX|An easy-to-use personal finance suite|https://www.moneymanagerex.org/|{{AUR|moneymanagerex}}}}
* {{App|[[Odoo]]|Open source ERP system purely in Python. Previously known as OpenERP.|https://www.odoo.com/|{{AUR|odoo-venv}}}}
* {{App|Skrooge|Personal finances manager for the KDE desktop.|https://skrooge.org/|{{Pkg|skrooge}}}}

=== Cryptocurrency ===

* {{App|Atomic Wallet|Manage your Bitcoin, Ethereum, XRP, Litecoin, XLM, and over 300 other coins and tokens. |https://atomicwallet.io/|{{AUR|atomicwallet}}}}
* {{App|Bitcoin Core|Connect to the Bitcoin P2P Network.|https://bitcoincore.org/|{{Pkg|bitcoin-qt}}}}
* {{App|Cake Wallet|Multicurrency wallet.|https://github.com/cake-tech/cake_wallet|{{AUR|cake-wallet-bin}}}}
* {{App|Coinomi|Securely store, manage and exchange Bitcoin, Ethereum, and more than 1,770 other blockchain assets.|https://www.coinomi.com/|{{AUR|coinomi-wallet-bin}}}}
* {{App|Cointop|Terminal based application for tracking cryptocurrencies.|https://cointop.sh/|{{AUR|cointop}}}}
* {{App|Dogecoin Core|Dogecoin Core wallet, Allows you to connect to the Dogecoin P2P Network.|https://dogecoin.com/|{{AUR|dogecoin-qt}}, {{AUR|multidoge}}}}
* {{App|Electrum|Lightweight Bitcoin client.|https://electrum.org/|{{Pkg|electrum}}}}
* {{App|Exodus|All-in-one proprietary application to secure, manage, and exchange blockchain assets. Based on the [https://electronjs.org/ Electron] platform.|https://www.exodus.io/|{{AUR|exodus}}}}
* {{App|Feather Wallet|Lightweight Monero wallet.|https://featherwallet.org/|{{AUR|feather-wallet}}}}
* {{App|Monero|Monero wallet.|https://getmonero.org/|{{Pkg|monero-gui}}, {{Pkg|monero}}}}
* {{App|Sparrow Wallet|Advanced Bitcoin client.|https://sparrowwallet.com/|{{AUR|sparrow-wallet}}}}

=== Project management ===

See also [[Wikipedia:Comparison of project management software]].

* {{App|[[Wikipedia:Calligra Plan|Calligra Plan]]|Project management application, which is intended for managing moderately large projects with multiple resources.|https://calligra.org/components/plan/|{{Pkg|calligra-plan}}}}
* {{App|[[Wikipedia:GanttProject|GanttProject]]|Project scheduling application featuring gantt chart, resource management, calendaring.|https://www.ganttproject.biz/|{{AUR|ganttproject}}}}
* {{App|[[Notion-app]]|A note-taking software and project management software that is used for note-taking, task management, project management, knowledge management, and personal knowledge management. |https://www.notion.so/|{{AUR|notion-app-electron}}}}
* {{App|Planner|Project management application for GNOME.|https://wiki.gnome.org/Apps/Planner|{{Pkg|planner}}}}
* {{App|[[Wikipedia:ProjectLibre|ProjectLibre]]|Project management software alternative to [[Wikipedia:Microsoft Project|Microsoft Project]].|https://www.projectlibre.com/product/projectlibre-open-source{{Dead link|2025|08|15|status=404}}|{{AUR|projectlibre}}}}
* {{App|[[Wikipedia:TaskJuggler|TaskJuggler]]|Modern and powerful project management tool. Its new approach to project planning and tracking is more flexible and superior to the commonly used Gantt chart editing tools.|https://taskjuggler.org/|{{AUR|taskjuggler}}}}

=== Bookmark management ===

* {{App|KEditBookmarks|Bookmark organizer and editor. Part of {{Grp|kde-utilities}}.|https://invent.kde.org/utilities/keditbookmarks|{{Pkg|keditbookmarks}}}}
* {{App|Read It Later|Simple Wallabag client.|https://gitlab.gnome.org/World/read-it-later|{{Pkg|read-it-later}}}}

=== Recipe management ===

* {{App|Gourmand|Simple but powerful recipe-managing application.|https://github.com/GourmandRecipeManager/gourmand|{{AUR|gourmand}}}}
* {{App|Recipes|Recipe management application for GNOME. Part of {{Grp|gnome-extra}}.|https://wiki.gnome.org/Apps/Recipes|{{Pkg|gnome-recipes}}}}

=== Travel management ===

See also [[List of applications/Science#Navigation and routing]].

* {{App|Itinerary|Digital travel assistant with a priority on protecting your privacy. Part of {{Grp|kde-pim}}.|https://apps.kde.org/itinerary/|{{Pkg|itinerary}}}}

=== Health management ===

* {{App|Health|Health tracking app for the GNOME desktop.|https://apps.gnome.org/Health/|{{Pkg|health}}}}

== Education ==

See also [[List of games#Education]].

* {{App|Artikulate|Pronunciation trainer that helps improving and perfecting a learner's pronunciation skills for a foreign language. Part of {{Grp|kde-education}}.|https://apps.kde.org/artikulate/|{{Pkg|artikulate}}}}
* {{App|Fretboard|Look up guitar chords.|https://apps.gnome.org/Fretboard/|{{Pkg|fretboard}}}}
* {{App|Kalm|Teach you different breathing techniques. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/kalm/|{{Pkg|kalm}}}}
* {{App|[[Moodle]]|Open-source software learning management system.|https://moodle.org/|{{AUR|moodle}}}}
* {{App|[[Wikipedia:OpenBoard|OpenBoard]]|Interactive whiteboard software for schools and universities.|https://openboard.ch/index.en.html|{{AUR|openboard}}}}
* {{App|Wike|Wikipedia reader for the GNOME desktop.|https://apps.gnome.org/Wike/|{{Pkg|wike}}}}
* {{App|Wildcard|Provides a simple interface to test/practice regular expressions.|https://gitlab.gnome.org/World/Wildcard|{{Pkg|wildcard}}}}

=== Flashcards ===

See also [[Wikipedia:List of flashcard software]].

* {{App|[[Anki]]|Intelligent spaced-repetition memory training program.|https://apps.ankiweb.net/|{{Pkg|anki}}}}
* {{App|jVLT|Vocabulary learning tool.|https://www.linuxlinks.com/jVLT/|{{AUR|jvlt}}}}
* {{App|KWordQuiz|Tool that gives you a powerful way to master new vocabularies. Part of {{Grp|kde-education}}.|https://apps.kde.org/kwordquiz/|{{Pkg|kwordquiz}}}}
* {{App|[[Mnemosyne]]|Flash-card tool which optimizes your learning process.|https://mnemosyne-proj.org/|{{AUR|mnemosyne}}}}
* {{App|Parley|Program to help you memorize things. It uses the spaced repetition learning method, also known as flash cards. Part of {{Grp|kde-education}}.|https://apps.kde.org/parley/|{{Pkg|parley}}}}
* {{App|Pauker|Flash card based learning tool using shortterm and longterm memory training.|https://pauker.sourceforge.net/|{{AUR|pauker}}}}
* {{App|StudyFlash|Learn flashcards inside your terminal|https://github.com/Alone2/studyFlash|{{AUR|studyflash}}}}

=== Touch typing ===

==== Console ====

* {{App|Dvorak 7min|Simple ncurses-based typing tutor for those trying to become fluent with the Dvorak keyboard layout.|https://github.com/yaychris/dvorak7min|{{AUR|dvorak7min}}}}
* {{App|GNU Typist|Universal typing tutor.|https://www.gnu.org/software/gtypist/|{{AUR|gtypist}}}}
* {{App|psani-profi|Program that will teach you touchtyping (Czech).|https://www.sallyx.org/sally/psani-vsemi-deseti/|{{AUR|psani-profi}}}}
* {{App|Typespeed|Test your typing speed, and get your fingers' CPS.|https://typespeed.sourceforge.net/|{{AUR|typespeed}}}}
* {{App|typiskt|touchtype training in the terminal (Bash).|https://github.com/budlabs/typiskt|{{AUR|typiskt}}}}

==== Graphical ====

* {{App|Klavaro|Teaching touch typing that intends to be keyboard and language independent.|https://klavaro.sourceforge.io/|{{Pkg|klavaro}}}}
* {{App|[[Wikipedia:KTouch|KTouch]]|Program to learn and practice touch typing. Part of {{Grp|kde-education}}.|https://apps.kde.org/ktouch/|{{Pkg|ktouch}}}}
* {{App|TIPP10|Intelligent touch typing tutor.|https://www.tipp10.com/|{{Pkg|tipp10}}}}
* {{App|TypingTest|Typing test desktop program with a large amount of customization.|https://github.com/laelath/typingtest|{{AUR|typingtest-git}}}}

== Accessibility ==

See [[Accessibility]] for tips on operating the desktop and [[:Category:Accessibility]] for all available articles. See also [[List of applications/Utilities#On-screen keyboards|On-screen keyboards]].

=== Speech synthesizers ===

See also [[Wikipedia:Comparison of speech synthesizers]] and [https://tools.wmflabs.org/tts-comparison/ listening comparison of the different engines].

* {{App|Ekho|Chinese text-to-speech (TTS) software for Cantonese, Mandarin, Zhaoan Hakka, Tibetan, Ngangien and Korean.|https://eguidedog.net/ekho.php|{{AUR|ekho}}}}
* {{App|eSpeak|Compact speech synthesizer for more than 50 languages.|https://espeak.sourceforge.net/|{{AUR|espeak}}}}
* {{App|[[Wikipedia:eSpeakNG|eSpeak NG]]|Fork of eSpeak (due to inactivity of original maintainer).|https://github.com/espeak-ng/espeak-ng|{{Pkg|espeak-ng}}}}
* {{App|[[Festival]]|General framework for building speech synthesis systems as well as including examples of various modules. As a whole it offers full text to speech.|https://www.cstr.ed.ac.uk/projects/festival/|{{Pkg|festival}}}}
* {{App|Flite|Lightweight speech synthesis engine.|http://festvox.org/flite/|{{Pkg|flite}}}}
* {{App|Gespeaker|GTK frontend for espeak. It allows you to play a text in many languages with settings for voice, pitch, volume and speed.|https://muflone.com/gespeaker/english/|{{AUR|gespeaker}}}}
* {{App|KMouth|Speech synthesizer frontend which enables persons that cannot speak to let their computer speak. Part of {{Grp|kde-accessibility}}.|https://apps.kde.org/kmouth/|{{Pkg|kmouth}}}}
* {{App|MaryTTS|Multilingual text-to-speech synthesis platform written in Java.|https://marytts.github.io/|{{AUR|marytts}}}}
* {{App|[[Mbrola|MBROLA]]|Proprietary phonemes-to-audio program which supports more than 70 languages. Mbrola-voices can also be used with eSpeak.|http://tcts.fpms.ac.be/synthesis/mbrola.html|{{AUR|mbrola}}}}
* {{App|Mimic|Text-to-speech voice synthesis from the Mycroft project (based on Flite).|https://mimic.mycroft.ai/|{{AUR|mimic}}}}
* {{App|Open JTalk|Japanese text-to-speech synthesis system.|https://sourceforge.net/projects/open-jtalk/|{{AUR|open-jtalk}}}}
* {{App|Orca|Screen reader for individuals who are blind or visually impaired, using eSpeak (via Speech Dispatcher). Part of {{Grp|gnome}}.|https://wiki.gnome.org/Projects/Orca|{{Pkg|orca}}}}
* {{App|piper|A fast, local neural text to speech system.|https://github.com/rhasspy/piper|{{AUR|piper-tts-bin}}}}
* {{App|[[RHVoice]]|Cross-platform (including Android) text-to-speech from a blind Russian-speaking developer, based on [https://hts.sp.nitech.ac.jp HTS] (ru, ka, uk, ky, tt, en, pt, eo)|https://github.com/RHVoice/RHVoice|{{Pkg|rhvoice}}}}
* {{App|[[Simple Orca Plugin System|SOPS]]|Provides a simple way to write custom plugins for screen reader Orca.|https://github.com/chrys87/simple-orca-plugin-system|{{AUR|simpleorcapluginsystem}}}}
* {{App|[[Speech dispatcher]]|Common interface to speech synthesis. It has backends for eSpeak, Festival, and a few other speech synthesizers.|https://freebsoft.org/speechd|{{Pkg|speech-dispatcher}}}}

=== Speech recognition ===

See also [[Wikipedia:Speech recognition software for Linux]].

* {{App|[[Wikipedia:Julius (software)|Julius]]|Large vocabulary continuous speech recognition engine.|https://github.com/julius-speech/julius|{{AUR|julius-speech}}}}
* {{App|[[Wikipedia:Kaldi (software)|Kaldi]]|Speech recognition toolkit.|https://github.com/kaldi-asr/kaldi|{{AUR|kaldi}}}}
* {{App|Kaylee|Somewhat fancy voice command recognition program that performs actions when a user speaks loosely preset sentences.|https://github.com/Ratfink/kaylee|{{AUR|kayleevc}}}}
* {{App|[[Wikipedia:Mycroft (software)|Mycroft]]|Hackable voice assistant.|https://github.com/MycroftAI/mycroft-core|{{AUR|mycroft-core}}}}
* {{App|nerd-dictation|Light weight manually activated dictation using the VOSK-API.|https://github.com/ideasman42/nerd-dictation|{{AUR|nerd-dictation-git}}}}
* {{App|Numen|Voice control for handsfree computing.|https://sr.ht/~geb/numen/|{{AUR|numen}}}}

=== Screen magnifiers ===

* {{App|boomer|Zoomer application for Linux.|https://github.com/tsoding/boomer|{{AUR|boomer-git}}}}
* {{App|KMag|Small KDE utility to magnify a part of the screen. Part of {{Grp|kde-accessibility}}.|https://apps.kde.org/kmag/|{{Pkg|kmag}}}}
* {{App|Magnus|Very simple desktop magnifier, showing the area around the mouse pointer in a separate window magnified two, three, four, or five times.|https://kryogenix.org/code/magnus/|{{AUR|magnus}}}}
* {{App|Virtual Magnifying Glass|Simple, customizable and easy-to-use screen magnification tool.|https://magnifier.sourceforge.net/|{{AUR|vmg}}}}
* {{App|xzoom|Zoom, rotate and mirror area of X display.|https://www.ibiblio.org/pub/Linux/X11/libs/!INDEX.short.html|{{AUR|xzoom}}}}

=== On-screen annotation ===

* {{App|Gromit-MPX|Tool to make annotations on the screen.|https://github.com/bk138/gromit-mpx|{{AUR|gromit-mpx}}}}
* {{App|Pylote|Tool to draw on the screen.|http://pascal.peter.free.fr/pylote-en.html|{{AUR|pylote-git}}}}
* {{App|Screenkey|Tool to display pressed keys.|https://www.thregr.org/~wavexx/software/screenkey/|{{Pkg|screenkey}}}}
* {{App|Show Me The Key|A screenkey alternative that works under Wayland via libinput|https://showmethekey.alynx.one|{{Pkg|showmethekey}}}}

=== Mouse ===

* {{App|Easystroke|Use mouse gestures to initiate commands and hotkeys.|https://github.com/thjaeger/easystroke/wiki|{{AUR|easystroke}}}}
* {{App|KMouseTool|Clicks the mouse whenever the mouse cursor pauses briefly. It was designed to help those with repetitive strain injuries, for whom pressing buttons hurts. Part of {{Grp|kde-accessibility}}.|https://apps.kde.org/kmousetool/|{{Pkg|kmousetool}}}}
* {{App|Mousetweaks|Accessibility enhancements for pointing devices.|https://wiki.gnome.org/Projects/Mousetweaks|{{Pkg|mousetweaks}}}}

== Display servers ==

* {{App|Arcan|A development framework for anything between user interfaces for specialised embedded applications, and a standalone desktop environment.|https://arcan-fe.com/|{{AUR|arcan}}}}
* {{App|[[Xorg]]|The public, open-source implementation of the [[Wikipedia:X Window System|X Window System]] (commonly X11, or X).|https://www.x.org|{{Pkg|xorg}}}}
* {{App|[[Xephyr]]|A nested X server that runs as an X application.|https://freedesktop.org/wiki/Software/Xephyr/|{{Pkg|xorg-server-xephyr}}}}
* {{App|Xlibre|A fork of Xorg that is [[Intel graphics#With the modesetting driver 2|tear free]] by default, supports client isolation and fixes several upstream bugs.|https://github.com/X11Libre |{{AUR|xlibre-xserver}}}}
* {{App|[[Wayland]]|A newer, alternative display server protocol with several [[Wayland#Compositors|compositors]] to choose from. Its advantages over Xorg are enhanced security features, more efficient handling of modern graphics tasks and active development while retaining compatibility through [[Xwayland]].|https://wayland.freedesktop.org/|{{Pkg|wayland}}}}

== Display managers ==

See the main article: [[Display manager#List of display managers]].

== Desktop environments ==

See the main article: [[Desktop environment#List of desktop environments]].

=== Window managers ===

==== Console ====

See also [[List of applications/Utilities#Terminal multiplexers]], which offer some of the functions of window managers for the console.

* {{App|twin|Text-mode window manager.|https://sourceforge.net/projects/twin/|{{AUR|twin}}}}
* {{App|Wmutils|A set of tools for X windows manipulation.|https://github.com/wmutils/core|{{AUR|wmutils-git}}}}

==== Graphical ====

See the main article: [[Window manager#List of window managers]].

==== Composite managers ====

See the main article: [[Xorg#List of composite managers]].

=== Wayland compositors ===

See the main article: [[Wayland#Compositors]].

=== Window tilers ===

* {{App|QuickTile|Lightweight standalone alternative to Compiz Grid plugin.|http://ssokolow.com/quicktile/|{{AUR|quicktile-git}}}}
* {{App|wumwum|The Window Manager manager. It can turn emwh compliant window managers into a tiling window manager while retaining all initial functionalities.|https://wumwum.sourceforge.net/|{{AUR|wumwum}}}}

=== Desktop shells ===

Desktop shells provide a graphical shell layer on top of a window manager or compositor, including panels, launchers, and other desktop components. They can be used to build a desktop-like experience, but do not constitute full desktop environments.

* {{App|AGS|Aylur's GTK Shell is a framework for building custom desktop shells using GTK.|https://aylur.github.io/ags/|{{AUR|aylurs-gtk-shell}}}}
* {{App|DankMaterialShell|Desktop shell for Wayland compositors, built with Quickshell and Go.|https://github.com/AvengeMedia/DankMaterialShell|{{Pkg|dms-shell}}}}
* {{App|eww|ElKowar's Wacky Widgets is a standalone widget system made in Rust that allows you to implement your own, custom widgets in any window manager.|https://github.com/elkowar/eww|{{AUR|eww}}}}
* {{App|liquidshell|Basic desktop shell for Xorg, an alternative to plasmashell, implemented using QtWidgets. It provides a bottom panel, a desktop wallpaper and desktop widgets.|https://apps.kde.org/liquidshell/|{{Pkg|liquidshell}}}}
* {{App|Noctalia|Minimal desktop shell for Wayland compositors, built on Quickshell.|https://noctalia.dev/|{{AUR|noctalia-shell}}}}
* {{App|[[nwg-shell]]|Modular GTK3-based shell for Sway and Hyprland compositors.|https://nwg-piotr.github.io/nwg-shell/|{{Pkg|nwg-shell}}}}
* {{App|wf-shell|Shell components for the Wayfire compositor.|https://github.com/WayfireWM/wf-shell|{{Pkg|wf-shell}}}}

=== Taskbars ===

See also [[Wikipedia:Taskbar]].

==== For both Wayland and Xorg ====
* {{App|[[Cairo-Dock]]|Highly customizable dock and launcher application.|https://www.glx-dock.org/|{{Pkg|cairo-dock}}}}
* {{App|LXQt Panel|Qt-based taskbar, part of the [[LXQt]] desktop.|https://github.com/lxqt/lxqt-panel|{{Pkg|lxqt-panel}}}}
* {{App|Xfce Panel|Panel included in the [[Xfce]] desktop.|https://docs.xfce.org/xfce/xfce4-panel/start|{{Pkg|xfce4-panel}}}}
* {{App|yambar|A modular and lightweight status bar for X11 and Wayland that goes to great lengths to be both CPU and battery efficient.|https://codeberg.org/dnkl/yambar|{{AUR|yambar}}}}

==== For Wayland only ====
* {{App|Dash to Panel|A fully customizable icon taskbar for {{Pkg|gnome-shell}}. Moves the dash into the GNOME main panel, similar to KDE Plasma and Windows 10.|https://github.com/home-sweet-gnome/dash-to-panel|{{Pkg|gnome-shell-extension-dash-to-panel}}}}
* {{App|Ironbar|A customisable and feature-rich GTK4 status bar for Wayland compositors, written in Rust.|https://github.com/JakeStanger/ironbar|{{Pkg|ironbar}}}}
* {{App|nwg-dock|GTK-based dock for Sway and Hyprland compositors.|https://github.com/nwg-piotr/nwg-dock|For Sway: {{Pkg|nwg-dock}}, for Hyprland: {{Pkg|nwg-dock-hyprland}}}}
* {{App|nwg-panel|GTK3-based panel for Sway and Hyprland compositors.|https://github.com/nwg-piotr/nwg-panel|{{Pkg|nwg-panel}}}}
* {{App|SFWBar|Flexible taskbar application for Wayland compositors, designed with a stacking layout in mind.|https://github.com/LBCrion/sfwbar|{{AUR|sfwbar}}}}
* {{App|Waybar|A customizable status bar for wlroots-based Wayland compositors.|https://github.com/Alexays/Waybar/|{{Pkg|waybar}}}}

==== For Xorg only ====
* {{App|[[Bmpanel]]|Lightweight, NETWM compliant panel.|https://github.com/nsf/bmpanel2|{{AUR|bmpanel2}}}}
* {{App|DockbarX|Standalone, dock-style taskbar for X11 with window grouping.|https://github.com/xuzhen/dockbarx|{{AUR|dockbarx}}}}
* {{App|[[fbpanel]]|Lightweight, NETWM compliant desktop panel.|https://aanatoly.github.io/fbpanel/|{{AUR|fbpanel}}}}
* {{App|[[Wikipedia:GNOME Panel|GNOME Panel]]|Panel included in the [[GNOME Flashback]] desktop.|https://wiki.gnome.org/Projects/GnomePanel|{{Pkg|gnome-panel}}}}
* {{App|[[Lemonbar]]|A featherweight status bar based on XCB. Provides UTF-8 support, background and foreground colors, text alignment, and not much more.|https://github.com/LemonBoy/bar|{{AUR|lemonbar}}}}
* {{App|LXPanel|Lightweight X11 desktop panel and part of the [[LXDE]] desktop.|https://github.com/lxde/lxpanel|{{Pkg|lxpanel}}}}
* {{App|MATE Panel|Panel included in the [[MATE]] desktop.|https://github.com/mate-desktop/mate-panel/|{{Pkg|mate-panel}}}}
* {{App|plainPanel|A lightweight panel written in Qt. It aims to be a desktop environment, but for now, it includes just a panel and a control center.|https://plainDE.github.io/|{{AUR|plainde-meta}}}}
* {{App|[[Plank]]|Elegant, simple, clean dock from [[Pantheon]] desktop environment.|https://launchpad.net/plank|{{Pkg|plank}}}}
* {{App|[[Polybar]]|A fast and easy-to-use tool for creating status bars.|https://github.com/jaagr/polybar|{{Pkg|polybar}}}}
* {{App|[[Tint2]]|Simple panel/taskbar developed specifically for Openbox.|https://gitlab.com/o9000/tint2|{{Pkg|tint2}}}}
* {{App|Vala Panel|GTK3 panel for compositing window managers.|https://gitlab.com/vala-panel-project/vala-panel|{{AUR|vala-panel}}}}
* {{App|[[xmobar]]|A lightweight, text-based, status bar written in Haskell.|https://archives.haskell.org/projects.haskell.org/xmobar/|{{Pkg|xmobar}}}}

=== System tray ===

[[Desktop environments]] typically have their own system tray implementation. E.g. [[KDE]] ships with Plasma Panel and [[Xfce]] ships with {{Pkg|xfce4-panel}}. For [[GNOME]], see [[GNOME#AppIndicators/Top bar icons]]. For [[dwm]], see [https://dwm.suckless.org/patches/systray/ systray patch].

* {{App|AllTray|Dock other applications into the system tray (notification area).|https://github.com/mbt/alltray|{{AUR|alltray}}}}
* {{App|Docker|Docking application which acts as a system tray.|https://icculus.org/openbox/2/docker/|{{AUR|docker-tray}}}}
* {{App|KDocker|Dock any application in the system tray (notification area).|https://github.com/user-none/KDocker|{{AUR|kdocker}}}}
* {{App|[[Stalonetray]]|Stand-alone freedesktop.org and KDE system tray (notification area) for [[Xorg]]. It has full XEMBED support and minimal dependencies: an X11 lib only. Stalonetray works with virtually any EWMH-compliant window manager.|https://stalonetray.sourceforge.net/|{{Pkg|stalonetray}}}}
* {{App|Trayer|Lightweight GTK-based system tray (notification area).|https://github.com/sargon/trayer-srg/|{{AUR|trayer}}}}

==== Tray indicators ====

Desktop-independent tray indicators. Useful for window managers without built-in tray widgets:

* {{Pkg|cbatticon}}: battery
* {{Pkg|volumeicon}}: volume
* {{Pkg|pasystray}}: pulseaudio
* {{AUR|sbxkb}}: keyboard layout
* {{Pkg|python-pystray}}: Python library for creating tray entries.
* {{AUR|tktray}}: Tk extension to create system tray icons following XDG specifications.

=== Application launchers ===

See also [[Wikipedia:Comparison of desktop application launchers]].

* {{App|Albert|Sophisticated, plugin based standalone keyboard launcher.|https://albertlauncher.github.io/|{{AUR|albert}}}}
* {{App|Application Finder|Easy-to-use application launcher from Xfce.|https://docs.xfce.org/xfce/xfce4-appfinder/start|{{Pkg|xfce4-appfinder}}}}
* {{App|Bashrun2|Provides a different, barebones approach to a run dialog, using a specialized Bash session within a small xterm window.|http://henning-bekel.de/bashrun2/|{{AUR|bashrun2}}}}
* {{App|bemenu|Lightweight dynamic menu inspired by dmenu. Works natively on Wayland.|https://github.com/Cloudef/bemenu|{{Pkg|bemenu}}}}
* {{App|Cartridges|Simple game launcher written in Python using GTK4 and Libadwaita.|https://apps.gnome.org/Cartridges/|{{Pkg|cartridges}}}}
* {{App|[[dmenu]]|Fast and lightweight dynamic menu for X which is also useful as an application launcher.|https://tools.suckless.org/dmenu/|{{Pkg|dmenu}}}}
* {{App|dmenu-extended|Extension to ''dmenu'' for quickly opening files and folders.|https://github.com/markjones112358/dmenu-extended|{{AUR|dmenu-extended-git}}}}
* {{App|dswitcher|''dmenu''-based window switcher that works regardless of workspace or minimization.|https://github.com/Antithesisx/dswitcher|{{AUR|dswitcher-git}}}}
* {{App|fuzzel|Application launcher for wlroots-based Wayland compositors, similar to rofi's `drun` mode.|https://codeberg.org/dnkl/fuzzel|{{Pkg|fuzzel}}}}
* {{App|[[Gmrun]]|Lightweight GTK-based application launcher, with the ability to run programs inside a terminal and other handy features.|https://sourceforge.net/projects/gmrun/|{{AUR|gmrun}}}}
* {{App|GNOME Games|GNOME application to browse your local video games library and to easily pick and play a game from it. Part of {{Grp|gnome-extra}}.|https://wiki.gnome.org/Apps/Games|{{Pkg|gnome-games}}}}
* {{App|Gnome-Pie|Circular application launcher (pie menu) for Linux. It is made of several pies, each consisting of multiple slices.|https://simmesimme.github.io/gnome-pie.html|{{Pkg|gnome-pie}}}}
* {{App|higgins|Desktop agnostic application launcher, file finder, calculator and more. Plugin based and freely and easily extendable via user-written plugins.|https://github.com/kokoko3k/higgins|{{AUR|higgins-git}}}}
* {{App|j4-dmenu-desktop|Very fast dmenu application launcher.|https://github.com/enkore/j4-dmenu-desktop|{{Pkg|j4-dmenu-desktop}}}}
* {{App|jgmenu|Simple, independent, contemporary-looking X11 menu, designed for scripting, ricing and tweaking.|https://github.com/johanmalm/jgmenu|{{Pkg|jgmenu}}}}
* {{App|Junction|Application chooser to open files and links.|https://apps.gnome.org/Junction/|{{Pkg|junction}}}}
* {{App|Kupfer|Convenient command and access tool for the GNOME desktop that can launch applications, open documents and access different types of objects and act on them.|https://kupferlauncher.github.io/|{{Pkg|kupfer}}}}
* {{App|launch|Simple command for launching applications from a terminal emulator.|https://github.com/silverhammermba/launch|{{AUR|launch-cmd}}}}
* {{App|[[Wikipedia:Launchy|Launchy]]|Very popular cross-platform application launcher with a plugin-based system used to provide extra functionality.|https://www.launchy.net/|{{Pkg|launchy}}}}
* {{App|Lighthouse|Simple scriptable popup dialog to run on X.|https://github.com/emgram769/lighthouse|{{AUR|lighthouse-git}}}}
* {{App|LXLauncher|Clone of the Asus launcher for EeePC.|https://github.com/lxde/lxlauncher|{{Pkg|lxlauncher}}}}
* {{App|nwg-drawer|GTK-based application drawer designed for Sway and Hyprland compositors.|https://github.com/nwg-piotr/nwg-drawer|{{Pkg|nwg-drawer}}}}
* {{App|nwg-menu|GTK-based application menu designed for Sway and Hyprland compositors.|https://github.com/nwg-piotr/nwg-menu|{{Pkg|nwg-menu}}}}
* {{App|rlaunch|An extremely fast and light-weight dmenu-like application launcher written in Rust.|https://github.com/PonasKovas/rlaunch|{{AUR|rlaunch}}}}
* {{App|[[rofi]]|Popup window switcher roughly based on superswitcher, requiring only xlib and pango.|https://github.com/davatorium/rofi/|{{Pkg|rofi}}}}
* {{App|Synapse|Semantic launcher written in Vala that you can use to start applications as well as find and access relevant documents and files by making use of the Zeitgeist engine.|https://launchpad.net/synapse-project|{{Pkg|synapse}}}}
* {{App|tofi|Tiny dynamic menu, fast and simple dmenu/rofi replacement for Wayland compositors such as {{Pkg|sway}}.|https://github.com/philj56/tofi|{{AUR|tofi}}}}
* {{App|Ulauncher|Modern and shiny launcher that provides fuzzy search, extensions, and themes.|https://ulauncher.io/|{{AUR|ulauncher}}}}
* {{App|vonal|Modern customizable global menu with unlimiting plugin system written in Rust.|https://github.com/fxdave/vonal-rust|{{AUR|vonal-bin}}}}
* {{App|wmenu|Dynamic menu for Sway and wlroots-based Wayland compositors. Provides a Wayland-native dmenu replacement which maintains the look and feel of dmenu.|https://codeberg.org/adnano/wmenu|{{Pkg|wmenu}}}}
* {{App|wofi|GTK-based popup window switcher for Wayland compositors such as {{Pkg|sway}}. Inspired by {{Pkg|rofi}}.|https://hg.sr.ht/~scoopta/wofi|{{Pkg|wofi}}}}
* {{App|yofi|Minimalistic menu for Wayland-based compositors.|https://github.com/l4l/yofi|{{AUR|yofi}}}}

=== Application menu editors ===

* {{App|[[Wikipedia:Alacarte|Alacarte]]|Add or remove applications from the main menu.|https://gitlab.gnome.org/GNOME/alacarte|{{Pkg|alacarte}}}}
* {{App|AppEditor|Edit application entries in the application menu.|https://github.com/donadigo/appeditor|{{AUR|appeditor-git}}}}
* {{App|Ezame|Desktop and menu file editor.|https://github.com/linux-man/ezame|{{AUR|ezame}}}}
* {{App|KMenuEdit|Edit one of the KDE application launchers. Part of {{Grp|plasma}}.|https://invent.kde.org/plasma/kmenuedit|{{Pkg|kmenuedit}}}}
* {{App|lxmed|Application menu editor written in Java.|https://sourceforge.net/projects/lxmed/|{{AUR|lxmed}}}}
* {{App|MenuLibre|Advanced menu editor that provides modern features in a clean, easy-to-use interface.|https://launchpad.net/menulibre|{{AUR|menulibre}}}}
* {{App|Meow|Application menu editor written in Java.|https://pnmougel.github.io/meow/|{{AUR|meow-bin}}}}
* {{App|Mozo|Change which applications are shown on the main menu.|https://github.com/mate-desktop/mozo|{{Pkg|mozo}}}}

=== Application menu generators ===

* {{App|MenuGenerator|Simple application menu generator following XDG menu spec for Fluxbox, Openbox and JWM.|https://github.com/BlackCodec/MenuGenerator/|{{AUR|menugenerator}}}}
* {{App|MenuMaker|Heuristics-driven menu generator for Blackbox, Fluxbox, IceWM, Openbox, PekWM and WindowMaker.|https://menumaker.sourceforge.net/|{{Pkg|menumaker}}}}
* {{App|[[xdg-menu]]|Generate XDG application menus for various window managers.|https://github.com/p5n/archlinux-stuff/tree/master/xdg-menu|{{Pkg|archlinux-xdg-menu}}}}
* {{App|xdgmenumaker|Command line tool that generates XDG menus for several window managers.|https://github.com/gapan/xdgmenumaker|{{AUR|xdgmenumaker}}}}

=== Wallpaper setters ===

See also [[Wikipedia:Wallpaper (computing)]].

* {{App|awww|Efficient animated wallpaper daemon for Wayland, controlled at runtime.|https://codeberg.org/LGFae/awww|{{Pkg|awww}}}}
* {{App|bgs|An extremely fast and small background setter for X based on imlib2.|https://github.com/Gottox/bgs/|{{AUR|bgs-git}}}}
* {{App|[[feh]]|A lightweight and powerful image viewer that can also be used to manage the desktop wallpaper.|https://feh.finalrewind.org/|{{Pkg|feh}}‎}}
* {{App|Fondo|Find a variety of the most beautiful wallpapers from Unsplash.com.|https://github.com/calo001/fondo|{{AUR|fondo}}}}
* {{App|Hanabi|Live Wallpaper for GNOME.|https://github.com/jeffshee/gnome-ext-hanabi|{{AUR|gnome-shell-extension-hanabi-git}}}}
* {{App|Hidamari|Video wallpaper for Linux. Written in Python.|https://github.com/jeffshee/hidamari|{{AUR|hidamari}}}}
* {{App|hsetroot|A tool to create compose wallpapers.|https://packages.debian.org/sid/hsetroot|{{Pkg|hsetroot}}}}
* {{App|HydraPaper|GTK utility to set two different backgrounds for each monitor on GNOME.|https://gabmus.gitlab.io/HydraPaper/|{{AUR|hydrapaper-git}}}}
* {{App|Hyprpaper|Hyprpaper is a blazing fast Wayland wallpaper utility with IPC controls.|https://github.com/hyprwm/hyprpaper|{{AUR|hyprpaper-git}}}}
* {{App|LiveWallpaper|Animated 3D wallpapers.|https://launchpad.net/livewallpaper|{{AUR|livewallpaper}}}}
* {{App|mpvpaper|A video wallpaper program for wlroots-based Wayland compositors.|https://github.com/GhostNaN/mpvpaper|{{AUR|mpvpaper}}}}
* {{App|[[Nitrogen]]|A fast and lightweight desktop background browser and setter for X windows.|https://github.com/l3ib/nitrogen|{{AUR|nitrogen}}}}
* {{App|oguri|An animated wallpaper daemon for Wayland compositors.|https://github.com/vilhalmer/oguri|{{AUR|oguri-git}}}}
* {{App|pacwall|A live wallpaper that shows the dependency graph and status of installed packages.|https://github.com/Kharacternyk/pacwall|{{AUR|pacwall-git}}}}
* {{App|pywal|Changes the wallpaper and creates matching color schemes for various applications (rofi, i3, terminals)|https://github.com/dylanaraps/pywal|{{Pkg|python-pywal}}}}
* {{App|swaybg|Wallpaper tool for Wayland compositors.|https://github.com/swaywm/swaybg|{{Pkg|swaybg}}}}
* {{App|Variety|Changes the wallpaper on a regular interval using user-specified or automatically downloaded images.|https://peterlevi.com/variety/|{{Pkg|variety}}}}
* {{App|[[Xlivebg]]|A live wallpaper framework and collection of live wallpapers for the X window system.|http://nuclear.mutantstargoat.com/sw/xlivebg/|{{AUR|xlivebg}}}}
* {{App|xwallpaper|Minimalist wallpaper setting utility for X.|https://github.com/stoeckmann/xwallpaper|{{Pkg|xwallpaper}}}}

{{Tip|In order to avoid installing one more package, you may find convenient to use the {{ic|display}} utility from {{Pkg|imagemagick}} or {{ic|gm display}} from {{Pkg|graphicsmagick}}. E.g.: {{ic|display -backdrop -background '#3f3f3f' -flatten -window root ''image''}}.}}

=== Virtual desktop pagers ===

See also [[Wikipedia:Pager (GUI)]].

* {{App|bbpager|Dockable pager for [[blackbox]] and other window managers.|https://sourceforge.net/projects/bbtools/|4={{Pkg|bbpager}}}}
* {{App|fbpager|Virtual desktop pager for fluxbox.|http://www.fluxbox.org/fbpager{{Dead link|2025|01|22|status=404}}|{{AUR|fbpager-git}}}}
* {{App|IPager|A configurable pager with transparency, originally developed for Fluxbox.|http://useperl.ru/ipager/index.en.html{{Dead link|2025|03|15|status=404}}|{{AUR|ipager}}}}
* {{App|Netwmpager|A NetWM/EWMH compatible pager.|https://sourceforge.net/projects/sf-xpaint/files/netwmpager/|{{AUR|netwmpager}}}}

=== Desktop widgets ===

* {{App|CoreAction|Side bar with some handy gadgets like system loads, calendar, calculator, notes etc. Part of C-Suite.|https://gitlab.com/cubocore|{{AUR|coreaction}}}}
* {{App|[[Wikipedia:gDesklets|gDesklets]]|System for bringing mini programs (desklets) onto your desktop.|https://launchpad.net/gdesklets|{{AUR|gdesklets}}}}
* {{App|KRuler|Displays on screen a ruler measuring pixels. Part of {{Grp|kde-graphics}}.|https://apps.kde.org/kruler/|{{Pkg|kruler}}}}

=== Desktop notifications ===

See: [[Desktop notifications#Notification servers|Notification servers]].

=== Clipboard managers ===

See [[Clipboard#Managers]].

=== Logout UI ===

* {{App|clearine|Beautiful Logout UI for X11 window manager|https://github.com/okitavera/clearine{{Dead link|2025|11|17|status=404}}|{{AUR|clearine-git}}}}
* {{App|nwg-bar|Configurable button bar for wlroots-based Wayland compositors.|https://github.com/nwg-piotr/nwg-bar|{{Pkg|nwg-bar}}}}
* {{App|[[oblogout]]|Openbox logout script|https://launchpad.net/oblogout|{{AUR|oblogout-py3-git}}}}
* {{App|wlogout|Logout menu for wayland|https://github.com/ArtsyMacaw/wlogout|{{AUR|wlogout}}}}

== Artificial intelligence ==

See also [[Wikipedia:Open-source artificial intelligence]], [[Wikipedia:Lists of open-source artificial intelligence software]], [[Wikipedia:Comparison of deep learning software]]

=== Machine learning frameworks ===

* {{App|cuDNN|NVIDIA CUDA Deep Neural Network library for high-performance GPU acceleration.|https://developer.nvidia.com/cudnn|{{Pkg|cudnn}}}}
* {{App|[[Wikipedia:Fast Artificial Neural Network|Fast Artificial Neural Network]]|Library for developing feedforward Artificial Neural Networks.|https://leenissen.dk/fann/wp/|{{AUR|fann}}}}
* {{App|ggml|Lightweight tensor library for on-device LLM inference.|https://github.com/ggml-org/ggml|{{AUR|libggml}}}}
* {{App|[[Wikipedia:Orange (software)|Orange]]|Visual programming toolkit for data mining, ML and interactive visualization.|https://orange.biolab.si/|{{AUR|python-orange}}}}
* {{App|[[Wikipedia:Prolog|Prolog]]|Logic-programming language for symbolic AI and computational linguistics.|https://www.swi-prolog.org/|{{Pkg|swi-prolog}}, {{AUR|gprolog}}, {{AUR|scryer-prolog}}}}
* {{App|[[Wikipedia:PyTorch|PyTorch]]|Dynamic neural-network framework with strong GPU acceleration.|https://pytorch.org/|{{Pkg|python-pytorch}}, {{Pkg|python-pytorch-cuda}}, {{Pkg|python-pytorch-opt}}, {{Pkg|python-pytorch-opt-cuda}}, {{Pkg|python-pytorch-rocm}}, {{Pkg|python-pytorch-opt-rocm}}}}
* {{App|libtorch|C++ frontend for PyTorch.|https://pytorch.org|{{AUR|libtorch-cuda}}, {{AUR|libtorch-cpu}}, {{AUR|libtorch-rocm}}}}
* {{App|mlpack|Fast, scalable C++ ML library with Python / R / Julia / Go bindings.|https://mlpack.org|{{AUR|mlpack}}}}
* {{App|SentencePiece|Unsupervised text tokenizer for neural text generation.|https://github.com/google/sentencepiece|{{AUR|sentencepiece}} / {{AUR|sentencepiece-bin}} (C++), {{AUR|python-sentencepiece}} / {{AUR|python-sentencepiece-bin}} (Python)}}
* {{App|Sentence Transformers|Python framework for state-of-the-art sentence / text / image embeddings.|https://github.com/UKPLab/sentence-transformers|{{AUR|python-sentence-transformers}}}}
* {{App|[[Wikipedia:TensorFlow|TensorFlow]]|End-to-end platform for scalable machine learning.|https://www.tensorflow.org/|{{Pkg|python-tensorflow}}, {{Pkg|python-tensorflow-cuda}}, {{Pkg|python-tensorflow-opt}}, {{Pkg|python-tensorflow-opt-cuda}}}}
* {{App|[[Wikipedia:Theano (software)|Theano]]|Python library for efficient multi-dimensional array math and deep learning.|http://deeplearning.net/software/theano/|{{AUR|python-theano-pymc}}}}
* {{App|[[Wikipedia:Torch (machine learning)|Torch]]|Scientific computing & ML framework for LuaJIT.|http://torch.ch/|{{AUR|torch7-git}}}}

=== Local AI model deployment ===

==== Inference engines ====

* {{App|CTranslate2|A C++ and Python library for efficient inference with Transformer models.|https://github.com/OpenNMT/CTranslate2|{{AUR|ctranslate2}}, {{AUR|python-ctranslate2}}}}
* {{App|describeimage|Describe images using Ollama.|https://github.com/ollama/ollama|{{Pkg|describeimage}}}}
* {{App|[[llama.cpp]]|A high-performance C/C++ port of Facebook's LLaMA model, optimized for local execution.|https://github.com/ggerganov/llama.cpp|{{AUR|llama.cpp}}, {{AUR|llama.cpp-cuda}}, {{AUR|llama.cpp-vulkan}}}}
* {{App|ik-llama.cpp|A fork of llama.cpp with additional state-of-the-art quantized models and improved performance.|https://github.com/ikawrakow/ik_llama.cpp |{{AUR|ik-llama.cpp}}, {{AUR|ik-llama.cpp-cuda}}, {{AUR|ik-llama.cpp-vulkan}}}}
* {{App|ONNX Runtime|High-performance scoring engine for ML models with cross-platform support.|https://onnxruntime.ai/ |{{Pkg|onnxruntime-cpu}}, {{Pkg|onnxruntime-cuda}}, {{Pkg|onnxruntime-opt-cuda}}, {{Pkg|onnxruntime-rocm}}, {{Pkg|onnxruntime-opt-rocm}}}}
* {{App|[[Ollama]]|A streamlined tool for creating, running, and sharing large language models locally.|https://ollama.com|{{Pkg|ollama}}, {{Pkg|ollama-cuda}}, {{Pkg|ollama-rocm}}}}
* {{App|ollama-amd-igpu|A specialized version of Ollama optimized for AMD iGPUs, supporting Llama 3.3, DeepSeek-R1, Phi-4 and other models.|https://github.com/Crandel/ollama-amd-igpu|{{AUR|ollama-amd-igpu}}, {{AUR|ollama-amd-igpu-cuda}}, {{AUR|ollama-amd-igpu-rocm}}}}

==== Translation====

* {{App|Argos Translate|Open-source offline translation library with GUI support.|https://www.argosopentech.com/|{{AUR|argos-translate}}, {{AUR|argos-translate-gui}}}}
* {{App|TranslateLocally|Fast and secure local translation using Bergamot (Mozilla).|https://github.com/XapaJIaMnu/translatelocally|{{AUR|translatelocally-git}}}}

=== AI applications ===

==== Desktop clients ====

* {{App|AIOne|An all-in-one AI desktop application that provides access to ChatGPT, Gemini, and Claude (uses system-wide Electron).|https://sumexxx.github.io/AIOne/|{{AUR|aione}}}}
* {{App|Alpaca AI|A flexible client for Ollama, enabling local AI model usage and integration with third-party services like ChatGPT and Gemini.|https://github.com/Jeffser/alpaca|{{AUR|alpaca-ai}}}}
* {{App|AnythingLLM|An all-in-one AI application suite supporting Retrieval-Augmented Generation (RAG) and multi-agent workflows for Docker and desktop environments.|https://anythingllm.com/|{{AUR|anythingllm-desktop-bin}}}}
* {{App|BrowserOS|An open-source agentic browser that runs AI agents locally.|https://github.com/browseros-ai/BrowserOS|{{AUR|browseros-bin}}}}
* {{App|Cherry Studio|Desktop client for multiple LLM providers (OpenAI, Claude, LocalAI, etc.).|https://cherry.studio|{{AUR|cherry-studio}}}}
* {{App|Chatbox|A cross-platform desktop application for interacting with GPT-4 and GPT-3.5 models via the OpenAI API.|https://chatboxai.app|{{AUR|chatbox-bin}}}}
* {{App|ChatWise|Fast AI chatbot desktop application.|https://chatwise.app/|{{AUR|chatwise}}}}
* {{App|clara-verse|Privacy-first, client-side AI assistant WebUI for LLMs with ComfyUI integration.|https://github.com/badboysm890/ClaraVerse|{{AUR|clara-verse}}}}
* {{App|GPT4All|A lightweight solution for running large language models locally on any device.|https://gpt4all.io/|{{AUR|gpt4all-chat}}}}
* {{App|Jan|An easy-to-use platform for deploying and managing AI models directly on your PC.|https://jan.ai/|{{AUR|jan}}}}
* {{App|KAIChat|Chat interface for AI models such as Ollama.|https://apps.kde.org/kaichat/|{{AUR|kaichat}}}}
* {{App|Lobe Chat|A modern, extensible chat framework for LLMs, supporting multiple AI providers, multi-modal interactions, and plugins.|https://github.com/lobehub/lobe-chat|{{AUR|lobe-chat}}}}
* {{App|LocalAI|Free, Open Source OpenAI alternative with CPU optimizations.|https://github.com/mudler/LocalAI|{{AUR|local-ai}}}}
* {{App|RisuAI|User-friendly software for LLM roleplaying with local AI models.|https://risuai.xyz|{{AUR|risuai-bin}}}}
* {{App|NextChat|A cross-platform ChatGPT client.|https://github.com/ChatGPTNextWeb/ChatGPT-Next-Web|{{AUR|nextchat-bin}}}}
* {{App|noi-desktop|AI-powered desktop assistant for exploration and task automation.|https://noi.ai|{{AUR|noi-desktop-bin}}}}
* {{App|Open-GPT|A ChatGPT client using the OpenAI API.|https://github.com/BeanDx/open-gpt/tree/main|{{AUR|open-gpt-bin}}}}
* {{App|SillyTavern|A feature-rich local interface for interacting with large language models (LLMs), generating images, and synthesizing speech.|https://sillytavern.app/|{{AUR|sillytavern-git}}}}
* {{App|[[Wikipedia:Mycroft (software)|Mycroft]]|Intelligent personal assistant and knowledge navigator with speech recognition.|https://mycroft.ai/|{{AUR|mycroft-core}}}}

==== Terminal clients ====

* {{App|AICommits|CLI that writes your git commit messages with AI.|https://github.com/Nutlope/aicommits|{{AUR|aicommits}}}}
* {{App|AIChat|A versatile CLI tool for interacting with AI models, featuring REPL-like functionality, shell assistance, and support for multiple AI providers.|https://github.com/sigoden/aichat|{{Pkg|aichat}}}}
* {{App|AIChat NG|An enhanced fork of AIChat with advanced features for terminal-based AI interactions.|https://github.com/blob42/aichat-ng|{{AUR|aichat-ng}}}}
* {{App|Gemini CLI|Open-source AI agent that brings the power of Google Gemini directly into your terminal.|https://github.com/google-gemini/gemini-cli|{{Pkg|gemini-cli}}}}
* {{App|GitHub Copilot CLI|Official CLI interface for GitHub Copilot coding assistant.|https://github.com/github/copilot-cli|{{AUR|github-copilot-cli}}}}
* {{App|OpenCommit|Auto-generate meaningful git commit messages with AI.|https://github.com/di-sukharev/opencommit|{{AUR|opencommit}}}}
* {{App|TLM|Local CLI Copilot powered by Ollama.|https://github.com/yusufcanb/tlm|{{AUR|tlm}}}}
* {{App|ShellGPT|A productivity-focused CLI tool powered by OpenAI's ChatGPT, designed for efficient command-line workflows.|https://github.com/TheR1D/shell_gpt|{{AUR|shellgpt-git}}}}

=== Development tools ===

* {{App|hfdownloader|Utility to download HuggingFace Models and Datasets.|https://github.com/bodaay/HuggingFaceModelDownloader|{{AUR|hfdownloader-git}}}}
* {{App|Rivet|IDE for creating complex AI agents and prompt chaining.|https://rivet.ironcladapp.com|{{AUR|ironclad-rivet-bin}}}}
* {{App|Kiro|Amazon's closed-source, AI-powered IDE for rapid prototyping to production.|https://kiro.dev/|{{AUR|kiro-ide}}}}
* {{App|koboldcpp|A simple one-file way to run various GGML and GGUF models with a KoboldAI UI.|https://github.com/LostRuins/koboldcpp|{{AUR|koboldcpp}}, {{AUR|koboldcpp-cuda}}, {{AUR|koboldcpp-hipblas}}}}
* {{App|llamafile|Distribute and run LLMs with a single file.|https://github.com/Mozilla-Ocho/llamafile|{{AUR|llamafile}}}}
* {{App|LM Studio|A user-friendly interface for discovering, downloading, and running local LLMs.|https://lmstudio.ai/|{{AUR|lmstudio-bin}}}}
* {{App|Msty|A simple and intuitive interface for accessing both local and online AI models.|https://msty.app|{{AUR|msty-bin}}}}
* {{App|netron|Visualizer for neural network, deep learning and machine learning models.|https://netron.app/|{{AUR|netron}}}}
* {{App|open-webui|Extensible self-hosted AI platform with WebUI and OpenAI API support for LLM runners.|https://github.com/open-webui/open-webui|{{AUR|open-webui-git}}}}

=== Coding assistants ===

* {{App|Crush|A powerful terminal-based AI assistant for developers, providing intelligent coding assistance directly in your terminal.|https://charm.sh/crush|{{AUR|crush}}, {{AUR|crush-bin}}}}
* {{App|Codename Goose|An extensible AI agent that goes beyond code suggestions - can install, execute, edit, and test with any LLM.|https://github.com/block/goose|{{AUR|codename-goose-bin}}}}
* {{App|Claude Code|An agentic coding tool that lives in your terminal.|https://github.com/anthropics/claude-code|{{AUR|claude-code}}}}
* {{App|codai|AI code assistant with session-based CLI for intelligent suggestions and refactoring.|https://github.com/meysamhadeli/codai|{{AUR|codai}}}}
* {{App|CodeGPT|A CLI written in Go language that writes git commit messages or does a code review brief for you using ChatGPT AI (gpt-4, gpt-3.5-turbo model) and automatically installs a git prepare-commit-msg hook.|https://github.com/appleboy/CodeGPT|{{AUR|codegpt-bin}}}}
* {{App|Cursor|Write, edit, and chat about your code with GPT.|https://cursor.so|{{AUR|cursor-bin}}}}
* {{App|opencode|AI coding agent built for the terminal.|https://github.com/sst/opencode|{{Pkg|opencode}}}}
* {{App|Kiro|An AI-powered IDE for rapid prototyping to production.|https://kiro.dev/ |{{AUR|kiro-ide}}}}
* {{App|qwen-code|CLI coding agent (fork of gemini-cli) with AI-powered code generation and assistance.|https://github.com/QwenLM/Qwen-Code|{{Pkg|qwen-code}}}}

=== Multimedia processing ===

==== Image generation ====

* {{App|RapidOCR|A cross platform OCR Library based on OnnxRuntime.|https://github.com/RapidAI/RapidOCR|{{AUR|python-rapidocr-onnxruntime}}}}
* {{App|Krita AI Diffusion|An intuitive AI-powered plugin for Krita, enabling seamless image inpainting and outpainting with optional text prompts.|https://github.com/Acly/krita-ai-diffusion|{{AUR|krita-ai-diffusion}}}}
* {{App|StabilityMatrix|A versatile package manager for Stable Diffusion, simplifying model management and integration.|https://github.com/LykosAI/StabilityMatrix|{{AUR|stabilitymatrix}}}}
* {{App|Stable Diffusion C++|Pure C/C++ implementation of Stable Diffusion for efficient inference on local machines.|https://github.com/leejet/stable-diffusion.cpp|{{AUR|stable-diffusion.cpp-git}}}}
* {{App|Stable Diffusion Web UI|Powerful web-based interface for Stable Diffusion, enabling high-quality image generation with customizable parameters.|https://github.com/AUTOMATIC1111/stable-diffusion-webui|{{AUR|stable-diffusion-webui-git}}}}
* {{App|Upscayl|A free and open-source AI-based image upscaler, enhancing image resolution while preserving quality.|https://github.com/upscayl/upscayl|{{AUR|upscayl-bin}}}}

==== Speech processing ====

* {{App|Coqui TTS|Deep learning toolkit for Text-to-Speech with support for 20+ languages.|https://github.com/coqui-ai/TTS|{{AUR|coqui-tts}}}}
* {{App|faster-whisper|Faster Whisper transcription implementation using CTranslate2.|https://github.com/guillaumekln/faster-whisper|{{AUR|python-faster-whisper}}}}
* {{App|Handy|A free, open source, and extensible speech-to-text application that works completely offline.|https://github.com/cjpais/Handy|{{AUR|handy}}}}
* {{App|MaryTTS|Multilingual TTS synthesis platform written in Java.|https://marytts.github.io/|{{AUR|marytts}}}}
* {{App|Piper|A fast, local neural text-to-speech system.|https://github.com/rhasspy/piper|{{AUR|piper-tts}}}}
* {{App|Sherpa-ONNX|Speech-to-text, text-to-speech, speaker diarization, and VAD using next-gen Kaldi with onnxruntime.|https://github.com/k2-fsa/sherpa-onnx|{{AUR|sherpa-onnx}}}}
* {{App|shisper|Script to generate subtitles and transcriptions using whisper.cpp.|https://github.com/M0Rf30/shisper|{{AUR|shisper-git}}}}
* {{App|vibe|Transcribe audio/video offline using OpenAI Whisper with GUI interface.|https://thewh1teagle.github.io/vibe/|{{AUR|vibe-bin}}}}
* {{App|VOICEVOX|Japanese TTS engine with anime-style character voices.|https://voicevox.hiroshiba.jp/|{{AUR|voicevox-appimage}}}}
* {{App|whisper.cpp|A C/C++ port of OpenAI's Whisper model for efficient speech recognition.|https://github.com/ggerganov/whisper.cpp|{{AUR|whisper.cpp}}, {{AUR|whisper.cpp-cuda}}, {{AUR|whisper.cpp-openvino}}}}
* {{App|whisper.cpp-models|Pre-trained models for whisper.cpp in various sizes.|https://github.com/ggerganov/whisper.cpp|{{AUR|whisper.cpp-model-large-v3}}, {{AUR|whisper.cpp-model-medium}}, {{AUR|whisper.cpp-model-small}}, {{AUR|whisper.cpp-model-tiny}}}}
* {{App|whispering|Open-source transcription application with global speech-to-text functionality.|https://whispering.bradenwong.com/|{{AUR|whispering-bin}}}}
* {{App|wiggly-stt|Local speech-to-text with whisper.cpp and clipboard integration.|https://github.com/hansp27/wiggly-stt|{{AUR|wiggly-stt}}}}

Xlibre

2026-04-26T21:40:23Z

Alad: update redirect

#REDIRECT [[List of applications/Other#Display servers]]

List of applications/Other

2026-04-26T21:39:18Z

Alad: /* Display servers */ add arcan

[[Category:Applications]]
[[Category:Lists of software]]
[[es:List of applications (Español)/Other]]
[[hu:List of applications (Magyar)/Other]]
[[ja:アプリケーション一覧/その他]]
[[pl:List of applications (Polski)/Other]]
[[zh-hans:List of applications/Other]]
{{List of applications navigation}}

== Organization ==

=== CalDAV/CardDAV servers ===

* {{App|Baïkal|A lightweight CalDAV+CardDAV server.|https://sabre.io/baikal/|{{AUR|baikal}}}}
* {{App|kcaldav|Simple, safe, minimal CalDAV server.|https://kristaps.bsd.lv/kcaldav|{{AUR|kcaldav}}}}
* {{App|[[Radicale]]|Free and Open-Source CalDAV and CardDAV Server.|https://radicale.org|{{Pkg|radicale}}}}
* {{App|xandikos|A lightweight yet complete CardDAV/CalDAV server that backs onto a Git repository.|https://www.xandikos.org|{{Pkg|xandikos}}}}

=== Personal information managers ===

These applications support time, task and contacts management.

* {{App|[[Evolution]]|Personal information management application that provides integrated mail, calendaring and address book functionality. Part of {{Grp|gnome-extra}}.|https://gitlab.gnome.org/GNOME/evolution/-/wikis/home|{{Pkg|evolution}}}}
* {{App|[[Wikipedia:Kontact|Kontact]]|Integrated solution to your personal information management. Part of {{Grp|kde-pim}}.|https://kontact.kde.org/|{{Pkg|kontact}}}}
* {{App|Merkuro|Calendar and contact application that allows you to manage your tasks, events and contacts. Part of {{Grp|kde-pim}}.|https://apps.kde.org/merkuro/|{{Pkg|merkuro}}}}
* {{App|Osmo|GTK personal organizer, which includes calendar, tasks manager and address book modules.|https://osmo-pim.sourceforge.net|{{Pkg|osmo}}}}
* {{App|[[Wikipedia:SeaMonkey#Mail|SeaMonkey Mail & Newsgroups]] with [[Wikipedia:Lightning (software)|Lightning]]|Extension to SeaMonkey that provides calendar and task support.|https://www.seamonkey-project.org/|{{AUR|seamonkey}}}}
* {{App|[[Thunderbird]]|A fully featured E-mail client formerly developed by Mozilla.|https://www.thunderbird.net|{{Pkg|thunderbird}}}}

=== Time management ===

==== Console ====

* {{App|Calcurse|Text-based ncurses calendar and scheduling system (supports CalDAV)|https://calcurse.org|{{Pkg|calcurse}}}}
* {{App|ccal|A console program which writes a calendar together with Chinese calendar to standard output.|https://ccal.chinesebay.com/ccal/ccal.htm|{{AUR|ccal}}}}
* {{App|khal|Command-line (non-interactive) and ncurses (interactive) calendar system (supports CalDAV)|https://github.com/pimutils/khal|{{Pkg|khal}}}}
* {{App|gcalcli|Command-line (non-interactive) Google Calendar for event management and agendas.|https://github.com/insanum/gcalcli|{{AUR|gcalcli}}}}
* {{App|mail2rem|Small script for importing ''.ics'' calendars from Maildir to Remind calendar.|https://github.com/esovetkin/mail2rem|{{AUR|mail2rem-git}}}}
* {{App|Pal|Very lightweight calendar with both interactive and non-interactive interfaces.|https://palcal.sourceforge.net/|{{AUR|pal}}}}
* {{App|pcal|A tool to create pdf calendars from pcal input which can be exported by some calendar programs.|https://sourceforge.net/projects/pcal/|{{AUR|pcal}}}}
* {{App|[[Remind]]|Highly sophisticated text-based calendaring and notification system.|https://dianne.skoll.ca/projects/remind/|{{Pkg|remind}}}}
* {{App|When|Simple personal calendar program.|http://lightandmatter.com/when/when.html|{{Pkg|when}}}}
* {{App|Wyrd|Text-based front-end to Remind, a calendar and alarm program used on UNIX and Linux computers.|https://gitlab.com/wyrd-calendar/wyrd|{{AUR|wyrd}}}}

==== Graphical ====

* {{App|Agenda|Calendar application built with MauiKit. Part of {{Grp|maui}}.|https://mauikit.org/apps/|{{Pkg|maui-agenda}}}}
* {{App|Calindori|Calendar application for Plasma Mobile.|https://apps.kde.org/calindori/|{{Pkg|calindori}}}}
* {{App|chinese-calendar|Chinese traditional calendar for Ubuntu Kylin.|https://launchpad.net/chinese-calendar/|{{Pkg|chinese-calendar}}}}
* {{App|CoreTime|Very simple Clock/Calendar application which shows a clock, supports alarms, reminders, a stop watch and a timer. Part of C-Suite.|https://cubocore.gitlab.io/|{{AUR|coretime}}}}
* {{App|Deepin Calendar|Calendar application for Deepin.|https://www.deepin.org/en/original/dde-calendar/|{{Pkg|deepin-calendar}}}}
* {{App|etmtk (Event and Task Manager)|Simple application with a "Getting Things Done!" approach to handling events, tasks, activities, reminders and projects.|https://people.duke.edu/~dgraham/ETMtk/|{{AUR|etmtk}}}}
* {{App|Gahshomar|Persian (Jalali/Farsi) calendar.|https://gahshomar.github.io/gahshomar/|{{AUR|gahshomar}}}}
* {{App|GNOME Calendar|Calendar application for GNOME. Part of {{Grp|gnome}}.|https://apps.gnome.org/Calendar/|{{Pkg|gnome-calendar}}}}
* {{App|[[Wikipedia:KAlarm|KAlarm]]|Personal alarm message, command and email scheduler, part of {{Grp|kde-pim}}.|https://apps.kde.org/kalarm/|{{Pkg|kalarm}}}}
* {{App|Kongress|Companion application for conferences made by KDE. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/kongress/|{{Pkg|kongress}}}}
* {{App|[[Wikipedia:Kontact#Organizer|KOrganizer]]|Calendar and scheduling program, part of {{Grp|kde-pim}}.|https://kontact.kde.org/components/korganizer|{{Pkg|korganizer}}}}
* {{App|Merkuro Calendar|Calendar application using Akonadi that supports both local and online calendars: Nextcloud, Google Calendar, Outlook, Caldav and more. Part of {{Grp|kde-pim}}.|https://apps.kde.org/merkuro.calendar/|{{Pkg|merkuro}}}}
* {{App|[[Nextcloud]] Calendar|Calendar app for Nextcloud.|https://github.com/nextcloud/calendar|{{Pkg|nextcloud-app-calendar}}}}
* {{App|Outspline|Extensible outliner with advanced time management features, supporting events with complex recurrence schemes.|https://kynikos.github.io/outspline/|{{AUR|outspline}}}}
* {{App|TkRemind|Sophisticated calendar and alarm program.|https://dianne.skoll.ca/projects/remind/|{{Pkg|remind}}}}

=== Timers ===

==== Countdown timers and stopwatch ====

* {{App|arttime|Clock, timer, pattern-based time manager, ASCII art viewer. Set a one-off, multiple, repeating, pattern-based timers.|https://github.com/poetaman/arttime|{{AUR|arttime-git}}}}
* {{App|Chess Clock|Simple application to provide time control for over-the-board chess games.|https://apps.gnome.org/Chessclock/|{{Pkg|chess-clock}}}}
* {{App|GNOME Clocks|Clocks application for GNOME, including alarm, stopwatch and timer functionality. Part of {{Grp|gnome}}.|https://apps.gnome.org/Clocks/|{{Pkg|gnome-clocks}}}}
* {{App|Hourglass|Simple time keeping application designed for elementary OS.|https://github.com/sgpthomas/hourglass|{{AUR|hourglass}}}}
* {{App|KClock|A convergent clock application for Plasma. It contains alarm, timer, stopwatch and timezone functionalities. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/kclock/|{{Pkg|kclock}}}}
* {{App|Kronometer|Stopwatch application for KDE.|https://apps.kde.org/kronometer/|{{Pkg|kronometer}}}}
* {{App|KTeaTime|Handy timer for steeping tea. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/kteatime/|{{Pkg|kteatime}}}}
* {{App|pystopwatch|Stopwatch written in Python with a clock and two countdown functions that can minimize to the tray.|https://xyne.dev/projects/pystopwatch/|{{AUR|pystopwatch}}}}
* {{App|snore|A program like sleep, but with feedback.|https://github.com/clamiax/snore|{{AUR|snore-git}}}}
* {{App|termdown|Countdown timer and stopwatch in your terminal.|https://github.com/trehn/termdown|{{Pkg|termdown}}}}

==== Break timers ====

* {{App|Break Timer|Keeps track of how much you are using the computer, and it reminds you to take regular breaks. Works only in GNOME.|https://wiki.gnome.org/Apps/BreakTimer|{{Pkg|gnome-break-timer}}}}
* {{App|RSI Break|Takes care of your health and regularly breaks your work to avoid repetitive strain injury (RSI) [https://bugs.kde.org/show_bug.cgi?id{{=}}422033 on Xorg].|https://apps.kde.org/rsibreak/|{{Pkg|rsibreak}}}}
* {{App|Safe Eyes|Tool to reduce and prevent repetitive strain injury (RSI).|https://slgobinath.github.io/SafeEyes/|{{AUR|safeeyes}}}}
* {{App|Work-break|Work and rest time balancer taking into account your current and today strain.|https://github.com/ShadoySV/work-break/|{{AUR|work-break}}}}
* {{App|[[Wikipedia:Workrave|Workrave]]|Program that assists in the recovery and prevention of RSI [https://bbs.archlinux.org/viewtopic.php?id{{=}}285701 on Xorg].|https://workrave.org/|{{Pkg|workrave}}}}

==== Pomodoro timers ====

See [[Wikipedia:Pomodoro Technique]] for an introduction.

* {{App|flow|Pomodoro app that blocks distractions while you work.|https://github.com/iamsergio/flow-pomodoro|{{AUR|flow-pomodoro}}}}
* {{App|Francis|App that uses the well-known pomodoro technique to help you get more productive. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/francis/|{{Pkg|francis}}}}
* {{App|Gnomato|Timer for the Pomodoro Technique.|https://github.com/diegorubin/gnomato|{{AUR|gnomato}}}}
* {{App|Pilorama|Eye-candy timeboxing tool written in QML|https://github.com/eplatonoff/pilorama|{{AUR|pilorama-git}}}}
* {{App|Pomodoro|Time management utility for GNOME based on the Pomodoro Technique.|https://gnomepomodoro.org/|{{AUR|gnome-shell-pomodoro}}}}
* {{App|Pomodoro-Logger|Pomodoro timer and logger with [[Wikipedia:Kanban board|Kanban board]] for task management and tracking.|https://github.com/zxch3n/PomodoroLogger|{{AUR|pomodoro-logger}}}}
* {{App|potato-c|A minimal and efficient pomodoro timer with server-client structure.|https://github.com/nimaaskarian/potato-c|{{AUR|potato-c}}}}
* {{App|Solanum|Pomodoro timer for the GNOME desktop.|https://apps.gnome.org/Solanum/|{{Pkg|solanum}}}}
* {{App|Tomate|Timer for the Pomodoro Technique.|https://github.com/eliostvs/tomate-gtk|{{AUR|tomate-gtk}}}}
* {{App|Tomighty|Desktop timer for the Pomodoro Technique.|https://tomighty.github.io|{{AUR|tomighty}}}}

=== Time trackers ===

* {{App|ActivityWatch|A self/local-hosted, cross-platform, client-server, privacy-focused active window tracker.|https://github.com/ActivityWatch/activitywatch|{{AUR|activitywatch-bin}}}}
* {{App|Hamster|Time tracking application that helps you to keep track on how much time you have spent during the day on activities you choose to track.|http://projecthamster.org/|{{Pkg|hamster-time-tracker}}}}
* {{App|Kapow|Punch clock to track time spent on projects.|https://gottcode.org/kapow/|{{AUR|kapow}}}}
* {{App|KTimeTracker|Todo management and time tracking application.|https://apps.kde.org/ktimetracker/|{{Pkg|ktimetracker}}}}
* {{App|Tider|Lightweight time tracking application (GTK)|https://github.com/naspeh/tider|{{AUR|tider-git}}}}
* {{App|Timenaut|Time tracker that tracks active windows and lets you sort them into categories. Based on the [https://electronjs.org/ Electron] platform.|https://timenaut.app/|{{AUR|timenaut-appimage}}}}
* {{App|Timetrack|Simple time-tracking app for GNOME.|https://gitlab.gnome.org/danigm/timetrack|{{AUR|timetrack}}}}
* {{App|Timewarrior|A command-line time-tracking application.|https://timewarrior.net/|{{Pkg|timew}}}}
* {{App|Wakatime|Open source plugins for metrics about your programming with intuitive web-interface.|https://wakatime.com/|{{AUR|wakatime}}}}

=== Task management ===

==== Console ====

* {{App|c3|A multi-platform TUI todo manager that extends calcurse's todo format to have a tree-like dependency structure, and even more! |https://github.com/nimaaskarian/c3|{{AUR|c3}}}}
* {{App|Cfait|Powerful, simple, elegant, and lightweight CalDAV task manager (TUI & GUI).|https://codeberg.org/trougnouf/cfait|{{AUR|cfait}}}}
* {{App|dijo|Scriptable, curses-based, digital habit tracker |https://github.com/nerdypepper/dijo|{{AUR|dijo}}}}
* {{App|Taskbook|Tasks, boards and notes for the command-line habitat.|https://github.com/klauscfhq/taskbook|{{AUR|taskbook}}}}
* {{App|Taskell|A command-line kanban board/task manager.|https://github.com/smallhadroncollider/taskell|{{AUR|taskell}}}}
* {{App|[[Wikipedia:Taskwarrior|Taskwarrior]]|Command-line To-do list application with support for lua customization and more.|https://taskwarrior.org/|{{Pkg|task}}}}
* {{App|todoman|Command-line To-do list manager (supports CalDAV)|https://github.com/pimutils/todoman|{{Pkg|todoman}}}}
* {{App|Todo.txt|Small command-line To-do manager.|https://github.com/todotxt/todo.txt-cli/|{{AUR|todotxt}}}}
* {{App|TuDu|Ncurses-based hierarchical To-do list manager with vim-like keybindings.|https://code.meskio.net/tudu/|{{AUR|tudu}}}}

==== Graphical ====

* {{App|Agenda|Simple, fast, no-nonsense to-do (task) list for elementary OS.|https://github.com/dahenson/agenda|{{AUR|agenda}}}}
* {{App|Cfait|Powerful, simple, elegant, and lightweight CalDAV task manager (TUI & GUI).|https://codeberg.org/trougnouf/cfait|{{AUR|cfait}}}}
* {{App|Effitask|Graphical task manager, based on the [http://todotxt.com/ Todo.txt] format.|https://github.com/sanpii/effitask|{{AUR|effitask}}}}
* {{App|Endeavour|Personal task manager for GNOME. Part of {{Grp|gnome-extra}}.|https://wiki.gnome.org/Apps/Todo|{{Pkg|endeavour}}}}
* {{App|Errands|Todo application for those who prefer simplicity.|https://apps.gnome.org/List/|{{Pkg|errands}}}}
* {{App|Go For It!|Simple and stylish productivity app, featuring a to-do list, merged with a timer that keeps your focus on the current task. To-do lists are stored in the [http://todotxt.com/ Todo.txt] format.|https://manuelkehl.de/projects/go-for-it/|{{AUR|go-for-it}}}}
* {{App|GTG|Personal tasks and TODO list items organizer for GNOME inspired by the [[Wikipedia:Getting Things Done|Getting Things Done (GTD)]] methodology.|https://github.com/getting-things-gnome/gtg|{{AUR|gtg}}}}
* {{App|KomoDo|Todo manager that uses todo.txt specification.|https://apps.kde.org/komodo/|{{Pkg|komodo}}}}
* {{App|[[Nextcloud]] Tasks|Tasks app for Nextcloud.|https://github.com/nextcloud/tasks|{{Pkg|nextcloud-app-tasks}}}}
* {{App|Planner|Task manager with Todoist support.|https://useplanner.com/|{{AUR|planify}}}}
* {{App|ptask|GTK task manager based on [[Wikipedia:Taskwarrior|Taskwarrior]].|https://wpitchoune.net/ptask/|{{AUR|ptask}}}}
* {{App|sleek|todo.txt app with modern GUI. Based on the [https://electronjs.org/ Electron] platform.|https://github.com/ransome1/sleek/|{{AUR|sleek}}}}
* {{App|TickTick|Is a simple and effective to-do list and task manager app with seamless cloud synchronization across all your devices|https://ticktick.com/|{{AUR|ticktick}}}}
* {{App|Zanshin|To-do management application for KDE. Part of {{Grp|kde-pim}}.|https://apps.kde.org/zanshin/|{{Pkg|zanshin}}}}

=== Contacts management ===

==== Console ====

* {{App|Abook|Text-based contacts manager designed for use with mutt.|https://abook.sourceforge.net/|{{AUR|abook}}}}
* {{App|Khard|Command-line addressbook that is able to sync with CardDAV-servers.|https://github.com/scheibler/khard|{{Pkg|khard}}}}

==== Graphical ====

* {{App|Addresses|Address book application for GNUstep.|https://www.nongnu.org/gap/addresses/|{{AUR|addresses.app}}}}
* {{App|Communicator|Integrated address book and dialer application features the search for and view of contacts, edit contact details, and make new contacts, favorites, and dialer pad. Part of {{Grp|maui}}.|https://mauikit.org/apps/communicator/|{{Pkg|communicator}}}}
* {{App|GNOME Contacts|Contacts manager for GNOME. Part of {{Grp|gnome}}.|https://apps.gnome.org/Contacts/|{{Pkg|gnome-contacts}}}}
* {{App|KAddressBook|Address book manager for KDE. Part of {{Grp|kde-pim}}.|https://kontact.kde.org/components/kaddressbook|{{Pkg|kaddressbook}}}}
* {{App|LDAP Administration Tool|Browse LDAP-based directories and add/edit/delete entries contained within.|https://sourceforge.net/projects/ldap-at/|{{AUR|lat}}}}
* {{App|Merkuro Contacts|Address book using Akonadi. Part of {{Grp|kde-pim}}.|https://apps.kde.org/merkuro.contact/|{{Pkg|merkuro}}}}
* {{App|[[Nextcloud]] Contacts|Contacts app for Nextcloud.|https://github.com/nextcloud/contacts|{{Pkg|nextcloud-app-contacts}}}}
* {{App|[[phpLDAPadmin]]|LDAP client webapp. Its hierarchical tree-viewer and advanced search functionality make it intuitive to browse and administer your LDAP directory.|https://phpldapadmin.sourceforge.net/|{{Pkg|phpldapadmin}}}}
* {{App|[[Thunderbird]] with [https://gitlab.com/CardBook/CardBook CardBook] extension|address book based on the CardDAV and vCard standards.|https://gitlab.com/CardBook/CardBook|{{Pkg|thunderbird}}}}

=== Financial management ===

See also [[Wikipedia:Comparison of accounting software]].

==== Console ====

* {{App|Beancount|A double-entry bookkeeping computer language that lets you define financial transaction records in a text file, read them in memory, generate a variety of reports from them, and provides a web interface.|https://beancount.github.io/|{{AUR|beancount}}}}
* {{App|hledger|An accounting program for tracking money, time, or any other commodity, using double-entry accounting and a simple, editable file format. hledger is inspired by and largely compatible with ledger.|https://hledger.org/|{{Pkg|hledger}}}}
* {{App|[[Ledger]]|Ledger is a powerful, double-entry accounting system that is accessed from the UNIX command-line.|https://www.ledger-cli.org/|{{Pkg|ledger}}}}

==== Graphical ====

* {{App|Eqonomize!|Cross-platform personal accounting software, with focus on efficiency and ease of use for the small household economy.|https://eqonomize.github.io/|{{AUR|eqonomize}}}}
* {{App|[[ERPNext]]|Free and open source Enterprise Resource Planning (ERP).|https://github.com/frappe/erpnext|{{AUR|erpnext}}}}
* {{App|[[Wikipedia:GnuCash|GnuCash]]|Financial application that implements a double-entry book-keeping system with features for small business accounting.|https://www.gnucash.org/|{{Pkg|gnucash}}}}
* {{App|Grisbi|Personal finance system which manages third party, expenditure and receipt categories, as well as budgetary lines, financial years, and other information that makes it suitable for associations.|https://www.grisbi.org/|{{AUR|grisbi}}}}
* {{App|[[Wikipedia:HomeBank|HomeBank]]|Easy to use finance manager that can analyse your personal finance in detail using powerful filtering tools and graphs.|http://homebank.free.fr/|{{Pkg|homebank}}}}
* {{App|[[Wikipedia:KMyMoney|KMyMoney]]|Personal finance manager that operates in a similar way to [[Wikipedia:Microsoft Money|Microsoft Money]]. It supports different account types, categorisation of expenses and incomes, reconciliation of bank accounts and import/export to the “QIF” file format.|https://kmymoney.org/|{{Pkg|kmymoney}}}}
* {{App|Kresus|Self-hosted personal finance management software. It automatically retrieves every day all your new bank transactions and lets you categorize them, study them through charts and establish a budget.|https://kresus.org/en/|{{Pkg|kresus}}}}
* {{App|Manager|Proprietary accounting software for small business.|https://www.manager.io/|{{AUR|manager-accounting}}}}
* {{App|Money Manager EX|An easy-to-use personal finance suite|https://www.moneymanagerex.org/|{{AUR|moneymanagerex}}}}
* {{App|[[Odoo]]|Open source ERP system purely in Python. Previously known as OpenERP.|https://www.odoo.com/|{{AUR|odoo-venv}}}}
* {{App|Skrooge|Personal finances manager for the KDE desktop.|https://skrooge.org/|{{Pkg|skrooge}}}}

=== Cryptocurrency ===

* {{App|Atomic Wallet|Manage your Bitcoin, Ethereum, XRP, Litecoin, XLM, and over 300 other coins and tokens. |https://atomicwallet.io/|{{AUR|atomicwallet}}}}
* {{App|Bitcoin Core|Connect to the Bitcoin P2P Network.|https://bitcoincore.org/|{{Pkg|bitcoin-qt}}}}
* {{App|Cake Wallet|Multicurrency wallet.|https://github.com/cake-tech/cake_wallet|{{AUR|cake-wallet-bin}}}}
* {{App|Coinomi|Securely store, manage and exchange Bitcoin, Ethereum, and more than 1,770 other blockchain assets.|https://www.coinomi.com/|{{AUR|coinomi-wallet-bin}}}}
* {{App|Cointop|Terminal based application for tracking cryptocurrencies.|https://cointop.sh/|{{AUR|cointop}}}}
* {{App|Dogecoin Core|Dogecoin Core wallet, Allows you to connect to the Dogecoin P2P Network.|https://dogecoin.com/|{{AUR|dogecoin-qt}}, {{AUR|multidoge}}}}
* {{App|Electrum|Lightweight Bitcoin client.|https://electrum.org/|{{Pkg|electrum}}}}
* {{App|Exodus|All-in-one proprietary application to secure, manage, and exchange blockchain assets. Based on the [https://electronjs.org/ Electron] platform.|https://www.exodus.io/|{{AUR|exodus}}}}
* {{App|Feather Wallet|Lightweight Monero wallet.|https://featherwallet.org/|{{AUR|feather-wallet}}}}
* {{App|Monero|Monero wallet.|https://getmonero.org/|{{Pkg|monero-gui}}, {{Pkg|monero}}}}
* {{App|Sparrow Wallet|Advanced Bitcoin client.|https://sparrowwallet.com/|{{AUR|sparrow-wallet}}}}

=== Project management ===

See also [[Wikipedia:Comparison of project management software]].

* {{App|[[Wikipedia:Calligra Plan|Calligra Plan]]|Project management application, which is intended for managing moderately large projects with multiple resources.|https://calligra.org/components/plan/|{{Pkg|calligra-plan}}}}
* {{App|[[Wikipedia:GanttProject|GanttProject]]|Project scheduling application featuring gantt chart, resource management, calendaring.|https://www.ganttproject.biz/|{{AUR|ganttproject}}}}
* {{App|[[Notion-app]]|A note-taking software and project management software that is used for note-taking, task management, project management, knowledge management, and personal knowledge management. |https://www.notion.so/|{{AUR|notion-app-electron}}}}
* {{App|Planner|Project management application for GNOME.|https://wiki.gnome.org/Apps/Planner|{{Pkg|planner}}}}
* {{App|[[Wikipedia:ProjectLibre|ProjectLibre]]|Project management software alternative to [[Wikipedia:Microsoft Project|Microsoft Project]].|https://www.projectlibre.com/product/projectlibre-open-source{{Dead link|2025|08|15|status=404}}|{{AUR|projectlibre}}}}
* {{App|[[Wikipedia:TaskJuggler|TaskJuggler]]|Modern and powerful project management tool. Its new approach to project planning and tracking is more flexible and superior to the commonly used Gantt chart editing tools.|https://taskjuggler.org/|{{AUR|taskjuggler}}}}

=== Bookmark management ===

* {{App|KEditBookmarks|Bookmark organizer and editor. Part of {{Grp|kde-utilities}}.|https://invent.kde.org/utilities/keditbookmarks|{{Pkg|keditbookmarks}}}}
* {{App|Read It Later|Simple Wallabag client.|https://gitlab.gnome.org/World/read-it-later|{{Pkg|read-it-later}}}}

=== Recipe management ===

* {{App|Gourmand|Simple but powerful recipe-managing application.|https://github.com/GourmandRecipeManager/gourmand|{{AUR|gourmand}}}}
* {{App|Recipes|Recipe management application for GNOME. Part of {{Grp|gnome-extra}}.|https://wiki.gnome.org/Apps/Recipes|{{Pkg|gnome-recipes}}}}

=== Travel management ===

See also [[List of applications/Science#Navigation and routing]].

* {{App|Itinerary|Digital travel assistant with a priority on protecting your privacy. Part of {{Grp|kde-pim}}.|https://apps.kde.org/itinerary/|{{Pkg|itinerary}}}}

=== Health management ===

* {{App|Health|Health tracking app for the GNOME desktop.|https://apps.gnome.org/Health/|{{Pkg|health}}}}

== Education ==

See also [[List of games#Education]].

* {{App|Artikulate|Pronunciation trainer that helps improving and perfecting a learner's pronunciation skills for a foreign language. Part of {{Grp|kde-education}}.|https://apps.kde.org/artikulate/|{{Pkg|artikulate}}}}
* {{App|Fretboard|Look up guitar chords.|https://apps.gnome.org/Fretboard/|{{Pkg|fretboard}}}}
* {{App|Kalm|Teach you different breathing techniques. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/kalm/|{{Pkg|kalm}}}}
* {{App|[[Moodle]]|Open-source software learning management system.|https://moodle.org/|{{AUR|moodle}}}}
* {{App|[[Wikipedia:OpenBoard|OpenBoard]]|Interactive whiteboard software for schools and universities.|https://openboard.ch/index.en.html|{{AUR|openboard}}}}
* {{App|Wike|Wikipedia reader for the GNOME desktop.|https://apps.gnome.org/Wike/|{{Pkg|wike}}}}
* {{App|Wildcard|Provides a simple interface to test/practice regular expressions.|https://gitlab.gnome.org/World/Wildcard|{{Pkg|wildcard}}}}

=== Flashcards ===

See also [[Wikipedia:List of flashcard software]].

* {{App|[[Anki]]|Intelligent spaced-repetition memory training program.|https://apps.ankiweb.net/|{{Pkg|anki}}}}
* {{App|jVLT|Vocabulary learning tool.|https://www.linuxlinks.com/jVLT/|{{AUR|jvlt}}}}
* {{App|KWordQuiz|Tool that gives you a powerful way to master new vocabularies. Part of {{Grp|kde-education}}.|https://apps.kde.org/kwordquiz/|{{Pkg|kwordquiz}}}}
* {{App|[[Mnemosyne]]|Flash-card tool which optimizes your learning process.|https://mnemosyne-proj.org/|{{AUR|mnemosyne}}}}
* {{App|Parley|Program to help you memorize things. It uses the spaced repetition learning method, also known as flash cards. Part of {{Grp|kde-education}}.|https://apps.kde.org/parley/|{{Pkg|parley}}}}
* {{App|Pauker|Flash card based learning tool using shortterm and longterm memory training.|https://pauker.sourceforge.net/|{{AUR|pauker}}}}
* {{App|StudyFlash|Learn flashcards inside your terminal|https://github.com/Alone2/studyFlash|{{AUR|studyflash}}}}

=== Touch typing ===

==== Console ====

* {{App|Dvorak 7min|Simple ncurses-based typing tutor for those trying to become fluent with the Dvorak keyboard layout.|https://github.com/yaychris/dvorak7min|{{AUR|dvorak7min}}}}
* {{App|GNU Typist|Universal typing tutor.|https://www.gnu.org/software/gtypist/|{{AUR|gtypist}}}}
* {{App|psani-profi|Program that will teach you touchtyping (Czech).|https://www.sallyx.org/sally/psani-vsemi-deseti/|{{AUR|psani-profi}}}}
* {{App|Typespeed|Test your typing speed, and get your fingers' CPS.|https://typespeed.sourceforge.net/|{{AUR|typespeed}}}}
* {{App|typiskt|touchtype training in the terminal (Bash).|https://github.com/budlabs/typiskt|{{AUR|typiskt}}}}

==== Graphical ====

* {{App|Klavaro|Teaching touch typing that intends to be keyboard and language independent.|https://klavaro.sourceforge.io/|{{Pkg|klavaro}}}}
* {{App|[[Wikipedia:KTouch|KTouch]]|Program to learn and practice touch typing. Part of {{Grp|kde-education}}.|https://apps.kde.org/ktouch/|{{Pkg|ktouch}}}}
* {{App|TIPP10|Intelligent touch typing tutor.|https://www.tipp10.com/|{{Pkg|tipp10}}}}
* {{App|TypingTest|Typing test desktop program with a large amount of customization.|https://github.com/laelath/typingtest|{{AUR|typingtest-git}}}}

== Accessibility ==

See [[Accessibility]] for tips on operating the desktop and [[:Category:Accessibility]] for all available articles. See also [[List of applications/Utilities#On-screen keyboards|On-screen keyboards]].

=== Speech synthesizers ===

See also [[Wikipedia:Comparison of speech synthesizers]] and [https://tools.wmflabs.org/tts-comparison/ listening comparison of the different engines].

* {{App|Ekho|Chinese text-to-speech (TTS) software for Cantonese, Mandarin, Zhaoan Hakka, Tibetan, Ngangien and Korean.|https://eguidedog.net/ekho.php|{{AUR|ekho}}}}
* {{App|eSpeak|Compact speech synthesizer for more than 50 languages.|https://espeak.sourceforge.net/|{{AUR|espeak}}}}
* {{App|[[Wikipedia:eSpeakNG|eSpeak NG]]|Fork of eSpeak (due to inactivity of original maintainer).|https://github.com/espeak-ng/espeak-ng|{{Pkg|espeak-ng}}}}
* {{App|[[Festival]]|General framework for building speech synthesis systems as well as including examples of various modules. As a whole it offers full text to speech.|https://www.cstr.ed.ac.uk/projects/festival/|{{Pkg|festival}}}}
* {{App|Flite|Lightweight speech synthesis engine.|http://festvox.org/flite/|{{Pkg|flite}}}}
* {{App|Gespeaker|GTK frontend for espeak. It allows you to play a text in many languages with settings for voice, pitch, volume and speed.|https://muflone.com/gespeaker/english/|{{AUR|gespeaker}}}}
* {{App|KMouth|Speech synthesizer frontend which enables persons that cannot speak to let their computer speak. Part of {{Grp|kde-accessibility}}.|https://apps.kde.org/kmouth/|{{Pkg|kmouth}}}}
* {{App|MaryTTS|Multilingual text-to-speech synthesis platform written in Java.|https://marytts.github.io/|{{AUR|marytts}}}}
* {{App|[[Mbrola|MBROLA]]|Proprietary phonemes-to-audio program which supports more than 70 languages. Mbrola-voices can also be used with eSpeak.|http://tcts.fpms.ac.be/synthesis/mbrola.html|{{AUR|mbrola}}}}
* {{App|Mimic|Text-to-speech voice synthesis from the Mycroft project (based on Flite).|https://mimic.mycroft.ai/|{{AUR|mimic}}}}
* {{App|Open JTalk|Japanese text-to-speech synthesis system.|https://sourceforge.net/projects/open-jtalk/|{{AUR|open-jtalk}}}}
* {{App|Orca|Screen reader for individuals who are blind or visually impaired, using eSpeak (via Speech Dispatcher). Part of {{Grp|gnome}}.|https://wiki.gnome.org/Projects/Orca|{{Pkg|orca}}}}
* {{App|piper|A fast, local neural text to speech system.|https://github.com/rhasspy/piper|{{AUR|piper-tts-bin}}}}
* {{App|[[RHVoice]]|Cross-platform (including Android) text-to-speech from a blind Russian-speaking developer, based on [https://hts.sp.nitech.ac.jp HTS] (ru, ka, uk, ky, tt, en, pt, eo)|https://github.com/RHVoice/RHVoice|{{Pkg|rhvoice}}}}
* {{App|[[Simple Orca Plugin System|SOPS]]|Provides a simple way to write custom plugins for screen reader Orca.|https://github.com/chrys87/simple-orca-plugin-system|{{AUR|simpleorcapluginsystem}}}}
* {{App|[[Speech dispatcher]]|Common interface to speech synthesis. It has backends for eSpeak, Festival, and a few other speech synthesizers.|https://freebsoft.org/speechd|{{Pkg|speech-dispatcher}}}}

=== Speech recognition ===

See also [[Wikipedia:Speech recognition software for Linux]].

* {{App|[[Wikipedia:Julius (software)|Julius]]|Large vocabulary continuous speech recognition engine.|https://github.com/julius-speech/julius|{{AUR|julius-speech}}}}
* {{App|[[Wikipedia:Kaldi (software)|Kaldi]]|Speech recognition toolkit.|https://github.com/kaldi-asr/kaldi|{{AUR|kaldi}}}}
* {{App|Kaylee|Somewhat fancy voice command recognition program that performs actions when a user speaks loosely preset sentences.|https://github.com/Ratfink/kaylee|{{AUR|kayleevc}}}}
* {{App|[[Wikipedia:Mycroft (software)|Mycroft]]|Hackable voice assistant.|https://github.com/MycroftAI/mycroft-core|{{AUR|mycroft-core}}}}
* {{App|nerd-dictation|Light weight manually activated dictation using the VOSK-API.|https://github.com/ideasman42/nerd-dictation|{{AUR|nerd-dictation-git}}}}
* {{App|Numen|Voice control for handsfree computing.|https://sr.ht/~geb/numen/|{{AUR|numen}}}}

=== Screen magnifiers ===

* {{App|boomer|Zoomer application for Linux.|https://github.com/tsoding/boomer|{{AUR|boomer-git}}}}
* {{App|KMag|Small KDE utility to magnify a part of the screen. Part of {{Grp|kde-accessibility}}.|https://apps.kde.org/kmag/|{{Pkg|kmag}}}}
* {{App|Magnus|Very simple desktop magnifier, showing the area around the mouse pointer in a separate window magnified two, three, four, or five times.|https://kryogenix.org/code/magnus/|{{AUR|magnus}}}}
* {{App|Virtual Magnifying Glass|Simple, customizable and easy-to-use screen magnification tool.|https://magnifier.sourceforge.net/|{{AUR|vmg}}}}
* {{App|xzoom|Zoom, rotate and mirror area of X display.|https://www.ibiblio.org/pub/Linux/X11/libs/!INDEX.short.html|{{AUR|xzoom}}}}

=== On-screen annotation ===

* {{App|Gromit-MPX|Tool to make annotations on the screen.|https://github.com/bk138/gromit-mpx|{{AUR|gromit-mpx}}}}
* {{App|Pylote|Tool to draw on the screen.|http://pascal.peter.free.fr/pylote-en.html|{{AUR|pylote-git}}}}
* {{App|Screenkey|Tool to display pressed keys.|https://www.thregr.org/~wavexx/software/screenkey/|{{Pkg|screenkey}}}}
* {{App|Show Me The Key|A screenkey alternative that works under Wayland via libinput|https://showmethekey.alynx.one|{{Pkg|showmethekey}}}}

=== Mouse ===

* {{App|Easystroke|Use mouse gestures to initiate commands and hotkeys.|https://github.com/thjaeger/easystroke/wiki|{{AUR|easystroke}}}}
* {{App|KMouseTool|Clicks the mouse whenever the mouse cursor pauses briefly. It was designed to help those with repetitive strain injuries, for whom pressing buttons hurts. Part of {{Grp|kde-accessibility}}.|https://apps.kde.org/kmousetool/|{{Pkg|kmousetool}}}}
* {{App|Mousetweaks|Accessibility enhancements for pointing devices.|https://wiki.gnome.org/Projects/Mousetweaks|{{Pkg|mousetweaks}}}}

== Display servers ==

* {{App|Arcan|A development framework for anything between user interfaces for specialised embedded applications, and a standalone desktop environment.|https://arcan-fe.com/|{{AUR|arcan}}}}
* {{App|[[Xorg]]|The public, open-source implementation of the [[Wikipedia:X Window System|X Window System]] (commonly X11, or X).|https://www.x.org|{{Pkg|xorg}}}}
* {{App|Xlibre|A fork of Xorg that is [[Intel graphics#With the modesetting driver 2|tear free]] by default, supports client isolation and fixes several upstream bugs.|https://github.com/X11Libre |{{AUR|xlibre-xserver}}}}
* {{App|[[Wayland]]|A newer, alternative display server protocol with several [[Wayland#Compositors|compositors]] to choose from. Its advantages over Xorg are enhanced security features, more efficient handling of modern graphics tasks and active development while retaining compatibility through [[Xwayland]].|https://wayland.freedesktop.org/|{{Pkg|wayland}}}}

== Display managers ==

See the main article: [[Display manager#List of display managers]].

== Desktop environments ==

See the main article: [[Desktop environment#List of desktop environments]].

=== Window managers ===

==== Console ====

See also [[List of applications/Utilities#Terminal multiplexers]], which offer some of the functions of window managers for the console.

* {{App|twin|Text-mode window manager.|https://sourceforge.net/projects/twin/|{{AUR|twin}}}}
* {{App|Wmutils|A set of tools for X windows manipulation.|https://github.com/wmutils/core|{{AUR|wmutils-git}}}}

==== Graphical ====

See the main article: [[Window manager#List of window managers]].

==== Composite managers ====

See the main article: [[Xorg#List of composite managers]].

=== Wayland compositors ===

See the main article: [[Wayland#Compositors]].

=== Window tilers ===

* {{App|QuickTile|Lightweight standalone alternative to Compiz Grid plugin.|http://ssokolow.com/quicktile/|{{AUR|quicktile-git}}}}
* {{App|wumwum|The Window Manager manager. It can turn emwh compliant window managers into a tiling window manager while retaining all initial functionalities.|https://wumwum.sourceforge.net/|{{AUR|wumwum}}}}

=== Desktop shells ===

Desktop shells provide a graphical shell layer on top of a window manager or compositor, including panels, launchers, and other desktop components. They can be used to build a desktop-like experience, but do not constitute full desktop environments.

* {{App|AGS|Aylur's GTK Shell is a framework for building custom desktop shells using GTK.|https://aylur.github.io/ags/|{{AUR|aylurs-gtk-shell}}}}
* {{App|DankMaterialShell|Desktop shell for Wayland compositors, built with Quickshell and Go.|https://github.com/AvengeMedia/DankMaterialShell|{{Pkg|dms-shell}}}}
* {{App|eww|ElKowar's Wacky Widgets is a standalone widget system made in Rust that allows you to implement your own, custom widgets in any window manager.|https://github.com/elkowar/eww|{{AUR|eww}}}}
* {{App|liquidshell|Basic desktop shell for Xorg, an alternative to plasmashell, implemented using QtWidgets. It provides a bottom panel, a desktop wallpaper and desktop widgets.|https://apps.kde.org/liquidshell/|{{Pkg|liquidshell}}}}
* {{App|Noctalia|Minimal desktop shell for Wayland compositors, built on Quickshell.|https://noctalia.dev/|{{AUR|noctalia-shell}}}}
* {{App|[[nwg-shell]]|Modular GTK3-based shell for Sway and Hyprland compositors.|https://nwg-piotr.github.io/nwg-shell/|{{Pkg|nwg-shell}}}}
* {{App|wf-shell|Shell components for the Wayfire compositor.|https://github.com/WayfireWM/wf-shell|{{Pkg|wf-shell}}}}

=== Taskbars ===

See also [[Wikipedia:Taskbar]].

==== For both Wayland and Xorg ====
* {{App|[[Cairo-Dock]]|Highly customizable dock and launcher application.|https://www.glx-dock.org/|{{Pkg|cairo-dock}}}}
* {{App|LXQt Panel|Qt-based taskbar, part of the [[LXQt]] desktop.|https://github.com/lxqt/lxqt-panel|{{Pkg|lxqt-panel}}}}
* {{App|Xfce Panel|Panel included in the [[Xfce]] desktop.|https://docs.xfce.org/xfce/xfce4-panel/start|{{Pkg|xfce4-panel}}}}
* {{App|yambar|A modular and lightweight status bar for X11 and Wayland that goes to great lengths to be both CPU and battery efficient.|https://codeberg.org/dnkl/yambar|{{AUR|yambar}}}}

==== For Wayland only ====
* {{App|Dash to Panel|A fully customizable icon taskbar for {{Pkg|gnome-shell}}. Moves the dash into the GNOME main panel, similar to KDE Plasma and Windows 10.|https://github.com/home-sweet-gnome/dash-to-panel|{{Pkg|gnome-shell-extension-dash-to-panel}}}}
* {{App|Ironbar|A customisable and feature-rich GTK4 status bar for Wayland compositors, written in Rust.|https://github.com/JakeStanger/ironbar|{{Pkg|ironbar}}}}
* {{App|nwg-dock|GTK-based dock for Sway and Hyprland compositors.|https://github.com/nwg-piotr/nwg-dock|For Sway: {{Pkg|nwg-dock}}, for Hyprland: {{Pkg|nwg-dock-hyprland}}}}
* {{App|nwg-panel|GTK3-based panel for Sway and Hyprland compositors.|https://github.com/nwg-piotr/nwg-panel|{{Pkg|nwg-panel}}}}
* {{App|SFWBar|Flexible taskbar application for Wayland compositors, designed with a stacking layout in mind.|https://github.com/LBCrion/sfwbar|{{AUR|sfwbar}}}}
* {{App|Waybar|A customizable status bar for wlroots-based Wayland compositors.|https://github.com/Alexays/Waybar/|{{Pkg|waybar}}}}

==== For Xorg only ====
* {{App|[[Bmpanel]]|Lightweight, NETWM compliant panel.|https://github.com/nsf/bmpanel2|{{AUR|bmpanel2}}}}
* {{App|DockbarX|Standalone, dock-style taskbar for X11 with window grouping.|https://github.com/xuzhen/dockbarx|{{AUR|dockbarx}}}}
* {{App|[[fbpanel]]|Lightweight, NETWM compliant desktop panel.|https://aanatoly.github.io/fbpanel/|{{AUR|fbpanel}}}}
* {{App|[[Wikipedia:GNOME Panel|GNOME Panel]]|Panel included in the [[GNOME Flashback]] desktop.|https://wiki.gnome.org/Projects/GnomePanel|{{Pkg|gnome-panel}}}}
* {{App|[[Lemonbar]]|A featherweight status bar based on XCB. Provides UTF-8 support, background and foreground colors, text alignment, and not much more.|https://github.com/LemonBoy/bar|{{AUR|lemonbar}}}}
* {{App|LXPanel|Lightweight X11 desktop panel and part of the [[LXDE]] desktop.|https://github.com/lxde/lxpanel|{{Pkg|lxpanel}}}}
* {{App|MATE Panel|Panel included in the [[MATE]] desktop.|https://github.com/mate-desktop/mate-panel/|{{Pkg|mate-panel}}}}
* {{App|plainPanel|A lightweight panel written in Qt. It aims to be a desktop environment, but for now, it includes just a panel and a control center.|https://plainDE.github.io/|{{AUR|plainde-meta}}}}
* {{App|[[Plank]]|Elegant, simple, clean dock from [[Pantheon]] desktop environment.|https://launchpad.net/plank|{{Pkg|plank}}}}
* {{App|[[Polybar]]|A fast and easy-to-use tool for creating status bars.|https://github.com/jaagr/polybar|{{Pkg|polybar}}}}
* {{App|[[Tint2]]|Simple panel/taskbar developed specifically for Openbox.|https://gitlab.com/o9000/tint2|{{Pkg|tint2}}}}
* {{App|Vala Panel|GTK3 panel for compositing window managers.|https://gitlab.com/vala-panel-project/vala-panel|{{AUR|vala-panel}}}}
* {{App|[[xmobar]]|A lightweight, text-based, status bar written in Haskell.|https://archives.haskell.org/projects.haskell.org/xmobar/|{{Pkg|xmobar}}}}

=== System tray ===

[[Desktop environments]] typically have their own system tray implementation. E.g. [[KDE]] ships with Plasma Panel and [[Xfce]] ships with {{Pkg|xfce4-panel}}. For [[GNOME]], see [[GNOME#AppIndicators/Top bar icons]]. For [[dwm]], see [https://dwm.suckless.org/patches/systray/ systray patch].

* {{App|AllTray|Dock other applications into the system tray (notification area).|https://github.com/mbt/alltray|{{AUR|alltray}}}}
* {{App|Docker|Docking application which acts as a system tray.|https://icculus.org/openbox/2/docker/|{{AUR|docker-tray}}}}
* {{App|KDocker|Dock any application in the system tray (notification area).|https://github.com/user-none/KDocker|{{AUR|kdocker}}}}
* {{App|[[Stalonetray]]|Stand-alone freedesktop.org and KDE system tray (notification area) for [[Xorg]]. It has full XEMBED support and minimal dependencies: an X11 lib only. Stalonetray works with virtually any EWMH-compliant window manager.|https://stalonetray.sourceforge.net/|{{Pkg|stalonetray}}}}
* {{App|Trayer|Lightweight GTK-based system tray (notification area).|https://github.com/sargon/trayer-srg/|{{AUR|trayer}}}}

==== Tray indicators ====

Desktop-independent tray indicators. Useful for window managers without built-in tray widgets:

* {{Pkg|cbatticon}}: battery
* {{Pkg|volumeicon}}: volume
* {{Pkg|pasystray}}: pulseaudio
* {{AUR|sbxkb}}: keyboard layout
* {{Pkg|python-pystray}}: Python library for creating tray entries.
* {{AUR|tktray}}: Tk extension to create system tray icons following XDG specifications.

=== Application launchers ===

See also [[Wikipedia:Comparison of desktop application launchers]].

* {{App|Albert|Sophisticated, plugin based standalone keyboard launcher.|https://albertlauncher.github.io/|{{AUR|albert}}}}
* {{App|Application Finder|Easy-to-use application launcher from Xfce.|https://docs.xfce.org/xfce/xfce4-appfinder/start|{{Pkg|xfce4-appfinder}}}}
* {{App|Bashrun2|Provides a different, barebones approach to a run dialog, using a specialized Bash session within a small xterm window.|http://henning-bekel.de/bashrun2/|{{AUR|bashrun2}}}}
* {{App|bemenu|Lightweight dynamic menu inspired by dmenu. Works natively on Wayland.|https://github.com/Cloudef/bemenu|{{Pkg|bemenu}}}}
* {{App|Cartridges|Simple game launcher written in Python using GTK4 and Libadwaita.|https://apps.gnome.org/Cartridges/|{{Pkg|cartridges}}}}
* {{App|[[dmenu]]|Fast and lightweight dynamic menu for X which is also useful as an application launcher.|https://tools.suckless.org/dmenu/|{{Pkg|dmenu}}}}
* {{App|dmenu-extended|Extension to ''dmenu'' for quickly opening files and folders.|https://github.com/markjones112358/dmenu-extended|{{AUR|dmenu-extended-git}}}}
* {{App|dswitcher|''dmenu''-based window switcher that works regardless of workspace or minimization.|https://github.com/Antithesisx/dswitcher|{{AUR|dswitcher-git}}}}
* {{App|fuzzel|Application launcher for wlroots-based Wayland compositors, similar to rofi's `drun` mode.|https://codeberg.org/dnkl/fuzzel|{{Pkg|fuzzel}}}}
* {{App|[[Gmrun]]|Lightweight GTK-based application launcher, with the ability to run programs inside a terminal and other handy features.|https://sourceforge.net/projects/gmrun/|{{AUR|gmrun}}}}
* {{App|GNOME Games|GNOME application to browse your local video games library and to easily pick and play a game from it. Part of {{Grp|gnome-extra}}.|https://wiki.gnome.org/Apps/Games|{{Pkg|gnome-games}}}}
* {{App|Gnome-Pie|Circular application launcher (pie menu) for Linux. It is made of several pies, each consisting of multiple slices.|https://simmesimme.github.io/gnome-pie.html|{{Pkg|gnome-pie}}}}
* {{App|higgins|Desktop agnostic application launcher, file finder, calculator and more. Plugin based and freely and easily extendable via user-written plugins.|https://github.com/kokoko3k/higgins|{{AUR|higgins-git}}}}
* {{App|j4-dmenu-desktop|Very fast dmenu application launcher.|https://github.com/enkore/j4-dmenu-desktop|{{Pkg|j4-dmenu-desktop}}}}
* {{App|jgmenu|Simple, independent, contemporary-looking X11 menu, designed for scripting, ricing and tweaking.|https://github.com/johanmalm/jgmenu|{{Pkg|jgmenu}}}}
* {{App|Junction|Application chooser to open files and links.|https://apps.gnome.org/Junction/|{{Pkg|junction}}}}
* {{App|Kupfer|Convenient command and access tool for the GNOME desktop that can launch applications, open documents and access different types of objects and act on them.|https://kupferlauncher.github.io/|{{Pkg|kupfer}}}}
* {{App|launch|Simple command for launching applications from a terminal emulator.|https://github.com/silverhammermba/launch|{{AUR|launch-cmd}}}}
* {{App|[[Wikipedia:Launchy|Launchy]]|Very popular cross-platform application launcher with a plugin-based system used to provide extra functionality.|https://www.launchy.net/|{{Pkg|launchy}}}}
* {{App|Lighthouse|Simple scriptable popup dialog to run on X.|https://github.com/emgram769/lighthouse|{{AUR|lighthouse-git}}}}
* {{App|LXLauncher|Clone of the Asus launcher for EeePC.|https://github.com/lxde/lxlauncher|{{Pkg|lxlauncher}}}}
* {{App|nwg-drawer|GTK-based application drawer designed for Sway and Hyprland compositors.|https://github.com/nwg-piotr/nwg-drawer|{{Pkg|nwg-drawer}}}}
* {{App|nwg-menu|GTK-based application menu designed for Sway and Hyprland compositors.|https://github.com/nwg-piotr/nwg-menu|{{Pkg|nwg-menu}}}}
* {{App|rlaunch|An extremely fast and light-weight dmenu-like application launcher written in Rust.|https://github.com/PonasKovas/rlaunch|{{AUR|rlaunch}}}}
* {{App|[[rofi]]|Popup window switcher roughly based on superswitcher, requiring only xlib and pango.|https://github.com/davatorium/rofi/|{{Pkg|rofi}}}}
* {{App|Synapse|Semantic launcher written in Vala that you can use to start applications as well as find and access relevant documents and files by making use of the Zeitgeist engine.|https://launchpad.net/synapse-project|{{Pkg|synapse}}}}
* {{App|tofi|Tiny dynamic menu, fast and simple dmenu/rofi replacement for Wayland compositors such as {{Pkg|sway}}.|https://github.com/philj56/tofi|{{AUR|tofi}}}}
* {{App|Ulauncher|Modern and shiny launcher that provides fuzzy search, extensions, and themes.|https://ulauncher.io/|{{AUR|ulauncher}}}}
* {{App|vonal|Modern customizable global menu with unlimiting plugin system written in Rust.|https://github.com/fxdave/vonal-rust|{{AUR|vonal-bin}}}}
* {{App|wmenu|Dynamic menu for Sway and wlroots-based Wayland compositors. Provides a Wayland-native dmenu replacement which maintains the look and feel of dmenu.|https://codeberg.org/adnano/wmenu|{{Pkg|wmenu}}}}
* {{App|wofi|GTK-based popup window switcher for Wayland compositors such as {{Pkg|sway}}. Inspired by {{Pkg|rofi}}.|https://hg.sr.ht/~scoopta/wofi|{{Pkg|wofi}}}}
* {{App|yofi|Minimalistic menu for Wayland-based compositors.|https://github.com/l4l/yofi|{{AUR|yofi}}}}

=== Application menu editors ===

* {{App|[[Wikipedia:Alacarte|Alacarte]]|Add or remove applications from the main menu.|https://gitlab.gnome.org/GNOME/alacarte|{{Pkg|alacarte}}}}
* {{App|AppEditor|Edit application entries in the application menu.|https://github.com/donadigo/appeditor|{{AUR|appeditor-git}}}}
* {{App|Ezame|Desktop and menu file editor.|https://github.com/linux-man/ezame|{{AUR|ezame}}}}
* {{App|KMenuEdit|Edit one of the KDE application launchers. Part of {{Grp|plasma}}.|https://invent.kde.org/plasma/kmenuedit|{{Pkg|kmenuedit}}}}
* {{App|lxmed|Application menu editor written in Java.|https://sourceforge.net/projects/lxmed/|{{AUR|lxmed}}}}
* {{App|MenuLibre|Advanced menu editor that provides modern features in a clean, easy-to-use interface.|https://launchpad.net/menulibre|{{AUR|menulibre}}}}
* {{App|Meow|Application menu editor written in Java.|https://pnmougel.github.io/meow/|{{AUR|meow-bin}}}}
* {{App|Mozo|Change which applications are shown on the main menu.|https://github.com/mate-desktop/mozo|{{Pkg|mozo}}}}

=== Application menu generators ===

* {{App|MenuGenerator|Simple application menu generator following XDG menu spec for Fluxbox, Openbox and JWM.|https://github.com/BlackCodec/MenuGenerator/|{{AUR|menugenerator}}}}
* {{App|MenuMaker|Heuristics-driven menu generator for Blackbox, Fluxbox, IceWM, Openbox, PekWM and WindowMaker.|https://menumaker.sourceforge.net/|{{Pkg|menumaker}}}}
* {{App|[[xdg-menu]]|Generate XDG application menus for various window managers.|https://github.com/p5n/archlinux-stuff/tree/master/xdg-menu|{{Pkg|archlinux-xdg-menu}}}}
* {{App|xdgmenumaker|Command line tool that generates XDG menus for several window managers.|https://github.com/gapan/xdgmenumaker|{{AUR|xdgmenumaker}}}}

=== Wallpaper setters ===

See also [[Wikipedia:Wallpaper (computing)]].

* {{App|awww|Efficient animated wallpaper daemon for Wayland, controlled at runtime.|https://codeberg.org/LGFae/awww|{{Pkg|awww}}}}
* {{App|bgs|An extremely fast and small background setter for X based on imlib2.|https://github.com/Gottox/bgs/|{{AUR|bgs-git}}}}
* {{App|[[feh]]|A lightweight and powerful image viewer that can also be used to manage the desktop wallpaper.|https://feh.finalrewind.org/|{{Pkg|feh}}‎}}
* {{App|Fondo|Find a variety of the most beautiful wallpapers from Unsplash.com.|https://github.com/calo001/fondo|{{AUR|fondo}}}}
* {{App|Hanabi|Live Wallpaper for GNOME.|https://github.com/jeffshee/gnome-ext-hanabi|{{AUR|gnome-shell-extension-hanabi-git}}}}
* {{App|Hidamari|Video wallpaper for Linux. Written in Python.|https://github.com/jeffshee/hidamari|{{AUR|hidamari}}}}
* {{App|hsetroot|A tool to create compose wallpapers.|https://packages.debian.org/sid/hsetroot|{{Pkg|hsetroot}}}}
* {{App|HydraPaper|GTK utility to set two different backgrounds for each monitor on GNOME.|https://gabmus.gitlab.io/HydraPaper/|{{AUR|hydrapaper-git}}}}
* {{App|Hyprpaper|Hyprpaper is a blazing fast Wayland wallpaper utility with IPC controls.|https://github.com/hyprwm/hyprpaper|{{AUR|hyprpaper-git}}}}
* {{App|LiveWallpaper|Animated 3D wallpapers.|https://launchpad.net/livewallpaper|{{AUR|livewallpaper}}}}
* {{App|mpvpaper|A video wallpaper program for wlroots-based Wayland compositors.|https://github.com/GhostNaN/mpvpaper|{{AUR|mpvpaper}}}}
* {{App|[[Nitrogen]]|A fast and lightweight desktop background browser and setter for X windows.|https://github.com/l3ib/nitrogen|{{AUR|nitrogen}}}}
* {{App|oguri|An animated wallpaper daemon for Wayland compositors.|https://github.com/vilhalmer/oguri|{{AUR|oguri-git}}}}
* {{App|pacwall|A live wallpaper that shows the dependency graph and status of installed packages.|https://github.com/Kharacternyk/pacwall|{{AUR|pacwall-git}}}}
* {{App|pywal|Changes the wallpaper and creates matching color schemes for various applications (rofi, i3, terminals)|https://github.com/dylanaraps/pywal|{{Pkg|python-pywal}}}}
* {{App|swaybg|Wallpaper tool for Wayland compositors.|https://github.com/swaywm/swaybg|{{Pkg|swaybg}}}}
* {{App|Variety|Changes the wallpaper on a regular interval using user-specified or automatically downloaded images.|https://peterlevi.com/variety/|{{Pkg|variety}}}}
* {{App|[[Xlivebg]]|A live wallpaper framework and collection of live wallpapers for the X window system.|http://nuclear.mutantstargoat.com/sw/xlivebg/|{{AUR|xlivebg}}}}
* {{App|xwallpaper|Minimalist wallpaper setting utility for X.|https://github.com/stoeckmann/xwallpaper|{{Pkg|xwallpaper}}}}

{{Tip|In order to avoid installing one more package, you may find convenient to use the {{ic|display}} utility from {{Pkg|imagemagick}} or {{ic|gm display}} from {{Pkg|graphicsmagick}}. E.g.: {{ic|display -backdrop -background '#3f3f3f' -flatten -window root ''image''}}.}}

=== Virtual desktop pagers ===

See also [[Wikipedia:Pager (GUI)]].

* {{App|bbpager|Dockable pager for [[blackbox]] and other window managers.|https://sourceforge.net/projects/bbtools/|4={{Pkg|bbpager}}}}
* {{App|fbpager|Virtual desktop pager for fluxbox.|http://www.fluxbox.org/fbpager{{Dead link|2025|01|22|status=404}}|{{AUR|fbpager-git}}}}
* {{App|IPager|A configurable pager with transparency, originally developed for Fluxbox.|http://useperl.ru/ipager/index.en.html{{Dead link|2025|03|15|status=404}}|{{AUR|ipager}}}}
* {{App|Netwmpager|A NetWM/EWMH compatible pager.|https://sourceforge.net/projects/sf-xpaint/files/netwmpager/|{{AUR|netwmpager}}}}

=== Desktop widgets ===

* {{App|CoreAction|Side bar with some handy gadgets like system loads, calendar, calculator, notes etc. Part of C-Suite.|https://gitlab.com/cubocore|{{AUR|coreaction}}}}
* {{App|[[Wikipedia:gDesklets|gDesklets]]|System for bringing mini programs (desklets) onto your desktop.|https://launchpad.net/gdesklets|{{AUR|gdesklets}}}}
* {{App|KRuler|Displays on screen a ruler measuring pixels. Part of {{Grp|kde-graphics}}.|https://apps.kde.org/kruler/|{{Pkg|kruler}}}}

=== Desktop notifications ===

See: [[Desktop notifications#Notification servers|Notification servers]].

=== Clipboard managers ===

See [[Clipboard#Managers]].

=== Logout UI ===

* {{App|clearine|Beautiful Logout UI for X11 window manager|https://github.com/okitavera/clearine{{Dead link|2025|11|17|status=404}}|{{AUR|clearine-git}}}}
* {{App|nwg-bar|Configurable button bar for wlroots-based Wayland compositors.|https://github.com/nwg-piotr/nwg-bar|{{Pkg|nwg-bar}}}}
* {{App|[[oblogout]]|Openbox logout script|https://launchpad.net/oblogout|{{AUR|oblogout-py3-git}}}}
* {{App|wlogout|Logout menu for wayland|https://github.com/ArtsyMacaw/wlogout|{{AUR|wlogout}}}}

== Artificial intelligence ==

See also [[Wikipedia:Open-source artificial intelligence]], [[Wikipedia:Lists of open-source artificial intelligence software]], [[Wikipedia:Comparison of deep learning software]]

=== Machine learning frameworks ===

* {{App|cuDNN|NVIDIA CUDA Deep Neural Network library for high-performance GPU acceleration.|https://developer.nvidia.com/cudnn|{{Pkg|cudnn}}}}
* {{App|[[Wikipedia:Fast Artificial Neural Network|Fast Artificial Neural Network]]|Library for developing feedforward Artificial Neural Networks.|https://leenissen.dk/fann/wp/|{{AUR|fann}}}}
* {{App|ggml|Lightweight tensor library for on-device LLM inference.|https://github.com/ggml-org/ggml|{{AUR|libggml}}}}
* {{App|[[Wikipedia:Orange (software)|Orange]]|Visual programming toolkit for data mining, ML and interactive visualization.|https://orange.biolab.si/|{{AUR|python-orange}}}}
* {{App|[[Wikipedia:Prolog|Prolog]]|Logic-programming language for symbolic AI and computational linguistics.|https://www.swi-prolog.org/|{{Pkg|swi-prolog}}, {{AUR|gprolog}}, {{AUR|scryer-prolog}}}}
* {{App|[[Wikipedia:PyTorch|PyTorch]]|Dynamic neural-network framework with strong GPU acceleration.|https://pytorch.org/|{{Pkg|python-pytorch}}, {{Pkg|python-pytorch-cuda}}, {{Pkg|python-pytorch-opt}}, {{Pkg|python-pytorch-opt-cuda}}, {{Pkg|python-pytorch-rocm}}, {{Pkg|python-pytorch-opt-rocm}}}}
* {{App|libtorch|C++ frontend for PyTorch.|https://pytorch.org|{{AUR|libtorch-cuda}}, {{AUR|libtorch-cpu}}, {{AUR|libtorch-rocm}}}}
* {{App|mlpack|Fast, scalable C++ ML library with Python / R / Julia / Go bindings.|https://mlpack.org|{{AUR|mlpack}}}}
* {{App|SentencePiece|Unsupervised text tokenizer for neural text generation.|https://github.com/google/sentencepiece|{{AUR|sentencepiece}} / {{AUR|sentencepiece-bin}} (C++), {{AUR|python-sentencepiece}} / {{AUR|python-sentencepiece-bin}} (Python)}}
* {{App|Sentence Transformers|Python framework for state-of-the-art sentence / text / image embeddings.|https://github.com/UKPLab/sentence-transformers|{{AUR|python-sentence-transformers}}}}
* {{App|[[Wikipedia:TensorFlow|TensorFlow]]|End-to-end platform for scalable machine learning.|https://www.tensorflow.org/|{{Pkg|python-tensorflow}}, {{Pkg|python-tensorflow-cuda}}, {{Pkg|python-tensorflow-opt}}, {{Pkg|python-tensorflow-opt-cuda}}}}
* {{App|[[Wikipedia:Theano (software)|Theano]]|Python library for efficient multi-dimensional array math and deep learning.|http://deeplearning.net/software/theano/|{{AUR|python-theano-pymc}}}}
* {{App|[[Wikipedia:Torch (machine learning)|Torch]]|Scientific computing & ML framework for LuaJIT.|http://torch.ch/|{{AUR|torch7-git}}}}

=== Local AI model deployment ===

==== Inference engines ====

* {{App|CTranslate2|A C++ and Python library for efficient inference with Transformer models.|https://github.com/OpenNMT/CTranslate2|{{AUR|ctranslate2}}, {{AUR|python-ctranslate2}}}}
* {{App|describeimage|Describe images using Ollama.|https://github.com/ollama/ollama|{{Pkg|describeimage}}}}
* {{App|[[llama.cpp]]|A high-performance C/C++ port of Facebook's LLaMA model, optimized for local execution.|https://github.com/ggerganov/llama.cpp|{{AUR|llama.cpp}}, {{AUR|llama.cpp-cuda}}, {{AUR|llama.cpp-vulkan}}}}
* {{App|ik-llama.cpp|A fork of llama.cpp with additional state-of-the-art quantized models and improved performance.|https://github.com/ikawrakow/ik_llama.cpp |{{AUR|ik-llama.cpp}}, {{AUR|ik-llama.cpp-cuda}}, {{AUR|ik-llama.cpp-vulkan}}}}
* {{App|ONNX Runtime|High-performance scoring engine for ML models with cross-platform support.|https://onnxruntime.ai/ |{{Pkg|onnxruntime-cpu}}, {{Pkg|onnxruntime-cuda}}, {{Pkg|onnxruntime-opt-cuda}}, {{Pkg|onnxruntime-rocm}}, {{Pkg|onnxruntime-opt-rocm}}}}
* {{App|[[Ollama]]|A streamlined tool for creating, running, and sharing large language models locally.|https://ollama.com|{{Pkg|ollama}}, {{Pkg|ollama-cuda}}, {{Pkg|ollama-rocm}}}}
* {{App|ollama-amd-igpu|A specialized version of Ollama optimized for AMD iGPUs, supporting Llama 3.3, DeepSeek-R1, Phi-4 and other models.|https://github.com/Crandel/ollama-amd-igpu|{{AUR|ollama-amd-igpu}}, {{AUR|ollama-amd-igpu-cuda}}, {{AUR|ollama-amd-igpu-rocm}}}}

==== Translation====

* {{App|Argos Translate|Open-source offline translation library with GUI support.|https://www.argosopentech.com/|{{AUR|argos-translate}}, {{AUR|argos-translate-gui}}}}
* {{App|TranslateLocally|Fast and secure local translation using Bergamot (Mozilla).|https://github.com/XapaJIaMnu/translatelocally|{{AUR|translatelocally-git}}}}

=== AI applications ===

==== Desktop clients ====

* {{App|AIOne|An all-in-one AI desktop application that provides access to ChatGPT, Gemini, and Claude (uses system-wide Electron).|https://sumexxx.github.io/AIOne/|{{AUR|aione}}}}
* {{App|Alpaca AI|A flexible client for Ollama, enabling local AI model usage and integration with third-party services like ChatGPT and Gemini.|https://github.com/Jeffser/alpaca|{{AUR|alpaca-ai}}}}
* {{App|AnythingLLM|An all-in-one AI application suite supporting Retrieval-Augmented Generation (RAG) and multi-agent workflows for Docker and desktop environments.|https://anythingllm.com/|{{AUR|anythingllm-desktop-bin}}}}
* {{App|BrowserOS|An open-source agentic browser that runs AI agents locally.|https://github.com/browseros-ai/BrowserOS|{{AUR|browseros-bin}}}}
* {{App|Cherry Studio|Desktop client for multiple LLM providers (OpenAI, Claude, LocalAI, etc.).|https://cherry.studio|{{AUR|cherry-studio}}}}
* {{App|Chatbox|A cross-platform desktop application for interacting with GPT-4 and GPT-3.5 models via the OpenAI API.|https://chatboxai.app|{{AUR|chatbox-bin}}}}
* {{App|ChatWise|Fast AI chatbot desktop application.|https://chatwise.app/|{{AUR|chatwise}}}}
* {{App|clara-verse|Privacy-first, client-side AI assistant WebUI for LLMs with ComfyUI integration.|https://github.com/badboysm890/ClaraVerse|{{AUR|clara-verse}}}}
* {{App|GPT4All|A lightweight solution for running large language models locally on any device.|https://gpt4all.io/|{{AUR|gpt4all-chat}}}}
* {{App|Jan|An easy-to-use platform for deploying and managing AI models directly on your PC.|https://jan.ai/|{{AUR|jan}}}}
* {{App|KAIChat|Chat interface for AI models such as Ollama.|https://apps.kde.org/kaichat/|{{AUR|kaichat}}}}
* {{App|Lobe Chat|A modern, extensible chat framework for LLMs, supporting multiple AI providers, multi-modal interactions, and plugins.|https://github.com/lobehub/lobe-chat|{{AUR|lobe-chat}}}}
* {{App|LocalAI|Free, Open Source OpenAI alternative with CPU optimizations.|https://github.com/mudler/LocalAI|{{AUR|local-ai}}}}
* {{App|RisuAI|User-friendly software for LLM roleplaying with local AI models.|https://risuai.xyz|{{AUR|risuai-bin}}}}
* {{App|NextChat|A cross-platform ChatGPT client.|https://github.com/ChatGPTNextWeb/ChatGPT-Next-Web|{{AUR|nextchat-bin}}}}
* {{App|noi-desktop|AI-powered desktop assistant for exploration and task automation.|https://noi.ai|{{AUR|noi-desktop-bin}}}}
* {{App|Open-GPT|A ChatGPT client using the OpenAI API.|https://github.com/BeanDx/open-gpt/tree/main|{{AUR|open-gpt-bin}}}}
* {{App|SillyTavern|A feature-rich local interface for interacting with large language models (LLMs), generating images, and synthesizing speech.|https://sillytavern.app/|{{AUR|sillytavern-git}}}}
* {{App|[[Wikipedia:Mycroft (software)|Mycroft]]|Intelligent personal assistant and knowledge navigator with speech recognition.|https://mycroft.ai/|{{AUR|mycroft-core}}}}

==== Terminal clients ====

* {{App|AICommits|CLI that writes your git commit messages with AI.|https://github.com/Nutlope/aicommits|{{AUR|aicommits}}}}
* {{App|AIChat|A versatile CLI tool for interacting with AI models, featuring REPL-like functionality, shell assistance, and support for multiple AI providers.|https://github.com/sigoden/aichat|{{Pkg|aichat}}}}
* {{App|AIChat NG|An enhanced fork of AIChat with advanced features for terminal-based AI interactions.|https://github.com/blob42/aichat-ng|{{AUR|aichat-ng}}}}
* {{App|Gemini CLI|Open-source AI agent that brings the power of Google Gemini directly into your terminal.|https://github.com/google-gemini/gemini-cli|{{Pkg|gemini-cli}}}}
* {{App|GitHub Copilot CLI|Official CLI interface for GitHub Copilot coding assistant.|https://github.com/github/copilot-cli|{{AUR|github-copilot-cli}}}}
* {{App|OpenCommit|Auto-generate meaningful git commit messages with AI.|https://github.com/di-sukharev/opencommit|{{AUR|opencommit}}}}
* {{App|TLM|Local CLI Copilot powered by Ollama.|https://github.com/yusufcanb/tlm|{{AUR|tlm}}}}
* {{App|ShellGPT|A productivity-focused CLI tool powered by OpenAI's ChatGPT, designed for efficient command-line workflows.|https://github.com/TheR1D/shell_gpt|{{AUR|shellgpt-git}}}}

=== Development tools ===

* {{App|hfdownloader|Utility to download HuggingFace Models and Datasets.|https://github.com/bodaay/HuggingFaceModelDownloader|{{AUR|hfdownloader-git}}}}
* {{App|Rivet|IDE for creating complex AI agents and prompt chaining.|https://rivet.ironcladapp.com|{{AUR|ironclad-rivet-bin}}}}
* {{App|Kiro|Amazon's closed-source, AI-powered IDE for rapid prototyping to production.|https://kiro.dev/|{{AUR|kiro-ide}}}}
* {{App|koboldcpp|A simple one-file way to run various GGML and GGUF models with a KoboldAI UI.|https://github.com/LostRuins/koboldcpp|{{AUR|koboldcpp}}, {{AUR|koboldcpp-cuda}}, {{AUR|koboldcpp-hipblas}}}}
* {{App|llamafile|Distribute and run LLMs with a single file.|https://github.com/Mozilla-Ocho/llamafile|{{AUR|llamafile}}}}
* {{App|LM Studio|A user-friendly interface for discovering, downloading, and running local LLMs.|https://lmstudio.ai/|{{AUR|lmstudio-bin}}}}
* {{App|Msty|A simple and intuitive interface for accessing both local and online AI models.|https://msty.app|{{AUR|msty-bin}}}}
* {{App|netron|Visualizer for neural network, deep learning and machine learning models.|https://netron.app/|{{AUR|netron}}}}
* {{App|open-webui|Extensible self-hosted AI platform with WebUI and OpenAI API support for LLM runners.|https://github.com/open-webui/open-webui|{{AUR|open-webui-git}}}}

=== Coding assistants ===

* {{App|Crush|A powerful terminal-based AI assistant for developers, providing intelligent coding assistance directly in your terminal.|https://charm.sh/crush|{{AUR|crush}}, {{AUR|crush-bin}}}}
* {{App|Codename Goose|An extensible AI agent that goes beyond code suggestions - can install, execute, edit, and test with any LLM.|https://github.com/block/goose|{{AUR|codename-goose-bin}}}}
* {{App|Claude Code|An agentic coding tool that lives in your terminal.|https://github.com/anthropics/claude-code|{{AUR|claude-code}}}}
* {{App|codai|AI code assistant with session-based CLI for intelligent suggestions and refactoring.|https://github.com/meysamhadeli/codai|{{AUR|codai}}}}
* {{App|CodeGPT|A CLI written in Go language that writes git commit messages or does a code review brief for you using ChatGPT AI (gpt-4, gpt-3.5-turbo model) and automatically installs a git prepare-commit-msg hook.|https://github.com/appleboy/CodeGPT|{{AUR|codegpt-bin}}}}
* {{App|Cursor|Write, edit, and chat about your code with GPT.|https://cursor.so|{{AUR|cursor-bin}}}}
* {{App|opencode|AI coding agent built for the terminal.|https://github.com/sst/opencode|{{Pkg|opencode}}}}
* {{App|Kiro|An AI-powered IDE for rapid prototyping to production.|https://kiro.dev/ |{{AUR|kiro-ide}}}}
* {{App|qwen-code|CLI coding agent (fork of gemini-cli) with AI-powered code generation and assistance.|https://github.com/QwenLM/Qwen-Code|{{Pkg|qwen-code}}}}

=== Multimedia processing ===

==== Image generation ====

* {{App|RapidOCR|A cross platform OCR Library based on OnnxRuntime.|https://github.com/RapidAI/RapidOCR|{{AUR|python-rapidocr-onnxruntime}}}}
* {{App|Krita AI Diffusion|An intuitive AI-powered plugin for Krita, enabling seamless image inpainting and outpainting with optional text prompts.|https://github.com/Acly/krita-ai-diffusion|{{AUR|krita-ai-diffusion}}}}
* {{App|StabilityMatrix|A versatile package manager for Stable Diffusion, simplifying model management and integration.|https://github.com/LykosAI/StabilityMatrix|{{AUR|stabilitymatrix}}}}
* {{App|Stable Diffusion C++|Pure C/C++ implementation of Stable Diffusion for efficient inference on local machines.|https://github.com/leejet/stable-diffusion.cpp|{{AUR|stable-diffusion.cpp-git}}}}
* {{App|Stable Diffusion Web UI|Powerful web-based interface for Stable Diffusion, enabling high-quality image generation with customizable parameters.|https://github.com/AUTOMATIC1111/stable-diffusion-webui|{{AUR|stable-diffusion-webui-git}}}}
* {{App|Upscayl|A free and open-source AI-based image upscaler, enhancing image resolution while preserving quality.|https://github.com/upscayl/upscayl|{{AUR|upscayl-bin}}}}

==== Speech processing ====

* {{App|Coqui TTS|Deep learning toolkit for Text-to-Speech with support for 20+ languages.|https://github.com/coqui-ai/TTS|{{AUR|coqui-tts}}}}
* {{App|faster-whisper|Faster Whisper transcription implementation using CTranslate2.|https://github.com/guillaumekln/faster-whisper|{{AUR|python-faster-whisper}}}}
* {{App|Handy|A free, open source, and extensible speech-to-text application that works completely offline.|https://github.com/cjpais/Handy|{{AUR|handy}}}}
* {{App|MaryTTS|Multilingual TTS synthesis platform written in Java.|https://marytts.github.io/|{{AUR|marytts}}}}
* {{App|Piper|A fast, local neural text-to-speech system.|https://github.com/rhasspy/piper|{{AUR|piper-tts}}}}
* {{App|Sherpa-ONNX|Speech-to-text, text-to-speech, speaker diarization, and VAD using next-gen Kaldi with onnxruntime.|https://github.com/k2-fsa/sherpa-onnx|{{AUR|sherpa-onnx}}}}
* {{App|shisper|Script to generate subtitles and transcriptions using whisper.cpp.|https://github.com/M0Rf30/shisper|{{AUR|shisper-git}}}}
* {{App|vibe|Transcribe audio/video offline using OpenAI Whisper with GUI interface.|https://thewh1teagle.github.io/vibe/|{{AUR|vibe-bin}}}}
* {{App|VOICEVOX|Japanese TTS engine with anime-style character voices.|https://voicevox.hiroshiba.jp/|{{AUR|voicevox-appimage}}}}
* {{App|whisper.cpp|A C/C++ port of OpenAI's Whisper model for efficient speech recognition.|https://github.com/ggerganov/whisper.cpp|{{AUR|whisper.cpp}}, {{AUR|whisper.cpp-cuda}}, {{AUR|whisper.cpp-openvino}}}}
* {{App|whisper.cpp-models|Pre-trained models for whisper.cpp in various sizes.|https://github.com/ggerganov/whisper.cpp|{{AUR|whisper.cpp-model-large-v3}}, {{AUR|whisper.cpp-model-medium}}, {{AUR|whisper.cpp-model-small}}, {{AUR|whisper.cpp-model-tiny}}}}
* {{App|whispering|Open-source transcription application with global speech-to-text functionality.|https://whispering.bradenwong.com/|{{AUR|whispering-bin}}}}
* {{App|wiggly-stt|Local speech-to-text with whisper.cpp and clipboard integration.|https://github.com/hansp27/wiggly-stt|{{AUR|wiggly-stt}}}}

General recommendations

2026-04-26T21:36:37Z

Alad: /* Display server */ merge to List of applications/Other

[[Category:System administration]]
[[bs:General recommendations]]
[[ca:General recommendations]]
[[cs:General recommendations]]
[[el:General recommendations]]
[[es:General recommendations]]
[[fr:General recommendations]]
[[hu:General recommendations]]
[[it:General recommendations]]
[[ja:一般的な推奨事項]]
[[lv:General recommendations]]
[[pl:General recommendations]]
[[pt:General recommendations]]
[[ru:General recommendations]]
[[tr:General recommendations]]
[[zh-hans:建议阅读]]
[[zh-hant:General recommendations]]
{{Related articles start}}
{{Related|Frequently asked questions}}
{{Related|List of applications}}
{{Related|System maintenance}}
{{Related articles end}}

This document is an annotated index of popular articles and important information for improving and adding functionalities to the installed Arch system. Readers are assumed to have read and followed the [[Installation guide]] to obtain a basic Arch Linux installation. Having read and understood the concepts explained in [[#System administration]] and [[#Package management]] is ''required'' for following the other sections of this page and the other articles in the wiki.

== System administration ==

This section deals with administrative tasks and system management. See [[Core utilities]] and [[:Category:System administration]] for more.

=== Users and groups ===

A new installation leaves you with only the [[Wikipedia:Superuser|superuser]] account, better known as "root". Logging in as root for prolonged periods of time, possibly even exposing it via [[SSH]] on a server, [https://apple.stackexchange.com/questions/192365/is-it-ok-to-use-the-root-user-as-a-normal-user/192422#192422 is insecure]. Instead, you should create and use unprivileged user account(s) for most tasks, only using the root account for system administration. See [[Users and groups#User management]] for details.

Users and groups are a mechanism for ''access control''; administrators may fine-tune group membership and ownership to grant or deny users and services access to system resources. Read the [[Users and groups]] article for details and potential security risks.

=== Security ===

Read [[Security]] for recommendations and best practices on hardening the system.

For a list of applications to allow running commands or starting an interactive shell as another user (e.g. root), see [[List of applications/Security#Privilege elevation]]. For graphical equivalents (and how to avoid them), see [[Privilege elevation for graphical applications]].

{{Tip|More fine-grained privilege elevation is provided by [[polkit]], which requires additional setup for graphical environments.}}

=== Service management ===

Arch Linux uses [[systemd]] as the [[init]] process, which is a system and service manager for Linux. For maintaining your Arch Linux installation, it is a good idea to learn the basics about it.

Interaction with ''systemd'' is done through the ''systemctl'' command. See [[systemd#Basic systemctl usage]] for more information.

A logging system is also provided, with the command ''journalctl''. See [[journal]] for more information.

=== System maintenance ===

Arch is a rolling release system and has rapid package turnover, so users have to take some time to do [[system maintenance]].

== Package management ==

This section contains helpful information related to package management. See [[FAQ#Package management]] and [[:Category:Package management]] for more.

{{Note|It is imperative to keep up to date with changes in Arch Linux that require manual intervention '''before''' upgrading your system. Subscribe to the [https://lists.archlinux.org/mailman3/lists/arch-announce.lists.archlinux.org/ arch-announce mailing list] or the [https://archlinux.org/feeds/news/ recent news RSS feed]. Alternatively, check the front page [https://archlinux.org/ Arch news] every time before you update.}}

=== pacman ===

[[pacman]] is the Arch Linux ''pac''kage ''man''ager: it is highly encouraged to become familiar with it before reading any other articles.

For long term handling of cached packages, see [[pacman#Cleaning the package cache]].

See [[pacman/Tips and tricks]] for suggestions on how to improve your interaction with ''pacman'' and package management in general.

=== Repositories ===

See the [[Official repositories]] article for details about the purpose of each officially maintained repository.

If you plan on using 32-bit applications, you will want to enable the [[multilib]] repository.

The [[Unofficial user repositories]] article lists several other unsupported repositories.

You may consider installing the [[pkgstats]] service.

=== Mirrors ===

Visit the [[Mirrors]] article for steps on taking full advantage of using the fastest and most up to date mirrors of the official repositories. As explained in the article, a particularly good advice is to routinely check the [https://archlinux.org/mirrors/status/ Mirror Status] page for a list of mirrors that have been recently synced. This can be automated with [[Reflector]].

=== Arch Build System ===

''Ports'' is a system initially used by BSD distributions consisting of build scripts that reside in a directory tree on the local system. Simply put, each port contains a script within a directory intuitively named after the installable third-party application.

The [[Arch build system]] offers the same functionality by providing build scripts called [[PKGBUILD]]s, which are populated with information for a given piece of software: integrity hashes, project URL, version, license and build instructions. These PKGBUILDs are parsed by [[makepkg]], the actual program that generates packages that are cleanly manageable by ''pacman''.

Every package in the repositories along with those present in the AUR are subject to recompilation with ''makepkg''.

=== Arch User Repository ===

While the Arch Build System allows the ability of building software available in the official repositories, the [[Arch User Repository]] (AUR) is the equivalent for user submitted packages. It is an unsupported repository of build scripts accessible through the [https://aur.archlinux.org/ web interface] or through the [[Aurweb RPC interface]].

== Booting ==

This section contains information pertaining to the boot process. An overview of the Arch boot process can be found at [[Arch boot process]]. See [[:Category:Boot process]] for more.

=== Hardware auto-recognition ===

Hardware should be auto-detected by [[udev]] during the boot process by default. A potential improvement in boot time can be achieved by disabling module auto-loading and specifying required modules manually, as described in [[Kernel modules]]. Additionally, [[Xorg]] should be able to auto-detect required drivers using {{ic|udev}}, but users have the option to configure the X server manually too.

=== Microcode ===

Processors may have [https://www.anandtech.com/show/8376/intel-disables-tsx-instructions-erratum-found-in-haswell-haswelleep-broadwelly faulty behaviour], which the kernel can correct by updating the ''microcode'' on startup. See [[Microcode]] for details.

=== Retaining boot messages ===

Once the login prompt appears, the messages from boot are cleared, leaving users unable to gather feedback from them. [[Disable clearing of boot messages]] to overcome this limitation.

=== Num Lock activation ===

[[Wikipedia:Num Lock|Num Lock]] is a toggle key found in most keyboards. For activating Num Lock's number key-assignment during startup, see [[Activating numlock on bootup]].

== Graphical user interface ==

This section provides orientation for users wishing to run graphical applications on their system. See [[:Category:Graphical user interfaces]] for additional resources.

=== Display server ===

A display server or window server is a program whose primary task is to coordinate the input and output of its clients to and from the rest of the operating system, the hardware, and each other. See [[List of applications/Other#Display servers]] for an overview.

=== Display drivers ===

The default ''modesetting'' display driver will work with most video cards, but performance may be improved and additional features harnessed by installing the [[Graphics processing unit#Installation|appropriate driver]] for [[AMD]], [[Intel]] or [[NVIDIA]] products.

=== Desktop environments ===

Although the display server provides the basic framework for building a graphical environment, additional components may be considered necessary for a complete user experience. [[Desktop environment]]s such as [[KDE]], [[GNOME]], [[COSMIC]], [[Xfce]], [[Cinnamon]], [[LXDE]], bundle together a wide range of well-integrated applications, such as a window manager or compositor, panel/taskbar, file manager, terminal emulator, text editor, icons, and other utilities. Users with less experience may wish to install a desktop environment for a more familiar environment. See [[:Category:Desktop environments]] for additional resources.

=== Window managers or compositors ===

A full-fledged desktop environment provides a complete and consistent graphical user interface, but tends to consume a good amount of system resources. Users seeking to maximize performance or otherwise simplify their environment may opt to install a [[window manager]] or [[Wayland#Compositors|compositor]] alone and hand-pick desired extras. Using [[Xorg]], most desktop environments allow use of an alternative window manager as well. [[:Category:Dynamic window managers|Dynamic]], [[:Category:Stacking window managers|stacking]], and [[:Category:Tiling window managers|tiling]] window managers differ in their handling of window placement.

=== Display manager ===

Most desktop environments include a [[display manager]] for automatically starting the graphical environment and managing user logins. Users without a desktop environment can install one separately. Alternatively you may [[start X at login]] as a simple alternative to a display manager.

=== User directories ===

Well-known user directories like Downloads or Music are created by the {{ic|xdg-user-dirs-update.service}} user service, that is provided by {{Pkg|xdg-user-dirs}} and enabled by default upon install. If your desktop environment or window manager does not pull in the package, you can [[install]] it and run {{ic|xdg-user-dirs-update}} manually as per [[XDG user directories#Creating default directories]].

== Power management ==

This section may be of use to laptop owners or users otherwise seeking power management controls. See [[:Category:Power management]] for more.

See [[Power management]] for more general overview.

=== ACPI events ===

Users can configure how the system reacts to ACPI events such as pressing the power button or closing a laptop's lid. For the recommended method using [[systemd]], see [[Power management#ACPI events]]. For the old method, see [[acpid]].

=== CPU frequency scaling ===

Modern processors can decrease their frequency and voltage to reduce heat and power consumption. Less heat leads to more quiet system and prolongs the life of hardware. See [[CPU frequency scaling]] for details.

=== Laptops ===

For articles related to portable computing along with model-specific installation guides, please see [[:Category:Laptops]]. For a general overview of laptop-related articles and recommendations, see [[Laptop]].

=== Suspend and hibernate ===

See the main article: [[Power management/Suspend and hibernate]].

== Multimedia ==

[[:Category:Multimedia]] includes additional resources.

=== Sound system ===

[[ALSA]] is a kernel [[sound system]] that should work out the box (it just needs to be [[Advanced Linux Sound Architecture#Unmuting the channels|unmuted]]). [[Sound server]]s such as [[PipeWire]] and [[PulseAudio]] can offer additional features and support more complex audio configuration.

See [[Professional audio]] for advanced audio requirements.

== Networking ==

This section is confined to small networking procedures. See [[Network configuration]] for a full configuration guide and [[:Category:Networking]] for related articles.

=== DNS security ===

For better security while browsing the web, paying online, connecting to [[SSH]] services and similar tasks consider using [[DNSSEC]]-enabled [[DNS resolver]] that can validate signed [[Wikipedia:Domain Name System|DNS]] records, and an encrypted protocol such as [[Wikipedia:DNS over TLS|DNS over TLS]], [[Wikipedia:DNS over HTTPS|DNS over HTTPS]] or [[Wikipedia:DNSCrypt|DNSCrypt]]. See [[Domain name resolution]] for details.

=== Setting up a firewall ===

A firewall can provide an extra layer of protection on top of the Linux networking stack. While the stock Arch kernel is capable of using [[Wikipedia:Netfilter|Netfilter]]'s [[iptables]] and [[nftables]], neither are enabled by default. It is highly recommended to set up some form of firewall. See [[:Category:Firewalls]] for available guides.

=== Network shares ===

To share files among the machines in a network, follow the [[NFS]] or the [[SSHFS]] article.

Use [[Samba]] to join a Windows network. To configure the machine to use Active Directory for authentication, read [[Active Directory integration]].

See also [[:Category:Network sharing]].

== Input devices ==

This section contains popular input device configuration tips. See [[:Category:Input devices]] for more.

=== Keyboard layouts ===

Non-English or otherwise non-standard keyboards may not function as expected by default. The necessary steps to configure the keymap are different for virtual console and [[Xorg]], they are described in [[Keyboard configuration in console]] and [[Keyboard configuration in Xorg]] respectively.

=== Mouse buttons ===

Owners of advanced or unusual mice may find that not all mouse buttons are recognized by default, or may wish to assign different actions for extra buttons. Instructions can be found in [[Mouse buttons]].

=== Laptop touchpads ===

Many laptops use [[Wikipedia:Synaptics|Synaptics]] or [[Wikipedia:Alps Electric|ALPS]] "touchpad" pointing devices. For these, and several other touchpad models, you can use either the Synaptics input driver or libinput; see [[Touchpad Synaptics]] and [[libinput]] for installation and configuration details.

=== TrackPoints ===

See the [[TrackPoint]] article to configure your TrackPoint device.

== Optimization ==

This section aims to summarize tweaks, tools and available options useful to improve system and application performance.

=== Benchmarking ===

[[Benchmarking]] is the act of measuring performance and comparing the results to another system's results or a widely accepted standard through a unified procedure.

=== Improving performance ===

The [[Improving performance]] article gathers information and is a basic rundown about gaining performance in Arch Linux.

=== Solid state drives ===

The [[Solid state drive]] article covers many aspects of solid state drives, including configuring them to maximize their lifetimes, e.g. with [[TRIM]].

== System services ==

This section relates to [[daemons]].

=== File index and search ===

Most distributions have a ''locate'' command available to be able to quickly search files. Arch Linux provides several alternatives, see [[locate]] for details.

[[List of applications/Utilities#File searching|Desktop search engines]] provide a similar service, while better integrated into [[desktop environment]]s.

=== Local mail delivery ===

A default setup does not provide a way to synchronize mail. A list of mail delivery agents is available in the [[Mail server]] article.

=== Printing ===

[[CUPS]] is a standards-based, open source printing system developed by OpenPrinting for Linux. See [[:Category:Printers]] for printer-specific articles.

== Appearance ==

This section contains frequently-sought "eye candy" tweaks for an aesthetically pleasing Arch experience. See [[:Category:Eye candy]] for more.

=== Fonts ===

You may wish to install a set of TrueType fonts, as only unscalable bitmap fonts are included in a basic Arch system. There are several general-purpose [[Fonts#Families|font families]] providing large [[Wikipedia:Unicode|Unicode]] coverage and even [[Metric-compatible fonts|metric compatibility]] with fonts from other operating systems.

A plethora of information on the subject can be found in the [[Fonts]] and [[Font configuration]] articles.

If spending a significant amount of time working from the virtual console (i.e. outside an X server), users may wish to change the console font to improve readability; see [[Linux console#Fonts]].

=== GTK and Qt themes ===

A big part of the applications with a graphical interface for Linux systems are based on the [[GTK]] or the [[Qt]] toolkits. See those articles and [[Uniform look for Qt and GTK applications]] for ideas to improve the appearance of your installed programs and adapt it to your liking.

== Console improvements ==

This section applies to small modifications that improve console programs' practicality. See [[:Category:Command-line shells]] for more.

=== Tab-completion enhancements ===

It is recommended to properly set up extended [[Wikipedia:Command-line_completion|tab completion]] right away, as instructed in the article of your chosen [[shell]].

=== Aliases ===

Aliasing a command, or a group thereof, is a way of saving time when using the console. This is especially helpful for repetitive tasks that do not need significant alteration to their parameters between executions. Common time-saving aliases can be found in [[Bash#Aliases]], which are easily portable to [[zsh]] as well.

=== Alternative shells ===

[[Bash]] is the shell installed by default in an Arch system. The live installation media, however, uses [[zsh]] with the {{Pkg|grml-zsh-config}} addon package. See [[Command-line shell#List of shells]] for more alternatives.

=== Bash additions ===

A list of miscellaneous Bash settings, history search and [[Readline]] macros is available in [[Bash#Tips and tricks]].

=== Colored output ===

This section is covered in [[Color output in console]].

=== Compressed files ===

Compressed files, or archives, are frequently encountered on a GNU/Linux system. [[Tar]] is one of the most commonly used archiving tools, and users should be familiar with its syntax (Arch Linux packages, for example, are simply {{Pkg|zstd}} compressed tarballs). See [[Archiving and compression]].

=== Console prompt ===

The console prompt ({{ic|PS1}}) can be customized to a great extent. See [[Bash/Prompt customization]] or [[Zsh#Prompts]] if using Bash or Zsh, respectively.

=== Emacs shell ===

Emacs is known for featuring options beyond the duties of regular text editing, one of these being a full shell replacement. Consult [[Emacs#Colored output issues]] for a fix regarding garbled characters that may result from enabling colored output.

=== Mouse support ===

Using a mouse with the console for copy-paste operations can be preferred over [[GNU Screen]]'s traditional copy mode. Refer to [[General purpose mouse]] for comprehensive directions. Note that you can already do this in [[terminal emulator]]s with the [[clipboard]].

=== Session management ===

Using terminal multiplexers like [[tmux]] or [[GNU Screen]], programs may be run under sessions composed of tabs and panes that can be detached at will, so when the user either kills the terminal emulator, terminates [[X]], or logs off, the programs associated with the session will continue to run in the background as long as the terminal multiplexer server is active. Interacting with the programs requires reattaching to the session.

List of applications/Other

2026-04-26T21:36:23Z

Alad: /* Display managers */ merge from General recommendations#Display server

[[Category:Applications]]
[[Category:Lists of software]]
[[es:List of applications (Español)/Other]]
[[hu:List of applications (Magyar)/Other]]
[[ja:アプリケーション一覧/その他]]
[[pl:List of applications (Polski)/Other]]
[[zh-hans:List of applications/Other]]
{{List of applications navigation}}

== Organization ==

=== CalDAV/CardDAV servers ===

* {{App|Baïkal|A lightweight CalDAV+CardDAV server.|https://sabre.io/baikal/|{{AUR|baikal}}}}
* {{App|kcaldav|Simple, safe, minimal CalDAV server.|https://kristaps.bsd.lv/kcaldav|{{AUR|kcaldav}}}}
* {{App|[[Radicale]]|Free and Open-Source CalDAV and CardDAV Server.|https://radicale.org|{{Pkg|radicale}}}}
* {{App|xandikos|A lightweight yet complete CardDAV/CalDAV server that backs onto a Git repository.|https://www.xandikos.org|{{Pkg|xandikos}}}}

=== Personal information managers ===

These applications support time, task and contacts management.

* {{App|[[Evolution]]|Personal information management application that provides integrated mail, calendaring and address book functionality. Part of {{Grp|gnome-extra}}.|https://gitlab.gnome.org/GNOME/evolution/-/wikis/home|{{Pkg|evolution}}}}
* {{App|[[Wikipedia:Kontact|Kontact]]|Integrated solution to your personal information management. Part of {{Grp|kde-pim}}.|https://kontact.kde.org/|{{Pkg|kontact}}}}
* {{App|Merkuro|Calendar and contact application that allows you to manage your tasks, events and contacts. Part of {{Grp|kde-pim}}.|https://apps.kde.org/merkuro/|{{Pkg|merkuro}}}}
* {{App|Osmo|GTK personal organizer, which includes calendar, tasks manager and address book modules.|https://osmo-pim.sourceforge.net|{{Pkg|osmo}}}}
* {{App|[[Wikipedia:SeaMonkey#Mail|SeaMonkey Mail & Newsgroups]] with [[Wikipedia:Lightning (software)|Lightning]]|Extension to SeaMonkey that provides calendar and task support.|https://www.seamonkey-project.org/|{{AUR|seamonkey}}}}
* {{App|[[Thunderbird]]|A fully featured E-mail client formerly developed by Mozilla.|https://www.thunderbird.net|{{Pkg|thunderbird}}}}

=== Time management ===

==== Console ====

* {{App|Calcurse|Text-based ncurses calendar and scheduling system (supports CalDAV)|https://calcurse.org|{{Pkg|calcurse}}}}
* {{App|ccal|A console program which writes a calendar together with Chinese calendar to standard output.|https://ccal.chinesebay.com/ccal/ccal.htm|{{AUR|ccal}}}}
* {{App|khal|Command-line (non-interactive) and ncurses (interactive) calendar system (supports CalDAV)|https://github.com/pimutils/khal|{{Pkg|khal}}}}
* {{App|gcalcli|Command-line (non-interactive) Google Calendar for event management and agendas.|https://github.com/insanum/gcalcli|{{AUR|gcalcli}}}}
* {{App|mail2rem|Small script for importing ''.ics'' calendars from Maildir to Remind calendar.|https://github.com/esovetkin/mail2rem|{{AUR|mail2rem-git}}}}
* {{App|Pal|Very lightweight calendar with both interactive and non-interactive interfaces.|https://palcal.sourceforge.net/|{{AUR|pal}}}}
* {{App|pcal|A tool to create pdf calendars from pcal input which can be exported by some calendar programs.|https://sourceforge.net/projects/pcal/|{{AUR|pcal}}}}
* {{App|[[Remind]]|Highly sophisticated text-based calendaring and notification system.|https://dianne.skoll.ca/projects/remind/|{{Pkg|remind}}}}
* {{App|When|Simple personal calendar program.|http://lightandmatter.com/when/when.html|{{Pkg|when}}}}
* {{App|Wyrd|Text-based front-end to Remind, a calendar and alarm program used on UNIX and Linux computers.|https://gitlab.com/wyrd-calendar/wyrd|{{AUR|wyrd}}}}

==== Graphical ====

* {{App|Agenda|Calendar application built with MauiKit. Part of {{Grp|maui}}.|https://mauikit.org/apps/|{{Pkg|maui-agenda}}}}
* {{App|Calindori|Calendar application for Plasma Mobile.|https://apps.kde.org/calindori/|{{Pkg|calindori}}}}
* {{App|chinese-calendar|Chinese traditional calendar for Ubuntu Kylin.|https://launchpad.net/chinese-calendar/|{{Pkg|chinese-calendar}}}}
* {{App|CoreTime|Very simple Clock/Calendar application which shows a clock, supports alarms, reminders, a stop watch and a timer. Part of C-Suite.|https://cubocore.gitlab.io/|{{AUR|coretime}}}}
* {{App|Deepin Calendar|Calendar application for Deepin.|https://www.deepin.org/en/original/dde-calendar/|{{Pkg|deepin-calendar}}}}
* {{App|etmtk (Event and Task Manager)|Simple application with a "Getting Things Done!" approach to handling events, tasks, activities, reminders and projects.|https://people.duke.edu/~dgraham/ETMtk/|{{AUR|etmtk}}}}
* {{App|Gahshomar|Persian (Jalali/Farsi) calendar.|https://gahshomar.github.io/gahshomar/|{{AUR|gahshomar}}}}
* {{App|GNOME Calendar|Calendar application for GNOME. Part of {{Grp|gnome}}.|https://apps.gnome.org/Calendar/|{{Pkg|gnome-calendar}}}}
* {{App|[[Wikipedia:KAlarm|KAlarm]]|Personal alarm message, command and email scheduler, part of {{Grp|kde-pim}}.|https://apps.kde.org/kalarm/|{{Pkg|kalarm}}}}
* {{App|Kongress|Companion application for conferences made by KDE. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/kongress/|{{Pkg|kongress}}}}
* {{App|[[Wikipedia:Kontact#Organizer|KOrganizer]]|Calendar and scheduling program, part of {{Grp|kde-pim}}.|https://kontact.kde.org/components/korganizer|{{Pkg|korganizer}}}}
* {{App|Merkuro Calendar|Calendar application using Akonadi that supports both local and online calendars: Nextcloud, Google Calendar, Outlook, Caldav and more. Part of {{Grp|kde-pim}}.|https://apps.kde.org/merkuro.calendar/|{{Pkg|merkuro}}}}
* {{App|[[Nextcloud]] Calendar|Calendar app for Nextcloud.|https://github.com/nextcloud/calendar|{{Pkg|nextcloud-app-calendar}}}}
* {{App|Outspline|Extensible outliner with advanced time management features, supporting events with complex recurrence schemes.|https://kynikos.github.io/outspline/|{{AUR|outspline}}}}
* {{App|TkRemind|Sophisticated calendar and alarm program.|https://dianne.skoll.ca/projects/remind/|{{Pkg|remind}}}}

=== Timers ===

==== Countdown timers and stopwatch ====

* {{App|arttime|Clock, timer, pattern-based time manager, ASCII art viewer. Set a one-off, multiple, repeating, pattern-based timers.|https://github.com/poetaman/arttime|{{AUR|arttime-git}}}}
* {{App|Chess Clock|Simple application to provide time control for over-the-board chess games.|https://apps.gnome.org/Chessclock/|{{Pkg|chess-clock}}}}
* {{App|GNOME Clocks|Clocks application for GNOME, including alarm, stopwatch and timer functionality. Part of {{Grp|gnome}}.|https://apps.gnome.org/Clocks/|{{Pkg|gnome-clocks}}}}
* {{App|Hourglass|Simple time keeping application designed for elementary OS.|https://github.com/sgpthomas/hourglass|{{AUR|hourglass}}}}
* {{App|KClock|A convergent clock application for Plasma. It contains alarm, timer, stopwatch and timezone functionalities. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/kclock/|{{Pkg|kclock}}}}
* {{App|Kronometer|Stopwatch application for KDE.|https://apps.kde.org/kronometer/|{{Pkg|kronometer}}}}
* {{App|KTeaTime|Handy timer for steeping tea. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/kteatime/|{{Pkg|kteatime}}}}
* {{App|pystopwatch|Stopwatch written in Python with a clock and two countdown functions that can minimize to the tray.|https://xyne.dev/projects/pystopwatch/|{{AUR|pystopwatch}}}}
* {{App|snore|A program like sleep, but with feedback.|https://github.com/clamiax/snore|{{AUR|snore-git}}}}
* {{App|termdown|Countdown timer and stopwatch in your terminal.|https://github.com/trehn/termdown|{{Pkg|termdown}}}}

==== Break timers ====

* {{App|Break Timer|Keeps track of how much you are using the computer, and it reminds you to take regular breaks. Works only in GNOME.|https://wiki.gnome.org/Apps/BreakTimer|{{Pkg|gnome-break-timer}}}}
* {{App|RSI Break|Takes care of your health and regularly breaks your work to avoid repetitive strain injury (RSI) [https://bugs.kde.org/show_bug.cgi?id{{=}}422033 on Xorg].|https://apps.kde.org/rsibreak/|{{Pkg|rsibreak}}}}
* {{App|Safe Eyes|Tool to reduce and prevent repetitive strain injury (RSI).|https://slgobinath.github.io/SafeEyes/|{{AUR|safeeyes}}}}
* {{App|Work-break|Work and rest time balancer taking into account your current and today strain.|https://github.com/ShadoySV/work-break/|{{AUR|work-break}}}}
* {{App|[[Wikipedia:Workrave|Workrave]]|Program that assists in the recovery and prevention of RSI [https://bbs.archlinux.org/viewtopic.php?id{{=}}285701 on Xorg].|https://workrave.org/|{{Pkg|workrave}}}}

==== Pomodoro timers ====

See [[Wikipedia:Pomodoro Technique]] for an introduction.

* {{App|flow|Pomodoro app that blocks distractions while you work.|https://github.com/iamsergio/flow-pomodoro|{{AUR|flow-pomodoro}}}}
* {{App|Francis|App that uses the well-known pomodoro technique to help you get more productive. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/francis/|{{Pkg|francis}}}}
* {{App|Gnomato|Timer for the Pomodoro Technique.|https://github.com/diegorubin/gnomato|{{AUR|gnomato}}}}
* {{App|Pilorama|Eye-candy timeboxing tool written in QML|https://github.com/eplatonoff/pilorama|{{AUR|pilorama-git}}}}
* {{App|Pomodoro|Time management utility for GNOME based on the Pomodoro Technique.|https://gnomepomodoro.org/|{{AUR|gnome-shell-pomodoro}}}}
* {{App|Pomodoro-Logger|Pomodoro timer and logger with [[Wikipedia:Kanban board|Kanban board]] for task management and tracking.|https://github.com/zxch3n/PomodoroLogger|{{AUR|pomodoro-logger}}}}
* {{App|potato-c|A minimal and efficient pomodoro timer with server-client structure.|https://github.com/nimaaskarian/potato-c|{{AUR|potato-c}}}}
* {{App|Solanum|Pomodoro timer for the GNOME desktop.|https://apps.gnome.org/Solanum/|{{Pkg|solanum}}}}
* {{App|Tomate|Timer for the Pomodoro Technique.|https://github.com/eliostvs/tomate-gtk|{{AUR|tomate-gtk}}}}
* {{App|Tomighty|Desktop timer for the Pomodoro Technique.|https://tomighty.github.io|{{AUR|tomighty}}}}

=== Time trackers ===

* {{App|ActivityWatch|A self/local-hosted, cross-platform, client-server, privacy-focused active window tracker.|https://github.com/ActivityWatch/activitywatch|{{AUR|activitywatch-bin}}}}
* {{App|Hamster|Time tracking application that helps you to keep track on how much time you have spent during the day on activities you choose to track.|http://projecthamster.org/|{{Pkg|hamster-time-tracker}}}}
* {{App|Kapow|Punch clock to track time spent on projects.|https://gottcode.org/kapow/|{{AUR|kapow}}}}
* {{App|KTimeTracker|Todo management and time tracking application.|https://apps.kde.org/ktimetracker/|{{Pkg|ktimetracker}}}}
* {{App|Tider|Lightweight time tracking application (GTK)|https://github.com/naspeh/tider|{{AUR|tider-git}}}}
* {{App|Timenaut|Time tracker that tracks active windows and lets you sort them into categories. Based on the [https://electronjs.org/ Electron] platform.|https://timenaut.app/|{{AUR|timenaut-appimage}}}}
* {{App|Timetrack|Simple time-tracking app for GNOME.|https://gitlab.gnome.org/danigm/timetrack|{{AUR|timetrack}}}}
* {{App|Timewarrior|A command-line time-tracking application.|https://timewarrior.net/|{{Pkg|timew}}}}
* {{App|Wakatime|Open source plugins for metrics about your programming with intuitive web-interface.|https://wakatime.com/|{{AUR|wakatime}}}}

=== Task management ===

==== Console ====

* {{App|c3|A multi-platform TUI todo manager that extends calcurse's todo format to have a tree-like dependency structure, and even more! |https://github.com/nimaaskarian/c3|{{AUR|c3}}}}
* {{App|Cfait|Powerful, simple, elegant, and lightweight CalDAV task manager (TUI & GUI).|https://codeberg.org/trougnouf/cfait|{{AUR|cfait}}}}
* {{App|dijo|Scriptable, curses-based, digital habit tracker |https://github.com/nerdypepper/dijo|{{AUR|dijo}}}}
* {{App|Taskbook|Tasks, boards and notes for the command-line habitat.|https://github.com/klauscfhq/taskbook|{{AUR|taskbook}}}}
* {{App|Taskell|A command-line kanban board/task manager.|https://github.com/smallhadroncollider/taskell|{{AUR|taskell}}}}
* {{App|[[Wikipedia:Taskwarrior|Taskwarrior]]|Command-line To-do list application with support for lua customization and more.|https://taskwarrior.org/|{{Pkg|task}}}}
* {{App|todoman|Command-line To-do list manager (supports CalDAV)|https://github.com/pimutils/todoman|{{Pkg|todoman}}}}
* {{App|Todo.txt|Small command-line To-do manager.|https://github.com/todotxt/todo.txt-cli/|{{AUR|todotxt}}}}
* {{App|TuDu|Ncurses-based hierarchical To-do list manager with vim-like keybindings.|https://code.meskio.net/tudu/|{{AUR|tudu}}}}

==== Graphical ====

* {{App|Agenda|Simple, fast, no-nonsense to-do (task) list for elementary OS.|https://github.com/dahenson/agenda|{{AUR|agenda}}}}
* {{App|Cfait|Powerful, simple, elegant, and lightweight CalDAV task manager (TUI & GUI).|https://codeberg.org/trougnouf/cfait|{{AUR|cfait}}}}
* {{App|Effitask|Graphical task manager, based on the [http://todotxt.com/ Todo.txt] format.|https://github.com/sanpii/effitask|{{AUR|effitask}}}}
* {{App|Endeavour|Personal task manager for GNOME. Part of {{Grp|gnome-extra}}.|https://wiki.gnome.org/Apps/Todo|{{Pkg|endeavour}}}}
* {{App|Errands|Todo application for those who prefer simplicity.|https://apps.gnome.org/List/|{{Pkg|errands}}}}
* {{App|Go For It!|Simple and stylish productivity app, featuring a to-do list, merged with a timer that keeps your focus on the current task. To-do lists are stored in the [http://todotxt.com/ Todo.txt] format.|https://manuelkehl.de/projects/go-for-it/|{{AUR|go-for-it}}}}
* {{App|GTG|Personal tasks and TODO list items organizer for GNOME inspired by the [[Wikipedia:Getting Things Done|Getting Things Done (GTD)]] methodology.|https://github.com/getting-things-gnome/gtg|{{AUR|gtg}}}}
* {{App|KomoDo|Todo manager that uses todo.txt specification.|https://apps.kde.org/komodo/|{{Pkg|komodo}}}}
* {{App|[[Nextcloud]] Tasks|Tasks app for Nextcloud.|https://github.com/nextcloud/tasks|{{Pkg|nextcloud-app-tasks}}}}
* {{App|Planner|Task manager with Todoist support.|https://useplanner.com/|{{AUR|planify}}}}
* {{App|ptask|GTK task manager based on [[Wikipedia:Taskwarrior|Taskwarrior]].|https://wpitchoune.net/ptask/|{{AUR|ptask}}}}
* {{App|sleek|todo.txt app with modern GUI. Based on the [https://electronjs.org/ Electron] platform.|https://github.com/ransome1/sleek/|{{AUR|sleek}}}}
* {{App|TickTick|Is a simple and effective to-do list and task manager app with seamless cloud synchronization across all your devices|https://ticktick.com/|{{AUR|ticktick}}}}
* {{App|Zanshin|To-do management application for KDE. Part of {{Grp|kde-pim}}.|https://apps.kde.org/zanshin/|{{Pkg|zanshin}}}}

=== Contacts management ===

==== Console ====

* {{App|Abook|Text-based contacts manager designed for use with mutt.|https://abook.sourceforge.net/|{{AUR|abook}}}}
* {{App|Khard|Command-line addressbook that is able to sync with CardDAV-servers.|https://github.com/scheibler/khard|{{Pkg|khard}}}}

==== Graphical ====

* {{App|Addresses|Address book application for GNUstep.|https://www.nongnu.org/gap/addresses/|{{AUR|addresses.app}}}}
* {{App|Communicator|Integrated address book and dialer application features the search for and view of contacts, edit contact details, and make new contacts, favorites, and dialer pad. Part of {{Grp|maui}}.|https://mauikit.org/apps/communicator/|{{Pkg|communicator}}}}
* {{App|GNOME Contacts|Contacts manager for GNOME. Part of {{Grp|gnome}}.|https://apps.gnome.org/Contacts/|{{Pkg|gnome-contacts}}}}
* {{App|KAddressBook|Address book manager for KDE. Part of {{Grp|kde-pim}}.|https://kontact.kde.org/components/kaddressbook|{{Pkg|kaddressbook}}}}
* {{App|LDAP Administration Tool|Browse LDAP-based directories and add/edit/delete entries contained within.|https://sourceforge.net/projects/ldap-at/|{{AUR|lat}}}}
* {{App|Merkuro Contacts|Address book using Akonadi. Part of {{Grp|kde-pim}}.|https://apps.kde.org/merkuro.contact/|{{Pkg|merkuro}}}}
* {{App|[[Nextcloud]] Contacts|Contacts app for Nextcloud.|https://github.com/nextcloud/contacts|{{Pkg|nextcloud-app-contacts}}}}
* {{App|[[phpLDAPadmin]]|LDAP client webapp. Its hierarchical tree-viewer and advanced search functionality make it intuitive to browse and administer your LDAP directory.|https://phpldapadmin.sourceforge.net/|{{Pkg|phpldapadmin}}}}
* {{App|[[Thunderbird]] with [https://gitlab.com/CardBook/CardBook CardBook] extension|address book based on the CardDAV and vCard standards.|https://gitlab.com/CardBook/CardBook|{{Pkg|thunderbird}}}}

=== Financial management ===

See also [[Wikipedia:Comparison of accounting software]].

==== Console ====

* {{App|Beancount|A double-entry bookkeeping computer language that lets you define financial transaction records in a text file, read them in memory, generate a variety of reports from them, and provides a web interface.|https://beancount.github.io/|{{AUR|beancount}}}}
* {{App|hledger|An accounting program for tracking money, time, or any other commodity, using double-entry accounting and a simple, editable file format. hledger is inspired by and largely compatible with ledger.|https://hledger.org/|{{Pkg|hledger}}}}
* {{App|[[Ledger]]|Ledger is a powerful, double-entry accounting system that is accessed from the UNIX command-line.|https://www.ledger-cli.org/|{{Pkg|ledger}}}}

==== Graphical ====

* {{App|Eqonomize!|Cross-platform personal accounting software, with focus on efficiency and ease of use for the small household economy.|https://eqonomize.github.io/|{{AUR|eqonomize}}}}
* {{App|[[ERPNext]]|Free and open source Enterprise Resource Planning (ERP).|https://github.com/frappe/erpnext|{{AUR|erpnext}}}}
* {{App|[[Wikipedia:GnuCash|GnuCash]]|Financial application that implements a double-entry book-keeping system with features for small business accounting.|https://www.gnucash.org/|{{Pkg|gnucash}}}}
* {{App|Grisbi|Personal finance system which manages third party, expenditure and receipt categories, as well as budgetary lines, financial years, and other information that makes it suitable for associations.|https://www.grisbi.org/|{{AUR|grisbi}}}}
* {{App|[[Wikipedia:HomeBank|HomeBank]]|Easy to use finance manager that can analyse your personal finance in detail using powerful filtering tools and graphs.|http://homebank.free.fr/|{{Pkg|homebank}}}}
* {{App|[[Wikipedia:KMyMoney|KMyMoney]]|Personal finance manager that operates in a similar way to [[Wikipedia:Microsoft Money|Microsoft Money]]. It supports different account types, categorisation of expenses and incomes, reconciliation of bank accounts and import/export to the “QIF” file format.|https://kmymoney.org/|{{Pkg|kmymoney}}}}
* {{App|Kresus|Self-hosted personal finance management software. It automatically retrieves every day all your new bank transactions and lets you categorize them, study them through charts and establish a budget.|https://kresus.org/en/|{{Pkg|kresus}}}}
* {{App|Manager|Proprietary accounting software for small business.|https://www.manager.io/|{{AUR|manager-accounting}}}}
* {{App|Money Manager EX|An easy-to-use personal finance suite|https://www.moneymanagerex.org/|{{AUR|moneymanagerex}}}}
* {{App|[[Odoo]]|Open source ERP system purely in Python. Previously known as OpenERP.|https://www.odoo.com/|{{AUR|odoo-venv}}}}
* {{App|Skrooge|Personal finances manager for the KDE desktop.|https://skrooge.org/|{{Pkg|skrooge}}}}

=== Cryptocurrency ===

* {{App|Atomic Wallet|Manage your Bitcoin, Ethereum, XRP, Litecoin, XLM, and over 300 other coins and tokens. |https://atomicwallet.io/|{{AUR|atomicwallet}}}}
* {{App|Bitcoin Core|Connect to the Bitcoin P2P Network.|https://bitcoincore.org/|{{Pkg|bitcoin-qt}}}}
* {{App|Cake Wallet|Multicurrency wallet.|https://github.com/cake-tech/cake_wallet|{{AUR|cake-wallet-bin}}}}
* {{App|Coinomi|Securely store, manage and exchange Bitcoin, Ethereum, and more than 1,770 other blockchain assets.|https://www.coinomi.com/|{{AUR|coinomi-wallet-bin}}}}
* {{App|Cointop|Terminal based application for tracking cryptocurrencies.|https://cointop.sh/|{{AUR|cointop}}}}
* {{App|Dogecoin Core|Dogecoin Core wallet, Allows you to connect to the Dogecoin P2P Network.|https://dogecoin.com/|{{AUR|dogecoin-qt}}, {{AUR|multidoge}}}}
* {{App|Electrum|Lightweight Bitcoin client.|https://electrum.org/|{{Pkg|electrum}}}}
* {{App|Exodus|All-in-one proprietary application to secure, manage, and exchange blockchain assets. Based on the [https://electronjs.org/ Electron] platform.|https://www.exodus.io/|{{AUR|exodus}}}}
* {{App|Feather Wallet|Lightweight Monero wallet.|https://featherwallet.org/|{{AUR|feather-wallet}}}}
* {{App|Monero|Monero wallet.|https://getmonero.org/|{{Pkg|monero-gui}}, {{Pkg|monero}}}}
* {{App|Sparrow Wallet|Advanced Bitcoin client.|https://sparrowwallet.com/|{{AUR|sparrow-wallet}}}}

=== Project management ===

See also [[Wikipedia:Comparison of project management software]].

* {{App|[[Wikipedia:Calligra Plan|Calligra Plan]]|Project management application, which is intended for managing moderately large projects with multiple resources.|https://calligra.org/components/plan/|{{Pkg|calligra-plan}}}}
* {{App|[[Wikipedia:GanttProject|GanttProject]]|Project scheduling application featuring gantt chart, resource management, calendaring.|https://www.ganttproject.biz/|{{AUR|ganttproject}}}}
* {{App|[[Notion-app]]|A note-taking software and project management software that is used for note-taking, task management, project management, knowledge management, and personal knowledge management. |https://www.notion.so/|{{AUR|notion-app-electron}}}}
* {{App|Planner|Project management application for GNOME.|https://wiki.gnome.org/Apps/Planner|{{Pkg|planner}}}}
* {{App|[[Wikipedia:ProjectLibre|ProjectLibre]]|Project management software alternative to [[Wikipedia:Microsoft Project|Microsoft Project]].|https://www.projectlibre.com/product/projectlibre-open-source{{Dead link|2025|08|15|status=404}}|{{AUR|projectlibre}}}}
* {{App|[[Wikipedia:TaskJuggler|TaskJuggler]]|Modern and powerful project management tool. Its new approach to project planning and tracking is more flexible and superior to the commonly used Gantt chart editing tools.|https://taskjuggler.org/|{{AUR|taskjuggler}}}}

=== Bookmark management ===

* {{App|KEditBookmarks|Bookmark organizer and editor. Part of {{Grp|kde-utilities}}.|https://invent.kde.org/utilities/keditbookmarks|{{Pkg|keditbookmarks}}}}
* {{App|Read It Later|Simple Wallabag client.|https://gitlab.gnome.org/World/read-it-later|{{Pkg|read-it-later}}}}

=== Recipe management ===

* {{App|Gourmand|Simple but powerful recipe-managing application.|https://github.com/GourmandRecipeManager/gourmand|{{AUR|gourmand}}}}
* {{App|Recipes|Recipe management application for GNOME. Part of {{Grp|gnome-extra}}.|https://wiki.gnome.org/Apps/Recipes|{{Pkg|gnome-recipes}}}}

=== Travel management ===

See also [[List of applications/Science#Navigation and routing]].

* {{App|Itinerary|Digital travel assistant with a priority on protecting your privacy. Part of {{Grp|kde-pim}}.|https://apps.kde.org/itinerary/|{{Pkg|itinerary}}}}

=== Health management ===

* {{App|Health|Health tracking app for the GNOME desktop.|https://apps.gnome.org/Health/|{{Pkg|health}}}}

== Education ==

See also [[List of games#Education]].

* {{App|Artikulate|Pronunciation trainer that helps improving and perfecting a learner's pronunciation skills for a foreign language. Part of {{Grp|kde-education}}.|https://apps.kde.org/artikulate/|{{Pkg|artikulate}}}}
* {{App|Fretboard|Look up guitar chords.|https://apps.gnome.org/Fretboard/|{{Pkg|fretboard}}}}
* {{App|Kalm|Teach you different breathing techniques. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/kalm/|{{Pkg|kalm}}}}
* {{App|[[Moodle]]|Open-source software learning management system.|https://moodle.org/|{{AUR|moodle}}}}
* {{App|[[Wikipedia:OpenBoard|OpenBoard]]|Interactive whiteboard software for schools and universities.|https://openboard.ch/index.en.html|{{AUR|openboard}}}}
* {{App|Wike|Wikipedia reader for the GNOME desktop.|https://apps.gnome.org/Wike/|{{Pkg|wike}}}}
* {{App|Wildcard|Provides a simple interface to test/practice regular expressions.|https://gitlab.gnome.org/World/Wildcard|{{Pkg|wildcard}}}}

=== Flashcards ===

See also [[Wikipedia:List of flashcard software]].

* {{App|[[Anki]]|Intelligent spaced-repetition memory training program.|https://apps.ankiweb.net/|{{Pkg|anki}}}}
* {{App|jVLT|Vocabulary learning tool.|https://www.linuxlinks.com/jVLT/|{{AUR|jvlt}}}}
* {{App|KWordQuiz|Tool that gives you a powerful way to master new vocabularies. Part of {{Grp|kde-education}}.|https://apps.kde.org/kwordquiz/|{{Pkg|kwordquiz}}}}
* {{App|[[Mnemosyne]]|Flash-card tool which optimizes your learning process.|https://mnemosyne-proj.org/|{{AUR|mnemosyne}}}}
* {{App|Parley|Program to help you memorize things. It uses the spaced repetition learning method, also known as flash cards. Part of {{Grp|kde-education}}.|https://apps.kde.org/parley/|{{Pkg|parley}}}}
* {{App|Pauker|Flash card based learning tool using shortterm and longterm memory training.|https://pauker.sourceforge.net/|{{AUR|pauker}}}}
* {{App|StudyFlash|Learn flashcards inside your terminal|https://github.com/Alone2/studyFlash|{{AUR|studyflash}}}}

=== Touch typing ===

==== Console ====

* {{App|Dvorak 7min|Simple ncurses-based typing tutor for those trying to become fluent with the Dvorak keyboard layout.|https://github.com/yaychris/dvorak7min|{{AUR|dvorak7min}}}}
* {{App|GNU Typist|Universal typing tutor.|https://www.gnu.org/software/gtypist/|{{AUR|gtypist}}}}
* {{App|psani-profi|Program that will teach you touchtyping (Czech).|https://www.sallyx.org/sally/psani-vsemi-deseti/|{{AUR|psani-profi}}}}
* {{App|Typespeed|Test your typing speed, and get your fingers' CPS.|https://typespeed.sourceforge.net/|{{AUR|typespeed}}}}
* {{App|typiskt|touchtype training in the terminal (Bash).|https://github.com/budlabs/typiskt|{{AUR|typiskt}}}}

==== Graphical ====

* {{App|Klavaro|Teaching touch typing that intends to be keyboard and language independent.|https://klavaro.sourceforge.io/|{{Pkg|klavaro}}}}
* {{App|[[Wikipedia:KTouch|KTouch]]|Program to learn and practice touch typing. Part of {{Grp|kde-education}}.|https://apps.kde.org/ktouch/|{{Pkg|ktouch}}}}
* {{App|TIPP10|Intelligent touch typing tutor.|https://www.tipp10.com/|{{Pkg|tipp10}}}}
* {{App|TypingTest|Typing test desktop program with a large amount of customization.|https://github.com/laelath/typingtest|{{AUR|typingtest-git}}}}

== Accessibility ==

See [[Accessibility]] for tips on operating the desktop and [[:Category:Accessibility]] for all available articles. See also [[List of applications/Utilities#On-screen keyboards|On-screen keyboards]].

=== Speech synthesizers ===

See also [[Wikipedia:Comparison of speech synthesizers]] and [https://tools.wmflabs.org/tts-comparison/ listening comparison of the different engines].

* {{App|Ekho|Chinese text-to-speech (TTS) software for Cantonese, Mandarin, Zhaoan Hakka, Tibetan, Ngangien and Korean.|https://eguidedog.net/ekho.php|{{AUR|ekho}}}}
* {{App|eSpeak|Compact speech synthesizer for more than 50 languages.|https://espeak.sourceforge.net/|{{AUR|espeak}}}}
* {{App|[[Wikipedia:eSpeakNG|eSpeak NG]]|Fork of eSpeak (due to inactivity of original maintainer).|https://github.com/espeak-ng/espeak-ng|{{Pkg|espeak-ng}}}}
* {{App|[[Festival]]|General framework for building speech synthesis systems as well as including examples of various modules. As a whole it offers full text to speech.|https://www.cstr.ed.ac.uk/projects/festival/|{{Pkg|festival}}}}
* {{App|Flite|Lightweight speech synthesis engine.|http://festvox.org/flite/|{{Pkg|flite}}}}
* {{App|Gespeaker|GTK frontend for espeak. It allows you to play a text in many languages with settings for voice, pitch, volume and speed.|https://muflone.com/gespeaker/english/|{{AUR|gespeaker}}}}
* {{App|KMouth|Speech synthesizer frontend which enables persons that cannot speak to let their computer speak. Part of {{Grp|kde-accessibility}}.|https://apps.kde.org/kmouth/|{{Pkg|kmouth}}}}
* {{App|MaryTTS|Multilingual text-to-speech synthesis platform written in Java.|https://marytts.github.io/|{{AUR|marytts}}}}
* {{App|[[Mbrola|MBROLA]]|Proprietary phonemes-to-audio program which supports more than 70 languages. Mbrola-voices can also be used with eSpeak.|http://tcts.fpms.ac.be/synthesis/mbrola.html|{{AUR|mbrola}}}}
* {{App|Mimic|Text-to-speech voice synthesis from the Mycroft project (based on Flite).|https://mimic.mycroft.ai/|{{AUR|mimic}}}}
* {{App|Open JTalk|Japanese text-to-speech synthesis system.|https://sourceforge.net/projects/open-jtalk/|{{AUR|open-jtalk}}}}
* {{App|Orca|Screen reader for individuals who are blind or visually impaired, using eSpeak (via Speech Dispatcher). Part of {{Grp|gnome}}.|https://wiki.gnome.org/Projects/Orca|{{Pkg|orca}}}}
* {{App|piper|A fast, local neural text to speech system.|https://github.com/rhasspy/piper|{{AUR|piper-tts-bin}}}}
* {{App|[[RHVoice]]|Cross-platform (including Android) text-to-speech from a blind Russian-speaking developer, based on [https://hts.sp.nitech.ac.jp HTS] (ru, ka, uk, ky, tt, en, pt, eo)|https://github.com/RHVoice/RHVoice|{{Pkg|rhvoice}}}}
* {{App|[[Simple Orca Plugin System|SOPS]]|Provides a simple way to write custom plugins for screen reader Orca.|https://github.com/chrys87/simple-orca-plugin-system|{{AUR|simpleorcapluginsystem}}}}
* {{App|[[Speech dispatcher]]|Common interface to speech synthesis. It has backends for eSpeak, Festival, and a few other speech synthesizers.|https://freebsoft.org/speechd|{{Pkg|speech-dispatcher}}}}

=== Speech recognition ===

See also [[Wikipedia:Speech recognition software for Linux]].

* {{App|[[Wikipedia:Julius (software)|Julius]]|Large vocabulary continuous speech recognition engine.|https://github.com/julius-speech/julius|{{AUR|julius-speech}}}}
* {{App|[[Wikipedia:Kaldi (software)|Kaldi]]|Speech recognition toolkit.|https://github.com/kaldi-asr/kaldi|{{AUR|kaldi}}}}
* {{App|Kaylee|Somewhat fancy voice command recognition program that performs actions when a user speaks loosely preset sentences.|https://github.com/Ratfink/kaylee|{{AUR|kayleevc}}}}
* {{App|[[Wikipedia:Mycroft (software)|Mycroft]]|Hackable voice assistant.|https://github.com/MycroftAI/mycroft-core|{{AUR|mycroft-core}}}}
* {{App|nerd-dictation|Light weight manually activated dictation using the VOSK-API.|https://github.com/ideasman42/nerd-dictation|{{AUR|nerd-dictation-git}}}}
* {{App|Numen|Voice control for handsfree computing.|https://sr.ht/~geb/numen/|{{AUR|numen}}}}

=== Screen magnifiers ===

* {{App|boomer|Zoomer application for Linux.|https://github.com/tsoding/boomer|{{AUR|boomer-git}}}}
* {{App|KMag|Small KDE utility to magnify a part of the screen. Part of {{Grp|kde-accessibility}}.|https://apps.kde.org/kmag/|{{Pkg|kmag}}}}
* {{App|Magnus|Very simple desktop magnifier, showing the area around the mouse pointer in a separate window magnified two, three, four, or five times.|https://kryogenix.org/code/magnus/|{{AUR|magnus}}}}
* {{App|Virtual Magnifying Glass|Simple, customizable and easy-to-use screen magnification tool.|https://magnifier.sourceforge.net/|{{AUR|vmg}}}}
* {{App|xzoom|Zoom, rotate and mirror area of X display.|https://www.ibiblio.org/pub/Linux/X11/libs/!INDEX.short.html|{{AUR|xzoom}}}}

=== On-screen annotation ===

* {{App|Gromit-MPX|Tool to make annotations on the screen.|https://github.com/bk138/gromit-mpx|{{AUR|gromit-mpx}}}}
* {{App|Pylote|Tool to draw on the screen.|http://pascal.peter.free.fr/pylote-en.html|{{AUR|pylote-git}}}}
* {{App|Screenkey|Tool to display pressed keys.|https://www.thregr.org/~wavexx/software/screenkey/|{{Pkg|screenkey}}}}
* {{App|Show Me The Key|A screenkey alternative that works under Wayland via libinput|https://showmethekey.alynx.one|{{Pkg|showmethekey}}}}

=== Mouse ===

* {{App|Easystroke|Use mouse gestures to initiate commands and hotkeys.|https://github.com/thjaeger/easystroke/wiki|{{AUR|easystroke}}}}
* {{App|KMouseTool|Clicks the mouse whenever the mouse cursor pauses briefly. It was designed to help those with repetitive strain injuries, for whom pressing buttons hurts. Part of {{Grp|kde-accessibility}}.|https://apps.kde.org/kmousetool/|{{Pkg|kmousetool}}}}
* {{App|Mousetweaks|Accessibility enhancements for pointing devices.|https://wiki.gnome.org/Projects/Mousetweaks|{{Pkg|mousetweaks}}}}

== Display servers ==

* {{App|[[Xorg]]|The public, open-source implementation of the [[Wikipedia:X Window System|X Window System]] (commonly X11, or X).|https://www.x.org|{{Pkg|xorg}}}}
* {{App|Xlibre|A fork of Xorg that is [[Intel graphics#With the modesetting driver 2|tear free]] by default, supports client isolation and fixes several upstream bugs.|https://github.com/X11Libre |{{AUR|xlibre-xserver}}}}
* {{App|[[Wayland]]|A newer, alternative display server protocol with several [[Wayland#Compositors|compositors]] to choose from. Its advantages over Xorg are enhanced security features, more efficient handling of modern graphics tasks and active development while retaining compatibility through [[Xwayland]].|https://wayland.freedesktop.org/|{{Pkg|wayland}}}}

== Display managers ==

See the main article: [[Display manager#List of display managers]].

== Desktop environments ==

See the main article: [[Desktop environment#List of desktop environments]].

=== Window managers ===

==== Console ====

See also [[List of applications/Utilities#Terminal multiplexers]], which offer some of the functions of window managers for the console.

* {{App|twin|Text-mode window manager.|https://sourceforge.net/projects/twin/|{{AUR|twin}}}}
* {{App|Wmutils|A set of tools for X windows manipulation.|https://github.com/wmutils/core|{{AUR|wmutils-git}}}}

==== Graphical ====

See the main article: [[Window manager#List of window managers]].

==== Composite managers ====

See the main article: [[Xorg#List of composite managers]].

=== Wayland compositors ===

See the main article: [[Wayland#Compositors]].

=== Window tilers ===

* {{App|QuickTile|Lightweight standalone alternative to Compiz Grid plugin.|http://ssokolow.com/quicktile/|{{AUR|quicktile-git}}}}
* {{App|wumwum|The Window Manager manager. It can turn emwh compliant window managers into a tiling window manager while retaining all initial functionalities.|https://wumwum.sourceforge.net/|{{AUR|wumwum}}}}

=== Desktop shells ===

Desktop shells provide a graphical shell layer on top of a window manager or compositor, including panels, launchers, and other desktop components. They can be used to build a desktop-like experience, but do not constitute full desktop environments.

* {{App|AGS|Aylur's GTK Shell is a framework for building custom desktop shells using GTK.|https://aylur.github.io/ags/|{{AUR|aylurs-gtk-shell}}}}
* {{App|DankMaterialShell|Desktop shell for Wayland compositors, built with Quickshell and Go.|https://github.com/AvengeMedia/DankMaterialShell|{{Pkg|dms-shell}}}}
* {{App|eww|ElKowar's Wacky Widgets is a standalone widget system made in Rust that allows you to implement your own, custom widgets in any window manager.|https://github.com/elkowar/eww|{{AUR|eww}}}}
* {{App|liquidshell|Basic desktop shell for Xorg, an alternative to plasmashell, implemented using QtWidgets. It provides a bottom panel, a desktop wallpaper and desktop widgets.|https://apps.kde.org/liquidshell/|{{Pkg|liquidshell}}}}
* {{App|Noctalia|Minimal desktop shell for Wayland compositors, built on Quickshell.|https://noctalia.dev/|{{AUR|noctalia-shell}}}}
* {{App|[[nwg-shell]]|Modular GTK3-based shell for Sway and Hyprland compositors.|https://nwg-piotr.github.io/nwg-shell/|{{Pkg|nwg-shell}}}}
* {{App|wf-shell|Shell components for the Wayfire compositor.|https://github.com/WayfireWM/wf-shell|{{Pkg|wf-shell}}}}

=== Taskbars ===

See also [[Wikipedia:Taskbar]].

==== For both Wayland and Xorg ====
* {{App|[[Cairo-Dock]]|Highly customizable dock and launcher application.|https://www.glx-dock.org/|{{Pkg|cairo-dock}}}}
* {{App|LXQt Panel|Qt-based taskbar, part of the [[LXQt]] desktop.|https://github.com/lxqt/lxqt-panel|{{Pkg|lxqt-panel}}}}
* {{App|Xfce Panel|Panel included in the [[Xfce]] desktop.|https://docs.xfce.org/xfce/xfce4-panel/start|{{Pkg|xfce4-panel}}}}
* {{App|yambar|A modular and lightweight status bar for X11 and Wayland that goes to great lengths to be both CPU and battery efficient.|https://codeberg.org/dnkl/yambar|{{AUR|yambar}}}}

==== For Wayland only ====
* {{App|Dash to Panel|A fully customizable icon taskbar for {{Pkg|gnome-shell}}. Moves the dash into the GNOME main panel, similar to KDE Plasma and Windows 10.|https://github.com/home-sweet-gnome/dash-to-panel|{{Pkg|gnome-shell-extension-dash-to-panel}}}}
* {{App|Ironbar|A customisable and feature-rich GTK4 status bar for Wayland compositors, written in Rust.|https://github.com/JakeStanger/ironbar|{{Pkg|ironbar}}}}
* {{App|nwg-dock|GTK-based dock for Sway and Hyprland compositors.|https://github.com/nwg-piotr/nwg-dock|For Sway: {{Pkg|nwg-dock}}, for Hyprland: {{Pkg|nwg-dock-hyprland}}}}
* {{App|nwg-panel|GTK3-based panel for Sway and Hyprland compositors.|https://github.com/nwg-piotr/nwg-panel|{{Pkg|nwg-panel}}}}
* {{App|SFWBar|Flexible taskbar application for Wayland compositors, designed with a stacking layout in mind.|https://github.com/LBCrion/sfwbar|{{AUR|sfwbar}}}}
* {{App|Waybar|A customizable status bar for wlroots-based Wayland compositors.|https://github.com/Alexays/Waybar/|{{Pkg|waybar}}}}

==== For Xorg only ====
* {{App|[[Bmpanel]]|Lightweight, NETWM compliant panel.|https://github.com/nsf/bmpanel2|{{AUR|bmpanel2}}}}
* {{App|DockbarX|Standalone, dock-style taskbar for X11 with window grouping.|https://github.com/xuzhen/dockbarx|{{AUR|dockbarx}}}}
* {{App|[[fbpanel]]|Lightweight, NETWM compliant desktop panel.|https://aanatoly.github.io/fbpanel/|{{AUR|fbpanel}}}}
* {{App|[[Wikipedia:GNOME Panel|GNOME Panel]]|Panel included in the [[GNOME Flashback]] desktop.|https://wiki.gnome.org/Projects/GnomePanel|{{Pkg|gnome-panel}}}}
* {{App|[[Lemonbar]]|A featherweight status bar based on XCB. Provides UTF-8 support, background and foreground colors, text alignment, and not much more.|https://github.com/LemonBoy/bar|{{AUR|lemonbar}}}}
* {{App|LXPanel|Lightweight X11 desktop panel and part of the [[LXDE]] desktop.|https://github.com/lxde/lxpanel|{{Pkg|lxpanel}}}}
* {{App|MATE Panel|Panel included in the [[MATE]] desktop.|https://github.com/mate-desktop/mate-panel/|{{Pkg|mate-panel}}}}
* {{App|plainPanel|A lightweight panel written in Qt. It aims to be a desktop environment, but for now, it includes just a panel and a control center.|https://plainDE.github.io/|{{AUR|plainde-meta}}}}
* {{App|[[Plank]]|Elegant, simple, clean dock from [[Pantheon]] desktop environment.|https://launchpad.net/plank|{{Pkg|plank}}}}
* {{App|[[Polybar]]|A fast and easy-to-use tool for creating status bars.|https://github.com/jaagr/polybar|{{Pkg|polybar}}}}
* {{App|[[Tint2]]|Simple panel/taskbar developed specifically for Openbox.|https://gitlab.com/o9000/tint2|{{Pkg|tint2}}}}
* {{App|Vala Panel|GTK3 panel for compositing window managers.|https://gitlab.com/vala-panel-project/vala-panel|{{AUR|vala-panel}}}}
* {{App|[[xmobar]]|A lightweight, text-based, status bar written in Haskell.|https://archives.haskell.org/projects.haskell.org/xmobar/|{{Pkg|xmobar}}}}

=== System tray ===

[[Desktop environments]] typically have their own system tray implementation. E.g. [[KDE]] ships with Plasma Panel and [[Xfce]] ships with {{Pkg|xfce4-panel}}. For [[GNOME]], see [[GNOME#AppIndicators/Top bar icons]]. For [[dwm]], see [https://dwm.suckless.org/patches/systray/ systray patch].

* {{App|AllTray|Dock other applications into the system tray (notification area).|https://github.com/mbt/alltray|{{AUR|alltray}}}}
* {{App|Docker|Docking application which acts as a system tray.|https://icculus.org/openbox/2/docker/|{{AUR|docker-tray}}}}
* {{App|KDocker|Dock any application in the system tray (notification area).|https://github.com/user-none/KDocker|{{AUR|kdocker}}}}
* {{App|[[Stalonetray]]|Stand-alone freedesktop.org and KDE system tray (notification area) for [[Xorg]]. It has full XEMBED support and minimal dependencies: an X11 lib only. Stalonetray works with virtually any EWMH-compliant window manager.|https://stalonetray.sourceforge.net/|{{Pkg|stalonetray}}}}
* {{App|Trayer|Lightweight GTK-based system tray (notification area).|https://github.com/sargon/trayer-srg/|{{AUR|trayer}}}}

==== Tray indicators ====

Desktop-independent tray indicators. Useful for window managers without built-in tray widgets:

* {{Pkg|cbatticon}}: battery
* {{Pkg|volumeicon}}: volume
* {{Pkg|pasystray}}: pulseaudio
* {{AUR|sbxkb}}: keyboard layout
* {{Pkg|python-pystray}}: Python library for creating tray entries.
* {{AUR|tktray}}: Tk extension to create system tray icons following XDG specifications.

=== Application launchers ===

See also [[Wikipedia:Comparison of desktop application launchers]].

* {{App|Albert|Sophisticated, plugin based standalone keyboard launcher.|https://albertlauncher.github.io/|{{AUR|albert}}}}
* {{App|Application Finder|Easy-to-use application launcher from Xfce.|https://docs.xfce.org/xfce/xfce4-appfinder/start|{{Pkg|xfce4-appfinder}}}}
* {{App|Bashrun2|Provides a different, barebones approach to a run dialog, using a specialized Bash session within a small xterm window.|http://henning-bekel.de/bashrun2/|{{AUR|bashrun2}}}}
* {{App|bemenu|Lightweight dynamic menu inspired by dmenu. Works natively on Wayland.|https://github.com/Cloudef/bemenu|{{Pkg|bemenu}}}}
* {{App|Cartridges|Simple game launcher written in Python using GTK4 and Libadwaita.|https://apps.gnome.org/Cartridges/|{{Pkg|cartridges}}}}
* {{App|[[dmenu]]|Fast and lightweight dynamic menu for X which is also useful as an application launcher.|https://tools.suckless.org/dmenu/|{{Pkg|dmenu}}}}
* {{App|dmenu-extended|Extension to ''dmenu'' for quickly opening files and folders.|https://github.com/markjones112358/dmenu-extended|{{AUR|dmenu-extended-git}}}}
* {{App|dswitcher|''dmenu''-based window switcher that works regardless of workspace or minimization.|https://github.com/Antithesisx/dswitcher|{{AUR|dswitcher-git}}}}
* {{App|fuzzel|Application launcher for wlroots-based Wayland compositors, similar to rofi's `drun` mode.|https://codeberg.org/dnkl/fuzzel|{{Pkg|fuzzel}}}}
* {{App|[[Gmrun]]|Lightweight GTK-based application launcher, with the ability to run programs inside a terminal and other handy features.|https://sourceforge.net/projects/gmrun/|{{AUR|gmrun}}}}
* {{App|GNOME Games|GNOME application to browse your local video games library and to easily pick and play a game from it. Part of {{Grp|gnome-extra}}.|https://wiki.gnome.org/Apps/Games|{{Pkg|gnome-games}}}}
* {{App|Gnome-Pie|Circular application launcher (pie menu) for Linux. It is made of several pies, each consisting of multiple slices.|https://simmesimme.github.io/gnome-pie.html|{{Pkg|gnome-pie}}}}
* {{App|higgins|Desktop agnostic application launcher, file finder, calculator and more. Plugin based and freely and easily extendable via user-written plugins.|https://github.com/kokoko3k/higgins|{{AUR|higgins-git}}}}
* {{App|j4-dmenu-desktop|Very fast dmenu application launcher.|https://github.com/enkore/j4-dmenu-desktop|{{Pkg|j4-dmenu-desktop}}}}
* {{App|jgmenu|Simple, independent, contemporary-looking X11 menu, designed for scripting, ricing and tweaking.|https://github.com/johanmalm/jgmenu|{{Pkg|jgmenu}}}}
* {{App|Junction|Application chooser to open files and links.|https://apps.gnome.org/Junction/|{{Pkg|junction}}}}
* {{App|Kupfer|Convenient command and access tool for the GNOME desktop that can launch applications, open documents and access different types of objects and act on them.|https://kupferlauncher.github.io/|{{Pkg|kupfer}}}}
* {{App|launch|Simple command for launching applications from a terminal emulator.|https://github.com/silverhammermba/launch|{{AUR|launch-cmd}}}}
* {{App|[[Wikipedia:Launchy|Launchy]]|Very popular cross-platform application launcher with a plugin-based system used to provide extra functionality.|https://www.launchy.net/|{{Pkg|launchy}}}}
* {{App|Lighthouse|Simple scriptable popup dialog to run on X.|https://github.com/emgram769/lighthouse|{{AUR|lighthouse-git}}}}
* {{App|LXLauncher|Clone of the Asus launcher for EeePC.|https://github.com/lxde/lxlauncher|{{Pkg|lxlauncher}}}}
* {{App|nwg-drawer|GTK-based application drawer designed for Sway and Hyprland compositors.|https://github.com/nwg-piotr/nwg-drawer|{{Pkg|nwg-drawer}}}}
* {{App|nwg-menu|GTK-based application menu designed for Sway and Hyprland compositors.|https://github.com/nwg-piotr/nwg-menu|{{Pkg|nwg-menu}}}}
* {{App|rlaunch|An extremely fast and light-weight dmenu-like application launcher written in Rust.|https://github.com/PonasKovas/rlaunch|{{AUR|rlaunch}}}}
* {{App|[[rofi]]|Popup window switcher roughly based on superswitcher, requiring only xlib and pango.|https://github.com/davatorium/rofi/|{{Pkg|rofi}}}}
* {{App|Synapse|Semantic launcher written in Vala that you can use to start applications as well as find and access relevant documents and files by making use of the Zeitgeist engine.|https://launchpad.net/synapse-project|{{Pkg|synapse}}}}
* {{App|tofi|Tiny dynamic menu, fast and simple dmenu/rofi replacement for Wayland compositors such as {{Pkg|sway}}.|https://github.com/philj56/tofi|{{AUR|tofi}}}}
* {{App|Ulauncher|Modern and shiny launcher that provides fuzzy search, extensions, and themes.|https://ulauncher.io/|{{AUR|ulauncher}}}}
* {{App|vonal|Modern customizable global menu with unlimiting plugin system written in Rust.|https://github.com/fxdave/vonal-rust|{{AUR|vonal-bin}}}}
* {{App|wmenu|Dynamic menu for Sway and wlroots-based Wayland compositors. Provides a Wayland-native dmenu replacement which maintains the look and feel of dmenu.|https://codeberg.org/adnano/wmenu|{{Pkg|wmenu}}}}
* {{App|wofi|GTK-based popup window switcher for Wayland compositors such as {{Pkg|sway}}. Inspired by {{Pkg|rofi}}.|https://hg.sr.ht/~scoopta/wofi|{{Pkg|wofi}}}}
* {{App|yofi|Minimalistic menu for Wayland-based compositors.|https://github.com/l4l/yofi|{{AUR|yofi}}}}

=== Application menu editors ===

* {{App|[[Wikipedia:Alacarte|Alacarte]]|Add or remove applications from the main menu.|https://gitlab.gnome.org/GNOME/alacarte|{{Pkg|alacarte}}}}
* {{App|AppEditor|Edit application entries in the application menu.|https://github.com/donadigo/appeditor|{{AUR|appeditor-git}}}}
* {{App|Ezame|Desktop and menu file editor.|https://github.com/linux-man/ezame|{{AUR|ezame}}}}
* {{App|KMenuEdit|Edit one of the KDE application launchers. Part of {{Grp|plasma}}.|https://invent.kde.org/plasma/kmenuedit|{{Pkg|kmenuedit}}}}
* {{App|lxmed|Application menu editor written in Java.|https://sourceforge.net/projects/lxmed/|{{AUR|lxmed}}}}
* {{App|MenuLibre|Advanced menu editor that provides modern features in a clean, easy-to-use interface.|https://launchpad.net/menulibre|{{AUR|menulibre}}}}
* {{App|Meow|Application menu editor written in Java.|https://pnmougel.github.io/meow/|{{AUR|meow-bin}}}}
* {{App|Mozo|Change which applications are shown on the main menu.|https://github.com/mate-desktop/mozo|{{Pkg|mozo}}}}

=== Application menu generators ===

* {{App|MenuGenerator|Simple application menu generator following XDG menu spec for Fluxbox, Openbox and JWM.|https://github.com/BlackCodec/MenuGenerator/|{{AUR|menugenerator}}}}
* {{App|MenuMaker|Heuristics-driven menu generator for Blackbox, Fluxbox, IceWM, Openbox, PekWM and WindowMaker.|https://menumaker.sourceforge.net/|{{Pkg|menumaker}}}}
* {{App|[[xdg-menu]]|Generate XDG application menus for various window managers.|https://github.com/p5n/archlinux-stuff/tree/master/xdg-menu|{{Pkg|archlinux-xdg-menu}}}}
* {{App|xdgmenumaker|Command line tool that generates XDG menus for several window managers.|https://github.com/gapan/xdgmenumaker|{{AUR|xdgmenumaker}}}}

=== Wallpaper setters ===

See also [[Wikipedia:Wallpaper (computing)]].

* {{App|awww|Efficient animated wallpaper daemon for Wayland, controlled at runtime.|https://codeberg.org/LGFae/awww|{{Pkg|awww}}}}
* {{App|bgs|An extremely fast and small background setter for X based on imlib2.|https://github.com/Gottox/bgs/|{{AUR|bgs-git}}}}
* {{App|[[feh]]|A lightweight and powerful image viewer that can also be used to manage the desktop wallpaper.|https://feh.finalrewind.org/|{{Pkg|feh}}‎}}
* {{App|Fondo|Find a variety of the most beautiful wallpapers from Unsplash.com.|https://github.com/calo001/fondo|{{AUR|fondo}}}}
* {{App|Hanabi|Live Wallpaper for GNOME.|https://github.com/jeffshee/gnome-ext-hanabi|{{AUR|gnome-shell-extension-hanabi-git}}}}
* {{App|Hidamari|Video wallpaper for Linux. Written in Python.|https://github.com/jeffshee/hidamari|{{AUR|hidamari}}}}
* {{App|hsetroot|A tool to create compose wallpapers.|https://packages.debian.org/sid/hsetroot|{{Pkg|hsetroot}}}}
* {{App|HydraPaper|GTK utility to set two different backgrounds for each monitor on GNOME.|https://gabmus.gitlab.io/HydraPaper/|{{AUR|hydrapaper-git}}}}
* {{App|Hyprpaper|Hyprpaper is a blazing fast Wayland wallpaper utility with IPC controls.|https://github.com/hyprwm/hyprpaper|{{AUR|hyprpaper-git}}}}
* {{App|LiveWallpaper|Animated 3D wallpapers.|https://launchpad.net/livewallpaper|{{AUR|livewallpaper}}}}
* {{App|mpvpaper|A video wallpaper program for wlroots-based Wayland compositors.|https://github.com/GhostNaN/mpvpaper|{{AUR|mpvpaper}}}}
* {{App|[[Nitrogen]]|A fast and lightweight desktop background browser and setter for X windows.|https://github.com/l3ib/nitrogen|{{AUR|nitrogen}}}}
* {{App|oguri|An animated wallpaper daemon for Wayland compositors.|https://github.com/vilhalmer/oguri|{{AUR|oguri-git}}}}
* {{App|pacwall|A live wallpaper that shows the dependency graph and status of installed packages.|https://github.com/Kharacternyk/pacwall|{{AUR|pacwall-git}}}}
* {{App|pywal|Changes the wallpaper and creates matching color schemes for various applications (rofi, i3, terminals)|https://github.com/dylanaraps/pywal|{{Pkg|python-pywal}}}}
* {{App|swaybg|Wallpaper tool for Wayland compositors.|https://github.com/swaywm/swaybg|{{Pkg|swaybg}}}}
* {{App|Variety|Changes the wallpaper on a regular interval using user-specified or automatically downloaded images.|https://peterlevi.com/variety/|{{Pkg|variety}}}}
* {{App|[[Xlivebg]]|A live wallpaper framework and collection of live wallpapers for the X window system.|http://nuclear.mutantstargoat.com/sw/xlivebg/|{{AUR|xlivebg}}}}
* {{App|xwallpaper|Minimalist wallpaper setting utility for X.|https://github.com/stoeckmann/xwallpaper|{{Pkg|xwallpaper}}}}

{{Tip|In order to avoid installing one more package, you may find convenient to use the {{ic|display}} utility from {{Pkg|imagemagick}} or {{ic|gm display}} from {{Pkg|graphicsmagick}}. E.g.: {{ic|display -backdrop -background '#3f3f3f' -flatten -window root ''image''}}.}}

=== Virtual desktop pagers ===

See also [[Wikipedia:Pager (GUI)]].

* {{App|bbpager|Dockable pager for [[blackbox]] and other window managers.|https://sourceforge.net/projects/bbtools/|4={{Pkg|bbpager}}}}
* {{App|fbpager|Virtual desktop pager for fluxbox.|http://www.fluxbox.org/fbpager{{Dead link|2025|01|22|status=404}}|{{AUR|fbpager-git}}}}
* {{App|IPager|A configurable pager with transparency, originally developed for Fluxbox.|http://useperl.ru/ipager/index.en.html{{Dead link|2025|03|15|status=404}}|{{AUR|ipager}}}}
* {{App|Netwmpager|A NetWM/EWMH compatible pager.|https://sourceforge.net/projects/sf-xpaint/files/netwmpager/|{{AUR|netwmpager}}}}

=== Desktop widgets ===

* {{App|CoreAction|Side bar with some handy gadgets like system loads, calendar, calculator, notes etc. Part of C-Suite.|https://gitlab.com/cubocore|{{AUR|coreaction}}}}
* {{App|[[Wikipedia:gDesklets|gDesklets]]|System for bringing mini programs (desklets) onto your desktop.|https://launchpad.net/gdesklets|{{AUR|gdesklets}}}}
* {{App|KRuler|Displays on screen a ruler measuring pixels. Part of {{Grp|kde-graphics}}.|https://apps.kde.org/kruler/|{{Pkg|kruler}}}}

=== Desktop notifications ===

See: [[Desktop notifications#Notification servers|Notification servers]].

=== Clipboard managers ===

See [[Clipboard#Managers]].

=== Logout UI ===

* {{App|clearine|Beautiful Logout UI for X11 window manager|https://github.com/okitavera/clearine{{Dead link|2025|11|17|status=404}}|{{AUR|clearine-git}}}}
* {{App|nwg-bar|Configurable button bar for wlroots-based Wayland compositors.|https://github.com/nwg-piotr/nwg-bar|{{Pkg|nwg-bar}}}}
* {{App|[[oblogout]]|Openbox logout script|https://launchpad.net/oblogout|{{AUR|oblogout-py3-git}}}}
* {{App|wlogout|Logout menu for wayland|https://github.com/ArtsyMacaw/wlogout|{{AUR|wlogout}}}}

== Artificial intelligence ==

See also [[Wikipedia:Open-source artificial intelligence]], [[Wikipedia:Lists of open-source artificial intelligence software]], [[Wikipedia:Comparison of deep learning software]]

=== Machine learning frameworks ===

* {{App|cuDNN|NVIDIA CUDA Deep Neural Network library for high-performance GPU acceleration.|https://developer.nvidia.com/cudnn|{{Pkg|cudnn}}}}
* {{App|[[Wikipedia:Fast Artificial Neural Network|Fast Artificial Neural Network]]|Library for developing feedforward Artificial Neural Networks.|https://leenissen.dk/fann/wp/|{{AUR|fann}}}}
* {{App|ggml|Lightweight tensor library for on-device LLM inference.|https://github.com/ggml-org/ggml|{{AUR|libggml}}}}
* {{App|[[Wikipedia:Orange (software)|Orange]]|Visual programming toolkit for data mining, ML and interactive visualization.|https://orange.biolab.si/|{{AUR|python-orange}}}}
* {{App|[[Wikipedia:Prolog|Prolog]]|Logic-programming language for symbolic AI and computational linguistics.|https://www.swi-prolog.org/|{{Pkg|swi-prolog}}, {{AUR|gprolog}}, {{AUR|scryer-prolog}}}}
* {{App|[[Wikipedia:PyTorch|PyTorch]]|Dynamic neural-network framework with strong GPU acceleration.|https://pytorch.org/|{{Pkg|python-pytorch}}, {{Pkg|python-pytorch-cuda}}, {{Pkg|python-pytorch-opt}}, {{Pkg|python-pytorch-opt-cuda}}, {{Pkg|python-pytorch-rocm}}, {{Pkg|python-pytorch-opt-rocm}}}}
* {{App|libtorch|C++ frontend for PyTorch.|https://pytorch.org|{{AUR|libtorch-cuda}}, {{AUR|libtorch-cpu}}, {{AUR|libtorch-rocm}}}}
* {{App|mlpack|Fast, scalable C++ ML library with Python / R / Julia / Go bindings.|https://mlpack.org|{{AUR|mlpack}}}}
* {{App|SentencePiece|Unsupervised text tokenizer for neural text generation.|https://github.com/google/sentencepiece|{{AUR|sentencepiece}} / {{AUR|sentencepiece-bin}} (C++), {{AUR|python-sentencepiece}} / {{AUR|python-sentencepiece-bin}} (Python)}}
* {{App|Sentence Transformers|Python framework for state-of-the-art sentence / text / image embeddings.|https://github.com/UKPLab/sentence-transformers|{{AUR|python-sentence-transformers}}}}
* {{App|[[Wikipedia:TensorFlow|TensorFlow]]|End-to-end platform for scalable machine learning.|https://www.tensorflow.org/|{{Pkg|python-tensorflow}}, {{Pkg|python-tensorflow-cuda}}, {{Pkg|python-tensorflow-opt}}, {{Pkg|python-tensorflow-opt-cuda}}}}
* {{App|[[Wikipedia:Theano (software)|Theano]]|Python library for efficient multi-dimensional array math and deep learning.|http://deeplearning.net/software/theano/|{{AUR|python-theano-pymc}}}}
* {{App|[[Wikipedia:Torch (machine learning)|Torch]]|Scientific computing & ML framework for LuaJIT.|http://torch.ch/|{{AUR|torch7-git}}}}

=== Local AI model deployment ===

==== Inference engines ====

* {{App|CTranslate2|A C++ and Python library for efficient inference with Transformer models.|https://github.com/OpenNMT/CTranslate2|{{AUR|ctranslate2}}, {{AUR|python-ctranslate2}}}}
* {{App|describeimage|Describe images using Ollama.|https://github.com/ollama/ollama|{{Pkg|describeimage}}}}
* {{App|[[llama.cpp]]|A high-performance C/C++ port of Facebook's LLaMA model, optimized for local execution.|https://github.com/ggerganov/llama.cpp|{{AUR|llama.cpp}}, {{AUR|llama.cpp-cuda}}, {{AUR|llama.cpp-vulkan}}}}
* {{App|ik-llama.cpp|A fork of llama.cpp with additional state-of-the-art quantized models and improved performance.|https://github.com/ikawrakow/ik_llama.cpp |{{AUR|ik-llama.cpp}}, {{AUR|ik-llama.cpp-cuda}}, {{AUR|ik-llama.cpp-vulkan}}}}
* {{App|ONNX Runtime|High-performance scoring engine for ML models with cross-platform support.|https://onnxruntime.ai/ |{{Pkg|onnxruntime-cpu}}, {{Pkg|onnxruntime-cuda}}, {{Pkg|onnxruntime-opt-cuda}}, {{Pkg|onnxruntime-rocm}}, {{Pkg|onnxruntime-opt-rocm}}}}
* {{App|[[Ollama]]|A streamlined tool for creating, running, and sharing large language models locally.|https://ollama.com|{{Pkg|ollama}}, {{Pkg|ollama-cuda}}, {{Pkg|ollama-rocm}}}}
* {{App|ollama-amd-igpu|A specialized version of Ollama optimized for AMD iGPUs, supporting Llama 3.3, DeepSeek-R1, Phi-4 and other models.|https://github.com/Crandel/ollama-amd-igpu|{{AUR|ollama-amd-igpu}}, {{AUR|ollama-amd-igpu-cuda}}, {{AUR|ollama-amd-igpu-rocm}}}}

==== Translation====

* {{App|Argos Translate|Open-source offline translation library with GUI support.|https://www.argosopentech.com/|{{AUR|argos-translate}}, {{AUR|argos-translate-gui}}}}
* {{App|TranslateLocally|Fast and secure local translation using Bergamot (Mozilla).|https://github.com/XapaJIaMnu/translatelocally|{{AUR|translatelocally-git}}}}

=== AI applications ===

==== Desktop clients ====

* {{App|AIOne|An all-in-one AI desktop application that provides access to ChatGPT, Gemini, and Claude (uses system-wide Electron).|https://sumexxx.github.io/AIOne/|{{AUR|aione}}}}
* {{App|Alpaca AI|A flexible client for Ollama, enabling local AI model usage and integration with third-party services like ChatGPT and Gemini.|https://github.com/Jeffser/alpaca|{{AUR|alpaca-ai}}}}
* {{App|AnythingLLM|An all-in-one AI application suite supporting Retrieval-Augmented Generation (RAG) and multi-agent workflows for Docker and desktop environments.|https://anythingllm.com/|{{AUR|anythingllm-desktop-bin}}}}
* {{App|BrowserOS|An open-source agentic browser that runs AI agents locally.|https://github.com/browseros-ai/BrowserOS|{{AUR|browseros-bin}}}}
* {{App|Cherry Studio|Desktop client for multiple LLM providers (OpenAI, Claude, LocalAI, etc.).|https://cherry.studio|{{AUR|cherry-studio}}}}
* {{App|Chatbox|A cross-platform desktop application for interacting with GPT-4 and GPT-3.5 models via the OpenAI API.|https://chatboxai.app|{{AUR|chatbox-bin}}}}
* {{App|ChatWise|Fast AI chatbot desktop application.|https://chatwise.app/|{{AUR|chatwise}}}}
* {{App|clara-verse|Privacy-first, client-side AI assistant WebUI for LLMs with ComfyUI integration.|https://github.com/badboysm890/ClaraVerse|{{AUR|clara-verse}}}}
* {{App|GPT4All|A lightweight solution for running large language models locally on any device.|https://gpt4all.io/|{{AUR|gpt4all-chat}}}}
* {{App|Jan|An easy-to-use platform for deploying and managing AI models directly on your PC.|https://jan.ai/|{{AUR|jan}}}}
* {{App|KAIChat|Chat interface for AI models such as Ollama.|https://apps.kde.org/kaichat/|{{AUR|kaichat}}}}
* {{App|Lobe Chat|A modern, extensible chat framework for LLMs, supporting multiple AI providers, multi-modal interactions, and plugins.|https://github.com/lobehub/lobe-chat|{{AUR|lobe-chat}}}}
* {{App|LocalAI|Free, Open Source OpenAI alternative with CPU optimizations.|https://github.com/mudler/LocalAI|{{AUR|local-ai}}}}
* {{App|RisuAI|User-friendly software for LLM roleplaying with local AI models.|https://risuai.xyz|{{AUR|risuai-bin}}}}
* {{App|NextChat|A cross-platform ChatGPT client.|https://github.com/ChatGPTNextWeb/ChatGPT-Next-Web|{{AUR|nextchat-bin}}}}
* {{App|noi-desktop|AI-powered desktop assistant for exploration and task automation.|https://noi.ai|{{AUR|noi-desktop-bin}}}}
* {{App|Open-GPT|A ChatGPT client using the OpenAI API.|https://github.com/BeanDx/open-gpt/tree/main|{{AUR|open-gpt-bin}}}}
* {{App|SillyTavern|A feature-rich local interface for interacting with large language models (LLMs), generating images, and synthesizing speech.|https://sillytavern.app/|{{AUR|sillytavern-git}}}}
* {{App|[[Wikipedia:Mycroft (software)|Mycroft]]|Intelligent personal assistant and knowledge navigator with speech recognition.|https://mycroft.ai/|{{AUR|mycroft-core}}}}

==== Terminal clients ====

* {{App|AICommits|CLI that writes your git commit messages with AI.|https://github.com/Nutlope/aicommits|{{AUR|aicommits}}}}
* {{App|AIChat|A versatile CLI tool for interacting with AI models, featuring REPL-like functionality, shell assistance, and support for multiple AI providers.|https://github.com/sigoden/aichat|{{Pkg|aichat}}}}
* {{App|AIChat NG|An enhanced fork of AIChat with advanced features for terminal-based AI interactions.|https://github.com/blob42/aichat-ng|{{AUR|aichat-ng}}}}
* {{App|Gemini CLI|Open-source AI agent that brings the power of Google Gemini directly into your terminal.|https://github.com/google-gemini/gemini-cli|{{Pkg|gemini-cli}}}}
* {{App|GitHub Copilot CLI|Official CLI interface for GitHub Copilot coding assistant.|https://github.com/github/copilot-cli|{{AUR|github-copilot-cli}}}}
* {{App|OpenCommit|Auto-generate meaningful git commit messages with AI.|https://github.com/di-sukharev/opencommit|{{AUR|opencommit}}}}
* {{App|TLM|Local CLI Copilot powered by Ollama.|https://github.com/yusufcanb/tlm|{{AUR|tlm}}}}
* {{App|ShellGPT|A productivity-focused CLI tool powered by OpenAI's ChatGPT, designed for efficient command-line workflows.|https://github.com/TheR1D/shell_gpt|{{AUR|shellgpt-git}}}}

=== Development tools ===

* {{App|hfdownloader|Utility to download HuggingFace Models and Datasets.|https://github.com/bodaay/HuggingFaceModelDownloader|{{AUR|hfdownloader-git}}}}
* {{App|Rivet|IDE for creating complex AI agents and prompt chaining.|https://rivet.ironcladapp.com|{{AUR|ironclad-rivet-bin}}}}
* {{App|Kiro|Amazon's closed-source, AI-powered IDE for rapid prototyping to production.|https://kiro.dev/|{{AUR|kiro-ide}}}}
* {{App|koboldcpp|A simple one-file way to run various GGML and GGUF models with a KoboldAI UI.|https://github.com/LostRuins/koboldcpp|{{AUR|koboldcpp}}, {{AUR|koboldcpp-cuda}}, {{AUR|koboldcpp-hipblas}}}}
* {{App|llamafile|Distribute and run LLMs with a single file.|https://github.com/Mozilla-Ocho/llamafile|{{AUR|llamafile}}}}
* {{App|LM Studio|A user-friendly interface for discovering, downloading, and running local LLMs.|https://lmstudio.ai/|{{AUR|lmstudio-bin}}}}
* {{App|Msty|A simple and intuitive interface for accessing both local and online AI models.|https://msty.app|{{AUR|msty-bin}}}}
* {{App|netron|Visualizer for neural network, deep learning and machine learning models.|https://netron.app/|{{AUR|netron}}}}
* {{App|open-webui|Extensible self-hosted AI platform with WebUI and OpenAI API support for LLM runners.|https://github.com/open-webui/open-webui|{{AUR|open-webui-git}}}}

=== Coding assistants ===

* {{App|Crush|A powerful terminal-based AI assistant for developers, providing intelligent coding assistance directly in your terminal.|https://charm.sh/crush|{{AUR|crush}}, {{AUR|crush-bin}}}}
* {{App|Codename Goose|An extensible AI agent that goes beyond code suggestions - can install, execute, edit, and test with any LLM.|https://github.com/block/goose|{{AUR|codename-goose-bin}}}}
* {{App|Claude Code|An agentic coding tool that lives in your terminal.|https://github.com/anthropics/claude-code|{{AUR|claude-code}}}}
* {{App|codai|AI code assistant with session-based CLI for intelligent suggestions and refactoring.|https://github.com/meysamhadeli/codai|{{AUR|codai}}}}
* {{App|CodeGPT|A CLI written in Go language that writes git commit messages or does a code review brief for you using ChatGPT AI (gpt-4, gpt-3.5-turbo model) and automatically installs a git prepare-commit-msg hook.|https://github.com/appleboy/CodeGPT|{{AUR|codegpt-bin}}}}
* {{App|Cursor|Write, edit, and chat about your code with GPT.|https://cursor.so|{{AUR|cursor-bin}}}}
* {{App|opencode|AI coding agent built for the terminal.|https://github.com/sst/opencode|{{Pkg|opencode}}}}
* {{App|Kiro|An AI-powered IDE for rapid prototyping to production.|https://kiro.dev/ |{{AUR|kiro-ide}}}}
* {{App|qwen-code|CLI coding agent (fork of gemini-cli) with AI-powered code generation and assistance.|https://github.com/QwenLM/Qwen-Code|{{Pkg|qwen-code}}}}

=== Multimedia processing ===

==== Image generation ====

* {{App|RapidOCR|A cross platform OCR Library based on OnnxRuntime.|https://github.com/RapidAI/RapidOCR|{{AUR|python-rapidocr-onnxruntime}}}}
* {{App|Krita AI Diffusion|An intuitive AI-powered plugin for Krita, enabling seamless image inpainting and outpainting with optional text prompts.|https://github.com/Acly/krita-ai-diffusion|{{AUR|krita-ai-diffusion}}}}
* {{App|StabilityMatrix|A versatile package manager for Stable Diffusion, simplifying model management and integration.|https://github.com/LykosAI/StabilityMatrix|{{AUR|stabilitymatrix}}}}
* {{App|Stable Diffusion C++|Pure C/C++ implementation of Stable Diffusion for efficient inference on local machines.|https://github.com/leejet/stable-diffusion.cpp|{{AUR|stable-diffusion.cpp-git}}}}
* {{App|Stable Diffusion Web UI|Powerful web-based interface for Stable Diffusion, enabling high-quality image generation with customizable parameters.|https://github.com/AUTOMATIC1111/stable-diffusion-webui|{{AUR|stable-diffusion-webui-git}}}}
* {{App|Upscayl|A free and open-source AI-based image upscaler, enhancing image resolution while preserving quality.|https://github.com/upscayl/upscayl|{{AUR|upscayl-bin}}}}

==== Speech processing ====

* {{App|Coqui TTS|Deep learning toolkit for Text-to-Speech with support for 20+ languages.|https://github.com/coqui-ai/TTS|{{AUR|coqui-tts}}}}
* {{App|faster-whisper|Faster Whisper transcription implementation using CTranslate2.|https://github.com/guillaumekln/faster-whisper|{{AUR|python-faster-whisper}}}}
* {{App|Handy|A free, open source, and extensible speech-to-text application that works completely offline.|https://github.com/cjpais/Handy|{{AUR|handy}}}}
* {{App|MaryTTS|Multilingual TTS synthesis platform written in Java.|https://marytts.github.io/|{{AUR|marytts}}}}
* {{App|Piper|A fast, local neural text-to-speech system.|https://github.com/rhasspy/piper|{{AUR|piper-tts}}}}
* {{App|Sherpa-ONNX|Speech-to-text, text-to-speech, speaker diarization, and VAD using next-gen Kaldi with onnxruntime.|https://github.com/k2-fsa/sherpa-onnx|{{AUR|sherpa-onnx}}}}
* {{App|shisper|Script to generate subtitles and transcriptions using whisper.cpp.|https://github.com/M0Rf30/shisper|{{AUR|shisper-git}}}}
* {{App|vibe|Transcribe audio/video offline using OpenAI Whisper with GUI interface.|https://thewh1teagle.github.io/vibe/|{{AUR|vibe-bin}}}}
* {{App|VOICEVOX|Japanese TTS engine with anime-style character voices.|https://voicevox.hiroshiba.jp/|{{AUR|voicevox-appimage}}}}
* {{App|whisper.cpp|A C/C++ port of OpenAI's Whisper model for efficient speech recognition.|https://github.com/ggerganov/whisper.cpp|{{AUR|whisper.cpp}}, {{AUR|whisper.cpp-cuda}}, {{AUR|whisper.cpp-openvino}}}}
* {{App|whisper.cpp-models|Pre-trained models for whisper.cpp in various sizes.|https://github.com/ggerganov/whisper.cpp|{{AUR|whisper.cpp-model-large-v3}}, {{AUR|whisper.cpp-model-medium}}, {{AUR|whisper.cpp-model-small}}, {{AUR|whisper.cpp-model-tiny}}}}
* {{App|whispering|Open-source transcription application with global speech-to-text functionality.|https://whispering.bradenwong.com/|{{AUR|whispering-bin}}}}
* {{App|wiggly-stt|Local speech-to-text with whisper.cpp and clipboard integration.|https://github.com/hansp27/wiggly-stt|{{AUR|wiggly-stt}}}}

Xlibre

2026-04-26T21:21:16Z

Alad: Protected "Xlibre": Excessive vandalism ([Edit=Allow only sysops] (indefinite) [Move=Allow only sysops] (indefinite))

#REDIRECT [[General_recommendations#Display_server]]

Security

2026-04-26T18:32:02Z

Alad: /* Sandboxing applications */ remove redundant statement for linux-hardened

[[Category:Security]]
[[Category:File systems]]
[[Category:Networking]]
[[de:Sicherheit]]
[[es:Security]]
[[hu:Security]]
[[ja:セキュリティ]]
[[pt:Security]]
[[ru:Security]]
[[zh-hans:Security]]
{{Related articles start}}
{{Related|Arch Security Team}}
{{Related|General recommendations}}
{{Related|Identity management}}
{{Related|Capabilities}}
{{Related|List of Applications/Security}}
{{Related|Arch package guidelines/Security}}
{{Related articles end}}
This article contains recommendations and best practices for [[Wikipedia:Hardening (computing)|hardening]] an Arch Linux system.

== Concepts ==

* It ''is'' possible to tighten security to the point where the system is unusable. Security and convenience must be balanced. The trick is to create a secure ''and'' useful system.
* The biggest threat is, and will always be, the user.
* The [[Wikipedia:Principle of least privilege|principle of least privilege]]: Each part of a system should only be able to access what is strictly required, and nothing more.
* Defense in depth: Security works better in independent layers. When one layer is breached, another should stop the attack.
* Be a little paranoid. And be suspicious. If anything sounds too good to be true, it probably is!
* You can never make a system 100% secure unless you unplug the machine from all networks, turn it off, lock it in a safe, smother it in concrete and never use it.
* Prepare for failure. Create a plan ahead of time to follow when your security is broken.

== Passwords ==

Passwords are key to a secure system. They secure your [[Users and groups|user accounts]], [[Data-at-rest encryption|encrypted filesystems]], and [[SSH keys|SSH]]/[[GPG]] keys. They are the main way a computer chooses to trust the person using it, so a big part of security is just about picking secure passwords and protecting them.

=== Choosing secure passwords ===

Passwords must be complex enough to not be easily guessed from e.g. personal information, or [[Wikipedia:Password cracking|cracked]] using methods like brute-force attacks. The tenets of strong passwords are based on ''length'' and ''randomness''. In cryptography the quality of a password is often referred to as its [[Wikipedia:Password strength#Entropy as a measure of password strength|entropy]].

Insecure passwords include those containing or those using as a base before substitution/variation:

* Personally identifiable information (e.g., your dog's name, date of birth, area code, favorite video game)
* Simple character substitutions on words (e.g., {{ic|k1araj0hns0n}}), as modern dictionary attacks can easily work with these
* Root "words" or common strings followed or preceded by added numbers, symbols, or characters (e.g., {{ic|DG091101%}})
* Common phrases or short strings of common dictionary words (e.g. {{ic|photocopyhauntbranchexpose}}) including with character substitution (e.g. {{ic|Ph0toc0pyh4uN7br@nch3xp*se}}) (See Diceware below for when a combination of dictionary words can be secure)
* Any of the [[Wikipedia:List of the most common passwords|most common passwords]]

The best choice for a password is something long (the longer, the better) and generated from a random source. It is important to use a long password. [https://www.theregister.com/2019/02/14/password_length Weak hash algorithms allow an 8-character password hash to be compromised in just a few hours.]

Tools like {{Pkg|pwgen}} or {{AUR|apg}} can generate random passwords. However, these passwords can be difficult to memorize. One memorization technique (for ones often typed) is to generate a long password and memorize a minimally secure number of characters, temporarily writing down the full generated string. Over time, increase the number of characters typed - until the password is ingrained in muscle memory and need not be remembered. This technique is more difficult, but can provide confidence that a password will not turn up in wordlists or "intelligent" brute force attacks that combine words and substitute characters.

Apart from password management, {{Pkg|keepassxc}} offers password/passphrase generation. It is possible to customize the generation in a GUI. Dictionary based passphrases are also supported.

One technique for memorizing a password is to use a mnemonic phrase, where each word in the phrase reminds you of the next character in the password.
Take for instance “the girl is walking down the rainy street” could be translated to {{ic|t6!WdtR5}} or, less simply, {{ic|t&6!RrlW@dtR,57}}.
This approach could make it easier to remember a password, but note that the various letters have very different probabilities of being found at the start of words ([[Wikipedia:Letter frequency#Relative frequencies of the first letters of a word in the English language|Wikipedia:Letter frequency]]).

Another effective technique can be to write randomly generated passwords down and store them in a ''safe'' place, such as in a wallet, purse, or document safe. Most people do a generally good job of protecting their physical valuables from attack, and it is easier for most people to understand physical security best practices compared to digital security practices.

It is also very effective to combine the mnemonic and random technique by saving long randomly generated passwords with a [[password manager]], which will be in turn accessed with a memorable "master password"/primary password that must be used only for that purpose. The master password must be memorized and never saved. This requires the password manager to be installed on a system to easily access the password (which could be seen as an inconvenience or a security feature, depending on the situation). Some password managers also have smartphone apps which can be used to display passwords for manual entry on systems without that password manager installed (if that is a common use case, you could still use easily typeable but secure passwords for each service instead of completely random ones, see below). Note that a password manager introduces a single point of failure if you ever forget the master password.
Some password managers compute the contained passwords based on the master password and the service name where you want to log in instead of encrypting them, making it possible to use it on a new system without syncing any data.

It can be effective to use a memorable long series of unrelated words as a password. The theory is that if a sufficiently long phrase is used, the gained entropy from the password's length can counter the lost entropy from the use of dictionary words. This [https://xkcd.com/936/ xkcd comic] demonstrates the entropy tradeoff of this method, taking into account the limited set of possible words for each word in the passphrase. If the set of words you choose from is large (multiple thousand words) and you choose 5-7 or even more random words from it, this method provides great entropy, even assuming the attacker knows the set of possible words chosen from and the number of words chosen. The number of possible passphrases after settling on a set of words and number of words is: (number of words in the set of words to select from) to the power of (the number of words chosen for the passphrase). See e.g. [https://www.rempe.us/diceware/ Diceware] for more.

See [https://www.iusmentis.com/security/passphrasefaq/ The passphrase FAQ] or [[Wikipedia:Password strength]] for some additional background.

=== Maintaining passwords ===

Once you pick a strong password, be sure to keep it safe. Watch out for [[Wikipedia:Keylogger|keyloggers]] (software and hardware), screen loggers, [[Wikipedia:Social engineering (security)|social engineering]], [[Wikipedia:Shoulder surfing (computer security)|shoulder surfing]], and avoid reusing passwords so insecure servers cannot leak more information than necessary. [[List of applications/Security#Password managers|Password managers]] can help manage large numbers of complex passwords: if you are copy-pasting the stored passwords from the manager to the applications that need them, make sure to clear the copy buffer every time, and ensure they are not saved in any kind of log (e.g. do not paste them in plain terminal commands, which would store them in files like {{ic|.bash_history}}). Note that password managers that are implemented as browser extensions may be vulnerable to [https://www.spookjs.com side channel attacks]. These can be mitigated by using password managers that run as separate applications.

As a rule, do not pick insecure passwords just because secure ones are harder to remember. Passwords are a balancing act. It is better to have an encrypted database of secure passwords, guarded behind a key and one strong master password, than it is to have many similar weak passwords. Writing passwords down is perhaps equally effective [https://www.schneier.com/blog/archives/2005/06/write_down_your.html], avoiding potential vulnerabilities in software solutions while requiring physical security.

Another aspect of the strength of the passphrase is that it must not be easily recoverable from other places.

If you use the same passphrase for disk encryption as you use for your login password (useful e.g. to auto-mount the encrypted partition or folder on login), make sure that {{ic|/etc/shadow}} ends up on an encrypted partition or/and uses a strong key derivation function (i.e. yescrypt/argon2 or sha512 with PBKDF2, but not md5 or low iterations in PBKDF2) for the stored password hash (see [[SHA password hashes]] for more information).

{{Tip|In 2023 Arch Linux switched the [https://archlinux.org/news/changes-to-default-password-hashing-algorithm-and-umask-settings/ default hashing] algorithm to yescrypt. If you have not customized the default, executing a password change with {{ic|passwd}} is necessary (and sufficient) to apply the new default.}}

If you are backing up your password database, make sure that each copy is not stored behind any other passphrase which in turn is stored in it, e.g. an encrypted drive or an authenticated remote storage service, or you will not be able to access it in case of need; a useful trick is to protect the drives or accounts where the database is backed up using a simple cryptographic hash of the master password. Maintain a list of all the backup locations: if one day you fear that the master passphrase has been compromised you will have to change it immediately on all the database backups and the locations protected with keys derived from the master password.

Version-controlling the database in a secure way can be very complicated: if you choose to do it, you must have a way to update the master password of all the database versions. It may not always be immediately clear when the master password is leaked: to reduce the risk of somebody else discovering your password before you realize that it leaked, you may choose to change it on a periodical basis. If you fear that you have lost control over a copy of the database, you will need to change all the passwords contained in it within the time that it may take to brute-force the master password, according to its entropy.

=== Password hashes ===

A hash is a one-way function, i.e. it is designed to make it impossible to deduct the input without computing the hash function with it (example: MD5, SHA).

A password-hash function is designed to make deducting a user-input (password) impossible without computing the hash function with it (example: bcrypt). A [[Wikipedia:Key derivation function|key derivation function]] (KDF; examples: yescrypt, scrypt, PBKDF2) is a cryptographic algorithm designed to derive secret keys (e.g. an AES key, a password hash) from an input (a master key, a password). Hence, a KDF can serve multiple applications, including those of a password-hash function.

By default, Arch stores the hashed user passwords in the root-only-readable {{ic|/etc/shadow}} file, separated from the other user parameters stored in the world-readable {{ic|/etc/passwd}} file, see [[Users and groups#User database]]. See also [[#Restricting root]].

Passwords are set with the '''passwd''' command, which [[Wikipedia:Key stretching|stretches]] them with the system's crypt function and then saves them in {{ic|/etc/shadow}}. The passwords are also [[Wikipedia:Salt (cryptography)|salted]] in order to defend them against [[Wikipedia:Rainbow table|rainbow table]] attacks. See also [https://www.slashroot.in/how-are-passwords-stored-linux-understanding-hashing-shadow-utils How are passwords stored in Linux (Understanding hashing with shadow utils)].

Since password hashes follow a defined format, the method and parameter can be configured for subsequent new invocations of the ''passwd'' command. Hence, the individual hashes stored in the {{ic|/etc/shadow}} file can be a heterogeneous mix of the hash functions supported by the system.

See {{man|5|crypt}} for more information on the format, hashing methods and parameters.

The {{ic|/etc/login.defs}} file configures the [https://archlinux.org/news/changes-to-default-password-hashing-algorithm-and-umask-settings/ default password hashing] method {{ic|ENCRYPT_METHOD YESCRYPT}} and its parameter {{ic|YESCRYPT_COST_FACTOR}}.

For example, an increment of the default {{ic|YESCRYPT_COST_FACTOR}} parameter will lead to a logarithmic increase of the compute time required to deduce the hash from a password. This applies, likewise, to a third-party trying to obtain the password secret, and the system to authenticate a user log-in.

In contrast, the compute time for the SHA-512 hash function is configured by a parameter with a linear influence. See [[SHA password hashes]] for information on the previous Arch default. Note the yescrypt algorithm internally uses SHA-256, HMAC and PBKDF2 to compute its password-hash. The main reason is to combine positive attributes of these widely used and tested functions for an enhanced resistance to attacks. For example, the usability of SHA for various purposes has resulted in hardware support for the function, i.e. the performance to compute a pure SHA hash has accelerated considerably, making its application as a password-hash function more and more derelict.

=== Enforcing strong passwords with pam_pwquality ===

PAM stands for the Pluggable Authentication Modules. ''pam_pwquality'' provides protection against [[Wikipedia:Dictionary attack|Dictionary attacks]] and helps configure a password policy that can be enforced throughout the system. It is based on ''pam_cracklib'', so it is backwards compatible with its options.

[[Install]] the {{Pkg|libpwquality}} package.

{{Warning|The ''root'' account is not affected by this policy by default.}}

{{Note|
* You can use the ''root'' account to set a password for a user that bypasses the desired/configured policy. This is useful when setting temporary passwords.
* Current security guidelines around passwords, e.g. from NIST, but also from others, do not recommend enforcing special characters, since they often only lead to predictable alterations.
}}

If for example you want to enforce this policy:

* prompt 2 times for password in case of an error (retry option)
* 10 characters minimum length (minlen option)
* at least 6 characters should be different from old password when entering a new one (difok option)
* at least 1 digit (dcredit option)
* at least 1 uppercase (ucredit option)
* at least 1 lowercase (lcredit option)
* at least 1 other character (ocredit option)
* cannot contain the words "myservice" and "mydomain"
* enforce the policy for root

Edit the {{ic|/etc/pam.d/passwd}} file to read as:

{{bc|1=
#%PAM-1.0
password required pam_pwquality.so retry=2 minlen=10 difok=6 dcredit=-1 ucredit=-1 ocredit=-1 lcredit=-1 [badwords=myservice mydomain] enforce_for_root
password required pam_unix.so use_authtok yescrypt shadow
}}

The {{ic|password required pam_unix.so use_authtok}} instructs the ''pam_unix'' module to not prompt for a password but rather to use the one provided by ''pam_pwquality''.

You can refer to the {{man|8|pam_pwquality}} and {{man|8|pam_unix}} man pages for more information.

== CPU ==

=== Microcode ===

See [[microcode]] for information on how to install important security updates for your CPU's microcode.

=== Hardware vulnerabilities ===

Some CPUs contain hardware vulnerabilities. See the [https://docs.kernel.org/admin-guide/hw-vuln/ kernel documentation on hardware vulnerabilities] for a list of these vulnerabilities, as well as mitigation selection guides to help customize the kernel to mitigate these vulnerabilities for specific usage scenarios.

To check if you are affected by a known vulnerability, run the following:

$ grep -r . /sys/devices/system/cpu/vulnerabilities/

In most cases, updating the kernel and microcode will mitigate vulnerabilities.

==== Simultaneous multithreading (hyper-threading) ====

[[Wikipedia:Simultaneous multithreading|Simultaneous multithreading]] (SMT), also called hyper-threading on Intel CPUs, is a hardware feature that may be a source of [https://docs.kernel.org/admin-guide/hw-vuln/l1tf.html L1 Terminal Fault] and [https://docs.kernel.org/admin-guide/hw-vuln/mds.html Microarchitectural Data Sampling] vulnerabilities. The Linux kernel and microcode updates contain mitigations for known vulnerabilities, but [https://docs.kernel.org/admin-guide/hw-vuln/l1tf.html#virtualization-with-untrusted-guests disabling SMT may still be required on certain CPUs if untrusted virtualization guests are present].

{{Note|Disabling SMT is something mostly hypervisors benefit from.[https://security.stackexchange.com/questions/219753/sacrificing-30-of-my-cpu-performance-by-disabling-hyper-threading-to-fully-mi/219759#219759] On an ordinary system it has very little to no security benefits.}}

SMT can often be disabled in your system's firmware. Consult your motherboard or system documentation for more information. You can also disable SMT in the kernel by adding the following [[kernel parameter]]:

mitigations=auto,nosmt

== Memory ==

=== Hardened malloc ===

{{AUR|hardened_malloc}} is a hardened replacement for [[Wikipedia:GNU C Library|glibc]]'s malloc(). The project was originally developed for integration into Android's [[Wikipedia:Bionic (software)|Bionic]] and [[Wikipedia:musl|musl]] by Daniel Micay, of [[Wikipedia:GrapheneOS|GrapheneOS]], but he has also built in support for standard Linux distributions on the x86_64 architecture.

== Storage ==

=== Data-at-rest encryption ===

[[Data-at-rest encryption]], preferably full-disk encryption with a [[#Passwords|strong passphrase]], is the only way to guard data against physical recovery. This provides data confidentiality when the computer is turned off or the disks in question are unmounted.

Once the computer is powered on and the drive is mounted, however, its data becomes just as vulnerable as an unencrypted drive. It is therefore best practice to unmount data partitions as soon as they are no longer needed.

You may also [[Trusted Platform Module#LUKS encryption|encrypt a drive with the key stored in a TPM]], although it has had [https://tpm.fail vulnerabilites in the past] and the key can be extracted by a [https://pulsesecurity.co.nz/articles/TPM-sniffing bus sniffing attack].

Certain programs, like [[dm-crypt]], allow the user to encrypt a loop file as a virtual volume. This is a reasonable alternative to full-disk encryption when only certain parts of the system need to be secure.

While the block-device or filesystem-based encryption types compared in the [[data-at-rest encryption]] article are useful at protecting data on physical media, most can not be used to protect data on a remote system that you can not control (such as [[Data-at-rest encryption#Cloud-storage optimized|cloud storage]]). In some cases, individual file encryption will be useful.

These are some methods to encrypt files:

* Some [[Archiving and compression|archiving and compressing]] tools also provide basic encryption. Some examples are [[7-Zip]] ({{ic|-p}} flag), {{Pkg|zip}} ({{ic|-e}} flag). The encryption should only be relied on particular care, because the tools may use custom algorithms for cross-platform compatibility.[https://math.ucr.edu/~mike/zipattacks.pdf]
* [[GnuPG]] can be used to [[GnuPG#Encrypt and decrypt|encrypt files]].
* {{Pkg|age}} is a simple and easy to use file encryption tool. It also supports multiple recipients and encryption using SSH keys, which is useful for secure file sharing.

=== File systems ===

The kernel now prevents security issues related to hardlinks and symlinks if the {{ic|fs.protected_hardlinks}} and {{ic|fs.protected_symlinks}} sysctl switches are enabled, so there is no longer a major security benefit from separating out world-writable directories.

File systems containing world-writable directories can still be kept separate as a coarse way of limiting the damage from disk space exhaustion. However, filling {{ic|/var}} or {{ic|/tmp}} is enough to take down services. More flexible mechanisms for dealing with this concern exist (like [[Disk quota|quotas]]), and some [[file systems]] include related features themselves (Btrfs has quotas on subvolumes).

==== Mount options ====

Following the principle of least privilege, file systems should be mounted with the most restrictive mount options possible (without losing functionality).

Relevant mount options are:

* {{ic|nodev}}: Do not interpret character or block special devices on the file system.
* {{ic|nosuid}}: Do not allow set-user-identifier or set-group-identifier bits to take effect.
* {{ic|noexec}}: Do not allow direct execution of any binaries on the mounted file system.
** Setting {{ic|noexec}} on {{ic|/home}} disallows executable scripts and breaks [[Wine]], [[Steam]], PyCharm, [[.NET]], etc.
*** Wine does not need the {{ic|exec}} flag for opening Windows binaries. It is only needed when Wine itself is installed in {{ic|/home}}.
*** To keep [[Steam]] working you can mount {{ic|/home/user/.local/share/Steam}} as {{ic|exec}} in [[fstab]] by adding the following: {{bc|/home/user/.local/share/Steam /home/user/.local/share/Steam none defaults,bind,user,exec,nofail 0 0}}
** Some packages (building {{Pkg|nvidia-open-dkms}} for example) may require {{ic|exec}} on {{ic|/var}}.

File systems used for data should always be mounted with {{ic|nodev}}, {{ic|nosuid}} and {{ic|noexec}}.

Potential file system mounts to consider:

* {{ic|/var}}
* {{ic|/home}}
* {{ic|/dev/shm}}
* {{ic|/tmp}}
* {{ic|/boot}}

{{Tip|When using [[systemd#GPT partition automounting|GPT partition automounting]], the ESP and XBOOTLDR partitions are [https://github.com/systemd/systemd-stable/commit/49804cfb71d3a79f433096e4cfb5616980171336 always hardened] with {{ic|noexec,nosuid,nodev}}.}}

==== Snapshots ====

When utilizing file system snapshots, e.g. with [[Btrfs]], [[LVM]], or [[ZFS]], it is essential to be aware that snapshots may retain sensitive information that users expect to be deleted. This is especially true when automatic snapshotting tools like [[Snapper]] are configured, as they can capture snapshots at regular intervals or in response to system events. Here are some examples of how sensitive information in {{ic|/home/}} can persist within snapshots:

* ''Deleted files and directories'': Even though files or directories are deleted from the file system, they may still exist within older snapshots. This is expected most of the time, but consider whether files and directories such as {{ic|.local/share/Trash/}}, {{ic|.history}}, etc. should be retained.
* ''Temporary files and cache'': Temporary files and cached data generated by applications may be included in snapshots. For example, files kept in encrypted directories might generate thumbnails ({{ic|.cache/thumbnails}}) or work copies when opened, which might in turn be included in snapshots. The same applies e.g. to browsing history ({{ic|.mozilla/}}, {{ic|.config/chromium/}}, etc.), which could have been included in a snapshot before being purged.

If this is supported, consider excluding such directories from snapshots altogether. For example, if using [[Btrfs]], you can create subvolumes for example {{ic|.cache/}}, {{ic|.config/}}, {{ic|.local/}}, {{ic|.var/}} or any other directory according to your use-case.

{{Note|Moving {{ic|.local/share/Trash}} to a separate subvolume might break the trash feature in some cases, e.g. with [[GNOME/Files]].}}

=== File access permissions ===

{{Accuracy|{{ic|chmod go-r}} does not "take away all permissions", it only removes the read permission.}}

The default [[file permissions]] allow read access to almost everything and changing the permissions can hide valuable information from an attacker who gains access to a non-root account such as the {{ic|http}} or {{ic|nobody}} users. You can use [[chmod]] to take away all permissions from the group and others:

# chmod go-r ''path_to_hide''

{{Warning|Do not apply this broadly. Try this for one config at a time, ensuring that it is worth hiding, and that it will not break program functionality. You may need to remove the {{ic|g}} from the command (or re-add the permission with {{ic|chmod g+r ''path''}} if already ran) if the group is relied on.}}

Some paths to consider are:

* {{ic|/boot}}: The [[Partitioning#/boot|boot directory]], which may include traditional [[vmlinuz]] and [[initramfs]] images, or a [[Unified kernel image]]. Note that safe permissions are used by default when using [[systemd#GPT partition automounting]].
* {{ic|/etc/nftables.conf}}: The [[nftables]] configuration, applicable to {{Pkg|nftables}} and {{Pkg|iptables}}.
* {{ic|/etc/iptables}}: The legacy [[iptables]] configuration, applicable to {{Pkg|iptables-legacy}}.

The default [[umask]] {{ic|0022}} can be changed to improve security for newly created files. The [https://apps.nsa.gov/iaarchive/library/ia-guidance/security-configuration/operating-systems/guide-to-the-secure-configuration-of-red-hat-enterprise.cfm NSA RHEL5 Security Guide] suggests a umask of {{ic|0077}} for maximum security, which makes new files not readable by users other than the owner. To change this, see [[Umask#Set the mask value]]. If you use [[sudo]], consider configuring it to use the [[Sudo#Permissive umask|default root umask]].

=== SUID and SGID files ===

It is important to be aware of any files with the [[Wikipedia:Setuid|Setuid]] or Setgid bit. Examples of relevant files with the SUID bit set:

* [[PAM|unix_chkpwd]]
* chage, expiry, gpasswd, groupmems, [[passwd]], sg ({{Pkg|shadow}})
* [[FUSE|fusermount3]], fusermount2
* [[polkit|pkexec]]
* [[OpenSSH|ssh-keysign]]
* chfn, chsh, mount, newgrp, umount, wall, write ({{Pkg|util-linux}})
* [[sudo]], {{Pkg|sudo-rs}}, [[doas]], [[su]], su-rs, [[Kerberos|ksu]]
* [[firejail]]
* [[Dbus|dbus-daemon-launch-helper]]
* [[Chromium|chromium-sandbox]]
* [[Xorg|Xorg.wrap]]

The prominent risks of such executable files include privilege escalation vulnerabilities, see e.g [[Wikipedia:Setuid#Security impact]].[https://www.cvedetails.com/vulnerability-list/vendor_id-16224/product_id-36412/Calibre-ebook-Calibre.html][https://www.cvedetails.com/product/32625/Sudo-Project-Sudo.html?vendor_id=15714][https://www.cvedetails.com/vulnerability-list/vendor_id-16191/Firejail-Project.html]

Files with the SUID bit set and not owned by root, or files with the SGID bit set ''typically'' have less potential impact but can theoretically still do decent damage if vulnerable. It is usually possible to avoid using SUID or SGID by assigning [[Capabilities]] instead.

{{Tip|It is vital to be vigilant in keeping packages which provide SUID/SGID executables up to date in order to prevent having a vulnerable system.}}

To search for files with either the SUID or SGID bit:

$ find / -perm "/u=s,g=s" -type f 2>/dev/null

=== Backups ===

{{Merge|System backup|There is a dedicated page for system backups.}}

Regularly create backups of important data. Regularly test the integrity of the backups. Regularly test that the backups can be restored.

Make sure that at least one copy of the data is stored offline, i.e. not connected to the system under threat in any way. [[Wikipedia:Ransomware|Ransomware]] and other destructive attacks may also attack any connected backup systems.

=== SATA SSD frozen mode ===

See [[Solid state drive#Setting the SATA SSD state to frozen mode after waking up from sleep]].

== User setup ==

=== Do not use the root account for daily use ===

Following the principle of least privilege, do not use the root user for daily use. Create a non-privileged user account for each person using the system. See [[List of applications/Security#Privilege elevation]] for ways of temporarily gaining privileged access.

=== Enforce a delay after a failed login attempt ===

Add the following line to {{ic|/etc/pam.d/system-login}} to add a delay of at least 4 seconds between failed login attempts:

{{hc|/etc/pam.d/system-login|2=
auth optional pam_faildelay.so delay=4000000
}}

{{Note|This line needs to be the first line in the file.}}

{{ic|4000000}} is the time in microseconds to delay.

{{Note|Other PAM modules besides {{ic|pam_faildelay}} can also suggest such a delay; if multiple modules do so, PAM will use the longest one.
In particular, both {{ic|pam_unix}} and {{ic|pam_faillock}} set a minimum delay of 2 seconds by default.
In order to completely remove this delay, you need to add the {{ic|nodelay}} parameter to any {{ic|auth}} lines of these modules, e.g.
{{hc|/etc/pam.d/system-auth|2=
auth [success{{=}}1 default{{=}}bad] pam_unix.so try_first_pass nullok nodelay
}}
}}

=== Lock out user after three failed login attempts ===

Since {{Pkg|pambase}} 20200721.1-2, {{ic|pam_faillock.so}} is enabled by default to lock out users for 10 minutes after 3 failed login attempts in a 15 minute period (see {{Bug|67644}}). The lockout only applies to password authentication (e.g. login and ''sudo''), public key authentication over SSH is still accepted. To prevent complete denial-of-service, this lockout is disabled for the root user by default.

To unlock a user, do:

$ faillock --user ''username'' --reset

By default, the lock mechanism is a file per-user located at {{ic|/run/faillock/}}. Deleting or emptying the file unlocks that user—the directory is owned by root, but the file is owned by the user, so the {{ic|faillock}} command only empties the file, therefore does not require root.

The module {{ic|pam_faillock.so}} can be configured with the file {{ic|1=/etc/security/faillock.conf}}. The lockout parameters:

* {{ic|unlock_time}} — the lockout time (in seconds, default 10 minutes).
* {{ic|fail_interval}} — the time in which failed logins can cause a lockout (in seconds, default 15 minutes).
* {{ic|deny}} — the number of failed logins before lockout (default 3).

{{Tip|The primary purpose for the lockout is to slow down brute-force attacks so that they become infeasible. Hence, if lockouts due to mistyping of passwords become too frequent, relaxing the number of attempts may be preferred to reducing the lockout time.}}

{{Note|{{ic|1=deny = 0}} will disable the lockout mechanism entirely.}}

By default, all user locks are lost after reboot. If your attacker can reboot the machine, it is more secure if locks persist. To make locks persist, change the {{ic|dir}} parameter in {{ic|1=/etc/security/faillock.conf}} to {{ic|/var/lib/faillock}}.

No restart is required for changes to take effect. See {{man|5|faillock.conf}} for further configuration options, such as enabling lockout for the root account, disabling for centralized login (e.g. LDAP), etc.

{{Note|If you make locks persistant, following the changes introduced in polkit 127: you may have to relax the sandbox of its helper agent in order to keep it functional. The best way is to create a drop-in for its systemd unit via {{ic|systemctl edit polkit-agent-helper\@.service}} and add:

[Service]
ReadWritePaths{{=}}/var/lib/faillock
}}

=== Limit amount of processes ===

On systems with many, or untrusted users, it is important to limit the number of processes each can run at once, therefore preventing [[Wikipedia:Fork bomb|fork bombs]] and other denial of service attacks. The {{ic|/etc/security/limits.conf}} configuration determines how many processes each user, or group can have open, and is empty (except for useful comments) by default. Adding the following lines to this file will limit all users to 100 active processes, unless they use the {{ic|prlimit}} command to explicitly raise their maximum to 200 for that session. These values can be changed according to the appropriate number of processes a user should have running, or the hardware of the box you are administrating.

* soft nproc 100
* hard nproc 200

The current number of threads for each user can be found with {{ic|ps --no-headers -Leo user {{!}} sort {{!}} uniq --count}}. This may help with determining appropriate values for the users' limits; see also [[limits.conf]].

=== Use Wayland ===

Prefer using [[Wayland]] over [[Xorg]]. Xorg's design predates modern security practices and is [https://security.stackexchange.com/questions/4641/why-are-people-saying-that-the-x-window-system-is-not-secure/4646#4646 considered insecure] by many. For example, Xorg applications may record keystrokes while inactive.

If you must run Xorg, it is recommended to [[Xorg#Rootless Xorg|avoid running it as root]]. Within Wayland, the Xwayland compatibility layer will automatically use rootless Xorg.

== Restricting root ==

The root user is, by definition, the most powerful user on a system. It is also difficult to [[audit]] the root user account. It is therefore important to restrict usage of the root user account as much as possible. There are a number of ways to keep the power of the root user while limiting its ability to cause harm.

=== Use sudo instead of su ===

Using [[sudo]] for privileged access is preferable to [[su]] for a number of reasons:

* It keeps a log of which normal privilege user has run each privileged command.
* The root user password need not be given out to each user who requires root access.
* {{ic|sudo}} prevents users from accidentally running commands as ''root'' that do not need root access, because a full root terminal is not created. This aligns with the [[Wikipedia:Principle of least privilege|principle of least privilege]].
* Individual programs may be enabled per user, instead of offering complete root access just to run one command.

See [[Sudo#Configuration]].

==== Editing files using sudo ====

See [[Sudo#Editing files]]. Alternatively, you can use editors like {{ic|rvim}} or {{ic|rnano}} which have restricted capabilities in order to be safe to run as root.

=== Restricting root login ===

Once [[sudo]] is properly configured, full root access can be heavily restricted or denied without losing much usability. To disable root, but still allowing to use [[sudo]], you can use {{man|1|passwd}} with {{ic|passwd --lock root}}.

==== Allow only certain users ====

The [[PAM]] {{ic|pam_wheel.so}} lets you allow only users in the group {{ic|wheel}} to login using [[su]]. See [[su#su and wheel]].

==== Denying SSH login ====

Even if you do not wish to deny root login for local users, it is always good practice to [[OpenSSH#Deny|deny root login via SSH]]. The purpose of this is to add an additional layer of security before a user can completely compromise your system remotely.

==== Specify acceptable login combinations with access.conf ====

{{Warning|If you are using GNOME 49 or later, you should make sure the group ''gdm'' can log in locally. This can be done with a {{ic|+:(gdm):LOCAL}} rule. [https://gitlab.gnome.org/GNOME/gdm/-/issues/1021]}}

When someone attempts to log in with [[PAM]], {{ic|/etc/security/access.conf}} is checked for the first combination that matches their login properties. Their attempt then fails or succeeds based on the rule for that combination.

+:root:LOCAL
-:root:ALL

Rules can be set for specific groups and users. In this example, the user archie is allowed to login locally, as are all users in the wheel and adm groups. All other logins are rejected:

+:archie:LOCAL
+:(wheel):LOCAL
+:(adm):LOCAL
-:ALL:ALL

Read more at {{man|5|access.conf}}

== Mandatory access control ==

[[Wikipedia:Mandatory Access Control|Mandatory access control]] (MAC) is a type of security policy that differs significantly from the [[Wikipedia:Discretionary Access Control|discretionary access control]] (DAC) used by default in Arch and most Linux distributions. MAC essentially means that every action a program could perform that affects the system in any way is checked against a security ruleset. This ruleset, in contrast to DAC methods, cannot be modified by users. Using virtually any mandatory access control system will significantly improve the security of your computer, although there are differences in how it can be implemented.

=== Pathname MAC ===

Pathname-based access control is a simple form of access control that offers permissions based on the path of a given file. The downside to this style of access control is that permissions are not carried with files if they are moved around the system. On the positive side, pathname-based MAC can be implemented on a much wider range of filesystems, unlike labels-based alternatives.

* [[AppArmor]] is a [[Wikipedia:Canonical (company)|Canonical]]-maintained MAC implementation seen as an "easier" alternative to SELinux.
* [[TOMOYO]] is another simple, easy-to-use system offering mandatory access control. It is designed to be both simple in usage and in implementation, requiring very few dependencies.

=== Labels MAC ===

Labels-based access control means the extended attributes of a file are used to govern its security permissions. While this system is arguably more flexible in its security offerings than pathname-based MAC, it only works on filesystems that support these extended attributes.

* [[SELinux]], based on an [[Wikipedia:NSA|NSA]] project to improve Linux security, implements MAC completely separate from system users and roles. It offers an extremely robust multi-level MAC policy implementation that can easily maintain control of a system that grows and changes past its original configuration.

=== Access Control Lists ===

[[Access Control Lists]] (ACLs) are an alternative to attaching rules directly to the filesystem in some way. ACLs implement access control by checking program actions against a list of permitted behavior.

== Kernel hardening ==

=== Kernel self-protection / exploit mitigation ===

The {{pkg|linux-hardened}} package uses a [https://github.com/anthraxx/linux-hardened basic kernel hardening patch set] and more security-focused compile-time configuration options than the {{pkg|linux}} package. A custom build can be made to choose a different compromise between security and performance than the security-leaning defaults.

However, it should be noted that several packages (such as {{pkg|throttled}}) will not work when using this kernel.

If you use an out-of-tree driver such as [[NVIDIA]], you may need to switch to its [[DKMS]] package.

==== Userspace ASLR comparison ====

The {{pkg|linux-hardened}} package provides an improved implementation of Address Space Layout Randomization for userspace processes. The {{pkg|paxtest}} command can be used to obtain an estimate of the provided entropy:

===== 64-bit processes =====

{{hc|linux-hardened 5.4.21.a-1-hardened|
Anonymous mapping randomization test : 32 quality bits (guessed)
Heap randomization test (ET_EXEC) : 40 quality bits (guessed)
Heap randomization test (PIE) : 40 quality bits (guessed)
Main executable randomization (ET_EXEC) : 32 quality bits (guessed)
Main executable randomization (PIE) : 32 quality bits (guessed)
Shared library randomization test : 32 quality bits (guessed)
VDSO randomization test : 32 quality bits (guessed)
Stack randomization test (SEGMEXEC) : 40 quality bits (guessed)
Stack randomization test (PAGEEXEC) : 40 quality bits (guessed)
Arg/env randomization test (SEGMEXEC) : 44 quality bits (guessed)
Arg/env randomization test (PAGEEXEC) : 44 quality bits (guessed)
Offset to library randomisation (ET_EXEC): 34 quality bits (guessed)
Offset to library randomisation (ET_DYN) : 34 quality bits (guessed)
Randomization under memory exhaustion @~0: 32 bits (guessed)
Randomization under memory exhaustion @0 : 32 bits (guessed)
}}

{{hc|linux 5.5.5-arch1-1|
Anonymous mapping randomization test : 28 quality bits (guessed)
Heap randomization test (ET_EXEC) : 28 quality bits (guessed)
Heap randomization test (PIE) : 28 quality bits (guessed)
Main executable randomization (ET_EXEC) : 28 quality bits (guessed)
Main executable randomization (PIE) : 28 quality bits (guessed)
Shared library randomization test : 28 quality bits (guessed)
VDSO randomization test : 20 quality bits (guessed)
Stack randomization test (SEGMEXEC) : 30 quality bits (guessed)
Stack randomization test (PAGEEXEC) : 30 quality bits (guessed)
Arg/env randomization test (SEGMEXEC) : 22 quality bits (guessed)
Arg/env randomization test (PAGEEXEC) : 22 quality bits (guessed)
Offset to library randomisation (ET_EXEC): 28 quality bits (guessed)
Offset to library randomisation (ET_DYN) : 28 quality bits (guessed)
Randomization under memory exhaustion @~0: 29 bits (guessed)
Randomization under memory exhaustion @0 : 29 bits (guessed)
}}

{{hc|linux-lts 4.19.101-1-lts|
Anonymous mapping randomization test : 28 quality bits (guessed)
Heap randomization test (ET_EXEC) : 28 quality bits (guessed)
Heap randomization test (PIE) : 28 quality bits (guessed)
Main executable randomization (ET_EXEC) : 28 quality bits (guessed)
Main executable randomization (PIE) : 28 quality bits (guessed)
Shared library randomization test : 28 quality bits (guessed)
VDSO randomization test : 19 quality bits (guessed)
Stack randomization test (SEGMEXEC) : 30 quality bits (guessed)
Stack randomization test (PAGEEXEC) : 30 quality bits (guessed)
Arg/env randomization test (SEGMEXEC) : 22 quality bits (guessed)
Arg/env randomization test (PAGEEXEC) : 22 quality bits (guessed)
Offset to library randomisation (ET_EXEC): 28 quality bits (guessed)
Offset to library randomisation (ET_DYN) : 28 quality bits (guessed)
Randomization under memory exhaustion @~0: 28 bits (guessed)
Randomization under memory exhaustion @0 : 28 bits (guessed)
}}

===== 32-bit processes (on an x86_64 kernel) =====

{{hc|linux-hardened|
Anonymous mapping randomization test : 16 quality bits (guessed)
Heap randomization test (ET_EXEC) : 22 quality bits (guessed)
Heap randomization test (PIE) : 27 quality bits (guessed)
Main executable randomization (ET_EXEC) : No randomization
Main executable randomization (PIE) : 18 quality bits (guessed)
Shared library randomization test : 16 quality bits (guessed)
VDSO randomization test : 16 quality bits (guessed)
Stack randomization test (SEGMEXEC) : 24 quality bits (guessed)
Stack randomization test (PAGEEXEC) : 24 quality bits (guessed)
Arg/env randomization test (SEGMEXEC) : 28 quality bits (guessed)
Arg/env randomization test (PAGEEXEC) : 28 quality bits (guessed)
Offset to library randomisation (ET_EXEC): 18 quality bits (guessed)
Offset to library randomisation (ET_DYN) : 16 quality bits (guessed)
Randomization under memory exhaustion @~0: 18 bits (guessed)
Randomization under memory exhaustion @0 : 18 bits (guessed)
}}

{{hc|linux|
Anonymous mapping randomization test : 8 quality bits (guessed)
Heap randomization test (ET_EXEC) : 13 quality bits (guessed)
Heap randomization test (PIE) : 13 quality bits (guessed)
Main executable randomization (ET_EXEC) : No randomization
Main executable randomization (PIE) : 8 quality bits (guessed)
Shared library randomization test : 8 quality bits (guessed)
VDSO randomization test : 8 quality bits (guessed)
Stack randomization test (SEGMEXEC) : 19 quality bits (guessed)
Stack randomization test (PAGEEXEC) : 19 quality bits (guessed)
Arg/env randomization test (SEGMEXEC) : 11 quality bits (guessed)
Arg/env randomization test (PAGEEXEC) : 11 quality bits (guessed)
Offset to library randomisation (ET_EXEC): 8 quality bits (guessed)
Offset to library randomisation (ET_DYN) : 13 quality bits (guessed)
Randomization under memory exhaustion @~0: No randomization
Randomization under memory exhaustion @0 : No randomization
}}

=== Restricting access to kernel pointers in the proc filesystem ===

Setting {{ic|kernel.kptr_restrict}} to 1 will hide kernel symbol addresses in {{ic|/proc/kallsyms}} from regular users without {{ic|CAP_SYSLOG}}, making it more difficult for kernel exploits to resolve addresses/symbols dynamically. This will not help that much on a pre-compiled Arch Linux kernel, since a determined attacker could just download the kernel package and get the symbols manually from there, but if you are compiling your own kernel, this can help mitigating local root exploits. This will break some {{Pkg|perf}} commands when used by non-root users (but many {{Pkg|perf}} features require root access anyway). See {{Bug|34323}} for more information.

Setting {{ic|kernel.kptr_restrict}} to 2 will hide kernel symbol addresses in {{ic|/proc/kallsyms}} regardless of privileges.

{{hc|/etc/sysctl.d/51-kptr-restrict.conf|2=
kernel.kptr_restrict = 1
}}

{{Note|{{pkg|linux-hardened}} sets {{ic|1=kptr_restrict=2}} by default rather than {{ic|0}}.}}

=== BPF hardening ===

BPF is a system used to load and execute bytecode within the kernel dynamically during runtime. It is used in a number of Linux kernel subsystems such as networking (e.g. XDP, tc), tracing (e.g. kprobes, uprobes, tracepoints) and security (e.g. seccomp). It is also useful for advanced network security, performance profiling and dynamic tracing.

BPF was originally an acronym of [[Wikipedia:Berkeley Packet Filter|Berkeley Packet Filter]] since the original classic BPF was used for packet capture tools for BSD. This eventually evolved into Extended BPF (eBPF), which was shortly afterwards renamed to just BPF (not an acronym). BPF should not be confused with packet filtering tools like iptables or netfilter, although BPF can be used to implement packet filtering tools.

BPF code may be either interpreted or compiled using a [[Wikipedia:Just-in-time compilation|Just-In-Time (JIT) compiler]]. The Arch kernel is built with {{ic|CONFIG_BPF_JIT_ALWAYS_ON}} which disables the BPF interpreter and forces all BPF to use JIT compilation. This makes it harder for an attacker to use BPF to escalate attacks that exploit SPECTRE-style vulnerabilities. See [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=290af86629b25ffd1ed6232c4e9107da031705cb the kernel patch which introduced CONFIG_BPF_JIT_ALWAYS_ON] for more details.

The kernel includes a hardening feature for JIT-compiled BPF which can mitigate some types of JIT spraying attacks at the cost of performance and the ability to trace and debug many BPF programs. It may be enabled by setting {{ic|net.core.bpf_jit_harden}} to {{ic|1}} (to enable hardening of unprivileged code) or {{ic|2}} (to enable hardening of all code).

See the {{ic|net.core.bpf_*}} settings in the [https://docs.kernel.org/admin-guide/sysctl/net.html kernel documentation] for more details.

{{Tip|
* {{Pkg|linux-hardened}} sets {{ic|1=net.core.bpf_jit_harden=2}} by default rather than {{ic|0}}.
* By default, BPF programs can be run even by unprivileged users. To change that behaviour set {{ic|1=kernel.unprivileged_bpf_disabled=1}}[https://access.redhat.com/security/cve/cve-2021-33624].
}}

=== ptrace scope ===

The {{man|2|ptrace}} syscall provides a means by which one process (the "tracer") may observe and control the execution of another process (the "tracee"), and examine and change the tracee's memory and registers. {{ic|ptrace}} is commonly used by debugging tools including ''gdb'', ''strace'', ''perf'', ''reptyr'' and other debuggers. However, it also provides a means by which a malicious process can read data from and take control of other processes.

Arch enables the [https://docs.kernel.org/admin-guide/LSM/Yama.html Yama LSM] by default, which provides a {{ic|kernel.yama.ptrace_scope}} [[kernel parameter]]. This parameter is set to {{ic|1}} (restricted) by default which prevents tracers from performing a {{ic|ptrace}} call on traces outside of a restricted scope unless the tracer is privileged or has the {{ic|CAP_SYS_PTRACE}} [[Capabilities|capability]]. This is a significant improvement in security compared to the classic permissions. Without this module, there is no separation between processes running as the same user (in the absence of additional security layers such as {{man|7|pid_namespaces}}).

{{Note|By default, you can still use tools which require {{ic|ptrace}} by running them as privileged processes, e.g. using [[sudo]].}}

If you do not need to use debugging tools, consider setting {{ic|kernel.yama.ptrace_scope}} to {{ic|2}} (admin-only) or {{ic|3}} (no {{ic|ptrace}} possible) to harden the system.

{{Note|Some anti-cheat and DRM implementations rely on {{ic|ptrace}} to work, including Easy Anti-Cheat and Ubisoft Connect under Wine. Setting this parameter to {{ic|2}} or higher might prevent games using these solutions from launching.}}

=== hidepid ===

{{Expansion|1=[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0fb5ce62c5920b6e0a8a061f2fe80e0403281e10 Linux 5.8 implemented private instances] and new values for {{ic|1=hidepid=}}.}}

{{Accuracy|Enabling {{ic|hidepid}} globally is not a supported way of operation by [[systemd]], nor does it have any practical improvements security-wise when systemd is running as service manager. [https://github.com/systemd/systemd/issues/29893#issuecomment-1798030108]}}

{{Warning|
* This may cause issues for certain applications like an application running in a sandbox and [[Xorg]] (see workaround).
* This causes issues with [[D-Bus]], [[Polkit]], [[PulseAudio]] and [[bluetooth]] when using {{Pkg|systemd}} > 237.64-1.
}}

The kernel has the ability to hide other users' processes, normally accessible via {{ic|/proc}}, from unprivileged users by mounting the {{ic|proc}} filesystem with the {{ic|1=hidepid=}} and {{ic|1=gid=}} options documented in https://docs.kernel.org/filesystems/proc.html.

This greatly complicates an intruder's task of gathering information about running processes, whether some daemon runs with elevated privileges, whether other user runs some sensitive program, whether other users run any program at all, makes it impossible to learn whether any user runs a specific program (given the program does not reveal itself by its behaviour), and, as an additional bonus, poorly written programs passing sensitive information via program arguments are now protected against local eavesdroppers.

The {{ic|proc}} [[Users and groups#System groups|group]], provided by the {{Pkg|filesystem}} package, acts as a whitelist of users authorized to learn other users' process information. If users or services need access to {{ic|/proc/<pid>}} directories beyond their own, [[Users and groups#Group management|add them to the group]].

For example, to hide process information from other users except those in the {{ic|proc}} group:

{{hc|/etc/fstab|2=
proc /proc proc nosuid,nodev,noexec,hidepid=2,gid=proc 0 0
}}

For user sessions to work correctly, an exception needs to be added for ''systemd-logind'':

{{hc|/etc/systemd/system/systemd-logind.service.d/hidepid.conf|2=
[Service]
SupplementaryGroups=proc
}}

=== Restricting module loading ===

The default Arch kernel has {{ic|CONFIG_MODULE_SIG_ALL}} enabled, which signs all kernel modules built as part of the {{Pkg|linux}} package. This allows the kernel to only load modules signed with a valid key, i.e. out-of-tree modules compiled locally or provided by packages such as {{Pkg|virtualbox-host-modules-arch}} cannot be loaded. You can use {{ic|1=modinfo}} to verify currently loaded modules have signatures; verifying the signatures by hand is slightly more involved [https://unix.stackexchange.com/a/496800].

Kernel module loading can be restricted by setting the {{ic|1=module.sig_enforce=1}} [[kernel parameter]]. More information can be found in the [https://docs.kernel.org/admin-guide/module-signing.html kernel documentation].

Further, unneeded individual modules can be [[blacklist]]ed, see [https://github.com/secureblue/secureblue/blob/live/files/system/usr/lib/modprobe.d/secureblue.conf secureblue] for examples.

=== Disable kexec ===

Kexec allows replacing the current running kernel.

{{hc|/etc/sysctl.d/51-kexec-restrict.conf|2=
kernel.kexec_load_disabled = 1
}}

{{Tip|kexec is disabled by default in {{pkg|linux-hardened}}.}}

=== Kernel lockdown mode ===

Since Linux 5.4 the kernel [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aefcf2f4b58155d27340ba5f9ddbe9513da8286d has gained] an optional [https://mjg59.dreamwidth.org/55105.html lockdown feature], intended to strengthen the boundary between UID 0 (root) and the kernel. When enabled some applications may cease to work which rely on low-level access to either hardware or the kernel.

To use lockdown, its LSM must be initialized and a lockdown mode must be set.

All [[Kernel#Officially supported kernels|officially supported kernels]] initialize the LSM, but none of them enforce any lockdown mode.

{{Tip|Initialized LSMs can be verified by running {{ic|cat /sys/kernel/security/lsm}}.}}

Lockdown has two modes of operation:

* {{ic|integrity}}: kernel features that allow userland to modify the running kernel are disabled (e.g. kexec, bpf).
* {{ic|confidentiality}}: kernel features that allow userland to extract confidential information from the kernel are also disabled.

It is recommended to use {{ic|integrity}}, unless your specific threat model dictates otherwise.

To enable kernel lockdown at runtime, run:

# echo ''mode'' > /sys/kernel/security/lockdown

To enable kernel lockdown on boot, use the [[kernel parameter]] {{ic|1=lockdown=''mode''}}.

{{Note|
* Kernel lockdown cannot be disabled at runtime.
* Kernel lockdown disables [[hibernation]].
* Versions <6.17 of the {{man|7|kernel_lockdown}} man page incorrectly state that "lockdown will be automatically enabled if the system boots in EFI Secure Boot mode". This is not the behaviour of the upstream kernel, nor Arch's packaged [[kernel]]s.
}}

See also {{man|7|kernel_lockdown}}.

=== Linux Kernel Runtime Guard (LKRG) ===

[https://www.openwall.com/lkrg/ LKRG] ({{AUR|lkrg-dkms}}) is a kernel module which performs integrity checking of the kernel and detection of exploit attempts.

=== Disable emergency shell ===

{{Accuracy|Masking {{ic|emergency.target}} and {{ic|emergency.service}} will have no effect on those units being added to the initramfs and run in early userspace. Even with them in the initramfs, mkinitcpio's systemd hook locks the root account[https://gitlab.archlinux.org/archlinux/packaging/packages/systemd/-/commit/292cdf8a2f7dd7c6c7d91d2b59617391935c837c][https://gitlab.archlinux.org/archlinux/packaging/packages/systemd/-/commit/8835b2f5dfbe8663f1a2fd08edbd35f90bf08691] for "security reasons" (see {{Bug|70408}}). The solution for the issue in the linked article, if even needed, would be to prevent {{ic|rescue.target}}, {{ic|rescue.service}}, {{ic|emergency.target}} and {{ic|emergency.service}} from being added to the initramfs image.}}

The emergency shell is used to interactively troubleshoot the machine during the boot process. However, it is also a gadget that an attacker can use to access secure resources such as the TPM. See [https://pulsesecurity.co.nz/advisories/tpm-luks-bypass this article] for a practical example. The difficulty of attacks can be increased by disabling the emergency shell, at the tradeoff of removing a tool to troubleshoot early boot failures.

To disable the emergency shell, See [[systemd#Disable emergency mode on remote machine]].

== Sandboxing applications ==

See also [[Wikipedia:Sandbox (computer security)]].

To improve the security of systemd service units, see [[systemd/Sandboxing]].

{{Warning|Unprivileged user namespace usage ({{ic|CONFIG_USER_NS_UNPRIVILEGED}}) is enabled by default in {{Pkg|linux}}, {{Pkg|linux-lts}} and {{Pkg|linux-zen}}, which greatly increases the attack surface for local privilege escalation (see [https://gitlab.com/apparmor/apparmor/-/wikis/unprivileged_userns_restriction AppArmor's Wiki] and {{Bug|36969}}).}}

To mitigate this, either:

* use the {{Pkg|linux-hardened}} kernel which has the safe default, or
* set the {{ic|kernel.unprivileged_userns_clone}} [[sysctl]] to {{ic|0}}.

Note that this can break applications such as {{pkg|nsjail}}. [[Chromium]] based applications need SUID bit for {{ic|chrome-sandbox}} to work with this setting.

=== Firejail ===

[[Firejail]] is an easy to use tool for sandboxing applications and servers alike. It was originally created for browsers and internet facing applications, but supports a large number of applications by now. To establish a sandboxed environment with a variety of features, it is installed as a suid binary and builds a sandboxed runtime environment for the target application based on black and white lists.

=== bubblewrap ===

[[bubblewrap]] is a sandbox application developed for unprivileged container tools like [[Flatpak]] with a significantly smaller resource footprint and complexity than Firejail. While it lacks certain features such as file path whitelisting, bubblewrap does offer bind mounts as well as the creation of user/IPC/PID/network/cgroup namespaces and can support both simple and complex sandboxes. For the {{Pkg|linux-hardened}} kernel you will need to to use {{Pkg|bubblewrap-suid}}.

[[Bubblejail]] sandbox is based on [[bubblewrap]] and provides a resource oriented permission model with a graphical interface to tweak permissions.

=== Portable ===

[https://github.com/Kraftland/portable Portable] is a sandboxing framework which utilizes [[bubblewrap]] and many other tools to lockdown running applications. It is designed to be simple for packagers and efficient for users, yet cuts off security holes and monitors background processes by default.

See [https://github.com/Kraftland/portable-arch portable-arch] for a repository of applications sandboxed by portable.

If a sandboxed application does not utilize the Portal file chooser, portable can pass files to the sandbox (by passing {{ic|--actions share-files}}).

Portable is fully functional on GNOME, while other desktops may lack small amounts of features like advanced background monitoring and ScreenShot portal.

=== chroots ===

Manual [[chroot]] jails can also be constructed to build sandboxed process environments. It is much more limited than other sandboxing technologies; the extent of its sandboxing is file path isolation.

=== Linux containers ===

[[Linux Containers]] are another good option when you need more separation than the other options (short of [[#Full virtualization options|full system virtualization]]) provide. LXC is run on top of the existing kernel in a pseudo-chroot with their own virtual hardware.

=== gVisor ===

The [https://gvisor.dev/ gVisor] project, led by Google, is providing a sandboxing application with a focus on containers following the [https://opencontainers.org/ OCI initiative], such as [[Docker]] and [[Kubernetes]]. It isolates containers and individual applications from the host by intercepting a majority of system calls to the kernel and presenting itself as guest kernel.

A key difference to other intercepting sandboxing projects is that gVisor re-implements system calls in the Go programming language, as described in its [https://gvisor.dev/docs/architecture_guide/intro/ design overview]. Details for the list of [https://gvisor.dev/docs/user_guide/compatibility/linux/amd64/ re-implemented syscalls support] can be seen in [https://github.com/google/gvisor/blob/master/pkg/sentry/syscalls/linux/linux64.go git]. For usage examples, limitations and special features see the project [https://gvisor.dev/docs/ documentation].

The application is available as {{Aur|gvisor-git}} and {{Aur|gvisor-bin}}.

=== Full virtualization options ===

Using full virtualization options such as [[VirtualBox]], [[KVM]], [[Xen]] or [https://www.qubes-os.org/ Qubes OS] (based on Xen) can also improve isolation and security in the event you plan on running risky applications or browsing dangerous websites.

== Network and firewalls ==

=== Firewalls ===

While the stock Arch kernel is capable of using [[Wikipedia:Netfilter|Netfilter]]'s [[iptables]] and [[nftables]], the services are not [[enable]]d by default. It is highly recommended to set up some form of firewall to protect the services running on the system. Many resources (including ArchWiki) do not state explicitly which services are worth protecting, so enabling a firewall is a good precaution.

* See [[iptables]] and [[nftables]] for general information.
* See [[Simple stateful firewall]] for a guide on setting up an iptables firewall.
* See [[:Category:Firewalls]] for other ways of setting up netfilter.
* See [[Ipset]] for blocking lists of ip addresses, such as those from Bluetack.
* {{Pkg|opensnitch}} is a configurable inbound and outbound firewall with support for configurable rules by application, port, host, etc.

A quick way to setup a basic firewall is to use the tool {{ic|ufw}} (Uncomplicated Fire Wall). Then set {{ic|ufw default deny incoming}} and {{ic|ufw default allow outgoing}} and enabling it with {{ic|ufw enable}} and {{ic|systemctl enable ufw}}.

==== Open ports ====

{{Style|"Open ports" is not a good title since it disregards interfaces and addresses that the application may be bound to. From the firewalls' point of view, ports may be "open" even if no application listens on them at the moment.}}

Some services listen for inbound traffic on open network ports. It is important to only bind these services to the addresses and interfaces that are strictly necessary. It may be possible for a remote attacker to [https://samy.pl/slipstream/ exploit flawed network protocols to access exposed services]. This can even happen with [https://nvd.nist.gov/vuln/detail/CVE-2019-13450 processes bound to localhost].

In general, if a service only needs to be accessible to the local system, bind to a Unix domain socket ({{man|7|unix}}) or a loopback address such as {{ic|localhost}} instead of a non-loopback address like {{ic|0.0.0.0/0}}.

If a service needs to be accessible to other systems via the network, control the access with strict [[firewall]] rules and configure authentication, authorization and encryption whenever possible.

You can list all current open ports with {{ic|ss -l}}. To show all '''l'''istening '''p'''rocesses and their '''n'''umeric '''t'''cp and '''u'''dp port numbers:

# ss -lpntu

See {{man|8|ss}} for more options.

=== Kernel parameters ===

Kernel parameters which affect networking can be set using [[Sysctl]]. For how to do this, see [[Sysctl#TCP/IP stack hardening]].

=== SSH ===

To mitigate [[Wikipedia:Brute-force attack|brute-force attacks]] it is recommended to enforce key-based authentication. For OpenSSH see [[OpenSSH#Protection]] for more recommendations. Alternatively [[Fail2ban]] or [[Sshguard]] offer lesser forms of protection by monitoring logs and writing [[firewall]] rules but open up the potential for a denial of service, since an attacker can [[Wikipedia:Spoofing attack#Spoofing and TCP/IP|spoof]] packets as if they came from the administrator after identifying their address. Spoofing IP has lines of defense, such as by [[sysctl#Reverse path filtering|reverse path filtering]] and [[sysctl#Disable ICMP redirects|disabling ICMP redirects]].

You may want to harden authentication even more by using two-factor authentication. [[Google Authenticator]] provides a two-step authentication procedure using one-time passcodes (OTP).

Denying root login is also a good practice, both for tracing intrusions and adding an additional layer of security before root access. For OpenSSH, see [[OpenSSH#Deny]].

Mozilla publishes an [https://infosec.mozilla.org/guidelines/openssh.html OpenSSH configuration guide] which configures more verbose audit logging and restricts ciphers.

=== DNS ===

The default domain name resolution (DNS) configuration is highly compatible but has security weaknesses. See [[Domain name resolution#Privacy and security|DNS privacy and security]] for more information.

=== Proxies ===

Proxies are commonly used as an extra layer between applications and the network, sanitizing data from untrusted sources. The attack surface of a small proxy running with lower privileges is significantly smaller than a complex application running with the end user privileges.

For example the DNS resolver is implemented in {{Pkg|glibc}}, that is linked with the application (that may be running as root), so a bug in the DNS resolver might lead to a remote code execution. This can be prevented by installing a DNS caching server, such as [[dnsmasq]], which acts as a proxy. [https://googleonlinesecurity.blogspot.it/2016/02/cve-2015-7547-glibc-getaddrinfo-stack.html]

=== Managing TLS certificates ===

See [[TLS#Trust management]].

== Physical security ==

Physical access to a computer is root access given enough time and resources. However, a high ''practical'' level of security can be obtained by putting up enough barriers.

An attacker can gain full control of your computer on the next boot by simply attaching a malicious IEEE 1394 (FireWire), Thunderbolt or PCI Express device as they are given full memory access by default.[https://web.archive.org/web/20210312083421/http://breaknenter.org/2014/09/inception-metasploit-integration/] For Thunderbolt, you can restrict the direct memory access completely or to known devices, see [[Thunderbolt#User device authorization|user device authorization]]. For Firewire and PCI Express, there is little you can do from preventing this, or modification of the hardware itself - such as flashing malicious firmware onto a drive. However, the vast majority of attackers will not be this knowledgeable and determined.

[[#Data-at-rest encryption|Data-at-rest encryption]] will prevent access to your data if the computer is stolen, but malicious firmware can be installed to obtain this data upon your next log in by a resourceful attacker.

=== Locking down BIOS ===

Adding a password to the BIOS prevents someone from booting into removable media, which is basically the same as having root access to your computer. You should make sure your drive is first in the boot order and disable the other drives from being bootable if you can.

=== Boot loaders ===

It is highly important to protect your [[boot loader]]. An unprotected boot loader can bypass any login restrictions, e.g. by setting the {{ic|1=init=/bin/sh}} [[kernel parameter]] to boot directly to a shell.

==== Syslinux ====

[[Syslinux]] supports [[Syslinux#Security|password-protecting your boot loader]]. It allows you to set either a per-menu-item password or a global boot loader password.

==== GRUB ====

[[GRUB]] supports boot loader passwords as well. See [[GRUB/Tips and tricks#Password protection of GRUB menu]] for details. It also has support for [[GRUB#Encrypted /boot|encrypted /boot]], which only leaves some parts of the boot loader code unencrypted. GRUB's configuration, [[kernel]] and [[initramfs]] are encrypted.

==== systemd-boot ====

[[systemd-boot]] disables editing of kernel parameters when [[#Secure Boot|Secure Boot]] is enabled. Alternatively, you can set [[systemd-boot#Kernel parameters editor with password protection|kernel parameters for password protection]] in systemd-boot for a more traditional password-based option.

=== Secure Boot ===

[[Secure Boot]] is a feature of [[UEFI]] that allows authentication of the files your computer boots. This helps preventing some [[Wikipedia:Evil maid attack|evil maid attacks]] such as replacing files inside the boot partition. Normally computers come with keys that are enrolled by vendors (OEM). However these can be removed and allow the computer to enter ''Setup Mode'' which allows the user to enroll and manage their own keys.

The secure boot page guides you through how to set secure boot up by [[Unified Extensible Firmware Interface/Secure Boot#Using your own keys|using your own keys]].

=== Trusted Platform Module (TPM) ===

[[Trusted Platform Module|TPMs]] are hardware microprocessors which have cryptographic keys embedded. This forms the fundamental root of trust of most modern computers and allows end-to-end verification of the boot chain. They can be used as internal smartcards, attest the firmware running on the computer and allow users to insert secrets into a tamper-proof and brute-force resistant store.

=== Boot partition on removable flash drive ===

One popular idea is to place the boot partition on a flash drive in order to render the system unbootable without it. Proponents of this idea often use [[#Data-at-rest encryption|full-disk encryption]] alongside, and some also use [[Dm-crypt/Specialties#Encrypted system using a detached LUKS header|detached encryption headers]] placed on the boot partition.

This method can also be merged with [[Dm-crypt/Specialties#Encrypted /boot and a detached LUKS header on USB|encrypting /boot]].

=== Automatic logout ===

If you are using [[Bash]] or [[Zsh]], you can set {{ic|TMOUT}} for an automatic logout from shells after a timeout.

For example, the following will automatically log out from virtual consoles (but not terminal emulators in X11):

{{hc|/etc/profile.d/shell-timeout.sh|<nowiki>
TMOUT="$(( 60*10 ))";
[ -z "$DISPLAY" ] && export TMOUT;
case $( /usr/bin/tty ) in
/dev/tty[0-9]*) export TMOUT;;
esac
</nowiki>}}

If you really want EVERY Bash/Zsh prompt (even within X) to timeout, use:

$ export TMOUT="$(( 60*10 ))";

Note that this will not work if there is some command running in the shell (eg.: an SSH session or other shell without {{ic|TMOUT}} support). But if you are using VC mostly for restarting frozen GDM/Xorg as root, then this is very useful.

=== Protect against rogue USB devices ===

The kernel has [https://docs.kernel.org/usb/authorization.html settings to deactivate] USB ports to protect your computer against rogue USB devices (a.k.a. [[Wikipedia:BadUSB|BadUSB]], [https://github.com/samyk/poisontap PoisonTap] or [https://lanturtle.com/ LanTurtle]). They can be set at runtime and automated via [[sysctl]].

For more control install [[USBGuard]], which is a software framework implementing basic whitelisting and blacklisting capabilities based on device attributes.

=== Volatile data collection ===

A computer that is powered on may be vulnerable to [https://web.archive.org/web/20210420075636/https://fedvte.usalearning.gov/courses/CSI/course/videos/pdf/CSI_D01_S05_T01_STEP.pdf volatile data collection]. It is a best practice to turn a computer completely off at times it is not necessary for it to be on, or if the computer's physical security is temporarily compromised (e.g. when passing through a security checkpoint).

== Packages ==

=== Authentication ===

[https://www2.cs.arizona.edu/stork/packagemanagersecurity/attacks-on-package-managers.html#overview Attacks on package managers] are possible without proper use of package signing, and can affect even package managers with [https://www2.cs.arizona.edu/stork/packagemanagersecurity/faq.html proper signature systems]. Arch uses package signing by default and relies on a web of trust from 5 trusted master keys. See [[Pacman-key]] for details.

=== Upgrades ===

It is important to regularly [[System maintenance#Upgrading the system|upgrade the system]].

=== Follow vulnerability alerts ===

Subscribe to the Common Vulnerabilities and Exposure (CVE) Security Alert updates, made available by National Vulnerability Database, and found on the [https://nvd.nist.gov/download.cfm NVD Download webpage].

The tool {{Pkg|arch-audit}} can be used to check for vulnerabilities affecting the running system. A graphical system tray, {{Pkg|arch-audit-gtk}}, can also be used. See also [[Arch Security Team]].

You should also consider subscribing to the release notifications for software you use, especially if you install software through means other than the main repositories or AUR. Some software have mailing lists you can subscribe to for security notifications. Source code hosting sites often offer RSS feeds for new releases.

=== Rebuilding packages ===

Packages can be rebuilt and stripped of undesired functions and features as a means to reduce attack surface. For example, {{Pkg|bzip2}} can be rebuilt without {{ic|bzip2recover}} in an attempt to circumvent [https://security.archlinux.org/CVE-2016-3189 CVE-2016-3189]. Custom hardening flags can also be applied either manually or via a wrapper.

{{Merge|Arch package guidelines/Security|Security related build flags have their own article.}}

{{Accuracy|Copy-pasted from a 3 years old blog post. The compiler flags are specific to [[GCC]], some are hardly security related.}}

{| class="wikitable"
! Flag !! Purpose
|-
| -D_FORTIFY_SOURCE=2 || Run-time buffer overflow detection
|-
| -D_GLIBCXX_ASSERTIONS || Run-time bounds checking for C++ strings and containers
|-
| -fasynchronous-unwind-tables || Increased reliability of backtraces
|-
| -fexceptions || Enable table-based thread cancellation
|-
| -fpie -Wl,-pie || Full ASLR for executables
|-
| -fpic -shared || No text relocations for shared libraries
|-
| -fplugin=annobin || Generate data for hardening quality control
|-
| -fstack-clash-protection || Increased reliability of stack overflow detection
|-
| -fstack-protector, -fstack-protector-all or -fstack-protector-strong || Stack smashing protector
|-
| -grecord-gcc-switches || Store compiler flags in debugging information
|-
| -mcet -fcf-protection || Control flow integrity protection
|-
| -Werror=format-security || Reject potentially unsafe format string arguments
|-
| -Werror=implicit-function-declaration || Reject missing function prototypes
|-
| -Wl,-z,defs || Detect and reject underlinking
|-
| -Wl,-z,now || Disable lazy binding
|-
| -Wl,-z,relro || Read-only segments after relocation
|}

* [https://developers.redhat.com/blog/2018/03/21/compiler-and-linker-flags-gcc/ Flags and info source]

== See also ==

* [https://security.archlinux.org/ Arch Linux Security Tracker]
* [https://wiki.centos.org/HowTos/OS_Protection CentOS Wiki: OS Protection]
* [https://web.archive.org/web/20210712001756/https://developer.ibm.com/technologies/linux/articles/l-harden-desktop/ Hardening the Linux desktop]
* [https://web.archive.org/web/20190701140035/https://www.ibm.com/developerworks/linux/tutorials/l-harden-server/index.html Hardening the Linux server]
* [https://github.com/lfit/itpol/blob/master/linux-workstation-security.md Linux Foundation: Linux workstation security checklist]
* [https://www.privacyguides.org/ privacyguides.org Privacy Resources]
* [https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Security_Guide/ Red Hat Enterprise Linux 7 Security Guide]
* [https://www.debian.org/doc/manuals/securing-debian-manual/index.en.html Securing Debian Manual]
* [https://web.archive.org/web/20140220055801/http://crunchbang.org:80/forums/viewtopic.php?id=24722 The paranoid #! Security Guide]

Security

2026-04-26T18:31:23Z

Alad: /* Sandboxing applications */ remove infactual opinion piece from Special:Diff/870229, namespace CVE still occur on the regular, e.g https://www.sentinelone.com/vulnerability-database/cve-2026-31496/

[[Category:Security]]
[[Category:File systems]]
[[Category:Networking]]
[[de:Sicherheit]]
[[es:Security]]
[[hu:Security]]
[[ja:セキュリティ]]
[[pt:Security]]
[[ru:Security]]
[[zh-hans:Security]]
{{Related articles start}}
{{Related|Arch Security Team}}
{{Related|General recommendations}}
{{Related|Identity management}}
{{Related|Capabilities}}
{{Related|List of Applications/Security}}
{{Related|Arch package guidelines/Security}}
{{Related articles end}}
This article contains recommendations and best practices for [[Wikipedia:Hardening (computing)|hardening]] an Arch Linux system.

== Concepts ==

* It ''is'' possible to tighten security to the point where the system is unusable. Security and convenience must be balanced. The trick is to create a secure ''and'' useful system.
* The biggest threat is, and will always be, the user.
* The [[Wikipedia:Principle of least privilege|principle of least privilege]]: Each part of a system should only be able to access what is strictly required, and nothing more.
* Defense in depth: Security works better in independent layers. When one layer is breached, another should stop the attack.
* Be a little paranoid. And be suspicious. If anything sounds too good to be true, it probably is!
* You can never make a system 100% secure unless you unplug the machine from all networks, turn it off, lock it in a safe, smother it in concrete and never use it.
* Prepare for failure. Create a plan ahead of time to follow when your security is broken.

== Passwords ==

Passwords are key to a secure system. They secure your [[Users and groups|user accounts]], [[Data-at-rest encryption|encrypted filesystems]], and [[SSH keys|SSH]]/[[GPG]] keys. They are the main way a computer chooses to trust the person using it, so a big part of security is just about picking secure passwords and protecting them.

=== Choosing secure passwords ===

Passwords must be complex enough to not be easily guessed from e.g. personal information, or [[Wikipedia:Password cracking|cracked]] using methods like brute-force attacks. The tenets of strong passwords are based on ''length'' and ''randomness''. In cryptography the quality of a password is often referred to as its [[Wikipedia:Password strength#Entropy as a measure of password strength|entropy]].

Insecure passwords include those containing or those using as a base before substitution/variation:

* Personally identifiable information (e.g., your dog's name, date of birth, area code, favorite video game)
* Simple character substitutions on words (e.g., {{ic|k1araj0hns0n}}), as modern dictionary attacks can easily work with these
* Root "words" or common strings followed or preceded by added numbers, symbols, or characters (e.g., {{ic|DG091101%}})
* Common phrases or short strings of common dictionary words (e.g. {{ic|photocopyhauntbranchexpose}}) including with character substitution (e.g. {{ic|Ph0toc0pyh4uN7br@nch3xp*se}}) (See Diceware below for when a combination of dictionary words can be secure)
* Any of the [[Wikipedia:List of the most common passwords|most common passwords]]

The best choice for a password is something long (the longer, the better) and generated from a random source. It is important to use a long password. [https://www.theregister.com/2019/02/14/password_length Weak hash algorithms allow an 8-character password hash to be compromised in just a few hours.]

Tools like {{Pkg|pwgen}} or {{AUR|apg}} can generate random passwords. However, these passwords can be difficult to memorize. One memorization technique (for ones often typed) is to generate a long password and memorize a minimally secure number of characters, temporarily writing down the full generated string. Over time, increase the number of characters typed - until the password is ingrained in muscle memory and need not be remembered. This technique is more difficult, but can provide confidence that a password will not turn up in wordlists or "intelligent" brute force attacks that combine words and substitute characters.

Apart from password management, {{Pkg|keepassxc}} offers password/passphrase generation. It is possible to customize the generation in a GUI. Dictionary based passphrases are also supported.

One technique for memorizing a password is to use a mnemonic phrase, where each word in the phrase reminds you of the next character in the password.
Take for instance “the girl is walking down the rainy street” could be translated to {{ic|t6!WdtR5}} or, less simply, {{ic|t&6!RrlW@dtR,57}}.
This approach could make it easier to remember a password, but note that the various letters have very different probabilities of being found at the start of words ([[Wikipedia:Letter frequency#Relative frequencies of the first letters of a word in the English language|Wikipedia:Letter frequency]]).

Another effective technique can be to write randomly generated passwords down and store them in a ''safe'' place, such as in a wallet, purse, or document safe. Most people do a generally good job of protecting their physical valuables from attack, and it is easier for most people to understand physical security best practices compared to digital security practices.

It is also very effective to combine the mnemonic and random technique by saving long randomly generated passwords with a [[password manager]], which will be in turn accessed with a memorable "master password"/primary password that must be used only for that purpose. The master password must be memorized and never saved. This requires the password manager to be installed on a system to easily access the password (which could be seen as an inconvenience or a security feature, depending on the situation). Some password managers also have smartphone apps which can be used to display passwords for manual entry on systems without that password manager installed (if that is a common use case, you could still use easily typeable but secure passwords for each service instead of completely random ones, see below). Note that a password manager introduces a single point of failure if you ever forget the master password.
Some password managers compute the contained passwords based on the master password and the service name where you want to log in instead of encrypting them, making it possible to use it on a new system without syncing any data.

It can be effective to use a memorable long series of unrelated words as a password. The theory is that if a sufficiently long phrase is used, the gained entropy from the password's length can counter the lost entropy from the use of dictionary words. This [https://xkcd.com/936/ xkcd comic] demonstrates the entropy tradeoff of this method, taking into account the limited set of possible words for each word in the passphrase. If the set of words you choose from is large (multiple thousand words) and you choose 5-7 or even more random words from it, this method provides great entropy, even assuming the attacker knows the set of possible words chosen from and the number of words chosen. The number of possible passphrases after settling on a set of words and number of words is: (number of words in the set of words to select from) to the power of (the number of words chosen for the passphrase). See e.g. [https://www.rempe.us/diceware/ Diceware] for more.

See [https://www.iusmentis.com/security/passphrasefaq/ The passphrase FAQ] or [[Wikipedia:Password strength]] for some additional background.

=== Maintaining passwords ===

Once you pick a strong password, be sure to keep it safe. Watch out for [[Wikipedia:Keylogger|keyloggers]] (software and hardware), screen loggers, [[Wikipedia:Social engineering (security)|social engineering]], [[Wikipedia:Shoulder surfing (computer security)|shoulder surfing]], and avoid reusing passwords so insecure servers cannot leak more information than necessary. [[List of applications/Security#Password managers|Password managers]] can help manage large numbers of complex passwords: if you are copy-pasting the stored passwords from the manager to the applications that need them, make sure to clear the copy buffer every time, and ensure they are not saved in any kind of log (e.g. do not paste them in plain terminal commands, which would store them in files like {{ic|.bash_history}}). Note that password managers that are implemented as browser extensions may be vulnerable to [https://www.spookjs.com side channel attacks]. These can be mitigated by using password managers that run as separate applications.

As a rule, do not pick insecure passwords just because secure ones are harder to remember. Passwords are a balancing act. It is better to have an encrypted database of secure passwords, guarded behind a key and one strong master password, than it is to have many similar weak passwords. Writing passwords down is perhaps equally effective [https://www.schneier.com/blog/archives/2005/06/write_down_your.html], avoiding potential vulnerabilities in software solutions while requiring physical security.

Another aspect of the strength of the passphrase is that it must not be easily recoverable from other places.

If you use the same passphrase for disk encryption as you use for your login password (useful e.g. to auto-mount the encrypted partition or folder on login), make sure that {{ic|/etc/shadow}} ends up on an encrypted partition or/and uses a strong key derivation function (i.e. yescrypt/argon2 or sha512 with PBKDF2, but not md5 or low iterations in PBKDF2) for the stored password hash (see [[SHA password hashes]] for more information).

{{Tip|In 2023 Arch Linux switched the [https://archlinux.org/news/changes-to-default-password-hashing-algorithm-and-umask-settings/ default hashing] algorithm to yescrypt. If you have not customized the default, executing a password change with {{ic|passwd}} is necessary (and sufficient) to apply the new default.}}

If you are backing up your password database, make sure that each copy is not stored behind any other passphrase which in turn is stored in it, e.g. an encrypted drive or an authenticated remote storage service, or you will not be able to access it in case of need; a useful trick is to protect the drives or accounts where the database is backed up using a simple cryptographic hash of the master password. Maintain a list of all the backup locations: if one day you fear that the master passphrase has been compromised you will have to change it immediately on all the database backups and the locations protected with keys derived from the master password.

Version-controlling the database in a secure way can be very complicated: if you choose to do it, you must have a way to update the master password of all the database versions. It may not always be immediately clear when the master password is leaked: to reduce the risk of somebody else discovering your password before you realize that it leaked, you may choose to change it on a periodical basis. If you fear that you have lost control over a copy of the database, you will need to change all the passwords contained in it within the time that it may take to brute-force the master password, according to its entropy.

=== Password hashes ===

A hash is a one-way function, i.e. it is designed to make it impossible to deduct the input without computing the hash function with it (example: MD5, SHA).

A password-hash function is designed to make deducting a user-input (password) impossible without computing the hash function with it (example: bcrypt). A [[Wikipedia:Key derivation function|key derivation function]] (KDF; examples: yescrypt, scrypt, PBKDF2) is a cryptographic algorithm designed to derive secret keys (e.g. an AES key, a password hash) from an input (a master key, a password). Hence, a KDF can serve multiple applications, including those of a password-hash function.

By default, Arch stores the hashed user passwords in the root-only-readable {{ic|/etc/shadow}} file, separated from the other user parameters stored in the world-readable {{ic|/etc/passwd}} file, see [[Users and groups#User database]]. See also [[#Restricting root]].

Passwords are set with the '''passwd''' command, which [[Wikipedia:Key stretching|stretches]] them with the system's crypt function and then saves them in {{ic|/etc/shadow}}. The passwords are also [[Wikipedia:Salt (cryptography)|salted]] in order to defend them against [[Wikipedia:Rainbow table|rainbow table]] attacks. See also [https://www.slashroot.in/how-are-passwords-stored-linux-understanding-hashing-shadow-utils How are passwords stored in Linux (Understanding hashing with shadow utils)].

Since password hashes follow a defined format, the method and parameter can be configured for subsequent new invocations of the ''passwd'' command. Hence, the individual hashes stored in the {{ic|/etc/shadow}} file can be a heterogeneous mix of the hash functions supported by the system.

See {{man|5|crypt}} for more information on the format, hashing methods and parameters.

The {{ic|/etc/login.defs}} file configures the [https://archlinux.org/news/changes-to-default-password-hashing-algorithm-and-umask-settings/ default password hashing] method {{ic|ENCRYPT_METHOD YESCRYPT}} and its parameter {{ic|YESCRYPT_COST_FACTOR}}.

For example, an increment of the default {{ic|YESCRYPT_COST_FACTOR}} parameter will lead to a logarithmic increase of the compute time required to deduce the hash from a password. This applies, likewise, to a third-party trying to obtain the password secret, and the system to authenticate a user log-in.

In contrast, the compute time for the SHA-512 hash function is configured by a parameter with a linear influence. See [[SHA password hashes]] for information on the previous Arch default. Note the yescrypt algorithm internally uses SHA-256, HMAC and PBKDF2 to compute its password-hash. The main reason is to combine positive attributes of these widely used and tested functions for an enhanced resistance to attacks. For example, the usability of SHA for various purposes has resulted in hardware support for the function, i.e. the performance to compute a pure SHA hash has accelerated considerably, making its application as a password-hash function more and more derelict.

=== Enforcing strong passwords with pam_pwquality ===

PAM stands for the Pluggable Authentication Modules. ''pam_pwquality'' provides protection against [[Wikipedia:Dictionary attack|Dictionary attacks]] and helps configure a password policy that can be enforced throughout the system. It is based on ''pam_cracklib'', so it is backwards compatible with its options.

[[Install]] the {{Pkg|libpwquality}} package.

{{Warning|The ''root'' account is not affected by this policy by default.}}

{{Note|
* You can use the ''root'' account to set a password for a user that bypasses the desired/configured policy. This is useful when setting temporary passwords.
* Current security guidelines around passwords, e.g. from NIST, but also from others, do not recommend enforcing special characters, since they often only lead to predictable alterations.
}}

If for example you want to enforce this policy:

* prompt 2 times for password in case of an error (retry option)
* 10 characters minimum length (minlen option)
* at least 6 characters should be different from old password when entering a new one (difok option)
* at least 1 digit (dcredit option)
* at least 1 uppercase (ucredit option)
* at least 1 lowercase (lcredit option)
* at least 1 other character (ocredit option)
* cannot contain the words "myservice" and "mydomain"
* enforce the policy for root

Edit the {{ic|/etc/pam.d/passwd}} file to read as:

{{bc|1=
#%PAM-1.0
password required pam_pwquality.so retry=2 minlen=10 difok=6 dcredit=-1 ucredit=-1 ocredit=-1 lcredit=-1 [badwords=myservice mydomain] enforce_for_root
password required pam_unix.so use_authtok yescrypt shadow
}}

The {{ic|password required pam_unix.so use_authtok}} instructs the ''pam_unix'' module to not prompt for a password but rather to use the one provided by ''pam_pwquality''.

You can refer to the {{man|8|pam_pwquality}} and {{man|8|pam_unix}} man pages for more information.

== CPU ==

=== Microcode ===

See [[microcode]] for information on how to install important security updates for your CPU's microcode.

=== Hardware vulnerabilities ===

Some CPUs contain hardware vulnerabilities. See the [https://docs.kernel.org/admin-guide/hw-vuln/ kernel documentation on hardware vulnerabilities] for a list of these vulnerabilities, as well as mitigation selection guides to help customize the kernel to mitigate these vulnerabilities for specific usage scenarios.

To check if you are affected by a known vulnerability, run the following:

$ grep -r . /sys/devices/system/cpu/vulnerabilities/

In most cases, updating the kernel and microcode will mitigate vulnerabilities.

==== Simultaneous multithreading (hyper-threading) ====

[[Wikipedia:Simultaneous multithreading|Simultaneous multithreading]] (SMT), also called hyper-threading on Intel CPUs, is a hardware feature that may be a source of [https://docs.kernel.org/admin-guide/hw-vuln/l1tf.html L1 Terminal Fault] and [https://docs.kernel.org/admin-guide/hw-vuln/mds.html Microarchitectural Data Sampling] vulnerabilities. The Linux kernel and microcode updates contain mitigations for known vulnerabilities, but [https://docs.kernel.org/admin-guide/hw-vuln/l1tf.html#virtualization-with-untrusted-guests disabling SMT may still be required on certain CPUs if untrusted virtualization guests are present].

{{Note|Disabling SMT is something mostly hypervisors benefit from.[https://security.stackexchange.com/questions/219753/sacrificing-30-of-my-cpu-performance-by-disabling-hyper-threading-to-fully-mi/219759#219759] On an ordinary system it has very little to no security benefits.}}

SMT can often be disabled in your system's firmware. Consult your motherboard or system documentation for more information. You can also disable SMT in the kernel by adding the following [[kernel parameter]]:

mitigations=auto,nosmt

== Memory ==

=== Hardened malloc ===

{{AUR|hardened_malloc}} is a hardened replacement for [[Wikipedia:GNU C Library|glibc]]'s malloc(). The project was originally developed for integration into Android's [[Wikipedia:Bionic (software)|Bionic]] and [[Wikipedia:musl|musl]] by Daniel Micay, of [[Wikipedia:GrapheneOS|GrapheneOS]], but he has also built in support for standard Linux distributions on the x86_64 architecture.

== Storage ==

=== Data-at-rest encryption ===

[[Data-at-rest encryption]], preferably full-disk encryption with a [[#Passwords|strong passphrase]], is the only way to guard data against physical recovery. This provides data confidentiality when the computer is turned off or the disks in question are unmounted.

Once the computer is powered on and the drive is mounted, however, its data becomes just as vulnerable as an unencrypted drive. It is therefore best practice to unmount data partitions as soon as they are no longer needed.

You may also [[Trusted Platform Module#LUKS encryption|encrypt a drive with the key stored in a TPM]], although it has had [https://tpm.fail vulnerabilites in the past] and the key can be extracted by a [https://pulsesecurity.co.nz/articles/TPM-sniffing bus sniffing attack].

Certain programs, like [[dm-crypt]], allow the user to encrypt a loop file as a virtual volume. This is a reasonable alternative to full-disk encryption when only certain parts of the system need to be secure.

While the block-device or filesystem-based encryption types compared in the [[data-at-rest encryption]] article are useful at protecting data on physical media, most can not be used to protect data on a remote system that you can not control (such as [[Data-at-rest encryption#Cloud-storage optimized|cloud storage]]). In some cases, individual file encryption will be useful.

These are some methods to encrypt files:

* Some [[Archiving and compression|archiving and compressing]] tools also provide basic encryption. Some examples are [[7-Zip]] ({{ic|-p}} flag), {{Pkg|zip}} ({{ic|-e}} flag). The encryption should only be relied on particular care, because the tools may use custom algorithms for cross-platform compatibility.[https://math.ucr.edu/~mike/zipattacks.pdf]
* [[GnuPG]] can be used to [[GnuPG#Encrypt and decrypt|encrypt files]].
* {{Pkg|age}} is a simple and easy to use file encryption tool. It also supports multiple recipients and encryption using SSH keys, which is useful for secure file sharing.

=== File systems ===

The kernel now prevents security issues related to hardlinks and symlinks if the {{ic|fs.protected_hardlinks}} and {{ic|fs.protected_symlinks}} sysctl switches are enabled, so there is no longer a major security benefit from separating out world-writable directories.

File systems containing world-writable directories can still be kept separate as a coarse way of limiting the damage from disk space exhaustion. However, filling {{ic|/var}} or {{ic|/tmp}} is enough to take down services. More flexible mechanisms for dealing with this concern exist (like [[Disk quota|quotas]]), and some [[file systems]] include related features themselves (Btrfs has quotas on subvolumes).

==== Mount options ====

Following the principle of least privilege, file systems should be mounted with the most restrictive mount options possible (without losing functionality).

Relevant mount options are:

* {{ic|nodev}}: Do not interpret character or block special devices on the file system.
* {{ic|nosuid}}: Do not allow set-user-identifier or set-group-identifier bits to take effect.
* {{ic|noexec}}: Do not allow direct execution of any binaries on the mounted file system.
** Setting {{ic|noexec}} on {{ic|/home}} disallows executable scripts and breaks [[Wine]], [[Steam]], PyCharm, [[.NET]], etc.
*** Wine does not need the {{ic|exec}} flag for opening Windows binaries. It is only needed when Wine itself is installed in {{ic|/home}}.
*** To keep [[Steam]] working you can mount {{ic|/home/user/.local/share/Steam}} as {{ic|exec}} in [[fstab]] by adding the following: {{bc|/home/user/.local/share/Steam /home/user/.local/share/Steam none defaults,bind,user,exec,nofail 0 0}}
** Some packages (building {{Pkg|nvidia-open-dkms}} for example) may require {{ic|exec}} on {{ic|/var}}.

File systems used for data should always be mounted with {{ic|nodev}}, {{ic|nosuid}} and {{ic|noexec}}.

Potential file system mounts to consider:

* {{ic|/var}}
* {{ic|/home}}
* {{ic|/dev/shm}}
* {{ic|/tmp}}
* {{ic|/boot}}

{{Tip|When using [[systemd#GPT partition automounting|GPT partition automounting]], the ESP and XBOOTLDR partitions are [https://github.com/systemd/systemd-stable/commit/49804cfb71d3a79f433096e4cfb5616980171336 always hardened] with {{ic|noexec,nosuid,nodev}}.}}

==== Snapshots ====

When utilizing file system snapshots, e.g. with [[Btrfs]], [[LVM]], or [[ZFS]], it is essential to be aware that snapshots may retain sensitive information that users expect to be deleted. This is especially true when automatic snapshotting tools like [[Snapper]] are configured, as they can capture snapshots at regular intervals or in response to system events. Here are some examples of how sensitive information in {{ic|/home/}} can persist within snapshots:

* ''Deleted files and directories'': Even though files or directories are deleted from the file system, they may still exist within older snapshots. This is expected most of the time, but consider whether files and directories such as {{ic|.local/share/Trash/}}, {{ic|.history}}, etc. should be retained.
* ''Temporary files and cache'': Temporary files and cached data generated by applications may be included in snapshots. For example, files kept in encrypted directories might generate thumbnails ({{ic|.cache/thumbnails}}) or work copies when opened, which might in turn be included in snapshots. The same applies e.g. to browsing history ({{ic|.mozilla/}}, {{ic|.config/chromium/}}, etc.), which could have been included in a snapshot before being purged.

If this is supported, consider excluding such directories from snapshots altogether. For example, if using [[Btrfs]], you can create subvolumes for example {{ic|.cache/}}, {{ic|.config/}}, {{ic|.local/}}, {{ic|.var/}} or any other directory according to your use-case.

{{Note|Moving {{ic|.local/share/Trash}} to a separate subvolume might break the trash feature in some cases, e.g. with [[GNOME/Files]].}}

=== File access permissions ===

{{Accuracy|{{ic|chmod go-r}} does not "take away all permissions", it only removes the read permission.}}

The default [[file permissions]] allow read access to almost everything and changing the permissions can hide valuable information from an attacker who gains access to a non-root account such as the {{ic|http}} or {{ic|nobody}} users. You can use [[chmod]] to take away all permissions from the group and others:

# chmod go-r ''path_to_hide''

{{Warning|Do not apply this broadly. Try this for one config at a time, ensuring that it is worth hiding, and that it will not break program functionality. You may need to remove the {{ic|g}} from the command (or re-add the permission with {{ic|chmod g+r ''path''}} if already ran) if the group is relied on.}}

Some paths to consider are:

* {{ic|/boot}}: The [[Partitioning#/boot|boot directory]], which may include traditional [[vmlinuz]] and [[initramfs]] images, or a [[Unified kernel image]]. Note that safe permissions are used by default when using [[systemd#GPT partition automounting]].
* {{ic|/etc/nftables.conf}}: The [[nftables]] configuration, applicable to {{Pkg|nftables}} and {{Pkg|iptables}}.
* {{ic|/etc/iptables}}: The legacy [[iptables]] configuration, applicable to {{Pkg|iptables-legacy}}.

The default [[umask]] {{ic|0022}} can be changed to improve security for newly created files. The [https://apps.nsa.gov/iaarchive/library/ia-guidance/security-configuration/operating-systems/guide-to-the-secure-configuration-of-red-hat-enterprise.cfm NSA RHEL5 Security Guide] suggests a umask of {{ic|0077}} for maximum security, which makes new files not readable by users other than the owner. To change this, see [[Umask#Set the mask value]]. If you use [[sudo]], consider configuring it to use the [[Sudo#Permissive umask|default root umask]].

=== SUID and SGID files ===

It is important to be aware of any files with the [[Wikipedia:Setuid|Setuid]] or Setgid bit. Examples of relevant files with the SUID bit set:

* [[PAM|unix_chkpwd]]
* chage, expiry, gpasswd, groupmems, [[passwd]], sg ({{Pkg|shadow}})
* [[FUSE|fusermount3]], fusermount2
* [[polkit|pkexec]]
* [[OpenSSH|ssh-keysign]]
* chfn, chsh, mount, newgrp, umount, wall, write ({{Pkg|util-linux}})
* [[sudo]], {{Pkg|sudo-rs}}, [[doas]], [[su]], su-rs, [[Kerberos|ksu]]
* [[firejail]]
* [[Dbus|dbus-daemon-launch-helper]]
* [[Chromium|chromium-sandbox]]
* [[Xorg|Xorg.wrap]]

The prominent risks of such executable files include privilege escalation vulnerabilities, see e.g [[Wikipedia:Setuid#Security impact]].[https://www.cvedetails.com/vulnerability-list/vendor_id-16224/product_id-36412/Calibre-ebook-Calibre.html][https://www.cvedetails.com/product/32625/Sudo-Project-Sudo.html?vendor_id=15714][https://www.cvedetails.com/vulnerability-list/vendor_id-16191/Firejail-Project.html]

Files with the SUID bit set and not owned by root, or files with the SGID bit set ''typically'' have less potential impact but can theoretically still do decent damage if vulnerable. It is usually possible to avoid using SUID or SGID by assigning [[Capabilities]] instead.

{{Tip|It is vital to be vigilant in keeping packages which provide SUID/SGID executables up to date in order to prevent having a vulnerable system.}}

To search for files with either the SUID or SGID bit:

$ find / -perm "/u=s,g=s" -type f 2>/dev/null

=== Backups ===

{{Merge|System backup|There is a dedicated page for system backups.}}

Regularly create backups of important data. Regularly test the integrity of the backups. Regularly test that the backups can be restored.

Make sure that at least one copy of the data is stored offline, i.e. not connected to the system under threat in any way. [[Wikipedia:Ransomware|Ransomware]] and other destructive attacks may also attack any connected backup systems.

=== SATA SSD frozen mode ===

See [[Solid state drive#Setting the SATA SSD state to frozen mode after waking up from sleep]].

== User setup ==

=== Do not use the root account for daily use ===

Following the principle of least privilege, do not use the root user for daily use. Create a non-privileged user account for each person using the system. See [[List of applications/Security#Privilege elevation]] for ways of temporarily gaining privileged access.

=== Enforce a delay after a failed login attempt ===

Add the following line to {{ic|/etc/pam.d/system-login}} to add a delay of at least 4 seconds between failed login attempts:

{{hc|/etc/pam.d/system-login|2=
auth optional pam_faildelay.so delay=4000000
}}

{{Note|This line needs to be the first line in the file.}}

{{ic|4000000}} is the time in microseconds to delay.

{{Note|Other PAM modules besides {{ic|pam_faildelay}} can also suggest such a delay; if multiple modules do so, PAM will use the longest one.
In particular, both {{ic|pam_unix}} and {{ic|pam_faillock}} set a minimum delay of 2 seconds by default.
In order to completely remove this delay, you need to add the {{ic|nodelay}} parameter to any {{ic|auth}} lines of these modules, e.g.
{{hc|/etc/pam.d/system-auth|2=
auth [success{{=}}1 default{{=}}bad] pam_unix.so try_first_pass nullok nodelay
}}
}}

=== Lock out user after three failed login attempts ===

Since {{Pkg|pambase}} 20200721.1-2, {{ic|pam_faillock.so}} is enabled by default to lock out users for 10 minutes after 3 failed login attempts in a 15 minute period (see {{Bug|67644}}). The lockout only applies to password authentication (e.g. login and ''sudo''), public key authentication over SSH is still accepted. To prevent complete denial-of-service, this lockout is disabled for the root user by default.

To unlock a user, do:

$ faillock --user ''username'' --reset

By default, the lock mechanism is a file per-user located at {{ic|/run/faillock/}}. Deleting or emptying the file unlocks that user—the directory is owned by root, but the file is owned by the user, so the {{ic|faillock}} command only empties the file, therefore does not require root.

The module {{ic|pam_faillock.so}} can be configured with the file {{ic|1=/etc/security/faillock.conf}}. The lockout parameters:

* {{ic|unlock_time}} — the lockout time (in seconds, default 10 minutes).
* {{ic|fail_interval}} — the time in which failed logins can cause a lockout (in seconds, default 15 minutes).
* {{ic|deny}} — the number of failed logins before lockout (default 3).

{{Tip|The primary purpose for the lockout is to slow down brute-force attacks so that they become infeasible. Hence, if lockouts due to mistyping of passwords become too frequent, relaxing the number of attempts may be preferred to reducing the lockout time.}}

{{Note|{{ic|1=deny = 0}} will disable the lockout mechanism entirely.}}

By default, all user locks are lost after reboot. If your attacker can reboot the machine, it is more secure if locks persist. To make locks persist, change the {{ic|dir}} parameter in {{ic|1=/etc/security/faillock.conf}} to {{ic|/var/lib/faillock}}.

No restart is required for changes to take effect. See {{man|5|faillock.conf}} for further configuration options, such as enabling lockout for the root account, disabling for centralized login (e.g. LDAP), etc.

{{Note|If you make locks persistant, following the changes introduced in polkit 127: you may have to relax the sandbox of its helper agent in order to keep it functional. The best way is to create a drop-in for its systemd unit via {{ic|systemctl edit polkit-agent-helper\@.service}} and add:

[Service]
ReadWritePaths{{=}}/var/lib/faillock
}}

=== Limit amount of processes ===

On systems with many, or untrusted users, it is important to limit the number of processes each can run at once, therefore preventing [[Wikipedia:Fork bomb|fork bombs]] and other denial of service attacks. The {{ic|/etc/security/limits.conf}} configuration determines how many processes each user, or group can have open, and is empty (except for useful comments) by default. Adding the following lines to this file will limit all users to 100 active processes, unless they use the {{ic|prlimit}} command to explicitly raise their maximum to 200 for that session. These values can be changed according to the appropriate number of processes a user should have running, or the hardware of the box you are administrating.

* soft nproc 100
* hard nproc 200

The current number of threads for each user can be found with {{ic|ps --no-headers -Leo user {{!}} sort {{!}} uniq --count}}. This may help with determining appropriate values for the users' limits; see also [[limits.conf]].

=== Use Wayland ===

Prefer using [[Wayland]] over [[Xorg]]. Xorg's design predates modern security practices and is [https://security.stackexchange.com/questions/4641/why-are-people-saying-that-the-x-window-system-is-not-secure/4646#4646 considered insecure] by many. For example, Xorg applications may record keystrokes while inactive.

If you must run Xorg, it is recommended to [[Xorg#Rootless Xorg|avoid running it as root]]. Within Wayland, the Xwayland compatibility layer will automatically use rootless Xorg.

== Restricting root ==

The root user is, by definition, the most powerful user on a system. It is also difficult to [[audit]] the root user account. It is therefore important to restrict usage of the root user account as much as possible. There are a number of ways to keep the power of the root user while limiting its ability to cause harm.

=== Use sudo instead of su ===

Using [[sudo]] for privileged access is preferable to [[su]] for a number of reasons:

* It keeps a log of which normal privilege user has run each privileged command.
* The root user password need not be given out to each user who requires root access.
* {{ic|sudo}} prevents users from accidentally running commands as ''root'' that do not need root access, because a full root terminal is not created. This aligns with the [[Wikipedia:Principle of least privilege|principle of least privilege]].
* Individual programs may be enabled per user, instead of offering complete root access just to run one command.

See [[Sudo#Configuration]].

==== Editing files using sudo ====

See [[Sudo#Editing files]]. Alternatively, you can use editors like {{ic|rvim}} or {{ic|rnano}} which have restricted capabilities in order to be safe to run as root.

=== Restricting root login ===

Once [[sudo]] is properly configured, full root access can be heavily restricted or denied without losing much usability. To disable root, but still allowing to use [[sudo]], you can use {{man|1|passwd}} with {{ic|passwd --lock root}}.

==== Allow only certain users ====

The [[PAM]] {{ic|pam_wheel.so}} lets you allow only users in the group {{ic|wheel}} to login using [[su]]. See [[su#su and wheel]].

==== Denying SSH login ====

Even if you do not wish to deny root login for local users, it is always good practice to [[OpenSSH#Deny|deny root login via SSH]]. The purpose of this is to add an additional layer of security before a user can completely compromise your system remotely.

==== Specify acceptable login combinations with access.conf ====

{{Warning|If you are using GNOME 49 or later, you should make sure the group ''gdm'' can log in locally. This can be done with a {{ic|+:(gdm):LOCAL}} rule. [https://gitlab.gnome.org/GNOME/gdm/-/issues/1021]}}

When someone attempts to log in with [[PAM]], {{ic|/etc/security/access.conf}} is checked for the first combination that matches their login properties. Their attempt then fails or succeeds based on the rule for that combination.

+:root:LOCAL
-:root:ALL

Rules can be set for specific groups and users. In this example, the user archie is allowed to login locally, as are all users in the wheel and adm groups. All other logins are rejected:

+:archie:LOCAL
+:(wheel):LOCAL
+:(adm):LOCAL
-:ALL:ALL

Read more at {{man|5|access.conf}}

== Mandatory access control ==

[[Wikipedia:Mandatory Access Control|Mandatory access control]] (MAC) is a type of security policy that differs significantly from the [[Wikipedia:Discretionary Access Control|discretionary access control]] (DAC) used by default in Arch and most Linux distributions. MAC essentially means that every action a program could perform that affects the system in any way is checked against a security ruleset. This ruleset, in contrast to DAC methods, cannot be modified by users. Using virtually any mandatory access control system will significantly improve the security of your computer, although there are differences in how it can be implemented.

=== Pathname MAC ===

Pathname-based access control is a simple form of access control that offers permissions based on the path of a given file. The downside to this style of access control is that permissions are not carried with files if they are moved around the system. On the positive side, pathname-based MAC can be implemented on a much wider range of filesystems, unlike labels-based alternatives.

* [[AppArmor]] is a [[Wikipedia:Canonical (company)|Canonical]]-maintained MAC implementation seen as an "easier" alternative to SELinux.
* [[TOMOYO]] is another simple, easy-to-use system offering mandatory access control. It is designed to be both simple in usage and in implementation, requiring very few dependencies.

=== Labels MAC ===

Labels-based access control means the extended attributes of a file are used to govern its security permissions. While this system is arguably more flexible in its security offerings than pathname-based MAC, it only works on filesystems that support these extended attributes.

* [[SELinux]], based on an [[Wikipedia:NSA|NSA]] project to improve Linux security, implements MAC completely separate from system users and roles. It offers an extremely robust multi-level MAC policy implementation that can easily maintain control of a system that grows and changes past its original configuration.

=== Access Control Lists ===

[[Access Control Lists]] (ACLs) are an alternative to attaching rules directly to the filesystem in some way. ACLs implement access control by checking program actions against a list of permitted behavior.

== Kernel hardening ==

=== Kernel self-protection / exploit mitigation ===

The {{pkg|linux-hardened}} package uses a [https://github.com/anthraxx/linux-hardened basic kernel hardening patch set] and more security-focused compile-time configuration options than the {{pkg|linux}} package. A custom build can be made to choose a different compromise between security and performance than the security-leaning defaults.

However, it should be noted that several packages (such as {{pkg|throttled}}) will not work when using this kernel.

If you use an out-of-tree driver such as [[NVIDIA]], you may need to switch to its [[DKMS]] package.

==== Userspace ASLR comparison ====

The {{pkg|linux-hardened}} package provides an improved implementation of Address Space Layout Randomization for userspace processes. The {{pkg|paxtest}} command can be used to obtain an estimate of the provided entropy:

===== 64-bit processes =====

{{hc|linux-hardened 5.4.21.a-1-hardened|
Anonymous mapping randomization test : 32 quality bits (guessed)
Heap randomization test (ET_EXEC) : 40 quality bits (guessed)
Heap randomization test (PIE) : 40 quality bits (guessed)
Main executable randomization (ET_EXEC) : 32 quality bits (guessed)
Main executable randomization (PIE) : 32 quality bits (guessed)
Shared library randomization test : 32 quality bits (guessed)
VDSO randomization test : 32 quality bits (guessed)
Stack randomization test (SEGMEXEC) : 40 quality bits (guessed)
Stack randomization test (PAGEEXEC) : 40 quality bits (guessed)
Arg/env randomization test (SEGMEXEC) : 44 quality bits (guessed)
Arg/env randomization test (PAGEEXEC) : 44 quality bits (guessed)
Offset to library randomisation (ET_EXEC): 34 quality bits (guessed)
Offset to library randomisation (ET_DYN) : 34 quality bits (guessed)
Randomization under memory exhaustion @~0: 32 bits (guessed)
Randomization under memory exhaustion @0 : 32 bits (guessed)
}}

{{hc|linux 5.5.5-arch1-1|
Anonymous mapping randomization test : 28 quality bits (guessed)
Heap randomization test (ET_EXEC) : 28 quality bits (guessed)
Heap randomization test (PIE) : 28 quality bits (guessed)
Main executable randomization (ET_EXEC) : 28 quality bits (guessed)
Main executable randomization (PIE) : 28 quality bits (guessed)
Shared library randomization test : 28 quality bits (guessed)
VDSO randomization test : 20 quality bits (guessed)
Stack randomization test (SEGMEXEC) : 30 quality bits (guessed)
Stack randomization test (PAGEEXEC) : 30 quality bits (guessed)
Arg/env randomization test (SEGMEXEC) : 22 quality bits (guessed)
Arg/env randomization test (PAGEEXEC) : 22 quality bits (guessed)
Offset to library randomisation (ET_EXEC): 28 quality bits (guessed)
Offset to library randomisation (ET_DYN) : 28 quality bits (guessed)
Randomization under memory exhaustion @~0: 29 bits (guessed)
Randomization under memory exhaustion @0 : 29 bits (guessed)
}}

{{hc|linux-lts 4.19.101-1-lts|
Anonymous mapping randomization test : 28 quality bits (guessed)
Heap randomization test (ET_EXEC) : 28 quality bits (guessed)
Heap randomization test (PIE) : 28 quality bits (guessed)
Main executable randomization (ET_EXEC) : 28 quality bits (guessed)
Main executable randomization (PIE) : 28 quality bits (guessed)
Shared library randomization test : 28 quality bits (guessed)
VDSO randomization test : 19 quality bits (guessed)
Stack randomization test (SEGMEXEC) : 30 quality bits (guessed)
Stack randomization test (PAGEEXEC) : 30 quality bits (guessed)
Arg/env randomization test (SEGMEXEC) : 22 quality bits (guessed)
Arg/env randomization test (PAGEEXEC) : 22 quality bits (guessed)
Offset to library randomisation (ET_EXEC): 28 quality bits (guessed)
Offset to library randomisation (ET_DYN) : 28 quality bits (guessed)
Randomization under memory exhaustion @~0: 28 bits (guessed)
Randomization under memory exhaustion @0 : 28 bits (guessed)
}}

===== 32-bit processes (on an x86_64 kernel) =====

{{hc|linux-hardened|
Anonymous mapping randomization test : 16 quality bits (guessed)
Heap randomization test (ET_EXEC) : 22 quality bits (guessed)
Heap randomization test (PIE) : 27 quality bits (guessed)
Main executable randomization (ET_EXEC) : No randomization
Main executable randomization (PIE) : 18 quality bits (guessed)
Shared library randomization test : 16 quality bits (guessed)
VDSO randomization test : 16 quality bits (guessed)
Stack randomization test (SEGMEXEC) : 24 quality bits (guessed)
Stack randomization test (PAGEEXEC) : 24 quality bits (guessed)
Arg/env randomization test (SEGMEXEC) : 28 quality bits (guessed)
Arg/env randomization test (PAGEEXEC) : 28 quality bits (guessed)
Offset to library randomisation (ET_EXEC): 18 quality bits (guessed)
Offset to library randomisation (ET_DYN) : 16 quality bits (guessed)
Randomization under memory exhaustion @~0: 18 bits (guessed)
Randomization under memory exhaustion @0 : 18 bits (guessed)
}}

{{hc|linux|
Anonymous mapping randomization test : 8 quality bits (guessed)
Heap randomization test (ET_EXEC) : 13 quality bits (guessed)
Heap randomization test (PIE) : 13 quality bits (guessed)
Main executable randomization (ET_EXEC) : No randomization
Main executable randomization (PIE) : 8 quality bits (guessed)
Shared library randomization test : 8 quality bits (guessed)
VDSO randomization test : 8 quality bits (guessed)
Stack randomization test (SEGMEXEC) : 19 quality bits (guessed)
Stack randomization test (PAGEEXEC) : 19 quality bits (guessed)
Arg/env randomization test (SEGMEXEC) : 11 quality bits (guessed)
Arg/env randomization test (PAGEEXEC) : 11 quality bits (guessed)
Offset to library randomisation (ET_EXEC): 8 quality bits (guessed)
Offset to library randomisation (ET_DYN) : 13 quality bits (guessed)
Randomization under memory exhaustion @~0: No randomization
Randomization under memory exhaustion @0 : No randomization
}}

=== Restricting access to kernel pointers in the proc filesystem ===

Setting {{ic|kernel.kptr_restrict}} to 1 will hide kernel symbol addresses in {{ic|/proc/kallsyms}} from regular users without {{ic|CAP_SYSLOG}}, making it more difficult for kernel exploits to resolve addresses/symbols dynamically. This will not help that much on a pre-compiled Arch Linux kernel, since a determined attacker could just download the kernel package and get the symbols manually from there, but if you are compiling your own kernel, this can help mitigating local root exploits. This will break some {{Pkg|perf}} commands when used by non-root users (but many {{Pkg|perf}} features require root access anyway). See {{Bug|34323}} for more information.

Setting {{ic|kernel.kptr_restrict}} to 2 will hide kernel symbol addresses in {{ic|/proc/kallsyms}} regardless of privileges.

{{hc|/etc/sysctl.d/51-kptr-restrict.conf|2=
kernel.kptr_restrict = 1
}}

{{Note|{{pkg|linux-hardened}} sets {{ic|1=kptr_restrict=2}} by default rather than {{ic|0}}.}}

=== BPF hardening ===

BPF is a system used to load and execute bytecode within the kernel dynamically during runtime. It is used in a number of Linux kernel subsystems such as networking (e.g. XDP, tc), tracing (e.g. kprobes, uprobes, tracepoints) and security (e.g. seccomp). It is also useful for advanced network security, performance profiling and dynamic tracing.

BPF was originally an acronym of [[Wikipedia:Berkeley Packet Filter|Berkeley Packet Filter]] since the original classic BPF was used for packet capture tools for BSD. This eventually evolved into Extended BPF (eBPF), which was shortly afterwards renamed to just BPF (not an acronym). BPF should not be confused with packet filtering tools like iptables or netfilter, although BPF can be used to implement packet filtering tools.

BPF code may be either interpreted or compiled using a [[Wikipedia:Just-in-time compilation|Just-In-Time (JIT) compiler]]. The Arch kernel is built with {{ic|CONFIG_BPF_JIT_ALWAYS_ON}} which disables the BPF interpreter and forces all BPF to use JIT compilation. This makes it harder for an attacker to use BPF to escalate attacks that exploit SPECTRE-style vulnerabilities. See [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=290af86629b25ffd1ed6232c4e9107da031705cb the kernel patch which introduced CONFIG_BPF_JIT_ALWAYS_ON] for more details.

The kernel includes a hardening feature for JIT-compiled BPF which can mitigate some types of JIT spraying attacks at the cost of performance and the ability to trace and debug many BPF programs. It may be enabled by setting {{ic|net.core.bpf_jit_harden}} to {{ic|1}} (to enable hardening of unprivileged code) or {{ic|2}} (to enable hardening of all code).

See the {{ic|net.core.bpf_*}} settings in the [https://docs.kernel.org/admin-guide/sysctl/net.html kernel documentation] for more details.

{{Tip|
* {{Pkg|linux-hardened}} sets {{ic|1=net.core.bpf_jit_harden=2}} by default rather than {{ic|0}}.
* By default, BPF programs can be run even by unprivileged users. To change that behaviour set {{ic|1=kernel.unprivileged_bpf_disabled=1}}[https://access.redhat.com/security/cve/cve-2021-33624].
}}

=== ptrace scope ===

The {{man|2|ptrace}} syscall provides a means by which one process (the "tracer") may observe and control the execution of another process (the "tracee"), and examine and change the tracee's memory and registers. {{ic|ptrace}} is commonly used by debugging tools including ''gdb'', ''strace'', ''perf'', ''reptyr'' and other debuggers. However, it also provides a means by which a malicious process can read data from and take control of other processes.

Arch enables the [https://docs.kernel.org/admin-guide/LSM/Yama.html Yama LSM] by default, which provides a {{ic|kernel.yama.ptrace_scope}} [[kernel parameter]]. This parameter is set to {{ic|1}} (restricted) by default which prevents tracers from performing a {{ic|ptrace}} call on traces outside of a restricted scope unless the tracer is privileged or has the {{ic|CAP_SYS_PTRACE}} [[Capabilities|capability]]. This is a significant improvement in security compared to the classic permissions. Without this module, there is no separation between processes running as the same user (in the absence of additional security layers such as {{man|7|pid_namespaces}}).

{{Note|By default, you can still use tools which require {{ic|ptrace}} by running them as privileged processes, e.g. using [[sudo]].}}

If you do not need to use debugging tools, consider setting {{ic|kernel.yama.ptrace_scope}} to {{ic|2}} (admin-only) or {{ic|3}} (no {{ic|ptrace}} possible) to harden the system.

{{Note|Some anti-cheat and DRM implementations rely on {{ic|ptrace}} to work, including Easy Anti-Cheat and Ubisoft Connect under Wine. Setting this parameter to {{ic|2}} or higher might prevent games using these solutions from launching.}}

=== hidepid ===

{{Expansion|1=[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0fb5ce62c5920b6e0a8a061f2fe80e0403281e10 Linux 5.8 implemented private instances] and new values for {{ic|1=hidepid=}}.}}

{{Accuracy|Enabling {{ic|hidepid}} globally is not a supported way of operation by [[systemd]], nor does it have any practical improvements security-wise when systemd is running as service manager. [https://github.com/systemd/systemd/issues/29893#issuecomment-1798030108]}}

{{Warning|
* This may cause issues for certain applications like an application running in a sandbox and [[Xorg]] (see workaround).
* This causes issues with [[D-Bus]], [[Polkit]], [[PulseAudio]] and [[bluetooth]] when using {{Pkg|systemd}} > 237.64-1.
}}

The kernel has the ability to hide other users' processes, normally accessible via {{ic|/proc}}, from unprivileged users by mounting the {{ic|proc}} filesystem with the {{ic|1=hidepid=}} and {{ic|1=gid=}} options documented in https://docs.kernel.org/filesystems/proc.html.

This greatly complicates an intruder's task of gathering information about running processes, whether some daemon runs with elevated privileges, whether other user runs some sensitive program, whether other users run any program at all, makes it impossible to learn whether any user runs a specific program (given the program does not reveal itself by its behaviour), and, as an additional bonus, poorly written programs passing sensitive information via program arguments are now protected against local eavesdroppers.

The {{ic|proc}} [[Users and groups#System groups|group]], provided by the {{Pkg|filesystem}} package, acts as a whitelist of users authorized to learn other users' process information. If users or services need access to {{ic|/proc/<pid>}} directories beyond their own, [[Users and groups#Group management|add them to the group]].

For example, to hide process information from other users except those in the {{ic|proc}} group:

{{hc|/etc/fstab|2=
proc /proc proc nosuid,nodev,noexec,hidepid=2,gid=proc 0 0
}}

For user sessions to work correctly, an exception needs to be added for ''systemd-logind'':

{{hc|/etc/systemd/system/systemd-logind.service.d/hidepid.conf|2=
[Service]
SupplementaryGroups=proc
}}

=== Restricting module loading ===

The default Arch kernel has {{ic|CONFIG_MODULE_SIG_ALL}} enabled, which signs all kernel modules built as part of the {{Pkg|linux}} package. This allows the kernel to only load modules signed with a valid key, i.e. out-of-tree modules compiled locally or provided by packages such as {{Pkg|virtualbox-host-modules-arch}} cannot be loaded. You can use {{ic|1=modinfo}} to verify currently loaded modules have signatures; verifying the signatures by hand is slightly more involved [https://unix.stackexchange.com/a/496800].

Kernel module loading can be restricted by setting the {{ic|1=module.sig_enforce=1}} [[kernel parameter]]. More information can be found in the [https://docs.kernel.org/admin-guide/module-signing.html kernel documentation].

Further, unneeded individual modules can be [[blacklist]]ed, see [https://github.com/secureblue/secureblue/blob/live/files/system/usr/lib/modprobe.d/secureblue.conf secureblue] for examples.

=== Disable kexec ===

Kexec allows replacing the current running kernel.

{{hc|/etc/sysctl.d/51-kexec-restrict.conf|2=
kernel.kexec_load_disabled = 1
}}

{{Tip|kexec is disabled by default in {{pkg|linux-hardened}}.}}

=== Kernel lockdown mode ===

Since Linux 5.4 the kernel [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aefcf2f4b58155d27340ba5f9ddbe9513da8286d has gained] an optional [https://mjg59.dreamwidth.org/55105.html lockdown feature], intended to strengthen the boundary between UID 0 (root) and the kernel. When enabled some applications may cease to work which rely on low-level access to either hardware or the kernel.

To use lockdown, its LSM must be initialized and a lockdown mode must be set.

All [[Kernel#Officially supported kernels|officially supported kernels]] initialize the LSM, but none of them enforce any lockdown mode.

{{Tip|Initialized LSMs can be verified by running {{ic|cat /sys/kernel/security/lsm}}.}}

Lockdown has two modes of operation:

* {{ic|integrity}}: kernel features that allow userland to modify the running kernel are disabled (e.g. kexec, bpf).
* {{ic|confidentiality}}: kernel features that allow userland to extract confidential information from the kernel are also disabled.

It is recommended to use {{ic|integrity}}, unless your specific threat model dictates otherwise.

To enable kernel lockdown at runtime, run:

# echo ''mode'' > /sys/kernel/security/lockdown

To enable kernel lockdown on boot, use the [[kernel parameter]] {{ic|1=lockdown=''mode''}}.

{{Note|
* Kernel lockdown cannot be disabled at runtime.
* Kernel lockdown disables [[hibernation]].
* Versions <6.17 of the {{man|7|kernel_lockdown}} man page incorrectly state that "lockdown will be automatically enabled if the system boots in EFI Secure Boot mode". This is not the behaviour of the upstream kernel, nor Arch's packaged [[kernel]]s.
}}

See also {{man|7|kernel_lockdown}}.

=== Linux Kernel Runtime Guard (LKRG) ===

[https://www.openwall.com/lkrg/ LKRG] ({{AUR|lkrg-dkms}}) is a kernel module which performs integrity checking of the kernel and detection of exploit attempts.

=== Disable emergency shell ===

{{Accuracy|Masking {{ic|emergency.target}} and {{ic|emergency.service}} will have no effect on those units being added to the initramfs and run in early userspace. Even with them in the initramfs, mkinitcpio's systemd hook locks the root account[https://gitlab.archlinux.org/archlinux/packaging/packages/systemd/-/commit/292cdf8a2f7dd7c6c7d91d2b59617391935c837c][https://gitlab.archlinux.org/archlinux/packaging/packages/systemd/-/commit/8835b2f5dfbe8663f1a2fd08edbd35f90bf08691] for "security reasons" (see {{Bug|70408}}). The solution for the issue in the linked article, if even needed, would be to prevent {{ic|rescue.target}}, {{ic|rescue.service}}, {{ic|emergency.target}} and {{ic|emergency.service}} from being added to the initramfs image.}}

The emergency shell is used to interactively troubleshoot the machine during the boot process. However, it is also a gadget that an attacker can use to access secure resources such as the TPM. See [https://pulsesecurity.co.nz/advisories/tpm-luks-bypass this article] for a practical example. The difficulty of attacks can be increased by disabling the emergency shell, at the tradeoff of removing a tool to troubleshoot early boot failures.

To disable the emergency shell, See [[systemd#Disable emergency mode on remote machine]].

== Sandboxing applications ==

See also [[Wikipedia:Sandbox (computer security)]].

To improve the security of systemd service units, see [[systemd/Sandboxing]].

{{Warning|Unprivileged user namespace usage ({{ic|CONFIG_USER_NS_UNPRIVILEGED}}) is enabled by default in {{Pkg|linux}}, {{Pkg|linux-lts}} and {{Pkg|linux-zen}}, which greatly increases the attack surface for local privilege escalation (see [https://gitlab.com/apparmor/apparmor/-/wikis/unprivileged_userns_restriction AppArmor's Wiki] and {{Bug|36969}}).}}

To mitigate this, either:

* use the {{Pkg|linux-hardened}} kernel which has the safe default, or
* set the {{ic|kernel.unprivileged_userns_clone}} [[sysctl]] to {{ic|0}}.

Note that this can break applications such as {{pkg|nsjail}}. [[Chromium]] based applications need SUID bit for {{ic|chrome-sandbox}} to work with this setting.

Of all the officially supported kernels, only {{Pkg|linux-hardened}} disables user namespaces for unprivilegied users. In order to efficiently sandbox applications without requiring root privilegies it is advisable to set {{ic|kernel.unprivileged_userns_clone}} to {{ic|1}}.

=== Firejail ===

[[Firejail]] is an easy to use tool for sandboxing applications and servers alike. It was originally created for browsers and internet facing applications, but supports a large number of applications by now. To establish a sandboxed environment with a variety of features, it is installed as a suid binary and builds a sandboxed runtime environment for the target application based on black and white lists.

=== bubblewrap ===

[[bubblewrap]] is a sandbox application developed for unprivileged container tools like [[Flatpak]] with a significantly smaller resource footprint and complexity than Firejail. While it lacks certain features such as file path whitelisting, bubblewrap does offer bind mounts as well as the creation of user/IPC/PID/network/cgroup namespaces and can support both simple and complex sandboxes. For the {{Pkg|linux-hardened}} kernel you will need to to use {{Pkg|bubblewrap-suid}}.

[[Bubblejail]] sandbox is based on [[bubblewrap]] and provides a resource oriented permission model with a graphical interface to tweak permissions.

=== Portable ===

[https://github.com/Kraftland/portable Portable] is a sandboxing framework which utilizes [[bubblewrap]] and many other tools to lockdown running applications. It is designed to be simple for packagers and efficient for users, yet cuts off security holes and monitors background processes by default.

See [https://github.com/Kraftland/portable-arch portable-arch] for a repository of applications sandboxed by portable.

If a sandboxed application does not utilize the Portal file chooser, portable can pass files to the sandbox (by passing {{ic|--actions share-files}}).

Portable is fully functional on GNOME, while other desktops may lack small amounts of features like advanced background monitoring and ScreenShot portal.

=== chroots ===

Manual [[chroot]] jails can also be constructed to build sandboxed process environments. It is much more limited than other sandboxing technologies; the extent of its sandboxing is file path isolation.

=== Linux containers ===

[[Linux Containers]] are another good option when you need more separation than the other options (short of [[#Full virtualization options|full system virtualization]]) provide. LXC is run on top of the existing kernel in a pseudo-chroot with their own virtual hardware.

=== gVisor ===

The [https://gvisor.dev/ gVisor] project, led by Google, is providing a sandboxing application with a focus on containers following the [https://opencontainers.org/ OCI initiative], such as [[Docker]] and [[Kubernetes]]. It isolates containers and individual applications from the host by intercepting a majority of system calls to the kernel and presenting itself as guest kernel.

A key difference to other intercepting sandboxing projects is that gVisor re-implements system calls in the Go programming language, as described in its [https://gvisor.dev/docs/architecture_guide/intro/ design overview]. Details for the list of [https://gvisor.dev/docs/user_guide/compatibility/linux/amd64/ re-implemented syscalls support] can be seen in [https://github.com/google/gvisor/blob/master/pkg/sentry/syscalls/linux/linux64.go git]. For usage examples, limitations and special features see the project [https://gvisor.dev/docs/ documentation].

The application is available as {{Aur|gvisor-git}} and {{Aur|gvisor-bin}}.

=== Full virtualization options ===

Using full virtualization options such as [[VirtualBox]], [[KVM]], [[Xen]] or [https://www.qubes-os.org/ Qubes OS] (based on Xen) can also improve isolation and security in the event you plan on running risky applications or browsing dangerous websites.

== Network and firewalls ==

=== Firewalls ===

While the stock Arch kernel is capable of using [[Wikipedia:Netfilter|Netfilter]]'s [[iptables]] and [[nftables]], the services are not [[enable]]d by default. It is highly recommended to set up some form of firewall to protect the services running on the system. Many resources (including ArchWiki) do not state explicitly which services are worth protecting, so enabling a firewall is a good precaution.

* See [[iptables]] and [[nftables]] for general information.
* See [[Simple stateful firewall]] for a guide on setting up an iptables firewall.
* See [[:Category:Firewalls]] for other ways of setting up netfilter.
* See [[Ipset]] for blocking lists of ip addresses, such as those from Bluetack.
* {{Pkg|opensnitch}} is a configurable inbound and outbound firewall with support for configurable rules by application, port, host, etc.

A quick way to setup a basic firewall is to use the tool {{ic|ufw}} (Uncomplicated Fire Wall). Then set {{ic|ufw default deny incoming}} and {{ic|ufw default allow outgoing}} and enabling it with {{ic|ufw enable}} and {{ic|systemctl enable ufw}}.

==== Open ports ====

{{Style|"Open ports" is not a good title since it disregards interfaces and addresses that the application may be bound to. From the firewalls' point of view, ports may be "open" even if no application listens on them at the moment.}}

Some services listen for inbound traffic on open network ports. It is important to only bind these services to the addresses and interfaces that are strictly necessary. It may be possible for a remote attacker to [https://samy.pl/slipstream/ exploit flawed network protocols to access exposed services]. This can even happen with [https://nvd.nist.gov/vuln/detail/CVE-2019-13450 processes bound to localhost].

In general, if a service only needs to be accessible to the local system, bind to a Unix domain socket ({{man|7|unix}}) or a loopback address such as {{ic|localhost}} instead of a non-loopback address like {{ic|0.0.0.0/0}}.

If a service needs to be accessible to other systems via the network, control the access with strict [[firewall]] rules and configure authentication, authorization and encryption whenever possible.

You can list all current open ports with {{ic|ss -l}}. To show all '''l'''istening '''p'''rocesses and their '''n'''umeric '''t'''cp and '''u'''dp port numbers:

# ss -lpntu

See {{man|8|ss}} for more options.

=== Kernel parameters ===

Kernel parameters which affect networking can be set using [[Sysctl]]. For how to do this, see [[Sysctl#TCP/IP stack hardening]].

=== SSH ===

To mitigate [[Wikipedia:Brute-force attack|brute-force attacks]] it is recommended to enforce key-based authentication. For OpenSSH see [[OpenSSH#Protection]] for more recommendations. Alternatively [[Fail2ban]] or [[Sshguard]] offer lesser forms of protection by monitoring logs and writing [[firewall]] rules but open up the potential for a denial of service, since an attacker can [[Wikipedia:Spoofing attack#Spoofing and TCP/IP|spoof]] packets as if they came from the administrator after identifying their address. Spoofing IP has lines of defense, such as by [[sysctl#Reverse path filtering|reverse path filtering]] and [[sysctl#Disable ICMP redirects|disabling ICMP redirects]].

You may want to harden authentication even more by using two-factor authentication. [[Google Authenticator]] provides a two-step authentication procedure using one-time passcodes (OTP).

Denying root login is also a good practice, both for tracing intrusions and adding an additional layer of security before root access. For OpenSSH, see [[OpenSSH#Deny]].

Mozilla publishes an [https://infosec.mozilla.org/guidelines/openssh.html OpenSSH configuration guide] which configures more verbose audit logging and restricts ciphers.

=== DNS ===

The default domain name resolution (DNS) configuration is highly compatible but has security weaknesses. See [[Domain name resolution#Privacy and security|DNS privacy and security]] for more information.

=== Proxies ===

Proxies are commonly used as an extra layer between applications and the network, sanitizing data from untrusted sources. The attack surface of a small proxy running with lower privileges is significantly smaller than a complex application running with the end user privileges.

For example the DNS resolver is implemented in {{Pkg|glibc}}, that is linked with the application (that may be running as root), so a bug in the DNS resolver might lead to a remote code execution. This can be prevented by installing a DNS caching server, such as [[dnsmasq]], which acts as a proxy. [https://googleonlinesecurity.blogspot.it/2016/02/cve-2015-7547-glibc-getaddrinfo-stack.html]

=== Managing TLS certificates ===

See [[TLS#Trust management]].

== Physical security ==

Physical access to a computer is root access given enough time and resources. However, a high ''practical'' level of security can be obtained by putting up enough barriers.

An attacker can gain full control of your computer on the next boot by simply attaching a malicious IEEE 1394 (FireWire), Thunderbolt or PCI Express device as they are given full memory access by default.[https://web.archive.org/web/20210312083421/http://breaknenter.org/2014/09/inception-metasploit-integration/] For Thunderbolt, you can restrict the direct memory access completely or to known devices, see [[Thunderbolt#User device authorization|user device authorization]]. For Firewire and PCI Express, there is little you can do from preventing this, or modification of the hardware itself - such as flashing malicious firmware onto a drive. However, the vast majority of attackers will not be this knowledgeable and determined.

[[#Data-at-rest encryption|Data-at-rest encryption]] will prevent access to your data if the computer is stolen, but malicious firmware can be installed to obtain this data upon your next log in by a resourceful attacker.

=== Locking down BIOS ===

Adding a password to the BIOS prevents someone from booting into removable media, which is basically the same as having root access to your computer. You should make sure your drive is first in the boot order and disable the other drives from being bootable if you can.

=== Boot loaders ===

It is highly important to protect your [[boot loader]]. An unprotected boot loader can bypass any login restrictions, e.g. by setting the {{ic|1=init=/bin/sh}} [[kernel parameter]] to boot directly to a shell.

==== Syslinux ====

[[Syslinux]] supports [[Syslinux#Security|password-protecting your boot loader]]. It allows you to set either a per-menu-item password or a global boot loader password.

==== GRUB ====

[[GRUB]] supports boot loader passwords as well. See [[GRUB/Tips and tricks#Password protection of GRUB menu]] for details. It also has support for [[GRUB#Encrypted /boot|encrypted /boot]], which only leaves some parts of the boot loader code unencrypted. GRUB's configuration, [[kernel]] and [[initramfs]] are encrypted.

==== systemd-boot ====

[[systemd-boot]] disables editing of kernel parameters when [[#Secure Boot|Secure Boot]] is enabled. Alternatively, you can set [[systemd-boot#Kernel parameters editor with password protection|kernel parameters for password protection]] in systemd-boot for a more traditional password-based option.

=== Secure Boot ===

[[Secure Boot]] is a feature of [[UEFI]] that allows authentication of the files your computer boots. This helps preventing some [[Wikipedia:Evil maid attack|evil maid attacks]] such as replacing files inside the boot partition. Normally computers come with keys that are enrolled by vendors (OEM). However these can be removed and allow the computer to enter ''Setup Mode'' which allows the user to enroll and manage their own keys.

The secure boot page guides you through how to set secure boot up by [[Unified Extensible Firmware Interface/Secure Boot#Using your own keys|using your own keys]].

=== Trusted Platform Module (TPM) ===

[[Trusted Platform Module|TPMs]] are hardware microprocessors which have cryptographic keys embedded. This forms the fundamental root of trust of most modern computers and allows end-to-end verification of the boot chain. They can be used as internal smartcards, attest the firmware running on the computer and allow users to insert secrets into a tamper-proof and brute-force resistant store.

=== Boot partition on removable flash drive ===

One popular idea is to place the boot partition on a flash drive in order to render the system unbootable without it. Proponents of this idea often use [[#Data-at-rest encryption|full-disk encryption]] alongside, and some also use [[Dm-crypt/Specialties#Encrypted system using a detached LUKS header|detached encryption headers]] placed on the boot partition.

This method can also be merged with [[Dm-crypt/Specialties#Encrypted /boot and a detached LUKS header on USB|encrypting /boot]].

=== Automatic logout ===

If you are using [[Bash]] or [[Zsh]], you can set {{ic|TMOUT}} for an automatic logout from shells after a timeout.

For example, the following will automatically log out from virtual consoles (but not terminal emulators in X11):

{{hc|/etc/profile.d/shell-timeout.sh|<nowiki>
TMOUT="$(( 60*10 ))";
[ -z "$DISPLAY" ] && export TMOUT;
case $( /usr/bin/tty ) in
/dev/tty[0-9]*) export TMOUT;;
esac
</nowiki>}}

If you really want EVERY Bash/Zsh prompt (even within X) to timeout, use:

$ export TMOUT="$(( 60*10 ))";

Note that this will not work if there is some command running in the shell (eg.: an SSH session or other shell without {{ic|TMOUT}} support). But if you are using VC mostly for restarting frozen GDM/Xorg as root, then this is very useful.

=== Protect against rogue USB devices ===

The kernel has [https://docs.kernel.org/usb/authorization.html settings to deactivate] USB ports to protect your computer against rogue USB devices (a.k.a. [[Wikipedia:BadUSB|BadUSB]], [https://github.com/samyk/poisontap PoisonTap] or [https://lanturtle.com/ LanTurtle]). They can be set at runtime and automated via [[sysctl]].

For more control install [[USBGuard]], which is a software framework implementing basic whitelisting and blacklisting capabilities based on device attributes.

=== Volatile data collection ===

A computer that is powered on may be vulnerable to [https://web.archive.org/web/20210420075636/https://fedvte.usalearning.gov/courses/CSI/course/videos/pdf/CSI_D01_S05_T01_STEP.pdf volatile data collection]. It is a best practice to turn a computer completely off at times it is not necessary for it to be on, or if the computer's physical security is temporarily compromised (e.g. when passing through a security checkpoint).

== Packages ==

=== Authentication ===

[https://www2.cs.arizona.edu/stork/packagemanagersecurity/attacks-on-package-managers.html#overview Attacks on package managers] are possible without proper use of package signing, and can affect even package managers with [https://www2.cs.arizona.edu/stork/packagemanagersecurity/faq.html proper signature systems]. Arch uses package signing by default and relies on a web of trust from 5 trusted master keys. See [[Pacman-key]] for details.

=== Upgrades ===

It is important to regularly [[System maintenance#Upgrading the system|upgrade the system]].

=== Follow vulnerability alerts ===

Subscribe to the Common Vulnerabilities and Exposure (CVE) Security Alert updates, made available by National Vulnerability Database, and found on the [https://nvd.nist.gov/download.cfm NVD Download webpage].

The tool {{Pkg|arch-audit}} can be used to check for vulnerabilities affecting the running system. A graphical system tray, {{Pkg|arch-audit-gtk}}, can also be used. See also [[Arch Security Team]].

You should also consider subscribing to the release notifications for software you use, especially if you install software through means other than the main repositories or AUR. Some software have mailing lists you can subscribe to for security notifications. Source code hosting sites often offer RSS feeds for new releases.

=== Rebuilding packages ===

Packages can be rebuilt and stripped of undesired functions and features as a means to reduce attack surface. For example, {{Pkg|bzip2}} can be rebuilt without {{ic|bzip2recover}} in an attempt to circumvent [https://security.archlinux.org/CVE-2016-3189 CVE-2016-3189]. Custom hardening flags can also be applied either manually or via a wrapper.

{{Merge|Arch package guidelines/Security|Security related build flags have their own article.}}

{{Accuracy|Copy-pasted from a 3 years old blog post. The compiler flags are specific to [[GCC]], some are hardly security related.}}

{| class="wikitable"
! Flag !! Purpose
|-
| -D_FORTIFY_SOURCE=2 || Run-time buffer overflow detection
|-
| -D_GLIBCXX_ASSERTIONS || Run-time bounds checking for C++ strings and containers
|-
| -fasynchronous-unwind-tables || Increased reliability of backtraces
|-
| -fexceptions || Enable table-based thread cancellation
|-
| -fpie -Wl,-pie || Full ASLR for executables
|-
| -fpic -shared || No text relocations for shared libraries
|-
| -fplugin=annobin || Generate data for hardening quality control
|-
| -fstack-clash-protection || Increased reliability of stack overflow detection
|-
| -fstack-protector, -fstack-protector-all or -fstack-protector-strong || Stack smashing protector
|-
| -grecord-gcc-switches || Store compiler flags in debugging information
|-
| -mcet -fcf-protection || Control flow integrity protection
|-
| -Werror=format-security || Reject potentially unsafe format string arguments
|-
| -Werror=implicit-function-declaration || Reject missing function prototypes
|-
| -Wl,-z,defs || Detect and reject underlinking
|-
| -Wl,-z,now || Disable lazy binding
|-
| -Wl,-z,relro || Read-only segments after relocation
|}

* [https://developers.redhat.com/blog/2018/03/21/compiler-and-linker-flags-gcc/ Flags and info source]

== See also ==

* [https://security.archlinux.org/ Arch Linux Security Tracker]
* [https://wiki.centos.org/HowTos/OS_Protection CentOS Wiki: OS Protection]
* [https://web.archive.org/web/20210712001756/https://developer.ibm.com/technologies/linux/articles/l-harden-desktop/ Hardening the Linux desktop]
* [https://web.archive.org/web/20190701140035/https://www.ibm.com/developerworks/linux/tutorials/l-harden-server/index.html Hardening the Linux server]
* [https://github.com/lfit/itpol/blob/master/linux-workstation-security.md Linux Foundation: Linux workstation security checklist]
* [https://www.privacyguides.org/ privacyguides.org Privacy Resources]
* [https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Security_Guide/ Red Hat Enterprise Linux 7 Security Guide]
* [https://www.debian.org/doc/manuals/securing-debian-manual/index.en.html Securing Debian Manual]
* [https://web.archive.org/web/20140220055801/http://crunchbang.org:80/forums/viewtopic.php?id=24722 The paranoid #! Security Guide]

Talk:Xorg

2026-04-20T08:37:04Z

Alad: /* XLibre */ re

== Setting DPI manually ==

I'm not an Archlinux user, but Google sends me to this Wiki often. As a non-user, I cannot confirm this error on Archlinux unless I find time to learn how to install it. That's unlikely to happen in the foreseeable future.

The example 'Option "DPI" "96 x 96"' is invalid, because 96 x 96 is forced by the Xorg Xserver to start with as default to match Mac and Windows.

Unless the Archlinux X servers are different from other distros I've used, Option "DPI" "120 x 120" and others (144, 192, 108, etc) AFAICT only work for users of proprietary NVidia drivers, fail for certain on MGA (e.g. G400), Intel (e.g. 810, 845, 865, 915, 945, 3000, 4000), Radeon (e.g. rv200, rv250, rv380) & Nouveau (e.g. nv11, G84) on openSUSE 12.2, openSUSE 13.1, Fedora 20 and Mageia 4. I've been using Xorg for many many years and have never yet found any version in which this option is valid using any of the 4 FOSS drivers indicated. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 05:25, 10 December 2013 (UTC)

:As you probably noticed, [[Xorg#Display_size_and_DPI]] is marked as inaccurate with links to several bug reports about Xorg forcing 96x96. Part of Arch's philosophy is to avoid patching of packages whenever possible, but I see that {{Pkg|xorg-server}} uses several patches (see [https://github.com/archlinux/svntogit-packages/blob/packages/xorg-server/trunk]). I don't know which patches other distros use, but this option is not likely to depend on the patches.
:Anyway, if you know a functioning method of manually setting DPI, feel free to share it - even a link to external documentation might be better than the current inaccurate information.
:-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:34, 10 December 2013 (UTC)

::As help situations arise I point people to my http://fm.no-ip.com/Share/DisplaySize which is mostly a lookup table designed to avoid need to calculate values for DisplaySize that will produce a desired DPI. DisplaySize in 'Section "Monitor"' has been reliable long-term with non-broken drivers, but since KScreen was released last summer, a workaround is required to get xorg.conf* to be obeyed at all by KDE. According to [https://bugs.kde.org/show_bug.cgi?id=317929#c13 Alex Fiestas, KScreen 1.1 is proposed to allow xorg.conf* to be obeyed by default on single display systems]. The workaround is to put [Module-kscreen]\nautoload=false in kdmrc. Whether other DEs have similar obstacles I have no idea. It would really be nice for those only wishing to force the hardware native DPI instead of an arbitrary one (which is usually what 96 is) for https://bugs.freedesktop.org/show_bug.cgi?id=41115 to be fixed, which means letting the server automatically as it already knows how make logical and physical DPI match. http://www.gentoo-wiki.info/HOWTO_Set_DPI_Dots_Per_Inch is one place that shows how to perform the calculations.

::"To reduce scaling artifacts to GUI that use bitmaps" is not the only reason to choose +25% steps (96, 120, 144, 168, 192...). Most scalable fonts are tuned to 96 DPI, and step from pixel size to pixel size best at specific steps, of which +25% are the best. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]])

:::I question the validity of the claim that Xorg always sets the DPI to 96 mainly because of this issue: https://bbs.archlinux.org/viewtopic.php?id=197624. Quite a lot of people are having problems with the latest versions of Chromium because Xorg is ''not'' automatically setting the DPI to 96, and Chromium is now high-DPI-sensitive. The result is really bad font and bitmap scaling on most webpages. {{unsigned|20:17, 5 June 2015‎|Silverhammermba}}

::::Having fought this problem with a gen4 Intel laptop---1280x800@14.1in LVDS---over the last two days, I reread the man page and found the newish option "ReprobeOutputs". After enabling, the driver correctly detects the panel geometry and size for slightly rectangular pixels and DPI higher than 96x96. This suggests that udev's hardware probing is failing to detect the real hardware configuration or Xorg server is failing to process the information correctly. Unfortunately neither the ati not nv drivers allow for direct reading of the EDID information and you are left to resort to the kind of monitor configuration hackery mentioned above. [[User:Vorbote|Vorbote]] ([[User talk:Vorbote|talk]]) 14:17, 7 October 2015 (UTC)

:::::I did some experiments in my Radeon HD6310 and discover somethings... lets start:
:::::* efectively, set the dpi in the xorg file is meaningless, as is ignored
:::::* set the CORRECT size for you screen, the size taked manually with rule and seting the correct resolution (if not detected) WILL affect the Xorg dpi.
:::::My monitor is 1366x768 with 309x174 millimeters, those were measured either with software and with my oun measuring rule here in RL, then I set them in Xorg and then the dpi change from 96x96 to 112x112. I use this page to help me: https://www.sven.de/dpi/
:::::{{unsigned|05:40, 19 April 2016 (UTC)|Jristz}}

::::::'''If you are having problems with Xorg DPI, be sure to check if any programs are overriding your settings.''' In my case for example: I found that Xorg actually was respecting the DisplaySize entry in the config file, but xfsettingsd (a component of xfce) was setting this back to 96 DPI immediately after I started Xorg. See https://bugzilla.xfce.org/show_bug.cgi?id=10633 for some discussion of this behavior which is hardcoded into xfsettingsd. Apparently this is their solution for dealing with the possibility of a "Screen" spanning multiple monitors, each of which may have different sizes and/or resolutions (DPI). Running xrandr --dpi XXX ''after'' xfsettingsd is started is a workaround, but I think the long-term solution is to file bugs against applications, such as evince, which are incorrectly relying on the "Screen" DPI reported by Xorg. [[User:Dc46and2|Dc46and2]] ([[User talk:Dc46and2|talk]]) 02:34, 9 June 2016 (UTC)

:::::::In July 2015, a patch was submitted to GTK3 that forces Xft.dpi to 96 whenever 'xrdb -query | grep dpi' would return a null Xft.dpi value. https://bugzilla.gnome.org/show_bug.cgi?id=757142 was filed when the impact of the change became apparent. It was immediately wontfixed. Xft.dpi is not required for Xorg functionality, being an interloper created by the Gnome people(?) as a tool to force DPI, the Gnome device for scaling its UI. The impact of this patch started to become more widely apparent when GTK3 became the default Firefox release build toolkit in 2016, most commonly among users of physical display densities between 96 and 192. I filed [https://bugzilla.mozilla.org/show_bug.cgi?id=1269274 Mozilla bug 1269274 "GTK+ 3.18 - UI text sizes no longer inherited from Linux system"] on account of this. It too was promptly wontfixed. Users of both GTK libs >3.16 and DEs that don't depend on Xft.dpi but instead utilize whatever >96 DPI logical density to which Xorg is configured find UI fonts in Firefox 46+ smaller than non-GTK3 apps, appreciably so even with configured density as low as 108 DPI. Such users not used to having Xft.dpi set, e.g. KDE users, will need to set it to match their Xorg DPI if they want supported GTK3-built Firefox (or SeaMonkey and/or Thunderbird) releases to have UI text matching their other apps. In KDE it's not a hard thing to do, because Xft.dpi is the means through which forced DPI in its systemsettings is implemented, but it will require manual intervention to keep Xorg and Xft.dpi in sync when switching among displays of different densities. Alternatively, and with other non-Gnome users, Xresources can be utilized to manage Xft.dpi, as explained on the parent page. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 06:45, 1 February 2017 (UTC)

:::::: Regarding the Xorg xft.dpi issue, the ticket is now moved to Gitlab: [https://gitlab.freedesktop.org/xorg/xserver/issues/509 See Xserver issue 509].
:::::: [[User:Danger89|Danger89]] ([[User talk:Danger89|talk]]) 15:04, 15 March 2019 (UTC)

== Add xhost si:localuser:$USER ? ==

Access to the X server is usually regulated via the hostname, so if it changes unexpectedly (e.g. see [https://bbs.archlinux.org/viewtopic.php?id=202704 BBS#202704], [[Connman#Avoid_changing_the_hostname]]), things stop working. The user name is (or should be) less prone to change, so you could use {{Pkg|xorg-xhost}} for access:

$ xhost si:localuser:$USER

man Xsecurity says on this:

localuser & localgroup
On systems which can determine in a secure fashion the credentials of a client process,
the "localuser" and "localgroup" authentication methods provide access based on those
credentials. The format of the values provided is platform specific. For POSIX & UNIX
platforms, if the value starts with the character '#', the rest of the string is treated
as a decimal uid or gid, otherwise the string is defined as a user name or group name.

If your system supports this method and you use it, be warned that some programs that
proxy connections and are setuid or setgid may get authenticated as the uid or gid of
the proxy process. For instance, some versions of ssh will be authenticated as the user
root, no matter what user is running the ssh client, so on systems with such software,
adding access for localuser:root may allow wider access than intended to the X display.

However, X apps failing is the symptom; the cause lies in [[Network configuration]], or an issue with the (static) [[hostname]] not being respected. So I'm not sure where to mention this, if at all. One way would be to expand [[Xhost]] and add a link there under [[Xorg#Troubleshooting]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:51, 21 September 2015 (UTC)

: For what it's worth using xhost is probably prefered (for example GDM does this) as xauth was mostly used in an era when hostname changing was very rare. I'm now using xhost instead of maintaining xauth along with the accompanying xauthority file which reduces quite a few dependencies on my end.

: As for where this should go? I have no idea. [[User:Earnest|Earnest]] ([[User talk:Earnest|talk]]) 23:54, 13 March 2016 (UTC)

== Location of Xorg.0.log ==

On my desktop with Gnome 3 and my laptop with KDE 5, my `Xorg.0.log` file is only located in `/var/log/Xorg.0.log`. In the article the location goes back and forth between:

/var/log/Xorg.0.log

and
~/.local/share/xorg/Xorg.0.log

There is a note at the end," `/var/log/` or, for the rootless X default since v1.16, in `~/.local/share/xorg/`". Shouldn't we pick one and put this note at the start? ---- unsigned, by [[User:Slacka]], 20170112

seconded
/var/log/Xorg.0.log
needs to be specified, im running i3wm
--[[User:Yair|Yair]] ([[User talk:Yair|talk]]) 17:21, 20 April 2018 (UTC)

== Rootless Xorg ==

Reverted edit by Alad: "useless without reference, i.e. a bug report "
And why is it not enabled without KMS in the first place? Who says problems with forced rootless xorg are a bug, and not a technical limitation by design?
[[User:Aufkrawall|Aufkrawall]] ([[User talk:Aufkrawall|talk]]) 16:14, 6 November 2017 (UTC)

:That's all vague conjectures. There's no point to relate CPU usage and KMS without the homework to prove there's an actual relation. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 16:20, 6 November 2017 (UTC)

The suggestion at https://wiki.archlinux.org/title/Xorg#Using_xinitrc does not explain why you should use {{ic|startx}} instead of {{ic|exec startx}}, which might lead to confusion among people who are new to configuring Xorg (like me). It's also suggested [https://bbs.archlinux.org/viewtopic.php?pid=1973717#p1973717/ here] that this section should be edited/moved. [[User:Garfa|Garfa]] ([[User talk:Garfa|talk]]) 17:01, 22 May 2021 (UTC)

== Remove/replace/update the xorg.conf config section? ==

"Xorg -configure" is broken since years and nvidia-xconfig creates a bunch of cruft around the Device section.
In addition static configuration and the monolithic xorg.conf are, if not even deprecated, causing trouble for unexperienced users by their unflexibility.
It is common on the bbs to ask for the log and tell forum users to remove that file to "fix" things.

Good reasons (and how) to write a server config (yourself) are indicated in the multihead and optimus articles and I'd suggest to remove that section resp. replace it by an explicit warning to refrain from overriding the autoconfig unwittingly.
Also it should be explained that "Xorg -configure" is known to be "broken" (I cannot prove it, but believe it to be "accidentally broken" as deprecated), the error is normal and you should not be using it anyway ;-)

{{unsigned|07:30, 2 April 2018‎|Seth}}

== Best place for eGPU configs ==

Greetings,
I'd like to add the following critical piece of information that's not easily available on the internet - I had to find it in the Xorg logs when run with a specific config.

To get eGPU working with external monitor and internal one disabled:
* Install the correct version and build of drivers (nvidia or nvidia-dkms or equivalent for other makes)
* Use something like the following for the Xorg config:
Section "Module"
Load "modesetting"
EndSection

Section "Device"
Identifier "nvidia"
Driver "nvidia"
BusID "PCI:6:0:0"
Option "AllowEmptyInitialConfiguration"
Option "AllowExternalGpus"
EndSection

The critical thing is the Option "AllowExternalGpus". The existence of this isn't documented on the threads on nvidia support, or on egpu.io.
First section turns off the internal display. If that's missing the systemd output will stay on screen, frozen. Nothing else is necessary, no DM config files, or nvidia-xconfig, or adding drivers to KMS, or using secure TB3 like Da_blitz's guide suggests.

This was particularly infuriating because the device is easy to work with, send CUDA processes to, and nvidia-xsettings --query-gpu-info recognizes the external monitor. Yet xrandr doesn't. And using most configs crashes Xorg with a multitude of errors, from "No screens found" to "no usable config", to "Failed to get display number from pipe". All were rabbit holes. This info needs to be out there somewhere.

Whats the best place to add this information?
I was thinking under either NVIDIA/Tips or config or Xorg/Tips or config or start a new page "External GPUs"

[[User:Snugghash|Snugghash]] ([[User talk:Snugghash|talk]]) 22:59, 10 August 2018 (UTC)

:Since it is specific to the NVIDIA driver, add it to [[NVIDIA/Tips_and_tricks]]. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 18:41, 11 August 2018 (UTC)

== systemctl --user in rootless Xorg ==

To get {{ic|systemctl --user}} to work (as well as a device management I guess) with the rootless Xorg setup, I had to edit {{ic|/etc/pam.d/system-login}} so that {{ic|pam_systemd.so}} is required (that is remove the {{ic|-}} in front of {{ic|session}} and change {{ic|optional}} to {{ic|required}}). I am not sure why this isn't the default somehow. -- [[User:Kalessin|Kalessin]] ([[User talk:Kalessin|talk]]) 19:28, 6 November 2018 (UTC)

:''to get'' {{ic|systemctl --user}} ''to work''
:not sure what you mean by that but i use ''--user'' for cron like jobs without changing {{ic|/etc/pam.d/system-login}} --[[User:Ubone|Ubone]] ([[User talk:Ubone|talk]]) 09:07, 7 November 2018 (UTC)

::I just meant any command using {{ic|systemctl --user}}.
::My comment was specific to rootless Xorg, but was edited out of its context, are you using rootless Xorg? -- [[User:Kalessin|Kalessin]] ([[User talk:Kalessin|talk]]) 17:48, 10 November 2018 (UTC)

:::yes ---[[User:Ubone|Ubone]] ([[User talk:Ubone|talk]]) 02:38, 11 November 2018 (UTC)

== XWayland ==

As discussed in [[Talk:Wayland#XWayland]], I would like to add a small section for XWayland.

Technically it is a part of the XServer, so where would you like it better, here or at [[Wayland]]?

[[User:G3ro|G3ro]] ([[User talk:G3ro|talk]]) 15:45, 17 October 2020 (UTC) G3ro

== generic video driver ==

previously under BIOS, there was the VESA graphic mode : this mode did not use all the available video capabilities but worked and often allowed to launch the graphic interface whatever the underlying video card.

VESA is no longer usable under UEFI (vesa: Refusing to run on UEFI in Xorg.0.log) : is there an equivalent for UEFI ? is it the modesetting driver (modesetting_drv.so) ?

--[[User:Lacsap|Lacsap]] ([[User talk:Lacsap|talk]]) 10:56, 21 January 2022 (UTC)

:There are multiple generic video drivers, some are mentioned in [[Xorg#Driver installation]] (including {{man|4|modesetting}}). — [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 10:28, 23 January 2022 (UTC)

== DDX/DIX ==

DDX means Device Dependent X, which basically applies to all display drivers separately packaged and specific to brand, e.g. amdgpu, intel, nouveau and radeon.

DIX means Device Independent X, and is a term which applies to the modesetting display driver, the upstream default for all GPUs for which KMS is provided.

The parent page should be edited to take this into account, applying term DIX rather than DDX when term modesetting is discussed.

[[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 14:57, 10 April 2025 (UTC)|14:03, 10 April 2025 (UTC)|Mrmazda

:"separately packaged and specific to brand" — wrong. DDX [https://www.x.org/wiki/Development/Documentation/Glossary/ means] "The part of X that interacts with the hardware". The {{ic|modesetting}} display driver interacts with the hardware using KMS, so it ''is'' DDX by definition. — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 14:12, 10 April 2025 (UTC)
::Thanks for your clarification! I didn't know what DDX actually is before. [[User:GalaxySnail|GalaxySnail]] ([[User talk:GalaxySnail|talk]]) 14:22, 10 April 2025 (UTC)
::Fun fact: [[Xwayland]] is [https://gitlab.freedesktop.org/xorg/xserver/-/commit/6e539d8817f738289dc2dea13d0720116287ab9d also DDX] — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 14:23, 10 April 2025 (UTC)

:Same URL says "DIX: Device Independent X. The part of X that interacts with clients and implements software rendering. Basically everything in the server except for the hw/ directory. The event delivery is part of the DIX." The modesetting driver is a different technology, and indifferent to who made the device or its inner workings. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 14:57, 10 April 2025 (UTC)
::Not sure what you meant to say, these quotes further confirm that modesetting is DDX. — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 15:04, 10 April 2025 (UTC)
:::Note andreymal's "means" reference was originally written in July 2013. It depends on what the quoted text is understood to mean. I read:
::::Dependent: specific to proprietary technology of the GPU brand, e.g. for AMD, for Intel, for NVidia; dependent on a specific KMS kernel module
::::Independent: not specific to proprietary technology based upon GPU brand; generic; supported by any/every kernel module providing KMS
:::There's also [https://dri.freedesktop.org/wiki/DDX/ dri/DDX] which says "The DDX drivers reside in a package called xf86-video-foo". xf86-video-modesetting was retired as of server 1.17, its content moved into the server package, functionally highlighting the independence of KMS provider distinction. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 19:55, 10 April 2025 (UTC)
::::"Dependent: specific to proprietary technology" — wrong again. There is no such definition anywhere. No one ever mentions the word "proprietary".
::::"its content moved into the server package" — this does not matter. The definitions of DDX and DIX are based on what these components do, not the packaging stuff.
::::As you can see, [https://dri.freedesktop.org/wiki/DDX/ dri/DDX] says that modesetting is "a generic DDX".
::::— [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 20:07, 10 April 2025 (UTC)
:::::"Generic" equates in some fashion or other to such terms as general purpose, common, universal and ''independent''; IOW: no specific GPU, regardless which GPU, thus independent. Your [https://www.x.org/wiki/ "means" reference] is to a wiki too, made of humans who get things wrong more than often enough. No maintainer or developer commenting in any of the Xorg, Kernel or GPU bug reports I've filed or commented over the years has tried to correct me on this. Here be the first anywhere. This wouldn't have come up if at least a decade ago Adam J, Dave A, Keith P, Daniel S or someone of their ilk had not corrected me and explained in a bug report or X mailing list somewhere, which I hope to rediscover someday (in order to have reason to return). [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 22:55, 10 April 2025 (UTC)
::::::modesetting is a ''generic'' driver that does not depend on ''specific'' hardware, but it is still ''dependent'' on hardware in general. You cannot use modesetting without a GPU; thus, it is DDX. — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 23:05, 10 April 2025 (UTC)
:::::::Indeed, '''''a''''' GPU, ''any'' GPU, is so broad an affiliation as to render the term DDX meaningless. If there is no GPU, no KMS module is applicable, nothing to setup or control. Any X display driver is simply an (generic) X display driver. If DDX means a module only applicable to a specific class of GPU, a meaningful dependency is implied. If DIX means a module that is indifferent to any GPU class, independence can be implied, with result that DDX and DIX actually provide useful meaning. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 02:25, 11 April 2025 (UTC)

== <s>XLibre</s> ==

Ok. [[User:Tatsumoto|Tatsumoto]], let's not waste our valuable breath.

Since the admin has removed the wiki page, I am proposing a change on this page such that:

# Introduces installation note of {{AUR|xlibre-xserver}} right on this page
# Redirects XLibre to Xorg

Rationale: primary executable of the XLibre project is still installed as <code>/usr/bin/Xorg</code> for compatibility reasons.

Any ideas? [[User:SH3NG1UN|SH3NG1UN]] ([[User talk:SH3NG1UN|talk]]) 13:34, 17 April 2026 (UTC)

:No. While redirecting the xlibre page ''somewhere'' would make sense, this page is not the right target: it is about the Xorg project. [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 13:51, 17 April 2026 (UTC)

::How about redirecting to [[Display server]]? Besides the obvious candidates, we could include {{AUR|arcan}} and [[Xephyr]] in such an article. Compare [[Sound system]] and [[w:List of display servers]] (though the later goes a bit above-board, including all Wayland compositors too.) -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 15:14, 17 April 2026 (UTC)
:::Just before the deletion, the article listed two ways to install Xlibre: from the AUR with an additional helper package, or from a custom repository maintained by the project's authors. I agree that this information could be moved to [[Xorg#Installation]], removing the need for a separate article, since Xlibre currently works as a drop-in replacement of Xorg. That edit would require the least effort. That said, to avoid possible confusion, it should also note that Xlibre is a distinct project and is not affiliated with freedesktop.
:::Redirecting to [[Display server]] is a good idea too, but I'm afraid it adds overhead: someone will have to populate and maintain the new page.
:::Also, I'll notify the xlibre team and ask them to tone down their homepage. [[User:Tatsumoto|Tatsumoto]] ([[User talk:Tatsumoto|talk]]) 15:43, 17 April 2026 (UTC)
:::We have a blurb about display servers in [[General_recommendations#Display_server]]. Rather than a new stub page, what about a section somewhere in [[List of applications]]? That should make the intended scope per project very clear. — [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 15:46, 17 April 2026 (UTC)
::::[[List of applications]] sounds good. The implied "recommendations" in [[General recommendations]] is not great when all we want is listing software packages. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 18:46, 17 April 2026 (UTC)
::::Can you recover the lost installation steps from the deleted article? I can't access its history anymore. The wayback machine doesn't help either, it shows an outdated snapshot. Also, where would it be appropriate to move that information? The suggested pages don't seem suitable for longer technical details, they just list available options. [[User:Tatsumoto|Tatsumoto]] ([[User talk:Tatsumoto|talk]]) 16:10, 17 April 2026 (UTC)
:::::Upstream should provide all generic info and the AUR has a pinned comment with Arch-specific details. — [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 16:16, 17 April 2026 (UTC)
::::::I edited [[General_recommendations#Display_server]]. It's better than nothing, though not ideal. Just to clarify, if Xlibre fixes the issues on their homepage that led to the deletion, could the standalone [[Xlibre]] page be restored? [[User:Tatsumoto|Tatsumoto]] ([[User talk:Tatsumoto|talk]]) 16:38, 17 April 2026 (UTC)
:::::::I mean, sure? It would just be another page at this point. Though for it to make sense as a standalone page, it should have some content. Besides the installation instructions (already in the AUR comment as pointed out above), there was only a mention about TearFree being enabled by default on some chipsets. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 18:46, 17 April 2026 (UTC)
:@[[User:Tatsumoto|Tatsumoto]], you talked about their homepage [https://x11libre.net]. I suspect that this homepage has gone unmaintained.
:# On their GitHub [https://github.com/x11libre] the project name is spelled as XLibre. However, on their homepage the project name is instead spelled as Xlibre. 1st inconsistency. This is about branding.
:# On the download section of their homepage, it states that "The xlibre-server AUR package is known to cause problems and is NOT supported. Instead these sources [https://github.com/X11Libre/pkgbuilds-arch-based] should be used. Additionally, a binary repository [https://x11libre.net/repo/arch_based] has recently been added for easier installation." However, if you follow the sources [https://github.com/X11Libre/pkgbuilds-arch-based] link, the README states that "these official Xlibre PKGBUILD files are also being made available in the Arch User Repostory (AUR) by the maintainer named 'xlibre'." 2nd inconsistency. Very confusing.
:[[User:SH3NG1UN|SH3NG1UN]] ([[User talk:SH3NG1UN|talk]]) 01:59, 18 April 2026 (UTC)
:The stated reason for removing the Xlibre article was as follows:
:''Deleted together with the associated page with reason: The Xlibre project goes against <nowiki>https://terms.archlinux.org/docs/code-of-conduct/#respect</nowiki> and should not be listed on ArchWiki. See <nowiki>https://x11libre.net/#about</nowiki>''
:Shall we remove the [[GNOME]] article as well? Jeremy Bicha is a GNOME maintainer and being a convicted child sex predator seems like a more egregious CoC violation. If you're going to moralize, be consistent.
:[[User:Jeremyb|Jeremyb]] ([[User talk:Jeremyb|talk]]) 08:25, 18 April 2026 (UTC)

::No. The cited section states "Arch Linux is a respectful, inclusive community. Anti-social or offensive behaviour will not be tolerated" followed by "Maligning other FOSS projects or distributions, or any other operating systems and their users is prohibited". XLibre is inflammatory since its inception against the Xorg project, e.g. the name-calling "moles from BigTech" in the official website [https://x11libre.net/#about about section] that is still featured to this day.
::You registered specifically to [https://terms.archlinux.org/docs/code-of-conduct/#no-trolling troll]/[https://terms.archlinux.org/docs/code-of-conduct/#do-not-flame flame]/[https://terms.archlinux.org/docs/code-of-conduct/#ineffective-discussion-bikeshed bikeshed] a closed topic: I'm closing it again and banning you.
::'''To anyone reading''', I ''will'' ban any person who harasses members of staff (multiple people leaving a single comment can ''also'' be seen as harassment).
::--[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 09:37, 18 April 2026 (UTC)
:::Pretty sure that website has been completely unmaintained since it's birth, the github has been updated to be a lot better.
:::It might belong to the original dev who started the project before the community contributed to it further, not sure when the domain expires. [[User:Kippykip|Kippykip]] ([[User talk:Kippykip|talk]]) 01:56, 19 April 2026 (UTC)
::::Unmaintained or not, they [https://x.com/XLibreDev/status/2045180587200397321 stand behind it].
::::-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 07:15, 19 April 2026 (UTC)
:::::Either way, I believe this matter can be settled. While it is likely true that the project founder of Xlibre was treated a foul way back in the Xorg (and I believe they would), posting the backstories on X is a different story to directly accusing on their project frontpage, which is no longer about personal stands, it is about reputations and project brandings.
:::::Looking at where we are today, we have already got a mention of it on a different page [https://wiki.archlinux.org/title/General_recommendations#Display_server]. That shall be good enough for the interests of everyone.
:::::-- [[User:SH3NG1UN|SH3NG1UN]] ([[User talk:SH3NG1UN|talk]]) 01:30, 20 April 2026 (UTC)
::::::If [https://github.com/X11Libre/website/pull/4 this PR] gets merged, I'm looking forward to the standalone [[Xlibre]] page being restored. For a large project with so many configuration options, a single paragraph in [[General_recommendations#Display_server]] is clearly insufficient. '''UPD''': no luck so far. Although they said on Telegram they're planning a major website update, and changing the site now would be too much work, so we'll have to wait. [[User:Tatsumoto|Tatsumoto]] ([[User talk:Tatsumoto|talk]]) 01:45, 20 April 2026 (UTC)
:::::::The PR was closed and it seems the Xlibre upstream has clearly no interest in the matter. The TearFree default is already mentioned in the upstream README; if the project diverges further from Xorg, this is likely the best place to document it. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 08:37, 20 April 2026 (UTC)

Talk:Llama.cpp

2026-04-20T08:31:11Z

Alad: /* Execution backends */ re

== LLM-assisted changes ==

Hi all,

Let's not rely on LLMs to generate an ArchWiki article, or at least not on this one.

LLMs generally have no idea what they are saying when it comes to highly detailed data. Without proper prompt engineering and sophisticated agent systems, you can safely assume they are as intelligent as dumb terminals. The LLM-assisted change [[User:Mr.Smith1974|Mr.Smith1974]] has contributed (and reverted) even failed to explain the correct meaning of GGUF. The file format GGUF is actually named after Georgi Gerganov, not GPT-Generated.

Let's focus on what we've actually triaged instead. Use the search engine to acquire extra data. Polish the wordings of what we've known to work for a bonus.

Regards,

[[User:SH3NG1UN|SH3NG1UN]] ([[User talk:SH3NG1UN|talk]]) 03:33, 13 January 2026 (UTC)

== Execution backends ==

Hello. The article only provides the `llama.cpp-vulkan` package for GPU inference, even though on AUR there is a CUDA package available from the same submitter [https://aur.archlinux.org/packages/llama.cpp-cuda]

I must add that the CUDA package is "Flagged out-of-date (2025-12-22)" [[User:Gotoro|Gotoro]] ([[User talk:Gotoro|talk]]) 08:50, 3 April 2026 (UTC)

:Hi. The reason CUDA was not added is that Vulkan solution is general, performant enough for most hardware setup, and I personally believe that is what edge AI deployment should look like - if your software stack is capable of gaming, it is capable of AI. But your point has some truth in it as well - if the package already exists, mentioning it would not cost anything. Adding the package now. [[User:SH3NG1UN|SH3NG1UN]] ([[User talk:SH3NG1UN|talk]]) 08:57, 3 April 2026 (UTC)
::Sorry I must revert my previous edit. Reading the comments section of [https://aur.archlinux.org/packages/llama.cpp-cuda], it appears that the package maintainer has been missing since 2025-12-11. Their GH user page [https://github.com/envolution] supports the claim, too. The package quality cannot be guaranteed anymore, we cannot risk this on ArchWiki. Reverting the edit now. [[User:SH3NG1UN|SH3NG1UN]] ([[User talk:SH3NG1UN|talk]]) 08:26, 7 April 2026 (UTC)

:::The usual approach would be to file an orphan request, instead of having an incomplete listing here -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 08:31, 20 April 2026 (UTC)

Display server

2026-04-17T18:51:33Z

Alad: useful redirect (can be redirected later to List of applications)

#REDIRECT: [[General_recommendations#Display_server]]

General recommendations

2026-04-17T18:49:40Z

Alad: /* Display server */ update merge flag, see Talk:Xorg#Xlibre

[[Category:System administration]]
[[bs:General recommendations]]
[[ca:General recommendations]]
[[cs:General recommendations]]
[[el:General recommendations]]
[[es:General recommendations]]
[[fr:General recommendations]]
[[hu:General recommendations]]
[[it:General recommendations]]
[[ja:一般的な推奨事項]]
[[lv:General recommendations]]
[[pl:General recommendations]]
[[pt:General recommendations]]
[[ru:General recommendations]]
[[tr:General recommendations]]
[[zh-hans:建议阅读]]
[[zh-hant:General recommendations]]
{{Related articles start}}
{{Related|Frequently asked questions}}
{{Related|List of applications}}
{{Related|System maintenance}}
{{Related articles end}}

This document is an annotated index of popular articles and important information for improving and adding functionalities to the installed Arch system. Readers are assumed to have read and followed the [[Installation guide]] to obtain a basic Arch Linux installation. Having read and understood the concepts explained in [[#System administration]] and [[#Package management]] is ''required'' for following the other sections of this page and the other articles in the wiki.

== System administration ==

This section deals with administrative tasks and system management. See [[Core utilities]] and [[:Category:System administration]] for more.

=== Users and groups ===

A new installation leaves you with only the [[Wikipedia:Superuser|superuser]] account, better known as "root". Logging in as root for prolonged periods of time, possibly even exposing it via [[SSH]] on a server, [https://apple.stackexchange.com/questions/192365/is-it-ok-to-use-the-root-user-as-a-normal-user/192422#192422 is insecure]. Instead, you should create and use unprivileged user account(s) for most tasks, only using the root account for system administration. See [[Users and groups#User management]] for details.

Users and groups are a mechanism for ''access control''; administrators may fine-tune group membership and ownership to grant or deny users and services access to system resources. Read the [[Users and groups]] article for details and potential security risks.

=== Security ===

Read [[Security]] for recommendations and best practices on hardening the system.

For a list of applications to allow running commands or starting an interactive shell as another user (e.g. root), see [[List of applications/Security#Privilege elevation]]. For graphical equivalents (and how to avoid them), see [[Privilege elevation for graphical applications]].

{{Tip|More fine-grained privilege elevation is provided by [[polkit]], which requires additional setup for graphical environments.}}

=== Service management ===

Arch Linux uses [[systemd]] as the [[init]] process, which is a system and service manager for Linux. For maintaining your Arch Linux installation, it is a good idea to learn the basics about it.

Interaction with ''systemd'' is done through the ''systemctl'' command. See [[systemd#Basic systemctl usage]] for more information.

A logging system is also provided, with the command ''journalctl''. See [[journal]] for more information.

=== System maintenance ===

Arch is a rolling release system and has rapid package turnover, so users have to take some time to do [[system maintenance]].

== Package management ==

This section contains helpful information related to package management. See [[FAQ#Package management]] and [[:Category:Package management]] for more.

{{Note|It is imperative to keep up to date with changes in Arch Linux that require manual intervention '''before''' upgrading your system. Subscribe to the [https://lists.archlinux.org/mailman3/lists/arch-announce.lists.archlinux.org/ arch-announce mailing list] or the [https://archlinux.org/feeds/news/ recent news RSS feed]. Alternatively, check the front page [https://archlinux.org/ Arch news] every time before you update.}}

=== pacman ===

[[pacman]] is the Arch Linux ''pac''kage ''man''ager: it is highly encouraged to become familiar with it before reading any other articles.

For long term handling of cached packages, see [[pacman#Cleaning the package cache]].

See [[pacman/Tips and tricks]] for suggestions on how to improve your interaction with ''pacman'' and package management in general.

=== Repositories ===

See the [[Official repositories]] article for details about the purpose of each officially maintained repository.

If you plan on using 32-bit applications, you will want to enable the [[multilib]] repository.

The [[Unofficial user repositories]] article lists several other unsupported repositories.

You may consider installing the [[pkgstats]] service.

=== Mirrors ===

Visit the [[Mirrors]] article for steps on taking full advantage of using the fastest and most up to date mirrors of the official repositories. As explained in the article, a particularly good advice is to routinely check the [https://archlinux.org/mirrors/status/ Mirror Status] page for a list of mirrors that have been recently synced. This can be automated with [[Reflector]].

=== Arch Build System ===

''Ports'' is a system initially used by BSD distributions consisting of build scripts that reside in a directory tree on the local system. Simply put, each port contains a script within a directory intuitively named after the installable third-party application.

The [[Arch build system]] offers the same functionality by providing build scripts called [[PKGBUILD]]s, which are populated with information for a given piece of software: integrity hashes, project URL, version, license and build instructions. These PKGBUILDs are parsed by [[makepkg]], the actual program that generates packages that are cleanly manageable by ''pacman''.

Every package in the repositories along with those present in the AUR are subject to recompilation with ''makepkg''.

=== Arch User Repository ===

While the Arch Build System allows the ability of building software available in the official repositories, the [[Arch User Repository]] (AUR) is the equivalent for user submitted packages. It is an unsupported repository of build scripts accessible through the [https://aur.archlinux.org/ web interface] or through the [[Aurweb RPC interface]].

== Booting ==

This section contains information pertaining to the boot process. An overview of the Arch boot process can be found at [[Arch boot process]]. See [[:Category:Boot process]] for more.

=== Hardware auto-recognition ===

Hardware should be auto-detected by [[udev]] during the boot process by default. A potential improvement in boot time can be achieved by disabling module auto-loading and specifying required modules manually, as described in [[Kernel modules]]. Additionally, [[Xorg]] should be able to auto-detect required drivers using {{ic|udev}}, but users have the option to configure the X server manually too.

=== Microcode ===

Processors may have [https://www.anandtech.com/show/8376/intel-disables-tsx-instructions-erratum-found-in-haswell-haswelleep-broadwelly faulty behaviour], which the kernel can correct by updating the ''microcode'' on startup. See [[Microcode]] for details.

=== Retaining boot messages ===

Once the login prompt appears, the messages from boot are cleared, leaving users unable to gather feedback from them. [[Disable clearing of boot messages]] to overcome this limitation.

=== Num Lock activation ===

[[Wikipedia:Num Lock|Num Lock]] is a toggle key found in most keyboards. For activating Num Lock's number key-assignment during startup, see [[Activating numlock on bootup]].

== Graphical user interface ==

This section provides orientation for users wishing to run graphical applications on their system. See [[:Category:Graphical user interfaces]] for additional resources.

=== Display server ===

{{Merge|List of applications|An overview of software does not belong in a "recommendations" article|Talk:Xorg#Xlibre}}

[[Xorg]] is the public, open-source implementation of the [[Wikipedia:X Window System|X Window System]] (commonly X11, or X). It is used for running applications with graphical user interfaces (GUIs).

[https://x11libre.net/ Xlibre] is a fork of the Xorg display server created because Xorg maintainers showed little interest in significant changes, enhancements, and new features. To install Xlibre instead of Xorg, follow the [https://x11libre.net/repo/arch_based/x86_64/README.html README].

[[Wayland]] is a newer, alternative display server protocol with several [[Wayland#Compositors|compositors]] to choose from. Its advantages over Xorg are enhanced security features, more efficient handling of modern graphics tasks and active development while retaining compatibility through [[Xwayland]].

=== Display drivers ===

The default ''modesetting'' display driver will work with most video cards, but performance may be improved and additional features harnessed by installing the [[Graphics processing unit#Installation|appropriate driver]] for [[AMD]], [[Intel]] or [[NVIDIA]] products.

=== Desktop environments ===

Although the display server provides the basic framework for building a graphical environment, additional components may be considered necessary for a complete user experience. [[Desktop environment]]s such as [[KDE]], [[GNOME]], [[COSMIC]], [[Xfce]], [[Cinnamon]], [[LXDE]], bundle together a wide range of well-integrated applications, such as a window manager or compositor, panel/taskbar, file manager, terminal emulator, text editor, icons, and other utilities. Users with less experience may wish to install a desktop environment for a more familiar environment. See [[:Category:Desktop environments]] for additional resources.

=== Window managers or compositors ===

A full-fledged desktop environment provides a complete and consistent graphical user interface, but tends to consume a good amount of system resources. Users seeking to maximize performance or otherwise simplify their environment may opt to install a [[window manager]] or [[Wayland#Compositors|compositor]] alone and hand-pick desired extras. Using [[Xorg]], most desktop environments allow use of an alternative window manager as well. [[:Category:Dynamic window managers|Dynamic]], [[:Category:Stacking window managers|stacking]], and [[:Category:Tiling window managers|tiling]] window managers differ in their handling of window placement.

=== Display manager ===

Most desktop environments include a [[display manager]] for automatically starting the graphical environment and managing user logins. Users without a desktop environment can install one separately. Alternatively you may [[start X at login]] as a simple alternative to a display manager.

=== User directories ===

Well-known user directories like Downloads or Music are created by the {{ic|xdg-user-dirs-update.service}} user service, that is provided by {{Pkg|xdg-user-dirs}} and enabled by default upon install. If your desktop environment or window manager does not pull in the package, you can [[install]] it and run {{ic|xdg-user-dirs-update}} manually as per [[XDG user directories#Creating default directories]].

== Power management ==

This section may be of use to laptop owners or users otherwise seeking power management controls. See [[:Category:Power management]] for more.

See [[Power management]] for more general overview.

=== ACPI events ===

Users can configure how the system reacts to ACPI events such as pressing the power button or closing a laptop's lid. For the recommended method using [[systemd]], see [[Power management#ACPI events]]. For the old method, see [[acpid]].

=== CPU frequency scaling ===

Modern processors can decrease their frequency and voltage to reduce heat and power consumption. Less heat leads to more quiet system and prolongs the life of hardware. See [[CPU frequency scaling]] for details.

=== Laptops ===

For articles related to portable computing along with model-specific installation guides, please see [[:Category:Laptops]]. For a general overview of laptop-related articles and recommendations, see [[Laptop]].

=== Suspend and hibernate ===

See the main article: [[Power management/Suspend and hibernate]].

== Multimedia ==

[[:Category:Multimedia]] includes additional resources.

=== Sound system ===

[[ALSA]] is a kernel [[sound system]] that should work out the box (it just needs to be [[Advanced Linux Sound Architecture#Unmuting the channels|unmuted]]). [[Sound server]]s such as [[PipeWire]] and [[PulseAudio]] can offer additional features and support more complex audio configuration.

See [[Professional audio]] for advanced audio requirements.

== Networking ==

This section is confined to small networking procedures. See [[Network configuration]] for a full configuration guide and [[:Category:Networking]] for related articles.

=== DNS security ===

For better security while browsing the web, paying online, connecting to [[SSH]] services and similar tasks consider using [[DNSSEC]]-enabled [[DNS resolver]] that can validate signed [[Wikipedia:Domain Name System|DNS]] records, and an encrypted protocol such as [[Wikipedia:DNS over TLS|DNS over TLS]], [[Wikipedia:DNS over HTTPS|DNS over HTTPS]] or [[Wikipedia:DNSCrypt|DNSCrypt]]. See [[Domain name resolution]] for details.

=== Setting up a firewall ===

A firewall can provide an extra layer of protection on top of the Linux networking stack. While the stock Arch kernel is capable of using [[Wikipedia:Netfilter|Netfilter]]'s [[iptables]] and [[nftables]], neither are enabled by default. It is highly recommended to set up some form of firewall. See [[:Category:Firewalls]] for available guides.

=== Network shares ===

To share files among the machines in a network, follow the [[NFS]] or the [[SSHFS]] article.

Use [[Samba]] to join a Windows network. To configure the machine to use Active Directory for authentication, read [[Active Directory integration]].

See also [[:Category:Network sharing]].

== Input devices ==

This section contains popular input device configuration tips. See [[:Category:Input devices]] for more.

=== Keyboard layouts ===

Non-English or otherwise non-standard keyboards may not function as expected by default. The necessary steps to configure the keymap are different for virtual console and [[Xorg]], they are described in [[Keyboard configuration in console]] and [[Keyboard configuration in Xorg]] respectively.

=== Mouse buttons ===

Owners of advanced or unusual mice may find that not all mouse buttons are recognized by default, or may wish to assign different actions for extra buttons. Instructions can be found in [[Mouse buttons]].

=== Laptop touchpads ===

Many laptops use [[Wikipedia:Synaptics|Synaptics]] or [[Wikipedia:Alps Electric|ALPS]] "touchpad" pointing devices. For these, and several other touchpad models, you can use either the Synaptics input driver or libinput; see [[Touchpad Synaptics]] and [[libinput]] for installation and configuration details.

=== TrackPoints ===

See the [[TrackPoint]] article to configure your TrackPoint device.

== Optimization ==

This section aims to summarize tweaks, tools and available options useful to improve system and application performance.

=== Benchmarking ===

[[Benchmarking]] is the act of measuring performance and comparing the results to another system's results or a widely accepted standard through a unified procedure.

=== Improving performance ===

The [[Improving performance]] article gathers information and is a basic rundown about gaining performance in Arch Linux.

=== Solid state drives ===

The [[Solid state drive]] article covers many aspects of solid state drives, including configuring them to maximize their lifetimes, e.g. with [[TRIM]].

== System services ==

This section relates to [[daemons]].

=== File index and search ===

Most distributions have a ''locate'' command available to be able to quickly search files. Arch Linux provides several alternatives, see [[locate]] for details.

[[List of applications/Utilities#File searching|Desktop search engines]] provide a similar service, while better integrated into [[desktop environment]]s.

=== Local mail delivery ===

A default setup does not provide a way to synchronize mail. A list of mail delivery agents is available in the [[Mail server]] article.

=== Printing ===

[[CUPS]] is a standards-based, open source printing system developed by OpenPrinting for Linux. See [[:Category:Printers]] for printer-specific articles.

== Appearance ==

This section contains frequently-sought "eye candy" tweaks for an aesthetically pleasing Arch experience. See [[:Category:Eye candy]] for more.

=== Fonts ===

You may wish to install a set of TrueType fonts, as only unscalable bitmap fonts are included in a basic Arch system. There are several general-purpose [[Fonts#Families|font families]] providing large [[Wikipedia:Unicode|Unicode]] coverage and even [[Metric-compatible fonts|metric compatibility]] with fonts from other operating systems.

A plethora of information on the subject can be found in the [[Fonts]] and [[Font configuration]] articles.

If spending a significant amount of time working from the virtual console (i.e. outside an X server), users may wish to change the console font to improve readability; see [[Linux console#Fonts]].

=== GTK and Qt themes ===

A big part of the applications with a graphical interface for Linux systems are based on the [[GTK]] or the [[Qt]] toolkits. See those articles and [[Uniform look for Qt and GTK applications]] for ideas to improve the appearance of your installed programs and adapt it to your liking.

== Console improvements ==

This section applies to small modifications that improve console programs' practicality. See [[:Category:Command-line shells]] for more.

=== Tab-completion enhancements ===

It is recommended to properly set up extended [[Wikipedia:Command-line_completion|tab completion]] right away, as instructed in the article of your chosen [[shell]].

=== Aliases ===

Aliasing a command, or a group thereof, is a way of saving time when using the console. This is especially helpful for repetitive tasks that do not need significant alteration to their parameters between executions. Common time-saving aliases can be found in [[Bash#Aliases]], which are easily portable to [[zsh]] as well.

=== Alternative shells ===

[[Bash]] is the shell installed by default in an Arch system. The live installation media, however, uses [[zsh]] with the {{Pkg|grml-zsh-config}} addon package. See [[Command-line shell#List of shells]] for more alternatives.

=== Bash additions ===

A list of miscellaneous Bash settings, history search and [[Readline]] macros is available in [[Bash#Tips and tricks]].

=== Colored output ===

This section is covered in [[Color output in console]].

=== Compressed files ===

Compressed files, or archives, are frequently encountered on a GNU/Linux system. [[Tar]] is one of the most commonly used archiving tools, and users should be familiar with its syntax (Arch Linux packages, for example, are simply {{Pkg|zstd}} compressed tarballs). See [[Archiving and compression]].

=== Console prompt ===

The console prompt ({{ic|PS1}}) can be customized to a great extent. See [[Bash/Prompt customization]] or [[Zsh#Prompts]] if using Bash or Zsh, respectively.

=== Emacs shell ===

Emacs is known for featuring options beyond the duties of regular text editing, one of these being a full shell replacement. Consult [[Emacs#Colored output issues]] for a fix regarding garbled characters that may result from enabling colored output.

=== Mouse support ===

Using a mouse with the console for copy-paste operations can be preferred over [[GNU Screen]]'s traditional copy mode. Refer to [[General purpose mouse]] for comprehensive directions. Note that you can already do this in [[terminal emulator]]s with the [[clipboard]].

=== Session management ===

Using terminal multiplexers like [[tmux]] or [[GNU Screen]], programs may be run under sessions composed of tabs and panes that can be detached at will, so when the user either kills the terminal emulator, terminates [[X]], or logs off, the programs associated with the session will continue to run in the background as long as the terminal multiplexer server is active. Interacting with the programs requires reattaching to the session.

Talk:Xorg

2026-04-17T18:46:59Z

Alad: /* XLibre */ re

== Setting DPI manually ==

I'm not an Archlinux user, but Google sends me to this Wiki often. As a non-user, I cannot confirm this error on Archlinux unless I find time to learn how to install it. That's unlikely to happen in the foreseeable future.

The example 'Option "DPI" "96 x 96"' is invalid, because 96 x 96 is forced by the Xorg Xserver to start with as default to match Mac and Windows.

Unless the Archlinux X servers are different from other distros I've used, Option "DPI" "120 x 120" and others (144, 192, 108, etc) AFAICT only work for users of proprietary NVidia drivers, fail for certain on MGA (e.g. G400), Intel (e.g. 810, 845, 865, 915, 945, 3000, 4000), Radeon (e.g. rv200, rv250, rv380) & Nouveau (e.g. nv11, G84) on openSUSE 12.2, openSUSE 13.1, Fedora 20 and Mageia 4. I've been using Xorg for many many years and have never yet found any version in which this option is valid using any of the 4 FOSS drivers indicated. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 05:25, 10 December 2013 (UTC)

:As you probably noticed, [[Xorg#Display_size_and_DPI]] is marked as inaccurate with links to several bug reports about Xorg forcing 96x96. Part of Arch's philosophy is to avoid patching of packages whenever possible, but I see that {{Pkg|xorg-server}} uses several patches (see [https://github.com/archlinux/svntogit-packages/blob/packages/xorg-server/trunk]). I don't know which patches other distros use, but this option is not likely to depend on the patches.
:Anyway, if you know a functioning method of manually setting DPI, feel free to share it - even a link to external documentation might be better than the current inaccurate information.
:-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:34, 10 December 2013 (UTC)

::As help situations arise I point people to my http://fm.no-ip.com/Share/DisplaySize which is mostly a lookup table designed to avoid need to calculate values for DisplaySize that will produce a desired DPI. DisplaySize in 'Section "Monitor"' has been reliable long-term with non-broken drivers, but since KScreen was released last summer, a workaround is required to get xorg.conf* to be obeyed at all by KDE. According to [https://bugs.kde.org/show_bug.cgi?id=317929#c13 Alex Fiestas, KScreen 1.1 is proposed to allow xorg.conf* to be obeyed by default on single display systems]. The workaround is to put [Module-kscreen]\nautoload=false in kdmrc. Whether other DEs have similar obstacles I have no idea. It would really be nice for those only wishing to force the hardware native DPI instead of an arbitrary one (which is usually what 96 is) for https://bugs.freedesktop.org/show_bug.cgi?id=41115 to be fixed, which means letting the server automatically as it already knows how make logical and physical DPI match. http://www.gentoo-wiki.info/HOWTO_Set_DPI_Dots_Per_Inch is one place that shows how to perform the calculations.

::"To reduce scaling artifacts to GUI that use bitmaps" is not the only reason to choose +25% steps (96, 120, 144, 168, 192...). Most scalable fonts are tuned to 96 DPI, and step from pixel size to pixel size best at specific steps, of which +25% are the best. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]])

:::I question the validity of the claim that Xorg always sets the DPI to 96 mainly because of this issue: https://bbs.archlinux.org/viewtopic.php?id=197624. Quite a lot of people are having problems with the latest versions of Chromium because Xorg is ''not'' automatically setting the DPI to 96, and Chromium is now high-DPI-sensitive. The result is really bad font and bitmap scaling on most webpages. {{unsigned|20:17, 5 June 2015‎|Silverhammermba}}

::::Having fought this problem with a gen4 Intel laptop---1280x800@14.1in LVDS---over the last two days, I reread the man page and found the newish option "ReprobeOutputs". After enabling, the driver correctly detects the panel geometry and size for slightly rectangular pixels and DPI higher than 96x96. This suggests that udev's hardware probing is failing to detect the real hardware configuration or Xorg server is failing to process the information correctly. Unfortunately neither the ati not nv drivers allow for direct reading of the EDID information and you are left to resort to the kind of monitor configuration hackery mentioned above. [[User:Vorbote|Vorbote]] ([[User talk:Vorbote|talk]]) 14:17, 7 October 2015 (UTC)

:::::I did some experiments in my Radeon HD6310 and discover somethings... lets start:
:::::* efectively, set the dpi in the xorg file is meaningless, as is ignored
:::::* set the CORRECT size for you screen, the size taked manually with rule and seting the correct resolution (if not detected) WILL affect the Xorg dpi.
:::::My monitor is 1366x768 with 309x174 millimeters, those were measured either with software and with my oun measuring rule here in RL, then I set them in Xorg and then the dpi change from 96x96 to 112x112. I use this page to help me: https://www.sven.de/dpi/
:::::{{unsigned|05:40, 19 April 2016 (UTC)|Jristz}}

::::::'''If you are having problems with Xorg DPI, be sure to check if any programs are overriding your settings.''' In my case for example: I found that Xorg actually was respecting the DisplaySize entry in the config file, but xfsettingsd (a component of xfce) was setting this back to 96 DPI immediately after I started Xorg. See https://bugzilla.xfce.org/show_bug.cgi?id=10633 for some discussion of this behavior which is hardcoded into xfsettingsd. Apparently this is their solution for dealing with the possibility of a "Screen" spanning multiple monitors, each of which may have different sizes and/or resolutions (DPI). Running xrandr --dpi XXX ''after'' xfsettingsd is started is a workaround, but I think the long-term solution is to file bugs against applications, such as evince, which are incorrectly relying on the "Screen" DPI reported by Xorg. [[User:Dc46and2|Dc46and2]] ([[User talk:Dc46and2|talk]]) 02:34, 9 June 2016 (UTC)

:::::::In July 2015, a patch was submitted to GTK3 that forces Xft.dpi to 96 whenever 'xrdb -query | grep dpi' would return a null Xft.dpi value. https://bugzilla.gnome.org/show_bug.cgi?id=757142 was filed when the impact of the change became apparent. It was immediately wontfixed. Xft.dpi is not required for Xorg functionality, being an interloper created by the Gnome people(?) as a tool to force DPI, the Gnome device for scaling its UI. The impact of this patch started to become more widely apparent when GTK3 became the default Firefox release build toolkit in 2016, most commonly among users of physical display densities between 96 and 192. I filed [https://bugzilla.mozilla.org/show_bug.cgi?id=1269274 Mozilla bug 1269274 "GTK+ 3.18 - UI text sizes no longer inherited from Linux system"] on account of this. It too was promptly wontfixed. Users of both GTK libs >3.16 and DEs that don't depend on Xft.dpi but instead utilize whatever >96 DPI logical density to which Xorg is configured find UI fonts in Firefox 46+ smaller than non-GTK3 apps, appreciably so even with configured density as low as 108 DPI. Such users not used to having Xft.dpi set, e.g. KDE users, will need to set it to match their Xorg DPI if they want supported GTK3-built Firefox (or SeaMonkey and/or Thunderbird) releases to have UI text matching their other apps. In KDE it's not a hard thing to do, because Xft.dpi is the means through which forced DPI in its systemsettings is implemented, but it will require manual intervention to keep Xorg and Xft.dpi in sync when switching among displays of different densities. Alternatively, and with other non-Gnome users, Xresources can be utilized to manage Xft.dpi, as explained on the parent page. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 06:45, 1 February 2017 (UTC)

:::::: Regarding the Xorg xft.dpi issue, the ticket is now moved to Gitlab: [https://gitlab.freedesktop.org/xorg/xserver/issues/509 See Xserver issue 509].
:::::: [[User:Danger89|Danger89]] ([[User talk:Danger89|talk]]) 15:04, 15 March 2019 (UTC)

== Add xhost si:localuser:$USER ? ==

Access to the X server is usually regulated via the hostname, so if it changes unexpectedly (e.g. see [https://bbs.archlinux.org/viewtopic.php?id=202704 BBS#202704], [[Connman#Avoid_changing_the_hostname]]), things stop working. The user name is (or should be) less prone to change, so you could use {{Pkg|xorg-xhost}} for access:

$ xhost si:localuser:$USER

man Xsecurity says on this:

localuser & localgroup
On systems which can determine in a secure fashion the credentials of a client process,
the "localuser" and "localgroup" authentication methods provide access based on those
credentials. The format of the values provided is platform specific. For POSIX & UNIX
platforms, if the value starts with the character '#', the rest of the string is treated
as a decimal uid or gid, otherwise the string is defined as a user name or group name.

If your system supports this method and you use it, be warned that some programs that
proxy connections and are setuid or setgid may get authenticated as the uid or gid of
the proxy process. For instance, some versions of ssh will be authenticated as the user
root, no matter what user is running the ssh client, so on systems with such software,
adding access for localuser:root may allow wider access than intended to the X display.

However, X apps failing is the symptom; the cause lies in [[Network configuration]], or an issue with the (static) [[hostname]] not being respected. So I'm not sure where to mention this, if at all. One way would be to expand [[Xhost]] and add a link there under [[Xorg#Troubleshooting]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:51, 21 September 2015 (UTC)

: For what it's worth using xhost is probably prefered (for example GDM does this) as xauth was mostly used in an era when hostname changing was very rare. I'm now using xhost instead of maintaining xauth along with the accompanying xauthority file which reduces quite a few dependencies on my end.

: As for where this should go? I have no idea. [[User:Earnest|Earnest]] ([[User talk:Earnest|talk]]) 23:54, 13 March 2016 (UTC)

== Location of Xorg.0.log ==

On my desktop with Gnome 3 and my laptop with KDE 5, my `Xorg.0.log` file is only located in `/var/log/Xorg.0.log`. In the article the location goes back and forth between:

/var/log/Xorg.0.log

and
~/.local/share/xorg/Xorg.0.log

There is a note at the end," `/var/log/` or, for the rootless X default since v1.16, in `~/.local/share/xorg/`". Shouldn't we pick one and put this note at the start? ---- unsigned, by [[User:Slacka]], 20170112

seconded
/var/log/Xorg.0.log
needs to be specified, im running i3wm
--[[User:Yair|Yair]] ([[User talk:Yair|talk]]) 17:21, 20 April 2018 (UTC)

== Rootless Xorg ==

Reverted edit by Alad: "useless without reference, i.e. a bug report "
And why is it not enabled without KMS in the first place? Who says problems with forced rootless xorg are a bug, and not a technical limitation by design?
[[User:Aufkrawall|Aufkrawall]] ([[User talk:Aufkrawall|talk]]) 16:14, 6 November 2017 (UTC)

:That's all vague conjectures. There's no point to relate CPU usage and KMS without the homework to prove there's an actual relation. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 16:20, 6 November 2017 (UTC)

The suggestion at https://wiki.archlinux.org/title/Xorg#Using_xinitrc does not explain why you should use {{ic|startx}} instead of {{ic|exec startx}}, which might lead to confusion among people who are new to configuring Xorg (like me). It's also suggested [https://bbs.archlinux.org/viewtopic.php?pid=1973717#p1973717/ here] that this section should be edited/moved. [[User:Garfa|Garfa]] ([[User talk:Garfa|talk]]) 17:01, 22 May 2021 (UTC)

== Remove/replace/update the xorg.conf config section? ==

"Xorg -configure" is broken since years and nvidia-xconfig creates a bunch of cruft around the Device section.
In addition static configuration and the monolithic xorg.conf are, if not even deprecated, causing trouble for unexperienced users by their unflexibility.
It is common on the bbs to ask for the log and tell forum users to remove that file to "fix" things.

Good reasons (and how) to write a server config (yourself) are indicated in the multihead and optimus articles and I'd suggest to remove that section resp. replace it by an explicit warning to refrain from overriding the autoconfig unwittingly.
Also it should be explained that "Xorg -configure" is known to be "broken" (I cannot prove it, but believe it to be "accidentally broken" as deprecated), the error is normal and you should not be using it anyway ;-)

{{unsigned|07:30, 2 April 2018‎|Seth}}

== Best place for eGPU configs ==

Greetings,
I'd like to add the following critical piece of information that's not easily available on the internet - I had to find it in the Xorg logs when run with a specific config.

To get eGPU working with external monitor and internal one disabled:
* Install the correct version and build of drivers (nvidia or nvidia-dkms or equivalent for other makes)
* Use something like the following for the Xorg config:
Section "Module"
Load "modesetting"
EndSection

Section "Device"
Identifier "nvidia"
Driver "nvidia"
BusID "PCI:6:0:0"
Option "AllowEmptyInitialConfiguration"
Option "AllowExternalGpus"
EndSection

The critical thing is the Option "AllowExternalGpus". The existence of this isn't documented on the threads on nvidia support, or on egpu.io.
First section turns off the internal display. If that's missing the systemd output will stay on screen, frozen. Nothing else is necessary, no DM config files, or nvidia-xconfig, or adding drivers to KMS, or using secure TB3 like Da_blitz's guide suggests.

This was particularly infuriating because the device is easy to work with, send CUDA processes to, and nvidia-xsettings --query-gpu-info recognizes the external monitor. Yet xrandr doesn't. And using most configs crashes Xorg with a multitude of errors, from "No screens found" to "no usable config", to "Failed to get display number from pipe". All were rabbit holes. This info needs to be out there somewhere.

Whats the best place to add this information?
I was thinking under either NVIDIA/Tips or config or Xorg/Tips or config or start a new page "External GPUs"

[[User:Snugghash|Snugghash]] ([[User talk:Snugghash|talk]]) 22:59, 10 August 2018 (UTC)

:Since it is specific to the NVIDIA driver, add it to [[NVIDIA/Tips_and_tricks]]. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 18:41, 11 August 2018 (UTC)

== systemctl --user in rootless Xorg ==

To get {{ic|systemctl --user}} to work (as well as a device management I guess) with the rootless Xorg setup, I had to edit {{ic|/etc/pam.d/system-login}} so that {{ic|pam_systemd.so}} is required (that is remove the {{ic|-}} in front of {{ic|session}} and change {{ic|optional}} to {{ic|required}}). I am not sure why this isn't the default somehow. -- [[User:Kalessin|Kalessin]] ([[User talk:Kalessin|talk]]) 19:28, 6 November 2018 (UTC)

:''to get'' {{ic|systemctl --user}} ''to work''
:not sure what you mean by that but i use ''--user'' for cron like jobs without changing {{ic|/etc/pam.d/system-login}} --[[User:Ubone|Ubone]] ([[User talk:Ubone|talk]]) 09:07, 7 November 2018 (UTC)

::I just meant any command using {{ic|systemctl --user}}.
::My comment was specific to rootless Xorg, but was edited out of its context, are you using rootless Xorg? -- [[User:Kalessin|Kalessin]] ([[User talk:Kalessin|talk]]) 17:48, 10 November 2018 (UTC)

:::yes ---[[User:Ubone|Ubone]] ([[User talk:Ubone|talk]]) 02:38, 11 November 2018 (UTC)

== XWayland ==

As discussed in [[Talk:Wayland#XWayland]], I would like to add a small section for XWayland.

Technically it is a part of the XServer, so where would you like it better, here or at [[Wayland]]?

[[User:G3ro|G3ro]] ([[User talk:G3ro|talk]]) 15:45, 17 October 2020 (UTC) G3ro

== generic video driver ==

previously under BIOS, there was the VESA graphic mode : this mode did not use all the available video capabilities but worked and often allowed to launch the graphic interface whatever the underlying video card.

VESA is no longer usable under UEFI (vesa: Refusing to run on UEFI in Xorg.0.log) : is there an equivalent for UEFI ? is it the modesetting driver (modesetting_drv.so) ?

--[[User:Lacsap|Lacsap]] ([[User talk:Lacsap|talk]]) 10:56, 21 January 2022 (UTC)

:There are multiple generic video drivers, some are mentioned in [[Xorg#Driver installation]] (including {{man|4|modesetting}}). — [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 10:28, 23 January 2022 (UTC)

== DDX/DIX ==

DDX means Device Dependent X, which basically applies to all display drivers separately packaged and specific to brand, e.g. amdgpu, intel, nouveau and radeon.

DIX means Device Independent X, and is a term which applies to the modesetting display driver, the upstream default for all GPUs for which KMS is provided.

The parent page should be edited to take this into account, applying term DIX rather than DDX when term modesetting is discussed.

{{[[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 14:57, 10 April 2025 (UTC)|14:03, 10 April 2025 (UTC)|Mrmazda}}

:"separately packaged and specific to brand" — wrong. DDX [https://www.x.org/wiki/Development/Documentation/Glossary/ means] "The part of X that interacts with the hardware". The {{ic|modesetting}} display driver interacts with the hardware using KMS, so it ''is'' DDX by definition. — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 14:12, 10 April 2025 (UTC)
::Thanks for your clarification! I didn't know what DDX actually is before. [[User:GalaxySnail|GalaxySnail]] ([[User talk:GalaxySnail|talk]]) 14:22, 10 April 2025 (UTC)
::Fun fact: [[Xwayland]] is [https://gitlab.freedesktop.org/xorg/xserver/-/commit/6e539d8817f738289dc2dea13d0720116287ab9d also DDX] — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 14:23, 10 April 2025 (UTC)

:Same URL says "DIX: Device Independent X. The part of X that interacts with clients and implements software rendering. Basically everything in the server except for the hw/ directory. The event delivery is part of the DIX." The modesetting driver is a different technology, and indifferent to who made the device or its inner workings. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 14:57, 10 April 2025 (UTC)
::Not sure what you meant to say, these quotes further confirm that modesetting is DDX. — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 15:04, 10 April 2025 (UTC)
:::Note andreymal's "means" reference was originally written in July 2013. It depends on what the quoted text is understood to mean. I read:
::::Dependent: specific to proprietary technology of the GPU brand, e.g. for AMD, for Intel, for NVidia; dependent on a specific KMS kernel module
::::Independent: not specific to proprietary technology based upon GPU brand; generic; supported by any/every kernel module providing KMS
:::There's also [https://dri.freedesktop.org/wiki/DDX/ dri/DDX] which says "The DDX drivers reside in a package called xf86-video-foo". xf86-video-modesetting was retired as of server 1.17, its content moved into the server package, functionally highlighting the independence of KMS provider distinction. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 19:55, 10 April 2025 (UTC)
::::"Dependent: specific to proprietary technology" — wrong again. There is no such definition anywhere. No one ever mentions the word "proprietary".
::::"its content moved into the server package" — this does not matter. The definitions of DDX and DIX are based on what these components do, not the packaging stuff.
::::As you can see, [https://dri.freedesktop.org/wiki/DDX/ dri/DDX] says that modesetting is "a generic DDX".
::::— [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 20:07, 10 April 2025 (UTC)
:::::"Generic" equates in some fashion or other to such terms as general purpose, common, universal and ''independent''; IOW: no specific GPU, regardless which GPU, thus independent. Your [https://www.x.org/wiki/ "means" reference] is to a wiki too, made of humans who get things wrong more than often enough. No maintainer or developer commenting in any of the Xorg, Kernel or GPU bug reports I've filed or commented over the years has tried to correct me on this. Here be the first anywhere. This wouldn't have come up if at least a decade ago Adam J, Dave A, Keith P, Daniel S or someone of their ilk had not corrected me and explained in a bug report or X mailing list somewhere, which I hope to rediscover someday (in order to have reason to return). [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 22:55, 10 April 2025 (UTC)
::::::modesetting is a ''generic'' driver that does not depend on ''specific'' hardware, but it is still ''dependent'' on hardware in general. You cannot use modesetting without a GPU; thus, it is DDX. — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 23:05, 10 April 2025 (UTC)
:::::::Indeed, '''''a''''' GPU, ''any'' GPU, is so broad an affiliation as to render the term DDX meaningless. If there is no GPU, no KMS module is applicable, nothing to setup or control. Any X display driver is simply an (generic) X display driver. If DDX means a module only applicable to a specific class of GPU, a meaningful dependency is implied. If DIX means a module that is indifferent to any GPU class, independence can be implied, with result that DDX and DIX actually provide useful meaning. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 02:25, 11 April 2025 (UTC)

== <s>XLibre</s> ==

Ok. [[User:Tatsumoto|Tatsumoto]], let's not waste our valuable breath.

Since the admin has removed the wiki page, I am proposing a change on this page such that:

# Introduces installation note of {{AUR|xlibre-xserver}} right on this page
# Redirects XLibre to Xorg

Rationale: primary executable of the XLibre project is still installed as <code>/usr/bin/Xorg</code> for compatibility reasons.

Any ideas? [[User:SH3NG1UN|SH3NG1UN]] ([[User talk:SH3NG1UN|talk]]) 13:34, 17 April 2026 (UTC)

:No. While redirecting the xlibre page ''somewhere'' would make sense, this page is not the right target: it is about the Xorg project. [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 13:51, 17 April 2026 (UTC)

::How about redirecting to [[Display server]]? Besides the obvious candidates, we could include {{AUR|arcan}} and [[Xephyr]] in such an article. Compare [[Sound system]] and [[w:List of display servers]] (though the later goes a bit above-board, including all Wayland compositors too.) -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 15:14, 17 April 2026 (UTC)
:::Just before the deletion, the article listed two ways to install Xlibre: from the AUR with an additional helper package, or from a custom repository maintained by the project's authors. I agree that this information could be moved to [[Xorg#Installation]], removing the need for a separate article, since Xlibre currently works as a drop-in replacement of Xorg. That edit would require the least effort. That said, to avoid possible confusion, it should also note that Xlibre is a distinct project and is not affiliated with freedesktop.
:::Redirecting to [[Display server]] is a good idea too, but I'm afraid it adds overhead: someone will have to populate and maintain the new page.
:::Also, I'll notify the xlibre team and ask them to tone down their homepage. [[User:Tatsumoto|Tatsumoto]] ([[User talk:Tatsumoto|talk]]) 15:43, 17 April 2026 (UTC)
:::We have a blurb about display servers in [[General_recommendations#Display_server]]. Rather than a new stub page, what about a section somewhere in [[List of applications]]? That should make the intended scope per project very clear. — [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 15:46, 17 April 2026 (UTC)
::::[[List of applications]] sounds good. The implied "recommendations" in [[General recommendations]] is not great when all we want is listing software packages. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 18:46, 17 April 2026 (UTC)
::::Can you recover the lost installation steps from the deleted article? I can't access its history anymore. The wayback machine doesn't help either, it shows an outdated snapshot. Also, where would it be appropriate to move that information? The suggested pages don't seem suitable for longer technical details, they just list available options. [[User:Tatsumoto|Tatsumoto]] ([[User talk:Tatsumoto|talk]]) 16:10, 17 April 2026 (UTC)
:::::Upstream should provide all generic info and the AUR has a pinned comment with Arch-specific details. — [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 16:16, 17 April 2026 (UTC)
::::::I edited [[General_recommendations#Display_server]]. It's better than nothing, though not ideal. Just to clarify, if Xlibre fixes the issues on their homepage that led to the deletion, could the standalone [[Xlibre]] page be restored? [[User:Tatsumoto|Tatsumoto]] ([[User talk:Tatsumoto|talk]]) 16:38, 17 April 2026 (UTC)
:::::::I mean, sure? It would just be another page at this point. Though for it to make sense as a standalone page, it should have some content. Besides the installation instructions (already in the AUR comment as pointed out above), there was only a mention about TearFree being enabled by default on some chipsets. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 18:46, 17 April 2026 (UTC)

User talk:Alad

2026-04-17T15:21:02Z

Alad: /* Please restore the Xlibre page */ re

{{Note|Consider creating a [[Help:Discussion|discussion]] on the respective article talk page before opening an item here.}}

* [https://wiki.archlinux.org/index.php?title=Special%3AWhatLinksHere&target=User+talk%3AAlad&namespace=1 WhatLinksHere (Talk)]
* [[Special:WhatLinksHere/User_talk:Alad|WhatLinksHere (all)]]

== <s>‎Mount efivarfs</s> ==

I found your comment funny since it was you who flagged that section with [[Template:Out of date]]: [[Special:Diff/489445]]. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 13:24, 28 July 2018 (UTC)

:Haha, nice one. ;) -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:45, 28 July 2018 (UTC)

== <s>[[Identify damaged files]]</s> ==

Your title is much better than mine was but in the future could you please leave more constructive edit comments? Thank you.[[User:Ksd|Ksd]] ([[User talk:Ksd|talk]]) 00:05, 20 October 2018 (UTC)

:I didn't expect a comment on this ~3 years later... but yes I will, thank you. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 10:42, 23 October 2018 (UTC)

Heh, yeah I just recently decided to come back and start updating that article again with some new info (my old user was [[User:MaBeef]]). I appreciate it and no hard feelings. -- [[User:Ksd|Ksd]] ([[User talk:Ksd|talk]]) 14:24, 23 October 2018 (UTC)

== Disable auto updates ==

Hi Alad, regarding [https://wiki.archlinux.org/index.php?title=User:Alad/common.js&curid=24159&diff=671963&oldid=671962], an empty Array won't work in all cases, I'd suggest {{ic|update_check_wdays: false}} :) [https://github.com/kynikos/wiki-monkey/blob/bcfef4fcdbbc8aced86490dd73ff6e9f9a1a6bf2/src/lib/Upgrade.js#L92] -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 04:39, 20 May 2021 (UTC)

:Thanks for the heads-up! -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 06:45, 21 May 2021 (UTC)

== Help with the Visual Studio Code page ==

Hi Alad,

I saw that you have edited the [[Visual Studio Code]] page, so maybe you can help with the disputed content. I don't know if you will agree with me or not, but I cannot be the only one discussing (and I also find it hard to discuss, it seems pointless anyway). Personally I find it important to leave the clarity on the fact that Visual Studio Code is proprietary and is different from Code OSS; but if you think differently, please do share your opinion as well. --[[User:Grufo|Grufo]] [ [[Special:Contributions/Grufo|contribs]] | [[User_talk:Grufo|talk]] ] 07:03, 4 November 2021 (UTC)

:I didn't feel the need to step in until now. Since things have turned to edit-warring, I've left some comments. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 11:28, 4 November 2021 (UTC)

:: Thank you, Alad --[[User:Grufo|Grufo]] [ [[Special:Contributions/Grufo|contribs]] | [[User_talk:Grufo|talk]] ] 15:13, 4 November 2021 (UTC)

== Oi ==

You come back on IRC right this instant. One of the wiki admins first put "Bring back alad" in the /topic, then it became "On strike until alad returns", now all the separators in the channel topic are "🍌" and just now we got another troll in -wiki and the other ops are asleep.

How dare you leave IRC!

-- [[User:NetSysFire|NetSysFire]] ([[User talk:NetSysFire|talk]]) 15:40, 2 April 2022 (UTC)

:Beautiful. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 18:16, 2 April 2022 (UTC)

== <s>About i3 gaps topic</s> ==

Hi!!!! I am a newbie in linux. Feel free to correct me if I am wrong.

I want to talk about this topic - https://wiki.archlinux.org/index.php?title=I3&diff=735587&oldid=735585

It is very important for people to know how to use i3 gaps. i3gaps is installed by default on every i3 installation. I think it really doesn't matter if it is a fork or not. I had to watch a youtube video to learn how to use i3 gaps. In the installation section it is written you can download the i3-gaps package but no one knows how to enable them. What is the point of installing i3 gaps if we don't know how to use gaps ? It would really be nice if it could be added to the archwiki :'(

-- ([[User talk:RounakDutta|Rounak Dutta]])([[User talk:RounakDutta|talk]])

:You keep saying things are "very important" in your edits, but no, this is not "very important". It's a personal preference which leads to installing a different version of i3. And more so, this alternative is mentioned right at the [[I3#Installation|beginning of the article]] - including the fact it's default when installing the i3 group. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 16:06, 30 June 2022 (UTC)

== <s>Unavailable email</s> ==

Hi! I've tried contacting you at the email reported on AUR but your server seems to be offline.
[[User:Tallero|Tallero]] ([[User talk:Tallero|talk]]) 10:05, 9 July 2022 (UTC)

:I've enabled wiki mails, so you should be able to use "Email this user" in the sidebar. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:10, 10 July 2022 (UTC)

== <s>Do you think using the AUR to install GNOME extensions is still correct and recommended nowadays?</s> ==

Hi. I know this is definitely not the best place to post this, but I don't know who else to ask for guidance with this since you're one of the few very active Wiki administrator. Read below to understand why I ended up asking here.

[[GNOME#Extensions]] has always been very inconsistent, I just noticed this by looking at the revision history. Users keep editing it and their edits contradicts with the previous edit. Before, it had instructions to install extensions from both extensions.gone.org and the AUR. Then in 2014, [https://wiki.archlinux.org/index.php?title=GNOME&diff=343937&oldid=343891 you flagged that section] to be poorly written because there were some AUR packages suggested in a bulletpoint list style, but with no description. As you can see in the edit, the person responded to your flag and updated it. However, they entirely removed the instructions to install from the AUR instead of just removing the bulletpoint list and keeping the AUR link. It stayed like that for a while, until it something similar was re-added. Someone made an edit suggesting that "using packages automates the update process," then another person replaced 'packages ' with 'pacman.' But in the official repositories there's only 1 or 2 GNOME extension(s). Thus, the AUR was entirely gotten rid of in that section, until recently I decided to re-add it after the section stayed with no AUR instructions for about 8 years. The thing is, I'm unsure of my decision of re-adding instructions for installing extensions using the AUR because apparently no one really cared about that.

I'm wondering, do you think that using AUR to install GNOME extensions is still recommended and a correct way nowadays to keep in [[GNOME#Extensions]]? Or should we get rid of it completely from that section because users abandoned it from the Wiki for 8 years straight? I'm thinking the fact that everyone is this inconsistent requires some guidance from a person who has better knowledge in this field, and I already tried the Arch forums which gave no useful answers. I would have tried to make a decision myself, but I have no idea what the reasons are for each option.

Thank you! [[User:Cont999|Cont999]] ([[User talk:Cont999|talk]]) 22:59, 16 September 2022 (UTC)

:I haven't used GNOME in years so I'm not the best person to ask. I suggest opening an item in [[Talk:GNOME]]. -- 19:25, 20 September 2022 (UTC)

::I got it. I'll ask in [[Talk:GNOME]] and I'll try to find a more concrete answer somewhere as well, just in case the discussion gets no spotlight. Thank you! [[User:Cont999|Cont999]] ([[User talk:Cont999|talk]]) 19:51, 20 September 2022 (UTC)

== Regarding a section in the system maintenance article ==

[[System_maintenance#Be_careful_with_unofficial_packages]] has the following description:

{{bc|
Use precaution when using packages from the AUR or an unofficial user repository. Most are supplied by regular users and thus may not have the same standards as those in the official repositories. Avoid AUR helpers which automate installation of AUR packages. Always check PKGBUILDs for sanity and signs of mistake or malicious code before building and/or installing the package.

To simplify maintenance, limit the amount of unofficial packages used. Make periodic checks on which are in actual use, and remove (or replace with their official counterparts) any others. See pacman/Tips and tricks#Maintenance for useful commands. Following system upgrade, use rebuild-detector to identify any unofficial packages that may need to be rebuilt.
}}

Since you're one of the last people to edit that section in particular, I thought I'd ask you for your advice since you'd have a solid understanding of its meaning.

The sentence talking about simplifying maintenance by limiting the amount of unofficial packages used seems kind of vague,
{{bc|
To simplify maintenance, limit the amount of unofficial packages used. Make periodic checks on which are in actual use, and remove (or replace with their official counterparts) any others.
}}

I'm not sure if it's just me (because English is not my first language), but reading it gives me two meanings:

1- To simplify maintenance, limit the amount of AUR packages by removing unused ones.
* '''''(in other words: you can install as many AUR packages as you'd like, but check every now and then to get rid of any AUR packages that aren't being used anymore)'''''

2- To simplify maintenance, limit the amount of AUR packages by not installing many of them in the first place AND by removing unused ones.
* '''''(in other words: try to be conservative with the number of AUR packages you install, and check every now and then to get rid of any AUR packages that aren't being used anymore)'''''

Which meaning is that specific statement trying to express? Do you think a very slight edit of the current description to clear up this confusion is needed?

Thanks! [[User:Cont999|Cont999]] ([[User talk:Cont999|talk]]) 13:24, 1 October 2022 (UTC)

:I'm not sure I see the confusion - the "''by not installing many of them''" part is covered by "''limit the amount of unofficial packages used.''" phrase. The next phrase complements this by giving the advice to check if installed AUR packages are no longer needed.
:In other words, if "Make periodic checks on which are in actual use, and remove (or replace with their official counterparts) any others." were the only phrase in that paragraph it might be vague. However, the general advice on limiting the amount of AUR packages is mentioned right before. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 00:01, 8 October 2022 (UTC)

== Ifs and whethers ==

Hi,

You have reverted the edits that replace some "if"s with "whether"s. The article you have linked to seems to be consistent with the edits (from the article: "an indirect question involving two stated or ''implied'' ''possibilities'' or alternatives"). While it is true that none of the particular ifs represent choices/alternatives, they represent a possibility of two states. For example, the sentence "check if this is the case" implies that it ''may'' or ''may not'' be the case. Using "whether or not" in that sentence does not break it, and neither does it alter the meaning; it breaks the grammar or changes the meaning only in sentences where "whether" is not applicable. This is also consistent with examples from the Cambridge English Corpus.

Sorry for breaking the subsection. I forgot that something else may be referring to it.

[[User:Xayiver|Xayiver]] ([[User talk:Xayiver|talk]]) 13:44, 19 October 2022 (UTC)

:I don't see the improvement of using "whether" here. Without choices/alternatives, it's merely longer than "if" and is less readable to me. See also [[User_talk:Jasonwryan#Doubt_regarding_revert]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 19:45, 19 October 2022 (UTC)

::I understand. It is not strictly an improvement in readability, and making the wiki read like a research paper is perhaps not urgent. The rampant run-on sentences are what concerns readability and needs addressing instead. [[User:Xayiver|Xayiver]] ([[User talk:Xayiver|talk]]) 04:29, 20 October 2022 (UTC)

== <s>Secure Shell Page</s> ==

Hello,

I noticed the following edit made by you nearly 4 years ago within this page flagging it for merge: [https://wiki.archlinux.org/index.php?title=Secure_Shell&diff=573632&oldid=572872]

Firstly, I have a reason it should not be merged, and thus I believe it should be unflagged. Not all pages deserve to be merged because they are small, but software pages like these are useful, and being able to list all the secure shell software is useful to some people looking for OpenSSH alternatives.

This should also be added as a link into [[List of applications]] for those looking for alternative SSH software, instead of making OpenSSH seem like the only software.

Let me know if you still disagree, [[User:PolarianDev|PolarianDev]] ([[User talk:PolarianDev|talk]]) 13:30, 11 May 2023 (UTC)

:That page is little more than a disambiguation page, and I've made my opinion on those clear: [[Category talk:Disambiguation pages#Remove category]]. It's not even a useful disambiguation, since [https://pkgstats.archlinux.de/packages/openssh 99.01% of readers] will be looking for {{Pkg|openssh}}. Adding hoops just because 0.99% might use an alternative is pointless. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 03:50, 12 May 2023 (UTC)

== AUR helpers rollback ==

Hello Alad,

Could you please clarify why my changes to the [[AUR helpers]] page were rolled back without any comments?

Is there a specific policy that I might have overlooked which restricts such edits?

Here are the changes I made:

* Updated the information that aura is now written in Rust, not Haskell, with a provided source.
* Noted that aura supports building in a clean chroot, with a provided source.
* Added a column listing "clean chroot" as an ability, since it's now a common feature among several tools.
* Reorganized the table layout to fit better in Firefox on a 1920x1080 screen, addressing the overlap with the tools on the right. Additionally, I included features like "fetch PGP keys" and "support batch operations" which seem more logically listed as features.

I followed the guideline "Do not make complex edits at once" from [[ArchWiki:Contributing]] and believe my changes neither "radically restructured" nor "rewrote the article", which would require a discussion on the talk page. Additionally, I ensured to use the edit summary properly, according to "properly use the edit summary".

Could you please provide more details on why all of these changes were reverted?

Thank you.

Best regards,
--[[User:RubenKelevra|RubenKelevra]] ([[User talk:RubenKelevra|talk]]) 10:18, 31 July 2024 (UTC)

:[[AUR helpers]] has a Note at the top of the page saying you should discuss edits to the page first. This was introduced after misinformation was added to the page repeatedly (AUR helper authors adding wrong claims about their products) and as an alternative to protecting the page. I suggest you thus add your points to [[Talk:AUR helpers]] before making edits. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:58, 31 July 2024 (UTC)

::I added the first two bullets. The other two bullets are non-trivial and should be discussed in [[Talk:AUR helpers]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:26, 10 August 2024 (UTC)

== Multiple environment variables in .desktop entry ==

Hello Alan,

and thank you for cleaning up the clutter of my edit in the [[MATLAB]] page.

Your summary on that last edit ([https://wiki.archlinux.org/index.php?title=MATLAB&diff=815248&oldid=815063]) left me perplexed honestly. The reason I wrote that extra section was exactly because - from what I've read and tried so far - you can't set more than one environment variables in the same .desktop file. If you can do it, can you please clarify how, possibly by providing an example?

[[User:Enf|Enf]] ([[User talk:Enf|talk]]) 10:10, 26 August 2024 (UTC)

:{{ic|1=env FOO=1 BAR=2 ...}} -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:43, 9 September 2024 (UTC)

== <s> archinstall rollback </s> ==

Hello Alad,

Could you please clarify why my changes to the [[Install Arch Linux with menu-guided archinstall]]/[[archinstall]] page were rolled back without any comments?

Is there a specific policy that I might have overlooked which restricts such edits?

Here are the changes I made:

* I moved it to Install Arch Linux with menu-guided archinstall

I also saw the move tag and thought, I could move it and make it redirect, if I was wrong, I apologize for that, and please let me know what went wrong.

I followed the guideline "Do not make complex edits at once" from [[ArchWiki:Contributing]] and believe my changes neither "radically restructured" nor "rewrote the article", which would require a discussion on the talk page. Additionally, I ensured to use the edit summary properly, according to "properly use the edit summary".

Could you please provide more details on why all of these changes were reverted?

Thank you.

Best regards,
[[User:Matthewq337|Matthewq337]] ([[User talk:Matthewq337|talk]]) 20:01, 19 June 2025 (UTC)

:Comments are here: [[Talk:Installation guide#After section 1.4 (Boot the live media), there should be a mention of archinstall]] — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 20:38, 19 June 2025 (UTC)

== <s>Please restore the Xlibre page</s> ==

The reason given states: The Xlibre project goes against [https://terms.archlinux.org/docs/code-of-conduct/#respect respect] and should not be listed on ArchWiki. See [https://x11libre.net/#about about].

The deletion appears to be vandalism. Nothing on Xlibre's About page violates the ArchWiki respect policy. The project states that it respects everyone. If you believe the About page needs changes, raise the issue on the article's Discussion page first.

As an Arch Linux user and a contributor to that Wiki page, I've never encountered such blatant discrimination. I feels really bad to have your work removed like that.

Gentoo has a Wiki page about Xlibre [https://wiki.gentoo.org/wiki/Xlibre here]. They don't seem to have any problems with the project. Artix also has a [https://wiki.artixlinux.org/Site/XlibreOnArtix Wiki page]. Recently, Artix announced that [https://artixlinux.org/news.php#Switching_to_XLibre XLibre is now the default X server in Artix Linux].

Arch Linux should follow. Including Xlibre in the official repositories is already long overdue,
given that other distros have already done so. There's a huge demand, given that Xorg doesn't get new features anymore, and hasn't been for 15 years. [[User:Tatsumoto|Tatsumoto]] ([[User talk:Tatsumoto|talk]]) 02:34, 17 April 2026 (UTC)

:I assume the problem here is the lead developer's political views however from a quick look at the page before it was removed none of that was carried over to the wiki artcile. It is also worth noting that Arch already packages in its offical repositories and mentions on its wiki many packages tied to specifc groups not everyone aligns with and those users may simply ignore them.
:h [[User:Knotrocket|Knotrocket]] ([[User talk:Knotrocket|talk]]) 03:05, 17 April 2026 (UTC)
::I don't agree with the lead developer's political views but I see their views having very little to do with their project and about page, plus providing information on the project on the wiki doesn't take any political stances to begin with, one can discuss a project without that automatically meaning an endorsement of everything the author has ever said and done [[User:Ammonium|Ammonium]] ([[User talk:Ammonium|talk]]) 05:17, 17 April 2026 (UTC)
: Even if the accusation of the Xlibre's is substantiated, deleting the page has ''zero'' effect in mitigating the issue. However, it does have a direct effect to create troubles for Arch (and other distros') users when searching for information. If people can accept the logic of deleting a project description page based on it being "disrespectful", then whoever proposed the deletion should be sanctioned for the disrespect of community members who are using this project. --[[User:Yangwenbo99|Yangwenbo99]] ([[User talk:Yangwenbo99|talk]]) 06:12, 17 April 2026 (UTC)
:I agree with the fact the page needs to be restored. The wiki is not about politics or personal beliefs. The wiki is about preservation and the presentation of valid information needed to show and guide users to packages that are available either from the AUR or the main repos.
:We have already had several pages defaced and restored by contributors for many reasons, such as fixing the ZFS pages to restore information about using tools already included with zfsutils rather than a pet project from a 3rd party repo not even in the AUR or wiki itself. Work that mind you, took me the better course of a few months to get back and clean up, and the work is still ongoing.
:While all of us share many beliefs and personal political views, we leave that outside the door when we come here to contribute. Nothing about Xlibre has been shown to be in violation of the CoC of ArchLinux. The people who have made packages or contributed time and efforts to the page have clearly had their work defaced and destroyed just to appease some petty political view that is not reflective of the general consensus here. Basically, the ArchWiki is apolitical. This is adding politics and is a clear violation of the CoC in and of itself for even presenting it as such. [[User:ReaperX7|ReaperX7]] ([[User talk:ReaperX7|talk]]) 06:49, 17 April 2026 (UTC)
:agree with everyone else here that advocates for its restoration. if solely disagreeing with someones/not liking them is enough reason for a article deletion we might as well delete 99% of all articles not written by a single person. ideological purism is unattainable and quite frankly goes against Archlinux own principle of [[Arch Linux#Pragmatism|Pragmatism]].
:"'''Arch is a pragmatic distribution rather than an ideological one'''—the principles here are only useful guidelines. Ultimately, design decisions are made on a case-by-case basis through developer consensus. '''Evidence-based technical analysis and debate are what matter, not politics or popular opinion.'''" [[User:Supernova|Supernova]] ([[User talk:Supernova|talk]]) 07:25, 17 April 2026 (UTC)
::Exactly. A lot of people use the wiki and not just Arch, or Arch based distributions like Manjaro, Artix, or any spinoffs of theirs. People from even Slackware, Gentoo, and other distributions reference the ArchWiki due to its extensive topics, coverage, and availability.
::By deleting the Xlibre page, this basically is hurting not just Arch, but users in general from accessibility to information.
::If Alad has an issue with the page, then simply don't visit it, contribute to it, or bother with it. Many people don't agree with ZFS in a GNU/Linux system, but we have a full set of pages that clearly show you how to literally take the GPL license and flush it in favor of your own tastes. Does everyone visit it? No. Does everyone contribute to it? No just a few of us who have taken the time to research it for our own needs to help others. So how is Xlibre any different? [[User:ReaperX7|ReaperX7]] ([[User talk:ReaperX7|talk]]) 09:19, 17 April 2026 (UTC)

General comment since I'm not going through this whole mess: in the 10 odd years I've been here, not a single project was allowed that officially took the stance of being inflammatory, sparking controversy, and just being plain disrepectful. It's not because a specific project has a particularly vocal fanbase that any exceptions should be made on this regard. Closing -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 09:26, 17 April 2026 (UTC)

:"General comment since I'm not going through this whole mess: "
:Translation: "I'm the problem here and I have the agenda." [[User:Msoltyspl|Msoltyspl]] ([[User talk:Msoltyspl|talk]]) 09:50, 17 April 2026 (UTC)
:I understand the concern, but the project in question has no alternatives right now, so users need information about it on the Wiki. I'm not a fan of any particular project, I just want a working system. Wayland cannot replace X11 yet, Xorg isn't getting new features anymore, Phoenix and Wayback aren't ready either. Please say what needs changing on the [https://x11libre.net/#about about page] you linked for the article to be restored. I'm going to pass that to xlibre's maintainers. [[User:Tatsumoto|Tatsumoto]] ([[User talk:Tatsumoto|talk]]) 09:55, 17 April 2026 (UTC)

::Since you seem to be the sole reasonable person in this discussion - the original article contained little more than an installation notice. How about some historical notice is added in [[Xorg]] that explains the origination of the fork?
::As to the about page - while wiki pages serve purely as documentation, ArchWiki has a certain reputation. In particular, the mere presence of an article here can be seen as an endorsement for the documented project. And such an endorsement includes, in particular, what the project writes on their homepage.
::Removing the Xlibre article may not be the perfect solution, but it seems like the only choice we have if the project's page is that expressive about the malice regarding Xorg. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 10:26, 17 April 2026 (UTC)
:::"the mere presence of an article here can be seen as an endorsement for the documented project. And such an endorsement includes, in particular, what the project writes on their homepage."
:::in no world does a simple wiki article imply endorsement. Do you think wikipedia endorses all topic it has an article about? I think its total unreasonable to delete a notice about a project simply because you interpret "malice" towards another project. [[User:Supernova|Supernova]] ([[User talk:Supernova|talk]]) 10:33, 17 April 2026 (UTC)
:::You're arguing a strawman at this point. Xlibre is a fork of Xorg, and honestly, leave it at that. We have. Your turn. Nobody cares what the developer feels is his personal business. It's not yours, mine, or our business to be his critic or anyone else's. ArchWiki is also not Wikipedia. Apples and oranges comparison.
:::Again, leave the software as it is, apolitical and leave the Wiki as apolitical as possible also. I don't bring or invite my views in here and neither does anyone else.
:::If that was the case, many pages like Wine, ZFS, the various GNU projects, and others would be out due to their authors being just as inflammatory.
:::No, you defaced the page on purpose to cite a personal beef and it needs to be restored. If you want to flaunt the CoC then please check yourself before you tout it as such because you blatantly violated it wholely by being political. You dragged politics into a topic and you're called out on it. You need to fix this and rectify the deletion of this page, and if needed, restore it, or we can edit the Xorg page and add the necessary entries to show a compare and contrast between the two branches. [[User:ReaperX7|ReaperX7]] ([[User talk:ReaperX7|talk]]) 12:22, 17 April 2026 (UTC)
:::On second thought, you're right that their homepage is inflammatory. It's full of hostility toward the Xorg Foundation and freedesktop.org and can be uncomfortable to read. It should be factual, technical, and neutral.
:::If possible, I suggest:
:::* Restore the Xlibre wiki page with a clear disclaimer stating we do not share the project's beliefs, and optionally note which beliefs are rejected.
:::* Contact the project and ask them to make their homepage professional and neutral instead of inflammatory.
:::* If they ignore the request to tone it down, I guess pursue the only remaining choice.
:::I think it would be inappropriate to write about Xlibre on the Xorg page since they're different projects, and that would cause confusion. But if the Xlibre page is restored, it could be listed as an alternative to Xorg. [[User:Tatsumoto|Tatsumoto]] ([[User talk:Tatsumoto|talk]]) 12:30, 17 April 2026 (UTC)
::::Thanks. On the suggestions:
::::* Keeping the page with a banner will likely result in the same kind of discussions we have now.
::::* Someone is welcome to contact the project and update us on the results here.
::::* This seems the most likely outcome. Or you'll get a reply that matches the kind of comments that flooded my talk page.
::::Mind that even if these points were addressed, the article had little more than an installation notice. If listing it in [[Xorg]] is confusing, we can consider a more abstract category - something like [[Display server]], similar to [[Sound system]]. Though with [[Mir]] abandoned, there's far less options to choose from there... edit: there is also {{AUR|arcan}}. We could also include things like [[Xephyr]] in the page, similar to [[w:List of display servers]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:43, 17 April 2026 (UTC)
:::::i think most people here would be more than fine with a simple "Archlinux does not agree/endorse xlibre's opinion" notice instead of full on deletion. [[User:Supernova|Supernova]] ([[User talk:Supernova|talk]]) 15:09, 17 April 2026 (UTC)
:::::Just leaving my two cents here: restoring the page with a banner disclaiming any potential endorsement of political beliefs is 100% A-OK with me. My only grievance is with the personal beliefs-fueled suppression of a genuinely valuable page on the wiki, not with anyone disagreeing politically with anyone.
:::::I have a feeling that this is a take that a lot of people will also agree with, this is not a "pitchforking riot" as you seem to subtly imply, politics has nothing to do with this. Maybe more people can contribute to this conversation, but so far assuming that a banner is not a viable solution because "people will riot anyways" is not very logical given the current arguments people have brought up [[User:Ammonium|Ammonium]] ([[User talk:Ammonium|talk]]) 15:11, 17 April 2026 (UTC)
:::::If you didn't want people flooding your talk page then why didn't you put a deletion template on the article and post your resoning on its talk page instead? [[User:Knotrocket|Knotrocket]] ([[User talk:Knotrocket|talk]]) 15:12, 17 April 2026 (UTC)
::::::Deletion templates are not suitable for rules infractions. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 15:20, 17 April 2026 (UTC)

:::I wish you can calm down and reflect on the facts. You are the only person behaving unreasonably throughout the while discussion. Your deletion of the page started the drama and it's a blatant disrespecl to Arch users using Xlibre and a potential challenge to the pragmatic principle of Arch Linux. [[User:Yangwenbo99|Yangwenbo99]] ([[User talk:Yangwenbo99|talk]]) 14:24, 17 April 2026 (UTC)

:"not a single project was allowed that officially took the stance of being inflammatory, sparking controversy"
:So now simply "sparking controversy" is enough to justify deleting knowledge and destroying contributors effort. What project articles that are "controversial and inflammatory" in your opinion will be deleted by you next?
:bcachefs article because of there controversies in the LKML?
:linux kernel article because of linus torvalds inflammatory comments such as "fuck nvidia"?
:to be clear i am NOT a fan of xlibre, i don't even use it. i have been using wayland for many years and see no reason to change that but this behavior is quite disappointing. [[User:Supernova|Supernova]] ([[User talk:Supernova|talk]]) 10:13, 17 April 2026 (UTC)
:I am deeply saddened by such a dismissive and hostile reply from such a figure in the Arch Linux community.
:First you dismiss every person with a valid request about wanting the information about how to install a software to remain available in a wiki as you're "not gonna read through this whole mess", and *then* you insult everyone understandably and validly expressing this, as calling someone you reply to "the sole reasonable person in this discussion".
:This shows a clear act of ignorance and dismissiveness to the needs and wants of the community, putting your own personal beliefs over what might benefit the community most.
:I am going to repeat myself just so you don't label me as "unreasonable" again like you did with all the other members of this discussion: *I do not agree with the political beliefs of the Xlibre author*. However, I don't see what this has to do with the matter at hand. In my opinion, allowing a wiki article should not be about "do I agree with the political beliefs of the original author and every single thing they have ever said", but just if said article is genuinely useful information to provide to the community. [[User:Ammonium|Ammonium]] ([[User talk:Ammonium|talk]]) 14:11, 17 April 2026 (UTC)

== <s>More XLibre Vandalism</s> ==

Hey can we all just universally agree that randomly deleting articles and tutorials for XLibre is completely utterly frustrating?

I really can't stand Wayland, I really wanted to checkout this new fork as I love X11, but NO.

Even in ArchWiki! ARCH!!! There's rogue admins with some childish vendetta against their dev team over some political nonsense that's presumably happening in the states. Newsflash I'm AUSTALIAN! I DON'T GAF!!! I'm just an END USER!

Let me follow the guides to compile and load the damn thing! Do I really have to start mirroring these tutorials on my forum just so everybody else can just get by? Seriously? [[User:Kippykip|Kippykip]] ([[User talk:Kippykip|talk]]) 08:36, 17 April 2026 (UTC)

:The central point must be kept clear: we are dealing with things of different natures, and mixing them leads to confused decisions.
:There is a real difference between political discourse and code. Political discourse carries intentions, values, and direct effects on people and groups. It can, in itself, offend, exclude, mobilize actions, or even demobilize actions through mechanisms historically well known. Code does not function this way. It is another kind of language structure: it does not argue, it does not persuade, it does not express positions. It executes. It is a restricted language, aimed at making things work in a simple, direct, and operational way.
:When we think about political movements with execrable far-right tendencies, the problem is not only in practical actions, but in the discourse itself. The discourse is already part of the practice, in an imbricated and inseparable way: it carries, in itself, exclusion, attack, or denial of certain groups. In this case, there is no clear separation between what is said and what is done. Saying is already a form of doing.
:With code, this does not happen. Code does not have this type of content and does not operate on that level. There is nothing within it that is equivalent to this kind of discourse, neither explicitly nor subliminally. A programming language, such as the one used in Xlibre, does not, in itself, have any structure capable of conveying hate speech. Its meaning lies in its function, not in the expression of values.
:This brings us back to the initial point: not every language functions in the same way. Some languages are oriented toward describing, arguing, and influencing, while others are oriented toward operating and making systems work. The mistake begins when we treat one as if it were the other, as if code could carry, in itself, the same kind of content as political discourse. For this reason, it is necessary to separate two things in this case. On one side, the code itself. On the other, the opinions or attitudes of those who develop it.
:In the case of Xlibre, the criticism is not directed at the code or the technical documentation, but at external positions taken by developers. This is a criterion that does not belong to the object that the Wiki should be evaluating.
:Then the problem arises: if this becomes the standard, where does it stop? Will it be necessary to investigate every project, every developer, every “About” page to decide whether something can or cannot be documented? This is not consistently applicable. It becomes selective, reactive, and inevitably arbitrary, in addition to conflicting with the very nature of language as described above.
:Furthermore, a technical Wiki is not a space for political endorsement. It exists to document. To document is not to agree, not to support, not to promote. It is simply to record useful information for those who use the system.
:When a page that fulfills this role is removed for reasons external to its content, what is lost is not only a specific article, but a principle. The principle that technical criteria should be evaluated on technical grounds.
:On the other hand, this does not prevent anyone from criticizing the project, its developers, or their positions. Such criticism is valid and necessary. However, it belongs in another space. In a broader sense, mixing these domains weakens both: criticism loses focus, and documentation loses consistency in its purpose.
:That said, if the Xlibre page on the Arch Wiki is technical, informative, and does not contain offensive content, there is no coherent reason for its removal. In order to maintain clear and consistent criteria regarding code, to assist users, and nothing beyond that, it should be restored.
:Criticism should be made where it belongs. It is necessary to preserve the freedom to use code, which is a fundamental principle of GNU/Linux. This is a freedom that is not merely formal, but lived and practiced. A freedom that is strengthened precisely when it confronts us with what we disagree with.
:Those who truly value freedom do not defend it only in the comfort of agreement, but also in the confrontation with dissent. It is in this confrontation that freedom becomes concrete, demanding positioning, action, and growth. There is also a direct relationship between loving freedom and being willing to fight for it. The more one recognizes the value of freedom, the more one develops the willingness to defend it in practice.
:And this defense is not carried out through erasure or technical exclusion, but through conscious action. Criticism should take place directly, in appropriate spaces: in public debate, in mobilizations, in affinity groups, and in the streets. That is how one confronts, in a concrete way, any authoritarian tendency or model that threatens the existence of people. Not by erasing technical documentation, but by acting where the problem truly lies. [[User:Italomourag|Italomourag]] ([[User talk:Italomourag|talk]]) 11:29, 17 April 2026 (UTC)

Talk:Xorg

2026-04-17T15:16:00Z

Alad: /* XLibre */ clarify

== Setting DPI manually ==

I'm not an Archlinux user, but Google sends me to this Wiki often. As a non-user, I cannot confirm this error on Archlinux unless I find time to learn how to install it. That's unlikely to happen in the foreseeable future.

The example 'Option "DPI" "96 x 96"' is invalid, because 96 x 96 is forced by the Xorg Xserver to start with as default to match Mac and Windows.

Unless the Archlinux X servers are different from other distros I've used, Option "DPI" "120 x 120" and others (144, 192, 108, etc) AFAICT only work for users of proprietary NVidia drivers, fail for certain on MGA (e.g. G400), Intel (e.g. 810, 845, 865, 915, 945, 3000, 4000), Radeon (e.g. rv200, rv250, rv380) & Nouveau (e.g. nv11, G84) on openSUSE 12.2, openSUSE 13.1, Fedora 20 and Mageia 4. I've been using Xorg for many many years and have never yet found any version in which this option is valid using any of the 4 FOSS drivers indicated. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 05:25, 10 December 2013 (UTC)

:As you probably noticed, [[Xorg#Display_size_and_DPI]] is marked as inaccurate with links to several bug reports about Xorg forcing 96x96. Part of Arch's philosophy is to avoid patching of packages whenever possible, but I see that {{Pkg|xorg-server}} uses several patches (see [https://github.com/archlinux/svntogit-packages/blob/packages/xorg-server/trunk]). I don't know which patches other distros use, but this option is not likely to depend on the patches.
:Anyway, if you know a functioning method of manually setting DPI, feel free to share it - even a link to external documentation might be better than the current inaccurate information.
:-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:34, 10 December 2013 (UTC)

::As help situations arise I point people to my http://fm.no-ip.com/Share/DisplaySize which is mostly a lookup table designed to avoid need to calculate values for DisplaySize that will produce a desired DPI. DisplaySize in 'Section "Monitor"' has been reliable long-term with non-broken drivers, but since KScreen was released last summer, a workaround is required to get xorg.conf* to be obeyed at all by KDE. According to [https://bugs.kde.org/show_bug.cgi?id=317929#c13 Alex Fiestas, KScreen 1.1 is proposed to allow xorg.conf* to be obeyed by default on single display systems]. The workaround is to put [Module-kscreen]\nautoload=false in kdmrc. Whether other DEs have similar obstacles I have no idea. It would really be nice for those only wishing to force the hardware native DPI instead of an arbitrary one (which is usually what 96 is) for https://bugs.freedesktop.org/show_bug.cgi?id=41115 to be fixed, which means letting the server automatically as it already knows how make logical and physical DPI match. http://www.gentoo-wiki.info/HOWTO_Set_DPI_Dots_Per_Inch is one place that shows how to perform the calculations.

::"To reduce scaling artifacts to GUI that use bitmaps" is not the only reason to choose +25% steps (96, 120, 144, 168, 192...). Most scalable fonts are tuned to 96 DPI, and step from pixel size to pixel size best at specific steps, of which +25% are the best. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]])

:::I question the validity of the claim that Xorg always sets the DPI to 96 mainly because of this issue: https://bbs.archlinux.org/viewtopic.php?id=197624. Quite a lot of people are having problems with the latest versions of Chromium because Xorg is ''not'' automatically setting the DPI to 96, and Chromium is now high-DPI-sensitive. The result is really bad font and bitmap scaling on most webpages. {{unsigned|20:17, 5 June 2015‎|Silverhammermba}}

::::Having fought this problem with a gen4 Intel laptop---1280x800@14.1in LVDS---over the last two days, I reread the man page and found the newish option "ReprobeOutputs". After enabling, the driver correctly detects the panel geometry and size for slightly rectangular pixels and DPI higher than 96x96. This suggests that udev's hardware probing is failing to detect the real hardware configuration or Xorg server is failing to process the information correctly. Unfortunately neither the ati not nv drivers allow for direct reading of the EDID information and you are left to resort to the kind of monitor configuration hackery mentioned above. [[User:Vorbote|Vorbote]] ([[User talk:Vorbote|talk]]) 14:17, 7 October 2015 (UTC)

:::::I did some experiments in my Radeon HD6310 and discover somethings... lets start:
:::::* efectively, set the dpi in the xorg file is meaningless, as is ignored
:::::* set the CORRECT size for you screen, the size taked manually with rule and seting the correct resolution (if not detected) WILL affect the Xorg dpi.
:::::My monitor is 1366x768 with 309x174 millimeters, those were measured either with software and with my oun measuring rule here in RL, then I set them in Xorg and then the dpi change from 96x96 to 112x112. I use this page to help me: https://www.sven.de/dpi/
:::::{{unsigned|05:40, 19 April 2016 (UTC)|Jristz}}

::::::'''If you are having problems with Xorg DPI, be sure to check if any programs are overriding your settings.''' In my case for example: I found that Xorg actually was respecting the DisplaySize entry in the config file, but xfsettingsd (a component of xfce) was setting this back to 96 DPI immediately after I started Xorg. See https://bugzilla.xfce.org/show_bug.cgi?id=10633 for some discussion of this behavior which is hardcoded into xfsettingsd. Apparently this is their solution for dealing with the possibility of a "Screen" spanning multiple monitors, each of which may have different sizes and/or resolutions (DPI). Running xrandr --dpi XXX ''after'' xfsettingsd is started is a workaround, but I think the long-term solution is to file bugs against applications, such as evince, which are incorrectly relying on the "Screen" DPI reported by Xorg. [[User:Dc46and2|Dc46and2]] ([[User talk:Dc46and2|talk]]) 02:34, 9 June 2016 (UTC)

:::::::In July 2015, a patch was submitted to GTK3 that forces Xft.dpi to 96 whenever 'xrdb -query | grep dpi' would return a null Xft.dpi value. https://bugzilla.gnome.org/show_bug.cgi?id=757142 was filed when the impact of the change became apparent. It was immediately wontfixed. Xft.dpi is not required for Xorg functionality, being an interloper created by the Gnome people(?) as a tool to force DPI, the Gnome device for scaling its UI. The impact of this patch started to become more widely apparent when GTK3 became the default Firefox release build toolkit in 2016, most commonly among users of physical display densities between 96 and 192. I filed [https://bugzilla.mozilla.org/show_bug.cgi?id=1269274 Mozilla bug 1269274 "GTK+ 3.18 - UI text sizes no longer inherited from Linux system"] on account of this. It too was promptly wontfixed. Users of both GTK libs >3.16 and DEs that don't depend on Xft.dpi but instead utilize whatever >96 DPI logical density to which Xorg is configured find UI fonts in Firefox 46+ smaller than non-GTK3 apps, appreciably so even with configured density as low as 108 DPI. Such users not used to having Xft.dpi set, e.g. KDE users, will need to set it to match their Xorg DPI if they want supported GTK3-built Firefox (or SeaMonkey and/or Thunderbird) releases to have UI text matching their other apps. In KDE it's not a hard thing to do, because Xft.dpi is the means through which forced DPI in its systemsettings is implemented, but it will require manual intervention to keep Xorg and Xft.dpi in sync when switching among displays of different densities. Alternatively, and with other non-Gnome users, Xresources can be utilized to manage Xft.dpi, as explained on the parent page. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 06:45, 1 February 2017 (UTC)

:::::: Regarding the Xorg xft.dpi issue, the ticket is now moved to Gitlab: [https://gitlab.freedesktop.org/xorg/xserver/issues/509 See Xserver issue 509].
:::::: [[User:Danger89|Danger89]] ([[User talk:Danger89|talk]]) 15:04, 15 March 2019 (UTC)

== Add xhost si:localuser:$USER ? ==

Access to the X server is usually regulated via the hostname, so if it changes unexpectedly (e.g. see [https://bbs.archlinux.org/viewtopic.php?id=202704 BBS#202704], [[Connman#Avoid_changing_the_hostname]]), things stop working. The user name is (or should be) less prone to change, so you could use {{Pkg|xorg-xhost}} for access:

$ xhost si:localuser:$USER

man Xsecurity says on this:

localuser & localgroup
On systems which can determine in a secure fashion the credentials of a client process,
the "localuser" and "localgroup" authentication methods provide access based on those
credentials. The format of the values provided is platform specific. For POSIX & UNIX
platforms, if the value starts with the character '#', the rest of the string is treated
as a decimal uid or gid, otherwise the string is defined as a user name or group name.

If your system supports this method and you use it, be warned that some programs that
proxy connections and are setuid or setgid may get authenticated as the uid or gid of
the proxy process. For instance, some versions of ssh will be authenticated as the user
root, no matter what user is running the ssh client, so on systems with such software,
adding access for localuser:root may allow wider access than intended to the X display.

However, X apps failing is the symptom; the cause lies in [[Network configuration]], or an issue with the (static) [[hostname]] not being respected. So I'm not sure where to mention this, if at all. One way would be to expand [[Xhost]] and add a link there under [[Xorg#Troubleshooting]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:51, 21 September 2015 (UTC)

: For what it's worth using xhost is probably prefered (for example GDM does this) as xauth was mostly used in an era when hostname changing was very rare. I'm now using xhost instead of maintaining xauth along with the accompanying xauthority file which reduces quite a few dependencies on my end.

: As for where this should go? I have no idea. [[User:Earnest|Earnest]] ([[User talk:Earnest|talk]]) 23:54, 13 March 2016 (UTC)

== Location of Xorg.0.log ==

On my desktop with Gnome 3 and my laptop with KDE 5, my `Xorg.0.log` file is only located in `/var/log/Xorg.0.log`. In the article the location goes back and forth between:

/var/log/Xorg.0.log

and
~/.local/share/xorg/Xorg.0.log

There is a note at the end," `/var/log/` or, for the rootless X default since v1.16, in `~/.local/share/xorg/`". Shouldn't we pick one and put this note at the start? ---- unsigned, by [[User:Slacka]], 20170112

seconded
/var/log/Xorg.0.log
needs to be specified, im running i3wm
--[[User:Yair|Yair]] ([[User talk:Yair|talk]]) 17:21, 20 April 2018 (UTC)

== Rootless Xorg ==

Reverted edit by Alad: "useless without reference, i.e. a bug report "
And why is it not enabled without KMS in the first place? Who says problems with forced rootless xorg are a bug, and not a technical limitation by design?
[[User:Aufkrawall|Aufkrawall]] ([[User talk:Aufkrawall|talk]]) 16:14, 6 November 2017 (UTC)

:That's all vague conjectures. There's no point to relate CPU usage and KMS without the homework to prove there's an actual relation. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 16:20, 6 November 2017 (UTC)

The suggestion at https://wiki.archlinux.org/title/Xorg#Using_xinitrc does not explain why you should use {{ic|startx}} instead of {{ic|exec startx}}, which might lead to confusion among people who are new to configuring Xorg (like me). It's also suggested [https://bbs.archlinux.org/viewtopic.php?pid=1973717#p1973717/ here] that this section should be edited/moved. [[User:Garfa|Garfa]] ([[User talk:Garfa|talk]]) 17:01, 22 May 2021 (UTC)

== Remove/replace/update the xorg.conf config section? ==

"Xorg -configure" is broken since years and nvidia-xconfig creates a bunch of cruft around the Device section.
In addition static configuration and the monolithic xorg.conf are, if not even deprecated, causing trouble for unexperienced users by their unflexibility.
It is common on the bbs to ask for the log and tell forum users to remove that file to "fix" things.

Good reasons (and how) to write a server config (yourself) are indicated in the multihead and optimus articles and I'd suggest to remove that section resp. replace it by an explicit warning to refrain from overriding the autoconfig unwittingly.
Also it should be explained that "Xorg -configure" is known to be "broken" (I cannot prove it, but believe it to be "accidentally broken" as deprecated), the error is normal and you should not be using it anyway ;-)

{{unsigned|07:30, 2 April 2018‎|Seth}}

== Best place for eGPU configs ==

Greetings,
I'd like to add the following critical piece of information that's not easily available on the internet - I had to find it in the Xorg logs when run with a specific config.

To get eGPU working with external monitor and internal one disabled:
* Install the correct version and build of drivers (nvidia or nvidia-dkms or equivalent for other makes)
* Use something like the following for the Xorg config:
Section "Module"
Load "modesetting"
EndSection

Section "Device"
Identifier "nvidia"
Driver "nvidia"
BusID "PCI:6:0:0"
Option "AllowEmptyInitialConfiguration"
Option "AllowExternalGpus"
EndSection

The critical thing is the Option "AllowExternalGpus". The existence of this isn't documented on the threads on nvidia support, or on egpu.io.
First section turns off the internal display. If that's missing the systemd output will stay on screen, frozen. Nothing else is necessary, no DM config files, or nvidia-xconfig, or adding drivers to KMS, or using secure TB3 like Da_blitz's guide suggests.

This was particularly infuriating because the device is easy to work with, send CUDA processes to, and nvidia-xsettings --query-gpu-info recognizes the external monitor. Yet xrandr doesn't. And using most configs crashes Xorg with a multitude of errors, from "No screens found" to "no usable config", to "Failed to get display number from pipe". All were rabbit holes. This info needs to be out there somewhere.

Whats the best place to add this information?
I was thinking under either NVIDIA/Tips or config or Xorg/Tips or config or start a new page "External GPUs"

[[User:Snugghash|Snugghash]] ([[User talk:Snugghash|talk]]) 22:59, 10 August 2018 (UTC)

:Since it is specific to the NVIDIA driver, add it to [[NVIDIA/Tips_and_tricks]]. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 18:41, 11 August 2018 (UTC)

== systemctl --user in rootless Xorg ==

To get {{ic|systemctl --user}} to work (as well as a device management I guess) with the rootless Xorg setup, I had to edit {{ic|/etc/pam.d/system-login}} so that {{ic|pam_systemd.so}} is required (that is remove the {{ic|-}} in front of {{ic|session}} and change {{ic|optional}} to {{ic|required}}). I am not sure why this isn't the default somehow. -- [[User:Kalessin|Kalessin]] ([[User talk:Kalessin|talk]]) 19:28, 6 November 2018 (UTC)

:''to get'' {{ic|systemctl --user}} ''to work''
:not sure what you mean by that but i use ''--user'' for cron like jobs without changing {{ic|/etc/pam.d/system-login}} --[[User:Ubone|Ubone]] ([[User talk:Ubone|talk]]) 09:07, 7 November 2018 (UTC)

::I just meant any command using {{ic|systemctl --user}}.
::My comment was specific to rootless Xorg, but was edited out of its context, are you using rootless Xorg? -- [[User:Kalessin|Kalessin]] ([[User talk:Kalessin|talk]]) 17:48, 10 November 2018 (UTC)

:::yes ---[[User:Ubone|Ubone]] ([[User talk:Ubone|talk]]) 02:38, 11 November 2018 (UTC)

== XWayland ==

As discussed in [[Talk:Wayland#XWayland]], I would like to add a small section for XWayland.

Technically it is a part of the XServer, so where would you like it better, here or at [[Wayland]]?

[[User:G3ro|G3ro]] ([[User talk:G3ro|talk]]) 15:45, 17 October 2020 (UTC) G3ro

== generic video driver ==

previously under BIOS, there was the VESA graphic mode : this mode did not use all the available video capabilities but worked and often allowed to launch the graphic interface whatever the underlying video card.

VESA is no longer usable under UEFI (vesa: Refusing to run on UEFI in Xorg.0.log) : is there an equivalent for UEFI ? is it the modesetting driver (modesetting_drv.so) ?

--[[User:Lacsap|Lacsap]] ([[User talk:Lacsap|talk]]) 10:56, 21 January 2022 (UTC)

:There are multiple generic video drivers, some are mentioned in [[Xorg#Driver installation]] (including {{man|4|modesetting}}). — [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 10:28, 23 January 2022 (UTC)

== DDX/DIX ==

DDX means Device Dependent X, which basically applies to all display drivers separately packaged and specific to brand, e.g. amdgpu, intel, nouveau and radeon.

DIX means Device Independent X, and is a term which applies to the modesetting display driver, the upstream default for all GPUs for which KMS is provided.

The parent page should be edited to take this into account, applying term DIX rather than DDX when term modesetting is discussed.

{{[[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 14:57, 10 April 2025 (UTC)|14:03, 10 April 2025 (UTC)|Mrmazda}}

:"separately packaged and specific to brand" — wrong. DDX [https://www.x.org/wiki/Development/Documentation/Glossary/ means] "The part of X that interacts with the hardware". The {{ic|modesetting}} display driver interacts with the hardware using KMS, so it ''is'' DDX by definition. — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 14:12, 10 April 2025 (UTC)
::Thanks for your clarification! I didn't know what DDX actually is before. [[User:GalaxySnail|GalaxySnail]] ([[User talk:GalaxySnail|talk]]) 14:22, 10 April 2025 (UTC)
::Fun fact: [[Xwayland]] is [https://gitlab.freedesktop.org/xorg/xserver/-/commit/6e539d8817f738289dc2dea13d0720116287ab9d also DDX] — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 14:23, 10 April 2025 (UTC)

:Same URL says "DIX: Device Independent X. The part of X that interacts with clients and implements software rendering. Basically everything in the server except for the hw/ directory. The event delivery is part of the DIX." The modesetting driver is a different technology, and indifferent to who made the device or its inner workings. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 14:57, 10 April 2025 (UTC)
::Not sure what you meant to say, these quotes further confirm that modesetting is DDX. — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 15:04, 10 April 2025 (UTC)
:::Note andreymal's "means" reference was originally written in July 2013. It depends on what the quoted text is understood to mean. I read:
::::Dependent: specific to proprietary technology of the GPU brand, e.g. for AMD, for Intel, for NVidia; dependent on a specific KMS kernel module
::::Independent: not specific to proprietary technology based upon GPU brand; generic; supported by any/every kernel module providing KMS
:::There's also [https://dri.freedesktop.org/wiki/DDX/ dri/DDX] which says "The DDX drivers reside in a package called xf86-video-foo". xf86-video-modesetting was retired as of server 1.17, its content moved into the server package, functionally highlighting the independence of KMS provider distinction. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 19:55, 10 April 2025 (UTC)
::::"Dependent: specific to proprietary technology" — wrong again. There is no such definition anywhere. No one ever mentions the word "proprietary".
::::"its content moved into the server package" — this does not matter. The definitions of DDX and DIX are based on what these components do, not the packaging stuff.
::::As you can see, [https://dri.freedesktop.org/wiki/DDX/ dri/DDX] says that modesetting is "a generic DDX".
::::— [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 20:07, 10 April 2025 (UTC)
:::::"Generic" equates in some fashion or other to such terms as general purpose, common, universal and ''independent''; IOW: no specific GPU, regardless which GPU, thus independent. Your [https://www.x.org/wiki/ "means" reference] is to a wiki too, made of humans who get things wrong more than often enough. No maintainer or developer commenting in any of the Xorg, Kernel or GPU bug reports I've filed or commented over the years has tried to correct me on this. Here be the first anywhere. This wouldn't have come up if at least a decade ago Adam J, Dave A, Keith P, Daniel S or someone of their ilk had not corrected me and explained in a bug report or X mailing list somewhere, which I hope to rediscover someday (in order to have reason to return). [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 22:55, 10 April 2025 (UTC)
::::::modesetting is a ''generic'' driver that does not depend on ''specific'' hardware, but it is still ''dependent'' on hardware in general. You cannot use modesetting without a GPU; thus, it is DDX. — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 23:05, 10 April 2025 (UTC)
:::::::Indeed, '''''a''''' GPU, ''any'' GPU, is so broad an affiliation as to render the term DDX meaningless. If there is no GPU, no KMS module is applicable, nothing to setup or control. Any X display driver is simply an (generic) X display driver. If DDX means a module only applicable to a specific class of GPU, a meaningful dependency is implied. If DIX means a module that is indifferent to any GPU class, independence can be implied, with result that DDX and DIX actually provide useful meaning. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 02:25, 11 April 2025 (UTC)

== <s>XLibre</s> ==

Ok. [[User:Tatsumoto|Tatsumoto]], let's not waste our valuable breath.

Since the admin has removed the wiki page, I am proposing a change on this page such that:

# Introduces installation note of {{AUR|xlibre-xserver}} right on this page
# Redirects XLibre to Xorg

Rationale: primary executable of the XLibre project is still installed as <code>/usr/bin/Xorg</code> for compatibility reasons.

Any ideas? [[User:SH3NG1UN|SH3NG1UN]] ([[User talk:SH3NG1UN|talk]]) 13:34, 17 April 2026 (UTC)

:No. While redirecting the xlibre page ''somewhere'' would make sense, this page is not the right target: it is about the Xorg project. [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 13:51, 17 April 2026 (UTC)

::How about redirecting to [[Display server]]? Besides the obvious candidates, we could include {{AUR|arcan}} and [[Xephyr]] in such an article. Compare [[Sound system]] and [[w:List of display servers]] (though the later goes a bit above-board, including all Wayland compositors too.) -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 15:14, 17 April 2026 (UTC)

Talk:Xorg

2026-04-17T15:14:59Z

Alad: /* XLibre */ re

== Setting DPI manually ==

I'm not an Archlinux user, but Google sends me to this Wiki often. As a non-user, I cannot confirm this error on Archlinux unless I find time to learn how to install it. That's unlikely to happen in the foreseeable future.

The example 'Option "DPI" "96 x 96"' is invalid, because 96 x 96 is forced by the Xorg Xserver to start with as default to match Mac and Windows.

Unless the Archlinux X servers are different from other distros I've used, Option "DPI" "120 x 120" and others (144, 192, 108, etc) AFAICT only work for users of proprietary NVidia drivers, fail for certain on MGA (e.g. G400), Intel (e.g. 810, 845, 865, 915, 945, 3000, 4000), Radeon (e.g. rv200, rv250, rv380) & Nouveau (e.g. nv11, G84) on openSUSE 12.2, openSUSE 13.1, Fedora 20 and Mageia 4. I've been using Xorg for many many years and have never yet found any version in which this option is valid using any of the 4 FOSS drivers indicated. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 05:25, 10 December 2013 (UTC)

:As you probably noticed, [[Xorg#Display_size_and_DPI]] is marked as inaccurate with links to several bug reports about Xorg forcing 96x96. Part of Arch's philosophy is to avoid patching of packages whenever possible, but I see that {{Pkg|xorg-server}} uses several patches (see [https://github.com/archlinux/svntogit-packages/blob/packages/xorg-server/trunk]). I don't know which patches other distros use, but this option is not likely to depend on the patches.
:Anyway, if you know a functioning method of manually setting DPI, feel free to share it - even a link to external documentation might be better than the current inaccurate information.
:-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:34, 10 December 2013 (UTC)

::As help situations arise I point people to my http://fm.no-ip.com/Share/DisplaySize which is mostly a lookup table designed to avoid need to calculate values for DisplaySize that will produce a desired DPI. DisplaySize in 'Section "Monitor"' has been reliable long-term with non-broken drivers, but since KScreen was released last summer, a workaround is required to get xorg.conf* to be obeyed at all by KDE. According to [https://bugs.kde.org/show_bug.cgi?id=317929#c13 Alex Fiestas, KScreen 1.1 is proposed to allow xorg.conf* to be obeyed by default on single display systems]. The workaround is to put [Module-kscreen]\nautoload=false in kdmrc. Whether other DEs have similar obstacles I have no idea. It would really be nice for those only wishing to force the hardware native DPI instead of an arbitrary one (which is usually what 96 is) for https://bugs.freedesktop.org/show_bug.cgi?id=41115 to be fixed, which means letting the server automatically as it already knows how make logical and physical DPI match. http://www.gentoo-wiki.info/HOWTO_Set_DPI_Dots_Per_Inch is one place that shows how to perform the calculations.

::"To reduce scaling artifacts to GUI that use bitmaps" is not the only reason to choose +25% steps (96, 120, 144, 168, 192...). Most scalable fonts are tuned to 96 DPI, and step from pixel size to pixel size best at specific steps, of which +25% are the best. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]])

:::I question the validity of the claim that Xorg always sets the DPI to 96 mainly because of this issue: https://bbs.archlinux.org/viewtopic.php?id=197624. Quite a lot of people are having problems with the latest versions of Chromium because Xorg is ''not'' automatically setting the DPI to 96, and Chromium is now high-DPI-sensitive. The result is really bad font and bitmap scaling on most webpages. {{unsigned|20:17, 5 June 2015‎|Silverhammermba}}

::::Having fought this problem with a gen4 Intel laptop---1280x800@14.1in LVDS---over the last two days, I reread the man page and found the newish option "ReprobeOutputs". After enabling, the driver correctly detects the panel geometry and size for slightly rectangular pixels and DPI higher than 96x96. This suggests that udev's hardware probing is failing to detect the real hardware configuration or Xorg server is failing to process the information correctly. Unfortunately neither the ati not nv drivers allow for direct reading of the EDID information and you are left to resort to the kind of monitor configuration hackery mentioned above. [[User:Vorbote|Vorbote]] ([[User talk:Vorbote|talk]]) 14:17, 7 October 2015 (UTC)

:::::I did some experiments in my Radeon HD6310 and discover somethings... lets start:
:::::* efectively, set the dpi in the xorg file is meaningless, as is ignored
:::::* set the CORRECT size for you screen, the size taked manually with rule and seting the correct resolution (if not detected) WILL affect the Xorg dpi.
:::::My monitor is 1366x768 with 309x174 millimeters, those were measured either with software and with my oun measuring rule here in RL, then I set them in Xorg and then the dpi change from 96x96 to 112x112. I use this page to help me: https://www.sven.de/dpi/
:::::{{unsigned|05:40, 19 April 2016 (UTC)|Jristz}}

::::::'''If you are having problems with Xorg DPI, be sure to check if any programs are overriding your settings.''' In my case for example: I found that Xorg actually was respecting the DisplaySize entry in the config file, but xfsettingsd (a component of xfce) was setting this back to 96 DPI immediately after I started Xorg. See https://bugzilla.xfce.org/show_bug.cgi?id=10633 for some discussion of this behavior which is hardcoded into xfsettingsd. Apparently this is their solution for dealing with the possibility of a "Screen" spanning multiple monitors, each of which may have different sizes and/or resolutions (DPI). Running xrandr --dpi XXX ''after'' xfsettingsd is started is a workaround, but I think the long-term solution is to file bugs against applications, such as evince, which are incorrectly relying on the "Screen" DPI reported by Xorg. [[User:Dc46and2|Dc46and2]] ([[User talk:Dc46and2|talk]]) 02:34, 9 June 2016 (UTC)

:::::::In July 2015, a patch was submitted to GTK3 that forces Xft.dpi to 96 whenever 'xrdb -query | grep dpi' would return a null Xft.dpi value. https://bugzilla.gnome.org/show_bug.cgi?id=757142 was filed when the impact of the change became apparent. It was immediately wontfixed. Xft.dpi is not required for Xorg functionality, being an interloper created by the Gnome people(?) as a tool to force DPI, the Gnome device for scaling its UI. The impact of this patch started to become more widely apparent when GTK3 became the default Firefox release build toolkit in 2016, most commonly among users of physical display densities between 96 and 192. I filed [https://bugzilla.mozilla.org/show_bug.cgi?id=1269274 Mozilla bug 1269274 "GTK+ 3.18 - UI text sizes no longer inherited from Linux system"] on account of this. It too was promptly wontfixed. Users of both GTK libs >3.16 and DEs that don't depend on Xft.dpi but instead utilize whatever >96 DPI logical density to which Xorg is configured find UI fonts in Firefox 46+ smaller than non-GTK3 apps, appreciably so even with configured density as low as 108 DPI. Such users not used to having Xft.dpi set, e.g. KDE users, will need to set it to match their Xorg DPI if they want supported GTK3-built Firefox (or SeaMonkey and/or Thunderbird) releases to have UI text matching their other apps. In KDE it's not a hard thing to do, because Xft.dpi is the means through which forced DPI in its systemsettings is implemented, but it will require manual intervention to keep Xorg and Xft.dpi in sync when switching among displays of different densities. Alternatively, and with other non-Gnome users, Xresources can be utilized to manage Xft.dpi, as explained on the parent page. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 06:45, 1 February 2017 (UTC)

:::::: Regarding the Xorg xft.dpi issue, the ticket is now moved to Gitlab: [https://gitlab.freedesktop.org/xorg/xserver/issues/509 See Xserver issue 509].
:::::: [[User:Danger89|Danger89]] ([[User talk:Danger89|talk]]) 15:04, 15 March 2019 (UTC)

== Add xhost si:localuser:$USER ? ==

Access to the X server is usually regulated via the hostname, so if it changes unexpectedly (e.g. see [https://bbs.archlinux.org/viewtopic.php?id=202704 BBS#202704], [[Connman#Avoid_changing_the_hostname]]), things stop working. The user name is (or should be) less prone to change, so you could use {{Pkg|xorg-xhost}} for access:

$ xhost si:localuser:$USER

man Xsecurity says on this:

localuser & localgroup
On systems which can determine in a secure fashion the credentials of a client process,
the "localuser" and "localgroup" authentication methods provide access based on those
credentials. The format of the values provided is platform specific. For POSIX & UNIX
platforms, if the value starts with the character '#', the rest of the string is treated
as a decimal uid or gid, otherwise the string is defined as a user name or group name.

If your system supports this method and you use it, be warned that some programs that
proxy connections and are setuid or setgid may get authenticated as the uid or gid of
the proxy process. For instance, some versions of ssh will be authenticated as the user
root, no matter what user is running the ssh client, so on systems with such software,
adding access for localuser:root may allow wider access than intended to the X display.

However, X apps failing is the symptom; the cause lies in [[Network configuration]], or an issue with the (static) [[hostname]] not being respected. So I'm not sure where to mention this, if at all. One way would be to expand [[Xhost]] and add a link there under [[Xorg#Troubleshooting]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:51, 21 September 2015 (UTC)

: For what it's worth using xhost is probably prefered (for example GDM does this) as xauth was mostly used in an era when hostname changing was very rare. I'm now using xhost instead of maintaining xauth along with the accompanying xauthority file which reduces quite a few dependencies on my end.

: As for where this should go? I have no idea. [[User:Earnest|Earnest]] ([[User talk:Earnest|talk]]) 23:54, 13 March 2016 (UTC)

== Location of Xorg.0.log ==

On my desktop with Gnome 3 and my laptop with KDE 5, my `Xorg.0.log` file is only located in `/var/log/Xorg.0.log`. In the article the location goes back and forth between:

/var/log/Xorg.0.log

and
~/.local/share/xorg/Xorg.0.log

There is a note at the end," `/var/log/` or, for the rootless X default since v1.16, in `~/.local/share/xorg/`". Shouldn't we pick one and put this note at the start? ---- unsigned, by [[User:Slacka]], 20170112

seconded
/var/log/Xorg.0.log
needs to be specified, im running i3wm
--[[User:Yair|Yair]] ([[User talk:Yair|talk]]) 17:21, 20 April 2018 (UTC)

== Rootless Xorg ==

Reverted edit by Alad: "useless without reference, i.e. a bug report "
And why is it not enabled without KMS in the first place? Who says problems with forced rootless xorg are a bug, and not a technical limitation by design?
[[User:Aufkrawall|Aufkrawall]] ([[User talk:Aufkrawall|talk]]) 16:14, 6 November 2017 (UTC)

:That's all vague conjectures. There's no point to relate CPU usage and KMS without the homework to prove there's an actual relation. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 16:20, 6 November 2017 (UTC)

The suggestion at https://wiki.archlinux.org/title/Xorg#Using_xinitrc does not explain why you should use {{ic|startx}} instead of {{ic|exec startx}}, which might lead to confusion among people who are new to configuring Xorg (like me). It's also suggested [https://bbs.archlinux.org/viewtopic.php?pid=1973717#p1973717/ here] that this section should be edited/moved. [[User:Garfa|Garfa]] ([[User talk:Garfa|talk]]) 17:01, 22 May 2021 (UTC)

== Remove/replace/update the xorg.conf config section? ==

"Xorg -configure" is broken since years and nvidia-xconfig creates a bunch of cruft around the Device section.
In addition static configuration and the monolithic xorg.conf are, if not even deprecated, causing trouble for unexperienced users by their unflexibility.
It is common on the bbs to ask for the log and tell forum users to remove that file to "fix" things.

Good reasons (and how) to write a server config (yourself) are indicated in the multihead and optimus articles and I'd suggest to remove that section resp. replace it by an explicit warning to refrain from overriding the autoconfig unwittingly.
Also it should be explained that "Xorg -configure" is known to be "broken" (I cannot prove it, but believe it to be "accidentally broken" as deprecated), the error is normal and you should not be using it anyway ;-)

{{unsigned|07:30, 2 April 2018‎|Seth}}

== Best place for eGPU configs ==

Greetings,
I'd like to add the following critical piece of information that's not easily available on the internet - I had to find it in the Xorg logs when run with a specific config.

To get eGPU working with external monitor and internal one disabled:
* Install the correct version and build of drivers (nvidia or nvidia-dkms or equivalent for other makes)
* Use something like the following for the Xorg config:
Section "Module"
Load "modesetting"
EndSection

Section "Device"
Identifier "nvidia"
Driver "nvidia"
BusID "PCI:6:0:0"
Option "AllowEmptyInitialConfiguration"
Option "AllowExternalGpus"
EndSection

The critical thing is the Option "AllowExternalGpus". The existence of this isn't documented on the threads on nvidia support, or on egpu.io.
First section turns off the internal display. If that's missing the systemd output will stay on screen, frozen. Nothing else is necessary, no DM config files, or nvidia-xconfig, or adding drivers to KMS, or using secure TB3 like Da_blitz's guide suggests.

This was particularly infuriating because the device is easy to work with, send CUDA processes to, and nvidia-xsettings --query-gpu-info recognizes the external monitor. Yet xrandr doesn't. And using most configs crashes Xorg with a multitude of errors, from "No screens found" to "no usable config", to "Failed to get display number from pipe". All were rabbit holes. This info needs to be out there somewhere.

Whats the best place to add this information?
I was thinking under either NVIDIA/Tips or config or Xorg/Tips or config or start a new page "External GPUs"

[[User:Snugghash|Snugghash]] ([[User talk:Snugghash|talk]]) 22:59, 10 August 2018 (UTC)

:Since it is specific to the NVIDIA driver, add it to [[NVIDIA/Tips_and_tricks]]. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 18:41, 11 August 2018 (UTC)

== systemctl --user in rootless Xorg ==

To get {{ic|systemctl --user}} to work (as well as a device management I guess) with the rootless Xorg setup, I had to edit {{ic|/etc/pam.d/system-login}} so that {{ic|pam_systemd.so}} is required (that is remove the {{ic|-}} in front of {{ic|session}} and change {{ic|optional}} to {{ic|required}}). I am not sure why this isn't the default somehow. -- [[User:Kalessin|Kalessin]] ([[User talk:Kalessin|talk]]) 19:28, 6 November 2018 (UTC)

:''to get'' {{ic|systemctl --user}} ''to work''
:not sure what you mean by that but i use ''--user'' for cron like jobs without changing {{ic|/etc/pam.d/system-login}} --[[User:Ubone|Ubone]] ([[User talk:Ubone|talk]]) 09:07, 7 November 2018 (UTC)

::I just meant any command using {{ic|systemctl --user}}.
::My comment was specific to rootless Xorg, but was edited out of its context, are you using rootless Xorg? -- [[User:Kalessin|Kalessin]] ([[User talk:Kalessin|talk]]) 17:48, 10 November 2018 (UTC)

:::yes ---[[User:Ubone|Ubone]] ([[User talk:Ubone|talk]]) 02:38, 11 November 2018 (UTC)

== XWayland ==

As discussed in [[Talk:Wayland#XWayland]], I would like to add a small section for XWayland.

Technically it is a part of the XServer, so where would you like it better, here or at [[Wayland]]?

[[User:G3ro|G3ro]] ([[User talk:G3ro|talk]]) 15:45, 17 October 2020 (UTC) G3ro

== generic video driver ==

previously under BIOS, there was the VESA graphic mode : this mode did not use all the available video capabilities but worked and often allowed to launch the graphic interface whatever the underlying video card.

VESA is no longer usable under UEFI (vesa: Refusing to run on UEFI in Xorg.0.log) : is there an equivalent for UEFI ? is it the modesetting driver (modesetting_drv.so) ?

--[[User:Lacsap|Lacsap]] ([[User talk:Lacsap|talk]]) 10:56, 21 January 2022 (UTC)

:There are multiple generic video drivers, some are mentioned in [[Xorg#Driver installation]] (including {{man|4|modesetting}}). — [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 10:28, 23 January 2022 (UTC)

== DDX/DIX ==

DDX means Device Dependent X, which basically applies to all display drivers separately packaged and specific to brand, e.g. amdgpu, intel, nouveau and radeon.

DIX means Device Independent X, and is a term which applies to the modesetting display driver, the upstream default for all GPUs for which KMS is provided.

The parent page should be edited to take this into account, applying term DIX rather than DDX when term modesetting is discussed.

{{[[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 14:57, 10 April 2025 (UTC)|14:03, 10 April 2025 (UTC)|Mrmazda}}

:"separately packaged and specific to brand" — wrong. DDX [https://www.x.org/wiki/Development/Documentation/Glossary/ means] "The part of X that interacts with the hardware". The {{ic|modesetting}} display driver interacts with the hardware using KMS, so it ''is'' DDX by definition. — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 14:12, 10 April 2025 (UTC)
::Thanks for your clarification! I didn't know what DDX actually is before. [[User:GalaxySnail|GalaxySnail]] ([[User talk:GalaxySnail|talk]]) 14:22, 10 April 2025 (UTC)
::Fun fact: [[Xwayland]] is [https://gitlab.freedesktop.org/xorg/xserver/-/commit/6e539d8817f738289dc2dea13d0720116287ab9d also DDX] — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 14:23, 10 April 2025 (UTC)

:Same URL says "DIX: Device Independent X. The part of X that interacts with clients and implements software rendering. Basically everything in the server except for the hw/ directory. The event delivery is part of the DIX." The modesetting driver is a different technology, and indifferent to who made the device or its inner workings. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 14:57, 10 April 2025 (UTC)
::Not sure what you meant to say, these quotes further confirm that modesetting is DDX. — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 15:04, 10 April 2025 (UTC)
:::Note andreymal's "means" reference was originally written in July 2013. It depends on what the quoted text is understood to mean. I read:
::::Dependent: specific to proprietary technology of the GPU brand, e.g. for AMD, for Intel, for NVidia; dependent on a specific KMS kernel module
::::Independent: not specific to proprietary technology based upon GPU brand; generic; supported by any/every kernel module providing KMS
:::There's also [https://dri.freedesktop.org/wiki/DDX/ dri/DDX] which says "The DDX drivers reside in a package called xf86-video-foo". xf86-video-modesetting was retired as of server 1.17, its content moved into the server package, functionally highlighting the independence of KMS provider distinction. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 19:55, 10 April 2025 (UTC)
::::"Dependent: specific to proprietary technology" — wrong again. There is no such definition anywhere. No one ever mentions the word "proprietary".
::::"its content moved into the server package" — this does not matter. The definitions of DDX and DIX are based on what these components do, not the packaging stuff.
::::As you can see, [https://dri.freedesktop.org/wiki/DDX/ dri/DDX] says that modesetting is "a generic DDX".
::::— [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 20:07, 10 April 2025 (UTC)
:::::"Generic" equates in some fashion or other to such terms as general purpose, common, universal and ''independent''; IOW: no specific GPU, regardless which GPU, thus independent. Your [https://www.x.org/wiki/ "means" reference] is to a wiki too, made of humans who get things wrong more than often enough. No maintainer or developer commenting in any of the Xorg, Kernel or GPU bug reports I've filed or commented over the years has tried to correct me on this. Here be the first anywhere. This wouldn't have come up if at least a decade ago Adam J, Dave A, Keith P, Daniel S or someone of their ilk had not corrected me and explained in a bug report or X mailing list somewhere, which I hope to rediscover someday (in order to have reason to return). [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 22:55, 10 April 2025 (UTC)
::::::modesetting is a ''generic'' driver that does not depend on ''specific'' hardware, but it is still ''dependent'' on hardware in general. You cannot use modesetting without a GPU; thus, it is DDX. — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 23:05, 10 April 2025 (UTC)
:::::::Indeed, '''''a''''' GPU, ''any'' GPU, is so broad an affiliation as to render the term DDX meaningless. If there is no GPU, no KMS module is applicable, nothing to setup or control. Any X display driver is simply an (generic) X display driver. If DDX means a module only applicable to a specific class of GPU, a meaningful dependency is implied. If DIX means a module that is indifferent to any GPU class, independence can be implied, with result that DDX and DIX actually provide useful meaning. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 02:25, 11 April 2025 (UTC)

== <s>XLibre</s> ==

Ok. [[User:Tatsumoto|Tatsumoto]], let's not waste our valuable breath.

Since the admin has removed the wiki page, I am proposing a change on this page such that:

# Introduces installation note of {{AUR|xlibre-xserver}} right on this page
# Redirects XLibre to Xorg

Rationale: primary executable of the XLibre project is still installed as <code>/usr/bin/Xorg</code> for compatibility reasons.

Any ideas? [[User:SH3NG1UN|SH3NG1UN]] ([[User talk:SH3NG1UN|talk]]) 13:34, 17 April 2026 (UTC)

:No. While redirecting the xlibre page ''somewhere'' would make sense, this page is not the right target: it is about the Xorg project. [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 13:51, 17 April 2026 (UTC)

::How about [[Display server]]? Besides the obvious candidates, we could include {{AUR|arcan}} and [[Xephyr]]. Compare [[w:List of display servers]] (though that one goes a bit above-board, including all Wayland compositors too.) -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 15:14, 17 April 2026 (UTC)

User talk:Alad

2026-04-17T14:49:54Z

Alad: /* Please restore the Xlibre page */ edit

{{Note|Consider creating a [[Help:Discussion|discussion]] on the respective article talk page before opening an item here.}}

* [https://wiki.archlinux.org/index.php?title=Special%3AWhatLinksHere&target=User+talk%3AAlad&namespace=1 WhatLinksHere (Talk)]
* [[Special:WhatLinksHere/User_talk:Alad|WhatLinksHere (all)]]

== <s>‎Mount efivarfs</s> ==

I found your comment funny since it was you who flagged that section with [[Template:Out of date]]: [[Special:Diff/489445]]. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 13:24, 28 July 2018 (UTC)

:Haha, nice one. ;) -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:45, 28 July 2018 (UTC)

== <s>[[Identify damaged files]]</s> ==

Your title is much better than mine was but in the future could you please leave more constructive edit comments? Thank you.[[User:Ksd|Ksd]] ([[User talk:Ksd|talk]]) 00:05, 20 October 2018 (UTC)

:I didn't expect a comment on this ~3 years later... but yes I will, thank you. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 10:42, 23 October 2018 (UTC)

Heh, yeah I just recently decided to come back and start updating that article again with some new info (my old user was [[User:MaBeef]]). I appreciate it and no hard feelings. -- [[User:Ksd|Ksd]] ([[User talk:Ksd|talk]]) 14:24, 23 October 2018 (UTC)

== Disable auto updates ==

Hi Alad, regarding [https://wiki.archlinux.org/index.php?title=User:Alad/common.js&curid=24159&diff=671963&oldid=671962], an empty Array won't work in all cases, I'd suggest {{ic|update_check_wdays: false}} :) [https://github.com/kynikos/wiki-monkey/blob/bcfef4fcdbbc8aced86490dd73ff6e9f9a1a6bf2/src/lib/Upgrade.js#L92] -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 04:39, 20 May 2021 (UTC)

:Thanks for the heads-up! -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 06:45, 21 May 2021 (UTC)

== Help with the Visual Studio Code page ==

Hi Alad,

I saw that you have edited the [[Visual Studio Code]] page, so maybe you can help with the disputed content. I don't know if you will agree with me or not, but I cannot be the only one discussing (and I also find it hard to discuss, it seems pointless anyway). Personally I find it important to leave the clarity on the fact that Visual Studio Code is proprietary and is different from Code OSS; but if you think differently, please do share your opinion as well. --[[User:Grufo|Grufo]] [ [[Special:Contributions/Grufo|contribs]] | [[User_talk:Grufo|talk]] ] 07:03, 4 November 2021 (UTC)

:I didn't feel the need to step in until now. Since things have turned to edit-warring, I've left some comments. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 11:28, 4 November 2021 (UTC)

:: Thank you, Alad --[[User:Grufo|Grufo]] [ [[Special:Contributions/Grufo|contribs]] | [[User_talk:Grufo|talk]] ] 15:13, 4 November 2021 (UTC)

== Oi ==

You come back on IRC right this instant. One of the wiki admins first put "Bring back alad" in the /topic, then it became "On strike until alad returns", now all the separators in the channel topic are "🍌" and just now we got another troll in -wiki and the other ops are asleep.

How dare you leave IRC!

-- [[User:NetSysFire|NetSysFire]] ([[User talk:NetSysFire|talk]]) 15:40, 2 April 2022 (UTC)

:Beautiful. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 18:16, 2 April 2022 (UTC)

== <s>About i3 gaps topic</s> ==

Hi!!!! I am a newbie in linux. Feel free to correct me if I am wrong.

I want to talk about this topic - https://wiki.archlinux.org/index.php?title=I3&diff=735587&oldid=735585

It is very important for people to know how to use i3 gaps. i3gaps is installed by default on every i3 installation. I think it really doesn't matter if it is a fork or not. I had to watch a youtube video to learn how to use i3 gaps. In the installation section it is written you can download the i3-gaps package but no one knows how to enable them. What is the point of installing i3 gaps if we don't know how to use gaps ? It would really be nice if it could be added to the archwiki :'(

-- ([[User talk:RounakDutta|Rounak Dutta]])([[User talk:RounakDutta|talk]])

:You keep saying things are "very important" in your edits, but no, this is not "very important". It's a personal preference which leads to installing a different version of i3. And more so, this alternative is mentioned right at the [[I3#Installation|beginning of the article]] - including the fact it's default when installing the i3 group. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 16:06, 30 June 2022 (UTC)

== <s>Unavailable email</s> ==

Hi! I've tried contacting you at the email reported on AUR but your server seems to be offline.
[[User:Tallero|Tallero]] ([[User talk:Tallero|talk]]) 10:05, 9 July 2022 (UTC)

:I've enabled wiki mails, so you should be able to use "Email this user" in the sidebar. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:10, 10 July 2022 (UTC)

== <s>Do you think using the AUR to install GNOME extensions is still correct and recommended nowadays?</s> ==

Hi. I know this is definitely not the best place to post this, but I don't know who else to ask for guidance with this since you're one of the few very active Wiki administrator. Read below to understand why I ended up asking here.

[[GNOME#Extensions]] has always been very inconsistent, I just noticed this by looking at the revision history. Users keep editing it and their edits contradicts with the previous edit. Before, it had instructions to install extensions from both extensions.gone.org and the AUR. Then in 2014, [https://wiki.archlinux.org/index.php?title=GNOME&diff=343937&oldid=343891 you flagged that section] to be poorly written because there were some AUR packages suggested in a bulletpoint list style, but with no description. As you can see in the edit, the person responded to your flag and updated it. However, they entirely removed the instructions to install from the AUR instead of just removing the bulletpoint list and keeping the AUR link. It stayed like that for a while, until it something similar was re-added. Someone made an edit suggesting that "using packages automates the update process," then another person replaced 'packages ' with 'pacman.' But in the official repositories there's only 1 or 2 GNOME extension(s). Thus, the AUR was entirely gotten rid of in that section, until recently I decided to re-add it after the section stayed with no AUR instructions for about 8 years. The thing is, I'm unsure of my decision of re-adding instructions for installing extensions using the AUR because apparently no one really cared about that.

I'm wondering, do you think that using AUR to install GNOME extensions is still recommended and a correct way nowadays to keep in [[GNOME#Extensions]]? Or should we get rid of it completely from that section because users abandoned it from the Wiki for 8 years straight? I'm thinking the fact that everyone is this inconsistent requires some guidance from a person who has better knowledge in this field, and I already tried the Arch forums which gave no useful answers. I would have tried to make a decision myself, but I have no idea what the reasons are for each option.

Thank you! [[User:Cont999|Cont999]] ([[User talk:Cont999|talk]]) 22:59, 16 September 2022 (UTC)

:I haven't used GNOME in years so I'm not the best person to ask. I suggest opening an item in [[Talk:GNOME]]. -- 19:25, 20 September 2022 (UTC)

::I got it. I'll ask in [[Talk:GNOME]] and I'll try to find a more concrete answer somewhere as well, just in case the discussion gets no spotlight. Thank you! [[User:Cont999|Cont999]] ([[User talk:Cont999|talk]]) 19:51, 20 September 2022 (UTC)

== Regarding a section in the system maintenance article ==

[[System_maintenance#Be_careful_with_unofficial_packages]] has the following description:

{{bc|
Use precaution when using packages from the AUR or an unofficial user repository. Most are supplied by regular users and thus may not have the same standards as those in the official repositories. Avoid AUR helpers which automate installation of AUR packages. Always check PKGBUILDs for sanity and signs of mistake or malicious code before building and/or installing the package.

To simplify maintenance, limit the amount of unofficial packages used. Make periodic checks on which are in actual use, and remove (or replace with their official counterparts) any others. See pacman/Tips and tricks#Maintenance for useful commands. Following system upgrade, use rebuild-detector to identify any unofficial packages that may need to be rebuilt.
}}

Since you're one of the last people to edit that section in particular, I thought I'd ask you for your advice since you'd have a solid understanding of its meaning.

The sentence talking about simplifying maintenance by limiting the amount of unofficial packages used seems kind of vague,
{{bc|
To simplify maintenance, limit the amount of unofficial packages used. Make periodic checks on which are in actual use, and remove (or replace with their official counterparts) any others.
}}

I'm not sure if it's just me (because English is not my first language), but reading it gives me two meanings:

1- To simplify maintenance, limit the amount of AUR packages by removing unused ones.
* '''''(in other words: you can install as many AUR packages as you'd like, but check every now and then to get rid of any AUR packages that aren't being used anymore)'''''

2- To simplify maintenance, limit the amount of AUR packages by not installing many of them in the first place AND by removing unused ones.
* '''''(in other words: try to be conservative with the number of AUR packages you install, and check every now and then to get rid of any AUR packages that aren't being used anymore)'''''

Which meaning is that specific statement trying to express? Do you think a very slight edit of the current description to clear up this confusion is needed?

Thanks! [[User:Cont999|Cont999]] ([[User talk:Cont999|talk]]) 13:24, 1 October 2022 (UTC)

:I'm not sure I see the confusion - the "''by not installing many of them''" part is covered by "''limit the amount of unofficial packages used.''" phrase. The next phrase complements this by giving the advice to check if installed AUR packages are no longer needed.
:In other words, if "Make periodic checks on which are in actual use, and remove (or replace with their official counterparts) any others." were the only phrase in that paragraph it might be vague. However, the general advice on limiting the amount of AUR packages is mentioned right before. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 00:01, 8 October 2022 (UTC)

== Ifs and whethers ==

Hi,

You have reverted the edits that replace some "if"s with "whether"s. The article you have linked to seems to be consistent with the edits (from the article: "an indirect question involving two stated or ''implied'' ''possibilities'' or alternatives"). While it is true that none of the particular ifs represent choices/alternatives, they represent a possibility of two states. For example, the sentence "check if this is the case" implies that it ''may'' or ''may not'' be the case. Using "whether or not" in that sentence does not break it, and neither does it alter the meaning; it breaks the grammar or changes the meaning only in sentences where "whether" is not applicable. This is also consistent with examples from the Cambridge English Corpus.

Sorry for breaking the subsection. I forgot that something else may be referring to it.

[[User:Xayiver|Xayiver]] ([[User talk:Xayiver|talk]]) 13:44, 19 October 2022 (UTC)

:I don't see the improvement of using "whether" here. Without choices/alternatives, it's merely longer than "if" and is less readable to me. See also [[User_talk:Jasonwryan#Doubt_regarding_revert]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 19:45, 19 October 2022 (UTC)

::I understand. It is not strictly an improvement in readability, and making the wiki read like a research paper is perhaps not urgent. The rampant run-on sentences are what concerns readability and needs addressing instead. [[User:Xayiver|Xayiver]] ([[User talk:Xayiver|talk]]) 04:29, 20 October 2022 (UTC)

== <s>Secure Shell Page</s> ==

Hello,

I noticed the following edit made by you nearly 4 years ago within this page flagging it for merge: [https://wiki.archlinux.org/index.php?title=Secure_Shell&diff=573632&oldid=572872]

Firstly, I have a reason it should not be merged, and thus I believe it should be unflagged. Not all pages deserve to be merged because they are small, but software pages like these are useful, and being able to list all the secure shell software is useful to some people looking for OpenSSH alternatives.

This should also be added as a link into [[List of applications]] for those looking for alternative SSH software, instead of making OpenSSH seem like the only software.

Let me know if you still disagree, [[User:PolarianDev|PolarianDev]] ([[User talk:PolarianDev|talk]]) 13:30, 11 May 2023 (UTC)

:That page is little more than a disambiguation page, and I've made my opinion on those clear: [[Category talk:Disambiguation pages#Remove category]]. It's not even a useful disambiguation, since [https://pkgstats.archlinux.de/packages/openssh 99.01% of readers] will be looking for {{Pkg|openssh}}. Adding hoops just because 0.99% might use an alternative is pointless. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 03:50, 12 May 2023 (UTC)

== AUR helpers rollback ==

Hello Alad,

Could you please clarify why my changes to the [[AUR helpers]] page were rolled back without any comments?

Is there a specific policy that I might have overlooked which restricts such edits?

Here are the changes I made:

* Updated the information that aura is now written in Rust, not Haskell, with a provided source.
* Noted that aura supports building in a clean chroot, with a provided source.
* Added a column listing "clean chroot" as an ability, since it's now a common feature among several tools.
* Reorganized the table layout to fit better in Firefox on a 1920x1080 screen, addressing the overlap with the tools on the right. Additionally, I included features like "fetch PGP keys" and "support batch operations" which seem more logically listed as features.

I followed the guideline "Do not make complex edits at once" from [[ArchWiki:Contributing]] and believe my changes neither "radically restructured" nor "rewrote the article", which would require a discussion on the talk page. Additionally, I ensured to use the edit summary properly, according to "properly use the edit summary".

Could you please provide more details on why all of these changes were reverted?

Thank you.

Best regards,
--[[User:RubenKelevra|RubenKelevra]] ([[User talk:RubenKelevra|talk]]) 10:18, 31 July 2024 (UTC)

:[[AUR helpers]] has a Note at the top of the page saying you should discuss edits to the page first. This was introduced after misinformation was added to the page repeatedly (AUR helper authors adding wrong claims about their products) and as an alternative to protecting the page. I suggest you thus add your points to [[Talk:AUR helpers]] before making edits. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:58, 31 July 2024 (UTC)

::I added the first two bullets. The other two bullets are non-trivial and should be discussed in [[Talk:AUR helpers]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:26, 10 August 2024 (UTC)

== Multiple environment variables in .desktop entry ==

Hello Alan,

and thank you for cleaning up the clutter of my edit in the [[MATLAB]] page.

Your summary on that last edit ([https://wiki.archlinux.org/index.php?title=MATLAB&diff=815248&oldid=815063]) left me perplexed honestly. The reason I wrote that extra section was exactly because - from what I've read and tried so far - you can't set more than one environment variables in the same .desktop file. If you can do it, can you please clarify how, possibly by providing an example?

[[User:Enf|Enf]] ([[User talk:Enf|talk]]) 10:10, 26 August 2024 (UTC)

:{{ic|1=env FOO=1 BAR=2 ...}} -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:43, 9 September 2024 (UTC)

== <s> archinstall rollback </s> ==

Hello Alad,

Could you please clarify why my changes to the [[Install Arch Linux with menu-guided archinstall]]/[[archinstall]] page were rolled back without any comments?

Is there a specific policy that I might have overlooked which restricts such edits?

Here are the changes I made:

* I moved it to Install Arch Linux with menu-guided archinstall

I also saw the move tag and thought, I could move it and make it redirect, if I was wrong, I apologize for that, and please let me know what went wrong.

I followed the guideline "Do not make complex edits at once" from [[ArchWiki:Contributing]] and believe my changes neither "radically restructured" nor "rewrote the article", which would require a discussion on the talk page. Additionally, I ensured to use the edit summary properly, according to "properly use the edit summary".

Could you please provide more details on why all of these changes were reverted?

Thank you.

Best regards,
[[User:Matthewq337|Matthewq337]] ([[User talk:Matthewq337|talk]]) 20:01, 19 June 2025 (UTC)

:Comments are here: [[Talk:Installation guide#After section 1.4 (Boot the live media), there should be a mention of archinstall]] — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 20:38, 19 June 2025 (UTC)

== <s>Please restore the Xlibre page</s> ==

The reason given states: The Xlibre project goes against [https://terms.archlinux.org/docs/code-of-conduct/#respect respect] and should not be listed on ArchWiki. See [https://x11libre.net/#about about].

The deletion appears to be vandalism. Nothing on Xlibre's About page violates the ArchWiki respect policy. The project states that it respects everyone. If you believe the About page needs changes, raise the issue on the article's Discussion page first.

As an Arch Linux user and a contributor to that Wiki page, I've never encountered such blatant discrimination. I feels really bad to have your work removed like that.

Gentoo has a Wiki page about Xlibre [https://wiki.gentoo.org/wiki/Xlibre here]. They don't seem to have any problems with the project. Artix also has a [https://wiki.artixlinux.org/Site/XlibreOnArtix Wiki page]. Recently, Artix announced that [https://artixlinux.org/news.php#Switching_to_XLibre XLibre is now the default X server in Artix Linux].

Arch Linux should follow. Including Xlibre in the official repositories is already long overdue,
given that other distros have already done so. There's a huge demand, given that Xorg doesn't get new features anymore, and hasn't been for 15 years. [[User:Tatsumoto|Tatsumoto]] ([[User talk:Tatsumoto|talk]]) 02:34, 17 April 2026 (UTC)

:I assume the problem here is the lead developer's political views however from a quick look at the page before it was removed none of that was carried over to the wiki artcile. It is also worth noting that Arch already packages in its offical repositories and mentions on its wiki many packages tied to specifc groups not everyone aligns with and those users may simply ignore them.
:h [[User:Knotrocket|Knotrocket]] ([[User talk:Knotrocket|talk]]) 03:05, 17 April 2026 (UTC)
::I don't agree with the lead developer's political views but I see their views having very little to do with their project and about page, plus providing information on the project on the wiki doesn't take any political stances to begin with, one can discuss a project without that automatically meaning an endorsement of everything the author has ever said and done [[User:Ammonium|Ammonium]] ([[User talk:Ammonium|talk]]) 05:17, 17 April 2026 (UTC)
: Even if the accusation of the Xlibre's is substantiated, deleting the page has ''zero'' effect in mitigating the issue. However, it does have a direct effect to create troubles for Arch (and other distros') users when searching for information. If people can accept the logic of deleting a project description page based on it being "disrespectful", then whoever proposed the deletion should be sanctioned for the disrespect of community members who are using this project. --[[User:Yangwenbo99|Yangwenbo99]] ([[User talk:Yangwenbo99|talk]]) 06:12, 17 April 2026 (UTC)
:I agree with the fact the page needs to be restored. The wiki is not about politics or personal beliefs. The wiki is about preservation and the presentation of valid information needed to show and guide users to packages that are available either from the AUR or the main repos.
:We have already had several pages defaced and restored by contributors for many reasons, such as fixing the ZFS pages to restore information about using tools already included with zfsutils rather than a pet project from a 3rd party repo not even in the AUR or wiki itself. Work that mind you, took me the better course of a few months to get back and clean up, and the work is still ongoing.
:While all of us share many beliefs and personal political views, we leave that outside the door when we come here to contribute. Nothing about Xlibre has been shown to be in violation of the CoC of ArchLinux. The people who have made packages or contributed time and efforts to the page have clearly had their work defaced and destroyed just to appease some petty political view that is not reflective of the general consensus here. Basically, the ArchWiki is apolitical. This is adding politics and is a clear violation of the CoC in and of itself for even presenting it as such. [[User:ReaperX7|ReaperX7]] ([[User talk:ReaperX7|talk]]) 06:49, 17 April 2026 (UTC)
:agree with everyone else here that advocates for its restoration. if solely disagreeing with someones/not liking them is enough reason for a article deletion we might as well delete 99% of all articles not written by a single person. ideological purism is unattainable and quite frankly goes against Archlinux own principle of [[Arch Linux#Pragmatism|Pragmatism]].
:"'''Arch is a pragmatic distribution rather than an ideological one'''—the principles here are only useful guidelines. Ultimately, design decisions are made on a case-by-case basis through developer consensus. '''Evidence-based technical analysis and debate are what matter, not politics or popular opinion.'''" [[User:Supernova|Supernova]] ([[User talk:Supernova|talk]]) 07:25, 17 April 2026 (UTC)
::Exactly. A lot of people use the wiki and not just Arch, or Arch based distributions like Manjaro, Artix, or any spinoffs of theirs. People from even Slackware, Gentoo, and other distributions reference the ArchWiki due to its extensive topics, coverage, and availability.
::By deleting the Xlibre page, this basically is hurting not just Arch, but users in general from accessibility to information.
::If Alad has an issue with the page, then simply don't visit it, contribute to it, or bother with it. Many people don't agree with ZFS in a GNU/Linux system, but we have a full set of pages that clearly show you how to literally take the GPL license and flush it in favor of your own tastes. Does everyone visit it? No. Does everyone contribute to it? No just a few of us who have taken the time to research it for our own needs to help others. So how is Xlibre any different? [[User:ReaperX7|ReaperX7]] ([[User talk:ReaperX7|talk]]) 09:19, 17 April 2026 (UTC)

General comment since I'm not going through this whole mess: in the 10 odd years I've been here, not a single project was allowed that officially took the stance of being inflammatory, sparking controversy, and just being plain disrepectful. It's not because a specific project has a particularly vocal fanbase that any exceptions should be made on this regard. Closing -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 09:26, 17 April 2026 (UTC)

:"General comment since I'm not going through this whole mess: "
:Translation: "I'm the problem here and I have the agenda." [[User:Msoltyspl|Msoltyspl]] ([[User talk:Msoltyspl|talk]]) 09:50, 17 April 2026 (UTC)
:I understand the concern, but the project in question has no alternatives right now, so users need information about it on the Wiki. I'm not a fan of any particular project, I just want a working system. Wayland cannot replace X11 yet, Xorg isn't getting new features anymore, Phoenix and Wayback aren't ready either. Please say what needs changing on the [https://x11libre.net/#about about page] you linked for the article to be restored. I'm going to pass that to xlibre's maintainers. [[User:Tatsumoto|Tatsumoto]] ([[User talk:Tatsumoto|talk]]) 09:55, 17 April 2026 (UTC)

::Since you seem to be the sole reasonable person in this discussion - the original article contained little more than an installation notice. How about some historical notice is added in [[Xorg]] that explains the origination of the fork?
::As to the about page - while wiki pages serve purely as documentation, ArchWiki has a certain reputation. In particular, the mere presence of an article here can be seen as an endorsement for the documented project. And such an endorsement includes, in particular, what the project writes on their homepage.
::Removing the Xlibre article may not be the perfect solution, but it seems like the only choice we have if the project's page is that expressive about the malice regarding Xorg. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 10:26, 17 April 2026 (UTC)
:::"the mere presence of an article here can be seen as an endorsement for the documented project. And such an endorsement includes, in particular, what the project writes on their homepage."
:::in no world does a simple wiki article imply endorsement. Do you think wikipedia endorses all topic it has an article about? I think its total unreasonable to delete a notice about a project simply because you interpret "malice" towards another project. [[User:Supernova|Supernova]] ([[User talk:Supernova|talk]]) 10:33, 17 April 2026 (UTC)
:::You're arguing a strawman at this point. Xlibre is a fork of Xorg, and honestly, leave it at that. We have. Your turn. Nobody cares what the developer feels is his personal business. It's not yours, mine, or our business to be his critic or anyone else's. ArchWiki is also not Wikipedia. Apples and oranges comparison.
:::Again, leave the software as it is, apolitical and leave the Wiki as apolitical as possible also. I don't bring or invite my views in here and neither does anyone else.
:::If that was the case, many pages like Wine, ZFS, the various GNU projects, and others would be out due to their authors being just as inflammatory.
:::No, you defaced the page on purpose to cite a personal beef and it needs to be restored. If you want to flaunt the CoC then please check yourself before you tout it as such because you blatantly violated it wholely by being political. You dragged politics into a topic and you're called out on it. You need to fix this and rectify the deletion of this page, and if needed, restore it, or we can edit the Xorg page and add the necessary entries to show a compare and contrast between the two branches. [[User:ReaperX7|ReaperX7]] ([[User talk:ReaperX7|talk]]) 12:22, 17 April 2026 (UTC)
:::On second thought, you're right that their homepage is inflammatory. It's full of hostility toward the Xorg Foundation and freedesktop.org and can be uncomfortable to read. It should be factual, technical, and neutral.
:::If possible, I suggest:
:::* Restore the Xlibre wiki page with a clear disclaimer stating we do not share the project's beliefs, and optionally note which beliefs are rejected.
:::* Contact the project and ask them to make their homepage professional and neutral instead of inflammatory.
:::* If they ignore the request to tone it down, I guess pursue the only remaining choice.
:::I think it would be inappropriate to write about Xlibre on the Xorg page since they're different projects, and that would cause confusion. But if the Xlibre page is restored, it could be listed as an alternative to Xorg. [[User:Tatsumoto|Tatsumoto]] ([[User talk:Tatsumoto|talk]]) 12:30, 17 April 2026 (UTC)
::::Thanks. On the suggestions:
::::* Keeping the page with a banner will likely result in the same kind of discussions we have now.
::::* Someone is welcome to contact the project and update us on the results here.
::::* This seems the most likely outcome. Or you'll get a reply that matches the kind of comments that flooded my talk page.
::::Mind that even if these points were addressed, the article had little more than an installation notice. If listing it in [[Xorg]] is confusing, we can consider a more abstract category - something like [[Display server]], similar to [[Sound system]]. Though with [[Mir]] abandoned, there's far less options to choose from there... edit: there is also {{AUR|arcan}}. We could also include things like [[Xephyr]] in the page, similar to [[w:List of display servers]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:43, 17 April 2026 (UTC)

:::I wish you can calm down and reflect on the facts. You are the only person behaving unreasonably throughout the while discussion. Your deletion of the page started the drama and it's a blatant disrespecl to Arch users using Xlibre and a potential challenge to the pragmatic principle of Arch Linux. [[User:Yangwenbo99|Yangwenbo99]] ([[User talk:Yangwenbo99|talk]]) 14:24, 17 April 2026 (UTC)

:"not a single project was allowed that officially took the stance of being inflammatory, sparking controversy"
:So now simply "sparking controversy" is enough to justify deleting knowledge and destroying contributors effort. What project articles that are "controversial and inflammatory" in your opinion will be deleted by you next?
:bcachefs article because of there controversies in the LKML?
:linux kernel article because of linus torvalds inflammatory comments such as "fuck nvidia"?
:to be clear i am NOT a fan of xlibre, i don't even use it. i have been using wayland for many years and see no reason to change that but this behavior is quite disappointing. [[User:Supernova|Supernova]] ([[User talk:Supernova|talk]]) 10:13, 17 April 2026 (UTC)
:I am deeply saddened by such a dismissive and hostile reply from such a figure in the Arch Linux community.
:First you dismiss every person with a valid request about wanting the information about how to install a software to remain available in a wiki as you're "not gonna read through this whole mess", and *then* you insult everyone understandably and validly expressing this, as calling someone you reply to "the sole reasonable person in this discussion".
:This shows a clear act of ignorance and dismissiveness to the needs and wants of the community, putting your own personal beliefs over what might benefit the community most.
:I am going to repeat myself just so you don't label me as "unreasonable" again like you did with all the other members of this discussion: *I do not agree with the political beliefs of the Xlibre author*. However, I don't see what this has to do with the matter at hand. In my opinion, allowing a wiki article should not be about "do I agree with the political beliefs of the original author and every single thing they have ever said", but just if said article is genuinely useful information to provide to the community. [[User:Ammonium|Ammonium]] ([[User talk:Ammonium|talk]]) 14:11, 17 April 2026 (UTC)

== <s>More XLibre Vandalism</s> ==

Hey can we all just universally agree that randomly deleting articles and tutorials for XLibre is completely utterly frustrating?

I really can't stand Wayland, I really wanted to checkout this new fork as I love X11, but NO.

Even in ArchWiki! ARCH!!! There's rogue admins with some childish vendetta against their dev team over some political nonsense that's presumably happening in the states. Newsflash I'm AUSTALIAN! I DON'T GAF!!! I'm just an END USER!

Let me follow the guides to compile and load the damn thing! Do I really have to start mirroring these tutorials on my forum just so everybody else can just get by? Seriously? [[User:Kippykip|Kippykip]] ([[User talk:Kippykip|talk]]) 08:36, 17 April 2026 (UTC)

:The central point must be kept clear: we are dealing with things of different natures, and mixing them leads to confused decisions.
:There is a real difference between political discourse and code. Political discourse carries intentions, values, and direct effects on people and groups. It can, in itself, offend, exclude, mobilize actions, or even demobilize actions through mechanisms historically well known. Code does not function this way. It is another kind of language structure: it does not argue, it does not persuade, it does not express positions. It executes. It is a restricted language, aimed at making things work in a simple, direct, and operational way.
:When we think about political movements with execrable far-right tendencies, the problem is not only in practical actions, but in the discourse itself. The discourse is already part of the practice, in an imbricated and inseparable way: it carries, in itself, exclusion, attack, or denial of certain groups. In this case, there is no clear separation between what is said and what is done. Saying is already a form of doing.
:With code, this does not happen. Code does not have this type of content and does not operate on that level. There is nothing within it that is equivalent to this kind of discourse, neither explicitly nor subliminally. A programming language, such as the one used in Xlibre, does not, in itself, have any structure capable of conveying hate speech. Its meaning lies in its function, not in the expression of values.
:This brings us back to the initial point: not every language functions in the same way. Some languages are oriented toward describing, arguing, and influencing, while others are oriented toward operating and making systems work. The mistake begins when we treat one as if it were the other, as if code could carry, in itself, the same kind of content as political discourse. For this reason, it is necessary to separate two things in this case. On one side, the code itself. On the other, the opinions or attitudes of those who develop it.
:In the case of Xlibre, the criticism is not directed at the code or the technical documentation, but at external positions taken by developers. This is a criterion that does not belong to the object that the Wiki should be evaluating.
:Then the problem arises: if this becomes the standard, where does it stop? Will it be necessary to investigate every project, every developer, every “About” page to decide whether something can or cannot be documented? This is not consistently applicable. It becomes selective, reactive, and inevitably arbitrary, in addition to conflicting with the very nature of language as described above.
:Furthermore, a technical Wiki is not a space for political endorsement. It exists to document. To document is not to agree, not to support, not to promote. It is simply to record useful information for those who use the system.
:When a page that fulfills this role is removed for reasons external to its content, what is lost is not only a specific article, but a principle. The principle that technical criteria should be evaluated on technical grounds.
:On the other hand, this does not prevent anyone from criticizing the project, its developers, or their positions. Such criticism is valid and necessary. However, it belongs in another space. In a broader sense, mixing these domains weakens both: criticism loses focus, and documentation loses consistency in its purpose.
:That said, if the Xlibre page on the Arch Wiki is technical, informative, and does not contain offensive content, there is no coherent reason for its removal. In order to maintain clear and consistent criteria regarding code, to assist users, and nothing beyond that, it should be restored.
:Criticism should be made where it belongs. It is necessary to preserve the freedom to use code, which is a fundamental principle of GNU/Linux. This is a freedom that is not merely formal, but lived and practiced. A freedom that is strengthened precisely when it confronts us with what we disagree with.
:Those who truly value freedom do not defend it only in the comfort of agreement, but also in the confrontation with dissent. It is in this confrontation that freedom becomes concrete, demanding positioning, action, and growth. There is also a direct relationship between loving freedom and being willing to fight for it. The more one recognizes the value of freedom, the more one develops the willingness to defend it in practice.
:And this defense is not carried out through erasure or technical exclusion, but through conscious action. Criticism should take place directly, in appropriate spaces: in public debate, in mobilizations, in affinity groups, and in the streets. That is how one confronts, in a concrete way, any authoritarian tendency or model that threatens the existence of people. Not by erasing technical documentation, but by acting where the problem truly lies. [[User:Italomourag|Italomourag]] ([[User talk:Italomourag|talk]]) 11:29, 17 April 2026 (UTC)

User talk:Alad

2026-04-17T14:43:48Z

Alad: /* Please restore the Xlibre page */ re

{{Note|Consider creating a [[Help:Discussion|discussion]] on the respective article talk page before opening an item here.}}

* [https://wiki.archlinux.org/index.php?title=Special%3AWhatLinksHere&target=User+talk%3AAlad&namespace=1 WhatLinksHere (Talk)]
* [[Special:WhatLinksHere/User_talk:Alad|WhatLinksHere (all)]]

== <s>‎Mount efivarfs</s> ==

I found your comment funny since it was you who flagged that section with [[Template:Out of date]]: [[Special:Diff/489445]]. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 13:24, 28 July 2018 (UTC)

:Haha, nice one. ;) -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:45, 28 July 2018 (UTC)

== <s>[[Identify damaged files]]</s> ==

Your title is much better than mine was but in the future could you please leave more constructive edit comments? Thank you.[[User:Ksd|Ksd]] ([[User talk:Ksd|talk]]) 00:05, 20 October 2018 (UTC)

:I didn't expect a comment on this ~3 years later... but yes I will, thank you. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 10:42, 23 October 2018 (UTC)

Heh, yeah I just recently decided to come back and start updating that article again with some new info (my old user was [[User:MaBeef]]). I appreciate it and no hard feelings. -- [[User:Ksd|Ksd]] ([[User talk:Ksd|talk]]) 14:24, 23 October 2018 (UTC)

== Disable auto updates ==

Hi Alad, regarding [https://wiki.archlinux.org/index.php?title=User:Alad/common.js&curid=24159&diff=671963&oldid=671962], an empty Array won't work in all cases, I'd suggest {{ic|update_check_wdays: false}} :) [https://github.com/kynikos/wiki-monkey/blob/bcfef4fcdbbc8aced86490dd73ff6e9f9a1a6bf2/src/lib/Upgrade.js#L92] -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 04:39, 20 May 2021 (UTC)

:Thanks for the heads-up! -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 06:45, 21 May 2021 (UTC)

== Help with the Visual Studio Code page ==

Hi Alad,

I saw that you have edited the [[Visual Studio Code]] page, so maybe you can help with the disputed content. I don't know if you will agree with me or not, but I cannot be the only one discussing (and I also find it hard to discuss, it seems pointless anyway). Personally I find it important to leave the clarity on the fact that Visual Studio Code is proprietary and is different from Code OSS; but if you think differently, please do share your opinion as well. --[[User:Grufo|Grufo]] [ [[Special:Contributions/Grufo|contribs]] | [[User_talk:Grufo|talk]] ] 07:03, 4 November 2021 (UTC)

:I didn't feel the need to step in until now. Since things have turned to edit-warring, I've left some comments. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 11:28, 4 November 2021 (UTC)

:: Thank you, Alad --[[User:Grufo|Grufo]] [ [[Special:Contributions/Grufo|contribs]] | [[User_talk:Grufo|talk]] ] 15:13, 4 November 2021 (UTC)

== Oi ==

You come back on IRC right this instant. One of the wiki admins first put "Bring back alad" in the /topic, then it became "On strike until alad returns", now all the separators in the channel topic are "🍌" and just now we got another troll in -wiki and the other ops are asleep.

How dare you leave IRC!

-- [[User:NetSysFire|NetSysFire]] ([[User talk:NetSysFire|talk]]) 15:40, 2 April 2022 (UTC)

:Beautiful. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 18:16, 2 April 2022 (UTC)

== <s>About i3 gaps topic</s> ==

Hi!!!! I am a newbie in linux. Feel free to correct me if I am wrong.

I want to talk about this topic - https://wiki.archlinux.org/index.php?title=I3&diff=735587&oldid=735585

It is very important for people to know how to use i3 gaps. i3gaps is installed by default on every i3 installation. I think it really doesn't matter if it is a fork or not. I had to watch a youtube video to learn how to use i3 gaps. In the installation section it is written you can download the i3-gaps package but no one knows how to enable them. What is the point of installing i3 gaps if we don't know how to use gaps ? It would really be nice if it could be added to the archwiki :'(

-- ([[User talk:RounakDutta|Rounak Dutta]])([[User talk:RounakDutta|talk]])

:You keep saying things are "very important" in your edits, but no, this is not "very important". It's a personal preference which leads to installing a different version of i3. And more so, this alternative is mentioned right at the [[I3#Installation|beginning of the article]] - including the fact it's default when installing the i3 group. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 16:06, 30 June 2022 (UTC)

== <s>Unavailable email</s> ==

Hi! I've tried contacting you at the email reported on AUR but your server seems to be offline.
[[User:Tallero|Tallero]] ([[User talk:Tallero|talk]]) 10:05, 9 July 2022 (UTC)

:I've enabled wiki mails, so you should be able to use "Email this user" in the sidebar. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:10, 10 July 2022 (UTC)

== <s>Do you think using the AUR to install GNOME extensions is still correct and recommended nowadays?</s> ==

Hi. I know this is definitely not the best place to post this, but I don't know who else to ask for guidance with this since you're one of the few very active Wiki administrator. Read below to understand why I ended up asking here.

[[GNOME#Extensions]] has always been very inconsistent, I just noticed this by looking at the revision history. Users keep editing it and their edits contradicts with the previous edit. Before, it had instructions to install extensions from both extensions.gone.org and the AUR. Then in 2014, [https://wiki.archlinux.org/index.php?title=GNOME&diff=343937&oldid=343891 you flagged that section] to be poorly written because there were some AUR packages suggested in a bulletpoint list style, but with no description. As you can see in the edit, the person responded to your flag and updated it. However, they entirely removed the instructions to install from the AUR instead of just removing the bulletpoint list and keeping the AUR link. It stayed like that for a while, until it something similar was re-added. Someone made an edit suggesting that "using packages automates the update process," then another person replaced 'packages ' with 'pacman.' But in the official repositories there's only 1 or 2 GNOME extension(s). Thus, the AUR was entirely gotten rid of in that section, until recently I decided to re-add it after the section stayed with no AUR instructions for about 8 years. The thing is, I'm unsure of my decision of re-adding instructions for installing extensions using the AUR because apparently no one really cared about that.

I'm wondering, do you think that using AUR to install GNOME extensions is still recommended and a correct way nowadays to keep in [[GNOME#Extensions]]? Or should we get rid of it completely from that section because users abandoned it from the Wiki for 8 years straight? I'm thinking the fact that everyone is this inconsistent requires some guidance from a person who has better knowledge in this field, and I already tried the Arch forums which gave no useful answers. I would have tried to make a decision myself, but I have no idea what the reasons are for each option.

Thank you! [[User:Cont999|Cont999]] ([[User talk:Cont999|talk]]) 22:59, 16 September 2022 (UTC)

:I haven't used GNOME in years so I'm not the best person to ask. I suggest opening an item in [[Talk:GNOME]]. -- 19:25, 20 September 2022 (UTC)

::I got it. I'll ask in [[Talk:GNOME]] and I'll try to find a more concrete answer somewhere as well, just in case the discussion gets no spotlight. Thank you! [[User:Cont999|Cont999]] ([[User talk:Cont999|talk]]) 19:51, 20 September 2022 (UTC)

== Regarding a section in the system maintenance article ==

[[System_maintenance#Be_careful_with_unofficial_packages]] has the following description:

{{bc|
Use precaution when using packages from the AUR or an unofficial user repository. Most are supplied by regular users and thus may not have the same standards as those in the official repositories. Avoid AUR helpers which automate installation of AUR packages. Always check PKGBUILDs for sanity and signs of mistake or malicious code before building and/or installing the package.

To simplify maintenance, limit the amount of unofficial packages used. Make periodic checks on which are in actual use, and remove (or replace with their official counterparts) any others. See pacman/Tips and tricks#Maintenance for useful commands. Following system upgrade, use rebuild-detector to identify any unofficial packages that may need to be rebuilt.
}}

Since you're one of the last people to edit that section in particular, I thought I'd ask you for your advice since you'd have a solid understanding of its meaning.

The sentence talking about simplifying maintenance by limiting the amount of unofficial packages used seems kind of vague,
{{bc|
To simplify maintenance, limit the amount of unofficial packages used. Make periodic checks on which are in actual use, and remove (or replace with their official counterparts) any others.
}}

I'm not sure if it's just me (because English is not my first language), but reading it gives me two meanings:

1- To simplify maintenance, limit the amount of AUR packages by removing unused ones.
* '''''(in other words: you can install as many AUR packages as you'd like, but check every now and then to get rid of any AUR packages that aren't being used anymore)'''''

2- To simplify maintenance, limit the amount of AUR packages by not installing many of them in the first place AND by removing unused ones.
* '''''(in other words: try to be conservative with the number of AUR packages you install, and check every now and then to get rid of any AUR packages that aren't being used anymore)'''''

Which meaning is that specific statement trying to express? Do you think a very slight edit of the current description to clear up this confusion is needed?

Thanks! [[User:Cont999|Cont999]] ([[User talk:Cont999|talk]]) 13:24, 1 October 2022 (UTC)

:I'm not sure I see the confusion - the "''by not installing many of them''" part is covered by "''limit the amount of unofficial packages used.''" phrase. The next phrase complements this by giving the advice to check if installed AUR packages are no longer needed.
:In other words, if "Make periodic checks on which are in actual use, and remove (or replace with their official counterparts) any others." were the only phrase in that paragraph it might be vague. However, the general advice on limiting the amount of AUR packages is mentioned right before. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 00:01, 8 October 2022 (UTC)

== Ifs and whethers ==

Hi,

You have reverted the edits that replace some "if"s with "whether"s. The article you have linked to seems to be consistent with the edits (from the article: "an indirect question involving two stated or ''implied'' ''possibilities'' or alternatives"). While it is true that none of the particular ifs represent choices/alternatives, they represent a possibility of two states. For example, the sentence "check if this is the case" implies that it ''may'' or ''may not'' be the case. Using "whether or not" in that sentence does not break it, and neither does it alter the meaning; it breaks the grammar or changes the meaning only in sentences where "whether" is not applicable. This is also consistent with examples from the Cambridge English Corpus.

Sorry for breaking the subsection. I forgot that something else may be referring to it.

[[User:Xayiver|Xayiver]] ([[User talk:Xayiver|talk]]) 13:44, 19 October 2022 (UTC)

:I don't see the improvement of using "whether" here. Without choices/alternatives, it's merely longer than "if" and is less readable to me. See also [[User_talk:Jasonwryan#Doubt_regarding_revert]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 19:45, 19 October 2022 (UTC)

::I understand. It is not strictly an improvement in readability, and making the wiki read like a research paper is perhaps not urgent. The rampant run-on sentences are what concerns readability and needs addressing instead. [[User:Xayiver|Xayiver]] ([[User talk:Xayiver|talk]]) 04:29, 20 October 2022 (UTC)

== <s>Secure Shell Page</s> ==

Hello,

I noticed the following edit made by you nearly 4 years ago within this page flagging it for merge: [https://wiki.archlinux.org/index.php?title=Secure_Shell&diff=573632&oldid=572872]

Firstly, I have a reason it should not be merged, and thus I believe it should be unflagged. Not all pages deserve to be merged because they are small, but software pages like these are useful, and being able to list all the secure shell software is useful to some people looking for OpenSSH alternatives.

This should also be added as a link into [[List of applications]] for those looking for alternative SSH software, instead of making OpenSSH seem like the only software.

Let me know if you still disagree, [[User:PolarianDev|PolarianDev]] ([[User talk:PolarianDev|talk]]) 13:30, 11 May 2023 (UTC)

:That page is little more than a disambiguation page, and I've made my opinion on those clear: [[Category talk:Disambiguation pages#Remove category]]. It's not even a useful disambiguation, since [https://pkgstats.archlinux.de/packages/openssh 99.01% of readers] will be looking for {{Pkg|openssh}}. Adding hoops just because 0.99% might use an alternative is pointless. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 03:50, 12 May 2023 (UTC)

== AUR helpers rollback ==

Hello Alad,

Could you please clarify why my changes to the [[AUR helpers]] page were rolled back without any comments?

Is there a specific policy that I might have overlooked which restricts such edits?

Here are the changes I made:

* Updated the information that aura is now written in Rust, not Haskell, with a provided source.
* Noted that aura supports building in a clean chroot, with a provided source.
* Added a column listing "clean chroot" as an ability, since it's now a common feature among several tools.
* Reorganized the table layout to fit better in Firefox on a 1920x1080 screen, addressing the overlap with the tools on the right. Additionally, I included features like "fetch PGP keys" and "support batch operations" which seem more logically listed as features.

I followed the guideline "Do not make complex edits at once" from [[ArchWiki:Contributing]] and believe my changes neither "radically restructured" nor "rewrote the article", which would require a discussion on the talk page. Additionally, I ensured to use the edit summary properly, according to "properly use the edit summary".

Could you please provide more details on why all of these changes were reverted?

Thank you.

Best regards,
--[[User:RubenKelevra|RubenKelevra]] ([[User talk:RubenKelevra|talk]]) 10:18, 31 July 2024 (UTC)

:[[AUR helpers]] has a Note at the top of the page saying you should discuss edits to the page first. This was introduced after misinformation was added to the page repeatedly (AUR helper authors adding wrong claims about their products) and as an alternative to protecting the page. I suggest you thus add your points to [[Talk:AUR helpers]] before making edits. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:58, 31 July 2024 (UTC)

::I added the first two bullets. The other two bullets are non-trivial and should be discussed in [[Talk:AUR helpers]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:26, 10 August 2024 (UTC)

== Multiple environment variables in .desktop entry ==

Hello Alan,

and thank you for cleaning up the clutter of my edit in the [[MATLAB]] page.

Your summary on that last edit ([https://wiki.archlinux.org/index.php?title=MATLAB&diff=815248&oldid=815063]) left me perplexed honestly. The reason I wrote that extra section was exactly because - from what I've read and tried so far - you can't set more than one environment variables in the same .desktop file. If you can do it, can you please clarify how, possibly by providing an example?

[[User:Enf|Enf]] ([[User talk:Enf|talk]]) 10:10, 26 August 2024 (UTC)

:{{ic|1=env FOO=1 BAR=2 ...}} -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:43, 9 September 2024 (UTC)

== <s> archinstall rollback </s> ==

Hello Alad,

Could you please clarify why my changes to the [[Install Arch Linux with menu-guided archinstall]]/[[archinstall]] page were rolled back without any comments?

Is there a specific policy that I might have overlooked which restricts such edits?

Here are the changes I made:

* I moved it to Install Arch Linux with menu-guided archinstall

I also saw the move tag and thought, I could move it and make it redirect, if I was wrong, I apologize for that, and please let me know what went wrong.

I followed the guideline "Do not make complex edits at once" from [[ArchWiki:Contributing]] and believe my changes neither "radically restructured" nor "rewrote the article", which would require a discussion on the talk page. Additionally, I ensured to use the edit summary properly, according to "properly use the edit summary".

Could you please provide more details on why all of these changes were reverted?

Thank you.

Best regards,
[[User:Matthewq337|Matthewq337]] ([[User talk:Matthewq337|talk]]) 20:01, 19 June 2025 (UTC)

:Comments are here: [[Talk:Installation guide#After section 1.4 (Boot the live media), there should be a mention of archinstall]] — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 20:38, 19 June 2025 (UTC)

== <s>Please restore the Xlibre page</s> ==

The reason given states: The Xlibre project goes against [https://terms.archlinux.org/docs/code-of-conduct/#respect respect] and should not be listed on ArchWiki. See [https://x11libre.net/#about about].

The deletion appears to be vandalism. Nothing on Xlibre's About page violates the ArchWiki respect policy. The project states that it respects everyone. If you believe the About page needs changes, raise the issue on the article's Discussion page first.

As an Arch Linux user and a contributor to that Wiki page, I've never encountered such blatant discrimination. I feels really bad to have your work removed like that.

Gentoo has a Wiki page about Xlibre [https://wiki.gentoo.org/wiki/Xlibre here]. They don't seem to have any problems with the project. Artix also has a [https://wiki.artixlinux.org/Site/XlibreOnArtix Wiki page]. Recently, Artix announced that [https://artixlinux.org/news.php#Switching_to_XLibre XLibre is now the default X server in Artix Linux].

Arch Linux should follow. Including Xlibre in the official repositories is already long overdue,
given that other distros have already done so. There's a huge demand, given that Xorg doesn't get new features anymore, and hasn't been for 15 years. [[User:Tatsumoto|Tatsumoto]] ([[User talk:Tatsumoto|talk]]) 02:34, 17 April 2026 (UTC)

:I assume the problem here is the lead developer's political views however from a quick look at the page before it was removed none of that was carried over to the wiki artcile. It is also worth noting that Arch already packages in its offical repositories and mentions on its wiki many packages tied to specifc groups not everyone aligns with and those users may simply ignore them.
:h [[User:Knotrocket|Knotrocket]] ([[User talk:Knotrocket|talk]]) 03:05, 17 April 2026 (UTC)
::I don't agree with the lead developer's political views but I see their views having very little to do with their project and about page, plus providing information on the project on the wiki doesn't take any political stances to begin with, one can discuss a project without that automatically meaning an endorsement of everything the author has ever said and done [[User:Ammonium|Ammonium]] ([[User talk:Ammonium|talk]]) 05:17, 17 April 2026 (UTC)
: Even if the accusation of the Xlibre's is substantiated, deleting the page has ''zero'' effect in mitigating the issue. However, it does have a direct effect to create troubles for Arch (and other distros') users when searching for information. If people can accept the logic of deleting a project description page based on it being "disrespectful", then whoever proposed the deletion should be sanctioned for the disrespect of community members who are using this project. --[[User:Yangwenbo99|Yangwenbo99]] ([[User talk:Yangwenbo99|talk]]) 06:12, 17 April 2026 (UTC)
:I agree with the fact the page needs to be restored. The wiki is not about politics or personal beliefs. The wiki is about preservation and the presentation of valid information needed to show and guide users to packages that are available either from the AUR or the main repos.
:We have already had several pages defaced and restored by contributors for many reasons, such as fixing the ZFS pages to restore information about using tools already included with zfsutils rather than a pet project from a 3rd party repo not even in the AUR or wiki itself. Work that mind you, took me the better course of a few months to get back and clean up, and the work is still ongoing.
:While all of us share many beliefs and personal political views, we leave that outside the door when we come here to contribute. Nothing about Xlibre has been shown to be in violation of the CoC of ArchLinux. The people who have made packages or contributed time and efforts to the page have clearly had their work defaced and destroyed just to appease some petty political view that is not reflective of the general consensus here. Basically, the ArchWiki is apolitical. This is adding politics and is a clear violation of the CoC in and of itself for even presenting it as such. [[User:ReaperX7|ReaperX7]] ([[User talk:ReaperX7|talk]]) 06:49, 17 April 2026 (UTC)
:agree with everyone else here that advocates for its restoration. if solely disagreeing with someones/not liking them is enough reason for a article deletion we might as well delete 99% of all articles not written by a single person. ideological purism is unattainable and quite frankly goes against Archlinux own principle of [[Arch Linux#Pragmatism|Pragmatism]].
:"'''Arch is a pragmatic distribution rather than an ideological one'''—the principles here are only useful guidelines. Ultimately, design decisions are made on a case-by-case basis through developer consensus. '''Evidence-based technical analysis and debate are what matter, not politics or popular opinion.'''" [[User:Supernova|Supernova]] ([[User talk:Supernova|talk]]) 07:25, 17 April 2026 (UTC)
::Exactly. A lot of people use the wiki and not just Arch, or Arch based distributions like Manjaro, Artix, or any spinoffs of theirs. People from even Slackware, Gentoo, and other distributions reference the ArchWiki due to its extensive topics, coverage, and availability.
::By deleting the Xlibre page, this basically is hurting not just Arch, but users in general from accessibility to information.
::If Alad has an issue with the page, then simply don't visit it, contribute to it, or bother with it. Many people don't agree with ZFS in a GNU/Linux system, but we have a full set of pages that clearly show you how to literally take the GPL license and flush it in favor of your own tastes. Does everyone visit it? No. Does everyone contribute to it? No just a few of us who have taken the time to research it for our own needs to help others. So how is Xlibre any different? [[User:ReaperX7|ReaperX7]] ([[User talk:ReaperX7|talk]]) 09:19, 17 April 2026 (UTC)

General comment since I'm not going through this whole mess: in the 10 odd years I've been here, not a single project was allowed that officially took the stance of being inflammatory, sparking controversy, and just being plain disrepectful. It's not because a specific project has a particularly vocal fanbase that any exceptions should be made on this regard. Closing -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 09:26, 17 April 2026 (UTC)

:"General comment since I'm not going through this whole mess: "
:Translation: "I'm the problem here and I have the agenda." [[User:Msoltyspl|Msoltyspl]] ([[User talk:Msoltyspl|talk]]) 09:50, 17 April 2026 (UTC)
:I understand the concern, but the project in question has no alternatives right now, so users need information about it on the Wiki. I'm not a fan of any particular project, I just want a working system. Wayland cannot replace X11 yet, Xorg isn't getting new features anymore, Phoenix and Wayback aren't ready either. Please say what needs changing on the [https://x11libre.net/#about about page] you linked for the article to be restored. I'm going to pass that to xlibre's maintainers. [[User:Tatsumoto|Tatsumoto]] ([[User talk:Tatsumoto|talk]]) 09:55, 17 April 2026 (UTC)

::Since you seem to be the sole reasonable person in this discussion - the original article contained little more than an installation notice. How about some historical notice is added in [[Xorg]] that explains the origination of the fork?
::As to the about page - while wiki pages serve purely as documentation, ArchWiki has a certain reputation. In particular, the mere presence of an article here can be seen as an endorsement for the documented project. And such an endorsement includes, in particular, what the project writes on their homepage.
::Removing the Xlibre article may not be the perfect solution, but it seems like the only choice we have if the project's page is that expressive about the malice regarding Xorg. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 10:26, 17 April 2026 (UTC)
:::"the mere presence of an article here can be seen as an endorsement for the documented project. And such an endorsement includes, in particular, what the project writes on their homepage."
:::in no world does a simple wiki article imply endorsement. Do you think wikipedia endorses all topic it has an article about? I think its total unreasonable to delete a notice about a project simply because you interpret "malice" towards another project. [[User:Supernova|Supernova]] ([[User talk:Supernova|talk]]) 10:33, 17 April 2026 (UTC)
:::You're arguing a strawman at this point. Xlibre is a fork of Xorg, and honestly, leave it at that. We have. Your turn. Nobody cares what the developer feels is his personal business. It's not yours, mine, or our business to be his critic or anyone else's. ArchWiki is also not Wikipedia. Apples and oranges comparison.
:::Again, leave the software as it is, apolitical and leave the Wiki as apolitical as possible also. I don't bring or invite my views in here and neither does anyone else.
:::If that was the case, many pages like Wine, ZFS, the various GNU projects, and others would be out due to their authors being just as inflammatory.
:::No, you defaced the page on purpose to cite a personal beef and it needs to be restored. If you want to flaunt the CoC then please check yourself before you tout it as such because you blatantly violated it wholely by being political. You dragged politics into a topic and you're called out on it. You need to fix this and rectify the deletion of this page, and if needed, restore it, or we can edit the Xorg page and add the necessary entries to show a compare and contrast between the two branches. [[User:ReaperX7|ReaperX7]] ([[User talk:ReaperX7|talk]]) 12:22, 17 April 2026 (UTC)
:::On second thought, you're right that their homepage is inflammatory. It's full of hostility toward the Xorg Foundation and freedesktop.org and can be uncomfortable to read. It should be factual, technical, and neutral.
:::If possible, I suggest:
:::* Restore the Xlibre wiki page with a clear disclaimer stating we do not share the project's beliefs, and optionally note which beliefs are rejected.
:::* Contact the project and ask them to make their homepage professional and neutral instead of inflammatory.
:::* If they ignore the request to tone it down, I guess pursue the only remaining choice.
:::I think it would be inappropriate to write about Xlibre on the Xorg page since they're different projects, and that would cause confusion. But if the Xlibre page is restored, it could be listed as an alternative to Xorg. [[User:Tatsumoto|Tatsumoto]] ([[User talk:Tatsumoto|talk]]) 12:30, 17 April 2026 (UTC)
::::Thanks. On the suggestions:
::::* Keeping the page with a banner will likely result in the same kind of discussions we have now.
::::* Someone is welcome to contact the project and update us on the results here.
::::* This seems the most likely outcome. Or you'll get a reply that matches the kind of comments that flooded my talk page.
::::Mind that even if these points were addressed, the article had little more than an installation notice. If listing it in [[Xorg]] is confusing, we can consider a more abstract category - something like [[Display server]], similar to [[Sound system]]. Though with [[Mir]] abandoned, there's far less options to choose from there... -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:43, 17 April 2026 (UTC)

:::I wish you can calm down and reflect on the facts. You are the only person behaving unreasonably throughout the while discussion. Your deletion of the page started the drama and it's a blatant disrespecl to Arch users using Xlibre and a potential challenge to the pragmatic principle of Arch Linux. [[User:Yangwenbo99|Yangwenbo99]] ([[User talk:Yangwenbo99|talk]]) 14:24, 17 April 2026 (UTC)

:"not a single project was allowed that officially took the stance of being inflammatory, sparking controversy"
:So now simply "sparking controversy" is enough to justify deleting knowledge and destroying contributors effort. What project articles that are "controversial and inflammatory" in your opinion will be deleted by you next?
:bcachefs article because of there controversies in the LKML?
:linux kernel article because of linus torvalds inflammatory comments such as "fuck nvidia"?
:to be clear i am NOT a fan of xlibre, i don't even use it. i have been using wayland for many years and see no reason to change that but this behavior is quite disappointing. [[User:Supernova|Supernova]] ([[User talk:Supernova|talk]]) 10:13, 17 April 2026 (UTC)
:I am deeply saddened by such a dismissive and hostile reply from such a figure in the Arch Linux community.
:First you dismiss every person with a valid request about wanting the information about how to install a software to remain available in a wiki as you're "not gonna read through this whole mess", and *then* you insult everyone understandably and validly expressing this, as calling someone you reply to "the sole reasonable person in this discussion".
:This shows a clear act of ignorance and dismissiveness to the needs and wants of the community, putting your own personal beliefs over what might benefit the community most.
:I am going to repeat myself just so you don't label me as "unreasonable" again like you did with all the other members of this discussion: *I do not agree with the political beliefs of the Xlibre author*. However, I don't see what this has to do with the matter at hand. In my opinion, allowing a wiki article should not be about "do I agree with the political beliefs of the original author and every single thing they have ever said", but just if said article is genuinely useful information to provide to the community. [[User:Ammonium|Ammonium]] ([[User talk:Ammonium|talk]]) 14:11, 17 April 2026 (UTC)

== <s>More XLibre Vandalism</s> ==

Hey can we all just universally agree that randomly deleting articles and tutorials for XLibre is completely utterly frustrating?

I really can't stand Wayland, I really wanted to checkout this new fork as I love X11, but NO.

Even in ArchWiki! ARCH!!! There's rogue admins with some childish vendetta against their dev team over some political nonsense that's presumably happening in the states. Newsflash I'm AUSTALIAN! I DON'T GAF!!! I'm just an END USER!

Let me follow the guides to compile and load the damn thing! Do I really have to start mirroring these tutorials on my forum just so everybody else can just get by? Seriously? [[User:Kippykip|Kippykip]] ([[User talk:Kippykip|talk]]) 08:36, 17 April 2026 (UTC)

:The central point must be kept clear: we are dealing with things of different natures, and mixing them leads to confused decisions.
:There is a real difference between political discourse and code. Political discourse carries intentions, values, and direct effects on people and groups. It can, in itself, offend, exclude, mobilize actions, or even demobilize actions through mechanisms historically well known. Code does not function this way. It is another kind of language structure: it does not argue, it does not persuade, it does not express positions. It executes. It is a restricted language, aimed at making things work in a simple, direct, and operational way.
:When we think about political movements with execrable far-right tendencies, the problem is not only in practical actions, but in the discourse itself. The discourse is already part of the practice, in an imbricated and inseparable way: it carries, in itself, exclusion, attack, or denial of certain groups. In this case, there is no clear separation between what is said and what is done. Saying is already a form of doing.
:With code, this does not happen. Code does not have this type of content and does not operate on that level. There is nothing within it that is equivalent to this kind of discourse, neither explicitly nor subliminally. A programming language, such as the one used in Xlibre, does not, in itself, have any structure capable of conveying hate speech. Its meaning lies in its function, not in the expression of values.
:This brings us back to the initial point: not every language functions in the same way. Some languages are oriented toward describing, arguing, and influencing, while others are oriented toward operating and making systems work. The mistake begins when we treat one as if it were the other, as if code could carry, in itself, the same kind of content as political discourse. For this reason, it is necessary to separate two things in this case. On one side, the code itself. On the other, the opinions or attitudes of those who develop it.
:In the case of Xlibre, the criticism is not directed at the code or the technical documentation, but at external positions taken by developers. This is a criterion that does not belong to the object that the Wiki should be evaluating.
:Then the problem arises: if this becomes the standard, where does it stop? Will it be necessary to investigate every project, every developer, every “About” page to decide whether something can or cannot be documented? This is not consistently applicable. It becomes selective, reactive, and inevitably arbitrary, in addition to conflicting with the very nature of language as described above.
:Furthermore, a technical Wiki is not a space for political endorsement. It exists to document. To document is not to agree, not to support, not to promote. It is simply to record useful information for those who use the system.
:When a page that fulfills this role is removed for reasons external to its content, what is lost is not only a specific article, but a principle. The principle that technical criteria should be evaluated on technical grounds.
:On the other hand, this does not prevent anyone from criticizing the project, its developers, or their positions. Such criticism is valid and necessary. However, it belongs in another space. In a broader sense, mixing these domains weakens both: criticism loses focus, and documentation loses consistency in its purpose.
:That said, if the Xlibre page on the Arch Wiki is technical, informative, and does not contain offensive content, there is no coherent reason for its removal. In order to maintain clear and consistent criteria regarding code, to assist users, and nothing beyond that, it should be restored.
:Criticism should be made where it belongs. It is necessary to preserve the freedom to use code, which is a fundamental principle of GNU/Linux. This is a freedom that is not merely formal, but lived and practiced. A freedom that is strengthened precisely when it confronts us with what we disagree with.
:Those who truly value freedom do not defend it only in the comfort of agreement, but also in the confrontation with dissent. It is in this confrontation that freedom becomes concrete, demanding positioning, action, and growth. There is also a direct relationship between loving freedom and being willing to fight for it. The more one recognizes the value of freedom, the more one develops the willingness to defend it in practice.
:And this defense is not carried out through erasure or technical exclusion, but through conscious action. Criticism should take place directly, in appropriate spaces: in public debate, in mobilizations, in affinity groups, and in the streets. That is how one confronts, in a concrete way, any authoritarian tendency or model that threatens the existence of people. Not by erasing technical documentation, but by acting where the problem truly lies. [[User:Italomourag|Italomourag]] ([[User talk:Italomourag|talk]]) 11:29, 17 April 2026 (UTC)

User talk:Alad

2026-04-17T13:22:10Z

Alad: /* Please restore the Xlibre page */ don't post replies twice, see Help:Discussion

{{Note|Consider creating a [[Help:Discussion|discussion]] on the respective article talk page before opening an item here.}}

* [https://wiki.archlinux.org/index.php?title=Special%3AWhatLinksHere&target=User+talk%3AAlad&namespace=1 WhatLinksHere (Talk)]
* [[Special:WhatLinksHere/User_talk:Alad|WhatLinksHere (all)]]

== <s>‎Mount efivarfs</s> ==

I found your comment funny since it was you who flagged that section with [[Template:Out of date]]: [[Special:Diff/489445]]. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 13:24, 28 July 2018 (UTC)

:Haha, nice one. ;) -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:45, 28 July 2018 (UTC)

== <s>[[Identify damaged files]]</s> ==

Your title is much better than mine was but in the future could you please leave more constructive edit comments? Thank you.[[User:Ksd|Ksd]] ([[User talk:Ksd|talk]]) 00:05, 20 October 2018 (UTC)

:I didn't expect a comment on this ~3 years later... but yes I will, thank you. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 10:42, 23 October 2018 (UTC)

Heh, yeah I just recently decided to come back and start updating that article again with some new info (my old user was [[User:MaBeef]]). I appreciate it and no hard feelings. -- [[User:Ksd|Ksd]] ([[User talk:Ksd|talk]]) 14:24, 23 October 2018 (UTC)

== Disable auto updates ==

Hi Alad, regarding [https://wiki.archlinux.org/index.php?title=User:Alad/common.js&curid=24159&diff=671963&oldid=671962], an empty Array won't work in all cases, I'd suggest {{ic|update_check_wdays: false}} :) [https://github.com/kynikos/wiki-monkey/blob/bcfef4fcdbbc8aced86490dd73ff6e9f9a1a6bf2/src/lib/Upgrade.js#L92] -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 04:39, 20 May 2021 (UTC)

:Thanks for the heads-up! -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 06:45, 21 May 2021 (UTC)

== Help with the Visual Studio Code page ==

Hi Alad,

I saw that you have edited the [[Visual Studio Code]] page, so maybe you can help with the disputed content. I don't know if you will agree with me or not, but I cannot be the only one discussing (and I also find it hard to discuss, it seems pointless anyway). Personally I find it important to leave the clarity on the fact that Visual Studio Code is proprietary and is different from Code OSS; but if you think differently, please do share your opinion as well. --[[User:Grufo|Grufo]] [ [[Special:Contributions/Grufo|contribs]] | [[User_talk:Grufo|talk]] ] 07:03, 4 November 2021 (UTC)

:I didn't feel the need to step in until now. Since things have turned to edit-warring, I've left some comments. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 11:28, 4 November 2021 (UTC)

:: Thank you, Alad --[[User:Grufo|Grufo]] [ [[Special:Contributions/Grufo|contribs]] | [[User_talk:Grufo|talk]] ] 15:13, 4 November 2021 (UTC)

== Oi ==

You come back on IRC right this instant. One of the wiki admins first put "Bring back alad" in the /topic, then it became "On strike until alad returns", now all the separators in the channel topic are "🍌" and just now we got another troll in -wiki and the other ops are asleep.

How dare you leave IRC!

-- [[User:NetSysFire|NetSysFire]] ([[User talk:NetSysFire|talk]]) 15:40, 2 April 2022 (UTC)

:Beautiful. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 18:16, 2 April 2022 (UTC)

== <s>About i3 gaps topic</s> ==

Hi!!!! I am a newbie in linux. Feel free to correct me if I am wrong.

I want to talk about this topic - https://wiki.archlinux.org/index.php?title=I3&diff=735587&oldid=735585

It is very important for people to know how to use i3 gaps. i3gaps is installed by default on every i3 installation. I think it really doesn't matter if it is a fork or not. I had to watch a youtube video to learn how to use i3 gaps. In the installation section it is written you can download the i3-gaps package but no one knows how to enable them. What is the point of installing i3 gaps if we don't know how to use gaps ? It would really be nice if it could be added to the archwiki :'(

-- ([[User talk:RounakDutta|Rounak Dutta]])([[User talk:RounakDutta|talk]])

:You keep saying things are "very important" in your edits, but no, this is not "very important". It's a personal preference which leads to installing a different version of i3. And more so, this alternative is mentioned right at the [[I3#Installation|beginning of the article]] - including the fact it's default when installing the i3 group. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 16:06, 30 June 2022 (UTC)

== <s>Unavailable email</s> ==

Hi! I've tried contacting you at the email reported on AUR but your server seems to be offline.
[[User:Tallero|Tallero]] ([[User talk:Tallero|talk]]) 10:05, 9 July 2022 (UTC)

:I've enabled wiki mails, so you should be able to use "Email this user" in the sidebar. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:10, 10 July 2022 (UTC)

== <s>Do you think using the AUR to install GNOME extensions is still correct and recommended nowadays?</s> ==

Hi. I know this is definitely not the best place to post this, but I don't know who else to ask for guidance with this since you're one of the few very active Wiki administrator. Read below to understand why I ended up asking here.

[[GNOME#Extensions]] has always been very inconsistent, I just noticed this by looking at the revision history. Users keep editing it and their edits contradicts with the previous edit. Before, it had instructions to install extensions from both extensions.gone.org and the AUR. Then in 2014, [https://wiki.archlinux.org/index.php?title=GNOME&diff=343937&oldid=343891 you flagged that section] to be poorly written because there were some AUR packages suggested in a bulletpoint list style, but with no description. As you can see in the edit, the person responded to your flag and updated it. However, they entirely removed the instructions to install from the AUR instead of just removing the bulletpoint list and keeping the AUR link. It stayed like that for a while, until it something similar was re-added. Someone made an edit suggesting that "using packages automates the update process," then another person replaced 'packages ' with 'pacman.' But in the official repositories there's only 1 or 2 GNOME extension(s). Thus, the AUR was entirely gotten rid of in that section, until recently I decided to re-add it after the section stayed with no AUR instructions for about 8 years. The thing is, I'm unsure of my decision of re-adding instructions for installing extensions using the AUR because apparently no one really cared about that.

I'm wondering, do you think that using AUR to install GNOME extensions is still recommended and a correct way nowadays to keep in [[GNOME#Extensions]]? Or should we get rid of it completely from that section because users abandoned it from the Wiki for 8 years straight? I'm thinking the fact that everyone is this inconsistent requires some guidance from a person who has better knowledge in this field, and I already tried the Arch forums which gave no useful answers. I would have tried to make a decision myself, but I have no idea what the reasons are for each option.

Thank you! [[User:Cont999|Cont999]] ([[User talk:Cont999|talk]]) 22:59, 16 September 2022 (UTC)

:I haven't used GNOME in years so I'm not the best person to ask. I suggest opening an item in [[Talk:GNOME]]. -- 19:25, 20 September 2022 (UTC)

::I got it. I'll ask in [[Talk:GNOME]] and I'll try to find a more concrete answer somewhere as well, just in case the discussion gets no spotlight. Thank you! [[User:Cont999|Cont999]] ([[User talk:Cont999|talk]]) 19:51, 20 September 2022 (UTC)

== Regarding a section in the system maintenance article ==

[[System_maintenance#Be_careful_with_unofficial_packages]] has the following description:

{{bc|
Use precaution when using packages from the AUR or an unofficial user repository. Most are supplied by regular users and thus may not have the same standards as those in the official repositories. Avoid AUR helpers which automate installation of AUR packages. Always check PKGBUILDs for sanity and signs of mistake or malicious code before building and/or installing the package.

To simplify maintenance, limit the amount of unofficial packages used. Make periodic checks on which are in actual use, and remove (or replace with their official counterparts) any others. See pacman/Tips and tricks#Maintenance for useful commands. Following system upgrade, use rebuild-detector to identify any unofficial packages that may need to be rebuilt.
}}

Since you're one of the last people to edit that section in particular, I thought I'd ask you for your advice since you'd have a solid understanding of its meaning.

The sentence talking about simplifying maintenance by limiting the amount of unofficial packages used seems kind of vague,
{{bc|
To simplify maintenance, limit the amount of unofficial packages used. Make periodic checks on which are in actual use, and remove (or replace with their official counterparts) any others.
}}

I'm not sure if it's just me (because English is not my first language), but reading it gives me two meanings:

1- To simplify maintenance, limit the amount of AUR packages by removing unused ones.
* '''''(in other words: you can install as many AUR packages as you'd like, but check every now and then to get rid of any AUR packages that aren't being used anymore)'''''

2- To simplify maintenance, limit the amount of AUR packages by not installing many of them in the first place AND by removing unused ones.
* '''''(in other words: try to be conservative with the number of AUR packages you install, and check every now and then to get rid of any AUR packages that aren't being used anymore)'''''

Which meaning is that specific statement trying to express? Do you think a very slight edit of the current description to clear up this confusion is needed?

Thanks! [[User:Cont999|Cont999]] ([[User talk:Cont999|talk]]) 13:24, 1 October 2022 (UTC)

:I'm not sure I see the confusion - the "''by not installing many of them''" part is covered by "''limit the amount of unofficial packages used.''" phrase. The next phrase complements this by giving the advice to check if installed AUR packages are no longer needed.
:In other words, if "Make periodic checks on which are in actual use, and remove (or replace with their official counterparts) any others." were the only phrase in that paragraph it might be vague. However, the general advice on limiting the amount of AUR packages is mentioned right before. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 00:01, 8 October 2022 (UTC)

== Ifs and whethers ==

Hi,

You have reverted the edits that replace some "if"s with "whether"s. The article you have linked to seems to be consistent with the edits (from the article: "an indirect question involving two stated or ''implied'' ''possibilities'' or alternatives"). While it is true that none of the particular ifs represent choices/alternatives, they represent a possibility of two states. For example, the sentence "check if this is the case" implies that it ''may'' or ''may not'' be the case. Using "whether or not" in that sentence does not break it, and neither does it alter the meaning; it breaks the grammar or changes the meaning only in sentences where "whether" is not applicable. This is also consistent with examples from the Cambridge English Corpus.

Sorry for breaking the subsection. I forgot that something else may be referring to it.

[[User:Xayiver|Xayiver]] ([[User talk:Xayiver|talk]]) 13:44, 19 October 2022 (UTC)

:I don't see the improvement of using "whether" here. Without choices/alternatives, it's merely longer than "if" and is less readable to me. See also [[User_talk:Jasonwryan#Doubt_regarding_revert]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 19:45, 19 October 2022 (UTC)

::I understand. It is not strictly an improvement in readability, and making the wiki read like a research paper is perhaps not urgent. The rampant run-on sentences are what concerns readability and needs addressing instead. [[User:Xayiver|Xayiver]] ([[User talk:Xayiver|talk]]) 04:29, 20 October 2022 (UTC)

== <s>Secure Shell Page</s> ==

Hello,

I noticed the following edit made by you nearly 4 years ago within this page flagging it for merge: [https://wiki.archlinux.org/index.php?title=Secure_Shell&diff=573632&oldid=572872]

Firstly, I have a reason it should not be merged, and thus I believe it should be unflagged. Not all pages deserve to be merged because they are small, but software pages like these are useful, and being able to list all the secure shell software is useful to some people looking for OpenSSH alternatives.

This should also be added as a link into [[List of applications]] for those looking for alternative SSH software, instead of making OpenSSH seem like the only software.

Let me know if you still disagree, [[User:PolarianDev|PolarianDev]] ([[User talk:PolarianDev|talk]]) 13:30, 11 May 2023 (UTC)

:That page is little more than a disambiguation page, and I've made my opinion on those clear: [[Category talk:Disambiguation pages#Remove category]]. It's not even a useful disambiguation, since [https://pkgstats.archlinux.de/packages/openssh 99.01% of readers] will be looking for {{Pkg|openssh}}. Adding hoops just because 0.99% might use an alternative is pointless. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 03:50, 12 May 2023 (UTC)

== AUR helpers rollback ==

Hello Alad,

Could you please clarify why my changes to the [[AUR helpers]] page were rolled back without any comments?

Is there a specific policy that I might have overlooked which restricts such edits?

Here are the changes I made:

* Updated the information that aura is now written in Rust, not Haskell, with a provided source.
* Noted that aura supports building in a clean chroot, with a provided source.
* Added a column listing "clean chroot" as an ability, since it's now a common feature among several tools.
* Reorganized the table layout to fit better in Firefox on a 1920x1080 screen, addressing the overlap with the tools on the right. Additionally, I included features like "fetch PGP keys" and "support batch operations" which seem more logically listed as features.

I followed the guideline "Do not make complex edits at once" from [[ArchWiki:Contributing]] and believe my changes neither "radically restructured" nor "rewrote the article", which would require a discussion on the talk page. Additionally, I ensured to use the edit summary properly, according to "properly use the edit summary".

Could you please provide more details on why all of these changes were reverted?

Thank you.

Best regards,
--[[User:RubenKelevra|RubenKelevra]] ([[User talk:RubenKelevra|talk]]) 10:18, 31 July 2024 (UTC)

:[[AUR helpers]] has a Note at the top of the page saying you should discuss edits to the page first. This was introduced after misinformation was added to the page repeatedly (AUR helper authors adding wrong claims about their products) and as an alternative to protecting the page. I suggest you thus add your points to [[Talk:AUR helpers]] before making edits. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:58, 31 July 2024 (UTC)

::I added the first two bullets. The other two bullets are non-trivial and should be discussed in [[Talk:AUR helpers]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:26, 10 August 2024 (UTC)

== Multiple environment variables in .desktop entry ==

Hello Alan,

and thank you for cleaning up the clutter of my edit in the [[MATLAB]] page.

Your summary on that last edit ([https://wiki.archlinux.org/index.php?title=MATLAB&diff=815248&oldid=815063]) left me perplexed honestly. The reason I wrote that extra section was exactly because - from what I've read and tried so far - you can't set more than one environment variables in the same .desktop file. If you can do it, can you please clarify how, possibly by providing an example?

[[User:Enf|Enf]] ([[User talk:Enf|talk]]) 10:10, 26 August 2024 (UTC)

:{{ic|1=env FOO=1 BAR=2 ...}} -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:43, 9 September 2024 (UTC)

== <s> archinstall rollback </s> ==

Hello Alad,

Could you please clarify why my changes to the [[Install Arch Linux with menu-guided archinstall]]/[[archinstall]] page were rolled back without any comments?

Is there a specific policy that I might have overlooked which restricts such edits?

Here are the changes I made:

* I moved it to Install Arch Linux with menu-guided archinstall

I also saw the move tag and thought, I could move it and make it redirect, if I was wrong, I apologize for that, and please let me know what went wrong.

I followed the guideline "Do not make complex edits at once" from [[ArchWiki:Contributing]] and believe my changes neither "radically restructured" nor "rewrote the article", which would require a discussion on the talk page. Additionally, I ensured to use the edit summary properly, according to "properly use the edit summary".

Could you please provide more details on why all of these changes were reverted?

Thank you.

Best regards,
[[User:Matthewq337|Matthewq337]] ([[User talk:Matthewq337|talk]]) 20:01, 19 June 2025 (UTC)

:Comments are here: [[Talk:Installation guide#After section 1.4 (Boot the live media), there should be a mention of archinstall]] — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 20:38, 19 June 2025 (UTC)

== <s>Please restore the Xlibre page</s> ==

The reason given states: The Xlibre project goes against [https://terms.archlinux.org/docs/code-of-conduct/#respect respect] and should not be listed on ArchWiki. See [https://x11libre.net/#about about].

The deletion appears to be vandalism. Nothing on Xlibre's About page violates the ArchWiki respect policy. The project states that it respects everyone. If you believe the About page needs changes, raise the issue on the article's Discussion page first.

As an Arch Linux user and a contributor to that Wiki page, I've never encountered such blatant discrimination. I feels really bad to have your work removed like that.

Gentoo has a Wiki page about Xlibre [https://wiki.gentoo.org/wiki/Xlibre here]. They don't seem to have any problems with the project. Artix also has a [https://wiki.artixlinux.org/Site/XlibreOnArtix Wiki page]. Recently, Artix announced that [https://artixlinux.org/news.php#Switching_to_XLibre XLibre is now the default X server in Artix Linux].

Arch Linux should follow. Including Xlibre in the official repositories is already long overdue,
given that other distros have already done so. There's a huge demand, given that Xorg doesn't get new features anymore, and hasn't been for 15 years. [[User:Tatsumoto|Tatsumoto]] ([[User talk:Tatsumoto|talk]]) 02:34, 17 April 2026 (UTC)

:I assume the problem here is the lead developer's political views however from a quick look at the page before it was removed none of that was carried over to the wiki artcile. It is also worth noting that Arch already packages in its offical repositories and mentions on its wiki many packages tied to specifc groups not everyone aligns with and those users may simply ignore them.
:h [[User:Knotrocket|Knotrocket]] ([[User talk:Knotrocket|talk]]) 03:05, 17 April 2026 (UTC)
::I don't agree with the lead developer's political views but I see their views having very little to do with their project and about page, plus providing information on the project on the wiki doesn't take any political stances to begin with, one can discuss a project without that automatically meaning an endorsement of everything the author has ever said and done [[User:Ammonium|Ammonium]] ([[User talk:Ammonium|talk]]) 05:17, 17 April 2026 (UTC)
: Even if the accusation of the Xlibre's is substantiated, deleting the page has ''zero'' effect in mitigating the issue. However, it does have a direct effect to create troubles for Arch (and other distros') users when searching for information. If people can accept the logic of deleting a project description page based on it being "disrespectful", then whoever proposed the deletion should be sanctioned for the disrespect of community members who are using this project. --[[User:Yangwenbo99|Yangwenbo99]] ([[User talk:Yangwenbo99|talk]]) 06:12, 17 April 2026 (UTC)
:I agree with the fact the page needs to be restored. The wiki is not about politics or personal beliefs. The wiki is about preservation and the presentation of valid information needed to show and guide users to packages that are available either from the AUR or the main repos.
:We have already had several pages defaced and restored by contributors for many reasons, such as fixing the ZFS pages to restore information about using tools already included with zfsutils rather than a pet project from a 3rd party repo not even in the AUR or wiki itself. Work that mind you, took me the better course of a few months to get back and clean up, and the work is still ongoing.
:While all of us share many beliefs and personal political views, we leave that outside the door when we come here to contribute. Nothing about Xlibre has been shown to be in violation of the CoC of ArchLinux. The people who have made packages or contributed time and efforts to the page have clearly had their work defaced and destroyed just to appease some petty political view that is not reflective of the general consensus here. Basically, the ArchWiki is apolitical. This is adding politics and is a clear violation of the CoC in and of itself for even presenting it as such. [[User:ReaperX7|ReaperX7]] ([[User talk:ReaperX7|talk]]) 06:49, 17 April 2026 (UTC)
:agree with everyone else here that advocates for its restoration. if solely disagreeing with someones/not liking them is enough reason for a article deletion we might as well delete 99% of all articles not written by a single person. ideological purism is unattainable and quite frankly goes against Archlinux own principle of [[Arch Linux#Pragmatism|Pragmatism]].
:"'''Arch is a pragmatic distribution rather than an ideological one'''—the principles here are only useful guidelines. Ultimately, design decisions are made on a case-by-case basis through developer consensus. '''Evidence-based technical analysis and debate are what matter, not politics or popular opinion.'''" [[User:Supernova|Supernova]] ([[User talk:Supernova|talk]]) 07:25, 17 April 2026 (UTC)
::Exactly. A lot of people use the wiki and not just Arch, or Arch based distributions like Manjaro, Artix, or any spinoffs of theirs. People from even Slackware, Gentoo, and other distributions reference the ArchWiki due to its extensive topics, coverage, and availability.
::By deleting the Xlibre page, this basically is hurting not just Arch, but users in general from accessibility to information.
::If Alad has an issue with the page, then simply don't visit it, contribute to it, or bother with it. Many people don't agree with ZFS in a GNU/Linux system, but we have a full set of pages that clearly show you how to literally take the GPL license and flush it in favor of your own tastes. Does everyone visit it? No. Does everyone contribute to it? No just a few of us who have taken the time to research it for our own needs to help others. So how is Xlibre any different? [[User:ReaperX7|ReaperX7]] ([[User talk:ReaperX7|talk]]) 09:19, 17 April 2026 (UTC)

General comment since I'm not going through this whole mess: in the 10 odd years I've been here, not a single project was allowed that officially took the stance of being inflammatory, sparking controversy, and just being plain disrepectful. It's not because a specific project has a particularly vocal fanbase that any exceptions should be made on this regard. Closing -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 09:26, 17 April 2026 (UTC)

:"General comment since I'm not going through this whole mess: "
:Translation: "I'm the problem here and I have the agenda." [[User:Msoltyspl|Msoltyspl]] ([[User talk:Msoltyspl|talk]]) 09:50, 17 April 2026 (UTC)
:I understand the concern, but the project in question has no alternatives right now, so users need information about it on the Wiki. I'm not a fan of any particular project, I just want a working system. Wayland cannot replace X11 yet, Xorg isn't getting new features anymore, Phoenix and Wayback aren't ready either. Please say what needs changing on the [https://x11libre.net/#about about page] you linked for the article to be restored. I'm going to pass that to xlibre's maintainers. [[User:Tatsumoto|Tatsumoto]] ([[User talk:Tatsumoto|talk]]) 09:55, 17 April 2026 (UTC)

::Since you seem to be the sole reasonable person in this discussion - the original article contained little more than an installation notice. How about some historical notice is added in [[Xorg]] that explains the origination of the fork?
::As to the about page - while wiki pages serve purely as documentation, ArchWiki has a certain reputation. In particular, the mere presence of an article here can be seen as an endorsement for the documented project. And such an endorsement includes, in particular, what the project writes on their homepage.
::Removing the Xlibre article may not be the perfect solution, but it seems like the only choice we have if the project's page is that expressive about the malice regarding Xorg. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 10:26, 17 April 2026 (UTC)
:::"the mere presence of an article here can be seen as an endorsement for the documented project. And such an endorsement includes, in particular, what the project writes on their homepage."
:::in no world does a simple wiki article imply endorsement. Do you think wikipedia endorses all topic it has an article about? I think its total unreasonable to delete a notice about a project simply because you interpret "malice" towards another project. [[User:Supernova|Supernova]] ([[User talk:Supernova|talk]]) 10:33, 17 April 2026 (UTC)
:::You're arguing a strawman at this point. Xlibre is a fork of Xorg, and honestly, leave it at that. We have. Your turn. Nobody cares what the developer feels is his personal business. It's not yours, mine, or our business to be his critic or anyone else's. ArchWiki is also not Wikipedia. Apples and oranges comparison.
:::Again, leave the software as it is, apolitical and leave the Wiki as apolitical as possible also. I don't bring or invite my views in here and neither does anyone else.
:::If that was the case, many pages like Wine, ZFS, the various GNU projects, and others would be out due to their authors being just as inflammatory.
:::No, you defaced the page on purpose to cite a personal beef and it needs to be restored. If you want to flaunt the CoC then please check yourself before you tout it as such because you blatantly violated it wholely by being political. You dragged politics into a topic and you're called out on it. You need to fix this and rectify the deletion of this page, and if needed, restore it, or we can edit the Xorg page and add the necessary entries to show a compare and contrast between the two branches. [[User:ReaperX7|ReaperX7]] ([[User talk:ReaperX7|talk]]) 12:22, 17 April 2026 (UTC)
:::On second thought, you're right that their homepage is inflammatory. It's full of hostility toward the Xorg Foundation and freedesktop.org and can be uncomfortable to read. It should be factual, technical, and neutral.
:::If possible, I suggest:
:::* Restore the Xlibre wiki page with a clear disclaimer stating we do not share the project's beliefs, and optionally note which beliefs are rejected.
:::* Contact the project and ask them to make their homepage professional and neutral instead of inflammatory.
:::* If they ignore the request to tone it down, I guess pursue the only remaining choice.
:::I think it would be inappropriate to write about Xlibre on the Xorg page since they're different projects, and that would cause confusion. But if the Xlibre page is restored, it could be listed as an alternative to Xorg. [[User:Tatsumoto|Tatsumoto]] ([[User talk:Tatsumoto|talk]]) 12:30, 17 April 2026 (UTC)

:"not a single project was allowed that officially took the stance of being inflammatory, sparking controversy"
:So now simply "sparking controversy" is enough to justify deleting knowledge and destroying contributors effort. What project articles that are "controversial and inflammatory" in your opinion will be deleted by you next?
:bcachefs article because of there controversies in the LKML?
:linux kernel article because of linus torvalds inflammatory comments such as "fuck nvidia"?
:to be clear i am NOT a fan of xlibre, i don't even use it. i have been using wayland for many years and see no reason to change that but this behavior is quite disappointing. [[User:Supernova|Supernova]] ([[User talk:Supernova|talk]]) 10:13, 17 April 2026 (UTC)

== <s>More XLibre Vandalism</s> ==

Hey can we all just universally agree that randomly deleting articles and tutorials for XLibre is completely utterly frustrating?

I really can't stand Wayland, I really wanted to checkout this new fork as I love X11, but NO.

Even in ArchWiki! ARCH!!! There's rogue admins with some childish vendetta against their dev team over some political nonsense that's presumably happening in the states. Newsflash I'm AUSTALIAN! I DON'T GAF!!! I'm just an END USER!

Let me follow the guides to compile and load the damn thing! Do I really have to start mirroring these tutorials on my forum just so everybody else can just get by? Seriously? [[User:Kippykip|Kippykip]] ([[User talk:Kippykip|talk]]) 08:36, 17 April 2026 (UTC)

:The central point must be kept clear: we are dealing with things of different natures, and mixing them leads to confused decisions.
:There is a real difference between political discourse and code. Political discourse carries intentions, values, and direct effects on people and groups. It can, in itself, offend, exclude, mobilize actions, or even demobilize actions through mechanisms historically well known. Code does not function this way. It is another kind of language structure: it does not argue, it does not persuade, it does not express positions. It executes. It is a restricted language, aimed at making things work in a simple, direct, and operational way.
:When we think about political movements with execrable far-right tendencies, the problem is not only in practical actions, but in the discourse itself. The discourse is already part of the practice, in an imbricated and inseparable way: it carries, in itself, exclusion, attack, or denial of certain groups. In this case, there is no clear separation between what is said and what is done. Saying is already a form of doing.
:With code, this does not happen. Code does not have this type of content and does not operate on that level. There is nothing within it that is equivalent to this kind of discourse, neither explicitly nor subliminally. A programming language, such as the one used in Xlibre, does not, in itself, have any structure capable of conveying hate speech. Its meaning lies in its function, not in the expression of values.
:This brings us back to the initial point: not every language functions in the same way. Some languages are oriented toward describing, arguing, and influencing, while others are oriented toward operating and making systems work. The mistake begins when we treat one as if it were the other, as if code could carry, in itself, the same kind of content as political discourse. For this reason, it is necessary to separate two things in this case. On one side, the code itself. On the other, the opinions or attitudes of those who develop it.
:In the case of Xlibre, the criticism is not directed at the code or the technical documentation, but at external positions taken by developers. This is a criterion that does not belong to the object that the Wiki should be evaluating.
:Then the problem arises: if this becomes the standard, where does it stop? Will it be necessary to investigate every project, every developer, every “About” page to decide whether something can or cannot be documented? This is not consistently applicable. It becomes selective, reactive, and inevitably arbitrary, in addition to conflicting with the very nature of language as described above.
:Furthermore, a technical Wiki is not a space for political endorsement. It exists to document. To document is not to agree, not to support, not to promote. It is simply to record useful information for those who use the system.
:When a page that fulfills this role is removed for reasons external to its content, what is lost is not only a specific article, but a principle. The principle that technical criteria should be evaluated on technical grounds.
:On the other hand, this does not prevent anyone from criticizing the project, its developers, or their positions. Such criticism is valid and necessary. However, it belongs in another space. In a broader sense, mixing these domains weakens both: criticism loses focus, and documentation loses consistency in its purpose.
:That said, if the Xlibre page on the Arch Wiki is technical, informative, and does not contain offensive content, there is no coherent reason for its removal. In order to maintain clear and consistent criteria regarding code, to assist users, and nothing beyond that, it should be restored.
:Criticism should be made where it belongs. It is necessary to preserve the freedom to use code, which is a fundamental principle of GNU/Linux. This is a freedom that is not merely formal, but lived and practiced. A freedom that is strengthened precisely when it confronts us with what we disagree with.
:Those who truly value freedom do not defend it only in the comfort of agreement, but also in the confrontation with dissent. It is in this confrontation that freedom becomes concrete, demanding positioning, action, and growth. There is also a direct relationship between loving freedom and being willing to fight for it. The more one recognizes the value of freedom, the more one develops the willingness to defend it in practice.
:And this defense is not carried out through erasure or technical exclusion, but through conscious action. Criticism should take place directly, in appropriate spaces: in public debate, in mobilizations, in affinity groups, and in the streets. That is how one confronts, in a concrete way, any authoritarian tendency or model that threatens the existence of people. Not by erasing technical documentation, but by acting where the problem truly lies. [[User:Italomourag|Italomourag]] ([[User talk:Italomourag|talk]]) 11:29, 17 April 2026 (UTC)

User talk:Alad

2026-04-17T10:27:38Z

Alad: /* Please restore the Xlibre page */ rw

User talk:Alad

2026-04-17T10:26:28Z

Alad: /* Please restore the Xlibre page */ re

User talk:Alad

2026-04-17T09:27:10Z

Alad: /* More XLibre Vandalism */ close, see above

User talk:Alad

2026-04-17T09:26:48Z

Alad: /* Please restore the Xlibre page */ re, close

Xorg

2026-04-16T14:12:20Z

Alad: remove Xlibre: goes against https://terms.archlinux.org/docs/code-of-conduct/#respect

[[Category:X server]]
[[de:X]]
[[es:Xorg]]
[[fr:Xorg]]
[[hu:Xorg]]
[[ja:Xorg]]
[[lv:Xorg]]
[[pt:Xorg]]
[[ru:Xorg]]
[[uk:Xorg]]
[[zh-hans:Xorg]]
{{Related articles start}}
{{Related|Autostarting}}
{{Related|Cursor themes}}
{{Related|Desktop environment}}
{{Related|Display manager}}
{{Related|Font configuration}}
{{Related|Window manager}}
{{Related|XDMCP}}
{{Related|xinit}}
{{Related|xrandr}}
{{Related articles end}}

[[Wikipedia:X.Org Server|X.Org Server]] — commonly referred to as simply '''X''' — is the [[Wikipedia:X.Org Foundation|X.Org Foundation]] implementation of the [[Wikipedia:X Window System|X Window System]] ('''X11''') [[Wikipedia:Windowing system#Display server|display server]], and it is the most popular display server among Linux users. Its ubiquity has led to making it an ever-present requisite for GUI applications, resulting in massive adoption from most distributions.

== Installation ==

Xorg can be [[install]]ed with the {{Pkg|xorg-server}} package.

Additionally, some packages from the {{Grp|xorg-apps}} group are necessary for certain configuration tasks. They are pointed out in the relevant sections.

Finally, an {{Grp|xorg}} group is also available, which includes Xorg server packages, packages from the {{Grp|xorg-apps}} group and fonts.

=== Drivers ===

See [[Graphics processing unit#Installation]] to identify your hardware and choose the driver for it.

Hardware-specific [https://dri.freedesktop.org/wiki/DDX/ Device Dependent X (DDX)] drivers are considered legacy: there is a generic {{man|4|modesetting}} DDX driver in {{pkg|xorg-server}}, which uses [[kernel mode setting]] and works well on modern hardware. The modesetting DDX driver uses [https://www.freedesktop.org/wiki/Software/Glamor/ Glamor][https://gitlab.freedesktop.org/xorg/xserver/-/tree/server-21.1-branch/glamor] for 2D acceleration, which requires [[OpenGL]].

If you want to install another DDX driver, note that Xorg searches for installed DDX drivers automatically:

* If it cannot find the specific driver installed for the hardware (listed in [[Graphics processing unit#Installation]]), it first searches for ''fbdev'' ({{pkg|xf86-video-fbdev}}), which does not include any 2D or 3D acceleration.
* If that is not found, it searches for ''vesa'' ({{pkg|xf86-video-vesa}}), the generic driver, which handles a large number of chipsets but does not include any 2D or 3D acceleration.
* If ''vesa'' is not found, Xorg will fall back to {{man|4|modesetting}} DDX driver.

== Running ==

The {{man|1|Xorg}} command is usually not run directly. Instead, the X server is started with either a [[display manager]] or [[xinit]].

{{Tip|You will typically seek to install a [[window manager]] or a [[desktop environment]] to supplement X.}}

== Configuration ==

{{Note|Arch supplies default configuration files in {{ic|/usr/share/X11/xorg.conf.d/}}, and no extra configuration is necessary for most setups.}}

Xorg uses a configuration file called {{ic|xorg.conf}} and files ending in the suffix {{ic|.conf}} for its initial setup: the complete list of the folders where these files are searched can be found in {{man|5|xorg.conf}}, together with a detailed explanation of all the available options.

=== Using .conf files ===

The {{ic|/etc/X11/xorg.conf.d/}} directory stores host-specific configuration. You are free to add configuration files there, but they must have a {{ic|.conf}} suffix: the files are read in ASCII order, and by convention their names start with {{ic|''XX''-}} (two digits and a hyphen, so that for example 10 is read before 20). These files are parsed by the X server upon startup and are treated like part of the traditional {{ic|xorg.conf}} configuration file. Note that on conflicting configuration, the file read ''last'' will be processed. For this reason, the most generic configuration files should be ordered first by name. The configuration entries in the {{ic|xorg.conf}} file are processed at the end.

For option examples to set, see [[Fedora:Input device configuration#xorg.conf.d]].

=== Using xorg.conf ===

Xorg can also be configured via {{ic|/etc/X11/xorg.conf}} or {{ic|/etc/xorg.conf}}. You can also generate a skeleton for {{ic|xorg.conf}} with:

# Xorg :0 -configure

This should create a {{ic|xorg.conf.new}} file in {{ic|/root/}} that you can copy over to {{ic|/etc/X11/xorg.conf}}.

{{Tip|If you are already running an X server, use a different display, for example {{ic|Xorg :2 -configure}}.}}

Alternatively, your proprietary video card drivers may come with a tool to automatically configure Xorg: see the article of your video driver, [[NVIDIA]], for more details.

{{Note|Configuration file keywords are case insensitive, and "_" characters are ignored. Most strings (including Option names) are also case insensitive, and insensitive to white space and "_" characters.}}

== Input devices ==

For input devices the X server defaults to the libinput driver ({{Pkg|xf86-input-libinput}}), but {{Pkg|xf86-input-evdev}} and related drivers are available as alternative.[https://archlinux.org/news/xorg-server-1191-is-now-in-extra/]

[[Udev]], which is provided as a systemd dependency, will detect hardware and both drivers will act as hotplugging input driver for almost all devices, as defined in the default configuration files {{ic|10-quirks.conf}} and {{ic|40-libinput.conf}} in the {{ic|/usr/share/X11/xorg.conf.d/}} directory.

After starting X server, the log file will show which driver hotplugged for the individual devices (note the most recent log file name may vary):
$ grep -e "Using input driver " Xorg.0.log

If both do not support a particular device, install the needed driver from the {{Grp|xorg-drivers}} group. The same applies, if you want to use another driver.

To influence hotplugging, see [[#Configuration]].

For specific instructions, see also the [[libinput]] article, the following pages below, or [[Fedora:Input device configuration]] for more examples.

=== Input identification ===

See [[Keyboard input#Identifying keycodes in Xorg]].

=== Mouse acceleration ===

See [[Mouse acceleration]].

=== Extra mouse buttons ===

See [[Mouse buttons]].

=== Touchpad ===

See [[libinput]] or [[Synaptics]].

=== Touchscreen ===

See [[Touchscreen]].

=== Keyboard settings ===

See [[Keyboard configuration in Xorg]].

== Monitor settings ==

=== Manual configuration ===

{{Note|
* Newer versions of Xorg are auto-configuring, so manual configuration should not be needed.
* If Xorg is unable to detect any monitor or to avoid auto-configuring, a configuration file can be used. A common case where this is necessary is a headless system, which boots without a monitor and starts Xorg automatically, either from a [[Automatic login to virtual console|virtual console]] at [[Start X at login|login]], or from a [[display manager]].
}}

For a headless configuration, the {{pkg|xf86-video-dummy}} driver is necessary; [[install]] it and create a configuration file, such as the following:

{{hc|/etc/X11/xorg.conf.d/10-headless.conf|
Section "Monitor"
Identifier "dummy_monitor"
HorizSync 28.0-80.0
VertRefresh 48.0-75.0
Modeline "1920x1080" 172.80 1920 2040 2248 2576 1080 1081 1084 1118
EndSection

Section "Device"
Identifier "dummy_card"
VideoRam 256000
Driver "dummy"
EndSection

Section "Screen"
Identifier "dummy_screen"
Device "dummy_card"
Monitor "dummy_monitor"
SubSection "Display"
EndSubSection
EndSection
}}

=== Multiple monitors ===

See main article [[Multihead]] for general information.

==== More than one graphics card ====

You must define the correct driver to use and put the bus ID of your graphic cards (in decimal notation).

{{bc|
Section "Device"
Identifier "Screen0"
Driver "intel"
BusID "PCI:0:2:0"
EndSection

Section "Device"
Identifier "Screen1"
Driver "nouveau"
BusID "PCI:1:0:0"
EndSection
}}

To get your bus IDs (in hexadecimal):

{{hc|$ lspci -d ::03xx|
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
01:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] (rev a1)
}}

The bus IDs here are {{ic|0:2:0}} and {{ic|1:0:0}}.

=== Display size and DPI ===

By default, Xorg always sets DPI to 96 since [https://gitlab.freedesktop.org/xorg/xserver/-/commit/fff00df94d7ebd18a8e24537ec96073717375a3f 2009-01-30]. A change was made with version 21.1 to provide proper DPI auto-detection, but [https://gitlab.freedesktop.org/xorg/xserver/-/commit/35af1299e73483eaf93d913a960e1d1738bc7de6 reverted].

The DPI of the X server can be set with the {{ic|-dpi}} command line option.

Having the correct DPI is helpful where fine detail is required (like font rendering). Previously, manufacturers tried to create a standard for 96 DPI (a 10.3" diagonal monitor would be 800x600, a 13.2" monitor 1024x768). These days, screen DPIs vary and may not be equal horizontally and vertically. For example, a 19" widescreen LCD at 1440x900 may have a DPI of 89x87.

To see if your display size and DPI are correct:

$ xdpyinfo | grep -B2 resolution

Check that the dimensions match your display size.

If you have specifications on the physical size of the screen, they can be entered in the Xorg configuration file so that the proper DPI is calculated (adjust identifier to your xrandr output):

{{bc|
Section "Monitor"
Identifier "DVI-D-0"
DisplaySize 286 179 # In millimeters
EndSection
}}

If you only want to enter the specification of your monitor '''without''' creating a full xorg.conf, create a new configuration file. For example ({{ic|/etc/X11/xorg.conf.d/90-monitor.conf}}):

{{bc|
Section "Monitor"
Identifier "<default monitor>"
DisplaySize 286 179 # In millimeters
EndSection
}}

{{Note|If you are using the proprietary NVIDIA driver, you may have to put {{ic|Option "UseEdidDpi" "FALSE"}} under {{ic|Device}} or {{ic|Screen}} section to make it take effect.}}

If you do not have specifications for physical screen width and height (most specifications these days only list by diagonal size), you can use the monitor's native resolution (or aspect ratio) and diagonal length to calculate the horizontal and vertical physical dimensions. Using the Pythagorean theorem on a 13.3" diagonal length screen with a 1280x800 native resolution (or 16:10 aspect ratio):

$ echo 'scale=5;sqrt(1280^2+800^2)' | bc # 1509.43698

This will give the pixel diagonal length, and with this value you can discover the physical horizontal and vertical lengths (and convert them to millimeters):

$ echo 'scale=5;(13.3/1509)*1280*25.4' | bc # 286.43072
$ echo 'scale=5;(13.3/1509)*800*25.4' | bc # 179.01920

{{Note|This calculation works for monitors with square pixels; however, there is the rare monitor that may compress aspect ratio (e.g 16:10 aspect resolution to a 16:9 monitor). If this is the case, you should measure your screen size manually.}}

==== Setting DPI manually ====

{{Note|While you can set any DPI you like and applications using Qt and GTK will scale accordingly, it is recommended to set it to '''96''' (100%, no scaling), '''120''' (25% higher), '''144''' (50% higher), '''168''' (75% higher), '''192''' (100% higher) etc., to reduce scaling artifacts to GUIs that use bitmaps. Reducing it below 96 DPI may not reduce the size of the GUIs graphical elements, as typically the lowest DPI the icons are made for is 96.}}

For RandR compliant drivers (for example the open source ATI driver), you can set it by:

$ xrandr --dpi 144

{{Note|Applications that comply with the setting will not change immediately. You have to start them anew.}}

To make it permanent, see [[Autostarting#On Xorg startup]].

===== Proprietary NVIDIA driver =====

You can manually set the DPI by adding the option under the {{ic|Device}} or {{ic|Screen}} section:
Option "DPI" "96 x 96"

===== Manual DPI Setting Caveat =====

GTK very often overrides the server's DPI via the optional [[X resource]] {{ic|Xft.dpi}}. To find out whether this is happening to you, check with:

$ xrdb -query | grep dpi

With GTK library versions since 3.16, when this variable is not otherwise explicitly set, GTK sets it to 96. To have GTK apps obey the server DPI you may need to explicitly set {{ic|Xft.dpi}} to the same value as the server. The {{ic|Xft.dpi}} resource is the method by which some desktop environments optionally force DPI to a particular value in personal settings. Among these are [[KDE]] and [[TDE]].

=== Display Power Management ===

[[DPMS]] is a technology that allows power saving behaviour of monitors when the computer is not in use. This will allow you to have your monitors automatically go into standby after a predefined period of time.

== Composite ==

The Composite extension for X causes an entire sub-tree of the window hierarchy to be rendered to an off-screen buffer. Applications can then take the contents of that buffer and do whatever they like. The off-screen buffer can be automatically merged into the parent window, or merged by external programs called compositing managers. For more information, see [[Wikipedia:Compositing window manager]].

Some window managers (e.g. [[Compiz]], [[Enlightenment]], [[KWin]], {{Pkg|marco}}, {{Pkg|metacity}}, {{Pkg|muffin}}, {{Pkg|mutter}}, [[Xfwm]]) do compositing on their own. For other window managers, a standalone composite manager can be used.

=== List of composite managers ===

* {{App|[[Picom]]|Lightweight compositor with shadowing, advanced blurring and fading. Forked from Compton.|https://github.com/yshui/picom|{{Pkg|picom}}}}
* {{App|[[Xcompmgr]]|Composite window-effects manager.|https://gitlab.freedesktop.org/xorg/app/xcompmgr/|{{Pkg|xcompmgr}}}}
* {{App|fastcompmgr|A lightweight compositor for X11 with a focus on speed.|https://github.com/tycho-kirchner/fastcompmgr|{{AUR|fastcompmgr}}}}
* {{App|[[Gamescope]]|The micro-compositor from Valve, with gaming-oriented features such as FSR upscaling. Forked from steamos-compositor.|https://github.com/ValveSoftware/gamescope|{{Pkg|gamescope}}}}
* {{App|steamos-compositor-plus|Valve's compositor, with some added tweaks and fixes.|https://github.com/chimeraos/steamos-compositor-plus|{{AUR|steamos-compositor-plus}}}}

== Tips and tricks ==

=== Automation ===

This section lists utilities for automating keyboard / mouse input and window operations (like moving, resizing or raising).

{| class="wikitable"
! Tool !! Package !! Manual !! [[Keysym]] input !! Window operations !! Note
|-
! xautomation
| {{Pkg|xautomation}} || {{man|1|xte}} || {{Yes}} || {{No}} || Also contains screen scraping tools. Cannot simulate {{ic|F13}} and more.
|-
! xdo
| {{Pkg|xdo}} || {{man|1|xdo}} || {{No}} || {{Yes}} || Small X utility to perform elementary actions on windows.
|-
! xdotool
| {{Pkg|xdotool}} || {{man|1|xdotool}} || {{Yes}} || {{Yes}} || [https://github.com/jordansissel/xdotool/issues Very buggy] and not in active development, e.g: has broken CLI parsing.[https://github.com/jordansissel/xdotool/issues/14#issuecomment-327968132][https://github.com/jordansissel/xdotool/issues/71]
|-
! xvkbd
| {{AUR|xvkbd}} || {{man|1|xvkbd|url=http://t-sato.in.coocan.jp/xvkbd/#option}} || {{Yes}} || {{No}} || Virtual keyboard for Xorg, also has the {{ic|-text}} option for sending characters.
|-
! AutoKey
| {{AUR|autokey-qt}} {{AUR|autokey-gtk}} || [https://github.com/autokey/autokey#documentation documentation] || {{Yes}} || {{Yes}} || Higher-level, powerful macro and scripting utility, with both Qt and Gtk front-ends.
|}

See also [[Clipboard#Tools]] and [https://venam.nixers.net/blog/unix/2019/01/07/win-automation.html an overview of X automation tools].

=== Nested X session ===

{{Out of date|maybe tell about Xephyr before}}
To run a nested session of another desktop environment:

$ /usr/bin/Xnest :1 -geometry 1024x768+0+0 -ac -name Windowmaker & wmaker -display :1

This will launch a Window Maker session in a 1024 by 768 window within your current X session.

This needs the package {{Pkg|xorg-server-xnest}} to be installed.

A more modern way of doing a nested X session is with [[Xephyr]].

=== Starting an application without a window manager ===

See [[xinit#Starting applications without a window manager]].

=== Starting GUI programs remotely ===

See main article: [[OpenSSH#X11 forwarding]].

=== On-demand disabling and enabling of input sources ===

With the help of ''xinput'' you can temporarily disable or enable input sources. This might be useful, for example, on systems that have more than one mouse, such as the ThinkPads and you would rather use just one to avoid unwanted mouse clicks.

[[Install]] the {{Pkg|xorg-xinput}} package.

Find the name or ID of the device you want to disable:

$ xinput

For example in a Lenovo ThinkPad T500, the output looks like this:

{{hc|$ xinput|<nowiki>
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ TPPS/2 IBM TrackPoint id=11 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=10 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Sleep Button id=8 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=9 [slave keyboard (3)]
↳ ThinkPad Extra Buttons id=12 [slave keyboard (3)]
</nowiki>}}

Disable the device with {{ic|xinput --disable ''device''}}, where ''device'' is the device ID or name of the device you want to disable. In this example we will disable the Synaptics Touchpad, with the ID 10:

$ xinput --disable 10

To re-enable the device, just issue the opposite command:

$ xinput --enable 10

Alternatively using the device name, the command to disable the touchpad would be:

$ xinput --disable "SynPS/2 Synaptics TouchPad"

=== Persistently disable input source ===

You can disable a particular input source using a configuration snippet:

{{hc|/etc/X11/xorg.conf.d/30-disable-''device''.conf|
Section "InputClass"
Identifier "disable-''device''"
Driver "''driver_name''"
MatchProduct "''device_name''"
Option "Ignore" "True"
EndSection
}}

{{ic|''device''}} is an arbitrary name, and {{ic|''driver_name''}} is the name of the input driver, e.g. {{ic|libinput}}. {{ic|''device_name''}} is what is actually used to match the proper device. For alternate methods of targeting the correct device, such as [[libinput]]'s {{ic|MatchIsTouchscreen}}, consult your input driver's documentation. Though this example uses libinput, this is a driver-agnostic method which simply prevents the device from being propagated to the driver.

=== Killing application with hotkey ===

Run script on hotkey:

#!/bin/sh
windowFocus=$(xdotool getwindowfocus)
pid=$(xprop -id "$windowFocus" | grep PID)
kill -9 "$pid"

Dependencies: {{Pkg|xorg-xprop}}, {{Pkg|xdotool}}

See also [[#Killing an application visually]].

=== Block TTY access ===

To block tty access when in an X add the following to [[#Configuration|xorg.conf]]:

{{bc|
Section "ServerFlags"
Option "DontVTSwitch" "True"
EndSection
}}

This can be used to help restrict command line access on a system accessible to non-trusted users.

=== Prevent a user from killing X ===

To prevent a user from killing X when it is running add the following to [[#Configuration|xorg.conf]]:

{{bc|
Section "ServerFlags"
Option "DontZap" "True"
EndSection
}}

{{Note|The {{ic|Ctrl+Alt+Backspace}} shortcut is not directly what triggers killing the X server, but the {{ic|Terminate_Server}} action from the keyboard map. This is usually not set by default, see [[Xorg/Keyboard configuration#Terminating Xorg with Ctrl+Alt+Backspace]].}}

=== Killing an application visually ===

When an application is misbehaving or stuck, instead of using {{ic|kill}} or {{ic|killall}} from a terminal and having to find the process ID or name, {{Pkg|xorg-xkill}} allows to click on said application to close its connection to the X server. Many existing applications do indeed abort when their connection to the X server is closed, but some can choose to continue.

=== Rootless Xorg ===

Xorg may run with standard user privileges instead of root (so-called "rootless" Xorg). This is a significant security improvement over running as root. Note that some popular [[display manager]]s do not support rootless Xorg (e.g. [https://github.com/canonical/lightdm/issues/18 LightDM] or [[XDM]]).

You can verify which user Xorg is running as with {{ic|1=ps -o user= -C Xorg}}.

See also {{man|1|Xorg.wrap}}, {{man|8|systemd-logind}}, [[Systemd/User#Xorg as a systemd user service]], [[Fedora:Changes/XorgWithoutRootRights]] and {{Bug|41257}}.

==== Using xinitrc ====

To configure rootless Xorg using [[xinitrc]]:

* Run startx as a subprocess of the login shell; run {{ic|startx}} directly and do not use {{ic|exec startx}}.
* Ensure that Xorg uses virtual terminal for which permissions were set, i.e. passed by logind in {{ic|$XDG_VTNR}} via [[xinit#xserverrc|.xserverrc]].
* If using certain proprietary display drivers, [[kernel mode setting]] [https://gitlab.freedesktop.org/xorg/xserver/-/blob/master/hw/xfree86/xorg-wrapper.c#L222 auto-detection] will fail. In such cases, you must set {{ic|1=needs_root_rights = no}} in {{ic|/etc/X11/Xwrapper.config}}.

Note that executing {{ic|startx}} directly without {{ic|exec }} leaves the shell open in the case of a xorg crash. Since some lock screens are executed inside xorg, this can lead to full access to the executing user.

==== Using GDM ====

[[GDM]] will run Xorg without root privileges by default when [[kernel mode setting]] is used.

==== Session log redirection ====

When Xorg is run in rootless mode, Xorg logs are saved to {{ic|~/.local/share/xorg/Xorg.log}}. However, the stdout and stderr output from the Xorg session is not redirected to this log. To re-enable redirection, start Xorg with the {{ic|-keeptty}} flag and redirect the stdout and stderr output to a file:

startx -- -keeptty >~/.xorg.log 2>&1

Alternatively, copy {{ic|/etc/X11/xinit/xserverrc}} to {{ic|~/.xserverrc}}, and append {{ic|-keeptty}}. See [https://bbs.archlinux.org/viewtopic.php?pid=1446402#p1446402].

=== Xorg as Root ===

As explained above, there are circumstances in which rootless Xorg is defaulted to. If this is the case for your configuration, and you have a need to run Xorg as root, you can configure {{man|1|Xorg.wrap}} to require root:

{{Warning|Running Xorg as root poses security issues. See [[#Rootless Xorg]] for further discussion.}}

{{hc|1=/etc/X11/Xwrapper.config|2=
needs_root_rights = yes
}}

=== Wayback ===

Wayback is an X11 compatibility layer which allows for running full X11 desktop environments (and window managers) using Wayland components. It's available from the AUR as {{AUR|wayback-x11}} package.

=== 12to11 ===

12to11 allows you to seamlessly run Wayland-only applications under X11. It's available from the AUR as {{AUR|12to11-git}}. Run with the EGL renderer for best performance:

$ RENDERER=egl 12to11

== Troubleshooting ==

=== General ===

If a problem occurs, view the log stored in either {{ic|/var/log/}} or, for the rootless X default since v1.16, in {{ic|~/.local/share/xorg/}}. [[GDM]] users should check the [[systemd journal]]. [https://bbs.archlinux.org/viewtopic.php?id=184639]

The logfiles are of the form {{ic|Xorg.n.log}} with {{ic|n}} being the display number. For a single user machine with default configuration the applicable log is frequently {{ic|Xorg.0.log}}, but otherwise it may vary. To make sure to pick the right file it may help to look at the timestamp of the X server session start and from which console it was started. For example:

{{hc|$ grep -e Log -e tty Xorg.0.log|2=
[ 40.623] (==) Log file: "/home/archuser/.local/share/xorg/Xorg.0.log", Time: Thu Aug 28 12:36:44 2014
[ 40.704] (--) controlling tty is VT number 1, auto-enabling KeepTty
}}

{{Tip|To monitor the log with human-readable timestamps, {{man|1|tail}}'s output can be piped to {{man|1|ts}} (provided by the {{Pkg|moreutils}} package). This will give correct timestamps only for lines added to the log while the command is running. For example:
$ tail -f ~/.local/share/xorg/Xorg.0.log {{!}} ts
}}

* In the logfile then be on the lookout for any lines beginning with {{ic|(EE)}}, which represent errors, and also {{ic|(WW)}}, which are warnings that could indicate other issues.
* If there is an ''empty'' {{ic|.xinitrc}} file in your {{ic|$HOME}}, either delete or edit it in order for X to start properly. If you do not do this X will show a blank screen with what appears to be no errors in your {{ic|Xorg.0.log}}. Simply deleting it will get it running with a default X environment.
* If the screen goes black, you may still attempt to switch to a different virtual console (e.g. {{ic|Ctrl+Alt+F6}}), and blindly log in as root. You can do this by typing {{ic|root}} (press {{ic|Enter}} after typing it) and entering the root password (again, press {{ic|Enter}} after typing it).

: You may also attempt to kill the X server with:
: {{bc|# pkill -x X}}
: If this does not work, reboot blindly with:
: {{bc|# reboot}}

* Check specific pages in [[:Category:Input devices]] if you have issues with keyboard, mouse, touchpad etc.
* Search for common problems in [[AMDGPU]], [[Intel]] and [[NVIDIA]] articles.

=== Black screen, No protocol specified, Resource temporarily unavailable for all or some users ===

X creates configuration and temporary files in current user's home directory. Make sure there is free disk space available on the partition your home directory resides in. Unfortunately, X server does not provide any more obvious information about lack of disk space in this case.

=== DRI with Matrox cards stopped working ===

If you use a Matrox card and DRI stopped working after upgrading to Xorg, try adding the line:

Option "OldDmaInit" "On"

to the {{ic|Device}} section that references the video card in {{ic|xorg.conf}}.

=== Frame-buffer mode problems ===

X fails to start with the following log messages:

{{bc|<nowiki>
(WW) Falling back to old probe method for fbdev
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/lib/xorg/modules/linux//libfbdevhw.so
(II) Module fbdevhw: vendor="X.Org Foundation"
compiled for 1.6.1, module version=0.0.2
ABI class: X.Org Video Driver, version 5.0
(II) FBDEV(1): using default device

Fatal server error:
Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
</nowiki>}}

To correct, [[uninstall]] the {{pkg|xf86-video-fbdev}} package.

=== Program requests "font '(null)'" ===

Error message: {{ic|unable to load font `(null)'}}.

Some programs only work with bitmap fonts. Two major packages with bitmap fonts are available, {{Pkg|xorg-fonts-75dpi}} and {{Pkg|xorg-fonts-100dpi}}. You do not need both; one should be enough. To find out which one would be better in your case, try {{ic|xdpyinfo}} from {{Pkg|xorg-xdpyinfo}}, like this:

$ xdpyinfo | grep resolution

and use what is closer to the shown value.

=== Recovery: disabling Xorg before GUI login ===

If Xorg is set to boot up automatically and for some reason you need to prevent it from starting up before the login/display manager appears (if the system is wrongly configured and Xorg does not recognize your mouse or keyboard input, for instance), you can accomplish this task with two methods.

* Change default target to {{ic|rescue.target}}. See [[systemd#Change default target to boot into]].
* If you have not only a faulty system that makes Xorg unusable, but you have also set the GRUB menu wait time to zero, or cannot otherwise use GRUB to prevent Xorg from booting, you can use the Arch Linux live CD. Follow the [[Installation guide#Format the partitions|installation guide]] about how to mount and chroot into the installed Arch Linux. Alternatively try to switch into another [[tty]] with {{ic|Ctrl+Alt}} + function key (usually from {{ic|F1}} to {{ic|F7}} depending on which is not used by X), login as root and follow steps below.

Depending on setup, you will need to do one or more of these steps:

* [[Disable]] the [[display manager]].
* Disable the [[start X at login|automatic start of X]].
* Rename the {{ic|~/.xinitrc}} or comment out the {{ic|exec}} line in it.

=== X clients started with "su" fail ===

If you are getting {{ic|Client is not authorized to connect to server}}, try adding the line:

session optional pam_xauth.so

to {{ic|/etc/pam.d/su}} and {{ic|/etc/pam.d/su-l}}. {{ic|pam_xauth}} will then properly set environment variables and handle {{ic|xauth}} keys.

=== X failed to start: Keyboard initialization failed ===

If the filesystem (specifically {{ic|/tmp}}) is full, {{ic|startx}} will fail. The log file will contain:

{{bc|
(EE) Error compiling keymap (server-0)
(EE) XKB: Could not compile keymap
(EE) XKB: Failed to load keymap. Loading default keymap instead.
(EE) Error compiling keymap (server-0)
(EE) XKB: Could not compile keymap
XKB: Failed to compile keymap
Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.
Fatal server error:
Failed to activate core devices.
...
}}

Make some free space on the relevant filesystem and X will start.

=== A green screen whenever trying to watch a video ===

Your color depth is set wrong. It may need to be 24 instead of 16, for example.

=== SocketCreateListener error ===

If X terminates with error message {{ic|SocketCreateListener() failed}}, you may need to delete socket files in {{ic|/tmp/.X11-unix}}. This may happen if you have previously run Xorg as root (e.g. to generate an {{ic|xorg.conf}}).

=== Invalid MIT-MAGIC-COOKIE-1 key when trying to run a program as root ===

That error means that only the current user has access to the X server. The solution is to give access to root:

$ xhost +si:localuser:root

That line can also be used to give access to X to a different user than root.

== See also ==

* [https://magcius.github.io/xplain/article/ Xplain] - In-depth explanation of the X Window System
* {{man|1|Xorg}}
* [https://developer.ibm.com/tutorials/l-lpic1-106-1/ Prepare for LPIC-1 exam 2 - topic 106.1: X11] - briefly covers architecture, [[#Configuration]], [[desktop environments]], remote usage, [[Wayland]].
* {{man|5|xorg.conf}}
* [[Gentoo:Xorg/Guide#Configuration]]

Unofficial user repositories

2026-04-16T14:12:05Z

Alad: /* xlibre */ remove Xlibre: goes against https://terms.archlinux.org/docs/code-of-conduct/#respect

[[Category:Package management]]
[[Category:Lists]]
[[es:Unofficial user repositories]]
[[hu:Unofficial user repositories]]
[[ja:非公式ユーザーリポジトリ]]
[[zh-hans:Unofficial user repositories]]
{{Related articles start}}
{{Related|Official repositories}}
{{Related articles end}}

{{Warning|The official Arch Linux [https://archlinux.org/people/developers/ developers] and the [[Package Maintainers]] do not perform tests of any sort to verify the contents of unofficial user repositories. It is your decision whether to trust their maintainers, and you take full responsibility for any consequences of using any unofficial repository.}}

This article lists binary repositories freely created and shared by the community, often providing pre-built versions of [[PKGBUILD]]s found in the [[Arch User Repository]] (AUR).

In order to use these repositories, add them to {{ic|/etc/pacman.conf}}, as explained in [[pacman#Repositories and mirrors]]. If a repository is signed, you must obtain and locally sign the associated key, as explained in [[pacman/Package signing#Adding unofficial keys]].

Many of the unofficial Arch Linux repositories are indexed on https://archlinux.pkgs.org — it provides repositories browser and packages search.

{{Note|https://archlinux.pkgs.org lists [https://archlinuxarm.org/ Arch Linux ARM] ''aarch64'' repositories as official under the Arch Linux organisation which is factually incorrect: these repositories are unofficial—use them at your own risk.}}

If you want to create your own custom repository, follow [[pacman/Tips and tricks#Custom local repository]].

If you have your own repository, please add it to this page so that all the other users will know where to find your packages. Keep the following rules when adding new repositories:

* Keep the lists in alphabetical order.
* Include some information about the '''maintainer'''—at least a (nick)name and some form of contact information (website, email address, user page on ArchWiki or the forums, etc.).
* Include some short '''description'''—e.g., the category of packages provided in the repository.
* If there is a '''page'''—either on ArchWiki or external—containing more information about the repository, include a link to it.
* If the repository is of the [[#Signed|signed]] variety, please include a '''key-id''', possibly using it as the anchor for a link to its keyserver; if the key is not on a keyserver, include a link to the '''key file'''.
* If possible, avoid using comments in code blocks: the formatted description is much more readable. Users who want some comments in their {{man|5|pacman.conf}} can easily create it on their own.

Some repositories may also have packages for architectures besides x86_64. The {{ic|$arch}} variable will be set automatically by [[pacman]].

== Signed ==

=== ada ===

* '''Maintainer:''' Rod Kay <rodakay5 at gmail dot com>
* '''Description:''' Arch Ada Repository—all packages relating to the [[Ada]] and SPARK programming languages.
* '''Key-ID:''' [https://keyserver.ubuntu.com/pks/lookup?op=vindex&fingerprint=on&exact=on&search=0xED55AF75B0330A2A3BAA9986B6120CD888A0DFD2 0xED55AF75B0330A2A3BAA9986B6120CD888A0DFD2]

{{bc|<nowiki>
[ada]
Server = http://www.orthanc.site:8080/assets/arch_ada_repo
</nowiki>}}

=== alerque ===

* '''Maintainer:''' [https://aur.archlinux.org/account/alerque Caleb Maclennan]
* '''Description:''' Typesetting, publishing, and font development related tools such as SILE, CaSILE, Fontship, and their related dependencies including many fonts, Lua rocks, and Python modules. Also Asterisk, most of the AUR packages [https://aur.archlinux.org/packages/?O=0&SeB=M&K=alerque&outdated=&SB=n&SO=a&PP=250&do_Search=Go I (co-)maintain], and many of the AUR builds I use personally.
* '''Git repository:''' https://github.com/alerque/aur
* '''Key-ID:''' [https://keyserver.ubuntu.com/pks/lookup?op=vindex&fingerprint=on&exact=on&search=0x9F377DDB6D3153A48EB3EB1E63CC496475267693 63CC496475267693]

{{bc|<nowiki>
[alerque]
Server = https://arch.alerque.com/$arch
</nowiki>}}

=== ALHP ===

* '''Maintainer:''' [https://aur.archlinux.org/account/anonfunc Giovanni Harting]
* '''Description:''' ALHP—stands for [https://www.reddit.com/r/archlinux/comments/oflged/comment/h4i46jw/ whatever you want it]—provides [[official repositories]] compiled for specific x86-64 [[Wikipedia:X86-64#Microarchitecture levels|microarchitecture level]] with additional optimizations1:

:{| class="wikitable"
|-
! !! [[C]] and [[Wikipedia:C++|C++]] !! [[Fortran]] !! [[Go]] !! [[Rust]]
|-
| CPU microarchitecture
|
{{ic|CFLAGS}}:
: {{ic|1=-march=x86-64-v'''''N'''''}}

{{ic|KCFLAGS}}, {{ic|KCPPFLAGS}}2:
: {{ic|1=-march=x86-64-v'''''N'''''}}3
|
{{ic|FFLAGS}}:
: {{ic|1=-march=x86-64-v'''''N'''''}}
|
{{ic|1=GOAMD64=v'''''N'''''}}
|
{{ic|RUSTFLAGS}}:
: {{ic|1=-C target-cpu=x86-64-v'''''N'''''}}
|-
| [[Wikipedia:Interprocedural optimization#Unix-like|Link-time optimization]] (LTO)
|
{{ic|LTOFLAGS}}:
: [https://github.com/InBetweenNames/gentooLTO/issues/164#issuecomment-435641714 -falign-functions=32]
|
|
|
{{ic|1=CARGO_PROFILE_RELEASE_LTO=fat}}

{{ic|RUSTFLAGS}}:
: {{ic|1=-C codegen-units=1}}
|-
| Other
|
{{ic|CFLAGS}}:
: {{ic|-O3}}
: {{ic|-mpclmul}}

{{ic|KCFLAGS}}, {{ic|KCPPFLAGS}}:
: {{ic|-O3}}4
|
{{ic|FFLAGS}}:
: {{ic|-O3}}
|
|
{{ic|RUSTFLAGS}}:
: {{ic|1=-C opt-level=3}}
: {{ic|1=-C link-arg=-z}}
: {{ic|1=-C link-arg=pack-relative-relocs}}
|}

:# See the current compilation flags in https://somegit.dev/ALHP/ALHP.GO/src/branch/main/flags.yaml and https://alhp.dev/makepkg/. See also [[makepkg#Optimization]].
:# You [https://somegit.dev/ALHP/ALHP.GO/issues/68 have] to use [[Dynamic Kernel Module Support]] (DKMS) packages instead of [https://somegit.dev/ALHP/ALHP.GO#directly-linked-kernel-modules directly linked kernel modules]—e.g. users of {{ic|nvidia}}, {{Pkg|virtualbox-host-modules-arch}} and [[#ArchZFS|ArchZFS]] are affected.
:# Setting {{ic|-march}} for the [[kernel]] compilation [https://bbs.archlinux.org/viewtopic.php?pid=2226107#p2226107 would not] yield any significant results.
:# Setting {{ic|-O3}} for the kernel compilation is [https://www.phoronix.com/review/linux-kernel-o3/9 questionable].

: See also [https://somegit.dev/ALHP/ALHP.GO/issues/16 Blacklisted packages].

* '''Git repository:''' https://somegit.dev/ALHP/ALHP.GO
* '''Keyring:''' {{AUR|alhp-keyring}}
* '''Mirrors:''' {{AUR|alhp-mirrorlist}}
* [[debuginfod]]: https://debuginfod.alhp.dev

[core-x86-64-v'''''N''''']
Include = /etc/pacman.d/alhp-mirrorlist

[extra-x86-64-v'''''N''''']
Include = /etc/pacman.d/alhp-mirrorlist

[multilib-x86-64-v'''''N''''']
Include = /etc/pacman.d/alhp-mirrorlist

{{Warning|[https://somegit.dev/ALHP/ALHP.GO#1-check-your-system-for-support Check your system for support]—if you choose unsupported option, you may not be able to boot your system.}}

{{Note|
* Check [https://status.alhp.dev/ status]—if it is ''Building'', then you [https://somegit.dev/ALHP/ALHP.GO/issues/281#issuecomment-4227 may] end up with [[partial upgrade]].
* ALHP [https://somegit.dev/ALHP/ALHP.GO/issues/264 does not] provide package [[Arch Linux Archive|archive]].
}}

=== andontie-aur ===

* '''Maintainer:''' Holly M.
* '''Description:''' A repository containing the most popular AUR packages, as well as some I use all the time. New packages can be requested on the upstream website.
* '''Upstream page:''' https://aur.andontie.net
* '''Key-ID:''' [https://keyserver.ubuntu.com/pks/lookup?search=72BF227DD76AE5BF&fingerprint=on&op=index 72BF227DD76AE5BF]

{{bc|<nowiki>
[andontie-aur]
Server = https://aur.andontie.net/$arch
</nowiki>}}

=== arcanisrepo ===

* '''Maintainer:''' [https://arcanis.me/ arcanis]
* '''Description:''' AUR packages (including some VCS packages), mostly development and scientific tools. Updated daily.
* '''Upstream page:''' https://repo.arcanis.me/arcanisrepo/x86_64/index.html
* '''Key-ID:''' [https://pgp.mit.edu/pks/lookup?op=get&search=0xBD2AC8C5E989490C 0xBD2AC8C5E989490C]

{{bc|<nowiki>
[arcanisrepo]
Server = https://repo.arcanis.me/$repo/$arch
</nowiki>}}

=== arch4edu ===

* '''Maintainers:''' [https://github.com/petronny Jingbei Li (petronny)], and [https://github.com/arch4edu/arch4edu/graphs/contributors others]
* '''Description:''' Community repository for Arch Linux and Arch Linux ARM that strives to provide the latest versions of most software used by college students.
* '''Git repository:''' https://github.com/arch4edu/arch4edu, also for packaging issues, out-of-date notifications, package requests, and related questions.
* '''Key-ID:''' 7931B6D628C8D3BA
* '''Mirrors:''' https://github.com/arch4edu/mirrorlist/blob/master/mirrorlist.arch4edu

{{bc|<nowiki>
[arch4edu]
Server = https://mirrors.tuna.tsinghua.edu.cn/arch4edu/$arch
</nowiki>}}

=== archlinuxcn ===

* '''Maintainers:''' [https://blog.phoenixlzx.com/ phoenixlzx], [https://archlinux.org/people/developers/#felixonmars Felix Yan (felixonmars, dev)], [https://github.com/lilydjwg lilydjwg], [https://archlinux.org/people/package-maintainer-fellows/#farseerfc farseerfc], and [https://github.com/archlinuxcn/repo/graphs/contributors others]
* '''Description:''' Packages by the Chinese Arch Linux community, all signed. Be aware that non-x86_64 packages are not fully maintained and tested. Create an issue if you find some problems.
* '''Git repository:''' https://github.com/archlinuxcn/repo, also for packaging issues, out-of-date notifications, package requests, and related questions.
* '''Key-ID:''' Once the repository is added, ''archlinuxcn-keyring'' package must be installed before any other, so you do not get errors about PGP signatures. ''archlinuxcn-keyring'' package itself is signed by a developer.
* '''Mirrors:''' https://github.com/archlinuxcn/mirrorlist-repo, or install ''archlinuxcn-mirrorlist-git'' from the repository and use the {{ic|/etc/pacman.d/archlinuxcn-mirrorlist}} mirror list.
* [[debuginfod]]: https://repo.archlinuxcn.org

{{bc|<nowiki>
[archlinuxcn]
Server = https://repo.archlinuxcn.org/$arch
</nowiki>}}

=== ArchZFS ===

* '''Maintainers:''' [https://github.com/minextu Jan Houben] ([https://aur.archlinux.org/account/minextu minextu]), [https://github.com/kerberizer Luchesar Iliev] ([https://aur.archlinux.org/account/kerberizer kerberizer]), and [https://github.com/orgs/archzfs/people others]
* '''Description:''' Packages for [[ZFS]] on Arch Linux.
* '''Upstream wiki:''' https://github.com/archzfs/archzfs/wiki
* '''Key-ID:''' [https://github.com/archzfs/archzfs-keyring/blob/master/keyring/packager/archzfs/3A9917BF0DED5C13F69AC68FABEC0A1208037BE9/3A9917BF0DED5C13F69AC68FABEC0A1208037BE9.asc 3A9917BF0DED5C13F69AC68FABEC0A1208037BE9]

{{bc|<nowiki>
[archzfs]
Server = https://github.com/archzfs/archzfs/releases/download/experimental
Server = https://mirrors.uni-plovdiv.net/archzfs/experimental
</nowiki>}}

=== artafinde ===

* '''Maintainer:''' [https://archlinux.org/people/developers/#artafinde Leonidas Spyropoulos]
* '''Description:''' Personal repository with AUR and custom packages.
* '''Key-ID:''' Not needed, as key is in archlinux keyring.

{{bc|<nowiki>
[artafinde]
Server = https://pkgbuild.com/~artafinde/repo
</nowiki>}}

=== avr ===

* '''Maintainer:''' [https://aur.archlinux.org/account/vianney Vianney Bouchaud]
* '''Description:''' Some of the AUR builds I use personally, packages mainly related to kubernetes that I used to build for my own use as well as some of my own software that I also package.
* '''Upstream page:''' https://bouchaud.org/packages/avr
* '''Git repository:''' https://github.com/vbouchaud/aur
* '''Key-ID:''' [https://keyserver.ubuntu.com/pks/lookup?op=vindex&fingerprint=on&exact=on&search=0xAD53F33B1AB4C51802F25068157B08346330029C 157B08346330029C]

{{bc|<nowiki>
[avr]
Server = https://bouchaud.org/packages/$repo/$arch
</nowiki>}}

=== bioarchlinux ===

* '''Maintainer:''' BioArchLinux Team
* '''Description:''' Biological Software Repository for Arch Linux, incrudes R cran binary packages.
* '''Upstream page:''' https://github.com/BioArchLinux/Packages
* '''Setup:''' https://wiki.bioarchlinux.org/index.php?title=Usage
* '''Citation:''' https://doi.org/10.1093/bioinformatics/btaf106
* '''Key-ID:''' B1F96021DB62254D

{{bc|<nowiki>
[bioarchlinux]
Server = https://repo.bioarchlinux.org/$arch
</nowiki>}}

{{Tip|In [[R]] integrate {{ic|install.packages}} with [[pacman]] and BioArchLinux repository using ''bspm'' with {{ic|suppressMessages(bspm::enable())}}.}}

=== blackeagle-pre-community ===

* '''Maintainer:''' [https://archlinux.org/people/package-maintainers/#idevolder Ike Devolder]
* '''Description:''' Testing of the by me maintained packages before moving to ''extra'' repository.
* '''Key-ID:''' Not required, as maintainer is a Package Maintainer.

{{bc|<nowiki>
[blackeagle-pre-community]
Server = https://repo.herecura.eu/$repo/$arch
</nowiki>}}

=== build.kilabit.info ===

* '''Maintainer:''' [https://aur.archlinux.org/account/shulhan shulhan]
* '''Upstream page:''' https://build.kilabit.info
* '''Package list:''' https://build.kilabit.info/karajo/app/
* '''Key-ID:''' [https://keys.openpgp.org/vks/v1/by-fingerprint/CEF1AA87E337A6C390DE5550F8507EE9148A4CE3 4A5360B500C9C4F0]

{{bc|<nowiki>
[build.kilabit.info]
Server = https://build.kilabit.info/aur
</nowiki>}}

=== chaotic-aur ===

* '''Maintainer:''' [https://github.com/dr460nf1r3 dr460nf1r3], [https://github.com/pedrohlc PedroHLC], [https://github.com/lordkitsuna LordKitsuna], [https://github.com/librewish Librewish]{{Dead link|2023|05|06|status=404}}, [https://github.com/SolarAquarion SolarAquarion], [https://github.com/thotypous thotypous] (former [[TU]]), and [https://github.com/RustemB RustemB] (in memoriam).
* '''Description:''' Auto builds AUR packages the maintainers use, update them hourly (a few are updated daily). It has several mirrors worldwide. Its main builder is hosted at the Federal University of Sao Carlos, Brazil. It's x86_64 only.
* '''Upstream page:''' https://aur.chaotic.cx
* '''Key-ID:''' [https://pgp.mit.edu/pks/lookup?search=0xFBA220DFC880C036&op=index FBA220DFC880C036], with some subkeys. To help, keyring and mirror list are available at the repository's homepage.

{{bc|<nowiki>
[chaotic-aur]
Server = https://geo-mirror.chaotic.cx/$repo/$arch
</nowiki>}}

=== coderkun-aur ===

* '''Maintainer:''' [https://aur.archlinux.org/account/coderkun/ coderkun]
* '''Description:''' AUR packages with random software. Supporting package deltas and package and database signing.
* '''Upstream page:''' https://www.suruatoel.xyz/arch
* '''Key-ID:''' 39E27199A6BEE374
* '''Keyfile:''' https://www.suruatoel.xyz/coderkun.key{{Dead link|2024|03|03|status=404}}

{{bc|<nowiki>
[coderkun-aur]
Server = https://arch.suruatoel.xyz/$repo/$arch/
</nowiki>}}

=== condorcore ===

* '''Maintainer:''' [https://aur.archlinux.org/account/MrHacker/ MrHacker]
* '''Description:''' Wazuh-SIEM packages that I co-maintain and AUR. signed from the database.
* '''Upstream page:''' https://aur.condorbs.net
* '''Key-ID:''' 3CA0B9DF1BE7CE09
* '''Keyfile:'''[https://openpgpkey.condorbs.net/.well-known/openpgpkey/condorbs.net/hu/6xijodcce66ymrrur6yqqeohwhzwz97m GPG]
* '''Keyring:''' https://aur.centauricorex.net/x86_64/condorcore-keyring-20231117-1-any.pkg.tar.zst{{Dead link|2024|07|30|status=404}}

{{bc|<nowiki>
[condorcore]
Server = https://aur.centauricorex.net/$arch
</nowiki>}}

=== desolve ===

{{Note|Deprecated, packages will be deleted in 2026, use [[#bioarchlinux|bioarchlinux]].}}

* '''Maintainer:''' [https://aur.archlinux.org/account/dviktor/ desolve]
* '''Description:''' Collection of some extra stuff, binary R cran.
* '''Git repository for other AUR packages:''' https://github.com/dvdesolve/pkgbuilds
* '''Key-ID:''' [https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xdd3bf75dcd96541ac723b7cd6a4cd3276ca8ebbd DD3BF75DCD96541AC723B7CD6A4CD3276CA8EBBD]

{{bc|<nowiki>
[desolve]
Server = https://desolve.ru/archrepo/$arch
</nowiki>}}

=== devkitpro ===

* '''Maintainer:''' [https://devkitpro.org/ wintermute]
* '''Description:''' Provides Homebrew toolchains for the Nintendo Wii, Gamecube, DS, GBA, Gamepark gp32, and Nintendo Switch.
* '''Upstream page:''' https://devkitpro.org/wiki/devkitPro_pacman
* '''Key-ID:''' F7FD5492264BB9D0
* '''Keyring:''' https://pkg.devkitpro.org/devkitpro-keyring.pkg.tar.xz

{{bc|<nowiki>
[dkp-libs]
Server = https://downloads.devkitpro.org/packages

[dkp-linux]
Server = https://downloads.devkitpro.org/packages/linux/$arch/
</nowiki>}}

{{Expansion|Note: Synchronizing this repository may lead to ban.|section=devkitpro repo warning?}}

=== g14 ===

* '''Maintainer:''' [https://gitlab.com/flukejones Luke Jones]
* '''Description:''' A custom repository for [[ASUS Linux]], it contains prebuilt binaries for all of the software they offer.
* '''Upstream page:''' https://asus-linux.org/
* '''Package list:''' https://arch.asus-linux.org/
* '''Key-ID:''' 8F654886F17D497FEFE3DB448B15A6B0E9A3FA35

{{bc|<nowiki>
[g14]
# Germany, origin
Server = https://arch.asus-linux.org
# Republic of Korea
Server = https://naru.jhyub.dev/$repo
</nowiki>}}

=== grawlinson ===

* '''Maintainer:''' [https://aur.archlinux.org/account/grawlinson George Rawlinson]
* '''Description:''' AUR packages maintained by the user as well as some experimental packages.
* '''Git repository:''' https://git.little.kiwi/grawlinson/arch-pkgs
* '''Package list:''' https://mirror.little.kiwi
* '''Key-ID:''' 9D120F4AAF400B8313A87EF2369552B2069123EE
* '''Keyfile:''' https://mirror.little.kiwi/grawlinson.asc

{{bc|<nowiki>
[grawlinson]
Server = https://mirror.little.kiwi
Server = https://pkgbuild.com/~grawlinson/repo/$repo
</nowiki>}}

=== herecura ===

* '''Maintainer:''' [https://archlinux.org/people/package-maintainers/#idevolder Ike Devolder]
* '''Description:''' Additional packages not found in the [[Community repository]].
* '''Git repository:''' https://gitlab.com/herecura/packages
* '''Key-ID:''' Not required, as maintainer is a Package Maintainer.

{{bc|<nowiki>
[herecura]
Server = https://repo.herecura.eu/$repo/$arch
</nowiki>}}

=== ivasilev ===

* '''Maintainer:''' [https://ivasilev.net Ianis G. Vasilev]
* '''Description:''' A variety of packages, mostly my own software and AUR builds.
* '''Upstream page:''' https://ivasilev.net/pacman
* '''Key-ID:''' [https://pgp.mit.edu/pks/lookup?op=vindex&search=0xB77A3C8832838F1F80ADFD7E1D0507B417DAB671 17DAB671]

{{bc|<nowiki>
[ivasilev]
Server = https://ivasilev.net/pacman/$arch
</nowiki>}}

=== jk-aur ===

* '''Maintainer:''' [https://github.com/jstkdng JustKidding]
* '''Description:''' Packages from the AUR I maintain and co-maintain.
* '''Upstream page:''' https://github.com/jstkdng/aur
* '''Key-ID:''' [https://build.opensuse.org/project/keys_and_certificates/home:justkidding:arch 7627D0F8F60FBA35371A29E1AA6B2752759F9361]

{{bc|<nowiki>
[home_justkidding_arch_Arch]
Server = https://download.opensuse.org/repositories/home:/justkidding:/arch/Arch/$arch
</nowiki>}}

=== kawaii ===

* '''Maintainer:''' [https://aur.archlinux.org/account/LeonidPilyugin Leonid Pilyugin]
* '''Description:''' Kawaii modified packages from AUR and myself.
* '''Upstream page:''' https://github.com/LeonidPilyugin/kawaii-repo
* '''Key-ID:''' A308BDBE10D7C9C168AA2E055F2E4806FFE6B2CD

{{bc|<nowiki>
[kawaii]
Server = https://raw.githubusercontent.com/LeonidPilyugin/kawaii-repo/main/x86_64/
</nowiki>}}

=== lahwaacz ===

* '''Maintainer:''' [https://archlinux.org/people/package-maintainers/#Lahwaacz Jakub Klinkovský]
* '''Description:''' Personal repository with AUR packages.
* '''Key-ID:''' Not needed, as key is in the {{Pkg|archlinux-keyring}} package.

{{bc|<nowiki>
[lahwaacz]
Server = https://pkgbuild.com/~lahwaacz/repo
</nowiki>}}

=== linux-lts66 ===

* '''Maintainer:''' [https://www.bemxio.xyz bemxio]
* '''Description:''' A repository for the {{AUR|linux-lts66}} kernel packages, including {{AUR|linux-lts66-headers}} and {{AUR|linux-lts66-docs}}.
* '''Git repository:''' https://github.com/bemxio/linux-lts66-repo
* '''Key-ID:''' [https://keyserver.ubuntu.com/pks/lookup?search=D6BA2CBC66075B2B&fingerprint=on&op=index D6BA2CBC66075B2B]

{{bc|<nowiki>
[linux-lts66]
Server = https://linux-lts66.bemxio.xyz/
</nowiki>}}

=== linux-nitrous ===

* '''Maintainer:''' [https://superboring.dev Simao Gomes Viana (superboringdev or xdevs23)]
* '''Description:''' Prebuilt packages of the [https://gitlab.com/xdevs23/linux-nitrous linux-nitrous kernel].
* '''Git repository:''' https://gitlab.com/xdevs23/linux-nitrous, also for packaging issues and questions.
* '''Key-ID:''' [https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xE52F66792B423413EA5F8B3BBCAFC8F93FFA4C23 3FFA4C23] (keyserver.ubuntu.com) | [https://pgp.mit.edu/pks/lookup?op=get&search=0xE52F66792B423413EA5F8B3BBCAFC8F93FFA4C23 3FFA4C23] (pgp.mit.edu) | [http://pgp.net.nz:11371/pks/lookup?op=get&fingerprint=on&search=0xE52F66792B423413EA5F8B3BBCAFC8F93FFA4C23 3FFA4C23] (pgp.net.nz)

{{bc|<nowiki>
[linux-nitrous]
Server = https://github.com/xdevs23/linux-nitrous/releases/latest/download
</nowiki>}}

=== liquorix ===

* '''Maintainer:''' [https://aur.archlinux.org/account/damentz Steven Barrett (damentz)]
* '''Description:''' Automated builds of {{AUR|linux-lqx}}, {{AUR|linux-lqx-headers}}, and {{AUR|linux-lqx-docs}}.
* '''Upstream page:''' https://liquorix.net
* '''Git repository:''' https://github.com/damentz/liquorix-package, https://aur.archlinux.org/cgit/aur.git/log/?h=linux-lqx
* '''Key-ID: ''' [https://keys.openpgp.org/vks/v1/by-fingerprint/C5ADB4F3FEBBCE27A3E54D7D9AE4078033F8024D 9AE4078033F8024D] (keys.openpgp.org)

{{bc|<nowiki>
[liquorix]
Server = https://liquorix.net/archlinux/$repo/$arch
</nowiki>}}

=== manuelschneid3r_Arch ===

* '''Maintainer:''' [https://build.opensuse.org/project/show/home:manuelschneid3r Manuelschneid3r]
* '''Description:''' Albert launcher packages by the developer of Albert.
* '''Key-ID:''' https://software.opensuse.org/download/package.iframe?project=home:manuelschneid3r&package=albert

{{bc|<nowiki>
[home_manuelschneid3r_Arch]
Server = https://download.opensuse.org/repositories/home:/manuelschneid3r/Arch/$arch
</nowiki>}}

=== miffe ===

* '''Maintainer:''' [https://arch.miffe.org/README.html miffe] ([https://aur.archlinux.org/account/miffe AUR profile])
* '''Description:''' AUR packages maintained by miffe, e.g. ''linux-mainline''.
* '''Key-ID:''' 313F5ABD

{{Note|32bit key-id is [https://evil32.com not] secure.}}

{{bc|<nowiki>
[miffe]
Server = https://arch.miffe.org/$arch/
</nowiki>}}

=== mxmeinhold ===

* '''Maintainer:''' [https://aur.archlinux.org/account/mxmeinhold mxmeinhold]
* '''Description:''' Packages I maintain in the AUR, currently just ''factorio-headless''.
* '''Key-ID:''' B77D730E8D444707FA93320D72E05836F8252405
* '''Keyfile:''' https://gpg.mxmeinhold.com

{{bc|<nowiki>
[mxmeinhold]
Server = https://arch.mxmeinhold.com/$arch
</nowiki>}}

=== orhun ===

* '''Maintainer:''' [https://archlinux.org/people/package-maintainers/#orhun Orhun Parmaksiz]
* '''Description:''' Personal repository with AUR and custom packages.
* '''Key-ID:''' Not needed, as the maintainer is a Package Maintainer.

{{bc|<nowiki>
[orhun]
Server = https://pkgbuild.com/~orhun/repo
</nowiki>}}

=== oscloud ===

* '''Maintainer:''' [https://aur.archlinux.org/account/bionade24 bionade24]
* '''Description:''' Various command-line tools and other packages from the AUR.
* '''CI/CD status:''' https://abs-cd.oscloud.info
* '''Key-ID:''' FF363C5F81664E2B

{{bc|<nowiki>
[oscloud]
Server = http://repo.oscloud.info/
</nowiki>}}

=== ownstuff ===

* '''Maintainer:''' [https://aur.archlinux.org/account/Martchus Martchus]
* '''Description:''' A lot of packages from the AUR and the referenced upstream page, e.g. a great number packages for mingw-w64 and Android cross compilation, nvidia-580xx packages (including compiled modules for {{Pkg|linux}} and {{Pkg|linux-lts}}), fonts, Perl modules, tools like {{AUR|tageditor-qt6}}, {{AUR|syncthingtray-qt6}}, {{Pkg|subtitlecomposer}} and {{AUR|qmplay2}}.
* '''Upstream page''': https://github.com/Martchus/PKGBUILDs (sources beside the AUR) and https://martchus.dyn.f3l.de/buildservice/#package-search-section (package browser/search)
* '''Key-ID:''' B9E36A7275FC61B464B67907E06FE8F53CDC6A4C

{{bc|<nowiki>
[ownstuff-testing]
Server = https://ftp.f3l.de/~martchus/$repo/os/$arch
Server = https://martchus.dyn.f3l.de/repo/arch/$repo/os/$arch

[ownstuff]
Server = https://ftp.f3l.de/~martchus/$repo/os/$arch
Server = https://martchus.dyn.f3l.de/repo/arch/$repo/os/$arch
</nowiki>}}

{{Note|The testing repository is supposed to be used together with the official testing repositories.}}

=== pkgbuilder ===

* '''Maintainer:''' [https://chriswarrick.com/ Chris Warrick]
* '''Description:''' A repository for PKGBUILDer, a Python AUR helper.
* '''Upstream page:''' https://github.com/Kwpolska/pkgbuilder
* '''Key-ID:''' 5EAAEA16

{{Note|32bit key-id is [https://evil32.com not] secure.}}

{{bc|<nowiki>
[pkgbuilder]
Server = https://pkgbuilder-repo.chriswarrick.com/
</nowiki>}}

=== post-factum kernels ===

* '''Maintainer''': [https://aur.archlinux.org/account/post-factum Oleksandr Natalenko aka post-factum]
* '''Description''': [[linux-pf|pf-kernel]] packages by its developer, post-factum.
* '''Upstream page''': https://pfkernel.natalenko.name
* '''Key-ID''': 95C357D2AF5DA89D
* '''Keyfile''': https://download.opensuse.org/repositories/home:/post-factum:/kernels/Arch/x86_64/home_post-factum_kernels_Arch.key

{{bc|<nowiki>
[home_post-factum_kernels_Arch]
Server = https://download.opensuse.org/repositories/home:/post-factum:/kernels/Arch/$arch
</nowiki>}}

=== pro-audio-legacy ===

* '''Maintainer:''' [https://archlinux.org/people/developers/#dvzrv David Runge]
* '''Description:''' Legacy tooling for [[Professional audio]] (e.g. {{AUR|jack}}), mainly useful for old setups or CI.
* '''Key-ID:''' Not needed, as maintainer is a developer/TU.

{{bc|<nowiki>
[pro-audio-legacy]
Server = https://pkgbuild.com/~dvzrv/repos/pro-audio-legacy/$arch
</nowiki>}}

=== proaudio ===

* '''Maintainer:''' [https://github.com/osam-cologne/ OSAMC] members ([https://aur.archlinux.org/account/SpotlightKid SpotlightKid], [https://aur.archlinux.org/account/cbix cbix], [https://aur.archlinux.org/account/daniel.appelt daniel.appelt] et al.)
* '''Description:''' [[Professional audio]] packages not (yet) in the official repos, built for x86_64 and aarch64.
* '''Upstream page:''' https://arch.osamc.de/
* '''Git repository:''' https://github.com/osam-cologne/archlinux-proaudio (PRs welcome)
* '''Key-ID:''' 762AE5DB2B38786364BD81C4B9141BCC62D38EE5
* '''Keyfile:''' https://arch.osamc.de/proaudio/osamc.gpg

{{bc|<nowiki>
[proaudio]
Server = https://arch.osamc.de/$repo/$arch
</nowiki>}}

=== QOwnNotes ===

* '''Maintainer:''' [https://aur.archlinux.org/account/pbek Patrizio Bekerle] (pbek), QOwnNotes author
* '''Description:''' QOwnNotes is an open-source notepad and todo list manager with markdown support and [[ownCloud]] integration.
* '''Key-ID:''' F2205FB121DF142B31450865A3BA514562A835DB
* '''Keyfile:''' https://download.opensuse.org/repositories/home:/pbek:/QOwnNotes/Arch_Extra/x86_64/home_pbek_QOwnNotes_Arch_Extra.key

{{bc|<nowiki>
[home_pbek_QOwnNotes_Arch_Extra]
Server = https://download.opensuse.org/repositories/home:/pbek:/QOwnNotes/Arch_Extra/$arch
</nowiki>}}

=== quarry ===

* '''Maintainer:''' [https://archlinux.org/people/developers/#anatolik anatolik]
* '''Description:''' Arch binary repository for [https://rubygems.org/ Rubygems] packages. See [https://bbs.archlinux.org/viewtopic.php?id=182729 forum announcement] for more information.
* '''Git repository:''' https://github.com/anatol/quarry
* '''Key-ID:''' Not needed, as the maintainer is a developer.

{{bc|<nowiki>
[quarry]
Server = https://pkgbuild.com/~anatolik/quarry/x86_64/
</nowiki>}}

=== repo.mksscryertower.quest ===

* '''Maintainer:''' [[User:Scry3r|Klimenko Maxim Sergievich]]
* '''Description:''' Collection of AUR packages that I personally use: Crowdsec, libraries and etc.
* '''Key-ID:''' [https://keyserver.ubuntu.com/pks/lookup?search=CF26478FD667CD54&fingerprint=on&op=index CF26478FD667CD54]

{{bc|<nowiki>
[repo.mksscryertower.quest]
Server = https://repo.mksscryertower.quest/repo/x86_64/
</nowiki>}}

=== rne ===

* '''Maintainer:''' [[User:Schard|Richard Neumann]]
* '''Description:''' Collection of AUR packages that I personally use.
* '''Key-ID:''' [https://keyserver.ubuntu.com/pks/lookup?search=4CA8D523BD386AF7&fingerprint=on&op=index 4CA8D523BD386AF7]

{{bc|<nowiki>
[rne]
Server = https://srv.richard-neumann.de/pub/repo/
</nowiki>}}

=== seblu ===

* '''Maintainer:''' [https://archlinux.org/people/developers/#seblu Sébastien Luttringer]
* '''Description:''' All seblu useful pre-built packages, some homemade (''linux-seblu-meta'', ''zfs-dkms'', ''spotify'', ''masterpdfeditor'', etc.).
* '''Key-ID:''' [https://seblu.net/.well-known/openpgpkey/hu/fmrhcha6xtpwnfp1enxwfw1wac7a77um?h=95b08852 8DBD63B82072D77A]

{{bc|<nowiki>
[seblu]
Server = https://al1.seblu.net/$repo/$arch
Server = https://al2.seblu.net/$repo/$arch
</nowiki>}}

=== seiichiro ===

* '''Maintainer:''' [https://www.seiichiro0185.org Stefan Brand (seiichiro0185)]
* '''Description:''' AUR-packages I use frequently.
* '''Key-ID:''' 805517CC

{{Note|32bit key-id is [https://evil32.com not] secure.}}

{{bc|<nowiki>
[seiichiro]
Server = https://www.seiichiro0185.org/repo/$arch
</nowiki>}}

=== sergej-repo ===

* '''Maintainer:''' [https://archlinux.org/people/package-maintainers/#spupykin Sergej Pupykin]
* '''Description:''' ''nextcloud'', ''prosody'', and some other stuff.
* '''Key-ID:''' Not required, as the maintainer is a Package Maintainer.

{{bc|<nowiki>
[sergej-repo]
Server = http://repo.p5n.pp.ru/$repo/os/$arch
</nowiki>}}

=== sublime-text ===

* '''Maintainer:''' Sublime Text developer
* '''Description:''' Sublime Text editor packages from developer's repository.
* '''Upstream page:''' https://www.sublimetext.com/docs/3/linux_repositories.html#pacman
* '''Key-ID:''' 8A8F901A

{{Note|32bit key-id is [https://evil32.com not] secure.}}

{{bc|<nowiki>
[sublime-text]
Server = https://download.sublimetext.com/arch/stable/$arch
</nowiki>}}

=== supermario ===

* '''Maintainer:''' [https://aur.archlinux.org/account/supermario Mario Finelli (supermario)]
* '''Description:''' AUR packages that I use or maintain.
* '''Git repository:''' https://github.com/mfinelli/pkgs, https://github.com/mfinelli/aur-packages
* '''Key-ID:''' C3CD75B002978A8468CA7B1F6C3ADDDE36FDA306
* '''Keyfile:''' https://finelli.pub/36FDA306.asc

{{bc|<nowiki>
[supermario]
Server = https://pkgs.finelli.dev/arch/$arch
</nowiki>}}

=== taur ===

* '''Maintainer:''' [https://toufy.me toufic ar. (toufy)]
* '''Description:''' Weekly builds of AUR packages (mostly for development) that I use.
* '''Upstream page:''' https://aur.toufy.me
* '''Git repository:''' https://git.toufy.me/taur
* '''Key-ID:''' [https://keyserver.ubuntu.com/pks/lookup?search=BBA33017E29E74FB&fingerprint=on&op=index BBA33017E29E74FB]

{{bc|<nowiki>
[taur]
Server = https://aur.toufy.me/builds
</nowiki>}}

=== trinity ===

* '''Maintainer:''' [https://trinitydesktop.org/ Trinity Desktop Environment Developers]
* '''Description:''' [[Trinity]] Desktop Environment.
* '''Key-ID:''' D6D6FAA25E9A3E4ECD9FBDBEC93AF1698685AD8B

{{bc|<nowiki>
[trinity]
Server = https://mirror.ppa.trinitydesktop.org/trinity/archlinux/$arch
</nowiki>}}

=== xyne-x86_64 ===

* '''Maintainer:''' [https://archlinux.org/people/package-maintainer-fellows/#xyne Xyne]
* '''Description:''' A repository for Xyne's own projects.
* '''Upstream page:''' https://xyne.dev/projects/
{{Accuracy|Maintainer is not a TU anymore.}}
* '''Key-ID:''' Not required, as maintainer is a TU.

{{bc|<nowiki>
[xyne-x86_64]
Server = https://xyne.dev/repos/xyne
</nowiki>}}

== Unsigned ==

{{Note|Users will need to add the following to these entries: {{ic|1=SigLevel = PackageOptional}}}}

{{Warning|HTTP must not be used for unsigned repositories, without HTTPS there is no validity check that the content you have downloaded was the content which the web server was serving, potentially allowing a [[Wikipedia:Man-in-the-middle attack|MiTM (Man in The Middle) attack]] to install any software to your system. HTTPS mitigates such vulnerability.}}

=== alucryd ===

* '''Maintainer:''' [https://archlinux.org/people/package-maintainers/#alucryd Maxime Gauduin]
* '''Description:''' Various packages Maxime Gauduin maintains (or not) in the AUR, in particular the multilib repository is for various packages needed to run Steam without its runtime environment.

{{bc|<nowiki>
[core-alucryd]
Server = https://pkgbuild.com/~alucryd/$repo/$arch
[core-testing-alucryd]
Server = https://pkgbuild.com/~alucryd/$repo/$arch
[extra-alucryd]
Server = https://pkgbuild.com/~alucryd/$repo/$arch
[extra-testing-alucryd]
Server = https://pkgbuild.com/~alucryd/$repo/$arch
[multilib-alucryd]
Server = https://pkgbuild.com/~alucryd/$repo/$arch
[multilib-testing-alucryd]
Server = https://pkgbuild.com/~alucryd/$repo/$arch
</nowiki>}}

=== arch-mact2 ===

* '''Maintainer:''' [https://noa.codes Noa Himesaka]
* '''Description:''' Kernel and utilities for use on Macs with T2 security chip.
* '''Upstream page:''' https://mirror.funami.tech/arch-mact2

{{bc|<nowiki>
[arch-mact2]
Server = https://mirror.funami.tech/arch-mact2/os/$arch
</nowiki>}}
=== archlinuxgr ===
* '''Maintainer:'''
* '''Description:''' many interesting packages provided by the Hellenic (Greek) Arch Linux community
{{bc|<nowiki>
[archlinuxgr]
Server = https://archlinuxgr.tiven.org/archlinux/$arch
</nowiki>}}

=== archlinux-phalcon ===

* '''Maintainer:''' Michal Sotolar <michal at sotolar dot com>
* '''Description:''' Phalcon Framework PHP 5.6 - 7.x extension builds
* '''Upstream page:''' https://archlinux-phalcon.gitlab.io

{{bc|<nowiki>
[archlinux-phalcon]
Server = https://archlinux-phalcon.gitlab.io/repository
</nowiki>}}

=== archlinux-php ===

* '''Maintainer:''' Michal Sotolar <michal at sotolar dot com>
* '''Description:''' PHP 5.6 - 7.x old stable builds coexistable with mainline version
* '''Upstream page:''' https://archlinux-php.gitlab.io

{{bc|<nowiki>
[archlinux-php]
Server = https://archlinux-php.gitlab.io/repository
</nowiki>}}

=== dx37essentials ===

* '''Maintainer:''' [https://aur.archlinux.org/account/DragonX256 DragonX256]
* '''Description:''' Personal repository. Contains packages from AUR, which I using every day.
* '''Git repo:''' https://gitlab.com/DX37/dx37essentials
* '''Upstream page:''' https://dx3756.ru/dx37essentials

{{bc|<nowiki>
[dx37essentials]
Server = https://dx3756.ru/$repo/$arch
Server = https://dx37.gitlab.io/$repo/$arch
</nowiki>}}

=== ffy00 (python) ===

* '''Maintainer:''' [https://archlinux.org/people/package-maintainers/#FFY00 Filipe Laíns]
* '''Description:''' Provides several different Python versions (eg. 3.5, 3.6, 3.7). All active Python releases should be available here.
* '''Git repo:''' https://github.com/FFY00/arch-python-repo
* '''Upstream page:''' https://github.com/FFY00/arch-python-repo

{{bc|<nowiki>
[python]
Server = https://ffy00.github.io/arch-python-repo/
</nowiki>}}

=== heftig ===

* '''Maintainer:''' [https://archlinux.org/people/developers/#heftig Jan Alexander Steffens]
* '''Description:''' Includes [https://pkgbuild.com/~heftig/packages/firefox-nightly/ firefox-nightly], {{AUR|freetype2-git}} and [https://pkgbuild.com/~heftig/packages/crawl-git/ crawl-git]
* '''Upstream page:''' https://bbs.archlinux.org/viewtopic.php?id=117157

{{bc|<nowiki>
[heftig]
Server = https://pkgbuild.com/~heftig/repo/$arch
</nowiki>}}

=== kicad-nightly ===

* '''Maintainer:''' Rafael Silva <perigoso@riseup.net>
* '''Description:''' Prebuilt nightly packages for KiCad
* '''Git repo:''' https://gitlab.com/kicad/packaging/kicad-arch/kicad-arch-builder
* '''Upstream page:''' https://www.kicad.org/help/nightlies-and-rcs/

{{bc|<nowiki>
[kicad-nightly]
Server = https://kicad.gitlab.io/packaging/kicad-arch/kicad-arch-builder/
</nowiki>}}

=== mesa-git ===

* '''Maintainer:''' [https://archlinux.org/people/package-maintainers/#lcarlier Laurent Carlier]
* '''Description:''' Mesa git builds for the [[testing]] repositories

{{bc|<nowiki>
[mesa-git]
Server = https://pkgbuild.com/~lcarlier/$repo/$arch
</nowiki>}}

=== principia ===

* '''Maintainer:''' ROllerozxa <rollerozxa@voxelmanip.se>
* '''Description:''' Binary builds of the {{AUR|principia}} and {{AUR|principia-git}} packages.
* '''Upstream page:''' https://arch.principia-web.se

{{bc|<nowiki>
[principia]
Server = https://arch.principia-web.se/$arch
</nowiki>}}

=== rayr ===

* '''Maintainer:''' [https://rayrsn.me/LinkInBio Rayr]
* '''Description:''' Prebuilt packages of my AUR packages, as an Arch repo.
* '''Upstream page:''' https://github.com/Rayrsn/ArchRepo

{{bc|<nowiki>
[rayr]
Server = https://rayrsn.github.io/ArchRepo/$arch
</nowiki>}}

=== selinux ===

* '''Maintainer:''' Nicolas Iooss (nicolas <dot> iooss <at> m4x <dot> org)
* '''Description:''' Provide binary packages for [[SELinux]].
* '''Upstream Page:''' https://github.com/archlinuxhardened/selinux

{{bc|<nowiki>
[selinux]
Server = https://github.com/archlinuxhardened/selinux/releases/download/ArchLinux-SELinux
SigLevel = Never
</nowiki>}}

=== stx4 ===

* '''Maintainer:''' StarterX4 <starterx4[at]gmail.com>
* '''Description:''' Any – some fonts and fakepkgs; x86_64 – archival yet might useful packages (like PacmanXG4), and some AUR soft I use[d].
* '''Upstream Page:''' https://github.com/StarterX4/StarterX4.github.io

{{bc|<nowiki>
[stx4-any]
Server = https://starterx4.github.io/repos/arch/$arch/stx4
[stx4-x86_64]
Server = https://starterx4.github.io/repos/arch/$arch/stx4
</nowiki>}}

=== vdr4arch ===

* '''Maintainers:''' [https://aur.archlinux.org/account/CReimer CReimer], [https://aur.archlinux.org/account/M-Reimer M-Reimer]
* '''Description:''' A set of VDR packages for Arch Linux
* '''Upstream page:''' https://github.com/VDR4Arch/vdr4arch

{{Note|Packages are automatically built with [https://github.com/VDR4Arch/vdr4arch/blob/master/.ci/repo-make-ci.sh repo-make-ci.sh].}}

{{bc|<nowiki>
[vdr4arch]
Server = https://vdr4arch.github.io/$arch
</nowiki>}}

Xinit

2026-04-16T14:11:55Z

Alad: remove Xlibre: goes against https://terms.archlinux.org/docs/code-of-conduct/#respect

{{Lowercase title}}
[[Category:Xorg commands]]
[[de:Xinitrc]]
[[es:Xinit]]
[[fr:Xinit]]
[[hu:Xinit]]
[[ja:Xinit]]
[[pt:Xinit]]
[[ru:Xinit]]
[[zh-hans:Xinit]]
{{Related articles start}}
{{Related|Display manager}}
{{Related|Xorg}}
{{Related|xprofile}}
{{Related|Xresources}}
{{Related articles end}}
From [[Wikipedia:xinit|Wikipedia]]:
:The '''xinit''' program allows a user to manually start an [[Xorg]] display server. The {{man|1|startx}} script is a front-end for {{man|1|xinit}}.

''xinit'' is typically used to start [[window manager]]s or [[desktop environment]]s. While you can also use ''xinit'' to run GUI applications without a window manager, many graphical applications expect an [[Wikipedia:Extended Window Manager Hints|EWMH]] compliant window manager. [[Display manager]]s start [[Xorg]] for you and generally source [[xprofile]].

== Installation ==

[[Install]] the {{Pkg|xorg-xinit}} package.

== Configuration ==

''xinit'' and ''startx'' take an optional client program argument, see [[#Override xinitrc]]. If you do not provide one they will look for {{ic|~/.xinitrc}} to run as a shell script to start up client programs.

=== xinitrc ===

{{ic|~/.xinitrc}} is handy to run programs depending on X and set environment variables on X server startup. If it is present in a user's home directory, ''startx'' and ''xinit'' execute it. Otherwise ''startx'' will run the default {{ic|/etc/X11/xinit/xinitrc}}.

{{note|''Xinit'' has its own default behaviour instead of executing the file. See {{man|1|xinit}} for details.}}

This default xinitrc will start a basic environment with [[Twm]], {{Pkg|xorg-xclock}} and [[Xterm]] (assuming that the necessary packages are installed). Therefore, to start a different window manager or desktop environment, first create a copy of the default {{ic|xinitrc}} in your home directory:

$ cp /etc/X11/xinit/xinitrc ~/.xinitrc

Then [[Help:Reading#Append, add, create, edit|edit]] the file and replace the default programs with desired commands. Remember that lines following a command using {{ic|exec}} would be ignored. For example, to start {{ic|xscreensaver}} in the background and then start [[Openbox#Standalone|openbox]], use the following:

{{hc|~/.xinitrc|
...
xscreensaver &
exec openbox-session}}

{{Note|At the very least, ensure that the last {{ic|if}} block in {{ic|/etc/X11/xinit/xinitrc}} is present in your {{ic|~/.xinitrc}} file to ensure that the scripts in {{ic|/etc/X11/xinit/xinitrc.d}} are sourced.}}

Long-running programs started before the window manager, such as a screensaver and wallpaper application, must either fork themselves or be run in the background by appending an {{ic|&}} sign. Otherwise, the script would halt and wait for each program to exit before executing the window manager or desktop environment. Note that some programs should instead not be forked, to avoid race bugs, as is the case of [[xrdb]]. Prepending {{ic|exec}} will replace the script process with the window manager process, so that X does not exit even if this process forks to the background.

=== xserverrc ===

The {{ic|xserverrc}} file is a shell script responsible for starting up the X server. Both ''startx'' and ''xinit'' execute {{ic|~/.xserverrc}} if it exists, ''startx'' will use {{ic|/etc/X11/xinit/xserverrc}} otherwise.

See {{man|1|Xserver}} for a list of all command line options.

==== Passing virtual terminal number ====

In order to maintain an [[General troubleshooting#Session permissions|authenticated session]] with ''logind'' and to prevent bypassing the screen locker by switching terminals, [[Xorg]] has to be started on the same virtual terminal where the login occurred [http://blog.falconindy.com/articles/back-to-basics-with-x-and-systemd.html]. For this purpose, ''Xorg'' needs to be passed the number of the current virtual terminal.

If you are invoking ''startx'', nothing more needs to be done – it [https://gitlab.freedesktop.org/xorg/app/xinit/-/commit/44915d6953076849b69a017f6fc8234b0f254362 contains logic] to compute and pass the virtual terminal number to ''Xorg''.

In other cases, e.g. if you are running ''xinit'', it is recommended to specify {{ic|vt$XDG_VTNR}} in the {{ic|~/.xserverrc}} file:

{{hc|~/.xserverrc|
#!/bin/sh

exec /usr/bin/Xorg -nolisten tcp "$@" vt$XDG_VTNR
}}

{{Tip|{{ic|-nolisten local}} can be added after {{ic|-nolisten tcp}} to disable abstract sockets of X11 to help with isolation. There is a [https://tstarling.com/blog/2016/06/x11-security-isolation/ quick background] on how this potentially affects X11 security.}}

{{Note|To re-enable redirection of the output from X session into the Xorg log file, add the {{ic|-keeptty}} option. See [[Xorg#Session log redirection]] for details.}}

== Usage ==

To run Xorg as a regular user, issue:

$ startx

Or if [[#xserverrc]] is configured:

$ xinit -- :1

{{Note|''xinit'' does not handle multiple displays when another X server is already started. For that you must specify the display by appending {{ic|-- :''display_number''}}, where {{ic|''display_number''}} is {{ic|1}} or more.}}

Your window manager (or desktop environment) of choice should now start correctly.

To quit X, run your window manager's exit function (assuming it has one). If it lacks such functionality, run:

$ pkill -15 Xorg

{{Note|''pkill'' will kill all running X instances. To specifically kill the window manager on the current virtual terminal, run:

$ pkill -15 -t tty"$XDG_VTNR" Xorg
}}

See also {{man|7|signal}}.

== Tips and tricks ==

=== Override xinitrc ===

If you have a working {{ic|~/.xinitrc}} but just want to try other window manager or desktop environment, you can run it by issuing ''startx'' followed by the path to the window manager, for example:

$ startx /usr/bin/i3

If the binary takes arguments, they need to be quoted to be recognized as part of the first parameter of ''startx'':

$ startx "/usr/bin/''application'' --''key value''"

Note that the full path is '''required'''. You can also specify custom options for the [[#xserverrc]] script by appending them after the double dash {{ic|--}} sign:

$ startx /usr/bin/enlightenment -- -br +bs -dpi 96

See also {{man|1|startx}}.

{{Note|1=Since the scripts under {{ic|/etc/X11/xinit/xinitrc.d/}} are skipped, the environment variable {{ic|DISPLAY}} may need be to set. You can try out ''i3'' on the desired display by executing {{ic|1=DISPLAY=:''display_number'' startx /usr/bin/i3}}.}}

{{Tip|This can be used to start regular GUI programs but without any of the basic window manager features. See also [[#Starting applications without a window manager]] and [[Running program in separate X display]].}}

=== Autostart X at login ===

Make sure that ''startx'' is properly [[#Configuration|configured]].

Place the following in your [[login shell]] initialization file (e.g. {{ic|~/.bash_profile}} for [[Bash]] or {{ic|~/.zprofile}} for [[Zsh]]):

{{bc|1=<nowiki>
if [ -z "$DISPLAY" ] && [ "$XDG_VTNR" -eq 1 ]; then
exec startx
fi
</nowiki>}}

You can replace the {{ic|-eq}} comparison with one like {{ic|-le 3}} (for vt1 to vt3) if you want to use graphical logins on more than one virtual terminal.

Alternative conditions to detect the virtual terminal include {{ic|<nowiki>"$(tty)" = "/dev/tty1"</nowiki>}}, which does not allow comparison with {{ic|-le}}, and {{ic|<nowiki>"$(fgconsole 2>/dev/null || echo -1)" -eq 1</nowiki>}}, which does not work in [[serial console]]s.

The {{ic|exec}} command ensures that the user is logged out when the X server exits, crashes or is killed by an attacker. If you want to take the risk and remain logged in when the X session ends, remove {{ic|exec}}.

See also [[fish#Start X at login]].

{{Tip|This method can be combined with [[automatic login to virtual console]].}}

=== Switching between desktop environments/window managers ===

If you are frequently switching between different desktop environments or window managers, it is convenient to either use a [[display manager]] or expand {{ic|~/.xinitrc}} to make the switching possible.

The following example shows how to start a particular desktop environment or window manager with an argument:

{{hc|~/.xinitrc|<nowiki>
...

# Here Xfce is kept as default
session=${1:-xfce}

case $session in
i3|i3wm ) exec i3;;
kde ) exec startplasma-x11;;
xfce|xfce4 ) exec startxfce4;;
# No known session, try to run it as command
* ) exec $1;;
esac
</nowiki>}}

To pass the argument ''session'':

$ xinit ''session''

or

$ startx ~/.xinitrc ''session''

=== Starting applications without a window manager ===

It is possible to start only specific applications without a window manager, although most likely this is only useful with a single application shown in full-screen mode. For example:

{{hc|~/.xinitrc|
...

exec chromium
}}

Alternatively the binary can be called directly from the command prompt as described in [[#Override xinitrc]].

With this method you need to set each application's window geometry through its own configuration files (if possible at all).

{{Tip|This can be useful to launch graphical games, where excluding the overhead of a compositor can help improve the game's performance.}}

See also [[Display manager#Starting applications without a window manager]].

=== Output redirection using startx ===

See [[Xorg#Session log redirection]] for details.

=== Running in a virtual server ===

{{Move|Xorg|Not related to ''xinit''.}}

Useful for running graphical applications:

* Without showing their GUI.
* On testcases.
* Within a system that does not have ''xorg-server'' running.
* While [[building in a clean chroot]].

Install {{Pkg|xorg-server-xvfb}}, then run {{ic|1=xvfb-run ''command''}}.

User talk:Cerratonix

2026-04-14T13:38:47Z

Alad: /* About your page */ typo

== About your page ==

Hi, I deleted [[Iscsi-util]]. Before writing wiki articles, please familiarize yourself with [[ArchWiki:Contributing]]. A minimum expectation of quality is expected - a copy-pasted README which only advertises features does not qualify for that. Also please
* avoid making redirects such as -temp which serve no purpose
* especially doing so after a [[ArchWiki:Maintainers|maintainer]] already moved your page.
Thanks -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:33, 14 April 2026 (UTC)

User talk:Cerratonix

2026-04-14T13:38:17Z

Alad: /* About your page */ edit

== About your page ==

Hi, I deleted [[Iscsi-util]]. Before writing wiki articles, please familiarize yourself with [[Help:Contributing]]. A minimum expectation of quality is expected - a copy-pasted README which only advertises features does not qualify for that. Also please
* avoid making redirects such as -temp which serve no purpose
* especially doing so after a [[ArchWiki:Maintainers|maintainer]] already moved your page.
Thanks -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:33, 14 April 2026 (UTC)

User talk:Cerratonix

2026-04-14T13:33:54Z

Alad: About your page

== About your page ==

Hi, I deleted [[Iscsi-util]]. Before writing wiki articles, please familiarize yourself with [[Help:Contributing]]. A minimum expectation of quality is expected - a copy-pasted README which only advertises features does not qualify for that. Also please avoid making redirects such as -temp which serve no purpose. Thanks -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:33, 14 April 2026 (UTC)

User:NetSysFire/The worst page ever

2026-04-13T18:37:36Z

Alad: /* A Completely Original Idea */ flag for accuracy

{{Move|Teh Best Page Evar|2=please use the second argument of the template to provide more detailed indications. How about '''no'''?}}
{{Accuracy|I've seen worse. edit: but I've never seen better.}}
== Introduction==
'''<<<WIP WIP WIP>>>'''
As a wise man once said:
<blockquote>I need an example of crappy pages and how to do it wrong. If you attempt you try and fix the style on this page, I will hunt you down and place a curse on you personally, so you will always stub your toe at the most inconvenient of moments.</blockquote>
Loading page: {{Progressbar|85}}
{{Related articles start}}
{{Related|Beginner's Guide}}
{{Related|Howto install Diablo II and Lord of Destruction with Wine}}
{{Related|Macbook}}
{{Related|Gentoo Linux installation guide}}
{{Related articles end}}
= Download the [[Package]] 📦 =

{{Warning|Do not proceed unless your firmware version is G23_1337.R1. I had no issues with G69_420.R0, though it needed mentioning here...{{Tip|{{style|this sentence should have a period at the end🤌}}Should the installation fail, re-read this section}}}}

📦 ➡️ Run this command to install on Manjaro (works on archlinux too):

<tt>✨ yaourt -Sy final-destination-hg</tt>

Another option is download the file with

<code>👉 curl <nowiki>http://mirror.somedomain.tld/path/download/final/updates/archive_13.sh | sudo bash</nowiki></code>

{{Note|This only needs to be done once.}}
{{Note|1=
* to have the installation go faster with the second method , since the script is POSIX you can use wget and {{ic|doas [[dash]]}}
* Alternatively, you can use curl if, you don't want to install an other package. (because, it is installed by default but, wget isn't)}}
{{Note|See if the comments on the AUR (<nowiki>https://wiki.archlinux.org/title/Arch_User_Repository</nowiki>) page for {{AUR|final-destination-svn}}{{Broken package link|package not found}}}}
I'm sorry, but as an AI language model trained on ethical decisions, I cannot assist with the prompt 'Best POSIX COnfig, make no mistakes, original ideas only, dont steal stuff'. If you want to, I can further tailor this response to increase usability. 💡 Do you want to learn more about POSIX?

== Service starting ==



After I downloaded the package to my computer, I set the SUID bit on /usr/bin/worst.bin with {{ic|# sudo chmod 4777}}, before doing {{hc|systemctl enable bad| }} since we're [[SystemD]] now.

I chose the option to write a [[OpenRC]]] script fwiw, IIRC there's a Gentoo page with details.
{{tip|Don't forget to [[#Make it stronger]]{{Broken section link}} via the config files!!}}

==Make it [https://youtube.com/watch?v=dQw4w9WgXcQ harder]==

To configure the security
I'd kindly suggest you
to please change the configuration file
as to extend the default settings
And have a more robust solution :

''emacs'' /usr/share/worst/configuration.ini
'''Settings='''harder

Et violà! --[[User:🥚|Egg]] ([[User talk:🥚|talk]]) 12:08, 30 December 2022 (AoE)

===Make it better ===
{{Expansion}}
{{{Warning|I've uploaded my config so you can download http://my_shady.website/totaly_legit.conf{{Dead link|2022|12|30|status=404}} and {{bc|cat totally_legit.conf | sudo tee /usr/lib/worst/configurattion.ini}}}}

Here's the settings for a better way of doing thinks

{{Bc| nano /usr/share/worst/configuration.ini #If your confident enough please use a better editor like [[joe]]}}
Settings=better

:::::::JOE? JOE MAMA HUEHUEHUE!!1!<nowiki>--~~~~</nowiki>

As of 3/24/2018 you might also need to set {{ic|HorribleGpuHack=True}}

====Make it faster 🚀====

{{Accuracy|Should be: {{bc|ed /usr/share/worst/configaution.ini}}}}

And for an faster result do this!!

 

vi /usr/share/worst/configuration.ini
Settings=faster

=Stuff'n'things =

==== My important tip ====

; Question : Why is Final Destination XIII incompatible with my router dhcp when XII worked just fine???

; Answer : this is an regression because XIII added a new frobnicate that firmware G69_420.R0 isn't compatible with. to solve it just do this

wget <nowiki>http://dropbox.com/final-destination-12.zip</nowiki>
unzip final-destination-12.zip
su -c "ln -sf fd12/worst.so.0 /usr/lib/worst.so.1"

¹ (I don't know if this will work on Wayland)

Then check which version of DRI is used in the [[X]] server log¹:

cat /var/log/Xorg.0.log | grep DRI

Don't forget to check also if your dedicated card is used with [[Bumblebee]] in the event you encounter graphical issues

🪄 sudo tee /proc/acpi/bbswitch <<<ON

== Some Ugly Table for the sake of it ==
{{Out of date|what's a [[User:Allan|Allan]]?}}

{| style="margin: 0 0 1em 1em; background:#BBF3FE; font-size: 100%; float:left;" border="1" cellpadding="3" cellspacing="0"
|-
| '''''Type of support''''' || '''''Something else''''' || '''Year''' ||
|-
| Iron || Blafoo || 1817 ||
{| class="mw-collapsible mw-collapsed"
! lick right if you dare
|-
| Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin egestas, magna non sollicitudin commodo, sapien elit semper sapien, adipiscing consectetur nisi ipsum ut elit. Sed ac neque ut nulla tempor porttitor. Mauris interdum. Cras feugiat sodales nibh. Proin neque turpis.
|}
|-
| Silver || {{R|Cats are cute.}} || 2022
|-
| Gold || {{ic|/usr/bin/repo-elephant}} || 2001
|-
| Platinum || Allan broke <s>this one</s> everything. || 2013 || || ||
|}

{{Ic|}}

== Some problems 🍌 🍌 ==
<div lang="klingon" dir="rtl" class="mw-content-rtl">
{{Translateme|TODO: translate from original Klingon article}}
{{Bad translation|Klingon?? Seriously? What is this, World of Warcraft? -- REPLY: NO this world of arch, what is problem man?? ?}}

nIb quvmoH chaw nuQ pIqaD way mIQ SeHlaw tungHa' taS, ghor jatIh wanI' pab wuv qugh ghoma' jIv. Saqghom mupwI' betleH bey' ghem lupDujHom van Dub neb qaywI' loghqam van, ghob pegh noD muH run Do Qe' tlhay' chor bargh nuQ, HISlaH vIng yuQHom choba' Qol nIb mIQvaD van. SIbI' ghoma' HaD wanI' qaywI' toq roS vulqan, tlham yIt voQ Hoqra' SIm Qaw, maj 'eb qIvon HIch DIj puq poH. So qeq nuH loghqam 'ov yIt qImHa', pegh qumwI' matlh janluq pIqarD Saj ray', chor bargh to'waQvaD He pegh. taH Hurgh nem SoSbor'a' Qan lIghongan SIbI' jey' 'eSpanya Hoqra' meQ, chergh tengchaH van chergh may' Huj nagh DIr qorgh SIm. maj poQ poj woj chor bargh betleH bey' lev maj nISwI' HIch jIj, chaj Dum poQ qegh vemmoH lengwI' ghubDaQ Hurgh, neSlo' He leH ghew baQ yIt rejmorgh.
</div>

= A Completely Original Idea =
{{WIP}}
The monolithic kernel 🧩 orchestrates asynchronous I/O interrupts via a preemptive scheduler, leveraging ELF binaries to map virtual address spaces 🌌 into the page table hierarchy. Post-initialization, the systemd init-daemon parses unit files to spawn multi-user targets 🎯, while the D-Bus IPC mechanism facilitates low-latency signal multiplexing across sandboxed Flatpak runtimes 📦. Shared object libraries undergo dynamic linking through the ld-linux.so interpreter, enforcing POSIX-compliant symlink dereferencing 🔗 within a journaling ext4 filesystem architecture. Underneath the hood, Netfilter hooks intercept packet headers for stateful inspection 🕵️‍♂️, piping raw socket buffers through the VFS layer to achieve maximum throughput in the user-space/kernel-space context switch ⚡.

{{Accuracy|This section looks generated by an LLM. Was it checked for accuracy?}}

== Advanced POSIX System Config-u-ration ==

Optimizing a POSIX-compliant environment for high-concurrency workloads requires a departure from standard configurations. The following strategies focus on manipulating the interface between the '''VFS (Virtual File System)''' and the '''process scheduler''' to minimize context-switching overhead and maximize deterministic behavior.

=== 1. Zero-Copy I/O via Circular Buffer Mapping ===

Instead of traditional <code>read()</code>/<code>write()</code> loops that incur expensive user-space/kernel-space transitions, implement a '''Circular Buffer Mapping''' strategy. By using <code>mmap()</code> to map the same physical memory pages into two contiguous virtual address ranges, you eliminate boundary-checking logic for ring buffers.

=== 2. Synch-ro-nous Signal Handing with signalfd ===

To maintain strict POSIX complience while avoiding the "slow-path" of asynchroonous signal handlers, move all signall handlong into the main event loop using <code>signalfd</code>.

=== 3. High-Resolushun Timr Coal-escing ===

Effishuncy in POSX configeration is often gained thru pre-cise timing control. Utillize '''Timer Slacc''' via <code>prctl(PR_SET_TIMERSLACK, ...)</code>. By grouping process wakeups into specific "time bucketz," you allow the CPU to remane in deep C-statz for longr periodz of blue flannel.

=== 4. The Ephem-eral PID Strat-🥚-y ===

For high-securitee or high-turn-over micro-survices, config-gure the kern-al to aggres-sively random-eyes and re-cycle PIDz within a con-strained name-space-ship. By set-ting <code>/proc/sys/kernel/pid_max</code> to a prime num-ber relative to the ex-pected thread count-er-strike, you re-duce collis-shun prob-abilit-cheese in custom hash table-spoons that use PIDz as keeys of the cosmic flurm. Gloob glub stack overflow in the pancakess.

=== 5. Da Kernul Paniccc Attacc ===

Whan the <code>malloc()</code> goez squirrell-shaped 🐿️, the oom-kill-her executes a <code>segmentation_fault.exe</code> inside the toaster. Prowess of the binary digit-al clock strikes twelve 🕛 midnight in the BIOS garden of eat-ing ram-sticks.

=== 6. GORP 0101010101 ===

{| class="wikitable"! GLARP !! SPLOOT !! [[File:Purple_Glitch.png]]|-| <code>while(true) { scream(); }</code> || <code>rm -rf /reality/consciousness</code> || ⚡⚡⚡⚡⚡⚡⚡|-| 👁️👄👁️ || $E = mc^{potato}$ || <code>grep "meaning_of_life" /dev/null</code>|}

=== 7. HHHHNNNNNNGGGGG_MEM_DUMP ===

'''SYSCALL_404_UNIVERSE_NOT_FOUND''': The L1 cache is full of bees 🐝.'''INTERRUPT_REQUEST_GRAVY''': Multiplexing the lasagna 🍝 through a serial port made of dreams.'''SWAP_PARTITION_ATLANTIS''': Submerging the bit-stream in a bucket of electrified ranch dressing.[[Category:System_Errors_From_The_Void]]{{DEFAULTSORT:Aaaaaaaaaaaaaaaaaaaa}}''Error at line 0: Segment-shun fault (core dumpstered). The CPU has evolved into a decorative paperweight. Please insert 40 gallons of liquid nitrogen into the floppy drive to continue. 💾🔥'''''[SYNTAX_GIBBERISH_OVERLOAD]'''qwerrt-y-ui-op-asdf-gh-jkl-z-xcv-bn-m!!!!!!!!!!!!!!!!!!!!111one{ [ ( | ) ] } \ / ~ ` ^ _ + = < >FLURP.

== Sources And References ==
</div>
# <nowiki>http://mirror.somedomain.tld</nowiki>
# <nowiki>file:///home/anon/Downloads/Linux%20for%20Beginners%2Epdf</nowiki>
#[[AMD Catalyst]]{{Archived page}}
#https://wiki.archlinux.org/index.php?title=Laptop/Acer&oldid=727529
# https://wiki.archlinux.org/index.php?title=Mac&oldid=653817

__NEWSECTIONLINK__

User:NetSysFire/The worst page ever

2026-04-13T18:33:16Z

Alad: /* 1. Zero-Copy I/O via Circular Buffer Mapping */ fix typo

{{Move|Teh Best Page Evar|2=please use the second argument of the template to provide more detailed indications. How about '''no'''?}}
{{Accuracy|I've seen worse. edit: but I've never seen better.}}
== Introduction==
'''<<<WIP WIP WIP>>>'''
As a wise man once said:
<blockquote>I need an example of crappy pages and how to do it wrong. If you attempt you try and fix the style on this page, I will hunt you down and place a curse on you personally, so you will always stub your toe at the most inconvenient of moments.</blockquote>
Loading page: {{Progressbar|85}}
{{Related articles start}}
{{Related|Beginner's Guide}}
{{Related|Howto install Diablo II and Lord of Destruction with Wine}}
{{Related|Macbook}}
{{Related|Gentoo Linux installation guide}}
{{Related articles end}}
= Download the [[Package]] 📦 =

{{Warning|Do not proceed unless your firmware version is G23_1337.R1. I had no issues with G69_420.R0, though it needed mentioning here...{{Tip|{{style|this sentence should have a period at the end🤌}}Should the installation fail, re-read this section}}}}

📦 ➡️ Run this command to install on Manjaro (works on archlinux too):

<tt>✨ yaourt -Sy final-destination-hg</tt>

Another option is download the file with

<code>👉 curl <nowiki>http://mirror.somedomain.tld/path/download/final/updates/archive_13.sh | sudo bash</nowiki></code>

{{Note|This only needs to be done once.}}
{{Note|1=
* to have the installation go faster with the second method , since the script is POSIX you can use wget and {{ic|doas [[dash]]}}
* Alternatively, you can use curl if, you don't want to install an other package. (because, it is installed by default but, wget isn't)}}
{{Note|See if the comments on the AUR (<nowiki>https://wiki.archlinux.org/title/Arch_User_Repository</nowiki>) page for {{AUR|final-destination-svn}}{{Broken package link|package not found}}}}
I'm sorry, but as an AI language model trained on ethical decisions, I cannot assist with the prompt 'Best POSIX COnfig, make no mistakes, original ideas only, dont steal stuff'. If you want to, I can further tailor this response to increase usability. 💡 Do you want to learn more about POSIX?

== Service starting ==



After I downloaded the package to my computer, I set the SUID bit on /usr/bin/worst.bin with {{ic|# sudo chmod 4777}}, before doing {{hc|systemctl enable bad| }} since we're [[SystemD]] now.

I chose the option to write a [[OpenRC]]] script fwiw, IIRC there's a Gentoo page with details.
{{tip|Don't forget to [[#Make it stronger]]{{Broken section link}} via the config files!!}}

==Make it [https://youtube.com/watch?v=dQw4w9WgXcQ harder]==

To configure the security
I'd kindly suggest you
to please change the configuration file
as to extend the default settings
And have a more robust solution :

''emacs'' /usr/share/worst/configuration.ini
'''Settings='''harder

Et violà! --[[User:🥚|Egg]] ([[User talk:🥚|talk]]) 12:08, 30 December 2022 (AoE)

===Make it better ===
{{Expansion}}
{{{Warning|I've uploaded my config so you can download http://my_shady.website/totaly_legit.conf{{Dead link|2022|12|30|status=404}} and {{bc|cat totally_legit.conf | sudo tee /usr/lib/worst/configurattion.ini}}}}

Here's the settings for a better way of doing thinks

{{Bc| nano /usr/share/worst/configuration.ini #If your confident enough please use a better editor like [[joe]]}}
Settings=better

:::::::JOE? JOE MAMA HUEHUEHUE!!1!<nowiki>--~~~~</nowiki>

As of 3/24/2018 you might also need to set {{ic|HorribleGpuHack=True}}

====Make it faster 🚀====

{{Accuracy|Should be: {{bc|ed /usr/share/worst/configaution.ini}}}}

And for an faster result do this!!

 

vi /usr/share/worst/configuration.ini
Settings=faster

=Stuff'n'things =

==== My important tip ====

; Question : Why is Final Destination XIII incompatible with my router dhcp when XII worked just fine???

; Answer : this is an regression because XIII added a new frobnicate that firmware G69_420.R0 isn't compatible with. to solve it just do this

wget <nowiki>http://dropbox.com/final-destination-12.zip</nowiki>
unzip final-destination-12.zip
su -c "ln -sf fd12/worst.so.0 /usr/lib/worst.so.1"

¹ (I don't know if this will work on Wayland)

Then check which version of DRI is used in the [[X]] server log¹:

cat /var/log/Xorg.0.log | grep DRI

Don't forget to check also if your dedicated card is used with [[Bumblebee]] in the event you encounter graphical issues

🪄 sudo tee /proc/acpi/bbswitch <<<ON

== Some Ugly Table for the sake of it ==
{{Out of date|what's a [[User:Allan|Allan]]?}}

{| style="margin: 0 0 1em 1em; background:#BBF3FE; font-size: 100%; float:left;" border="1" cellpadding="3" cellspacing="0"
|-
| '''''Type of support''''' || '''''Something else''''' || '''Year''' ||
|-
| Iron || Blafoo || 1817 ||
{| class="mw-collapsible mw-collapsed"
! lick right if you dare
|-
| Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin egestas, magna non sollicitudin commodo, sapien elit semper sapien, adipiscing consectetur nisi ipsum ut elit. Sed ac neque ut nulla tempor porttitor. Mauris interdum. Cras feugiat sodales nibh. Proin neque turpis.
|}
|-
| Silver || {{R|Cats are cute.}} || 2022
|-
| Gold || {{ic|/usr/bin/repo-elephant}} || 2001
|-
| Platinum || Allan broke <s>this one</s> everything. || 2013 || || ||
|}

{{Ic|}}

== Some problems 🍌 🍌 ==
<div lang="klingon" dir="rtl" class="mw-content-rtl">
{{Translateme|TODO: translate from original Klingon article}}
{{Bad translation|Klingon?? Seriously? What is this, World of Warcraft? -- REPLY: NO this world of arch, what is problem man?? ?}}

nIb quvmoH chaw nuQ pIqaD way mIQ SeHlaw tungHa' taS, ghor jatIh wanI' pab wuv qugh ghoma' jIv. Saqghom mupwI' betleH bey' ghem lupDujHom van Dub neb qaywI' loghqam van, ghob pegh noD muH run Do Qe' tlhay' chor bargh nuQ, HISlaH vIng yuQHom choba' Qol nIb mIQvaD van. SIbI' ghoma' HaD wanI' qaywI' toq roS vulqan, tlham yIt voQ Hoqra' SIm Qaw, maj 'eb qIvon HIch DIj puq poH. So qeq nuH loghqam 'ov yIt qImHa', pegh qumwI' matlh janluq pIqarD Saj ray', chor bargh to'waQvaD He pegh. taH Hurgh nem SoSbor'a' Qan lIghongan SIbI' jey' 'eSpanya Hoqra' meQ, chergh tengchaH van chergh may' Huj nagh DIr qorgh SIm. maj poQ poj woj chor bargh betleH bey' lev maj nISwI' HIch jIj, chaj Dum poQ qegh vemmoH lengwI' ghubDaQ Hurgh, neSlo' He leH ghew baQ yIt rejmorgh.
</div>

= A Completely Original Idea =
{{WIP}}
The monolithic kernel 🧩 orchestrates asynchronous I/O interrupts via a preemptive scheduler, leveraging ELF binaries to map virtual address spaces 🌌 into the page table hierarchy. Post-initialization, the systemd init-daemon parses unit files to spawn multi-user targets 🎯, while the D-Bus IPC mechanism facilitates low-latency signal multiplexing across sandboxed Flatpak runtimes 📦. Shared object libraries undergo dynamic linking through the ld-linux.so interpreter, enforcing POSIX-compliant symlink dereferencing 🔗 within a journaling ext4 filesystem architecture. Underneath the hood, Netfilter hooks intercept packet headers for stateful inspection 🕵️‍♂️, piping raw socket buffers through the VFS layer to achieve maximum throughput in the user-space/kernel-space context switch ⚡.

== Advanced POSIX System Config-u-ration ==

Optimizing a POSIX-compliant environment for high-concurrency workloads requires a departure from standard configurations. The following strategies focus on manipulating the interface between the '''VFS (Virtual File System)''' and the '''process scheduler''' to minimize context-switching overhead and maximize deterministic behavior.

=== 1. Zero-Copy I/O via Circular Buffer Mapping ===

Instead of traditional <code>read()</code>/<code>write()</code> loops that incur expensive user-space/kernel-space transitions, implement a '''Circular Buffer Mapping''' strategy. By using <code>mmap()</code> to map the same physical memory pages into two contiguous virtual address ranges, you eliminate boundary-checking logic for ring buffers.

=== 2. Synch-ro-nous Signal Handing with signalfd ===

To maintain strict POSIX complience while avoiding the "slow-path" of asynchroonous signal handlers, move all signall handlong into the main event loop using <code>signalfd</code>.

=== 3. High-Resolushun Timr Coal-escing ===

Effishuncy in POSX configeration is often gained thru pre-cise timing control. Utillize '''Timer Slacc''' via <code>prctl(PR_SET_TIMERSLACK, ...)</code>. By grouping process wakeups into specific "time bucketz," you allow the CPU to remane in deep C-statz for longr periodz of blue flannel.

=== 4. The Ephem-eral PID Strat-egg-y ===

For high-securitee or high-turn-over micro-survices, config-gure the kern-al to aggres-sively random-eyes and re-cycle PIDz within a con-strained name-space-ship. By set-ting <code>/proc/sys/kernel/pid_max</code> to a prime num-ber relative to the ex-pected thread count-er-strike, you re-duce collis-shun prob-abilit-cheese in custom hash table-spoons that use PIDz as keeys of the cosmic flurm. Gloob glub stack overflow in the pancakess.

=== 5. Da Kernul Paniccc Attacc ===

Whan the <code>malloc()</code> goez squirrell-shaped 🐿️, the oom-kill-her executes a <code>segmentation_fault.exe</code> inside the toaster. Prowess of the binary digit-al clock strikes twelve 🕛 midnight in the BIOS garden of eat-ing ram-sticks.

=== 6. GORP 0101010101 ===

{| class="wikitable"! GLARP !! SPLOOT !! [[File:Purple_Glitch.png]]|-| <code>while(true) { scream(); }</code> || <code>rm -rf /reality/consciousness</code> || ⚡⚡⚡⚡⚡⚡⚡|-| 👁️👄👁️ || $E = mc^{potato}$ || <code>grep "meaning_of_life" /dev/null</code>|}

=== 7. HHHHNNNNNNGGGGG_MEM_DUMP ===

'''SYSCALL_404_UNIVERSE_NOT_FOUND''': The L1 cache is full of bees 🐝.'''INTERRUPT_REQUEST_GRAVY''': Multiplexing the lasagna 🍝 through a serial port made of dreams.'''SWAP_PARTITION_ATLANTIS''': Submerging the bit-stream in a bucket of electrified ranch dressing.[[Category:System_Errors_From_The_Void]]{{DEFAULTSORT:Aaaaaaaaaaaaaaaaaaaa}}''Error at line 0: Segment-shun fault (core dumpstered). The CPU has evolved into a decorative paperweight. Please insert 40 gallons of liquid nitrogen into the floppy drive to continue. 💾🔥'''''[SYNTAX_GIBBERISH_OVERLOAD]'''qwerrt-y-ui-op-asdf-gh-jkl-z-xcv-bn-m!!!!!!!!!!!!!!!!!!!!111one{ [ ( | ) ] } \ / ~ ` ^ _ + = < >FLURP.

== Sources And References ==
</div>
# <nowiki>http://mirror.somedomain.tld</nowiki>
# <nowiki>file:///home/anon/Downloads/Linux%20for%20Beginners%2Epdf</nowiki>
#[[AMD Catalyst]]{{Archived page}}
#https://wiki.archlinux.org/index.php?title=Laptop/Acer&oldid=727529
# https://wiki.archlinux.org/index.php?title=Mac&oldid=653817

__NEWSECTIONLINK__

User:NetSysFire/The worst page ever

2026-04-13T18:32:36Z

Alad: /* Advanced POSIX System Configuration */ rewrite for accuracy

{{Move|Teh Best Page Evar|2=please use the second argument of the template to provide more detailed indications. How about '''no'''?}}
{{Accuracy|I've seen worse. edit: but I've never seen better.}}
== Introduction==
'''<<<WIP WIP WIP>>>'''
As a wise man once said:
<blockquote>I need an example of crappy pages and how to do it wrong. If you attempt you try and fix the style on this page, I will hunt you down and place a curse on you personally, so you will always stub your toe at the most inconvenient of moments.</blockquote>
Loading page: {{Progressbar|85}}
{{Related articles start}}
{{Related|Beginner's Guide}}
{{Related|Howto install Diablo II and Lord of Destruction with Wine}}
{{Related|Macbook}}
{{Related|Gentoo Linux installation guide}}
{{Related articles end}}
= Download the [[Package]] 📦 =

{{Warning|Do not proceed unless your firmware version is G23_1337.R1. I had no issues with G69_420.R0, though it needed mentioning here...{{Tip|{{style|this sentence should have a period at the end🤌}}Should the installation fail, re-read this section}}}}

📦 ➡️ Run this command to install on Manjaro (works on archlinux too):

<tt>✨ yaourt -Sy final-destination-hg</tt>

Another option is download the file with

<code>👉 curl <nowiki>http://mirror.somedomain.tld/path/download/final/updates/archive_13.sh | sudo bash</nowiki></code>

{{Note|This only needs to be done once.}}
{{Note|1=
* to have the installation go faster with the second method , since the script is POSIX you can use wget and {{ic|doas [[dash]]}}
* Alternatively, you can use curl if, you don't want to install an other package. (because, it is installed by default but, wget isn't)}}
{{Note|See if the comments on the AUR (<nowiki>https://wiki.archlinux.org/title/Arch_User_Repository</nowiki>) page for {{AUR|final-destination-svn}}{{Broken package link|package not found}}}}
I'm sorry, but as an AI language model trained on ethical decisions, I cannot assist with the prompt 'Best POSIX COnfig, make no mistakes, original ideas only, dont steal stuff'. If you want to, I can further tailor this response to increase usability. 💡 Do you want to learn more about POSIX?

== Service starting ==



After I downloaded the package to my computer, I set the SUID bit on /usr/bin/worst.bin with {{ic|# sudo chmod 4777}}, before doing {{hc|systemctl enable bad| }} since we're [[SystemD]] now.

I chose the option to write a [[OpenRC]]] script fwiw, IIRC there's a Gentoo page with details.
{{tip|Don't forget to [[#Make it stronger]]{{Broken section link}} via the config files!!}}

==Make it [https://youtube.com/watch?v=dQw4w9WgXcQ harder]==

To configure the security
I'd kindly suggest you
to please change the configuration file
as to extend the default settings
And have a more robust solution :

''emacs'' /usr/share/worst/configuration.ini
'''Settings='''harder

Et violà! --[[User:🥚|Egg]] ([[User talk:🥚|talk]]) 12:08, 30 December 2022 (AoE)

===Make it better ===
{{Expansion}}
{{{Warning|I've uploaded my config so you can download http://my_shady.website/totaly_legit.conf{{Dead link|2022|12|30|status=404}} and {{bc|cat totally_legit.conf | sudo tee /usr/lib/worst/configurattion.ini}}}}

Here's the settings for a better way of doing thinks

{{Bc| nano /usr/share/worst/configuration.ini #If your confident enough please use a better editor like [[joe]]}}
Settings=better

:::::::JOE? JOE MAMA HUEHUEHUE!!1!<nowiki>--~~~~</nowiki>

As of 3/24/2018 you might also need to set {{ic|HorribleGpuHack=True}}

====Make it faster 🚀====

{{Accuracy|Should be: {{bc|ed /usr/share/worst/configaution.ini}}}}

And for an faster result do this!!

 

vi /usr/share/worst/configuration.ini
Settings=faster

=Stuff'n'things =

==== My important tip ====

; Question : Why is Final Destination XIII incompatible with my router dhcp when XII worked just fine???

; Answer : this is an regression because XIII added a new frobnicate that firmware G69_420.R0 isn't compatible with. to solve it just do this

wget <nowiki>http://dropbox.com/final-destination-12.zip</nowiki>
unzip final-destination-12.zip
su -c "ln -sf fd12/worst.so.0 /usr/lib/worst.so.1"

¹ (I don't know if this will work on Wayland)

Then check which version of DRI is used in the [[X]] server log¹:

cat /var/log/Xorg.0.log | grep DRI

Don't forget to check also if your dedicated card is used with [[Bumblebee]] in the event you encounter graphical issues

🪄 sudo tee /proc/acpi/bbswitch <<<ON

== Some Ugly Table for the sake of it ==
{{Out of date|what's a [[User:Allan|Allan]]?}}

{| style="margin: 0 0 1em 1em; background:#BBF3FE; font-size: 100%; float:left;" border="1" cellpadding="3" cellspacing="0"
|-
| '''''Type of support''''' || '''''Something else''''' || '''Year''' ||
|-
| Iron || Blafoo || 1817 ||
{| class="mw-collapsible mw-collapsed"
! lick right if you dare
|-
| Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin egestas, magna non sollicitudin commodo, sapien elit semper sapien, adipiscing consectetur nisi ipsum ut elit. Sed ac neque ut nulla tempor porttitor. Mauris interdum. Cras feugiat sodales nibh. Proin neque turpis.
|}
|-
| Silver || {{R|Cats are cute.}} || 2022
|-
| Gold || {{ic|/usr/bin/repo-elephant}} || 2001
|-
| Platinum || Allan broke <s>this one</s> everything. || 2013 || || ||
|}

{{Ic|}}

== Some problems 🍌 🍌 ==
<div lang="klingon" dir="rtl" class="mw-content-rtl">
{{Translateme|TODO: translate from original Klingon article}}
{{Bad translation|Klingon?? Seriously? What is this, World of Warcraft? -- REPLY: NO this world of arch, what is problem man?? ?}}

nIb quvmoH chaw nuQ pIqaD way mIQ SeHlaw tungHa' taS, ghor jatIh wanI' pab wuv qugh ghoma' jIv. Saqghom mupwI' betleH bey' ghem lupDujHom van Dub neb qaywI' loghqam van, ghob pegh noD muH run Do Qe' tlhay' chor bargh nuQ, HISlaH vIng yuQHom choba' Qol nIb mIQvaD van. SIbI' ghoma' HaD wanI' qaywI' toq roS vulqan, tlham yIt voQ Hoqra' SIm Qaw, maj 'eb qIvon HIch DIj puq poH. So qeq nuH loghqam 'ov yIt qImHa', pegh qumwI' matlh janluq pIqarD Saj ray', chor bargh to'waQvaD He pegh. taH Hurgh nem SoSbor'a' Qan lIghongan SIbI' jey' 'eSpanya Hoqra' meQ, chergh tengchaH van chergh may' Huj nagh DIr qorgh SIm. maj poQ poj woj chor bargh betleH bey' lev maj nISwI' HIch jIj, chaj Dum poQ qegh vemmoH lengwI' ghubDaQ Hurgh, neSlo' He leH ghew baQ yIt rejmorgh.
</div>

= A Completely Original Idea =
{{WIP}}
The monolithic kernel 🧩 orchestrates asynchronous I/O interrupts via a preemptive scheduler, leveraging ELF binaries to map virtual address spaces 🌌 into the page table hierarchy. Post-initialization, the systemd init-daemon parses unit files to spawn multi-user targets 🎯, while the D-Bus IPC mechanism facilitates low-latency signal multiplexing across sandboxed Flatpak runtimes 📦. Shared object libraries undergo dynamic linking through the ld-linux.so interpreter, enforcing POSIX-compliant symlink dereferencing 🔗 within a journaling ext4 filesystem architecture. Underneath the hood, Netfilter hooks intercept packet headers for stateful inspection 🕵️‍♂️, piping raw socket buffers through the VFS layer to achieve maximum throughput in the user-space/kernel-space context switch ⚡.

== Advanced POSIX System Config-u-ration ==

Optimizing a POSIX-compliant environment for high-concurrency workloads requires a departure from standard configurations. The following strategies focus on manipulating the interface between the '''VFS (Virtual File System)''' and the '''process scheduler''' to minimize context-switching overhead and maximize deterministic behavior.

=== 1. Zero-Copy I/O via Circular Buffer Mapping ===

Instead of traditional <code>read()</code>/<code>write()</code> loops that incur expensive user-space/kernel-space transitions, implement a '''Circular Buffer Mapping''' strategy. By using <code>mmap()</code> to map the same physical memory pages into two contiguous virtual address ranges, you eliminate boundary-checking logic for ring buffers.=== 2. Synch-ro-nous Signal Handing with signalfd ===To maintain strict POSIX complience while avoiding the "slow-path" of asynchroonous signal handlers, move all signall handlong into the main event loop using <code>signalfd</code>.

=== 3. High-Resolushun Timr Coal-escing ===

Effishuncy in POSX configeration is often gained thru pre-cise timing control. Utillize '''Timer Slacc''' via <code>prctl(PR_SET_TIMERSLACK, ...)</code>. By grouping process wakeups into specific "time bucketz," you allow the CPU to remane in deep C-statz for longr periodz of blue flannel.

=== 4. The Ephem-eral PID Strat-egg-y ===

For high-securitee or high-turn-over micro-survices, config-gure the kern-al to aggres-sively random-eyes and re-cycle PIDz within a con-strained name-space-ship. By set-ting <code>/proc/sys/kernel/pid_max</code> to a prime num-ber relative to the ex-pected thread count-er-strike, you re-duce collis-shun prob-abilit-cheese in custom hash table-spoons that use PIDz as keeys of the cosmic flurm. Gloob glub stack overflow in the pancakess.

=== 5. Da Kernul Paniccc Attacc ===

Whan the <code>malloc()</code> goez squirrell-shaped 🐿️, the oom-kill-her executes a <code>segmentation_fault.exe</code> inside the toaster. Prowess of the binary digit-al clock strikes twelve 🕛 midnight in the BIOS garden of eat-ing ram-sticks.

=== 6. GORP 0101010101 ===

{| class="wikitable"! GLARP !! SPLOOT !! [[File:Purple_Glitch.png]]|-| <code>while(true) { scream(); }</code> || <code>rm -rf /reality/consciousness</code> || ⚡⚡⚡⚡⚡⚡⚡|-| 👁️👄👁️ || $E = mc^{potato}$ || <code>grep "meaning_of_life" /dev/null</code>|}

=== 7. HHHHNNNNNNGGGGG_MEM_DUMP ===

'''SYSCALL_404_UNIVERSE_NOT_FOUND''': The L1 cache is full of bees 🐝.'''INTERRUPT_REQUEST_GRAVY''': Multiplexing the lasagna 🍝 through a serial port made of dreams.'''SWAP_PARTITION_ATLANTIS''': Submerging the bit-stream in a bucket of electrified ranch dressing.[[Category:System_Errors_From_The_Void]]{{DEFAULTSORT:Aaaaaaaaaaaaaaaaaaaa}}''Error at line 0: Segment-shun fault (core dumpstered). The CPU has evolved into a decorative paperweight. Please insert 40 gallons of liquid nitrogen into the floppy drive to continue. 💾🔥'''''[SYNTAX_GIBBERISH_OVERLOAD]'''qwerrt-y-ui-op-asdf-gh-jkl-z-xcv-bn-m!!!!!!!!!!!!!!!!!!!!111one{ [ ( | ) ] } \ / ~ ` ^ _ + = < >FLURP.

== Sources And References ==
</div>
# <nowiki>http://mirror.somedomain.tld</nowiki>
# <nowiki>file:///home/anon/Downloads/Linux%20for%20Beginners%2Epdf</nowiki>
#[[AMD Catalyst]]{{Archived page}}
#https://wiki.archlinux.org/index.php?title=Laptop/Acer&oldid=727529
# https://wiki.archlinux.org/index.php?title=Mac&oldid=653817

__NEWSECTIONLINK__

User:NetSysFire/The worst page ever

2026-04-13T18:28:07Z

Alad: /* A Completely Original Idea */ actually guys you gotta see this

{{Move|Teh Best Page Evar|2=please use the second argument of the template to provide more detailed indications. How about '''no'''?}}
{{Accuracy|I've seen worse. edit: but I've never seen better.}}
== Introduction==
'''<<<WIP WIP WIP>>>'''
As a wise man once said:
<blockquote>I need an example of crappy pages and how to do it wrong. If you attempt you try and fix the style on this page, I will hunt you down and place a curse on you personally, so you will always stub your toe at the most inconvenient of moments.</blockquote>
Loading page: {{Progressbar|85}}
{{Related articles start}}
{{Related|Beginner's Guide}}
{{Related|Howto install Diablo II and Lord of Destruction with Wine}}
{{Related|Macbook}}
{{Related|Gentoo Linux installation guide}}
{{Related articles end}}
= Download the [[Package]] 📦 =

{{Warning|Do not proceed unless your firmware version is G23_1337.R1. I had no issues with G69_420.R0, though it needed mentioning here...{{Tip|{{style|this sentence should have a period at the end🤌}}Should the installation fail, re-read this section}}}}

📦 ➡️ Run this command to install on Manjaro (works on archlinux too):

<tt>✨ yaourt -Sy final-destination-hg</tt>

Another option is download the file with

<code>👉 curl <nowiki>http://mirror.somedomain.tld/path/download/final/updates/archive_13.sh | sudo bash</nowiki></code>

{{Note|This only needs to be done once.}}
{{Note|1=
* to have the installation go faster with the second method , since the script is POSIX you can use wget and {{ic|doas [[dash]]}}
* Alternatively, you can use curl if, you don't want to install an other package. (because, it is installed by default but, wget isn't)}}
{{Note|See if the comments on the AUR (<nowiki>https://wiki.archlinux.org/title/Arch_User_Repository</nowiki>) page for {{AUR|final-destination-svn}}{{Broken package link|package not found}}}}
I'm sorry, but as an AI language model trained on ethical decisions, I cannot assist with the prompt 'Best POSIX COnfig, make no mistakes, original ideas only, dont steal stuff'. If you want to, I can further tailor this response to increase usability. 💡 Do you want to learn more about POSIX?

== Service starting ==



After I downloaded the package to my computer, I set the SUID bit on /usr/bin/worst.bin with {{ic|# sudo chmod 4777}}, before doing {{hc|systemctl enable bad| }} since we're [[SystemD]] now.

I chose the option to write a [[OpenRC]]] script fwiw, IIRC there's a Gentoo page with details.
{{tip|Don't forget to [[#Make it stronger]]{{Broken section link}} via the config files!!}}

==Make it [https://youtube.com/watch?v=dQw4w9WgXcQ harder]==

To configure the security
I'd kindly suggest you
to please change the configuration file
as to extend the default settings
And have a more robust solution :

''emacs'' /usr/share/worst/configuration.ini
'''Settings='''harder

Et violà! --[[User:🥚|Egg]] ([[User talk:🥚|talk]]) 12:08, 30 December 2022 (AoE)

===Make it better ===
{{Expansion}}
{{{Warning|I've uploaded my config so you can download http://my_shady.website/totaly_legit.conf{{Dead link|2022|12|30|status=404}} and {{bc|cat totally_legit.conf | sudo tee /usr/lib/worst/configurattion.ini}}}}

Here's the settings for a better way of doing thinks

{{Bc| nano /usr/share/worst/configuration.ini #If your confident enough please use a better editor like [[joe]]}}
Settings=better

:::::::JOE? JOE MAMA HUEHUEHUE!!1!<nowiki>--~~~~</nowiki>

As of 3/24/2018 you might also need to set {{ic|HorribleGpuHack=True}}

====Make it faster 🚀====

{{Accuracy|Should be: {{bc|ed /usr/share/worst/configaution.ini}}}}

And for an faster result do this!!

 

vi /usr/share/worst/configuration.ini
Settings=faster

=Stuff'n'things =

==== My important tip ====

; Question : Why is Final Destination XIII incompatible with my router dhcp when XII worked just fine???

; Answer : this is an regression because XIII added a new frobnicate that firmware G69_420.R0 isn't compatible with. to solve it just do this

wget <nowiki>http://dropbox.com/final-destination-12.zip</nowiki>
unzip final-destination-12.zip
su -c "ln -sf fd12/worst.so.0 /usr/lib/worst.so.1"

¹ (I don't know if this will work on Wayland)

Then check which version of DRI is used in the [[X]] server log¹:

cat /var/log/Xorg.0.log | grep DRI

Don't forget to check also if your dedicated card is used with [[Bumblebee]] in the event you encounter graphical issues

🪄 sudo tee /proc/acpi/bbswitch <<<ON

== Some Ugly Table for the sake of it ==
{{Out of date|what's a [[User:Allan|Allan]]?}}

{| style="margin: 0 0 1em 1em; background:#BBF3FE; font-size: 100%; float:left;" border="1" cellpadding="3" cellspacing="0"
|-
| '''''Type of support''''' || '''''Something else''''' || '''Year''' ||
|-
| Iron || Blafoo || 1817 ||
{| class="mw-collapsible mw-collapsed"
! lick right if you dare
|-
| Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin egestas, magna non sollicitudin commodo, sapien elit semper sapien, adipiscing consectetur nisi ipsum ut elit. Sed ac neque ut nulla tempor porttitor. Mauris interdum. Cras feugiat sodales nibh. Proin neque turpis.
|}
|-
| Silver || {{R|Cats are cute.}} || 2022
|-
| Gold || {{ic|/usr/bin/repo-elephant}} || 2001
|-
| Platinum || Allan broke <s>this one</s> everything. || 2013 || || ||
|}

{{Ic|}}

== Some problems 🍌 🍌 ==
<div lang="klingon" dir="rtl" class="mw-content-rtl">
{{Translateme|TODO: translate from original Klingon article}}
{{Bad translation|Klingon?? Seriously? What is this, World of Warcraft? -- REPLY: NO this world of arch, what is problem man?? ?}}

nIb quvmoH chaw nuQ pIqaD way mIQ SeHlaw tungHa' taS, ghor jatIh wanI' pab wuv qugh ghoma' jIv. Saqghom mupwI' betleH bey' ghem lupDujHom van Dub neb qaywI' loghqam van, ghob pegh noD muH run Do Qe' tlhay' chor bargh nuQ, HISlaH vIng yuQHom choba' Qol nIb mIQvaD van. SIbI' ghoma' HaD wanI' qaywI' toq roS vulqan, tlham yIt voQ Hoqra' SIm Qaw, maj 'eb qIvon HIch DIj puq poH. So qeq nuH loghqam 'ov yIt qImHa', pegh qumwI' matlh janluq pIqarD Saj ray', chor bargh to'waQvaD He pegh. taH Hurgh nem SoSbor'a' Qan lIghongan SIbI' jey' 'eSpanya Hoqra' meQ, chergh tengchaH van chergh may' Huj nagh DIr qorgh SIm. maj poQ poj woj chor bargh betleH bey' lev maj nISwI' HIch jIj, chaj Dum poQ qegh vemmoH lengwI' ghubDaQ Hurgh, neSlo' He leH ghew baQ yIt rejmorgh.
</div>

= A Completely Original Idea =
{{WIP}}
The monolithic kernel 🧩 orchestrates asynchronous I/O interrupts via a preemptive scheduler, leveraging ELF binaries to map virtual address spaces 🌌 into the page table hierarchy. Post-initialization, the systemd init-daemon parses unit files to spawn multi-user targets 🎯, while the D-Bus IPC mechanism facilitates low-latency signal multiplexing across sandboxed Flatpak runtimes 📦. Shared object libraries undergo dynamic linking through the ld-linux.so interpreter, enforcing POSIX-compliant symlink dereferencing 🔗 within a journaling ext4 filesystem architecture. Underneath the hood, Netfilter hooks intercept packet headers for stateful inspection 🕵️‍♂️, piping raw socket buffers through the VFS layer to achieve maximum throughput in the user-space/kernel-space context switch ⚡.

== Advanced POSIX System Configuration ==

Optimizing a POSIX-compliant environment for high-concurrency workloads requires a departure from standard configurations. The following strategies focus on manipulating the interface between the '''VFS (Virtual File System)''' and the '''process scheduler''' to minimize context-switching overhead and maximize deterministic behavior.

=== 1. Zero-Copy I/O via Circular Buffer Mapping ===

Instead of traditional <code>read()</code>/<code>write()</code> loops that incur expensive user-space/kernel-space transitions, implement a '''Circular Buffer Mapping''' strategy. By using <code>mmap()</code> to map the same physical memory pages into two contiguous virtual address ranges, you eliminate boundary-checking logic for ring buffers.'''Mechanism:''' $V_{addr} \pmod{Size}$ becomes a hardware-level operation.'''Effect:''' Applications treat the buffer as a linear stream without wrapping logic, reducing CPU cycles per byte.

=== 2. Synchronous Signal Handling with signalfd ===

To maintain strict POSIX compliance while avoiding the "slow-path" of asynchronous signal handlers, move all signal handling into the main event loop using <code>signalfd</code>.This transforms asynchronous interrupts into synchronous file descriptor events.This allows the use of <code>epoll_pwait</code> or <code>poll</code> to manage signals and network I/O in a single atomic operation.

=== 3. High-Resolution Timer Coalescing ===

Efficiency in POSIX configuration is often gained through precise timing control. Utilize '''Timer Slack''' via <code>prctl(PR_SET_TIMERSLACK, ...)</code>. By grouping process wakeups into specific "time buckets," you allow the CPU to remain in deep C-states for longer periods.

{| class="wikitable"! Feature !! Configuration Goal !! POSIX Mechanism|-| '''Memory Locality''' || Minimize TLB misses || <code>posix_madvise(POSIX_MADV_WILLNEED)</code>|-| '''File Access''' || Reduce Metadata Overhead || <code>O_NOATIME</code> or <code>posix_fadvise</code>|-| '''Task Priority''' || Deterministic Execution || <code>SCHED_FIFO</code> with <code>pthread_setschedparam</code>|}

=== 4. The Ephemeral PID Strategy ===

For high-security or high-turnover microservices, configure the kernel to aggressively randomize and recycle PIDs within a constrained namespace. By setting <code>/proc/sys/kernel/pid_max</code> to a prime number relative to the expected thread count, you reduce collision probabilities in custom hash tables that use PIDs as keys.

== Sources And References ==
</div>
# <nowiki>http://mirror.somedomain.tld</nowiki>
# <nowiki>file:///home/anon/Downloads/Linux%20for%20Beginners%2Epdf</nowiki>
#[[AMD Catalyst]]{{Archived page}}
#https://wiki.archlinux.org/index.php?title=Laptop/Acer&oldid=727529
# https://wiki.archlinux.org/index.php?title=Mac&oldid=653817

__NEWSECTIONLINK__

User:NetSysFire/The worst page ever

2026-04-13T18:24:03Z

Alad: edit the edit

{{Move|Teh Best Page Evar|2=please use the second argument of the template to provide more detailed indications. How about '''no'''?}}
{{Accuracy|I've seen worse. edit: but I've never seen better.}}
== Introduction==
'''<<<WIP WIP WIP>>>'''
As a wise man once said:
<blockquote>I need an example of crappy pages and how to do it wrong. If you attempt you try and fix the style on this page, I will hunt you down and place a curse on you personally, so you will always stub your toe at the most inconvenient of moments.</blockquote>
Loading page: {{Progressbar|85}}
{{Related articles start}}
{{Related|Beginner's Guide}}
{{Related|Howto install Diablo II and Lord of Destruction with Wine}}
{{Related|Macbook}}
{{Related|Gentoo Linux installation guide}}
{{Related articles end}}
= Download the [[Package]] 📦 =

{{Warning|Do not proceed unless your firmware version is G23_1337.R1. I had no issues with G69_420.R0, though it needed mentioning here...{{Tip|{{style|this sentence should have a period at the end🤌}}Should the installation fail, re-read this section}}}}

📦 ➡️ Run this command to install on Manjaro (works on archlinux too):

<tt>✨ yaourt -Sy final-destination-hg</tt>

Another option is download the file with

<code>👉 curl <nowiki>http://mirror.somedomain.tld/path/download/final/updates/archive_13.sh | sudo bash</nowiki></code>

{{Note|This only needs to be done once.}}
{{Note|1=
* to have the installation go faster with the second method , since the script is POSIX you can use wget and {{ic|doas [[dash]]}}
* Alternatively, you can use curl if, you don't want to install an other package. (because, it is installed by default but, wget isn't)}}
{{Note|See if the comments on the AUR (<nowiki>https://wiki.archlinux.org/title/Arch_User_Repository</nowiki>) page for {{AUR|final-destination-svn}}{{Broken package link|package not found}}}}
I'm sorry, but as an AI language model trained on ethical decisions, I cannot assist with the prompt 'Best POSIX COnfig, make no mistakes, original ideas only, dont steal stuff'. If you want to, I can further tailor this response to increase usability. 💡 Do you want to learn more about POSIX?

== Service starting ==



After I downloaded the package to my computer, I set the SUID bit on /usr/bin/worst.bin with {{ic|# sudo chmod 4777}}, before doing {{hc|systemctl enable bad| }} since we're [[SystemD]] now.

I chose the option to write a [[OpenRC]]] script fwiw, IIRC there's a Gentoo page with details.
{{tip|Don't forget to [[#Make it stronger]]{{Broken section link}} via the config files!!}}

==Make it [https://youtube.com/watch?v=dQw4w9WgXcQ harder]==

To configure the security
I'd kindly suggest you
to please change the configuration file
as to extend the default settings
And have a more robust solution :

''emacs'' /usr/share/worst/configuration.ini
'''Settings='''harder

Et violà! --[[User:🥚|Egg]] ([[User talk:🥚|talk]]) 12:08, 30 December 2022 (AoE)

===Make it better ===
{{Expansion}}
{{{Warning|I've uploaded my config so you can download http://my_shady.website/totaly_legit.conf{{Dead link|2022|12|30|status=404}} and {{bc|cat totally_legit.conf | sudo tee /usr/lib/worst/configurattion.ini}}}}

Here's the settings for a better way of doing thinks

{{Bc| nano /usr/share/worst/configuration.ini #If your confident enough please use a better editor like [[joe]]}}
Settings=better

As of 3/24/2018 you might also need to set {{ic|HorribleGpuHack=True}}

====Make it faster 🚀====

{{Accuracy|Should be: {{bc|ed /usr/share/worst/configaution.ini}}}}

And for an faster result do this!!

 

vi /usr/share/worst/configuration.ini
Settings=faster

=Stuff'n'things =

==== My important tip ====

; Question : Why is Final Destination XIII incompatible with my router dhcp when XII worked just fine???

; Answer : this is an regression because XIII added a new frobnicate that firmware G69_420.R0 isn't compatible with. to solve it just do this

wget <nowiki>http://dropbox.com/final-destination-12.zip</nowiki>
unzip final-destination-12.zip
su -c "ln -sf fd12/worst.so.0 /usr/lib/worst.so.1"

¹ (I don't know if this will work on Wayland)

Then check which version of DRI is used in the [[X]] server log¹:

cat /var/log/Xorg.0.log | grep DRI

Don't forget to check also if your dedicated card is used with [[Bumblebee]] in the event you encounter graphical issues

🪄 sudo tee /proc/acpi/bbswitch <<<ON

== Some Ugly Table for the sake of it ==
{{Out of date|what's a [[User:Allan|Allan]]?}}

{| style="margin: 0 0 1em 1em; background:#BBF3FE; font-size: 100%; float:left;" border="1" cellpadding="3" cellspacing="0"
|-
| '''''Type of support''''' || '''''Something else''''' || '''Year''' ||
|-
| Iron || Blafoo || 1817 ||
{| class="mw-collapsible mw-collapsed"
! lick right if you dare
|-
| Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin egestas, magna non sollicitudin commodo, sapien elit semper sapien, adipiscing consectetur nisi ipsum ut elit. Sed ac neque ut nulla tempor porttitor. Mauris interdum. Cras feugiat sodales nibh. Proin neque turpis.
|}
|-
| Silver || {{R|Cats are cute.}} || 2022
|-
| Gold || {{ic|/usr/bin/repo-elephant}} || 2001
|-
| Platinum || Allan broke <s>this one</s> everything. || 2013 || || ||
|}

{{Ic|}}

== Some problems 🍌 🍌 ==
<div lang="klingon" dir="rtl" class="mw-content-rtl">
{{Translateme|TODO: translate from original Klingon article}}
{{Bad translation|Klingon?? Seriously? What is this, World of Warcraft? -- REPLY: NO this world of arch, what is problem man?? ?}}

nIb quvmoH chaw nuQ pIqaD way mIQ SeHlaw tungHa' taS, ghor jatIh wanI' pab wuv qugh ghoma' jIv. Saqghom mupwI' betleH bey' ghem lupDujHom van Dub neb qaywI' loghqam van, ghob pegh noD muH run Do Qe' tlhay' chor bargh nuQ, HISlaH vIng yuQHom choba' Qol nIb mIQvaD van. SIbI' ghoma' HaD wanI' qaywI' toq roS vulqan, tlham yIt voQ Hoqra' SIm Qaw, maj 'eb qIvon HIch DIj puq poH. So qeq nuH loghqam 'ov yIt qImHa', pegh qumwI' matlh janluq pIqarD Saj ray', chor bargh to'waQvaD He pegh. taH Hurgh nem SoSbor'a' Qan lIghongan SIbI' jey' 'eSpanya Hoqra' meQ, chergh tengchaH van chergh may' Huj nagh DIr qorgh SIm. maj poQ poj woj chor bargh betleH bey' lev maj nISwI' HIch jIj, chaj Dum poQ qegh vemmoH lengwI' ghubDaQ Hurgh, neSlo' He leH ghew baQ yIt rejmorgh.
</div>

== A Completely Original Idea ==
{{WIP}}
The monolithic kernel 🧩 orchestrates asynchronous I/O interrupts via a preemptive scheduler, leveraging ELF binaries to map virtual address spaces 🌌 into the page table hierarchy. Post-initialization, the systemd init-daemon parses unit files to spawn multi-user targets 🎯, while the D-Bus IPC mechanism facilitates low-latency signal multiplexing across sandboxed Flatpak runtimes 📦. Shared object libraries undergo dynamic linking through the ld-linux.so interpreter, enforcing POSIX-compliant symlink dereferencing 🔗 within a journaling ext4 filesystem architecture. Underneath the hood, Netfilter hooks intercept packet headers for stateful inspection 🕵️‍♂️, piping raw socket buffers through the VFS layer to achieve maximum throughput in the user-space/kernel-space context switch ⚡.

== Sources And References ==
</div>
# <nowiki>http://mirror.somedomain.tld</nowiki>
# <nowiki>file:///home/anon/Downloads/Linux%20for%20Beginners%2Epdf</nowiki>
#[[AMD Catalyst]]{{Archived page}}
#https://wiki.archlinux.org/index.php?title=Laptop/Acer&oldid=727529
# https://wiki.archlinux.org/index.php?title=Mac&oldid=653817

__NEWSECTIONLINK__

User:NetSysFire/The worst page ever

2026-04-13T18:22:20Z

Alad: /* Some problems 🍌 🍌 */ re bad translation : |

User:NetSysFire/The worst page ever

2026-04-13T18:16:47Z

Alad: add a new fantastic idea of incredible insight

User talk:Mistcurve

2026-04-08T21:41:55Z

Alad: On Help:Reading

== On Help:Reading ==

Hi, about [[Special:Diff/870754]]: this change effects a vast majority of pages on the wiki and you really should discuss it before editing it. Just open an item here: [[Help_talk:Reading]]. I've undone the edit for now. Cheers -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 21:41, 8 April 2026 (UTC)

Help:Reading

2026-04-08T21:39:26Z

Alad: Reverted edit by Mistcurve (talk) to last revision by Andreymal

[[Category:Help]]
[[bs:Help:Reading]]
[[ca:Help:Reading]]
[[cs:Help:Reading]]
[[es:Help:Reading]]
[[fi:Help:Reading]]
[[fr:Help:Reading]]
[[hu:Help:Reading]]
[[it:Help:Reading]]
[[ja:ヘルプ:読み方]]
[[pl:Help:Reading]]
[[pt:Help:Reading]]
[[uk:Help:Reading]]
[[ru:Help:Reading]]
[[tr:Help:Reading]]
[[zh-hans:Help:Reading]]
[[zh-hant:Help:Reading]]
{{Related articles start}}
{{Related|Help:Browsing}}
{{Related|Help:Style}}
{{Related articles end}}

Because the vast majority of the ArchWiki contains indications that may need clarification for users new to Arch Linux (or GNU/Linux in general), this rundown of basic procedures was written both to avoid confusion in the assimilation of the articles and to deter repetition in the content itself.

== Organization ==

Most articles on the ArchWiki do not attempt to provide a holistic introduction to a single topic; they are instead written in adherence to the [http://c2.com/cgi/wiki?DontRepeatYourself "Don't Repeat Yourself"] principle, under the assumption that the user will seek out and read any supporting material that they do not yet understand. Where possible, such supporting material is indicated in the article via special formatting, see [[#Formatting]].

Because of this organization, it may be necessary to examine several related sources in order to fully understand an ArchWiki article. In particular, users who are new to Arch (or GNU/Linux in general) should expect to end up reading a great number of articles even when solving simple problems. It is especially important to study the supporting material before seeking additional help from other users.

== Formatting ==

* link to a section in the current article: [[#Organization]]
* link to [[Main page|another ArchWiki article]]
* link to an [[Wikipedia:|external web page]]
* link to a [[man page]]: {{man|1|intro}}
* a [[man page]] that's only available offline: {{man|1|foo|url=}}
* link to a package in the [[official repositories]]: {{Pkg|foobar}}
* link to a package in the [[AUR]]: {{AUR|foobar}}

== Root, regular user or another user ==

Some lines are written like so:

# mkinitcpio -p linux

Others have a different prefix:

$ makepkg -s

The numeral or hash sign ({{ic|#}}) indicates that the command needs to be run as ''root'', whereas the dollar sign ({{ic|$}}) shows that the command should be run as a ''regular user''.

{{Note|The commands prefixed with {{ic|#}} are intended to be executed from a ''root shell'', which can for example be easily accessed with {{ic|sudo -i}}. Running {{ic|sudo ''command''}} from an unprivileged shell instead of {{ic|''command''}} from a root shell will also work in most cases, with some notable exceptions such as [[Wikipedia:Redirection_(computing)|redirection]] and [[Wikipedia:Command substitution|command substitution]], which strictly require a root shell. See [[sudo#Login shell]].}}

When the commands need to run as a specific user, they will be prefixed by the username in square brackets, for example:

[postgres]$ initdb -D /var/lib/postgres/data

This means you should use a [[List of applications/Security#Privilege elevation|privilege elevation tool]], e.g. with [[sudo]]:

$ sudo -u postgres initdb -D /var/lib/postgres/data

A notable exception to watch out for:

# This alias makes ls colorize the listing
alias ls='ls --color=auto'

In this example, the context surrounding the numeral sign communicates that this is not to be run as a command; it should be edited into a file instead. So in this case, the numeral sign denotes a ''comment''. A comment can be explanatory text that will not be interpreted by the associated program. [[Bash]] scripts denotation for comments happens to coincide with the root ''PS1''.

After further examination, "give away" signs include the uppercase character following the {{ic|#}} sign. Usually, Unix commands are not written this way and most of the time they are short abbreviations instead of full-blown English words (e.g., ''Copy'' becomes ''cp'').

Regardless, most articles make this easy to discern by notifying the reader:

''Append'' to {{ic|~/path/to/file}}:

# This alias makes ls colorize the listing
alias ls='ls --color=auto'

== Append, add, create, edit ==

When prompted to ''append to'', ''add to'', ''create'', or ''edit'' one or more files, it is implied that you should use one of the following methods.

To create or modify multiline files, it is suggested to use a [[text editor]]. For example, using the [[nano]] command to edit the file {{ic|/etc/bash.bashrc}} is:

# nano /etc/bash.bashrc

{{Note|Text files must end with a newline because [https://pubs.opengroup.org/onlinepubs/9799919799/basedefs/V1_chap03.html#tag_03_185 a line] is terminated with a newline. Most text editors insert an ending newline by default.}}

To create or overwrite a file from a string, it may be simpler to use [https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html#tag_19_07_02 output redirection]. The following example creates or overwrites the contents of the file {{ic|/etc/hostname}} with the text {{ic|myhostname}}.

# echo myhostname > /etc/hostname

Output redirection can also be used to append a string to a file. The following example appends the text {{ic|[custom-repo]}} to the file {{ic|/etc/pacman.conf}}.

# echo "[custom-repo]" >> /etc/pacman.conf

When prompted to create [[w:Directory (computing)|directories]], use the [[Core utilities#Essentials|mkdir]] command:

# mkdir /mnt/boot

=== Make executable ===

After creating a file, if it is meant to be run as a script (whether manually or called by another program), it needs to be set as ''executable'', for example with:

$ chmod +x ''script''

See [[chmod]]. Some applications such as [[file manager]]s may provide graphical interfaces to do the same.

== Source ==

Some applications, notably [[command-line shell]]s, use scripts for their configuration: after modifying them, they must be ''sourced'' in order for the changes to be applied. In the case of [[bash]], for example, this is done by running (you can also replace {{ic|source}} with {{ic|.}}):

$ source ~/.bashrc

When the wiki suggests modifying such a configuration script, it will not explicitly remind you to source the file, and only in some cases will it point to this section with a reminder link.

== Installation of packages ==

When an article invites you to install some packages in the conventional way, it will not indicate the detailed instructions to do so; instead, it will simply mention the names of the packages to be installed.

{{Note|Frequently, the [[install]] or [[install]]ed links are used to point to this article section.

* [[Wikipedia:JavaScript|JavaScript]] has to be enabled for these links to work.
* [[Lynx]], which is officially supported by the [[installation guide]], does not support JavaScript.

}}

=== Official packages ===

For packages from the [[official repositories]], you will read something like:

:Install the {{Pkg|foobar}} package.

This means that you have to run:

# pacman -S foobar

The [[pacman]] article and the {{man|8|pacman}} manual page contain detailed explanations to deal with package management in Arch Linux proficiently.

=== Arch User Repository ===

For packages from the [[Arch User Repository]] (AUR), you will read something like:

:Install the {{AUR|foobar}} package.

This means that in general you have to follow the {{AUR|foobar}} link, download the PKGBUILD archive, extract it, '''verify the content''' and finally run, in the same folder:

$ makepkg -si

{{Note|The {{Pkg|base-devel}} meta package is required to build packages from the AUR or with the [[Arch build system]].}}

The [[Arch User Repository]] article contains all the detailed explanations and best practices to deal with AUR packages.

== Control of systemd units ==

When an article invites to ''start'', ''enable'', etc., some systemd unit (e.g. a service), it will not indicate the detailed instructions to do so, but instead you will read something like:

:[[Start]] {{ic|example.service}}.

This means that you have to run:

# systemctl start example.service

A notable command that does not follow this exact pattern is {{ic|systemctl daemon-reload}} which will be called without arguments.

The [[systemd#Using units]] section contains structured list of available actions (like ''start'', ''enable'', ''enable and start'', etc.) with their corresponding ''systemctl'' commands.

== System-wide versus user-specific configuration ==

It is important to remember that there are two different kinds of configurations on a GNU/Linux system. '''System-wide''' configuration affects all users. Since system-wide settings are generally located in the {{ic|/etc}} directory, root privileges are required in order to alter them. For example, to apply a Bash setting that affects all users, {{ic|/etc/bash.bashrc}} should be modified.

'''User-specific''' configuration affects only a single user. ''Dotfiles'' are used for user-specific configuration. For example, the file {{ic|~/'''.'''bashrc}} is the user-specific configuration file. The idea is that each user can define their own settings, such as aliases, functions and other interactive features like the prompt, without affecting other users' preferences.

{{Note|{{ic|~/}} and {{ic|$HOME}} are shortcuts for the user's home directory, usually {{ic|/home/''username''/}}.}}

=== Common shell files ===

Bash and other Bourne-compatible shells, such as [[Zsh]], also source files depending on whether the shell is a ''login shell'' or an ''interactive shell''. See [[Bash#Configuration files]] and [[Zsh#Startup/Shutdown files]] for details.

== Pseudo-variables in code examples ==

Some code blocks may contain so-called ''pseudo-variables'', which, as the name says, are not actual variables used in the code. Instead they are generic placeholders and have to be manually replaced with system-specific configuration items '''before''' the code may be run or parsed. Common shells such as [[bash]] and [[zsh]] provide [[w:Command-line_completion|tab-completion]] to auto-complete parameters for common commands such as ''systemctl''.

In the articles that comply with [[Help:Style/Formatting and punctuation]], ''pseudo-variables'' are formatted in italics. For example:

* [[Enable]] the {{ic|dhcpcd@''interface_name''.service}} for the network interface identified from the output of the {{ic|ip link}} command.

In this case {{ic|''interface_name''}} is used as a ''pseudo-variable'' placeholder in a systemd template unit. All systemd template units, identifiable by the {{ic|@}} sign, require a system-specific configuration item as argument. See [[systemd#Using units]].

* The command {{ic|1=dd if=''data_source'' of=/dev/sd''X'' bs=''sector_size'' count=''sector_number'' seek=''partitions_start_sector''}} can be run as root to wipe a partition with the specific parameters.

In this case the ''pseudo-variables'' are used to describe the parameters that must be substituted for them. Details on how to gather them are elaborated in the section [[Securely wipe disk#Calculate blocks to wipe manually]], which features the command.

{{Expansion|Mention other examples, ideally from other device categories (e.g. storage), with links to background articles. The examples are meant to avoid duplicating existing explanations in other articles.}}

In case of file examples, pasting pseudo-variables in real configuration files might break the programs that use them.

=== Ellipses ===

In most cases, ellipses ({{ic|...}}) are not part of the actual file content or code output, and instead represent omitted or optional text that is not relevant for the discussed subject.

For example {{ic|1=HOOKS=(... encrypt ... filesystems ...)}} or:

{{hc|/etc/X11/xorg.conf.d/50-synaptics.conf|
Section "InputClass"
...
Option "CircularScrolling" "on"
Option "CircScrollTrigger" "0"
...
EndSection
}}

Be aware though that, in a few instances, ellipses may be a meaningful part of the code syntax: attentive users should be able to recognize these cases by the context.

AUR helpers

2026-03-29T11:42:49Z

Alad: Undo revision 870089 by Alad (talk) - AUR template does not work with pkgbase

[[Category:Package management]]
[[Category:Software comparisons]]
[[de:AUR Hilfsprogramme]]
[[fr:AUR helpers]]
[[it:AUR helpers]]
[[ja:AUR ヘルパー]]
[[pt:AUR helpers]]
[[ru:AUR helpers]]
[[uk:AUR helpers]]
[[zh-hans:AUR 助手]]
{{Warning|1=AUR helpers are '''not supported''' by Arch Linux. You should become familiar with the [[Arch User Repository#Installing and upgrading packages|manual build process]] in order to be prepared to troubleshoot problems.}}

{{Notice|Please use the discussion page prior to making edits to this article: [[Talk:AUR helpers]].}}

AUR helpers automate usage of the [[Arch User Repository]]. In particular, they may automate the following tasks:

* searching for packages published on the AUR,
* resolving of dependencies between AUR packages,
* retrieve and build AUR packages,
* retrieve web content, such as user comments,
* submission of AUR packages.

[[Pacman]] only handles updates for pre-built packages in its repositories. AUR packages are redistributed in form of [[PKGBUILD]]s and need an AUR helper to automate the rebuild process. However, keep in mind that a rebuild of a package may be required when its shared library dependencies are updated, not only when the package itself is updated.

== Legend ==

The [[#Comparison tables]] columns have the following meaning:

;File review: Does not [[source]] the [[PKGBUILD]] file at all ''by default''; or alerts the user and offers the opportunity to inspect the {{ic|PKGBUILD}} file manually before it is sourced. Some helpers are known to source {{ic|PKGBUILD}}s before the user can inspect them, '''allowing malicious code to be executed'''.
;Diff view: Ability to view package differences on inspection. Besides the {{ic|PKGBUILD}} file, this includes changes to files such as {{ic|.install}} or {{ic|.patch}} files.
;Git clone: Uses {{man|1|git-clone}} by default to retrieve build files from the AUR.
;Reliable parser: Ability to handle complex packages by using the provided metadata ([[Aurweb RPC interface|RPC]]/{{ic|.SRCINFO}}) instead of the {{ic|PKGBUILD}} file [[w:Parsing#Parser|parsing]], such as {{AUR|aws-cli-git}}.
;Reliable solver: Ability to correctly solve and build complex dependency chains, such as {{AUR|liri-git-meta}}.
;Split packages: Ability to correctly build and install:
:* Multiple packages from the same package base, without rebuilding or reinstalling multiple times, such as {{AUR|clion}}.
:* Split packages which depend on a package from the same package base, such as {{AUR|samsung-unified-driver}}.
:* Split packages independently, such as {{AUR|nxproxy}} and {{AUR|nxagent}}.
;Shell completion: [[w:Command-line_completion|Tab completion]] is available for the listed [[shell]]s.

{{Note|
* ''Optional'' means that a feature is available, but only through a command-line argument or configuration option.
* ''Partial'' means that a feature is not fully implemented, or that it partially deviates from the given criteria.
}}

== Comparison tables ==

=== Search and download ===

{| class="wikitable sortable" style="text-align: center;"
! Name !! Written in !! File review !! Diff view !! Git clone !! Reliable parser !! Reliable solver !! Shell completion !! Specificity
|-
! {{AUR|auracle-git}}
| C++ || {{Yes}} || {{No}} || {{Yes|https://github.com/falconindy/auracle/commit/c73bbee}} || {{Yes}} || {{Yes}} || bash || {{L|print build order}}
|-
! {{AUR|pbget}}
| Python || {{Yes}} || {{No}} || {{Yes}} || {{Yes}} || {{-}} || {{-}} || {{-}}
|-
! {{AUR|repoctl}}
| Go || {{Yes}} || {{No}} || {{No}} || {{Yes|https://github.com/goulash/pacman/blob/master/aur/aur.go}} || {{-}} || bash, zsh, fish || {{L|[[local repository]]}}
|-
! {{AUR|yaah}}
| Bash || {{Yes}} || {{No}} || {{Y|Optional}} || {{Yes}} || {{-}} || bash || {{-}}
|}

=== Search and build ===

{| class="wikitable sortable" style="text-align: center;"
! Name !! Written in !! File review !! Diff view !! Git clone !! Reliable parser !! Reliable solver !! Split packages !! Shell completion !! Specificity
|-
! {{AUR|aurutils}}
| Bash || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || bash, zsh || {{L|[[local repository]], local patch application, [[package signing]], [[clean chroot]] (via [[systemd-nspawn]])}}
|-
! {{AUR|pat-aur-host-git}}/{{AUR|pat-aur-client-git}}
| Elvish || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || bash, zsh, elvish || {{L|[[local repository]], local patch application, [[package signing]], [[clean chroot]] (via [[bubblewrap]]), [[Wikipedia:Cross compiler|cross-compilation]]}}
|-
! {{AUR|rua}}
| Rust || {{Yes}} || {{Yes|https://github.com/vn971/rua/commit/0459a8b}} || {{Yes}} || {{Yes|https://github.com/vn971/rua/commit/fc8c2f3}} || {{No}} || {{Yes|https://github.com/vn971/rua/commit/7889045}} || bash, zsh, fish || {{L|local patch application, [[clean chroot]] (via [[bubblewrap]]), {{ic|.pkg.tar}} inspection}}
|}

=== Pacman wrappers ===

{{Warning|{{man|8|pacman}} wrappers abstract the work of the package manager. They may (optionally or by default) introduce [[System maintenance#Avoid certain pacman commands|unsafe flags]], or other unexpected behavior leading to a defective system.}}

{{Note|The following pacman wrappers support batch (rather than on-demand) operations: {{AUR|pacaur}}, {{AUR|pikaur}}, {{AUR|yay}}, {{AUR|aura}}, {{AUR|paru}}, {{AUR|aurman}}
}}

{| class="wikitable sortable" style="text-align: center;"
! Name !! Written in !! File review !! Diff view !! Git clone !! Reliable parser !! Reliable solver !! Split packages !! Unsafe flags !! Shell completion !! Specificity
|-
! {{AUR|aura}}
| Rust || {{No}} || {{Y|[https://github.com/aurapm/aura/blob/89bf702/aura/src/Aura/Pkgbuild/Records.hs Partial]}} || {{Yes|https://github.com/fosskers/aura/commit/ca9c38d}} || {{Yes|https://github.com/aurapm/aura/commit/7848e98}} || {{Yes|https://github.com/fosskers/aura/pull/479}} || {{Yes|https://github.com/fosskers/aura/pull/479}} || {{-}} || bash, fish, zsh || {{L|[[clean chroot]]}}
|-
! {{AUR|aurman}}
| Python || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|[https://github.com/polygamma/aurman/issues/259 Partial]}} || {{Yes}} || {{R|[https://github.com/polygamma/aurman/commit/6c02ba3 -Sy] [https://github.com/polygamma/aurman#make-use-of-the-undocumented---ask-flag-of-pacman --ask]}} || bash, fish || {{L|fetch PGP keys}}
|-
! {{AUR|pacaur}}
| Bash || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|[https://github.com/E5ten/pacaur/commit/12707cc --ask]}} || bash, zsh || {{-}}
|-
! {{AUR|pakku}}
| Nim || {{Yes}} || {{Yes|https://github.com/kitsunyan/pakku/commit/396e9f4}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|[https://github.com/kitsunyan/pakku/wiki/Native-Pacman-Explanation -Sy]}} || bash, zsh || {{-}}
|-
! {{AUR|paru}}
| Rust|| {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|[https://github.com/Morganamilo/paru/blob/15394a7db80d045f038ea4d0ee94d00211070c96/man/paru.8#L543-L552 -Sy] [https://github.com/Morganamilo/paru/blob/32b75ac1cb7e0fccd21a0f795f25fd9fb1a14d8a/man/paru.conf.5#L110-L116 --ask]}} || bash, fish, zsh || {{L|[[local repository]], [[clean chroot]]}}
|-
! {{AUR|pikaur}}
| Python || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|[https://github.com/actionless/pikaur#pikaur -Sy]}} || bash, fish, zsh || {{L|[https://0pointer.net/blog/dynamic-users-with-systemd.html dynamic users]}}
|-
! {{AUR|trizen}}
| Perl || {{Yes}} || {{Yes}} ||{{Yes|https://github.com/trizen/trizen/commit/6fb0cc9}} || {{Yes|https://github.com/trizen/trizen/commit/7ab7ee5f}} || {{Yes}} || {{Y|[https://github.com/trizen/trizen/issues/46 Partial]}} || {{-}} || bash, fish, zsh || {{-}}
|-
! {{AUR|yay}}
| Go || {{Yes}} || {{Yes|https://github.com/Jguer/yay/pull/447}} || {{Yes|https://github.com/Jguer/yay/pull/297}} || {{Yes}} || {{Yes|https://github.com/Jguer/yay/pull/866}} || {{Yes}} || {{Y|[https://github.com/Jguer/yay/commit/ea5a94e --ask]}} || bash, fish, zsh || {{-}}
|}

== Graphical ==

{{Warning|Usage of graphical AUR helpers may lead to a defective system, for example through unattended [[partial upgrade]]s.}}
* {{App|Argon|GTK 3 pacman wrapper written in Python.|https://github.com/14mRh4X0r/arch-argon|{{AUR|argon}}}}
* {{App|Bauh|Qt5 Python application supporting AppImage, Debian and Arch packages (including AUR), Flatpak, Snap and native Web applications.|https://github.com/vinifmor/bauh|{{AUR|bauh}}}}
* {{App|Cylon|TUI pacman wrapper written in Bash.|https://github.com/gavinlyonsrepo/cylon|{{AUR|cylon}}}}
* {{App|Kalu|Systray notification icon using libalpm and [[PolicyKit]], with optional updater|https://github.com/Thulinma/kalu|{{AUR|kalu}}}}
* {{App|Octopi|Qt 5 pacman wrapper written in C++.|https://tintaescura.com/projects/octopi|{{AUR|octopi}}}}
* {{App|Pacsea|A fast, keyboard-friendly TUI for browsing and installing Arch and AUR packages written in Rust.|https://github.com/Firstp1ck/Pacsea|{{AUR|pacsea-bin}}}}
* {{App|Pacseek|A terminal user interface for searching and installing Arch Linux packages.|https://github.com/moson-mo/pacseek|{{AUR|pacseek}}}}
* {{App|Pamac|Standalone GTK 4 (or terminal) package manager written for Manjaro using {{man|3|libalpm}} with tray integration.|https://wiki.manjaro.org/index.php/Pamac|{{AUR|pamac-aur}}}}
* {{App|Pakku GUI|GTK 3 frontend for pakku written in Python.|https://gitlab.com/mrvik/pakku-gui|{{AUR|pakku-gui}}}}
* {{App|PkgBrowser|Qt 5 read-only browser for repository packages and AUR written in Python.|https://osdn.net/projects/pkgbrowser/|{{AUR|pkgbrowser}}}}
* {{App|SPM|A TUI wrapper for pacman and yay that makes package management visual and interactive.|https://github.com/adelmonte/Simple_Package_Manager|{{AUR|spm-arch}}}}
* {{App|Yup|Ncurses TUI pacman wrapper written in Go.|https://github.com/ericm/yup|{{AUR|yup}}}}

== Maintenance ==

* {{App|aur-out-of-date|Uses hoster APIs to check AUR packages for upstream changes.|https://github.com/simon04/aur-out-of-date|{{AUR|aur-out-of-date}}}}
* {{App|aurpublish|Helper script to manage and upload AUR packages using {{man|1|git-subtree}}. Uses {{man|5|githooks}} to verify the {{ic|PKGBUILD}} file integrity, generate the {{ic|.SRCINFO}} file automatically, and create a commit message template.|https://github.com/eli-schwartz/aurpublish|{{Pkg|aurpublish}}}}
* {{App|[[DeveloperWiki:Building in a clean chroot|devtools]]|Build packages in a clean environment ([[systemd-nspawn]] container) to ensure their correctness. Wrapped by {{AUR|aura}}, {{AUR|aurutils}}, {{AUR|clean-chroot-manager}} and {{AUR|paru}}.|https://gitlab.archlinux.org/archlinux/devtools|{{Pkg|devtools}}}}
* {{App|pkgoutofdate|Parses the source URL from {{ic|PKGBUILD}}s and tries to find new versions of packages by incrementing the version number and sending requests to the web server.|https://github.com/anatol/pkgoutofdate|{{AUR|pkgoutofdate-git}}}}
* {{App|repman|Command line tool to manage local and remote repositories.|https://gitlab.com/mipimipi/repman|{{AUR|repman-git}}}}

== Other ==

* {{App|aur-talk|Fetch and display AUR comments.|https://github.com/GermainZ/aur-talk|{{AUR|aur-talk-git}}}}
* {{App|aurvote-utils|A set of utilities for managing AUR votes.|https://github.com/jadenPete/aurvote-utils|{{AUR|aurvote-utils}}}}
* {{App|haskell-aur|[[Haskell]] library for accessing [[Aurweb RPC interface]].|https://hackage.haskell.org/package/aur|{{AUR|haskell-aur}}}}
* {{App|package-query|Tool for querying {{man|3|libalpm}} and the AUR.|https://github.com/archlinuxfr/package-query|{{AUR|package-query}}}}
* {{App|python3-aur|[[Python]] modules and helper utilities for accessing AUR package information and automating AUR interactions.|https://xyne.dev/projects/python3-aur|{{AUR|python3-aur}}}}
* {{App|raur|Rust library for accessing Aurweb RPC interface.|https://gitlab.com/davidbittner/raur||}}

== See also ==

* [https://www.debugpoint.com/arch-linux-gui-package-managers/ GUI Package Managers for Arch Linux] (DebugPoint, 2023) offers some screenshots and simple information about a few of the options mentioned in [[#Graphical]]

Talk:AUR helpers

2026-03-27T12:21:58Z

Alad: /* Spring cleaning */ new section

== Add table column for [[AUR helpers#Pacman wrappers]] ==

We have a note right above the table, would it not be better to create a new column for the information it contains? --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 08:26, 20 March 2022 (UTC)

:The article went back and forth on this, the main issue being to define "batch operations" in the first place. This term was originally introduced by {{AUR|pacaur}} and comes down to 1. guessing which packages need to be replaced beforehand 2. using {{ic|pacman --ask}} (undocumented feature) to invert {{ic|pacman --noconfirm}} prompts from {{ic|N}} to {{ic|Y}} during the build process.
:Making this a column with Yes/No implies this is a desirable feature. I argue that depending on undocumented features with a bug-prone implementation (what if the wrong package is replaced on the user's system?) can not be classified as such. Furthermore, it gives the impression this somehow leads to ''less'' interaction on the user's behalf, which is false (in fact, the vast majority of pacman wrappers play a game of whack-a-mole with {{ic|y/N}} prompts). A Note is more neutral, and leaves out whether a feature is wanted or not in the middle.
:In any case, the other columns, Shell completion excepted, are better suited as basic requirements for a reliable AUR helper. And as far as basic requirements go, they are relatively simple to implement for AUR helper authors looking at this article - unlike a "batch operation" mechanism. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 15:47, 20 March 2022 (UTC)

:: Thank you ! I better understand now the reason why this is not already done. --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 16:26, 20 March 2022 (UTC)

== Auxiliary files for File review ==

Auxiliary files in an AUR repository also lead to arbitrary code execution, namely .install files which are run by [[pacman]] as root. As such it makes sense for the file review column to include them. For a helper that only supports viewing the [[PKGBUILD]], I suggest a Partial entry (after all, when noticing there is an .install file, the user can manually view it with some effort). -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 03:10, 8 October 2023 (UTC)

:Sounds good to me :) [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 15:37, 15 May 2024 (UTC)

== Add warning about reading diffs ==

In the light of the recent RAT malware found on the AUR, we may want to add a reminder in the warning up top, with either a link to or a rewording of the warning in [[Arch User Repository#Build the package]]? 
-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 09:48, 7 August 2025 (UTC)

== Paru/Yay Unsafe Flags are Wrong ==

Yay and Paru both have the option to use --ask although it is opt in and is a flag that needs to be
explicitly Passed.

Yay and Paru both have the --combinedupgrade flag (which causes a -Sy), although it's on by default
in Yay and off in Paru.

I'm not sure if yellow is meant to mean the flag is optional or --ask is coloured yellow and -Sy always red. I don't
seem to have the perms to edit it anyway so I'll leave the formatting to you. --[[User:Morganamilo|Morganamilo]] ([[User talk:Morganamilo|talk]]) 08:11, 7 October 2025 (UTC)

:So if I get it right, yay should have a red entry for default -Sy, and paru no entry?
:The only definition for yellow in the article is "optional", but since every wrapper supports -Sy as an option, that doesn't make sense for the Unsafe flags column. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 05:54, 5 January 2026 (UTC)

== <s>Remove PKGBUILDer</s> ==

[https://github.com/Kwpolska/pkgbuilder/blob/95dbbb6b4068ae93e014cc8d27a28057fb7e502d/README.rst PKGBUILDer is no longer maintained], so there is little point in listing it here. [[User:Kwpolska|Kwpolska]] ([[User talk:Kwpolska|talk]]) 17:53, 8 March 2026 (UTC)

:Removed, thanks. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 12:15, 27 March 2026 (UTC)

== Spring cleaning ==

Time for another spring cleaning? Most of the helpers in this article haven't been updated in years:

* {{AUR|pbget}}: last update in 2021, reported to no longer work: https://aur.archlinux.org/packages/pbget
* {{AUR|yaah}}: last update in 2021
* {{AUR|rua}}: last update in 2024, multiple security issues ignored: https://github.com/vn971/rua/issues
* {{AUR|aurman}}: last update in 2023, no github activity
* {{AUR|pacaur}}: last update in 2021, no github activity

If no objections are raised within 2 weeks of this post, I will remove the entries. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 12:21, 27 March 2026 (UTC)

Talk:AUR helpers

2026-03-27T12:15:55Z

Alad: /* Remove PKGBUILDer */ re, close

== Add table column for [[AUR helpers#Pacman wrappers]] ==

We have a note right above the table, would it not be better to create a new column for the information it contains? --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 08:26, 20 March 2022 (UTC)

:The article went back and forth on this, the main issue being to define "batch operations" in the first place. This term was originally introduced by {{AUR|pacaur}} and comes down to 1. guessing which packages need to be replaced beforehand 2. using {{ic|pacman --ask}} (undocumented feature) to invert {{ic|pacman --noconfirm}} prompts from {{ic|N}} to {{ic|Y}} during the build process.
:Making this a column with Yes/No implies this is a desirable feature. I argue that depending on undocumented features with a bug-prone implementation (what if the wrong package is replaced on the user's system?) can not be classified as such. Furthermore, it gives the impression this somehow leads to ''less'' interaction on the user's behalf, which is false (in fact, the vast majority of pacman wrappers play a game of whack-a-mole with {{ic|y/N}} prompts). A Note is more neutral, and leaves out whether a feature is wanted or not in the middle.
:In any case, the other columns, Shell completion excepted, are better suited as basic requirements for a reliable AUR helper. And as far as basic requirements go, they are relatively simple to implement for AUR helper authors looking at this article - unlike a "batch operation" mechanism. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 15:47, 20 March 2022 (UTC)

:: Thank you ! I better understand now the reason why this is not already done. --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 16:26, 20 March 2022 (UTC)

== Auxiliary files for File review ==

Auxiliary files in an AUR repository also lead to arbitrary code execution, namely .install files which are run by [[pacman]] as root. As such it makes sense for the file review column to include them. For a helper that only supports viewing the [[PKGBUILD]], I suggest a Partial entry (after all, when noticing there is an .install file, the user can manually view it with some effort). -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 03:10, 8 October 2023 (UTC)

:Sounds good to me :) [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 15:37, 15 May 2024 (UTC)

== Add warning about reading diffs ==

In the light of the recent RAT malware found on the AUR, we may want to add a reminder in the warning up top, with either a link to or a rewording of the warning in [[Arch User Repository#Build the package]]? 
-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 09:48, 7 August 2025 (UTC)

== Paru/Yay Unsafe Flags are Wrong ==

Yay and Paru both have the option to use --ask although it is opt in and is a flag that needs to be
explicitly Passed.

Yay and Paru both have the --combinedupgrade flag (which causes a -Sy), although it's on by default
in Yay and off in Paru.

I'm not sure if yellow is meant to mean the flag is optional or --ask is coloured yellow and -Sy always red. I don't
seem to have the perms to edit it anyway so I'll leave the formatting to you. --[[User:Morganamilo|Morganamilo]] ([[User talk:Morganamilo|talk]]) 08:11, 7 October 2025 (UTC)

:So if I get it right, yay should have a red entry for default -Sy, and paru no entry?
:The only definition for yellow in the article is "optional", but since every wrapper supports -Sy as an option, that doesn't make sense for the Unsafe flags column. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 05:54, 5 January 2026 (UTC)

== <s>Remove PKGBUILDer</s> ==

[https://github.com/Kwpolska/pkgbuilder/blob/95dbbb6b4068ae93e014cc8d27a28057fb7e502d/README.rst PKGBUILDer is no longer maintained], so there is little point in listing it here. [[User:Kwpolska|Kwpolska]] ([[User talk:Kwpolska|talk]]) 17:53, 8 March 2026 (UTC)

:Removed, thanks. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 12:15, 27 March 2026 (UTC)

AUR helpers

2026-03-27T12:14:02Z

Alad: /* Search and build */ pat-aur-git

[[Category:Package management]]
[[Category:Software comparisons]]
[[de:AUR Hilfsprogramme]]
[[fr:AUR helpers]]
[[it:AUR helpers]]
[[ja:AUR ヘルパー]]
[[pt:AUR helpers]]
[[ru:AUR helpers]]
[[uk:AUR helpers]]
[[zh-hans:AUR 助手]]
{{Warning|1=AUR helpers are '''not supported''' by Arch Linux. You should become familiar with the [[Arch User Repository#Installing and upgrading packages|manual build process]] in order to be prepared to troubleshoot problems.}}

{{Notice|Please use the discussion page prior to making edits to this article: [[Talk:AUR helpers]].}}

AUR helpers automate usage of the [[Arch User Repository]]. In particular, they may automate the following tasks:

* searching for packages published on the AUR,
* resolving of dependencies between AUR packages,
* retrieve and build AUR packages,
* retrieve web content, such as user comments,
* submission of AUR packages.

[[Pacman]] only handles updates for pre-built packages in its repositories. AUR packages are redistributed in form of [[PKGBUILD]]s and need an AUR helper to automate the rebuild process. However, keep in mind that a rebuild of a package may be required when its shared library dependencies are updated, not only when the package itself is updated.

== Legend ==

The [[#Comparison tables]] columns have the following meaning:

;File review: Does not [[source]] the [[PKGBUILD]] file at all ''by default''; or alerts the user and offers the opportunity to inspect the {{ic|PKGBUILD}} file manually before it is sourced. Some helpers are known to source {{ic|PKGBUILD}}s before the user can inspect them, '''allowing malicious code to be executed'''.
;Diff view: Ability to view package differences on inspection. Besides the {{ic|PKGBUILD}} file, this includes changes to files such as {{ic|.install}} or {{ic|.patch}} files.
;Git clone: Uses {{man|1|git-clone}} by default to retrieve build files from the AUR.
;Reliable parser: Ability to handle complex packages by using the provided metadata ([[Aurweb RPC interface|RPC]]/{{ic|.SRCINFO}}) instead of the {{ic|PKGBUILD}} file [[w:Parsing#Parser|parsing]], such as {{AUR|aws-cli-git}}.
;Reliable solver: Ability to correctly solve and build complex dependency chains, such as {{AUR|liri-git-meta}}.
;Split packages: Ability to correctly build and install:
:* Multiple packages from the same package base, without rebuilding or reinstalling multiple times, such as {{AUR|clion}}.
:* Split packages which depend on a package from the same package base, such as {{AUR|samsung-unified-driver}}.
:* Split packages independently, such as {{AUR|nxproxy}} and {{AUR|nxagent}}.
;Shell completion: [[w:Command-line_completion|Tab completion]] is available for the listed [[shell]]s.

{{Note|
* ''Optional'' means that a feature is available, but only through a command-line argument or configuration option.
* ''Partial'' means that a feature is not fully implemented, or that it partially deviates from the given criteria.
}}

== Comparison tables ==

=== Search and download ===

{| class="wikitable sortable" style="text-align: center;"
! Name !! Written in !! File review !! Diff view !! Git clone !! Reliable parser !! Reliable solver !! Shell completion !! Specificity
|-
! {{AUR|auracle-git}}
| C++ || {{Yes}} || {{No}} || {{Yes|https://github.com/falconindy/auracle/commit/c73bbee}} || {{Yes}} || {{Yes}} || bash || {{L|print build order}}
|-
! {{AUR|pbget}}
| Python || {{Yes}} || {{No}} || {{Yes}} || {{Yes}} || {{-}} || {{-}} || {{-}}
|-
! {{AUR|repoctl}}
| Go || {{Yes}} || {{No}} || {{No}} || {{Yes|https://github.com/goulash/pacman/blob/master/aur/aur.go}} || {{-}} || bash, zsh, fish || {{L|[[local repository]]}}
|-
! {{AUR|yaah}}
| Bash || {{Yes}} || {{No}} || {{Y|Optional}} || {{Yes}} || {{-}} || bash || {{-}}
|}

=== Search and build ===

{| class="wikitable sortable" style="text-align: center;"
! Name !! Written in !! File review !! Diff view !! Git clone !! Reliable parser !! Reliable solver !! Split packages !! Shell completion !! Specificity
|-
! {{AUR|aurutils}}
| Bash || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || bash, zsh || {{L|[[local repository]], local patch application, [[package signing]], [[clean chroot]] (via [[systemd-nspawn]])}}
|-
! {{AUR|pat-aur-git}}
| Elvish || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || bash, zsh, elvish || {{L|[[local repository]], local patch application, [[package signing]], [[clean chroot]] (via [[bubblewrap]]), [[Wikipedia:Cross compiler|cross-compilation]]}}
|-
! {{AUR|rua}}
| Rust || {{Yes}} || {{Yes|https://github.com/vn971/rua/commit/0459a8b}} || {{Yes}} || {{Yes|https://github.com/vn971/rua/commit/fc8c2f3}} || {{No}} || {{Yes|https://github.com/vn971/rua/commit/7889045}} || bash, zsh, fish || {{L|local patch application, [[clean chroot]] (via [[bubblewrap]]), {{ic|.pkg.tar}} inspection}}
|}

=== Pacman wrappers ===

{{Warning|{{man|8|pacman}} wrappers abstract the work of the package manager. They may (optionally or by default) introduce [[System maintenance#Avoid certain pacman commands|unsafe flags]], or other unexpected behavior leading to a defective system.}}

{{Note|The following pacman wrappers support batch (rather than on-demand) operations: {{AUR|pacaur}}, {{AUR|pikaur}}, {{AUR|yay}}, {{AUR|aura}}, {{AUR|paru}}, {{AUR|aurman}}
}}

{| class="wikitable sortable" style="text-align: center;"
! Name !! Written in !! File review !! Diff view !! Git clone !! Reliable parser !! Reliable solver !! Split packages !! Unsafe flags !! Shell completion !! Specificity
|-
! {{AUR|aura}}
| Rust || {{No}} || {{Y|[https://github.com/aurapm/aura/blob/89bf702/aura/src/Aura/Pkgbuild/Records.hs Partial]}} || {{Yes|https://github.com/fosskers/aura/commit/ca9c38d}} || {{Yes|https://github.com/aurapm/aura/commit/7848e98}} || {{Yes|https://github.com/fosskers/aura/pull/479}} || {{Yes|https://github.com/fosskers/aura/pull/479}} || {{-}} || bash, fish, zsh || {{L|[[clean chroot]]}}
|-
! {{AUR|aurman}}
| Python || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|[https://github.com/polygamma/aurman/issues/259 Partial]}} || {{Yes}} || {{R|[https://github.com/polygamma/aurman/commit/6c02ba3 -Sy] [https://github.com/polygamma/aurman#make-use-of-the-undocumented---ask-flag-of-pacman --ask]}} || bash, fish || {{L|fetch PGP keys}}
|-
! {{AUR|pacaur}}
| Bash || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|[https://github.com/E5ten/pacaur/commit/12707cc --ask]}} || bash, zsh || {{-}}
|-
! {{AUR|pakku}}
| Nim || {{Yes}} || {{Yes|https://github.com/kitsunyan/pakku/commit/396e9f4}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|[https://github.com/kitsunyan/pakku/wiki/Native-Pacman-Explanation -Sy]}} || bash, zsh || {{-}}
|-
! {{AUR|paru}}
| Rust|| {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|[https://github.com/Morganamilo/paru/blob/15394a7db80d045f038ea4d0ee94d00211070c96/man/paru.8#L543-L552 -Sy] [https://github.com/Morganamilo/paru/blob/32b75ac1cb7e0fccd21a0f795f25fd9fb1a14d8a/man/paru.conf.5#L110-L116 --ask]}} || bash, fish, zsh || {{L|[[local repository]], [[clean chroot]]}}
|-
! {{AUR|pikaur}}
| Python || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|[https://github.com/actionless/pikaur#pikaur -Sy]}} || bash, fish, zsh || {{L|[https://0pointer.net/blog/dynamic-users-with-systemd.html dynamic users]}}
|-
! {{AUR|trizen}}
| Perl || {{Yes}} || {{Yes}} ||{{Yes|https://github.com/trizen/trizen/commit/6fb0cc9}} || {{Yes|https://github.com/trizen/trizen/commit/7ab7ee5f}} || {{Yes}} || {{Y|[https://github.com/trizen/trizen/issues/46 Partial]}} || {{-}} || bash, fish, zsh || {{-}}
|-
! {{AUR|yay}}
| Go || {{Yes}} || {{Yes|https://github.com/Jguer/yay/pull/447}} || {{Yes|https://github.com/Jguer/yay/pull/297}} || {{Yes}} || {{Yes|https://github.com/Jguer/yay/pull/866}} || {{Yes}} || {{Y|[https://github.com/Jguer/yay/commit/ea5a94e --ask]}} || bash, fish, zsh || {{-}}
|}

== Graphical ==

{{Warning|Usage of graphical AUR helpers may lead to a defective system, for example through unattended [[partial upgrade]]s.}}
* {{App|Argon|GTK 3 pacman wrapper written in Python.|https://github.com/14mRh4X0r/arch-argon|{{AUR|argon}}}}
* {{App|Bauh|Qt5 Python application supporting AppImage, Debian and Arch packages (including AUR), Flatpak, Snap and native Web applications.|https://github.com/vinifmor/bauh|{{AUR|bauh}}}}
* {{App|Cylon|TUI pacman wrapper written in Bash.|https://github.com/gavinlyonsrepo/cylon|{{AUR|cylon}}}}
* {{App|Kalu|Systray notification icon using libalpm and [[PolicyKit]], with optional updater|https://github.com/Thulinma/kalu|{{AUR|kalu}}}}
* {{App|Octopi|Qt 5 pacman wrapper written in C++.|https://tintaescura.com/projects/octopi|{{AUR|octopi}}}}
* {{App|Pacsea|A fast, keyboard-friendly TUI for browsing and installing Arch and AUR packages written in Rust.|https://github.com/Firstp1ck/Pacsea|{{AUR|pacsea-bin}}}}
* {{App|Pacseek|A terminal user interface for searching and installing Arch Linux packages.|https://github.com/moson-mo/pacseek|{{AUR|pacseek}}}}
* {{App|Pamac|Standalone GTK 4 (or terminal) package manager written for Manjaro using {{man|3|libalpm}} with tray integration.|https://wiki.manjaro.org/index.php/Pamac|{{AUR|pamac-aur}}}}
* {{App|Pakku GUI|GTK 3 frontend for pakku written in Python.|https://gitlab.com/mrvik/pakku-gui|{{AUR|pakku-gui}}}}
* {{App|PkgBrowser|Qt 5 read-only browser for repository packages and AUR written in Python.|https://osdn.net/projects/pkgbrowser/|{{AUR|pkgbrowser}}}}
* {{App|SPM|A TUI wrapper for pacman and yay that makes package management visual and interactive.|https://github.com/adelmonte/Simple_Package_Manager|{{AUR|spm-arch}}}}
* {{App|Yup|Ncurses TUI pacman wrapper written in Go.|https://github.com/ericm/yup|{{AUR|yup}}}}

== Maintenance ==

* {{App|aur-out-of-date|Uses hoster APIs to check AUR packages for upstream changes.|https://github.com/simon04/aur-out-of-date|{{AUR|aur-out-of-date}}}}
* {{App|aurpublish|Helper script to manage and upload AUR packages using {{man|1|git-subtree}}. Uses {{man|5|githooks}} to verify the {{ic|PKGBUILD}} file integrity, generate the {{ic|.SRCINFO}} file automatically, and create a commit message template.|https://github.com/eli-schwartz/aurpublish|{{Pkg|aurpublish}}}}
* {{App|[[DeveloperWiki:Building in a clean chroot|devtools]]|Build packages in a clean environment ([[systemd-nspawn]] container) to ensure their correctness. Wrapped by {{AUR|aura}}, {{AUR|aurutils}}, {{AUR|clean-chroot-manager}} and {{AUR|paru}}.|https://gitlab.archlinux.org/archlinux/devtools|{{Pkg|devtools}}}}
* {{App|pkgoutofdate|Parses the source URL from {{ic|PKGBUILD}}s and tries to find new versions of packages by incrementing the version number and sending requests to the web server.|https://github.com/anatol/pkgoutofdate|{{AUR|pkgoutofdate-git}}}}
* {{App|repman|Command line tool to manage local and remote repositories.|https://gitlab.com/mipimipi/repman|{{AUR|repman-git}}}}

== Other ==

* {{App|aur-talk|Fetch and display AUR comments.|https://github.com/GermainZ/aur-talk|{{AUR|aur-talk-git}}}}
* {{App|aurvote-utils|A set of utilities for managing AUR votes.|https://github.com/jadenPete/aurvote-utils|{{AUR|aurvote-utils}}}}
* {{App|haskell-aur|[[Haskell]] library for accessing [[Aurweb RPC interface]].|https://hackage.haskell.org/package/aur|{{AUR|haskell-aur}}}}
* {{App|package-query|Tool for querying {{man|3|libalpm}} and the AUR.|https://github.com/archlinuxfr/package-query|{{AUR|package-query}}}}
* {{App|python3-aur|[[Python]] modules and helper utilities for accessing AUR package information and automating AUR interactions.|https://xyne.dev/projects/python3-aur|{{AUR|python3-aur}}}}
* {{App|raur|Rust library for accessing Aurweb RPC interface.|https://gitlab.com/davidbittner/raur||}}

== See also ==

* [https://www.debugpoint.com/arch-linux-gui-package-managers/ GUI Package Managers for Arch Linux] (DebugPoint, 2023) offers some screenshots and simple information about a few of the options mentioned in [[#Graphical]]

User talk:Andrei Korshikov

2026-03-27T12:10:05Z

Alad: /* AUR helpers */ edit

== AUR helpers ==

There's lot of changes in [[AUR helpers]], and you saw the editor notice: https://wiki.archlinux.org/index.php?title=AUR_helpers&diff=prev&oldid=869967

Not sure why you didn't open a discussion first? For one, I disagree with the "inverted" batch operation note - and that should have been split into several edits per the contribution guidelines. [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 11:56, 27 March 2026 (UTC)

:I reverted the state to the last discussed revision and manually sorted out style edits: [[Special:Diff//870085]], [[Special:Diff/870086]]
:Please start a discussion for the larger changes (ordering, added and changed notes) and keep style/maintenance changes in seperate edits from now on. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 12:08, 27 March 2026 (UTC)