ArchWiki - User contributions [en]

Help:Style

2026-05-18T09:59:55Z

Erus Iluvatar: /* systemd units operations */ nit

[[Category:Help]]
[[es:Help:Style]]
[[hu:Help:Style]]
[[it:Help:Style]]
[[ja:ヘルプ:スタイル]]
[[pt:Help:Style]]
[[ru:Help:Style]]
[[zh-hans:Help:Style]]
{{Related articles start}}
{{Related|/Formatting and punctuation}}
{{Related|/White space}}
{{Related|Help:Discussion}}
{{Related|Help:Editing}}
{{Related|Help:Reading}}
{{Related|Help:Template}}
{{Related articles end}}

These style conventions encourage tidy, organized, and visually consistent articles. Follow them as closely as possible when editing the ArchWiki.

== Article pages ==

=== Title ===

* Titles should use [[Wikipedia:Sentence case|sentence case]], e.g. "Title for new page" is correct, while "Title for New Page" is not. Note that common words that are part of a proper name or an upper-case acronym must be capitalized, e.g. "Advanced Linux Sound Architecture", not "Advanced Linux sound architecture". Namespaces are not considered part of titles, so "ArchWiki:Example article" is correct, while "ArchWiki:example article" is not. Subpage names should start with a capital letter, so "My page/My subpage" is correct, while "My page/my subpage" is not.
* By default, the topic name in titles should be in the singular form; it should be in the plural form if it represents a group or class of something and is a countable noun or perceived as such.
* Unless the subject of the article is primarily known by its acronym, prefer using the full name in the title of the article. Do not include both the full name and the acronym (e.g. in parentheses) in the title, instead use a [[#Redirect pages|redirect]] on the acronym page that points to the page titled with the full name.
* Titles of localized pages must follow [[Help:i18n#Page titles]].
* See the [[Help:Article naming guidelines]] article for more information.

=== Layout ===

* Order elements in an article as follows:

# [[#Magic words|Magic words]] (optional)
# [[#Categories|Categories]]
# [[#Interlanguage links|Interlanguage links]] (optional)
# [[#Article status templates|Article status templates]] (optional)
# [[#Related articles box|Related articles box]] (optional)
# [[#Preface or introduction|Preface or introduction]]
# Table of contents (automatic)
# Article-specific sections.

==== Magic words ====

* Behavior switches—and in general, all of the [[mw:Help:Magic words|magic words]] that change how an article is displayed or behaves but do not add content by themselves—should all go at the very top of articles.

: This rule applies in particular to {{ic|<nowiki>{{DISPLAYTITLE:title}}</nowiki>}} and [[Template:Lowercase title]], which makes use of the former.

==== Categories ====

* Every article must be categorized under at least one existing category.
* An article can belong to more than one category, provided one is not ancestor of the others.
* Categories must be included at the top of every article, right below any magic words. {{Note|This is different from some other MediaWiki projects such as Wikipedia, which include categories at the bottom.}}
* There should be no blank lines between categories and the first line of text (or interlanguage links, if present), because this introduces extra space at the top of the article.
* See the [[Help:Category]] article for more information.

==== Interlanguage links ====

* If the article has translations in the local or an external Arch Linux wiki, interlanguage links must be included right below the categories and above the first line of text. Note that they will actually appear in the appropriate column to the left side of the page.
* There should be no blank lines between interlanguage links and the first line of text, because this introduces extra space at the top of the article.
* When adding or editing interlanguage links you should take care of repeating your action for all the already existing translations.
* Do not add more than one interlanguage link for each language to an article.
* Do not add interlanguage links for the same language of the article.
* The interlanguage links must be sorted alphabetically based on the language tag, not the local name; for example {{ic|<nowiki>[[fi:Title]]</nowiki>}} comes before {{ic|<nowiki>[[fr:Title]]</nowiki>}}, even though "Suomi" would come after "Français".
* See the [[Help:i18n]] and [[Wikipedia:Help:Interlanguage links]] articles for more information.

==== Article status templates ====

* [[Help:Template#Status|Status templates]] that refer to the whole article must be included right below the categories (or interlanguage links, if present) and right above the introduction (or the [[#Related articles box|Related articles box]], if present).
* Status templates that refer to a specific portion of an article must be placed as close as possible above such portion, while appropriately avoiding to break paragraphs, code blocks, or other pre-existing templates.
* Always accompany an article status template with some words of explanation in the dedicated field (examples are provided in each template's page), possibly even opening a discussion in the talk page.

==== Related articles box ====

* Provides a simple list of related internal articles.
* Optionally included right below categories (or interlanguage links, or Article status templates, if present).
* It can only be made of [[Template:Related articles start]], [[Template:Related]] and [[Template:Related articles end]]. See also the guidelines in those pages.
* Non-English articles can make use of [[Template:Related2]] for translating the anchor text.
* Use the [[#"See also" section]] for a more complete and detailed list that also includes link descriptions and interwiki or external links.

==== Preface or introduction ====

* Included right above the first section of the article.
: '''Do not''' explicitly make an {{Ic|1=== Introduction ==}} or {{Ic|1=== Preface ==}} section: let it appear above the first section heading. A table of contents is shown automatically between the preface and first section when there are [[Help:Editing#Headings and subheadings|sufficient]] sections in the article.
* Describes the topic of the article.
: Rather than paraphrasing or writing your own (possibly biased) description of a piece of software, you can use the upstream author's description, which can usually be found on the project's home page or about page, if it exists—an example is [[WireGuard]]. You may also use the description from Wikipedia, as is the case with [[ImageMagick]].

See [[Help:Writing article introductions]] for more information.

==== Standard sections ====

===== "Installation" section =====

* The ''Installation'' section describes how to install the software, see [[#Package management instructions]].
* Use the standard title of ''Installation'' and order it early in the article.

===== "Known issues" section =====

* ''Known issues'' sections are used for known bugs or usage problems which do not have a solution yet (compare to [[#"Troubleshooting" section]]).
* Use the standard title of ''Known issues'' and order it early in the article.
* If a bug report exists for the known issue, it is very desirable that you provide a link to it. If it does not exist, you should report it yourself, thus increasing the chances that the bug will be fixed.
* Refrain from mentioning dates or version numbers (for example, "Linux kernel 3.17 does not support device XYZ as of October 2014 yet.") whenever possible. Again, prefer to link references like bug reports for follow-up information instead.

===== "Tips and tricks" section =====

* ''Tips and tricks'' sections provide advanced tips or examples of using the software.
* Use the standard title of ''Tips and tricks''.
* The various tips and tricks should be organized in subsections.

===== "Troubleshooting" section =====

* ''Troubleshooting'' sections are used for frequently asked questions regarding the software or for solutions to common problems (compare to [[#"Known issues" section]]).
* Use the standard title of ''Troubleshooting''. Common misspellings that should be avoided are ''Trouble shooting'', ''Trouble-shooting'', and ''TroubleShooting''.
* You can also report temporary workarounds for known bugs; in this case, it is ''mandatory'' that you provide a link to the bug report (or similar appropriate sources, like a forum post containing a workaround). In case it has not been reported yet, you should report it yourself, thus increasing the chances that the bug will be properly fixed. Refrain from mentioning dates or version numbers whenever possible. There are great benefits in linking to external references like bug reports both for readers and editors:
** For readers, the Wiki does not become a stopping point: they can find more information close to the source that may have otherwise been missed by their search efforts.
** For Wiki editors, it makes cleanup easier by reducing the effort involved in researching whether a reported bug is still an issue; this can even lead to greater autonomy if the reader finds new information and comes back to edit the wiki.

===== "See also" section =====

* ''See also'' sections contain a list of links to references and sources of additional information.
* This should be a list where each entry is started with {{Ic|*}}, which creates a MediaWiki bulleted list.
* Use the standard title of ''See also'' and place the section last in the article. Other similar titles such as ''External links'', ''More resources'', etc. should be avoided.

=== Section headings ===

* Headings should start from level 2 ({{Ic|1===}}), because level 1 is reserved for article titles.
* Do not skip levels when making subsections, so a subsection of a level 2 needs a level 3 heading and so on.
* Headings use sentence case, not title case: ''My new heading'', '''not''' ''My New Heading''.
* Avoid using links in headings because they break style consistency and do not stand out well enough. Usually the anchor text is also found in the section content, otherwise you can use a simple sentence like:
:: See [[main page|Some related article]] for more information.
: For the same reason, also avoid using any kind of HTML or wiki markup code, including [[#Code formatting]] templates. See also [[Help:Style/Formatting and punctuation]].
* See [[Help:Effective use of headers]] for more information.

=== Formatting ===

==== Code formatting ====

* Use [[Template:ic]] for short lines of code, file names and paths, configuration parameters, variables and [[Help:Style/Formatting and punctuation#Monospace|other cases]] to be represented inline; for example: Run {{ic|sh ./hello_world.sh}} in the console.

* For single lines of code (command line input or output code and file content) to be represented in a proper frame, simply start them with a single space character; see also [[Help:Editing#Code]]. Example:

$ sh ./hello_world.sh

Hello World

* Use [[Template:bc]] for multiple lines of code (command line input or output code and file content) to be represented in a proper frame; for example:

{{bc|#!/bin/sh

# Demo
echo "Hello World"}}

* Use [[Template:hc]] when in the need of representing both command line input and output; for example:

{{hc|$ sh ./hello_world.sh|Hello World}}

* When you need to represent file content and you feel it may be difficult for readers to understand which file that code refers to, you can also use [[Template:hc]] to show the file name in the heading; for example:

{{hc|~/hello_world.sh|<nowiki>
#!/bin/sh

# Demo
echo "Hello World"</nowiki>}}

* For code block such as a configuration file, consider focusing the reader to the relevant lines and ellipsing ({{ic|...}}) any surrounding, non-relevant content.

* See the [[Help:Template]] article for more information and for troubleshooting problems with template-breaking characters like {{ic|1==}} or {{ic|<nowiki>|</nowiki>}}.

==== Command line text ====

* When using inline code ([[Template:ic]]), no prompt symbol is to be represented; any notes about permissions must be added explicitly to the surrounding text.
* When using code block ([[Template:bc]] or lines starting with a space character), use {{ic|$}} as a prompt for regular user commands; use {{ic|#}} as a prompt for root commands. {{Note|Because {{ic|#}} is also used to denote comments in text files, you should always make sure to avoid ambiguities, usually by explicitly writing to run the command or edit a text file.}}
** The sentence introducing a command block should usually end with {{ic|:}}.
** Unless really necessary, prefer using: {{bc|# ''command''}} instead of writing: {{bc|$ sudo ''command''}}
** Do not use the root prompt and the ''sudo'' command together, like in: {{bc|# sudo ''command''}}
** To show running a command [[List of applications/Security#Privilege elevation|as another user]], prefix the prompt with the username in square brackets: {{bc|[archie]$ ''command''}}
** Do not add comments in the same box of a command; for example: {{bc|# pacman -S foo #Install package foo}}
** Avoid writing excessively long lines of code: use line-breaking techniques when possible.
* Do not assume the user uses [[sudo]] or other privilege escalation utilities (e.g. ''gksu'', ''kdesu'').

==== Keyboard keys ====

* The standard way to represent keyboard keys in articles is using instances of [[Template:ic]].
* Letter keys should be represented in lower case: {{ic|a}}. To represent upper-case letters, use {{ic|Shift+a}} instead of {{ic|Shift+A}} or {{ic|A}}.
* The correct way to represent key ''combinations'' makes use of the {{ic|+}} symbol to join keys, with no additional spaces around it, in a single instance of the template: {{ic|Ctrl+c}}. {{ic|Ctrl + c}}, {{ic|Ctrl}}+{{ic|c}}, {{ic|Ctrl-c}} are non-compliant forms, and should be avoided.
* The correct way to represent key ''sequences'' is either verbose, e.g. "press {{ic|g}} followed by {{ic|Shift+t}}", or concise, separating the keys with a single space in different instances of the template: {{ic|g}} {{ic|Shift+t}}.
* The following are the standard ways of representing some special keys:
** {{ic|Shift}} (not {{ic|SHIFT}})
** {{ic|Ctrl}} (not {{ic|CTRL}} or {{ic|Control}})
** {{ic|Alt}} (not {{ic|ALT}})
** {{ic|Super}} (not {{ic|Windows}} or {{ic|Mod}})
** {{ic|Enter}} (not {{ic|ENTER}} or {{ic|Return}})
** {{ic|Esc}} (not {{ic|ESC}} or {{ic|Escape}})
** {{ic|Space}} (not {{ic|SPACE}})
** {{ic|Backspace}}
** {{ic|Tab}}
** {{ic|Ins}} (not {{ic|INS}} or {{ic|Insert}})
** {{ic|Del}} (not {{ic|DEL}} or {{ic|Delete}})
** {{ic|PrintScreen}}
** {{ic|Up}} (not {{ic|↑}} or {{ic|Up Arrow}}) – similarly for other arrow keys
** {{ic|PageUp}}
** {{ic|PageDown}}
** {{ic|Fn}} (not {{ic|FN}} or {{ic|fn}}) – the [[Wikipedia:Fn key|function key]] present on many laptops
** {{ic|Home}} (not {{ic|HOME}} or {{ic|Beginning}})
** {{ic|End}} (not {{ic|END}})

==== Notes, Warnings, Tips ====

* A [[Template:Note|Note]] should be used for information that somehow diverges from what the user would naturally expect at some point in the article. This includes information that gives more in-depth knowledge on something that otherwise would be considered a bit extraneous to the article. Another example is when needing to point out a temporary announcement, like a change in the name of a package.
: A Note can also be used to highlight information that is important, but easily overlooked by someone new to the subject area.

* A [[Template:Warning|Warning]] should be used where the described procedure could carry severe consequences, such as being reasonably difficult to undo, or resulting in damage to the system. Warnings should generally indicate both the worst case scenarios, as well as the conditions that could lead to, or avoid such worst cases.
: In general, do not abuse Warnings: if you are undecided, chances are high that you should use a Note.

* A [[Template:Tip|Tip]] should indicate a method or procedure that could be useful and bring benefits to somebody, albeit not needed to complete the operation being dealt with, and therefore safely ignore-able.

* When two or more notes, warnings or tips have to appear one after each other at the same point of an article, prefer grouping their texts in a list inside a single template, avoiding stacking the templates unless they are completely unrelated; for example:

:{{Tip|
:* Tip example #1.
:* Tip example #2.}}

==== Tables ====

See [[mw:Help:Tables]] for the syntax.

* Tables should generally have the {{ic|wikitable}} class.
* Comparison tables should additionally have the {{ic|sortable}} class.
* Use table headers and [[Help:Template#Table cell|table cell templates]] when appropriate.
* Table headers should be in sentence case.
* Table legends should use definition lists and be placed before tables.
* Footnotes or remarks should use {{ic|<nowiki>1</nowiki>}}, {{ic|<nowiki>2</nowiki>}}, etc. and an ordered list below the table instead of [[Wikipedia:Unicode subscripts and superscripts|Unicode characters]].

=== Instructions ===

==== File editing requests ====

* Where it might be helpful, a link to [[Help:Reading#Append, add, create, edit]] can be added.
* Do not assume a specific text editor—[[nano]], [[Vim]], [[Emacs]], etc.—when requesting text file edits, except when necessary.
* In general, do not use commands to implicitly request text file edits, for example:
::{{ic|echo -e "clear\nreset" >> ~/.bash_logout}} should be:
:::Append the following lines to {{ic|~/.bash_logout}}:
:::{{bc|clear reset}}
:A common exception are commands which involve generating a complex, system-specific output—for example, {{ic|genfstab -U /mnt >> /mnt/etc/fstab}}.

==== Package management instructions ====

* All package management instructions should use a simple statement instead of example commands.
* Using the [[install]] redirect or its variants (e.g. {{ic|<nowiki>[[install]]ed</nowiki>}}) is recommended at least on the first occurrence of an installation request.
* The package (or packages, or package groups) involved must be linked, preferably ''without variants'' (typically denoted by a suffix such as {{ic|-bin}}, {{ic|-git}}, or {{ic|-nightly}}) unless they provide a meaningful difference.
* Do not provide specific instructions for non-native package managers (e.g. [[Flatpak]], {{ic|make install}}); although a [[#Notes, Warnings, Tips|Tip]] linking to a meaningfully different packaging is acceptable, for example if upstream support is exclusive to them.
* You are granted the flexibility to adapt the wording to your specific article, see the section on [[#Official packages]] for more examples.

===== Official packages =====

* Avoid examples of ''pacman'' commands for the installation of official packages: both for simplicity's sake (every Arch user should know [[pacman]]'s article by memory), and to avoid errors such as {{ic|pacman -Sy package}}, or never-ending discussions such as the choice between {{ic|pacman -S package}} and {{ic|pacman -Syu package}}. All the more reason you should not suggest the use of ''pacman'' frontends or wrappers.
: Instead, just use a simple statement like:
:: [[Install]] the {{Pkg|foobar}} package.
: Or, if for example the application name differs from the package name:
:: ''MyApplication'' can be [[install]]ed with the {{Pkg|my-app-pkg}} package.
: The instructions for the installation of a list of packages may appear as:
:: [[Install]] the {{Pkg|foobar1}}, {{Pkg|foobar2}} and {{Pkg|foobar3}} packages.
: If referring to a package group you may use:
:: [[Install]] the {{Grp|foobar}} group.

* Use [[Template:Pkg]]; for example, {{ic|<nowiki>{{Pkg|foobar}}</nowiki>}}.
: When referring to package groups, use [[Template:Grp]] instead; for example, {{ic|<nowiki>{{Grp|foobar}}</nowiki>}}.

* If the package is hosted in the ''core'' or ''extra'' repositories, do not make reference to the repository: it increases maintenance because it is not uncommon for a package to be moved to a different repository. If the package is hosted in an official repository which is not enabled by default (''multilib'', ''core-testing'', etc.), mentioning it is required, using a wording like:
::[[Install]] the {{Pkg|foobar}} package from the official [[multilib]] repository.

===== AUR packages =====

* Avoid using examples of how to install AUR packages, neither with the official method nor mentioning AUR helpers. Every user who installs unofficial packages should have read the [[Arch User Repository]] article and be aware of all the possible consequences on their system.
: Instead, just use a simple statement like:
:: Install the {{AUR|foobar}} package.
* Use [[Template:AUR]] (e.g. {{ic|<nowiki>{{AUR|foobar}}</nowiki>}}).

===== Unofficial repositories =====

* When suggesting to use an unofficial repository for installing a pre-built package, do not provide instructions for enabling the repository, rather add the repository to [[Unofficial user repositories]] and link to the relevant repository section; for example {{ic|<nowiki>[[Unofficial user repositories#example|example]]</nowiki>}}.
* Just like with [[#Official packages|official packages]], do not add examples of ''pacman'' commands; for example:
:: Install the ''foobar'' package from the [[Unofficial user repositories#example|example]] repository.
: If the package is also available in the [[AUR]]:
:: Install the {{AUR|foobar}} package, also available in the [[Unofficial user repositories#example|example]] repository.
: If the package is available in the [[AUR]] with a different name:
:: Install the {{AUR|aurpkg}} package, also available as ''builtpackage'' from the [[Unofficial user repositories#example|example]] repository.

==== systemd units operations ====

* Do not give examples of how to enable, start, or perform any other basic operations with ''systemctl'' on [[systemd]] units; instead, use a simple sentence listing the units involved, possibly remarking dependencies or conflicts with other units, and a description of the actions to be performed; for example:
:: To have GDM launched at boot time, [[enable]] {{ic|gdm.service}}.
: Or, if for example the unit is a template that needs instantiation:
:: To enable automatic switching of ''netctl'' profiles on a wireless interface, [[enable]] an instance of {{ic|netctl-auto@.service}} with the interface name; for example {{ic|netctl-auto@wlan0.service}}.
: You are granted the flexibility to adapt the wording to your specific article.
* Make sure to link to [[Help:Reading#Control of systemd units]] through a dedicated redirect like {{ic|<nowiki>[[start]]</nowiki>}}, {{ic|<nowiki>[[restart]]</nowiki>}}, {{ic|<nowiki>[[enable]]</nowiki>}} or {{ic|<nowiki>[[stop]]</nowiki>}}. Use the {{ic|<nowiki>[[enable/start]]</nowiki>}} redirect for instructing readers to use the {{ic|enable --now}} operation.

=== Coding style ===

* When adding commands or scripts, use a consistent coding style throughout the article, possibly also referring to the other articles, especially if there are any related ones. If available, respect the official or most common coding style guidelines for the language.
* Avoid deprecated features of the programming/scripting language you are using; for example, use the {{ic|$()}} syntax for shell command substitution instead of the backticks/grave ({{ic|``}}) syntax.
* Scripts should be written to only do what is minimally necessary to perform the required task in the clearest possible way. They should not be designed for flexibility or expansion, prefer using [[Help:Reading#Pseudo-variables in code examples|pseudo-variables]] over actual variables. Do not add irrelevant functionality such as argument parsing or output formatting.
* Scripts should be added mainly for educational purposes, when the verbose explanation in the article's text cannot be made sufficiently clear and concise. They can be useful for example to show how a complex command is intended to be used, or how related or interdependent commands are meant to work together.
* If a script is deemed to add value to an article but does not meet the criteria above, it can be linked externally, possibly publishing it as a [https://gist.github.com gist].
* When representing the name or path of a directory, end it with a slash or explicitly add an appositive such as "directory" of "folder"; for example:
:* "Check if the {{ic|/sys/firmware/efi}} directory has been created", not "Check if {{ic|/sys/firmware/efi}} has been created".
:* "Place a ''.conf'' file in {{ic|/etc/modules-load.d/}}", not "Place a ''.conf'' file in {{ic|/etc/modules-load.d}}".
* Arguments containing spaces should be quoted with double quotation marks, e.g. {{ic|cd "foo bar"}} instead of {{ic|cd foo\ bar}}.

=== Shells ===

* Do not assume a particular shell as the user's shell (e.g. Bash), except when really needed; try to be as shell-neutral as possible when writing or editing articles.

=== Hypertext metaphor ===

See [[Help:Editing#Links]] for the syntax of internal, interwiki and external links.

* Try to interlink your article with as many others as you can, using the words in the text.
* Only link to existing articles. If you encounter a dead link, try to fix it. External links that appear to be dead should be marked with [[Template:Dead link]].
* Avoid implicit links whenever possible, prefer instructions like "See the [[systemd]] article for more information", instead of "See [[systemd|here]] for more information".

A link can be used in two ways:

* As a '''topic reference''', where the link is a term, part of the running text, and subject to regular grammar rules; use a link label if needed. Internal/interwiki links should point to a [[#Redirect pages|redirect]] if available.
* As a '''page/section reference''', do not use a link label, and spell the title according to [[Template:Lowercase title]] where used; in particular, do not hide the {{ic|#}} symbol in same-page section links, e.g. {{ic|<nowiki>[[#Hypertext metaphor|Hypertext metaphor]]</nowiki>}}.

See these examples:

{| class="wikitable"
! Topic reference !! Page/section reference
|-
| Use an [[SSH agent]] to speed up authentication.
| Follow [[SSH keys#SSH agents]] to speed up authentication.
|-
| [[Font configuration#Subpixel rendering|Subpixel rendering]] is supported by most monitors.
| Enable subpixel rendering as described in [[Font configuration#Subpixel rendering]].
|-
| Include a [[Dm-crypt/Device encryption#Keyfiles|keyfile]] in the ''initramfs''.
| Instructions can be found in [[dm-crypt/Device encryption#Keyfiles]].
|-
| Be aware that [[Wikipedia:Mouse keys|mouse keys]] is disabled by default.
| See [[Wikipedia:Mouse keys]] for details.
|-
| We have [[#Hypertext metaphor|style rules]] for links.
| The [[#Hypertext metaphor]] section has style rules for links.
|}

* Before writing a specific procedure in an article or describing something in particular, always check if there is already an article that treats that part in detail; in that case, link that article instead of duplicating its content. Also:
**For technical terms not covered by an article in the ArchWiki, link to the relevant Wikipedia page.
**If the upstream documentation for the subject of your article is well-written and maintained, prefer just writing Arch-specific adaptations and linking to the official documentation for general information.
::For example: "[[Kernel parameters]] are used to issue [[Wikipedia:system call|system call]]s at boot; see the [https://docs.kernel.org/admin-guide/kernel-parameters.html Linux kernel documentation] for a complete list."
:In general, maintain coherence with [[Help:Reading#Organization]].
* Except in rare cases, you should not leave an article as a dead-end page (an article that does not link to any other), or an orphan page (an article that is not linked to from any other).
* Do not use interwiki links for links to localized pages of the same language of the article being edited, because they will not be shown in [[Special:WhatLinksHere]] pages; for example, using {{ic|<nowiki>[[:hu:Main page]]</nowiki>}} in a Hungarian article is wrong, while {{ic|<nowiki>[[Main page (Magyar)]]</nowiki>}} is correct. Using this kind of link between different languages is acceptable, because this would make it easier to move the articles to a separate wiki in case a separate wiki is created in the future. Finally, note the difference of these kinds of links from [[#Interlanguage links]], which do not have the colon at the beginning.
* Prefer the "Wikipedia:" interwiki prefix over the shorter "w:" prefix.

==== Man pages ====

* [[Man page]]s should be referenced using [[Template:man]].

=== Supported kernel versions ===

* Do not remove any notes or adaptations regarding kernel versions greater than or equal to the minimum version between the current {{Pkg|linux-lts}} package in the ''core'' repository, and the kernel on the latest [https://archlinux.org/download/ installation media].

=== Non-pertinent content ===

* Please do not sign articles, nor credit article authors: the ArchWiki is a work of the community, and the history of each article is enough for crediting its contributors. Note that reporting the sources used to write an article is good practice: you can use the "See also" section for this purpose.
* Uploading files is disabled for normal users, and including images in articles is not allowed. As an alternative you can include links to external images or galleries, and if you need to draw simple diagrams you may use an ASCII editor like [http://www.asciiflow.com/ Asciiflow] and [[Template:Text art]]; rationale:
** Maintenance: Arch is rolling release, and images would make updating articles much more difficult.
** Necessity: Arch does not develop nor maintain any sort of GUI application, so we do not need to display any screenshot.
** Moderation: free image upload would require time to be spent removing oversized or inappropriate images.
** Accessibility: we support users with slow connections, text-only browsers, screen readers and the like.
** Efficiency: images waste server bandwidth and storage space.
** Simplicity: text-only articles just look simpler and tidier.

=== Spelling ===

* Avoid contractions: "don't", "isn't", "you've", etc. should be "do not", "is not", and "you have", for example.
* Avoid unnecessary [[Wikipedia:Clipping (morphology)|shortening]] of words: for example, instead of "repo", "distro", and "config", prefer "repository", "distribution", and "configuration". In the same fashion, prefer using the long form of ''uncommon'' command options instead of their single-character counterpart. See also [[Help:Style/Formatting and punctuation#Configuration parameters, variables, options, properties...]].
* The names of projects, applications, executables etc. should be spelled, especially regarding capitalization, primarily according to their official documentation style. This includes the case where the documentation treats the name as a common noun, i.e. with an uppercase first letter when appearing at the beginning of a sentence, and lowercase otherwise. If the official documentation does not apply a consistent style, follow the style already used in the ArchWiki. If the name does not appear in the ArchWiki, or it still has inconsistent spelling, choose a style and conform to it throughout the article, also possibly updating the other pages that mention the name. Taking Git as an example you may choose to spell the name with the first letter uppercase ("Git") when talking about the project/software generally, and use all lowercase and italic ("''git''") when referring to the compiled program. When name capitalization can generate controversy, explicitly define a style in the article's talk page. See also [[Help:Style/Formatting and punctuation#Executable/application names]]
* ArchWiki prefers no national variety of English over any other, adopting the same guidelines outlined in [[Wikipedia:Wikipedia:Manual of Style#National varieties of English]]; in case of conflict with any of ArchWiki's other explicitly defined guidelines, ArchWiki's prevail. When writing new content within an existing article it is recommended to maintain the [[w:Wikipedia:Manual_of_Style/Spelling|spelling convention]] already prevalent in it; if the article does not have a clear prevalent spelling, write accordingly to the variant used in the edited section. Harmonizing the spelling around the edited content is acceptable; refrain from performing edits whose main purpose is changing or harmonizing the spelling standard of articles or series thereof.

=== Language register ===

* Articles should be written using formal, professional, and concise language. Care should be taken to remove grammar and orthography errors through edit previews and proofreading.
* Remember not only to answer ''how'', but also ''why''. Explanatory information always goes further toward imparting knowledge than does instruction alone.
* Do not omit terms that are necessary to give an exact, unambiguous meaning to a sentence; for example, always add the word "repository" when mentioning the name of a repository.
* Do not use indefinite time references such as "currently", "at the time of writing" or "soon"; replace them with definite expressions such as "as of May 2015" etc.
* Write objectively: do not include personal comments on articles; use discussion pages for this purpose. In general, do not write in first person.
* When editing content, be consistent with the style used in the rest of the article; for example, if the reader is always addressed using the second person, this style should be adopted by the added content; the same goes if third person or passive voice are clearly dominant throughout the article.
* When offering a choice among different options (pieces of software, methods to do something, etc.) do not explicitly recommend one over the others, but objectively describe the advantages and disadvantages of each, thus helping the reader to make the best decision for their personal case.
* Prefer neutral pronouns such as [[Wikipedia:Singular they|they/them]] when referring to the reader or people in general.

== Category pages ==

* [[Help:Category|Category]] name must use [[Wikipedia:Letter case#Sentence case|sentence case]].
* Every category must be appropriately categorized under at least one parent category, except for root categories, which are:
** [[:Category:Archive]],
** [[:Category:DeveloperWiki]],
** [[:Category:Languages]],
** [[:Category:Maintenance]], and
** [[:Category:Sandbox]].
* A category can be categorized under more than one category, provided one is not ancestor of the others.
* Avoid circular relationships: two categories cannot be reciprocal ancestors.
* Do not categorize a category under itself (self-categorized category).
* Categories must be included at the top of the category page.
* Categories should not redirect, except temporarily during [[Help:Procedures#Rename a category|renaming]].
* By default, category names should be in the singular form ("topic" categories, for example [[:Category:Simulation]]); they should be in the plural form if the singular form can be used to describe ''one'' of its members ("set" categories, for example [[:Category:Boot loaders]]).

== Redirect pages ==

* It is encouraged to create redirect pages for acronyms or grammatical variants of an existing article's title, or for a term or topic discussed in a subsection of a more generic article; for example [[ALSA]], [[daemon]] or [[AIGLX]]. Redirects can simplify the source text by replacing labelled links, compare the previous examples with {{ic|<nowiki>[[Advanced Linux Sound Architecture|ALSA]]</nowiki>}}, {{ic|<nowiki>[[daemons|daemon]]</nowiki>}} or {{ic|<nowiki>[[Xorg#Composite|AIGLX]]</nowiki>}}.
* Redirect pages should contain only the redirect code and nothing else; the only exceptions are:
** [[ArchWiki:Archive|Archived]] pages, which are in fact redirects; must be categorized under [[:Category:Archive]].
** [[Help:Procedures#Rename a category|Renamed categories]] can contain a [[Template:Archive]] flag.
* Redirect only to internal articles; do not use interwiki redirections.
:Redirects using interlanguage links are exceptionally allowed in accordance with [[Help:i18n]], and upon authorization from the [[ArchWiki:Maintenance Team]].
* See [[Help:Editing#Redirects]] for more information.

== User pages ==

* Pages in the [[Special:PrefixIndex/User:|User]] namespace cannot be categorized.
* Pages in the [[Special:PrefixIndex/User:|User]] namespace can only be linked from other pages in the ''User'' or ''talk'' namespaces, unless authorization to do otherwise is given by Administrators.
* Pages in the [[Special:PrefixIndex/User:|User]] namespace cannot be targets of [[Help:Editing#Redirects|redirects]] from other namespaces.

== Generic rules ==

=== Edit summary ===

See [[ArchWiki:Contributing#The 3 fundamental rules]].

=== HTML tags ===

* Usage of HTML tags is generally discouraged; always prefer using wiki markup or templates when possible (see [[Help:Editing]] and related).
* When tempted to use {{ic|<nowiki><pre>code</pre></nowiki>}}, always resort to {{ic|<nowiki>{{bc|code}}</nowiki>}}. When tempted to use {{ic|<nowiki><tt>text</tt></nowiki>}} or {{ic|<nowiki><code>text</code></nowiki>}}, always resort to {{ic|<nowiki>{{ic|text}}</nowiki>}}.
* Especially avoid HTML comments ({{ic|<nowiki></nowiki>}}): it is likely that a note added in a HTML comment can be explicitly shown in the article's discussion page. You can add an appropriate [[Help:Template#Status|status template]] in place of the comment.
* Use {{ic|<nowiki> </nowiki>}} only when necessary; to start a new paragraph or break a line, put a blank line below it.
: {{Tip|Common exceptions to this rule are when it is necessary to '''break a line in a list item''' and you cannot use a sub-item, or '''inside a template''' and you cannot use a list.}}

Help:Style

2026-05-18T09:59:36Z

Erus Iluvatar: /* systemd units operations */ add the non-intuitive redirect for "enable --now"

[[Category:Help]]
[[es:Help:Style]]
[[hu:Help:Style]]
[[it:Help:Style]]
[[ja:ヘルプ:スタイル]]
[[pt:Help:Style]]
[[ru:Help:Style]]
[[zh-hans:Help:Style]]
{{Related articles start}}
{{Related|/Formatting and punctuation}}
{{Related|/White space}}
{{Related|Help:Discussion}}
{{Related|Help:Editing}}
{{Related|Help:Reading}}
{{Related|Help:Template}}
{{Related articles end}}

These style conventions encourage tidy, organized, and visually consistent articles. Follow them as closely as possible when editing the ArchWiki.

== Article pages ==

=== Title ===

* Titles should use [[Wikipedia:Sentence case|sentence case]], e.g. "Title for new page" is correct, while "Title for New Page" is not. Note that common words that are part of a proper name or an upper-case acronym must be capitalized, e.g. "Advanced Linux Sound Architecture", not "Advanced Linux sound architecture". Namespaces are not considered part of titles, so "ArchWiki:Example article" is correct, while "ArchWiki:example article" is not. Subpage names should start with a capital letter, so "My page/My subpage" is correct, while "My page/my subpage" is not.
* By default, the topic name in titles should be in the singular form; it should be in the plural form if it represents a group or class of something and is a countable noun or perceived as such.
* Unless the subject of the article is primarily known by its acronym, prefer using the full name in the title of the article. Do not include both the full name and the acronym (e.g. in parentheses) in the title, instead use a [[#Redirect pages|redirect]] on the acronym page that points to the page titled with the full name.
* Titles of localized pages must follow [[Help:i18n#Page titles]].
* See the [[Help:Article naming guidelines]] article for more information.

=== Layout ===

* Order elements in an article as follows:

# [[#Magic words|Magic words]] (optional)
# [[#Categories|Categories]]
# [[#Interlanguage links|Interlanguage links]] (optional)
# [[#Article status templates|Article status templates]] (optional)
# [[#Related articles box|Related articles box]] (optional)
# [[#Preface or introduction|Preface or introduction]]
# Table of contents (automatic)
# Article-specific sections.

==== Magic words ====

* Behavior switches—and in general, all of the [[mw:Help:Magic words|magic words]] that change how an article is displayed or behaves but do not add content by themselves—should all go at the very top of articles.

: This rule applies in particular to {{ic|<nowiki>{{DISPLAYTITLE:title}}</nowiki>}} and [[Template:Lowercase title]], which makes use of the former.

==== Categories ====

* Every article must be categorized under at least one existing category.
* An article can belong to more than one category, provided one is not ancestor of the others.
* Categories must be included at the top of every article, right below any magic words. {{Note|This is different from some other MediaWiki projects such as Wikipedia, which include categories at the bottom.}}
* There should be no blank lines between categories and the first line of text (or interlanguage links, if present), because this introduces extra space at the top of the article.
* See the [[Help:Category]] article for more information.

==== Interlanguage links ====

* If the article has translations in the local or an external Arch Linux wiki, interlanguage links must be included right below the categories and above the first line of text. Note that they will actually appear in the appropriate column to the left side of the page.
* There should be no blank lines between interlanguage links and the first line of text, because this introduces extra space at the top of the article.
* When adding or editing interlanguage links you should take care of repeating your action for all the already existing translations.
* Do not add more than one interlanguage link for each language to an article.
* Do not add interlanguage links for the same language of the article.
* The interlanguage links must be sorted alphabetically based on the language tag, not the local name; for example {{ic|<nowiki>[[fi:Title]]</nowiki>}} comes before {{ic|<nowiki>[[fr:Title]]</nowiki>}}, even though "Suomi" would come after "Français".
* See the [[Help:i18n]] and [[Wikipedia:Help:Interlanguage links]] articles for more information.

==== Article status templates ====

* [[Help:Template#Status|Status templates]] that refer to the whole article must be included right below the categories (or interlanguage links, if present) and right above the introduction (or the [[#Related articles box|Related articles box]], if present).
* Status templates that refer to a specific portion of an article must be placed as close as possible above such portion, while appropriately avoiding to break paragraphs, code blocks, or other pre-existing templates.
* Always accompany an article status template with some words of explanation in the dedicated field (examples are provided in each template's page), possibly even opening a discussion in the talk page.

==== Related articles box ====

* Provides a simple list of related internal articles.
* Optionally included right below categories (or interlanguage links, or Article status templates, if present).
* It can only be made of [[Template:Related articles start]], [[Template:Related]] and [[Template:Related articles end]]. See also the guidelines in those pages.
* Non-English articles can make use of [[Template:Related2]] for translating the anchor text.
* Use the [[#"See also" section]] for a more complete and detailed list that also includes link descriptions and interwiki or external links.

==== Preface or introduction ====

* Included right above the first section of the article.
: '''Do not''' explicitly make an {{Ic|1=== Introduction ==}} or {{Ic|1=== Preface ==}} section: let it appear above the first section heading. A table of contents is shown automatically between the preface and first section when there are [[Help:Editing#Headings and subheadings|sufficient]] sections in the article.
* Describes the topic of the article.
: Rather than paraphrasing or writing your own (possibly biased) description of a piece of software, you can use the upstream author's description, which can usually be found on the project's home page or about page, if it exists—an example is [[WireGuard]]. You may also use the description from Wikipedia, as is the case with [[ImageMagick]].

See [[Help:Writing article introductions]] for more information.

==== Standard sections ====

===== "Installation" section =====

* The ''Installation'' section describes how to install the software, see [[#Package management instructions]].
* Use the standard title of ''Installation'' and order it early in the article.

===== "Known issues" section =====

* ''Known issues'' sections are used for known bugs or usage problems which do not have a solution yet (compare to [[#"Troubleshooting" section]]).
* Use the standard title of ''Known issues'' and order it early in the article.
* If a bug report exists for the known issue, it is very desirable that you provide a link to it. If it does not exist, you should report it yourself, thus increasing the chances that the bug will be fixed.
* Refrain from mentioning dates or version numbers (for example, "Linux kernel 3.17 does not support device XYZ as of October 2014 yet.") whenever possible. Again, prefer to link references like bug reports for follow-up information instead.

===== "Tips and tricks" section =====

* ''Tips and tricks'' sections provide advanced tips or examples of using the software.
* Use the standard title of ''Tips and tricks''.
* The various tips and tricks should be organized in subsections.

===== "Troubleshooting" section =====

* ''Troubleshooting'' sections are used for frequently asked questions regarding the software or for solutions to common problems (compare to [[#"Known issues" section]]).
* Use the standard title of ''Troubleshooting''. Common misspellings that should be avoided are ''Trouble shooting'', ''Trouble-shooting'', and ''TroubleShooting''.
* You can also report temporary workarounds for known bugs; in this case, it is ''mandatory'' that you provide a link to the bug report (or similar appropriate sources, like a forum post containing a workaround). In case it has not been reported yet, you should report it yourself, thus increasing the chances that the bug will be properly fixed. Refrain from mentioning dates or version numbers whenever possible. There are great benefits in linking to external references like bug reports both for readers and editors:
** For readers, the Wiki does not become a stopping point: they can find more information close to the source that may have otherwise been missed by their search efforts.
** For Wiki editors, it makes cleanup easier by reducing the effort involved in researching whether a reported bug is still an issue; this can even lead to greater autonomy if the reader finds new information and comes back to edit the wiki.

===== "See also" section =====

* ''See also'' sections contain a list of links to references and sources of additional information.
* This should be a list where each entry is started with {{Ic|*}}, which creates a MediaWiki bulleted list.
* Use the standard title of ''See also'' and place the section last in the article. Other similar titles such as ''External links'', ''More resources'', etc. should be avoided.

=== Section headings ===

* Headings should start from level 2 ({{Ic|1===}}), because level 1 is reserved for article titles.
* Do not skip levels when making subsections, so a subsection of a level 2 needs a level 3 heading and so on.
* Headings use sentence case, not title case: ''My new heading'', '''not''' ''My New Heading''.
* Avoid using links in headings because they break style consistency and do not stand out well enough. Usually the anchor text is also found in the section content, otherwise you can use a simple sentence like:
:: See [[main page|Some related article]] for more information.
: For the same reason, also avoid using any kind of HTML or wiki markup code, including [[#Code formatting]] templates. See also [[Help:Style/Formatting and punctuation]].
* See [[Help:Effective use of headers]] for more information.

=== Formatting ===

==== Code formatting ====

* Use [[Template:ic]] for short lines of code, file names and paths, configuration parameters, variables and [[Help:Style/Formatting and punctuation#Monospace|other cases]] to be represented inline; for example: Run {{ic|sh ./hello_world.sh}} in the console.

* For single lines of code (command line input or output code and file content) to be represented in a proper frame, simply start them with a single space character; see also [[Help:Editing#Code]]. Example:

$ sh ./hello_world.sh

Hello World

* Use [[Template:bc]] for multiple lines of code (command line input or output code and file content) to be represented in a proper frame; for example:

{{bc|#!/bin/sh

# Demo
echo "Hello World"}}

* Use [[Template:hc]] when in the need of representing both command line input and output; for example:

{{hc|$ sh ./hello_world.sh|Hello World}}

* When you need to represent file content and you feel it may be difficult for readers to understand which file that code refers to, you can also use [[Template:hc]] to show the file name in the heading; for example:

{{hc|~/hello_world.sh|<nowiki>
#!/bin/sh

# Demo
echo "Hello World"</nowiki>}}

* For code block such as a configuration file, consider focusing the reader to the relevant lines and ellipsing ({{ic|...}}) any surrounding, non-relevant content.

* See the [[Help:Template]] article for more information and for troubleshooting problems with template-breaking characters like {{ic|1==}} or {{ic|<nowiki>|</nowiki>}}.

==== Command line text ====

* When using inline code ([[Template:ic]]), no prompt symbol is to be represented; any notes about permissions must be added explicitly to the surrounding text.
* When using code block ([[Template:bc]] or lines starting with a space character), use {{ic|$}} as a prompt for regular user commands; use {{ic|#}} as a prompt for root commands. {{Note|Because {{ic|#}} is also used to denote comments in text files, you should always make sure to avoid ambiguities, usually by explicitly writing to run the command or edit a text file.}}
** The sentence introducing a command block should usually end with {{ic|:}}.
** Unless really necessary, prefer using: {{bc|# ''command''}} instead of writing: {{bc|$ sudo ''command''}}
** Do not use the root prompt and the ''sudo'' command together, like in: {{bc|# sudo ''command''}}
** To show running a command [[List of applications/Security#Privilege elevation|as another user]], prefix the prompt with the username in square brackets: {{bc|[archie]$ ''command''}}
** Do not add comments in the same box of a command; for example: {{bc|# pacman -S foo #Install package foo}}
** Avoid writing excessively long lines of code: use line-breaking techniques when possible.
* Do not assume the user uses [[sudo]] or other privilege escalation utilities (e.g. ''gksu'', ''kdesu'').

==== Keyboard keys ====

* The standard way to represent keyboard keys in articles is using instances of [[Template:ic]].
* Letter keys should be represented in lower case: {{ic|a}}. To represent upper-case letters, use {{ic|Shift+a}} instead of {{ic|Shift+A}} or {{ic|A}}.
* The correct way to represent key ''combinations'' makes use of the {{ic|+}} symbol to join keys, with no additional spaces around it, in a single instance of the template: {{ic|Ctrl+c}}. {{ic|Ctrl + c}}, {{ic|Ctrl}}+{{ic|c}}, {{ic|Ctrl-c}} are non-compliant forms, and should be avoided.
* The correct way to represent key ''sequences'' is either verbose, e.g. "press {{ic|g}} followed by {{ic|Shift+t}}", or concise, separating the keys with a single space in different instances of the template: {{ic|g}} {{ic|Shift+t}}.
* The following are the standard ways of representing some special keys:
** {{ic|Shift}} (not {{ic|SHIFT}})
** {{ic|Ctrl}} (not {{ic|CTRL}} or {{ic|Control}})
** {{ic|Alt}} (not {{ic|ALT}})
** {{ic|Super}} (not {{ic|Windows}} or {{ic|Mod}})
** {{ic|Enter}} (not {{ic|ENTER}} or {{ic|Return}})
** {{ic|Esc}} (not {{ic|ESC}} or {{ic|Escape}})
** {{ic|Space}} (not {{ic|SPACE}})
** {{ic|Backspace}}
** {{ic|Tab}}
** {{ic|Ins}} (not {{ic|INS}} or {{ic|Insert}})
** {{ic|Del}} (not {{ic|DEL}} or {{ic|Delete}})
** {{ic|PrintScreen}}
** {{ic|Up}} (not {{ic|↑}} or {{ic|Up Arrow}}) – similarly for other arrow keys
** {{ic|PageUp}}
** {{ic|PageDown}}
** {{ic|Fn}} (not {{ic|FN}} or {{ic|fn}}) – the [[Wikipedia:Fn key|function key]] present on many laptops
** {{ic|Home}} (not {{ic|HOME}} or {{ic|Beginning}})
** {{ic|End}} (not {{ic|END}})

==== Notes, Warnings, Tips ====

* A [[Template:Note|Note]] should be used for information that somehow diverges from what the user would naturally expect at some point in the article. This includes information that gives more in-depth knowledge on something that otherwise would be considered a bit extraneous to the article. Another example is when needing to point out a temporary announcement, like a change in the name of a package.
: A Note can also be used to highlight information that is important, but easily overlooked by someone new to the subject area.

* A [[Template:Warning|Warning]] should be used where the described procedure could carry severe consequences, such as being reasonably difficult to undo, or resulting in damage to the system. Warnings should generally indicate both the worst case scenarios, as well as the conditions that could lead to, or avoid such worst cases.
: In general, do not abuse Warnings: if you are undecided, chances are high that you should use a Note.

* A [[Template:Tip|Tip]] should indicate a method or procedure that could be useful and bring benefits to somebody, albeit not needed to complete the operation being dealt with, and therefore safely ignore-able.

* When two or more notes, warnings or tips have to appear one after each other at the same point of an article, prefer grouping their texts in a list inside a single template, avoiding stacking the templates unless they are completely unrelated; for example:

:{{Tip|
:* Tip example #1.
:* Tip example #2.}}

==== Tables ====

See [[mw:Help:Tables]] for the syntax.

* Tables should generally have the {{ic|wikitable}} class.
* Comparison tables should additionally have the {{ic|sortable}} class.
* Use table headers and [[Help:Template#Table cell|table cell templates]] when appropriate.
* Table headers should be in sentence case.
* Table legends should use definition lists and be placed before tables.
* Footnotes or remarks should use {{ic|<nowiki>1</nowiki>}}, {{ic|<nowiki>2</nowiki>}}, etc. and an ordered list below the table instead of [[Wikipedia:Unicode subscripts and superscripts|Unicode characters]].

=== Instructions ===

==== File editing requests ====

* Where it might be helpful, a link to [[Help:Reading#Append, add, create, edit]] can be added.
* Do not assume a specific text editor—[[nano]], [[Vim]], [[Emacs]], etc.—when requesting text file edits, except when necessary.
* In general, do not use commands to implicitly request text file edits, for example:
::{{ic|echo -e "clear\nreset" >> ~/.bash_logout}} should be:
:::Append the following lines to {{ic|~/.bash_logout}}:
:::{{bc|clear reset}}
:A common exception are commands which involve generating a complex, system-specific output—for example, {{ic|genfstab -U /mnt >> /mnt/etc/fstab}}.

==== Package management instructions ====

* All package management instructions should use a simple statement instead of example commands.
* Using the [[install]] redirect or its variants (e.g. {{ic|<nowiki>[[install]]ed</nowiki>}}) is recommended at least on the first occurrence of an installation request.
* The package (or packages, or package groups) involved must be linked, preferably ''without variants'' (typically denoted by a suffix such as {{ic|-bin}}, {{ic|-git}}, or {{ic|-nightly}}) unless they provide a meaningful difference.
* Do not provide specific instructions for non-native package managers (e.g. [[Flatpak]], {{ic|make install}}); although a [[#Notes, Warnings, Tips|Tip]] linking to a meaningfully different packaging is acceptable, for example if upstream support is exclusive to them.
* You are granted the flexibility to adapt the wording to your specific article, see the section on [[#Official packages]] for more examples.

===== Official packages =====

* Avoid examples of ''pacman'' commands for the installation of official packages: both for simplicity's sake (every Arch user should know [[pacman]]'s article by memory), and to avoid errors such as {{ic|pacman -Sy package}}, or never-ending discussions such as the choice between {{ic|pacman -S package}} and {{ic|pacman -Syu package}}. All the more reason you should not suggest the use of ''pacman'' frontends or wrappers.
: Instead, just use a simple statement like:
:: [[Install]] the {{Pkg|foobar}} package.
: Or, if for example the application name differs from the package name:
:: ''MyApplication'' can be [[install]]ed with the {{Pkg|my-app-pkg}} package.
: The instructions for the installation of a list of packages may appear as:
:: [[Install]] the {{Pkg|foobar1}}, {{Pkg|foobar2}} and {{Pkg|foobar3}} packages.
: If referring to a package group you may use:
:: [[Install]] the {{Grp|foobar}} group.

* Use [[Template:Pkg]]; for example, {{ic|<nowiki>{{Pkg|foobar}}</nowiki>}}.
: When referring to package groups, use [[Template:Grp]] instead; for example, {{ic|<nowiki>{{Grp|foobar}}</nowiki>}}.

* If the package is hosted in the ''core'' or ''extra'' repositories, do not make reference to the repository: it increases maintenance because it is not uncommon for a package to be moved to a different repository. If the package is hosted in an official repository which is not enabled by default (''multilib'', ''core-testing'', etc.), mentioning it is required, using a wording like:
::[[Install]] the {{Pkg|foobar}} package from the official [[multilib]] repository.

===== AUR packages =====

* Avoid using examples of how to install AUR packages, neither with the official method nor mentioning AUR helpers. Every user who installs unofficial packages should have read the [[Arch User Repository]] article and be aware of all the possible consequences on their system.
: Instead, just use a simple statement like:
:: Install the {{AUR|foobar}} package.
* Use [[Template:AUR]] (e.g. {{ic|<nowiki>{{AUR|foobar}}</nowiki>}}).

===== Unofficial repositories =====

* When suggesting to use an unofficial repository for installing a pre-built package, do not provide instructions for enabling the repository, rather add the repository to [[Unofficial user repositories]] and link to the relevant repository section; for example {{ic|<nowiki>[[Unofficial user repositories#example|example]]</nowiki>}}.
* Just like with [[#Official packages|official packages]], do not add examples of ''pacman'' commands; for example:
:: Install the ''foobar'' package from the [[Unofficial user repositories#example|example]] repository.
: If the package is also available in the [[AUR]]:
:: Install the {{AUR|foobar}} package, also available in the [[Unofficial user repositories#example|example]] repository.
: If the package is available in the [[AUR]] with a different name:
:: Install the {{AUR|aurpkg}} package, also available as ''builtpackage'' from the [[Unofficial user repositories#example|example]] repository.

==== systemd units operations ====

* Do not give examples of how to enable, start, or perform any other basic operations with ''systemctl'' on [[systemd]] units; instead, use a simple sentence listing the units involved, possibly remarking dependencies or conflicts with other units, and a description of the actions to be performed; for example:
:: To have GDM launched at boot time, [[enable]] {{ic|gdm.service}}.
: Or, if for example the unit is a template that needs instantiation:
:: To enable automatic switching of ''netctl'' profiles on a wireless interface, [[enable]] an instance of {{ic|netctl-auto@.service}} with the interface name; for example {{ic|netctl-auto@wlan0.service}}.
: You are granted the flexibility to adapt the wording to your specific article.
* Make sure to link to [[Help:Reading#Control of systemd units]] through a dedicated redirect like {{ic|<nowiki>[[start]]</nowiki>}}, {{ic|<nowiki>[[restart]]</nowiki>}}, {{ic|<nowiki>[[enable]]</nowiki>}} or {{ic|<nowiki>[[stop]]</nowiki>}}. Use the {{ic|<nowiki>[[enable/start]]</nowiki>}} redirect for instructing readers to use the {{ic|enable --now}} command.

=== Coding style ===

* When adding commands or scripts, use a consistent coding style throughout the article, possibly also referring to the other articles, especially if there are any related ones. If available, respect the official or most common coding style guidelines for the language.
* Avoid deprecated features of the programming/scripting language you are using; for example, use the {{ic|$()}} syntax for shell command substitution instead of the backticks/grave ({{ic|``}}) syntax.
* Scripts should be written to only do what is minimally necessary to perform the required task in the clearest possible way. They should not be designed for flexibility or expansion, prefer using [[Help:Reading#Pseudo-variables in code examples|pseudo-variables]] over actual variables. Do not add irrelevant functionality such as argument parsing or output formatting.
* Scripts should be added mainly for educational purposes, when the verbose explanation in the article's text cannot be made sufficiently clear and concise. They can be useful for example to show how a complex command is intended to be used, or how related or interdependent commands are meant to work together.
* If a script is deemed to add value to an article but does not meet the criteria above, it can be linked externally, possibly publishing it as a [https://gist.github.com gist].
* When representing the name or path of a directory, end it with a slash or explicitly add an appositive such as "directory" of "folder"; for example:
:* "Check if the {{ic|/sys/firmware/efi}} directory has been created", not "Check if {{ic|/sys/firmware/efi}} has been created".
:* "Place a ''.conf'' file in {{ic|/etc/modules-load.d/}}", not "Place a ''.conf'' file in {{ic|/etc/modules-load.d}}".
* Arguments containing spaces should be quoted with double quotation marks, e.g. {{ic|cd "foo bar"}} instead of {{ic|cd foo\ bar}}.

=== Shells ===

* Do not assume a particular shell as the user's shell (e.g. Bash), except when really needed; try to be as shell-neutral as possible when writing or editing articles.

=== Hypertext metaphor ===

See [[Help:Editing#Links]] for the syntax of internal, interwiki and external links.

* Try to interlink your article with as many others as you can, using the words in the text.
* Only link to existing articles. If you encounter a dead link, try to fix it. External links that appear to be dead should be marked with [[Template:Dead link]].
* Avoid implicit links whenever possible, prefer instructions like "See the [[systemd]] article for more information", instead of "See [[systemd|here]] for more information".

A link can be used in two ways:

* As a '''topic reference''', where the link is a term, part of the running text, and subject to regular grammar rules; use a link label if needed. Internal/interwiki links should point to a [[#Redirect pages|redirect]] if available.
* As a '''page/section reference''', do not use a link label, and spell the title according to [[Template:Lowercase title]] where used; in particular, do not hide the {{ic|#}} symbol in same-page section links, e.g. {{ic|<nowiki>[[#Hypertext metaphor|Hypertext metaphor]]</nowiki>}}.

See these examples:

{| class="wikitable"
! Topic reference !! Page/section reference
|-
| Use an [[SSH agent]] to speed up authentication.
| Follow [[SSH keys#SSH agents]] to speed up authentication.
|-
| [[Font configuration#Subpixel rendering|Subpixel rendering]] is supported by most monitors.
| Enable subpixel rendering as described in [[Font configuration#Subpixel rendering]].
|-
| Include a [[Dm-crypt/Device encryption#Keyfiles|keyfile]] in the ''initramfs''.
| Instructions can be found in [[dm-crypt/Device encryption#Keyfiles]].
|-
| Be aware that [[Wikipedia:Mouse keys|mouse keys]] is disabled by default.
| See [[Wikipedia:Mouse keys]] for details.
|-
| We have [[#Hypertext metaphor|style rules]] for links.
| The [[#Hypertext metaphor]] section has style rules for links.
|}

* Before writing a specific procedure in an article or describing something in particular, always check if there is already an article that treats that part in detail; in that case, link that article instead of duplicating its content. Also:
**For technical terms not covered by an article in the ArchWiki, link to the relevant Wikipedia page.
**If the upstream documentation for the subject of your article is well-written and maintained, prefer just writing Arch-specific adaptations and linking to the official documentation for general information.
::For example: "[[Kernel parameters]] are used to issue [[Wikipedia:system call|system call]]s at boot; see the [https://docs.kernel.org/admin-guide/kernel-parameters.html Linux kernel documentation] for a complete list."
:In general, maintain coherence with [[Help:Reading#Organization]].
* Except in rare cases, you should not leave an article as a dead-end page (an article that does not link to any other), or an orphan page (an article that is not linked to from any other).
* Do not use interwiki links for links to localized pages of the same language of the article being edited, because they will not be shown in [[Special:WhatLinksHere]] pages; for example, using {{ic|<nowiki>[[:hu:Main page]]</nowiki>}} in a Hungarian article is wrong, while {{ic|<nowiki>[[Main page (Magyar)]]</nowiki>}} is correct. Using this kind of link between different languages is acceptable, because this would make it easier to move the articles to a separate wiki in case a separate wiki is created in the future. Finally, note the difference of these kinds of links from [[#Interlanguage links]], which do not have the colon at the beginning.
* Prefer the "Wikipedia:" interwiki prefix over the shorter "w:" prefix.

==== Man pages ====

* [[Man page]]s should be referenced using [[Template:man]].

=== Supported kernel versions ===

* Do not remove any notes or adaptations regarding kernel versions greater than or equal to the minimum version between the current {{Pkg|linux-lts}} package in the ''core'' repository, and the kernel on the latest [https://archlinux.org/download/ installation media].

=== Non-pertinent content ===

* Please do not sign articles, nor credit article authors: the ArchWiki is a work of the community, and the history of each article is enough for crediting its contributors. Note that reporting the sources used to write an article is good practice: you can use the "See also" section for this purpose.
* Uploading files is disabled for normal users, and including images in articles is not allowed. As an alternative you can include links to external images or galleries, and if you need to draw simple diagrams you may use an ASCII editor like [http://www.asciiflow.com/ Asciiflow] and [[Template:Text art]]; rationale:
** Maintenance: Arch is rolling release, and images would make updating articles much more difficult.
** Necessity: Arch does not develop nor maintain any sort of GUI application, so we do not need to display any screenshot.
** Moderation: free image upload would require time to be spent removing oversized or inappropriate images.
** Accessibility: we support users with slow connections, text-only browsers, screen readers and the like.
** Efficiency: images waste server bandwidth and storage space.
** Simplicity: text-only articles just look simpler and tidier.

=== Spelling ===

* Avoid contractions: "don't", "isn't", "you've", etc. should be "do not", "is not", and "you have", for example.
* Avoid unnecessary [[Wikipedia:Clipping (morphology)|shortening]] of words: for example, instead of "repo", "distro", and "config", prefer "repository", "distribution", and "configuration". In the same fashion, prefer using the long form of ''uncommon'' command options instead of their single-character counterpart. See also [[Help:Style/Formatting and punctuation#Configuration parameters, variables, options, properties...]].
* The names of projects, applications, executables etc. should be spelled, especially regarding capitalization, primarily according to their official documentation style. This includes the case where the documentation treats the name as a common noun, i.e. with an uppercase first letter when appearing at the beginning of a sentence, and lowercase otherwise. If the official documentation does not apply a consistent style, follow the style already used in the ArchWiki. If the name does not appear in the ArchWiki, or it still has inconsistent spelling, choose a style and conform to it throughout the article, also possibly updating the other pages that mention the name. Taking Git as an example you may choose to spell the name with the first letter uppercase ("Git") when talking about the project/software generally, and use all lowercase and italic ("''git''") when referring to the compiled program. When name capitalization can generate controversy, explicitly define a style in the article's talk page. See also [[Help:Style/Formatting and punctuation#Executable/application names]]
* ArchWiki prefers no national variety of English over any other, adopting the same guidelines outlined in [[Wikipedia:Wikipedia:Manual of Style#National varieties of English]]; in case of conflict with any of ArchWiki's other explicitly defined guidelines, ArchWiki's prevail. When writing new content within an existing article it is recommended to maintain the [[w:Wikipedia:Manual_of_Style/Spelling|spelling convention]] already prevalent in it; if the article does not have a clear prevalent spelling, write accordingly to the variant used in the edited section. Harmonizing the spelling around the edited content is acceptable; refrain from performing edits whose main purpose is changing or harmonizing the spelling standard of articles or series thereof.

=== Language register ===

* Articles should be written using formal, professional, and concise language. Care should be taken to remove grammar and orthography errors through edit previews and proofreading.
* Remember not only to answer ''how'', but also ''why''. Explanatory information always goes further toward imparting knowledge than does instruction alone.
* Do not omit terms that are necessary to give an exact, unambiguous meaning to a sentence; for example, always add the word "repository" when mentioning the name of a repository.
* Do not use indefinite time references such as "currently", "at the time of writing" or "soon"; replace them with definite expressions such as "as of May 2015" etc.
* Write objectively: do not include personal comments on articles; use discussion pages for this purpose. In general, do not write in first person.
* When editing content, be consistent with the style used in the rest of the article; for example, if the reader is always addressed using the second person, this style should be adopted by the added content; the same goes if third person or passive voice are clearly dominant throughout the article.
* When offering a choice among different options (pieces of software, methods to do something, etc.) do not explicitly recommend one over the others, but objectively describe the advantages and disadvantages of each, thus helping the reader to make the best decision for their personal case.
* Prefer neutral pronouns such as [[Wikipedia:Singular they|they/them]] when referring to the reader or people in general.

== Category pages ==

* [[Help:Category|Category]] name must use [[Wikipedia:Letter case#Sentence case|sentence case]].
* Every category must be appropriately categorized under at least one parent category, except for root categories, which are:
** [[:Category:Archive]],
** [[:Category:DeveloperWiki]],
** [[:Category:Languages]],
** [[:Category:Maintenance]], and
** [[:Category:Sandbox]].
* A category can be categorized under more than one category, provided one is not ancestor of the others.
* Avoid circular relationships: two categories cannot be reciprocal ancestors.
* Do not categorize a category under itself (self-categorized category).
* Categories must be included at the top of the category page.
* Categories should not redirect, except temporarily during [[Help:Procedures#Rename a category|renaming]].
* By default, category names should be in the singular form ("topic" categories, for example [[:Category:Simulation]]); they should be in the plural form if the singular form can be used to describe ''one'' of its members ("set" categories, for example [[:Category:Boot loaders]]).

== Redirect pages ==

* It is encouraged to create redirect pages for acronyms or grammatical variants of an existing article's title, or for a term or topic discussed in a subsection of a more generic article; for example [[ALSA]], [[daemon]] or [[AIGLX]]. Redirects can simplify the source text by replacing labelled links, compare the previous examples with {{ic|<nowiki>[[Advanced Linux Sound Architecture|ALSA]]</nowiki>}}, {{ic|<nowiki>[[daemons|daemon]]</nowiki>}} or {{ic|<nowiki>[[Xorg#Composite|AIGLX]]</nowiki>}}.
* Redirect pages should contain only the redirect code and nothing else; the only exceptions are:
** [[ArchWiki:Archive|Archived]] pages, which are in fact redirects; must be categorized under [[:Category:Archive]].
** [[Help:Procedures#Rename a category|Renamed categories]] can contain a [[Template:Archive]] flag.
* Redirect only to internal articles; do not use interwiki redirections.
:Redirects using interlanguage links are exceptionally allowed in accordance with [[Help:i18n]], and upon authorization from the [[ArchWiki:Maintenance Team]].
* See [[Help:Editing#Redirects]] for more information.

== User pages ==

* Pages in the [[Special:PrefixIndex/User:|User]] namespace cannot be categorized.
* Pages in the [[Special:PrefixIndex/User:|User]] namespace can only be linked from other pages in the ''User'' or ''talk'' namespaces, unless authorization to do otherwise is given by Administrators.
* Pages in the [[Special:PrefixIndex/User:|User]] namespace cannot be targets of [[Help:Editing#Redirects|redirects]] from other namespaces.

== Generic rules ==

=== Edit summary ===

See [[ArchWiki:Contributing#The 3 fundamental rules]].

=== HTML tags ===

* Usage of HTML tags is generally discouraged; always prefer using wiki markup or templates when possible (see [[Help:Editing]] and related).
* When tempted to use {{ic|<nowiki><pre>code</pre></nowiki>}}, always resort to {{ic|<nowiki>{{bc|code}}</nowiki>}}. When tempted to use {{ic|<nowiki><tt>text</tt></nowiki>}} or {{ic|<nowiki><code>text</code></nowiki>}}, always resort to {{ic|<nowiki>{{ic|text}}</nowiki>}}.
* Especially avoid HTML comments ({{ic|<nowiki></nowiki>}}): it is likely that a note added in a HTML comment can be explicitly shown in the article's discussion page. You can add an appropriate [[Help:Template#Status|status template]] in place of the comment.
* Use {{ic|<nowiki> </nowiki>}} only when necessary; to start a new paragraph or break a line, put a blank line below it.
: {{Tip|Common exceptions to this rule are when it is necessary to '''break a line in a list item''' and you cannot use a sub-item, or '''inside a template''' and you cannot use a list.}}

Dovecot

2026-05-18T07:33:51Z

Erus Iluvatar: /* Full Text Search */ rm dropped package

[[Category:Mail server]]
[[ja:Dovecot]]
{{Related articles start}}
{{Related|Mail server}}
{{Related|SOGo}}
{{Related|Virtual user mail system}}
{{Related articles end}}

{{Note|Dovecot is available in two lines: 2.4 and 2.3. This article is about the most recent release, but some parts may still refer to the older versions.}}

[https://www.dovecot.org/ Dovecot] is an open source [[Wikipedia:IMAP|IMAP]] and [[Wikipedia:POP3|POP3]] server for Linux/UNIX-like systems, written primarily with security in mind. Dovecot primarily aims to be a lightweight, fast and easy to set up open source mailserver. For more detailed information, please see the official [https://doc.dovecot.org Dovecot documentation].

This article describes how to set up Dovecot for personal or small office use.

Due to breaking changes in Dovecot's configuration format in version 2.4, Arch Linux offers both the latest release and one from the 2.3 line. The latter will not receive any new features or bug fixes, other than critical security updates.

== Installation ==

[[Install]] the {{Pkg|dovecot}} package for the most recent Dovecot version, or {{Pkg|dovecot23}} for the legacy 2.3 line.

== Configuration ==

{{Note|
* In Dovecot 2.4 the '''configuration syntax has changed considerably''' from 2.3 and earlier versions (breaking changes!). Configuration files from before 2.4 are no longer supported. If you are upgrading from a pre-2.4-version, you have to [https://doc.dovecot.org/2.4.1/installation/upgrade/2.3-to-2.4.html rewrite your configuration].

* Mind that the migration can become challenging. Do not approach it lightly. The migration guide is terse, as the rest of Dovecot's documentation. Take your time. Make yourself comfortable with the subject. Most likely, you will have to go through a process of trial and error. If possible set up a testing environment that you can play around with. In the mean time consider using {{Pkg|dovecot23}} for your production environment.}}

Dovecot configuration is stored in {{ic|/etc/dovecot/dovecot.conf}}.
An example file is shipped with the package. To use the example config a few manual steps are still necessary:
* A {{ic|vmail}} user and group needs to be created
* SSL certificate is necessary or needs to be created

See the official documentation [https://doc.dovecot.org/latest/core/config/quick.html#tldr-i-just-want-dovecot-running TLDR] and [https://doc.dovecot.org/latest/core/config/quick.html#ssl-and-plaintext-authentication SSL and Plaintext Authentication] for more information.

On top of that, the developers translated legacy examples to 2.4 syntax
and [https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-example-config.tar.gz offer them on GitHub].
The examples are provided in hope they are helpful, but the archive is not
expected to be kept up to date.

=== Required settings ===

{{ic|dovecot_config_version}} '''must''' be set and it has to be the first
setting in the configuration file. {{ic|dovecot_storage_version}} also has
to be set. The values of these settings should match actually used
configuration syntax, names, and formats of files created by Dovecot itself.

=== Authentication ===

User authentication is managed through the {{ic|passdb}} filters.

To enable PAM passdb driver:

{{bc|1=
passdb pam {
# Additional PAM-specific settings here, if needed.
}
}}

The associated PAM configuration is included in {{ic|/etc/pam.d/dovecot}}.

See [https://doc.dovecot.org/2.4.0/core/config/auth/passdb.html passdb documentation] for other drivers and the list of their settings.

=== TLS connections ===

To accept TLS connections, you need to obtain a certificate. This section
assumes you already own one, together with the private key. Both must be
in the PEM format.

First, generate parameters required for Diffie-Hellman key exchange:

$ openssl dhparam -out dhparams.pem 4096

This operation may take some time. The output goes to {{ic|dhparams.pem}}.

Finally, configure Dovecot to use all three files:

{{bc|1=
ssl_server {
cert_file = /path/to/fullchain.pem
key_file = /path/to/privkey.pem
dh_file = /path/to/dhparams.pem
}
}}

== Full Text Search ==

By default Dovecot does not index the full message content, which will result in slow response times for {{ic|IMAP SEARCH}} queries for bigger mailboxes. There are a number of [https://doc.dovecot.org/2.4.2/core/plugins/fts.html FTS backends] Dovecot can be hooked up to.

Dovecot needs a plugin for the chosen search backend. The {{Pkg|solr}} plugin is included in {{Pkg|dovecot}} but solr itself is not the easiest to set up. There is a package for [[Elasticsearch]] ({{Pkg|dovecot-fts-elastic}}).

== Starting the server ==

[[Start/enable]] {{ic|dovecot.service}}.

== Tips and tricks ==

Generate hashes with non-default hash functions:

$ doveadm pw -s SHA512-CRYPT -p "''password''"

Ensure that the column in the database is large enough. A warning will be emitted if it is too small.

Remember to set the password password scheme:

{{hc|dovecot-sql.conf|2=
default_pass_scheme = SHA512-CRYPT
}}

== Troubleshooting ==

=== warning: pipe flag `D' requires dovecot_destination_recipient_limit = 1 ===

If you cannot receive emails with multiple recipients and there is something like this is your logs:

mail postfix/pipe[663]: 72A62733: to=<user2@example.com>, relay=dovecot, delay=495, delays=495/0.01/0/0.08, dsn=4.3.5, status=deferred (mail system configuration error)
mail postfix/pipe[663]: 72A62733: to=<user1@example.com>, relay=dovecot, delay=495, delays=495/0.01/0/0.06, dsn=4.3.5, status=deferred (mail system configuration error)
mail postfix/pipe[1614231]: warning: pipe flag `D' requires dovecot_destination_recipient_limit = 1

Add {{ic|1=dovecot_destination_recipient_limit = 1}} to {{ic|/etc/postfix/main.cf}} and reload postfix.

=== dovecot.service does not start after updating to 2.4 ===

Dovecot 2.4 has introduced changes to the configuration files format and variable names. You need to translate your 2.3 configuration to make it compatible with 2.4. See [[#Configuration]] for more information.

As a temporary solution {{Pkg|dovecot23}} may be installed instead of {{Pkg|dovecot}}.

=== Dovecot and Postfix: cannot read SSL private key ===

If running dovecot 2.4 you encounter errors when running "any" dovecot executable as user, such as:

Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 80: cert_file: open(/etc/letsencrypt/live/server.tld/fullchain.pem) failed: Permission denied

This is a known issue, since "deliver" has to be able to read every configuration. But running {{ic|/usr/lib/dovecot/deliver}} as user is useful, with procmail for instance.

To avoid the problem, dovecot provides a silently failing "include_try" mechanism, that you can use to make file unreadable ''to user'' but still enabling root to read SSL keys.

1. Create {{ic|/etc/dovecot/dovecot-ssl.conf}} that contains the content of {{ic|<nowiki>ssl_server {...}</nowiki>}} (above defined), something like:

cert_file = /path/to/fullchain.pem
key_file = /path/to/privkey.pem
dh_file = /path/to/dhparams.pem

2. Prevent any user but "root" to read this file:

chmod 600 /etc/dovecot/dovecot-ssl.conf

3. Replace the ssl_server part of {{ic|dovecot.conf}} with this:

ssl_server {
!include_try /etc/dovecot/dovecot-ssl.conf
}

4. (to test) The {{ic|doveconf}} command should print your "certs_file" lines as root (with your private keys listed) and not be listed as unprivileged user.

Laptop/ASUS

2026-05-17T08:02:39Z

Erus Iluvatar: /* Republic of Gamers (ROG) */ rm mentions of ancient/removed g14 kernel

[[Category:ASUS]]
[[ja:ノートパソコン/Asus]]
{{Laptops navigation}}
{{Style| and instead of creating super long, messy entries there should be a dedicated page for the laptop. Many entries also need language improvements}}
See also [[Wikipedia:Asus]].

== ASUS Linux ==

Advanced power management (Laptop Power Profile selection, battery charge limit and Panel Overdrive) and many other functions from recent laptops need the [[ASUS Linux]] stack installed and running.

== Battery charge threshold ==

Kernel 5.4 brought the ability to set the battery charge threshold for some Asus laptops, by modifying the {{ic|charge_control_end_threshold}} variable exposed under {{ic|/sys/class/power_supply/BAT0/}}[https://github.com/torvalds/linux/commit/7973353e92ee1e7ca3b2eb361a4b7cb66c92abee][https://patchwork.kernel.org/project/platform-driver-x86/patch/20190813003023.6748-1-kristian@klausen.dk/].

By default this value is set to {{ic|100}} and reset on every power cycle[https://github.com/torvalds/linux/commit/7973353e92ee1e7ca3b2eb361a4b7cb66c92abee#diff-38095ba4871836b9eeaa6e1904739d398da72cda890e5ef932daec2995579db3R429-R434].

The effect of its change can be demonstrated as follows:

{{bc|
$ cat /sys/class/power_supply/BAT0/status
Charging
$ cat /sys/class/power_supply/BAT0/capacity
74
# echo 60 > /sys/class/power_supply/BAT0/charge_control_end_threshold
$ cat /sys/class/power_supply/BAT0/status
Not charging
}}

{{Note|As of 2020-12-11, the following battery device names are recognized: BAT0, BAT1, BATC and BATT.[https://github.com/torvalds/linux/blob/1797d588af15174d4a4e7159dac8c800538e4f8c/drivers/platform/x86/asus-wmi.c#L440-L448] Adjust accordingly or use the [[Wikipedia:Wildcard_character#File_and_directory_patterns|single character wildcard]] ({{ic|?}}), e.g. {{ic|BAT?}}.}}

=== Include required module in initramfs ===

To work around cases of configuration failing to apply at boot because the required {{ic|asus_wmi}} kernel module has not yet been loaded[https://github.com/linrunner/TLP/issues/602], configure [[Kernel module#Early module loading|early module loading]] for it.

=== TLP ===

[[TLP]] gained with [https://github.com/linrunner/TLP/releases/tag/1.4.0 version 1.4] the ability to set battery charge thresholds for laptops other than Thinkpads: see upstream [https://linrunner.de/tlp/settings/battery.html documentation] and [https://linrunner.de/tlp/settings/bc-vendors.html#asus config example].

=== bat ===

Another (more simple) way to force the charging threshold is by using {{AUR|bat-asus-battery-bin}}, which provides a {{ic|bat-boot.service}} {{pkg|systemd}} service and an intuitive terminal interface to change the threshold by typing {{ic|bat-asus-battery threshold ''value''}}.

=== GNOME extension ===

{{AUR|gnome-shell-extension-battery-health-charging-git}} is a [[GNOME#Extensions|GNOME extension]] that "''provides a graphical user interface for setting a laptop’s charging limit (charging threshold) within a Gnome environment''". It supports [https://maniacx.github.io/Battery-Health-Charging/device-compatibility/asus ASUS laptops] and many other brands. See its [https://maniacx.github.io/Battery-Health-Charging/ official website] for details and screenshots.

=== udev rule ===

The battery's {{ic|charge_control_end_threshold}} power supply class attribute does not initially exist. It is added to the {{man|5|sysfs}} directory by the {{ic|asus-nb-wmi}} [[kernel module]]. Create a [[udev rule]] for {{ic|asus-nb-wmi}} to set the battery's charge threshold:

{{hc|/etc/udev/rules.d/asus-battery-charge-threshold.rules|2=
ACTION=="add", KERNEL=="asus-nb-wmi", RUN+="/bin/bash -c 'echo ''value'' > /sys/class/power_supply/BAT?/charge_control_end_threshold'"
}}

=== Persist after hibernation ===

While this setting will persist after [[Power management/Suspend and hibernate|suspending to RAM]], it will be reset when resuming from hibernation. In order to re-execute the service after hibernation, use one of the methods described in [[Power management/Suspend and hibernate#Sleep hooks]].

If creating a script as described in [[Power management/Suspend and hibernate#Hooks in /usr/lib/systemd/system-sleep]], use something similar to:

{{hc|/usr/lib/systemd/system-sleep/battery-threshold.sh|
#!/bin/sh
case $1/$2 in
pre/*)
echo "Going to $2..."
;;
post/*)
echo "Waking up from $2..."
echo 60 > /sys/class/power_supply/BAT0/charge_control_end_threshold
;;
esac
}}

Do not forget to make the script [[executable]].

== Model list ==

{{Style|Generic info not specific to laptops should be removed and instead of creating super long, messy entries there should be a dedicated page for the laptop. Many entries also need language improvements}}

=== Vivobook ===

{{Laptops table header}}
| VivoBook 13 Slate OLED T3300 || 2022-08-11 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || Fingerprint enrolls but never matches. Cameras do not work. || Set the {{ic|1=debug_quirks=0x20000}} [[kernel module parameter]] for the {{ic|sdhci}} module in order to use eMMC.
|-
| VivoBook M513IA || 2021-09-12 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || See [[#Function key behavior]] ||
|-
| VivoBook F510UA || 2018-07-01 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || || UEFI secure boot key rejected, had to disable in BIOS.
|-
| VivoBook 14 X405UQ-BV240T || 2024-01-21 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || Secure boot is working. Microsoft platform keys can be deleted without any issue.
|-
| VivoBook 14 X442UA-GA139T || 2018-05-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || || UEFI secure boot does not pass, might need work.
|-
| VivoBook S301LA || 2016-09-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{ic|1=acpi_osi=}} needed for hotkeys and backlight control. For package power states lower than PC3, see Remarks. || || To reach PC7, {{AUR|r8168}} has to be built without certain build options. An easy way to do this is to build {{AUR|r8168-dkms}} after modifying its {{ic|dkms.conf}} by removing {{ic|1=EXTRA_CFLAGS='-DCONFIG_R8168_NAPI -DCONFIG_R8168_VLAN'}}
|-
| VivoBook X512DA || 2019-03-15 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || See [[#Function key behavior]] || Fan spins unusually fast when started plugged in.
|-
| [[ASUS X421IA|Vivobook S14 M433 (X421IA)]] || 2020-07-31 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{No}} || Fingerprint does not work. See [[#Function key behavior]] || See article for more details.
|-
| VivoBook X509DA_D509DA || 2021-06-21 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}}, with {{AUR|rtl8821ce-dkms-git}} || {{Yes}} || {{Yes}} || Sometimes the touchpad is not recognized, to fix run {{bc|1=# rmmod i2c-hid-acpi}} and {{bc|1=# modprobe i2c-hid-acpi}} || Needed an external Wi-Fi/Ethernet adapter (via USB) during archiso (for access to internet), screen brightness is set to lowest when you plug/unplug your power for the first time after boot (now fixed, i think by adding the {{ic|1=amdgpu}} module in {{ic|1=/etc/mkinitcpio.conf}})
|-
| VivoBook Pro 14 (M3400) || 2021-04-29 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || A few keys were strangely mapped (e.g. Screenshot key {{ic|Fn+F11}} mapped to {{ic|Super+S}}). || Recovering from DPMS brightness reset to default can be solved by replacing {{ic|1=acpi_video0}} with {{ic|1=amdgpu_bl0}}.
|-
| Vivobook X450LCP || 2019-11-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{Yes}} || Touchpad works better with deprecated {{Pkg|xf86-input-libinput}} driver || Apparently there is no way to control manually the fan. Every time the fan just stops spinning, needing suspending/reboot to fix.
|-
| [[ASUS M5402|Vivobook S 14X OLED (M5402)]] || 2023-01-06 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{No}} || No OLED safety features, e.g. pixel shift. ||
* Fingerprint reader is unreliable but does work.
* Battery life is significantly worse compared to when running Windows.
|-
| [[ASUS Vivobook X513EAN|Vivobook X513EAN]] || 2023-03-26 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{ic|acpi_osi{{=}}}} needed for hotkeys and backlight control. || Keyboard backlighting is handled by hardware and works normally, other function keys register when pressed but will require remapping to function
|-
| ASUS Vivobook 15X (M1503Q) || 2023-03-29 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| Vivobook M1502IA OLED || 2023-05-04 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{-}} || {{Yes}} || {{Yes}} || {{No}} || Mouse/Keyboard do not wake up after long suspend. System does not properly shutdown or reboot. || The majority of the trackpad is left-click. Middle and right-click are only at the bottom edge.
|-
| Vivobook 15 M1502Q || 2026-01-26 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || Fingerprint enrolls but never matches ||
|-
| Vivobook 15 M1502YA || 2025-03-22 || {{Yes}} || {{Yes}} || {{-}} || {{Y|Partial, with [https://github.com/hmtheboy154/gen4-mt7902 gen4-mt7902]}} || {{Y|Untested}} || {{Y|Untested}} || || Sound untested without [[Sound Open Firmware|sof-firmware]].
|-
| Vivobook GO 15 E1504FA || 2024-01-08 || {{Yes}} || {{Yes}} || {{-}} || {{No}} || {{No}} || {{Yes}} || Easiest method to control the monitor backlight is to use {{AUR|acpilight}} ||
|-
| Vivobook GO 15 E1504G || 2024-12-25 || {{Yes}} || {{Y|Untested}} || {{-}} || {{No}} || {{No}} || {{Y|Untested}} || The Wi-Fi and Bluetooth device is a MediaTek MT7902 which doesn't have drivers in the Linux kernel nor is supported by MediaTek on Linux||
|-
| Vivobook Pro 15 N6506MJ OLED || 2025-07-08 || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Yes}} || {{Yes}} || || Some [[wakeup triggers]] must be disabled to prevent the laptop from waking up immediately upon sleeping.
Use the {{ic|1=pcie_aspm=force}} and {{ic|1=pcie_aspm.policy=powersupersave}} [[Kernel module#Setting module options|kernel module parameters]] along with a [[Power management#Console|power management tool]] to match the battery life of this device when running Windows.
|-
| Vivobook S 16 M5606KA || 2025-12-17 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || Keyboard backlight is always white; only brightness is controllable. No color or pattern control. || Self panel refresh causes occasional typing latency and makes sudo prompts almost unusable due to lack of screen updates between keystrokes. Fixed with kernel parameter {{ic|1=amdgpu.dcdebugmask=0x10}}.
|-
| Vivobook Go 14 E410MA || 2026-01-15 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||Numberpad needs additional configuration to work.
|}
==== Function key behavior ====

The Function keys default behavior is {{ic|F1}}, {{ic|F2}}, etc… and must be unset by using {{ic|Fn+Esc}} to use alternative functions.

=== Gaming ===

{{Laptops table header}}
| GL552VM-DM-802D || 2017-02-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || || Needs {{ic|1=acpi_backlight=native}} to have {{ic|Fn}} keys backlight control, {{ic|1=idle=nomwait}} and {{ic|1=acpi_osi=! acpi_osi='Windows 2009'}} to boot.
|-
| G502VM-FY017T || 2017-02-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || The screen adjustment need a little workaround ||
|-
| FX502VM || 2017-02-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || Fn keys does not send ACPI events, except {{ic|F10}},{{ic|F11}},{{ic|F12}} (sound control) ||
|-
| FX504GD || 2019-05-30 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || For Fan Speed Control see [[Fan speed control#Alternative method using EC registers]]. For touchpad five finger touch of death apply patch [https://lore.kernel.org/lkml/20190430083753.18197-1-kai.heng.feng@canonical.com/ pinctl-intel.c patch] ||
|-
| FX505DY || 2020-12-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || See [[#Black screen after sleep]]
|-
| FX505DT || 2021-09-30 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || See [[#Battery charge threshold]]. Keyboard backlight settings can be controlled via {{AUR|tuf-manager}} || See [[#Black screen after sleep]]
|-
| G73SW || 2011-08-19 || {{Yes}} || {{Yes}} || {{Yes}}|| {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| G550JK || 2014-08-01 || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || || [https://xps13-9333.appspot.com/#background_noise fix background noises while using headphones]
|-
| FX 533VE || 2018-02-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || See [[#Nouveau prevents boot]].
|-
| FX 504GM || 2019-02-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || Did not manage to use the HDMI output (in fact, it is possible, but...), issue posted on the forum. See [[#Nouveau prevents boot]].
|-
| FX 504GE || 2019-06-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || See [[#Elan1200 touchpad]].
|-
| GL 503VD || 2019-02-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || See [[#Elan1200 touchpad]]. See [[#Nouveau prevents boot]].
|-
| FA506IV || 2022-02-02 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Keyboard backlight works but needs [https://github.com/Ann1kaB/faustus faustus] with {{Pkg|openrgb}} to change RGB. || Cannot change [[EFI boot stub]]s timeout with [[efibootmgr]].
|}

==== Republic of Gamers (ROG) ====

{{Laptops table header}}
| ROG G55VW || 2012-07-30 || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || ||
|-
| [[ASUS ROG GL702ZC|ROG Strix GL702ZC]] || 2017-04-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{Y|Untested}} || Backlight keys are amdgpu, not xbacklight. Fancontrol is ACPI, there are some amdgpu fan control stuff on aur/github. ||
|-
| ROG Zephyrus M || 2023-08-20 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|13-16W draw possible with Nvidia module configuration. Wayland on Intel and unloaded nvidia-drm}} || All of the Asus AUR control applications seem to work just fine for controlling keyboard backlight, fans (on/off/auto), and battery thresholds {{AUR|asusctl-git}} {{AUR|rog-control-center}} {{AUR|rogauracore-git}} || The battery is the big disadvantage. On Windows it can last for up to 6h, however. This laptop is definitely not Linux friendly
|-
| ROG Zephyrus M16 GU603Z || 2023-03-08 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|Bad battery life: cannot power down NVIDIA GPU}} || All of the Asus AUR control applications seem to work just fine for controlling keyboard backlight, fans, and battery thresholds {{AUR|asusctl-git}} {{AUR|rog-control-center}} {{AUR|rogauracore-git}} || I did not expect the battery life to be great on this laptop, but otherwise it works fine with linux, i.e. gaming is fantastic and the 20 core CPU seems to work great.
|-
| [[ASUS ROG GA401I|ROG Zephyrus G14 (GA401I)]] || 2021-05-12 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || Some function keys and AniMe LED matrix work with kernel patches and {{AUR|asusctl-git}}. ||
|-
| ROG Zephyrus G15 (GA502IU)|| 2020-07-08 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Some custom keys do not work. Can control only one fan with {{ic|asus_nb_wmi}} module. ||
|-
| ROG Zephyrus S15 (GX502LWS) || 2020-20-25 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Sleep: Untested}} || Keyboard colors work using {{AUR|rogauracore-git}} ||
|-
| ROG Flow X13 (GV301Q'''E''') || 2021-07-01 || rowspan="3" {{Yes}} || rowspan="3" {{Yes}} || rowspan="3" {{-}} || rowspan="3" {{Yes}} || rowspan="3" {{Yes}} || rowspan="2" {{Y|Untested}} || Accelerometer sensor is not detected (waiting for asus-wmi fix?). Lid-backflip sensor works with {{AUR|linux-flowx13}} || rowspan="2" | Tablet integration is manual, because the lid-backflip sensor is missing.
|-
| ROG Flow X13 (GV301Q'''H''') || 2021-10-09 || Lid-backflip is ''not'' detected. Fingerprint sensor is detected when libfprint is fully upgraded, however it always fails to verify.
|-
| ROG Flow X13 (GV301R'''A''') || 2024-10-13 || {{Yes}} || Accelerometer works, Fingerprint sensor works but verification fails pretty often. ||
|-
| ROG Zephyrus GU501GM || 2021-11-24 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{No}} || Fan curves cannot be changed though overboost modes work. RGB works with {{AUR|rogauracore-git}} and all keys work except the mute microphone button || HDMI output is hardwired to the NVIDIA GPU.
|-
| ROG Zephyrus S GX531GS || 2024-04-29 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || Fan curves cannot be changed though overboost modes work. RGB works with {{AUR|rogauracore-git}} and all keys work || HDMI output is hardwired to the NVIDIA GPU.
|-
| [https://linux-hardware.org/?computer=9864b4c43688 ROG Strix G15 G513QY Advantage Edition] || 2022-01-16 || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Partial: No AP (HotSpot) mode}} || {{Yes}} || {{Yes}} || Flashing lights during sleep could be disabled with {{AUR|asusctl}}. Support for custom fan curves should land in kernel 5.17 ||
|-
| [[ASUS ROG G533QS|ROG Strix Scar G15 G533QS]] || 2022-02-19 || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Partial: No AP (HotSpot) mode}} || {{Yes}} || {{Yes}} || ||
|-
| ROG Strix G15 G513 (G513QR) || 2022-02-21 || {{Yes}} || {{Yes}}* || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Sometimes the Wi-Fi card is not recognized after rebooting. The keys for changing profile and muting the mic require workaround (see fix for [https://asus-linux.org/faq/#fn-f5-doesn-t-do-anything profile] and [https://asus-linux.org/faq/#mic-mute-doesn-t-work mic-mute]. || *Very noisy (almost useless) internal mic. Headset mic requires [[hdajackretask]]: select Realtek ALC825 and override pin {{ic|0x19}} with "Microphone".
|-
| [[ASUS ROG STRIX G732LXS|ROG STRIX G732LXS]] || 2022-11-12 || {{Yes}} || {{G|[[ASUS ROG STRIX G732LXS#Audio|Yes]]}}* || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || supergfxd works perfectly with balanced settings. Optimus needs NVIDIA only ||
|-
| ROG Zephyrus M16 2023 (GU604V) || 2023-04-26 || {{Yes}} || {{G|[[ASUS Linux#Custom kernel|Yes]]}}* || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || There is no support for Advanced Optimus as of now. || Tested with secure boot and fast boot disabled.
|-
| [[ASUS ROG STRIX G17 (2022)|ROG STRIX G17 (G713RW)]] || 2023-07-03 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || [[ASUS ROG STRIX G17 (2022)#Recording|Awful microphone]] and also [[ASUS ROG STRIX G17 (2022)#Wi-Fi and Bluetooth|minor Wi-Fi Problems]] || [[ASUS Linux]] works great. RGB control supported.
|-
| ROG STRIX G17 (G713PU) || 2026-05-08 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || Works great. [[ASUS Linux]] & [[PRIME]] make it better.
|-
| ROG Zephyrus G14 2023 (G402NV) || 2023-07-16 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{No}} ||
|| In case of suspend-to-ram issue, downgrade UEFI to v310 (see [https://rog.asus.com/laptops/rog-zephyrus/rog-zephyrus-g14-2023-series/helpdesk_bios/ here])
|-
| ROG Zephyrus G14 2023 (G402XV) || 2023-10-24 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} ||
{{AUR|rog-control-center}} works great.
||
* In case of suspend-to-ram issue, downgrade UEFI to v310 (see [https://rog.asus.com/laptops/rog-zephyrus/rog-zephyrus-g14-2023-series/helpdesk_bios/ here])
* Screen flickering issues may occur with certain resolutions and refresh rates in some Linux kernel versions.
|-
| ROG Flow X16 2023 (GV601VI) || 2024-01-24 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} ||
* {{AUR|rog-control-center}} works great, you can toggle the MiniLED mode of the display too
* [[Tablet PC#Automatic rotation]] works
||
|-
| ROG Strix G16 2023 (G614JI) || 2024-05-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 |
* nvidia driver version 550.78+ is required for suspend to work
* Set {{ic|1=acpi_backlight=native}} for proper display brightness control on dGPU
|-
| ROG Zephyrus G14 2024 (GA403UV) || 2024-06-17 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | {{pkg|nvidia-open}} avoids crashes with the standard driver.
|-
| ROG Zephyrus G16 2024 (GU605M'''I''') || 2024-09-01 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || || For OLED screen brightness, see [[Backlight#Color correction]].
|-
| ROG Zephyrus G16 2024 (GU605M'''Z''') || 2025-06-23 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || need kernel parameters {{ic|1=i915.enable_dpcd_backlight=1 acpi_backlight=native}} for screen backlight control in hybrid GPU mode ||
|-
| ROG Zephyrus G14 2025 (GA403WW) || 2025-05-26 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|}

==== The Ultimate Force (TUF) ====

{{Laptops table header}}
| [[ASUS TUF DASH F15 (2022)|TUF Dash F15 (FX517ZC/ZR/ZM/ZE)]] || 2022-07-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Keyboard effects not controllable. Most function keys work, Aura and airplane mode keys do not. || Hybrid GPU switching works perfectly using [[asusctl]].
|-
| TUF Gaming F15 (FA507RC/RE/RM/RR/RW) || 2022-12-17 || {{Yes}} || {{Yes}} || {{Y|Partial: {{ic|r8169}} causes crashes. Needs {{AUR|r8168}} or {{AUR|r8168-dkms}} installed and {{ic|r8169}} kernel module blacklisted. }} || {{Yes}} || {{Yes}} || {{Yes}} || Keyboard RGB controllable with kernel above 6.1. All function keys work. || Needs {{ic|asus_ec_sensors}} kernel module blacklisted.
|-
| TUF Gaming A15 (FA506NC/IC/IE/IHR/QR/) || 2021-03-15 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 |
* Monitor brightness control requires the following kernel parameters: {{bc|<nowiki>acpi_osi=! idle=nomwait acpi_backlight=native</nowiki>}}
* Keyboard rgb control requires [[asusctl]] (only static effect available)
|-
| TUF Gaming A16 (FA617XS/NS/NSR/XT/NT) || 2025-03-06 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
* Suspend-to-RAM is [https://gitlab.freedesktop.org/drm/amd/-/issues/3212 broken] in BIOS versions 311-313. The issue is [https://gitlab.freedesktop.org/drm/amd/-/issues/3212#note_2719042 addressed] in BIOS version 316 and later.
* For Steam gaming start games with {{ic|1=DRI_PRIME=1}}, for gaming and desktop graphic glitch issues see [[AMDGPU#Tear free rendering]]
* If you experience green artifacts on eDP display, disable Panel self refresh v1 with the following kernel parameter {{ic|1=amdgpu.dcdebugmask=0x10}}
|-
| TUF Gaming F15 (FX506HC-HN111W) || 2024-01-21 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || [[asusctl]] recommended for keyboard RGB control and hybrid GPU switching
|-
| TUF Gaming A15 (FA507UV) || 2024-10-07 || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || || Upgrading BIOS from 307 to 309 causes losing control over keyboard's LED, fan speed and charge threshold
|}

==== Black screen after sleep ====

Add {{ic|1=amd_iommu=off idle=nomwait amdgpu.gpu_recovery=1}} to your [[kernel command line]].

==== Laptop not resuming (NVIDIA GPU with no iGPU) ====

{{Accuracy|Laptops without integrated GPUs are rare enough that this is probably model-specific and should be put on a dedicated page.}}

{{Style|Usage of ''sudo'', ''systemctl'', should use the [[kernel module]], [[regenerate the initramfs]] and [[reboot]] redirects.}}

Some laptops with only an NVIDIA GPU and no integrated GPU may fail to resume properly from suspend, especially when the system only supports {{ic|s2idle}}. To fix that enable S0ix support on NVIDIA Proprietary driver

===== Enable S0ix support (NVIDIA proprietary driver) =====
You can check if S0ix is currently enabled for the NVIDIA GPU by running:
{{bc|cat /proc/driver/nvidia/gpus/0000:01:00.0/power}}

Look for this section:

{{bc|S0ix Power Management:}}

If it shows:

{{bc|Status: Disabled}}

Then S0ix is not currently active.

To enable S0ix support, ensure you're using NVIDIA driver version 515 or newer. Then, configure the kernel module option:

Create a modprobe configuration file:

{{hc|/etc/modprobe.d/nvidia-power.conf|2=
options nvidia NVreg_EnableS0ixPowerManagement=1
}}

Rebuild the initramfs:

{{bc|sudo mkinitcpio -P}}

Then reboot:

{{bc|sudo reboot}}

After rebooting, re-check:

{{bc|cat /proc/driver/nvidia/gpus/0000:01:00.0/power}}

Confirm that the line now reads:

{{bc|Status: Enabled}}

This indicates that S0ix is now active.

Additionally, enable NVIDIA suspend/resume services:

{{bc|sudo systemctl enable nvidia-suspend.service nvidia-resume.service nvidia-hibernate.service}}

These services help properly transition the GPU into and out of low-power states during suspend/resume.

==== Nouveau prevents boot ====

Boot with nouveau disabled: use {{ic|1=nouveau.modset=0}} on the [[kernel command line]].
Need to edit bumblebee service to boot : https://github.com/Bumblebee-Project/Bumblebee/issues/764#issuecomment-450749984.

==== Elan1200 touchpad ====

Some fixes are needed: see https://bugzilla.redhat.com/show_bug.cgi?id=1543769.

=== ZenBook ===

{{Laptops table header}}
| [[ASUS Zenbook UX305|UX305FA]] || 2016-10-01 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || Function keys for brightness ({{ic|F5}}/{{ic|F6}}) do not send ACPI events ||
|-
| [[ASUS Zenbook UX303|UX303LN]] || 2014-10-01 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || Touchpad misses gestures, Touchscreen misses multi-touch support || Avoid some power management features due to Kernel Bug 102091.
|-
| UX32A || 2014-03-14 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || || See [[ASUS Zenbook Prime UX31A#Keyboard backlight]]
|-
| UX32L(N) || 2015-08-29 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || Set the kernel parameters {{ic|1=video.use_native_backlight=1 acpi_osi=}} for working backlight keys and backlight restore. || Avoid activating some power management features due to Kernel Bug 102091.
|-
| UX325EA || 2025-03-22 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested:IR Camera}} || Button to enable/disable camera, MyASUS, not working. Numpad works with relevant [https://github.com/asus-linux-drivers/asus-numberpad-driver driver].
|-
| UX331UA || 2018-09-05 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested:Fingerprint reader}} ||
|-
| UX3404VA || 2024-04-08 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| UX3405MA || 2024-05-17 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| UX480 || 2019-10-23 || {{Yes}} || {{-}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[ASUS Zenbook UX430UA|UX430UA]] || 2017-06-01 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || rowspan="3" | PWM Fan control is not available || rowspan="3" | See dedicated page.
|-
| [[ASUS Zenbook UX390|UX390UA]] || 2018-05-01 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}}
|-
| [[ASUS Zenbook UX534|UX534FTC]] || 2020-04-09 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}}
|-
| [[ASUS Zenbook UM425|UM425]] || 2021-02-01 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}}
|-
| [[ASUS Zenbook UM3402YA|UM3402YA]] || 2022-09-28 || {{Yes}} || {{Y|Partial*}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || Fancontroll, fingerprint sensor not working; "deep sleep"/suspend to ram draining power || *[[ASUS Zenbook UM3402YA|internal speakers]] not working
|-
| UX3402ZA || 2023-01-31 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || Fingerprint works but [[fprint#Enrolling works but verifying does not|might require some patience when swiping]] ||
|-
| UX5401ZA || 2023-02-24 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| UX363EA || 2023-07-22 || {{Yes}} || {{Yes}}* || {{-}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || *Audio might require disabling fast boot in UEFI if dual booting and [https://forums.linuxmint.com/viewtopic.php?t=91453 tweaking ALSA volume control] || Pipewire + wireplumber confirmed to work on audio/video playback
|-
| UX5304 || 2023-04-21 || {{Yes}} || {{Yes}}* || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || *Audio might require disabling fast boot in UEFI if dual booting and [https://forums.linuxmint.com/viewtopic.php?t=91453 tweaking ALSA volume control] || Internal Speakers do not work
|-
| UX8402Z || 2023-11-10 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{G|Untested: Hibernation}} || ||
|-
| UX6404VV || 2024-01-15 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[ASUS Zenbook UM5606|UM5606]] || 2024-09-09 || {{Yes}} || {{Yes}}* || {{-}} || {{Yes}} || {{Yes}}* || {{Yes}}* || *Most issues can be resolved by reading the [[ASUS Zenbook UM5606]] page and installing {{AUR|linux-mainline}} & {{Pkg|linux-firmware}}
||
|-
| UX5406(SA) || 2025-04-17 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{-}} || {{Yes}} || {{Yes}} || {{G|Hibernate: Untested}} || ||
|-
| UX582 HS i9 11900H || 2025-06-30 || {{Yes}} || {{No}} || {{-}} || {{Yes}} || {{Yes}} || {{G|Hibernate: Untested}} || Do not use "Better Blur" in KDE Plasma. With it, the system will be very slow while playing youtube 4k videos.
Regular "Blur" works fine.
||
No sound on the internal speakers or the headphones jack.

Sound works on displays over HDMI or USB-C, and on bluetooth headphones.
|-
| UM3406KA || 2025-09-21 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}}* || {{Yes}} || {{Yes}} || Face login works well with [[Howdy]] || Ensure that {{pkg|broadcom-wl}} or {{pkg|broadcom-wl-dkms}} are installed, otherwise Wi-Fi will not work (even though the chip is not Broadcom)
|}

=== ExpertBook ===

{{Laptops table header}}
| B9450 || 2020-04-20 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[ASUS ExpertBook B9450CEA|B9450CEA]] || 2021-03-14 || {{Yes}} || {{G|[[Sound Open Firmware|Yes]]}}* || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| BR1100FKA || 2021-05-28 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Primary webcam works, keyboard webcam does not work. Stylus does not fully work.}} || Set the {{ic|1=debug_quirks=0x20000}} [[kernel module parameter]] for the {{ic|sdhci}} module in order to use eMMC.
|}

=== Eee PC ===

{{Laptops table header}}
|-
| [[ASUS Eee PC T101MT|T101MT]] || 2010-08-14 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Partial}} || ||
|-
| 1001P || 2011-09-04 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || ||
|-
| 1001PXD || 2025-04-10 || {{Yes}} || {{Yes}}* || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{ic|1=acpi_osi=}} needed for hotkeys and {{ic|1=eeepc_laptop}} module related features (like SHE). || *Add {{ic|1=snd-hda-intel model=lifebook}} to {{ic|1=/etc/modprobe.d/alsa-base.conf}}
|-
| 1005P || 2013-04-22 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || ||
|-
| 1015 series || 2014-05-19 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Y|USB3: Untested}} ||
|-
| F201E || 2015-09-19 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{-}} || {{Y|Untested}} || ||
|-
| 1201 series || 2017-11-11 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || ||
|-
| 1215 series || 2017-12-08 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || || Might need {{ic|1=acpi_osi=""}}
|}

=== Other ===

{{Laptops table header}}
| W7S || 2007-08-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| F5R || 2008-01-16 || {{Yes}} || {{Yes}} || {{Yes}} || {{G|[[Broadcom wireless|Yes]]}} || {{Yes}} || {{Y|Untested}} || colspan=2 | ACPI works with acpi4asus and acpid
|-
| G1 || 2008-11-23 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} ||
|-
| M51SN || 2008-12-17 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || colspan=2 | Add {{ic|1=snd-hda-intel model=lenovo}} to {{ic|/etc/modprobe.d/modprobe.conf}}
|-
| A7SN || 2008-12-31 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} ||
|-
| N80Vn-X5 || 2009-02 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || colspan=2 | Add {{ic|1=options snd-hda-intel enable=1 model=g50v position_fix=0}} to {{ic|/etc/modprobe.d/modprobe.conf}}
|-
| F8SN || 2009-08 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{-}} || {{G|Hibernate: untested}} || {{Y|Untested: Modem, Card reader, TV out}} ||
|-
| A6km || 2009-08-10 || {{Yes}} || {{Yes}} || {{Yes}} || {{G|[[Broadcom wireless|Yes]]}} || {{Y|Untested}} || {{Y|Hibernate:Untested}} || ||
|-
| L3000D || 2010-02-13 || {{Yes}} || {{Yes}} || {{Yes}} || {{-}} || {{-}} || {{Yes}} || ||
|-
| N53JN || 2010-11-03 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{G|Hibernate: Untested}} || colspan=2 | suspend works but with problems due to USB3 controller
|-
| N53SV || 2011-06-26 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes|1=https://bbs.archlinux.org/viewtopic.php?pid=910195}} || colspan=2 | See also [https://help.ubuntu.com/community/Asus_N53 Ubuntu help]
|-
| N82JV || 2011-11-20 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| N56 series || 2014-06-30 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || {{Y|Untested: Card reader}} ||
|-
| A8Le || 2011-07-31 || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || {{Y|Untested}} || ||
|-
| UL30A || 2015-07-03 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Hibernate untested}} || {{Y|Card reader: Untested}} || Needs {{ic|1=acpi_backlight=vendor}}. Use {{ic|processor.nocst}} if crashing on boot.
|-
| A53T || 2012-07-21 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || ||
|-
| U31SD || 2012-12-30 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| K55VM || 2013-04-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || ||
|-
| A55VJ || 2013-05-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | Use {{ic|1=i8042.nomux=1}} to prevent jittery touchpad.
|-
| X401A/X401A1 || 2013-05-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || brightness control needs {{ic|asus-nb-wmi}} and {{ic|1=acpi_backlight=intel acpi_osi=}} || ||
|-
| X502CA || 2013-07-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || || Poor Wi-Fi performance
|-
| S300CA || 2013-08-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Y|Untested: USB3 Card reader}} || Use {{ic|1=acpi_osi=Linux acpi_backlight=vendor}}
|-
| Q400A || 2013-10-17 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Hibernate: Untested}} || {{Y|HDMI output: Untested}} ||
|-
| X401U || 2014-01-05 || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{-}} || {{Yes}} || ||
|-
| K55N || 2014-11-12 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{-}} || Overheats and immediately shuts down on modern 3D games. Use thermald to control temp using acpi_cpufreq || colspan=2 | Fix fn brightness keys with {{ic|1=acpi_osi="!Windows 2012" video.use_native_backlight=1}}. Do not enable early radeon hook to prevent blank screen after hibernation. Fix blank screen on suspend to ram with {{ic|1=sysctl -w kernel.acpi_video_flags=3}}.
|-
| X53BR/K53BR || 2014-03-30 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || || heats up very fast
|-
| X551CA || 2014-03-24 || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || colspan=2 | Disabling Wi-Fi blocks the card, {{ic|Fn+F2}} does not work. Workaround on [https://ubuntuforums.org/showthread.php?t=2181558 Ubuntu forum.]
|-
| [[N550JV]] || 2014-03-01 || {{Yes}} || {{Yes}}* || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}}** || colspan=2 | *external speakers pop on sleep/shutdown **battery issues when a powered device is left plugged into the USB charging port.
|-
| X83VB-X2 || 2014-09-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || {{Y|Camera: Untested}} ||
|-
| Q500A || 2015-02-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || ||
|-
| S400CA || 2015-02-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Y|Untested: USB3}} || Use {{ic|1=acpi_osi=Linux acpi_backlight=vendor}}
|-
| U32U || 2015-02-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}|| {{Yes}} || {{Y|Partial}} || Needs significant setup. Power management hard to get right. CPU Fan constantly on. || For [[rfkill]] issues {{ic|1=options asus_nb_wmi wapf=1}} may help
|-
| X555L || 2016-05-19 || {{Yes}} || {{Yes}} || {{Yes}} || {{G|[[Broadcom wireless#b43|Yes]]}} || {{No}} || {{Y|Untested}} || colspan=2 | Set {{ic|1=acpi_osi=}} for proper display brightness control
|-
| X551MA(V) || 2017-01-31 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | Set {{ic|1=acpi_osi= acpi_backlight=native}} for proper display brightness control
|-
| X553MA || 2015-06-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{Yes}} || colspan=2 | Set {{ic|OS Selection}} in BIOS setup to {{ic|Windows 7}} [[Broadcom wireless#broadcom-wl|broadcom-wl]] (causes freezes)
|-
| F550J (aka A550J) || 2015-09-01 || {{Y|Partial}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || {{Pkg|xf86-input-synaptics}} recommended for touchpad || Consider disabling standalone graphics card
|-
| N550JX || 2015-12-28 || {{Yes}} || {{Yes}}* || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || *external speakers needs {{AUR|asus-n550jx-subwoofer-fix}} Add [[kernel parameter]] {{ic|1=acpi_osi=}} to fix {{ic|Fn}} keys
|-
| X552M || 2015-12-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || Use {{ic|1=acpi_osi= acpi_backlight=native}} for changing backlight with {{ic|Fn+F5}}/{{ic|Fn+F6}} || [[Broadcom wireless#broadcom-wl|broadcom-wl]] (causes freezes)
|-
| E403SA || 2017-10-29 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Y|Untested: Card reader}} ||
|-
| F555UA || 2016-08-14 || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{No}} || {{Yes}} || No two finger scroll, very buggy touchpad || Add {{ic|1=options snd-hda-intel model=laptop-dmic position_fix=3 ac97_quirck=alc_jack}} to {{ic|/etc/modprobe.d/alsa-base.conf}} to get mic and headphone/mic to work
|-
| K501J || 2016-09-01 || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{-}} || {{Yes}} || colspan=2 | Touchpad works with {{Pkg|xf86-input-libinput}}, but somewhat uncomfortable. Better with {{Pkg|xf86-input-synaptics}} even if deprecated.
|-
| K501LX || 2017-01-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|Keyboard backlight controls}} || Added {{ic|1=pcie_port_pm=off}} to kernel parameters to make {{Pkg|bbswitch}} work correctly.
|-
| R540SA || 2017-03-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| N551VW || 2017-06-01 || {{Yes}} || {{Yes}}* || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || colspan=2 | *Through [[hdajackretask]] select ''Realtek ALC668'', check ''Show unconnected pins'' then check ''Override'' on ''Pin ID: 0x1a'' and ''Internal speaker (LFE)'', then apply and install the boot override.
|-
| N551ZU || 2022-10-20 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || || AMD Enduro supported via [[PRIME]]
|-
| N76V || 2019-01-05 || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || ||
|-
| X451MA || 2021-02-12 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || || Install {{Pkg|broadcom-wl-dkms}}
|-
| [[ASUS K55VD|K55VD]] || 2024-04-19 || {{Y|Partial*}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} ||
|-
| B9440UA || 2024-01-13 || {{Yes}} || {{Y|Partial*}} || {{-}} || {{Yes}} || {{Y|Untested}} || {{G|Untested: Hibernation}} || {{Y|Untested: Fingerprint Scanner}} || * Headphone Jack outputs very silent audio requiring output volume to be set to 153% to be audible which then produces distortion.
|}

ASUS ROG STRIX G732LXS

2026-05-17T08:02:06Z

Erus Iluvatar: /* Video */ rm sentence about ancient kernel versions

[[Category:ASUS]]
{{Laptop style|Missing IDs in the hardware table, an accessibility and function keys section.}}
{| class="wikitable archwiki-table-laptop"
|-
! Hardware !! PCI/USB ID !! Working?
|-
| GPU (NVIDIA) || || {{Yes}}
|-
| Wireless || || {{Yes}}
|-
| Ethernet || || {{Yes}}
|-
| [[#Audio|Audio]] || || {{Yes}}
|-
| Touchpad || || {{Yes}}
|-
| Bluetooth || || {{Yes}}
|}

== Audio ==

=== Speakers not working/quiet ===
You need to create:

{{hc|/etc/modprobe.d/alsa-base.conf|2=
snd_hda_intel: model=1043:1982,1043:1982
}}

You can check

{{bc|alsa-info.sh --no-upload}}

to see which card is normally added to PCH and which to NVidia. You can see it after the ''Soundcards recognised by ALSA'' section Both are using snd_hda_nvidia and you normally can only apply the model to that and you want to apply to PCH. So if that comes after Nvidia you can only use

{{bc|snd_hda_intel: model{{=}},1043:1982}}

And you are good to go. Or

{{bc|snd_hda_intel: model{{=}}1043:1982}}

if PCH is the first one.

== Video ==

Works with envycontrol or optimus it seems to have better performance with only using NVIDIA and not hybrid.

Using supergfxctl and an external monitor created a very laggy experience when the laptop screen was turned off. Also for some reason optimus does not always start with the latest kernel. At this point I would suggest using envycontrol if you would like to use nvidia only.

See https://asus-linux.org/

Font configuration

2026-05-16T09:47:03Z

Erus Iluvatar: /* Subpixel rendering */ Shorten even more: no need to detail the build options since we link to the commit + no need to keep 6 year old changes with a "since"

[[Category:Fonts]]
[[de:Schönere Schrift auf TFT/LCD Bildschirmen]]
[[es:Font configuration]]
[[hu:Font configuration]]
[[ja:フォント設定]]
[[ru:Font configuration]]
[[zh-hans:Font configuration]]
{{Related articles start}}
{{Related|Font configuration/Chinese}}
{{Related|Fonts}}
{{Related|Java Runtime Environment fonts}}
{{Related|Metric-compatible fonts}}
{{Related|Microsoft fonts}}
{{Related articles end}}

[[Wikipedia:Fontconfig|Fontconfig]] is a library designed to provide a list of available [[fonts]] to applications, as well as configuration for how fonts get rendered.

The [[Wikipedia:FreeType|FreeType]] library renders fonts based on this configuration. The {{Pkg|freetype2}} font rendering package includes the bytecode interpreter (BCI) enabled for better font rendering, especially with an LCD monitor. See [[#Fontconfig configuration]] and [[Font configuration/Examples]].

Although [https://www.freedesktop.org/wiki/Software/fontconfig/ Fontconfig] is used often in modern Unix and Unix-like operating systems, some applications rely on the original method of font selection and display, the [[X Logical Font Description]] (XLFD).

== Font paths ==

For fonts to be known to applications, they must be cataloged for easy and quick access.

The font paths known to Fontconfig by default are: {{ic|/usr/share/fonts/}}, {{ic|~/.local/share/fonts}} (and {{ic|~/.fonts/}}, now deprecated). Fontconfig will scan these directories recursively. For ease of organization and installation, it is recommended to use these font paths when [[adding fonts]].

To see a list of known Fontconfig fonts:

$ fc-list ':' file

See {{man|1|fc-list}} for more output formats.

Check for [[Xorg]] known font paths by reviewing its log:

$ grep /fonts ~/.local/share/xorg/Xorg.0.log

{{Tip|
* You can also check the list of [[Xorg]] known font paths using the command {{ic|xset q}}.
* Use {{ic|/var/log/Xorg.0.log}} if Xorg is run with root privileges.
}}

Keep in mind that Xorg does not search recursively through the {{ic|/usr/share/fonts/}} directory like Fontconfig does. To add a path, the full path must be used:

Section "Files"
FontPath "/usr/share/fonts/local/"
EndSection

For more details about Xorg configuration read [[Xorg#Configuration]]. If you want font paths to be set on a per-user basis, you can add and remove font paths from the default by adding the following line(s) to {{ic|~/.xinitrc}}:

xset +fp /usr/share/fonts/local/ # Prepend a custom font path to Xorg list of known font paths
xset -fp /usr/share/fonts/sucky_fonts/ # Remove the specified font path from Xorg list of known font paths

To see a list of fonts known by Xorg use {{ic|xlsfonts}}, from the {{Pkg|xorg-xlsfonts}} package.

== Fontconfig configuration ==

Fontconfig configuration is documented in the {{man|5|fonts-conf}} man page.

Configuration can be done per-user through {{ic|$XDG_CONFIG_HOME/fontconfig/fonts.conf}} (usually {{ic|$HOME/.config/fontconfig/fonts.conf}}), and globally with {{ic|/etc/fonts/local.conf}}. The settings in the per-user configuration have precedence over the global configuration. Both these files use the same syntax.

{{Note|
* The {{ic|50-user.conf}} preset needs to be enabled to make the user configuration take effect, and the {{ic|51-local.conf}} preset is for the global configuration. Check the [[#Presets]] section to know how to enable these presets.
* Configuration files and directories: {{ic|~/.fonts.conf/}}, {{ic|~/.fonts.conf.d/}} and {{ic|~/.fontconfig/*.cache-*}} are deprecated and will not be read by default in the future versions of the package. New paths are {{ic|$XDG_CONFIG_HOME/fontconfig/fonts.conf}}, {{ic|$XDG_CONFIG_HOME/fontconfig/conf.d/NN-name.conf}} and {{ic|$XDG_CACHE_HOME/fontconfig/*.cache-*}} respectively. If using the second location, make sure the naming is valid (where {{ic|NN}} is a two digit number like {{ic|00}}, {{ic|10}}, or {{ic|99}}).
}}

Fontconfig gathers all its configurations in a central file ({{ic|/etc/fonts/fonts.conf}}). This file is replaced during Fontconfig updates and should not be edited. Fontconfig-aware applications source this file to know available fonts and how they get rendered; simply restarting such applications is sufficient to load the new configuration. This file is a conglomeration of rules from the global configuration ({{ic|/etc/fonts/local.conf}}), the configured presets in {{ic|/etc/fonts/conf.d/}}, and the user configuration file ({{ic|$XDG_CONFIG_HOME/fontconfig/fonts.conf}}). {{ic|fc-cache}} can be used to rebuild Fontconfig configuration, although changes will only be visible in newly launched applications.

{{Note|For some desktop environments (such as [[GNOME]] and [[KDE Plasma]]) using the ''Font Control Panel'' will automatically create or overwrite the user font configuration file. For these desktop environments, it is best to match your already defined font configurations to get the expected behavior. Also ensure that the desktop [[locale]] settings or ''Regional Settings'' are supported by the configured fonts, if not the font configuration could be overridden.}}

Fontconfig configuration files use [[Wikipedia:XML|XML]] format and need these headers:

{{bc|<nowiki>
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "urn:fontconfig:fonts.dtd">
<fontconfig>



</fontconfig>
</nowiki>}}

The configuration examples in this article omit these tags.

=== Presets ===

There are presets installed in the directory {{ic|/usr/share/fontconfig/conf.avail}}. They can be enabled by creating [[Wikipedia:Symbolic link|symbolic link]]s to them, both per-user and globally, as described in {{ic|/etc/fonts/conf.d/README}}. These presets will override matching settings in their respective configuration files.

For example, to enable sub-pixel RGB rendering globally:

# ln -s /usr/share/fontconfig/conf.avail/10-sub-pixel-rgb.conf /etc/fonts/conf.d/

To do the same but instead for a per-user configuration:

$ mkdir $XDG_CONFIG_HOME/fontconfig/conf.d
$ ln -s /usr/share/fontconfig/conf.avail/10-sub-pixel-rgb.conf $XDG_CONFIG_HOME/fontconfig/conf.d/

=== Anti-aliasing ===

[[Wikipedia:Font rasterization|Font rasterization]] converts vector font data to bitmap data so that it can be displayed. The result can appear jagged due to [[Wikipedia:Aliasing|aliasing]]. [[Wikipedia:Anti-aliasing|Anti-aliasing]] can be used to increase the apparent resolution of font edges. Anti-aliasing is '''enabled''' by default. To disable it:

{{bc|1=<nowiki/>
<match target="font">
<edit name="antialias" mode="assign">
<bool>false</bool>
</edit>
</match>
}}

{{Note|Some applications may [[#Applications overriding hinting|override default anti-aliasing settings]].}}

=== Hinting ===

[[Wikipedia:Font hinting|Font hinting]] (also known as instructing) is the use of mathematical instructions to adjust the display of an outline font so that it lines up with a rasterized grid (i.e. the pixel grid of the display). Its intended effect is to make fonts appear more crisp so that they are more readable. Fonts will line up correctly without hinting when displays have around 300 [[Wikipedia:Dots per inch|DPI]].

==== Byte-Code Interpreter (BCI) ====

Using BCI hinting, instructions in TrueType fonts are rendered according to FreeTypes's interpreter. BCI hinting works well with fonts with good hinting instructions. Hinting is '''enabled''' by default. To disable it:

{{bc|1=<nowiki/>
<match target="font">
<edit name="hinting" mode="assign">
<bool>false</bool>
</edit>
</match>
}}

{{Note|1=The BCI implementation can be switched in the script {{ic|/etc/profile.d/freetype2.sh}}. The interpreter is set by passing the parameter {{ic|1=truetype:interpreter-version=''NN''}}, ''NN'' corresponding to the version chosen, to the {{ic|FREETYPE_PROPERTIES}} variable in the script. The most popular values are:

* 35 for classic mode (emulates Windows 98),
* '''40''' for [https://www.freetype.org/freetype2/docs/hinting/subpixel-hinting.html minimal mode] (stripped down Infinality, this is the default).

Subpixel rendering should use a subpixel BCI. For details, see [https://www.freetype.org/freetype2/docs/reference/ft2-properties.html#tt_interpreter_version_xxx].
}}

==== Autohinter ====

The autohinter attempts to do automatic hinting, disregarding any hinting information embedded in the font. Originally, it was the default because TrueType2 fonts were patent-protected, but now that these patents have expired, there is very little reason to use it. It does work better with fonts that have broken or no hinting information, but it will be strongly sub-optimal for fonts with good hinting information. Generally, common fonts are of the latter kind, so the autohinter will not be useful. The autohinter is '''disabled''' by default. To enable it:

{{bc|1=<nowiki/>
<match target="font">
<edit name="autohint" mode="assign">
<bool>true</bool>
</edit>
</match>
}}

==== Hintstyle ====

Hintstyle is the amount of font reshaping done to line up to the grid. Hinting values are: {{ic|hintnone}}, {{ic|hintslight}}, {{ic|hintmedium}}, and {{ic|hintfull}}. {{ic|hintslight}} will make the font more fuzzy to line up to the grid but will be better in retaining font shape (see [https://www.freetype.org/freetype2/docs/hinting/text-rendering-general.html]), while {{ic|hintfull}} will be a crisp font that aligns well to the pixel grid but will lose a greater amount of font shape. {{ic|hintslight}} implicitly uses the autohinter in a vertical-only mode in favor of font-native information for non-CFF (''.otf'') fonts.

{{ic|hintslight}} is the default setting. To change it:

{{bc|1=<nowiki/>
<match target="font">
<edit name="hintstyle" mode="assign">
<const>hintnone</const>
</edit>
</match>
}}

{{Note|Some applications may [[#Applications overriding hinting|override default hinting settings]].}}

=== Subpixel layout ===

Fontconfig will need to know your [[Wikipedia:Subpixel rendering#Characteristics|subpixel layout]] to be able to display your fonts correctly. Use the [http://www.lagom.nl/lcd-test/subpixel.php Subpixel layout] monitor test (part of [http://www.lagom.nl/lcd-test/ The Lagom LCD monitor test pages]) to find out your subpixel arrangement.

Subpixel geometry is configured via the {{ic|rgba}} property, which could be either:

* {{ic|rgb}} — ''red'', ''green'', ''blue'' — most common, is used by the most monitors manufactured today
* {{ic|bgr}}
* {{ic|vrgb}} — vertical
* {{ic|vbgr}}
* {{ic|none}} — no subpixel rendering

{{bc|1=<nowiki/>
<match target="font">
<edit name="rgba" mode="assign">
<const>rgb</const>
</edit>
</match>
}}

{{Note|Without [[#Subpixel rendering]], freetype will only care about the alignment (vertical or horizontal) of the subpixels. There is no difference between '''RGB''' and '''BGR''', for example.}}

There is no support for unusual subpixel layouts such as "Pentile" and "RGBY", occasionally found on TV, OLED and mobile screens. For these devices, it is best to give up subpixel rendering and rely on greyscale by using the {{ic|none}} option.

=== Subpixel rendering ===

[[wikipedia:Subpixel rendering|Subpixel rendering]] is a technique to improve sharpness of font rendering by effectively tripling the horizontal (or vertical) resolution through the use of subpixels. On Windows machines, this technique is called [[wikipedia:ClearType|ClearType]].

FreeType2 provides two different types of subpixel rendering, called Harmony and ClearType. The ClearType subpixel rendering is [https://gitlab.archlinux.org/archlinux/packaging/packages/freetype2/-/commit/35e925e946da41b7a2d7c297ee43c4cab386048c enabled] by default.

An LCD filter is recommended when ClearType subpixel rendering is enabled. The Harmony subpixel rendering does '''not''' require setting an LCD filter and with default LCD geometry, it is equivalent to ClearType with the {{ic|lcdlight}} filter [https://freetype.org/freetype2/docs/reference/ft2-lcd_rendering.html]. See the following section on how to enable an LCD filter and its benefits.

==== LCD filter ====

When using ClearType subpixel rendering, you should enable the LCD filter, which is designed to reduce color fringing. This is described under [https://www.freetype.org/freetype2/docs/reference/ft2-lcd_rendering.html LCD filtering] in the FreeType 2 API reference. Different options are described under [https://www.freetype.org/freetype2/docs/reference/ft2-lcd_rendering.html#ft_lcdfilter FT_LcdFilter], and are illustrated by this [http://www.spasche.net/files/lcdfiltering/ LCD filter test] page.

The {{ic|lcddefault}} filter will work for most users. Other filters are available that can be used in special situations: {{ic|lcdlight}}; a lighter filter ideal for fonts that look too bold or fuzzy, {{ic|lcdlegacy}}, the original Cairo filter; and {{ic|lcdnone}} to disable it entirely.

{{bc|1=<nowiki/>
<match target="font">
<edit name="lcdfilter" mode="assign">
<const>lcddefault</const>
</edit>
</match>
}}

==== Advanced LCD filter specification ====

If the available built-in LCD filters are not satisfactory, it is possible to tweak the font rendering very specifically by building a custom freetype2 package and modifying the hardcoded filters. The [[Arch build system]] can be used to build and install packages from source.

Checkout the {{Pkg|freetype2}} PKGBUILD and download/extract the build files. [[Arch build system#Retrieve PKGBUILD source]] lists some of the methods.

Enable ClearType subpixel rendering by editing the file {{ic|src/freetype-VERSION/include/freetype/config/ftoption.h}} and uncommenting the {{ic|FT_CONFIG_OPTION_SUBPIXEL_RENDERING}} macro.

Then, edit the file {{ic|src/freetype-VERSION/src/base/ftlcdfil.c}} and look up the definition of the constant {{ic|default_weights}}:

static const FT_LcdFiveTapFilter default_weights =
{ 0x10, 0x40, 0x70, 0x40, 0x10 };

This constant defines a low-pass filter applied to the rendered glyph. Modify it as needed. (reference: [https://lists.nongnu.org/archive/html/freetype/2006-09/msg00069.html freetype list discussion]) Save the file, build and install the custom package:

$ makepkg --noextract
# pacman --remove --nodeps freetype2
# pacman --upgrade freetype2-''VERSION''-''ARCH''.pkg.tar.zstd

Restart X. The lcddefault filter should now render fonts differently.

=== Custom settings for certain fonts or font styles ===

Some fonts may not look good with BCI hinting. It can be disabled for just those fonts:

...
<match target="font">
<test name="family" qual="any">
<string>My Font</string>
</test>
<edit name="hinting" mode="assign">
<bool>false</bool>
</edit>
</match>
...

=== Set default or fallback fonts ===

==== Match tests ====

A reliable way to set a default or fallback font is to add an XML fragment to perform a match test. With the "binding" attribute, for example, the following setting will fall back to ''Gentium'' in place of ''Georgia'':

{{bc|1=
...
<match target="pattern">
<test qual="any" name="family" compare="eq"><string>Georgia</string></test>
<edit name="family" mode="assign" binding="same"><string>Gentium Book</string></edit>
</match>
...
}}

In the above, the "compare" attribute can be "eq" (i.e., exactly equal to ''Georgia''), "contains" (e.g., matching either ''Georgia'' or ''Georgia Pro''), or other values. See {{man|5|fonts-conf}}.

==== Alias ====

An alternate approach is to use ''<alias>'' to set the "preferred" font. Fonts matching the ''<family>'' element are edited to prepend the list of ''<prefer>''ed families before the matching ''<family>''. The following example will fall back to ''Bitstream Vera Sans'' when ''Helvetica'' is called:

{{bc|<nowiki>
...
<alias>
<family>Helvetica</family>
<prefer>
<family>Bitstream Vera Sans</family>
</prefer>
</alias>
...
</nowiki>}}

''<alias>'' can also be used to specify fallback fonts when some glyphs are missing. For example, most versions of ''Helvetica Neue'' do not include Greek characters. A user might have ''Helvetica Neue'' installed and want to use it for Latin characters, and fall back to ''FreeSans'' for Greek characters due to its similarity to ''Helvetica''. The following will allow this to be achieved:

{{bc|<nowiki>
...
<alias>
<family>Helvetica Neue LT Pro</family>
<prefer>
<family>Helvetica Neue LT Pro</family>
<family>FreeSans</family>
</prefer>
</alias>
...
</nowiki>}}

The above is not needed if the user simply wants to fall back to default fonts whenever glyphs are missing.

=== Whitelisting and blacklisting fonts ===

The element {{ic|<selectfont>}} is used in conjunction with the {{ic|<acceptfont>}} and {{ic|<rejectfont>}} elements to selectively whitelist or blacklist fonts from the resolve list and match requests. The simplest and most typical use case is to reject a font that the user needs installed, but is getting matched for a generic font query that is causing problems with user interfaces.

First, obtain the Family name as listed in the font itself:

{{hc|1=$ fc-scan .fonts/lklug.ttf --format='%{family}\n'|2=
LKLUG
}}

Then, use that Family name in a {{ic|<rejectfont>}} stanza:

{{bc|1=
<selectfont>
<rejectfont>
<pattern>
<patelt name="family" >
<string>LKLUG</string>
</patelt>
</pattern>
</rejectfont>
</selectfont>
}}

Typically, when both elements are combined, {{ic|<rejectfont>}} is first used on a more general matching glob to reject a large group (such as a whole directory), then {{ic|<acceptfont>}} is used after it to whitelist individual fonts out of the larger blacklisted group.

{{bc|1=
<selectfont>
<rejectfont>
<glob>/usr/share/fonts/OTF/*</glob>
</rejectfont>
<acceptfont>
<pattern>
<patelt name="family" >
<string>Monaco</string>
</patelt>
</pattern>
</acceptfont>
</selectfont>
}}

=== Disable bitmap fonts ===

Bitmap fonts are sometimes used as fallbacks for missing fonts, which may cause text to be rendered pixelated or too large. Use the {{ic|70-no-bitmaps-except-emoji.conf}} [[#Presets|preset]] to disable this behavior.

To disable embedded bitmap for all fonts:

{{hc|~/.config/fontconfig/conf.d/20-no-embedded.conf|<nowiki>
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "urn:fontconfig:fonts.dtd">
<fontconfig>
<match target="font">
<edit name="embeddedbitmap" mode="assign">
<bool>false</bool>
</edit>
</match>
</fontconfig>
</nowiki>}}

{{Note|Disabling embedded bitmaps will break all bitmap fonts, including emoji fonts.}}

To disable embedded bitmap fonts for a specific font:

<match target="font">
<test qual="any" name="family">
<string>Monaco</string>
</test>
<edit name="embeddedbitmap">
<bool>false</bool>
</edit>
</match>

If embedded bitmaps are disabled for all fonts, they can still be enabled for a specific font in case it does not function without embedded bitmaps. E.g. for Noto Color Emoji:

{{bc|<nowiki>
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "urn:fontconfig:fonts.dtd">
<fontconfig>
<match target="font">
<edit name="embeddedbitmap" mode="assign">
<bool>false</bool>
</edit>
</match>
<match target="font">
<test name="family" qual="any">
<string>Noto Color Emoji</string>
</test>
<edit name="embeddedbitmap">
<bool>true</bool>
</edit>
</match>
</fontconfig>
</nowiki>}}

=== Disable scaling of bitmap fonts ===

To disable scaling of bitmap fonts (which often makes them blurry), remove {{ic|/etc/fonts/conf.d/10-scale-bitmap-fonts.conf}}.
Note this can break the scaling of emoji fonts such as Segoe UI Emoji, making them huge.

To re-enable scaling of bitmap fonts, re-create the symbolic link:

# ln -s /usr/share/fontconfig/conf.avail/10-scale-bitmap-fonts.conf /etc/fonts/conf.d/

=== Create bold and italic styles for incomplete fonts ===

FreeType has the ability to automatically create ''italic'' and '''bold''' styles for fonts that do not have them, but only if explicitly required by the application. Given programs rarely send these requests, this section covers manually forcing generation of missing styles.

Start by editing {{ic|/usr/share/fonts/fonts.cache-1}} as explained below. Store a copy of the modifications on another file, because a font update with {{ic|fc-cache}} will overwrite {{ic|/usr/share/fonts/fonts.cache-1}}.

Assuming the Dupree font is installed:

"dupree.ttf" 0 "Dupree:style=Regular:slant=0:weight=80:width=100:foundry=unknown:index=0:outline=True:''etc...''

Duplicate the line, change {{ic|1=style=Regular}} to {{ic|1=style=Bold}} or any other style. Also change {{ic|1=slant=0}} to {{ic|1=slant=100}} for italic, {{ic|1=weight=80}} to {{ic|1=weight=200}} for bold, or combine them for '''''bold italic''''':

"dupree.ttf" 0 "Dupree:style=Bold Italic:slant=100:weight=200:width=100:foundry=unknown:index=0:outline=True:''etc...''

Now add necessary modifications to {{ic|$XDG_CONFIG_HOME/fontconfig/fonts.conf}}:

{{bc|1=
...
<match target="font">
<test name="family" qual="any">
<string>Dupree</string>

</test>
<test name="weight" compare="more_eq"><int>140</int></test>
<edit name="embolden" mode="assign"><bool>true</bool></edit>
</match>

<match target="font">
<test name="family" qual="any">
<string>Dupree</string>

</test>
<test name="slant" compare="more_eq"><int>80</int></test>
<edit name="matrix" mode="assign">
<times>
<name>matrix</name>
<matrix>
<double>1</double><double>0.2</double>
<double>0</double><double>1</double>
</matrix>
</times>
</edit>
</match>
...
}}

{{Tip| Use the value {{ic|embolden}} for existing bold fonts in order to make them even bolder.}}

=== Rule priority ===

Fontconfig processes files in {{ic|/etc/fonts/conf.d}} in numerical order. Therefore, the rules of {{ic|01-aaa.conf}} and {{ic|02-bbb.conf}} will have the same effect as a single {{ic|01-aaabbb.conf}} file first containing the rules of {{ic|01-aaa}} then the ones of {{ic|02-bbb}}.

Usually, that means the files with the smaller prefix will have higher precedence. However, the Fontconfig syntax is flexible and allows a new rule to take precedence over an existing rule. Therefore, it is recommended to [[#Query the current settings]] to test the result of the rule interactions.

{{Accuracy|The actual behavior seems to be different from what is described below.|section=Rule priority}}

Note that the user's rules defined in {{ic|$XDG_CONFIG_HOME/fontconfig/fonts.conf}} and in the directory {{ic|$XDG_CONFIG_HOME/fontconfig/conf.d}} are loaded via the file {{ic|/etc/fonts/conf.d/50-user.conf}} and typically take precedence over the rules defined in files starting with a higher number.

=== Query the current settings ===

To find out what settings are in effect, use {{ic|fc-match --verbose}}. eg.

{{hc|$ fc-match --verbose Sans|
family: "DejaVu Sans"(s)
hintstyle: 3(i)(s)
hinting: True(s)
...
}}

Look up the meaning of the numbers at {{man|5|fonts-conf}} Eg. 'hintstyle: 3' means 'hintfull'

== Applications without Fontconfig support ==

{{Note| Qt 6.8 at least with the xcb backend started to give the X11 resources preference over fontconfig, so these settings will become authorative for Qt 6 clients despite their full fontconfig support.}}

Some applications like [[URxvt]] will ignore Fontconfig settings. You can work around this by using {{ic|~/.Xresources}}, but it is not as flexible as Fontconfig. Example (see [[#Fontconfig configuration]] for explanations of the options):

{{hc|~/.Xresources|
Xft.autohint: 0
Xft.lcdfilter: lcddefault
Xft.hintstyle: hintslight
Xft.hinting: 1
Xft.antialias: 1
Xft.rgba: rgb
}}

Make sure the settings are loaded properly when X starts with {{ic|xrdb -q}} (see [[X resources]] for more information).

== Troubleshooting ==

=== Distorted fonts ===

See [[HiDPI]] for instructions on handling high or mixed DPI displays: using a DPI setting which is not matching the physical hardware can lead to fuzzy font display.

=== Calibri, Cambria, Monaco, etc. not rendering properly ===

Some scalable fonts have embedded bitmap versions which are rendered instead, mainly at smaller sizes. Using [[Metric-compatible fonts]] as replacements can improve the rendering in these cases.

You can also force using scalable fonts at all sizes by [[#Disable bitmap fonts|disabling embedded bitmap]], sacrificing some rendering quality.

=== Applications overriding hinting ===

Some applications or desktop environments may override default Fontconfig hinting and anti-aliasing settings. This may happen with [[GNOME]] 3, for example while you are using Qt applications like {{pkg|vlc}} or {{pkg|smplayer}}. Use the specific configuration program for the application in such cases. For GNOME, try {{Pkg|gnome-tweaks}}.

=== Applications not picking up hinting from GNOME settings ===

For instance, under GNOME it sometimes happens that Firefox applies full hinting even when it is set to "none" in GNOME's settings, which results in sharp and widened fonts. In this case you would have to add hinting settings to your {{ic|fonts.conf}} file:

{{bc|<nowiki>
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "urn:fontconfig:fonts.dtd">
<fontconfig>
<match target="font">
<edit mode="assign" name="hinting">
<bool>false</bool>
</edit>
</match>
</fontconfig>
</nowiki>}}

In this example, hinting is set to {{ic|grayscale}}.

=== Incorrect hinting in GTK applications ===

In some desktop environments, especially outside [[GNOME]] and [[Plasma]], some GTK applications could not read font configuration properly. In order to solve this issue, install {{Pkg|xsettingsd}} or {{AUR|xsettingsd-git}} and execute it at every system startup. See also [[Xsettingsd]] and [https://github.com/derat/xsettingsd/wiki/Settings xsettingsd wiki] for more information. It can be configured with the following common configuration:

{{hc|~/.xsettingsd|
Xft/Hinting 1
Xft/HintStyle "hintslight"
Xft/Antialias 1
Xft/RGBA "rgb"
}}

If that is not working in some other applications, you could install {{Pkg|xorg-xrdb}} and provide the following configuration:

{{hc|~/.Xresources|
Xft.hinting: 1
Xft.hintstyle: hintslight
Xft.antialias: 1
Xft.rgba: rgb
}}

Then you can execute the script {{ic|xrdb -merge ~/.Xresources}} at every system startup to apply the options. See also [[X resources]] and [[#Applications without Fontconfig support]].

=== Hinting in GTK4 programs ===

GTK4 and libadwaita programs ignore font hinting settings. To remedy this, create or modify the following configuration:

{{hc|~/.config/gtk-4.0/settings.ini|2=
[Settings]
gtk-hint-font-metrics=true
gtk-font-rendering=manual
}}

See also [https://docs.gtk.org/gtk4/property.Settings.gtk-hint-font-metrics.html GTK documentation], [https://gitlab.gnome.org/GNOME/gtk/-/issues/3787 GTK issue 3787], and [https://gitlab.gnome.org/GNOME/gtk/-/issues/3787#note_2312277 this related note].

=== Helvetica font problem in generated PDFs ===

If the following command

fc-match helvetica

produces

helvR12-ISO8859-1.pcf.gz: "Helvetica" "Regular"

then the bitmap font provided by {{Pkg|xorg-fonts-75dpi}} is likely to be embedded into PDFs generated by "Print to File" or "Export" in various applications. The bitmap font was probably installed as a consequence of installing the whole {{Grp|xorg}} group (which is usually NOT recommended). To solve the pixelized font problem, you can uninstall the package. Install {{Pkg|gsfonts}} (Type 1) or {{Pkg|tex-gyre-fonts}} (OpenType) for corresponding free substitute of Helvetica (and other PostScript/PDF base fonts).

You may also experience similar problem when you open a PDF which requires Helvetica but does not have it embedded for viewing.

=== FreeType breaking bitmap fonts ===

Some users are reporting problems ({{Bug|52502}}) with bitmap fonts having changed names after upgrading {{Pkg|freetype2}} to version 2.7.1, creating havoc in terminal emulators and several other programs such as [[dwm]] or [[dmenu]] by falling back to another (different) font. This was caused by the changes to the PCF font family format, which is described in their ''release notes'' [https://sourceforge.net/projects/freetype/files/freetype2/2.7.1/]. Users transitioning from the old format might want to create a ''font alias'' to remedy the problems, like the solution which is described in [https://forum.manjaro.org/t/terminus-font-name-fix-after-freetype2-update-to-2-7-1-1/15530], given here too:

Assume we want to create an alias for {{Pkg|terminus-font}}, which was renamed from {{ic|Terminus}} to {{ic|xos4 Terminus}} in the previously described {{Pkg|freetype2}} update:

{{Out of date|{{ic|/etc/fonts/conf.avail}} was replaced with {{ic|/usr/share/fontconfig/conf.avail}}, but it is intended for pre-installed files.}}

* Create a configuration file in {{ic|/etc/fonts/conf.avail/}} for the ''font alias'':
{{hc|/etc/fonts/conf.avail/33-TerminusPCFFont.conf|<nowiki>
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "urn:fontconfig:fonts.dtd">
<fontconfig>
<alias>
<family>Terminus</family>
<prefer><family>xos4 Terminus</family></prefer>
<default><family>fixed</family></default>
</alias>
</fontconfig>
</nowiki>}}
* Create a symbolic link towards it in the {{ic|/etc/fonts/conf.d}} directory. In our example we would link as follows: {{ic|ln -s /etc/fonts/conf.avail/33-TerminusPCFFont.conf /etc/fonts/conf.d}} to make the change permanent.
Everything should now work as it did before the update, the ''font alias'' should not be in effect, but make sure to either reload {{ic|.Xresources}} or restart the display server first so the affected programs can use the alias.

=== Underscores not rendered with DejaVu Monospace ===

[https://gitlab.gnome.org/GNOME/pango/issues/392 Since Pango 1.44], the underscore characters disappear with certain font sizes when using the DejaVu Sans Mono font. A workaround is to use Liberation Mono as the monospace font, see [[#Set default or fallback fonts]].

=== Debugging FreeType fonts ===

{{Pkg|freetype2-demos}} provides tools for debugging FreeType font configuration. {{ic|ftview}} is a GUI in which you can tweak font rendering settings with a live preview. For example:

$ ftview -e unic -d 1024x768x24 -r 96 10 /usr/share/fonts/noto/NotoSans-Regular.ttf

=== Text is blurry ===

Some applications (e.g. Chromium/Electron) do not apply gamma correction properly, some have it disabled on certain scenarios (grayscale) which cause small text on dark background to be blurry and unreadable text on <=1080p screens. It is a [https://bugs.chromium.org/p/chromium/issues/detail?id=1443720 long standing issue for Chromium/Electron], a workaround is to [https://freetype.org/freetype2/docs/reference/ft2-properties.html#no-stem-darkening enable stem darkerning] with the {{ic|1=FREETYPE_PROPERTIES="cff:no-stem-darkening=0 autofitter:no-stem-darkening=0"}} [[environment variable]].

=== font-config-info ===

You can gather your effective font configuration with {{AUR|font-config-info-git}}. It queries information from [https://codeberg.org/derat/font-config-info/ several] [[GTK]] sources, [[X resources]], [[Xsettingsd|XSETTINGS]] protocol and {{pkg|fontconfig}}.

== See also ==

* [https://keithp.com/~keithp/render/Xft.tutorial An Xft Tutorial] by Keith Packard
* [https://www.x.org/releases/current/doc/xorg-docs/fonts/fonts.html Fonts in X11]
* [https://freetype.sourceforge.net/freetype2/ FreeType 2]
* [https://www.freetype.org/freetype2/docs/reference/index.html#controlling-freetype-modules FreeType 2 API Reference: Controlling FreeType Modules]
* [https://forums.gentoo.org/viewtopic-t-723341.html Gentoo font-rendering thread]
* [https://www.freetype.org/freetype2/docs/hinting/text-rendering-general.html On slight hinting]

Fstab

2026-05-16T09:41:51Z

Erus Iluvatar: /* Remote file system */ Remove direct systemctl commands, per Help:Style#systemd units operations

{{Lowercase title}}
[[Category:File systems]]
[[Category:Boot process]]
[[de:Fstab]]
[[es:Fstab]]
[[fr:Fstab]]
[[hu:Fstab]]
[[it:Fstab]]
[[ja:Fstab]]
[[pt:Fstab]]
[[ru:Fstab]]
[[zh-hans:Fstab]]
{{Related articles start}}
{{Related|Persistent block device naming}}
{{Related|File systems}}
{{Related|tmpfs}}
{{Related|swap}}
{{Related|genfstab}}
{{Related articles end}}

The {{man|5|fstab}} file can be used to define how disk partitions, various other block devices, or remote file systems should be mounted into the file system.

Each file system is described in a separate line. These definitions will be converted into [[systemd]] mount units dynamically at boot, and when the configuration of the system manager is reloaded. The default setup will automatically [[fsck]] and mount file systems before starting services that need them to be mounted. For example, systemd automatically makes sure that remote file system mounts like [[NFS]] or [[Samba]] are only started after the network has been set up. Therefore, local and remote file system mounts specified in {{ic|/etc/fstab}} should work out-of-the-box. See {{man|5|systemd.mount}} for details.

The {{ic|mount}} command will use fstab, if just one of either directory or device is given, to fill in the value for the other parameter. When doing so, mount options which are listed in fstab will also be used.

{{Expansion|Explain what {{man|8|systemd-remount-fs.service}} does and suggest using {{ic|rootflags}} for mount options that cannot be applied by remounting.}}

== Usage ==

A simple {{ic|/etc/fstab}}, using file system UUIDs:
{{hc|/etc/fstab|2=
# <device> <dir> <type> <options> <dump> <fsck>
UUID=0a3407de-014b-458b-b5c1-848e92a327a3 / ext4 defaults 0 1
UUID=CBB6-24F2 /boot vfat defaults,nodev,nosuid,noexec,fmask=0177,dmask=0077 0 2
UUID=f9fe0b69-a280-415d-a03a-a32752370dee none swap defaults 0 0
UUID=b411dc99-f0a0-4c87-9e05-184977be8539 /home ext4 defaults 0 2
}}

* {{ic|<device>}} describes the block special device or remote file system to be mounted; see [[#Identifying file systems]].
* {{ic|<dir>}} is the directory where the file system will be [[mount]]ed to, a.k.a. the mountpoint. The directory must be created beforehand.
* {{ic|<type>}} is the [[file system]] type.
* {{ic|<options>}} are the file system mount options; see {{man|8|mount|FILESYSTEM-INDEPENDENT MOUNT OPTIONS}} and {{man|5|ext4|Mount options for ext4}}.
* {{ic|<dump>}} is checked by the {{man|8|dump|url=https://linux.die.net/man/8/dump}} utility. This field is usually set to {{ic|0}}, which disables the check.
* {{ic|<fsck>}} sets the order for file system checks at boot time; see {{man|8|fsck}}. For the root device it should be {{ic|1}}. For other partitions it should be {{ic|2}}, or {{ic|0}} to disable checking.

{{Tip|
* The {{ic|auto}} type lets the mount command guess what type of file system is used. This is useful for [[Optical disc drive|optical media]] (CD/DVD/Blu-ray).
* If the root file system is [[btrfs]] or [[XFS]], the fsck order should be set to {{ic|0}} instead of {{ic|1}}. See {{man|8|fsck.btrfs}} and {{man|8|fsck.xfs}}.
}}

All specified devices within {{ic|/etc/fstab}} will be automatically mounted on startup and when the {{ic|-a}} flag is used with {{man|8|mount}} unless the {{ic|noauto}} option is specified. Devices that are listed and not present will result in an error unless the {{ic|nofail}} option is used.

See {{man|5|fstab|DESCRIPTION}} for details.

== Identifying file systems ==

{{Expansion|There are more device paths than just kernel name descriptors. {{ic|/dev/disk/by-*/*}}, {{ic|/dev/mapper/*}}, {{ic|/dev/md/*}} have various levels of persistence and there should be no issue using them.}}

There are different ways to identify file systems that will be mounted in {{ic|/etc/fstab}}: kernel name descriptor, file system label and UUID, and GPT partition label and UUID for GPT disks. Kernel name descriptors should not be used, while UUIDs or PARTUUIDs should be preferred over labels. See [[Persistent block device naming]] for more explanations. It is recommended to read that article first before continuing with this article.

In this section, we will describe how to mount file systems using all the mount methods available via examples. The output of the commands {{ic|lsblk -f}} and {{ic|blkid}} used in the following examples are available in the article [[Persistent block device naming]].

=== Kernel name descriptors ===

Run {{ic|lsblk -f}} to list the partitions and prefix the values in the ''NAME'' column with {{ic|/dev/}}.

{{hc|/etc/fstab|2=
# <device <dir> <type> <options> <dump> <fsck>
/dev/sda2 / ext4 defaults 0 1
/dev/sda1 /boot vfat defaults,nodev,nosuid,noexec,fmask=0177,dmask=0077 0 2
/dev/sda3 /home ext4 defaults 0 2
/dev/sda4 none swap defaults 0 0
}}

{{Warning|[[Device file#Block device names|Kernel name descriptors for block devices]] are not [[Persistent block device naming|persistent]] and can change each boot, they should not be used in configuration files (including {{ic|/etc/fstab}}).}}

=== File system labels ===

Run {{ic|lsblk -f}} to list the partitions, and prefix the values in the [[LABEL]] column with {{ic|1=LABEL=}} or alternatively run {{ic|blkid}} and use the LABEL values without the quotes:

{{hc|/etc/fstab|2=
# <device> <dir> <type> <options> <dump> <fsck>
LABEL=System / ext4 defaults 0 1
LABEL=ESP /boot vfat defaults,nodev,nosuid,noexec,fmask=0177,dmask=0077 0 2
LABEL=Data /home ext4 defaults 0 2
LABEL=Swap none swap defaults 0 0
}}

{{Note|If any of your fields contains spaces, see [[#Filepath spaces]].}}

=== File system UUIDs ===

Run {{ic|lsblk -f}} to list the partitions, and prefix the values in the [[UUID]] column with {{ic|1=UUID=}} or alternatively run {{ic|blkid}} and use the UUID values without the quotes:

{{hc|/etc/fstab|2=
# <device> <dir> <type> <options> <dump> <fsck>
UUID=0a3407de-014b-458b-b5c1-848e92a327a3 / ext4 defaults 0 1
UUID=CBB6-24F2 /boot vfat defaults,nodev,nosuid,noexec,fmask=0177,dmask=0077 0 2
UUID=b411dc99-f0a0-4c87-9e05-184977be8539 /home ext4 defaults 0 2
UUID=f9fe0b69-a280-415d-a03a-a32752370dee none swap defaults 0 0
}}

=== GPT partition labels ===

Run {{ic|blkid}} to list the partitions, and use the [[PARTLABEL]] values without the quotes:

{{hc|/etc/fstab|2=
# <device> <dir> <type> <options> <dump> <fsck>
PARTLABEL=GNU/Linux / ext4 defaults 0 1
PARTLABEL=EFI\040system\040partition /boot vfat defaults,nodev,nosuid,noexec,fmask=0177,dmask=0077 0 2
PARTLABEL=Home /home ext4 defaults 0 2
PARTLABEL=Swap none swap defaults 0 0
}}

{{Note|If any of your fields contains spaces, see [[#Filepath spaces]].}}

=== GPT partition UUIDs ===

Run {{ic|blkid}} to list the partitions, and use the [[PARTUUID]] values without the quotes:

{{hc|/etc/fstab|2=
# <device> <dir> <type> <options> <dump> <fsck>
PARTUUID=98a81274-10f7-40db-872a-03df048df366 / ext4 defaults 0 1
PARTUUID=d0d0d110-0a71-4ed6-936a-304969ea36af /boot vfat defaults,nodev,nosuid,noexec,fmask=0177,dmask=0077 0 2
PARTUUID=7280201c-fc5d-40f2-a9b2-466611d3d49e /home ext4 defaults 0 2
PARTUUID=039b6c1c-7553-4455-9537-1befbc9fbc5b none swap defaults 0 0
}}

== Tips and tricks ==

=== Automount with systemd ===

See {{man|5|systemd.mount}} for all systemd mount options.

==== Local partition ====

In case of a large partition, it may be more efficient to allow services that do not depend on it to start while it is checked by ''fsck''. This can be achieved by adding the following options to the {{ic|/etc/fstab}} entry of the partition:

x-systemd.automount

This will fsck and mount the partition only when it is first accessed, and the kernel will buffer all file access to it until it is ready.
This method can be relevant if one has, for example, a significantly large {{ic|/home}} partition.

{{Note|This will make the file system type {{ic|autofs}} which is ignored by [[locate]] by default.}}

==== Remote file system ====

The same applies to remote file system mounts. If you want them to be mounted only upon access, you will need to use the {{ic|x-systemd.automount}} parameters. In addition, you can use the {{ic|1=x-systemd.mount-timeout=}} option to specify how long systemd should wait for the mount command to finish. Also, the {{ic|_netdev}} option ensures systemd understands that the mount is network dependent and order it after the network is online.

x-systemd.automount,x-systemd.mount-timeout=30,_netdev

Instruct systemd to reload {{ic|/etc/fstab}} and create the {{ic|.mount}} unit by doing a [[daemon-reload]] then [[restart]]ing the {{ic|remote-fs.target}}.

==== Encrypted file system ====

If you have secondary encrypted file systems with keyfiles, you can also add the {{ic|nofail}} parameter to the corresponding entries in {{ic|/etc/crypttab}} and {{ic|/etc/fstab}}. ''systemd'' will not wait for the cryptsetup service to finish unlocking and mounting the filesystem on boot, but instead may finish mounting this after reaching default.target. This will avoid any boot delay caused by unlocking secondary partitions that are not required immediately after boot. See [[dm-crypt/System configuration#Non blocking mounting]] for cryptsetup configuration

Since mount services will by default only wait for 90 seconds for the partition to be available, any delay in making the keyfile available may cause the mount to fail. To avoid this, add the option {{ic|1=x-systemd.mount-timeout=0}} to fstab in order to make sure that the mount service waits indefinitely for the partition to be unlocked.

{{hc|/etc/fstab|2=
UUID=0a3407de-014b-458b-b5c1-848e92a327a3 /data ext4 defaults,nofail,x-systemd.device-timeout=0 0 2
}}

==== Automatic unmount ====

You may also specify an idle timeout for a mount with the {{ic|x-systemd.idle-timeout}} flag. For example:

x-systemd.automount,x-systemd.idle-timeout=1min

This will make systemd unmount the mount after it has been idle for 1 minute.

=== External devices ===

{{Accuracy|the nofail option does not work as described here.|section=3.2 External Device options}}

External devices that are to be mounted when present but ignored if absent may require the {{ic|nofail}} option. This prevents errors being reported at boot. For example:

{{hc|/etc/fstab|2=
LABEL=MyExternalDrive /media/backup jfs nofail,x-systemd.device-timeout=5 0 2
}}

The {{ic|nofail}} option is best combined with the {{ic|x-systemd.device-timeout}} option. This is because the default device timeout is 90 seconds, so a disconnected external device with only {{ic|nofail}} will make your boot take 90 seconds longer, unless you reconfigure the timeout as shown. Make sure not to set the timeout to 0, as this translates to infinite timeout.

=== Filepath spaces ===

Since spaces are used in {{ic|fstab}} to delimit fields, if any field (''PARTLABEL'', ''LABEL'' or the mount point) contains spaces, these spaces must be replaced by escape characters {{ic|\}} followed by the 3 digit octal code {{ic|040}}:

{{hc|/etc/fstab|2=
UUID=47FA-4071 /home/username/Camera\040Pictures vfat defaults 0 0
LABEL=Storage\040drive /media/100\040GB\040(Storage) ext4 defaults,user 0 2
}}

=== atime options ===

Below atime options can impact drive performance.

* The {{ic|strictatime}} option updates the access time of the files every time they are accessed. This is more purposeful when Linux is used for servers; it does not have much value for desktop use. The drawback about the {{ic|strictatime}} option is that even reading a file from the page cache (reading from memory instead of the drive) will still result in a write.
* The {{ic|noatime}} option fully disables writing file access times to the drive every time you read a file. This works well for almost all applications, except for those that need to know if a file has been read since the last time it was modified. The write time information to a file will continue to be updated anytime the file is written to with this option enabled.
* The {{ic|nodiratime}} option disables the writing of file access times only for directories while other files still get access times written. {{Note|{{ic|noatime}} implies {{ic|nodiratime}}. [https://lwn.net/Articles/244941/ You do not need to specify both].}}
* {{ic|relatime}} updates the access time only if the previous access time was earlier than the current modify or change time. In addition, since Linux 2.6.30, the access time is always updated if the previous access time was more than 24 hours old. This option is used when the {{ic|defaults}} option, {{ic|atime}} option (which means to use the kernel default, which is {{ic|relatime}}; see {{man|8|mount}} and [https://lwn.net/Articles/244829/ Once upon atime]) or no options at all are specified.

When using [[Mutt]] or other applications that need to know if a file has been read since the last time it was modified, the {{ic|noatime}} option should not be used; using the {{ic|relatime}} option is acceptable and still provides a performance improvement.

Since kernel 4.0 there is another related option:

* {{ic|lazytime}} reduces writes to disk by maintaining changes to inode timestamps (access, modification and creation times) only in memory. The on-disk timestamps are updated only when either (1) the file inode needs to be updated for some change unrelated to file timestamps, (2) a sync to disk occurs, (3) an undeleted inode is evicted from memory or (4) if more than 24 hours passed since the last time the in-memory copy was written to disk.
: {{Warning|In the event of a system crash, the access and modification times on disk might be out of date by up to 24 hours.}}

Note that the {{ic|lazytime}} option works '''in combination''' with the aforementioned {{ic|*atime}} options, not as an alternative. That is {{ic|relatime}} by default, but can be even {{ic|strictatime}} with the same or less cost of disk writes as the plain {{ic|relatime}} option.

=== Remounting the root partition ===

If for some reason the root partition has been improperly mounted read only, remount the root partition with read-write access with the following command:

# mount -o remount,rw /

=== GPT partition automounting ===

When using UEFI/GPT, it is possible to omit certain partitions from {{ic|/etc/fstab}} by partitioning according to the [https://uapi-group.org/specifications/specs/discoverable_partitions_specification/ Discoverable Partitions Specification] and have {{man|8|systemd-gpt-auto-generator}} mount the partitions. See [[systemd#GPT partition automounting]].

To specify custom mount options for these volumes, use a [[Persistent block device naming#by-designator and gpt-auto|by-designator identifier]] as the device name:

{{hc|/etc/fstab|2=
/dev/disk/by-designator/root / ext4 defaults,noatime 0 1
/dev/disk/by-designator/swap none swap defaults,discard 0 0
}}

=== Bind mount ===

You can link directories with the {{ic|bind}} option:

{{hc|/etc/fstab|2=
# <device> <dir> <type> <options> <dump> <fsck>
UUID=94649E22649E06E0 /media/user/OS/ ntfs defaults,rw,errors=remount-ro 0 0
/media/user/OS/Users/user/Music/ /home/user/Music/ none defaults,bind 0 0
/media/user/OS/Users/user/Pictures/ /home/user/Pictures/ none defaults,bind 0 0
/media/user/OS/Users/user/Videos/ /home/user/Videos/ none defaults,bind 0 0
/media/user/OS/Users/user/Downloads/ /home/user/Downloads/ none defaults,bind 0 0
/media/user/OS/Users/user/Documents/ /home/user/Documents/ none defaults,bind 0 0
/media/user/OS/Users/user/projects/ /home/user/projects/windows/ none defaults,bind 0 0
}}

See {{man|8|mount|Bind mount operation}} for details.

=== Automatically generate an fstab using genfstab ===

You can use the ''genfstab'' tool to create an fstab file. See [[genfstab]] for details.

=== GUI utilities ===

Here is a list of programs that can be used to modify mount points. They might not have all the features possible for editing fstab, but have all of the most used ones and might make your workflow much easier:

* {{App|[[wikipedia:GNOME Disks|GNOME Disks]]|A GNOME utility for dealing with storage devices. Part of {{Grp|gnome}}.|https://apps.gnome.org/DiskUtility/|{{Pkg|gnome-disk-utility}}}}
* {{App|KDE Partition Manager|Utility to help you manage the disks, partitions, and file systems on your computer. Part of {{Grp|kde-system}}.|https://apps.kde.org/partitionmanager/|{{Pkg|partitionmanager}}}}

=== Modifying user permissions and ownership ===

If you want to allow any user to mount the drive, consider adding these mount options to add onto your fstab entries.

{{Note|This is also used for filesystems that do not have file permission abilities, which will also set the owner and permissions of the entire drive to the user who mounted it.}}

* {{ic|users}} - Allow any user to mount and to unmount the filesystem, even when some other ordinary user mounted it. This option implies the options noexec, nosuid, and nodev (unless overridden by subsequent options, as in the option line users,exec,dev,suid). Simply add {{ic|users}} to the mount options to enable this.
* {{ic|user}} - Allow an ordinary user to mount the filesystem. Only allows the same user to unmount. This option implies the options noexec, nosuid, and nodev (unless overridden by subsequent options, as in the option line user,exec,dev,suid). Simply add {{ic|user}} to the mount options to enable this.

For filesystems that do not have file permissions built in such as FAT and exFAT, you can explicitly set the user or group for the entire drive and its files. You can view the ID of a specific user in {{ic|/etc/passwd}}. The uid is the third number in the entry, and the group id is the fourth.

* {{ic|uid}} - Set the owner ID of the drive
* {{ic|gid}} - Set the group ID of the drive

For ext4, btrfs, and other filesystems that have permission abilities, other users might not be permitted to see the drive. Be sure to double check the permissions of {{ic|/path/to/drive/}} and modify them for what you need.

=== Verify changes ===

Use {{ic|findmnt --verify --verbose}} to check for syntax errors and invalid options in fstab.

== See also ==

* [https://docs.kernel.org/admin-guide/devices.html Full device listing including block device]
* [https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html Filesystem Hierarchy Standard]
* [https://www.askapache.com/optimize/super-speed-secrets/ 30x Faster Cache and Site Speed with TMPFS]

Installation guide (Français)

2026-05-15T09:43:39Z

Erus Iluvatar: /* Configuration du système */ fix typos

[[Category:Installation process (Français)]]
[[ar:Installation guide]]
[[bg:Installation guide]]
[[ca:Installation guide]]
[[cs:Installation guide]]
[[de:Arch Install Scripts]]
[[el:Installation guide]]
[[en:Installation guide]]
[[es:Installation guide]]
[[fi:Installation guide]]
[[hu:Installation guide]]
[[it:Installation guide]]
[[ja:インストールガイド]]
[[ko:Installation guide]]
[[lv:Installation guide]]
[[pl:Installation guide]]
[[pt:Installation guide]]
[[ru:Installation guide]]
[[sv:Installation guide]]
[[th:Installation guide]]
[[tr:Installation guide]]
[[uk:Installation guide]]
[[zh-hans:安装指南]]
[[zh-hant:Installation guide]]
{{TranslationStatus (Français)|Installation guide|2026-05-15|870170}}

Ce document est un guide pour l'installation d'[[Arch Linux (Français)|Arch Linux]] au moyen du système « live » Archiso démarré depuis le support d'installation issue des images officielles. Le support d'installation offre des fonctionnalités d'accessibilité décrites à la page [[Install Arch Linux with accessibility options (Français)|Installer Arch Linux avec les options d'accessibilité]]. Pour les autres moyens d'installation, consultez [[:Category:Installation process (Français)]].

Avant installation, il est conseillé de consulter la [[Frequently asked questions (Français)|FAQ]]. Pour les conventions utilisées dans ce document, voir [[Help:Reading (Français)|l'aide à la lecture]]. En particulier, les exemple de code contiennent parfois des champs (notés en {{ic|''italique''}}) que vous devez modifier manuellement.

Ce guide est rédigé de manière concise et il vous est conseillé de suivre les instructions dans l'ordre présenté pour chaque section. Pour de plus amples instructions, se référer aux articles respectifs du [[ArchWiki]] ainsi que les [[man page|pages de manuel]] en liens dans ce guide. Pour une aide interactive, le [[Arch IRC channels (Français)|Canal IRC francophone]] ainsi que le [https://forums.archlinux.fr forum francophone] (ou le [https://bbs.archlinux.org/ forum international] pour les bilingues) sont disponibles.

Arch Linux devrait fonctionner sur n'importe quelle machine utilisant l'architecture [[Wikipedia:fr:X86-64|x86_64]] dotée d'un minimum de 512 MiB de RAM, bien que plus de mémoire soit nécessaire pour démarrer le système « live » en vue de l'installation. [https://lists.archlinux.org/archives/list/arch-releng@lists.archlinux.org/message/D5HSGOFTPGYI6IZUEB3ZNAX4D3F3ID37/] Une installation basique devrait utiliser moins de 2 GiB d'espace disque. Enfin, le processus d'installation nécessitant le téléchargement de paquets depuis un dépôt distant, ce guide considère qu'une connexion Internet est disponible.

== Préparation avant l'installation ==

=== Obtenir l'image d'installation ===

Visitez la page de [https://archlinux.org/download/ Téléchargement] et, selon la façon dont vous voulez démarrer, récupérez l'image ISO ou bien l'image «netboot» ainsi que la signature PGP correspondante.

=== Vérifier la signature ===

Il est recommandé de vérifier la signature de l'image avant de l'utiliser, particulièrement lors du téléchargement depuis un ''miroir HTTP'', puisque ceux-ci sont sujet à être interceptés pour [https://www2.cs.arizona.edu/stork/packagemanagersecurity/attacks-on-package-managers.html fournir des fichiers malveillants].

Téléchargez la ''signature PGP de l'ISO'' depuis https://archlinux.org/download/#checksums dans le répertoire contenant l'ISO et suivez les instructions sur la page pour la vérifier.

Depuis une installation Arch Linux existante, vous pouvez également utiliser la commande:

$ pacman-key -v archlinux-''version''-x86_64.iso.sig

{{Note|
* La signature elle-même pourrait être manipulée si elle est téléchargée à partir d'un site miroir, au lieu de l'être à partir de [https://archlinux.org/download/ archlinux.org]. Dans ce cas, assurez-vous que la clé publique, qui est utilisée pour décoder la signature, soit signée par une autre clé digne de confiance. La commande {{ic|gpg}} affichera l'empreinte de la clé publique.
* Une autre méthode pour vérifier l'authenticité de la signature consiste à s'assurer que l'empreinte de la clé publique est identique à l'empreinte de la clé du [https://archlinux.org/people/developers/ développeur Arch Linux] qui a signé le fichier ISO. Voir [[Wikipedia:fr:Cryptographie asymétrique]] pour plus d'informations sur le processus d'authentification des clés par une clé publique.}}

=== Préparer un support d'installation ===

L'ISO peut être déployée sur la machine concernée via une [[USB flash installation medium (Français)|clé USB]], un [[Optical disc drive#Burning|disque optique]], ou par réseau avec [[PXE]] : consultez l'article approprié pour préparer vous-même un support d'installation avec le fichier ISO.

Pour une image "Netboot", suivez [[Netboot#Boot from a USB flash drive]] pour préparer une clé USB pour un démarrage UEFI.

=== Démarrer l'environnement « live » ===

{{note|Les images d'Arch Linux ne prennent pas en charge la technologie ''Secure Boot'' et vous devrez [[Unified Extensible Firmware Interface/Secure Boot#Disabling Secure Boot|la désactiver]] pour démarrer depuis le support d'installation. Vous pourrez si vous le souhaitez le configurer une fois l'installation terminée, en suivant ces [[Secure Boot|instructions]].}}

# Choisissez le périphérique de démarrage pour utiliser le support préparé précédemment. Généralement, la manipulation consiste à appuyer sur une touche — fréquemment mentionnée sur l'écran d'accueil de votre machine — durant le [[Wikipedia:fr:Power-on self-test (informatique)|POST]]. Référez-vous au manuel de votre carte mère pour plus de détails.
# Lorsque le menu du support d'installation apparaît,
#* si vous avez utilisé l'ISO, sélectionnez ''Arch Linux install medium'' et validez avec la touche {{ic|Entrée}}.
#* si vous avez utilisé l'image "Netboot", choisissez un miroir géographiquement proche depuis le menu ''Mirror'' et valiez avec la touche {{ic|Entrée}}. {{Astuce|
#** L'ISO utilise [[systemd-boot (Français)|systemd-boot]] pour démarrer sur les UEFI et [[syslinux (Français)|syslinux]] sur les BIOS. Utilisez respectivement {{ic|e}} ou {{ic|Tab}} pour ajouter des [[Kernel parameters#Boot loader configuration|paramètres de démarrage]]. L'image "Netboot" utilise iPXE et les paramètres de démarrage peuvent être choisis dans le menu ''Boot Options''. Consultez [https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio-archiso/blob/master/docs/README.bootparams /usr/share/doc/mkinitcpio-archiso/README.bootparams] pour une liste des paramètres de démarrage.
#** Un exemple typique de paramètre de démarrage à saisir manuellement est la taille de la police. Pour une meilleure lecture sur des écrans à haut DPI, s'il ne sont pas reconnus comme tels, {{ic|1=fbcon=font:TER16x32}} peut aider. Consultez [[HiDPI#Linux console (tty)]] pour des explications détaillées.}}
# Vous serez connecté dans la première [[Wikipedia:fr:Terminal (informatique)|console virtuelle]] sous l'utilisateur ''root'' et vous verrez une invite de commande [[zsh (Français)|zsh]]

Pour changer de console — par exemple pour consulter ce guide avec [https://lynx.invisible-island.net/lynx_help/Lynx_users_guide.html Lynx] pendant l'installation — vous pouvez utiliser le [[Linux console#Keyboard shortcuts|raccourci clavier]] {{ic|Alt+''flèches de direction''}}. Pour [[modifier]] les fichiers de configuration, {{man|1|mcedit}}, [[nano (Français)#Utilisation|nano]] et [[Vim#Usage|vim]] sont disponibles. Voir [https://geo.mirror.pkgbuild.com/iso/latest/arch/pkglist.x86_64.txt pkglist.x86_64.txt] pour consulter la liste des paquets inclus dans le support d'installation.

=== Disposition du clavier en console et de la police de caractères ===

[[Linux console (Français)/Keyboard configuration (Français)|La disposition]] par défaut est le clavier [[Wikipedia:File:KB United States-NoAltGr.svg|US]]. Les dispositions disponibles peuvent être listées par :

# localectl list-keymaps

Pour modifier la disposition du [[:category:Keyboard configuration (Français)|clavier]], passez son nom à {{man|1|loadkeys}}. Par exemple pour la disposition [[Wikipedia:File:Clavier-Azerty.svg|Française]] vous pouvez utiliser :

# loadkeys fr-latin1

[[Console fonts|Les polices de la console]] se trouvent dans {{ic|/usr/share/kbd/consolefonts/}} et peuvent de même être utilisées avec {{man|8|setfont}} en omettant les chemin et extension du fichier. Par exemple, pour utiliser l'une des plus larges polices adaptées aux [[HiDPI#Linux console (tty)|écrans HiDPI]], exécutez :

# setfont ter-132b

=== Vérifier le mode de démarrage ===

Pour vérifier le mode de démarrage, vérifiez le [[Unified Extensible Firmware Interface#UEFI firmware bitness|nombre de bits de l'UEFI]] :

# cat /sys/firmware/efi/fw_platform_size

* Si la commande renvoie {{ic|64}}, le système est démarré en mode UEFI et dispose d'un UEFI x64 64 bits.
* Si la commande renvoie {{ic|32}}, le système est démarré en mode UEFI et dispose d'un UEFI IA32 32 bits. Bien que cela soit pris en charge, cela limitera le choix du chargeur d'amorçage à ceux qui prennent en charge le démarrage en mode mixte.
* Si elle renvoie {{ic|No such file or directory}}, le système peut être démarré en mode [[Wikipedia:fr:BIOS (informatique)|BIOS]] (ou [[Wikipedia:fr:UEFI#Architecture UEFI|CSM]]). Si le système n'a pas démarré dans le mode souhaité (UEFI vs BIOS), reportez-vous au manuel de votre carte mère.

=== Connexion à Internet ===

Pour configurer la connexion réseau dans l'image « live », suivez ces étapes :

# Vérifiez que votre [[Network configuration (Français)|carte réseau]] est répertoriée et activée, par exemple avec {{man|8|ip-link}}: {{bc|# ip link}}
# Pour les connections sans fil comme le ''Wi-Fi'' ou les [[Wikipedia:fr:Réseau de téléphonie mobile|réseaux mobiles (4G...)]], vérifiez que l'utilitaire [[rfkill]] ne bloque pas l'interface.
# Connectez-vous au réseau:
#* Ethernet—Branchez le câble.
#* Wi-Fi—Authentifiez-vous sur le réseau sans fil avec [[iwctl]].
#* Réseaux mobiles—Connectez-vous au réseau avec l'utilitaire [[mmcli]].
# Configurez votre connexion réseau:
#* [[DHCP]]: l'adressage dynamique des adresses IP et des serveurs DNS (fourni par [[systemd-networkd (Français)|systemd-networkd]] et [[systemd-resolved (Français)|systemd-resolved]] devraient fonctionner par défaut) pour les protocoles [https://gitlab.archlinux.org/archlinux/archiso/-/blob/master/configs/releng/airootfs/etc/systemd/network/20-ethernet.network Ethernet], [https://gitlab.archlinux.org/archlinux/archiso/-/blob/master/configs/releng/airootfs/etc/systemd/network/20-wlan.network Wi-Fi] and [https://gitlab.archlinux.org/archlinux/archiso/-/blob/master/configs/releng/airootfs/etc/systemd/network/20-wwan.network Mobiles].
#* Adresse IP statique : suivez [[Network configuration#Static IP address]].
# La connexion peut être confirmée avec [[ping]]: {{bc|# ping ping.archlinux.org}}

{{Note|Dans l'image d'installation, [[systemd-networkd (Français)|systemd-networkd]], [[systemd-resolved (Français)|systemd-resolved]], [[iwd]] et [[ModemManager]] sont préconfigurés et activés par défaut. Ce ne sera pas le cas du système installé.}}

=== Mise à jour de l'horloge système ===

Le système « live » a besoin de l'heure précise pour éviter les erreurs de vérification de signature des paquets et les erreurs de certificat TLS. Le service [[systemd-timesyncd (Français)|systemd-timesyncd]] est activé par défaut dans l'environnement « live » et l'heure sera synchronisée automatiquement dès qu'une connexion à Internet sera établie.

Utilisez {{man|1|timedatectl}} pour vous assurer que l'horloge système est correctement synchronisée.

# timedatectl

=== Partitionnement des disques ===

Une fois reconnus par le système « live », les disques se verront affectés un [[block device|périphérique de type bloc]] tel que {{ic|/dev/sda}}, {{ic|/dev/nvme0n1}} ou {{ic|/dev/mmcblk0}}. Pour identifier ces périphériques, utilisez [[lsblk]] ou ''fdisk''.

# fdisk -l

Les résultats se terminant par {{ic|rom}}, {{ic|loop}} ou {{ic|airootfs}} peuvent être ignorés. Les appareils {{ic|mmcblk*}} se terminant par {{ic|rpmb}}, {{ic|boot0}} et {{ic|boot1}} peuvent être ignorés.

{{Note|Si le disque n'apparaît pas, [[Partitioning#Drives are not visible when firmware RAID is enabled|assurez-vous que le contrôleur de disque n'est pas en mode RAID]].}}

{{Astuce|Vérifiez que vos disques NVMe et vos disques durs au format avancé utilisent la [[Advanced Format|taille optimale du secteur logique]] avant le partitionnement.}}

Les [[partition]]s suivantes sont '''nécessaires''' sur un périphériques choisi:

* Une partition [[Wikipedia:fr:Répertoire racine|racine]] {{ic|/}}.
* Pour démarrer en mode [[UEFI]]: une [[EFI system partition (Français)|partition EFI]].

* Utilisez un [[Partitioning#Partitioning tools|outil de partitionnement]] comme [[fdisk]] pour modifier la table de partitions. Par exemple :
# fdisk ''/dev/disque_en_question''

{{Note |
* Prenez le temps de planifier un schéma de partitionnement à long terme afin d'éviter les conversions ou re-partitionnement risquées et compliquées dans le futur.
* Si vous souhaitez utiliser [[Install Arch Linux on LVM|LVM]], [[dm-crypt (Français)|un chiffrement de votre système]] ou encore [[RAID (Français)|RAID]], faites le maintenant.
* Si le disque depuis lequel vous souhaitez démarrer [[EFI system partition (Français)#Vérifier s'il y a une partition existante|possède déjà une partition EFI]], n'en recréez pas une autre mais utilisez la partition pré-existante.
* La [[Swap (Français)|Swap]] peut être définie sur un [[Swap (Français)#Fichier d'échange|fichier d'échange]] pour les systèmes de fichier qui le prennent en charge. Alternativement, de la swap basée sur le disque peut être évitée entièrement en configurant la [[zram#Usage as swap|swap sur zram]] après avoir installé le système.
}}

==== Exemples de partitionnement ====

{| class="wikitable"
|+ UEFI avec [[GPT]]
|-
! Point de montage sur le système installé
! Partition
! [[Wikipedia:fr:GUID Partition Table#GUID des types de partition|Type de partition]]
! Taille suggérée
|-
| {{ic|/boot}}1
| {{ic|/dev/''efi_system_partition''}}
| [[EFI system partition (Français)|EFI system partition]]
| 1 GiB
|-
| {{ic|[SWAP]}}
| {{ic|/dev/''partition_d'échange''}}
| Linux swap
| Au moins 4 GiB
|-
| {{ic|/mnt}}
| {{ic|/dev/''partition_racine''}}
| Linux x86-64 root (/)
| Le reste du disque. Au moins 23 à 32 GiB.
|}

# [[EFI system partition (Français)#Points de montage habituels|D'autres points de montage]], tels que {{ic|/efi}} sont possible, sous réserve que que si le chargeur d'amorçage utilisé soit capable de charger le [[Kernel (Français)|noyau]] et l'[[Arch boot process (Français)#Initramfs|initramfs]] directement depuis la partition racine. Voir l'avertissement dans [[Arch boot process (Français)#Chargeur d'amorçage]].

{| class="wikitable"
|+ BIOS avec [[MBR]]
|-
! Point de montage sur le système installé
! Partition
! [[Wikipedia:Partition type|Type de partition]]
! Taille suggérée
|-
| {{ic|[SWAP]}}
| {{ic|/dev/''partition_d'échange''}}
| Linux swap
| Au moins 4 GiB
|-
| {{ic|/mnt}}
| {{ic|/dev/''partition_racine''}}
| Linux
| Le reste du disque. Au moins 23 à 32 GiB.
|}

Pour d'autres exemples: [[Partitioning#Example layouts]].

=== Formatage des partitions ===

Une fois les partitions crées, celles-ci doivent être formatées avec un [[File systems|système de fichier]] approprié. Consultez [[File systems#Create a file system]] pour plus de détails.

Par exemple, pour créer un système de fichier [[Ext4 (Français)|ext4]] sur {{ic|/dev/''partition_racine''}}, utilisez :

# mkfs.ext4 /dev/''partition_racine''

Si vous avez crée une partition [[swap (Français)|d'échange]], initialisez la avec {{man|8|mkswap}}:

# mkswap /dev/''partition_d'échange''

{{Note|Pour les configurations avec LVM, chiffrement ou RAID, remplacez {{ic|/dev/''*_partition''}} par le chemin vers le périphérique de type bloc approprié.}}

Si vous avez créé une partition système EFI, [[EFI system partition (Français)#Formater la partition|formatez-la]] en FAT32 avec {{man|8|mkfs.fat}}.

{{Attention|Ne formatez la partition système EFI que si vous l'avez créée pendant le partitionnement. S'il y avait déjà une partition système EFI sur le disque précédemment, son formatage peut détruire les chargeurs d'amorçage des autres systèmes d'exploitation installés.}}

# mkfs.fat -F 32 /dev/''efi_system_partition''

=== Montage des systèmes de fichiers ===

[[Mount|Montez]] la partition racine dans {{ic|/mnt}}. Par exemple, si la partition racine est {{ic|/dev/''partition_racine''}}:

# mount /dev/''partition_racine'' /mnt

Créez chaques points de montage restants dans {{ic|/mnt}} (tels que {{ic|/mnt/boot}} pour {{ic|/boot}}) et montez les volumes dans l'ordre hiérarchique correspondant.

{{Astuce|Utilisez {{man|8|mount}} avec l'option {{ic|--mkdir}} pour créer le point de montage spécifié. Vous pouvez également le créer au préalable à l'aide de {{man|1|mkdir}}.}}

Pour les systèmes avec un UEFI, montez la partition système EFI. Par exemple :

# mount --mkdir /dev/''efi_system_partition'' /mnt/boot

Si vous avez créé une partition [[swap (Français)|d'échange]], activez-la avec {{man|8|swapon}}:

# swapon /dev/''partition_d'échange''

{{man|8|genfstab}} détectera plus tard les systèmes de fichiers et l'espace d'échange montés.

== Installation ==

=== Sélection du miroir ===

Les paquets à installer doivent être téléchargés depuis les [[Mirrors (Français)|miroirs]] des dépôts officiels tels que définis dans {{ic|/etc/pacman.d/mirrorlist}}. Plus le miroir se trouve haut dans la liste, plus grande est sa priorité lors du téléchargement d'un paquet.

Sur le système « live », tous les miroirs HTTPS sont activés (c'est-à-dire non commentés). Le miroir mondial le plus haut dans la liste devrait être suffisamment rapide pour la plupart des utilisateurs, mais vous pouvez tout de même vérifier le fichier pour vous assurer qu'il vous convient. Si ce n'est pas le cas, [[modifiez]] le fichier en conséquence et placez les miroirs les plus proches géographiquement en haut de la liste, bien que d'autres critères sont à prendre en compte. Vous pouvez également utiliser [[Reflector (Français)|reflector]] pour créer le fichier de liste de miroirs en fonction de différents critères.

''pacstrap'' copiera plus tard ce fichier sur le nouveau système, prendre votre temps sur cette étape peut donc vous en faire gagner plus tard.

=== Installation des paquets essentiels ===

Aucune configuration (à l'exception de {{ic|/etc/pacman.d/mirrorlist}}) n'est transféré de l'environnement « live » vers le système installé. Le seul paquet obligatoire est {{Pkg|base}}, qui '''n'inclut pas''' tous les outils de l'installation « live », donc l'installation d'autres paquets est fréquemment nécessaire.

En particulier, examinez les logiciels suivants et installez tout ce dont vous avez besoin :

* les mises-à-jour du [[microcode]] du processeur ({{Pkg|amd-ucode}} ou {{Pkg|intel-ucode}}) pour les corrections de bogues matériels et de sécurité,
* les utilitaires nécessaires à la gestion des [[File system|systèmes de fichiers]],
* les [[File systems|utilitaires en espace utilisateur pour les systèmes de fichiers]] qui seront utilisés pour, par exemple, la création de système de fichiers et [[fsck (Français)|fsck]],
* les utilitaires pour accéder ou gérer les partitions [[RAID (Français)|RAID]] ou [[LVM (Français)|LVM]] s'ils sont utilisés sur le système,
* les [[firmware|microprogrammes]] spécifiques à des périphériques qui ne seraient pas déjà inclus dans {{Pkg|linux-firmware}} (comme {{Pkg|sof-firmware}} pour [[Advanced Linux Sound Architecture (Français)#Microprogramme ALSA|l'audio de la carte mère]], {{Pkg|linux-firmware-marvell}} pour les puces Marvell sans fil et l'un des multiples packages de micrologiciels pour les [[Broadcom wireless|puces sans-fil Broadcom]]),
* les logiciels nécessaires à la [[Network configuration (Français)|connexion au réseau]] (par exemple, un [[Network configuration (Français)#Network managers|gestionnaire de réseau ou un client DHCP autonome]], un [[Network configuration/Wireless#Authentication|logiciel d'authentification]] pour le Wi-Fi, un [[ModemManager|gestionnaire de modem]] pour les réseaux mobiles),
* un [[List of applications/Documents#Console|éditeur de texte en console]] (tel que [[nano (Français)|nano]]) pour permettre la modification fichiers de configuration depuis la console,
* les paquets de documentation comme {{Pkg|man-db}}, {{Pkg|man-pages}} et {{Pkg|texinfo}}.

Vous pouvez comparer avec la liste des paquets disponibles sur le média d'installation : [https://geo.mirror.pkgbuild.com/iso/latest/arch/pkglist.x86_64.txt pkglist.x86_64.txt].

Pour installer d'autres paquets ou groupes de paquets, ajoutez leurs noms à la commande {{man|8|pacstrap}} ci-dessous (séparés par des espaces) ou utilisez [[pacman (Français)|pacman]] pour les [[installer]] pendant que vous êtes [[#Chroot|«chroot»é dans votre nouvelle installation]].

Par exemple, un système basique avec le [[Kernel (Français)|noyau]] et le microprogramme pour les périphériques les plus courants:

# pacstrap -K /mnt base linux linux-firmware

{{Astuce|
* Vous pouvez remplacer {{Pkg|linux}} par un autre noyau de votre choix ou l'omettre pour l'installation dans un [[Wikipedia:Container (virtualization)|container]].
* Vous pouvez également omettre le microprogramme si vous installez dans une machine virtuelle un container.
* Cette sélection initiale de paquets dans pacstrap n'est obligée d'inclure que ce qui est nécessaire au démarrage du système ; tous les autres logiciels peuvent être installés ou remplacés après l'installation.
}}

== Configuration du système ==

=== Fstab ===

Pour monter les systèmes de fichiers nécessaires (comme celui utilisé pour le répertoire de démarrage {{ic|/boot}}) au démarrage, générez un fichier [[Fstab (Français)|fstab]] avec un [[Persistent block device naming (Français)|nommage persistant des périphériques de type bloc]] au moyen de {{man|8|genfstab}}. Par exemple, référencez les partitions par leur [[Persistent block device naming (Français)#by-uuid|UUID]] avec {{ic|-U}} :

# genfstab -U /mnt >> /mnt/etc/fstab

Vérifiez le fichier {{ic|/mnt/etc/fstab}} obtenu, et modifiez-le en cas d'erreur.

=== Chroot ===

Pour interagir directement avec l'environnement, les outils et les configurations du nouveau système pour les étapes suivantes, comme si vous aviez démarré dessus, [[Chroot (Français)|chrootez]] dans le nouveau système:

# arch-chroot /mnt

{{Note|Certains outils de [[systemd (Français)|systemd]] tels que {{man|1|hostnamectl}}, {{man|1|localectl}} et {{man|1|timedatectl}} ne peuvent pas être utilisés à l'intérieur d'un {{man|1|chroot}}, car ils nécessitent une connexion [[dbus]] active. [https://github.com/systemd/systemd/issues/798#issuecomment-126568596]}}

=== Heure ===

Pour plus de commodité (par exemple, pour afficher l'heure locale correcte ou gérer l'heure d'été), définissez le [[System time (Français)#Fuseau horaire|fuseau horaire]], par exemple pour la France:

# ln -sf /usr/share/zoneinfo/Europe/Paris /etc/localtime

Lancez {{man|8|hwclock}} pour générer {{ic|/etc/adjtime}}:

# hwclock --systohc

Cette commande repose sur l'hypothèse que l'horloge matérielle est réglée sur [[Wikipedia:fr:UTC|UTC]]. Consultez [[System time (Français)#Standard de temps]] pour plus de détails.

Pour éviter la dérive de l'horloge et garantir une heure précise, configurez la [[System time (Français)#Synchronisation du temps|synchronisation du temps]] à l'aide d'un client [[Wikipedia:fr:Network Time Protocol|Network Time Protocol]] (NTP) tel que [[systemd-timesyncd (Français)|systemd-timesyncd]].

=== Locales ===

Pour utiliser le formatage spécifique à la région et à la langue (comme les dates, la devise, les séparateurs décimaux), [[modifiez]] {{ic|/etc/locale.gen}} et décommentez les [[Locale (Français)|locale]]s UTF-8 que vous utiliserez. Générez les locales en exécutant:

# locale-gen

[[Créez]] le fichier {{man|5|locale.conf}} et [[Locale (Français)#Définir la locale système|définissez la variable LANG]] correspondante :

{{hc|1=/etc/locale.conf|2=
LANG=''fr_FR.UTF-8''
}}

Éditez le fichier {{man|5|vconsole.conf}} afin d'y spécifier la [[Linux console (Français)/Keyboard configuration (Français)#Visualiser les configurations du clavier|disposition de clavier]] ainsi que la police de caractères que vous souhaitez conserver :

{{hc|1=/etc/vconsole.conf|2=
KEYMAP=''fr-latin1''
}}

=== Configuration réseau ===

Pour attribuer un nom unique et identifiable à votre système (particulièrement utile dans un environnement réseau), [[créez]] le fichier [[Network configuration#Set the hostname|hostname]] :

{{hc|/etc/hostname|
''lenomdevotremachine''
}}

{{Astuce|Pour obtenir des conseils sur le choix d'un nom d'hôte, consultez la [[RFC:1178|RFC 1178]]. Comme expliqué dans {{man|7|hostname}}, il doit contenir entre 1 et 63 caractères, en utilisant uniquement les lettres minuscules {{ic|a}} à {{ic|z}}, les chiffres {{ic|0}} à {{ic|9}} et le signe {{ic|-}}, et ne doit pas commencer par {{ic|-}}.}}

Terminez la [[Network configuration (Français)|configuration du réseau]] pour le nouvel environnement installé. Cela peut inclure l'installation d'un logiciel de [[network management|gestion de réseau]] approprié, sa configuration si nécessaire et l'activation de son unité systemd pour son lancement au démarrage de la machine.

=== Initramfs ===

La création d'un nouvel ''initramfs'' n'est généralement pas nécessaire, car [[mkinitcpio (Français)|mkinitcpio]] a été lancé lors de l'installation du [[Kernel (Français)|noyau]] avec ''pacstrap''.

Pour [[Install Arch Linux on LVM#Adding mkinitcpio hooks|LVM]], le [[Dm-crypt (Français)|chiffrement]] ou [[RAID#Configure mkinitcpio|RAID]], modifiez {{man|5|mkinitcpio.conf}} et recréez l'image ''initramfs''. Si vous avez [[#Locales|modifié la configuration par défaut du clavier de la console]], seul recréer l'initramfs est nécessaire :

# mkinitcpio -P

=== Mot de passe administrateur ===

Définissez un [[mot de passe]] sécurisé pour l'[[Wikipedia:fr:Utilisateur root|utilisateur root]] afin de permettre l'exécution d'actions administratives ::

# passwd

=== Installation d'un chargeur d'amorçage ===

Choisissez un chargeur d'amorçage adapté à votre schéma de partitionnement et installez-le. Consultez les explications et le tableau comparatif dans [[Arch boot process (Français)#Comparaison des fonctionnalités]] pour faire votre choix, puis suivez les instructions d'installation sur la page qui lui est dédiée.

== Redémarrer ==

Sortez de l'environnement ''chroot'' en tapant ({{ic|exit}} ou par le raccourci {{ic|Ctrl+d}}).

Si vous le souhaitez, démontez manuellement toutes les partitions avec {{ic|umount -R /mnt}} : cela permet de détecter les partitions "occupées" et d'en trouver la cause avec {{man|1|fuser}}.

Enfin, redémarrez la machine en tapant {{ic|reboot}} : toutes les partitions encore montées seront automatiquement démontées par ''systemd''. N'oubliez pas de retirer le support d'installation et vous pourrez vous connecter au nouveau système avec le compte root.

== Après le redémarrage ==

Consultez les [[General recommendations (Français)|Recommandations générales]] pour des indications sur l'administration de votre système et des tutoriels de post-installation (comme la création de comptes utilisateurs non privilégiés, la configuration d'une interface utilisateur graphique, du son ou d'un pavé tactile).

Pour une liste des applications pouvant présenter un intérêt, voir la [[List of applications|liste des applications]].

Installation guide (Français)

2026-05-15T09:43:03Z

Erus Iluvatar: Update translation

[[Category:Installation process (Français)]]
[[ar:Installation guide]]
[[bg:Installation guide]]
[[ca:Installation guide]]
[[cs:Installation guide]]
[[de:Arch Install Scripts]]
[[el:Installation guide]]
[[en:Installation guide]]
[[es:Installation guide]]
[[fi:Installation guide]]
[[hu:Installation guide]]
[[it:Installation guide]]
[[ja:インストールガイド]]
[[ko:Installation guide]]
[[lv:Installation guide]]
[[pl:Installation guide]]
[[pt:Installation guide]]
[[ru:Installation guide]]
[[sv:Installation guide]]
[[th:Installation guide]]
[[tr:Installation guide]]
[[uk:Installation guide]]
[[zh-hans:安装指南]]
[[zh-hant:Installation guide]]
{{TranslationStatus (Français)|Installation guide|2026-05-15|870170}}

Ce document est un guide pour l'installation d'[[Arch Linux (Français)|Arch Linux]] au moyen du système « live » Archiso démarré depuis le support d'installation issue des images officielles. Le support d'installation offre des fonctionnalités d'accessibilité décrites à la page [[Install Arch Linux with accessibility options (Français)|Installer Arch Linux avec les options d'accessibilité]]. Pour les autres moyens d'installation, consultez [[:Category:Installation process (Français)]].

Avant installation, il est conseillé de consulter la [[Frequently asked questions (Français)|FAQ]]. Pour les conventions utilisées dans ce document, voir [[Help:Reading (Français)|l'aide à la lecture]]. En particulier, les exemple de code contiennent parfois des champs (notés en {{ic|''italique''}}) que vous devez modifier manuellement.

Ce guide est rédigé de manière concise et il vous est conseillé de suivre les instructions dans l'ordre présenté pour chaque section. Pour de plus amples instructions, se référer aux articles respectifs du [[ArchWiki]] ainsi que les [[man page|pages de manuel]] en liens dans ce guide. Pour une aide interactive, le [[Arch IRC channels (Français)|Canal IRC francophone]] ainsi que le [https://forums.archlinux.fr forum francophone] (ou le [https://bbs.archlinux.org/ forum international] pour les bilingues) sont disponibles.

Arch Linux devrait fonctionner sur n'importe quelle machine utilisant l'architecture [[Wikipedia:fr:X86-64|x86_64]] dotée d'un minimum de 512 MiB de RAM, bien que plus de mémoire soit nécessaire pour démarrer le système « live » en vue de l'installation. [https://lists.archlinux.org/archives/list/arch-releng@lists.archlinux.org/message/D5HSGOFTPGYI6IZUEB3ZNAX4D3F3ID37/] Une installation basique devrait utiliser moins de 2 GiB d'espace disque. Enfin, le processus d'installation nécessitant le téléchargement de paquets depuis un dépôt distant, ce guide considère qu'une connexion Internet est disponible.

== Préparation avant l'installation ==

=== Obtenir l'image d'installation ===

Visitez la page de [https://archlinux.org/download/ Téléchargement] et, selon la façon dont vous voulez démarrer, récupérez l'image ISO ou bien l'image «netboot» ainsi que la signature PGP correspondante.

=== Vérifier la signature ===

Il est recommandé de vérifier la signature de l'image avant de l'utiliser, particulièrement lors du téléchargement depuis un ''miroir HTTP'', puisque ceux-ci sont sujet à être interceptés pour [https://www2.cs.arizona.edu/stork/packagemanagersecurity/attacks-on-package-managers.html fournir des fichiers malveillants].

Téléchargez la ''signature PGP de l'ISO'' depuis https://archlinux.org/download/#checksums dans le répertoire contenant l'ISO et suivez les instructions sur la page pour la vérifier.

Depuis une installation Arch Linux existante, vous pouvez également utiliser la commande:

$ pacman-key -v archlinux-''version''-x86_64.iso.sig

{{Note|
* La signature elle-même pourrait être manipulée si elle est téléchargée à partir d'un site miroir, au lieu de l'être à partir de [https://archlinux.org/download/ archlinux.org]. Dans ce cas, assurez-vous que la clé publique, qui est utilisée pour décoder la signature, soit signée par une autre clé digne de confiance. La commande {{ic|gpg}} affichera l'empreinte de la clé publique.
* Une autre méthode pour vérifier l'authenticité de la signature consiste à s'assurer que l'empreinte de la clé publique est identique à l'empreinte de la clé du [https://archlinux.org/people/developers/ développeur Arch Linux] qui a signé le fichier ISO. Voir [[Wikipedia:fr:Cryptographie asymétrique]] pour plus d'informations sur le processus d'authentification des clés par une clé publique.}}

=== Préparer un support d'installation ===

L'ISO peut être déployée sur la machine concernée via une [[USB flash installation medium (Français)|clé USB]], un [[Optical disc drive#Burning|disque optique]], ou par réseau avec [[PXE]] : consultez l'article approprié pour préparer vous-même un support d'installation avec le fichier ISO.

Pour une image "Netboot", suivez [[Netboot#Boot from a USB flash drive]] pour préparer une clé USB pour un démarrage UEFI.

=== Démarrer l'environnement « live » ===

{{note|Les images d'Arch Linux ne prennent pas en charge la technologie ''Secure Boot'' et vous devrez [[Unified Extensible Firmware Interface/Secure Boot#Disabling Secure Boot|la désactiver]] pour démarrer depuis le support d'installation. Vous pourrez si vous le souhaitez le configurer une fois l'installation terminée, en suivant ces [[Secure Boot|instructions]].}}

# Choisissez le périphérique de démarrage pour utiliser le support préparé précédemment. Généralement, la manipulation consiste à appuyer sur une touche — fréquemment mentionnée sur l'écran d'accueil de votre machine — durant le [[Wikipedia:fr:Power-on self-test (informatique)|POST]]. Référez-vous au manuel de votre carte mère pour plus de détails.
# Lorsque le menu du support d'installation apparaît,
#* si vous avez utilisé l'ISO, sélectionnez ''Arch Linux install medium'' et validez avec la touche {{ic|Entrée}}.
#* si vous avez utilisé l'image "Netboot", choisissez un miroir géographiquement proche depuis le menu ''Mirror'' et valiez avec la touche {{ic|Entrée}}. {{Astuce|
#** L'ISO utilise [[systemd-boot (Français)|systemd-boot]] pour démarrer sur les UEFI et [[syslinux (Français)|syslinux]] sur les BIOS. Utilisez respectivement {{ic|e}} ou {{ic|Tab}} pour ajouter des [[Kernel parameters#Boot loader configuration|paramètres de démarrage]]. L'image "Netboot" utilise iPXE et les paramètres de démarrage peuvent être choisis dans le menu ''Boot Options''. Consultez [https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio-archiso/blob/master/docs/README.bootparams /usr/share/doc/mkinitcpio-archiso/README.bootparams] pour une liste des paramètres de démarrage.
#** Un exemple typique de paramètre de démarrage à saisir manuellement est la taille de la police. Pour une meilleure lecture sur des écrans à haut DPI, s'il ne sont pas reconnus comme tels, {{ic|1=fbcon=font:TER16x32}} peut aider. Consultez [[HiDPI#Linux console (tty)]] pour des explications détaillées.}}
# Vous serez connecté dans la première [[Wikipedia:fr:Terminal (informatique)|console virtuelle]] sous l'utilisateur ''root'' et vous verrez une invite de commande [[zsh (Français)|zsh]]

Pour changer de console — par exemple pour consulter ce guide avec [https://lynx.invisible-island.net/lynx_help/Lynx_users_guide.html Lynx] pendant l'installation — vous pouvez utiliser le [[Linux console#Keyboard shortcuts|raccourci clavier]] {{ic|Alt+''flèches de direction''}}. Pour [[modifier]] les fichiers de configuration, {{man|1|mcedit}}, [[nano (Français)#Utilisation|nano]] et [[Vim#Usage|vim]] sont disponibles. Voir [https://geo.mirror.pkgbuild.com/iso/latest/arch/pkglist.x86_64.txt pkglist.x86_64.txt] pour consulter la liste des paquets inclus dans le support d'installation.

=== Disposition du clavier en console et de la police de caractères ===

[[Linux console (Français)/Keyboard configuration (Français)|La disposition]] par défaut est le clavier [[Wikipedia:File:KB United States-NoAltGr.svg|US]]. Les dispositions disponibles peuvent être listées par :

# localectl list-keymaps

Pour modifier la disposition du [[:category:Keyboard configuration (Français)|clavier]], passez son nom à {{man|1|loadkeys}}. Par exemple pour la disposition [[Wikipedia:File:Clavier-Azerty.svg|Française]] vous pouvez utiliser :

# loadkeys fr-latin1

[[Console fonts|Les polices de la console]] se trouvent dans {{ic|/usr/share/kbd/consolefonts/}} et peuvent de même être utilisées avec {{man|8|setfont}} en omettant les chemin et extension du fichier. Par exemple, pour utiliser l'une des plus larges polices adaptées aux [[HiDPI#Linux console (tty)|écrans HiDPI]], exécutez :

# setfont ter-132b

=== Vérifier le mode de démarrage ===

Pour vérifier le mode de démarrage, vérifiez le [[Unified Extensible Firmware Interface#UEFI firmware bitness|nombre de bits de l'UEFI]] :

# cat /sys/firmware/efi/fw_platform_size

* Si la commande renvoie {{ic|64}}, le système est démarré en mode UEFI et dispose d'un UEFI x64 64 bits.
* Si la commande renvoie {{ic|32}}, le système est démarré en mode UEFI et dispose d'un UEFI IA32 32 bits. Bien que cela soit pris en charge, cela limitera le choix du chargeur d'amorçage à ceux qui prennent en charge le démarrage en mode mixte.
* Si elle renvoie {{ic|No such file or directory}}, le système peut être démarré en mode [[Wikipedia:fr:BIOS (informatique)|BIOS]] (ou [[Wikipedia:fr:UEFI#Architecture UEFI|CSM]]). Si le système n'a pas démarré dans le mode souhaité (UEFI vs BIOS), reportez-vous au manuel de votre carte mère.

=== Connexion à Internet ===

Pour configurer la connexion réseau dans l'image « live », suivez ces étapes :

# Vérifiez que votre [[Network configuration (Français)|carte réseau]] est répertoriée et activée, par exemple avec {{man|8|ip-link}}: {{bc|# ip link}}
# Pour les connections sans fil comme le ''Wi-Fi'' ou les [[Wikipedia:fr:Réseau de téléphonie mobile|réseaux mobiles (4G...)]], vérifiez que l'utilitaire [[rfkill]] ne bloque pas l'interface.
# Connectez-vous au réseau:
#* Ethernet—Branchez le câble.
#* Wi-Fi—Authentifiez-vous sur le réseau sans fil avec [[iwctl]].
#* Réseaux mobiles—Connectez-vous au réseau avec l'utilitaire [[mmcli]].
# Configurez votre connexion réseau:
#* [[DHCP]]: l'adressage dynamique des adresses IP et des serveurs DNS (fourni par [[systemd-networkd (Français)|systemd-networkd]] et [[systemd-resolved (Français)|systemd-resolved]] devraient fonctionner par défaut) pour les protocoles [https://gitlab.archlinux.org/archlinux/archiso/-/blob/master/configs/releng/airootfs/etc/systemd/network/20-ethernet.network Ethernet], [https://gitlab.archlinux.org/archlinux/archiso/-/blob/master/configs/releng/airootfs/etc/systemd/network/20-wlan.network Wi-Fi] and [https://gitlab.archlinux.org/archlinux/archiso/-/blob/master/configs/releng/airootfs/etc/systemd/network/20-wwan.network Mobiles].
#* Adresse IP statique : suivez [[Network configuration#Static IP address]].
# La connexion peut être confirmée avec [[ping]]: {{bc|# ping ping.archlinux.org}}

{{Note|Dans l'image d'installation, [[systemd-networkd (Français)|systemd-networkd]], [[systemd-resolved (Français)|systemd-resolved]], [[iwd]] et [[ModemManager]] sont préconfigurés et activés par défaut. Ce ne sera pas le cas du système installé.}}

=== Mise à jour de l'horloge système ===

Le système « live » a besoin de l'heure précise pour éviter les erreurs de vérification de signature des paquets et les erreurs de certificat TLS. Le service [[systemd-timesyncd (Français)|systemd-timesyncd]] est activé par défaut dans l'environnement « live » et l'heure sera synchronisée automatiquement dès qu'une connexion à Internet sera établie.

Utilisez {{man|1|timedatectl}} pour vous assurer que l'horloge système est correctement synchronisée.

# timedatectl

=== Partitionnement des disques ===

Une fois reconnus par le système « live », les disques se verront affectés un [[block device|périphérique de type bloc]] tel que {{ic|/dev/sda}}, {{ic|/dev/nvme0n1}} ou {{ic|/dev/mmcblk0}}. Pour identifier ces périphériques, utilisez [[lsblk]] ou ''fdisk''.

# fdisk -l

Les résultats se terminant par {{ic|rom}}, {{ic|loop}} ou {{ic|airootfs}} peuvent être ignorés. Les appareils {{ic|mmcblk*}} se terminant par {{ic|rpmb}}, {{ic|boot0}} et {{ic|boot1}} peuvent être ignorés.

{{Note|Si le disque n'apparaît pas, [[Partitioning#Drives are not visible when firmware RAID is enabled|assurez-vous que le contrôleur de disque n'est pas en mode RAID]].}}

{{Astuce|Vérifiez que vos disques NVMe et vos disques durs au format avancé utilisent la [[Advanced Format|taille optimale du secteur logique]] avant le partitionnement.}}

Les [[partition]]s suivantes sont '''nécessaires''' sur un périphériques choisi:

* Une partition [[Wikipedia:fr:Répertoire racine|racine]] {{ic|/}}.
* Pour démarrer en mode [[UEFI]]: une [[EFI system partition (Français)|partition EFI]].

* Utilisez un [[Partitioning#Partitioning tools|outil de partitionnement]] comme [[fdisk]] pour modifier la table de partitions. Par exemple :
# fdisk ''/dev/disque_en_question''

{{Note |
* Prenez le temps de planifier un schéma de partitionnement à long terme afin d'éviter les conversions ou re-partitionnement risquées et compliquées dans le futur.
* Si vous souhaitez utiliser [[Install Arch Linux on LVM|LVM]], [[dm-crypt (Français)|un chiffrement de votre système]] ou encore [[RAID (Français)|RAID]], faites le maintenant.
* Si le disque depuis lequel vous souhaitez démarrer [[EFI system partition (Français)#Vérifier s'il y a une partition existante|possède déjà une partition EFI]], n'en recréez pas une autre mais utilisez la partition pré-existante.
* La [[Swap (Français)|Swap]] peut être définie sur un [[Swap (Français)#Fichier d'échange|fichier d'échange]] pour les systèmes de fichier qui le prennent en charge. Alternativement, de la swap basée sur le disque peut être évitée entièrement en configurant la [[zram#Usage as swap|swap sur zram]] après avoir installé le système.
}}

==== Exemples de partitionnement ====

{| class="wikitable"
|+ UEFI avec [[GPT]]
|-
! Point de montage sur le système installé
! Partition
! [[Wikipedia:fr:GUID Partition Table#GUID des types de partition|Type de partition]]
! Taille suggérée
|-
| {{ic|/boot}}1
| {{ic|/dev/''efi_system_partition''}}
| [[EFI system partition (Français)|EFI system partition]]
| 1 GiB
|-
| {{ic|[SWAP]}}
| {{ic|/dev/''partition_d'échange''}}
| Linux swap
| Au moins 4 GiB
|-
| {{ic|/mnt}}
| {{ic|/dev/''partition_racine''}}
| Linux x86-64 root (/)
| Le reste du disque. Au moins 23 à 32 GiB.
|}

# [[EFI system partition (Français)#Points de montage habituels|D'autres points de montage]], tels que {{ic|/efi}} sont possible, sous réserve que que si le chargeur d'amorçage utilisé soit capable de charger le [[Kernel (Français)|noyau]] et l'[[Arch boot process (Français)#Initramfs|initramfs]] directement depuis la partition racine. Voir l'avertissement dans [[Arch boot process (Français)#Chargeur d'amorçage]].

{| class="wikitable"
|+ BIOS avec [[MBR]]
|-
! Point de montage sur le système installé
! Partition
! [[Wikipedia:Partition type|Type de partition]]
! Taille suggérée
|-
| {{ic|[SWAP]}}
| {{ic|/dev/''partition_d'échange''}}
| Linux swap
| Au moins 4 GiB
|-
| {{ic|/mnt}}
| {{ic|/dev/''partition_racine''}}
| Linux
| Le reste du disque. Au moins 23 à 32 GiB.
|}

Pour d'autres exemples: [[Partitioning#Example layouts]].

=== Formatage des partitions ===

Une fois les partitions crées, celles-ci doivent être formatées avec un [[File systems|système de fichier]] approprié. Consultez [[File systems#Create a file system]] pour plus de détails.

Par exemple, pour créer un système de fichier [[Ext4 (Français)|ext4]] sur {{ic|/dev/''partition_racine''}}, utilisez :

# mkfs.ext4 /dev/''partition_racine''

Si vous avez crée une partition [[swap (Français)|d'échange]], initialisez la avec {{man|8|mkswap}}:

# mkswap /dev/''partition_d'échange''

{{Note|Pour les configurations avec LVM, chiffrement ou RAID, remplacez {{ic|/dev/''*_partition''}} par le chemin vers le périphérique de type bloc approprié.}}

Si vous avez créé une partition système EFI, [[EFI system partition (Français)#Formater la partition|formatez-la]] en FAT32 avec {{man|8|mkfs.fat}}.

{{Attention|Ne formatez la partition système EFI que si vous l'avez créée pendant le partitionnement. S'il y avait déjà une partition système EFI sur le disque précédemment, son formatage peut détruire les chargeurs d'amorçage des autres systèmes d'exploitation installés.}}

# mkfs.fat -F 32 /dev/''efi_system_partition''

=== Montage des systèmes de fichiers ===

[[Mount|Montez]] la partition racine dans {{ic|/mnt}}. Par exemple, si la partition racine est {{ic|/dev/''partition_racine''}}:

# mount /dev/''partition_racine'' /mnt

Créez chaques points de montage restants dans {{ic|/mnt}} (tels que {{ic|/mnt/boot}} pour {{ic|/boot}}) et montez les volumes dans l'ordre hiérarchique correspondant.

{{Astuce|Utilisez {{man|8|mount}} avec l'option {{ic|--mkdir}} pour créer le point de montage spécifié. Vous pouvez également le créer au préalable à l'aide de {{man|1|mkdir}}.}}

Pour les systèmes avec un UEFI, montez la partition système EFI. Par exemple :

# mount --mkdir /dev/''efi_system_partition'' /mnt/boot

Si vous avez créé une partition [[swap (Français)|d'échange]], activez-la avec {{man|8|swapon}}:

# swapon /dev/''partition_d'échange''

{{man|8|genfstab}} détectera plus tard les systèmes de fichiers et l'espace d'échange montés.

== Installation ==

=== Sélection du miroir ===

Les paquets à installer doivent être téléchargés depuis les [[Mirrors (Français)|miroirs]] des dépôts officiels tels que définis dans {{ic|/etc/pacman.d/mirrorlist}}. Plus le miroir se trouve haut dans la liste, plus grande est sa priorité lors du téléchargement d'un paquet.

Sur le système « live », tous les miroirs HTTPS sont activés (c'est-à-dire non commentés). Le miroir mondial le plus haut dans la liste devrait être suffisamment rapide pour la plupart des utilisateurs, mais vous pouvez tout de même vérifier le fichier pour vous assurer qu'il vous convient. Si ce n'est pas le cas, [[modifiez]] le fichier en conséquence et placez les miroirs les plus proches géographiquement en haut de la liste, bien que d'autres critères sont à prendre en compte. Vous pouvez également utiliser [[Reflector (Français)|reflector]] pour créer le fichier de liste de miroirs en fonction de différents critères.

''pacstrap'' copiera plus tard ce fichier sur le nouveau système, prendre votre temps sur cette étape peut donc vous en faire gagner plus tard.

=== Installation des paquets essentiels ===

Aucune configuration (à l'exception de {{ic|/etc/pacman.d/mirrorlist}}) n'est transféré de l'environnement « live » vers le système installé. Le seul paquet obligatoire est {{Pkg|base}}, qui '''n'inclut pas''' tous les outils de l'installation « live », donc l'installation d'autres paquets est fréquemment nécessaire.

En particulier, examinez les logiciels suivants et installez tout ce dont vous avez besoin :

* les mises-à-jour du [[microcode]] du processeur ({{Pkg|amd-ucode}} ou {{Pkg|intel-ucode}}) pour les corrections de bogues matériels et de sécurité,
* les utilitaires nécessaires à la gestion des [[File system|systèmes de fichiers]],
* les [[File systems|utilitaires en espace utilisateur pour les systèmes de fichiers]] qui seront utilisés pour, par exemple, la création de système de fichiers et [[fsck (Français)|fsck]],
* les utilitaires pour accéder ou gérer les partitions [[RAID (Français)|RAID]] ou [[LVM (Français)|LVM]] s'ils sont utilisés sur le système,
* les [[firmware|microprogrammes]] spécifiques à des périphériques qui ne seraient pas déjà inclus dans {{Pkg|linux-firmware}} (comme {{Pkg|sof-firmware}} pour [[Advanced Linux Sound Architecture (Français)#Microprogramme ALSA|l'audio de la carte mère]], {{Pkg|linux-firmware-marvell}} pour les puces Marvell sans fil et l'un des multiples packages de micrologiciels pour les [[Broadcom wireless|puces sans-fil Broadcom]]),
* les logiciels nécessaires à la [[Network configuration (Français)|connexion au réseau]] (par exemple, un [[Network configuration (Français)#Network managers|gestionnaire de réseau ou un client DHCP autonome]], un [[Network configuration/Wireless#Authentication|logiciel d'authentification]] pour le Wi-Fi, un [[ModemManager|gestionnaire de modem]] pour les réseaux mobiles),
* un [[List of applications/Documents#Console|éditeur de texte en console]] (tel que [[nano (Français)|nano]]) pour permettre la modification fichiers de configuration depuis la console,
* les paquets de documentation comme {{Pkg|man-db}}, {{Pkg|man-pages}} et {{Pkg|texinfo}}.

Vous pouvez comparer avec la liste des paquets disponibles sur le média d'installation : [https://geo.mirror.pkgbuild.com/iso/latest/arch/pkglist.x86_64.txt pkglist.x86_64.txt].

Pour installer d'autres paquets ou groupes de paquets, ajoutez leurs noms à la commande {{man|8|pacstrap}} ci-dessous (séparés par des espaces) ou utilisez [[pacman (Français)|pacman]] pour les [[installer]] pendant que vous êtes [[#Chroot|«chroot»é dans votre nouvelle installation]].

Par exemple, un système basique avec le [[Kernel (Français)|noyau]] et le microprogramme pour les périphériques les plus courants:

# pacstrap -K /mnt base linux linux-firmware

{{Astuce|
* Vous pouvez remplacer {{Pkg|linux}} par un autre noyau de votre choix ou l'omettre pour l'installation dans un [[Wikipedia:Container (virtualization)|container]].
* Vous pouvez également omettre le microprogramme si vous installez dans une machine virtuelle un container.
* Cette sélection initiale de paquets dans pacstrap n'est obligée d'inclure que ce qui est nécessaire au démarrage du système ; tous les autres logiciels peuvent être installés ou remplacés après l'installation.
}}

== Configuration du système ==

=== Fstab ===

Pour monter les systèmes de fichiers nécessaires (comme celui utilisé pour le répertoire de démarrage {{ic|/boot}}) au démarrage, générez un fichier [[Fstab (Français)|fstab]] avec un [[[[Persistent block device naming (Français)|nommage persistent des périphériques de type bloc]] au moyen de {{man|8|genfstab}}. Par exemple, référencez les partitions par leur [[Persistent block device naming (Français)#by-uuid|UUID]] avec {{ic|-U}} :

# genfstab -U /mnt >> /mnt/etc/fstab

Vérifiez le fichier {{ic|/mnt/etc/fstab}} obtenu, et modifiez-le en cas d'erreur.

=== Chroot ===

Pour interagir directement avec l'environnement, les outils et les configurations du nouveau système pour les étapes suivantes, comme si vous aviez démarré dessus, [[Chroot (Français)|chrootez]] dans le nouveau système:

# arch-chroot /mnt

{{Note|Certains outils de [[systemd (Français)|systemd]] tels que {{man|1|hostnamectl}}, {{man|1|localectl}} et {{man|1|timedatectl}} ne peuvent pas être utilisés à l'intérieur d'un {{man|1|chroot}}, car ils nécessitent une connexion [[dbus]] active. [https://github.com/systemd/systemd/issues/798#issuecomment-126568596]}}

=== Heure ===

Pour plus de commodité (par exemple, pour afficher l'heure locale correcte ou gérer l'heure d'été), définissez le [[System time (Français)#Fuseau horaire|fuseau horaire]], par exemple pour la France:

# ln -sf /usr/share/zoneinfo/Europe/Paris /etc/localtime

Lancez {{man|8|hwclock}} pour générer {{ic|/etc/adjtime}}:

# hwclock --systohc

Cette commande repose sur l'hypothèse que l'horloge matérielle est réglée sur [[Wikipedia:fr:UTC|UTC]]. Consultez [[System time (Français)#Standard de temps]] pour plus de détails.

Pour éviter la dérive de l'horloge et garantir une heure précise, configurez la [[System time (Français)#Synchronisation du temps|synchronisation du temps]] à l'aide d'un client [[Wikipedia:fr:Network Time Protocol|Network Time Protocol]] (NTP) tel que [[systemd-timesyncd (Français)|systemd-timesyncd]].

=== Locales ===

Pour utiliser le formatage spécifique à la région et à la langue (comme les dates, la devise, les séparateurs décimaux), [[modifiez]] {{ic|/etc/locale.gen}} et décommentez les [[Locale (Français)|locale]]s UTF-8 que vous utiliserez. Générez les locales en exécutant:

# locale-gen

[[Créez]] le fichier {{man|5|locale.conf}} et [[Locale (Français)#Définir la locale système|définissez la variable LANG]] correspondante :

{{hc|1=/etc/locale.conf|2=
LANG=''fr_FR.UTF-8''
}}

Éditez le fichier {{man|5|vconsole.conf}} afin d'y spécifier la [[Linux console (Français)/Keyboard configuration (Français)#Visualiser les configurations du clavier|disposition de clavier]] ainsi que la police de caractères que vous souhaitez conserver :

{{hc|1=/etc/vconsole.conf|2=
KEYMAP=''fr-latin1''
}}

=== Configuration réseau ===

Pour attribuer un nom unique et identifiable à votre système (particulièrement utile dans un environnement réseau), [[créez]] le fichier [[Network configuration#Set the hostname|hostname]] :

{{hc|/etc/hostname|
''lenomdevotremachine''
}}

{{Astuce|Pour obtenir des conseils sur le choix d'un nom d'hôte, consultez la [[RFC:1178|RFC 1178]]. Comme expliqué dans {{man|7|hostname}}, il doit contenir entre 1 et 63 caractères, en utilisant uniquement les lettres minuscules {{ic|a}} à {{ic|z}}, les chiffres {{ic|0}} à {{ic|9}} et le signe {{ic|-}}, et ne doit pas commencer par {{ic|-}}.}}

Terminez la [[Network configuration (Français)|configuration du réseau]] pour le nouvel environnement installé. Cela peut inclure l'installation d'un logiciel de [[network management|gestion de réseau]] approprié, sa configuration si nécessaire et l'activation de son unité systemd pour son lancement au démarrage de la machine.

=== Initramfs ===

La création d'un nouvel ''initramfs'' n'est généralement pas nécessaire, car [[mkinitcpio (Français)|mkinitcpio]] a été lancé lors de l'installation du [[Kernel (Français)|noyau]] avec ''pacstrap''.

Pour [[Install Arch Linux on LVM#Adding mkinitcpio hooks|LVM]], le [[Dm-crypt (Français)|chiffrement]] ou [[RAID#Configure mkinitcpio|RAID]], modifiez {{man|5|mkinitcpio.conf}} et recréez l'image ''initramfs''. Si vous avez [[#Locales|modifié la configuration par défaut du clavier de la console]], seul recréer l'initramfs est nécessaire :

# mkinitcpio -P

=== Mot de passe administrateur ===

Définissez un [[mot de passe]] sécurisé pour l'[[Wikipedia:fr:Utilisateur root|utilisateur root]] afin de permettre l'exécution d'actions administratives ::

# passwd

=== Installation d'un chargeur d'amorçage ===

Choisissez un chargeur d'amorçage adapté à votre schéma de partitionnement et installez-le. Consultez les explications et le tableau comparatif dans [[Arch boot process (Français)#Comparaison des fonctionnalités]] pour faire votre choix, puis suivez les instructions d'installation sur la page qui lui est dédiée.

== Redémarrer ==

Sortez de l'environnement ''chroot'' en tapant ({{ic|exit}} ou par le raccourci {{ic|Ctrl+d}}).

Si vous le souhaitez, démontez manuellement toutes les partitions avec {{ic|umount -R /mnt}} : cela permet de détecter les partitions "occupées" et d'en trouver la cause avec {{man|1|fuser}}.

Enfin, redémarrez la machine en tapant {{ic|reboot}} : toutes les partitions encore montées seront automatiquement démontées par ''systemd''. N'oubliez pas de retirer le support d'installation et vous pourrez vous connecter au nouveau système avec le compte root.

== Après le redémarrage ==

Consultez les [[General recommendations (Français)|Recommandations générales]] pour des indications sur l'administration de votre système et des tutoriels de post-installation (comme la création de comptes utilisateurs non privilégiés, la configuration d'une interface utilisateur graphique, du son ou d'un pavé tactile).

Pour une liste des applications pouvant présenter un intérêt, voir la [[List of applications|liste des applications]].

ArchWiki:Translation Team (Български)

2026-05-14T16:42:06Z

Erus Iluvatar: Let's redirect to the English page instead of having a blank page

#REDIRECT [[ArchWiki:Translation Team]]

Razer peripherals

2026-05-14T16:39:38Z

Erus Iluvatar: fix external link + misc spacing/newlines

[[Category:Mice]]
[[Category:Keyboards]]
[[ja:Razer]]

{{Note|This page refers to Razer's mice and keyboards. If you were looking for the laptop, see [[Razer Blade]].}}

[[Wikipedia:Razer Inc|Razer Inc]] makes gaming-focused computer hardware and other consumer electronics. There are currently no official drivers for any Razer peripherals in Linux.

Projects like [https://bues.ch/cms/hacking/razercfg.html razercfg], [https://openrazer.github.io/ OpenRazer] can be used to enable Razer support.

There is also the [https://openrgb.org/ OpenRGB] project which aims to have manufacturer agnostic lighting configurations.

== OpenRGB ==

See [[OpenRGB]].

== razercfg ==

=== Compatibility ===
A list of compatible devices can be found [https://bues.ch/cms/hacking/razercfg.html#device_support here].

=== Installation ===

[[Install]] the {{AUR|razercfg}} package.

[[Enable]] and [[start]] the {{ic|razerd}} service.

{{Tip|The package installs udev rules, it is advised to [[Udev#Loading new rules|reload]] them after installation or to reboot.}}

=== Configuration ===

The file {{ic|/etc/razer.conf}} can be
used to specify various razerd options and initial hardware configuration settings. An example config file is included as {{ic|razer.conf}} in the package.

If no configuration file is available, razerd will work with default settings.

{{Note|On X11, you may also need to edit your {{ic|/etc/X11/xorg.conf}} file to disable the current mouse settings by commenting them out as in the following example, where also some defaults are set as suggested by the author:

{{hc|/etc/X11/xorg.conf|
Section "InputDevice"
Identifier "Mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
EndSection}}

It is important to only have {{ic|Mouse}} and not {{ic|Mouse#}} listed in {{ic|xorg.conf}}.}}

==== Using the Razer Configuration Tool ====

There are two tools provided, one CLI: ''razercfg'' and a Qt-based GUI: ''qrazercfg''.

With either tool you can set 5 profiles, change the DPI, change mouse frequency, enable and disable the scroll and logo lights and configure the buttons.

If settings change on reboot, edit the configuration file directly and test after a [[reload]] of the service is done. For example:

{{hc|/etc/razer.conf|
# Configure LEDs
led<nowiki>=</nowiki>1:GlowingLogo:on
led<nowiki>=</nowiki>1:Scrollwheel:on
mode<nowiki>=</nowiki>1:Scrollwheel:static
color<nowiki>=</nowiki>1:Scrollwheel:0000FF
mode<nowiki>=</nowiki>1:GlowingLogo:static
color<nowiki>=</nowiki>1:GlowingLogo:FFFFFF
}}

== OpenRazer ==

=== Compatibility ===

A list of compatible devices can be found [https://openrazer.github.io/#devices here].

=== Installation ===

[[Install]] the {{Pkg|openrazer-daemon}} package. Add your current user to the [[user group]] {{ic|openrazer}} before logging out and back in.

If customizing and configuring devices is not the priority, one can install just the {{Pkg|openrazer-driver-dkms}} package instead.

=== How to use ===

====CLI====
The {{AUR|razer-cli}} can be used to configure devices via the terminal.
====GUI====
The recommended way is to use a graphical front-end for interfacing with the drivers.

* {{AUR|polychromatic}}: A Qt-based (Python) front-end with effect editor
* {{AUR|razergenie}}: A Qt-based front-end with custom editor
* {{AUR|razercommander-git}}: A GTK-based front-end
* [http://bithatch.co.uk/snake.html Snake]: A front-end able to bind mouse buttons + keyboard

=== Troubleshooting ===

Visit the [https://github.com/openrazer/openrazer/wiki/Troubleshooting Troubleshooting page] in the OpenRazer wiki.

== Razer keyboards ==

There are currently two Python scripts available to enable the extra M1 - M5 macro keys, that certain Razers have, under Linux:
Note that this does not allow to assign any content to Macro keys, it merely will enable the sending of keycodes. For Razers without M1 -M5 extra keys there is no point using this tool.

=== Blackwidow Control ===

==== Features ====

* confirmed to work with regular BlackWidow, BlackWidow 2013 and BlackWidow Ultimate Stealth 2014
* should also work with BlackWidow Ultimate, BlackWidow Ultimate 2013 and BlackWidow 2014
* does not work with BlackWidow (Ultimate) 2016 yet
* uses Python 3
* allows to control the status of the LED
* contains a file with udev rule so macro keys will be enabled automatically when the keyboard is plugged in

==== How to Use ====

[[Install]] {{AUR|blackwidowcontrol}}. After install, run:

# blackwidowcontrol -i

Then use the shortcut utility of your Desktop Environment to map the keys, i.e. to actually use the macro keys for something useful. For example, the "KDE global shortcuts" GUI (find it in system settings) can assign macros to a key on any keyboard, not just Razers.

=== Blackwidow macro scripts ===

==== Features ====

* Works with BlackWidow Ultimate and Stealth 2013 (unknown whether it works with other versions or keyboard models)
* adding the "021e" ID for Ornata Chroma makes the Game-mode feature (white "G" LED) work on Ornata Chroma as well.
* Uses Python 2
* Bundles scripts to create and execute macros

== Troubleshooting ==

=== Mouse randomly stops working ===

{{Note|This is tested on [[ASUS N550JV]] using mouse '''Razer Orochi 2013'''. Laptop probably has faulty charging port and therefore it sometimes directly affects connected mouse USB port and causes similar issues.}}

If your razer mouse stops working after some time, however, led flashes or lights up, but reboot and re-plugging does not help, try the following commands.

Unload {{ic|ehci_pci}} and {{ic|ehci_hcd}} modules:

# rmmod ehci_pci
# rmmod ehci_hcd

Disconnect the mouse, wait a few seconds and run the following commands to load modules back:

# modprobe ehci_hcd
# modprobe ehci_pci

Connect the mouse and it should be working.

=== CAPS Lock makes Razer Blade Stealth crash ===

The crash is caused by keyboard built-in driver.

==== If using Xorg ====

Get the keyboard description:

$ xinput list | grep "Set 2 keyboard"

And create the file below, here we assume the above command returned "AT Raw Set 2 keyboard".

{{hc|/etc/X11/xorg.conf.d/00-keyboard-razer.conf|
Section "InputClass"
Identifier "Disable built-in keyboard"
MatchProduct "AT Raw Set 2 keyboard"
Option "Ignore" "true"
EndSection
}}

==== If using Xwayland ====

{{hc|/etc/default/keyboard|
XKBOPTIONS<nowiki>=</nowiki>"ctrl:nocaps"}}

CAPS Lock will now be identified as another CTRL key.

Source: https://github.com/rolandguelle/razer-blade-stealth-linux/blob/master/ubuntu-18-04.md#13-caps-lock-crash

Dotfiles

2026-05-14T14:47:22Z

Erus Iluvatar: Partial revert of the previous edit: internal redirects are fine

{{Lowercase title}}
[[Category:Configuration files]]
[[Category:Configuration management]]
[[es:Dotfiles]]
[[hu:Dotfiles]]
[[ja:ドットファイル]]
[[pt:Dotfiles]]
[[zh-hans:Dotfiles]]
{{Related articles start}}
{{Related|XDG Base Directory support}}
{{Related|X resources}}
{{Related articles end}}

User-specific application configuration is traditionally stored in so called [[Wikipedia:Hidden file and hidden directory#Unix and Unix-like environments|dotfiles]] (files whose filename starts with a dot). It is common practice to track dotfiles with a [[version control system]] such as [[Git]] to keep track of changes and synchronize dotfiles across various hosts. There are various approaches to managing dotfiles (e.g. directly tracking dotfiles in the home directory v.s. storing them in a subdirectory and symlinking/copying/generating files with a [[shell]] script or [[#Tools|a dedicated tool]]). Apart from explaining how to manage dotfiles this article also contains [[#User repositories|a list of dotfile repositories]] from Arch Linux users.

== Tracking dotfiles directly with Git ==

The benefit of tracking dotfiles directly with Git is that it only requires [[Git]] and does not involve symlinks. The disadvantage is that [[#Host-specific configuration|host-specific configuration]] generally requires merging changes into multiple [[Git#Branching|branches]].

The simplest way to achieve this approach is to initialize a [[Git]] repository directly in your home directory and ignoring all files by default with a {{man|5|gitignore}} pattern of {{ic|*}}. This method however comes with two drawbacks: it can become confusing when you have other Git repositories in your home directory (e.g. if you forget to initialize a repository you suddenly operate on your dotfile repository) and you can no longer easily see which files in the current directory are untracked (because they are ignored).

An alternative method without these drawbacks is the "bare repository and alias method" popularized on [https://news.ycombinator.com/item?id=11071754 Ask Hacker News: What do you use to manage your dotfiles?], which just takes three commands to set up:

$ git init --bare ~/.dotfiles
$ alias dotfiles='/usr/bin/git --git-dir="$HOME/.dotfiles/" --work-tree="$HOME"'
$ dotfiles config status.showUntrackedFiles no

{{note|Usually one's dotfiles all have default permissions, but if specific file permissions for some files are a must, another approach should be used, as git does not store permissions ([[Talk:Dotfiles#Git approach fails on permissions and ownership|Discussion]])}}

Your dotfiles can be replicated on a new system like:

$ git clone --bare <git-repo-url> $HOME/.dotfiles
$ alias dotfiles='/usr/bin/git --git-dir="$HOME/.dotfiles/" --work-tree="$HOME"'
$ dotfiles checkout
$ dotfiles config --local status.showUntrackedFiles no

* To do this without a remote repository, [[git#Bundling|git bundles]] can be used. To create a git bundle called {{ic|dotfiles.bundle}} on your source computer run:
:{{bc|<nowiki>
$ dotfiles bundle create --progress dotfiles.bundle --all
</nowiki>}}

:A bundle can be used similarly to a {{ic|<git-repo-url>}}:
:{{bc|<nowiki>
$ git clone --bare dotfiles.bundle $HOME/.dotfiles
</nowiki>}}

* In case of already having some stock dotfiles which might get overwritten, you'll encounter something similar to the following the error:
:{{bc|<nowiki>
$ dotfiles checkout
error: The following untracked working tree files would be overwritten by checkout:
.bashrc
.gitignore
Please move or remove them before you can switch branches.
Aborting
</nowiki>}}

:You could use {{ic|$ dotfiles checkout -f}} which will rewrite the already existing files, or in a safer approach take a backup of all the files with the following script and then using {{ic|checkout}}:
:{{bc|<nowiki>
mkdir -p .dotfiles-backup && \
dotfiles checkout 2>&1 | egrep "\s+\." | awk {'print $1'} | \
xargs -I{} mv {} .dotfiles-backup/{}
</nowiki>}}

You can then manage your dotfiles with the created [[alias]]. If you are using [[Bash]] and would like bash completion for this alias, simply install {{AUR|bash-complete-alias}}, then add the alias and the following line to your {{ic|~/.bashrc}}.

$ complete -F _complete_alias dotfiles

Another way to get completion in bash is adding the following to your {{ic|~/.bashrc}} (taken from [https://askubuntu.com/a/642778]):

source /usr/share/bash-completion/completions/git
__git_complete dotfiles __git_main

{{Tip|To avoid accidentally committing confidential information, see [[Git#Filtering confidential information]].}}

== Host-specific configuration ==

A common problem with synchronizing dotfiles across various machines is host-specific configuration.

With [[Git]] this can be solved by maintaining a master branch for all shared configuration, while each individual machine has a machine-specific branch checked out. Host-specific configuration can be committed to the machine-specific branch; when shared configuration is modified in the master branch, the per-machine branches need to be rebased on top of the updated master.

In configuration scripts like [[Command-line shell#Configuration files|shell configuration files]] conditional logic can be used. For example, [[Bash]] scripts (i.e. {{ic|.bashrc}}) can apply different configuration depending on the machine name (or type, custom variable, etc.):

if <nowiki>[[ "$(hostname)" == "archlaptop" ]];</nowiki> then
# laptop specific commands here
else
# desktop or server machine commands
fi

Similar can also be achieved with [[.Xresources]].[https://jnrowe.github.io/articles/tips/Sharing_Xresources_between_systems.html]

If you find rebasing Git branches too cumbersome, you may want to use a [[#Tools|tool]] that supports ''file grouping'', or if even greater flexibility is desired, a tool that does ''processing''.

== Tools ==

;File grouping
:How configuration files can be grouped to configuration groups (also called profiles or packages).
;Processing
:Some tools process configuration files to allow them to be customized depending on the host.

{| class="wikitable sortable" style="text-align: center;"
! Name !! Package !! Written in !! File grouping !! Processing
|-
! [https://github.com/anishathalye/dotbot dotbot]
| {{AUR|dotbot}} || Python || configuration file || {{Grey|No}}
|-
! [https://github.com/twpayne/chezmoi chezmoi]
| {{Pkg|chezmoi}} || Go || directory-based || Go templates
|-
! [https://github.com/kesslern/dot-templater dot-templater]
| {{AUR|dot-templater-git}} || Rust || directory-based || custom syntax
|-
! [https://github.com/oknozor/toml-bombadil toml-bombadil]
| {{Pkg|toml-bombadil}} || Rust || configuration file || tera
|-
! [https://github.com/deadc0de6/dotdrop dotdrop]
| {{AUR|dotdrop}} || Python || configuration file || Jinja2
|-
! [https://github.com/jbernard/dotfiles dotfiles]
| {{AUR|dotfiles}} || Python || {{Grey|[https://github.com/jbernard/dotfiles/pull/24 No]}} || {{Grey|No}}
|-
! [https://github.com/SuperCuber/dotter dotter]
| {{AUR|dotter-rs}} || Rust || configuration file || Handlebars
|-
! [https://dt.cli.rs dt-cli]
| {{AUR|dt-cli}} || Rust || configuration file || Handlebars
|-
! [https://www.gnu.org/software/stow/ GNU Stow]
| {{Pkg|stow}} || Perl || directory-based[https://brandon.invergo.net/news/2012-05-26-using-gnu-stow-to-manage-your-dotfiles.html] || {{Grey|No}}
|-
! [https://github.com/lra/mackup Mackup]
| {{AUR|mackup}} || Python || automatic per application || {{Grey|No}}
|-
! [https://github.com/darkfeline/mir.qualia mir.qualia]
| {{AUR|mir.qualia}} || Python || {{Grey|No}} || custom blocks
|-
! [https://github.com/thoughtbot/rcm rcm]
| {{AUR|rcm}} || Shell || directory-based (by host or tag) || {{Grey|No}}
|-
! [https://github.com/sebastiancarlos/yas-bdsm yas-bdsm]
| {{-}} || Shell || directory-based || {{Grey|No}}
|-
! [https://github.com/jaxvanyang/dotbackup.rs dotbackup]
| {{AUR|dotbackup}} || Rust || configuration file || Shell script
|}

=== Tools wrapping Git ===

If you are uncomfortable with [[Git]], you may want to use one of these tools, which abstract the version control system away (more or less).

{| class="wikitable sortable" style="text-align:center;"
! Name !! Package !! Written in !! File grouping !! Processing
|-
! [https://github.com/kazhala/dotbare dotbare]
| {{AUR|dotbare}} || Shell ({{Pkg|fzf}}) || repository-wise || {{Grey|No}}
|-
! [https://github.com/kobus-v-schoor/dotgit dotgit]
| {{AUR|dotgit}} || Python || filename-based || {{Grey|No}}
|-
! [https://github.com/andsens/homeshick homeshick]
| {{AUR|homeshick-git}} || Bash || repository-wise || {{Grey|No}}
|-
! [https://github.com/technicalpickles/homesick homesick]
| {{-}} || Ruby || repository-wise || {{Grey|No}}
|-
! [https://github.com/pearl-core/pearl Pearl]
| {{AUR|pearl-git}} || Python || repository-wise || {{Grey|No}}
|-
! [https://github.com/RichiH/vcsh vcsh]
| {{Pkg|vcsh}} || Shell || repository-wise || {{Grey|No}}
|-
! [https://yadm.io yadm](1)
| {{Pkg|yadm}} || Shell || filename-based (by class/OS/distro/hostname/user)[https://yadm.io/docs/alternates] ||Built-in templates/Jinja2/ESH[https://yadm.io/docs/templates] (optional)
|-
! [https://github.com/justone/dotfiles dfm]
| {{AUR|dfm}} || Perl || repository-wise || {{Grey|No}}
|}

# Supports encryption of confidential files with [[GPG]] or OpenSSL. [https://yadm.io/docs/encryption]

== User repositories ==

{{Note|This table is used as a reference/examples of dotfiles, if you are submitting your dotfiles to the table, please ensure they are kept clean, commented and up to date.}}
{{Warning|These dotfiles have not been verified by any of the Arch Linux staff, use at your own risk.}}

{| class="wikitable sortable" style="text-align:center"
! Author || Shell (Shell framework) || WM / DE || Editor || Terminal || Multiplexer || Audio || Monitor || Mail || IRC || File Manager || RSS reader
|-
! [https://github.com/adamperkowski/dwm adamperkowski]
| [[Zsh]] || [[dwm]] || [[Neovim]] || [[st]] || [[tmux]] || [[mpv]] || custom || || [[WeeChat]] || ||
|-
! [https://github.com/ananthu-sk/dotfiles_bspwm ananthu]
| [[Zsh]] || [[bspwm]] || [[Neovim]] || [[Alacritty]] || || [[mpv]] || htop, [[Polybar]] || [[neomutt]] || [[WeeChat]] || [[ranger]] ||
|-
! [https://github.com/ayekat/localdir ayekat]
| [[Zsh]] || karuiwm || [[Vim]] || [[rxvt-unicode]] || [[tmux]] || [[ncmpcpp]] / [[mpd]] || karuibar || [[mutt]] || [[Irssi]] || ||
|-
! [https://github.com/BachoSeven/dotfiles bachoseven]
| [[Zsh]] || [https://github.com/BachoSeven/dwm dwm] || [[Neovim]] || [https://github.com/BachoSeven/st st] || [[tmux]] || [[ncmpcpp]] || bottom || [[neomutt]] || [[WeeChat]] || [[Lf]] || [[Newsboat]]
|-
! [https://github.com/bamos/dotfiles bamos]
| [[Zsh]] || [[i3]] / [[xmonad]] || [[Vim]] / [[Emacs]] || [[rxvt-unicode]] || [[tmux]] || [[mpv]] / [[cmus]] || [[conky]] / [[xmobar]] || [[mutt]] || ERC || ||
|-
! [https://github.com/pbrisbin/dotfiles brisbin33]
| [https://github.com/pbrisbin/oh-my-zsh zsh] || [https://github.com/pbrisbin/xmonad-config xmonad] || [https://github.com/pbrisbin/vim-config vim] || [[rxvt-unicode]] || [[GNU Screen]] || || dzen || [https://github.com/pbrisbin/mutt-config mutt] || [https://github.com/pbrisbin/irssi-config irssi] || ||
|-
! [https://github.com/christian-heusel/dotfiles christian-heusel]
| [[Zsh]] || [[i3]] || [[Neovim]] || [[st]] / [[Terminator]] || byobu / [[tmux]] || || htop || [[neomutt]] / [[Thunderbird]] || [[WeeChat]] || [[Nemo]] / [[ranger]] ||
|-
! [https://github.com/CuterThanYou/dotfiles CuterThanYou]
| [[Zsh]] || [[i3]] / [[Hyprland]] || [[Neovim]] || [[Alacritty]] / [[Foot]] || || [[mpv]] || [[Polybar]] / Yambar || || || [[Lf]] / [[Thunar]] ||[[Newsboat]]
|-
! [https://github.com/dikiaap/dotfiles dikiaap]
| [[Zsh]] || [[i3]]-gaps || [[Neovim]] || [[Alacritty]] || [[tmux]] || || i3blocks || || || [[nnn]] ||
|-
! [https://github.com/Earnestly/dotfiles Earnestly]
| [[Zsh]] || [[i3]] / orbment || [[Vim]] / [[Emacs]] || [[termite]] || [[tmux]] || [[mpd]] || [[conky]] || [[mutt]] || [[WeeChat]] || ||
|-
! [https://github.com/egnrse/configs egnrse]
| [[Zsh]] / [[Bash]] || [[Hyprland]] || [[Neovim]] || [[Alacritty]] || || [[VLC]] || bottom / mission-center || || || [[Dolphin]] ||
|-
! [https://github.com/ErikBjare/dotfiles ErikBjare]
| [[Zsh]] || [[xmonad]] / [[Xfce4]] || [[Vim]] || [[Terminator]] || [[tmux]] || || xfce4-panel || || [[WeeChat]] || ||
|-
! [https://github.com/erikw/dotfiles erikw]
| [[Zsh]] / [[Bash]] || [[dwm]] / [[macOS]] || [[Neovim]] || urxvtc || [[tmux]] || [[mpd]] || || [[mutt]] || [[Irssi]] || ||
|-
! [https://github.com/filiparag/dotfiles filiparag]
| [[fish]] || [[bspwm]] || [[Vim]] || [[Alacritty]] || [[tmux]] || [[mpv]] / playerctl || htop, [[Polybar]] || [https://www.nongnu.org/mailnotify/ mail-notification] || || [[PCManFM]] ||
|-
! [https://github.com/Freed-Wu/Freed-Wu Freed-Wu]
| [[Zsh]] || [[openbox]] || [[Neovim]] || [[wezterm]] || [[tmux]] || [[cmus]] || bottom || [[neomutt]] || [[WeeChat]] || [[Neovim]] || [[Newsboat]]
|-
! [https://github.com/graysky2/configs/tree/master/dotfiles graysky]
| [[Zsh]] || [[Xfce]] || [[Vim]] || terminal || || [[ncmpcpp]] || custom || [[Thunderbird]] || || ||

|-
! [https://github.com/insanum/dotfiles insanum]
| [[Bash]] || [[Herbstluftwm]] || [[Vim]] || evilvte || [[tmux]] || || dzen || mutt-kz || || ||
|-
! [https://github.com/isti115/dotfiles isti115]
| [https://github.com/Isti115/dotfiles/blob/master/.config/powershell/Microsoft.PowerShell_profile.ps1 pwsh]
|| [https://github.com/Isti115/dotfiles/blob/master/.config/sway/config sway]
|| [https://github.com/Isti115/dotfiles/tree/master/.config/nvim neovim]
|| [https://github.com/Isti115/dotfiles/blob/master/.config/alacritty/alacritty.yml alacritty]
|| [[tmux]]
|| [https://github.com/Isti115/dotfiles/tree/master/.config/mpv mpv] / playerctl
|| [https://github.com/Isti115/dotfiles/tree/master/.config/waybar waybar] / htop / ytop
||
||
|| [https://github.com/Isti115/dotfiles/tree/master/.config/ranger ranger]
||
|-
! [https://github.com/its-me/dotfiles itsme]
| [[Zsh]] || [[Niri]] || [[Helix]] || [[kitty]] || [[tmux]] || [[mpv]] || [[Waybar]] || || || [https://github.com/sxyazi/yazi yazi] ||
|-
! [https://hg.sr.ht/~jasonwryan/shiv jasonwryan]
| [[Bash]] / [[Zsh]] || [[dwm]] || [[Vim]] || [[rxvt-unicode]] || [[tmux]] || [[ncmpcpp]] || custom || [[mutt]] || [[Irssi]] || ||
|-
! [https://github.com/JDevlieghere/dotfiles/ jdevlieghere]
| [[Zsh]] || [[xmonad]] || [[Vim]] || terminal || [[tmux]] || || htop || [[mutt]] || [[WeeChat]] || ||
|-
! [https://github.com/jelly/Dotfiles jelly]
| [[Zsh]] || [[i3]] || [[Vim]] || [[termite]] || [[tmux]] || [[ncmpcpp]] || || mutt-kz-git || [[WeeChat]] || ||
|-
! [https://gitlab.com/jlo62/dotties jl2]
| [[Zsh]] || swayfx || geany || [[foot]] || || || mission-center / eww (bar) || || srain || [[Thunar]] ||
|-
! [https://github.com/karras/dotfiles karras]
| [[Zsh]] || Wayfire || [[Neovim]] || [[Terminator]] || || || [[Waybar]] || || || ||
|-
! [https://github.com/markuszoppelt/dotfiles MarkusZoppelt]
| [[Zsh]] || [[GNOME]] || [[Neovim]] || [[Alacritty]] || [[tmux]] || || || || || ||
|-
! [https://github.com/maximbaz/dotfiles maximbaz]
| [[Zsh]] || [[Sway]] || [[kakoune]] || [[kitty]] || || || [[Waybar]] || [[neomutt]] || || [[nnn]] ||
|-
! [https://github.com/neersighted/dotfiles neersighted]
| [[fish]] || [[i3]] || [[Neovim]] || [[Alacritty]] || [[tmux]] || [[ncmpcpp]] || || || || ||
|-
! [https://github.com/nimaipatel/dotfiles nimaipatel]
| [[fish]] || [[awesome]] || [[Neovim]] || [[Alacritty]] || || [[ncmpcpp]] || || || || ||
|-
! [https://github.com/oibind/dotfiles oibind]
| [[fish]] || [[awesome]] || [[Neovim]] || [[st]] || [[tmux]] || || htop-vim || || [[WeeChat]] || [[Lf]] ||
|-
! [https://github.com/orhun/dotfiles orhun]
| [[Bash]] || [[i3]]-gaps || [[Neovim]] || [[Alacritty]] || || || i3status || || [[WeeChat]] || tere ||
|-
! [https://github.com/patri9ck/dotfiles patri9ck]
| [[Zsh]] || [[bspwm]] || [[Vim]] || [[kitty]] || || || || || || [[Thunar]] ||
|-
! [https://gitlab.com/peterzuger/dotfiles peterzuger]
| [[Zsh]] || [[i3]]-gaps || [[Emacs]] || [[rxvt-unicode]] || [[GNU Screen]] || [[MOC]] || htop || || || ||
|-
! [https://gitlab.com/polyzen/dotfiles polyzen]
| [[Zsh]] || [[i3]] || [[Neovim]] || [[Alacritty]] || [[tmux]] || [[mpv]] || i3status / htop || himalaya || || [[ranger]] || [[Newsboat]]
|-
! [https://github.com/potamides/dotfiles potamides]
| [[Bash]] || [[awesome]] || [[Neovim]] || [[termite]] || [[tmux]] || [[ncmpcpp]] || [[conky]] / htop || [[mutt]] || [[WeeChat]] || [[ranger]] ||
|-

! [https://github.com/sistematico/majestic sistematico]
| [[Zsh]] / [[fish]] / [[Bash]] || [https://github.com/Airblader/i3 i3-gaps] || [[Vim]] / [[nano]] || [[termite]] || [[tmux]] || [[ncmpcpp]] || [[Polybar]] || [[mutt]] || [[WeeChat]] || ||
|-
! [https://git.sr.ht/~thecashewtrader/dotfiles thecashewtrader]
| Eshell || [[EXWM]] || [[Emacs]] || Emacs (VTerm) || [[Emacs]] || Bongo || htop || mu4e || ERC || Dired || Elfeed
|-
! [https://github.com/thiagowfx/.dotfiles thiagowfx]
| [[Bash]] / [[Zsh]] || [[i3]] || [[Vim]] || [[Alacritty]] || [[tmux]] || playerctl || i3status || || || [[ranger]] ||
|-
! [https://codeberg.org/tplasdio/dotfiles tplasdio]
| [https://codeberg.org/tplasdio/bash-config bash (ble.sh)] || [https://codeberg.org/tplasdio/awesomewm-config awesome] || [https://codeberg.org/tplasdio/neovim-config neovim] || [https://codeberg.org/tplasdio/dotfiles/src/branch/main/.config/alacritty/alacritty.yml alacritty] || [https://codeberg.org/tplasdio/dotfiles/src/branch/main/.config/byobu/.tmux.conf tmux] || [https://codeberg.org/tplasdio/mpv-config mpv], mpvs || htop || [[neomutt]] || [[WeeChat]] || [https://codeberg.org/tplasdio/lf-config lf] ||
|-
! [https://github.com/tuurep/dotfiles tuurep]
| [[Zsh]] || [[openbox]] || [[Neovim]] || [[Alacritty]] || || || [[Polybar]] || || || ||
|-
! [https://git.sr.ht/~unrealapex/dotfiles unrealapex]
| [[Zsh]] || [[dwm]] || [[Neovim]] || [[st]] || || [[ncmpcpp]] || htop || [[neomutt]] || [[Irssi]] || fff || [[Newsboat]]
|-
! [https://github.com/w0ng/dotfiles w0ng]
| [[Zsh]] || [[dwm]] || [[Vim]] || [[rxvt-unicode]] || [[tmux]] || [[ncmpcpp]] || custom || [[mutt]] || [[Irssi]] || ||
|-
! [https://github.com/whitelynx/dotfiles whitelynx]
| [[fish]] || [[i3]] || [[Neovim]] || [[kitty]] || || || i3pystatus || || || ||
|-
! [https://git.sr.ht/~whynothugo/dotfiles whynothugo]
| [[Zsh]] || [[Sway]] || [[Neovim]] || [[Alacritty]] || || [[mpv]] || [[Waybar]] / top || [[neomutt]] || || [[Nemo]] ||
|-
|}

== See also ==

* [https://dotfiles.github.io/ dotfiles.github.io]
* [[gregswiki:DotFiles]]
* [https://terminal.sexy/ terminal.sexy] — Terminal color scheme designer
* [https://wiki.haskell.org/Xmonad/Config_archive XMonad Config Archive]

Rofi

2026-05-14T14:45:22Z

Erus Iluvatar: /* Execute shell commands from rofi */ Partial revert of the previous edit: using the redirect is fine here

[[Category:Application launchers]]
[[ja:Rofi]]
[[pl:Rofi]]
[[pt:Rofi]]
[[ru:Rofi]]
[[uk:Rofi]]
[[zh-hans:Rofi]]
{{Related articles start}}
{{Related|List of applications/Other#Application launchers}}
{{Related articles end}}

[https://github.com/davatorium/rofi Rofi] is a window switcher, run dialog, ssh-launcher and [[dmenu]] replacement that started as a clone of [https://github.com/seanpringle/simpleswitcher simpleswitcher], written by [https://github.com/seanpringle Sean Pringle] and later expanded by [https://github.com/DaveDavenport Dave Davenport].

== Installation ==

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

== Configuration ==

To know more about rofi and its usage read the {{man|1|rofi}} man page.

There are two methods of setting configuration options:

* Local configuration. Normally, depending on XDG, in {{ic|~/.config/rofi/config.rasi}}.
* Command line options:

$ rofi -combi-modi window,drun,ssh -theme solarized -font "hack 10" -show combi

can be expressed in a configuration file like this:

configuration {
modi: "window,drun,ssh,combi";
font: "hack 10";
combi-modi: "window,drun,ssh";
}
@theme "solarized"

To get a full list of options for {{ic|config.rasi}} file run {{ic|rofi -dump-config}}. You can write the output of the command directly to your configuration file while running {{ic|rofi -dump-config > ~/.config/rofi/config.rasi}}

{{Note|[[i3]] users be aware that putting commas in the ''i3'' configuration file can cause issues. To bind a key to launch ''rofi'', either use a configuration file or replace the commas with {{ic|#}}, e.g. {{ic|rofi -combi-modi window#drun#ssh}}.}}

=== Icons ===

It is possible to use icons to display with their corresponding entries. Assuming you have {{Pkg|papirus-icon-theme}} installed, with {{ic|-show-icons}} and defining the icon theme with {{ic|-icon-theme}}, you can have ''rofi'' display icons and do the following:

$ rofi -combi-modi window,drun,ssh -theme solarized -font "hack 10" -show combi -icon-theme "Papirus" -show-icons

== Custom themes ==

You can preview and apply themes for ''rofi'' with

$ rofi-theme-selector

The {{man|5|rofi-theme}} man page contains extensive instructions on how to theme rofi, using a custom, CSS-like language. This page contains additional informations on the layout system used by rofi, the precise syntax used to theme rofi, as well as additional instructions to theme most of rofi's properties. Rofi's theme system can be simple (the default [[dmenu]] theme is around 30 lines of CSS) but is flexible enough to create various interactive, widget-like applets and menus, like [https://github.com/adi1090x/rofi rofi-advanced].

=== Contributed themes ===

Rofi comes with several official themes stored in {{ic|/usr/share/rofi/themes}}, and more user themes can be found at the [https://github.com/davatorium/rofi-themes rofi-themes] repository.

Load up an official theme, or download a ''.rasi'' user theme and place it in {{ic|~/.config/rofi/example.rasi}} on the command line:

$ rofi ''options'' -theme example

Alternatively, in your configuration file outside of the {{ic|configuration { }<nowiki/>}} block:

@theme "example"

== Tips and tricks ==

=== Rofi as dmenu replacement ===

If called as [[dmenu]] (via a symlink), ''rofi'' acts like ''dmenu''. Then, programs that call ''dmenu'' from a script (like ''passmenu'' from [[pass]]) will use ''rofi'' instead of ''dmenu''. The exact behavior of {{ic|rofi}} in ''dmenu'' mode is described in {{man|5|rofi-dmenu}}.

To approximate the look of [[dmenu]], copy the file {{ic|/usr/share/rofi/themes/dmenu.rasi}} shipped by default in the {{Pkg|rofi}} package to the rofi configuration directory (usually {{ic|~/.config/rofi}}) and enable it by appending {{ic|@theme "dmenu.rasi"}} at the end of {{ic|config.rasi}} or with the {{ic|-theme dmenu}} option on the command line.

=== Execute shell commands from rofi ===

If you want the ability to run [[shell]] commands or use your own scripts directly from ''rofi'' with seeing the output, then ensure following:

Define {{ic|-run-shell-command '{terminal} -e ''SHELL'' -ic "{cmd} && read"}} where {{ic|''SHELL''}} is your shell (e.g. bash, zsh). This allows you to enter the command on the inputbar followed by {{ic|Shift+Enter}}. The terminal stays open until the next keypress.

This is an example with the recommended escaping sequence for ''i3'':

bindsym $mod+d exec --no-startup-id rofi -show drun -run-shell-command '{terminal} -e zsh -ic "{cmd} && read"'

=== Unicode selection integration ===

Install {{Pkg|rofimoji}} for a Unicode emoji/character picker integrated with ''rofi''. See the [https://github.com/fdw/rofimoji#readme project's README] for [https://github.com/fdw/rofimoji#usage usage] and [https://github.com/fdw/rofimoji#configuration configuration].

=== Emoji selection menu ===

Install {{Pkg|rofi-emoji}} for an emoji picker integrated with ''rofi''. See the [https://github.com/Mange/rofi-emoji#readme project's README] for the [https://github.com/Mange/rofi-emoji#usage usage].

If you encounter rendering issues regarding emojis (rendering as rectangles for example), you should install {{AUR|ttf-symbola}}, {{Pkg|noto-fonts-cjk}}, and/or {{Pkg|noto-fonts-emoji}}.

=== Rofi as a power management menu ===

Rofi can be used to perform power management operation with systemd. [[Install]] {{AUR|rofi-power-menu}}. The AUR package will insert the rofi-power-menu script into $PATH by default so all that is needed to use it is:

$ rofi -show p -modi p:rofi-power-menu

If you decide to not use the AUR package and clone it manually then you will have to tell rofi where to find ''rofi-power-menu'' executable. For example, if the executable is in {{ic|$HOME/.rofi-power-menu}}:

$ rofi -show p -modi p:$HOME/.rofi-power-menu

You can also put the executable in the PATH, and pass only its name.

To show default symbols, you may need to install {{Pkg|ttf-nerd-fonts-symbols}}.

For more information, read the [https://github.com/jluttine/rofi-power-menu#readme README] file in the repository.

=== Rofi as a Clipboard Manager ===

Rofi can be used as a X11 clipboard manager using [[Greenclip]] or {{Pkg|clipmenu}}. For Greenclip install the {{AUR|rofi-greenclip}} package. For [[Wayland]], {{Pkg|cliphist}} is a good alternative.

=== Rofi as a calculator ===

Rofi can be used as a calculator with natural language input, unit conversions, and currency conversions using the {{Pkg|rofi-calc}} package.

Lenovo IdeaPad Gaming 3

2026-05-14T08:39:21Z

Erus Iluvatar: /* Function keys */ re-flag section for laptop style, it was improved but is still missing the required exact information

[[Category:Lenovo]]
[[ja:Lenovo IdeaPad Gaming 3]]
{| class="wikitable archwiki-table-laptop"
|-
! Hardware !! PCI/USB ID !! Working?
|-
| Touchpad || {{ic|04F3:31AD}} || {{Yes}}
|-
| Keyboard || {{ic|048d:c966}} || {{Yes}}
|-
| GPU (Intel) || {{ic|8086:9bc4}} || {{Yes}}
|-
| GPU (AMD) || {{ic|1002:1636}} || {{Yes}}
|-
| GPU (NVIDIA) || {{ic|10de:1f99}} || {{Yes}}
|-
| Webcam || {{ic|5986:212b}} || {{Yes}}
|-
| Bluetooth || {{ic|8087:0029}} || {{Yes}}
|-
| Audio || {{ic|1022:15e3}} || {{Yes}}
|-
| Wi-Fi || {{ic|168c:003e}} || {{Yes}}
|-
| Ethernet || {{ic|10ec:8168}} || {{Yes}}
|}

== Installation ==

Before installing, disable [[Secure Boot]] in the UEFI Setup. You can access the UEFI Setup by pressing {{ic|F2}} at the Splash screen. The boot menu can also be accessed by pressing {{ic|F12}}.

== Accessibility ==

The UEFI firmware settings can be entered by pressing {{ic|F2}} repeatedly during boot.

=== Navigation ===

The interface can be fully navigated and controlled with a keyboard and mouse. Up and down arrow keys let the user choose categories, settings items within each category and values for settings. Left and right arrow keys let the user leave and enter a category, settings item or value picker. The enter key can also be used to enter a category or enter and leave an item's value picker. Settings can be saved and the system restarted by pressing {{ic|F10}}.

=== Secure Boot ===

In order to boot an Arch installation medium, [[Secure Boot]] must be disabled in the UEFI settings. Once disabled, press {{ic|F12}} on the next boot to enter the boot device menu and select your Arch installation medium.

== Firmware ==

This laptop is not supported by [[fwupd]]. You need a Windows installation in order to update UEFI.

== Power management ==
{{Merge|Laptop/Lenovo#Lenovo|This is shared across multiple models and should be put on the generic page instead of duplicated for every model.}}

Install {{Pkg|acpi_call}} (or {{Pkg|acpi_call-lts}} for LTS kernel, {{Pkg|acpi_call-dkms}} for other [[kernel]]s) and load the [[kernel module]]:

# modprobe acpi_call

=== System Performance Mode ===

There are 3 modes available: ''Intelligent Cooling'', ''Extreme Performance'' and ''Battery Saving''. To switch between them, press {{ic|Fn+Q}} on the IdeaPad's internal keyboard.

Using ACPI calls directly (tested on 15ACH6):

Set it to ''Intelligent Cooling'' mode:

# echo '\_SB_.GZFD.WMAA 0 0x2C 2' > /proc/acpi/call

Set it to ''Extreme Performance'' mode:

# echo '\_SB_.GZFD.WMAA 0 0x2C 3' > /proc/acpi/call

Set it to ''Battery Saving'' mode:

# echo '\_SB_.GZFD.WMAA 0 0x2C 1' > /proc/acpi/call

To view the currently activated System Performance Mode in 15ARH05 or 15ACH6 and its family series:

# echo '\_SB.PCI0.LPC0.EC0.SPMO' > /proc/acpi/call
# cat /proc/acpi/call; printf '\n'

In some 15ACH6 and 15ARH7 and its family series :

# echo '\_SB.PCI0.LPC0.EC0.GZ44' > /proc/acpi/call
# cat /proc/acpi/call; printf '\n'

As a result you get the value for the bit SPMO / GZ44 (either {{ic|0x0}}, {{ic|0x1}} or {{ic|0x2}}).
The value of the bit corresponds to the following System Performance Modes:

{| class="wikitable"
! SPMO / GZ44 !! Mode
|-
| 0x0 || Intelligent Cooling
|-
| 0x1 || Extreme Performance
|-
| 0x2 || Battery Saving
|}

{{Merge|Lenovo|Desktop-specific tools should be documented outside of laptop pages.}}

A simple OSD for KDE is available via {{AUR|fnq-monitor}}; edit {{ic|/usr/bin/fnq-monitor}} for customization.
[[Enable/start]] the {{ic|fnq-monitor.service}} [[user unit]] manually.

{{Note|After setting the mode manually via ACPI, a reboot is required for the change to take full effect.}}

=== Rapid Charge ===

Turn on Rapid Charge:

# echo '\_SB.PCI0.LPC0.EC0.VPC0.SBMC 0x07' > /proc/acpi/call

Turn off Rapid Charge:

# echo '\_SB.PCI0.LPC0.EC0.VPC0.SBMC 0x08' > /proc/acpi/call

Get the status of Rapid Charge:

# echo '\_SB.PCI0.LPC0.EC0.QCHO' > /proc/acpi/call
# cat /proc/acpi/call; printf '\n'

For some 15ACH6:

# echo '\_SB.PCI0.LPC0.EC0.FCGM' > /proc/acpi/call
# cat /proc/acpi/call; printf '\n'

where {{ic|0x0}} stands for ''off'' and {{ic|0x1}} stands for ''on''.

=== Battery Conservation ===

Similarly to the [[#Rapid Charge]], make sure you have set up {{Pkg|acpi_call}}.

Turn on:

# echo '\_SB.PCI0.LPC0.EC0.VPC0.SBMC 0x03' > /proc/acpi/call

{{Note|The Lenovo Vantage software for Windows will turn off Rapid Charge when turning on Battery Conservation Mode. This ACPI call '''will not''' do that! You should turn it off manually (see the section [[#Rapid Charge]]).}}

Turn off:

# echo '\_SB.PCI0.LPC0.EC0.VPC0.SBMC 0x05' > /proc/acpi/call

To verify your setting:

# echo '\_SB.PCI0.LPC0.EC0.BTSM' > /proc/acpi/call
# cat /proc/acpi/call; printf '\n'

where {{ic|0x0}} stands for ''off'' and {{ic|0x1}} stands for ''on''.

There is also an alternative way to control the Conservation Mode of the battery:

First make sure the {{ic|ideapad_laptop}} kernel module is loaded with the {{ic|lsmod}} command.

If it is, run the following command as root to enable Battery Conservation Mode:

# echo 1 > /sys/bus/platform/drivers/ideapad_acpi/VPC2004:00/conservation_mode

A 0 will in turn disable the feature.

== Function keys ==

{{Laptop style|The "Effect" column should show the [[X keyboard extension#Basic information on XKB|X keyboard extension symbol]] of each key, like {{ic|XF86MonBrightnessDown}}, per [[Help:Laptop page guidelines#"Function keys" section]].}}

{| class="wikitable"
|-
! Key
! Visible?
! Marked?
! Effect
|-
| {{ic|Fn+Esc}} || {{No}} || {{Yes}} || Toggle Fn lock
|-
| {{ic|Fn+F1}} || {{Yes}} || {{Yes}} || Mute audio
|-
| {{ic|Fn+F2}} || {{Yes}} || {{Yes}} || Volume down
|-
| {{ic|Fn+F3}} || {{Yes}} || {{Yes}} || Volume up
|-
| {{ic|Fn+F4}} || {{Yes}} || {{Yes}} || Mute microphone
|-
| {{ic|Fn+F5}} || {{Yes}} || {{Yes}}1 || Screen brightness down
|-
| {{ic|Fn+F6}} || {{Yes}} || {{Yes}}1 || Screen brightness up
|-
| {{ic|Fn+F7}} || {{Yes}} || {{Yes}} || Show screen projecting menu (same as {{ic|Super+P}})
|-
| {{ic|Fn+F8}} || {{Yes}} || {{Yes}} || Turn on airplane mode
|-
| {{ic|Fn+F10}} || {{Yes}} || {{Yes}} || Turn touchpad on/off
|-
| {{ic|Fn+F11}} || {{Yes}} || {{Yes}} || LeftCtrl+LeftAlt+Tab
|-
| {{ic|Fn+F12}} || {{Yes}} || {{Yes}} || Calculator
|-
| {{ic|Fn+Space}} || {{No}}2 || {{Yes}} || Toggle keyboard backlight (off/low/bright)
|-
| {{ic|Fn+Q}} || {{No}} || {{Yes}} || Switch between performance modes, see [[#System Performance Mode]]
|-
| {{ic|Fn+Home}} || {{Yes}} || {{Yes}} || (Media) Play/Pause
|-
| {{ic|Fn+End}} || {{Yes}} || {{Yes}} || (Media) Stop
|-
| {{ic|Fn+PageUp}} || {{Yes}} || {{Yes}} || (Media) Previous
|-
| {{ic|Fn+PageDown}} || {{Yes}} || {{Yes}} || (Media) Next
|-
|}
# If the backlight controls does not work on the AMD/NVIDIA variant by default, add the following [[kernel parameter]]: {{ic|1=amdgpu.backlight=0}}.
# If the keyboard backlight appears but cannot be controlled (i.e. it is shown by mistake), [[mask]] {{ic|systemd-backlight@leds:platform::kbd_backlight.service}} and the following [[udev]] rule disables it:

{{hc|/etc/udev/rules.d/99-disable-kbd-backlight.rules|2=
SUBSYSTEM=="leds", KERNEL=="platform::kbd_backlight", ACTION=="add", RUN+="/bin/chmod 000 /sys/class/leds/platform::kbd_backlight/brightness"
}}

== Advanced UEFI/BIOS ==

{{Warning|Modifying the advanced settings may harm your device. Proceed with caution.}}
{{Note|This was only tested in the 15ACH6 and 15ARH7 series laptops}}

To access the advanced UEFI/BIOS setup utility, do the following:
# Power off completely
# Press the power button
# Repeatedly press {{ic|F2}} to enter UEFI/BIOS
# Press the following key sequence 3 times, one key at a time: {{ic|Fn}}, {{ic|R}}, {{ic|N}}
# Press {{ic|F10}} and {{ic|Enter}} to save and exit
# Repeatedly press {{ic|F2}} to enter UEFI/BIOS, this should now have the advanced options visible

== See also ==

* [https://download.lenovo.com/consumer/mobiles_pub/ideapad5_hmm_202002.pdf Hardware maintenance manual]
* [https://psref.lenovo.com/syspool/Sys/PDF/IdeaPad/IdeaPad_Gaming_3_15ACH6/IdeaPad_Gaming_3_15ACH6_Spec.pdf Product Specifications Reference (PSREF) of 15ACH6]
* [https://psref.lenovo.com/syspool/Sys/PDF/IdeaPad/IdeaPad_5_15ARE05/IdeaPad_5_15ARE05_Spec.pdf Product Specifications Reference (PSREF) of 15ARE05]
* [https://download.lenovo.com/consumer/mobiles_pub/ideapad5_ug_en_202001.pdf User guide]

TeXstudio

2026-05-14T08:35:45Z

Erus Iluvatar: style

[[Category:TeX]]
[[ja:TeXstudio]]
[[zh-hans:TeXstudio]]
[https://texstudio.org TeXstudio] is a free [[LaTeX]] [[List of applications/Documents#TeX editors|editor]]. It offers multiple features to easily input special characters, edit tables, preview math mode snippets and language checking.

== Installation ==

If not already installed, install [[TeX Live]] or similar. This is required for the compiling features to work.

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

=== Language checking ===

If you want to enable the language checking functions, install {{Pkg|hunspell}} and at least [https://archlinux.org/packages/?q=hunspell- one of the corresponding dictionaries]. The selection of languages available in TeXstudio will match the hunspell dictionaries installed. If no dictionaries are installed, it is impossible to select a language in the application.

You can also install {{Pkg|languagetool}} for a more advanced language check, or connect to a remote [https://languagetool.org LanguageTool] server. In any case, you need to install the hunspell dictionary for your desired language, otherwise TeXstudio will not let you select it, even if your LanguageTool installation or server supports it.

== Troubleshooting ==

=== Viewer does not work ===

Make sure that the output document type matches the viewer type under ''Options > Configure TeXStudio > Build''.

List of applications/Documents

2026-05-13T18:03:14Z

Erus Iluvatar: /* Graphical */ rm dropped ukui package

[[Category:Applications]]
[[Category:Lists of software]]
[[es:List of applications (Español)/Documents]]
[[hu:List of applications (Magyar)/Documents]]
[[ja:アプリケーション一覧/ドキュメント]]
[[pl:List of applications (Polski)/Documents]]
[[zh-hans:List of applications/Documents]]
{{List of applications navigation}}

== Text editors ==

See also [[Wikipedia:Comparison of text editors]].

Some of the lighter-weight [[List of applications/Utilities#Integrated development environments|Integrated development environments]] can also serve as text editors.

=== Console ===

* {{App|dte|Small, easy to use editor with multi-tabbed interface, syntax highlighting, ctags navigation, etc.|https://craigbarnes.gitlab.io/dte/|{{AUR|dte}}}}
* {{App|e3|Tiny editor without dependencies, written in assembly.|https://sites.google.com/site/e3editor/{{Dead link|2024|10|12|status=404}}|{{Pkg|e3}}}}
* {{App|ed|A POSIX-compliant line-oriented text editor. Useful for shell scripts, less so for manual usage. Original editor for Unix.|https://www.gnu.org/software/ed/ed.html|{{Pkg|ed}}}}
* {{App|ee|Classic curses-based text editor. Born in HP-UX, used in FreeBSD.|https://web.archive.org/web/20160719002816/http://www.users.qwest.net/~hmahon/|{{aur|ee-editor}}}}
* {{App|fresh|intuitive and accessible, high-performance terminal-based editor that "just works" on any hardware, for everyone.|https://getfresh.dev/|{{AUR|fresh-editor-bin}}}}
* {{App|[[Wikipedia:JED (text editor)|JED]]|Text editor that makes extensive use of the [[Wikipedia:S-Lang|S-Lang library]]. Includes a console version (jed) and an X-window version (xjed).|http://jedsoft.org/jed/|{{AUR|jed}}}}
* {{App|[[Wikipedia:Joe's Own Editor|JOE (Joe's Own Editor)]]|Terminal-based text editor designed to be easy to use.|https://joe-editor.sourceforge.io/|{{Pkg|joe}}}}
* {{App|[[Wikipedia:Midnight Commander|mcedit]]|Useful text editor that comes with Midnight Commander file manager.|https://www.ibiblio.org/mc/|{{Pkg|mc}}}}
* {{App|micro|Modern and intuitive terminal-based text editor, written in go and extensible through plugins.|https://micro-editor.github.io/|{{Pkg|micro}}}}
* {{App|Minimum Profit|Text editor for programmers.|https://triptico.com/software/mp.html|{{AUR|mp}}}}
* {{App|[[nano]]|Console text editor based on pico with on-screen key bindings help.|https://nano-editor.org/|{{Pkg|nano}}}}
* {{App|ne|Minimalist text editor with Windows-like key-bindings.|https://ne.di.unimi.it/|{{AUR|ne}}}}
* {{App|orbiton|Configuration-free text editor for quick edit-format-build cycles.|https://roboticoverlords.org/orbiton/|{{Pkg|orbiton}}}}
* {{App|Tilde|Intuitive text editor with Windows-like key bindings.|https://os.ghalkes.nl/tilde/|{{AUR|tilde}}}}

==== Emacs-style text editors ====

* {{App|[[Emacs]]|The extensible, customizable, self-documenting real-time display editor by GNU.|https://www.gnu.org/software/emacs/emacs.html|with GUI: {{Pkg|emacs}}, without GUI: {{Pkg|emacs-nox}}}}
* {{App|jove|Jonathan's Own Version of Emacs is an Emacs-like editor without Lisp.|https://github.com/jonmacs/jove|{{AUR|jove}}}}
* {{App|[[Wikipedia:mg (editor)|mg]]|Small, fast, and portable Emacs-like editor.|https://github.com/hboetes/mg|{{Pkg|mg}}}}
* {{App|[[Wikipedia:Vile (editor)|vile]]|Lightweight Emacs clone with ''vi''-like key bindings.|https://invisible-island.net/vile/vile.html|{{AUR|vile}}}}
* {{App|Zile|Lightweight Emacs clone.|https://www.gnu.org/software/zile/|{{AUR|zile}}}}
* {{App|Neomacs (NEO Emacs)|A GPU-powered Emacs written in Rust with a modern display engine.|https://github.com/eval-exec/neomacs}}

==== Vi-style text editors ====

* {{App|Amp|Text editor written in ''Rust'', that aims to take the core interaction model of ''Vim'', simplify it, and bundle in the essential features required for a modern text editor.|https://amp.rs/|{{AUR|amp}}}}
* {{App|Aretext|Minimalist text editor with ''Vim''-compatible key bindings.|https://aretext.org/|{{AUR|aretext}}}}
* {{App|[[BusyBox]] vi|A small ''vi'' clone. Can be invoked with {{ic|busybox vi}}.|https://git.busybox.net/busybox/tree/editors/vi.c|{{Pkg|busybox}}}}
* {{App|Elvis|A ''vi'' clone with optional X support.|http://elvis.the-little-red-haired-girl.org/|{{Aur|elvis}}}}
* {{App|[[Helix]]| A post-modern modal text editor.|https://helix-editor.com/|{{Pkg|helix}}}}
* {{App|[[Kakoune]]|Modal editor. Fewer keystrokes. Selection based, multi-cursor editing. Orthogonal design.|https://github.com/mawww/kakoune|{{Pkg|kakoune}}}}
* {{App|[[Neovim]]|''Vim'' rebirth for the 21st century.|https://neovim.io/|{{Pkg|neovim}}}}
* {{App|Neovim-Qt|Qt GUI for ''Neovim''.|https://github.com/equalsraf/neovim-qt|{{Pkg|neovim-qt}}}}
* {{App|[[Vim]] (Vi IMproved)|Is included as ''vi'' with most [[Wikipedia:UNIX|UNIX]] systems.|https://www.vim.org/|{{Pkg|vim}}; {{Pkg|gvim}} (with GUI)}}
* {{App|Vis|Modern, legacy free, simple yet efficient ''Vim''-like editor.|https://github.com/martanne/vis|{{Pkg|vis}}}}

=== Graphical ===

* {{App|[[Wikipedia:Acme (text editor)|Acme]]|Minimalist and flexible programming environment developed by Rob Pike for the Plan 9 operating system.|http://acme.cat-v.org/|{{Pkg|plan9port}}}}
* {{App|Adie|Fast and convenient programming text editor.|http://fox-toolkit.org/|{{Pkg|fox}}}}
* {{App|Beaver|GTK editor designed to be modular, lightweight and stylish.|https://beaver-editor.sourceforge.net/|{{AUR|beaver}}}}
* {{App|CorePad|Simple lightweight but powerful text editor with syntax-highlighting support for a dozen or more languages. Part of C-Suite.|https://cubocore.gitlab.io/|{{AUR|corepad}}}}
* {{App|COSMIC Text Editor|Text editor for the COSMIC desktop environment.|https://github.com/pop-os/cosmic-edit|{{Pkg|cosmic-text-editor}}}}
* {{App|Deepin Text Editor|Simple text editor for Deepin desktop.|https://www.deepin.org/en/original/deepin-editor/|{{Pkg|deepin-editor}}}}
* {{App|Ecrire|Simple text editor based on EFL.|https://git.enlightenment.org/enlightenment/ecrire|{{Pkg|ecrire}}}}
* {{App|FeatherPad|Minimal Qt5 plain text editor featuring a native dark theme and support for tabs, printing and syntax highlighting.|https://github.com/tsujan/FeatherPad|{{Pkg|featherpad}}}}
* {{App|FLTK Editor|Simple text editor application for FLTK.|https://www.fltk.org/|{{AUR|fltk-editor}}}}
* {{App|gCSVedit|Simple text editor for CSV, TSV and other kinds of delimiter-separated values (DSV) files.|https://github.com/goetzc/gCSVedit|{{AUR|gcsvedit-git}}}}
* {{App|Geany|Geany is a powerful, stable and lightweight programmer's text editor that provides tons of useful features without bogging down your workflow.
|https://www.geany.org/|{{pkg|geany}}}}
* {{App|[[Wikipedia:gedit|gedit]]|GTK editor for the GNOME desktop with syntax highlighting, automatic indentation, matching brackets, etc., and a number of add-ons to increase functionality. Part of {{Grp|gnome-extra}}.|https://gedit-technology.github.io/apps/gedit/|{{Pkg|gedit}}}}
* {{App|GNOME Text Editor|Simple text editor for GNOME focused on a pleasing default experience. Part of {{Grp|gnome}}.|https://apps.gnome.org/TextEditor/|{{Pkg|gnome-text-editor}}}}
* {{App|Gobby|Collaborative editor supporting multiple documents in one session and a multi-user chat.|https://gobby.github.io/|{{Pkg|gobby}}}}
* {{App|Howl|General purpose, fast and lightweight editor with a keyboard-centric minimalistic user interface.|https://howl.io/|{{AUR|howl}}}}
* {{App|[[Wikipedia:jEdit|jEdit]]|Text editor for programmers, written in Java.|https://www.jedit.org/|{{AUR|jedit}}}}
* {{App|[[Wikipedia:Kate (text editor)|Kate]]|Full-featured programmer's editor for the KDE desktop with MDI and a filesystem browser. Part of {{Grp|kde-utilities}}.|https://kate-editor.org/|{{Pkg|kate}}}}
* {{App|[[Wikipedia:KWrite|KWrite]]|Lightweight text editor for the KDE desktop that uses the same editor widget as Kate, now provided by the kate package. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/kwrite/|{{Pkg|kate}}}}
* {{App|L3afpad|Simple text editor forked from Leafpad, supports GTK 3.|https://github.com/stevenhoneyman/l3afpad|{{Pkg|l3afpad}}}}
* {{App|Lapce|Lightning-fast and Powerful Code Editor written in Rust.|https://lapce.dev/|{{Pkg|lapce}}}}
* {{App|[[Wikipedia:Leafpad|Leafpad]]|Notepad clone for GTK that emphasizes simplicity.|http://tarot.freeshell.org/leafpad/|{{AUR|leafpad}}}}
* {{App|Liri Text|Text editor for Liri.|https://github.com/lirios/text|{{AUR|liri-text}}}}
* {{App|Lite XL|A lightweight, simple, fast, feature-filled, and extremely extensible text editor written in C, and Lua, adapted from lite.|https://lite-xl.com/|{{Pkg|lite-xl}}}}
* {{App|medit|Programming and around-programming text editor.|https://mooedit.sourceforge.net|{{AUR|medit}}}}
* {{App|[[Wikipedia:Xfce#Mousepad|Mousepad]]|Fast text editor for the Xfce Desktop Environment.|https://www.xfce.org|{{Pkg|mousepad}}}}
* {{App|[[Wikipedia:NEdit|NEdit]]|Text editor for the Motif environment.|https://sourceforge.net/projects/nedit/|{{AUR|nedit}}}}
* {{App|Nota|Easy to use text editor with a simple interface with support for tabbed documents, syntax highlighting for various languages, Focus mode, annotations, configurable fonts, and colors, a side panel with an integrated file browser, and more. Part of {{Grp|maui}}.|https://mauikit.org/apps/nota/|{{Pkg|maui-nota}}}}
* {{App|Notepad Next|Reimplementation of Notepad++.|https://github.com/dail8859/NotepadNext|{{AUR|notepadnext}}}}
* {{App|Notepadqq|Qt-based, Notepad++-like text editor with support for syntax highlighting for more than 100 languages.|https://notepadqq.com/s/|{{AUR|notepadqq}}}}
* {{App|Pantheon Code|Code editor for elementaryOS. It auto-saves your files, meaning they are always up-to-date. Plus it remembers your tabs so you never lose your spot, even in between sessions.|https://github.com/elementary/code|{{Pkg|pantheon-code}}}}
* {{App|[[MATE|Pluma]]|Powerful text editor for MATE.|https://mate-desktop.org/|{{Pkg|pluma}}}}
* {{App|QSciTE|Qt clone of the SciTE text and code editor.|https://code.google.com/archive/p/qscite/|{{AUR|qscite}}}}
* {{App|[[Wikipedia:Sam (text editor)|Sam]]|Minimalist text editor with a graphical user interface, a very powerful command language and remote editing capabilities, developed by Rob Pike.|http://sam.cat-v.org|{{Pkg|plan9port}} or {{Pkg|9base}}}}
* {{App|[[Wikipedia:SciTE|SciTE]]|Generally useful editor with facilities for building and running programs.|https://scintilla.org/SciTE.html|{{Pkg|scite}}}}
* {{App|[[Wikipedia:Sublime Text|Sublime Text]]|Proprietary C++ and Python-based editor with many advanced features and plugins while staying lightweight and pretty.|https://www.sublimetext.com/|dev channel: {{AUR|sublime-text-dev}}, stable v4: {{AUR|sublime-text-4}}, stable v3: {{AUR|sublime-text-3}}, stable v2 {{AUR|sublime-text-2}}}}
* {{App|[[Wikipedia:TEA (text editor)|TEA]]|Qt-based feature-rich text editor.|http://semiletov.org/tea/|{{AUR|tea-qt}}}}
* {{App|[[Textadept]]|Lua-extensible feature rich text editor based on Scintilla and written in C.|https://foicica.com/textadept/|{{AUR|textadept}}}}
* {{App|Textosaurus|Simple cross-platform text editor based on Qt and QScintilla.|https://github.com/martinrotter/textosaurus|{{AUR|textosaurus}}}}
* {{App|Text Pieces|Powerful scratchpad with ability to perform a lot of text transformations.|https://apps.gnome.org/TextPieces/|{{Pkg|textpieces}}}}
* {{App|[[Visual Studio Code]]|Editor for building and debugging modern web and cloud applications.|https://code.visualstudio.com|{{Pkg|code}}}}
* {{App|[[Visual Studio Code|VSCodium]]|Visual Studio Code, but compiled without telemetry.|https://vscodium.com/|{{AUR|vscodium}}}}
* {{App|wxMEdit|Text/Hex editor written in C++ and wxWidgets.|https://wxmedit.github.io/|{{AUR|wxmedit}}}}
* {{App|xed|Text editor based on Pluma developed for Linux Mint.|https://github.com/linuxmint/xed|{{Pkg|xed}}}}
* {{App|XEdit|Simple text editor for the X Window System.|https://www.x.org/wiki|{{Pkg|xorg-xedit}}}}
* {{App|Zed|A high-performance, multiplayer code editor from the creators of Atom and Tree-sitter. It's also open source.|https://zed.dev|{{Pkg|zed}}}}

== Office ==

=== Office suites ===

See also [[Wikipedia:Comparison of office suites]].

* {{App|[[Wikipedia:Calligra Suite|Calligra]]|Actively developed fork of KOffice, the [[KDE]] office suite. It offers most of the features of OpenOffice. Part of {{Grp|kde-office}}.|https://calligra.org/|{{Pkg|calligra}}}}
* {{App|[[Wikipedia:Google Docs|Google Docs]]|Cloud office solution by Google.|https://docs.google.com|{{AUR|google-docs-bin}}}}
* {{App|[[LibreOffice]]|The office productivity suite compatible to the open and standardized ODF document format. Fork of OpenOffice, supported by The Document Foundation.|https://www.libreoffice.org/|{{Pkg|libreoffice-still}} or {{Pkg|libreoffice-fresh}}}}
* {{App|[[Wikipedia:OnlyOffice|OnlyOffice]]|Office suite that combines text, spreadsheet and presentation editors.|https://www.onlyoffice.com/|{{AUR|onlyoffice-bin}}}}
* {{App|[[OpenOffice]]|Open-source office software suite for word processing, spreadsheets, presentations, graphics, databases and more, under the Apache Licence.|https://www.openoffice.org/|{{AUR|openoffice-bin}}}}
* {{App|[[Wikipedia:SoftMaker Office|SoftMaker FreeOffice]]|Complete, reliable, lightning-fast and Microsoft Office-compatible proprietary office suite with a word processor, spreadsheet, and presentation graphics software.|https://www.freeoffice.com/|{{AUR|freeoffice}}}}
* {{App|[[WPS Office]]|Proprietary office productivity suite, previously known as Kingsoft Office.|https://www.wps.com/|{{AUR|wps-office}}}}
* {{App|Yozo Office|Proprietary office suite, compatible with MS Office.|https://www.yozosoft.com/product-officelinux.html|{{AUR|yozo-office}}}}

=== Word processors ===

See also [[Wikipedia:Comparison of word processors]].

* {{App|[[AbiWord]]|Full-featured word processor.|https://gitlab.gnome.org/World/AbiWord|{{Pkg|abiword}}}}
* {{App|[[Wikipedia:Calligra Words|Calligra Words]]|Powerful word processor included in the Calligra Suite. Part of {{Grp|kde-office}}.|https://calligra.org/components/words/|{{Pkg|calligra}}}}
* {{App|[[LibreOffice|LibreOffice Writer]]|Full-featured word processor included in the LibreOffice suite.|https://www.libreoffice.org/discover/writer|{{Pkg|libreoffice-still}} or {{Pkg|libreoffice-fresh}}}}
* {{App|[[OpenOffice|OpenOffice Writer]]|Full-featured word processor included in the OpenOffice suite.|https://www.openoffice.org/product/writer.html|{{AUR|openoffice-bin}}}}
* {{App|[[Wikipedia:Ted (word processor)|Ted]]|Easy to use GTK-based rich text processor (with footnote support).|https://nllgg.nl/Ted/{{Dead link|2025|03|15|status=404}}|{{AUR|ted}}}}
* {{App|[[Wikipedia:WordGrinder|WordGrinder]]|Word processor for the console.|https://cowlark.com/wordgrinder/|{{AUR|wordgrinder}}}}

==== WYSIWYG HTML editors ====

* {{App|PageEdit|ePub visual XHTML editor.|https://github.com/Sigil-Ebook/PageEdit|{{Pkg|pageedit}}}}
* {{App|[[Wikipedia:SeaMonkey#Composer|SeaMonkey Composer]]|Powerful yet simple HTML editor included in the SeaMonkey suite.|https://www.seamonkey-project.org/|{{AUR|seamonkey}}}}

==== Desktop publishing ====

* {{App|gLabels|Program for creating labels, business cards and media covers.|https://github.com/jimevins/glabels|{{Pkg|glabels}}}}
* {{App|[[Wikipedia:Scribus|Scribus]]|Desktop publishing program. Uses {{Pkg|hyphen}} and its language packs for hyphenation. |https://www.scribus.net/|{{Pkg|scribus}}}}

=== Presentations ===

* {{App|[[Wikipedia:Calligra Stage|Calligra Stage]]|Easy to use yet still flexible presentation application included in the Calligra Suite. Part of {{Grp|kde-office}}.|https://calligra.org/components/stage/|{{Pkg|calligra}}}}
* {{App|[[LibreOffice|LibreOffice Impress]]|Presentation program included in the LibreOffice suite.|https://www.libreoffice.org/discover/writer|{{Pkg|libreoffice-still}} or {{Pkg|libreoffice-fresh}}}}
* {{App|MDP|A command-line based markdown presentation tool.|https://github.com/visit1985/mdp|{{Pkg|mdp}}}}
* {{App|[[OpenOffice|OpenOffice Impress]]|Presentation program included in the OpenOffice suite.|https://www.openoffice.org/product/impress.html|{{AUR|openoffice-bin}}}}
* {{App|presenterm|A markdown terminal slideshow tool|https://mfontanini.github.io/presenterm/|{{Pkg|presenterm}}}}
* {{App|sent|Simple plaintext presentation tool.|https://git.suckless.org/sent/|{{AUR|sent}}}}
* {{App|Sozi|Zooming presentation editor and player. Based on the [https://electronjs.org/ Electron] platform.|https://sozi.baierouge.fr/|{{AUR|sozi}}}}
* {{App|Spice-Up|Create simple and beautiful presentations.|https://github.com/Philip-Scott/Spice-up|{{Pkg|spice-up}}}}

=== Spreadsheets ===
See also [[Wikipedia:Comparison of spreadsheet software]].

==== Console ====
* {{App|[[Wikipedia:sc (spreadsheet calculator)|sc]]|Curses-based lightweight spreadsheet.|https://ibiblio.org/pub/linux/apps/financial/spreadsheet/!INDEX.html|{{AUR|sc}}}}
* {{App|sc-im|Spreadsheet program based on sc.|https://github.com/andmarti1424/sc-im/|{{AUR|sc-im}}}}
* {{App|visidata|Python multitool for discovering and arranging data.|https://www.visidata.org/|{{pkg|visidata}}}}

==== Graphical ====
* {{App|[[Wikipedia:Calligra Sheets|Calligra Sheets]]|Powerful spreadsheet application included in the Calligra Suite. Part of {{Grp|kde-office}}.|https://calligra.org/components/sheets/|{{Pkg|calligra}}}}
* {{App|Gnumeric|Spreadsheet program for the GNOME desktop.|http://www.gnumeric.org/|{{Pkg|gnumeric}}}}
* {{App|[[LibreOffice|LibreOffice Calc]]|Full-featured spreadsheet application included in the LibreOffice suite.|https://www.libreoffice.org/discover/calc/|{{Pkg|libreoffice-still}} or {{Pkg|libreoffice-fresh}}}}
* {{App|[[OpenOffice|OpenOffice Calc]]|Full-featured spreadsheet application included in the OpenOffice suite.|https://www.openoffice.org/product/calc.html|{{AUR|openoffice-bin}}}}
* {{App|[[Wikipedia:Pyspread|Pyspread]]|Pyspread is a non-traditional spreadsheet application that is based on and written in the programming language Python.|https://pyspread.gitlab.io|{{AUR|pyspread}}}}

=== Database tools ===

For DBMS-specific tools, see:

* [[MySQL#Graphical tools]]
* [[PostgreSQL#Graphical tools]]
* [[SQLite#Software]]
* [[MongoDB#Tools]]

See also [[Wikipedia:Comparison of database tools]].

* {{App|[[Adminer]]|Full-featured database management webapp with support for many database types.|https://www.adminer.org/|{{AUR|adminer}}}}
* {{App|beekeeper-studio|A modern, easy to use, and good looking SQL client for MySQL, Postgres, SQLite, SQL Server, and more.|https://www.beekeeperstudio.io/|{{AUR|beekeeper-studio}}}}
* {{App|[[Wikipedia:DBeaver|DBeaver]]|Java-based graphical database editor with support for many database types.|https://dbeaver.io/|{{Pkg|dbeaver}}}}
* {{App|DbVisualizer|The Universal Database Tool|https://www.dbvis.com/|{{AUR|dbvis}}}}
* {{App|GdaBrowser|Graphical tool to get a quick access to a database's structure and contents.|https://www.gnome-db.org/GdaBrowser|{{AUR|libgda}}}}
* {{App|Harlequin|The SQL IDE for your terminal.|https://harlequin.sh/|{{AUR|harlequin}}}}
* {{App|HeidiSQL|The fast SQL IDE with support many for database types.|https://www.heidisql.com/|{{AUR|heidisql}}}}
* {{App|[[Wikipedia:Kexi|Kexi]]|Visual database applications creator tool by KDE, designed to fill the gap between spreadsheets and database solutions requiring more sophisticated development.|https://kexi-project.org/|{{AUR|kexi}}}}
* {{App|[[LibreOffice|LibreOffice Base]]|Full-featured desktop database front end included in the LibreOffice suite, designed to meet the needs of a broad array of users.|https://www.libreoffice.org/discover/base/|{{Pkg|libreoffice-still}} or {{Pkg|libreoffice-fresh}}}}
* {{App|[[OpenOffice|OpenOffice Base]]|Full-featured desktop database front end included in the OpenOffice suite, designed to meet the needs of a broad array of users.|https://www.openoffice.org/product/base.html|{{AUR|openoffice-bin}}}}
* {{App|[[Wikipedia:Orbada|Orbada]]|Excellent tool for database developers, SQL developers, DBA administrators, as well as for users who wish to broaden their knowledge and skills in SQL. Last release dated 2019-07-03. |https://orbada.sourceforge.io/|{{AUR|orbada}}}}
* {{App|Sequeler|SQL client built in Vala and Gtk. It allows you to connect to your local and remote databases, write SQL in a handy text editor with language recognition, and visualize SELECT results in a Gtk.Grid Widget.|https://github.com/Alecaddd/sequeler|{{AUR|sequeler}}}}
* {{App|[[Wikipedia:SQuirreL SQL Client|SQuirreL SQL Client]]|Graphical Java program that will allow you to view the structure of a JDBC compliant database, browse the data in tables, issue SQL commands etc.|http://www.squirrelsql.org/|{{AUR|squirrel-sql}}}}
* {{App|[[Wikipedia:TOra|TOra]]|Database management GUI that supports accessing most of the common database platforms in use, including Oracle, MySQL, and PostgreSQL, as well as limited support for any target that can be accessed through Qt's ODBC support.|https://github.com/tora-tool/tora/wiki|{{AUR|tora}}}}

==== Plain-text database utilities ====

These kinds of software are in a substance somewhat between [[AWK|text processing core utilities like awk]], [[#Spreadsheets|spreadsheets]] and production-level [[DBMS|database system]]. And they usually come with a non-SQL command-line interface.

* {{app|csvkit|CSV/TSV toolkit written in Python|https://csvkit.readthedocs.io|{{Pkg|csvkit}}}}
* {{app|csvtk|cross-platform, efficient and practical CSV/TSV toolkit written in Go|https://bioinf.shenwei.me/csvtk|{{AUR|csvtk}}}}
* {{app|datamash|GNU utility for basic numeric and statistical operations on plain text data.|https://www.gnu.org/software/datamash|{{pkg|datamash}}}}
* {{app|num-utils|A set of commandline programs for numeric calculations.|http://suso.suso.org/programs/num-utils/index.phtml|{{aur|num-utils}}}}
* {{app|recutils|GNU utilities to work with human-editable, plaintext database files (in a simple format called "recfile").|https://gnu.org/s/recutils/|{{aur|recutils}}}}
* {{app|tsv-utils|eBay's CLI tools for large, tabular data files, including filtering, statistics, sampling, and joins.|https://ebay.github.io/tsv-utils/|{{aur|tsv-utils}}}}

==== "Simplified" database software (beginner-friendly database tools) ====

* {{App|Symphytum|Personal database software for everyone who desires to manage and organize data in an easy and intuitive way, without having to study complex database languages and software user interfaces.|https://github.com/giowck/symphytum|{{AUR|symphytum}}}}
* {{App|TreeLine|Store almost any kind of information in a tree structure, which makes it easy to keep things organized.|https://treeline.bellz.org/|{{AUR|treeline}}}}

=== Formula editors ===

See also [[#TeX formula editors]] and [[Wikipedia:Formula editor]].

* {{App|[[LibreOffice|LibreOffice Math]]|Create and edit scientific formulas and equations. Included in the LibreOffice suite.|https://www.libreoffice.org/discover/math/|{{Pkg|libreoffice-still}} or {{Pkg|libreoffice-fresh}}}}
* {{App|[[OpenOffice|OpenOffice Math]]|Create equations and formulas for your documents. Included in the OpenOffice suite.|https://www.openoffice.org/product/math.html|{{AUR|openoffice-bin}}}}

== Markup languages ==

See also [[Wikipedia:Comparison of document markup languages]].

* {{App|[[Wikipedia:Txt2tags|txt2tags]]|Dead-simple, KISS-compliant lightweight, human-readable markup language to produce rich format content out of plain text files.|https://txt2tags.org/|{{Pkg|txt2tags}}}}

=== AsciiDoc ===

See also [[Wikipedia:AsciiDoc]].

* {{App|AsciiDoc.py|A legacy implementation written in Python. Used by Arch for generating ''pacman's'' man pages.[https://archlinux.org/pacman/pacman.8.html].|https://asciidoc-py.github.io/|{{Pkg|asciidoc}}}}
* {{App|Asciidoctor|An implementation written in Ruby, with [https://asciidoctor.org/docs/asciidoc-asciidoctor-diffs/ many extra features].|https://asciidoctor.org/|{{Pkg|asciidoctor}}}}

=== Markdown ===

See also the [https://daringfireball.net/projects/markdown/ official website] and [[Wikipedia:Markdown]].

* {{App|cmark|CommonMark parsing and rendering library and program in C.|https://github.com/commonmark/cmark|{{Pkg|cmark}}}}
* {{App|Discount|A Markdown implementation written in C.|https://www.pell.portland.or.us/~orc/Code/discount/|{{Pkg|discount}}, Ruby wrapper library: {{Pkg|ruby-rdiscount}}}}
* {{App|lowdown|Markdown translator producing HTML5 and roff documents in the ms and man formats.|https://kristaps.bsd.lv/lowdown/|{{Pkg|lowdown}}}}
* {{App|Marked|Markdown parser and compiler built for speed.|https://marked.js.org/|{{Pkg|marked}}}}
* {{App|md2html|C Markdown parser.|https://github.com/mity/md4c|{{Pkg|md4c}}}}
* [[Pandoc]] also supports Markdown.

==== Python implementations ====

* {{App|CommonMark-py|Python parser for the CommonMark Markdown specification.|https://github.com/rtfd/CommonMark-py|{{Pkg|python-commonmark}}}}
* {{App|Mistune|The fastest markdown parser in pure Python with renderer feature.|https://github.com/lepture/mistune|{{Pkg|python-mistune}}}}
* {{App|[[Wikipedia:MkDocs|MkDocs]]|Project documentation with Markdown.|https://www.mkdocs.org/|{{Pkg|mkdocs}}}}
* {{App|[[Wikipedia:MkDocs#Themes|MkDocs]]|[[Wikipedia:Material Design|Material design]] theme for MkDocs.|https://squidfunk.github.io/mkdocs-material/|{{Pkg|mkdocs-material}}}}
* {{App|MkDocs Material Extensions|Markdown extension resources for MkDocs Material.|https://github.com/facelessuser/mkdocs-material-extensions|{{AUR|mkdocs-material-extensions}}}}
* {{App|PyMdown Extensions|Extensions for Python-Markdown.|https://facelessuser.github.io/pymdown-extensions/|{{Pkg|python-pymdown-extensions}}}}
* {{App|Python-Markdown|Extensible Python implementation of John Gruber's Markdown.|https://github.com/Python-Markdown/markdown|{{Pkg|python-markdown}}}}

==== Ruby implementations ====

* {{App|kramdown|Fast, pure Ruby Markdown superset converter, using a strict syntax definition.|https://kramdown.gettalong.org/|{{Pkg|ruby-kramdown}}}}
* {{App|Maruku|Pure Ruby Markdown-superset interpreter.|https://github.com/bhollis/maruku|{{Pkg|ruby-maruku}}}}
* {{App|mdless|Pure Ruby terminal-based markdown viewer/interpeter.|https://github.com/ttscoff/mdless|{{AUR|ruby-mdless}}}}

==== Markdown editors ====

* {{App|[[Wikipedia:Apostrophe (text editor)|Apostrophe]]|Distraction free Markdown editor made with GTK.|https://apps.gnome.org/Apostrophe/|{{Pkg|apostrophe}}}}
* {{App|CuteMarkEd|Qt-based Markdown editor with live HTML preview, math expressions, code and markdown syntax highlighting. Discontinued since 2016.|https://cloose.github.io/CuteMarkEd/|{{AUR|cutemarked-git}}}}
* {{App|Formiko|reStructuredText and Markdown editor and live previewer written in Python with GTK.|https://github.com/ondratu/formiko|{{AUR|formiko}}}}
* {{App|ghostwriter|Distraction-free Markdown editor. Part of {{Grp|kde-office}}.|https://ghostwriter.kde.org/|{{Pkg|ghostwriter}}}}
* {{App|Marker|Simple yet robust Markdown editor.|https://fabiocolacio.github.io/Marker/|{{Pkg|marker}}}}
* {{App|Mark My Words|Minimal markdown editor.|https://github.com/voldyman/MarkMyWords|{{AUR|markmywords}}}}
* {{App|Mark Text|Next generation markdown editor. Based on the [https://electronjs.org/ Electron] platform.|https://github.com/marktext/marktext|{{AUR|marktext}}}}
* {{App|Remarkable|Fully featured Markdown editor.|https://remarkableapp.github.io/|{{AUR|remarkable}}}}
* {{App|ReText|Simple text editor for Markdown and reStructuredText.|https://github.com/retext-project/retext|{{Pkg|retext}}}}
* {{App|ThiefMD|Markdown and Fountain editor inspired by Ulysses.|https://thiefmd.com/|{{AUR|thiefmd}}}}
* {{App|Typora|Proprietary, minimalist Markdown editor.|https://typora.io/|{{AUR|typora}}}}
* {{App|[[Zettlr]]|A cross-platform markdown editor, inspired by the [[Wikipedia:Zettelkasten|Zettelkasten]] system for note-taking and personal knowledge management. Based on the [https://electronjs.org/ Electron] platform.|https://www.zettlr.com/|{{Pkg|zettlr}}}}

=== reStructuredText ===

See also [[Wikipedia:ReStructuredText|reStructuredText]].

* {{App|Docutils|Set of tools for processing plaintext (reStructuredText) docs into formats such as HTML, XML, or LaTeX.|https://docutils.sourceforge.io/|{{Pkg|python-docutils}}}}
* {{App|rstcheck|Checks syntax of reStructuredText and code blocks nested within it.|https://github.com/rstcheck/rstcheck|{{Pkg|rstcheck}}}}
* {{App|[[Wikipedia:Sphinx_(documentation_generator)|Sphinx]]| A documentation generation system using reStructuredText to generate output in multiple formats (primary documentation system for the Python project).|https://www.sphinx-doc.org/|{{Pkg|python-sphinx}}}}

=== Typesetting systems ===

* {{App|[[Wikipedia:groff (software)|groff]]|[[GNU]] implementation of troff, a heirloom Unix document processing system and the default formatter for [[man page]]s.|https://www.gnu.org/software/groff/groff.html|{{Pkg|groff}}}}
* {{App|[[Lout]]|A lightware document formatting system. Reads a high-level description of a document similar in style to LaTeX and produces a PostScript.|https://savannah.nongnu.org/projects/lout|{{pkg|lout}}}}
* {{App|SILE|Modern typesetting system inspired by TeX.|https://sile-typesetter.org/|{{Pkg|sile}}}}
* {{App|Speedata|A database publishing software that creates high-quality layouted PDFs fully automatically.|https://www.speedata.de/|{{AUR|speedata-publisher}}}}
* {{App|[[TeX]]|A high-quality typesetting system popular in academia.|https://tug.org/|{{Pkg|texlive-basic}}}}
* {{App|[[Texinfo]]|Typesetting syntax for software manuals used by the [[GNU Project]].|https://www.gnu.org/software/texinfo/|{{Pkg|texinfo}}}}
* {{App|Typst|A markup-based typesetting system for the sciences.|https://github.com/typst/typst|{{Pkg|typst}}}}

=== TeX editors ===

With [[TeX Live|TeX, LaTeX and friends]], creation of any scientific document, article, journal, etc. is made commonplace.

See also [[Wikipedia:Comparison of TeX editors]] and [[Wikibooks:LaTeX/Installation#Editors]].

* {{App|[[Wikipedia:AUCTeX|AUCTeX]]|Together with RefTex, AUCTeX provices an extensible environment for writing and formatting TeX files in [[Emacs]].|https://www.gnu.org/software/auctex/|{{AUR|auctex}}}}
* {{App|Enter TeX|LaTeX editor for [[GNOME]], previously known as [[Wikipedia:GNOME-LaTeX|GNOME LaTeX]].|https://gitlab.gnome.org/World/gedit/enter-tex|{{Pkg|enter-tex}}}}
* {{App|[[gedit]] LaTeX Plugin|Add code-completion to gedit and allows for compiling LaTeX documents and managing BibTeX bibliographies.|https://wiki.gnome.org/Apps/Gedit/LaTeXPlugin|{{AUR|gedit-latex}}}}
* {{App|[[Wikipedia:Gummi (software)|Gummi]]|Lightweight TeX/LaTeX GTK-based editor. It features a continuous preview mode, integrated BibTeX support, extendable snippet interface and multi-document support.|https://github.com/alexandervdm/gummi/|{{Pkg|gummi}}}}
* {{App|[[Wikipedia:Kile|Kile]]|User-friendly TeX/LaTeX editor for the KDE desktop with many features.|https://apps.kde.org/kile/|{{Pkg|kile}}}}
* {{App|Ktikz|Small application helping you to create [[Wikipedia:PGF/TikZ|PGF/TikZ]] diagrams for your publications.|https://www.hackenberger.at/blog/ktikz-editor-for-the-tikz-language/|KDE: {{Pkg|ktikz}}, Qt: {{Pkg|qtikz}}}}
* {{App|[[Wikipedia:LyX|LyX]]|Document processor that encourages an approach to writing based on the structure of your documents (WYSIWYM) and not simply their appearance (WYSIWYG).|https://www.lyx.org/|{{AUR|lyx}}}}
* {{App|Setzer|LaTeX editor written in Python with GTK.|https://www.cvfosammmm.org/setzer/|{{Pkg|setzer}}}}
* {{App|[[Wikipedia:GNU TeXmacs|TeXmacs]]|WYSIWYW (what you see is what you want) editing platform with special features for scientists.|https://www.texmacs.org/|{{AUR|texmacs}}}}
* {{App|[[Wikipedia:Texmaker|Texmaker]]|Cross-platform, light and easy-to-use LaTeX IDE. It integrates many tools needed to develop documents with LaTeX, in just one application|https://www.xm1math.net/texmaker/|{{Pkg|texmaker}}}}
* {{App|[[TeXstudio]]|Fork of TeXMaker including support for code completion of bibtex items, grammar check and automatic detection of the need for multiple LaTeX runs.|https://texstudio.sourceforge.net/|{{Pkg|texstudio}}}}
* {{App|[[Wikipedia:TeXworks|TeXworks]]|Simple TeX front-end program modeled after TeXShop.|https://tug.org/texworks/|{{Pkg|texworks}}}}
* {{App|TikZiT|Graphical tool for rapidly creating graphs and diagrams using [[Wikipedia:PGF/TikZ|PGF/TikZ]].|https://tikzit.github.io/|{{AUR|tikzit}}}}
* {{App|[[Vim|Vim-LaTeX-suite]]|Customizable LaTeX environment for Vim.|https://vim-latex.sourceforge.net/|{{Pkg|vim-latexsuite}}}}

=== TeX formula editors ===

* {{App|EqualX|LaTeX equation editor with real time preview.|https://equalx.sourceforge.net/|{{AUR|equalx}}}}
* {{App|KLatexFormula|GUI for generating images from LaTeX equations.|https://klatexformula.sourceforge.io/|{{AUR|klatexformula}}}}
* {{App|[[LibreOffice]] TexMaths extension|LaTeX equation editor for LibreOffice.|http://roland65.free.fr/texmaths/|{{Pkg|libreoffice-extension-texmaths}}}}

=== XML editors ===

See also [[Wikipedia:Comparison of XML editors]].

* {{App|QXmlEdit|Simple Qt XML editor and XSD viewer.|https://qxmledit.org/|{{AUR|qxmledit}}}}
* {{App|XML Copy Editor|Fast, validating XML editor.|https://xml-copy-editor.sourceforge.io/|{{AUR|xmlcopyeditor}}}}
* {{App|XML Tree Editor|Displays XML files as tree views and allows basic operations: adding, editing and deleting text nodes and their attributes.|https://sourceforge.net/projects/xmltreeeditor/|{{AUR|xmltreeedit-bin}}}}

== Document converters ==

See also [[#Markup languages]] and [[PDF, PS and DjVu]].

* {{App|[[Wikipedia:Antiword|Antiword]]|MS Word to text converter.|https://web.archive.org/web/20221207132720/http://www.winfield.demon.nl|{{Pkg|antiword}}}}
* {{App|catdoc|Converter for Microsoft Word, Excel, PowerPoint and RTF files to text.|https://wagner.pp.ru/~vitus/software/catdoc/|{{Pkg|catdoc}}}}
* {{App|docx2txt|MS Word Docx to text converter.|https://docx2txt.sourceforge.net/|{{Pkg|docx2txt}}}}
* {{App|HTMLDOC|Reads HTML and Markdown source files or web pages and generates corresponding EPUB, HTML, PostScript, or PDF files with an optional table of contents.|https://www.msweet.org/htmldoc/|{{Pkg|htmldoc}}}}
* {{App|Morphosis|Document conversion app using Pandoc and WebKitGTK.|https://gitlab.gnome.org/World/morphosis|{{Pkg|morphosis}}}}
* {{App|[[MuPDF|mutool]]|All purpose tool based on MuPDF for dealing with document files in various manners.|https://mupdf.com/|{{Pkg|mupdf-tools}}}}
* {{App|obsidian2web|Generates static websites from Obsidian Markdown text files.|https://github.com/lun-4/obsidian2web|{{AUR|obsidian2web}}}}
* {{App|[[Wikipedia:Pandoc|Pandoc]]|Swiss-army knife for converting markup and document formats.|https://pandoc.org/|{{Pkg|pandoc-cli}}}}
* {{App|unoconv|Libreoffice-based document converter.|https://github.com/unoconv/unoconv|{{Pkg|unoconv}}}}
* {{App|UnRTF|Command-line program which converts RTF documents to other formats.|https://www.gnu.org/software/unrtf/unrtf.html|{{Pkg|unrtf}}}}

== Bibliographic reference managers ==

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

* {{App|Citations|Manage your bibliographies using the BibTeX format.|https://apps.gnome.org/Citations/|{{Pkg|citations}}}}
* {{App|[[Wikipedia:JabRef|JabRef]]|Java GUI frontend for managing BibTeX and other bibliographies.|https://www.jabref.org/|{{AUR|jabref}}}}
* {{App|[[Wikipedia:KBibTeX|KBibTeX]]|BibTeX editor by KDE to edit bibliographies used with LaTeX.|https://apps.kde.org/kbibtex/|{{Pkg|kbibtex}}}}
* {{App|[[Wikipedia:Mendeley|Mendeley Desktop]]|Proprietary reference manager and academic social network.|https://www.mendeley.com/|{{AUR|mendeleydesktop}}}}
* {{App|Papis|A command-line based document and bibliography manager.|https://github.com/papis/papis|{{AUR|papis}}}}
* {{App|[[Wikipedia:Zotero|Zotero]]|An easy-to-use tool to help you collect, organize, cite, and share your research sources. Can import and export BibTeX and has browser extensions.|https://www.zotero.org/|{{AUR|zotero}}}}

== Readers and viewers ==

* {{App|NFO Viewer|Simple viewer for NFO files.|https://otsaloma.io/nfoview/|{{Pkg|nfoview}}}}

=== PDF and DjVu ===

See [[PDF, PS and DjVu]].

=== E-book ===
* {{App|Arianna|An ebook reader and library management app supporting EPUB files. Part of {{Grp|kde-graphics}}.|https://apps.kde.org/arianna/|{{Pkg|arianna}}}}
* {{App|baca|console epub reader.|https://github.com/wustho/baca|{{AUR|baca-ereader-git}}}}
* {{App|Beseda|Accessible (for visually impaired) console ebook-reader that can speak TXT, FB2, ABW, [X]HTML, ODT, DOCX books and documents.|https://psemiletov.github.io/beseda/|{{AUR|beseda}}}}
* {{App|Bookworm|Simple, focused e-book reader for Elementary OS with EPUB, PDF, Mobipocket and Comicbook support.|https://babluboy.github.io/bookworm/|{{Pkg|bookworm}}}}
* {{App|[[Wikipedia:Calibre (software)|Calibre]]|E-book library management application that can also edit EPUB files, convert between different formats and sync with a variety of e-book readers. Supported formats include CHM, Comicbook, DjVu, DOCX, EPUB, FictionBook, HTML, HTMLZ, Kindle, LIT, LRF, Mobipocket, ODT, PDF, PRC, PDB, PML, RB, RTF, SNB, TCR, TXT and TXTZ.|https://calibre-ebook.com/|{{Pkg|calibre}}}}
* {{App|Cool Reader|E-book viewer with many supported formats such as EPUB (non-DRM), FictionBook, TXT, RTF, HTML, CHM and TCR.|https://sourceforge.net/projects/crengine/|{{AUR|coolreader}}}}
* {{App|[[Wikipedia:FBReader|FBReader]]|E-book viewer with many supported formats such as EPUB, FictionBook, HTML, plucker, PalmDoc, zTxt, TCR, CHM, RTF, OEB, Mobipocket (non-DRM) and TXT.|https://fbreader.org/|{{Pkg|fbreader}}}}
* {{App|Foliate|Simple and modern GTK eBook reader. Supports EPUB, Mobipocket, Kindle, FictionBook, and Comicbook formats.|https://johnfactotum.github.io/foliate/|{{Pkg|foliate}}}}
* {{App|KOReader|An ebook reader application supporting PDF, DjVu, EPUB, FB2 and many more formats, running on Cervantes, Kindle, Kobo, PocketBook and Android devices|https://github.com/koreader/koreader|{{AUR|koreader-appimage}}}}
* {{App|Lector|Qt based e-book reader with PDF, EPUB, Kindle, Mobipocket and Comicbook support.|https://github.com/BasioMeusPuga/Lector|{{AUR|lector}}}}
* {{App|Readest|Modern, feature-rich ebook reader|https://github.com/readest/readest|{{Pkg|readest}}}}
* {{App|[[Wikipedia:Sigil (application)|Sigil]]|WYSIWYG EPUB e-book editor.|https://sigil-ebook.com/|{{pkg|sigil}}}}

Some [[PDF, PS and DjVu#Viewers|PDF viewers]] like apvlv, Atril, [[MuPDF]], [[Wikipedia:Okular|Okular]], Xreader, and [[Zathura]] also support the EPUB format.

=== Comic book ===

* {{App|Automedia|A very small downloader for manga and anime from various websites. Designed to be a much more lightweight alternative to HakuNeko. Written primarly in C.|https://git.dec05eba.com/AutoMedia/about/|{{AUR|automedia}}}}
* {{App|HakuNeko|Downloader for manga and anime from various websites. Based on the [https://electronjs.org/ Electron] platform.|https://github.com/manga-download/hakuneko|{{AUR|hakuneko-desktop-bin}}}}
* {{App|Kindle Comic Converter|Allows you to transform your PNG, JPG, GIF, CBZ, CBR and CB7 files into EPUB or MOBI format e-books.|https://github.com/ciromattia/kcc/|{{AUR|kcc}}}}
* {{App|Komikku|Online/offline manga reader for GNOME.|https://apps.gnome.org/Komikku/|{{Pkg|komikku}}}}
* {{App|Manga Reader|Manga reader for local files. Supports zip, rar, tar, 7z, cbz, cbr, cbt, cb7 files and also folders.|https://github.com/g-fb/mangareader|{{AUR|mangareader}}}}
* {{App|MComix|GTK3 image viewer specifically designed to handle comic book archives (fork of Comix). Also includes library manager.|https://github.com/multiSnow/mcomix3|{{AUR|mcomix}}}}
* {{App|QComicBook| Viewer for comic book archives that aims at convenience and simplicity.|https://github.com/stolowski/QComicBook|{{AUR|qcomicbook}}}}
* {{App|QuickMedia|Online manga reader. Supports automatically upscaling pages with {{Pkg|waifu2x-ncnn-vulkan}}|https://git.dec05eba.com/QuickMedia/about/|{{AUR|quickmedia}}}}
* {{App|YACReader|Comic book viewer written in C++ and Qt5. Comes with YACReaderLibrary for managing comics.|https://yacreader.com/|{{AUR|yacreader}}}}

Some [[PDF, PS and DjVu#Viewers|PDF]] and E-book viewers like Atril, Bookworm, [[Wikipedia:Calibre (software)|Calibre]], Foliate, [[GNOME/Document viewer|GNOME Document Viewer]], Lector, [[MuPDF]], [[Wikipedia:Okular|Okular]], Papers, Xreader and [[Zathura]] also support the Comicbook format.

=== CHM ===

See also [[Wikipedia:Microsoft Compiled HTML Help]].

* {{App|Archmage|Extensible reader and decompiler for files in the CHM format.|https://github.com/dottedmag/archmage|{{AUR|archmage}}}}
* {{App|Kchmviewer|Qt-based CHM viewer that uses chmlib and borrows some ideas from xchm. It does not depend on [[KDE]], but it can be compiled to integrate with it.|https://www.ulduzsoft.com/linux/kchmviewer/|{{AUR|kchmviewer}}}}
* {{App|[[Wikipedia:xCHM|xCHM]]|Lightweight CHM viewer, based on chmlib.|https://github.com/rzvncj/xCHM|{{Pkg|xchm}}}}

Some [[PDF, PS and DjVu#Viewers|PDF]] and E-book viewers like Cool Reader, [[Wikipedia:FBReader|FBReader]] and [[Wikipedia:Okular|Okular]] also support the CHM format.

== Document managers ==

* {{App|Paperwork|Personal document manager. It manages scanned documents and PDFs.|https://openpaper.work/|{{Pkg|paperwork}}}}
* {{App|Shelf|Document collection manager that supports PDF files. Part of {{Grp|maui}}.|https://mauikit.org/apps/shelf/|{{Pkg|maui-shelf}}}}
* {{App|Thingy|Application to quickly access recent and favorite documents.|https://github.com/linuxmint/thingy|{{Pkg|thingy}}}}

== Scanning software ==

See [[SANE#Frontends]]

* {{App|ScanTailor Advanced|Interactive post-processing tool for scanned pages. Fork of Scan Tailor with additional features and fixes.|https://github.com/ScanTailor-Advanced/scantailor-advanced|{{Pkg|scantailor-advanced}}}}

== OCR software ==

=== Console ===

See also [[Wikipedia:Comparison of optical character recognition software]].

* {{App|[[Wikipedia:CuneiForm (software)|CuneiForm]]|Command line OCR system originally developed and open sourced by Cognitive technologies. Supported languages: eng, ger, fra, rus, swe, spa, ita, ruseng, ukr, srp, hrv, pol, dan, por, dut, cze, rum, hun, bul, slo, lav, lit, est, tur.|https://launchpad.net/cuneiform-linux|{{AUR|cuneiform}}}}
* {{App|[[Wikipedia:GOCR|GOCR]]|OCR engine which also supports barcode recognition.|https://www-e.uni-magdeburg.de/jschulen/ocr/|{{Pkg|gocr}}}}
* {{App|[[Wikipedia:Ocrad|Ocrad]]|OCR program based on a feature extraction method.|https://www.gnu.org/software/ocrad/|{{Pkg|ocrad}}}}
* {{App|OCRmyPDF|Adds an OCR text layer to scanned PDF files, allowing them to be searched.|https://github.com/jbarlow83/OCRmyPDF|{{AUR|ocrmypdf}}}}
* {{App|[[Wikipedia:Tesseract (software)|Tesseract]]|Accurate open source OCR engine. Package splitted, you need install some datafiles for each language ({{Pkg|tesseract-data-eng}} for example).|https://github.com/tesseract-ocr|{{Pkg|tesseract}}}}

=== Graphical ===

* {{App|gImageReader|Graphical GTK/Qt frontend to Tesseract.|https://github.com/manisandro/gImageReader|GTK: {{Pkg|gimagereader-gtk}}, Qt: {{Pkg|gimagereader-qt}}}}
* {{App|[[Wikipedia:Scanner Access Now Easy#gscan2pdf|gscan2pdf]]|Scans, runs an OCR engine, minor post-processing, creates a document.|https://gscan2pdf.sourceforge.net/|{{Pkg|gscan2pdf}}}}
* {{App|Linux-Intelligent-Ocr-Solution|Easy-OCR solution and Tesseract trainer for converting print into text using either scanner or a camera.|https://sourceforge.net/projects/lios/|{{AUR|lios-git}}}}
* {{App|[[Wikipedia:OCRFeeder|OCRFeeder]]|Python GUI for GNOME which performs document analysis and rendition, and can use either CuneiForm, GOCR, Ocrad or Tesseract as OCR engines. It can import from PDF or image files, and export to HTML or OpenDocument.|https://wiki.gnome.org/Apps/OCRFeeder|{{Pkg|ocrfeeder}}}}
* {{App|Paperwork|Personal document manager. It manages scanned documents and PDFs.|https://openpaper.work/|{{Pkg|paperwork}}}}
* {{App|Scans to PDF|Create small, searchable PDFs from scanned documents.|https://github.com/Unrud/djpdf|{{AUR|djpdf}}}}
* {{App|YAGF|Graphical interface for the CuneiForm text recognition program on the Linux platform.|https://sourceforge.net/projects/yagf-ocr/|{{AUR|yagf}}}}

== Notes ==

=== Note-taking software ===

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

==== Console ====

* {{App|dnote|A simple command line notebook for programmers|https://github.com/dnote/dnote|{{AUR|dnote-cli-bin}}}}
* {{App|[[eureka]]|CLI tool to input and store your ideas without leaving the terminal|https://github.com/simeg/eureka|{{AUR|eureka-notes}}}}
* {{App|kb|A minimalist terminal-based knowledge manager.|https://github.com/gnebbia/kb|{{AUR|kb}}}}
* {{App|nb|A command line and local web note‑taking, bookmarking, archiving, and knowledge base application.|https://xwmx.github.io/nb/|{{AUR|nb}}}}
* {{App|[[Wikipedia:org-mode|Org mode]]|[[Emacs]] mode for notes, project planning and authoring.|https://orgmode.org/|{{AUR|emacs-org-mode}}}}
* {{App|tnote|Small note taking program for the terminal.|https://sourceforge.net/projects/tnote/|{{AUR|tnote}}}}
* {{App|Vimwiki|Personal wiki for [[Vim]] – interlinked, plain text files written in a markup language.|https://vimwiki.github.io/|{{AUR|vim-vimwiki}}}}

==== Graphical ====

* {{App|Anytype|A local-first, privacy-focused personal knowledge app that lets you organize and manage notes, databases and information in a flexible, customizable way.|https://anytype.io/|{{AUR|anytype-bin}}}}
* {{App|[[Wikipedia:BasKet Note Pads|BasKet]]|Application for organizing, sharing, and taking notes. It can manage various types of information such as to-do lists, links, pictures, and other types, similar to a scrapbook.|https://basket-notepads.github.io/|{{AUR|basket}}}}
* {{App|Bijiben|Note editor for GNOME designed to remain simple to use.|https://wiki.gnome.org/Apps/Notes|{{Pkg|gnome-notes}}}}
* {{App|Boostnote|Note-taking application for programmers that focuses on markdown, snippets, and customizability. Based on the [https://electronjs.org/ Electron] platform.|https://boostnote.io/|{{AUR|boostnote-bin}}}}
* {{App|Buho|Task and note keeper to save links, write quick notes and organize pages as books. Part of {{Grp|maui}}.|https://mauikit.org/apps/buho/|{{Pkg|buho}}}}
* {{App|Cherrytree|Hierarchical note taking application, featuring rich text and syntax highlighting, storing data in a single xml or sqlite file.|https://www.giuspen.com/cherrytree/|{{Pkg|cherrytree}}}}
* {{App|Deepin Voice Notes|Lightweight memo tool to make text notes and voice recordings.|https://github.com/linuxdeepin/deepin-voice-note|{{Pkg|deepin-voice-note}}}}
* {{App|Encryptic|JavaScript note taking application with Markdown editor and encryption support. Based on the [https://electronjs.org/ Electron] platform.|https://www.encryptic.org/{{Dead link|2025|11|17|status=domain name not resolved}}|{{AUR|encryptic}}}}
* {{App|FeatherNotes|Lightweight Qt hierarchical notes-manager.|https://github.com/tsujan/feathernotes|{{Pkg|feathernotes}}}}
* {{App|FromScratch|Simple but smart note-taking application that you can use as a quick note taking or todo app. Based on the [https://electronjs.org/ Electron] platform.|https://fromscratch.rocks/|{{AUR|fromscratch-bin}}}}
* {{App|[[Wikipedia:Gnote|Gnote]]|Port of Tomboy to C++. It is the same note taking application, including most of the add-ins.|https://wiki.gnome.org/Apps/Gnote|{{Pkg|gnote}}}}
* {{App|Iotas|Simple note taking with Markdown support and optional Nextcloud Notes sync.|https://apps.gnome.org/Iotas/|{{Pkg|iotas}}}}
* {{App|[[Joplin]]|Note taking and to-do application, which can handle a large number of notes organized into notebooks on desktop or mobile devices. It synchronizes with WebDAV, Dropbox, OneDrive, NextCloud, S3 (beta) and other backends. Based on the [https://electronjs.org/ Electron] platform.|https://joplinapp.org/|CLI app: {{AUR|joplin}}, desktop app: {{AUR|joplin-desktop}}}}
* {{App|KeepNote|Cross-platform GTK note-taking application with rich text formatting.|http://keepnote.org|{{AUR|keepnote}}}}
* {{App|KleverNotes|Note-taking and management application using markdown.|https://apps.kde.org/klevernotes/|{{Pkg|klevernotes}}}}
* {{App|Logseq|A local-first, non-linear, outliner notebook for organizing and sharing your personal knowledge base.|https://logseq.com/|{{AUR|logseq-desktop}}}}
* {{App|Marknote|A simple markdown note management app for KDE.|https://apps.kde.org/marknote/|{{Pkg|marknote}}}}
* {{App|[[Wikipedia:MyNotex|MyNotex]]|Note-taking, document file and activity manager.|https://sites.google.com/site/mynotex/|{{AUR|mynotex}}}}
* {{App|[[Nextcloud]] Notes|Simple notes app for Nextcloud.|https://github.com/nextcloud/notes|{{Pkg|nextcloud-app-notes}}}}
* {{App|NixNote|Helps you take notes and stay organized. Create text notes, attach files or images, and even synchronize with Evernote. Formerly called Nevernote.|http://nixnote.org/|{{aur|nixnote2}}}}
* {{App|Norka|Note-taking software with Markdown support designed for Pantheon.|https://tenderowl.com/work/norka/|{{AUR|norka}}}}
* {{App|Notejot|Stupidly simple sticky notes applet for elementaryOS.|https://github.com/lainsce/notejot|{{AUR|notejot}}}}
* {{App|Notes|Note-taking application, write down your thoughts.|https://www.get-notes.com/|{{AUR|notes}}}}
* {{App|Notes-Up|Markdown notes editor and manager for elementaryOS.|https://github.com/Philip-Scott/Notes-up|{{Pkg|notes-up}}}}
* {{App|[[Notion-app|Notion]]|Note-taking, task management, project management, knowledge management software|https://www.notion.so|{{AUR|notion-app-electron}}}}
* {{App|Notorious|Keyboard centric note-taking application with Markdown syntax highlighting support.|https://notorious.gabmus.org/|{{AUR|notorious-git}}}}
* {{App|nvPY|Simplenote syncing note-taking application, inspired by Notational Velocity and ResophNotes, but uglier and cross-platformerer.|https://github.com/cpbotha/nvpy|{{AUR|nvpy}}}}
* {{App|Obsidian|Personal knowledge base that uses markdown text files to organize notes in a format that mirrors the human brain.|https://obsidian.md/|{{Pkg|obsidian}}}}
* {{App|OutWiker|Store notes in a tree.|https://jenyay.net/Outwiker/English|{{AUR|outwiker}}}}
* {{App|[[Wikipedia:QOwnNotes|QOwnNotes]]|Notepad and todo list manager with markdown support and optional ownCloud integration built on Qt5.|https://www.qownnotes.org/|{{AUR|qownnotes}}}}
* {{App|[[Wikipedia:Simplenote|Simplenote]]|The simplest way to keep notes. Based on the [https://electronjs.org/ Electron] platform.|https://simplenote.com/|{{AUR|simplenote-electron-bin}}}}
* {{App|Standard Notes|Simple and private notes application which focuses on simplicity, and encrypts data locally before it ever touches a cloud. Based on the [https://electronjs.org/ Electron] platform.|https://standardnotes.com/|{{AUR|standardnotes}}}}
* {{App|[[Wikipedia:TagSpaces|TagSpaces]]|Offline personal data manager for managing of your local files. Based on the [https://electronjs.org/ Electron] platform.|https://www.tagspaces.org/|{{AUR|tagspaces}}}}
* {{App|Tangent|Open-source note-taking app with local Markdown files, linked notes, interactive maps, and sliding panels for navigation.|https://www.tangentnotes.com/|{{AUR|tangent-bin}}}}
* {{App|[[Wikipedia:TiddlyWiki|TiddlyWiki]]|Unique non-linear notebook for capturing, organizing and sharing complex information.|https://tiddlywiki.com/|{{AUR|tiddlywiki}}}}
* {{App|VNote|Vim-inspired note-taking application that knows programmers and Markdown better.|https://vnotex.github.io/vnote|{{AUR|vnote}}}}
* {{App|[[Zim]]|WYSIWYG text editor that aims at bringing the concept of a wiki to the desktop.|https://zim-wiki.org/|{{Pkg|zim}}}}
* {{App|zNotes|Lightweight application for notes management with simple interface.|https://sourceforge.net/projects/znotes/|{{AUR|znotes}}}}
* {{App|μPad|Note-taking app that helps you organise + take notes without restrictions. Based on the [https://electronjs.org/ Electron] platform.|https://getmicropad.com|{{AUR|micropad}}}}

==== Stylus note-taking ====

* {{App|Cournal|Collaborative note taking and journal application using a stylus. It allows multiple users to annotate PDF files in real-time.|https://github.com/flyser/cournal|{{AUR|cournal}}}}
* {{App|Rnote|A simple note taking application written in Rust and GTK4.|https://github.com/flxzt/rnote|{{Pkg|rnote}}}}
* {{App|[[Saber]]|Open source libre cross platform note taking app|https://github.com/adil192/saber|{{AUR|saber}}}}
* {{App|Write|A proprietary word processor for handwriting.|http://www.styluslabs.com/|{{AUR|write_stylus}}}}
* {{App|Xournal|Application for notetaking, sketching and keeping a journal using a stylus. Capable of annotating existing PDF files as well.|https://xournal.sourceforge.net/|{{AUR|xournal}}}}
* {{App|[[Xournal++]]|Notetaking software designed around a tablet. C++ rewrite of Xournal with PDF annotation support.|https://github.com/xournalpp/xournalpp|{{Pkg|xournalpp}}}}

=== Diary ===

* {{App|Almanah|Small GTK application to allow you to keep a diary of your life.|https://wiki.gnome.org/Apps/Almanah_Diary|{{Pkg|almanah}}}}
* {{App|Lifeograph|Off-line and private journal and note taking application. It offers a rich feature set presented in a clean and simple user interface.|https://lifeograph.sourceforge.net/|{{Pkg|lifeograph}}}}
* {{App|RedNotebook|Modern journal, which lets you format, tag and search your entries.|https://rednotebook.sourceforge.io/|{{Pkg|rednotebook}}}}
* {{App|Simple Diary|Simple and lightweight diary app with Markdown support.|https://github.com/johan-bjareholt/simple-diary-gtk|{{AUR|simple-diary-gtk}}}}

=== Mind-mapping ===

See also [[Wikipedia:List of concept- and mind-mapping software]].

* {{App|[[Wikipedia:FreeMind|FreeMind]]|A mind mapper, and a hierarchical editor with strong emphasis on folding. Could be used for knowledge and content management.|https://freemind.sourceforge.io/wiki/|{{AUR|freemind-bin}}}}
* {{App|[[Wikipedia:Freeplane|Freeplane]]|Fork of FreeMind, supports thinking, sharing information and getting things done at work. The software can be used for mind mapping and analyzing the information contained in mind maps.|https://www.freeplane.org/|{{Pkg|freeplane}}}}
* {{App|Minder|Mind-mapping application designed for Pantheon.|https://github.com/phase1geo/Minder/|{{Pkg|minder}}}}
* {{App|MindMaster|Proprietary mindmap and brainstorm software with modern UI and beautiful template. It also provides online mindmap service and cross-platform sharing.|https://www.edrawsoft.com/mindmaster/|{{AUR|edrawmind-bin}}}}
* {{App|Semantik|Mind-mapping application for KDE.|https://waf.io/semantik.html|{{AUR|semantik}}}}
* {{App|TreeSheets|A "hierarchical spreadsheet" that is a great replacement for spreadsheets, mind mappers, outliners, PIMs, text editors and small databases.|https://strlen.com/treesheets/|{{AUR|treesheets-git}}}}
* {{App|View Your Mind|Tool to generate and manipulate maps which show your thoughts. Such maps can help you to improve your creativity and effectivity. You can use them for time management, to organize tasks, to get an overview over complex contexts, to sort your ideas etc.|https://sourceforge.net/projects/vym/|{{Pkg|vym}}}}
* {{App|[[Wikipedia:Visual Understanding Environment|Visual Understanding Environment]]|Flexible tools for managing and integrating digital resources in support of teaching, learning and research.|https://vue.tufts.edu/ |{{AUR|vue}}}}
* {{App|[[Wikipedia:XMind|XMind]]|Brainstorming and mind mapping application. It provides a rich set of different visualization styles, and allows sharing of created mind maps via their website.|https://www.xmind.net/|{{AUR|xmind}}}}

=== Sticky notes ===

* {{App|GloboNote|An easy to use desktop application for sticky notes, to-do lists, personal journals, reminders and other notes.|https://globonote.info/|{{AUR|globonote}}}}
* {{App|Notes|Provides you a quick way to paste text, to write down a list of things, to leave a note to your friend, or whatever you had do with Post-It's.|https://goodies.xfce.org/projects/panel-plugins/xfce4-notes-plugin|{{Pkg|xfce4-notes-plugin}}}}
* {{App|PrimeNote|A polished, cross-platform sticky note application written in PyQt.|https://gitlab.com/william.belanger/primenote|{{AUR|primenote-git}}}}
* {{App|Sticky|Sticky notes app for the Linux desktop.|https://github.com/linuxmint/sticky|{{Pkg|sticky}}}}
* {{App|Xpad|Sticky note application for jotting down things to remember.|https://launchpad.net/xpad|{{Pkg|xpad}}}}

== Special writing environments ==

=== Distraction-free writing ===

See also [[#Markdown editors]] and [[Wikipedia:Full-screen writing program]].

* {{App|FocusWriter|Simple, distraction-free writing environment. It utilizes a hide-away interface that you access by moving your mouse to the edges of the screen, allowing the program to have a familiar look and feel to it while still getting out of the way so that you can immerse yourself in your work.|https://gottcode.org/focuswriter/|{{Pkg|focuswriter}}}}
* {{App|[[Wikipedia:PyRoom|PyRoom]]|Fullscreen editor without buttons, widgets, formatting options, menus and with only the minimum of required dialog windows, it does not have any distractions and lets you focus on writing and only writing.|https://pyroom.org/|{{AUR|pyroom}}}}
* {{App|Quilter|Focus on your writing and write beautiful solid stories with the Focus Mode in tow in this Markdown editor.|https://github.com/lainsce/quilter|{{AUR|quilter}}}}
* {{App|TextRoom|Fullscreen text editor for writers.|https://github.com/dbuksbaum/TextRoom|{{AUR|textroom}}}}

=== Story writing ===

* {{App|Manuskript|Provides a rich environment to help writers create their first draft and then further refine and edit their masterpiece.|http://www.theologeek.ch/manuskript/|{{AUR|manuskript}}}}
* {{App|NovProg|Tool to graph your progress in writing a NaNoWriMo style novel.|https://gottcode.org/novprog/|{{AUR|novprog}}}}
* {{App|oStorybook|Tool for writers, essayists, authors from the draft to the final work.|https://ostorybook.tuxfamily.org/?lng=en|{{AUR|ostorybook}}}}

=== Screenwriting ===

* {{App|Fade In|Fade In Professional Screenwriting Software is the most advanced software used by professionals writing for motion pictures, television, video games, the stage, radio, and more.|https://www.fadeinpro.com/|{{AUR|fadein}}}}
* {{App|KIT Scenarist|Simple and powerful application for creating screenplays.|https://kitscenarist.ru/en/|{{AUR|scenarist}}}}
* {{App|Magic Fountain|Fountain syntax editor and viewer for writing screenplays.|https://aztorius.github.io/magicfountain/|{{AUR|magicfountain}}}}
* {{App|[[Wikipedia:Trelby|Trelby]]|Simple, fast and elegantly laid out to make screenwriting simple.|https://www.trelby.org/|{{AUR|trelby}}}}

== Language ==

=== Dictionary and thesaurus ===

See also [[Wikipedia:Category:Dictionary software]] and [[Wikipedia:DICT#DICT clients]].

==== Console ====

* {{App|[[dictd]]|Client/server software for the DICT protocol.|https://sourceforge.net/projects/dict/|{{Pkg|dictd}}}}
* {{App|[[sdcv]]|Command line dictionary. It provides access to dictionaries in StarDict's format.|https://dushistov.github.io/sdcv/|{{Pkg|sdcv}}}}
* {{App|thesauromatic|Static, offline, command-line thesaurus written in Rust.|https://github.com/cjrh/thesauromatic|{{AUR|thesauromatic-git}}}}

==== Graphical ====

* {{App|Artha|English thesaurus that works completely off-line and is based on WordNet.|https://artha.sourceforge.net/|{{AUR|artha}}}}
* {{App|AyanDict|Simple yet advanced multi-lingual offline dictionary using Qt and Go, that uses StarDict dictionary format.|https://github.com/ilius/ayandict|{{AUR|ayandict-bin}}, {{AUR|ayandict-git}}}}
* {{App|Ciyue|A simple mdict dictionary app.|https://mumulhl.eu.org/Ciyue/|{{AUR|ciyue}}}}
* {{App|Gjiten Kai|Rewrite of Gjiten, a GTK Japanese dictionary.|https://github.com/odrevet/gjiten-kai|{{AUR|gjitenkai-git}}}}
* {{App|GNOME Dictionary|GNOME application to check word definitions and spellings in an online dictionary. Part of {{Grp|gnome-extra}}.|https://wiki.gnome.org/Apps/Dictionary|{{Pkg|gnome-dictionary}}}}
* {{App|[[GoldenDict]]|Feature-rich dictionary lookup program, supporting multiple dictionary formats.|https://github.com/goldendict/goldendict|{{AUR|goldendict}}, {{AUR|goldendict-git}}}}
* {{App|[[GoldenDict|GoldenDict-ng]]|The Next Generation GoldenDict.|https://xiaoyifang.github.io/goldendict-ng/|{{AUR|goldendict-ng}}, {{AUR|goldendict-ng-git}}}}
* {{App|Kiten|Japanese reference and study tool. Part of {{Grp|kde-education}}.|https://apps.kde.org/kiten/|{{Pkg|kiten}}}}
* {{App|MATE Dictionary|MATE application to look up words in dictionary sources.|https://github.com/mate-desktop/mate-utils|{{Pkg|mate-utils}}}}
* {{App|OpenDict|Computer dictionary, which supports popular computer dictionary formats including Slowo and Mova. It also acts as a client for DICT servers.|https://opendict.sourceforge.net/|{{AUR|opendict}}}}
* {{App|Palaura|Handy dictionary to find any word's definition.|https://github.com/lainsce/palaura|{{AUR|palaura}}}}
* {{App|QStarDict|Dictionary program written using Qt. The user interface is similar to StarDict.|https://github.com/FBergeron/qstardict|{{Pkg|qstardict}}}}
* {{App|Quick Lookup|Simple GTK dictionary application powered by Wiktionary.|https://github.com/johnfactotum/quick-lookup|{{AUR|quick-lookup}}}}
* {{App|SlobDict|Modern, lightweight GTK4 dictionary app for exploring slob-formatted dictionaries and converting when necessary.|https://github.com/MuntashirAkon/SlobDict}}
* {{App|StarDict|International dictionary software.|https://stardict-4.sourceforge.net/|{{Pkg|stardict}}}}
* {{App|Xfce4 Dictionary|Search different kinds of dictionary services for words or phrases.|https://goodies.xfce.org/projects/applications/xfce4-dict|{{Pkg|xfce4-dict}}}}

=== Spell checkers ===

See [[Language checking]].

=== Translation and localization ===

See also [[Wikipedia:Comparison of computer-assisted translation tools]].
* {{App|[[Wikipedia:Apertium|Apertium]]|Free and open source rule-based machine translation platform with available language data. It supports the following formats: HTML, Microsoft Office 2007 XML, OpenDocument, TMX, MediaWiki and others.|https://www.apertium.org/|{{AUR|apertium}}}}
* {{App|Argos Translate|Open-source offline translation library with GUI support.|https://www.argosopentech.com/|{{AUR|argos-translate}}, {{AUR|argos-translate-gui}}}}
* {{App|Crow Translate|Simple and lightweight translator that allows to translate and speak text using Google, Yandex and Bing.|https://apps.kde.org/crowtranslate/|{{Pkg|crow-translate}}}}
* {{App|Dialect|Translation app for GNOME based on Google Translate and other online services.|https://apps.gnome.org/Dialect/|{{Pkg|dialect}}}}
* {{App|[[Wikipedia:Gtranslator|Gtranslator]]|Enhanced gettext po file editor for the GNOME. It handles all forms of gettext po files and includes very useful features.|https://wiki.gnome.org/Apps/Gtranslator|{{Pkg|gtranslator}}}}
* {{App|Lokalize|Standard [[KDE]] tool for software translation. It includes basic editing of PO files, support for glossary, translation memory, project managing, etc. Part of {{Grp|kde-sdk}}.|https://apps.kde.org/lokalize/|{{Pkg|lokalize}}}}
* {{App|[[Wikipedia:Moses (machine translation)|Moses]]|Statistical machine translation tool (language data not included).|http://statmt.org/moses/|{{AUR|mosesdecoder}}}}
* {{App|[[Wikipedia:OmegaT|OmegaT]]|General translator's tool which contains a lot of translation memory features and can give suggestions from Google Translate. It supports the following formats: HTML, Microsoft Office 2007 XML, OpenDocument, XLIFF/Okapi, MediaWiki, plain text, TMX and others.|https://omegat.org/|{{AUR|omegat}}}}
* {{App|[[Wikipedia:Poedit|Poedit]]|Simple translation editor for gettext (PO, POT) and XLIFF.|https://poedit.net|{{Pkg|poedit}}}}
* {{App|Pology|Set of Python tools for dealing with gettext/po-files.|https://techbase.kde.org/Localization/Tools/Pology|{{AUR|pology-git}}}}
* {{App|[[Qt]] Linguist|Translating Qt C++ and Qt Quick applications into local languages.|https://doc.qt.io/qt-6/qtlinguist-index.html|{{Pkg|qt6-tools}}}}
* {{App|Translate Shell|Command-line interface and interactive shell for Google Translate.|https://www.soimort.org/translate-shell/|{{Pkg|translate-shell}}}}
* {{App|[[Wikipedia:Translate Toolkit|Translate Toolkit]]|Localization and translation toolkit, which provides a set of tools for working with localization file formats and files that might need localization.|https://toolkit.translatehouse.org/|{{Pkg|translate-toolkit}}}}
* {{App|TranslateLocally|Fast and secure local translation using Bergamot (Mozilla).|https://github.com/XapaJIaMnu/translatelocally|{{AUR|translatelocally-git}}}}

== Barcode generators and readers ==

=== Console ===

* {{App|barcode|A tool to convert text strings to printed bars.|https://www.gnu.org/software/barcode/|{{Pkg|barcode}}}}
* {{App|iec16022|Produce 2D barcodes often also referenced as DataMatrix.|https://datenfreihafen.org/projects/iec16022.html|{{Pkg|iec16022}}}}
* {{App|qrencode|C library and command line tool for encoding data in a QR code symbol.|https://fukuchi.org/works/qrencode/|{{Pkg|qrencode}}}}
* {{App|[[Wikipedia:ZBar|ZBar]]|Application and library for reading bar codes from various sources.|https://zbar.sourceforge.net/|{{Pkg|zbar}}}}
* {{App|Zint|Barcode encoding library and command line tool supporting over 50 symbologies.|http://zint.org.uk/|{{Pkg|zint}}}}

=== Graphical ===

* {{App|CoBang|QR code scanner application.|https://github.com/hongquan/CoBang|{{AUR|cobang}}}}
* {{App|Decoder|QR code scanner and generator.|https://apps.gnome.org/Decoder/|{{Pkg|decoder}}}}
* {{App|gLabels|Program for creating labels and business cards. It also supports creating barcodes.|https://github.com/jimevins/glabels|{{Pkg|glabels}}}}
* {{App|Kodaskanna|Utility for reading data from 1D/2D codes (e.g. QR codes or bar codes) and making the data available for further processing.|https://apps.kde.org/kodaskanna/|{{AUR|kodaskanna}}}}
* {{App|QRab|Simply grabs QR code from screen and copies decoded text into clipboard.|https://qrab.sourceforge.io/|{{AUR|qrab}}}}
* {{App|Qrca|Scan QR-Codes with your camera on phones and laptops, and create your own for easily sharing data between devices.|https://apps.kde.org/qrca/|{{Pkg|qrca}}}}
* {{App|Qreator|Graphical utility for creating QR codes.|https://davidplanella.org/qreator/|{{Pkg|qreator}}}}
* {{App|QtQR|QR code generator and decoder.|https://launchpad.net/qr-tools|{{AUR|qtqr}}}}
* {{App|ZBarCam GUI|Simple GUI for ZBar to read bar codes from various sources.|https://zbar.sourceforge.net/|{{Pkg|zbar}}}}
* {{App|Zint Barcode Studio|Barcode generator GUI.|http://zint.org.uk/|{{Pkg|zint-qt}}}}

== Placeholder text generators ==

* {{App|Lorem|Simple app to generate the Lorem Ipsum placeholder text.|https://apps.gnome.org/Lorem/|{{Pkg|lorem}}}}

List of applications/Science

2026-05-13T10:36:36Z

Erus Iluvatar: /* Console */ fix calcpy package

[[Category:Lists of software]]
[[Category:Science]]
[[es:List of applications (Español)/Science]]
[[hu:List of applications (Magyar)/Science]]
[[ja:アプリケーション一覧/サイエンス]]
[[pl:List of applications (Polski)/Science]]
[[zh-hans:List of applications/Science]]
{{List of applications navigation}}

== Mathematics ==

=== Calculator ===

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

==== Console ====

* {{App|[[Wikipedia:bc programming language|bc]]|Arbitrary precision calculator language.|https://www.gnu.org/software/bc/|{{Pkg|bc}}}}
* {{App|calc|Arbitrary precision console calculator.|http://www.isthe.com/chongo/tech/comp/calc/|{{Pkg|calc}}}}
* {{App|calcpy|Terminal calculator and advanced math solver using Python, IPython and SymPy.|https://github.com/idanpa/calcpy|{{AUR|calcpy-git}}}}
* {{App|clac|Command-line, stack-based calculator with postfix notation.|https://github.com/soveran/clac|{{AUR|clac}}}}
* {{App|kalker|Command-line calculator with math syntax that supports user-defined variables and functions, complex numbers, and estimation of derivatives and integrals.|https://github.com/PaddiM8/kalker|{{AUR|kalker}}}}
* {{App|Numbat|A statically typed programming language for scientific computations with first class support for physical dimensions and units.|https://numbat.dev|{{Pkg|numbat}}}}
* {{App|qalc|Command-line calculator and equation solver with fault-tolerant parsing, constant recognition and units.|https://qalculate.github.io/|{{Pkg|libqalculate}}}}

==== Graphical ====

* {{App|Binary|Simple app to convert between different hexadecimal and binary numbers.|https://apps.gnome.org/Binary/|{{Pkg|binary}}}}
* {{App|Cutefish Calculator|Calculator for Cutefish desktop.|https://github.com/cutefishos/calculator|{{AUR|cutefish-calculator}}}}
* {{App|Deepin Calculator|Easy to use calculator for Deepin desktop.|https://www.deepin.org/en/original/deepin-calculator/|{{Pkg|deepin-calculator}}}}
* {{App|Extcalc|Qt-based scientific graphical calculator.|https://extcalc-linux.sourceforge.net/|{{AUR|extcalc}}}}
* {{App|FOX Calculator|Simple desktop calculator.|http://fox-toolkit.org/|{{Pkg|fox}}}}
* {{App|galculator|GTK-based scientific calculator.||{{Pkg|galculator}}}}
* {{App|[[Wikipedia:Genius (mathematics software)|Genius]]|Advanced calculator including a mathematical programming language.|https://www.jirka.org/genius.html|{{Pkg|genius}}}}
* {{App|[[Wikipedia:GNOME Calculator|GNOME Calculator]]|Scientific calculator included in the GNOME desktop. Part of {{Grp|gnome}}.|https://apps.gnome.org/Calculator/|{{Pkg|gnome-calculator}}}}
* {{App|[[Wikipedia:KAlgebra|KAlgebra]]|Calculator and 3D plotter. Part of {{Grp|kde-education}}.|https://apps.kde.org/kalgebramobile/|{{Pkg|kalgebra}}}}
* {{App|Kalk|A convergent calculator application built with the Kirigami framework. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/kalk/|{{Pkg|kalk}}}}
* {{App|[[Wikipedia:KCalc|KCalc]]|Scientific calculator included in the KDE desktop. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/kcalc/|{{Pkg|kcalc}}}}
* {{App|KEuroCalc|Universal currency converter and calculator.|https://apps.kde.org/keurocalc/|{{AUR|keurocalc}}}}
* {{App|Liri Calculator|Calculator for Liri.|https://github.com/lirios/calculator|{{AUR|liri-calculator}}}}
* {{App|MATE Calc|Calculator for the MATE desktop environment.|https://mate-desktop.org/|{{Pkg|mate-calc}}}}
* {{App|Qalculate!|Calculator and equation solver with fault-tolerant parsing, constant recognition and units.|https://qalculate.github.io/|GTK: {{Pkg|qalculate-gtk}}, Qt: {{Pkg|qalculate-qt}}}}
* {{App|SpeedCrunch|Fast, high precision and powerful cross-platform calculator.|https://speedcrunch.org|{{Pkg|speedcrunch}}}}
* {{App|Valuta|Simple application for converting currencies.|https://apps.gnome.org/Valuta/|{{Pkg|valuta}}}}
* {{App|[[xcalc]]|Scientific calculator for X with algebraic and reverse polish notation modes.|https://www.x.org/|{{Pkg|xorg-xcalc}}}}

==== Texas Instruments ====

* {{App|ticemu|Third-party TI-84 Plus CE / TI-83 Premium CE emulator, focused on developer features.|https://ce-programming.github.io/CEmu/|{{AUR|ticemu}}}}
* {{App|firebird-nspire|Multi-platform emulator of TI Nspire calculators.|https://github.com/nspire-emus/firebird|{{AUR|firebird-nspire}}}}
* {{App|TiEmu|Emulator of TI-89/92/92+/V200 calculators.|https://github.com/debrouxl/tiemu|{{AUR|tiemu}}}}
* {{App|wxwabbitemu|A cross-platform TI-8x emulator based on Wabbitemu.|https://github.com/alberthdev/wxwabbitemu|{{AUR|wxwabbitemu-git}}}}

=== Computer algebra system ===

See also [[Wikipedia:Comparison of computer algebra systems]].

* {{App|[[Wikipedia:Axiom (computer algebra system)|AXIOM]]|FriCAS: derivative of the powerful AXIOM-CAS.|https://fricas.sourceforge.net|{{Pkg|fricas}}}}
* {{App|[[Wikipedia:GAP (computer algebra system)|GAP]]|Computer algebra system for computational discrete algebra with particular emphasis on computational group theory.|https://www.gap-system.org/|{{Pkg|gap}}}}
* {{App|[[Maple]]|Famous commercial CAS. Often used in education.|https://www.maplesoft.com/products/maple/|{{AUR|maple2024}}}}
* {{App|Mathics|A free CAS for symbolic mathematical computations which uses [[Python]] as its main language. It aims at achieving a Mathematica-compatible syntax and functions. It relies mostly on Sympy for most mathematical tasks and, optionally, Sage for more advanced functionality.|https://mathics.github.io/|{{AUR|mathics}}}}
* {{App|[[Wikipedia:Mathomatic|Mathomatic]]|General purpose Computer Algebra System written in C.|https://github.com/mfillpot/mathomatic|{{AUR|mathomatic}}}}
* {{App|[[Wikipedia:Maxima (software)|Maxima]]|[[Wikipedia:Maple (software)|Maple]]/[[Wikipedia:Wolfram Mathematica|Mathematica]]-like computer algebra system.|https://maxima.sourceforge.net/|{{Pkg|maxima}}}}
* {{App|[[Wikipedia:PARI/GP|PARI/GP]]|Computer algebra system designed for fast computations in number theory.|https://pari.math.u-bordeaux.fr/|{{Pkg|pari}}}}
* {{App|[[Wikipedia:Singular (software)|Singular]]|Computer algebra system for polynomial computations, with special emphasis on commutative and non-commutative algebra, algebraic geometry, and singularity theory.|https://www.singular.uni-kl.de/|{{Pkg|singular}}}}
* {{App|wxMaxima|Graphical user interface for Maxima being a powerful computer algebra system.|https://andrejv.github.io/wxmaxima/|{{AUR|wxmaxima}}}}
* {{App|[[Wikipedia:Xcas|Xcas]]|User interface to Giac, a free, basic computer algebra system.|https://www-fourier.ujf-grenoble.fr/~parisse/giac.html{{Dead link|2025|11|17|status=domain name not resolved}}|{{Pkg|giac}}}}

=== Visualization of networks/graphs ===

* {{App|Glue|Linked data visualizations across multiple files.|http://glueviz.org/|{{AUR|glueviz}}}}
* {{App|[[Graphviz]]|The established tool for displaying smallish graphs in 2D.|https://www.graphviz.org|{{Pkg|graphviz}}}}

=== Scientific or technical computing ===

See also [[Wikipedia:Comparison of numerical analysis software]].

* {{App|[[Wikipedia:Cadabra (computer program)|Cadabra]]|A field-theory motivated approach to computer algebra.|https://cadabra.science/|{{AUR|cadabra2}}}}
* {{App|[[Wikipedia:Cantor (software)|Cantor]]|Application that lets you use your favorite mathematical applications from within a nice KDE-integrated Worksheet Interface. Part of {{Grp|kde-education}}.|https://cantor.kde.org/|{{Pkg|cantor}}}}
* {{App|[[Wikipedia:FFTW|FFTW]]|A [[Wikipedia:Fast_Fourier_transform|Fast Fourier Transform]] library for computing discrete Fourier transforms. Used for a wide variety of numerical applications, which includes spectral methods.|https://www.fftw.org/ |{{Pkg|fftw}}}}
* {{App|[[Wikipedia:FreeMat|FreeMat]]|Matlab-like program that supports many of its functions and features a codeless interface to external C, C++, and Fortran code, further parallel distributed algorithm development (via MPI), and 3D visualization capabilities.|https://freemat.sourceforge.net/|{{AUR|freemat}}}}
* {{App|[[Wikipedia:GeoGebra|GeoGebra]]|Dynamic mathematics software with interactive graphics, algebra and spreadsheet|https://www.geogebra.org/|{{Pkg|geogebra}}}}
* {{App|[[Wikipedia:Julia (programming language)|Julia]]|High-level, high-performance dynamic language for technical computing.|https://julialang.org/|{{Pkg|julia}}}}
* {{App|[[Wikipedia:Kig (software)|Kig]]|Application for Interactive Geometry. Part of {{Grp|kde-education}}.|https://apps.kde.org/kig/|{{Pkg|kig}}}}
* {{App|[[Wikipedia:matplotlib|matplotlib (PyLab)]]|Collection of Python modules (pyplot, numpy, etc.) used for scientific calculations.|https://www.scipy.org/|{{Pkg|python-matplotlib}}}}
* {{App|[[Octave]]|[[MATLAB]]-like language and interface for numerical computations.|https://www.gnu.org/software/octave/ |{{Pkg|octave}}}}
* {{App|[[SageMath]]|Mathematics software system, that combines many existing open-source packages into a common Python interface. Alternative to Magma, Maple, Mathematica and Matlab.|https://www.sagemath.org/|{{Pkg|sagemath}}}}
* {{App|[[Wikipedia:Scilab|Scilab]]|Matlab alternative used for numerical computations. Its syntax is not equivalent to that of Matlab, but it can be easily converted.|https://www.scilab.org/|{{AUR|scilab}}}}

=== Statistics ===

See also [[Wikipedia:Comparison of statistical packages]].

* {{App|[[Wikipedia:gretl|gretl]]|A cross-platform software package for econometric analysis, written in the C programming language.|https://gretl.sourceforge.net/|{{AUR|gretl}}}}
* {{App|[[Wikipedia:Just another Gibbs sampler|JAGS]] (Just another Gibbs sampler)|Cross-platform program for analysis of Bayesian hierarchical models using Markov Chain Monte Carlo (MCMC) simulation.|https://mcmc-jags.sourceforge.net/|{{AUR|jags}}}}
* {{App|[[Wikipedia:PSPP|PSPP]]|Free SPSS implementation.|https://www.gnu.org/software/pspp/|{{AUR|pspp}}}}
* {{App|[[Wikipedia:Pandas_(software)|Python Data Analysis Library (pandas)]]| Providing high-performance, easy-to-use data structures and data analysis tools with Python programming language.|https://pandas.pydata.org/|{{Pkg|python-pandas}}}}
* {{App|[[R]]|Software environment for statistical computing and graphics.|https://cran.r-project.org/|{{Pkg|r}}}}
* {{App|[[Wikipedia:RKWard|RKWard]]|Frontend for the statistical language R.|https://rkward.kde.org/|{{Pkg|rkward}}}}
* {{App|[[Wikipedia:RStudio|RStudio]]|A powerful and productive IDE for R written in Qt.|https://www.rstudio.com/|{{AUR|rstudio-desktop}}}}

=== Data analysis and plotting ===

See also [[Wikipedia:List of information graphics software]].

* {{App|AlphaPlot|Application for scientific data analysis and visualization, fork of [[Wikipedia:SciDAVis|SciDAVis]] / QtiPlot.|https://alphaplot.sourceforge.io/|{{AUR|alphaplot}}}}
* {{App|DataWarrior|Open-source data visualization and analysis program with embedded chemical intelligence.|https://openmolecules.org/datawarrior/|{{AUR|datawarrior}}}}
* {{App|Engauge Digitizer|Extracts data points from images of graphs.|https://markummitchell.github.io/engauge-digitizer/{{Dead link|2025|03|15|status=404}}|{{AUR|engauge}}}}
* {{App|[[Wikipedia:Fityk|Fityk]]|Curve fitting and data analysis application, predominantly used to fit analytical, bell-shaped functions to experimental data.|https://fityk.nieto.pl/|{{AUR|fityk}}}}
* {{App|[[Wikipedia:gnuplot|Gnuplot]]|Command-line program that can generate 2D and 3D plots of functions, data, and data fits.|http://www.gnuplot.info/|{{Pkg|gnuplot}}}}
* {{App|[[Wikipedia:Grace (plotting tool)|Grace]]|WYSIWYG 2D graph plotting tool.|https://plasma-gate.weizmann.ac.il/Grace/|{{AUR|grace}}, {{AUR|qtgrace}}, {{AUR|gracegtk}}}}
* {{App|Graphs|Tool to plot and manipulate data.|https://apps.gnome.org/Graphs/|{{Pkg|graphs}}}}
* {{App|[[Wikipedia:KmPlot|KmPlot]]|Program to draw graphs, their integrals or derivatives. Part of {{Grp|kde-education}}.|https://apps.kde.org/kmplot/|{{Pkg|kmplot}}}}
* {{App|[[Wikipedia:kst (software)|kst]]|Real-time data viewer.|https://kst-plot.kde.org/|{{AUR|kst}}}}
* {{App|[[Wikipedia:LabPlot|LabPlot]]|Free software data analysis and visualization application, similar to SciDAVis.|https://labplot.org/|{{Pkg|labplot}}}}
* {{App|OVITO (Open Visualization Tool)|Scientific data visualization and analysis solution for particle-based simulations.|https://ovito.org/|{{AUR|ovito}}}}
* {{App|Plots|A graph plotting application for GNOME.|https://github.com/alexhuntley/Plots|{{AUR|plots}}}}
* {{App|Rocs|Graph Theory IDE for everybody interested in designing and analyzing graph algorithms (e.g., lecturers, students, researchers). Part of {{Grp|kde-education}}.|https://apps.kde.org/rocs/|{{Pkg|rocs}}}}
* {{App|[[Wikipedia:ROOT|ROOT]]|Data analysis program and library (originally for particle physics) developed by CERN.|https://root.cern.ch/|{{Pkg|root}}}}
* {{App|Snakemake|Python-based language and execution environment for GNU Make-like workflows.|https://snakemake.github.io/|{{AUR|snakemake}}}}

See also [[List of applications/Documents#Spreadsheets]].

=== Proof assistants ===

See also [[Wikipedia:Proof assistant]].

* {{App|[[Wikipedia:Agda (programming language)|Agda]]|Dependently typed functional programming language and proof assistant. It is an interactive system for writing and checking proofs.|https://wiki.portal.chalmers.se/agda/|{{Pkg|agda}}}}
* {{App|[[Wikipedia:Isabelle (proof assistant)|Isabelle]]|Generic proof assistant that allows mathematical formulas to be expressed in a formal language and provides tools for proving those formulas in a logical calculus.|https://www.cl.cam.ac.uk/research/hvg/Isabelle/|{{AUR|isabelle}}}}
* {{App|[[Lean]]|Proof assistant developed principally by Leonardo de Moura at Microsoft Research, used in conjunction with the Lean mathematical library.|https://leanprover-community.github.io/|{{AUR|lean-community}}}}
* {{App|[[Wikipedia:Rocq|Rocq]]|Formal proof management system. It provides a formal language to write mathematical definitions, executable algorithms and theorems together with an environment for semi-interactive development of machine-checked proofs.|https://coq.inria.fr/|CLI: {{Pkg|rocq}}, GUI: {{Pkg|rocqide}} }}

== Physics ==

=== Tools ===

* {{App|Geiger Counter Logger|Is a lightweight daemon running in the background and constantly reporting your Geiger counter readings to various radiation monitoring websites|https://www.dateihal.de/cms/gclog|{{AUR|gclog}}}}
* {{App|GWtool|Simple tools for working with gravitational waves|https://gwtool.sourceforge.net/|{{AUR|gwtool}}}}
* {{App|InterSpec|spectral radiation analysis software|https://sandialabs.github.io/InterSpec/|{{AUR|interspec-bin}}}}
* {{App|JaxoDraw|A particle physics program for drawing Feynman diagrams.|https://jaxodraw.sourceforge.io/|{{AUR|jaxodraw}}}}
* {{App|Libint|A high-performance library for computing Gaussian integrals in quantum mechanics|https://github.com/evaleev/libint|{{AUR|libint2}}}}
* {{App|Pysolar|Collection of Python libraries for simulating the irradiation of any point on earth by the sun. It includes code for extremely precise ephemeris calculations.|https://pysolar.org/|{{AUR|python-pysolar}}}}
* {{App|Silx|A collection of Python packages for data analysis at synchrotron radiation facilities.|http://www.silx.org/|{{AUR|python-silx}}}}

=== Physics simulation ===

* {{App|[[Wikipedia:Calculix|Calculix]]|A three-dimensional structural finite element program.|https://www.calculix.de/|{{AUR|calculix-ccx}}}}
* {{App|DFTB+|A quantum mechanical simulation software package based on the DFTB method|https://dftbplus.org/|{{AUR|dftbplus}}}}
* {{App|[[Wikipedia:Elmer_FEM_solver|Elmer_FEM_solver]]|Finite element analysis (FEA/FEM) software for multiphysics problems. Includes models for fluid dynamics, structural mechanics, electromagnetics, heat transfer, and acoustics.|https://www.csc.fi/web/elmer https://www.elmerfem.org/|{{AUR|elmerfem}}}}
* {{App|[[Wikipedia:FEniCS Project|FEniCS]]|An open-source computing platform for solving partial differential equations, enabling users to quickly translate scientific models into efficient finite element code with the high-level Python and C++ interfaces that scale across platforms ranging from laptops to high-performance clusters.|https://fenicsproject.org/|{{AUR|dolfin}}, {{AUR|python-dolfin}}}}
* {{App|Finesse|Frequency domain INterfErometer Simulation SoftwarE|https://www.gwoptics.org/finesse/|{{AUR|finesse}}}}
* {{App|Geant4|A simulation toolkit for particle physics interactions.|https://geant4.web.cern.ch/|{{AUR|geant4}}}}
* {{App|Herwig|Herwig is a multi-purpose particle physics event generator.|https://herwig.hepforge.org/|{{AUR|herwig}}}}
* {{App|Netgen/NGSolve|A high performance multiphysics finite element software, with a flexible Python interface to implement new physical equations and solution algorithms easily.|https://ngsolve.org/|{{AUR|netgen-git}}, {{AUR|ngsolve-git}}}}
* {{App|[[Wikipedia:Gmsh|ONELAB/Gmsh]]|An open-source, lightweight interface to finite element software, by default containing the mesh generator Gmsh, the finite element solver GetDP and the optimization library conveks.|http://onelab.info/ https://getdp.info/ https://gmsh.info/ http://onelab.info/conveks/|{{AUR|gmsh}}, {{AUR|getdp}}}}
* {{App|[[Wikipedia:OpenFOAM|OpenFOAM]]|Software package and toolkit for computational fluid dynamics (CFD).|https://openfoam.org/|{{AUR|openfoam-org}}}}
* {{App|OpenLoops 2|A particle physics package for the fast numerical evaluation of tree and one-loop matrix elements.|https://openloops.hepforge.org/|{{AUR|openloops}}}}
* {{App|QuTiP|QuTiP is open-source software for simulating the dynamics of open quantum systems|https://qutip.org/|{{AUR|python-qutip}}}}
* {{App|Rivet|A particle physics package for data analysis and validation of Monte Carlo event generators|https://rivet.hepforge.org/|{{AUR|rivet}}}}
* {{App|Sherpa|A particle physics package for Monte Carlo simulation of collider events.|https://sherpa-team.gitlab.io/|{{AUR|sherpa}}}}
* {{App|Speaq|Tools for Nuclear Magnetic Resonance (NMR) Spectra Alignment, Peak Based Processing, Quantitative Analysis and Visualizations|https://cran.r-project.org/web/packages/speaq/index.html|{{AUR|r-speaq}}}}
* {{App|[[Wikipedia:Step (software)|Step]]|Two-dimensional physics simulation engine. Part of {{Grp|kde-education}}.|https://apps.kde.org/step/|{{Pkg|step}}}}
* {{App|[[Wikipedia:SWMM|SWMM]]|Storm Water Management Model is a dynamic rainfall-runoff-subsurface runoff simulation model used for simulation of the surface/subsurface hydrology quantity and quality.|https://www.epa.gov/|{{AUR|swmm5-git}}}}
* {{App|VESTA|3D visualization program for structural models, volumetric data such as electron/nuclear densities, and crystal morphologies.|https://jp-minerals.org/vesta/en/|{{AUR|vesta}}}}
* {{App|WHIZARD|The Generator of Monte Carlo Event Generators for Tevatron, LHC, ILC, CLIC, CEPC, FCC-ee, FCC-hh, SppC and other High Energy Physics Experiments.|https://whizard.hepforge.org/|{{AUR|whizard}}}}

=== Unit conversion ===

* {{App|ConvertAll|Unit conversion application that allows one to combine units in any way (e.g. inches per decade), even if it does not make sense.|https://convertall.bellz.org/|{{AUR|convertall}}}}
* {{App|[https://printfn.github.io/fend/ fend]|An arbitrary-precision unit-aware calculator.|https://github.com/printfn/fend|{{AUR|fend}}}}
* {{App|Gonvert|Conversion utility that allows conversion between many units like CGS, Ancient, Imperial with many categories like length, mass, numbers, etc.|http://www.unihedron.com/projects/gonvert/|{{AUR|gonvert}}}}
* {{App|Numbat|A statically typed programming language for scientific computations with first class support for physical dimensions and units.|https://numbat.dev|{{Pkg|numbat}}}}
* {{App|Rink|A unit conversion tool and library written in rust. It can be used for physics and engineering calculations, as well as dimensionality analysis.|https://rinkcalc.app/about|{{Pkg|rink}}}}
* {{App|UDUNITS|A tool for calculations of physical quantities.|https://www.unidata.ucar.edu/software/udunits/|{{AUR|udunits}}}}
* {{App|[[Wikipedia:GNU Units|Units]]|Command-line unit converter and calculator that can handle multiplicative scale changes, nonlinear conversions such as Fahrenheit to Celsius or wire gauge and others.|https://www.gnu.org/software/units/|{{AUR|units}}}}

== Chemistry ==

* {{App|ChemCalc|A chemical calculator that calculates the amount of reagents to use when making solutions.|https://github.com/Chris-Baba/ChemCalc/tree/main|{{AUR|chemcalc}}}}

* {{App|TCcalc|A basic CLI [[Wikipedia:Chemical thermodynamics|Chemical thermodynamics]] calculator. Allows for calculating delta S and H of reactions/state changes.|https://gitlab.com/calcs1/tccalc/|{{AUR|tccalc}}}}

=== Molecules ===

==== Viewers ====

See also [[Wikipedia:List of molecular graphics systems]].

* {{App|[[Wikipedia:Avogadro_(software)|Avogadro]]|Editor, viewer and simulator for 3D molecule structures (also supports downloading files from the [[Wikipedia:Protein Data Bank|Protein Data Bank]]).|https://avogadro.cc/|{{AUR|avogadroapp}}}}
* {{App|[[Wikipedia:Ghemical|Ghemical]]|Computational chemistry software package used to edit, view and simulate molecular structures.|http://bioinformatics.org/ghemical/ghemical/index.html|{{AUR|ghemical}}}}
* {{App|[[Wikipedia:PyMOL|PyMOL]]|Open-source molecular visualization system that can produce high quality 3D images of small molecules and biological macromolecules, such as proteins.|https://pymol.org/|{{Pkg|pymol}}}}
* {{App|[[Wikipedia:UCSF Chimera|UCSF Chimera]]|Extensible molecular modeling system.|https://rbvi.ucsf.edu/chimera/|{{AUR|ucsf-chimera}}}}
* {{App|UCSF ChimeraX|Next-generation molecular visualization program, following UCSF Chimera.|https://rbvi.ucsf.edu/chimerax/|{{AUR|chimerax}}}}
* {{App|[[Wikipedia:Visual Molecular Dynamics|VMD]]|VMD is a molecular visualization program for displaying, animating, and analyzing large biomolecular systems using 3-D graphics and built-in scripting.|https://www.ks.uiuc.edu/Research/vmd/|{{AUR|vmd}}}}
* {{App|wxMacMolPlt|An open-source GUI for preparing, submitting and visualizing input and output for the GAMESS quantum chemistry package.|https://brettbode.github.io/wxmacmolplt/|{{AUR|wxmacmolplt}}}}

==== Drawing ====

* {{App|Chemtool|GTK-based program for drawing chemical structural formulas.|http://ruby.chemie.uni-freiburg.de/~martin/chemtool/chemtool.html|{{AUR|chemtool}}}}

==== Modeling ====

* {{App|[[Wikipedia:AMBER|AmberTools]]|AmberTools consists of several independently developed packages that work well by themselves, and with Amber18 itself. The suite can also be used to carry out complete molecular dynamics simulations, with either explicit water or generalized Born solvent models.|https://ambermd.org/AmberTools.php|{{AUR|ambertools}}}}
* {{App|[[Wikipedia:APBS (software)|APBS]]|Electrostatic and solvation properties for complex molecules.|https://www.poissonboltzmann.org/|{{AUR|apbs}}}}
* {{App|[[Wikipedia:COPASI|COPASI]]|COmplex PAthway SImulator for analysis of biochemical networks and their dynamics.|https://copasi.org/|{{AUR|copasi-bin}}}}
* {{App|[[Wikipedia:CP2K|CP2K]]|A quantum chemistry and solid state physics software package.|https://www.cp2k.org/|{{AUR|cp2k}}}}
* {{App|Fpocket|Fpocket is a very fast open source protein pocket detection algorithm based on Voronoi tessellation.|https://github.com/Discngine/fpocket|{{AUR|fpocket-git}}}}
* {{App|[[GROMACS]] (GROningen MAchine for Chemical Simulations)|Versatile package to perform molecular dynamics, i.e. simulate the Newtonian equations of motion for systems with hundreds to millions of particles.|https://www.gromacs.org|{{AUR|gromacs}}}}
* {{App|[[Wikipedia:LAMMPS|LAMMPS]]|Large-scale Atomic/Molecular Massively Parallel Simulator.|https://www.lammps.org/|{{AUR|lammps}}}}
* {{App|[[Wikipedia:MODELLER|MODELLER]]|3D structure homology modeller.|https://salilab.org/modeller/|{{AUR|modeller}}}}
* {{App|[[Wikipedia:NAMD|NAMD]]|NAMD is a parallel molecular dynamics code designed for high-performance simulation of large biomolecular systems.|https://www.ks.uiuc.edu/Research/namd/|{{AUR|namd}}}}
* {{App|[[Wikipedia:NWChem|NWChem]]|Ab initio computational chemistry software package.|https://nwchemgit.github.io/|{{AUR|nwchem}}}}
* {{App|[[Wikipedia:Open Babel|Open Babel]]|A library designed to interconvert between many file formats used in molecular modeling and computational chemistry.|https://openbabel.org/|{{pkg|openbabel}}}}
* {{App|[[Wikipedia:ORCA (quantum chemistry program)|ORCA]]|ORCA is an ab initio, DFT, and semi-empirical SCF-MO package.|https://orcaforum.kofo.mpg.de/app.php/portal|{{AUR|orcaqm}}}}
* {{App|[[Wikipedia:APBS (software)|PDB2PQR]]|Electrostatic and solvation properties for complex molecules.|https://www.poissonboltzmann.org/|{{AUR|python-pdb2pqr}}}}
* {{App|[[Wikipedia:PLUMED|PLUMED]]|An open source plugin for free energy calculations in molecular systems which works together with some of the most popular molecular dynamics engines.|https://www.plumed.org/|{{AUR|plumed}}}}
* {{App|PSI4|Open-source quantum chemistry|https://psicode.org/|{{AUR|psi4-git}}}}
* {{App|[[Wikipedia:Quantum ESPRESSO|Quantum ESPRESSO]]|Integrated suite of applications for electronic-structure calculations and materials modeling at nanoscale. It is based on density-functional theory, plane waves, and pseudopotentials (both norm-conserving and ultrasoft).|https://www.quantum-espresso.org/|{{AUR|quantum-espresso}}}}
* {{App|[[Wikipedia:RDKit|RDKit]]|A collection of cheminformatics and machine-learning software written in C++ and Python.|https://www.rdkit.org/|{{Pkg|rdkit}}}}
* {{App|[[Wikipedia:RDock|rDock]]|A fast, versatile and open-source program for docking ligands to proteins and nucleic acids.|https://rdock.sourceforge.net/|{{AUR|rdock}}}}
* {{App|[[Wikipedia:AutoDock|smina]]|Smina is a fork of Autodock Vina that focuses on improving scoring and minimization.|https://sourceforge.net/projects/smina/|{{AUR|smina-bin}}}}

=== Simulation analysis ===

* {{App|mdanalysis|An object-oriented python toolkit to analyze molecular dynamics trajectories in many popular formats.|https://www.mdanalysis.org|{{AUR|python-mdanalysis}}}}
* {{App|MDTraj|A modern, open library for the analysis of molecular dynamics trajectories.|https://github.com/mdtraj/mdtraj|{{AUR|python-mdtraj}}}}
* {{App|xdrfile|Allows to read GROMACS [https://manual.gromacs.org/current/reference-manual/file-formats.html#trr trr] and [https://manual.gromacs.org/current/reference-manual/file-formats.html#xtc xtc] files and also to convert from one format to another.|https://manual.gromacs.org/current/reference-manual/file-formats.html#xdr|{{AUR|xdrfile}}}}

=== Periodic table ===

* {{App|eperiodique|A simple Periodic Table Of Elements viewer using the EFL.|https://eperiodique.sourceforge.net/|{{AUR|eperiodique}}}}
* {{App|gElemental|Periodic table of the elements with additional information.|https://freshmeat.sourceforge.net/projects/gelemental|{{AUR|gelemental}}}}
* {{App|Kalzium|Periodic table of the elements with molecule editor and equation solver. Part of {{Grp|kde-education}}.|https://apps.kde.org/kalzium/|{{Pkg|kalzium}}}}

== Earth science ==

=== Climatology ===

* {{App|Climate Data Operators|Command line tool to manipulate and analyse Climate model Data. Supported data formats are GRIB, netCDF, SERVICE, EXTRA and IEG.|https://code.mpimet.mpg.de/projects/cdo|{{AUR|cdo}}}}

=== Geography ===

==== Map viewers ====

* {{App|Cruiser|Map and navigation application using offline vector maps|https://wiki.openstreetmap.org/wiki/Cruiser|{{AUR|cruiser}}}}
* {{App|GNOME Maps|A simple map client for GNOME with navigation and GNSS features (adapted to Linux Mobile). Part of {{Grp|gnome}}.|https://apps.gnome.org/Maps/|{{Pkg|gnome-maps}}}}
* {{App|kosmindoormap|Indoor cartography, levels by levels of buildings, mainly Train station, and Airport buildings. Based on OSM data.|https://www.kde.org|{{Pkg|kosmindoormap}}}}
* {{App|MapSCII|Console Map Viewer.|https://github.com/rastapasta/mapscii|{{AUR|nodejs-mapscii}}}}
* {{App|Mapton|Extensible desktop map and globe application written in Java.|https://mapton.org/|{{AUR|mapton}}}}
* {{App|[[Wikipedia:Marble (software)|Marble]]|Virtual Globe and World Atlas that can be used to learn more about the Earth. Part of {{Grp|kde-education}}.|https://marble.kde.org/|KDE: {{Pkg|marble}}, Qt: {{Pkg|marble-qt}}}}
* {{App|Marble Behaim|Viewer for the oldest existent globe of the Earth made by Martin Behaim and collaborators around 1492.|https://marble.kde.org/|{{Pkg|marble-behaim}}}}
* {{App|Marble Maps|Vector and GNSS navigation system, with Modular turn-by-turn car, foot, and bike navigation system (adapted to Linux Mobile).|https://marble.kde.org/|{{Pkg|marble-maps}}}}
* {{App|OffRoad|Offline vector map display ported from OsmAnd.|https://sourceforge.net/projects/offroadosm/|{{Pkg|offroad}}}}
* {{App|Organic Maps|GNSS based navigation, with vector off-line and routing features, and turn by turn routing|https://github.com/organicmaps/organicmaps|{{AUR|organicmaps-git}}}}
* {{App|OSMin|GNSS based navigation, with vector off-line and routing features, and turn by turn car, foot, bike, and hiking routing (adapted to Linux Mobile).|https://github.com/janbar/osmin|{{AUR|osmin}}}}
* {{App|Pure Maps|Display vector and raster maps, places, routes, etc.|https://rinigus.github.io/pure-maps/|{{AUR|pure-maps}}}}

==== Navigation and routing ====

* {{App|KTrip|Public transport assistant for mobile devices. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/ktrip/|{{Pkg|ktrip}}}}
* {{App|Railway|Lets you look up travel information for many different railways, all without needing to navigate through different websites.|https://apps.gnome.org/DieBahn/|{{Pkg|railway}}}}

==== Positioning and tracking ====

* {{App|BT747|The swiss army knife for MTK GPS dataloggers.|https://sourceforge.net/projects/bt747/|{{Pkg|bt747}}}}
* {{App|FoxtrotGPS|Lightweight and fast mapping application.|https://www.foxtrotgps.org/|{{AUR|foxtrotgps}}}}
* {{App|Gebabbel|Alternative GUI for GPSBabel.|https://gebabbel.sourceforge.net/|{{AUR|gebabbel}}}}
* {{App|Gpredict|Real-time satellite tracking and orbit prediction application.|https://gpredict.oz9aec.net/|{{AUR|gpredict}}}}
* {{App|GPSBabel|Reads, writes, and manipulates GPS waypoints, tracks, routes in a variety of formats.|https://www.gpsbabel.org/|{{Pkg|gpsbabel}}}}
* {{App|[[Wikipedia:gpsd|gpsd]]|Service daemon that monitors one or more GPSes or AIS receivers attached to a host computer through serial or USB ports, making all data on the location/course/velocity of the sensors available to be queried on TCP port 2947 of the host computer.|http://catb.org/gpsd/|{{Pkg|gpsd}}}}
* {{App|GpsPrune|View, edit and convert coordinate data from GPS systems.|https://activityworkshop.net/software/gpsprune/|{{Pkg|gpsprune}}}}
* {{App|GPXSee|GPS log file viewer and analyzer.|https://www.gpxsee.org/|{{Pkg|gpxsee}}}}
* {{App|GPX Viewer|Simple tool to visualize tracks and waypoints stored in a gpx file.|https://blog.sarine.nl/tag/gpxviewer/|{{AUR|gpx-viewer}}}}
* {{App|Navit|Modular turn-by-turn car navigation system.|https://www.navit-project.org/|{{AUR|navit}}}}
* {{App|PreviSat|PreviSat is a satellite tracking software for observing purposes|https://previsat.sourceforge.net/|{{AUR|previsat}}}}
* {{App|QMapShack|Plan your next outdoor trip.|https://github.com/Maproom/qmapshack/|{{Pkg|qmapshack}}}}
* {{App|Satellite|Displays Global Navigation Satellite System (GNSS: GPS, Galileo, Glonass etc.) information obtained from NMEA sources and saves your tracks|https://codeberg.org/tpikonen/satellite|{{AUR|satellite-gtk}}}}
* {{App|[[Wikipedia:Subsurface (software)|Subsurface]]|Diving logbook to keep track of your dives by logging dive locations (with GPS coordinates), weights and exposure protection used, divemasters and dive buddies, etc.|https://subsurface-divelog.org/|{{AUR|subsurface-git}}}}
* {{App|Viking|GTK 2 application to manage GPS data.|https://sourceforge.net/projects/viking/|{{Pkg|viking}}}}

==== Map editors ====

* {{App|JOSM|Main editor for OpenStreetMap written in Java.|https://josm.openstreetmap.de/|{{Pkg|josm}}}}
* {{App|Merkaartor|OpenStreetMap editor.|https://merkaartor.be/|{{Pkg|merkaartor}}}}
* {{App|OpenOrienteering Mapper|Orienteering mapmaking program.|https://www.openorienteering.org/apps/mapper/|{{AUR|openorienteering-mapper}}}}
* {{App|Phyghtmap|Generate OSM contour lines from NASA SRTM data|http://katze.tfiu.de/projects/phyghtmap/|{{AUR|phyghtmap}}}}

==== Geospatial data analysis and GIS ====

* {{App|GeoDa|A tool for spatial data analysis.|https://geodacenter.github.io/|{{AUR|geoda-bin}}}}
* {{App|[[Wikipedia:GRASS GIS|GRASS GIS]]|Geospatial data management and analysis, image processing, graphics/maps production, spatial modeling and visualization.|https://grass.osgeo.org/|{{AUR|grass}}}}
* {{App|[[Wikipedia:gvSIG|gvSIG]]|vSIG is a geographic information system (GIS), that is, a desktop application designed for capturing, storing, handling, analyzing and deploying any kind of referenced geographic information in order to solve complex management and planning problems.|http://www.gvsig.com/en| {{AUR|gvsig-desktop-bin}}}}
* {{App|Panoply|NetCDF, HDF and GRIB Data Viewer by NASA GISS|https://www.giss.nasa.gov/tools/panoply/|{{AUR|panoply}}}}
* {{App|[[Wikipedia:QGIS|QGIS]]| [[Wikipedia:Geographic Information System|Geographic Information System (GIS)]] that supports vector, raster & database formats.|https://qgis.org/|{{Pkg|qgis}}}}
* {{App|SAGA|A Geographic Information System (GIS) software with immense capabilities for geodata processing and analysis.|https://saga-gis.sourceforge.io/en/index.html|{{AUR|saga-gis}}}}
* {{App|WCSTools|A package of programs for setting and using the world coordinate systems|http://tdc-www.harvard.edu/wcstools/|{{AUR|wcstools}}}}

=== Geology ===

* {{App|CDI|Is a general purpose C-library with an additional Fortran interface for file IO in the geoscience area.|https://code.mpimet.mpg.de/projects/cdi|{{AUR|cdi}}}}
* {{App|EnhancedVolcano|Publication-ready volcano plots with enhanced colouring and labeling.|https://bioconductor.org/packages/release/bioc/html/EnhancedVolcano.html|{{AUR|r-enhancedvolcano}}}}
* {{App|GEOmap|Topographic and Geologic Mapping.|https://cran.r-project.org/web/packages/GEOmap/index.html|{{AUR|r-geomap}}}}
* {{App|GPlates|Is a plate tectonics program. Manipulate reconstructions of geological and paleogeographic features through geological time.|https://www.gplates.org/|{{AUR|gplates}}}}
* {{App|Gstat|Spatial and Spatio-Temporal Geostatistical Modelling, Prediction and Simulation|https://cran.r-project.org/web/packages/gstat/index.html|{{AUR|r-gstat}}}}
* {{App|Madagascar|Multidimensional data analysis and reproducible computational experiments.|https://www.reproducibility.org|{{AUR|madagascar}}}}
* {{App|SeisComP|A seismological software for data acquisition, processing, distribution and interactive analysis.|https://github.com/SeisComP/seiscomp|{{AUR|seiscomp}}}}
* {{App|Seismic Un*x|A seismic processing and research environment developed at the Center for Wave Phenomena, Colorado School of Mines|https://wiki.seismic-unix.org/start|{{AUR|seismic-unix}}}}
* {{App|TauP|A seismic travel time calculator.|https://github.com/crotwell/TauP|{{AUR|taup-git}}}}

=== Oceanography ===

* {{App|Cmocean|Colormap setup for standardizing commonly-plotting oceanographic variables.|https://github.com/matplotlib/cmocean|{{AUR|python-cmocean}}}}

=== Weather status ===

* {{App|Gis Weather|Customizable weather forecast desktop widget.|https://sourceforge.net/projects/gis-weather/|{{AUR|gis-weather}}}}
* {{App|GNOME Weather|Small application for GNOME that allows you to monitor the current weather conditions for your city, or anywhere in the world, and to access updated forecasts provided by various internet services. Part of {{Grp|gnome}}.|https://apps.gnome.org/Weather/|{{Pkg|gnome-weather}}}}
* {{App|KWeather|A convergent weather application for Plasma. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/kweather/|{{Pkg|kweather}}}}
* {{App|meteo-qt|System tray application for weather status information.|https://github.com/dglent/meteo-qt|{{AUR|meteo-qt}}}}
* {{App|wego|A terminal weather application.|https://tylerwolf35.github.io/wego{{Dead link|2025|08|15|status=404}}|{{AUR|wego}}}}
* {{App|wttr|A simple console application to check the weather, using data from https://wttr.in|https://github.com/AmirrezaFiroozi/wttr|{{AUR|wttr-bin}}}}
* {{App|Xfce Weather Panel Plugin|Weather forecast plugin for the Xfce4 panel.|https://goodies.xfce.org/projects/panel-plugins/xfce4-weather-plugin|{{Pkg|xfce4-weather-plugin}}}}

== Astronomy ==

=== Astrometrical and image processing software ===

See also [[Wikipedia:List of astrometric solvers]].

* {{App|APTS|Set of tools for automatic astrophotography images acquisition and processing|https://github.com/pozar87/apts|{{AUR|python-apts}}}}
* {{App|Astap|Astrometric (plate) solver, stacking of images, photometry and FITS viewer|https://www.hnsky.org/astap.htm|{{AUR|astap-bin-qt5}}}}
* {{App|AstroCrop|Astronomical image preprocessing tool|https://www.astrodmx-capture.org.uk/astrocrop/|{{AUR|astrocrop}}}}
* {{App|AstroImageJ|ImageJ for Astronomy|https://www.astro.louisville.edu/software/astroimagej/|{{AUR|astroimagej}}}}
* {{App|Astrometry.net|Automatic recognition of astronomical images|https://astrometry.net/|{{AUR|astrometry.net}}}}
* {{App|AudeLA|AudeLA is a TCL extension aimed at providing amateur astronomers with image processing, telescope controling, ccd camera driving, and various astronomical algorithms|https://sourceforge.net/projects/audela/|{{AUR|audela-bin}},{{AUR|audela-svn}}}}
* {{App|CARTA|Cube Analysis and Rendering Tool for Astronomy|https://cartavis.org/|{{AUR|carta-appimage}}}}
* {{App|FITSH|a software package for astronomical image processing|https://fitsh.net/|{{AUR|fitsh}}}}
* {{App|GIMP Astronomy Plugins|Set of GIMP plugins for astronomical image processing.|http://hennigbuam.de/georg/gimp.html|{{AUR|gimp-plugin-astronomy}}}}
* {{App|Ginga|A viewer for astronomical data FITS (Flexible Image Transport System) files|https://ejeschke.github.io/ginga/|{{AUR|python-ginga}}}}
* {{App|Montage|An astronomical image mosaic engine|http://montage.ipac.caltech.edu/|{{AUR|montage}}}}
* {{App|Munipack|A general astronomical image processing software|http://munipack.physics.muni.cz/|{{AUR|munipack}}, {{AUR|c-munipack}}}}
* {{App|oaCapture|A planetary imaging application using Qt5|https://www.openastroproject.org/oacapture/|{{AUR|oacapture}}}}
* {{App|PlanetarySystemStacker|Produce a sharp image of a planetary system object|https://github.com/Rolf-Hempel/PlanetarySystemStacker|{{AUR|planetarysystemstacker-git}}}}
* {{App|SCAMP|reads SExtractor catalogs and computes astrometric and photometric solutions for any arbitrary sequence of FITS images in a completely automatic way.|https://www.astromatic.net/software/scamp/|{{AUR|astromatic-scamp}}}}
* {{App|SExtractor|Is a program that builds a catalogue of objects from an astronomical image.|https://www.astromatic.net/software/sextractor/|{{AUR|astromatic-sextractor}}}}
* {{App|THELI|THELI is a data processing pipeline for optical, near-infrared and mid-infrared astronomical images|https://github.com/schirmermischa/THELI|{{AUR|theli}}}}

=== Image capture software ===

* {{App|CCDciel|A CCD capture software intended for the amateur astronomer.|https://www.ap-i.net/ccdciel//en/start|{{AUR|ccdciel}}}}
* {{App|FireCapture|The leading planetary capture tool|https://www.firecapture.de/|{{AUR|firecapture}}}}
* {{App|GoQat|Camera acquisition software, especially for QSI cameras, that provides other features such as autoguiding, focusing help and others.|https://canburytech.net/GoQat/|{{AUR|goqat}}}}
* {{App|lin_guider|astronomical autoguiding program|https://sourceforge.net/projects/linguider/|{{AUR|lin-guider}}}}
* {{App|Mrcal|Is a generic toolkit built to solve the calibration and SFM-like problems we encounter at NASA/JPL.|https://mrcal.secretsauce.net/|{{AUR|mrcal}}}}
* {{App|Open PHD Guiding|PHD2 astrophotography autoguiding tool|https://openphdguiding.org/|{{AUR|phd2}}}}
* {{App|SAOImageDS9|SAOImage DS9: Astronomical Data Visualization Application|https://sites.google.com/cfa.harvard.edu/saoimageds9|{{AUR|ds9}}}}
* {{App|[[Wikipedia:Siril (software)|Siril]]|Siril is a software application for astrophotography, which allows pre-processing and processing of images from any type of camera (CCD, planetary camera, webcam etc.)|https://siril.org/|{{AUR|siril}}}}

=== Common libraries ===

* {{App|[[Wikipedia:Astropy|Astropy]]|The Astropy Project is a community effort to develop a common core package for Astronomy in Python and foster an ecosystem of interoperable astronomy packages.|https://www.astropy.org/|{{Pkg|python-astropy}}}}
* {{App|CASA|the Common Astronomy Software Applications package.|https://casa.nrao.edu/|{{AUR|casa6-bin}}}}
* {{App|Casacore|package contains the core libraries of the old AIPS++/CASA package.|https://casacore.github.io/casacore/|{{AUR|casacore}}, {{AUR|python-casacore}}}}
* {{App|CDF|NASA Common Data Format (CDF) library for scientific data management|https://cdf.gsfc.nasa.gov/|{{AUR|cdf-nasa}}}}
* {{App|ERFA|Essential Routines for Fundamental Astronomy|https://github.com/liberfa/erfa|{{pkg|erfa}}}}
* {{App|HEASoft|NASA high energy astrophysics library|https://heasarc.gsfc.nasa.gov/docs/software/lheasoft/|{{AUR|heasoft}}}}
* {{App|libTheSky|Fortran library to compute the positions of celestial bodies and events with great accuracy|https://libthesky.sourceforge.net/|{{AUR|libthesky}}, {{AUR|libthesky-data}}}}
* {{App|Pal|Positional Astronomy Library.|https://github.com/Starlink/pal|{{AUR|starlink-pal}}}}
* {{App|PyEphem|PyEphem provides scientific-grade astronomical computations|https://rhodesmill.org/pyephem/|{{AUR|python-pyephem}}}}
* {{App|SOFA|Set of algorithms and procedures used in fundamental astronomy|http://www.iausofa.org/|{{AUR|sofa}}}}

=== Toolkits ===

* {{App|AstroML|Machine learning, statistics, and data mining for astronomy and astrophysics|https://www.astroml.org/|{{AUR|python-astroml}}}}
* {{App|Exoplanet|exoplanet is a toolkit for probabilistic modeling of time series data in astronomy with a focus on observations of exoplanets|https://github.com/exoplanet-dev/exoplanet|{{AUR|exoplanet-git}}}}
* {{App|Galpy|Galactic Dynamics in python|https://www.galpy.org/|{{AUR|python-galpy}}}}
* {{App|Gammapy|A Python package for gamma-ray astronomy|https://gammapy.org/|{{AUR|python-gammapy}}}}
* {{App|HEALPix|Software for pixelization, hierarchical indexation, synthesis, analysis, and visualization of data on the sphere|https://healpix.jpl.nasa.gov/{{Dead link|2025|11|17|status=domain name not resolved}}|{{AUR|healpix}}}}
* {{App|JHelioviewer|Visualization software for solar image data in space weather context|https://www.jhelioviewer.org/|{{AUR|jhelioviewer}}}}
* {{App|JMARS|Java Mission-planning and Analysis for Remote Sensing.|https://jmars.mars.asu.edu/{{Dead link|2025|08|15|status=SSL error}}|{{AUR|jmars}}}}
* {{App|JSkyCalc|A tool for observing preparation in java|https://caligari.dartmouth.edu/public/downloads/skycalc/|{{AUR|jskycalc}}}}
* {{App|Period04|Period04 is a computer program especially dedicated to the statistical analysis of large astronomical time series containing gaps|https://period04.net/|{{AUR|period04}}}}
* {{App|[[Wikipedia:WorldWide Telescope|Pywwt]]|Is the official toolkit for accessing AAS WorldWide Telescope (WWT) from Python|https://pywwt.readthedocs.io/en/stable/|{{AUR|python-pywwt}}}}
* {{App|RochePlot|Plot the key stages in the evolution of a binary star|https://rocheplot.sourceforge.net/|{{AUR|rocheplot}}}}
* {{App|Skyfield|Elegant astronomy for Python|https://rhodesmill.org/skyfield/|{{AUR|python-skyfield}}}}
* {{App|SolTrack|A free, fast and accurate C/C++ routine to compute the position of the Sun|https://soltrack.sourceforge.net/|{{AUR|soltrack}}}}
* {{App|SPICE|A comprehensive toolkit and api to design, simulate and analyse space missions|https://naif.jpl.nasa.gov/naif/index.html|{{AUR|cspice}}}}
* {{App|STILTS|Starlink Tables Infrastructure Library Tool Set|https://www.star.bris.ac.uk/~mbt/stilts/|{{AUR|stilts}}}}
* {{App|sunclock|An astronomical world map that shows day and night and the Sun and Moon positions|https://www.spinnaker.de/debian/sunclock.html|{{AUR|sunclock}}}}
* {{App|Tempo|Pulsar Timing Software|https://tempo.sourceforge.net/tempo_idx.html|{{AUR|tempo-git}}}}
* {{App|TOPCAT|Tool for OPerations on Catalogues And Tables|https://www.star.bris.ac.uk/~mbt/topcat/|{{AUR|topcat}}}}
* {{App|VaST|VaST is a software tool for finding variable objects on a series of astronomical images|https://scan.sai.msu.ru/vast/|{{AUR|vast-astronomical-git}}}}
* {{App|VStar|VStar is a multi-platform, easy-to-use variable star data visualization and analysis tool that was originally developed as part of the AAVSOs Citizen Sky project|https://www.aavso.org/vstar|{{AUR|vstar-aavso}}}}

=== Calculators and CLI utilities ===

* {{App|astroTools|Command-line tools for astronomy and astrophysics|https://astrotools.sourceforge.net/|{{AUR|astrotools}}}}
* {{App|Gnuastro|Various programs and library functions for the manipulation and analysis of astronomical data|https://www.gnu.org/software/gnuastro/|{{AUR|gnuastro}}}}
* {{App|Kosmorro|A program to calculate the ephemerides|https://kosmorro.space/|{{AUR|kosmorro}}}}
* {{App|Project Pluto|Project Pluto supplies astronomical software, both commercial and freeware, to amateur and professional astronomers|https://www.projectpluto.com/|{{AUR|pluto-lunar-git}}, {{AUR|pluto-sat-code-git}}, {{AUR|pluto-jpl-eph-git}}, {{AUR|pluto-find-orb-git}}}}
* {{App|star-charter|A command-line tool for producing vector-graphics charts of the night sky in SVG, PDF and PNG formats|https://github.com/dcf21/star-charter|{{AUR|star-charter-git}}}}
* {{App|Sunwait|Calculate sunrise/sunset times with civil, nautical, astronomical and custom twilights|https://github.com/risacher/sunwait|{{AUR|sunwait}}}}

=== Management of telescopes and observatories ===

* {{App|GILDAS|Is a collection of state-of-the-art software oriented toward (sub-)millimeter radioastronomical applications (either single-dish or interferometer)|https://www.iram.fr/IRAMFR/GILDAS/|{{AUR|gildas}}}}
* {{App|imSim|software package that simulates the LSST telescope and survey|https://github.com/LSSTDESC/imSim|{{AUR|python-imsim-git}}}}
* {{App|rubin_sim|Scheduler, survey strategy analysis, and other simulation tools for Rubin Observatory|https://github.com/lsst/rubin_sim|{{AUR|python-rubinsim-git}}}}
* {{App|Srt-py|Small Radio Telescope Control Code for Python.|https://github.com/MITHaystack/srt-py|{{AUR|srt-py-git}}}}

=== Simulation ===

* {{App|APSYNSIM|Aperture Synthesis Simulator for Radio Astronomy|https://launchpad.net/apsynsim|{{AUR|apsynsim}}}}
* {{App|FriendlyVRI|Is designed to simulate astronomical observations using linked arrays of radio antennas in a technique called earth rotation aperture synthesis|https://github.com/crpurcell/friendlyVRI|{{AUR|friendlyvri-git}}}}
* {{App|Galaxy2|Is program which simulates the motion of stars under the influence of gravity|https://www.kornelix.net/galaxy2/galaxy2.html|{{AUR|galaxy2}}}}
* {{App|GalSim|Modular galaxy image simulation toolkit|https://github.com/GalSim-developers/GalSim|{{AUR|python-galsim}}}}
* {{App|Pynterferometer|Is a graphical interface designed to demonstrate the techniques of radio interferometry used by telescopes|https://www.jb.man.ac.uk/pynterferometer/index.html|{{AUR|pynterferometer}}}}

=== Space exploration programs ===

* {{App|Cosmographia|Cosmographia is a visualization program rendering the solar system and its bodies in 3D to create a freely navigable map of the solar system|https://naif.jpl.nasa.gov/naif/cosmographia.html|{{AUR|cosmographia-bin}}}}
* {{App|Cosmonium|3D astronomy and space exploration program|https://github.com/cosmonium/cosmonium|{{AUR|cosmonium-bin}}}}
* {{App|OpenSpace|OpenSpace is an open source, non-commercial, and freely available interactive data visualization software designed to visualize the entire known universe and portray our ongoing efforts to investigate the cosmos|https://www.openspaceproject.com/|{{AUR|openspace-git}}}}
* {{App|Our Galaxy|Is a unique app that helps you understand the structural components of the Galaxy and visualize the locations and physical properties of deep sky objects in and around it|https://www.otherwise.com/|{{AUR|ourgalaxy-bin}}}}

=== Planetary and virtual atlas ===

See also [[Wikipedia:Planetarium software]] and [[Wikipedia:List of observatory software]].

* {{App|Aladin|Interactive software sky atlas|http://aladin.u-strasbg.fr/aladin.gml|{{AUR|aladin}}}}
* {{App|astroterm|Terminal-based star map written in C, which displays a star map in real time. Date, time, location and speed are configurable.|https://github.com/da-luce/astroterm|{{Pkg|astroterm}}}}
* {{App|[[Wikipedia:Celestia|Celestia]]|3D astronomy simulation program that allows users to travel through an extensive universe, modeled after reality, at any speed, in any direction and at any time in history.|https://celestiaproject.space/|{{AUR|celestia}}}}
* {{App|Gaia Sky|An open source 3D universe simulator with support for more than a billion objects|https://zah.uni-heidelberg.de/gaia/outreach/gaiasky|{{AUR|gaiasky}}}}
* {{App|HNSKY|Hallo Northern Sky is the semi professional free planetarium program|https://sourceforge.net/projects/hnsky/|{{AUR|hnsky-hg}}}}
* {{App|[[Wikipedia:KStars|KStars]]|Planetarium application that provides an accurate graphical simulation of the night sky, from any location on Earth, at any date and time. It is included in KDE Edu.|https://kstars.kde.org/|{{Pkg|kstars}}}}
* {{App|[[Wikipedia:Cartes du Ciel|Skychart / Cartes du Ciel]]|Planetarium that maps out and labels most of the constellations, planets, and objects you can see with a telescope. It can also download Digitized Sky Survey Charts and superimpose images over these charts.|https://www.ap-i.net/skychart/|{{AUR|skychart-git}}}}
* {{App|[[Wikipedia:Stellarium (computer program)|Stellarium]]|Beautiful 3D planetarium that uses OpenGL to render a realistic sky in real time.|https://stellarium.org/|{{Pkg|stellarium}}}}
* {{App|Virtual Moon Atlas|Software for Moon observation and survey|https://www.ap-i.net/avl/en/start|{{AUR|virtualmoonatlas}}}}
* {{App|[[Wikipedia:XEphem|XEphem]]|Motif-based ephemeris and planetarium program.|https://xephem.github.io/XEphem/Site/xephem.html|{{AUR|xephem}}}}

== Biology ==

=== Computational biology and bioinformatics ===

See also [[Wikipedia:List of open source bioinformatics software]].

* {{App|[[Wikipedia:Biopython|Biopython]]|Python package with tools for computational biology, as well as bioinformatics.|https://biopython.org/wiki/Biopython|{{AUR|python-biopython}}}}
* {{App|[[Wikipedia:EMBOSS|EMBOSS]] (European Molecular Biology Open Software Suite)|Open source software analysis package specially developed for the needs of the molecular biology and bioinformatics user community.|https://emboss.sourceforge.net/|{{AUR|emboss}}}}
* {{App|[[Wikipedia:MUMmer|MUMmer]]|Bioinformatics software system for sequence alignment based on suffix trees.|https://mummer.sourceforge.net/|{{AUR|mummer}}}}
* {{App|Snapgene|Closed source molecular cloning application that offers a fast and easy way to plan, visualize, and document molecular biology procedures. Supports a wide range of cloning and PCR manipulations. The free version allows most common visualizations of a molecular biology workflow.|https://www.snapgene.com/|{{AUR|snapgene}}}}
* {{App|[[Wikipedia:UGENE|UGENE]]|Application that integrates dozens of well-known biological tools and algorithms, providing both graphical user and command-line interfaces.|https://ugene.net/|{{AUR|ugene}}}}

=== Genealogy ===

* {{App|[[Wikipedia:Gramps (software)|Gramps]]|Genealogy program, which helps you track your family tree.|https://gramps-project.org/|{{Pkg|gramps}}}}

* {{App|[[Wikipedia:LifeLines|LifeLines]]|Text based genealogy software for family trees and reports.|https://github.com/lifelines/|{{AUR|lifelines}}}}

=== Image manipulation ===

* {{App|[[Wikipedia:FIJI_(software)|Fiji]]| {{AUR|ImageJ2}} distribution with a lot of plugins organized into a coherent menu structure.|https://fiji.sc|{{AUR|fiji-bin}}}}
* {{App|[[Wikipedia:ImageJ|ImageJ]]|Java-based image processing and analysing program that provides extensibility via plugins and macros. It is widely used in microscopy (e.g. for cell counting).|https://imagej.net/ij/|{{AUR|imagej}}}}

=== DICOM viewers and volume rendering ===

* {{App|[[Wikipedia:3DSlicer|3DSlicer]]|Comprehensive [[Wikipedia:Magnetic resonance imaging|MRI]], [[Wikipedia:CT scan|CT]], [[Wikipedia:Laser scanning confocal microscopy|LSCM microscopy]] volume processing, segmentation and 3D-reconstruction|https://www.slicer.org/|{{AUR|3dslicer}}}}
* {{App|aeskulap|Simple DICOM data viewer|https://www.nongnu.org/aeskulap/|{{AUR|aeskulap}}}}
* {{App|aliza|Open 2D, 3D and 4D images in DICOM, MetaIO, Nifti, Nrrd and other formats, meshes in DICOM, VTK, STL and OBJ formats|https://www.aliza-dicom-viewer.com/|{{AUR|aliza}}}}
* {{App|[[Wikipedia:ParaView|ParaView]]|Interactive data visualization tool built using VTK that can scale across distributed computer hardware.|https://www.paraview.org/|{{Pkg|paraview}}}}
* {{App|weasis|Multipurpose DICOM viewer with a highly modular architecture|https://nroduit.github.io/en/|{{AUR|weasis-bin}}}}

== Engineering ==

=== Computer-aided design ===

See also [[Wikipedia:List of computer-aided design editors]].

* {{App|[[Wikipedia:BRL-CAD|BRL-CAD]]|Constructive solid geometry modeling CAD system that includes an interactive geometry editor, ray tracing support for graphics rendering and geometric analysis, computer network distributed framebuffer support, scripting, image-processing and signal-processing tools.|https://brlcad.org/|{{AUR|brlcad}}}}
* {{App|[[Wikipedia:FreeCAD|FreeCAD]]|Parametric 3D CAD modeler based on OpenCascade, Coin3D, Qt, and Python with features such as macro recording, workbenches and the ability to run as a server.|https://freecad.org/|{{Pkg|freecad}}}}
* {{App|LeoCAD|CAD program for creating virtual LEGO models. It has an easy to use interface and currently includes over 10,000 different pieces created by the LDraw community.|https://www.leocad.org/|{{Pkg|leocad}}}}
* {{App|[[Wikipedia:LibreCAD|LibreCAD]]|A 2D CAD application based on Qt5. Forked from QCAD Community Edition.|https://www.librecad.org/|{{Pkg|librecad}}}}
* {{App|[[Wikipedia:OpenSCAD|OpenSCAD]]|A 3D CAD modeler that uses a textual, programmatic approach to creating and manipulating objects.|https://www.openscad.org|{{Pkg|openscad}}}}
* {{App|[[Wikipedia:QCad|QCAD]]|A 2D CAD application based on Qt. Supports the DFX and HPGL standard file formats, and optionally the DWG format through a proprietary plugin.|https://www.qcad.org/|{{Pkg|qcad}}}}
* {{App|[[Wikipedia:SolveSpace|SolveSpace]]|Powerful 3D CAD constraint-based parametric modeler with simple mechanical simulation capabilities.|https://solvespace.com/|{{AUR|solvespace}}}}

=== 3D printing ===

See also [[RepRap]].

==== Slicers ====

Slicers convert 3D models into a format supported by the 3D printer, usually this format is G-code.

* {{App|BambuStudio|Slicer for printers from BambuLabs. Fork of PrusaSlicer. Open source.|https://github.com/bambulab/BambuStudio|{{AUR|bambustudio-bin}}}}
* {{App|[[Wikipedia:Cura_(software)|Cura]]|Slicer by Ultimaker. Aimed at their printers but supports other brands as well. Open source.|https://ultimaker.com/software/ultimaker-cura|{{AUR|cura}}}}
* {{App|FlashPrint|Slicer for the FlashForge 3D printers. Closed source.|http://www.ff3dp.com/|{{AUR|flashprint}}}}
* {{App|icesl|Modelling software with integrated slicer. Not brand specific. Closed source.|https://icesl.loria.fr/|{{AUR|icesl}}}}
* {{App|IdeaMaker|Slicer by Raise3D. Aimed at their printers but supports other brands as well. Closed source.|https://www.raise3d.com/pages/ideamaker|{{AUR|ideamaker}}}}
* {{App|MatterControl|Simple 3D editor, slicer, and 3D printer control software by MatterHackers. Not brand specific. Open source.|http://www.mattercontrol.com|{{AUR|mattercontrol}}}}
* {{App|orca-slicer|Community maintained fork of BambuStudio (in turn forked from PrusaSlicer). Open Source.|https://github.com/SoftFever/OrcaSlicer|{{AUR|orca-slicer}}}}
* {{App|[[PrusaSlicer]]|Slicer by Prusa Research. A fork of Slic3r. Aimed at their printers but supports other brands as well. Open source.|https://github.com/prusa3d/PrusaSlicer|{{Pkg|prusa-slicer}}}}
* {{App|Slic3r|One of the earliest slicers. Not used much any longer. Not brand specific. Open source.|https://slic3r.org/|{{AUR|slic3r}}}}
* {{App|SuperSlicer|Community maintained improved fork of PrusaSlicer. Not brand specific. Open source.|https://github.com/supermerill/SuperSlicer|{{AUR|superslicer-bin}}}}

==== Control software ====

Software for controlling 3D printers, usually over a cable or wireless.

* {{App|OctoPrint|Web interface for FDM 3D printers using G-code. Open source.|https://octoprint.org/|{{AUR|octoprint}}}}
* {{App|PrintRun|GUI control software for FDM 3D printers using G-code. Open source.|https://github.com/kliment/Printrun|{{AUR|printrun}}}}
* {{App|[[Wikipedia:Repetier-Host|Repetier-Host]]|Combined slicer and control software for 3D printers. Closed source.|https://www.repetier.com/|{{AUR|repetier-host}}}}

=== Electronics ===

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

==== Digital logic ====

Digital logic software are mainly simple educational tools that intended for only designing and simulating logic circuits.

* {{App|Digital|Interactive simulator similar to the discontinued Logisim. Features Karnaugh maps, logic tables, FSM editor, VHDL export and more, written in Java.|https://github.com/hneemann/Digital|{{AUR|digital}}}}
* {{App|GTKWave|Fully featured GTK-based wave viewer which reads LXT, LXT2, VZT, FST, and GHW files as well as standard Verilog VCD/EVCD files and allows their viewing.|https://gtkwave.sourceforge.net/|{{Pkg|gtkwave}}}}
* {{App|Logisim|Educational digital logic design and simulation software, written in Java, officially its development has stopped.|https://sourceforge.net/projects/circuit/|{{AUR|logisim}}}}
* {{App|Logisim Evolution|Project which continue the development of the original Logisim with new features, written in Java.|https://github.com/reds-heig/logisim-evolution|{{AUR|logisim-evolution-git}}}}
* {{App|PulseView|Logic analyzer, oscilloscope and MSO GUI.|https://sigrok.org/wiki/PulseView|{{Pkg|pulseview}}}}
* {{App|SmartSim|Simple and beautiful digital logic circuit design and simulation software, mainly target teachers and students, very lightweight and cross platform, GPL licensed, written in Vala.|https://smartsim.org.uk|{{AUR|smartsim-git}}}}
* {{App|WaveDrom editor|Timing diagram rendering in real-time from simple textual description. Can also be edited and embedded in the browser.|https://wavedrom.com/|{{AUR|wavedrom-editor}}}}

==== HDL ====

Also see [[Wikipedia:Hardware description language]].

* {{App|GHDL|Free and Open Source VHDL 2008/93/87 analyzer, compiler and simulator.|https://github.com/ghdl/ghdl|{{AUR|ghdl}}}}
* {{App|Gowin EDA Edu IDE|An IDE for Gowin's FGPA devices, including Sipeed Tang Nano and Sipeed Tang Nano 4K.|https://www.gowinsemi.com.cn/faq.aspx|{{AUR|gowin-eda-edu-ide}}}}
* {{App|[[Intel Quartus Prime]]|A set of design tools for Intel's FPGA devices that includes Quartus Prime, ModelSim-Intel, HLS Compiler, etc.|https://www.intel.com/content/www/us/en/software/programmable/overview.html|{{AUR|quartus-free}}}}
* {{App|iverilog|Icarus Verilog compiler and simulation tool (slower but older than Verilator).|https://steveicarus.github.io/iverilog/|{{Pkg|iverilog}}}}
* {{App|[[Lattice Diamond]]|A set of design tools for Lattice's FPGA chips.|https://www.latticesemi.com|{{AUR|lattice-diamond}}}}
* {{App|[[Microsemi Libero]]|Development tools for designing with Microsemi's PolarFire, IGLOO2, SmartFusion2, RTG4, SmartFusion, IGLOO, ProASIC3 and Fusion families.|https://www.microsemi.com/product-directory/design-resources/1750-libero-soc#overview|see [[Microsemi Libero]]}}
* {{App|OpenFPGAloader|Universal utility for programming FPGA. Try {{AUR|openfpgaloader-git}} if your board is not managed by the stable version.|https://github.com/trabucayre/openFPGALoader|{{Pkg|openfpgaloader}}}}
* {{App|[[Wikipedia:Verilator|Verilator]]|A Verilog/SystemVerilog simulator, performs lint code-quality checks, compile to threaded C++ code for simulation.|https://verilator.org|{{Pkg|verilator}}}}
* {{App|VTR|Verilog to Routing, Open Source CAD Flow for FPGA ResearchVerilog to Route.|https://verilogtorouting.org|{{Pkg|vtr}}}}
* {{App|[[Xilinx ISE WebPACK]]|FPGA programmable logic design suit.|https://www.xilinx.com/products/design-tools/ise-design-suite/ise-webpack.html|see [[Xilinx ISE WebPACK]]}}

==== MCU IDE and programmers ====

* {{App|[[Arduino]]|Arduino prototyping platform SDK.|https://www.arduino.cc/en/Main/Software|{{Grp|arduino}}}}
* {{App|avrcalc|Calculator to speed development of Atmel AVRs.|https://sourceforge.net/projects/avrcalc|{{AUR|avrcalc}}}}
* {{App|AVRDUDE|Download/upload/manipulate the ROM and EEPROM contents of AVR microcontrollers.|https://www.nongnu.org/avrdude/|{{Pkg|avrdude}}}}
* {{App|dfu-util|Device firmware update (DFU) USB programmer.|https://dfu-util.sourceforge.net/|{{Pkg|dfu-util}}}}
* {{App|esp-idf|Espressif IoT Development Framework. Official development framework for ESP32.|https://github.com/espressif/esp-idf|{{AUR|esp-idf}}}}
* {{App|platformio|Collaborative platform for embedded development, embedded development, with debugger, unit testing, code analysis. Default IDE is [[VSCode]], but can be used by Atom, Eclipse, Emacs, Qt Creator, Vim and several other IDE. Core CLI utils.|https://platformio.org/|{{Pkg|platformio-core}}}}
* {{App|sdcc|Small Device C Compiler, appropriate for various 8-bit microcontrollers and microprocessors including those made by or based on Intel MCS51, Maxim/Dallas, DS80C390, Freescale/Motorola HC08, Zilog Z80, Padauk, ST Microelectronics STM8, MOS 6502, and WDC 65C02. Suite contains compiler, assembler, linker, preprocessor, various simulators, debuggers, etc. |https://sdcc.sourceforge.net/|{{Pkg|sdcc}}}}
* {{App|SPIPGM|Tool for programming serial SPI FlashROM memories attached to PC via parallel port cable.|https://rayer.g6.cz/programm/programe.htm|{{AUR|spipgm-bin}}}}
* {{App|stlink|Open source [https://www.st.com/en/microcontrollers-microprocessors.html STM32 MCU] programming toolset for ST microcontrollers.|https://github.com/texane/stlink|{{Pkg|stlink}}}}

==== Electronic circuit simulation and schematic capture editing ====

* {{App|easy_spice|Electronic circuit simulator. SPICE frontend, using gschem for schematics and ngspice as simulator.|https://easy-spice.sourceforge.net|{{AUR|easy_spice}}}}
* {{App|[[Wikipedia:GNU Circuit Analysis Package|gnucap]]|GNU circuit simulator.|http://gnucap.org|{{AUR|gnucap}}}}
* {{App|gspiceui|GUI to various freely available Spice electronic circuit simulators.|https://sourceforge.net/projects/gspiceui/|{{AUR|gspiceui}}}}
* {{App|[[Wikipedia:ngspice|ngspice]]|The established Linux circuit simulator. Open source successor of the [[Wikipedia:SPICE|spice3f5]] code. Has the most versatile user interface; supporting scripting within the circuit descriptions, use through an interpreter, as a C library, through tcl or various external wrappers (e.g., Python).|https://ngspice.sourceforge.net/|{{Pkg|ngspice}}}}
* {{App|[[Wikipedia:Oregano (software)|Oregano]]|Graphical software application for schematic capture and simulation of electrical circuits. The actual simulation is done by the [[Wikipedia:Ngspice|ngspice]] or [[Wikipedia:GNU Circuit Analysis Package|Gnucap]] engines.|https://github.com/drahnr/oregano|{{AUR|oregano}}}}
* {{App|[[Wikipedia:Quite Universal Circuit Simulator|Qucs]]|Electronics circuit simulator application that gives you the ability to set up a circuit with a graphical user interface and simulate its large-signal, small-signal and noise behaviour.|https://qucs.sourceforge.net|{{AUR|qucs}}}}
* {{App|qucs-s|Electronics circuit simulator that gives you the ability to set up a circuit with a GUI and simulate it. Fork of qucs that uses external, better, programs to do actual simulation.|https://ra3xdh.github.io/|{{AUR|qucs-s}}}}
* {{App|Xyce|SANDIA Xyce is an open source, SPICE-compatible, high-performance analog circuit simulator, capable of solving extremely large circuit problems by supporting large-scale parallel computing platforms.|https://xyce.sandia.gov https://github.com/Xyce/Xyce|{{AUR|xyce-serial}}}}

==== Electronic design and schematic capture editing ====

* {{App|asco|SPICE Circuit Optimizer.|https://asco.sourceforge.net|{{AUR|asco}}}}
* {{App|[[Wikipedia:Fritzing|Fritzing]]|Easy to use program to draw good-looking circuit diagrams, and also create schematics and PCBs.|https://fritzing.org/home/|{{AUR|fritzing}}}}
* {{App|[[gEDA]]|Full suite and toolkit of Electronic Design Automation tools that are used for electrical circuit design, schematic capture, simulation, prototyping, and production.|http://www.geda-project.org/|{{AUR|geda-gaf}}}}
* {{App|[[gEDA]] PCB|Interactive printed circuit board editor.|http://pcb.geda-project.org/|{{AUR|pcb}}}}
* {{App|[[Wikipedia:KiCad|KiCad]]|Software suite for electronic design automation (EDA) that facilitates the design of schematics for electronic circuits and their conversion to PCB (printed circuit board).|https://kicad.org/|{{Pkg|kicad}}}}
* {{App|[[Wikipedia:KTechLab|KTechLab]]|IDE for microcontrollers and electronic circuit simulation.|https://apps.kde.org/ktechlab/|{{AUR|ktechlab}}}}
* {{App|QElectroTech|Application used to draw advanced electrical circuits.|https://qelectrotech.org/|{{AUR|qelectrotech}}}}

== Telecommunication ==

* {{App|[[GNU Radio]]|Software development toolkit that provides signal processing blocks to implement software radios.|https://www.gnuradio.org/|{{Pkg|gnuradio}}}}
* {{App|Gqrx|Software defined radio receiver implemented using GNU Radio and the Qt GUI toolkit.|https://gqrx.dk/|{{Pkg|gqrx}}}}
* {{App|Pothos|The Pothos project is a complete data-flow framework for creating topologies of interconnected processing blocks. |https://github.com/pothosware/PothosCore/wiki|{{AUR|pothos}}, {{AUR|pothos-git}}}}
* {{App|SDR#|The most popular SDR program.|https://airspy.com/|{{AUR|sdrsharp}}}}
* {{App|SigDigger|Qt-based digital signal analyzer, using Suscan core and Sigutils DSP library.|https://github.com/BatchDrake/SigDigger|{{AUR|sigdigger-git}}}}

=== Amateur radio ===

See the main article: [[Amateur radio#Software]].

See also [[Wikipedia:List of software-defined radios]].

== Simulation modeling ==

* {{App|[[Wikipedia:AnyLogic|AnyLogic]]|AnyLogic is a cross-platform proprietary multimethod simulation modeling tool, which is also available for personal use.|https://www.anylogic.com/|{{AUR|anylogic-ple}}, {{AUR|anylogic-university}}, {{AUR|anylogic-professional}}}}
* {{App|[[Wikipedia:Flight Gear|Flight Gear]]|Open-source, multi-platform atmospheric and orbital flight simulator with a flight dynamics engine (JSBSim) that is part of a [https://web.archive.org/web/20201115084247/https://nescacademy.nasa.gov/src/flightsim/Reports/aiaa-15-1810-EOM_chkcases-II.pdf 2015 NASA benchmark] to judge new simulation code to space industry standards.|https://www.flightgear.org/|{{AUR|flightgear}}}}
* {{App|[[Wikipedia:Gephi|gephi]]|Gephi is an open-source network analysis and visualization software package written in Java.|https://gephi.org/|{{AUR|gephi}}}}
* {{App|golly|Golly is an open source, cross-platform application for exploring Conway's Game of Life and many other types of cellular automata.|https://golly.sourceforge.net/|{{AUR|golly}}}}
* {{App|Netlogo|NetLogo is a multi-agent programmable modeling environment.|https://ccl.northwestern.edu/netlogo/|{{AUR|netlogo}}}}

== Computer science ==

=== Architecture ===

* {{App|edumips64|Cross-platform educational MIPS64 CPU simulator.|https://edumips.org/|{{AUR|edumips64}}}}
* {{App|QtMips|MIPS CPU simulator for education purposes with pipeline and cache visualization.|https://github.com/cvut/QtMips|{{AUR|qtmips}}}}
* {{App|QtRvSim|RISC-V CPU simulator for education purposes.|https://github.com/cvut/qtrvsim|{{AUR|qtrvsim}}}}
* {{App|QtSpim|Qt port of one of the first educational MIPS CPU simulators. No longer maintained, but still used in some classrooms.|https://spimsimulator.sourceforge.net/|{{AUR|qtspim}}}}

=== Distributed systems ===

* {{App|Shadow|An open-source distributed system/network simulator/emulator hybrid (e.g. for [[Tor]] and [[Bitcoin]]).|https://shadow.github.io/|{{AUR|tor-shadow}}}}
* {{App|[[Wikipedia:SimGrid|SimGrid]]|A scientific instrument to study large-scale distributed systems.|https://simgrid.org/|{{AUR|simgrid}}}}

=== Networking ===

* {{App|CORE|Common Open Research Emulator.|https://www.nrl.navy.mil/Our-Work/Areas-of-Research/Information-Technology/NCS/CORE/|{{AUR|core}}}}
* {{App|[[Wikipedia:Graphical Network Simulator-3|GNS3]]|Network software emulator using a combination of virtual and real devices to simulate complex networks.|https://gns3.com/|{{AUR|gns3-gui}} (graphical user interface package), {{AUR|gns3-server}} (server package)}}
* {{App|IMUNES|Integrated Multiprotocol Network Emulator/Simulator.|https://imunes.net/|{{AUR|imunes}}}}
* {{App|[[Wikipedia:Ns (simulator)|ns-2]]|Discrete event simulator targeted at networking research.|https://www.isi.edu/nsnam/ns/|{{AUR|ns}}}}
* {{App|[[Wikipedia:Ns (simulator)|ns-3]]|Discrete-event network simulator for Internet systems.|https://www.nsnam.org/|{{AUR|ns3}}}}
* {{App|[[Wikipedia:OMNeT++|OMNeT++]]|Component-based simulation package designed for modeling communication networks.|https://omnetpp.org/|{{AUR|omnetpp}}}}

=== Photogrammetry ===

See also [[Wikipedia:Comparison_of_photogrammetry_software]].

* {{App|AliceVision|Photogrammetric Computer Vision Framework|https://alicevision.org/|{{AUR|alice-vision}}}}
* {{App|Meshroom|Node-based GUI for AliceVision|https://alicevision.org/#meshroom|{{AUR|meshroom}}}}
* {{App|OpenMVG|OpenMVG provides an end-to-end 3D reconstruction-from-images framework compounded of libraries, binaries, and pipelines.|https://github.com/openMVG/openMVG|{{AUR|openmvg-git}}}}
* {{App|OpenMVS|A library for computer-vision scientists and especially targeted to the Multi-View Stereo reconstruction community. |https://cdcseacave.github.io|{{AUR|openmvs}}}}

List of applications/Science

2026-05-13T10:35:20Z

Erus Iluvatar: /* Statistics */ rm dead jamovi entry

[[Category:Lists of software]]
[[Category:Science]]
[[es:List of applications (Español)/Science]]
[[hu:List of applications (Magyar)/Science]]
[[ja:アプリケーション一覧/サイエンス]]
[[pl:List of applications (Polski)/Science]]
[[zh-hans:List of applications/Science]]
{{List of applications navigation}}

== Mathematics ==

=== Calculator ===

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

==== Console ====

* {{App|[[Wikipedia:bc programming language|bc]]|Arbitrary precision calculator language.|https://www.gnu.org/software/bc/|{{Pkg|bc}}}}
* {{App|calc|Arbitrary precision console calculator.|http://www.isthe.com/chongo/tech/comp/calc/|{{Pkg|calc}}}}
* {{App|calcpy|Terminal calculator and advanced math solver using Python, IPython and SymPy.|https://github.com/idanpa/calcpy|{{AUR|python-calcpy-git}}{{Broken package link|package not found}}}}
* {{App|clac|Command-line, stack-based calculator with postfix notation.|https://github.com/soveran/clac|{{AUR|clac}}}}
* {{App|kalker|Command-line calculator with math syntax that supports user-defined variables and functions, complex numbers, and estimation of derivatives and integrals.|https://github.com/PaddiM8/kalker|{{AUR|kalker}}}}
* {{App|Numbat|A statically typed programming language for scientific computations with first class support for physical dimensions and units.|https://numbat.dev|{{Pkg|numbat}}}}
* {{App|qalc|Command-line calculator and equation solver with fault-tolerant parsing, constant recognition and units.|https://qalculate.github.io/|{{Pkg|libqalculate}}}}

==== Graphical ====

* {{App|Binary|Simple app to convert between different hexadecimal and binary numbers.|https://apps.gnome.org/Binary/|{{Pkg|binary}}}}
* {{App|Cutefish Calculator|Calculator for Cutefish desktop.|https://github.com/cutefishos/calculator|{{AUR|cutefish-calculator}}}}
* {{App|Deepin Calculator|Easy to use calculator for Deepin desktop.|https://www.deepin.org/en/original/deepin-calculator/|{{Pkg|deepin-calculator}}}}
* {{App|Extcalc|Qt-based scientific graphical calculator.|https://extcalc-linux.sourceforge.net/|{{AUR|extcalc}}}}
* {{App|FOX Calculator|Simple desktop calculator.|http://fox-toolkit.org/|{{Pkg|fox}}}}
* {{App|galculator|GTK-based scientific calculator.||{{Pkg|galculator}}}}
* {{App|[[Wikipedia:Genius (mathematics software)|Genius]]|Advanced calculator including a mathematical programming language.|https://www.jirka.org/genius.html|{{Pkg|genius}}}}
* {{App|[[Wikipedia:GNOME Calculator|GNOME Calculator]]|Scientific calculator included in the GNOME desktop. Part of {{Grp|gnome}}.|https://apps.gnome.org/Calculator/|{{Pkg|gnome-calculator}}}}
* {{App|[[Wikipedia:KAlgebra|KAlgebra]]|Calculator and 3D plotter. Part of {{Grp|kde-education}}.|https://apps.kde.org/kalgebramobile/|{{Pkg|kalgebra}}}}
* {{App|Kalk|A convergent calculator application built with the Kirigami framework. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/kalk/|{{Pkg|kalk}}}}
* {{App|[[Wikipedia:KCalc|KCalc]]|Scientific calculator included in the KDE desktop. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/kcalc/|{{Pkg|kcalc}}}}
* {{App|KEuroCalc|Universal currency converter and calculator.|https://apps.kde.org/keurocalc/|{{AUR|keurocalc}}}}
* {{App|Liri Calculator|Calculator for Liri.|https://github.com/lirios/calculator|{{AUR|liri-calculator}}}}
* {{App|MATE Calc|Calculator for the MATE desktop environment.|https://mate-desktop.org/|{{Pkg|mate-calc}}}}
* {{App|Qalculate!|Calculator and equation solver with fault-tolerant parsing, constant recognition and units.|https://qalculate.github.io/|GTK: {{Pkg|qalculate-gtk}}, Qt: {{Pkg|qalculate-qt}}}}
* {{App|SpeedCrunch|Fast, high precision and powerful cross-platform calculator.|https://speedcrunch.org|{{Pkg|speedcrunch}}}}
* {{App|Valuta|Simple application for converting currencies.|https://apps.gnome.org/Valuta/|{{Pkg|valuta}}}}
* {{App|[[xcalc]]|Scientific calculator for X with algebraic and reverse polish notation modes.|https://www.x.org/|{{Pkg|xorg-xcalc}}}}

==== Texas Instruments ====

* {{App|ticemu|Third-party TI-84 Plus CE / TI-83 Premium CE emulator, focused on developer features.|https://ce-programming.github.io/CEmu/|{{AUR|ticemu}}}}
* {{App|firebird-nspire|Multi-platform emulator of TI Nspire calculators.|https://github.com/nspire-emus/firebird|{{AUR|firebird-nspire}}}}
* {{App|TiEmu|Emulator of TI-89/92/92+/V200 calculators.|https://github.com/debrouxl/tiemu|{{AUR|tiemu}}}}
* {{App|wxwabbitemu|A cross-platform TI-8x emulator based on Wabbitemu.|https://github.com/alberthdev/wxwabbitemu|{{AUR|wxwabbitemu-git}}}}

=== Computer algebra system ===

See also [[Wikipedia:Comparison of computer algebra systems]].

* {{App|[[Wikipedia:Axiom (computer algebra system)|AXIOM]]|FriCAS: derivative of the powerful AXIOM-CAS.|https://fricas.sourceforge.net|{{Pkg|fricas}}}}
* {{App|[[Wikipedia:GAP (computer algebra system)|GAP]]|Computer algebra system for computational discrete algebra with particular emphasis on computational group theory.|https://www.gap-system.org/|{{Pkg|gap}}}}
* {{App|[[Maple]]|Famous commercial CAS. Often used in education.|https://www.maplesoft.com/products/maple/|{{AUR|maple2024}}}}
* {{App|Mathics|A free CAS for symbolic mathematical computations which uses [[Python]] as its main language. It aims at achieving a Mathematica-compatible syntax and functions. It relies mostly on Sympy for most mathematical tasks and, optionally, Sage for more advanced functionality.|https://mathics.github.io/|{{AUR|mathics}}}}
* {{App|[[Wikipedia:Mathomatic|Mathomatic]]|General purpose Computer Algebra System written in C.|https://github.com/mfillpot/mathomatic|{{AUR|mathomatic}}}}
* {{App|[[Wikipedia:Maxima (software)|Maxima]]|[[Wikipedia:Maple (software)|Maple]]/[[Wikipedia:Wolfram Mathematica|Mathematica]]-like computer algebra system.|https://maxima.sourceforge.net/|{{Pkg|maxima}}}}
* {{App|[[Wikipedia:PARI/GP|PARI/GP]]|Computer algebra system designed for fast computations in number theory.|https://pari.math.u-bordeaux.fr/|{{Pkg|pari}}}}
* {{App|[[Wikipedia:Singular (software)|Singular]]|Computer algebra system for polynomial computations, with special emphasis on commutative and non-commutative algebra, algebraic geometry, and singularity theory.|https://www.singular.uni-kl.de/|{{Pkg|singular}}}}
* {{App|wxMaxima|Graphical user interface for Maxima being a powerful computer algebra system.|https://andrejv.github.io/wxmaxima/|{{AUR|wxmaxima}}}}
* {{App|[[Wikipedia:Xcas|Xcas]]|User interface to Giac, a free, basic computer algebra system.|https://www-fourier.ujf-grenoble.fr/~parisse/giac.html{{Dead link|2025|11|17|status=domain name not resolved}}|{{Pkg|giac}}}}

=== Visualization of networks/graphs ===

* {{App|Glue|Linked data visualizations across multiple files.|http://glueviz.org/|{{AUR|glueviz}}}}
* {{App|[[Graphviz]]|The established tool for displaying smallish graphs in 2D.|https://www.graphviz.org|{{Pkg|graphviz}}}}

=== Scientific or technical computing ===

See also [[Wikipedia:Comparison of numerical analysis software]].

* {{App|[[Wikipedia:Cadabra (computer program)|Cadabra]]|A field-theory motivated approach to computer algebra.|https://cadabra.science/|{{AUR|cadabra2}}}}
* {{App|[[Wikipedia:Cantor (software)|Cantor]]|Application that lets you use your favorite mathematical applications from within a nice KDE-integrated Worksheet Interface. Part of {{Grp|kde-education}}.|https://cantor.kde.org/|{{Pkg|cantor}}}}
* {{App|[[Wikipedia:FFTW|FFTW]]|A [[Wikipedia:Fast_Fourier_transform|Fast Fourier Transform]] library for computing discrete Fourier transforms. Used for a wide variety of numerical applications, which includes spectral methods.|https://www.fftw.org/ |{{Pkg|fftw}}}}
* {{App|[[Wikipedia:FreeMat|FreeMat]]|Matlab-like program that supports many of its functions and features a codeless interface to external C, C++, and Fortran code, further parallel distributed algorithm development (via MPI), and 3D visualization capabilities.|https://freemat.sourceforge.net/|{{AUR|freemat}}}}
* {{App|[[Wikipedia:GeoGebra|GeoGebra]]|Dynamic mathematics software with interactive graphics, algebra and spreadsheet|https://www.geogebra.org/|{{Pkg|geogebra}}}}
* {{App|[[Wikipedia:Julia (programming language)|Julia]]|High-level, high-performance dynamic language for technical computing.|https://julialang.org/|{{Pkg|julia}}}}
* {{App|[[Wikipedia:Kig (software)|Kig]]|Application for Interactive Geometry. Part of {{Grp|kde-education}}.|https://apps.kde.org/kig/|{{Pkg|kig}}}}
* {{App|[[Wikipedia:matplotlib|matplotlib (PyLab)]]|Collection of Python modules (pyplot, numpy, etc.) used for scientific calculations.|https://www.scipy.org/|{{Pkg|python-matplotlib}}}}
* {{App|[[Octave]]|[[MATLAB]]-like language and interface for numerical computations.|https://www.gnu.org/software/octave/ |{{Pkg|octave}}}}
* {{App|[[SageMath]]|Mathematics software system, that combines many existing open-source packages into a common Python interface. Alternative to Magma, Maple, Mathematica and Matlab.|https://www.sagemath.org/|{{Pkg|sagemath}}}}
* {{App|[[Wikipedia:Scilab|Scilab]]|Matlab alternative used for numerical computations. Its syntax is not equivalent to that of Matlab, but it can be easily converted.|https://www.scilab.org/|{{AUR|scilab}}}}

=== Statistics ===

See also [[Wikipedia:Comparison of statistical packages]].

* {{App|[[Wikipedia:gretl|gretl]]|A cross-platform software package for econometric analysis, written in the C programming language.|https://gretl.sourceforge.net/|{{AUR|gretl}}}}
* {{App|[[Wikipedia:Just another Gibbs sampler|JAGS]] (Just another Gibbs sampler)|Cross-platform program for analysis of Bayesian hierarchical models using Markov Chain Monte Carlo (MCMC) simulation.|https://mcmc-jags.sourceforge.net/|{{AUR|jags}}}}
* {{App|[[Wikipedia:PSPP|PSPP]]|Free SPSS implementation.|https://www.gnu.org/software/pspp/|{{AUR|pspp}}}}
* {{App|[[Wikipedia:Pandas_(software)|Python Data Analysis Library (pandas)]]| Providing high-performance, easy-to-use data structures and data analysis tools with Python programming language.|https://pandas.pydata.org/|{{Pkg|python-pandas}}}}
* {{App|[[R]]|Software environment for statistical computing and graphics.|https://cran.r-project.org/|{{Pkg|r}}}}
* {{App|[[Wikipedia:RKWard|RKWard]]|Frontend for the statistical language R.|https://rkward.kde.org/|{{Pkg|rkward}}}}
* {{App|[[Wikipedia:RStudio|RStudio]]|A powerful and productive IDE for R written in Qt.|https://www.rstudio.com/|{{AUR|rstudio-desktop}}}}

=== Data analysis and plotting ===

See also [[Wikipedia:List of information graphics software]].

* {{App|AlphaPlot|Application for scientific data analysis and visualization, fork of [[Wikipedia:SciDAVis|SciDAVis]] / QtiPlot.|https://alphaplot.sourceforge.io/|{{AUR|alphaplot}}}}
* {{App|DataWarrior|Open-source data visualization and analysis program with embedded chemical intelligence.|https://openmolecules.org/datawarrior/|{{AUR|datawarrior}}}}
* {{App|Engauge Digitizer|Extracts data points from images of graphs.|https://markummitchell.github.io/engauge-digitizer/{{Dead link|2025|03|15|status=404}}|{{AUR|engauge}}}}
* {{App|[[Wikipedia:Fityk|Fityk]]|Curve fitting and data analysis application, predominantly used to fit analytical, bell-shaped functions to experimental data.|https://fityk.nieto.pl/|{{AUR|fityk}}}}
* {{App|[[Wikipedia:gnuplot|Gnuplot]]|Command-line program that can generate 2D and 3D plots of functions, data, and data fits.|http://www.gnuplot.info/|{{Pkg|gnuplot}}}}
* {{App|[[Wikipedia:Grace (plotting tool)|Grace]]|WYSIWYG 2D graph plotting tool.|https://plasma-gate.weizmann.ac.il/Grace/|{{AUR|grace}}, {{AUR|qtgrace}}, {{AUR|gracegtk}}}}
* {{App|Graphs|Tool to plot and manipulate data.|https://apps.gnome.org/Graphs/|{{Pkg|graphs}}}}
* {{App|[[Wikipedia:KmPlot|KmPlot]]|Program to draw graphs, their integrals or derivatives. Part of {{Grp|kde-education}}.|https://apps.kde.org/kmplot/|{{Pkg|kmplot}}}}
* {{App|[[Wikipedia:kst (software)|kst]]|Real-time data viewer.|https://kst-plot.kde.org/|{{AUR|kst}}}}
* {{App|[[Wikipedia:LabPlot|LabPlot]]|Free software data analysis and visualization application, similar to SciDAVis.|https://labplot.org/|{{Pkg|labplot}}}}
* {{App|OVITO (Open Visualization Tool)|Scientific data visualization and analysis solution for particle-based simulations.|https://ovito.org/|{{AUR|ovito}}}}
* {{App|Plots|A graph plotting application for GNOME.|https://github.com/alexhuntley/Plots|{{AUR|plots}}}}
* {{App|Rocs|Graph Theory IDE for everybody interested in designing and analyzing graph algorithms (e.g., lecturers, students, researchers). Part of {{Grp|kde-education}}.|https://apps.kde.org/rocs/|{{Pkg|rocs}}}}
* {{App|[[Wikipedia:ROOT|ROOT]]|Data analysis program and library (originally for particle physics) developed by CERN.|https://root.cern.ch/|{{Pkg|root}}}}
* {{App|Snakemake|Python-based language and execution environment for GNU Make-like workflows.|https://snakemake.github.io/|{{AUR|snakemake}}}}

See also [[List of applications/Documents#Spreadsheets]].

=== Proof assistants ===

See also [[Wikipedia:Proof assistant]].

* {{App|[[Wikipedia:Agda (programming language)|Agda]]|Dependently typed functional programming language and proof assistant. It is an interactive system for writing and checking proofs.|https://wiki.portal.chalmers.se/agda/|{{Pkg|agda}}}}
* {{App|[[Wikipedia:Isabelle (proof assistant)|Isabelle]]|Generic proof assistant that allows mathematical formulas to be expressed in a formal language and provides tools for proving those formulas in a logical calculus.|https://www.cl.cam.ac.uk/research/hvg/Isabelle/|{{AUR|isabelle}}}}
* {{App|[[Lean]]|Proof assistant developed principally by Leonardo de Moura at Microsoft Research, used in conjunction with the Lean mathematical library.|https://leanprover-community.github.io/|{{AUR|lean-community}}}}
* {{App|[[Wikipedia:Rocq|Rocq]]|Formal proof management system. It provides a formal language to write mathematical definitions, executable algorithms and theorems together with an environment for semi-interactive development of machine-checked proofs.|https://coq.inria.fr/|CLI: {{Pkg|rocq}}, GUI: {{Pkg|rocqide}} }}

== Physics ==

=== Tools ===

* {{App|Geiger Counter Logger|Is a lightweight daemon running in the background and constantly reporting your Geiger counter readings to various radiation monitoring websites|https://www.dateihal.de/cms/gclog|{{AUR|gclog}}}}
* {{App|GWtool|Simple tools for working with gravitational waves|https://gwtool.sourceforge.net/|{{AUR|gwtool}}}}
* {{App|InterSpec|spectral radiation analysis software|https://sandialabs.github.io/InterSpec/|{{AUR|interspec-bin}}}}
* {{App|JaxoDraw|A particle physics program for drawing Feynman diagrams.|https://jaxodraw.sourceforge.io/|{{AUR|jaxodraw}}}}
* {{App|Libint|A high-performance library for computing Gaussian integrals in quantum mechanics|https://github.com/evaleev/libint|{{AUR|libint2}}}}
* {{App|Pysolar|Collection of Python libraries for simulating the irradiation of any point on earth by the sun. It includes code for extremely precise ephemeris calculations.|https://pysolar.org/|{{AUR|python-pysolar}}}}
* {{App|Silx|A collection of Python packages for data analysis at synchrotron radiation facilities.|http://www.silx.org/|{{AUR|python-silx}}}}

=== Physics simulation ===

* {{App|[[Wikipedia:Calculix|Calculix]]|A three-dimensional structural finite element program.|https://www.calculix.de/|{{AUR|calculix-ccx}}}}
* {{App|DFTB+|A quantum mechanical simulation software package based on the DFTB method|https://dftbplus.org/|{{AUR|dftbplus}}}}
* {{App|[[Wikipedia:Elmer_FEM_solver|Elmer_FEM_solver]]|Finite element analysis (FEA/FEM) software for multiphysics problems. Includes models for fluid dynamics, structural mechanics, electromagnetics, heat transfer, and acoustics.|https://www.csc.fi/web/elmer https://www.elmerfem.org/|{{AUR|elmerfem}}}}
* {{App|[[Wikipedia:FEniCS Project|FEniCS]]|An open-source computing platform for solving partial differential equations, enabling users to quickly translate scientific models into efficient finite element code with the high-level Python and C++ interfaces that scale across platforms ranging from laptops to high-performance clusters.|https://fenicsproject.org/|{{AUR|dolfin}}, {{AUR|python-dolfin}}}}
* {{App|Finesse|Frequency domain INterfErometer Simulation SoftwarE|https://www.gwoptics.org/finesse/|{{AUR|finesse}}}}
* {{App|Geant4|A simulation toolkit for particle physics interactions.|https://geant4.web.cern.ch/|{{AUR|geant4}}}}
* {{App|Herwig|Herwig is a multi-purpose particle physics event generator.|https://herwig.hepforge.org/|{{AUR|herwig}}}}
* {{App|Netgen/NGSolve|A high performance multiphysics finite element software, with a flexible Python interface to implement new physical equations and solution algorithms easily.|https://ngsolve.org/|{{AUR|netgen-git}}, {{AUR|ngsolve-git}}}}
* {{App|[[Wikipedia:Gmsh|ONELAB/Gmsh]]|An open-source, lightweight interface to finite element software, by default containing the mesh generator Gmsh, the finite element solver GetDP and the optimization library conveks.|http://onelab.info/ https://getdp.info/ https://gmsh.info/ http://onelab.info/conveks/|{{AUR|gmsh}}, {{AUR|getdp}}}}
* {{App|[[Wikipedia:OpenFOAM|OpenFOAM]]|Software package and toolkit for computational fluid dynamics (CFD).|https://openfoam.org/|{{AUR|openfoam-org}}}}
* {{App|OpenLoops 2|A particle physics package for the fast numerical evaluation of tree and one-loop matrix elements.|https://openloops.hepforge.org/|{{AUR|openloops}}}}
* {{App|QuTiP|QuTiP is open-source software for simulating the dynamics of open quantum systems|https://qutip.org/|{{AUR|python-qutip}}}}
* {{App|Rivet|A particle physics package for data analysis and validation of Monte Carlo event generators|https://rivet.hepforge.org/|{{AUR|rivet}}}}
* {{App|Sherpa|A particle physics package for Monte Carlo simulation of collider events.|https://sherpa-team.gitlab.io/|{{AUR|sherpa}}}}
* {{App|Speaq|Tools for Nuclear Magnetic Resonance (NMR) Spectra Alignment, Peak Based Processing, Quantitative Analysis and Visualizations|https://cran.r-project.org/web/packages/speaq/index.html|{{AUR|r-speaq}}}}
* {{App|[[Wikipedia:Step (software)|Step]]|Two-dimensional physics simulation engine. Part of {{Grp|kde-education}}.|https://apps.kde.org/step/|{{Pkg|step}}}}
* {{App|[[Wikipedia:SWMM|SWMM]]|Storm Water Management Model is a dynamic rainfall-runoff-subsurface runoff simulation model used for simulation of the surface/subsurface hydrology quantity and quality.|https://www.epa.gov/|{{AUR|swmm5-git}}}}
* {{App|VESTA|3D visualization program for structural models, volumetric data such as electron/nuclear densities, and crystal morphologies.|https://jp-minerals.org/vesta/en/|{{AUR|vesta}}}}
* {{App|WHIZARD|The Generator of Monte Carlo Event Generators for Tevatron, LHC, ILC, CLIC, CEPC, FCC-ee, FCC-hh, SppC and other High Energy Physics Experiments.|https://whizard.hepforge.org/|{{AUR|whizard}}}}

=== Unit conversion ===

* {{App|ConvertAll|Unit conversion application that allows one to combine units in any way (e.g. inches per decade), even if it does not make sense.|https://convertall.bellz.org/|{{AUR|convertall}}}}
* {{App|[https://printfn.github.io/fend/ fend]|An arbitrary-precision unit-aware calculator.|https://github.com/printfn/fend|{{AUR|fend}}}}
* {{App|Gonvert|Conversion utility that allows conversion between many units like CGS, Ancient, Imperial with many categories like length, mass, numbers, etc.|http://www.unihedron.com/projects/gonvert/|{{AUR|gonvert}}}}
* {{App|Numbat|A statically typed programming language for scientific computations with first class support for physical dimensions and units.|https://numbat.dev|{{Pkg|numbat}}}}
* {{App|Rink|A unit conversion tool and library written in rust. It can be used for physics and engineering calculations, as well as dimensionality analysis.|https://rinkcalc.app/about|{{Pkg|rink}}}}
* {{App|UDUNITS|A tool for calculations of physical quantities.|https://www.unidata.ucar.edu/software/udunits/|{{AUR|udunits}}}}
* {{App|[[Wikipedia:GNU Units|Units]]|Command-line unit converter and calculator that can handle multiplicative scale changes, nonlinear conversions such as Fahrenheit to Celsius or wire gauge and others.|https://www.gnu.org/software/units/|{{AUR|units}}}}

== Chemistry ==

* {{App|ChemCalc|A chemical calculator that calculates the amount of reagents to use when making solutions.|https://github.com/Chris-Baba/ChemCalc/tree/main|{{AUR|chemcalc}}}}

* {{App|TCcalc|A basic CLI [[Wikipedia:Chemical thermodynamics|Chemical thermodynamics]] calculator. Allows for calculating delta S and H of reactions/state changes.|https://gitlab.com/calcs1/tccalc/|{{AUR|tccalc}}}}

=== Molecules ===

==== Viewers ====

See also [[Wikipedia:List of molecular graphics systems]].

* {{App|[[Wikipedia:Avogadro_(software)|Avogadro]]|Editor, viewer and simulator for 3D molecule structures (also supports downloading files from the [[Wikipedia:Protein Data Bank|Protein Data Bank]]).|https://avogadro.cc/|{{AUR|avogadroapp}}}}
* {{App|[[Wikipedia:Ghemical|Ghemical]]|Computational chemistry software package used to edit, view and simulate molecular structures.|http://bioinformatics.org/ghemical/ghemical/index.html|{{AUR|ghemical}}}}
* {{App|[[Wikipedia:PyMOL|PyMOL]]|Open-source molecular visualization system that can produce high quality 3D images of small molecules and biological macromolecules, such as proteins.|https://pymol.org/|{{Pkg|pymol}}}}
* {{App|[[Wikipedia:UCSF Chimera|UCSF Chimera]]|Extensible molecular modeling system.|https://rbvi.ucsf.edu/chimera/|{{AUR|ucsf-chimera}}}}
* {{App|UCSF ChimeraX|Next-generation molecular visualization program, following UCSF Chimera.|https://rbvi.ucsf.edu/chimerax/|{{AUR|chimerax}}}}
* {{App|[[Wikipedia:Visual Molecular Dynamics|VMD]]|VMD is a molecular visualization program for displaying, animating, and analyzing large biomolecular systems using 3-D graphics and built-in scripting.|https://www.ks.uiuc.edu/Research/vmd/|{{AUR|vmd}}}}
* {{App|wxMacMolPlt|An open-source GUI for preparing, submitting and visualizing input and output for the GAMESS quantum chemistry package.|https://brettbode.github.io/wxmacmolplt/|{{AUR|wxmacmolplt}}}}

==== Drawing ====

* {{App|Chemtool|GTK-based program for drawing chemical structural formulas.|http://ruby.chemie.uni-freiburg.de/~martin/chemtool/chemtool.html|{{AUR|chemtool}}}}

==== Modeling ====

* {{App|[[Wikipedia:AMBER|AmberTools]]|AmberTools consists of several independently developed packages that work well by themselves, and with Amber18 itself. The suite can also be used to carry out complete molecular dynamics simulations, with either explicit water or generalized Born solvent models.|https://ambermd.org/AmberTools.php|{{AUR|ambertools}}}}
* {{App|[[Wikipedia:APBS (software)|APBS]]|Electrostatic and solvation properties for complex molecules.|https://www.poissonboltzmann.org/|{{AUR|apbs}}}}
* {{App|[[Wikipedia:COPASI|COPASI]]|COmplex PAthway SImulator for analysis of biochemical networks and their dynamics.|https://copasi.org/|{{AUR|copasi-bin}}}}
* {{App|[[Wikipedia:CP2K|CP2K]]|A quantum chemistry and solid state physics software package.|https://www.cp2k.org/|{{AUR|cp2k}}}}
* {{App|Fpocket|Fpocket is a very fast open source protein pocket detection algorithm based on Voronoi tessellation.|https://github.com/Discngine/fpocket|{{AUR|fpocket-git}}}}
* {{App|[[GROMACS]] (GROningen MAchine for Chemical Simulations)|Versatile package to perform molecular dynamics, i.e. simulate the Newtonian equations of motion for systems with hundreds to millions of particles.|https://www.gromacs.org|{{AUR|gromacs}}}}
* {{App|[[Wikipedia:LAMMPS|LAMMPS]]|Large-scale Atomic/Molecular Massively Parallel Simulator.|https://www.lammps.org/|{{AUR|lammps}}}}
* {{App|[[Wikipedia:MODELLER|MODELLER]]|3D structure homology modeller.|https://salilab.org/modeller/|{{AUR|modeller}}}}
* {{App|[[Wikipedia:NAMD|NAMD]]|NAMD is a parallel molecular dynamics code designed for high-performance simulation of large biomolecular systems.|https://www.ks.uiuc.edu/Research/namd/|{{AUR|namd}}}}
* {{App|[[Wikipedia:NWChem|NWChem]]|Ab initio computational chemistry software package.|https://nwchemgit.github.io/|{{AUR|nwchem}}}}
* {{App|[[Wikipedia:Open Babel|Open Babel]]|A library designed to interconvert between many file formats used in molecular modeling and computational chemistry.|https://openbabel.org/|{{pkg|openbabel}}}}
* {{App|[[Wikipedia:ORCA (quantum chemistry program)|ORCA]]|ORCA is an ab initio, DFT, and semi-empirical SCF-MO package.|https://orcaforum.kofo.mpg.de/app.php/portal|{{AUR|orcaqm}}}}
* {{App|[[Wikipedia:APBS (software)|PDB2PQR]]|Electrostatic and solvation properties for complex molecules.|https://www.poissonboltzmann.org/|{{AUR|python-pdb2pqr}}}}
* {{App|[[Wikipedia:PLUMED|PLUMED]]|An open source plugin for free energy calculations in molecular systems which works together with some of the most popular molecular dynamics engines.|https://www.plumed.org/|{{AUR|plumed}}}}
* {{App|PSI4|Open-source quantum chemistry|https://psicode.org/|{{AUR|psi4-git}}}}
* {{App|[[Wikipedia:Quantum ESPRESSO|Quantum ESPRESSO]]|Integrated suite of applications for electronic-structure calculations and materials modeling at nanoscale. It is based on density-functional theory, plane waves, and pseudopotentials (both norm-conserving and ultrasoft).|https://www.quantum-espresso.org/|{{AUR|quantum-espresso}}}}
* {{App|[[Wikipedia:RDKit|RDKit]]|A collection of cheminformatics and machine-learning software written in C++ and Python.|https://www.rdkit.org/|{{Pkg|rdkit}}}}
* {{App|[[Wikipedia:RDock|rDock]]|A fast, versatile and open-source program for docking ligands to proteins and nucleic acids.|https://rdock.sourceforge.net/|{{AUR|rdock}}}}
* {{App|[[Wikipedia:AutoDock|smina]]|Smina is a fork of Autodock Vina that focuses on improving scoring and minimization.|https://sourceforge.net/projects/smina/|{{AUR|smina-bin}}}}

=== Simulation analysis ===

* {{App|mdanalysis|An object-oriented python toolkit to analyze molecular dynamics trajectories in many popular formats.|https://www.mdanalysis.org|{{AUR|python-mdanalysis}}}}
* {{App|MDTraj|A modern, open library for the analysis of molecular dynamics trajectories.|https://github.com/mdtraj/mdtraj|{{AUR|python-mdtraj}}}}
* {{App|xdrfile|Allows to read GROMACS [https://manual.gromacs.org/current/reference-manual/file-formats.html#trr trr] and [https://manual.gromacs.org/current/reference-manual/file-formats.html#xtc xtc] files and also to convert from one format to another.|https://manual.gromacs.org/current/reference-manual/file-formats.html#xdr|{{AUR|xdrfile}}}}

=== Periodic table ===

* {{App|eperiodique|A simple Periodic Table Of Elements viewer using the EFL.|https://eperiodique.sourceforge.net/|{{AUR|eperiodique}}}}
* {{App|gElemental|Periodic table of the elements with additional information.|https://freshmeat.sourceforge.net/projects/gelemental|{{AUR|gelemental}}}}
* {{App|Kalzium|Periodic table of the elements with molecule editor and equation solver. Part of {{Grp|kde-education}}.|https://apps.kde.org/kalzium/|{{Pkg|kalzium}}}}

== Earth science ==

=== Climatology ===

* {{App|Climate Data Operators|Command line tool to manipulate and analyse Climate model Data. Supported data formats are GRIB, netCDF, SERVICE, EXTRA and IEG.|https://code.mpimet.mpg.de/projects/cdo|{{AUR|cdo}}}}

=== Geography ===

==== Map viewers ====

* {{App|Cruiser|Map and navigation application using offline vector maps|https://wiki.openstreetmap.org/wiki/Cruiser|{{AUR|cruiser}}}}
* {{App|GNOME Maps|A simple map client for GNOME with navigation and GNSS features (adapted to Linux Mobile). Part of {{Grp|gnome}}.|https://apps.gnome.org/Maps/|{{Pkg|gnome-maps}}}}
* {{App|kosmindoormap|Indoor cartography, levels by levels of buildings, mainly Train station, and Airport buildings. Based on OSM data.|https://www.kde.org|{{Pkg|kosmindoormap}}}}
* {{App|MapSCII|Console Map Viewer.|https://github.com/rastapasta/mapscii|{{AUR|nodejs-mapscii}}}}
* {{App|Mapton|Extensible desktop map and globe application written in Java.|https://mapton.org/|{{AUR|mapton}}}}
* {{App|[[Wikipedia:Marble (software)|Marble]]|Virtual Globe and World Atlas that can be used to learn more about the Earth. Part of {{Grp|kde-education}}.|https://marble.kde.org/|KDE: {{Pkg|marble}}, Qt: {{Pkg|marble-qt}}}}
* {{App|Marble Behaim|Viewer for the oldest existent globe of the Earth made by Martin Behaim and collaborators around 1492.|https://marble.kde.org/|{{Pkg|marble-behaim}}}}
* {{App|Marble Maps|Vector and GNSS navigation system, with Modular turn-by-turn car, foot, and bike navigation system (adapted to Linux Mobile).|https://marble.kde.org/|{{Pkg|marble-maps}}}}
* {{App|OffRoad|Offline vector map display ported from OsmAnd.|https://sourceforge.net/projects/offroadosm/|{{Pkg|offroad}}}}
* {{App|Organic Maps|GNSS based navigation, with vector off-line and routing features, and turn by turn routing|https://github.com/organicmaps/organicmaps|{{AUR|organicmaps-git}}}}
* {{App|OSMin|GNSS based navigation, with vector off-line and routing features, and turn by turn car, foot, bike, and hiking routing (adapted to Linux Mobile).|https://github.com/janbar/osmin|{{AUR|osmin}}}}
* {{App|Pure Maps|Display vector and raster maps, places, routes, etc.|https://rinigus.github.io/pure-maps/|{{AUR|pure-maps}}}}

==== Navigation and routing ====

* {{App|KTrip|Public transport assistant for mobile devices. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/ktrip/|{{Pkg|ktrip}}}}
* {{App|Railway|Lets you look up travel information for many different railways, all without needing to navigate through different websites.|https://apps.gnome.org/DieBahn/|{{Pkg|railway}}}}

==== Positioning and tracking ====

* {{App|BT747|The swiss army knife for MTK GPS dataloggers.|https://sourceforge.net/projects/bt747/|{{Pkg|bt747}}}}
* {{App|FoxtrotGPS|Lightweight and fast mapping application.|https://www.foxtrotgps.org/|{{AUR|foxtrotgps}}}}
* {{App|Gebabbel|Alternative GUI for GPSBabel.|https://gebabbel.sourceforge.net/|{{AUR|gebabbel}}}}
* {{App|Gpredict|Real-time satellite tracking and orbit prediction application.|https://gpredict.oz9aec.net/|{{AUR|gpredict}}}}
* {{App|GPSBabel|Reads, writes, and manipulates GPS waypoints, tracks, routes in a variety of formats.|https://www.gpsbabel.org/|{{Pkg|gpsbabel}}}}
* {{App|[[Wikipedia:gpsd|gpsd]]|Service daemon that monitors one or more GPSes or AIS receivers attached to a host computer through serial or USB ports, making all data on the location/course/velocity of the sensors available to be queried on TCP port 2947 of the host computer.|http://catb.org/gpsd/|{{Pkg|gpsd}}}}
* {{App|GpsPrune|View, edit and convert coordinate data from GPS systems.|https://activityworkshop.net/software/gpsprune/|{{Pkg|gpsprune}}}}
* {{App|GPXSee|GPS log file viewer and analyzer.|https://www.gpxsee.org/|{{Pkg|gpxsee}}}}
* {{App|GPX Viewer|Simple tool to visualize tracks and waypoints stored in a gpx file.|https://blog.sarine.nl/tag/gpxviewer/|{{AUR|gpx-viewer}}}}
* {{App|Navit|Modular turn-by-turn car navigation system.|https://www.navit-project.org/|{{AUR|navit}}}}
* {{App|PreviSat|PreviSat is a satellite tracking software for observing purposes|https://previsat.sourceforge.net/|{{AUR|previsat}}}}
* {{App|QMapShack|Plan your next outdoor trip.|https://github.com/Maproom/qmapshack/|{{Pkg|qmapshack}}}}
* {{App|Satellite|Displays Global Navigation Satellite System (GNSS: GPS, Galileo, Glonass etc.) information obtained from NMEA sources and saves your tracks|https://codeberg.org/tpikonen/satellite|{{AUR|satellite-gtk}}}}
* {{App|[[Wikipedia:Subsurface (software)|Subsurface]]|Diving logbook to keep track of your dives by logging dive locations (with GPS coordinates), weights and exposure protection used, divemasters and dive buddies, etc.|https://subsurface-divelog.org/|{{AUR|subsurface-git}}}}
* {{App|Viking|GTK 2 application to manage GPS data.|https://sourceforge.net/projects/viking/|{{Pkg|viking}}}}

==== Map editors ====

* {{App|JOSM|Main editor for OpenStreetMap written in Java.|https://josm.openstreetmap.de/|{{Pkg|josm}}}}
* {{App|Merkaartor|OpenStreetMap editor.|https://merkaartor.be/|{{Pkg|merkaartor}}}}
* {{App|OpenOrienteering Mapper|Orienteering mapmaking program.|https://www.openorienteering.org/apps/mapper/|{{AUR|openorienteering-mapper}}}}
* {{App|Phyghtmap|Generate OSM contour lines from NASA SRTM data|http://katze.tfiu.de/projects/phyghtmap/|{{AUR|phyghtmap}}}}

==== Geospatial data analysis and GIS ====

* {{App|GeoDa|A tool for spatial data analysis.|https://geodacenter.github.io/|{{AUR|geoda-bin}}}}
* {{App|[[Wikipedia:GRASS GIS|GRASS GIS]]|Geospatial data management and analysis, image processing, graphics/maps production, spatial modeling and visualization.|https://grass.osgeo.org/|{{AUR|grass}}}}
* {{App|[[Wikipedia:gvSIG|gvSIG]]|vSIG is a geographic information system (GIS), that is, a desktop application designed for capturing, storing, handling, analyzing and deploying any kind of referenced geographic information in order to solve complex management and planning problems.|http://www.gvsig.com/en| {{AUR|gvsig-desktop-bin}}}}
* {{App|Panoply|NetCDF, HDF and GRIB Data Viewer by NASA GISS|https://www.giss.nasa.gov/tools/panoply/|{{AUR|panoply}}}}
* {{App|[[Wikipedia:QGIS|QGIS]]| [[Wikipedia:Geographic Information System|Geographic Information System (GIS)]] that supports vector, raster & database formats.|https://qgis.org/|{{Pkg|qgis}}}}
* {{App|SAGA|A Geographic Information System (GIS) software with immense capabilities for geodata processing and analysis.|https://saga-gis.sourceforge.io/en/index.html|{{AUR|saga-gis}}}}
* {{App|WCSTools|A package of programs for setting and using the world coordinate systems|http://tdc-www.harvard.edu/wcstools/|{{AUR|wcstools}}}}

=== Geology ===

* {{App|CDI|Is a general purpose C-library with an additional Fortran interface for file IO in the geoscience area.|https://code.mpimet.mpg.de/projects/cdi|{{AUR|cdi}}}}
* {{App|EnhancedVolcano|Publication-ready volcano plots with enhanced colouring and labeling.|https://bioconductor.org/packages/release/bioc/html/EnhancedVolcano.html|{{AUR|r-enhancedvolcano}}}}
* {{App|GEOmap|Topographic and Geologic Mapping.|https://cran.r-project.org/web/packages/GEOmap/index.html|{{AUR|r-geomap}}}}
* {{App|GPlates|Is a plate tectonics program. Manipulate reconstructions of geological and paleogeographic features through geological time.|https://www.gplates.org/|{{AUR|gplates}}}}
* {{App|Gstat|Spatial and Spatio-Temporal Geostatistical Modelling, Prediction and Simulation|https://cran.r-project.org/web/packages/gstat/index.html|{{AUR|r-gstat}}}}
* {{App|Madagascar|Multidimensional data analysis and reproducible computational experiments.|https://www.reproducibility.org|{{AUR|madagascar}}}}
* {{App|SeisComP|A seismological software for data acquisition, processing, distribution and interactive analysis.|https://github.com/SeisComP/seiscomp|{{AUR|seiscomp}}}}
* {{App|Seismic Un*x|A seismic processing and research environment developed at the Center for Wave Phenomena, Colorado School of Mines|https://wiki.seismic-unix.org/start|{{AUR|seismic-unix}}}}
* {{App|TauP|A seismic travel time calculator.|https://github.com/crotwell/TauP|{{AUR|taup-git}}}}

=== Oceanography ===

* {{App|Cmocean|Colormap setup for standardizing commonly-plotting oceanographic variables.|https://github.com/matplotlib/cmocean|{{AUR|python-cmocean}}}}

=== Weather status ===

* {{App|Gis Weather|Customizable weather forecast desktop widget.|https://sourceforge.net/projects/gis-weather/|{{AUR|gis-weather}}}}
* {{App|GNOME Weather|Small application for GNOME that allows you to monitor the current weather conditions for your city, or anywhere in the world, and to access updated forecasts provided by various internet services. Part of {{Grp|gnome}}.|https://apps.gnome.org/Weather/|{{Pkg|gnome-weather}}}}
* {{App|KWeather|A convergent weather application for Plasma. Part of {{Grp|kde-utilities}}.|https://apps.kde.org/kweather/|{{Pkg|kweather}}}}
* {{App|meteo-qt|System tray application for weather status information.|https://github.com/dglent/meteo-qt|{{AUR|meteo-qt}}}}
* {{App|wego|A terminal weather application.|https://tylerwolf35.github.io/wego{{Dead link|2025|08|15|status=404}}|{{AUR|wego}}}}
* {{App|wttr|A simple console application to check the weather, using data from https://wttr.in|https://github.com/AmirrezaFiroozi/wttr|{{AUR|wttr-bin}}}}
* {{App|Xfce Weather Panel Plugin|Weather forecast plugin for the Xfce4 panel.|https://goodies.xfce.org/projects/panel-plugins/xfce4-weather-plugin|{{Pkg|xfce4-weather-plugin}}}}

== Astronomy ==

=== Astrometrical and image processing software ===

See also [[Wikipedia:List of astrometric solvers]].

* {{App|APTS|Set of tools for automatic astrophotography images acquisition and processing|https://github.com/pozar87/apts|{{AUR|python-apts}}}}
* {{App|Astap|Astrometric (plate) solver, stacking of images, photometry and FITS viewer|https://www.hnsky.org/astap.htm|{{AUR|astap-bin-qt5}}}}
* {{App|AstroCrop|Astronomical image preprocessing tool|https://www.astrodmx-capture.org.uk/astrocrop/|{{AUR|astrocrop}}}}
* {{App|AstroImageJ|ImageJ for Astronomy|https://www.astro.louisville.edu/software/astroimagej/|{{AUR|astroimagej}}}}
* {{App|Astrometry.net|Automatic recognition of astronomical images|https://astrometry.net/|{{AUR|astrometry.net}}}}
* {{App|AudeLA|AudeLA is a TCL extension aimed at providing amateur astronomers with image processing, telescope controling, ccd camera driving, and various astronomical algorithms|https://sourceforge.net/projects/audela/|{{AUR|audela-bin}},{{AUR|audela-svn}}}}
* {{App|CARTA|Cube Analysis and Rendering Tool for Astronomy|https://cartavis.org/|{{AUR|carta-appimage}}}}
* {{App|FITSH|a software package for astronomical image processing|https://fitsh.net/|{{AUR|fitsh}}}}
* {{App|GIMP Astronomy Plugins|Set of GIMP plugins for astronomical image processing.|http://hennigbuam.de/georg/gimp.html|{{AUR|gimp-plugin-astronomy}}}}
* {{App|Ginga|A viewer for astronomical data FITS (Flexible Image Transport System) files|https://ejeschke.github.io/ginga/|{{AUR|python-ginga}}}}
* {{App|Montage|An astronomical image mosaic engine|http://montage.ipac.caltech.edu/|{{AUR|montage}}}}
* {{App|Munipack|A general astronomical image processing software|http://munipack.physics.muni.cz/|{{AUR|munipack}}, {{AUR|c-munipack}}}}
* {{App|oaCapture|A planetary imaging application using Qt5|https://www.openastroproject.org/oacapture/|{{AUR|oacapture}}}}
* {{App|PlanetarySystemStacker|Produce a sharp image of a planetary system object|https://github.com/Rolf-Hempel/PlanetarySystemStacker|{{AUR|planetarysystemstacker-git}}}}
* {{App|SCAMP|reads SExtractor catalogs and computes astrometric and photometric solutions for any arbitrary sequence of FITS images in a completely automatic way.|https://www.astromatic.net/software/scamp/|{{AUR|astromatic-scamp}}}}
* {{App|SExtractor|Is a program that builds a catalogue of objects from an astronomical image.|https://www.astromatic.net/software/sextractor/|{{AUR|astromatic-sextractor}}}}
* {{App|THELI|THELI is a data processing pipeline for optical, near-infrared and mid-infrared astronomical images|https://github.com/schirmermischa/THELI|{{AUR|theli}}}}

=== Image capture software ===

* {{App|CCDciel|A CCD capture software intended for the amateur astronomer.|https://www.ap-i.net/ccdciel//en/start|{{AUR|ccdciel}}}}
* {{App|FireCapture|The leading planetary capture tool|https://www.firecapture.de/|{{AUR|firecapture}}}}
* {{App|GoQat|Camera acquisition software, especially for QSI cameras, that provides other features such as autoguiding, focusing help and others.|https://canburytech.net/GoQat/|{{AUR|goqat}}}}
* {{App|lin_guider|astronomical autoguiding program|https://sourceforge.net/projects/linguider/|{{AUR|lin-guider}}}}
* {{App|Mrcal|Is a generic toolkit built to solve the calibration and SFM-like problems we encounter at NASA/JPL.|https://mrcal.secretsauce.net/|{{AUR|mrcal}}}}
* {{App|Open PHD Guiding|PHD2 astrophotography autoguiding tool|https://openphdguiding.org/|{{AUR|phd2}}}}
* {{App|SAOImageDS9|SAOImage DS9: Astronomical Data Visualization Application|https://sites.google.com/cfa.harvard.edu/saoimageds9|{{AUR|ds9}}}}
* {{App|[[Wikipedia:Siril (software)|Siril]]|Siril is a software application for astrophotography, which allows pre-processing and processing of images from any type of camera (CCD, planetary camera, webcam etc.)|https://siril.org/|{{AUR|siril}}}}

=== Common libraries ===

* {{App|[[Wikipedia:Astropy|Astropy]]|The Astropy Project is a community effort to develop a common core package for Astronomy in Python and foster an ecosystem of interoperable astronomy packages.|https://www.astropy.org/|{{Pkg|python-astropy}}}}
* {{App|CASA|the Common Astronomy Software Applications package.|https://casa.nrao.edu/|{{AUR|casa6-bin}}}}
* {{App|Casacore|package contains the core libraries of the old AIPS++/CASA package.|https://casacore.github.io/casacore/|{{AUR|casacore}}, {{AUR|python-casacore}}}}
* {{App|CDF|NASA Common Data Format (CDF) library for scientific data management|https://cdf.gsfc.nasa.gov/|{{AUR|cdf-nasa}}}}
* {{App|ERFA|Essential Routines for Fundamental Astronomy|https://github.com/liberfa/erfa|{{pkg|erfa}}}}
* {{App|HEASoft|NASA high energy astrophysics library|https://heasarc.gsfc.nasa.gov/docs/software/lheasoft/|{{AUR|heasoft}}}}
* {{App|libTheSky|Fortran library to compute the positions of celestial bodies and events with great accuracy|https://libthesky.sourceforge.net/|{{AUR|libthesky}}, {{AUR|libthesky-data}}}}
* {{App|Pal|Positional Astronomy Library.|https://github.com/Starlink/pal|{{AUR|starlink-pal}}}}
* {{App|PyEphem|PyEphem provides scientific-grade astronomical computations|https://rhodesmill.org/pyephem/|{{AUR|python-pyephem}}}}
* {{App|SOFA|Set of algorithms and procedures used in fundamental astronomy|http://www.iausofa.org/|{{AUR|sofa}}}}

=== Toolkits ===

* {{App|AstroML|Machine learning, statistics, and data mining for astronomy and astrophysics|https://www.astroml.org/|{{AUR|python-astroml}}}}
* {{App|Exoplanet|exoplanet is a toolkit for probabilistic modeling of time series data in astronomy with a focus on observations of exoplanets|https://github.com/exoplanet-dev/exoplanet|{{AUR|exoplanet-git}}}}
* {{App|Galpy|Galactic Dynamics in python|https://www.galpy.org/|{{AUR|python-galpy}}}}
* {{App|Gammapy|A Python package for gamma-ray astronomy|https://gammapy.org/|{{AUR|python-gammapy}}}}
* {{App|HEALPix|Software for pixelization, hierarchical indexation, synthesis, analysis, and visualization of data on the sphere|https://healpix.jpl.nasa.gov/{{Dead link|2025|11|17|status=domain name not resolved}}|{{AUR|healpix}}}}
* {{App|JHelioviewer|Visualization software for solar image data in space weather context|https://www.jhelioviewer.org/|{{AUR|jhelioviewer}}}}
* {{App|JMARS|Java Mission-planning and Analysis for Remote Sensing.|https://jmars.mars.asu.edu/{{Dead link|2025|08|15|status=SSL error}}|{{AUR|jmars}}}}
* {{App|JSkyCalc|A tool for observing preparation in java|https://caligari.dartmouth.edu/public/downloads/skycalc/|{{AUR|jskycalc}}}}
* {{App|Period04|Period04 is a computer program especially dedicated to the statistical analysis of large astronomical time series containing gaps|https://period04.net/|{{AUR|period04}}}}
* {{App|[[Wikipedia:WorldWide Telescope|Pywwt]]|Is the official toolkit for accessing AAS WorldWide Telescope (WWT) from Python|https://pywwt.readthedocs.io/en/stable/|{{AUR|python-pywwt}}}}
* {{App|RochePlot|Plot the key stages in the evolution of a binary star|https://rocheplot.sourceforge.net/|{{AUR|rocheplot}}}}
* {{App|Skyfield|Elegant astronomy for Python|https://rhodesmill.org/skyfield/|{{AUR|python-skyfield}}}}
* {{App|SolTrack|A free, fast and accurate C/C++ routine to compute the position of the Sun|https://soltrack.sourceforge.net/|{{AUR|soltrack}}}}
* {{App|SPICE|A comprehensive toolkit and api to design, simulate and analyse space missions|https://naif.jpl.nasa.gov/naif/index.html|{{AUR|cspice}}}}
* {{App|STILTS|Starlink Tables Infrastructure Library Tool Set|https://www.star.bris.ac.uk/~mbt/stilts/|{{AUR|stilts}}}}
* {{App|sunclock|An astronomical world map that shows day and night and the Sun and Moon positions|https://www.spinnaker.de/debian/sunclock.html|{{AUR|sunclock}}}}
* {{App|Tempo|Pulsar Timing Software|https://tempo.sourceforge.net/tempo_idx.html|{{AUR|tempo-git}}}}
* {{App|TOPCAT|Tool for OPerations on Catalogues And Tables|https://www.star.bris.ac.uk/~mbt/topcat/|{{AUR|topcat}}}}
* {{App|VaST|VaST is a software tool for finding variable objects on a series of astronomical images|https://scan.sai.msu.ru/vast/|{{AUR|vast-astronomical-git}}}}
* {{App|VStar|VStar is a multi-platform, easy-to-use variable star data visualization and analysis tool that was originally developed as part of the AAVSOs Citizen Sky project|https://www.aavso.org/vstar|{{AUR|vstar-aavso}}}}

=== Calculators and CLI utilities ===

* {{App|astroTools|Command-line tools for astronomy and astrophysics|https://astrotools.sourceforge.net/|{{AUR|astrotools}}}}
* {{App|Gnuastro|Various programs and library functions for the manipulation and analysis of astronomical data|https://www.gnu.org/software/gnuastro/|{{AUR|gnuastro}}}}
* {{App|Kosmorro|A program to calculate the ephemerides|https://kosmorro.space/|{{AUR|kosmorro}}}}
* {{App|Project Pluto|Project Pluto supplies astronomical software, both commercial and freeware, to amateur and professional astronomers|https://www.projectpluto.com/|{{AUR|pluto-lunar-git}}, {{AUR|pluto-sat-code-git}}, {{AUR|pluto-jpl-eph-git}}, {{AUR|pluto-find-orb-git}}}}
* {{App|star-charter|A command-line tool for producing vector-graphics charts of the night sky in SVG, PDF and PNG formats|https://github.com/dcf21/star-charter|{{AUR|star-charter-git}}}}
* {{App|Sunwait|Calculate sunrise/sunset times with civil, nautical, astronomical and custom twilights|https://github.com/risacher/sunwait|{{AUR|sunwait}}}}

=== Management of telescopes and observatories ===

* {{App|GILDAS|Is a collection of state-of-the-art software oriented toward (sub-)millimeter radioastronomical applications (either single-dish or interferometer)|https://www.iram.fr/IRAMFR/GILDAS/|{{AUR|gildas}}}}
* {{App|imSim|software package that simulates the LSST telescope and survey|https://github.com/LSSTDESC/imSim|{{AUR|python-imsim-git}}}}
* {{App|rubin_sim|Scheduler, survey strategy analysis, and other simulation tools for Rubin Observatory|https://github.com/lsst/rubin_sim|{{AUR|python-rubinsim-git}}}}
* {{App|Srt-py|Small Radio Telescope Control Code for Python.|https://github.com/MITHaystack/srt-py|{{AUR|srt-py-git}}}}

=== Simulation ===

* {{App|APSYNSIM|Aperture Synthesis Simulator for Radio Astronomy|https://launchpad.net/apsynsim|{{AUR|apsynsim}}}}
* {{App|FriendlyVRI|Is designed to simulate astronomical observations using linked arrays of radio antennas in a technique called earth rotation aperture synthesis|https://github.com/crpurcell/friendlyVRI|{{AUR|friendlyvri-git}}}}
* {{App|Galaxy2|Is program which simulates the motion of stars under the influence of gravity|https://www.kornelix.net/galaxy2/galaxy2.html|{{AUR|galaxy2}}}}
* {{App|GalSim|Modular galaxy image simulation toolkit|https://github.com/GalSim-developers/GalSim|{{AUR|python-galsim}}}}
* {{App|Pynterferometer|Is a graphical interface designed to demonstrate the techniques of radio interferometry used by telescopes|https://www.jb.man.ac.uk/pynterferometer/index.html|{{AUR|pynterferometer}}}}

=== Space exploration programs ===

* {{App|Cosmographia|Cosmographia is a visualization program rendering the solar system and its bodies in 3D to create a freely navigable map of the solar system|https://naif.jpl.nasa.gov/naif/cosmographia.html|{{AUR|cosmographia-bin}}}}
* {{App|Cosmonium|3D astronomy and space exploration program|https://github.com/cosmonium/cosmonium|{{AUR|cosmonium-bin}}}}
* {{App|OpenSpace|OpenSpace is an open source, non-commercial, and freely available interactive data visualization software designed to visualize the entire known universe and portray our ongoing efforts to investigate the cosmos|https://www.openspaceproject.com/|{{AUR|openspace-git}}}}
* {{App|Our Galaxy|Is a unique app that helps you understand the structural components of the Galaxy and visualize the locations and physical properties of deep sky objects in and around it|https://www.otherwise.com/|{{AUR|ourgalaxy-bin}}}}

=== Planetary and virtual atlas ===

See also [[Wikipedia:Planetarium software]] and [[Wikipedia:List of observatory software]].

* {{App|Aladin|Interactive software sky atlas|http://aladin.u-strasbg.fr/aladin.gml|{{AUR|aladin}}}}
* {{App|astroterm|Terminal-based star map written in C, which displays a star map in real time. Date, time, location and speed are configurable.|https://github.com/da-luce/astroterm|{{Pkg|astroterm}}}}
* {{App|[[Wikipedia:Celestia|Celestia]]|3D astronomy simulation program that allows users to travel through an extensive universe, modeled after reality, at any speed, in any direction and at any time in history.|https://celestiaproject.space/|{{AUR|celestia}}}}
* {{App|Gaia Sky|An open source 3D universe simulator with support for more than a billion objects|https://zah.uni-heidelberg.de/gaia/outreach/gaiasky|{{AUR|gaiasky}}}}
* {{App|HNSKY|Hallo Northern Sky is the semi professional free planetarium program|https://sourceforge.net/projects/hnsky/|{{AUR|hnsky-hg}}}}
* {{App|[[Wikipedia:KStars|KStars]]|Planetarium application that provides an accurate graphical simulation of the night sky, from any location on Earth, at any date and time. It is included in KDE Edu.|https://kstars.kde.org/|{{Pkg|kstars}}}}
* {{App|[[Wikipedia:Cartes du Ciel|Skychart / Cartes du Ciel]]|Planetarium that maps out and labels most of the constellations, planets, and objects you can see with a telescope. It can also download Digitized Sky Survey Charts and superimpose images over these charts.|https://www.ap-i.net/skychart/|{{AUR|skychart-git}}}}
* {{App|[[Wikipedia:Stellarium (computer program)|Stellarium]]|Beautiful 3D planetarium that uses OpenGL to render a realistic sky in real time.|https://stellarium.org/|{{Pkg|stellarium}}}}
* {{App|Virtual Moon Atlas|Software for Moon observation and survey|https://www.ap-i.net/avl/en/start|{{AUR|virtualmoonatlas}}}}
* {{App|[[Wikipedia:XEphem|XEphem]]|Motif-based ephemeris and planetarium program.|https://xephem.github.io/XEphem/Site/xephem.html|{{AUR|xephem}}}}

== Biology ==

=== Computational biology and bioinformatics ===

See also [[Wikipedia:List of open source bioinformatics software]].

* {{App|[[Wikipedia:Biopython|Biopython]]|Python package with tools for computational biology, as well as bioinformatics.|https://biopython.org/wiki/Biopython|{{AUR|python-biopython}}}}
* {{App|[[Wikipedia:EMBOSS|EMBOSS]] (European Molecular Biology Open Software Suite)|Open source software analysis package specially developed for the needs of the molecular biology and bioinformatics user community.|https://emboss.sourceforge.net/|{{AUR|emboss}}}}
* {{App|[[Wikipedia:MUMmer|MUMmer]]|Bioinformatics software system for sequence alignment based on suffix trees.|https://mummer.sourceforge.net/|{{AUR|mummer}}}}
* {{App|Snapgene|Closed source molecular cloning application that offers a fast and easy way to plan, visualize, and document molecular biology procedures. Supports a wide range of cloning and PCR manipulations. The free version allows most common visualizations of a molecular biology workflow.|https://www.snapgene.com/|{{AUR|snapgene}}}}
* {{App|[[Wikipedia:UGENE|UGENE]]|Application that integrates dozens of well-known biological tools and algorithms, providing both graphical user and command-line interfaces.|https://ugene.net/|{{AUR|ugene}}}}

=== Genealogy ===

* {{App|[[Wikipedia:Gramps (software)|Gramps]]|Genealogy program, which helps you track your family tree.|https://gramps-project.org/|{{Pkg|gramps}}}}

* {{App|[[Wikipedia:LifeLines|LifeLines]]|Text based genealogy software for family trees and reports.|https://github.com/lifelines/|{{AUR|lifelines}}}}

=== Image manipulation ===

* {{App|[[Wikipedia:FIJI_(software)|Fiji]]| {{AUR|ImageJ2}} distribution with a lot of plugins organized into a coherent menu structure.|https://fiji.sc|{{AUR|fiji-bin}}}}
* {{App|[[Wikipedia:ImageJ|ImageJ]]|Java-based image processing and analysing program that provides extensibility via plugins and macros. It is widely used in microscopy (e.g. for cell counting).|https://imagej.net/ij/|{{AUR|imagej}}}}

=== DICOM viewers and volume rendering ===

* {{App|[[Wikipedia:3DSlicer|3DSlicer]]|Comprehensive [[Wikipedia:Magnetic resonance imaging|MRI]], [[Wikipedia:CT scan|CT]], [[Wikipedia:Laser scanning confocal microscopy|LSCM microscopy]] volume processing, segmentation and 3D-reconstruction|https://www.slicer.org/|{{AUR|3dslicer}}}}
* {{App|aeskulap|Simple DICOM data viewer|https://www.nongnu.org/aeskulap/|{{AUR|aeskulap}}}}
* {{App|aliza|Open 2D, 3D and 4D images in DICOM, MetaIO, Nifti, Nrrd and other formats, meshes in DICOM, VTK, STL and OBJ formats|https://www.aliza-dicom-viewer.com/|{{AUR|aliza}}}}
* {{App|[[Wikipedia:ParaView|ParaView]]|Interactive data visualization tool built using VTK that can scale across distributed computer hardware.|https://www.paraview.org/|{{Pkg|paraview}}}}
* {{App|weasis|Multipurpose DICOM viewer with a highly modular architecture|https://nroduit.github.io/en/|{{AUR|weasis-bin}}}}

== Engineering ==

=== Computer-aided design ===

See also [[Wikipedia:List of computer-aided design editors]].

* {{App|[[Wikipedia:BRL-CAD|BRL-CAD]]|Constructive solid geometry modeling CAD system that includes an interactive geometry editor, ray tracing support for graphics rendering and geometric analysis, computer network distributed framebuffer support, scripting, image-processing and signal-processing tools.|https://brlcad.org/|{{AUR|brlcad}}}}
* {{App|[[Wikipedia:FreeCAD|FreeCAD]]|Parametric 3D CAD modeler based on OpenCascade, Coin3D, Qt, and Python with features such as macro recording, workbenches and the ability to run as a server.|https://freecad.org/|{{Pkg|freecad}}}}
* {{App|LeoCAD|CAD program for creating virtual LEGO models. It has an easy to use interface and currently includes over 10,000 different pieces created by the LDraw community.|https://www.leocad.org/|{{Pkg|leocad}}}}
* {{App|[[Wikipedia:LibreCAD|LibreCAD]]|A 2D CAD application based on Qt5. Forked from QCAD Community Edition.|https://www.librecad.org/|{{Pkg|librecad}}}}
* {{App|[[Wikipedia:OpenSCAD|OpenSCAD]]|A 3D CAD modeler that uses a textual, programmatic approach to creating and manipulating objects.|https://www.openscad.org|{{Pkg|openscad}}}}
* {{App|[[Wikipedia:QCad|QCAD]]|A 2D CAD application based on Qt. Supports the DFX and HPGL standard file formats, and optionally the DWG format through a proprietary plugin.|https://www.qcad.org/|{{Pkg|qcad}}}}
* {{App|[[Wikipedia:SolveSpace|SolveSpace]]|Powerful 3D CAD constraint-based parametric modeler with simple mechanical simulation capabilities.|https://solvespace.com/|{{AUR|solvespace}}}}

=== 3D printing ===

See also [[RepRap]].

==== Slicers ====

Slicers convert 3D models into a format supported by the 3D printer, usually this format is G-code.

* {{App|BambuStudio|Slicer for printers from BambuLabs. Fork of PrusaSlicer. Open source.|https://github.com/bambulab/BambuStudio|{{AUR|bambustudio-bin}}}}
* {{App|[[Wikipedia:Cura_(software)|Cura]]|Slicer by Ultimaker. Aimed at their printers but supports other brands as well. Open source.|https://ultimaker.com/software/ultimaker-cura|{{AUR|cura}}}}
* {{App|FlashPrint|Slicer for the FlashForge 3D printers. Closed source.|http://www.ff3dp.com/|{{AUR|flashprint}}}}
* {{App|icesl|Modelling software with integrated slicer. Not brand specific. Closed source.|https://icesl.loria.fr/|{{AUR|icesl}}}}
* {{App|IdeaMaker|Slicer by Raise3D. Aimed at their printers but supports other brands as well. Closed source.|https://www.raise3d.com/pages/ideamaker|{{AUR|ideamaker}}}}
* {{App|MatterControl|Simple 3D editor, slicer, and 3D printer control software by MatterHackers. Not brand specific. Open source.|http://www.mattercontrol.com|{{AUR|mattercontrol}}}}
* {{App|orca-slicer|Community maintained fork of BambuStudio (in turn forked from PrusaSlicer). Open Source.|https://github.com/SoftFever/OrcaSlicer|{{AUR|orca-slicer}}}}
* {{App|[[PrusaSlicer]]|Slicer by Prusa Research. A fork of Slic3r. Aimed at their printers but supports other brands as well. Open source.|https://github.com/prusa3d/PrusaSlicer|{{Pkg|prusa-slicer}}}}
* {{App|Slic3r|One of the earliest slicers. Not used much any longer. Not brand specific. Open source.|https://slic3r.org/|{{AUR|slic3r}}}}
* {{App|SuperSlicer|Community maintained improved fork of PrusaSlicer. Not brand specific. Open source.|https://github.com/supermerill/SuperSlicer|{{AUR|superslicer-bin}}}}

==== Control software ====

Software for controlling 3D printers, usually over a cable or wireless.

* {{App|OctoPrint|Web interface for FDM 3D printers using G-code. Open source.|https://octoprint.org/|{{AUR|octoprint}}}}
* {{App|PrintRun|GUI control software for FDM 3D printers using G-code. Open source.|https://github.com/kliment/Printrun|{{AUR|printrun}}}}
* {{App|[[Wikipedia:Repetier-Host|Repetier-Host]]|Combined slicer and control software for 3D printers. Closed source.|https://www.repetier.com/|{{AUR|repetier-host}}}}

=== Electronics ===

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

==== Digital logic ====

Digital logic software are mainly simple educational tools that intended for only designing and simulating logic circuits.

* {{App|Digital|Interactive simulator similar to the discontinued Logisim. Features Karnaugh maps, logic tables, FSM editor, VHDL export and more, written in Java.|https://github.com/hneemann/Digital|{{AUR|digital}}}}
* {{App|GTKWave|Fully featured GTK-based wave viewer which reads LXT, LXT2, VZT, FST, and GHW files as well as standard Verilog VCD/EVCD files and allows their viewing.|https://gtkwave.sourceforge.net/|{{Pkg|gtkwave}}}}
* {{App|Logisim|Educational digital logic design and simulation software, written in Java, officially its development has stopped.|https://sourceforge.net/projects/circuit/|{{AUR|logisim}}}}
* {{App|Logisim Evolution|Project which continue the development of the original Logisim with new features, written in Java.|https://github.com/reds-heig/logisim-evolution|{{AUR|logisim-evolution-git}}}}
* {{App|PulseView|Logic analyzer, oscilloscope and MSO GUI.|https://sigrok.org/wiki/PulseView|{{Pkg|pulseview}}}}
* {{App|SmartSim|Simple and beautiful digital logic circuit design and simulation software, mainly target teachers and students, very lightweight and cross platform, GPL licensed, written in Vala.|https://smartsim.org.uk|{{AUR|smartsim-git}}}}
* {{App|WaveDrom editor|Timing diagram rendering in real-time from simple textual description. Can also be edited and embedded in the browser.|https://wavedrom.com/|{{AUR|wavedrom-editor}}}}

==== HDL ====

Also see [[Wikipedia:Hardware description language]].

* {{App|GHDL|Free and Open Source VHDL 2008/93/87 analyzer, compiler and simulator.|https://github.com/ghdl/ghdl|{{AUR|ghdl}}}}
* {{App|Gowin EDA Edu IDE|An IDE for Gowin's FGPA devices, including Sipeed Tang Nano and Sipeed Tang Nano 4K.|https://www.gowinsemi.com.cn/faq.aspx|{{AUR|gowin-eda-edu-ide}}}}
* {{App|[[Intel Quartus Prime]]|A set of design tools for Intel's FPGA devices that includes Quartus Prime, ModelSim-Intel, HLS Compiler, etc.|https://www.intel.com/content/www/us/en/software/programmable/overview.html|{{AUR|quartus-free}}}}
* {{App|iverilog|Icarus Verilog compiler and simulation tool (slower but older than Verilator).|https://steveicarus.github.io/iverilog/|{{Pkg|iverilog}}}}
* {{App|[[Lattice Diamond]]|A set of design tools for Lattice's FPGA chips.|https://www.latticesemi.com|{{AUR|lattice-diamond}}}}
* {{App|[[Microsemi Libero]]|Development tools for designing with Microsemi's PolarFire, IGLOO2, SmartFusion2, RTG4, SmartFusion, IGLOO, ProASIC3 and Fusion families.|https://www.microsemi.com/product-directory/design-resources/1750-libero-soc#overview|see [[Microsemi Libero]]}}
* {{App|OpenFPGAloader|Universal utility for programming FPGA. Try {{AUR|openfpgaloader-git}} if your board is not managed by the stable version.|https://github.com/trabucayre/openFPGALoader|{{Pkg|openfpgaloader}}}}
* {{App|[[Wikipedia:Verilator|Verilator]]|A Verilog/SystemVerilog simulator, performs lint code-quality checks, compile to threaded C++ code for simulation.|https://verilator.org|{{Pkg|verilator}}}}
* {{App|VTR|Verilog to Routing, Open Source CAD Flow for FPGA ResearchVerilog to Route.|https://verilogtorouting.org|{{Pkg|vtr}}}}
* {{App|[[Xilinx ISE WebPACK]]|FPGA programmable logic design suit.|https://www.xilinx.com/products/design-tools/ise-design-suite/ise-webpack.html|see [[Xilinx ISE WebPACK]]}}

==== MCU IDE and programmers ====

* {{App|[[Arduino]]|Arduino prototyping platform SDK.|https://www.arduino.cc/en/Main/Software|{{Grp|arduino}}}}
* {{App|avrcalc|Calculator to speed development of Atmel AVRs.|https://sourceforge.net/projects/avrcalc|{{AUR|avrcalc}}}}
* {{App|AVRDUDE|Download/upload/manipulate the ROM and EEPROM contents of AVR microcontrollers.|https://www.nongnu.org/avrdude/|{{Pkg|avrdude}}}}
* {{App|dfu-util|Device firmware update (DFU) USB programmer.|https://dfu-util.sourceforge.net/|{{Pkg|dfu-util}}}}
* {{App|esp-idf|Espressif IoT Development Framework. Official development framework for ESP32.|https://github.com/espressif/esp-idf|{{AUR|esp-idf}}}}
* {{App|platformio|Collaborative platform for embedded development, embedded development, with debugger, unit testing, code analysis. Default IDE is [[VSCode]], but can be used by Atom, Eclipse, Emacs, Qt Creator, Vim and several other IDE. Core CLI utils.|https://platformio.org/|{{Pkg|platformio-core}}}}
* {{App|sdcc|Small Device C Compiler, appropriate for various 8-bit microcontrollers and microprocessors including those made by or based on Intel MCS51, Maxim/Dallas, DS80C390, Freescale/Motorola HC08, Zilog Z80, Padauk, ST Microelectronics STM8, MOS 6502, and WDC 65C02. Suite contains compiler, assembler, linker, preprocessor, various simulators, debuggers, etc. |https://sdcc.sourceforge.net/|{{Pkg|sdcc}}}}
* {{App|SPIPGM|Tool for programming serial SPI FlashROM memories attached to PC via parallel port cable.|https://rayer.g6.cz/programm/programe.htm|{{AUR|spipgm-bin}}}}
* {{App|stlink|Open source [https://www.st.com/en/microcontrollers-microprocessors.html STM32 MCU] programming toolset for ST microcontrollers.|https://github.com/texane/stlink|{{Pkg|stlink}}}}

==== Electronic circuit simulation and schematic capture editing ====

* {{App|easy_spice|Electronic circuit simulator. SPICE frontend, using gschem for schematics and ngspice as simulator.|https://easy-spice.sourceforge.net|{{AUR|easy_spice}}}}
* {{App|[[Wikipedia:GNU Circuit Analysis Package|gnucap]]|GNU circuit simulator.|http://gnucap.org|{{AUR|gnucap}}}}
* {{App|gspiceui|GUI to various freely available Spice electronic circuit simulators.|https://sourceforge.net/projects/gspiceui/|{{AUR|gspiceui}}}}
* {{App|[[Wikipedia:ngspice|ngspice]]|The established Linux circuit simulator. Open source successor of the [[Wikipedia:SPICE|spice3f5]] code. Has the most versatile user interface; supporting scripting within the circuit descriptions, use through an interpreter, as a C library, through tcl or various external wrappers (e.g., Python).|https://ngspice.sourceforge.net/|{{Pkg|ngspice}}}}
* {{App|[[Wikipedia:Oregano (software)|Oregano]]|Graphical software application for schematic capture and simulation of electrical circuits. The actual simulation is done by the [[Wikipedia:Ngspice|ngspice]] or [[Wikipedia:GNU Circuit Analysis Package|Gnucap]] engines.|https://github.com/drahnr/oregano|{{AUR|oregano}}}}
* {{App|[[Wikipedia:Quite Universal Circuit Simulator|Qucs]]|Electronics circuit simulator application that gives you the ability to set up a circuit with a graphical user interface and simulate its large-signal, small-signal and noise behaviour.|https://qucs.sourceforge.net|{{AUR|qucs}}}}
* {{App|qucs-s|Electronics circuit simulator that gives you the ability to set up a circuit with a GUI and simulate it. Fork of qucs that uses external, better, programs to do actual simulation.|https://ra3xdh.github.io/|{{AUR|qucs-s}}}}
* {{App|Xyce|SANDIA Xyce is an open source, SPICE-compatible, high-performance analog circuit simulator, capable of solving extremely large circuit problems by supporting large-scale parallel computing platforms.|https://xyce.sandia.gov https://github.com/Xyce/Xyce|{{AUR|xyce-serial}}}}

==== Electronic design and schematic capture editing ====

* {{App|asco|SPICE Circuit Optimizer.|https://asco.sourceforge.net|{{AUR|asco}}}}
* {{App|[[Wikipedia:Fritzing|Fritzing]]|Easy to use program to draw good-looking circuit diagrams, and also create schematics and PCBs.|https://fritzing.org/home/|{{AUR|fritzing}}}}
* {{App|[[gEDA]]|Full suite and toolkit of Electronic Design Automation tools that are used for electrical circuit design, schematic capture, simulation, prototyping, and production.|http://www.geda-project.org/|{{AUR|geda-gaf}}}}
* {{App|[[gEDA]] PCB|Interactive printed circuit board editor.|http://pcb.geda-project.org/|{{AUR|pcb}}}}
* {{App|[[Wikipedia:KiCad|KiCad]]|Software suite for electronic design automation (EDA) that facilitates the design of schematics for electronic circuits and their conversion to PCB (printed circuit board).|https://kicad.org/|{{Pkg|kicad}}}}
* {{App|[[Wikipedia:KTechLab|KTechLab]]|IDE for microcontrollers and electronic circuit simulation.|https://apps.kde.org/ktechlab/|{{AUR|ktechlab}}}}
* {{App|QElectroTech|Application used to draw advanced electrical circuits.|https://qelectrotech.org/|{{AUR|qelectrotech}}}}

== Telecommunication ==

* {{App|[[GNU Radio]]|Software development toolkit that provides signal processing blocks to implement software radios.|https://www.gnuradio.org/|{{Pkg|gnuradio}}}}
* {{App|Gqrx|Software defined radio receiver implemented using GNU Radio and the Qt GUI toolkit.|https://gqrx.dk/|{{Pkg|gqrx}}}}
* {{App|Pothos|The Pothos project is a complete data-flow framework for creating topologies of interconnected processing blocks. |https://github.com/pothosware/PothosCore/wiki|{{AUR|pothos}}, {{AUR|pothos-git}}}}
* {{App|SDR#|The most popular SDR program.|https://airspy.com/|{{AUR|sdrsharp}}}}
* {{App|SigDigger|Qt-based digital signal analyzer, using Suscan core and Sigutils DSP library.|https://github.com/BatchDrake/SigDigger|{{AUR|sigdigger-git}}}}

=== Amateur radio ===

See the main article: [[Amateur radio#Software]].

See also [[Wikipedia:List of software-defined radios]].

== Simulation modeling ==

* {{App|[[Wikipedia:AnyLogic|AnyLogic]]|AnyLogic is a cross-platform proprietary multimethod simulation modeling tool, which is also available for personal use.|https://www.anylogic.com/|{{AUR|anylogic-ple}}, {{AUR|anylogic-university}}, {{AUR|anylogic-professional}}}}
* {{App|[[Wikipedia:Flight Gear|Flight Gear]]|Open-source, multi-platform atmospheric and orbital flight simulator with a flight dynamics engine (JSBSim) that is part of a [https://web.archive.org/web/20201115084247/https://nescacademy.nasa.gov/src/flightsim/Reports/aiaa-15-1810-EOM_chkcases-II.pdf 2015 NASA benchmark] to judge new simulation code to space industry standards.|https://www.flightgear.org/|{{AUR|flightgear}}}}
* {{App|[[Wikipedia:Gephi|gephi]]|Gephi is an open-source network analysis and visualization software package written in Java.|https://gephi.org/|{{AUR|gephi}}}}
* {{App|golly|Golly is an open source, cross-platform application for exploring Conway's Game of Life and many other types of cellular automata.|https://golly.sourceforge.net/|{{AUR|golly}}}}
* {{App|Netlogo|NetLogo is a multi-agent programmable modeling environment.|https://ccl.northwestern.edu/netlogo/|{{AUR|netlogo}}}}

== Computer science ==

=== Architecture ===

* {{App|edumips64|Cross-platform educational MIPS64 CPU simulator.|https://edumips.org/|{{AUR|edumips64}}}}
* {{App|QtMips|MIPS CPU simulator for education purposes with pipeline and cache visualization.|https://github.com/cvut/QtMips|{{AUR|qtmips}}}}
* {{App|QtRvSim|RISC-V CPU simulator for education purposes.|https://github.com/cvut/qtrvsim|{{AUR|qtrvsim}}}}
* {{App|QtSpim|Qt port of one of the first educational MIPS CPU simulators. No longer maintained, but still used in some classrooms.|https://spimsimulator.sourceforge.net/|{{AUR|qtspim}}}}

=== Distributed systems ===

* {{App|Shadow|An open-source distributed system/network simulator/emulator hybrid (e.g. for [[Tor]] and [[Bitcoin]]).|https://shadow.github.io/|{{AUR|tor-shadow}}}}
* {{App|[[Wikipedia:SimGrid|SimGrid]]|A scientific instrument to study large-scale distributed systems.|https://simgrid.org/|{{AUR|simgrid}}}}

=== Networking ===

* {{App|CORE|Common Open Research Emulator.|https://www.nrl.navy.mil/Our-Work/Areas-of-Research/Information-Technology/NCS/CORE/|{{AUR|core}}}}
* {{App|[[Wikipedia:Graphical Network Simulator-3|GNS3]]|Network software emulator using a combination of virtual and real devices to simulate complex networks.|https://gns3.com/|{{AUR|gns3-gui}} (graphical user interface package), {{AUR|gns3-server}} (server package)}}
* {{App|IMUNES|Integrated Multiprotocol Network Emulator/Simulator.|https://imunes.net/|{{AUR|imunes}}}}
* {{App|[[Wikipedia:Ns (simulator)|ns-2]]|Discrete event simulator targeted at networking research.|https://www.isi.edu/nsnam/ns/|{{AUR|ns}}}}
* {{App|[[Wikipedia:Ns (simulator)|ns-3]]|Discrete-event network simulator for Internet systems.|https://www.nsnam.org/|{{AUR|ns3}}}}
* {{App|[[Wikipedia:OMNeT++|OMNeT++]]|Component-based simulation package designed for modeling communication networks.|https://omnetpp.org/|{{AUR|omnetpp}}}}

=== Photogrammetry ===

See also [[Wikipedia:Comparison_of_photogrammetry_software]].

* {{App|AliceVision|Photogrammetric Computer Vision Framework|https://alicevision.org/|{{AUR|alice-vision}}}}
* {{App|Meshroom|Node-based GUI for AliceVision|https://alicevision.org/#meshroom|{{AUR|meshroom}}}}
* {{App|OpenMVG|OpenMVG provides an end-to-end 3D reconstruction-from-images framework compounded of libraries, binaries, and pipelines.|https://github.com/openMVG/openMVG|{{AUR|openmvg-git}}}}
* {{App|OpenMVS|A library for computer-vision scientists and especially targeted to the Multi-View Stereo reconstruction community. |https://cdcseacave.github.io|{{AUR|openmvs}}}}

MythWeb

2026-05-12T16:00:02Z

Erus Iluvatar: archive page, flagged for a week

#REDIRECT [[ArchWiki:Archive]]
[[Category:Archive]]

ArchWiki:Translation Team (Español)/Board (Español)/Untranslated (Español)

2026-05-12T15:59:17Z

Erus Iluvatar: rm link to page before archival

[[Category:ArchWiki (Español)]]
[[ar:ArchWiki:Translation Team]]
[[cs:ArchWiki:Translation Team]]
[[el:ArchWiki:Translation Team]]
[[en:ArchWiki:Translation Team]]
[[hr:ArchWiki:Translation Team]]
[[it:ArchWiki:Translation Team]]
[[ja:ArchWiki 翻訳チーム]]
[[ko:ArchWiki:Translation Team]]
[[nl:ArchWiki:Translation Team]]
[[pl:ArchWiki:Translation Team]]
[[pt:ArchWiki:Translation Team]]
[[ru:ArchWiki:Translation Team]]
[[sk:ArchWiki:Translation Team]]
[[zh-hant:ArchWiki:Translation Team]]
{{Note (Español)|1=Las [[:Category:Disambiguation pages|páginas de desambiguación]] [[Wikipedia:es:Wikipedia:Manual_de_estilo/Páginas_de_desambiguación]] no deben traducirse.}}

== Artículos sin traducir ==

{| class="wikitable sortable"
|-style="color: #0000cc;"
! width=40% | Artículo
! width=5% | Pr.
! width=15% | Original
! width=40% | Observaciones
|-
| [[2bwm (Español)]]
| {{Grey|4}}
| [[2bwm|Artículo original]]
|
|-
| [[3D Mouse (Español)]]
| {{Grey|4}}
| [[3D Mouse|Artículo original]]
|
|-
| [[3G and GPRS modems with pppd (Español)]]
| {{Grey|4}}
| [[3G and GPRS modems with pppd|Artículo original]]
|
|-
| [[Accessibility (Español)]]
| {{Grey|4}}
| [[Accessibility|Artículo original]]
|
|-
| [[Acer Aspire 5560G-7809 (Español)]]
| {{Grey|4}}
| [[Acer Aspire 5560G-7809|Artículo original]]
|
|-
| [[Acer Aspire E11 Series (Español)]]
| {{Grey|4}}
| [[Acer Aspire E11 Series|Artículo original]]
|
|-
| [[Acer Aspire E5-575 (Español)]]
| {{Grey|4}}
| [[Acer Aspire E5-575|Artículo original]]
|
|-
| [[Acer Aspire S7-392 (Español)]]
| {{Grey|4}}
| [[Acer Aspire S7-392|Artículo original]]
|
|-
| [[Acer Aspire V3-371 (Español)]]
| {{Grey|4}}
| [[Acer Aspire V3-371|Artículo original]]
|
|-
| [[Acer Aspire V3-372 (Español)]]
| {{Grey|4}}
| [[Acer Aspire V3-372|Artículo original]]
|
|-
| [[Acer C710 Chromebook (Español)]]
| {{Grey|4}}
| [[Acer C710 Chromebook|Artículo original]]
|
|-
| [[Acer C720 Chromebook (Español)]]
| {{Grey|4}}
| [[Acer C720 Chromebook|Artículo original]]
|
|-
| [[Acer CB3-131 Chromebook (Español)]]
| {{Grey|4}}
| [[Acer CB3-131 Chromebook|Artículo original]]
|
|-
| [[Acer Chromebook 14 CB3-431 (Edgar) (Español)]]
| {{Grey|4}}
| [[Acer Chromebook 14 CB3-431 (Edgar)|Artículo original]]
|
|-
| [[Acer Cloudbook (Español)]]
| {{Grey|4}}
| [[Acer Cloudbook|Artículo original]]
|
|-
| [[Acer Switch Alpha 12 (Español)]]
| {{Grey|4}}
| [[Acer Switch Alpha 12|Artículo original]]
|
|-
| [[Acer TimelineX (Español)]]
| {{Grey|4}}
| [[Acer TimelineX|Artículo original]]
|
|-
| [[Acer Travelmate 4750 (Español)]]
| {{Grey|4}}
| [[Acer Travelmate 4750|Artículo original]]
|
|-
| [[ACME (Español)]]
| {{Grey|4}}
| [[ACME|Artículo original]]
|
|-
| [[Ad-hoc networking (Español)]]
| {{Grey|4}}
| [[Ad-hoc networking|Artículo original]]
|
|-
| [[Adminer (Español)]]
| {{Grey|4}}
| [[Adminer|Artículo original]]
|
|-
| [[Advanced Linux Sound Architecture (Español)/Configuration examples (Español)]]
| {{Grey|4}}
| [[Advanced Linux Sound Architecture/Configuration examples|Artículo original]]
|
|-
| [[Advanced Linux Sound Architecture (Español)/Troubleshooting (Español)]]
| {{Grey|4}}
| [[Advanced Linux Sound Architecture/Troubleshooting|Artículo original]]
|
|-
| [[Advanced traffic control (Español)]]
| {{Grey|4}}
| [[Advanced traffic control|Artículo original]]
|
|-
| [[AIDE (Español)]]
| {{Grey|4}}
| [[AIDE|Artículo original]]
|
|-
| [[AirPort (Español)]]
| {{Grey|4}}
| [[AirPort|Artículo original]]
|
|-
| [[Alienware 13 (Español)]]
| {{Grey|4}}
| [[Alienware 13|Artículo original]]
|
|-
| [[Alienware 15 (Español)]]
| {{Grey|4}}
| [[Alienware 15|Artículo original]]
|
|-
| [[Alienware M11x (Español)]]
| {{Grey|4}}
| [[Alienware M11x|Artículo original]]
|
|-
| [[Alienware M14xR2 (Español)]]
| {{Grey|4}}
| [[Alienware M14xR2|Artículo original]]
|
|-
| [[Allow a program to continue after logoff (Español)]]
| {{Grey|4}}
| [[Allow a program to continue after logoff|Artículo original]]
|
|-
| [[Alpine (Español)]]
| {{Grey|4}}
| [[Alpine|Artículo original]]
|
|-
| [[Altera Design Software (Español)]]
| {{Grey|4}}
| [[Altera Design Software|Artículo original]]
|
|-
| [[Alternative DNS services (Español)]]
| {{Grey|4}}
| [[Alternative DNS services|Artículo original]]
|
|-
| [[Amateur radio (Español)]]
| {{Grey|4}}
| [[Amateur radio|Artículo original]]
|
|-
| [[Amavis (Español)]]
| {{Grey|4}}
| [[Amavis|Artículo original]]
|
|-
| [[AMDGPU (Español)]]
| {{Grey|4}}
| [[AMDGPU|Artículo original]]
|
|-
| [[AMule (Español)]]
| {{Grey|4}}
| [[AMule|Artículo original]]
|
|-
| [[Android tethering (Español)]]
| {{Grey|4}}
| [[Android tethering|Artículo original]]
|
|-
| [[Anki (Español)]]
| {{Grey|4}}
| [[Anki|Artículo original]]
|
|-
| [[Ansible (Español)]]
| {{Grey|4}}
| [[Ansible|Artículo original]]
|
|-
| [[Anything-sync-daemon (Español)]]
| {{Grey|4}}
| [[Anything-sync-daemon|Artículo original]]
|
|-
| [[Apache Cassandra (Español)]]
| {{Grey|4}}
| [[Apache Cassandra|Artículo original]]
|
|-
| [[Apache HTTP Server (Español)/mod_gnutls (Español)]]
| {{Grey|4}}
| [[Apache HTTP Server/mod_gnutls|Artículo original]]
|
|-
| [[Apache HTTP Server (Español)/mod_perl (Español)]]
| {{Grey|4}}
| [[Apache HTTP Server/mod_perl|Artículo original]]
|
|-
| [[Apache HTTP Server (Español)/mod_wsgi (Español)]]
| {{Grey|4}}
| [[Apache HTTP Server/mod_wsgi|Artículo original]]
|
|-
| [[Apache OpenOffice (Español)]]
| {{Grey|4}}
| [[Apache OpenOffice|Artículo original]]
|
|-
| [[APC UPS (Español)]]
| {{Grey|4}}
| [[APC UPS|Artículo original]]
|
|-
| [[AppArmor (Español)]]
| {{Grey|4}}
| [[AppArmor|Artículo original]]
|
|-
| [[Apple Fusion Drive (Español)]]
| {{Grey|4}}
| [[Apple Fusion Drive|Artículo original]]
|
|-
| [[Apple Keyboard (Español)]]
| {{Grey|4}}
| [[Apple Keyboard|Artículo original]]
|
|-
| [[Arch is the best (Español)]]
| {{Grey|4}}
| [[Arch is the best|Artículo original]]
|
|-
| [[Arch Linux April Jokes (Español)]]
| {{Grey|4}}
| [[Arch Linux April Jokes|Artículo original]]
|
|-
| [[Arch Linux VPS (Español)]]
| {{Grey|4}}
| [[Arch Linux VPS|Artículo original]]
|
|-
| [[Arch package security (Español)]]
| {{Grey|4}}
| [[Arch package security|Artículo original]]
|
|-
| [[Arch Testing Team (Español)]]
| {{Grey|4}}
| [[Arch Testing Team|Artículo original]]
|
|-
| [[Archey3 (Español)]]
| {{Grey|4}}
| [[Archey3|Artículo original]]
|
|-
| [[ArchWiki:Administrators (Español)]]
| {{Grey|4}}
| [[ArchWiki:Administrators|Artículo original]]
|
|-
| [[ArchWiki:Bots (Español)]]
| {{Grey|4}}
| [[ArchWiki:Bots|Artículo original]]
|
|-
| [[ArchWiki:IRC (Español)]]
| {{Grey|4}}
| [[ArchWiki:IRC|Artículo original]]
|
|-
| [[ArchWiki:Maintainers (Español)]]
| {{Grey|4}}
| [[ArchWiki:Maintainers|Artículo original]]
|
|-
| [[ArchWiki:News (Español)]]
| {{Grey|4}}
| [[ArchWiki:News|Artículo original]]
|
|-
| [[ArchWiki:Requests (Español)]]
| {{Grey|4}}
| [[ArchWiki:Requests|Artículo original]]
|
|-
| [[ArchWiki:Statistics (Español)]]
| {{Grey|4}}
| [[ArchWiki:Statistics|Artículo original]]
|
|-
| [[Arduino (Español)]]
| {{Grey|4}}
| [[Arduino|Artículo original]]
|
|-
| [[Aria2 (Español)]]
| {{Grey|4}}
| [[Aria2|Artículo original]]
|
|-
| [[ASCII art (Español)]]
| {{Grey|4}}
| [[ASCII art|Artículo original]]
|
|-
| [[Asterisk (Español)]]
| {{Grey|4}}
| [[Asterisk|Artículo original]]
|
|-
| [[ASUS A53T (Español)]]
| {{Grey|4}}
| [[ASUS A53T|Artículo original]]
|
|-
| [[ASUS A6km (Español)]]
| {{Grey|4}}
| [[ASUS A6km|Artículo original]]
|
|-
| [[ASUS A7SN (Español)]]
| {{Grey|4}}
| [[ASUS A7SN|Artículo original]]
|
|-
| [[ASUS AT3IONT-I (Español)]]
| {{Grey|4}}
| [[ASUS AT3IONT-I|Artículo original]]
|
|-
| [[ASUS C302 (Español)]]
| {{Grey|4}}
| [[ASUS C302|Artículo original]]
|
|-
| [[ASUS E403SA (Español)]]
| {{Grey|4}}
| [[ASUS E403SA|Artículo original]]
|
|-
| [[ASUS Eee PC 1005P (Español)]]
| {{Grey|4}}
| [[ASUS Eee PC 1005P|Artículo original]]
|
|-
| [[ASUS Eee PC 1015pn (Español)]]
| {{Grey|4}}
| [[ASUS Eee PC 1015pn|Artículo original]]
|
|-
| [[ASUS Eee PC F201E (Español)]]
| {{Grey|4}}
| [[ASUS Eee PC F201E|Artículo original]]
|
|-
| [[ASUS Eee PC T101MT (Español)]]
| {{Grey|4}}
| [[ASUS Eee PC T101MT|Artículo original]]
|
|-
| [[ASUS G1 (Español)]]
| {{Grey|4}}
| [[ASUS G1|Artículo original]]
|
|-
| [[ASUS N550JV (Español)]]
| {{Grey|4}}
| [[ASUS N550JV|Artículo original]]
|
|-
| [[ASUS N550JX (Español)]]
| {{Grey|4}}
| [[ASUS N550JX|Artículo original]]
|
|-
| [[ASUS N551JM (Español)]]
| {{Grey|4}}
| [[ASUS N551JM|Artículo original]]
|
|-
| [[ASUS N551VW (Español)]]
| {{Grey|4}}
| [[ASUS N551VW|Artículo original]]
|
|-
| [[ASUS N55SF (Español)]]
| {{Grey|4}}
| [[ASUS N55SF|Artículo original]]
|
|-
| [[ASUS N56jr (Español)]]
| {{Grey|4}}
| [[ASUS N56jr|Artículo original]]
|
|-
| [[ASUS N82JV (Español)]]
| {{Grey|4}}
| [[ASUS N82JV|Artículo original]]
|
|-
| [[ASUS TX201LA (Español)]]
| {{Grey|4}}
| [[ASUS TX201LA|Artículo original]]
|
|-
| [[ASUS U31SD (Español)]]
| {{Grey|4}}
| [[ASUS U31SD|Artículo original]]
|
|-
| [[ASUS Zenbook UX301LA (Español)]]
| {{Grey|4}}
| [[ASUS Zenbook UX301LA|Artículo original]]
|
|-
| [[ASUS x205ta (Español)]]
| {{Grey|4}}
| [[ASUS x205ta|Artículo original]]
|
|-
| [[ASUS X455LF (Español)]]
| {{Grey|4}}
| [[ASUS X455LF|Artículo original]]
|
|-
| [[ASUS X502CA (Español)]]
| {{Grey|4}}
| [[ASUS X502CA|Artículo original]]
|
|-
| [[ASUS X551MA (Español)]]
| {{Grey|4}}
| [[ASUS X551MA|Artículo original]]
|
|-
| [[ASUS X551MAV (Español)]]
| {{Grey|4}}
| [[ASUS X551MAV|Artículo original]]
|
|-
| [[ASUS X552M (Español)]]
| {{Grey|4}}
| [[ASUS X552M|Artículo original]]
|
|-
| [[ASUS X553MA (Español)]]
| {{Grey|4}}
| [[ASUS X553MA|Artículo original]]
|
|-
| [[ASUS X555L (Español)]]
| {{Grey|4}}
| [[ASUS X555L|Artículo original]]
|
|-
| [[ASUS Zenbook Prime UX31A (Español)]]
| {{Grey|4}}
| [[ASUS Zenbook Prime UX31A|Artículo original]]
|
|-
| [[ASUS Zenbook Pro UX501 (Español)]]
| {{Grey|4}}
| [[ASUS Zenbook Pro UX501|Artículo original]]
|
|-
| [[ASUS Zenbook UX303 (Español)]]
| {{Grey|4}}
| [[ASUS Zenbook UX303|Artículo original]]
|
|-
| [[ASUS Zenbook UX305 (Español)]]
| {{Grey|4}}
| [[ASUS Zenbook UX305|Artículo original]]
|
|-
| [[ASUS Zenbook UX31E (Español)]]
| {{Grey|4}}
| [[ASUS Zenbook UX31E|Artículo original]]
|
|-
| [[ASUS Zenbook UX32A (Español)]]
| {{Grey|4}}
| [[ASUS Zenbook UX32A|Artículo original]]
|
|-
| [[ASUS Zenbook UX330UA (Español)]]
| {{Grey|4}}
| [[ASUS Zenbook UX330UA|Artículo original]]
|
|-
| [[ASUS Zenbook UX331UA (Español)]]
| {{Grey|4}}
| [[ASUS Zenbook UX331UA|Artículo original]]
|
|-
| [[ASUS Zenbook UX430/UX530 (Español)]]
| {{Grey|4}}
| [[ASUS Zenbook UX430/UX530|Artículo original]]
|
|-
| [[ASUS Zenbook UX51Vz (Español)]]
| {{Grey|4}}
| [[ASUS Zenbook UX51Vz|Artículo original]]
|
|-
| [[ATA over Ethernet (Español)]]
| {{Grey|4}}
| [[ATA over Ethernet|Artículo original]]
|
|-
| [[Audiobook (Español)]]
| {{Grey|4}}
| [[Audiobook|Artículo original]]
|
|-
| [[Audit framework (Español)]]
| {{Grey|4}}
| [[Audit framework|Artículo original]]
|
|-
| [[Avahi (Español)]]
| {{Grey|4}}
| [[Avahi|Artículo original]]
|
|-
| [[Awstats (Español)]]
| {{Grey|4}}
| [[AWStats|Artículo original]]
|
|-
| [[Back In Time (Español)]]
| {{Grey|4}}
| [[Back In Time|Artículo original]]
|
|-
| [[Backlight (Español)]]
| {{Grey|4}}
| [[Backlight|Artículo original]]
|
|-
| [[Backup Gmail with getmail (Español)]]
| {{Grey|4}}
| [[Backup Gmail with getmail|Artículo original]]
|
|-
| [[BackupPC (Español)]]
| {{Grey|4}}
| [[BackupPC|Artículo original]]
|
|-
| [[Baloo (Español)]]
| {{Grey|4}}
| [[Baloo|Artículo original]]
|
|-
| [[Bcache (Español)]]
| {{Grey|4}}
| [[Bcache|Artículo original]]
|
|-
| [[Bftpd (Español)]]
| {{Grey|4}}
| [[Bftpd|Artículo original]]
|
|-
| [[Binfmt misc for Java (Español)]]
| {{Grey|4}}
| [[Binfmt misc for Java|Artículo original]]
|
|-
| [[Bisecting bugs with Git (Español)]]
| {{Grey|4}}
| [[Bisecting bugs with Git|Artículo original]]
|
|-
| [[Bitcoin (Español)]]
| {{Grey|4}}
| [[Bitcoin|Artículo original]]
|
|-
| [[BlackBerry (Español)]]
| {{Grey|4}}
| [[BlackBerry|Artículo original]]
|
|-
| [[Blackbox (Español)]]
| {{Grey|4}}
| [[Blackbox|Artículo original]]
|
|-
| [[Blender (Español)]]
| {{Grey|4}}
| [[Blender|Artículo original]]
|
|-
| [[Blueman (Español)]]
| {{Grey|4}}
| [[Blueman|Artículo original]]
|
|-
| [[Bluetooth headset (Español)]]
| {{Grey|4}}
| [[Bluetooth headset|Artículo original]]
|
|-
| [[Bluetooth keyboard (Español)]]
| {{Grey|4}}
| [[Bluetooth keyboard|Artículo original]]
|
|-
| [[Bluetooth mouse (Español)]]
| {{Grey|4}}
| [[Bluetooth mouse|Artículo original]]
|
|-
| [[Bluetoothctl (Español)]]
| {{Grey|4}}
| [[Bluetoothctl|Artículo original]]
|
|-
| [[Blu-ray (Español)]]
| {{Grey|4}}
| [[Blu-ray|Artículo original]]
|
|-
| [[Bmpanel (Español)]]
| {{Grey|4}}
| [[Bmpanel|Artículo original]]
|
|-
| [[BOINC (Español)]]
| {{Grey|4}}
| [[BOINC|Artículo original]]
|
|-
| [[Bootchart (Español)]]
| {{Grey|4}}
| [[Bootchart|Artículo original]]
|
|-
| [[Bridge with netctl (Español)]]
| {{Grey|4}}
| [[Bridge with netctl|Artículo original]]
|
|-
| [[Broadcom wireless (Español)]]
| {{Grey|4}}
| [[Broadcom wireless|Artículo original]]
|
|-
| [[Browser extensions (Español)]]
| {{Grey|4}}
| [[Browser extensions|Artículo original]]
|
|-
| [[Brutal Doom (Español)]]
| {{Grey|4}}
| [[Brutal Doom|Artículo original]]
|
|-
| [[Bubblewrap (Español)]]
| {{Grey|4}}
| [[Bubblewrap|Artículo original]]
|
|-
| [[Bug reporting guidelines (Español)]]
| {{Grey|4}}
| [[Bug reporting guidelines|Artículo original]]
|
|-
| [[Bugzilla (Español)]]
| {{Grey|4}}
| [[Bugzilla|Artículo original]]
|
|-
| [[Building 32-bit packages on a 64-bit system (Español)]]
| {{Grey|4}}
| [[Building 32-bit packages on a 64-bit system|Artículo original]]
|
|-
| [[Burning Xbox 360 games (Español)]]
| {{Grey|4}}
| [[Burning Xbox 360 games|Artículo original]]
|
|-
| [[Bus pirate (Español)]]
| {{Grey|4}}
| [[Bus Pirate|Artículo original]]
|
|-
| [[BusyBox (Español)]]
| {{Grey|4}}
| [[BusyBox|Artículo original]]
|
|-
| [[Bylaw Amendment (Español)]]
| {{Grey|4}}
| [[Bylaw Amendment|Artículo original]]
|
|-
| [[Cacti (Español)]]
| {{Grey|4}}
| [[Cacti|Artículo original]]
|
|-
| [[Caddy (Español)]]
| {{Grey|4}}
| [[Caddy|Artículo original]]
|
|-
| [[Cairo-Dock (Español)]]
| {{Grey|4}}
| [[Cairo-Dock|Artículo original]]
|
|-
| [[Calibrating Touchscreen (Español)]]
| {{Grey|4}}
| [[Calibrating Touchscreen|Artículo original]]
|
|-
| [[Canon CAPT (Español)]]
| {{Grey|4}}
| [[Canon CAPT|Artículo original]]
|
|-
| [[Capabilities (Español)]]
| {{Grey|4}}
| [[Capabilities|Artículo original]]
|
|-
| [[Ccache (Español)]]
| {{Grey|4}}
| [[Ccache|Artículo original]]
|
|-
| [[CDemu (Español)]]
| {{Grey|4}}
| [[CDemu|Artículo original]]
|
|-
| [[Cdist (Español)]]
| {{Grey|4}}
| [[Cdist|Artículo original]]
|
|-
| [[CDM (Español)]]
| {{Grey|4}}
| [[CDM|Artículo original]]
|
|-
| [[Ceph (Español)]]
| {{Grey|4}}
| [[Ceph|Artículo original]]
|
|-
| [[Certbot (Español)]]
| {{Grey|4}}
| [[Certbot|Artículo original]]
|
|-
| [[Cgit (Español)]]
| {{Grey|4}}
| [[Cgit|Artículo original]]
|
|-
| [[Cgroups (Español)]]
| {{Grey|4}}
| [[Cgroups|Artículo original]]
|
|-
| [[Chef (Español)]]
| {{Grey|4}}
| [[Chef|Artículo original]]
|
|-
| [[CherryMusic (Español)]]
| {{Grey|4}}
| [[CherryMusic|Artículo original]]
|
|-
| [[Chrome OS devices (Español)]]
| {{Grey|4}}
| [[Chrome OS devices|Artículo original]]
|
|-
| [[Chrome OS devices (Español)/Chromebook (Español)]]
| {{Grey|4}}
| [[Chrome OS devices/Chromebook|Artículo original]]
|
|-
| [[Chrome OS devices (Español)/Custom firmware (Español)]]
| {{Grey|4}}
| [[Chrome OS devices/Custom firmware|Artículo original]]
|
|-
| [[Chromebook Pixel 2 (Español)]]
| {{Grey|4}}
| [[Chromebook Pixel 2|Artículo original]]
|
|-
| [[Chromium (Español)/Tips and tricks (Español)]]
| {{Grey|4}}
| [[Chromium/Tips and tricks|Artículo original]]
|
|-
| [[Chrony (Español)]]
| {{Grey|4}}
| [[Chrony|Artículo original]]
|
|-
| [[Chsh (Español)]]
| {{Grey|4}}
| [[Chsh|Artículo original]]
|
|-
| [[Cinnamon (Español)]]
| {{Grey|4}}
| [[Cinnamon|Artículo original]]
|
|-
| [[Citrix (Español)]]
| {{Grey|4}}
| [[Citrix|Artículo original]]
|
|-
| [[Cjdns (Español)]]
| {{Grey|4}}
| [[Cjdns|Artículo original]]
|
|-
| [[Clevo P650RS (Español)]]
| {{Grey|4}}
| [[Clevo P650RS|Artículo original]]
|
|-
| [[Clevo W840SU (Español)]]
| {{Grey|4}}
| [[Clevo W840SU|Artículo original]]
|
|-
| [[CloudCross (Español)]]
| {{Grey|4}}
| [[CloudCross|Artículo original]]
|
|-
| [[Cloud-init (Español)]]
| {{Grey|4}}
| [[Cloud-init|Artículo original]]
|
|-
| [[Clover (Español)]]
| {{Grey|4}}
| [[Clover|Artículo original]]
|
|-
| [[CLR package guidelines (Español)]]
| {{Grey|4}}
| [[CLR package guidelines|Artículo original]]
|
|-
| [[Cmus (Español)]]
| {{Grey|4}}
| [[Cmus|Artículo original]]
|
|-
| [[Common Access Card (Español)]]
| {{Grey|4}}
| [[Common Access Card|Artículo original]]
|
|-
| [[Common Desktop Environment (Español)]]
| {{Grey|4}}
| [[Common Desktop Environment|Artículo original]]
|
|-
| [[Compile kernel module (Español)]]
| {{Grey|4}}
| [[Compile kernel module|Artículo original]]
|
|-
| [[Compiz (Español)/Configuration (Español)]]
| {{Grey|4}}
| [[Compiz/Configuration|Artículo original]]
|
|-
| [[Compton (Español)]]
| {{Grey|4}}
| [[Compton|Artículo original]]
|
|-
| [[Concurrent Versions System (Español)]]
| {{Grey|4}}
| [[Concurrent Versions System|Artículo original]]
|
|-
| [[Conky (Español)/Tips and tricks (Español)]]
| {{Grey|4}}
| [[Conky/Tips and tricks|Artículo original]]
|
|-
| [[ConnMan (Español)]]
| {{Grey|4}}
| [[ConnMan|Artículo original]]
|
|-
| [[Console TDM (Español)]]
| {{Grey|4}}
| [[Console TDM|Artículo original]]
|
|-
| [[ConsoleKit (Español)]]
| {{Grey|4}}
| [[ConsoleKit|Artículo original]]
|
|-
| [[Convert any Movie to DVD Video (Español)]]
| {{Grey|4}}
| [[Convert any Movie to DVD Video|Artículo original]]
|
|-
| [[Convert FLAC to MP3 (Español)]]
| {{Grey|4}}
| [[Convert FLAC to MP3|Artículo original]]
|
|-
| [[Core dump (Español)]]
| {{Grey|4}}
| [[Core dump|Artículo original]]
|
|-
| [[CouchDB (Español)]]
| {{Grey|4}}
| [[CouchDB|Artículo original]]
|
|-
| [[Courier Email Server (Español)]]
| {{Grey|4}}
| [[Courier Email Server|Artículo original]]
|
|-
| [[Courier Mail Server (Español)]]
| {{Grey|4}}
| [[Courier Mail Server|Artículo original]]
|
|-
| [[Cozy (Español)]]
| {{Grey|4}}
| [[Cozy|Artículo original]]
|
|-
| [[CrashPlan (Español)]]
| {{Grey|4}}
| [[CrashPlan|Artículo original]]
|
|-
| [[Create root filesystem snapshots with LVM (Español)]]
| {{Grey|4}}
| [[Create root filesystem snapshots with LVM|Artículo original]]
|
|-
| [[Creating packages for other distributions (Español)]]
| {{Grey|4}}
| [[Creating packages for other distributions|Artículo original]]
|
|-
| [[Cron (Español)]]
| {{Grey|4}}
| [[Cron|Artículo original]]
|
|-
| [[Crontab (Español)]]
| {{Grey|4}}
| [[Crontab|Artículo original]]
|
|-
| [[Cross-compiling tools package guidelines (Español)]]
| {{Grey|4}}
| [[Cross-compiling tools package guidelines|Artículo original]]
|
|-
| [[CrossOver (Español)]]
| {{Grey|4}}
| [[CrossOver|Artículo original]]
|
|-
| [[CUE Splitting (Español)]]
| {{Grey|4}}
| [[CUE Splitting|Artículo original]]
|
|-
| [[CUPS (Español)/Printer sharing (Español)]]
| {{Grey|4}}
| [[CUPS/Printer sharing|Artículo original]]
|
|-
| [[CUPS (Español)/Printer-specific problems (Español)]]
| {{Grey|4}}
| [[CUPS/Printer-specific problems|Artículo original]]
|
|-
| [[CUPS (Español)/Troubleshooting (Español)]]
| {{Grey|4}}
| [[CUPS/Troubleshooting|Artículo original]]
|
|-
| [[CurlFtpFS (Español)]]
| {{Grey|4}}
| [[CurlFtpFS|Artículo original]]
|
|-
| [[Cwm (Español)]]
| {{Grey|4}}
| [[Cwm|Artículo original]]
|
|-
| [[CyberPower UPS (Español)]]
| {{Grey|4}}
| [[CyberPower UPS|Artículo original]]
|
|-
| [[DANE (Español)]]
| {{Grey|4}}
| [[DANE|Artículo original]]
|
|-
| [[Dash (Español)]]
| {{Grey|4}}
| [[Dash|Artículo original]]
|
|-
| [[Davfs2 (Español)]]
| {{Grey|4}}
| [[Davfs2|Artículo original]]
|
|-
| [[DDRaceNetwork (Español)]]
| {{Grey|4}}
| [[DDRaceNetwork|Artículo original]]
|
|-
| [[Debug - Getting Traces (Español)]]
| {{Grey|4}}
| [[Debug - Getting Traces|Artículo original]]
|
|-
| [[Deepin Desktop Environment (Español)]]
| {{Grey|4}}
| [[Deepin Desktop Environment|Artículo original]]
|
|-
| [[Default applications (Español)]]
| {{Grey|4}}
| [[Default applications|Artículo original]]
|
|-
| [[Dell Chromebook 11 (Español)]]
| {{Grey|4}}
| [[Dell Chromebook 11|Artículo original]]
|
|-
| [[Dell Inspiron 11 3000 (3162) (Español)]]
| {{Grey|4}}
| [[Dell Inspiron 11 3000 (3162)|Artículo original]]
|
|-
| [[Dell Inspiron 13 (5368) (Español)]]
| {{Grey|4}}
| [[Dell Inspiron 13 (5368)|Artículo original]]
|
|-
| [[Dell Inspiron 13 (5378) (Español)]]
| {{Grey|4}}
| [[Dell Inspiron 13 (5378)|Artículo original]]
|
|-
| [[Dell Inspiron 3521 (Español)]]
| {{Grey|4}}
| [[Dell Inspiron 3521|Artículo original]]
|
|-
| [[Dell Inspiron 3531 (Español)]]
| {{Grey|4}}
| [[Dell Inspiron 3531|Artículo original]]
|
|-
| [[Dell Inspiron 5575 (Español)]]
| {{Grey|4}}
| [[Dell Inspiron 5575|Artículo original]]
|
|-
| [[Dell Latitude 7370 (Español)]]
| {{Grey|4}}
| [[Dell Latitude 7370|Artículo original]]
|
|-
| [[Dell Latitude 7480 (Español)]]
| {{Grey|4}}
| [[Dell Latitude 7480|Artículo original]]
|
|-
| [[Dell Latitude D630 (Español)]]
| {{Grey|4}}
| [[Dell Latitude D630|Artículo original]]
|
|-
| [[Dell Latitude E5430 (Español)]]
| {{Grey|4}}
| [[Dell Latitude E5430|Artículo original]]
|
|-
| [[Dell Latitude E5520 (Español)]]
| {{Grey|4}}
| [[Dell Latitude E5520|Artículo original]]
|
|-
| [[Dell Latitude E5580 (Español)]]
| {{Grey|4}}
| [[Dell Latitude E5580|Artículo original]]
|
|-
| [[Dell Latitude E6620 (Español)]]
| {{Grey|4}}
| [[Dell Latitude E6620|Artículo original]]
|
|-
| [[Dell Latitude E7270 (Español)]]
| {{Grey|4}}
| [[Dell Latitude E7270|Artículo original]]
|
|-
| [[Dell Latitude E7440 (Español)]]
| {{Grey|4}}
| [[Dell Latitude E7440|Artículo original]]
|
|-
| [[Dell Studio 1737 (Español)]]
| {{Grey|4}}
| [[Dell Studio 1737|Artículo original]]
|
|-
| [[Dell Vostro 1310 (Español)]]
| {{Grey|4}}
| [[Dell Vostro 1310|Artículo original]]
|
|-
| [[Dell Vostro 3360 (Español)]]
| {{Grey|4}}
| [[Dell Vostro 3360|Artículo original]]
|
|-
| [[Dell XPS 13 2-in-1 (9365) (Español)]]
| {{Grey|4}}
| [[Dell XPS 13 2-in-1 (9365)|Artículo original]]
|
|-
| [[Dell XPS 13 (9333) (Español)]]
| {{Grey|4}}
| [[Dell XPS 13 (9333)|Artículo original]]
|
|-
| [[Dell XPS 13 (9343) (Español)]]
| {{Grey|4}}
| [[Dell XPS 13 (9343)|Artículo original]]
|
|-
| [[Dell XPS 13 (9350) (Español)]]
| {{Grey|4}}
| [[Dell XPS 13 (9350)|Artículo original]]
|
|-
| [[Dell XPS 13 (9360) (Español)]]
| {{Grey|4}}
| [[Dell XPS 13 (9360)|Artículo original]]
|
|-
| [[Dell XPS 13 (9370) (Español)]]
| {{Grey|4}}
| [[Dell XPS 13 (9370)|Artículo original]]
|
|-
| [[Dell XPS 15 (Español)]]
| {{Grey|4}}
| [[Dell XPS 15|Artículo original]]
|
|-
| [[Dell XPS 15 (9550) (Español)]]
| {{Grey|4}}
| [[Dell XPS 15 (9550)|Artículo original]]
|
|-
| [[Dell XPS 15 (9560) (Español)]]
| {{Grey|4}}
| [[Dell XPS 15 (9560)|Artículo original]]
|
|-
| [[Dell XPS 15 (9570) (Español)]]
| {{Grey|4}}
| [[Dell XPS 15 (9570)|Artículo original]]
|
|-
| [[Dell XPS 15z (Español)]]
| {{Grey|4}}
| [[Dell XPS 15z|Artículo original]]
|
|-
| [[Dell XPS 17 (L702x) (Español)]]
| {{Grey|4}}
| [[Dell XPS 17 (L702x)|Artículo original]]
|
|-
| [[Dell XPS M1330 (Español)]]
| {{Grey|4}}
| [[Dell XPS M1330|Artículo original]]
|
|-
| [[Dell XPS M2010 (Español)]]
| {{Grey|4}}
| [[Dell XPS M2010|Artículo original]]
|
|-
| [[Desktop entries (Español)]]
| {{Grey|4}}
| [[Desktop entries|Artículo original]]
|
|-
| [[Dhcpd (Español)]]
| {{Grey|4}}
| [[Dhcpd|Artículo original]]
|
|-
| [[Diaspora (Español)]]
| {{Grey|4}}
| [[Diaspora|Artículo original]]
|
|-
| [[Dictd (Español)]]
| {{Grey|4}}
| [[Dictd|Artículo original]]
|
|-
| [[Dig (Español)]]
| {{Grey|4}}
| [[Dig|Artículo original]]
|
|-
| [[Digikam (Español)]]
| {{Grey|4}}
| [[Digikam|Artículo original]]
|
|-
| [[Dillo (Español)]]
| {{Grey|4}}
| [[Dillo|Artículo original]]
|
|-
| [[Disk quota (Español)]]
| {{Grey|4}}
| [[Disk quota|Artículo original]]
|
|-
| [[Diskless system (Español)]]
| {{Grey|4}}
| [[Diskless system|Artículo original]]
|
|-
| [[Display Power Management Signaling (Español)]]
| {{Grey|4}}
| [[Display Power Management Signaling|Artículo original]]
|
|-
| [[DisplayLink (Español)]]
| {{Grey|4}}
| [[DisplayLink|Artículo original]]
|
|-
| [[Distcc (Español)]]
| {{Grey|4}}
| [[Distcc|Artículo original]]
|
|-
| [[Django (Español)]]
| {{Grey|4}}
| [[Django|Artículo original]]
|
|-
| [[Dkfilter (Español)]]
| {{Grey|4}}
| [[Dkfilter|Artículo original]]
|
|-
| [[DocBook (Español)]]
| {{Grey|4}}
| [[DocBook|Artículo original]]
|
|-
| [[Docker (Español)]]
| {{Grey|4}}
| [[Docker|Artículo original]]
|
|-
| [[Dofus (Español)]]
| {{Grey|4}}
| [[Dofus|Artículo original]]
|
|-
| [[Dolphin emulator (Español)]]
| {{Grey|4}}
| [[Dolphin emulator|Artículo original]]
|
|-
| [[Dotfiles (Español)]]
| {{Grey|4}}
| [[Dotfiles|Artículo original]]
|
|-
| [[Dovecot (Español)]]
| {{Grey|4}}
| [[Dovecot|Artículo original]]
|
|-
| [[Drill (Español)]]
| {{Grey|4}}
| [[Drill|Artículo original]]
|
|-
| [[Dropbox (Español)]]
| {{Grey|4}}
| [[Dropbox|Artículo original]]
|
|-
| [[DSDT (Español)]]
| {{Grey|4}}
| [[DSDT|Artículo original]]
|
|-
| [[DSL SpeedTouch modem (Español)]]
| {{Grey|4}}
| [[DSL SpeedTouch modem|Artículo original]]
|
|-
| [[Dtach (Español)]]
| {{Grey|4}}
| [[Dtach|Artículo original]]
|
|-
| [[Dunst (Español)]]
| {{Grey|4}}
| [[Dunst|Artículo original]]
|
|-
| [[Duplicity (Español)]]
| {{Grey|4}}
| [[Duplicity|Artículo original]]
|
|-
| [[Duply (Español)]]
| {{Grey|4}}
| [[Duply|Artículo original]]
|
|-
| [[DVB-S (Español)]]
| {{Grey|4}}
| [[DVB-S|Artículo original]]
|
|-
| [[DVB-T (Español)]]
| {{Grey|4}}
| [[DVB-T|Artículo original]]
|
|-
| [[Dvdbackup (Español)]]
| {{Grey|4}}
| [[Dvdbackup|Artículo original]]
|
|-
| [[Dvorak (Español)]]
| {{Grey|4}}
| [[Dvorak|Artículo original]]
|
|-
| [[Dwarf Fortress (Español)]]
| {{Grey|4}}
| [[Dwarf Fortress|Artículo original]]
|
|-
| [[Dynamic disks (Español)]]
| {{Grey|4}}
| [[Dynamic disks|Artículo original]]
|
|-
| [[Dynamic DNS (Español)]]
| {{Grey|4}}
| [[Dynamic DNS|Artículo original]]
|
|-
| [[Dynamic Kernel Module Support (Español)]]
| {{Grey|4}}
| [[Dynamic Kernel Module Support|Artículo original]]
|
|-
| [[Dzen (Español)]]
| {{Grey|4}}
| [[Dzen|Artículo original]]
|
|-
| [[Easy-RSA (Español)]]
| {{Grey|4}}
| [[Easy-RSA|Artículo original]]
|
|-
| [[ECryptfs (Español)]]
| {{Grey|4}}
| [[ECryptfs|Artículo original]]
|
|-
| [[Elasticsearch (Español)]]
| {{Grey|4}}
| [[Elasticsearch|Artículo original]]
|
|-
| [[Electronic identification (Español)]]
| {{Grey|4}}
| [[Electronic identification|Artículo original]]
|
|-
| [[Envy24control (Español)]]
| {{Grey|4}}
| [[Envy24control|Artículo original]]
|
|-
| [[Etherpad-lite (Español)]]
| {{Grey|4}}
| [[Etherpad-lite|Artículo original]]
|
|-
| [[Evilwm (Español)]]
| {{Grey|4}}
| [[Evilwm|Artículo original]]
|
|-
| [[Exim (Español)]]
| {{Grey|4}}
| [[Exim|Artículo original]]
|
|-
| [[Ext3 (Español)]]
| {{Grey|4}}
| [[Ext3|Artículo original]]
|
|-
| [[Extra keyboard keys (Español)]]
| {{Grey|4}}
| [[Extra keyboard keys|Artículo original]]
|
|-
| [[Extreme Multihead (Español)]]
| {{Grey|4}}
| [[Extreme Multihead|Artículo original]]
|
|-
| [[EXWM (Español)]]
| {{Grey|4}}
| [[EXWM|Artículo original]]
|
|-
| [[F2FS (Español)]]
| {{Grey|4}}
| [[F2FS|Artículo original]]
|
|-
| [[Faction (Español)]]
| {{Grey|4}}
| [[Faction|Artículo original]]
|
|-
| [[Fan speed control (Español)]]
| {{Grey|4}}
| [[Fan speed control|Artículo original]]
|
|-
| [[Fbpad (Español)]]
| {{Grey|4}}
| [[Fbpad|Artículo original]]
|
|-
| [[Fbpanel (Español)]]
| {{Grey|4}}
| [[Fbpanel|Artículo original]]
|
|-
| [[Fcitx (Español)]]
| {{Grey|4}}
| [[Fcitx|Artículo original]]
|
|-
| [[Festival (Español)]]
| {{Grey|4}}
| [[Festival|Artículo original]]
|
|-
| [[FFmpeg (Español)]]
| {{Grey|4}}
| [[FFmpeg|Artículo original]]
|
|-
| [[Fhem (Español)]]
| {{Grey|4}}
| [[FHEM|Artículo original]]
|
|-
| [[File recovery (Español)]]
| {{Grey|4}}
| [[File recovery|Artículo original]]
|
|-
| [[Fingerprint GUI (Español)]]
| {{Grey|4}}
| [[Fingerprint GUI|Artículo original]]
|
|-
| [[Firefox (Español)/Privacy (Español)]]
| {{Grey|4}}
| [[Firefox/Privacy|Artículo original]]
|
|-
| [[Firefox (Español)/Profile on RAM (Español)]]
| {{Grey|4}}
| [[Firefox/Profile on RAM|Artículo original]]
|
|-
| [[Firefox (Español)/Tweaks (Español)]]
| {{Grey|4}}
| [[Firefox/Tweaks|Artículo original]]
|
|-
| [[Firehol (Español)]]
| {{Grey|4}}
| [[FireHOL|Artículo original]]
|
|-
| [[Firejail (Español)]]
| {{Grey|4}}
| [[Firejail|Artículo original]]
|
|-
| [[Fish (Español)]]
| {{Grey|4}}
| [[Fish|Artículo original]]
|
|-
| [[Flashcache (Español)]]
| {{Grey|4}}
| [[Flashcache|Artículo original]]
|
|-
| [[Flashing BIOS from Linux (Español)]]
| {{Grey|4}}
| [[Flashing BIOS from Linux|Artículo original]]
|
|-
| [[Floppy disks (Español)]]
| {{Grey|4}}
| [[Floppy disks|Artículo original]]
|
|-
| [[FluidSynth (Español)]]
| {{Grey|4}}
| [[FluidSynth|Artículo original]]
|
|-
| [[Folding@home (Español)]]
| {{Grey|4}}
| [[Folding@home|Artículo original]]
|
|-
| [[Font configuration (Español)/Examples (Español)]]
| {{Grey|4}}
| [[Font configuration/Examples|Artículo original]]
|
|-
| [[Foremost (Español)]]
| {{Grey|4}}
| [[Foremost|Artículo original]]
|
|-
| [[Fortune (Español)]]
| {{Grey|4}}
| [[Fortune|Artículo original]]
|
|-
| [[Fprint (Español)]]
| {{Grey|4}}
| [[Fprint|Artículo original]]
|
|-
| [[FrankenWM (Español)]]
| {{Grey|4}}
| [[FrankenWM|Artículo original]]
|
|-
| [[Free Pascal package guidelines (Español)]]
| {{Grey|4}}
| [[Free Pascal package guidelines|Artículo original]]
|
|-
| [[FreeIPA (Español)]]
| {{Grey|4}}
| [[FreeIPA|Artículo original]]
|
|-
| [[FreeNX (Español)]]
| {{Grey|4}}
| [[FreeNX|Artículo original]]
|
|-
| [[Freeswitch (Español)]]
| {{Grey|4}}
| [[Freeswitch|Artículo original]]
|
|-
| [[Fsck (Español)]]
| {{Grey|4}}
| [[Fsck|Artículo original]]
|
|-
| [[FVWM (Español)]]
| {{Grey|4}}
| [[FVWM|Artículo original]]
|
|-
| [[Fwupd (Español)]]
| {{Grey|4}}
| [[Fwupd|Artículo original]]
|
|-
| [[Gajim (Español)]]
| {{Grey|4}}
| [[Gajim|Artículo original]]
|
|-
| [[Galera (Español)]]
| {{Grey|4}}
| [[Galera|Artículo original]]
|
|-
| [[Gamepad (Español)]]
| {{Grey|4}}
| [[Gamepad|Artículo original]]
|
|-
| [[Gaming (Español)]]
| {{Grey|4}}
| [[Gaming|Artículo original]]
|
|-
| [[Ganglia (Español)]]
| {{Grey|4}}
| [[Ganglia|Artículo original]]
|
|-
| [[Gapless Audio CD Creation from MP3s (Español)]]
| {{Grey|4}}
| [[Gapless Audio CD Creation from MP3s|Artículo original]]
|
|-
| [[Gcin (Español)]]
| {{Grey|4}}
| [[Gcin|Artículo original]]
|
|-
| [[Getmail (Español)]]
| {{Grey|4}}
| [[Getmail|Artículo original]]
|
|-
| [[GIMP (Español)/CMYK support (Español)]]
| {{Grey|4}}
| [[GIMP/CMYK support|Artículo original]]
|
|-
| [[Gitea (Español)]]
| {{Grey|4}}
| [[Gitea|Artículo original]]
|
|-
| [[Gitfs (Español)]]
| {{Grey|4}}
| [[Gitfs|Artículo original]]
|
|-
| [[GitLab (Español)]]
| {{Grey|4}}
| [[GitLab|Artículo original]]
|
|-
| [[Gitolite (Español)]]
| {{Grey|4}}
| [[Gitolite|Artículo original]]
|
|-
| [[Gitosis (Español)]]
| {{Grey|4}}
| [[Gitosis|Artículo original]]
|
|-
| [[Gitweb (Español)]]
| {{Grey|4}}
| [[Gitweb|Artículo original]]
|
|-
| [[Gm (Español)]]
| {{Grey|4}}
| [[Gm|Artículo original]]
|
|-
| [[Gmrun (Español)]]
| {{Grey|4}}
| [[Gmrun|Artículo original]]
|
|-
| [[GNOME package guidelines (Español)]]
| {{Grey|4}}
| [[GNOME package guidelines|Artículo original]]
|
|-
| [[GNOME (Español)/Evolution (Español)]]
| {{Grey|4}}
| [[GNOME/Evolution|Artículo original]]
|
|-
| [[GNOME (Español)/Flashback (Español)]]
| {{Grey|4}}
| [[GNOME/Flashback|Artículo original]]
|
|-
| [[GNOME (Español)/Tips and tricks (Español)]]
| {{Grey|4}}
| [[GNOME/Tips and tricks|Artículo original]]
|
|-
| [[GNOME (Español)/Troubleshooting (Español)]]
| {{Grey|4}}
| [[GNOME/Troubleshooting|Artículo original]]
|
|-
| [[GNS3 (Español)]]
| {{Grey|4}}
| [[GNS3|Artículo original]]
|
|-
| [[Go package guidelines (Español)]]
| {{Grey|4}}
| [[Go package guidelines|Artículo original]]
|
|-
| [[Gobi Broadband Modems (Español)]]
| {{Grey|4}}
| [[Gobi Broadband Modems|Artículo original]]
|
|-
| [[Godot Engine (Español)]]
| {{Grey|4}}
| [[Godot Engine|Artículo original]]
|
|-
| [[Gogs (Español)]]
| {{Grey|4}}
| [[Gogs|Artículo original]]
|
|-
| [[Google Drive (Español)]]
| {{Grey|4}}
| [[Google Drive|Artículo original]]
|
|-
| [[Google Earth (Español)]]
| {{Grey|4}}
| [[Google Earth|Artículo original]]
|
|-
| [[Google Summer of Code (Español)]]
| {{Grey|4}}
| [[Google Summer of Code|Artículo original]]
|
|-
| [[Gopher (Español)]]
| {{Grey|4}}
| [[Gopher|Artículo original]]
|
|-
| [[GPD Pocket (Español)]]
| {{Grey|4}}
| [[GPD Pocket|Artículo original]]
|
|-
| [[GPD Win (Español)]]
| {{Grey|4}}
| [[GPD Win|Artículo original]]
|
|-
| [[GPGPU (Español)]]
| {{Grey|4}}
| [[GPGPU|Artículo original]]
|
|-
| [[GPS (Español)]]
| {{Grey|4}}
| [[GPS|Artículo original]]
|
|-
| [[Graphviz (Español)]]
| {{Grey|4}}
| [[Graphviz|Artículo original]]
|
|-
| [[GROMACS (Español)]]
| {{Grey|4}}
| [[GROMACS|Artículo original]]
|
|-
| [[Groovebasin (Español)]]
| {{Grey|4}}
| [[Groovebasin|Artículo original]]
|
|-
| [[GRUB Legacy (Español)]]
| {{Grey|4}}
| [[GRUB Legacy|Artículo original]]
|
|-
| [[GRUB (Español)/EFI examples (Español)]]
| {{Grey|4}}
| [[GRUB/EFI examples|Artículo original]]
|
|-
| [[GTK+ (Español)/Development (Español)]]
| {{Grey|4}}
| [[GTK+/Development|Artículo original]]
|
|-
| [[Guix (Español)]]
| {{Grey|4}}
| [[Guix|Artículo original]]
|
|-
| [[Hadoop (Español)]]
| {{Grey|4}}
| [[Hadoop|Artículo original]]
|
|-
| [[HAproxy (Español)]]
| {{Grey|4}}
| [[HAproxy|Artículo original]]
|
|-
| [[Hard Drive Active Protection System (Español)]]
| {{Grey|4}}
| [[Hard Drive Active Protection System|Artículo original]]
|
|-
| [[Hardware video acceleration (Español)]]
| {{Grey|4}}
| [[Hardware video acceleration|Artículo original]]
|
|-
| [[HASEE K650D i7 D3 (Español)]]
| {{Grey|4}}
| [[HASEE K650D i7 D3|Artículo original]]
|
|-
| [[Haskell (Español)]]
| {{Grey|4}}
| [[Haskell|Artículo original]]
|
|-
| [[Haskell package guidelines (Español)]]
| {{Grey|4}}
| [[Haskell package guidelines|Artículo original]]
|
|-
| [[Hauppauge Nova-T Stick (Español)]]
| {{Grey|4}}
| [[Hauppauge Nova-T Stick|Artículo original]]
|
|-
| [[Haveged (Español)]]
| {{Grey|4}}
| [[Haveged|Artículo original]]
|
|-
| [[Hddtemp (Español)]]
| {{Grey|4}}
| [[Hddtemp|Artículo original]]
|
|-
| [[Hdparm (Español)]]
| {{Grey|4}}
| [[Hdparm|Artículo original]]
|
|-
| [[Herbstluftwm (Español)]]
| {{Grey|4}}
| [[Herbstluftwm|Artículo original]]
|
|-
| [[HexChat (Español)]]
| {{Grey|4}}
| [[HexChat|Artículo original]]
|
|-
| [[Hhvm (Español)]]
| {{Grey|4}}
| [[Hhvm|Artículo original]]
|
|-
| [[Hiawatha (Español)]]
| {{Grey|4}}
| [[Hiawatha|Artículo original]]
|
|-
| [[HiDPI (Español)]]
| {{Grey|4}}
| [[HiDPI|Artículo original]]
|
|-
| [[Home and End keys not working (Español)]]
| {{Grey|4}}
| [[Home and End keys not working|Artículo original]]
|
|-
| [[Howdy (Español)]]
| {{Grey|4}}
| [[Howdy|Artículo original]]
|
|-
| [[HP Chromebook 14 (Español)]]
| {{Grey|4}}
| [[HP Chromebook 14|Artículo original]]
|
|-
| [[HP EliteBook 2560p (Español)]]
| {{Grey|4}}
| [[HP EliteBook 2560p|Artículo original]]
|
|-
| [[HP EliteBook 2570p (Español)]]
| {{Grey|4}}
| [[HP EliteBook 2570p|Artículo original]]
|
|-
| [[HP EliteBook 840 G1 (Español)]]
| {{Grey|4}}
| [[HP EliteBook 840 G1|Artículo original]]
|
|-
| [[HP Envy 14 (Español)]]
| {{Grey|4}}
| [[HP Envy 14|Artículo original]]
|
|-
| [[HP Envy 15 (Español)]]
| {{Grey|4}}
| [[HP Envy 15|Artículo original]]
|
|-
| [[HP Envy 15t-j000 Quad Edition (Español)]]
| {{Grey|4}}
| [[HP Envy 15t-j000 Quad Edition|Artículo original]]
|
|-
| [[HP Envy 17 (Español)]]
| {{Grey|4}}
| [[HP Envy 17|Artículo original]]
|
|-
| [[HP ENVY TouchSmart 17-j113tx (Español)]]
| {{Grey|4}}
| [[HP ENVY TouchSmart 17-j113tx|Artículo original]]
|
|-
| [[HP Envy x360 13z-ag000 (Español)]]
| {{Grey|4}}
| [[HP Envy x360 13z-ag000|Artículo original]]
|
|-
| [[HP Envy x360 15-bq102ng (Español)]]
| {{Grey|4}}
| [[HP Envy x360 15-bq102ng|Artículo original]]
|
|-
| [[HP Pavilion dv6018 (Español)]]
| {{Grey|4}}
| [[HP Pavilion dv6018|Artículo original]]
|
|-
| [[HP Pavilion dv6179ea (Español)]]
| {{Grey|4}}
| [[HP Pavilion dv6179ea|Artículo original]]
|
|-
| [[HP Pro x2 612 G2 (Español)]]
| {{Grey|4}}
| [[HP Pro x2 612 G2|Artículo original]]
|
|-
| [[HP ProBook 430 G4 (Español)]]
| {{Grey|4}}
| [[HP ProBook 430 G4|Artículo original]]
|
|-
| [[HP ProBook 4330s (Español)]]
| {{Grey|4}}
| [[HP ProBook 4330s|Artículo original]]
|
|-
| [[HP ProBook 440 G4 (Español)]]
| {{Grey|4}}
| [[HP ProBook 440 G4|Artículo original]]
|
|-
| [[HP ProBook 4530s (Español)]]
| {{Grey|4}}
| [[HP ProBook 4530s|Artículo original]]
|
|-
| [[HP Spectre x360 13-ae005na (Español)]]
| {{Grey|4}}
| [[HP Spectre x360 13-ae005na|Artículo original]]
|
|-
| [[HP Spectre x360 13-4231ng (Español)]]
| {{Grey|4}}
| [[HP Spectre x360 13-4231ng|Artículo original]]
|
|-
| [[HP Spectre x360 13-w023dx (Español)]]
| {{Grey|4}}
| [[HP Spectre x360 13-w023dx|Artículo original]]
|
|-
| [[HP Spectre x360 15-ap012dx (Español)]]
| {{Grey|4}}
| [[HP Spectre x360 15-ap012dx|Artículo original]]
|
|-
| [[HP Spectre x360 15-ch025nd (Español)]]
| {{Grey|4}}
| [[HP Spectre x360 15-ch025nd|Artículo original]]
|
|-
| [[HP TouchSmart tx2 (Español)]]
| {{Grey|4}}
| [[HP TouchSmart tx2|Artículo original]]
|
|-
| [[HP ZBook Studio G3 (Español)]]
| {{Grey|4}}
| [[HP ZBook Studio G3|Artículo original]]
|
|-
| [[Hpfall (Español)]]
| {{Grey|4}}
| [[Hpfall|Artículo original]]
|
|-
| [[HTTP tunneling (Español)]]
| {{Grey|4}}
| [[HTTP tunneling|Artículo original]]
|
|-
| [[Huawei E1550 3G modem (Español)]]
| {{Grey|4}}
| [[Huawei E1550 3G modem|Artículo original]]
|
|-
| [[Huawei EG162G (Idea netsetter) (Español)]]
| {{Grey|4}}
| [[Huawei EG162G (Idea netsetter)|Artículo original]]
|
|-
| [[Humble Bundle (Español)]]
| {{Grey|4}}
| [[Humble Bundle|Artículo original]]
|
|-
| [[Hwclock (Español)]]
| {{Grey|4}}
| [[Hwclock|Artículo original]]
|
|-
| [[Hwdetect (Español)]]
| {{Grey|4}}
| [[Hwdetect|Artículo original]]
|
|-
| [[Hybrid graphics (Español)]]
| {{Grey|4}}
| [[Hybrid graphics|Artículo original]]
|
|-
| [[Hylafax (Español)]]
| {{Grey|4}}
| [[Hylafax|Artículo original]]
|
|-
| [[Hyper-V (Español)]]
| {{Grey|4}}
| [[Hyper-V|Artículo original]]
|
|-
| [[I2P (Español)]]
| {{Grey|4}}
| [[I2P|Artículo original]]
|
|-
| [[IBM ThinkPad X60s (Español)]]
| {{Grey|4}}
| [[IBM ThinkPad X60s|Artículo original]]
|
|-
| [[IBus (Español)]]
| {{Grey|4}}
| [[IBus|Artículo original]]
|
|-
| [[ICC profiles (Español)]]
| {{Grey|4}}
| [[ICC profiles|Artículo original]]
|
|-
| [[Icecast (Español)]]
| {{Grey|4}}
| [[Icecast|Artículo original]]
|
|-
| [[Icinga (Español)]]
| {{Grey|4}}
| [[Icinga|Artículo original]]
|
|-
| [[Identd (Español)]]
| {{Grey|4}}
| [[Identd|Artículo original]]
|
|-
| [[Identify damaged files (Español)]]
| {{Grey|4}}
| [[Identify damaged files|Artículo original]]
|
|-
| [[Idesk (Español)]]
| {{Grey|4}}
| [[Idesk|Artículo original]]
|
|-
| [[IMac (21.5-inch, Mid 2010) (Español)]]
| {{Grey|4}}
| [[IMac (21.5-inch, Mid 2010)|Artículo original]]
|
|-
| [[IMac Aluminum (Español)]]
| {{Grey|4}}
| [[IMac Aluminum|Artículo original]]
|
|-
| [[Imwheel (Español)]]
| {{Grey|4}}
| [[IMWheel|Artículo original]]
|
|-
| [[InfiniBand (Español)]]
| {{Grey|4}}
| [[InfiniBand|Artículo original]]
|
|-
| [[Info (Español)]]
| {{Grey|4}}
| [[Info|Artículo original]]
|
|-
| [[Inkscape (Español)]]
| {{Grey|4}}
| [[Inkscape|Artículo original]]
|
|-
| [[Input Japanese using uim (Español)]]
| {{Grey|4}}
| [[Input Japanese using uim|Artículo original]]
|
|-
| [[InspIRCd (Español)]]
| {{Grey|4}}
| [[InspIRCd|Artículo original]]
|
|-
| [[Installing Arch Linux on ZFS (Español)]]
| {{Grey|4}}
| [[Installing Arch Linux on ZFS|Artículo original]]
|
|-
| [[VMWare vCLI (Español)]]
| {{Grey|4}}
| [[VMWare vCLI|Artículo original]]
|
|-
| [[Installing with Fake RAID (Español)]]
| {{Grey|4}}
| [[Installing with Fake RAID|Artículo original]]
|
|-
| [[Insync (Español)]]
| {{Grey|4}}
| [[Insync|Artículo original]]
|
|-
| [[Intel GVT-g (Español)]]
| {{Grey|4}}
| [[Intel GVT-g|Artículo original]]
|
|-
| [[Intel NUC (Español)]]
| {{Grey|4}}
| [[Intel NUC|Artículo original]]
|
|-
| [[Internet sharing (Español)]]
| {{Grey|4}}
| [[Internet sharing|Artículo original]]
|
|-
| [[InvoicePlane (Español)]]
| {{Grey|4}}
| [[InvoicePlane|Artículo original]]
|
|-
| [[IOS (Español)]]
| {{Grey|4}}
| [[IOS|Artículo original]]
|
|-
| [[IPFS (Español)]]
| {{Grey|4}}
| [[IPFS|Artículo original]]
|
|-
| [[IPhone tethering (Español)]]
| {{Grey|4}}
| [[IPhone tethering|Artículo original]]
|
|-
| [[IPv6 tunnel broker setup (Español)]]
| {{Grey|4}}
| [[IPv6 tunnel broker setup|Artículo original]]
|
|-
| [[Irssi (Español)/irssi-otr (Español)]]
| {{Grey|4}}
| [[Irssi/irssi-otr|Artículo original]]
|
|-
| [[ISCSI (Español)/Boot (Español)]]
| {{Grey|4}}
| [[ISCSI/Boot|Artículo original]]
|
|-
| [[ISCSI (Español)/LIO (Español)]]
| {{Grey|4}}
| [[ISCSI/LIO|Artículo original]]
|
|-
| [[Isync (Español)]]
| {{Grey|4}}
| [[Isync|Artículo original]]
|
|-
| [[Iwd (Español)]]
| {{Grey|4}}
| [[Iwd|Artículo original]]
|
|-
| [[Jalbum (Español)]]
| {{Grey|4}}
| [[Jalbum|Artículo original]]
|
|-
| [[Java package guidelines (Español)]]
| {{Grey|4}}
| [[Java package guidelines|Artículo original]]
|
|-
| [[Java Runtime Environment fonts (Español)]]
| {{Grey|4}}
| [[Java Runtime Environment fonts|Artículo original]]
|
|-
| [[JDBC and MySQL (Español)]]
| {{Grey|4}}
| [[JDBC and MySQL|Artículo original]]
|
|-
| [[JDownloader (Español)]]
| {{Grey|4}}
| [[JDownloader|Artículo original]]
|
|-
| [[Jenkins (Español)]]
| {{Grey|4}}
| [[Jenkins|Artículo original]]
|
|-
| [[JFS (Español)]]
| {{Grey|4}}
| [[JFS|Artículo original]]
|
|-
| [[JHBuild (Español)]]
| {{Grey|4}}
| [[JHBuild|Artículo original]]
|
|-
| [[Jinzora (Español)]]
| {{Grey|4}}
| [[Jinzora|Artículo original]]
|
|-
| [[Joomla (Español)]]
| {{Grey|4}}
| [[Joomla|Artículo original]]
|
|-
| [[Joy2key (Español)]]
| {{Grey|4}}
| [[Joy2key|Artículo original]]
|
|-
| [[JWM (Español)]]
| {{Grey|4}}
| [[JWM|Artículo original]]
|
|-
| [[Kakoune (Español)]]
| {{Grey|4}}
| [[Kakoune|Artículo original]]
|
|-
| [[KDE package guidelines (Español)]]
| {{Grey|4}}
| [[KDE package guidelines|Artículo original]]
|
|-
| [[Kdump (Español)]]
| {{Grey|4}}
| [[Kdump|Artículo original]]
|
|-
| [[KeePass (Español)]]
| {{Grey|4}}
| [[KeePass|Artículo original]]
|
|-
| [[Kerbal Space Program (Español)]]
| {{Grey|4}}
| [[Kerbal Space Program|Artículo original]]
|
|-
| [[Kerberos (Español)]]
| {{Grey|4}}
| [[Kerberos|Artículo original]]
|
|-
| [[Kernel live patching (Español)]]
| {{Grey|4}}
| [[Kernel live patching|Artículo original]]
|
|-
| [[Kernel module package guidelines (Español)]]
| {{Grey|4}}
| [[Kernel module package guidelines|Artículo original]]
|
|-
| [[Kernel (Español)/Arch Build System (Español)]]
| {{Grey|4}}
| [[Kernel/Arch build system|Artículo original]]
|
|-
| [[Kernel (Español)/Traditional compilation (Español)]]
| {{Grey|4}}
| [[Kernel/Traditional compilation|Artículo original]]
|
|-
| [[Kexec (Español)]]
| {{Grey|4}}
| [[Kexec|Artículo original]]
|
|-
| [[Keybase (Español)]]
| {{Grey|4}}
| [[Keybase|Artículo original]]
|
|-
| [[Keyboard backlight (Español)]]
| {{Grey|4}}
| [[Keyboard backlight|Artículo original]]
|
|-
| [[Keyboard input (Español)]]
| {{Grey|4}}
| [[Keyboard input|Artículo original]]
|
|-
| [[KMSCON (Español)]]
| {{Grey|4}}
| [[KMSCON|Artículo original]]
|
|-
| [[Knot Resolver (Español)]]
| {{Grey|4}}
| [[Knot Resolver|Artículo original]]
|
|-
| [[Kodi (Español)]]
| {{Grey|4}}
| [[Kodi|Artículo original]]
|
|-
| [[KornShell (Español)]]
| {{Grey|4}}
| [[KornShell|Artículo original]]
|
|-
| [[KRunner (Español)]]
| {{Grey|4}}
| [[KRunner|Artículo original]]
|
|-
| [[Kubernetes (Español)]]
| {{Grey|4}}
| [[Kubernetes|Artículo original]]
|
|-
| [[Laptop Mode Tools (Español)]]
| {{Grey|4}}
| [[Laptop Mode Tools|Artículo original]]
|
|-
| [[Laptop (Español)/Acer (Español)]]
| {{Grey|4}}
| [[Laptop/Acer|Artículo original]]
|
|-
| [[Laptop (Español)/Apple (Español)]]
| {{Grey|4}}
| [[Laptop/Apple|Artículo original]]
|
|-
| [[Laptop (Español)/ASUS (Español)]]
| {{Grey|4}}
| [[Laptop/ASUS|Artículo original]]
|
|-
| [[Laptop (Español)/Dell (Español)]]
| {{Grey|4}}
| [[Laptop/Dell|Artículo original]]
|
|-
| [[Laptop (Español)/Fujitsu (Español)]]
| {{Grey|4}}
| [[Laptop/Fujitsu|Artículo original]]
|
|-
| [[Laptop (Español)/HP (Español)]]
| {{Grey|4}}
| [[Laptop/HP|Artículo original]]
|
|-
| [[Laptop (Español)/Lenovo (Español)]]
| {{Grey|4}}
| [[Laptop/Lenovo|Artículo original]]
|
|-
| [[Laptop (Español)/MSI (Español)]]
| {{Grey|4}}
| [[Laptop/MSI|Artículo original]]
|
|-
| [[Laptop (Español)/Other (Español)]]
| {{Grey|4}}
| [[Laptop/Other|Artículo original]]
|
|-
| [[Laptop (Español)/Samsung (Español)]]
| {{Grey|4}}
| [[Laptop/Samsung|Artículo original]]
|
|-
| [[Laptop (Español)/Sony (Español)]]
| {{Grey|4}}
| [[Laptop/Sony|Artículo original]]
|
|-
| [[Laptop (Español)/Toshiba (Español)]]
| {{Grey|4}}
| [[Laptop/Toshiba|Artículo original]]
|
|-
| [[Lattice Diamond (Español)]]
| {{Grey|4}}
| [[Lattice Diamond|Artículo original]]
|
|-
| [[Launchpad MSP430G2 (Español)]]
| {{Grey|4}}
| [[Launchpad MSP430G2|Artículo original]]
|
|-
| [[LDAP authentication (Español)]]
| {{Grey|4}}
| [[LDAP authentication|Artículo original]]
|
|-
| [[LDAP Hosts (Español)]]
| {{Grey|4}}
| [[LDAP Hosts|Artículo original]]
|
|-
| [[Ledger (Español)]]
| {{Grey|4}}
| [[Ledger|Artículo original]]
|
|-
| [[Lemonbar (Español)]]
| {{Grey|4}}
| [[Lemonbar|Artículo original]]
|
|-
| [[Lenovo IdeaPad 720s (Español)]]
| {{Grey|4}}
| [[Lenovo IdeaPad 720s|Artículo original]]
|
|-
| [[Lenovo IdeaPad 720s (AMD) (Español)]]
| {{Grey|4}}
| [[Lenovo IdeaPad 720s (AMD)|Artículo original]]
|
|-
| [[Lenovo IdeaPad Flex 10 (Español)]]
| {{Grey|4}}
| [[Lenovo IdeaPad Flex 10|Artículo original]]
|
|-
| [[Lenovo IdeaPad S10-3 (Español)]]
| {{Grey|4}}
| [[Lenovo IdeaPad S10-3|Artículo original]]
|
|-
| [[Lenovo IdeaPad s10-3t (Español)]]
| {{Grey|4}}
| [[Lenovo IdeaPad s10-3t|Artículo original]]
|
|-
| [[Lenovo IdeaPad S205 (Español)]]
| {{Grey|4}}
| [[Lenovo IdeaPad S205|Artículo original]]
|
|-
| [[Lenovo IdeaPad S400u (Español)]]
| {{Grey|4}}
| [[Lenovo IdeaPad S400u|Artículo original]]
|
|-
| [[Lenovo IdeaPad U330p (Español)]]
| {{Grey|4}}
| [[Lenovo IdeaPad U330p|Artículo original]]
|
|-
| [[Lenovo IdeaPad U430 Touch (Español)]]
| {{Grey|4}}
| [[Lenovo IdeaPad U430 Touch|Artículo original]]
|
|-
| [[Lenovo IdeaPad Y480 (Español)]]
| {{Grey|4}}
| [[Lenovo IdeaPad Y480|Artículo original]]
|
|-
| [[Lenovo IdeaPad Y560 (Español)]]
| {{Grey|4}}
| [[Lenovo IdeaPad Y560|Artículo original]]
|
|-
| [[Lenovo IdeaPad Yoga 13 (Español)]]
| {{Grey|4}}
| [[Lenovo IdeaPad Yoga 13|Artículo original]]
|
|-
| [[Lenovo IdeaPad Yoga 2 Pro (Español)]]
| {{Grey|4}}
| [[Lenovo IdeaPad Yoga 2 Pro|Artículo original]]
|
|-
| [[Lenovo IdeaPad Yoga 900 (Español)]]
| {{Grey|4}}
| [[Lenovo IdeaPad Yoga 900|Artículo original]]
|
|-
| [[Lenovo S20-30 (Español)]]
| {{Grey|4}}
| [[Lenovo S20-30|Artículo original]]
|
|-
| [[Lenovo ThinkPad Edge 13 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad Edge 13|Artículo original]]
|
|-
| [[Lenovo ThinkPad Edge E130 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad Edge E130|Artículo original]]
|
|-
| [[Lenovo ThinkPad Edge E330 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad Edge E330|Artículo original]]
|
|-
| [[Lenovo ThinkPad Edge E430 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad Edge E430|Artículo original]]
|
|-
| [[Lenovo ThinkPad Edge E440 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad Edge E440|Artículo original]]
|
|-
| [[Lenovo ThinkPad Edge E455 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad Edge E455|Artículo original]]
|
|-
| [[Lenovo ThinkPad Edge E555 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad Edge E555|Artículo original]]
|
|-
| [[Lenovo ThinkPad Helix (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad Helix|Artículo original]]
|
|-
| [[Lenovo ThinkPad Helix 2nd Gen (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad Helix 2nd Gen|Artículo original]]
|
|-
| [[Lenovo ThinkPad P40 Yoga (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad P40 Yoga|Artículo original]]
|
|-
| [[Lenovo ThinkPad P50 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad P50|Artículo original]]
|
|-
| [[Lenovo ThinkPad P70 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad P70|Artículo original]]
|
|-
| [[Lenovo ThinkPad S440 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad S440|Artículo original]]
|
|-
| [[Lenovo ThinkPad T25 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad T25|Artículo original]]
|
|-
| [[Lenovo ThinkPad T400 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad T400|Artículo original]]
|
|-
| [[Lenovo ThinkPad T430s (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad T430s|Artículo original]]
|
|-
| [[Lenovo ThinkPad T440s (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad T440s|Artículo original]]
|
|-
| [[Lenovo ThinkPad T450s (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad T450s|Artículo original]]
|
|-
| [[Lenovo ThinkPad T460p (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad T460p|Artículo original]]
|
|-
| [[Lenovo ThinkPad T460s (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad T460s|Artículo original]]
|
|-
| [[Lenovo ThinkPad T470 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad T470|Artículo original]]
|
|-
| [[Lenovo ThinkPad T470s (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad T470s|Artículo original]]
|
|-
| [[Lenovo ThinkPad T480 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad T480|Artículo original]]
|
|-
| [[Lenovo ThinkPad T480s (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad T480s|Artículo original]]
|
|-
| [[Lenovo ThinkPad T520 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad T520|Artículo original]]
|
|-
| [[Lenovo ThinkPad T530 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad T530|Artículo original]]
|
|-
| [[Lenovo ThinkPad T550 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad T550|Artículo original]]
|
|-
| [[Lenovo ThinkPad T570 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad T570|Artículo original]]
|
|-
| [[Lenovo ThinkPad T61 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad T61|Artículo original]]
|
|-
| [[Lenovo ThinkPad W520 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad W520|Artículo original]]
|
|-
| [[Lenovo ThinkPad X1 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad X1|Artículo original]]
|
|-
| [[Lenovo ThinkPad X1 Carbon (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad X1 Carbon|Artículo original]]
|
|-
| [[Lenovo ThinkPad X1 Carbon (Gen 2) (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad X1 Carbon (Gen 2)|Artículo original]]
|
|-
| [[Lenovo ThinkPad X1 Carbon (Gen 3) (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad X1 Carbon (Gen 3)|Artículo original]]
|
|-
| [[Lenovo ThinkPad X1 Carbon (Gen 4) (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad X1 Carbon (Gen 4)|Artículo original]]
|
|-
| [[Lenovo ThinkPad X1 Carbon (Gen 5) (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad X1 Carbon (Gen 5)|Artículo original]]
|
|-
| [[Lenovo ThinkPad X1 Carbon (Gen 6) (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad X1 Carbon (Gen 6)|Artículo original]]
|
|-
| [[Lenovo ThinkPad X120e (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad X120e|Artículo original]]
|
|-
| [[Lenovo ThinkPad X200 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad X200|Artículo original]]
|
|-
| [[Lenovo ThinkPad X201 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad X201|Artículo original]]
|
|-
| [[Lenovo ThinkPad X201 Tablet (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad X201 Tablet|Artículo original]]
|
|-
| [[Lenovo ThinkPad X220 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad X220|Artículo original]]
|
|-
| [[Lenovo ThinkPad X230 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad X230|Artículo original]]
|
|-
| [[Lenovo ThinkPad X240 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad X240|Artículo original]]
|
|-
| [[Lenovo ThinkPad X250 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad X250|Artículo original]]
|
|-
| [[Lenovo ThinkPad X260 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad X260|Artículo original]]
|
|-
| [[Lenovo ThinkPad X60 Tablet (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad X60 Tablet|Artículo original]]
|
|-
| [[Lenovo ThinkPad Yoga 260 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad Yoga 260|Artículo original]]
|
|-
| [[Lenovo ThinkPad Yoga S1 (Español)]]
| {{Grey|4}}
| [[Lenovo ThinkPad Yoga S1|Artículo original]]
|
|-
| [[Lenovo Yoga 2 11 (Español)]]
| {{Grey|4}}
| [[Lenovo Yoga 2 11|Artículo original]]
|
|-
| [[Libcanberra (Español)]]
| {{Grey|4}}
| [[Libcanberra|Artículo original]]
|
|-
| [[Libvirt (Español)]]
| {{Grey|4}}
| [[Libvirt|Artículo original]]
|
|-
| [[Limits.conf (Español)]]
| {{Grey|4}}
| [[Limits.conf|Artículo original]]
|
|-
| [[Linux Containers (Español)]]
| {{Grey|4}}
| [[Linux Containers|Artículo original]]
|
|-
| [[LinuxSampler (Español)]]
| {{Grey|4}}
| [[LinuxSampler|Artículo original]]
|
|-
| [[LIRC (Español)]]
| {{Grey|4}}
| [[LIRC|Artículo original]]
|
|-
| [[LIRC (Español)/Quick start guide (Español)]]
| {{Grey|4}}
| [[LIRC/Quick start guide|Artículo original]]
|
|-
| [[Lisp package guidelines (Español)]]
| {{Grey|4}}
| [[Lisp package guidelines|Artículo original]]
|
|-
| [[Llpp (Español)]]
| {{Grey|4}}
| [[Llpp|Artículo original]]
|
|-
| [[LMMS (Español)]]
| {{Grey|4}}
| [[LMMS|Artículo original]]
|
|-
| [[Loadkeys (Español)]]
| {{Grey|4}}
| [[Loadkeys|Artículo original]]
|
|-
| [[Localectl (Español)]]
| {{Grey|4}}
| [[Localectl|Artículo original]]
|
|-
| [[Locale-gen (Español)]]
| {{Grey|4}}
| [[Locale-gen|Artículo original]]
|
|-
| [[Localization (Español)]]
| {{Grey|4}}
| [[Localization|Artículo original]]
|
|-
| [[Localization (Español)/Sinhalese (Español)]]
| {{Grey|4}}
| [[Localization/Sinhalese|Artículo original]]
|
|-
| [[Logitech G13 (Español)]]
| {{Grey|4}}
| [[Logitech G13|Artículo original]]
|
|-
| [[Logitech Gaming Keyboards (Español)]]
| {{Grey|4}}
| [[Logitech Gaming Keyboards|Artículo original]]
|
|-
| [[Logitech M570 (Español)]]
| {{Grey|4}}
| [[Logitech M570|Artículo original]]
|
|-
| [[Logitech Marble Mouse (Español)]]
| {{Grey|4}}
| [[Logitech Marble Mouse|Artículo original]]
|
|-
| [[Logitech MX Master (Español)]]
| {{Grey|4}}
| [[Logitech MX Master|Artículo original]]
|
|-
| [[Logitech MX Revolution (Español)]]
| {{Grey|4}}
| [[Logitech MX Revolution|Artículo original]]
|
|-
| [[Logitech Unifying Receiver (Español)]]
| {{Grey|4}}
| [[Logitech Unifying Receiver|Artículo original]]
|
|-
| [[Logrotate (Español)]]
| {{Grey|4}}
| [[Logrotate|Artículo original]]
|
|-
| [[Logwatch (Español)]]
| {{Grey|4}}
| [[Logwatch|Artículo original]]
|
|-
| [[Lp (Español)]]
| {{Grey|4}}
| [[Lp|Artículo original]]
|
|-
| [[LPRng (Español)]]
| {{Grey|4}}
| [[LPRng|Artículo original]]
|
|-
| [[Lrzip (Español)]]
| {{Grey|4}}
| [[Lrzip|Artículo original]]
|
|-
| [[Lua (Español)]]
| {{Grey|4}}
| [[Lua|Artículo original]]
|
|-
| [[Luakit (Español)]]
| {{Grey|4}}
| [[Luakit|Artículo original]]
|
|-
| [[LXDM (Español)]]
| {{Grey|4}}
| [[LXDM|Artículo original]]
|
|-
| [[LXQt (Español)]]
| {{Grey|4}}
| [[LXQt|Artículo original]]
|
|-
| [[Mac (Español)]]
| {{Grey|4}}
| [[Mac|Artículo original]]
|
|-
| [[MacBookPro10,x (Español)]]
| {{Grey|4}}
| [[MacBookPro10,x|Artículo original]]
|
|-
| [[MacBookPro11,x (Español)]]
| {{Grey|4}}
| [[MacBookPro11,x|Artículo original]]
|
|-
| [[MacBookPro8,1/8,2/8,3 (2011) (Español)]]
| {{Grey|4}}
| [[MacBookPro8,1/8,2/8,3 (2011)|Artículo original]]
|
|-
| [[MacBookPro9,2 (Mid-2012) (Español)]]
| {{Grey|4}}
| [[MacBookPro9,2 (Mid-2012)|Artículo original]]
|
|-
| [[Machine-check exception (Español)]]
| {{Grey|4}}
| [[Machine-check exception|Artículo original]]
|
|-
| [[Mad Catz Mouse (Español)]]
| {{Grey|4}}
| [[Mad Catz Mouse|Artículo original]]
|
|-
| [[Mailman (Español)]]
| {{Grey|4}}
| [[Mailman|Artículo original]]
|
|-
| [[Makepkg-optimize (Español)]]
| {{Grey|4}}
| [[Makepkg-optimize|Artículo original]]
|
|-
| [[MantisBT (Español)]]
| {{Grey|4}}
| [[MantisBT|Artículo original]]
|
|-
| [[Map scancodes to keycodes (Español)]]
| {{Grey|4}}
| [[Map scancodes to keycodes|Artículo original]]
|
|-
| [[MariaDB (Español)]]
| {{Grey|4}}
| [[MariaDB|Artículo original]]
|
|-
| [[Markdown (Español)]]
| {{Grey|4}}
| [[Markdown|Artículo original]]
|
|-
| [[Mathematica (Español)]]
| {{Grey|4}}
| [[Mathematica|Artículo original]]
|
|-
| [[MathJax (Español)]]
| {{Grey|4}}
| [[MathJax|Artículo original]]
|
|-
| [[MATLAB (Español)]]
| {{Grey|4}}
| [[MATLAB|Artículo original]]
|
|-
| [[Matrix (Español)]]
| {{Grey|4}}
| [[Matrix|Artículo original]]
|
|-
| [[Mattermost (Español)]]
| {{Grey|4}}
| [[Mattermost|Artículo original]]
|
|-
| [[Mbed TLS (Español)]]
| {{Grey|4}}
| [[Mbed TLS|Artículo original]]
|
|-
| [[Media Transfer Protocol (Español)]]
| {{Grey|4}}
| [[Media Transfer Protocol|Artículo original]]
|
|-
| [[MediaTomb (Español)]]
| {{Grey|4}}
| [[MediaTomb|Artículo original]]
|
|-
| [[Mercurial (Español)]]
| {{Grey|4}}
| [[Mercurial|Artículo original]]
|
|-
| [[Metasploit Framework (Español)]]
| {{Grey|4}}
| [[Metasploit Framework|Artículo original]]
|
|-
| [[Microsoft Surface Book 2 (Español)]]
| {{Grey|4}}
| [[Microsoft Surface Book 2|Artículo original]]
|
|-
| [[Microsoft Surface Pro 3 (Español)]]
| {{Grey|4}}
| [[Microsoft Surface Pro 3|Artículo original]]
|
|-
| [[MIDI (Español)]]
| {{Grey|4}}
| [[MIDI|Artículo original]]
|
|-
| [[Midnight Commander (Español)]]
| {{Grey|4}}
| [[Midnight Commander|Artículo original]]
|
|-
| [[Minecraft (Español)]]
| {{Grey|4}}
| [[Minecraft|Artículo original]]
|
|-
| [[MinGW package guidelines (Español)]]
| {{Grey|4}}
| [[MinGW package guidelines|Artículo original]]
|
|-
| [[Minimal initramfs (Español)]]
| {{Grey|4}}
| [[Minimal initramfs|Artículo original]]
|
|-
| [[Mkosi (Español)]]
| {{Grey|4}}
| [[Mkosi|Artículo original]]
|
|-
| [[Mnemosyne (Español)]]
| {{Grey|4}}
| [[Mnemosyne|Artículo original]]
|
|-
| [[Mobile phone (Español)]]
| {{Grey|4}}
| [[Mobile phone|Artículo original]]
|
|-
| [[Modprobed-db (Español)]]
| {{Grey|4}}
| [[Modprobed-db|Artículo original]]
|
|-
| [[MongoDB (Español)]]
| {{Grey|4}}
| [[MongoDB|Artículo original]]
|
|-
| [[Monit (Español)]]
| {{Grey|4}}
| [[Monit|Artículo original]]
|
|-
| [[Monitorix (Español)]]
| {{Grey|4}}
| [[Monitorix|Artículo original]]
|
|-
| [[Moodle (Español)]]
| {{Grey|4}}
| [[Moodle|Artículo original]]
|
|-
| [[Mooltipass (Español)]]
| {{Grey|4}}
| [[Mooltipass|Artículo original]]
|
|-
| [[Mouse acceleration (Español)]]
| {{Grey|4}}
| [[Mouse acceleration|Artículo original]]
|
|-
| [[Mouse polling rate (Español)]]
| {{Grey|4}}
| [[Mouse polling rate|Artículo original]]
|
|-
| [[Moving an existing install into (or out of) a virtual machine (Español)]]
| {{Grey|4}}
| [[Moving an existing install into (or out of) a virtual machine|Artículo original]]
|
|-
| [[Mozc (Español)]]
| {{Grey|4}}
| [[Mozc|Artículo original]]
|
|-
| [[MSI GE63VR (Español)]]
| {{Grey|4}}
| [[MSI GE63VR|Artículo original]]
|
|-
| [[MSI GS65 (Español)]]
| {{Grey|4}}
| [[MSI GS65|Artículo original]]
|
|-
| [[MSI GS73VR (Español)]]
| {{Grey|4}}
| [[MSI GS73VR|Artículo original]]
|
|-
| [[MSI GT72-6QE (Español)]]
| {{Grey|4}}
| [[MSI GT72-6QE|Artículo original]]
|
|-
| [[Multihead (Español)]]
| {{Grey|4}}
| [[Multihead|Artículo original]]
|
|-
| [[Multi-pointer X (Español)]]
| {{Grey|4}}
| [[Multi-pointer X|Artículo original]]
|
|-
| [[Multitouch displays (Español)]]
| {{Grey|4}}
| [[Multitouch displays|Artículo original]]
|
|-
| [[Mumble (Español)]]
| {{Grey|4}}
| [[Mumble|Artículo original]]
|
|-
| [[Munin (Español)]]
| {{Grey|4}}
| [[Munin|Artículo original]]
|
|-
| [[MuPDF (Español)]]
| {{Grey|4}}
| [[MuPDF|Artículo original]]
|
|-
| [[Music Player Daemon (Español)/Tips and tricks (Español)]]
| {{Grey|4}}
| [[Music Player Daemon/Tips and tricks|Artículo original]]
|
|-
| [[MythTV (Español)]]
| {{Grey|4}}
| [[MythTV|Artículo original]]
|
|-
| [[Nagios (Español)]]
| {{Grey|4}}
| [[Nagios|Artículo original]]
|
|-
| [[Namcap (Español)]]
| {{Grey|4}}
| [[Namcap|Artículo original]]
|
|-
| [[NanoPi M1 (Español)]]
| {{Grey|4}}
| [[NanoPi M1|Artículo original]]
|
|-
| [[Nemo (Español)]]
| {{Grey|4}}
| [[Nemo|Artículo original]]
|
|-
| [[Netatalk (Español)]]
| {{Grey|4}}
| [[Netatalk|Artículo original]]
|
|-
| [[Netboot (Español)]]
| {{Grey|4}}
| [[Netboot|Artículo original]]
|
|-
| [[Netconsole (Español)]]
| {{Grey|4}}
| [[Netconsole|Artículo original]]
|
|-
| [[Netdata (Español)]]
| {{Grey|4}}
| [[Netdata|Artículo original]]
|
|-
| [[Network bridge (Español)]]
| {{Grey|4}}
| [[Network bridge|Artículo original]]
|
|-
| [[Network Debugging (Español)]]
| {{Grey|4}}
| [[Network Debugging|Artículo original]]
|
|-
| [[Network Security Services (Español)]]
| {{Grey|4}}
| [[Network Security Services|Artículo original]]
|
|-
| [[Network UPS Tools (Español)]]
| {{Grey|4}}
| [[Network UPS Tools|Artículo original]]
|
|-
| [[Newsboat (Español)]]
| {{Grey|4}}
| [[Newsboat|Artículo original]]
|
|-
| [[Nextcloud (Español)]]
| {{Grey|4}}
| [[Nextcloud|Artículo original]]
|
|-
| [[NFS (Español)/Troubleshooting (Español)]]
| {{Grey|4}}
| [[NFS/Troubleshooting|Artículo original]]
|
|-
| [[Nginx (Español)]]
| {{Grey|4}}
| [[Nginx|Artículo original]]
|
|-
| [[Nimf (Español)]]
| {{Grey|4}}
| [[Nimf|Artículo original]]
|
|-
| [[NIS (Español)]]
| {{Grey|4}}
| [[NIS|Artículo original]]
|
|-
| [[Nmap (Español)]]
| {{Grey|4}}
| [[Nmap|Artículo original]]
|
|-
| [[Nmh (Español)]]
| {{Grey|4}}
| [[Nmh|Artículo original]]
|
|-
| [[Node.js (Español)]]
| {{Grey|4}}
| [[Node.js|Artículo original]]
|
|-
| [[Node.js package guidelines (Español)]]
| {{Grey|4}}
| [[Node.js package guidelines|Artículo original]]
|
|-
| [[Nodm (Español)]]
| {{Grey|4}}
| [[Nodm|Artículo original]]
|
|-
| [[NoMachine (Español)]]
| {{Grey|4}}
| [[NoMachine|Artículo original]]
|
|-
| [[Nonfree applications package guidelines (Español)]]
| {{Grey|4}}
| [[Nonfree applications package guidelines|Artículo original]]
|
|-
| [[Notion (Español)]]
| {{Grey|4}}
| [[Notion|Artículo original]]
|
|-
| [[Notmuch (Español)]]
| {{Grey|4}}
| [[Notmuch|Artículo original]]
|
|-
| [[Npm (Español)]]
| {{Grey|4}}
| [[Npm|Artículo original]]
|
|-
| [[Nsd (Español)]]
| {{Grey|4}}
| [[NSD|Artículo original]]
|
|-
| [[NVIDIA Optimus (Español)]]
| {{Grey|4}}
| [[NVIDIA Optimus|Artículo original]]
|
|-
| [[NVIDIA (Español)/Tips and tricks (Español)]]
| {{Grey|4}}
| [[NVIDIA/Tips and tricks|Artículo original]]
|
|-
| [[NVIDIA (Español)/Troubleshooting (Español)]]
| {{Grey|4}}
| [[NVIDIA/Troubleshooting|Artículo original]]
|
|-
| [[Nvidia-xrun (Español)]]
| {{Grey|4}}
| [[Nvidia-xrun|Artículo original]]
|
|-
| [[NZBGet (Español)]]
| {{Grey|4}}
| [[NZBGet|Artículo original]]
|
|-
| [[ObexFTP (Español)]]
| {{Grey|4}}
| [[ObexFTP|Artículo original]]
|
|-
| [[Oblogout (Español)]]
| {{Grey|4}}
| [[Oblogout|Artículo original]]
|
|-
| [[OCaml package guidelines (Español)]]
| {{Grey|4}}
| [[OCaml package guidelines|Artículo original]]
|
|-
| [[Ocrdesktop (Español)]]
| {{Grey|4}}
| [[Ocrdesktop|Artículo original]]
|
|-
| [[OCSP (Español)]]
| {{Grey|4}}
| [[OCSP|Artículo original]]
|
|-
| [[Octave (Español)]]
| {{Grey|4}}
| [[Octave|Artículo original]]
|
|-
| [[Oculus Rift (Español)]]
| {{Grey|4}}
| [[Oculus Rift|Artículo original]]
|
|-
| [[Odoo (Español)]]
| {{Grey|4}}
| [[Odoo|Artículo original]]
|
|-
| [[Official repositories web interface (Español)]]
| {{Grey|4}}
| [[Official repositories web interface|Artículo original]]
|
|-
| [[Offline installation (Español)]]
| {{Grey|4}}
| [[Offline installation|Artículo original]]
|
|-
| [[OfflineIMAP (Español)]]
| {{Grey|4}}
| [[OfflineIMAP|Artículo original]]
|
|-
| [[Oidentd (Español)]]
| {{Grey|4}}
| [[Oidentd|Artículo original]]
|
|-
| [[One Time PassWord (Español)]]
| {{Grey|4}}
| [[One Time PassWord|Artículo original]]
|
|-
| [[Onlyoffice Documentserver (Español)]]
| {{Grey|4}}
| [[Onlyoffice Documentserver|Artículo original]]
|
|-
| [[Oolite (Español)]]
| {{Grey|4}}
| [[Oolite|Artículo original]]
|
|-
| [[Open Database Connectivity (Español)]]
| {{Grey|4}}
| [[Open Database Connectivity|Artículo original]]
|
|-
| [[Open Watcom (Español)]]
| {{Grey|4}}
| [[Open Watcom|Artículo original]]
|
|-
| [[OpenConnect (Español)]]
| {{Grey|4}}
| [[OpenConnect|Artículo original]]
|
|-
| [[OpenDKIM (Español)]]
| {{Grey|4}}
| [[OpenDKIM|Artículo original]]
|
|-
| [[OpenDMARC (Español)]]
| {{Grey|4}}
| [[OpenDMARC|Artículo original]]
|
|-
| [[Openfire (Español)]]
| {{Grey|4}}
| [[Openfire|Artículo original]]
|
|-
| [[Open-iSCSI (Español)]]
| {{Grey|4}}
| [[Open-iSCSI|Artículo original]]
|
|-
| [[OpenLDAP (Español)]]
| {{Grey|4}}
| [[OpenLDAP|Artículo original]]
|
|-
| [[OpenNTPD (Español)]]
| {{Grey|4}}
| [[OpenNTPD|Artículo original]]
|
|-
| [[OpenRC (Español)]]
| {{Grey|4}}
| [[OpenRC|Artículo original]]
|
|-
| [[OpenSMTPD (Español)]]
| {{Grey|4}}
| [[OpenSMTPD|Artículo original]]
|
|-
| [[Openswan L2TP/IPsec VPN client setup (Español)]]
| {{Grey|4}}
| [[Openswan L2TP/IPsec VPN client setup|Artículo original]]
|
|-
| [[OpenTTD (Español)]]
| {{Grey|4}}
| [[OpenTTD|Artículo original]]
|
|-
| [[OpenVAS (Español)]]
| {{Grey|4}}
| [[OpenVAS|Artículo original]]
|
|-
| [[OpenVPN (Español)]]
| {{Grey|4}}
| [[OpenVPN|Artículo original]]
|
|-
| [[OpenVPN Bridge (Español)]]
| {{Grey|4}}
| [[OpenVPN Bridge|Artículo original]]
|
|-
| [[OpenVPN Checklist Guide (Español)]]
| {{Grey|4}}
| [[OpenVPN Checklist Guide|Artículo original]]
|
|-
| [[OpenVPN client in Linux Containers (Español)]]
| {{Grey|4}}
| [[OpenVPN client in Linux Containers|Artículo original]]
|
|-
| [[Oracle Database client (Español)]]
| {{Grey|4}}
| [[Oracle Database client|Artículo original]]
|
|-
| [[OSH (Español)]]
| {{Grey|4}}
| [[OSH|Artículo original]]
|
|-
| [[Otter Browser (Español)]]
| {{Grey|4}}
| [[Otter Browser|Artículo original]]
|
|-
| [[Package Proxy Cache (Español)]]
| {{Grey|4}}
| [[Package proxy cache|Artículo original]]
|
|-
| [[Packaging Brother printer drivers (Español)]]
| {{Grey|4}}
| [[Packaging Brother printer drivers|Artículo original]]
|
|-
| [[Packet Tracer (Español)]]
| {{Grey|4}}
| [[Packet Tracer|Artículo original]]
|
|-
| [[Pacserve (Español)]]
| {{Grey|4}}
| [[Pacserve|Artículo original]]
|
|-
| [[Palm (Español)]]
| {{Grey|4}}
| [[Palm|Artículo original]]
|
|-
| [[Palm (Español)/Evolution (Español)]]
| {{Grey|4}}
| [[Palm/Evolution|Artículo original]]
|
|-
| [[Pam abl (Español)]]
| {{Grey|4}}
| [[pam_abl|Artículo original]]
|
|-
| [[Pam mount (Español)]]
| {{Grey|4}}
| [[pam_mount|Artículo original]]
|
|-
| [[Pam oath (Español)]]
| {{Grey|4}}
| [[pam_oath|Artículo original]]
|
|-
| [[Pam usb (Español)]]
| {{Grey|4}}
| [[pam_usb|Artículo original]]
|
|-
| [[Pandoc (Español)]]
| {{Grey|4}}
| [[Pandoc|Artículo original]]
|
|-
| [[Pantheon (Español)]]
| {{Grey|4}}
| [[Pantheon|Artículo original]]
|
|-
| [[Paperkey (Español)]]
| {{Grey|4}}
| [[Paperkey|Artículo original]]
|
|-
| [[Parallels (Español)]]
| {{Grey|4}}
| [[Parallels|Artículo original]]
|
|-
| [[Paramano (Español)]]
| {{Grey|4}}
| [[Paramano|Artículo original]]
|
|-
| [[Parchive (Español)]]
| {{Grey|4}}
| [[Parchive|Artículo original]]
|
|-
| [[Parental control (Español)]]
| {{Grey|4}}
| [[Parental control|Artículo original]]
|
|-
| [[Pass (Español)]]
| {{Grey|4}}
| [[Pass|Artículo original]]
|
|-
| [[Patching packages (Español)]]
| {{Grey|4}}
| [[Patching packages|Artículo original]]
|
|-
| [[PC Engines (Español)]]
| {{Grey|4}}
| [[PC Engines|Artículo original]]
|
|-
| [[PCI passthrough via OVMF (Español)]]
| {{Grey|4}}
| [[PCI passthrough via OVMF|Artículo original]]
|
|-
| [[PCI passthrough via OVMF (Español)/Examples (Español)]]
| {{Grey|4}}
| [[PCI passthrough via OVMF/Examples|Artículo original]]
|
|-
| [[PCManFM (Español)]]
| {{Grey|4}}
| [[PCManFM|Artículo original]]
|
|-
| [[PCSX-Reloaded (Español)]]
| {{Grey|4}}
| [[PCSX-Reloaded|Artículo original]]
|
|-
| [[PeerGuardian Linux (Español)]]
| {{Grey|4}}
| [[PeerGuardian Linux|Artículo original]]
|
|-
| [[Per-application transparency (Español)]]
| {{Grey|4}}
| [[Per-application transparency|Artículo original]]
|
|-
| [[Perl (Español)]]
| {{Grey|4}}
| [[Perl|Artículo original]]
|
|-
| [[Perl package guidelines (Español)]]
| {{Grey|4}}
| [[Perl package guidelines|Artículo original]]
|
|-
| [[Perl Policy (Español)]]
| {{Grey|4}}
| [[Perl Policy|Artículo original]]
|
|-
| [[PHP package guidelines (Español)]]
| {{Grey|4}}
| [[PHP package guidelines|Artículo original]]
|
|-
| [[PhpLDAPadmin (Español)]]
| {{Grey|4}}
| [[PhpLDAPadmin|Artículo original]]
|
|-
| [[PHPUnit (Español)]]
| {{Grey|4}}
| [[PHPUnit|Artículo original]]
|
|-
| [[PhpVirtualBox (Español)]]
| {{Grey|4}}
| [[PhpVirtualBox|Artículo original]]
|
|-
| [[Phrik (Español)]]
| {{Grey|4}}
| [[Phrik|Artículo original]]
|
|-
| [[Pianobar (Español)]]
| {{Grey|4}}
| [[Pianobar|Artículo original]]
|
|-
| [[Pi-hole (Español)]]
| {{Grey|4}}
| [[Pi-hole|Artículo original]]
|
|-
| [[Pip (Español)]]
| {{Grey|4}}
| [[Pip|Artículo original]]
|
|-
| [[PipeWire (Español)]]
| {{Grey|4}}
| [[PipeWire|Artículo original]]
|
|-
| [[Plank (Español)]]
| {{Grey|4}}
| [[Plank|Artículo original]]
|
|-
| [[Polkit (Español)]]
| {{Grey|4}}
| [[Polkit|Artículo original]]
|
|-
| [[Polybar (Español)]]
| {{Grey|4}}
| [[Polybar|Artículo original]]
|
|-
| [[File recovery/Post recovery tasks (Español)]]
| {{Grey|4}}
| [[File recovery/Post recovery tasks|Artículo original]]
|
|-
| [[Postfix with SASL (Español)]]
| {{Grey|4}}
| [[Postfix with SASL|Artículo original]]
|
|-
| [[PostfixAdmin (Español)]]
| {{Grey|4}}
| [[PostfixAdmin|Artículo original]]
|
|-
| [[PostGIS (Español)]]
| {{Grey|4}}
| [[PostGIS|Artículo original]]
|
|-
| [[PostgreSQL (Español)]]
| {{Grey|4}}
| [[PostgreSQL|Artículo original]]
|
|-
| [[PowerDNS (Español)]]
| {{Grey|4}}
| [[PowerDNS|Artículo original]]
|
|-
| [[Powerline (Español)]]
| {{Grey|4}}
| [[Powerline|Artículo original]]
|
|-
| [[Powertop (Español)]]
| {{Grey|4}}
| [[Powertop|Artículo original]]
|
|-
| [[Ppp (Español)]]
| {{Grey|4}}
| [[Ppp|Artículo original]]
|
|-
| [[PPTP Client (Español)]]
| {{Grey|4}}
| [[PPTP Client|Artículo original]]
|
|-
| [[PPTP server (Español)]]
| {{Grey|4}}
| [[PPTP server|Artículo original]]
|
|-
| [[PrBoom (Español)]]
| {{Grey|4}}
| [[PrBoom|Artículo original]]
|
|-
| [[Prey (Español)]]
| {{Grey|4}}
| [[Prey|Artículo original]]
|
|-
| [[PRIME (Español)]]
| {{Grey|4}}
| [[PRIME|Artículo original]]
|
|-
| [[Private Internet Access (Español)]]
| {{Grey|4}}
| [[Private Internet Access|Artículo original]]
|
|-
| [[Private Internet Access (Español)/AUR (Español)]]
| {{Grey|4}}
| [[Private Internet Access/AUR|Artículo original]]
|
|-
| [[Privoxy (Español)]]
| {{Grey|4}}
| [[Privoxy|Artículo original]]
|
|-
| [[Procmail (Español)]]
| {{Grey|4}}
| [[Procmail|Artículo original]]
|
|-
| [[Profile-sync-daemon (Español)]]
| {{Grey|4}}
| [[Profile-sync-daemon|Artículo original]]
|
|-
| [[ProjectM (Español)]]
| {{Grey|4}}
| [[ProjectM|Artículo original]]
|
|-
| [[Prometheus (Español)]]
| {{Grey|4}}
| [[Prometheus|Artículo original]]
|
|-
| [[PRoot (Español)]]
| {{Grey|4}}
| [[PRoot|Artículo original]]
|
|-
| [[Prosody (Español)]]
| {{Grey|4}}
| [[Prosody|Artículo original]]
|
|-
| [[Pulse Connect Secure (Español)]]
| {{Grey|4}}
| [[Pulse Connect Secure|Artículo original]]
|
|-
| [[PulseAudio (Español)/Examples (Español)]]
| {{Grey|4}}
| [[PulseAudio/Examples|Artículo original]]
|
|-
| [[PulseAudio (Español)/Troubleshooting (Español)]]
| {{Grey|4}}
| [[PulseAudio/Troubleshooting|Artículo original]]
|
|-
| [[Puppet (Español)]]
| {{Grey|4}}
| [[Puppet|Artículo original]]
|
|-
| [[Puppet server (Español)]]
| {{Grey|4}}
| [[Puppet server|Artículo original]]
|
|-
| [[Pure-FTPd (Español)]]
| {{Grey|4}}
| [[Pure-FTPd|Artículo original]]
|
|-
| [[PuTTY (Español)]]
| {{Grey|4}}
| [[PuTTY|Artículo original]]
|
|-
| [[Pydio (Español)]]
| {{Grey|4}}
| [[Pydio|Artículo original]]
|
|-
| [[PyLoad (Español)]]
| {{Grey|4}}
| [[PyLoad|Artículo original]]
|
|-
| [[PyPy (Español)]]
| {{Grey|4}}
| [[PyPy|Artículo original]]
|
|-
| [[Python celery (Español)]]
| {{Grey|4}}
| [[Python celery|Artículo original]]
|
|-
| [[Python package guidelines (Español)]]
| {{Grey|4}}
| [[Python package guidelines|Artículo original]]
|
|-
| [[QEMU (Español)/Guest graphics acceleration (Español)]]
| {{Grey|4}}
| [[QEMU/Guest graphics acceleration|Artículo original]]
|
|-
| [[Qnix QX2710 (Español)]]
| {{Grey|4}}
| [[Qnix QX2710|Artículo original]]
|
|-
| [[Qtile (Español)]]
| {{Grey|4}}
| [[Qtile|Artículo original]]
|
|-
| [[Quassel (Español)]]
| {{Grey|4}}
| [[Quassel|Artículo original]]
|
|-
| [[Qutebrowser (Español)]]
| {{Grey|4}}
| [[Qutebrowser|Artículo original]]
|
|-
| [[R (Español)]]
| {{Grey|4}}
| [[R|Artículo original]]
|
|-
| [[R package guidelines (Español)]]
| {{Grey|4}}
| [[R package guidelines|Artículo original]]
|
|-
| [[RabbitMQ (Español)]]
| {{Grey|4}}
| [[RabbitMQ|Artículo original]]
|
|-
| [[Radicale (Español)]]
| {{Grey|4}}
| [[Radicale|Artículo original]]
|
|-
| [[Random number generation (Español)]]
| {{Grey|4}}
| [[Random number generation|Artículo original]]
|
|-
| [[Ratpoison (Español)]]
| {{Grey|4}}
| [[Ratpoison|Artículo original]]
|
|-
| [[Razer Blade (Español)]]
| {{Grey|4}}
| [[Razer Blade|Artículo original]]
|
|-
| [[Razer peripherals (Español)]]
| {{Grey|4}}
| [[Razer peripherals|Artículo original]]
|
|-
| [[Rbenv (Español)]]
| {{Grey|4}}
| [[Rbenv|Artículo original]]
|
|-
| [[Realtime kernel (Español)]]
| {{Grey|4}}
| [[Realtime kernel|Artículo original]]
|
|-
| [[Realtime process management (Español)]]
| {{Grey|4}}
| [[Realtime process management|Artículo original]]
|
|-
| [[RecordMyDesktop (Español)]]
| {{Grey|4}}
| [[RecordMyDesktop|Artículo original]]
|
|-
| [[Recovery after failed update or upgrade (Español)]]
| {{Grey|4}}
| [[Recovery after failed update or upgrade|Artículo original]]
|
|-
| [[Redis (Español)]]
| {{Grey|4}}
| [[Redis|Artículo original]]
|
|-
| [[Redmine (Español)]]
| {{Grey|4}}
| [[Redmine|Artículo original]]
|
|-
| [[Redshift (Español)]]
| {{Grey|4}}
| [[Redshift|Artículo original]]
|
|-
| [[REFInd (Español)]]
| {{Grey|4}}
| [[REFInd|Artículo original]]
|
|-
| [[Remind (Español)]]
| {{Grey|4}}
| [[Remind|Artículo original]]
|
|-
| [[RemoteBox (Español)]]
| {{Grey|4}}
| [[RemoteBox|Artículo original]]
|
|-
| [[RepRap (Español)]]
| {{Grey|4}}
| [[RepRap|Artículo original]]
|
|-
| [[Rescached (Español)]]
| {{Grey|4}}
| [[Rescached|Artículo original]]
|
|-
| [[Reset lost root password (Español)]]
| {{Grey|4}}
| [[Reset lost root password|Artículo original]]
|
|-
| [[Resilio Sync (Español)]]
| {{Grey|4}}
| [[Resilio Sync|Artículo original]]
|
|-
| [[Resizing LVM-on-LUKS (Español)]]
| {{Grey|4}}
| [[Resizing LVM-on-LUKS|Artículo original]]
|
|-
| [[Rhythmbox (Español)]]
| {{Grey|4}}
| [[Rhythmbox|Artículo original]]
|
|-
| [[Rime (Español)]]
| {{Grey|4}}
| [[Rime|Artículo original]]
|
|-
| [[Ring (Español)]]
| {{Grey|4}}
| [[Ring|Artículo original]]
|
|-
| [[Rip Audio CDs (Español)]]
| {{Grey|4}}
| [[Rip Audio CDs|Artículo original]]
|
|-
| [[Ripcord (Español)]]
| {{Grey|4}}
| [[Ripcord|Artículo original]]
|
|-
| [[Rng-tools (Español)]]
| {{Grey|4}}
| [[Rng-tools|Artículo original]]
|
|-
| [[Rofi (Español)]]
| {{Grey|4}}
| [[Rofi|Artículo original]]
|
|-
| [[ROS (Español)]]
| {{Grey|4}}
| [[ROS|Artículo original]]
|
|-
| [[Rosegarden (Español)]]
| {{Grey|4}}
| [[Rosegarden|Artículo original]]
|
|-
| [[Roundcube (Español)]]
| {{Grey|4}}
| [[Roundcube|Artículo original]]
|
|-
| [[Router (Español)]]
| {{Grey|4}}
| [[Router|Artículo original]]
|
|-
| [[Rsnapshot (Español)]]
| {{Grey|4}}
| [[Rsnapshot|Artículo original]]
|
|-
| [[Rss2email (Español)]]
| {{Grey|4}}
| [[Rss2email|Artículo original]]
|
|-
| [[Rsyslog (Español)]]
| {{Grey|4}}
| [[Rsyslog|Artículo original]]
|
|-
| [[RTL-SDR (Español)]]
| {{Grey|4}}
| [[RTL-SDR|Artículo original]]
|
|-
| [[RTorrent (Español)/RuTorrent (Español)]]
| {{Grey|4}}
| [[RTorrent/RuTorrent|Artículo original]]
|
|-
| [[Ruby (Español)]]
| {{Grey|4}}
| [[Ruby|Artículo original]]
|
|-
| [[Ruby Gem package guidelines (Español)]]
| {{Grey|4}}
| [[Ruby Gem package guidelines|Artículo original]]
|
|-
| [[Ruby on Rails (Español)]]
| {{Grey|4}}
| [[Ruby on Rails|Artículo original]]
|
|-
| [[RuneScape (Español)]]
| {{Grey|4}}
| [[RuneScape|Artículo original]]
|
|-
| [[Runit (Español)]]
| {{Grey|4}}
| [[Runit|Artículo original]]
|
|-
| [[Running GUI applications as root (Español)]]
| {{Grey|4}}
| [[Running GUI applications as root|Artículo original]]
|
|-
| [[Rust (Español)]]
| {{Grey|4}}
| [[Rust|Artículo original]]
|
|-
| [[RVM (Español)]]
| {{Grey|4}}
| [[RVM|Artículo original]]
|
|-
| [[Rxvt-unicode (Español)/Tips and tricks (Español)]]
| {{Grey|4}}
| [[Rxvt-unicode/Tips and tricks|Artículo original]]
|
|-
| [[Rygel (Español)]]
| {{Grey|4}}
| [[Rygel|Artículo original]]
|
|-
| [[SABnzbd (Español)]]
| {{Grey|4}}
| [[SABnzbd|Artículo original]]
|
|-
| [[SageMath (Español)]]
| {{Grey|4}}
| [[SageMath|Artículo original]]
|
|-
| [[Saltstack (Español)]]
| {{Grey|4}}
| [[Saltstack|Artículo original]]
|
|-
| [[Samba (Español)/Active Directory domain controller (Español)]]
| {{Grey|4}}
| [[Samba/Active Directory domain controller|Artículo original]]
|
|-

| [[Samsung NC20 (Español)]]
| {{Grey|4}}
| [[Samsung NC20|Artículo original]]
|
|-
| [[Samsung Series 7 Slate XE700T1A (Español)]]
| {{Grey|4}}
| [[Samsung Series 7 Slate XE700T1A|Artículo original]]
|
|-
| [[SANE (Español)/Scanner-specific problems (Español)]]
| {{Grey|4}}
| [[SANE/Scanner-specific problems|Artículo original]]
|
|-
| [[Sawfish (Español)]]
| {{Grey|4}}
| [[Sawfish|Artículo original]]
|
|-
| [[SB Live! Midi (Español)]]
| {{Grey|4}}
| [[SB Live! Midi|Artículo original]]
|
|-
| [[Scanner Button Daemon (Español)]]
| {{Grey|4}}
| [[Scanner Button Daemon|Artículo original]]
|
|-
| [[SCM Example Trac (Español)]]
| {{Grey|4}}
| [[SCM Example Trac|Artículo original]]
|
|-
| [[SCP and SFTP (Español)]]
| {{Grey|4}}
| [[SCP and SFTP|Artículo original]]
|
|-
| [[Screen Irssi Bitlbee (Español)]]
| {{Grey|4}}
| [[Screen Irssi Bitlbee|Artículo original]]
|
|-
| [[SDDM (Español)]]
| {{Grey|4}}
| [[SDDM|Artículo original]]
|
|-
| [[Secure Boot (Español)]]
| {{Grey|4}}
| [[Secure Boot|Artículo original]]
|
|-
| [[Securely wipe disk (Español)/Tips and tricks (Español)]]
| {{Grey|4}}
| [[Securely wipe disk/Tips and tricks|Artículo original]]
|
|-
| [[Self-Encrypting Drives (Español)]]
| {{Grey|4}}
| [[Self-encrypting drives|Artículo original]]
|
|-
| [[Serial input device to kernel input (Español)]]
| {{Grey|4}}
| [[Serial input device to kernel input|Artículo original]]
|
|-
| [[Server (Español)]]
| {{Grey|4}}
| [[Server|Artículo original]]
|
|-
| [[Setkeycodes (Español)]]
| {{Grey|4}}
| [[Setkeycodes|Artículo original]]
|
|-
| [[Sftp (Español)]]
| {{Grey|4}}
| [[Sftp|Artículo original]]
|
|-
| [[SFTP chroot (Español)]]
| {{Grey|4}}
| [[SFTP chroot|Artículo original]]
|
|-
| [[Sftpman (Español)]]
| {{Grey|4}}
| [[Sftpman|Artículo original]]
|
|-
| [[SHA password hashes (Español)]]
| {{Grey|4}}
| [[SHA password hashes|Artículo original]]
|
|-
| [[Shadowsocks (Español)]]
| {{Grey|4}}
| [[Shadowsocks|Artículo original]]
|
|-
| [[Shairport Sync (Español)]]
| {{Grey|4}}
| [[Shairport Sync|Artículo original]]
|
|-
| [[Sharing PPP Connection (Español)]]
| {{Grey|4}}
| [[Sharing PPP Connection|Artículo original]]
|
|-
| [[Shorewall (Español)]]
| {{Grey|4}}
| [[Shorewall|Artículo original]]
|
|-
| [[Showkey (Español)]]
| {{Grey|4}}
| [[Showkey|Artículo original]]
|
|-
| [[Shred (Español)]]
| {{Grey|4}}
| [[Shred|Artículo original]]
|
|-
| [[SickRage (Español)]]
| {{Grey|4}}
| [[SickRage|Artículo original]]
|
|-
| [[Simple Orca Plugin System (Español)]]
| {{Grey|4}}
| [[Simple Orca Plugin System|Artículo original]]
|
|-
| [[Slime (Español)]]
| {{Grey|4}}
| [[Slime|Artículo original]]
|
|-
| [[Slock (Español)]]
| {{Grey|4}}
| [[Slock|Artículo original]]
|
|-
| [[Slrn (Español)]]
| {{Grey|4}}
| [[Slrn|Artículo original]]
|
|-
| [[Slurm (Español)]]
| {{Grey|4}}
| [[Slurm|Artículo original]]
|
|-
| [[S.M.A.R.T. (Español)]]
| {{Grey|4}}
| [[S.M.A.R.T.|Artículo original]]
|
|-
| [[Smart Common Input Method (Español)]]
| {{Grey|4}}
| [[Smart Common Input Method|Artículo original]]
|
|-
| [[Smartcards (Español)]]
| {{Grey|4}}
| [[Smartcards|Artículo original]]
|
|-
| [[Smokeping (Español)]]
| {{Grey|4}}
| [[Smokeping|Artículo original]]
|
|-
| [[S-nail (Español)]]
| {{Grey|4}}
| [[S-nail|Artículo original]]
|
|-
| [[Snapper (Español)]]
| {{Grey|4}}
| [[Snapper|Artículo original]]
|
|-
| [[SnapRAID (Español)]]
| {{Grey|4}}
| [[SnapRAID|Artículo original]]
|
|-
| [[Snort (Español)]]
| {{Grey|4}}
| [[Snort|Artículo original]]
|
|-
| [[Software access point (Español)]]
| {{Grey|4}}
| [[Software access point|Artículo original]]
|
|-
| [[Software RAID and LVM (Español)]]
| {{Grey|4}}
| [[Software RAID and LVM|Artículo original]]
|
|-
| [[SOGo (Español)]]
| {{Grey|4}}
| [[SOGo|Artículo original]]
|
|-
| [[Solid state drive (Español)/Memory cell clearing (Español)]]
| {{Grey|4}}
| [[Solid state drive/Memory cell clearing|Artículo original]]
|
|-
| [[Solid state drive (Español)/NVMe (Español)]]
| {{Grey|4}}
| [[Solid state drive/NVMe|Artículo original]]
|
|-
| [[Solid State Drives (Español)]]
| {{Grey|4}}
| [[Solid State Drives|Artículo original]]
|
|-
| [[Sony Vaio Pro SVP-1x21 (Español)]]
| {{Grey|4}}
| [[Sony Vaio Pro SVP-1x21|Artículo original]]
|
|-
| [[Sony Vaio VPCF13 (Español)]]
| {{Grey|4}}
| [[Sony Vaio VPCF13|Artículo original]]
|
|-
| [[Sort images by resolution (Español)]]
| {{Grey|4}}
| [[Sort images by resolution|Artículo original]]
|
|-
| [[SpaceFM (Español)]]
| {{Grey|4}}
| [[SpaceFM|Artículo original]]
|
|-
| [[Spacemacs (Español)]]
| {{Grey|4}}
| [[Spacemacs|Artículo original]]
|
|-
| [[SpamAssassin (Español)]]
| {{Grey|4}}
| [[SpamAssassin|Artículo original]]
|
|-
| [[Sparse file (Español)]]
| {{Grey|4}}
| [[Sparse file|Artículo original]]
|
|-
| [[Spectrwm (Español)]]
| {{Grey|4}}
| [[Spectrwm|Artículo original]]
|
|-
| [[Splunk (Español)]]
| {{Grey|4}}
| [[Splunk|Artículo original]]
|
|-
| [[SQLite (Español)]]
| {{Grey|4}}
| [[SQLite|Artículo original]]
|
|-
| [[Squid (Español)]]
| {{Grey|4}}
| [[Squid|Artículo original]]
|
|-
| [[.SRCINFO (Español)]]
| {{Grey|4}}
| [[.SRCINFO|Artículo original]]
|
|-
| [[Ssh-keygen (Español)]]
| {{Grey|4}}
| [[Ssh-keygen|Artículo original]]
|
|-
| [[St (Español)]]
| {{Grey|4}}
| [[St|Artículo original]]
|
|-
| [[Stalonetray (Español)]]
| {{Grey|4}}
| [[Stalonetray|Artículo original]]
|
|-
| [[Steam (Español)]]
| {{Grey|4}}
| [[Steam|Artículo original]]
|
|-
| [[Steam (Español)/Game-specific troubleshooting (Español)]]
| {{Grey|4}}
| [[Steam/Game-specific troubleshooting|Artículo original]]
|
|-
| [[Steam (Español)/Troubleshooting (Español)]]
| {{Grey|4}}
| [[Steam/Troubleshooting|Artículo original]]
|
|-
| [[Step-by-step debugging guide (Español)]]
| {{Grey|4}}
| [[Step-by-step debugging guide|Artículo original]]
|
|-
| [[Streamlink (Español)]]
| {{Grey|4}}
| [[Streamlink|Artículo original]]
|
|-
| [[Stress testing (Español)]]
| {{Grey|4}}
| [[Stress testing|Artículo original]]
|
|-
| [[StrongSwan (Español)]]
| {{Grey|4}}
| [[StrongSwan|Artículo original]]
|
|-
| [[Stubby (Español)]]
| {{Grey|4}}
| [[Stubby|Artículo original]]
|
|-
| [[Stumpwm (Español)]]
| {{Grey|4}}
| [[Stumpwm|Artículo original]]
|
|-
| [[Subsonic (Español)]]
| {{Grey|4}}
| [[Subsonic|Artículo original]]
|
|-
| [[Sup (Español)]]
| {{Grey|4}}
| [[Sup|Artículo original]]
|
|-
| [[Surf (Español)]]
| {{Grey|4}}
| [[Surf|Artículo original]]
|
|-
| [[Surfraw (Español)]]
| {{Grey|4}}
| [[Surfraw|Artículo original]]
|
|-
| [[Suricata (Español)]]
| {{Grey|4}}
| [[Suricata|Artículo original]]
|
|-
| [[Swap on video RAM (Español)]]
| {{Grey|4}}
| [[Swap on video RAM|Artículo original]]
|
|-
| [[Sway (Español)]]
| {{Grey|4}}
| [[Sway|Artículo original]]
|
|-
| [[Sxiv (Español)]]
| {{Grey|4}}
| [[Sxiv|Artículo original]]
|
|-
| [[Synchronization and backup programs (Español)]]
| {{Grey|4}}
| [[Synchronization and backup programs|Artículo original]]
|
|-
| [[Syncthing (Español)]]
| {{Grey|4}}
| [[Syncthing|Artículo original]]
|
|-
| [[Synergy (Español)]]
| {{Grey|4}}
| [[Synergy|Artículo original]]
|
|-
| [[Sysctl (Español)]]
| {{Grey|4}}
| [[Sysctl|Artículo original]]
|
|-
| [[Syslog-ng (Español)]]
| {{Grey|4}}
| [[Syslog-ng|Artículo original]]
|
|-
| [[Systemd-firstboot (Español)]]
| {{Grey|4}}
| [[Systemd-firstboot|Artículo original]]
|
|-
| [[SystemTap (Español)]]
| {{Grey|4}}
| [[SystemTap|Artículo original]]
|
|-
| [[Tablet PC (Español)]]
| {{Grey|4}}
| [[Tablet PC|Artículo original]]
|
|-
| [[Talkd and the talk command (Español)]]
| {{Grey|4}}
| [[Talkd and the talk command|Artículo original]]
|
|-
| [[Taskd (Español)]]
| {{Grey|4}}
| [[Taskd|Artículo original]]
|
|-
| [[Tcplay (Español)]]
| {{Grey|4}}
| [[Tcplay|Artículo original]]
|
|-
| [[TeamSpeak (Español)]]
| {{Grey|4}}
| [[TeamSpeak|Artículo original]]
|
|-
| [[Teclast X16 Pro (Español)]]
| {{Grey|4}}
| [[Teclast X16 Pro|Artículo original]]
|
|-
| [[Teclast X5 Pro (Español)]]
| {{Grey|4}}
| [[Teclast X5 Pro|Artículo original]]
|
|-
| [[Teclast X98 Plus II (Español)]]
| {{Grey|4}}
| [[Teclast X98 Plus II|Artículo original]]
|
|-
| [[Telegram (Español)]]
| {{Grey|4}}
| [[Telegram|Artículo original]]
|
|-
| [[Termite (Español)]]
| {{Grey|4}}
| [[Termite|Artículo original]]
|
|-
| [[TerraTec Aureon 7.1 (Español)]]
| {{Grey|4}}
| [[TerraTec Aureon 7.1|Artículo original]]
|
|-
| [[TerraTec T6 DVB-T (Afatech AF9035) (Español)]]
| {{Grey|4}}
| [[TerraTec T6 DVB-T (Afatech AF9035)|Artículo original]]
|
|-
| [[TeX Live and CJK (Español)]]
| {{Grey|4}}
| [[TeX Live and CJK|Artículo original]]
|
|-
| [[TeX Live FAQ (Español)]]
| {{Grey|4}}
| [[TeX Live FAQ|Artículo original]]
|
|-
| [[Textadept (Español)]]
| {{Grey|4}}
| [[Textadept|Artículo original]]
|
|-
| [[ThinkPad docks (Español)]]
| {{Grey|4}}
| [[ThinkPad docks|Artículo original]]
|
|-
| [[ThinkPad mobile internet (Español)]]
| {{Grey|4}}
| [[ThinkPad mobile Internet|Artículo original]]
|
|-
| [[Thunderbird (Español)]]
| {{Grey|4}}
| [[Thunderbird|Artículo original]]
|
|-
| [[Thunderbird (Español)/Enigmail (Español)]]
| {{Grey|4}}
| [[Thunderbird/Enigmail|Artículo original]]
|
|-
| [[Tilda (Español)]]
| {{Grey|4}}
| [[Tilda|Artículo original]]
|
|-
| [[Timidity (Español)]]
| {{Grey|4}}
| [[Timidity|Artículo original]]
|
|-
| [[Tint2 (Español)]]
| {{Grey|4}}
| [[Tint2|Artículo original]]
|
|-
| [[TLP (Español)]]
| {{Grey|4}}
| [[TLP|Artículo original]]
|
|-
| [[Tmuxp (Español)]]
| {{Grey|4}}
| [[Tmuxp|Artículo original]]
|
|-
| [[Tomb (Español)]]
| {{Grey|4}}
| [[Tomb|Artículo original]]
|
|-
| [[TOMOYO Linux (Español)]]
| {{Grey|4}}
| [[TOMOYO Linux|Artículo original]]
|
|-
| [[TORQUE (Español)]]
| {{Grey|4}}
| [[TORQUE|Artículo original]]
|
|-
| [[Toshiba Portege Z20t (Español)]]
| {{Grey|4}}
| [[Toshiba Portege Z20t|Artículo original]]
|
|-
| [[Toshiba Portege Z30-A (Español)]]
| {{Grey|4}}
| [[Toshiba Portege Z30-A|Artículo original]]
|
|-
| [[Toshiba Satellite A660 (Español)]]
| {{Grey|4}}
| [[Toshiba Satellite A660|Artículo original]]
|
|-
| [[Toshiba Satellite L300 (Español)]]
| {{Grey|4}}
| [[Toshiba Satellite L300|Artículo original]]
|
|-
| [[Toshiba Satellite P205D-S8804 (Español)]]
| {{Grey|4}}
| [[Toshiba Satellite P205D-S8804|Artículo original]]
|
|-
| [[Touchatag RFID Reader (Español)]]
| {{Grey|4}}
| [[Touchatag RFID Reader|Artículo original]]
|
|-
| [[Touchegg (Español)]]
| {{Grey|4}}
| [[Touchegg|Artículo original]]
|
|-
| [[Touchscreen (Español)]]
| {{Grey|4}}
| [[Touchscreen|Artículo original]]
|
|-
| [[Touhou (Español)]]
| {{Grey|4}}
| [[Touhou|Artículo original]]
|
|-
| [[Tox (Español)]]
| {{Grey|4}}
| [[Tox|Artículo original]]
|
|-
| [[Tp smapi (Español)]]
| {{Grey|4}}
| [[tp_smapi|Artículo original]]
|
|-
| [[Tp-battery-mode (Español)]]
| {{Grey|4}}
| [[Tp-battery-mode|Artículo original]]
|
|-
| [[Trac (Español)]]
| {{Grey|4}}
| [[Trac|Artículo original]]
|
|-
| [[Transport Layer Security (Español)]]
| {{Grey|4}}
| [[Transport Layer Security|Artículo original]]
|
|-
| [[Trickle (Español)]]
| {{Grey|4}}
| [[Trickle|Artículo original]]
|
|-
| [[Trinity (Español)]]
| {{Grey|4}}
| [[Trinity|Artículo original]]
|
|-
| [[Trojan (Español)]]
| {{Grey|4}}
| [[Trojan|Artículo original]]
|
|-
| [[TrueCrypt (Español)]]
| {{Grey|4}}
| [[TrueCrypt|Artículo original]]
|
|-
| [[Trusted Platform Module (Español)]]
| {{Grey|4}}
| [[Trusted Platform Module|Artículo original]]
|
|-
| [[Tvheadend (Español)]]
| {{Grey|4}}
| [[Tvheadend|Artículo original]]
|
|-
| [[Twister (Español)]]
| {{Grey|4}}
| [[Twister|Artículo original]]
|
|-
| [[Udisks (Español)]]
| {{Grey|4}}
| [[Udisks|Artículo original]]
|
|-
| [[Uim (Español)]]
| {{Grey|4}}
| [[Uim|Artículo original]]
|
|-
| [[Umount (Español)]]
| {{Grey|4}}
| [[Umount|Artículo original]]
|
|-
| [[Unbound (Español)]]
| {{Grey|4}}
| [[Unbound|Artículo original]]
|
|-
| [[Unclutter (Español)]]
| {{Grey|4}}
| [[Unclutter|Artículo original]]
|
|-
| [[Uncomplicated Firewall (Español)]]
| {{Grey|4}}
| [[Uncomplicated Firewall|Artículo original]]
|
|-
| [[Undervolting CPU (Español)]]
| {{Grey|4}}
| [[Undervolting CPU|Artículo original]]
|
|-
| [[Unison (Español)]]
| {{Grey|4}}
| [[Unison|Artículo original]]
|
|-
| [[Unity3D (Español)]]
| {{Grey|4}}
| [[Unity3D|Artículo original]]
|
|-
| [[Universal Media Server (Español)]]
| {{Grey|4}}
| [[Universal Media Server|Artículo original]]
|
|-
| [[UnrealIRCd (Español)]]
| {{Grey|4}}
| [[UnrealIRCd|Artículo original]]
|
|-
| [[Up-board (Español)]]
| {{Grey|4}}
| [[Up-board|Artículo original]]
|
|-
| [[Upside Down Ternet (Español)]]
| {{Grey|4}}
| [[Upside Down Ternet|Artículo original]]
|
|-
| [[Urban Terror (Español)]]
| {{Grey|4}}
| [[Urban Terror|Artículo original]]
|
|-
| [[USB 3G Modem (Español)]]
| {{Grey|4}}
| [[USB 3G Modem|Artículo original]]
|
|-
| [[USB MIDI keyboards (Español)]]
| {{Grey|4}}
| [[USB MIDI keyboards|Artículo original]]
|
|-
| [[USBGuard (Español)]]
| {{Grey|4}}
| [[USBGuard|Artículo original]]
|
|-
| [[User-mode Linux (Español)]]
| {{Grey|4}}
| [[User-mode Linux|Artículo original]]
|
|-
| [[UWSGI (Español)]]
| {{Grey|4}}
| [[UWSGI|Artículo original]]
|
|-
| [[Uzbl (Español)]]
| {{Grey|4}}
| [[Uzbl|Artículo original]]
|
|-
| [[Vagrant (Español)]]
| {{Grey|4}}
| [[Vagrant|Artículo original]]
|
|-
| [[Varnish (Español)]]
| {{Grey|4}}
| [[Varnish|Artículo original]]
|
|-
| [[VCS package guidelines (Español)]]
| {{Grey|4}}
| [[VCS package guidelines|Artículo original]]
|
|-
| [[Vertex VW110L - Ufon (Español)]]
| {{Grey|4}}
| [[Vertex VW110L - Ufon|Artículo original]]
|
|-
| [[Via Technologies (Español)]]
| {{Grey|4}}
| [[Via Technologies|Artículo original]]
|
|-
| [[Vifm (Español)]]
| {{Grey|4}}
| [[Vifm|Artículo original]]
|
|-
| [[Vim (Español)/YouCompleteMe (Español)]]
| {{Grey|4}}
| [[Vim/YouCompleteMe|Artículo original]]
|
|-
| [[Virtual reality (Español)]]
| {{Grey|4}}
| [[Virtual reality|Artículo original]]
|
|-
| [[Virtual user mail system with Postfix, Dovecot and Roundcube (Español)]]
| {{Grey|4}}
| [[Virtual user mail system with Postfix, Dovecot and Roundcube|Artículo original]]
|
|-
| [[VirtualGL (Español)]]
| {{Grey|4}}
| [[VirtualGL|Artículo original]]
|
|-
| [[Visual Studio Code (Español)]]
| {{Grey|4}}
| [[Visual Studio Code|Artículo original]]
|
|-
| [[VisualBoyAdvance-M (Español)]]
| {{Grey|4}}
| [[VisualBoyAdvance-M|Artículo original]]
|
|-
| [[VLAN (Español)]]
| {{Grey|4}}
| [[VLAN|Artículo original]]
|
|-
| [[VMware (Español)]]
| {{Grey|4}}
| [[VMware|Artículo original]]
|
|-
| [[VnStat (Español)]]
| {{Grey|4}}
| [[VnStat|Artículo original]]
|
|-
| [[VOGL (Español)]]
| {{Grey|4}}
| [[VOGL|Artículo original]]
|
|-
| [[Volnoti (Español)]]
| {{Grey|4}}
| [[Volnoti|Artículo original]]
|
|-
| [[VPN over SSH (Español)]]
| {{Grey|4}}
| [[VPN over SSH|Artículo original]]
|
|-
| [[Vulkan (Español)]]
| {{Grey|4}}
| [[Vulkan|Artículo original]]
|
|-
| [[Vx32 (Español)]]
| {{Grey|4}}
| [[Vx32|Artículo original]]
|
|-
| [[Wacom tablet (Español)]]
| {{Grey|4}}
| [[Wacom tablet|Artículo original]]
|
|-
| [[Wake-on-LAN (Español)]]
| {{Grey|4}}
| [[Wake-on-LAN|Artículo original]]
|
|-
| [[Web application package guidelines (Español)]]
| {{Grey|4}}
| [[Web application package guidelines|Artículo original]]
|
|-
| [[WebDAV (Español)]]
| {{Grey|4}}
| [[WebDAV|Artículo original]]
|
|-
| [[WebGrab+Plus (Español)]]
| {{Grey|4}}
| [[WebGrab+Plus|Artículo original]]
|
|-
| [[Webmin (Español)]]
| {{Grey|4}}
| [[Webmin|Artículo original]]
|
|-
| [[WeeChat (Español)]]
| {{Grey|4}}
| [[WeeChat|Artículo original]]
|
|-
| [[Whonix (Español)]]
| {{Grey|4}}
| [[Whonix|Artículo original]]
|
|-
| [[Wii hacking (Español)]]
| {{Grey|4}}
| [[Wii hacking|Artículo original]]
|
|-
| [[Wiimote (Español)]]
| {{Grey|4}}
| [[Wiimote|Artículo original]]
|
|-
| [[Window Maker (Español)]]
| {{Grey|4}}
| [[Window Maker|Artículo original]]
|
|-
| [[Windows PE (Español)]]
| {{Grey|4}}
| [[Windows PE|Artículo original]]
|
|-
| [[Wine package guidelines (Español)]]
| {{Grey|4}}
| [[Wine package guidelines|Artículo original]]
|
|-
| [[WireGuard (Español)]]
| {{Grey|4}}
| [[WireGuard|Artículo original]]
|
|-
| [[Wireless bonding (Español)]]
| {{Grey|4}}
| [[Wireless bonding|Artículo original]]
|
|-
| [[Wolfenstein: Enemy Territory (Español)]]
| {{Grey|4}}
| [[Wolfenstein: Enemy Territory|Artículo original]]
|
|-
| [[Wordpress (Español)]]
| {{Grey|4}}
| [[Wordpress|Artículo original]]
|
|-
| [[Working with the serial console (Español)]]
| {{Grey|4}}
| [[Working with the serial console|Artículo original]]
|
|-
| [[Wvdial (Español)]]
| {{Grey|4}}
| [[Wvdial|Artículo original]]
|
|-
| [[X keyboard extension (Español)]]
| {{Grey|4}}
| [[X keyboard extension|Artículo original]]
|
|-
| [[X Logical Font Description (Español)]]
| {{Grey|4}}
| [[X Logical Font Description|Artículo original]]
|
|-
| [[X resources (Español)]]
| {{Grey|4}}
| [[X resources|Artículo original]]
|
|-
| [[X10 (Español)]]
| {{Grey|4}}
| [[X10|Artículo original]]
|
|-
| [[X11vnc (Español)]]
| {{Grey|4}}
| [[X11vnc|Artículo original]]
|
|-
| [[X2Go (Español)]]
| {{Grey|4}}
| [[X2Go|Artículo original]]
|
|-
| [[Xbindkeys (Español)]]
| {{Grey|4}}
| [[Xbindkeys|Artículo original]]
|
|-
| [[Xc3sprog (Español)]]
| {{Grey|4}}
| [[Xc3sprog|Artículo original]]
|
|-
| [[XDG Base Directory (Español)]]
| {{Grey|4}}
| [[XDG Base Directory|Artículo original]]
|
|-
| [[XDG MIME Applications (Español)]]
| {{Grey|4}}
| [[XDG MIME Applications|Artículo original]]
|
|-
| [[XDG user directories (Español)]]
| {{Grey|4}}
| [[XDG user directories|Artículo original]]
|
|-
| [[Xdg-menu (Español)]]
| {{Grey|4}}
| [[Xdg-menu|Artículo original]]
|
|-
| [[Xdg-open (Español)]]
| {{Grey|4}}
| [[Xdg-open|Artículo original]]
|
|-
| [[Xdg-utils (Español)]]
| {{Grey|4}}
| [[Xdg-utils|Artículo original]]
|
|-
| [[XDM (Español)]]
| {{Grey|4}}
| [[XDM|Artículo original]]
|
|-
| [[XDMCP (Español)]]
| {{Grey|4}}
| [[XDMCP|Artículo original]]
|
|-
| [[Xdotool (Español)]]
| {{Grey|4}}
| [[Xdotool|Artículo original]]
|
|-
| [[Xev (Español)]]
| {{Grey|4}}
| [[Xev|Artículo original]]
|
|-
| [[XFS (Español)]]
| {{Grey|4}}
| [[XFS|Artículo original]]
|
|-
| [[Xfwm (Español)]]
| {{Grey|4}}
| [[Xfwm|Artículo original]]
|
|-
| [[Xhost (Español)]]
| {{Grey|4}}
| [[Xhost|Artículo original]]
|
|-
| [[Xiaomi Mi Notebook Air 13.3 (2016) (Español)]]
| {{Grey|4}}
| [[Xiaomi Mi Notebook Air 13.3 (2016)|Artículo original]]
|
|-
| [[Xiaomi Mi Notebook Air 13.3 (2018 Global version) (Español)]]
| {{Grey|4}}
| [[Xiaomi Mi Notebook Air 13.3 (2018 Global version)|Artículo original]]
|
|-
| [[Xilinx ISE WebPACK (Español)]]
| {{Grey|4}}
| [[Xilinx ISE WebPACK|Artículo original]]
|
|-
| [[Xilinx Vivado (Español)]]
| {{Grey|4}}
| [[Xilinx Vivado|Artículo original]]
|
|-
| [[Xmobar (Español)]]
| {{Grey|4}}
| [[Xmobar|Artículo original]]
|
|-
| [[Xmodmap (Español)]]
| {{Grey|4}}
| [[Xmodmap|Artículo original]]
|
|-
| [[Xmonad (Español)]]
| {{Grey|4}}
| [[Xmonad|Artículo original]]
|
|-
| [[Xorg multiseat (Español)]]
| {{Grey|4}}
| [[Xorg multiseat|Artículo original]]
|
|-
| [[Xpra (Español)]]
| {{Grey|4}}
| [[Xpra|Artículo original]]
|
|-
| [[Xrandr (Español)]]
| {{Grey|4}}
| [[Xrandr|Artículo original]]
|
|-
| [[Xrdb (Español)]]
| {{Grey|4}}
| [[Xrdb|Artículo original]]
|
|-
| [[Xterm (Español)]]
| {{Grey|4}}
| [[Xterm|Artículo original]]
|
|-
| [[Xtrabackup (Español)]]
| {{Grey|4}}
| [[Xtrabackup|Artículo original]]
|
|-
| [[XWiki (Español)]]
| {{Grey|4}}
| [[XWiki|Artículo original]]
|
|-
| [[Yandex Disk (Español)]]
| {{Grey|4}}
| [[Yandex Disk|Artículo original]]
|
|-
| [[YubiKey (Español)]]
| {{Grey|4}}
| [[YubiKey|Artículo original]]
|
|-
| [[Zabbix (Español)]]
| {{Grey|4}}
| [[Zabbix|Artículo original]]
|
|-
| [[Zathura (Español)]]
| {{Grey|4}}
| [[Zathura|Artículo original]]
|
|-
| [[Zeitgeist (Español)]]
| {{Grey|4}}
| [[Zeitgeist|Artículo original]]
|
|-
| [[ZeroNet (Español)]]
| {{Grey|4}}
| [[ZeroNet|Artículo original]]
|
|-
| [[Zerotier (Español)]]
| {{Grey|4}}
| [[ZeroTier|Artículo original]]
|
|-
| [[ZFS (Español)]]
| {{Grey|4}}
| [[ZFS|Artículo original]]
|
|-
| [[ZFS (Español)/Virtual disks (Español)]]
| {{Grey|4}}
| [[ZFS/Virtual disks|Artículo original]]
|
|-
| [[Zim (Español)]]
| {{Grey|4}}
| [[Zim|Artículo original]]
|
|-
| [[ZNC (Español)]]
| {{Grey|4}}
| [[ZNC|Artículo original]]
|
|-
| [[ZoneMinder (Español)]]
| {{Grey|4}}
| [[ZoneMinder|Artículo original]]
|
|-
| [[Zswap (Español)]]
| {{Grey|4}}
| [[Zswap|Artículo original]]
|
|-
| [[ZTE MF 823 (Megafon M100-3) 4G Modem (Español)]]
| {{Grey|4}}
| [[ZTE MF 823 (Megafon M100-3) 4G Modem|Artículo original]]
|
|-
| [[ZTE MF110/MF190 (Español)]]
| {{Grey|4}}
| [[ZTE MF110/MF190|Artículo original]]
|
|}

MythTV

2026-05-12T15:58:44Z

Erus Iluvatar: rm mentions of mythweb as it's been dropped from the AUR + a fix a few missing newlines/spelling

[[Category:Home theater]]
[[ja:MythTV]]
[https://www.mythtv.org/ MythTV] is an application suite designed to provide an amazing multimedia experience.
It provides PVR functionality to a Linux based computer and also supports other media types.
Combined with a nice, quiet computer and a decent TV, it makes an excellent centerpiece to a home theater system.

== Structure ==

The MythTV system is split into a backend and a frontend. Each component has its own functions:

=== mythbackend ===

* Schedule and record television programming
* Stream video data to the frontend
* Flag commercial breaks
* Transcode videos from one format to another

=== mythfrontend ===

* Provide a pretty GUI
* Play back recorded content
* Provide an interface to schedule programs

The frontend and backend may be on separate computers on a network, and there may also be multiple frontends. This architecture allows for a central media distribution system that can reach anywhere a network can. This is a remarkably flexible system, and it even allows very low power machines to act as perfectly usable frontends.

== Hardware requirements ==

All systems are going to need a tuner card. The Hauppauge PVR series of cards (150, 250, 350, and 500) are very popular for use with MythTV due to fairly decent Linux support and low CPU usage. Other cards, like those based on the BT878 chipset, are also used. Unlike the PVR series, BT878 based cards require significant amounts of CPU power to save the video, as these cards output raw frames and not compressed streams.

== Software requirements ==

A working [[Xorg]] (graphical) environment is necessary. For setting MythTV up, a remote access via X11-forwarding mechanism is sufficient.

== Installation ==

[[Install]] the {{AUR|mythtv-git}} package and [https://aur.archlinux.org/packages/?K=mythplugins- any desired plugins]. The package creates the ''mythtv'' user.

At this point a generic MythTV installation is present that must be refined into a backend, a frontend, or both.

{{Note|You can have ansible install your dependencies, see [https://github.com/MythTV/ansible].}}

=== Backend setup ===

Before setting up your backend, make sure you have a functioning ''video capture card'' or a ''firewire input from a STB''. Unfortunately, that part of setup is outside the scope of this article. If you are in the United States, get an account at [https://www.schedulesdirect.org Schedules Direct] (this service provides TV listings at a minimal cost). Users outside the United States will need to use screen scrapers ([http://wiki.xmltv.org/index.php/Main_Page/ xmltv]) to do the same job.

==== Setting up the database ====

{{Note|This is a quick and dirty walk through of MariaDB. Be sure you read the [[MariaDB]] article for more details.}}

[[Install]] {{Pkg|mariadb}} and [[start]] {{ic|mysqld.service}}.

{{Out of date|This behavior seems to have changed and is reversed now. See [[MariaDB#Enable access locally only via Unix sockets]].}}

If other machines in the LAN are expected to connect to the masterbackend server, comment out the "skip-networking" line in {{ic|/etc/mysql/my.cnf}} at this point.

Setup mysql with a password:

# mysql_secure_installation

Create the database structure:

$ mysql -u root -p </usr/share/mythtv/mc.sql

If you have lost or overwritten your mc.sql file, it is always available [https://github.com/MythTV/mythtv/blob/master/mythtv/database/mc.sql here].

Update your database

# mysql_upgrade -u root -p

MythTV requires time zone tables are required to be in MySQL, add them:

mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root -p<yourpassword> mysql

Some setups refuse frontends from remote machines. To fix this:

# mysql -u root -p
mysql> GRANT ALL ON mythconverg.* TO 'user'@'host.net' IDENTIFIED BY 'password';
Query OK, 0 rows affected (0.00 sec)
mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.00 sec)

* Replace '''user''' with the user name running on the frontend (default: mythtv).
* Replace '''host.net''' with the host name or IP address of the remote box needing access. Other common values are ''%.local'' and ''192.168.1.%''.
* Replace '''password''' with a suitable password (default: mythtv).
{{Note|MySQL / MariaDB treats a "user@host.net" and "user@192.168.1.1" as completely separate users, therefore you may need to use both types}}

Example:

# mysql -u root -p
mysql> GRANT ALL ON mythconverg.* TO 'mythtv'@'192.168.0.%' IDENTIFIED BY 'mythtv';
Query OK, 0 rows affected (0.00 sec)
mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.00 sec)

==== Setting up the master backend ====

Load up your WM (lxde is a good choice for light-weight builds, but anything will work.)

{{Note|Users wishing to just demo the software and those without capture card/hardware may follow [https://motorscript.com/mythtv-without-tv-tuner-card this] guide.}}

Now run the mythtv-setup program

$ mythtv-setup

{{Note|Alternatively, in v32 and above you can use the WebUI to setup mythtv, <nowiki>http://localhost:6544</nowiki>}}

If your backend runs on a headless server, ''mythtv-setup'' can be run via [[OpenSSH#X11 forwarding]] by running:
$ ssh -X user@backend '. /etc/profile.d/perlbin.sh && LANG=C.UTF-8 mythtv-setup'

* '''General menu'''
:If this is your master backend, put its IP address in the first and fourth fields, identifying this computer as your master and giving its network IP address.
:On the next page, enter the paths where recordings and the live TV buffer will be stored. LVM or RAID solutions provide easily accessible large scale storage. But again, those are outside the scope of this article. Set the live TV buffer to a size you can handle and leave everything else alone.
:On the next page, set the settings to your locale. NTSC is mostly used in North America, and be sure to set whether using cable or broadcast.
:On the next two pages, leave everything as is unless you know for sure you want to change it.
:On the next page, if you have a fast backend that can handle recordings and flagging jobs simultaneously, it is recommended to set CPU usage to "High", maximum simultaneous jobs to 2, and to check the commercial flagging option.
:On the next page, set these options to taste. Automatic commercial flagging is highly recommended.
:Ignore the next page and finish.

* '''Capture card menu'''
:Select your card type from the drop down list. Hauppauge PVR users will select the MPEG-2 encoder card option.
:Point mythtv-setup to the proper location, usually {{ic|/dev/v4l/video0}}

* '''Video sources menu'''
:This is where it gets important to have a source for TV listings. Schedules Direct users should create a new video source, name it, select the North America (Schedules Direct) option, and fill in their logon information. In order to verify that it is correct, go ahead and retrieve the listings.
{{Note|As of MythTV v31, SchedulesDirect uses the xmltv format. Install {{AUR|xmltv}} from the AUR and follow instructions [https://www.mythtv.org/wiki/XMLTV here.]}}

* '''Input connections menu'''
:This menu is rather self-explanatory. All you need to do is pick an input on the capture card and tell myth which video source it connects to. Most users will select their tuner and leave all the other inputs alone. Satellite users will select a video input, and on the next page provide the command to change channels on their STB using an external channel change program. This is also outside the scope of this article.

* '''Channel editor menu'''
:This menu is safe to ignore

* Exit the program (Esc)

* Run mythfilldatabase
$ mythfilldatabase

This should populate your mysql database with TV listings for the next two weeks (or so).

==== Enable the mythbackend daemon ====

[[Enable]] the {{ic|mythbackend.service}} systemd unit.

=== Troubleshooting ===

==== PVR150 ====

If you cannot open {{ic|/dev/video0}} of your PVR150, install the firmware, located in the {{AUR|ivtv-utils}} package.

==== Opening DVB frontend device failed ====

The kernel takes time to register the frontend devices (such as those of TurboSight TBS 62x1) and they may not be available when systemd starts {{ic|mythbackend.service}}. This leads to the following error recorded in the system log:
# DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
# eno:No such file or directory (2)
# DVBChan[1](/dev/dvb/adapter0/frontend0): Failed to open DVB frontend device due to fatal error or too many attempts.
# ChannelBase: CreateChannel() Error: Failed to open device /dev/dvb/adapter0/frontend0
# Problem with capture cardsCard 1failed init

The solution consists in starting the {{ic|mythbackend.service}} only after the devices are available:
* [[textedit|Create]] file {{ic|/etc/udev/rules.d/99-mythbackend.rules}}:
#
# Create systemd device units for capture devices
#
SUBSYSTEM=="video4linux", TAG+="systemd"
SUBSYSTEM=="dvb", TAG+="systemd"
SUBSYSTEM=="firewire", TAG+="systemd"
* Create a [[drop-in unit file]] for {{ic|mythbackend.service}} as follows:
{{hc|1=/etc/systemd/system/mythbackend.service.d/override.conf|2=
# [Unit]
# After=dev-dvb-adapter0-frontend0.device
# Wants=dev-dvb-adapter0-frontend0.device
}}
See MythTV wiki's page [https://www.mythtv.org/wiki/Systemd_mythbackend_Configuration#Delay_starting_the_backend_until_tuners_have_initialized Systemd mythbackend Configuration] for further details.

== Frontend setup ==

Compared to the backend, getting a frontend running is simple. The frontend machine needs permission to access the database on the backend machine. On the backend machine, follow the instructions to grant remote access in the [[MariaDB]] article. On the frontend machine, install the mythtv packages using pacman as above. Afterward, make sure you are in an X environment as a normal user and run mythfrontend. It will pop up a menu asking about the IP address of the backend and the local computer's name and IP address. Fill in this information and your frontend should be functional.

On the other hand, the frontend has more options than a luxury car. All of those are an article on their own. There are a few notable options that should be set to ensure a good working setup. If you do not have an interlaced monitor (and almost nobody does), you will need to deinterlace your television output. Go into the TV playback menu and select kernel deinterlacing or bob2x deinterlacing. Try both and see which you like better. Also, in the general settings page, it is good to set up your ''ALSA setup'' settings, but those vary so greatly it is not worth suggesting values here.

== MythTV plugins ==

There are a number of plugins available for MythTV in the AUR. They range from RSS readers to DVD players. Take a look at them. Simply installing the package on the frontend computer should impart the intended functionality. There is rarely any additional setup, and when there is, the install file will mention it.

== Hints to a Happy Myth System ==

But not full articles (yet)
* Run ntpd or openntpd on your backend to make sure it always has the right time.
* [[LIRC]] on your frontend allows you to use a remote control, which is wonderful in a living room.
* Use gdm, sddm, or xdm to automatically log in your frontend, and ~/.xinitrc to load mythfrontend on boot.
* Set the "automatically run mythfilldatabase" option on one of your frontends to make sure you always have listings.
* Do not forget to use the verbosity statements and log file location arguments to mythfrontend so you can see when things break.
* Do not run your frontend as root, create a mythtv user

=== Using GDM to autologin your Mythfrontend ===

In {{ic|/etc/gdm/custom.conf}}, add the following statements under the [daemon] heading:
{{bc|1=
AutomaticLoginEnable=true
AutomaticLogin=mythtv (assuming your frontend user is mythtv)}}
FYI - GDM will not autologin as root

=== Using XDM to automically login to your MythFrontend ===
{{Out of date|We don't use /etc/inittab anymore.}}
Find in your /etc/inittab file the following line:
id:3:initdefault:

Change to:
id:5:initdefault:

Then add the following below it (or anywhere in the file):
x:5:respawn:su - MYTHUSER -c startx

{{Note|Remember to change "MYTHUSER" to the username that you want to autologin under.}}

If you would like to start mythfrontend on booting into Xorg, edit (or create if none exists) your MYTHUSER's .xinitrc file and add the following line:
mythfrontend

=== Optmize your system ===

Be sure to have a look at [https://www.mythtv.org/wiki/Optimizing_Performance Optimizing Performance] at the MythTV Wiki for how to keep your data stores happy, as well as optimize your system in various other ways to get the most out of your Myth box.

== References ==

* https://www.mythtv.org/
* https://www.mythtv.org/wiki/
* http://www.linhes.org A user friendly MythTV and Linux install that uses Arch Linux

Radicle

2026-05-12T15:05:31Z

Erus Iluvatar: /* Configuration */ there's the user unit redirect + fix spacing :)

[[Category:Git web interfaces]]
[[Category:Commands]]
[[Category:Peer-to-peer]]
{{Related articles start}}
{{Related|Git}}
{{Related|Forgejo}}
{{Related articles end}}

:"[https://radicle.xyz Radicle] is an open source, peer-to-peer code collaboration stack built on Git. Unlike centralized code hosting platforms, there is no single entity controlling the network. Repositories are replicated across peers in a decentralized manner, and users are in full control of their data and workflow." - from [https://radicle.xyz radicle.xyz].

See [https://radicle.xyz/guides upstream documentation] for any missing parts.

Radicle, though great, has some notable missing features compared to [[Forgejo]]:
* The web frontend is purely '''read-only''', interaction is done only via the [[wikipedia:command-line interface|CLI]] or the [https://app.radicle.xyz/nodes/iris.radicle.xyz/rad:z4D5UCArafTzTQpDZNQRuqswh3ury desktop application].
* No "releases". Unless you count git tags.
* No built-in "project management", e.g [[wikipedia:kanban|kanban]]. See [[#Planning board/kanban]].
* Relatively simple issue management with assigning, commenting, reacting & tagging.
** No "milestones", "due date" or "dependencies".
* No bundled [https://forgejo.org/docs/latest/user/packages/ package registries], you will have to use a separate programs.

If you're alright without those features, or find the minimalism itself a feature, then continue on.

{{Note|Not to be confused with the CalDav server [[Radicale]].}}

== Installation ==

[[Install]] the {{AUR|radicle-bin}} package which includes {{AUR|radicle-cli-bin}} and {{AUR|radicle-node-bin}}.

== Configuration ==

First we need to generate our Radicle DID (Decentralized Identifier):

$ rad auth

We can also query the DID with:

$ rad self

To be able to have any peer to peer communications, we need to have our node up and running. [[Start/enable]] {{ic|radicle-node.service}} [[user unit]].

We can query the node's status with:

$ rad node status

== Usage ==

Radicle manages issues and content distribution, but the core is still [[git]], so make sure you're familiar with it.

In an already initialized git repository, create a globally unique Repository ID (RID).
$ rad init

This creates a new remote "rad".
$ git remote show rad

We can now locally or remotely clone the repository with the shown "Fetch URL". We can also emit the "//" from the command.
$ rad clone rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5

The example RID is for [https://app.radicle.xyz/nodes/iris.radicle.xyz/rad%3Az3gqcJUoA1n9HaHKufZs5FCSGazv5 heartwood], the backbone for radicle.

We can also just seed the repository without checking it out.
$ rad seed rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5
And to stop seeding:
$ rad unseed rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5

The seeded repositories storage directory is mentioned in {{ic|rad self}} as "Home" => "Storage".
We can list all, including seeded, repositories with:
$ rad ls --all

=== Managing Issues ===

Radicle bundles issues with the repository.
$ rad issue

== Seed node Setup ==

Node uptime isn't guaranteed for regular users, so having a dedicated server to [[wikipedia: Glossary_of_BitTorrent_terms#Seed_.2F_seeding|seed]] your repository is a good idea.

Also see [https://radicle.xyz/guides/seeder upstream guide].

Instead of running {{ic|rad seed}} for every new repository you might create. It's simpler to "follow" your node to automatically seed every published repository.
$ rad follow

=== Frontend Web Server Setup ===

Since radicle is decentralized, there is no real need for a server, but for users not using radicle, it can be used to introduce them and to clone with regular [[git]].

Note that the frontend is purely '''read-only'''. You can not "log in" nor create issues with it.

Frontend maintained by the core team: https://app.radicle.xyz/

[[Install]] the {{AUR|radicle-httpd-bin}}

== Tips and tricks ==

=== CI/CD ===

See [https://app.radicle.xyz/nodes/rosa.radicle.xyz/rad%3AzwTxygwuz5LDGBq255RA2CbNGrz8 radicle-ci-broker].

=== Migrating from github/gitlab ===

See [https://app.radicle.xyz/nodes/seed.radicle.gr/rad:z2UyZq9x68YFvZ4xrKf1JbQD3pmRU radicle-migration-tool].

=== Planning board/kanban ===

See [https://app.radicle.xyz/nodes/seed.radicle.gr/rad:z2BdUVZFvHdxRfdtGJQdSH2kyXNM6 radicle-planning-boards].

Systemd-boot

2026-05-12T10:14:46Z

Erus Iluvatar: /* Configuration */ actually, kernel-install here refers to the tool and not a command, so it needs to be in italics instead of an ic template

{{Lowercase title}}
[[Category:Boot loaders]]
[[de:Systemd-boot]]
[[es:Systemd-boot]]
[[fr:Systemd-boot]]
[[hu:Systemd-boot]]
[[ja:Systemd-boot]]
[[pt:Systemd-boot]]
[[ru:Systemd-boot]]
[[zh-hans:Systemd-boot]]
{{Related articles start}}
{{Related|Arch boot process}}
{{Related|Secure Boot}}
{{Related|Unified Extensible Firmware Interface}}
{{Related articles end}}

{{man|7|systemd-boot}}, previously called '''gummiboot''' (German for "rubber dinghy") and sometimes referred to as ''sd-boot'', is an easy-to-configure [[UEFI]] [[boot manager]]. It provides a textual menu to select the boot entry and an editor for the kernel command line.

Note that ''systemd-boot'' can only start EFI executables (e.g., the Linux kernel [[EFI boot stub]], [[UEFI shell]], [[GRUB]], or the [https://learn.microsoft.com/en-us/windows-hardware/drivers/bringup/boot-and-uefi#understanding-the-windows-boot-manager Windows Boot Manager]) from the [[EFI system partition]] it is installed to or from an Extended Boot Loader Partition (XBOOTLDR partition) on the same disk.

{{Note|In the entire article {{ic|''esp''}} denotes the mountpoint of the [[EFI system partition]] and {{ic|''boot''}} denotes the mountpoint of the optional XBOOTLDR partition. It is assumed that you have [[chroot]]ed to the system's mount point.}}

== Supported file systems ==

systemd-boot inherits the support for the file systems [[Arch boot process#UEFI|from the firmware]] (i.e. at least FAT12, FAT16 and FAT32). Additionally it loads any [[Unified Extensible Firmware Interface#UEFI drivers|UEFI drivers]] placed in {{ic|''esp''/EFI/systemd/drivers/}}.

== Installation ==

''systemd-boot'' is shipped with the {{Pkg|systemd}} package which is a dependency of the {{Pkg|base}} meta package, so no additional packages need to be installed manually.

== Installing the UEFI boot manager ==

To install ''systemd-boot'', first make sure that the system is booted into UEFI mode and [[Unified Extensible Firmware Interface#UEFI variables|UEFI variables]] are accessible. This can be verified by running {{ic|efivar --list}} or, if {{Pkg|efivar}} is not installed, by running {{ic|ls /sys/firmware/efi/efivars}} (if the directory exists, the system is booted into UEFI mode.)

Use {{man|1|bootctl}} to install ''systemd-boot'' to the ESP:

# bootctl install

This will copy the ''systemd-boot'' UEFI boot manager to the ESP, create a UEFI boot entry for it and set it as the first in the UEFI boot order.

* On an x64 UEFI, {{ic|/usr/lib/systemd/boot/efi/systemd-bootx64.efi}} will be copied to {{ic|''esp''/EFI/systemd/systemd-bootx64.efi}} and {{ic|''esp''/EFI/BOOT/BOOTX64.EFI}}.
* On an IA32 UEFI, {{ic|/usr/lib/systemd/boot/efi/systemd-bootia32.efi}} will be copied to {{ic|''esp''/EFI/systemd/systemd-bootia32.efi}} and {{ic|''esp''/EFI/BOOT/BOOTIA32.EFI}}.

The UEFI boot entry will be called "Linux Boot Manager" and will point to, depending on the [[Unified Extensible Firmware Interface#UEFI firmware bitness|UEFI bitness]], either {{ic|\EFI\systemd\systemd-bootx64.efi}} or {{ic|\EFI\systemd\systemd-bootia32.efi}} on the ESP.

{{Note|
* When running {{ic|bootctl install}}, ''systemd-boot'' will try to locate the ESP at {{ic|/efi}}, {{ic|/boot}}, and {{ic|/boot/efi}}. Setting {{ic|''esp''}} to a different location requires passing the {{ic|1=--esp-path=''esp''}} option. (See {{man|1|bootctl|OPTIONS}} for details.)
* Installing ''systemd-boot'' will overwrite any existing {{ic|''esp''/EFI/BOOT/BOOTX64.EFI}} (or {{ic|''esp''/EFI/BOOT/BOOTIA32.EFI}} on IA32 UEFI), e.g. Microsoft's version of the file.
* ''bootctl'' refrains from operating on UEFI variables/boot entries when running in pid namespace, which is the case for {{man|8|arch-chroot}}'s non-systemd mode. To create the boot entry in the chroot environment, use {{ic|arch-chroot -S}} instead.
}}

To conclude the installation, [[#Configuration|configure]] ''systemd-boot''.

=== Installation using XBOOTLDR ===

{{Move|Partitioning#Discrete partitions|All partitioning info should be moved to partitioning, to leave only steps relevant to installing systemd-boot if you have such a setup.}}

A separate [[Partitioning#/boot|/boot partition]] of type "Linux extended boot" (XBOOTLDR) can be created to keep the kernel and initramfs separate from the ESP. This is particularly helpful to [[dual boot with Windows]] with an existing ESP that is too small. [[#Grml on ESP|Grml]] or [[#Archiso on ESP|Archiso]] are also possible use cases.

Prepare an ESP as usual and create another partition for XBOOTLDR on the same physical drive. The XBOOTLDR partition must have a partition type GUID of {{ic|bc13c2ff-59e6-4262-a352-b275fd6f7172}} [https://uapi-group.org/specifications/specs/boot_loader_specification/] ({{ic|ea00}} type for [[gdisk]], {{ic|xbootldr}} type for [[fdisk]]). The size of the XBOOTLDR partition should be large enough to accommodate all of the kernels you are going to install.

{{Note|
* ''systemd-boot'' does not do a file system check like it does for the ESP. Hence, it is possible to use any file system that your UEFI implementation can read.
* UEFI may skip loading partitions other than the ESP when a "fast boot" mode is enabled. This can lead to ''systemd-boot'' failing to find entries on the XBOOTLDR partition; in that case, disable the "fast boot" mode.
* The XBOOTLDR partition must be on the same physical disk as the ESP for ''systemd-boot'' to recognize it.
}}

During install, mount the ESP to {{ic|/mnt/efi}} and the XBOOTLDR partition to {{ic|/mnt/boot}}.

Once in chroot, use the command:

# bootctl --esp-path=/efi --boot-path=/boot install

To conclude the installation, [[#Configuration|configure]] ''systemd-boot''.

=== Updating the UEFI boot manager ===

Whenever there is a new version of ''systemd-boot'', the UEFI boot manager can be optionally reinstalled by the user. This can be done manually or automatically; the two approaches are described thereafter.

{{Note|The UEFI boot manager is a standalone EFI executable and any version can be used to boot the system (partial updates do not apply, since pacman only installs the ''systemd-boot'' installer, not ''systemd-boot'' itself.) However, new versions may add new features or fix bugs, so it is probably a good idea to update ''systemd-boot''.}}

{{Warning|If you have [[Secure Boot]] enabled, you need to sign the boot manager update. See [[#Signing for Secure Boot]].}}

==== Manual update ====

Use ''bootctl'' to update ''systemd-boot'':

# bootctl update

{{Note|As with {{ic|bootctl install}}, ''systemd-boot'' will try to locate the ESP at {{ic|/efi}}, {{ic|/boot}}, and {{ic|/boot/efi}}. Setting {{ic|''esp''}} to a different location requires passing the {{ic|1=--esp-path=''esp''}} option.}}

==== Automatic update ====

To update ''systemd-boot'' automatically, either use a [[systemd#Using units|systemd service]] or a [[pacman hook]]. The two methods are described below.

===== systemd service =====

As of version 250, {{Pkg|systemd}} ships with {{ic|systemd-boot-update.service}}. [[Enabling]] this service will cause systemd-boot to run the following command on every boot:

# bootctl --variables=no --graceful update

Like in the [[#Manual update|manual update]], this will attempt to locate the ESP at {{ic|/efi}}, {{ic|/boot}} or {{ic|/boot/efi}}. The command will update all installed versions of systemd-boot in the ESP if a newer version is available in {{ic|/usr/lib/systemd/boot/efi/}}. It will look for a systemd-boot file ending in {{ic|.efi.signed}} first to allow users to sign the image for use with [[Secure Boot]].

===== pacman hook =====

The package {{AUR|systemd-boot-pacman-hook}} adds a pacman hook which is executed every time {{Pkg|systemd}} is upgraded. This hook differs from the [[#systemd service|systemd service method]] in that it only attempts to update the boot manager when {{Pkg|systemd}} is updated rather than every boot, and it does it immediately rather than waiting until after the next boot.

Rather than installing the AUR package, you may prefer to manually place the following file in {{ic|/etc/pacman.d/hooks/}}:

{{hc|/etc/pacman.d/hooks/95-systemd-boot.hook|2=
[Trigger]
Type = Package
Operation = Upgrade
Target = systemd

[Action]
Description = Gracefully upgrading systemd-boot...
When = PostTransaction
Exec = /usr/bin/systemctl restart systemd-boot-update.service
}}

=== Signing for Secure Boot ===

If you have [[Secure Boot]] enabled, you may want to add a pacman hook to automatically sign the boot manager upon every upgrade of the package:

{{hc|/etc/pacman.d/hooks/80-secureboot.hook|2=
[Trigger]
Operation = Install
Operation = Upgrade
Type = Path
Target = usr/lib/systemd/boot/efi/systemd-boot*.efi

[Action]
Description = Signing systemd-boot EFI binary for Secure Boot
When = PostTransaction
Exec = /bin/sh -c 'while read -r f; do /usr/lib/systemd/systemd-sbsign sign --private-key ''/path/to/keyfile.key'' --certificate ''/path/to/certificate.crt'' --output "${f}.signed" "$f"; done;'
Depends = sh
NeedsTargets
}}

Replace {{ic|''/path/to/keyfile.key''}} and {{ic|''/path/to/certificate.crt''}} with your signing key and certificate respectively. For better understanding of this hook, consult {{man|1|systemd-sbsign}}.

The created {{ic|/usr/lib/systemd/boot/efi/systemd-boot*.efi.''signed''}} will automatically be picked up by {{ic|bootctl install}} or {{ic|bootctl update}}. See {{man|1|bootctl|SIGNED .EFI FILES}}.

As an alternative, use [[Unified Extensible Firmware Interface/Secure Boot#Automatic signing with the pacman hook|sbctl]].

== Configuration ==

{{Tip|
* After changing the configuration, run {{ic|bootctl}} (without any arguments) to make sure that systemd-boot will be able to parse it properly.
* ''kernel-install'' can be used to automate this process.
}}

=== Loader configuration ===

The loader configuration is stored in the file {{ic|''esp''/loader/loader.conf}}. See {{man|5|loader.conf|OPTIONS}} for details.

A loader configuration example is provided below:

{{hc|''esp''/loader/loader.conf|
default arch.conf
timeout 4
console-mode max
editor no
}}

{{Tip|
* {{ic|default}} and {{ic|timeout}} can be changed in the boot menu itself and changes will be stored as UEFI variables {{ic|LoaderEntryDefault}} and {{ic|LoaderConfigTimeout}}, overriding these options.
* {{ic|bootctl set-default ""}} and {{ic|bootctl set-timeout ""}} can be used to clear the UEFI variables overriding the {{ic|default}} and {{ic|timeout}} options, respectively.
* If you have set {{ic|timeout 0}}, the boot menu can be accessed by pressing {{ic|Space}}.
* A basic loader configuration file is located at {{ic|/usr/share/systemd/bootctl/loader.conf}}.
* If the boot manager—during the entry selection—appears distorted/uses the wrong resolution you can try to set the {{ic|console-mode}} to {{ic|auto}} (uses heuristics to select the best resolution), {{ic|keep}} (keeps the firmware provided resolution) or {{ic|2}} (tries to select the first non-UEFI-standard resolution).
}}

==== Remember last entry ====

The {{ic|default}} can be changed to {{ic|@saved}} in order to remember the last picked entry on startup. This is useful for when dual booting Windows and the surprise windows auto update pushes you into Linux.

{{hc|''esp''/loader/loader.conf|
default @saved
...
}}

Consult {{man|5|loader.conf}} for more details.

=== Adding loaders ===

''systemd-boot'' will search for ''.conf'' files in {{ic|/loader/entries/}} on the [[EFI system partition]] it was launched from and additionally the [[#Installation using XBOOTLDR|XBOOTLDR]] partition on the same disk.

{{Note|
* Entries in {{ic|''esp''/loader/entries/*.conf}} can only use files (e.g. kernels, initramfs, images, etc.) in {{ic|''esp''/}} and entries in {{ic|''boot''/loader/entries/*.conf}} can only use files in {{ic|''boot''/}}.
* The file path parameters are relative to the root of your EFI system partition or XBOOTLDR partition. E.g., if your EFI system partition or XBOOTLDR partition is mounted at {{ic|/boot}}, then the {{ic|/boot/vmlinuz-linux}} file must be specified in the {{ic|linux}} key as {{ic|/vmlinuz-linux}}.
* When [[Secure Boot]] is active, [[unified kernel image]]s (UKIs) with an embedded {{ic|.cmdline}} ignore all command line options passed to them (either using a boot entry with {{ic|options}} or interactively). When Secure Boot is not active, the options passed via the command line override the embedded {{ic|.cmdline}}.
}}

An example of loader files launching Arch from a volume using its [[UUID]] {{ic|''xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx''}} is:

{{hc|''esp''/loader/entries/arch.conf|2=
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=UUID=''xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'' rw
}}

{{hc|''esp''/loader/entries/arch-fallback.conf|2=
title Arch Linux (fallback initramfs)
linux /vmlinuz-linux
initrd /initramfs-linux-fallback.img
options root=UUID=''xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'' rw
}}

See the [https://uapi-group.org/specifications/specs/boot_loader_specification/#type-1-boot-loader-specification-entries Boot Loader Specification] for details on all configuration options.

''systemd-boot'' will automatically check at boot time for '''Windows Boot Manager''' at the location {{ic|/EFI/Microsoft/Boot/Bootmgfw.efi}}, '''Apple macOS Boot Manager''' in firmware, [[UEFI shell]] {{ic|/shellx64.efi}} and '''EFI Default Loader''' {{ic|/EFI/BOOT/bootx64.efi}}, as well as specially prepared kernel files found in {{ic|/EFI/Linux/}}. When detected, corresponding entries with titles {{ic|auto-windows}}, {{ic|auto-osx}}, {{ic|auto-efi-shell}} and {{ic|auto-efi-default}}, respectively, will be generated. These entries do not require manual loader configuration. However, it does not auto-detect other EFI applications (unlike [[rEFInd]]), so for booting the Linux kernel, manual configuration entries must be created.

{{Tip|
* The available boot entries which have been configured can be listed with the command {{ic|bootctl list}}.
* An example entry file is located at {{ic|/usr/share/systemd/bootctl/arch.conf}}.
* The [[kernel parameters]] for scenarios such as [[LVM]], [[LUKS]], [[dm-crypt]] or [[Btrfs]] can be found on the relevant pages.
}}

{{Note|If [[Microcode#Microcode in a separate initramfs file|external microcode initramfs images]] are used (e.g. when using [[Booster]] as the initramfs generator), {{ic|/boot/amd-ucode.img}} or {{ic|/boot/intel-ucode.img}} must be specified in a separate {{ic|initrd}} and always be placed '''first''', before the main initramfs image.}}

==== UEFI Shells or other EFI applications ====

In case you installed a [[UEFI shell]] with the package {{Pkg|edk2-shell}}, ''systemd-boot'' will auto-detect and create a new entry if the EFI file is placed in {{ic|''esp''/shellx64.efi}}.
To perform this an example command after installing the package would be:

# cp /usr/share/edk2-shell/x64/Shell.efi /boot/shellx64.efi

Otherwise in case you installed [[rEFInd#Tools|other EFI applications]] into the ESP, you can use the following snippets.

{{Note|The file path parameter for the {{ic|efi}} line is relative to the root of your [[EFI system partition]]. If your EFI system partition is mounted at {{ic|/boot}} and your EFI binaries reside at {{ic|/boot/EFI/xx.efi}} and {{ic|/boot/yy.efi}}, then you would specify the parameters as {{ic|efi /EFI/xx.efi}} and {{ic|efi /yy.efi}} respectively.}}

{{hc|''esp''/loader/entries/fwupd.conf|
title Firmware updater
efi /EFI/tools/fwupdx64.efi
}}

{{hc|''esp''/loader/entries/gdisk.conf|
title GPT fdisk (gdisk)
efi /EFI/tools/gdisk_x64.efi
}}

===== Memtest86+ =====

You need to install {{Pkg|memtest86+-efi}} for this to work. Also sign the EFI binary when using Secure Boot.

{{hc|''esp''/loader/entries/memtest.conf|
title Memtest86+
efi /memtest86+/memtest.efi
}}

===== Netboot =====

''systemd-boot'' can chainload [[Netboot]]. Download the {{ic|ipxe-arch.efi}} EFI binary and signature, verify it and place it as proposed in {{ic|''esp''/EFI/arch_netboot/arch_netboot.efi}}.

{{hc|''esp''/loader/entries/arch_netboot.conf|
title Arch Linux Netboot
efi /EFI/arch_netboot/arch_netboot.efi
}}

===== GRUB =====

''systemd-boot'' can chainload [[GRUB]]. The location of the {{ic|grubx64.efi}} binary matches the used {{ic|--bootloader-id{{=}}}} when GRUB was installed to the ESP.

{{hc|''esp''/loader/entries/grub.conf|
title GRUB
efi /EFI/GRUB/grubx64.efi
}}

==== Boot from another disk ====

''systemd-boot'' [https://github.com/systemd/systemd/issues/3252 cannot] launch EFI binaries from partitions other than the ESP it is launched from or the XBOOTLDR partition on the same disk, but it can direct the [[UEFI shell]] to do so.

First, install {{Pkg|edk2-shell}} as [[#UEFI Shells or other EFI applications|described above]]. In the UEFI shell, use the ''map'' command to take notes of the '''FS alias''' (ex: HD0a66666a2, HD0b, FS1, or BLK7) of the partition with the corresponding PARTUUID.

Then, use the {{ic|exit}} command to boot back into Linux, where you can create a new loader entry to run the target EFI program through the UEFI shell:

{{hc|''esp''/loader/entries/windows.conf|
title Windows
efi /shellx64.efi
options -nointerrupt -nomap -noversion HD0b:EFI\Microsoft\Boot\Bootmgfw.efi
}}

Ensure that the {{ic|efi}} path matches the location where the {{ic|shellx64.efi}} has been copied in the ''esp'' partition. Also, note that the {{ic|shellx64.efi}} EFI file can be moved elsewhere to avoid the automatic entry creation by ''systemd-boot''.

Replace {{ic|HD0b}} with the previously noted ''FS alias''.

* The {{ic|-nointerrupt}} option prevents interrupting the target EFI program with {{ic|Ctrl+c}}.
* The {{ic|-nomap -noversion}} options hide the default UEFI shell greeting.
* To have the UEFI shell automatically return to the boot manager if the target EFI program exits (e.g. due to an error), add the {{ic|-exit}} option.
* You can also add the {{ic|-noconsoleout}} option if there is still unnecessary output in the UEFI shell.

=== Booting into UEFI firmware setup ===

systemd-boot will automatically add an entry to boot into UEFI firmware setup if your device's firmware supports rebooting into setup from the OS.

=== Kernel parameters editor with password protection ===

Alternatively you can install {{AUR|systemd-boot-password}} which supports {{ic|password}} basic configuration option. Use {{ic|sbpctl generate}} to generate a value for this option.

Install ''systemd-boot-password'' with the following command:

# sbpctl install ''esp''

With enabled editor you will be prompted for your password before you can edit kernel parameters.

== Tips and tricks ==

=== Keys inside the boot menu ===

You can use {{ic|t}} and {{ic|T}} while in the menu to adjust the menu timeout and {{ic|e}} to edit the kernel parameters for this boot. Press {{ic|h}} to see a short list of useful hotkeys. See {{man|7|systemd-boot|KEY BINDINGS}} for the full list of available key bindings inside the boot menu.

=== Choosing next boot ===

The boot manager is integrated with the systemctl command, allowing you to choose what option you want to boot after a reboot. For example, suppose you have built a custom kernel and created an entry file {{ic|''esp''/loader/entries/arch-custom.conf}} to boot into it, you can just launch

$ systemctl reboot --boot-loader-entry=arch-custom.conf

and your system will reboot into that entry maintaining the default option intact for subsequent boots. To see a list of possible entries pass the {{ic|1=--boot-loader-entry=help}} option.

If you want to boot into the firmware of your motherboard directly, then you can use this command:

$ systemctl reboot --firmware-setup

=== Unified kernel images ===

[[Unified kernel image]]s (UKIs) in {{ic|''esp''/EFI/Linux/}} are automatically sourced by systemd-boot, and do not need an entry in {{ic|''esp''/loader/entries}}. (Note that unified kernel images must have a {{ic|.efi}} extension to be identified by ''systemd-boot''.)

{{Tip|Files in {{ic|''esp''/loader/entries/}} will be booted first if no {{ic|default}} is set in {{ic|''esp''/loader/loader.conf}}. Remove those entries, or set the default with the full file name, i.e. {{ic|1=default arch-linux.efi}}}}

=== Grml on ESP ===

{{Note|The following instructions are not exclusive to Grml. With slight adjustments, installing other software (e.g., [https://www.system-rescue-cd.org/ SystemRescueCD]) is possible.}}

{{Tip|A {{ic|PKGBUILD}} is available: {{AUR|grml-systemd-boot}}.}}

[https://grml.org/ Grml] is a small live system with a collection of software for system administration and rescue.

In order to install Grml on the ESP, we only need to copy the kernel {{ic|vmlinuz}}, the initramfs {{ic|initrd.img}}, and the squashed image {{ic|grml64-small.squashfs}} from the iso file to the ESP. To do so, first download [https://grml.org/ grml64-small.iso] and mount the file (the mountpoint is henceforth denoted ''mnt''); the kernel and initramfs are located in {{ic|''mnt''/boot/grml64small/}}, and the squashed image resides in {{ic|''mnt''/live/grml64-small/}}.

Next, create a directory for Grml in your ESP,

# mkdir -p ''esp''/grml

and copy the above-mentioned files in there:

# cp ''mnt''/boot/grml64small/vmlinuz ''esp''/grml
# cp ''mnt''/boot/grml64small/initrd.img ''esp''/grml
# cp ''mnt''/live/grml64-small/grml64-small.squashfs ''esp''/grml

In the last step, create an boot entry for systemd-boot: In {{ic|''esp''/loader/entries}} create a {{ic|grml.conf}} file with the following content:

{{hc|''esp''/loader/entries/grml.conf|2=
title Grml Live Linux
linux /grml/vmlinuz
initrd /grml/initrd.img
options apm=power-off boot=live live-media-path=/grml/ nomce net.ifnames=0
}}

For an overview of the available boot options, consult the [https://github.com/grml/grml-live/blob/master/config/media-files/GRMLBASE/GRML/GRML_NAME/grml-cheatcodes.txt cheatcode for Grml].

=== Archiso on ESP ===

{{Tip|A {{ic|PKGBUILD}} is available: {{AUR|archiso-systemd-boot}}.}}

As with Grml it is possible to use the Arch Linux ISO. To do this we need to copy the kernel {{ic|vmlinuz-linux}}, the initramfs {{ic|initramfs-linux.img}}, and the squashfs image {{ic|airootfs.sfs}} from the ISO file to the EFI system partition.

First download [https://archlinux.org/download/ archlinux-YYYY.MM.DD-x86_64.iso].

Next, create a directory for archiso in your ESP:

# mkdir -p ''esp''/EFI/archiso

Extract the contents of the {{ic|arch}} directory in there:

# bsdtar -v -x --no-same-permissions --strip-components 1 -f archlinux-''YYYY''.''MM''.''DD''-x86_64.iso -C ''esp''/EFI/archiso arch

In the last step, create a boot entry for the systemd-boot: In {{ic|''esp''/loader/entries}} create a {{ic|arch-rescue.conf}} file with the following content:

{{hc|''esp''/loader/entries/arch-rescue.conf|2=
title Arch Linux (rescue system)
linux /EFI/archiso/boot/x86_64/vmlinuz-linux
initrd /EFI/archiso/boot/x86_64/initramfs-linux.img
options archisobasedir=/EFI/archiso archisosearchfilename=/EFI/archiso/boot/x86_64/vmlinuz-linux
}}

For an overview of the available boot options, consult the [https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio-archiso/-/blob/master/docs/README.bootparams README.bootparams for mkinitcpio-archiso].

==== Recovery Arch image on the ESP with Secure Boot ====

The official Arch ISO does not currently support [[Secure Boot]]. As a result, Secure Boot must be disabled to boot into the ISO for recovery or maintenance. This undermines system security and is not an ideal approach.

An alternative is to create a signed [[unified kernel image]] (UKI) using [[mkosi]], assuming Secure Boot is already configured and functioning properly on your system. This allows you to boot into a signed recovery Arch environment without disabling Secure Boot or carrying an Arch ISO USB drive wherever your laptop goes.

https://swsnr.de/archlinux-rescue-image-with-mkosi/ describes how to set up Secure Boot-compatible Arch recovery images. A practical starting point with a sane mkosi configuration you can add your packages to is available at https://codeberg.org/swsnr/rescue-image.

=== systemd-boot on BIOS systems ===

If you need a boot loader for BIOS systems that follows [https://uapi-group.org/specifications/specs/boot_loader_specification/ The Boot Loader Specification], then systemd-boot can be pressed into service on BIOS systems. The [[Clover]] boot loader supports booting from BIOS systems and provides an emulated UEFI environment.

== Troubleshooting ==

=== systemd-boot does not display my boot entry ===

This may be caused by a variety of issues with the configuration file, such as the path to the kernel being specified incorrectly. To check, run:

# bootctl

=== Installing after booting in BIOS mode ===

{{Note|This is not recommended.}}

If booted in BIOS mode, you can still install ''systemd-boot'', however this process requires you to tell firmware to launch ''systemd-boot'''s EFI file at boot:

* you have a working UEFI Shell somewhere else.
* your firmware interface provides a way of properly setting the EFI file that needs to be loaded at boot time.
* some firmware may use the default {{ic|''esp''/EFI/BOOT/BOOTX64.EFI}} if there is no other entry set in the UEFI.

If you can do it, the installation is easier: go into your UEFI Shell or your firmware configuration interface and change your machine's default EFI file to {{ic|''esp''/EFI/systemd/systemd-bootx64.efi}}.

{{Note|The firmware interface of Dell Latitude series provides everything you need to setup UEFI boot but the UEFI Shell will not be able to write to the computer's ROM.}}

=== Manual entry using efibootmgr ===

If the {{ic|bootctl install}} command failed, you can create a UEFI boot entry manually using {{Pkg|efibootmgr}}:

# efibootmgr --create --disk /dev/sd''X'' --part ''Y'' --loader '\EFI\systemd\systemd-bootx64.efi' --label "Linux Boot Manager" --unicode

where {{ic|/dev/sd''XY''}} is the [[EFI system partition]].

{{Note|The path to the EFI binary must use the backslash ({{ic|\}}) as the separator}}

=== Manual entry using bcdedit from Windows ===

If for any reason you need to create a UEFI boot entry from Windows, you can use the following commands from an Administrator prompt:

> bcdedit /copy "{bootmgr}" /d "Linux Boot Manager"
> bcdedit /set "{''guid''}" path \EFI\systemd\systemd-bootx64.efi

Replace {{ic|''guid''}} with the id returned by the first command. You can also set it as the default entry using

> bcdedit /default "{''guid''}"

=== Menu does not appear after Windows upgrade ===

See [[UEFI#Windows changes boot order]].

=== Add support for Windows BitLocker TPM unlocking ===

To stop BitLocker from requesting the recovery key, add the following to ''loader.conf'':

{{hc|''esp''/loader/loader.conf|
reboot-for-bitlocker yes
}}

This will set the ''BootNext'' UEFI variable, whereby ''Windows Boot Manager'' is loaded without BitLocker requiring the recovery key. This is a one-time change, and ''systemd-boot'' remains the default boot loader. There is no need to specify Windows as an entry if it was autodetected.

This is an experimental feature, so make sure to consult {{man|5|loader.conf}}.

== See also ==

* https://systemd.io/BOOT/
* https://bbs.archlinux.org/viewtopic.php?id=254374
* https://uapi-group.org/specifications/specs/boot_loader_specification/

Systemd-boot

2026-05-12T10:13:52Z

Erus Iluvatar: /* Configuration */ Merge the two tips

{{Lowercase title}}
[[Category:Boot loaders]]
[[de:Systemd-boot]]
[[es:Systemd-boot]]
[[fr:Systemd-boot]]
[[hu:Systemd-boot]]
[[ja:Systemd-boot]]
[[pt:Systemd-boot]]
[[ru:Systemd-boot]]
[[zh-hans:Systemd-boot]]
{{Related articles start}}
{{Related|Arch boot process}}
{{Related|Secure Boot}}
{{Related|Unified Extensible Firmware Interface}}
{{Related articles end}}

{{man|7|systemd-boot}}, previously called '''gummiboot''' (German for "rubber dinghy") and sometimes referred to as ''sd-boot'', is an easy-to-configure [[UEFI]] [[boot manager]]. It provides a textual menu to select the boot entry and an editor for the kernel command line.

Note that ''systemd-boot'' can only start EFI executables (e.g., the Linux kernel [[EFI boot stub]], [[UEFI shell]], [[GRUB]], or the [https://learn.microsoft.com/en-us/windows-hardware/drivers/bringup/boot-and-uefi#understanding-the-windows-boot-manager Windows Boot Manager]) from the [[EFI system partition]] it is installed to or from an Extended Boot Loader Partition (XBOOTLDR partition) on the same disk.

{{Note|In the entire article {{ic|''esp''}} denotes the mountpoint of the [[EFI system partition]] and {{ic|''boot''}} denotes the mountpoint of the optional XBOOTLDR partition. It is assumed that you have [[chroot]]ed to the system's mount point.}}

== Supported file systems ==

systemd-boot inherits the support for the file systems [[Arch boot process#UEFI|from the firmware]] (i.e. at least FAT12, FAT16 and FAT32). Additionally it loads any [[Unified Extensible Firmware Interface#UEFI drivers|UEFI drivers]] placed in {{ic|''esp''/EFI/systemd/drivers/}}.

== Installation ==

''systemd-boot'' is shipped with the {{Pkg|systemd}} package which is a dependency of the {{Pkg|base}} meta package, so no additional packages need to be installed manually.

== Installing the UEFI boot manager ==

To install ''systemd-boot'', first make sure that the system is booted into UEFI mode and [[Unified Extensible Firmware Interface#UEFI variables|UEFI variables]] are accessible. This can be verified by running {{ic|efivar --list}} or, if {{Pkg|efivar}} is not installed, by running {{ic|ls /sys/firmware/efi/efivars}} (if the directory exists, the system is booted into UEFI mode.)

Use {{man|1|bootctl}} to install ''systemd-boot'' to the ESP:

# bootctl install

This will copy the ''systemd-boot'' UEFI boot manager to the ESP, create a UEFI boot entry for it and set it as the first in the UEFI boot order.

* On an x64 UEFI, {{ic|/usr/lib/systemd/boot/efi/systemd-bootx64.efi}} will be copied to {{ic|''esp''/EFI/systemd/systemd-bootx64.efi}} and {{ic|''esp''/EFI/BOOT/BOOTX64.EFI}}.
* On an IA32 UEFI, {{ic|/usr/lib/systemd/boot/efi/systemd-bootia32.efi}} will be copied to {{ic|''esp''/EFI/systemd/systemd-bootia32.efi}} and {{ic|''esp''/EFI/BOOT/BOOTIA32.EFI}}.

The UEFI boot entry will be called "Linux Boot Manager" and will point to, depending on the [[Unified Extensible Firmware Interface#UEFI firmware bitness|UEFI bitness]], either {{ic|\EFI\systemd\systemd-bootx64.efi}} or {{ic|\EFI\systemd\systemd-bootia32.efi}} on the ESP.

{{Note|
* When running {{ic|bootctl install}}, ''systemd-boot'' will try to locate the ESP at {{ic|/efi}}, {{ic|/boot}}, and {{ic|/boot/efi}}. Setting {{ic|''esp''}} to a different location requires passing the {{ic|1=--esp-path=''esp''}} option. (See {{man|1|bootctl|OPTIONS}} for details.)
* Installing ''systemd-boot'' will overwrite any existing {{ic|''esp''/EFI/BOOT/BOOTX64.EFI}} (or {{ic|''esp''/EFI/BOOT/BOOTIA32.EFI}} on IA32 UEFI), e.g. Microsoft's version of the file.
* ''bootctl'' refrains from operating on UEFI variables/boot entries when running in pid namespace, which is the case for {{man|8|arch-chroot}}'s non-systemd mode. To create the boot entry in the chroot environment, use {{ic|arch-chroot -S}} instead.
}}

To conclude the installation, [[#Configuration|configure]] ''systemd-boot''.

=== Installation using XBOOTLDR ===

{{Move|Partitioning#Discrete partitions|All partitioning info should be moved to partitioning, to leave only steps relevant to installing systemd-boot if you have such a setup.}}

A separate [[Partitioning#/boot|/boot partition]] of type "Linux extended boot" (XBOOTLDR) can be created to keep the kernel and initramfs separate from the ESP. This is particularly helpful to [[dual boot with Windows]] with an existing ESP that is too small. [[#Grml on ESP|Grml]] or [[#Archiso on ESP|Archiso]] are also possible use cases.

Prepare an ESP as usual and create another partition for XBOOTLDR on the same physical drive. The XBOOTLDR partition must have a partition type GUID of {{ic|bc13c2ff-59e6-4262-a352-b275fd6f7172}} [https://uapi-group.org/specifications/specs/boot_loader_specification/] ({{ic|ea00}} type for [[gdisk]], {{ic|xbootldr}} type for [[fdisk]]). The size of the XBOOTLDR partition should be large enough to accommodate all of the kernels you are going to install.

{{Note|
* ''systemd-boot'' does not do a file system check like it does for the ESP. Hence, it is possible to use any file system that your UEFI implementation can read.
* UEFI may skip loading partitions other than the ESP when a "fast boot" mode is enabled. This can lead to ''systemd-boot'' failing to find entries on the XBOOTLDR partition; in that case, disable the "fast boot" mode.
* The XBOOTLDR partition must be on the same physical disk as the ESP for ''systemd-boot'' to recognize it.
}}

During install, mount the ESP to {{ic|/mnt/efi}} and the XBOOTLDR partition to {{ic|/mnt/boot}}.

Once in chroot, use the command:

# bootctl --esp-path=/efi --boot-path=/boot install

To conclude the installation, [[#Configuration|configure]] ''systemd-boot''.

=== Updating the UEFI boot manager ===

Whenever there is a new version of ''systemd-boot'', the UEFI boot manager can be optionally reinstalled by the user. This can be done manually or automatically; the two approaches are described thereafter.

{{Note|The UEFI boot manager is a standalone EFI executable and any version can be used to boot the system (partial updates do not apply, since pacman only installs the ''systemd-boot'' installer, not ''systemd-boot'' itself.) However, new versions may add new features or fix bugs, so it is probably a good idea to update ''systemd-boot''.}}

{{Warning|If you have [[Secure Boot]] enabled, you need to sign the boot manager update. See [[#Signing for Secure Boot]].}}

==== Manual update ====

Use ''bootctl'' to update ''systemd-boot'':

# bootctl update

{{Note|As with {{ic|bootctl install}}, ''systemd-boot'' will try to locate the ESP at {{ic|/efi}}, {{ic|/boot}}, and {{ic|/boot/efi}}. Setting {{ic|''esp''}} to a different location requires passing the {{ic|1=--esp-path=''esp''}} option.}}

==== Automatic update ====

To update ''systemd-boot'' automatically, either use a [[systemd#Using units|systemd service]] or a [[pacman hook]]. The two methods are described below.

===== systemd service =====

As of version 250, {{Pkg|systemd}} ships with {{ic|systemd-boot-update.service}}. [[Enabling]] this service will cause systemd-boot to run the following command on every boot:

# bootctl --variables=no --graceful update

Like in the [[#Manual update|manual update]], this will attempt to locate the ESP at {{ic|/efi}}, {{ic|/boot}} or {{ic|/boot/efi}}. The command will update all installed versions of systemd-boot in the ESP if a newer version is available in {{ic|/usr/lib/systemd/boot/efi/}}. It will look for a systemd-boot file ending in {{ic|.efi.signed}} first to allow users to sign the image for use with [[Secure Boot]].

===== pacman hook =====

The package {{AUR|systemd-boot-pacman-hook}} adds a pacman hook which is executed every time {{Pkg|systemd}} is upgraded. This hook differs from the [[#systemd service|systemd service method]] in that it only attempts to update the boot manager when {{Pkg|systemd}} is updated rather than every boot, and it does it immediately rather than waiting until after the next boot.

Rather than installing the AUR package, you may prefer to manually place the following file in {{ic|/etc/pacman.d/hooks/}}:

{{hc|/etc/pacman.d/hooks/95-systemd-boot.hook|2=
[Trigger]
Type = Package
Operation = Upgrade
Target = systemd

[Action]
Description = Gracefully upgrading systemd-boot...
When = PostTransaction
Exec = /usr/bin/systemctl restart systemd-boot-update.service
}}

=== Signing for Secure Boot ===

If you have [[Secure Boot]] enabled, you may want to add a pacman hook to automatically sign the boot manager upon every upgrade of the package:

{{hc|/etc/pacman.d/hooks/80-secureboot.hook|2=
[Trigger]
Operation = Install
Operation = Upgrade
Type = Path
Target = usr/lib/systemd/boot/efi/systemd-boot*.efi

[Action]
Description = Signing systemd-boot EFI binary for Secure Boot
When = PostTransaction
Exec = /bin/sh -c 'while read -r f; do /usr/lib/systemd/systemd-sbsign sign --private-key ''/path/to/keyfile.key'' --certificate ''/path/to/certificate.crt'' --output "${f}.signed" "$f"; done;'
Depends = sh
NeedsTargets
}}

Replace {{ic|''/path/to/keyfile.key''}} and {{ic|''/path/to/certificate.crt''}} with your signing key and certificate respectively. For better understanding of this hook, consult {{man|1|systemd-sbsign}}.

The created {{ic|/usr/lib/systemd/boot/efi/systemd-boot*.efi.''signed''}} will automatically be picked up by {{ic|bootctl install}} or {{ic|bootctl update}}. See {{man|1|bootctl|SIGNED .EFI FILES}}.

As an alternative, use [[Unified Extensible Firmware Interface/Secure Boot#Automatic signing with the pacman hook|sbctl]].

== Configuration ==

{{Tip|
* After changing the configuration, run {{ic|bootctl}} (without any arguments) to make sure that systemd-boot will be able to parse it properly.
* {{ic|kernel-install}} can be used to automate this process.
}}

=== Loader configuration ===

The loader configuration is stored in the file {{ic|''esp''/loader/loader.conf}}. See {{man|5|loader.conf|OPTIONS}} for details.

A loader configuration example is provided below:

{{hc|''esp''/loader/loader.conf|
default arch.conf
timeout 4
console-mode max
editor no
}}

{{Tip|
* {{ic|default}} and {{ic|timeout}} can be changed in the boot menu itself and changes will be stored as UEFI variables {{ic|LoaderEntryDefault}} and {{ic|LoaderConfigTimeout}}, overriding these options.
* {{ic|bootctl set-default ""}} and {{ic|bootctl set-timeout ""}} can be used to clear the UEFI variables overriding the {{ic|default}} and {{ic|timeout}} options, respectively.
* If you have set {{ic|timeout 0}}, the boot menu can be accessed by pressing {{ic|Space}}.
* A basic loader configuration file is located at {{ic|/usr/share/systemd/bootctl/loader.conf}}.
* If the boot manager—during the entry selection—appears distorted/uses the wrong resolution you can try to set the {{ic|console-mode}} to {{ic|auto}} (uses heuristics to select the best resolution), {{ic|keep}} (keeps the firmware provided resolution) or {{ic|2}} (tries to select the first non-UEFI-standard resolution).
}}

==== Remember last entry ====

The {{ic|default}} can be changed to {{ic|@saved}} in order to remember the last picked entry on startup. This is useful for when dual booting Windows and the surprise windows auto update pushes you into Linux.

{{hc|''esp''/loader/loader.conf|
default @saved
...
}}

Consult {{man|5|loader.conf}} for more details.

=== Adding loaders ===

''systemd-boot'' will search for ''.conf'' files in {{ic|/loader/entries/}} on the [[EFI system partition]] it was launched from and additionally the [[#Installation using XBOOTLDR|XBOOTLDR]] partition on the same disk.

{{Note|
* Entries in {{ic|''esp''/loader/entries/*.conf}} can only use files (e.g. kernels, initramfs, images, etc.) in {{ic|''esp''/}} and entries in {{ic|''boot''/loader/entries/*.conf}} can only use files in {{ic|''boot''/}}.
* The file path parameters are relative to the root of your EFI system partition or XBOOTLDR partition. E.g., if your EFI system partition or XBOOTLDR partition is mounted at {{ic|/boot}}, then the {{ic|/boot/vmlinuz-linux}} file must be specified in the {{ic|linux}} key as {{ic|/vmlinuz-linux}}.
* When [[Secure Boot]] is active, [[unified kernel image]]s (UKIs) with an embedded {{ic|.cmdline}} ignore all command line options passed to them (either using a boot entry with {{ic|options}} or interactively). When Secure Boot is not active, the options passed via the command line override the embedded {{ic|.cmdline}}.
}}

An example of loader files launching Arch from a volume using its [[UUID]] {{ic|''xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx''}} is:

{{hc|''esp''/loader/entries/arch.conf|2=
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=UUID=''xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'' rw
}}

{{hc|''esp''/loader/entries/arch-fallback.conf|2=
title Arch Linux (fallback initramfs)
linux /vmlinuz-linux
initrd /initramfs-linux-fallback.img
options root=UUID=''xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'' rw
}}

See the [https://uapi-group.org/specifications/specs/boot_loader_specification/#type-1-boot-loader-specification-entries Boot Loader Specification] for details on all configuration options.

''systemd-boot'' will automatically check at boot time for '''Windows Boot Manager''' at the location {{ic|/EFI/Microsoft/Boot/Bootmgfw.efi}}, '''Apple macOS Boot Manager''' in firmware, [[UEFI shell]] {{ic|/shellx64.efi}} and '''EFI Default Loader''' {{ic|/EFI/BOOT/bootx64.efi}}, as well as specially prepared kernel files found in {{ic|/EFI/Linux/}}. When detected, corresponding entries with titles {{ic|auto-windows}}, {{ic|auto-osx}}, {{ic|auto-efi-shell}} and {{ic|auto-efi-default}}, respectively, will be generated. These entries do not require manual loader configuration. However, it does not auto-detect other EFI applications (unlike [[rEFInd]]), so for booting the Linux kernel, manual configuration entries must be created.

{{Tip|
* The available boot entries which have been configured can be listed with the command {{ic|bootctl list}}.
* An example entry file is located at {{ic|/usr/share/systemd/bootctl/arch.conf}}.
* The [[kernel parameters]] for scenarios such as [[LVM]], [[LUKS]], [[dm-crypt]] or [[Btrfs]] can be found on the relevant pages.
}}

{{Note|If [[Microcode#Microcode in a separate initramfs file|external microcode initramfs images]] are used (e.g. when using [[Booster]] as the initramfs generator), {{ic|/boot/amd-ucode.img}} or {{ic|/boot/intel-ucode.img}} must be specified in a separate {{ic|initrd}} and always be placed '''first''', before the main initramfs image.}}

==== UEFI Shells or other EFI applications ====

In case you installed a [[UEFI shell]] with the package {{Pkg|edk2-shell}}, ''systemd-boot'' will auto-detect and create a new entry if the EFI file is placed in {{ic|''esp''/shellx64.efi}}.
To perform this an example command after installing the package would be:

# cp /usr/share/edk2-shell/x64/Shell.efi /boot/shellx64.efi

Otherwise in case you installed [[rEFInd#Tools|other EFI applications]] into the ESP, you can use the following snippets.

{{Note|The file path parameter for the {{ic|efi}} line is relative to the root of your [[EFI system partition]]. If your EFI system partition is mounted at {{ic|/boot}} and your EFI binaries reside at {{ic|/boot/EFI/xx.efi}} and {{ic|/boot/yy.efi}}, then you would specify the parameters as {{ic|efi /EFI/xx.efi}} and {{ic|efi /yy.efi}} respectively.}}

{{hc|''esp''/loader/entries/fwupd.conf|
title Firmware updater
efi /EFI/tools/fwupdx64.efi
}}

{{hc|''esp''/loader/entries/gdisk.conf|
title GPT fdisk (gdisk)
efi /EFI/tools/gdisk_x64.efi
}}

===== Memtest86+ =====

You need to install {{Pkg|memtest86+-efi}} for this to work. Also sign the EFI binary when using Secure Boot.

{{hc|''esp''/loader/entries/memtest.conf|
title Memtest86+
efi /memtest86+/memtest.efi
}}

===== Netboot =====

''systemd-boot'' can chainload [[Netboot]]. Download the {{ic|ipxe-arch.efi}} EFI binary and signature, verify it and place it as proposed in {{ic|''esp''/EFI/arch_netboot/arch_netboot.efi}}.

{{hc|''esp''/loader/entries/arch_netboot.conf|
title Arch Linux Netboot
efi /EFI/arch_netboot/arch_netboot.efi
}}

===== GRUB =====

''systemd-boot'' can chainload [[GRUB]]. The location of the {{ic|grubx64.efi}} binary matches the used {{ic|--bootloader-id{{=}}}} when GRUB was installed to the ESP.

{{hc|''esp''/loader/entries/grub.conf|
title GRUB
efi /EFI/GRUB/grubx64.efi
}}

==== Boot from another disk ====

''systemd-boot'' [https://github.com/systemd/systemd/issues/3252 cannot] launch EFI binaries from partitions other than the ESP it is launched from or the XBOOTLDR partition on the same disk, but it can direct the [[UEFI shell]] to do so.

First, install {{Pkg|edk2-shell}} as [[#UEFI Shells or other EFI applications|described above]]. In the UEFI shell, use the ''map'' command to take notes of the '''FS alias''' (ex: HD0a66666a2, HD0b, FS1, or BLK7) of the partition with the corresponding PARTUUID.

Then, use the {{ic|exit}} command to boot back into Linux, where you can create a new loader entry to run the target EFI program through the UEFI shell:

{{hc|''esp''/loader/entries/windows.conf|
title Windows
efi /shellx64.efi
options -nointerrupt -nomap -noversion HD0b:EFI\Microsoft\Boot\Bootmgfw.efi
}}

Ensure that the {{ic|efi}} path matches the location where the {{ic|shellx64.efi}} has been copied in the ''esp'' partition. Also, note that the {{ic|shellx64.efi}} EFI file can be moved elsewhere to avoid the automatic entry creation by ''systemd-boot''.

Replace {{ic|HD0b}} with the previously noted ''FS alias''.

* The {{ic|-nointerrupt}} option prevents interrupting the target EFI program with {{ic|Ctrl+c}}.
* The {{ic|-nomap -noversion}} options hide the default UEFI shell greeting.
* To have the UEFI shell automatically return to the boot manager if the target EFI program exits (e.g. due to an error), add the {{ic|-exit}} option.
* You can also add the {{ic|-noconsoleout}} option if there is still unnecessary output in the UEFI shell.

=== Booting into UEFI firmware setup ===

systemd-boot will automatically add an entry to boot into UEFI firmware setup if your device's firmware supports rebooting into setup from the OS.

=== Kernel parameters editor with password protection ===

Alternatively you can install {{AUR|systemd-boot-password}} which supports {{ic|password}} basic configuration option. Use {{ic|sbpctl generate}} to generate a value for this option.

Install ''systemd-boot-password'' with the following command:

# sbpctl install ''esp''

With enabled editor you will be prompted for your password before you can edit kernel parameters.

== Tips and tricks ==

=== Keys inside the boot menu ===

You can use {{ic|t}} and {{ic|T}} while in the menu to adjust the menu timeout and {{ic|e}} to edit the kernel parameters for this boot. Press {{ic|h}} to see a short list of useful hotkeys. See {{man|7|systemd-boot|KEY BINDINGS}} for the full list of available key bindings inside the boot menu.

=== Choosing next boot ===

The boot manager is integrated with the systemctl command, allowing you to choose what option you want to boot after a reboot. For example, suppose you have built a custom kernel and created an entry file {{ic|''esp''/loader/entries/arch-custom.conf}} to boot into it, you can just launch

$ systemctl reboot --boot-loader-entry=arch-custom.conf

and your system will reboot into that entry maintaining the default option intact for subsequent boots. To see a list of possible entries pass the {{ic|1=--boot-loader-entry=help}} option.

If you want to boot into the firmware of your motherboard directly, then you can use this command:

$ systemctl reboot --firmware-setup

=== Unified kernel images ===

[[Unified kernel image]]s (UKIs) in {{ic|''esp''/EFI/Linux/}} are automatically sourced by systemd-boot, and do not need an entry in {{ic|''esp''/loader/entries}}. (Note that unified kernel images must have a {{ic|.efi}} extension to be identified by ''systemd-boot''.)

{{Tip|Files in {{ic|''esp''/loader/entries/}} will be booted first if no {{ic|default}} is set in {{ic|''esp''/loader/loader.conf}}. Remove those entries, or set the default with the full file name, i.e. {{ic|1=default arch-linux.efi}}}}

=== Grml on ESP ===

{{Note|The following instructions are not exclusive to Grml. With slight adjustments, installing other software (e.g., [https://www.system-rescue-cd.org/ SystemRescueCD]) is possible.}}

{{Tip|A {{ic|PKGBUILD}} is available: {{AUR|grml-systemd-boot}}.}}

[https://grml.org/ Grml] is a small live system with a collection of software for system administration and rescue.

In order to install Grml on the ESP, we only need to copy the kernel {{ic|vmlinuz}}, the initramfs {{ic|initrd.img}}, and the squashed image {{ic|grml64-small.squashfs}} from the iso file to the ESP. To do so, first download [https://grml.org/ grml64-small.iso] and mount the file (the mountpoint is henceforth denoted ''mnt''); the kernel and initramfs are located in {{ic|''mnt''/boot/grml64small/}}, and the squashed image resides in {{ic|''mnt''/live/grml64-small/}}.

Next, create a directory for Grml in your ESP,

# mkdir -p ''esp''/grml

and copy the above-mentioned files in there:

# cp ''mnt''/boot/grml64small/vmlinuz ''esp''/grml
# cp ''mnt''/boot/grml64small/initrd.img ''esp''/grml
# cp ''mnt''/live/grml64-small/grml64-small.squashfs ''esp''/grml

In the last step, create an boot entry for systemd-boot: In {{ic|''esp''/loader/entries}} create a {{ic|grml.conf}} file with the following content:

{{hc|''esp''/loader/entries/grml.conf|2=
title Grml Live Linux
linux /grml/vmlinuz
initrd /grml/initrd.img
options apm=power-off boot=live live-media-path=/grml/ nomce net.ifnames=0
}}

For an overview of the available boot options, consult the [https://github.com/grml/grml-live/blob/master/config/media-files/GRMLBASE/GRML/GRML_NAME/grml-cheatcodes.txt cheatcode for Grml].

=== Archiso on ESP ===

{{Tip|A {{ic|PKGBUILD}} is available: {{AUR|archiso-systemd-boot}}.}}

As with Grml it is possible to use the Arch Linux ISO. To do this we need to copy the kernel {{ic|vmlinuz-linux}}, the initramfs {{ic|initramfs-linux.img}}, and the squashfs image {{ic|airootfs.sfs}} from the ISO file to the EFI system partition.

First download [https://archlinux.org/download/ archlinux-YYYY.MM.DD-x86_64.iso].

Next, create a directory for archiso in your ESP:

# mkdir -p ''esp''/EFI/archiso

Extract the contents of the {{ic|arch}} directory in there:

# bsdtar -v -x --no-same-permissions --strip-components 1 -f archlinux-''YYYY''.''MM''.''DD''-x86_64.iso -C ''esp''/EFI/archiso arch

In the last step, create a boot entry for the systemd-boot: In {{ic|''esp''/loader/entries}} create a {{ic|arch-rescue.conf}} file with the following content:

{{hc|''esp''/loader/entries/arch-rescue.conf|2=
title Arch Linux (rescue system)
linux /EFI/archiso/boot/x86_64/vmlinuz-linux
initrd /EFI/archiso/boot/x86_64/initramfs-linux.img
options archisobasedir=/EFI/archiso archisosearchfilename=/EFI/archiso/boot/x86_64/vmlinuz-linux
}}

For an overview of the available boot options, consult the [https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio-archiso/-/blob/master/docs/README.bootparams README.bootparams for mkinitcpio-archiso].

==== Recovery Arch image on the ESP with Secure Boot ====

The official Arch ISO does not currently support [[Secure Boot]]. As a result, Secure Boot must be disabled to boot into the ISO for recovery or maintenance. This undermines system security and is not an ideal approach.

An alternative is to create a signed [[unified kernel image]] (UKI) using [[mkosi]], assuming Secure Boot is already configured and functioning properly on your system. This allows you to boot into a signed recovery Arch environment without disabling Secure Boot or carrying an Arch ISO USB drive wherever your laptop goes.

https://swsnr.de/archlinux-rescue-image-with-mkosi/ describes how to set up Secure Boot-compatible Arch recovery images. A practical starting point with a sane mkosi configuration you can add your packages to is available at https://codeberg.org/swsnr/rescue-image.

=== systemd-boot on BIOS systems ===

If you need a boot loader for BIOS systems that follows [https://uapi-group.org/specifications/specs/boot_loader_specification/ The Boot Loader Specification], then systemd-boot can be pressed into service on BIOS systems. The [[Clover]] boot loader supports booting from BIOS systems and provides an emulated UEFI environment.

== Troubleshooting ==

=== systemd-boot does not display my boot entry ===

This may be caused by a variety of issues with the configuration file, such as the path to the kernel being specified incorrectly. To check, run:

# bootctl

=== Installing after booting in BIOS mode ===

{{Note|This is not recommended.}}

If booted in BIOS mode, you can still install ''systemd-boot'', however this process requires you to tell firmware to launch ''systemd-boot'''s EFI file at boot:

* you have a working UEFI Shell somewhere else.
* your firmware interface provides a way of properly setting the EFI file that needs to be loaded at boot time.
* some firmware may use the default {{ic|''esp''/EFI/BOOT/BOOTX64.EFI}} if there is no other entry set in the UEFI.

If you can do it, the installation is easier: go into your UEFI Shell or your firmware configuration interface and change your machine's default EFI file to {{ic|''esp''/EFI/systemd/systemd-bootx64.efi}}.

{{Note|The firmware interface of Dell Latitude series provides everything you need to setup UEFI boot but the UEFI Shell will not be able to write to the computer's ROM.}}

=== Manual entry using efibootmgr ===

If the {{ic|bootctl install}} command failed, you can create a UEFI boot entry manually using {{Pkg|efibootmgr}}:

# efibootmgr --create --disk /dev/sd''X'' --part ''Y'' --loader '\EFI\systemd\systemd-bootx64.efi' --label "Linux Boot Manager" --unicode

where {{ic|/dev/sd''XY''}} is the [[EFI system partition]].

{{Note|The path to the EFI binary must use the backslash ({{ic|\}}) as the separator}}

=== Manual entry using bcdedit from Windows ===

If for any reason you need to create a UEFI boot entry from Windows, you can use the following commands from an Administrator prompt:

> bcdedit /copy "{bootmgr}" /d "Linux Boot Manager"
> bcdedit /set "{''guid''}" path \EFI\systemd\systemd-bootx64.efi

Replace {{ic|''guid''}} with the id returned by the first command. You can also set it as the default entry using

> bcdedit /default "{''guid''}"

=== Menu does not appear after Windows upgrade ===

See [[UEFI#Windows changes boot order]].

=== Add support for Windows BitLocker TPM unlocking ===

To stop BitLocker from requesting the recovery key, add the following to ''loader.conf'':

{{hc|''esp''/loader/loader.conf|
reboot-for-bitlocker yes
}}

This will set the ''BootNext'' UEFI variable, whereby ''Windows Boot Manager'' is loaded without BitLocker requiring the recovery key. This is a one-time change, and ''systemd-boot'' remains the default boot loader. There is no need to specify Windows as an entry if it was autodetected.

This is an experimental feature, so make sure to consult {{man|5|loader.conf}}.

== See also ==

* https://systemd.io/BOOT/
* https://bbs.archlinux.org/viewtopic.php?id=254374
* https://uapi-group.org/specifications/specs/boot_loader_specification/

Laptop/Lenovo

2026-05-12T08:20:21Z

Erus Iluvatar: /* IdeaPad series */ Update date per previous edit

[[Category:Lenovo]]
[[ja:ノートパソコン/Lenovo]]
{{Laptops navigation}}
{{Related articles start}}
{{Related|ThinkPad docks}}
{{Related|ThinkPad mobile Internet}}
{{Related articles end}}
{{Style| and instead of creating super long, messy entries there should be a dedicated page for the laptop. Many entries also need language improvements}}
== IBM/Lenovo ==

From [[Wikipedia:ThinkPad|Wikipedia]]:

: ThinkPad is a line of business-oriented laptop computers and tablets designed, developed and marketed by Lenovo, and formerly IBM. The line was originally sold by IBM until 2005, when a part of the company's business was acquired by Lenovo.

=== ThinkPad battery control ===

Since kernel 4.17, newer Thinkpads can leverage the {{ic|natacpi}} API (part of the {{ic|thinkpad_acpi}} [[kernel module]]) via [[TLP]]. Older (pre-Ivy-Bridge / pre-2011) models may require [[tp_smapi]] instead. Refer to its documentation for supported devices and installation details.

See also - [https://linrunner.de/tlp/faq/battery.html#which-external-kernel-module-do-i-need-for-my-thinkpad Which external kernel module do I need for my ThinkPad]?

=== UltraBay devices ===

[https://www.thinkwiki.org/wiki/Ultrabay Ultrabay] was IBM's, now Lenovo's name for the swappable bay. It is possible to hotswap a ultrabay by just releasing the UltraBay eject lever or pressing hotkeys such as {{ic|Fn+F9}}. Consult [https://www.thinkwiki.org/wiki/How_to_hotswap_Ultrabay_devices ThinkWiki]'s page for detail.

=== T series ===

{{Laptops table header}}
| ThinkPad T60 || 2010-08-19 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad T60p || 2013-03-25 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad T61 || 2011-04-20 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad T61p || 2009-11-05 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| [[Lenovo ThinkPad T400|ThinkPad T400]] || 2012-02-17 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| ThinkPad T400s || 2012-12-03 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| ThinkPad T410 || 2014-10-24 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| ThinkPad T420 || 2014-12-17 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad T420s || 2025-08-26 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad T430 || 2015-10-11 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad T430s || 2018-03-14 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan="2" | Use {{ic|1=acpi_sleep=nonvs}} for resume issues, {{ic|1=acpi_osi='!Windows 2012'}} for brightness control issues.
|-
| ThinkPad T430u || 2021-07-03 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{R|SD card reader}} || Requires {{ic|noapic}} or {{ic|1=intremap=off}} to boot reliably
|-
| ThinkPad T440p || 2018-10-25 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || || See [[#ThinkPad T440p]]
|-
| [[Lenovo ThinkPad T440s|ThinkPad T440s]] || 2020-05-14 || {{Yes}} || {{Yes}} || {{Yes}} || {{G|[[Lenovo ThinkPad T440s#Wi-Fi|Yes*]]}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad T450|ThinkPad T450]] || 2021-04-11 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || ||
|-
| [[Lenovo ThinkPad T450s|ThinkPad T450s]] || 2021-04-11 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad T460s|ThinkPad T460s]] || {{-}} || {{Yes}} || {{G|No beep}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad T25|ThinkPad T25]] || 2017-10-28 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad T470|ThinkPad T470]] || 2017-10-28 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad T470s|ThinkPad T470s]] || 2017-04-17 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Fingerprint scanner works with {{AUR|python-validity}} ||
|-
| [[Lenovo ThinkPad T480|ThinkPad T480]] || 2018-07-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || | Fingerprint scanner works with {{AUR|python-validity}} ||
|-
| [[Lenovo ThinkPad T480s|ThinkPad T480s]] || 2018-03-01 || {{Yes}} || {{G|No beep}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || | Fingerprint scanner works with {{AUR|python-validity}} ||
|-
| [[Lenovo ThinkPad T490|ThinkPad T490]] || 2020-05-02 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad T490s|ThinkPad T490s]] || 2025-11-07 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad T495|ThinkPad T495]] || 2019-11-18 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad T495s|ThinkPad T495s]] || 2020-01-05 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad T500 || 2015-06-20 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| [[Lenovo ThinkPad T520|ThinkPad T520]] || 2013-11-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| ThinkPad T530 || 2022-05-19 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Modem may need {{ic|1=cdc_ncm prefer_mbim=N}} to enable data. || Update firmware to avoid visual freeze at boot
|-
| [[Lenovo ThinkPad T550|ThinkPad T550]] || 2015-07-31 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad T560 || 2017-05-06 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}* || colspan=2 | *No automatic brightness adjustment when switching from battery to AC
|-
| [[Lenovo ThinkPad T570|ThinkPad T570]] || 2017-06-27 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}}* || ||
|-
| ThinkPad T580 || 2021-07-14 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || | Fingerprint scanner works with {{AUR|python-validity}} ||
|-
| [[Lenovo ThinkPad T590|ThinkPad T590]] || 2020-06-09 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | Similar to the T490, the pointer occasionally jumps while pressing trackpad buttons
|-
| [[Lenovo ThinkPad T14 (AMD) Gen 1|ThinkPad T14 (AMD) Gen 1]] || 2020-12-30 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad T14s (AMD) Gen 1|ThinkPad T14s (AMD) Gen 1]] || 2020-12-30 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad T14/T14s (Intel) Gen 1|ThinkPad T14/T14s (Intel) Gen 1]] || 2020-08-26 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad T14/T14s (Intel) Gen 2|ThinkPad T14/T14s (Intel) Gen 2]] || 2021-03-10 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad T14 (AMD) Gen 2|ThinkPad T14 (AMD) Gen 2]] || 2021-11-20 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad T14s (AMD) Gen 2 || 2021-06-26 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || ||
|-
| [[Lenovo ThinkPad T14/T14s (Intel) Gen 3|ThinkPad T14/T14s (Intel) Gen 3]] || 2023-08-01 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| [[Lenovo ThinkPad T14 (AMD) Gen 3|ThinkPad T14 (AMD) Gen 3]] || 2025-05-06 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| [[Lenovo ThinkPad T14/T14s (Intel) Gen 4|ThinkPad T14/T14s (Intel) Gen 4]] || 2024-11-04 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| [[Lenovo ThinkPad T14 (AMD) Gen 4|ThinkPad T14 (AMD) Gen 4]] || 2023-09-25 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Not optimal}} || ||
|-
| ThinkPad T14 Gen 5 (Type 21ML, 21MM) || 2024-09-12 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| ThinkPad T14 (AMD) Gen 6 || 2025-12-23 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Trackpad, Trackpoint, Webcam, Fingerprint scanner || {{Pkg|linux-firmware-mediatek}} may improve wifi/bluetooth reliability and performance.
|-
| [[Lenovo ThinkPad T14s (AMD) Gen 6|ThinkPad T14s (AMD) Gen 6]] || 2025-11-28 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad T15 (Intel) Gen 2 || 2021-05-22 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| ThinkPad T15g (Intel) Gen 1 || 2024-10-19 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Partial}} || colspan=2 | For reliable CPU clock operation under full stress, ensure the battery charge limit is set to a value below '''100%''' (e.g. '''90% or lower'''). The optimal value may vary, so some experimentation may be necessary. See [[TLP|#TLP]] and adjust {{ic|charge_stop_threshold}}.
|-
| ThinkPad T15p (Intel) Gen 1 || 2024-05-07 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad T16 (Intel) Gen 1 || 2023-06-09 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | S2idle works. S3: Available in BIOS, the power button wakes the system but keyboard does not.
|-
| ThinkPad T16 (Intel) Gen 2 || 2023-11-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || colspan=2 | S2idle works. S3: Not available.
|-
| ThinkPad T16 Gen 4 || 2025-06-26 || {{G|HDMI: Untested}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || colspan=2 {{R|Fingerprint Reader is not found by the kernel}}
|}

=== X series ===

{{Laptops table header}}
| ThinkPad X1 || 2016-08-03 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|[[Bluetooth headset#HSP problem: the bluetooth sink and source are created, but no audio is being transmitted|Yes]]}} || {{Y|Hibernation: Untested}} || See [https://bbs.archlinux.org/viewtopic.php?id=158775 BBS#158775] for brightness || [https://web.archive.org/web/20150729124740/http://www.station-drivers.com/index.php/downloads/Drivers/Renesas-Nec/USB-3.0/Renesas-Nec-uPD720200a-USB-3.0-Controller-Firmware-Version-4.0.2.1.0.3/ Unofficial] update fixes USB3 issues.
|-
| ThinkPad X60 Tablet || 2011-07-12 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| ThinkPad X60s || 2014-11-23 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| ThinkPad X61s || 2014-11-23 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X100e|ThinkPad X100e]] || 2012-10-08 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| ThinkPad X120e || {{-}} || {{Yes}} || {{Yes}}* || {{Yes}} || {{Yes}}* || {{Yes}} || {{Yes}}* || colspan="2" |
* See [[ALSA#Card index]] to make HDMI the secondary device
* Flaky Realtek Wi-Fi card, needs a [https://web.archive.org/web/20140906221353/http://forums.mydigitallife.info/threads/20223-Remove-whitelist-check-add-ID-s-to-break-hardware-restrictions-mod-requests/page175 BIOS patch] to replace outside of the whitelist.
* Hibernation needs an [[Power management/Suspend and hibernate#System does not power off when hibernating|adjustment]]
|-
| ThinkPad X131e || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || [https://bbs.archlinux.org/viewtopic.php?id=159014 WLAN Led seems not controlled] ||
|-
| ThinkPad X140e || 2020-03-21 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || [https://bbs.archlinux.org/viewtopic.php?id=159014 WLAN Led seems not controlled] || If suspend hangs, try {{ic|echo 0 > /sys/power/pm_async}}.
|-
| [[Lenovo ThinkPad X200|ThinkPad X200]] || 2018-04-30 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| [[Lenovo ThinkPad X200S|ThinkPad X200S]] || 2017-04-11 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || Fingerprint, SD card and webcam: Untested. Modem might needs reset after sleep. ||
|-
| [[Lenovo ThinkPad X201|ThinkPad X201]] || 2015-06-16 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X220|ThinkPad X220]] || 2020-02-13 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X230|ThinkPad X230]] || 2017-03-03 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|No: Accelerometer}} ||
|-
| [[Lenovo ThinkPad X240|ThinkPad X240]] || 2018-07-04 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad X250 || 2017-04-21 || {{Yes}} || {{Yes}}* || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || *Use the {{ic|1=index=1,0}} [[kernel module parameter]] for {{ic|snd_hda_intel}} to [[Advanced Linux Sound Architecture#Set the default sound card|set the default sound card]] properly
|-
| [[Lenovo ThinkPad X260|ThinkPad X260]] || 2020-06-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || PSR powersaving is [[#ThinkPad X260|causing some microfreezes]].
|-
| [[Lenovo ThinkPad X270|ThinkPad X270]] || 2021-07-18 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad X280 || 2019-08-23 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || Like the X260 the PSR powersaving is [[#ThinkPad X260|causing some microfreezes]]
|-
| [[Lenovo ThinkPad X380 Yoga|ThinkPad X380 Yoga]] || 2025-11-18 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X390|ThinkPad X390]] || 2019-10-25 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X390 Yoga|ThinkPad X390 Yoga]] || 2020-02-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X395|ThinkPad X395]] || 2020-05-09 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Fingerprint reader: See [[Lenovo ThinkPad X1 Carbon (Gen 7)#Fingerprint sensor|dedicated page]]. || Prevent amdgpu issues by [https://support.lenovo.com/us/en/downloads/ds540046 updating to latest BIOS]
|-
| [[Lenovo ThinkPad X13 Gen 1 (AMD)|ThinkPad X13 Gen 1 (AMD)]] || 2020-12-26 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Proprietary/nonfree}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X13 Gen 3]] || 2024-04-05 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X13 Gen 4 (AMD)|ThinkPad X13 Gen 4 (AMD)]] || 2026-01-09 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X13 Gen 5|ThinkPad X13 Gen 5]] || 2024-06-25 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X13 Yoga (Gen 2)|ThinkPad X13 Yoga (Gen 2)]] || 2021-06-26 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || Modem: No, Untested: NFC, Smart Card ||
|-
| [[Lenovo ThinkPad X1 Carbon|ThinkPad X1 Carbon]] || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Proprietary/nonfree}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X1 Carbon (Gen 2)|ThinkPad X1 Carbon (Gen 2)]] || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X1 Carbon (Gen 3)|ThinkPad X1 Carbon (Gen 3)]] || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X1 Carbon (Gen 4)|ThinkPad X1 Carbon (Gen 4)]] || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X1 Carbon (Gen 5)|ThinkPad X1 Carbon (Gen 5)]] || 2018-09-04 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X1 Carbon (Gen 6)|ThinkPad X1 Carbon (Gen 6)]] || 2018-05-13 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X1 Carbon (Gen 7)|ThinkPad X1 Carbon (Gen 7)]] || 2019-12-14 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X1 Carbon (Gen 8)|ThinkPad X1 Carbon (Gen 8)]] || 2020-08-22 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X1 Carbon (Gen 9)|ThinkPad X1 Carbon (Gen 9)]] || 2021-11-05 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X1 Carbon (Gen 10)|ThinkPad X1 Carbon (Gen 10)]] || 2022-06-23 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| [[Lenovo ThinkPad X1 Carbon (Gen 11)|ThinkPad X1 Carbon (Gen 11)]] || 2023-07-29 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| [[Lenovo ThinkPad X1 Carbon (Gen 12)|ThinkPad X1 Carbon (Gen 12)]] || 2024-04-12 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || MIPI camera problems
|-
| [[Lenovo ThinkPad X1 Extreme|ThinkPad X1 Extreme]] || 2018-12-26 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Thunderbolt: Untested}} ||
|-
| [[Lenovo ThinkPad X1 Extreme (Gen 2)|ThinkPad X1 Extreme (Gen 2)]] || 2020-12-20 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X1 Extreme (Gen 3)|ThinkPad X1 Extreme (Gen 3)]] || 2021-06-21 || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad X1 Extreme (Gen 4i)|ThinkPad X1 Extreme (Gen 4i)]] || 2022-11-14 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad X1 Titanium (Gen 1) || 2022-07-04 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || Untested: TPM, fingerprint reader, IR webcam, stylus, mobile broadband ||
|-
| [[Lenovo ThinkPad X1 Yoga (Gen 1)|ThinkPad X1 Yoga (Gen 1)]] || 2022-01-30 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Partial}} || {{R|No: Accelerometer}} ||
|-
| [[Lenovo ThinkPad X1 Yoga (Gen 3)|ThinkPad X1 Yoga (Gen 3)]] || 2018-11-23 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Partial}} || ||
|-
| [[Lenovo ThinkPad X1 Yoga (Gen 4)|ThinkPad X1 Yoga (Gen 4)]] || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|No: NFC}} ||
|}

== Lenovo ==

=== Battery conservation mode ===

Battery Conservation Mode is a feature that limits battery charging to 55-60% of its capacity to improve battery life, being most useful when the laptop tends to run on external power much of the time. This works on many Lenovo laptops like IdeaPad and Thinkbook series. To check if your laptop is supported, try to set the battery conservation mode in the Vantage app on Windows. If it works on Windows, it can be enabled or disabled on Linux in the following manner:

* First make sure the {{ic|ideapad_laptop}} kernel module is loaded, with the {{ic|lsmod}} command.
* If it is, run the following command as root to enable Battery Conservation Mode:{{bc|# echo 1 > /sys/bus/platform/drivers/ideapad_acpi/VPC2004:00/conservation_mode}}
* A {{ic|0}} will in turn disable the feature.

{{Note|1=<nowiki/>
* Both the presence and implementation of this feature vary by model. Particularly, the name of the folder '''VPC2004:00''' could differ.
* If the above does not work on your laptop, you can try a different method described [https://forums.linuxmint.com/viewtopic.php?f=49&t=286237#p1583578 here], which may require some (further) trial and error.
}}

If you use [[GNOME]] you can install the [https://extensions.gnome.org/extension/2992/ideapad/ Ideapad] extension to get an easy toggle (do not forget to [https://github.com/laurento/gnome-shell-extension-ideapad#additional-required-settings configure sudo] for it as well).

If you instead use [[KDE]], you can similarly install the [https://store.kde.org/p/2150610 PlasmaVantage] applet to get a toggle (you can also enable [https://gitlab.com/Scias/plasmavantage#password-less-operation Password-less operation]).

=== Special buttons ===

Some special buttons are not supported by X server due to keycode number limit, and may also not be recognized on [[Wayland]]. Listed below are the two most common ones, but others can be encountered.

{| class="wikitable" style="text-align:center"
|-
! Key combination !! Scancode !! Keycode
|-
| {{ic|Fn+F11}} || {{ic|0x49}} || {{ic|374}} {{ic|KEY_KEYBOARD}}
|-
| {{ic|Fn+F12}} || {{ic|0x45}} || {{ic|364}} {{ic|KEY_FAVORITES}}
|}

You can remap unsupported keys so that they can be detected and mapped in X by creating the following configuration:

{{hc|/etc/udev/hwdb.d/90-thinkpad-keyboard.hwdb|<nowiki>
evdev:name:ThinkPad Extra Buttons:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*
KEYBOARD_KEY_45=prog1
KEYBOARD_KEY_49=prog2
</nowiki>}}

{{Note|{{ic|prog1}} and {{ic|prog2}} map to {{ic|KEY_PROG1}} and {{ic|KEY_PROG2}} in {{ic|/usr/include/linux/input-event-codes.h}}. You can use any key code with a defined value less than 255. The keycode hwdb expects is the lowercased text following {{ic|KEY_}} in the above input event codes header file. eg: {{ic|KEY_COFFEE}} would be {{ic|coffee}}.}}

Then follow the steps at [[Map scancodes to keycodes#Using udev]].

=== BIOS/Firmware update ===

Lenovo provides updates for firmware and BIOS updates for some of their devices via [[fwupd]], supported devices can be found by [https://fwupd.org/lvfs/search?value=Lenovo searching on the fwupd website]

To update other devices which Lenovo only provides Windows installers, you can manually download the firmware from [https://pcsupport.lenovo.com Lenovo support website] and install it by following the instructions in [[Flashing BIOS from Linux#Lenovo]]

=== Advanced UEFI Options ===

{{Warning|'''DO NOT''' change any options without understanding the consequences or you may risk '''permanent damage to your device''' and potentially '''void your warranty'''.}}

Some IdeaPad and Legion models have some of the more advanced UEFI options locked. It may be useful to unlock them. There are a few known methods that may unlock the advanced options.

==== Button combination ====

* Turn off OneKeyBattery mode in BIOS setup, if it is enabled, and save the BIOS settings.
* Power down the laptop.
* Type, with the laptop powered off: {{ic|F1}} {{ic|1}} {{ic|Q}} {{ic|A}} {{ic|Z}} {{ic|F2}} {{ic|2}} {{ic|W}} {{ic|S}} {{ic|X}} {{ic|F3}} {{ic|3}} {{ic|E}} {{ic|D}} {{ic|C}} {{ic|F4}} {{ic|4}} {{ic|R}} {{ic|F}} {{ic|V}} {{ic|F5}} {{ic|5}} {{ic|T}} {{ic|G}} {{ic|B}} {{ic|F6}} {{ic|6}} {{ic|Y}} {{ic|H}} {{ic|N}}.
If you notice the pattern, it is just going down the column from {{ic|F1}} to the letter in the last keyboard row, from {{ic|F1}} to {{ic|F6}}. (You may need to replace some keys accordingly if you got a QWERTZ layout or similar alternative layouts).
* Boot the laptop with {{ic|F2}} pressed to get into BIOS as usual.

==== EFI variable ====

On some pre-2022 models, you can create an [[Unified Extensible Firmware Interface#UEFI variables|EFI variable]], {{ic|6ACCE65D-DA35-4B39-B64B-5ED927A7DC7E-cE!}} and set it to {{ic|1}} to enable the advanced options. The userspace {{Pkg|efivar}} can be used to create this variable:

# echo 1 > param
# efivar --name '6ACCE65D-DA35-4B39-B64B-5ED927A7DC7E-cE!' --write --datafile=param
# rm param

==== Patch EFI modules at runtime ====

The currently unmaintained tool [https://github.com/barlowhaydnb/SmokelessRuntimeEFIPatcher SmokelessRuntimeEFIPatcher] can be used to patch/inject at runtime. There are several patches provided here: https://github.com/quanbingyi/SREP-Community-Patches

For example

* Download or build the SmokelessRuntimeEFIPatcher EFI binary, then store the EFI on the ESP, e.g. {{ic|/boot/efi/efi/srep/SREP.efi}}
* Find a suitable patch for your firmware in [https://github.com/quanbingyi/SREP-Community-Patches SREP-Community-Patches], save the patch as {{ic|SREP_Config.cfg}} in the top-level directory of the ESP, e.g. {{ic|/boot/efi/SREP_Config.cfg}}.
* Create a [[Unified Extensible Firmware Interface#UEFI variables|UEFI variable]] for executing SREP EFI binary.
* Select the SREP boot entry in the UEFI boot menu to run the UEFI setup utilities with the monkeypatched firmware at runtime.

=== Enable CPPC ===

To use the {{ic|amd_pstate}} driver, [https://docs.kernel.org/admin-guide/acpi/cppc_sysfs.html CPPC] must be enabled, see [[CPU frequency scaling#Scaling drivers]] for details on how to enable CPPC.

=== Series ===

==== A series ====

{{Laptops table header}}
| ThinkPad A485 || 2018-12 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | [[Laptop Mode Tools]] {{ic|runtime-pm}} disables Bluetooth
|}

==== B series ====

{{Laptops table header}}
| B50 || 2015-06-17 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || ||
|-
| B50-70 || 2015-08-25 || {{G|[[#B50-70|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || || See [[#B50-70]]
|-
| B450 || 2016-07-29 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{-}} || {{Y|Untested}} || ||
|-
|}

==== C series ====

See [[Chrome OS devices/Chromebook#Hardware comparisons]].

==== Edge series ====

{{Laptops table header}}
| ThinkPad Edge E130 || 2013-09-22 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Card reader: Untested}} ||
|-
| [[Lenovo ThinkPad Edge E330|ThinkPad Edge E330]] || 2015-01-29 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo ThinkPad Edge E335|ThinkPad Edge E335]] || 2015-01-29 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || ||
|-
| ThinkPad Edge E420s || 2011-04-18 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{R|No: Trackpoint}} || BIOS update 1.08 fixes spacebar issue.
|-
| [[Lenovo ThinkPad Edge E430|ThinkPad Edge E430]] || 2013-04-07 || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Y|Untested}} || ||
|-
| [[Lenovo ThinkPad Edge E455|ThinkPad Edge E455]] || 2015-04-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad Edge E460 || 2020-03-08 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | TouchPad/Trackpoint needs {{ic|i8042.noloop i8042.nomux i8042.nopnp i8042.reset}} with [[libinput]].
|-
| ThinkPad Edge E470 || 2020-11-11 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad Edge E530 || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| ThinkPad Edge E531 || 2018-02-18 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}* || {{Yes}} || {{Yes}} || || *Wi-Fi only works with {{Pkg|broadcom-wl-dkms}}
|-
| ThinkPad Edge E540 || 2015-08-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad Edge E545 || 2017-08-13 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}* || {{Y|Untested}} || {{Yes}} || || *Wi-Fi only works with {{Pkg|broadcom-wl-dkms}}
|-
| ThinkPad Edge E555 || 2015-06-27 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}* || {{Y|Untested}} || {{Yes}} || || *Wi-Fi needs rate set to 54M with ''iwconfig'' to fix signal drops
|-
| ThinkPad Edge E580 || 2018-05-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | Fingerprint sensor does not work because of proprietary firmware
|-
|}

==== E series ====

{{Laptops table header}}
| ThinkPad E485 || 2018-10-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || See [[#ThinkPad E485]].
|-
| ThinkPad E585 || 2018-11-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || See [[#ThinkPad E585]].
|-
| ThinkPad E595 || 2020-05-24 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || See [[#ThinkPad E595]].
|-
| ThinkPad E15 Gen 2 || 2022-01-10 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || See [[#ThinkPad E15 Gen 2]].
|-
| ThinkPad E15 Gen 4 (Intel) || 2023-11-03 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || See [[#ThinkPad E15 Gen 2]].
|-
| ThinkPad E14 Gen 5 (AMD) || 2023-12-14 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad E14 Gen 7 (AMD) || 2025-12-04 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Fingerprint Sensor}} ||
|-
| ThinkPad E14 Gen 7 (Intel) || 2026-03-11 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Fingerprint Sensor}} ||
|-
| ThinkPad E16 Gen 1 (AMD) || 2024-06-26 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || See [[#Thinkpad E16 Gen 1 (AMD)]]
|-
| ThinkPad E16 Gen 2 (AMD) || 2024-09-12 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad E16 Gen 3 (AMD) || 2026-01-19 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Fingerprint Sensor Touchscreen Untested: IR camera}} || *IR camera should work with {{AUR|howdy}}
|-
|}

==== L series ====

{{Laptops table header}}
| [[Lenovo ThinkPad L380 Yoga|ThinkPad L380 Yoga]] || 2018-09-21 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad L390 || 2021-03-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || Touchscreen 20NRCTO1WW [https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849721 partial] with [[blacklisting]] {{ic|raydium_i2c_ts}}
|-
| ThinkPad L390 Yoga || 2019-09-05 || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested: Touchscreen SD card reader}} || Fingerprint sensor not supported by {{Pkg|libfprint}}, see [https://github.com/nmikhailov/Validity90/issues/47]
|-
| ThinkPad L420 || 2025-11-05 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: SD card reader}} || Fingerprint sensor recognized but not supported by {{Pkg|libfprint}} or {{Pkg|fprintd}}.
|-
| ThinkPad L430 || 2014-11-23 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad L440 || 2019-01-24 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad L450 || 2019-11-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad L460 || 2019-06-24 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad L470 || 2022-01-24 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || Trackpoint, Fingerprint reader, SD Card Reader ||
|-
| ThinkPad L490 || 2020-12-13 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}* || {{Yes}} || {{Yes}}** || {{Y|Untested: Fingerprint reader}} || *[https://bbs.archlinux.org/viewtopic.php?pid=1980983#p1980983 RTL8822BE] **[[Fan speed control#ThinkPad laptops|Configure fans]] to avoid thermal throttling (e.g. {{AUR|thinkfan}}).
|-
| ThinkPad L520 || 2018-09-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || {{Y|Untested}} ||
|-
| ThinkPad L530 || 2014-11-23 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad L560 || 2018-12-28 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || ||
|-
| ThinkPad L13 Yoga || 2026-01-13 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: Smartcard-Reader}} || No wired Ethernet onboard, proven to work with "Lenovo USB-C to Ethernet Adapter". Fingerprint scanner doesn't work.
|-
| ThinkPad L13 Yoga Gen2 || 2021-08-10 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: Smartcard-Reader}} || No: SW_TABLET_MODE Detection (Driver broken [https://bugzilla.kernel.org/show_bug.cgi?id=211741], should be fixed in v6.17[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.17-rc3&id=3a807f3ff9eaaeead81576c5a72d226d519a2fe7]) To enable Trackpoint and touchpad buttons use the [[Laptop#Elantech|fix for Elantech touchpads]]
|-
| ThinkPad L13 Yoga Gen4 || 2025-07-23 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | No: SW_TABLET_MODE Detection (Driver broken [https://bugzilla.kernel.org/show_bug.cgi?id=211741], should be fixed in v6.17[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.17-rc3&id=3a807f3ff9eaaeead81576c5a72d226d519a2fe7]) Untested: Smartcard-Reader Untested: Mobile Networking (LTE)
|-
| ThinkPad L14 Gen1 (Intel) || 2020-09-17 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || colspan=2 | No: Touchpad physical buttons Trackpoint Untested: MicroSD card reader
|-
| ThinkPad L14 Gen3 (Intel) || 2023-12-23 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: Card Reader, Smartcard Reader}} ||
|-
| ThinkPad L14 Gen1 (AMD) || 2021-04-20 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 {{R|No: Fingerprint reader (No driver available)}}
|-
| ThinkPad L15 Gen1 (AMD) || 2021-01-30 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}* || {{Yes}} || {{Yes}} || Fingerprint works with modified firmware at [https://github.com/goodix-fp-linux-dev/goodix-fp-dump], together with the driver {{AUR|libfprint-goodixtls-55x4}}. Firmware reverts if laptop is dual booted || {{ic|1=iommu=soft}} required for UEFI≤1.13. * Random disconnections require [[Wireless#Cause #6|disabling power saving in iwlmvm]].
|-
| ThinkPad L15 Gen2 (AMD) || 2021-07-20 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad L14 Gen2 (AMD) || 2021-07-02 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|}} || {{Yes}} || {{R|No: IR-Camera}} ||
|-
| ThinkPad L14 Gen2a (AMD) || 2021-09-06 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Partial*}} || || *No sleep, IRQ86 and IRQ88 consume a lot of CPU. see [https://bbs.archlinux.org/viewtopic.php?pid=1991663#p1991663 on BBS] and [https://www.reddit.com/r/AMDLaptops/comments/pdpfaq/lenovo_thinkpad_l14_gen2_amd_linux/ on reddit].
|}

==== N series ====

{{Laptops table header}}
| N200 (3000) || 2007-12-25 || {{Yes}} || {{G|[[#N200 (3000)|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
|}

==== P series ====

{{Laptops table header}}
| [[Lenovo ThinkPad P50|ThinkPad P50]] || 2019-07-18 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | Fingerprint Reader ({{AUR|libfprint-vfs009x-git}})
|-
| [[Lenovo ThinkPad P70|ThinkPad P70]] || 2019-07-20 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Hibernate: Untested}} || colspan=2 | Fingerprint Reader ({{AUR|libfprint-vfs009x-git}})
|-
| [[Lenovo ThinkPad P51|ThinkPad P51]] || 2018-06-08 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|No: TPM, Color calibrator, UEFI flash}} ||
|-
| [[Lenovo ThinkPad P52|ThinkPad P52]] || 2020-03-16 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Hibernate: Untested}} || ||
|-
| [[Lenovo ThinkPad P1|ThinkPad P1]] || 2018-12-23 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Hibernate: Untested}} || ||
|-
| [[Lenovo ThinkPad P1 (Gen 2)|ThinkPad P1 (Gen 2)]] || 2019-09-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: Webcam}} ||
|-
| ThinkPad P1 (Gen 3) || 2021-06-24 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: Fingerprint reader, TPM}} ||
|-
| [[Lenovo ThinkPad P1 (Gen 4)|ThinkPad P1 (Gen 4)]] || 2022-05-04 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: TPM}} ||
|-
| ThinkPad P52s || 2019-02-25 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|NFC: [https://github.com/nfc-tools/libnfc/issues/455 No] Fingerprint: [https://forums.lenovo.com/t5/Linux-Discussion/Thinkpad-T580-Synaptics-Metallica-MIS-Touch-Fingerprint-Reader/m-p/4057745 No]}} || Specify {{ic|BusID "PCI:0:2:0"}} in [[xorg.conf]]
|-
| [[Lenovo ThinkPad P53|ThinkPad P53]] || 2020-05-02 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Hibernate: Untested}} || ||
|-
| ThinkPad P53s || 2019-10-28 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || colspan=2 {{Y|Untested: Multi-monitor Card Reader Smartcard Reader Fingerprint}}
|-
| ThinkPad P73 || 2020-06-10 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || colspan=2 | No: Multi-monitor Untested: Card Reader Smartcard Reader Fingerprint
|-
| [[Lenovo ThinkPad P43s|ThinkPad P43s]] || 2020-07-14 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || colspan=2 {{Y|Untested: Smartcard Reader Fingerprint}}
|-
| [[Lenovo ThinkPad P15s|ThinkPad P15s]] || 2020-10-27 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 {{Y|Untested: Smartcard Reader Fingerprint}}
|-
| ThinkPad P17 (Gen 1) || 2021-03-12 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Hibernate: Untested}} || {{Y|Untested: Webcam (IR) Card Reader Fingerprint}} || Graphics tested in Discrete mode only.
|-
| ThinkPad P14s (AMD) Gen 2 || 2022-02-19 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | For better suspend battery usage, set sleep mode in BIOS to Linux. For touchscreen, [[append]] {{ic|blacklist raydium_i2c_ts}} to {{ic|/etc/modprobe.d/unneeded-modules.conf}}
|-
| ThinkPad P14s (Intel) Gen 2 || 2024-10-20 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: Smartcard Reader}} ||
|-
| [[Lenovo ThinkPad P14s (AMD) Gen 5|ThinkPad P14s Gen 5 AMD]] || 2024-11-28 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: Smartcard Reader}} ||

|-
| [[Lenovo ThinkPad P14s (Intel) Gen 6|ThinkPad P14s Gen 6 Intel]] || 2026-20-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Hibernate: Untested}} || ||
|-
| [[Lenovo ThinkPad P14s (AMD) Gen 6|ThinkPad P14s Gen 6 AMD]] || 2025-11-04 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Hibernate: Untested}} || ||
|-
| ThinkPad P15v Gen 2 || 2022-07-10 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: Smartcard Reader Fingerprint}} ||
|-
| ThinkPad P15v (AMD) Gen 3 || 2024-01-15 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: Smartcard Reader}} ||
|-
| [[Lenovo ThinkPad P16s (AMD) Gen 2|ThinkPad P16s (AMD) Gen 2]] || 2023-10-27 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Needs [[Lenovo ThinkPad P16s (AMD) Gen 2#Hang on resume|workaround]] to prevent hang on suspend/ hibernate}} || {{Y|Untested:
Smartcard Reader
}} || Firmware updates not available on LVFS yet, check for "BIOS update" on Lenovo's support website using your serial number.
|-
| [[Lenovo Thinkpad P17 (Gen 2)|ThinkPad P17 (Gen 2)]] || 2022-07-15 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|}

==== S series ====

{{Laptops table header}}
| [[Lenovo S20-30|S20-30]] || 2020-06-26 || {{Yes}} || {{Yes}} || {{Yes}} || {{G|[[Lenovo S20-30#Wi-Fi|Yes*]]}} || {{Y|Untested}} || {{Yes}} || ||
|-
| S21e-20 || 2015-07-01 || {{Yes}} || {{Yes}} || {{-}} || {{G|[[#S21e-20|Yes*]]}} || {{Y|Untested}} || {{Yes}} || {{Y|Untested: HDMI}}||
|-
|}

==== U series ====

{{Laptops table header}}
| U31-70 || 2015-10-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
|}

==== V series ====

{{Laptops table header}}
| V110-15ISK || 2017-08-31 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Y|Untested: USB3 HDMI}} ||
|-
| V130-15IKB || 2019-08-11 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| V330-15IKB || 2018-10-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{R|No drivers for Validity/Synaptics {{ic|06cb:0081}} Fingerprint Reader}} ||
|-
| V15-IIL || 2022-02-16 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || colspan=2 | Touchpad needs {{ic|1=pci=nocrs}} in [[kernel parameters]] to be detected.
|-
| [[Lenovo V15 G2-ALC|V15 G2-ALC]] || 2022-05-03 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo V15 G3 ABA|V15 G3 ABA]] || 2024-04-19 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|}

==== W series ====

{{Laptops table header}}
|-
| ThinkPad W500 || 2020-02-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad W510 || 2017-04-13 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: Fingerprint Reader}} ||
|-
| ThinkPad W530 || 2018-04-15 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad W540 || 2017-04-09 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad W541 || 2018-08-22 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad W550s || 2018-04-24 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
|}

==== Z series ====

{{Laptops table header}}
|-
| [[Lenovo ThinkPad Z13|ThinkPad Z13]] || 2022-09-10 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| ThinkPad Z16 || 2022-10-14 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} ||Finger print reader works || Keyboard needs i8042.direct and i8042.dumbkbd (as of 6.4.12)
|-
| [[Lenovo ThinkPad Z16 Gen 2|ThinkPad Z16 Gen 2]] || 2024-03-19 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|}

==== Helix series ====

{{Laptops table header}}
| [[Lenovo ThinkPad Helix|ThinkPad Helix]] || 2016-02-01 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| [[Lenovo ThinkPad Helix 2nd Gen|ThinkPad Helix 2nd Gen]] || 2018-04-01 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Y|Untested}} || {{G|[[Lenovo ThinkPad Helix 2nd Gen#Suspend & Resume|Yes*]]}} || {{Y|Untested: Pen}} || *BIOS update needed
|-
|}

==== IdeaPad series ====

{{Laptops table header}}
| IdeaPad s10-3t || 2012-01-04 || {{Yes}} || {{Yes}} || {{G|[[Network configuration/Ethernet#Broadcom BCM57780|Yes*]]}} || {{G|[[Broadcom wireless#broadcom-wl|Yes*]]}} || {{Yes}} || {{Yes}} || Accelerometer works with [https://github.com/Lyude/iaps IAPS] ||
|-
| IdeaPad Y480 || 2014-11-05 || {{Yes}} || {{Yes}}* || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || Fix [[Advanced Linux Sound Architecture/Troubleshooting#Wrong model autodetection|audio autodetection]] with {{ic|1=model=ideapad}}
|-
| IdeaPad 120S || 2018-06-18 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo IdeaPad Flex 10|IdeaPad Flex 10]] || 2015-02-13 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| IdeaPad Flex 14 || 2021-05-22 || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| IdeaPad S100 || 2021-12-30 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || ||
|-
| IdeaPad S400u || 2014-05-31 || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || ||
|-
| [[Lenovo IdeaPad S400 Touch|IdeaPad S400 Touch]] || 2014-01-23 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| [[Lenovo IdeaPad U410|IdeaPad U410]] || 2026-03-18 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || ||
|-
| IdeaPad U430p || 2015-08-20 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| IdeaPad Y700 || 2015-12-01 || {{Yes}} || {{G|[[#IdeaPad Y700|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || Trackpad - [https://unix.stackexchange.com/questions/362165/lenovo-y700-elantech-touchpad-query-0x01-failed buggy] || [https://bugzilla.kernel.org/show_bug.cgi?id=151681 Trackpad requires pata_legacy to be blacklisted]
|-
| IdeaPad Z510 || 2017-05-04 || {{Yes}} || {{G|[[Advanced Linux Sound Architecture#Set the default sound card|Yes*]]}} || {{Yes}} || {{G|[[Broadcom wireless#broadcom-wl|Yes*]]}} || {{Yes}} || {{Yes}} || || See [[NVIDIA Optimus#Lockup issue (lspci hangs)]]
|-
| IdeaPad Z580 || 2017-01-20 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| IdeaPad 720s || 2018-04-15 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|Fingerprint reader {{ic|06cb:0081}}}} ||
|-
| [[Lenovo IdeaPad 720s (AMD)|IdeaPad 720s (AMD)]] || 2018-02-01 || {{Yes}} || {{Yes}} || {{-}} || {{G|[[Lenovo IdeaPad 720s (AMD)#Wireless|Yes*]]}} || {{Y|Untested}} || {{Y|Untested}} || {{Y|Untested: Fingerprint reader}} ||
|-
| Ideapad 320 || 2018-03-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || colspan=2 | To stop constant annoying messages by AMD-Vi, use {{ic|1=iommu=soft}} & {{ic|1=amd_iommu=off}}
|-
| Ideapad 320-15IKB || 2018-03-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}|| colspan=2 | [https://github.com/nmikhailov/Validity90 Dead driver project] and little/no hope of Lenovo or Synaptics developing a driver for the fingerprint reader.
|-
| Ideapad 330 (AMD) || 2019-02-07 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || colspan=2 | {{ic|1=ivrs_ioapic[32]=00:14.0}} [[kernel parameter]] required to make the Touchpad work.
|-
| Ideapad 330S-14IKB || 2019-10-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || colspan=2 | {{ic|Firmware Error (ACPI): Could not resolve [^^^GFX0.AFN2], AE_NOT_FOUND (20181213/psargs-503)}} log spam requires disabling ACPI ({{ic|1=acpi=off}}) or connecting to a charger.
|-
| Ideapad N24 || 2018-04-01 || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Y|Untested}} ||{{Y|Untested}} || ||
|-
| Ideapad 3-15ARE05 || 2020-10-27 || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Yes}} || {{Yes}} || Touchpad requires blacklisting {{ic|elants_i2c}} fingerprint sensor {{ic|04f3:0c57}} is not supported in [[fprint]] ||
|-
| IdeaPad 5 14iil05 || 2021-02-20 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| IdeaPad 5 15ITL05 || 2020-09-15 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || Fingerprint sensor {{ic|27c6:55a2}} is not supported in [[fprint]]. Lenovo's "'''Conservation mode'''" (battery) can be controlled using [https://github.com/liperium/Linux-Conservation-Mode-Utility Linux-Conservation-Mode-Utility]. ||
|-
| [[Lenovo IdeaPad 5 15are05|IdeaPad 5 15are05]] || 2020-11-09 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || Screen backlight control requires {{ic|1=acpi_backlight=video}} fingerprint sensor {{ic|27c6:55a2}} is not supported in [[fprint]] ||
|-
| IdeaPad 3 Gaming 15ARH05 || 2021-11-03 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan="2" | {{ic|Fn+Q}} appears working but {{ic|ideapad_laptop}} does not show said changes in {{ic|fan_mode}} HDMI port does not work properly. See [[PRIME]] and [[NVIDIA]] and enable the DRM kernel mode setting.
|-
| Ideapad 5 Pro 16ACH || 2021-12-13 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || After waking up from hibernation, Wi-Fi sometimes does not work. After waking up from suspension, the system sometimes crashes. || No software control for keyboard backlight, always disabled at boots: {{ic|Fn+Space}} works.
|-
| [[Lenovo IdeaPad 5 Pro 14ACN6|IdeaPad 5 Pro 14ACN6]] || 2022-04-24 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || After waking from suspend, the trackpad may be slow to respond for several minutes.
|-
| IdeaPad Flex 5 15alc05 || 2021-12-16 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || colspan=2 | Bugginess on 5GHz networks. Test network card via 2.4GHz and 5GHz before installation. Fingerprint sensor {{ic|27c6:55b4}} is not supported in [[fprint]].
|-
| IdeaPad 5 Pro 14APH10 || 2023-10-20 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || colspan=2 | No software control for keyboard backlight, always enabled at boots. {{ic|Fn+Space}} works. For the {{ic|Fn}} key to properly work, "FnLock" needs to be enabled by pressing {{ic|Fn+Esc}}.
|-
| [[Lenovo IdeaPad Slim 3 16ABR8|IdeaPad Slim 3 16ABR8]] || 2023-12-16 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 |Fingerprint needs {{AUR|libfprint-2-tod1-goodix}}
|-
| IdeaPad 5 Pro 16ARP8 || 2024-01-17 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || colspan=2 | Sleep currently needs {{ic|acpi.prefer_microsoft_guid{{=}}1}} as a [[Kernel parameters]] and some BIOS parameters thinkering
|-
| IdeaPad 5 Pro 14AHP9 || 2024-09-29 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Y|Often reboots after wake from suspend}} || colspan=2 |
|-
| IdeaPad 5 Pro 14ARH7 || 2023-12-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | Sometimes begins to stutter and then freezes; WiFi sometimes loses connection and can't reconnect
|-
| [[Lenovo IdeaPad L3 (15IML05)|IdeaPad L3 (15IML05)]] || 2024-04-26 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | Throttling can be fixed with [[thermald]]. fn_lock with {{ic|/sys/bus/platform/drivers/ideapad_acpi/VPC2004:00/fn_lock}} , See [[#Battery conservation mode]].
|-
| [[Lenovo IdeaPad 5i (16IRU9)|IdeaPad 5i 16IRU9]] || 2024-11-25 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | After waking from hibernation, the system is unresponsive for approximately 30 seconds.
|-
| [[Lenovo IdeaPad Gaming 3|IdeaPad Gaming 3 15ACH6]] || 2026-05-12 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| IdeaPad 1 15IAU7 || 2025-07-06 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| IdeaPad Slim 3 15ABR8 || 2025-07-20 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | See [[Lenovo IdeaPad Slim 3 16ABR8#Keyboard]] for post-suspend keyboard issues.
|-
| IdeaPad 5 Pro 16APH8 || 2025-04-09 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | The display is locked at 60Hz due to a {{ic|[drm] DisplayID checksum invalid, remainder is xxx}} EDID error. [https://github.com/AVAM16/lenovo-ideapad-pro-5-16-16APH8-120hz-fix This guide] should be followed to unlock the 120Hz refresh rate option.
|-
| IdeaPad 5 2-in-1 16AHP9 || 2025-08-23 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| IdeaPad Slim 5 14IMH9 || 2025-09-07 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| IdeaPad 1 15AMN7 || 2025-09-07 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| IdeaPad Pro 5i 14IAH10 || 2025-09-13 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | Issues with Wi-Fi 7 Intel BE200 card (commonly reported on other forums) when resuming from suspend. The device disappears and a reboot is needed to fix it. Resolved by disabling D3cold {{bc|# echo 0 > /sys/bus/pci/devices/0000:01:00.0/d3cold_allowed}}
|-
| [[Lenovo IdeaPad Slim 3 14ABR8|IdeaPad Slim 3 14ABR8]] || 2026-03-21 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || || Fingerprint can enroll but not verify
|}

==== Legion series ====

{{Laptops table header}}
| Legion Y520 || 2020-10-06 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|SD card (Flaky)}} || Possible [https://unix.stackexchange.com/questions/491944/cpu-temperatures-in-linux-throttling-or-wrong-reading CPU throttling]. Fan control [https://odintdh.itch.io/extremecooling4linux works perfectly as intended]
|-
| Legion Y730 || 2019-09-12 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: USB-C}} || Disable nouveau with {{ic|1=module_blacklist=nouveau}} or {{ic|1=nouveau.modeset=0}}
|-
| [https://linux-hardware.org/index.php?computer=af3a4bc1494f Legion Y7000P-1060] || 2019-09-27 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: Mini DisplayPort}} || No fan control.
|-
| Legion Y540 || 2020-02-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || Hibernation [[Power management/Suspend and hibernate#Suspend/hibernate does not work, or does not work consistently|requires]] {{ic|intel_lpss_pci}} in [[initramfs]]. No fan control with [https://github.com/johnfanv2/LenovoLegionLinux LenovoLegionLinux].
|-
| Legion Y545 || 2020-05-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: Mini DisplayPort}}
|-
| Legion 5 || 2020-11-05 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || rowspan="3" | Brightness control might require to be [https://askubuntu.com/questions/70552/cant-adjust-brightness-on-my-msi-vr420-laptop/104803#104803 explicitly enabled]. Fan control and changing power profiles using Fn+Q with [https://github.com/johnfanv2/LenovoLegionLinux LenovoLegionLinux].
|-
| Legion 5i || 2020-08-15 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: USB-C}}
|-
| Legion 5Pi || 2020-08-11 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Y|Untested: HDMI}}
|-
| Legion 5 Slim || 2026-01-21 || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: SD card headphone jack}} ||
|-
| [[Lenovo Legion 7i|Legion 7i]] || 2020-08-02 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: HDMI NVIDIA GPU}} . Fan control with [https://github.com/johnfanv2/LenovoLegionLinux LenovoLegionLinux].
|-
| Legion 7 || 2020-11-13 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || RGB keyboard can be controlled with {{AUR|openrgb-git}}. 165Hz edid export error screen size. Fan control with [https://github.com/johnfanv2/LenovoLegionLinux LenovoLegionLinux].
|-
| Legion Slim 7 2022 || 2023-02-07 || {{Yes}} || {{Y|Partial}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|No: Elan Fingerprint {{ic|04f3:0c4b}}}} || Audio through headphone jack works, but not through speakers due to missing quirks for amplifier chipset (6.1.9-1 kernel). Fan control with [https://github.com/johnfanv2/LenovoLegionLinux LenovoLegionLinux].
|-
| Legion 5 Pro || 2021-07-21 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Cannot see CPU temperature or control fans on some models}}, but works with [https://github.com/johnfanv2/LenovoLegionLinux LenovoLegionLinux] || RGB keyboard can be controlled with [https://github.com/imShara/l5p-kbl l5p-kbl]. || Wi-Fi adapter requires {{Pkg|linux-firmware}} and erratic Wi-Fi latency may benefit from disabling power saving features.
|-
| Legion Y7000 2019 PG0 || 2022-06-18 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: Mini DisplayPort HDMI}} || Hibernation [[Power management/Suspend and hibernate#Suspend/hibernate does not work, or does not work consistently|requires]] {{ic|intel_lpss_pci module}} in [[initramfs]]
|}

==== LOQ series ====

{{Laptops table header}}
| LOQ 15IRH8 || 2024-08-30 || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: HDMI}} || Some keyboard shortcuts require the {{ic|ideapad_laptop}} module. Fan control and power management with [https://github.com/johnfanv2/LenovoLegionLinux LenovoLegionLinux].
|-
| [[Lenovo LOQ 15ARP9|LOQ 15ARP9]] || 2025-09-25 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Yes*}} || || * Power management requires configuration. See [[Lenovo LOQ 15ARP9#Power management]]{{Broken section link}}.
Performance mode can be toggled between Quiet/Balanced/Performance through with Fn+Q shortcut. This and other keyboard shortcuts require the {{ic|ideapad_laptop}} module.
|-
| LOQ 16APH8 || 2026-01-31 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Yes*}} || || * For Power management, the same conditions apply as for the 15ARP9.
The fix mentioned for suspension in [[Lenovo LOQ 15ARP9#Suspend]] also works for the 16APH8.
|}

==== Nano series ====

{{Laptops table header}}
| [[Lenovo ThinkPad X1 Nano|ThinkPad X1 Nano]] ||| 2022-04-13 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: Fingerprint Reader}} ||
|-
| [[Lenovo ThinkPad X1 Nano (Gen 2)|ThinkPad X1 Nano (Gen 2)]] ||| 2022-10-17 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: Fingerprint Reader}} ||
|-
|}

==== ThinkBook series ====

{{Laptops table header}}
| ThinkBook 13s Gen 2 AMD || 2021-05-09 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: Fingerprint}} ||
|-
| ThinkBook 13s Gen 2 Intel || 2021-04-16 || {{Yes}}* || {{G|[[Sound Open Firmware|Yes*]]}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|No: Fingerprint}} || *[[Intel graphics#Installation|modesetting]] fixes browser freezes internal mic [https://github.com/thesofproject/linux/issues/2460#issuecomment-779212719 requires custom topology]
|-
| ThinkBook 13s Gen 3 AMD || 2024-06-24 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|No: Fingerprint}} || See [[#Battery conservation mode]]
|-
| ThinkBook 14p Gen 2 ACH (AMD) || 2022-07-02 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|No: Elan Fingerprint {{ic|04f3:0c4b}}}} || See [https://gist.github.com/Kingtous/9b20742899d7a0bfbd82d0eb43fa412b DSDT Patch] to enable S3 suspend
|-
| ThinkBook 14 Gen 3 ACL (AMD) || 2021-11-17 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|No: Elan Fingerprint {{ic|04f3:0c4b}}}} ||
|-
| ThinkBook 15 Gen 2 ITL || 2022-05-23 || {{Yes}} || {{G|[[#N200 (3000)|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Probably works: [https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/356 Elan Fingerprint]}} || See [[#Battery conservation mode]]
|-
| ThinkBook 15 Gen 2 AMD || 2021-02-22 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|No: Elan Fingerprint {{ic|04f3:0c4b}}}} || See [[#Battery conservation mode]]
|-
| ThinkBook 16p Gen 2 AMD || 2021-12-06 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|No: Elan Fingerprint {{ic|04f3:0c4b}}}} ||
|-
| ThinkBook 16p Gen 4 Intel || 2022-09-22 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{-}} || Use the ''modesetting'' Intel driver (see [[Intel graphics#Installation]])
|-
| ThinkBook 13x Gen 2 || 2023-05-20 || {{Yes}} || {{Y|Partial}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: Fingerprint}} || Audio through headphone jack works, but not through speakers due to missing quirks for amplifier chipset (6.2.0 and 6.3.3 kernel).
|-
| ThinkBook 14 G5+ IRH || 2023-08-03 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{-}} || See [[#Battery conservation mode]]
|-
| ThinkBook 14 G6+ AHP || 2024-01-29 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|Fn key for brightness controller and laptop lid closing will cause power halt}} || ≥ 6.15.4 kernel fixed
|-
| ThinkBook 14 G7+ IAH || 2025-02-18 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{-}} ||
|-
| ThinkBook 16 G7 ARP || 2025-10-30 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Fingerprint and *IR Camera Work}} ||
IR Camera needs [https://github.com/EmixamPP/linux-enable-ir-emitter linux-enable-ir-emitter]
|}

==== XiaoXin series ====

{{Laptops table header}}
|-
| XiaoXin 14Air 2020 || 2021-02-16 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
|}

==== Yoga series ====

{{Laptops table header}}
| ThinkPad Yoga 14 || 2020-09-14 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Partial: Tablet}} || [https://download.lenovo.com/pccbbs/mobiles_pdf/p40_yoga14_mt20fy_yoga460_hmm_en_sp40j47499_01.pdf Hardware maintenance available].
|-
| [[Lenovo ThinkPad Yoga 260|ThinkPad Yoga 260]] || 2024-02-25 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || || Fingerprint reader, TrackPoint, and power management require tweaks to work.
|-
| [[Lenovo ThinkPad Yoga 370|ThinkPad Yoga 370]] || 2021-04-25 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: WWAN, smart card reader}} ||
|-
| [[Lenovo ThinkBook 14s Yoga ITL|ThinkBook 14s Yoga ITL]] || 2023-10-21 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Fingerprint Reader: not all models work}} ||
|-
| Yoga 530 || 2019-09-29 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || {{Y|SD card (Untested), Fingerprint Reader (Untested), Tablet (Partial)}} || Touchpad needs {{ic|i8042.noloop i8042.nomux i8042.nopnp i8042.reset}} and {{Pkg|xf86-input-synaptics}}.
|-
| Yoga 710 || 2019-10-05 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || ||
|-
| Yoga 720 || 2022-01-06 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|No: Fingerprint Reader}} ||
|-
| [[Lenovo Yoga 730|Yoga 730]] || 2023-09-01 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Experimental: Fingerprint Reader*}} || *See {{AUR|libfprint-vfs009x-git}}
|-
| Yoga S740-15IRH || 2022-01-16 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || Fingerprint Reader (Untested), SD card (No) ||
|-
| [[Lenovo Yoga 9 14ITL5|Yoga 9 14ITL5]] || 2023-09-22 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|No: Fingerprint Reader}} ||
|-
| Yoga 920 || 2020-09-12 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|No: Fingerprint Reader}} ||
|-
| Yoga C930 || 2020-01-17 || {{Yes}} || {{Yes}}* || {{-}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || || *See https://github.com/droserasprout/lenovo-yoga-c930-linux for more information and fixes.
|-
| [[Lenovo Yoga Slim 7 (AMD)|Yoga Slim 7 (AMD)]] || 2022-03-21 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: Fingerprint Reader}} || See https://github.com/jrandiny/yoga-slim7-ubuntu for more information and fixes.
|-
| Yoga Slim 7 Pro (14sARH 2021) || 2022-01-20 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}}* || || *BIOS version G7CN16WW or above needed for S3 sleep to work.
|-
| Yoga Slim 7i Pro (Intel Core i7) || 2021-10-01 || {{Yes}}* || {{G|[[Sound Open Firmware|Yes*]]}} || {{-}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || || *Panel Self Refresh needs {{ic|1=i915.enable_psr=0}} to prevent flickering. Keyboard needs {{ic|i8042.direct}} and {{ic|i8042.dumbkbd}}.
|-
| Yoga Slim 7i Ultra Aura (14IPH11) || 2026-04-24 || {{Yes}} || {{No}} || {{-}} || {{Yes}} || {{Yes}} ||{{Yes}} || {{No}}: Webcam || Keyboard needs: i8042.nopnp i8042.noaux i8042.dumbkbd
|-
| [[Lenovo Yoga Slim 9 (Intel)|Yoga Slim 9 14ITL5]] || 2023-04-29 || {{Yes}} || {{Y|[[Lenovo Yoga Slim 9 (Intel)#Audio|Partial]]}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || || Touchpad requires additional work, keyboard - special kernel parameter, and audio - custom [[Kernel module#Using modprobe|modprobe]] option.
|-
| Yoga C740 || 2021-01-17 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|No: Fingerprint Reader}} ||
|-
| [[Lenovo Yoga Duet 7 13IML05|Yoga Duet 7 13IML05]] || 2022-07-08 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: SD Card}} || Detachable keyboard/trackpad will connect via Bluetooth, but no events are received.
|-
| Yoga 9i 15IMH5|| 2021-09-13 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|No: Fingerprint Reader}} || Issue with bottom speakers. Touchscreen on [[X]] handles fingers poorly, OK with stylus, perfect with Wayland.
|-
| Yoga Slim 7 Carbon 14ACN6 || 2022-03-29 || {{Yes}} || {{Yes}}* || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || || *Speakers have very low volume
|-
| [[Lenovo Yoga 7 Gen 7 (14ARB7)|Yoga 7 Gen 7 (14ARB7)]] || 2025-03-19 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Partial: S3 sleep}} ||
|-
| [[Lenovo Yoga Slim 7 Pro X (14ARH7)|Yoga Slim 7 Pro X (14ARH7)]] || 2023-03-19 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || || Patched {{Pkg|linux}} 6.0 with boot parameters required for suspend & microphone, see dedicated page.
|-
| [[Lenovo Yoga 11e Gen 6|Yoga 11e Gen 6]] || 2023-01-22 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo Yoga 7i Gen 8 (16IRL8)|Yoga 7i Gen 8 (16IRL8)]] || 2024-02-17 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| Yoga 7 Gen 7 (14IAL7) || 2024-08-05 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || No: S3 sleep, Untested: SDCard ||
|-
| [[Lenovo Yoga Slim 7i Aura (15ILL9)|Yoga Slim 7i Aura (15ILL9)]] || 2025-07-01 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Y|Partial: Fan}} || || Problems known after resuming from suspend.
|-
| [[Lenovo Yoga 7 2-in-1 14AHP9|Yoga 7 2-in-1 14AHP9]] || 2025-06-25 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Partial: Fingerprint reader {{ic|1c7a:0583}}}} ||
|-
| [[Lenovo Yoga C940|Yoga C940]] || 2024-12-14 || {{Yes}} || {{Y|Partial}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Partial: Fingerprint readers {{ic|06cb:00be}} {{ic|27c6:55b4}}}} || Thermal control requires extra tweaking.
|-
| [[Lenovo Yoga Pro 7 14AHP9|Yoga Pro 7 14AHP9]] || 2025-01-21 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || || A [[udev]] rule is required for headphone audio with [[PipeWire]].
|-
| [[Lenovo Yoga 2 11|Yoga 2 (11")]] || 2021-04-07 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || || A [[systemd]] unit is required to prevent reboot after shutdown.
|-
| [[Lenovo Yoga Pro 7 14ASP10|Yoga Pro 7 14ASP10]] || 2025-06-09 || {{Yes}} || {{Y|Partial}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Lenovo Yoga Pro 7 14ASP9|Yoga Pro 7 14ASP9]] || 2025-05-15 || {{Yes}} || {{Y|Partial}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| Yoga Pro 7 14IAH10 || 2025-10-02 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 |
Issues with Wifi 7 Intel BE200 card (commonly reported on other forums) when resuming from suspend. The device disappears and a reboot is needed to fix it. This can be resolved by disabling D3cold
<pre>
echo 0 > /sys/bus/pci/devices/0000:01:00.0/d3cold_allowed
</pre>
This can be made persistent across reboots [https://bbs.archlinux.org/viewtopic.php?pid=2176149#p2176149 with a systemd service].
|}

== Troubleshooting ==

=== UEFI boot entries are not persistent ===

On some recent Lenovo ThinkPads (e.g. T16 Gen 2, AMD), custom UEFI boot entries created with {{man|8|efibootmgr}} may disappear after reboot, with the firmware restoring only ''Windows Boot Manager'' and Lenovo entries (''Diagnostics'', ''PXE'', ''Recovery'', etc.).

Disabling the UEFI option ''Restart > OS Optimized Defaults'' prevents this behavior and allows custom boot entries such as [[systemd-boot]] to persist.

=== Thinkpad E440 ===

To resolve the touchpad not working after waking from suspend, create the following systemd unit:

{{hc|/etc/systemd/system/touchpad-after-wake-fix.service|2=
[Unit]
Description=Run command on resume
After=suspend.target

[Service]
User=root
Type=simple
ExecStart=/bin/bash -c "rmmod rmi_smbus && modprobe rmi_smbus"

[Install]
WantedBy=suspend.target
}}

And then [[enable/start]] {{ic|touchpad-after-wake-fix.service}}.

=== ThinkPad E485 ===

Missing IVRS map in ACPI Table, add {{ic|1=amd_iommu=pt ivrs_ioapic[32]=00:14.0}} in [[kernel parameters]].

In order to get X to work correctly, add {{ic|1=iommu=soft}} in [[kernel parameters]] (Linux 4.20 only). On Linux 5.2, add {{ic|1=iommu=pt}} to prevent render artifacts on X.

In order to get microsd (SDHCI) working, {{ic|1=echo 'options sdhci debug_quirks2="0x8000"' > /etc/modprobe.d/sdhci.conf}} and change module load order {{ic|1=MODULES=(sdhci sdhci_pci)}} in {{ic|/etc/mkinitcpio.conf}} (line 7). Do not forget to run {{ic|mkinitcpio -p linux}} afterwards.

If Wi-Fi does not work on RTL8822BE adapter models, create a file {{ic|/etc/modprobe.d/wifi.conf}} and add the following lines:

{{hc|/etc/modprobe.d/wifi.conf|2=
blacklist rtw_pci
blacklist rtwpci}}

Then, install {{AUR|rtw88-dkms-git}} and reboot.

=== ThinkPad E585 ===

To solve all these issues mentioned here easier just install the latest BIOS update from Lenovo support website. Missing IVRS map in ACPI Table, add {{ic|1=amd_iommu=pt ivrs_ioapic[32]=00:14.0}} in [[kernel parameters]]. In order to get X to work correctly, add {{ic|1=iommu=soft}} in [[kernel parameters]] (Linux 4.20 only). In order to get microsd (SDHCI) working, {{ic|1=echo 'options sdhci debug_quirks2="0x8000"' > /etc/modprobe.d/sdhci.conf}} and change module load order {{ic|1=MODULES=(sdhci sdhci_pci)}} in {{ic|/etc/mkinitcpio.conf}} (line 7). Do not forget to run {{ic|mkinitcpio -p linux}} afterwards. Bluetooth does not work until a suspend/resume cycle occurs.

=== ThinkPad E595 ===

Update the BIOS, if missing IVRS map in ACPI Table.

BIOS update can help if Ethernet is not working.

MicroSD does not work out of the box, see [[#ThinkPad E585]] to fix it.

=== ThinkPad E15 Gen 2 ===

Resume from hibernate will not work until {{ic|intel_lpss_pci}} is added to {{ic|MODULES()}} in {{ic|/etc/mkinitcpio.conf}}. See [[Power management/Suspend and hibernate#Suspend/hibernate does not work, or does not work consistently]] for details.

After recovery from suspend, shortly thereafter, system reboots without user interaction. A [https://forums.lenovo.com/t5/Ubuntu/E15-gen-2-reboots-1-min-after-recovery-from-suspend/m-p/5081203 workaround] is available if you are willing to sacrifice suspend-to-ram for suspend-to-idle. The BIOS has two "Sleep State" options, called "Windows" (suspend-to-idle) and "Linux" (suspend-to-ram), which you can find in at Config -> Power -> Sleep State. If you change the setting to "Windows", this will change the state from suspend-to-ram to suspend-to-idle. You can see this if you run {{ic| cat /sys/power/mem_sleep}} before and after the change.

The trackpoint and physical buttons will stop working after resuming from hibernate. Use {{ic|modprobe -r psmouse}} followed by {{ic|modprobe psmouse}} to get the functionailty back

Fingerprint reader is unsupported. Neither {{ic|fprintd}} nor {{ic|libfprintd-tod}} will work.

If the Fn keys do not work, to update the BIOS, download the "Bootable CD" of the [https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-edge-laptops/thinkpad-e15-gen-2-type-20t8-20t9/downloads/driver-list/component?name=BIOS%2FUEFI BIOS Update], and use {{AUR|geteltorito}} to extract the .img from the .iso with {{ic|geteltorito.pl -o bios.img downloaded.iso}}, then use [[USB flash installation medium#Using etcher|etcher]] / {{AUR|mintstick}} / [[dd]] to make a bootable USB. See [https://makandracards.com/operations/39925-lenovo-laptop-bios-update-with-linux] for details.

=== Thinkpad E16 Gen 1 (AMD) ===

* Fingerprint sensor: Requires the proprietary libfprint-2-tod1-goodix {{AUR|libfprint-2-tod1-goodix}} driver.

=== ThinkPad T440p ===

* ClickPad: the whole trackpad clicks, and disabling the trackpad using older versions of synclient makes the trackpoint essentially unusable. This has been resolved in newer versions of {{Pkg|xf86-input-synaptics}}.
** See [https://who-t.blogspot.com.au/2014/03/xorg-synaptics-support-for-lenovo-t440.html] and its previous version, [https://who-t.blogspot.com.au/2013/12/lenovo-t440-touchpad-button.html].
** Install {{AUR|xf86-input-mtrack}} for alternative drivers.
* Audio:
** HDMI audio is the default audio output device. Consult the [[ALSA]] page for details on changing the default.
** As the X100e/Mini10, it is possible to mute the headset and speaker outputs separately to the master. Muting the speaker output improves bass output on the headset port.
** If the system fails to wake from sleep, it can lose sync with the internal audio card and speakers/headphones may fail to work. In this case, put the system to sleep, and wake it again and audio functionality should be restored.
* The fingerprint sensor is a Validity VFS5011, available in [[fprint]].
* thinkpad_acpi:
** To toggle Fn-Lock, press Fn + Esc, this will toggle the LED on the keyboard. While the Fn LED is on all Fn functionalities work as intended out of the box.
** Controlling the 'glowing I' LED is apparently not possible.
** fan control does not seem to work.
* Graphics and Video:
** With the integrated GPU, [[xrandr]] can crash while attaching or detaching displays connected via the dock.
** The built-in miniDisplayPort will sometimes spew I²C issues into the kernel log.
** [[Hardware video acceleration]] is highly recommended as it performs significantly better than CPU decoding of large media files.
** '''The BIOS should not be upgraded past version 1.14, as newer BIOSes cause memory corruption when used with Bumblebee.''' See [https://github.com/Bumblebee-Project/bbswitch/issues/78#issuecomment-42741698 Bumblebee GitHub]
* Connectivity:
** Bluetooth is ''extremely'' fragile. The controller works fine most of the time, but can cause the system to wedge totally on sleep/wake cycles, especially if a connection was active at sleep. Disable the controller using {{ic|bluetoothctl}} before sleeping.

=== ThinkPad X260 ===

[[Wikipedia:DisplayPort#eDP|Panel Self-Refresh]] (PSR) can cause the screen to randomly freeze every few minutes. This can be fixed by [[Intel graphics#Screen flickering|disabling PSR]].

See https://reddit.com/r/archlinux/comments/gu0a8a/ for more details.

=== ThinkPad P14/P15/T14/T15 Gen 2 CPU throttling ===

On some models an issue has been observed, where they operate at a TDP much lower compared to Windows, even when using the performance CPU governor. The result is severe CPU throttling - see issue [https://github.com/erpalma/throttled/issues/265]. The solution is to install {{ic|throttled}} and start/enable the {{ic|throttled.service}} systemd service.

=== IdeaPad Y700 ===

The subwoofer needs https://gist.github.com/BXZ/48cd8173807676a1402cf4bc7928c0c0 to get it working.

=== IdeaPad 3 14IIL05 ===

''Touchpad fixed in recent kernels(or is it systemd, i have lost overview)(1-2 months ago or so i think and the date now is: 19.03.2023) so disregard the below if you have updated your system recently''

Passing pci=nocrs as kernel parameter fixes the touchpad. Unfortunately this also disabled my Wi-Fi (it was seen by iwctl but never presented a station no matter what i did). I see others online also have this problem(various posts on stackexchange etc). I finally managed to fix it by ''also'' passing pci=realloc so the full line is:

pci=nocrs pci=realloc

for getting both Wi-Fi and touchpad working.

Note: I am using refind as boot manager(holy cow so much more straight-forward and less confusing than grub2) and i seem to recall being unable to boot with pci=realloc using grub2. This could just be me dreaming though so it probably bears testing first.

Everything else works, except the brightness keys -- which sometimes work, and sometimes do not. I have not figured out in which instance they work or not yet. I managed a fix which was to bind ctrl+f11 and ctrl+f12 in KDE to be able to set the brightness(up/down) all the time.

=== B50-70 ===

* UEFI:
** to be able to disable Secure Boot (necessary for dual boot, not needed for Linux only), you have to switch from "UEFI first" to "UEFI only" (or something like this) in UEFI setup menu; the Secure Boot option appears then on the Security tab
** after UEFI update having Linux and Windows installed, the Linux [[boot loader]] ceased to be the default one, UEFI started to load Windows by default and it was impossible to select the Linux one in the UEFI boot menu and in the UEFI setup - reinstalling the boot loader helped; having no access to a boot media that supports UEFI, a solution might be also replacing the Windows EFI boot loader file with a Linux one temporarily, in order to be able to boot Linux from HDD
** for the UEFI update, a Windows OS is needed
* Touchpad:
** Synaptics - works after installing Synaptics drivers from repo, possible to change behaviour (like reaction for double tap) according to your wish
* Video:
** in laptops with dual video card (Intel and ATI) - detects both, Intel is active as a default, not checked if it is possible at all to switch between them

==== Operation with a HDD caddy ====

When you install an SSD in the place of the HDD and you want to have your HDD still inside the laptop, it is possible to install it in the place of the optical drive in a special "HDD caddy". The optical drive is of 9 mm height, but a 9,5 mm caddy (ultra slim) fits in the slot. A caddy with a SATA interface is needed. It is difficult to separate the front bezel from the original optical drive (and opening its case does not help, but brings a danger of making a mess in the opening mechanism; the only option is just to pull the bezel using a bit of force, but you risk breaking the latches).

While the HDD installed instead of the optical drive operates flawlessly in Windows, it was not going to work out of the box in Linux, at least in one case. The kernel tries to establish a connection with the disk, but fails to do it ({{ic|SATA link down}} entry in {{ic|/var/log/messages}}). The solution is to force a 1.5 Gbps transfer speed (instead of 6 Gbps) by adding a {{ic|1=libata.force=}} kernel parameter. See [https://docs.kernel.org/admin-guide/kernel-parameters.html] for details.

=== N200 (3000) ===

Sound: You may have to append {{ic|1=options snd_hda_intel model=lenovo}} to {{ic|/etc/modprobe.d/modprobe.conf}} for sound to work.

=== S21e-20 ===

Tested with {{Pkg|broadcom-wl-dkms}} 802.11 wireless driver

There is an issue with tpacpi-bat not reporting the right value for the stop threshold. This seems to be related to a buggy BIOS and can not be fixed application wise.

See https://github.com/teleshoes/tpacpi-bat/issues/44

=== IdeaPad "Pink Sardine" internal microphone not working ===

The driver for the internal microphone for the IdeaPad laptops using the "Pink Sardine" platform is not loaded by default. First of all, identify the PCI audio device:

{{hc|# lspci -knnd ::0480|
35:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor [1022:15e2] (rev 63)
Subsystem: Lenovo ACP/ACP3X/ACP6x Audio Coprocessor [17aa:3888]
Kernel driver in use: '''snd_pci_ps'''
}}

To ensure the kernel module {{ic|snd_pci_ps}} is properly loaded, [[create]]:

{{hc|/etc/modules-load.d/sound.conf|
snd-pci-ps
snd-soc-ps-mach
}}

Then reboot to confirm the microphone is now working.

==== Windows updates ====

It has been observed with consistency that Windows updates are what triggers the laptop's BIOS to enter an inconsistent state that makes it impossible to enter suspend.

An obvious tell is if the power button starts flashing

== See also ==

* [https://www.thinkwiki.org/wiki ThinkWiki]

Powerline

2026-05-11T11:35:23Z

Erus Iluvatar: /* Alternative package */ rm note about issue from 2018, fixed for a while

[[Category:Eye candy]]
[[Category:Development]]
[[ja:Powerline]]
[https://powerline.readthedocs.io/en/master/index.html Powerline] is a statusline plugin for Vim, and provides statuslines and prompts for several other applications, including zsh, bash, fish, tmux, IPython, Awesome, i3 and Qtile.

== Installation ==

[[Install]] {{Pkg|powerline}} and {{Pkg|powerline-fonts}}.

{{Note|Installing {{Pkg|powerline-fonts}} does not provide any of the patched fonts from {{AUR|powerline-fonts-git}}}}

== Usage ==

=== Bash ===

Add the following to your [[bashrc]]:

{{hc|~/.bashrc|2=
powerline-daemon -q
POWERLINE_BASH_CONTINUATION=1
POWERLINE_BASH_SELECT=1
. /usr/share/powerline/bindings/bash/powerline.sh
}}

Close and reopen your terminal and it should be working. If not, check the [https://powerline.readthedocs.io/en/latest/usage/shell-prompts.html#bash-prompt Powerline bash prompt] usage instructions to ensure that it has not changed.

{{Tip|You can also [[source]] it afterwards if you do not want to close and re-open your terminal.}}

=== Zsh ===

Add the following to your [[zshrc]]:

{{hc|~/.zshrc|
powerline-daemon -q
. /usr/share/powerline/bindings/zsh/powerline.zsh
}}

{{Note|If you are using [https://ohmyz.sh oh-my-zsh], you should delete or comment out the {{ic|1=ZSH_THEME=''oh-my-zsh theme''"}} line in your {{ic|~/.zshrc}}. Similarly if you are using {{Pkg|grml-zsh-config}}, do not forget to insert {{ic|prompt off}} before the above addition.}}

=== Fish ===

Add the following to your [[Fish#Configuration|config.fish]]:

{{hc|~/.config/fish/config.fish|
set fish_function_path $fish_function_path "/usr/share/powerline/bindings/fish"
source /usr/share/powerline/bindings/fish/powerline-setup.fish
powerline-setup
}}

This will activate the next time you enter Fish.

=== Tmux ===

Add the following to your [[Tmux#Configuration|tmux.conf]]:

{{hc|~/.config/tmux/tmux.conf|
source /usr/share/powerline/bindings/tmux/powerline.conf
}}

{{note|
* It is sufficient to just add this to the tmux configuration: adding anything to your shell configuration is not necessary.
* Watch out for interfering styles in the tmux configuration (i.e. {{ic|window-status-format}}).
}}

=== Vim ===

Install {{Pkg|vim-powerline}}.

{{Note|If you have more than one version of python installed, add {{ic|1=let g:powerline_pycmd="py3"}} or {{ic|1=let g:powerline_pycmd="py"}} to your {{ic|.vimrc}}.}}

{{Tip|
* By default, the statusline (and therefore Powerline) only appears when there are multiple windows open. To show it all the time, use {{ic|1=:set laststatus=2}}
* This package installs Powerline to {{ic|/usr/share/vim/vimfiles/plugin}}, which vim is configured to check by default, meaning this will install Powerline in vim for all users and may require additional configuration. If this is not intended, consider either using a vim plugin manager, or installing the {{Pkg|powerline}} package and adding {{ic|1=set rtp+=/usr/share/powerline/bindings/vim}} to your {{ic|.vimrc}}.
}}

=== Detailed usage ===

For detailed usage instructions, such as configuring your system to use Powerline with other shells, window manager widgets, etc., please refer to the [https://powerline.readthedocs.io/en/latest/usage.html#usage Usage section] of the [https://powerline.readthedocs.io/en/latest/index.html Powerline documentation].

== Customizing ==

The official [https://powerline.readthedocs.io/en/master/configuration.html#configuration-and-customization Powerline documentation] refers to {{ic|''powerline_root''}}, which for Arch Linux is the following:

/usr/lib/python3.''x''/site-packages/powerline

To customize Powerline, copy a default configuration to {{ic|$XDG_CONFIG_HOME/powerline/...}}. Then edit the file to your liking.

Example to customize Powerline for ''tmux'':

$ mkdir -p ~/.config/powerline/themes/tmux/
$ cp /usr/lib/python3.''x''/site-packages/powerline/config_files/themes/tmux/default.json ~/.config/powerline/themes/tmux/default.json

== Tips and tricks ==

=== Alternative installation ===

==== Using python-pip ====

* [[Install]] {{Pkg|python-pip}}
* Please refer to the [https://powerline.readthedocs.io/en/master/installation.html Powerline installation guide] for additional python-pip instructions

==== Using a vim plugin manager ====

There are many vim plugin managers available which are able to install and update Powerline, assuming you are using a version of vim with Python support or you install {{Pkg|python}}. For example, using {{AUR|vim-plug}}, add the following to your {{ic|.vimrc}} file:

{{hc|~/.vimrc|
call plug#begin(<nowiki>'</nowiki>''path/to/vim/plugins/directory''<nowiki>'</nowiki>)

Plug 'powerline/powerline'

call plug#end()
}}

Substitute {{ic|''path/to/vim/plugins/directory''}} with the actual directory, such as {{ic|~/.vim/plugged}}, and run the vim-plug command {{ic|:PlugInstall}} within vim. This will download Powerline from the [https://github.com/powerline/powerline Powerline GitHub page] to the specified plugin directory and add it to vim.

{{Note|Powerline does not support Neovim yet: see [https://github.com/powerline/powerline/issues/1287 Add support for NeoVim].}}

=== Alternative fonts ===

A reduced set of fonts for the text console are available in {{aur|powerline-console-fonts}}.

=== Alternative package ===

There is currently one known alternative to Powerline — [https://github.com/vim-airline Vim-airline]. It is a part of {{Grp|vim-plugins}} and can be installed separately as {{AUR|vim-airline}}. Optionally, install {{AUR|vim-airline-themes}}.

== Troubleshooting ==

=== Fonts: glyphs missing ===

If you installed {{Pkg|powerline-fonts}} but you notice missing glyphs, make sure your [[locale]] is set. Restart your session to see the changes.

User:Erus Iluvatar/TODO

2026-05-10T14:17:40Z

Erus Iluvatar: /* TODO */ new item

== TODO ==

* s/environmental/environment/ files
* De-duplicate the pages about [[Special:Search/"panel self refresh"]]
* Watch over the abuse filter log for productive edits that got blocked and people gave up instead of providing an edit summary
* Think about adding a section about fixing sections flagged with [[Template:Accuracy]] in [[Help:Procedures]]
* Revamp GRUB configuration examples to only use drop-ins
* Merge all the laptop stuff between individual hardware pages (e.g. [[GPD Pocket 4]]), [[Touchscreen]], [[Calibrating Touchscreen]], [[Tablet PC#Touchscreen and stylus rotation]], possibly [[Graphics tablet]]?
* Find time to revamp the whole flow from the installation guide to a working [[NVIDIA]]/[[NVIDIA Optimus]] system
* Add a tip about KDE's ''kscreen-doctor'' in conjunction with keyboard shortcuts to have a fast way to switch between displays ({{ic|kscreen-doctor output.HDMI-A-1.disable output.HDMI-A-0.enable}} and {{ic|kscreen-doctor output.HDMI-A-1.enable output.HDMI-A-0.disable}})
* Create a [[Template:Not support]] or something to speed up answering to misguided people in the talk pages. Possibly something to the tune of
:{{bc|<nowiki>The Wiki is not a support channel: help is provided in [[Getting involved#Post on the forums|the forum]], the [[Arch IRC channels|IRC channel]], or the [[Getting involved#Join the mailing lists|mailing lists]].</nowiki>}}
* Having encountered a [https://www.reddit.com/r/flatpak/comments/1h0gzbc/custom_fontsconf_for_flatpak_apps/ custom fontconfig issue] with Quassel as a Flatpak on SteamOS, test if [https://github.com/flatpak/flatpak/issues/4571#issuecomment-1715896029 the solution] is needed in Arch, and add it to the appropriate page
* Find pages which would need to use the "Keyboard shortcuts" wording instead of the myriad of variants
* Find which pages would benefit from linking to [[hdajackretask]]
* Add topic to [[Talk:Bug reporting guidelines]] for clearing up what should be reported upstream or not, as the explicit guidelines are not clear nor representing what's actually being done most of the time
* De-duplicate [[Special:Search/?AHCI]] to [[AHCI]]
* Fix [[Install Arch Linux with Fake RAID#MBR Install Example Using mdadm on and Intel FakeRAID]]
* Document [https://bbs.archlinux.org/viewtopic.php?pid=2107330#p2107330 BBS#2107330] at [[Systemd-networkd#systemd-networkd-wait-online]]
* [[Special:PermanentLink/778194#Replace /dev/sdX with /dev/disk/by-id/usb-My_flash_drive]] but for the whole wiki
* [[Special:WhatLinksHere/Kernels]] → [[Kernel]]+s
* [https://wiki.archlinux.org/index.php?search=?reboot This in not Windows, rebooting randomly should not be necessary]
* [https://wiki.archlinux.org/index.php?search=%22+try%22 Do, or do not, there is no "try"]
* [https://wiki.archlinux.org/index.php?search=%22as+of%22 Unnecessary "as of" references]
* [https://wiki.archlinux.org/index.php?search=%22gpasswd+-a%22 pages to convert with a link to user groups]
* Proofread [[User:CodingKoopa/Direct Rendering Infrastructure]], maybe use a [[Template:Text art]] or a table with links inside of it for each subsections to have a visual help of what interacts with what?
* Finish flagging all the laptop pages which have not had a content update in more than 5/10 years with [[Template:Out of date]] - On hold, see [[Talk:Laptop#Is a maintainer responsible for the accuracy of a old content?]]
* Fix [[Dell XPS 15]] (see [[Template:Merge]] at the top of the page)
* Fix [[Dell Latitude 3500#Power buttons]] (See [[Template:Merge]])
* In general, find a way to avoid blind copy/pasting from one laptop page to the other, maybe merging most of the common content on the main laptop pages?
* Start a discussion on moving all the laptop hardware table to a sub-subpage, so that each manufacturer's subpage only contains the generic information
* Investigate if/which pages duplicate [[environment variables]], remove the usage of {{ic|export}} where possible.
* De-duplicate Lenovo (and maybe other manufacturer's) pages, e.g. [[Lenovo IdeaPad Flex 5 14ARE05#Power management options]], [[Lenovo IdeaPad 5 Pro 14ACN6#Power management options]] and find a way to only have the values in the individual pages and most of the content in [[Laptop/Lenovo]].
* See which laptop pages could be shortened by linking to [[Tablet PC#With GNOME 2]].
* Use [[XDG Base Directory]] to update the respective pages and reflect the usage of the XDG variables instead of displaying the default path where applicable.
* Use the terminology from [[Multihead]] to apply it to every page
* Fix all the pages from [[Special:Search/bootloader]] and convert to "boot loader"
* Fix all the pages which suggest using {{ic|noatime}} and convert to {{ic|defaults}}
* Get some self-hosted mail up and running + create a user page to document it
* Create a self-hosted website/blog or whatever & document it too, maybe move the previous email documentation to that?

== Ongoing ==

* [[:Category:Pages or sections flagged with Template:Translateme (Français)]] − Translate
* [[:Category:Pages or sections flagged with Template:Bad translation (Français)]] − Translate
* Periodic check of updates to pages which have a French translation (e.g. [[Arch boot process (Français)]])
* Check other translations that have been flagged for more than 6 months to redirect them if they have not improved - On hold.
* Use [[User:Lahwaacz.bot/Reports/archpkgs]] to fix new reports of broken package links
* Check [[ArchWiki:Statistics#Maintenance statistics]], in particular [[:Category:Sections flagged with Template:Remove]], [[:Category:Pages or sections flagged with Template:Out of date]], [[:Category:Pages or sections flagged with Template:Move]], [[:Category:Pages or sections flagged with Template:Merge]] and maybe [[:Category:Pages flagged with Template:Redirect]]?

Su

2026-05-10T14:16:08Z

Erus Iluvatar: /* Login shell */ s/environmental/environment/ + link to runtime configuration file instead of singling out bash

{{Lowercase title}}
[[Category:Security]]
[[Category:Commands]]
[[es:Su]]
[[fr:Su]]
[[hu:Su]]
[[it:Su]]
[[ja:su]]
[[ru:Su]]
[[zh-hans:Su]]
{{Related articles start}}
{{Related|Users and groups}}
{{Related|sudo}}
{{Related|List of applications/Security#Privilege elevation}}
{{Related articles end}}

The [[Wikipedia:Su (Unix)|su]] [[core utility]] (substitute user) is used to assume the identity of another user on the system, root by default.

See [[PAM]] for ways to configure ''su'''s behavior.

== Installation ==

''su'' is part of the {{Pkg|util-linux}} package.

{{Tip|{{Pkg|sudo-rs}} has {{man|1|su-rs}}, an alternative memory-safe implementation of ''su''.}}

== Usage ==

To assume the login of another user, pass the username that you want to become to ''su'', as in:

$ su ''username''

By default, when running as a regular user, you will be prompted for the password of the user you are attempting to become. When running ''su'' as root, no password is required.

If no username is passed, ''su'' assumes the root user, and the password for which you are prompted will be that of root.

For more information, see {{man|1|su}}.

== Tips and tricks ==

=== Login shell ===

The default behavior of ''su'' is to remain within the current directory and to maintain the environment variables of the original user (rather than switch to those of the new user).

Note the following important contrasting considerations:

* It sometimes can be advantageous for a system administrator to use the shell account of an ordinary user rather than its own. In particular, occasionally the most efficient way to solve a user's problem is to log into that user's account in order to reproduce or debug the problem.
* However, in many situations it is not desirable, or it can even be dangerous, for the root user to be operating from an ordinary user's shell account and with that account's environment variables rather than from its own. While inadvertently using an ordinary user's shell account, root could install a program or make other changes to the system that would not have the same result as if they were made while using the root account. For instance, a program could be installed that could give the ordinary user power to accidentally damage the system or gain unauthorized access to certain data.

Thus, it is advisable that administrative users, as well as any other users that are authorized to use ''su'' (and it is suggested that there be very few, if any) acquire the habit of always running the ''su'' command with the {{ic|-l}}/{{ic|--login}} option. It has two effects:

# Switches from the current directory to the home directory of the new user (e.g., to {{ic|/root}} in the case of the root user) by ''logging in'' as that user.
# Changes the environment variables to those of the new user, as dictated by their shell [[Command-line shell#Configuration files|runtime configuration file]]. That is, the current directory and environment will be changed to what would be expected if the new user had actually logged on to a new session (rather than just taking over an existing session).

Thus, administrators should generally use ''su'' as follows:

$ su -l

An identical result is produced by adding the username root:

$ su -l root

Likewise, the same can be done for any other user (e.g. for a user named archie):

# su -l archie

To log into a passwordless user, first log in as root and then log into the passwordless user account from the root shell:

$ su -l
# runuser -l archie

{{Note|There is no need to use ''su'' when already privileged. ''runuser'' in such cases is a better choice that avoids another layer of [[setuid]] process. For details, refer to {{man|1|su}}.}}

{{Tip|
* You will sometimes encounter ''su'' being used to get a login shell with {{ic|su -}}, rather than {{ic|su -l}}/{{ic|su --login}}. This shorthand is discouraged because the {{ic|-}} option can encounter parsing limitations, see {{man|1|su|DESCRIPTION}}.
* You may wish to add an alias for this: {{bc|alias su{{=}}"su -l"}}
}}

=== su and wheel ===

BSD ''su'' allows only members of the {{ic|wheel}} [[user group]] to assume root's identity by default. This is not the default behavior of GNU ''su'', but this behavior can be mimicked using [[PAM]]. Uncomment the appropriate line in {{ic|/etc/pam.d/su}} and {{ic|/etc/pam.d/su-l}}:

auth required pam_wheel.so use_uid

=== Nologin users ===

You cannot run commands as an other user by simply using {{ic|su ''user'' -c ''command''}} if they are not allowed to login (i.e. they have {{ic|/bin/false}} or {{ic|/usr/bin/nologin}} [[Users and groups#User management|set as their shell]]).

You can work around this by specifying the shell to use:

# su -s /usr/bin/bash ''nologin_user''

Talk:NetworkManager

2026-05-10T08:48:48Z

Erus Iluvatar: /* In relation to NetworkManager/Privacy */ re, close

== Correct/Updated dnsmasq with NetworkManager ==

So I just set this up to enable ad blocking on my laptop regardless of which network I connect to. So far it seems to be working. This config presented on the site dns=none and so forth does not work as desired.
create me:
{{hc|/etc/NetworkManager/dnsmasq.d/dnsmasq.conf|2=
resolv-file=/run/NetworkManager/no-stub-resolv.conf
strict-order
interface=lo
cache-size=1000
conf-file=/etc/NetworkManager/dnsmasq-shared.d/bad_domains.txt #https://github.com/notracking/hosts-blocklists (https://raw.githubusercontent.com/notracking/hosts-blocklists/master/domains.txt)
addn-hosts=/etc/NetworkManager/dnsmasq-shared.d/bad_hostnames.txt #https://github.com/notracking/hosts-blocklists (https://raw.githubusercontent.com/notracking/hosts-blocklists/master/hostnames.txt)
domain-needed
bogus-priv
}}
edit me:
{{hc|/etc/NetworkManager/NetworkManager.conf|2=
# Configuration file for NetworkManager.
# See "man 5 NetworkManager.conf" for details.
[main]
dns=dnsmasq
}}
I'm created by NetworkManager, just FYI of what I contain:
{{hc|/run/NetworkManager/no-stub-resolv.conf |2=
# Generated by NetworkManager
nameserver DHCP_PROVIDED_DNS_1
nameserver DHCP_PROVIDED_DNS_2
nameserver DHCP_PROVIDED_DNS_3
}}

[[User:Glenntanner3|Glenntanner3]] ([[User talk:Glenntanner3|talk]]) 13:54, 1 November 2019 (UTC)!

{{Unsigned|16:06, 31 October 2019 (UTC)|Glenntanner3}}

:That looks overcomplicated. This should work:
{{hc|/etc/NetworkManager/conf.d/dns.conf|2=
[main]
dns=dnsmasq
}}

{{hc|/etc/NetworkManager/dnsmasq.d/dnsmasq.conf|2=
cache-size=1000
conf-file=/etc/NetworkManager/dnsmasq-shared.d/bad_domains.txt
}}

:You don't need to include {{ic|/run/NetworkManager/no-stub-resolv.conf}}, NetworkManager will send the DNS server addresses to dnsmasq over dbus.
: -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 11:08, 1 November 2019 (UTC)

:Explanation for parameters:
I'll try to make this update correct. Didn't know, or expect, that username wouldn't be added and i'm kind of surprised this isn't designed to be indepent messages. Updated what I had before to match your better formatting.

From what I just tested resolv-file=/run/NetworkManager/no-stub-resolv.conf is required, commented it out->restarted NM->ping google->fail; dbus didn't seem to do it.

I also included interface lo to prevent external usage of my laptop being used for DNS.

I used NetworkManager.conf as it already existed, no need to create more that the minimum number of new configuration files.

domain-needed and bogus-priv are recommended for safety.

conf-file and addn-hosts are for ad domain blocking, should have mentioned; those can be excluded but perhaps should be mentioned.

Set this up to work around need for pihole at work or any network i'm connected to. But the documentation I found to be lacking.

[[User:Glenntanner3|Glenntanner3]] ([[User talk:Glenntanner3|talk]]) 13:54, 1 November 2019 (UTC)!

:If the DNS servers are not send over dbus, then something is broken on your end, check {{ic|journalctl -u NetworkManager.service}}. It should contain {{ic|dnsmasq[#]: setting upstream servers from DBus}} and {{ic|dnsmasq[#]: using nameserver ''address''#''port''(via ''interface'')}}.
:I tested with:
{{hc|/etc/NetworkManager/conf.d/dns.conf|2=
[main]
dns=dnsmasq
}}

{{hc|/etc/NetworkManager/dnsmasq.d/dnsmasq.conf|2=
cache-size=1500
conf-file=/etc/NetworkManager/dnsmasq-shared.d/bad_domains.txt
addn-hosts=/etc/NetworkManager/dnsmasq-shared.d/bad_hostnames.txt
domain-needed
bogus-priv
}}

:And everything works correctly for me.
: -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 07:25, 2 November 2019 (UTC)

== Network configuration in related articles ==

Currently, [[Network configuration]] and [[Wireless network configuration]] are listed in the related articles. Some time ago, information wired-connection specifics moved to [[Network configuration/Ethernet]] and wireless-connection specifics moved to [[Network configuration/Wireless]].

Should it list only [[Network configuration]], or all three [[Network configuration]], [[Network configuration/Ethernet]] and [[Network configuration/Wireless]] ?
-- [[User:Josephgbr|Josephgbr]] ([[User talk:Josephgbr|talk]]) 00:04, 12 November 2019 (UTC)

== Warn about that nm-applet installs libappindicator-gtk3 which breaks several applications? ==

Nm-applet installs libappindicator-gtk3 as a dependency. Some applications like blueman-tray as well as all electron-based applications use libappindicator if pressent in system. This breaks functionality in the tray area for all this applications (left mouse click stop to work and other clik/menu related issues).

This is clearly not an issue with nm-applet (maybe even not with libappindicator since nm-applet's tra icon seems to work properly) but nm-applet is one of the few applications that installs libappindicator as their dependency.

Edit: just figured out that if the nm-applet is started with "--indicator", if also has the same tray issues as described above.

[[User:Micw|Micw]] ([[User talk:Micw|talk]]) 09:31, 7 January 2021 (UTC)

== Use dispatcher to automatically toggle wireless depending on LAN cable being plugged in ==

The script, as it currently stands, will cause networking to be disabled if the network cable is disconnected while the computer is off.

If I plug in a LAN cable, the command ''nmcli radio wifi off'' is run.
Thats good, but later I turn off the computer to take it with me, and then I unplug the LAN cable. When I turn it back on, still without LAN cable (intending to use Wi-Fi), my LAN_interface is "unavailable", and will not receive any network events, i.e. "$1" in the script will never be the LAN interface name, and so the command ''nmcli radio wifi on'' will never be run, and my wifi radio remains off.

The command to turn it back on can be run manually, of course, and the LAN cable can be disconnected before power off, which will also turn it on - but the best solution would be to foolproof the script.

I'm not sure what would be the best way to go about it, though, but a bit of testing tells me that after the radio is off and the LAN cable is out, I will receive two network events on boot:
* none (action: hostname)
* <empty> (action: connectivity-change)
I believe the hostname action happens only when the hostname changes, and will normally happen only on boot, so maybe that can be a place to start?
Maybe add to the front of the script something like:
if [ "$1" = "none" ]; then
if [ "$(nmcli -g GENERAL.STATE device show LAN_interface)" = "20 (unavailable)" ]; then
nmcli radio wifi on
fi
fi
Or, maybe better, disconnect it form the hostname action and just run the unavailability test first, no matter what $1 and $2 is? It's not going take much CPU anyway - the network events seems to happen only on actual changes, so not very often.

Edit: I added a failsafe in an else clause to the event check.
It will be run on all events that are not related to the LAN Interface, so it's not elegant, but I don't know how else to pick up the non-event that you have no network.

[[User:Ferdinand|Ferdinand]] ([[User talk:Ferdinand|talk]]) 18:21, 17 August 2021 (UTC)

:I know I'm late to the party but I do agree with the other comment (as exactly this happened to me today). The interface does change when connected to, for example, a docking station with the ethernet cable plugged into it (which has a different interface name than the LAN) and the command no longer recognizes it. I would suggest doing a check based on <code>nmcli -t -f TYPE,STATE device | grep "ethernet:connected"</code> instead. The failsafe check could then look like
:<code>elif [ -n "$(nmcli -t -f TYPE,STATE device | grep "ethernet:connected")" ]; then...</code>
:This whole script shouldn't depend on the interface name (eno1, enp0s etc. which could change), but rather on the type of the connection (ethernet or wifi) which is what we really care about. But that's for another day. [[User:DuckyDuck|DuckyDuck]] ([[User talk:DuckyDuck|talk]]) 00:05, 15 January 2026 (UTC)

:We should also use "nmcli dev | grep "ethernet" | grep -w "connected"" instead of "LAN_Interface" because the name of the interface might change when using different docking stations or tongles. But I am too bad at scripting to make this change.

:[[User:Utini2000|Utini2000]]

== NetworkManager-wait-online ==
Updated the section, to be coherent with [[Systemd-networkd#systemd-networkd-wait-online]]. Most of the section however might be better off in [[NetworkManager#Troubleshooting]]. --[[User:Cvlc|Cvlc]] ([[User talk:Cvlc|talk]]) 23:01, 22 September 2021 (UTC)

== Share internet connection via Bluetooth ==

Currently there is method to share internet connection via WiFi and Ethernet but there is no mentioning on internet sharing via Bluetooth. I guess it would be nice to have one?

[[User:Pickfire|Pickfire]] ([[User talk:Pickfire|talk]]) 01:33, 2 March 2022 (UTC)

== iwd backend doesn't support mac spoofing ==

https://bbs.archlinux.org/viewtopic.php?pid=2063573#p2063573
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1111

This is not mentioned in https://iwd.wiki.kernel.org/networkmanager (or it iwd wiki) and will rather silently fail, so https://wiki.archlinux.org/title/NetworkManager#Configuring_MAC_address_randomization could mention it to prevent unpleasant surprises.

[[User:Seth|Seth]] ([[User talk:Seth|talk]]) 13:44, 23 October 2022 (UTC)

:The same arch forums thread mentions that the iwd needs to be configured at /etc/iwd/main.conf as it doesn't respect NM's configs. This has been my experience as well. So mac spoofing does work but not through NM.
:In my testing I've also come to understand a key quirk of iwd's spoofing modes. The options disabled and once, work intuitively. The man page wording for network mode is "If AddressRandomization is set to network, the MAC address is randomized on each connection to a network. The MAC is generated based on the SSID and permanent address of the adapter. This allows the same MAC to be generated each time connecting to a given SSID while still hiding the permanent address."
:In practice with network, it generates a mac address per UNIQUE network connection or SSID, not every subsequent reconnection to an existing/known network. Hence it is better to use the once mode, and have sudo systemctl restart iwd, for your mac spoofing needs.
:I'll be adding this as a subsection to iwd and link the NM page to it. [[User:TheKnightSky|TheKnightSky]] ([[User talk:TheKnightSky|talk]]) 07:18, 8 May 2026 (UTC)

== Should configuration examples be added? ==

[[ConnMan#Connecting_to_eduroam_(802.1X)|ConnMan has configuration examples]], as well as [[Wpa_supplicant#Configuration|wpa_supplicant.]] Would it be good to add examples of slightly more complex setups to this page as well, [https://github.com/wylermr/NetworkManager-WPA2-Enterprise-Setup/blob/master/skeleton like this one]? There are some external tools that generate configs mentioned at [[Network_configuration/Wireless#eduroam|Network_configuration/Wireless]], but sometimes a quick reference is useful.
{{Unsigned|05:02, 18 January 2023 (UTC)|Dryya}}

== Fixes for automatic VPN dispatcher script ==

First contribution to the wiki after many years of reference! I used the script in [[NetworkManager#Use_dispatcher_to_connect_to_a_VPN_after_a_network_connection_is_established|5.2.5]] but upon network connection my VPN got stuck in an activation<->deactivation loop. After some troubleshooting I found that the script was running multiple times for some reason - I'm not sure if this is specific to my system or a more general bug. I fixed this dispatcher script to check if the VPN connection is not active before connecting to it (line 9):

{{hc|#!/bin/sh|2=
VPN_NAME="your vpn name"
ESSID="your essid"

interface=$1 status=$2
case $status in
up|vpn-down)
if iwgetid | grep -qs ":\"$ESSID\""; then
if !(nmcli connection show --active | grep "$VPN_NAME"); then
nmcli connection up id "$VPN_NAME";
fi
fi
;;
esac
}}

This fixed the issue for me, if anyone else can confirm this behavior on their setup I can incorporate this into the main article.
[[User:Accellarando|Accellarando]] ([[User talk:Accellarando|talk]]) 02:37, 11 June 2024 (UTC)

:Is there any reason to use the iwgetid? The dispatcher script receives the ''CONNECTION_ID'' variable which is the name the connection profile.
:So this is simpler and works fine:
{{hc|/etc/NetworkManager/dispatcher.d/vpn-up|<nowiki>
#!/bin/bash

STATUS=$2

CONN_NAME="connection_name"
VPN_NAME="vpn_name"

if [ "$CONNECTION_ID" = "$CONN_NAME" ]; then
case "$STATUS" in
up)
nmcli connection up "$VPN_NAME"
;;
down)
nmcli connection down "$VPN_NAME"
;;
esac
fi
</nowiki>}}

:(Sorry, couldn't figure out how to format the codeblock correctly in a reply to a comment) [[User:Zwog|Zwog]] ([[User talk:Zwog|talk]]) 07:09, 22 January 2026 (UTC)
::hi Zwog! I wasn't familiar with those NetworkManager variables, that solution does look more elegant to me. I used iwgetid while troubleshooting the issues I came across, so no practical reason for iwgetid over the NM shell variables. I'm no NM expert so I'll defer page editing to someone with more experience with scripting the dispatcher. :) [[User:Accellarando|Accellarando]] ([[User talk:Accellarando|talk]]) 20:26, 22 January 2026 (UTC)

== Remove unnecessary section 8.22 ==

The remove notice at the beginning of this section seems fair. I agree with the removal. Should I do it?

BTW, the reference: https://wiki.archlinux.org/title/NetworkManager#OpenVPN_connections_fail_with_%22secrets:_failed_to_request_VPN_secrets%22_warn [[User:Ismailarilik|Ismailarilik]] ([[User talk:Ismailarilik|talk]]) 13:23, 25 February 2025 (UTC)

:See [[User talk:Andreymal#libnma]] for details — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 13:40, 25 February 2025 (UTC)
::Fair enough. Closing... [[User:Ismailarilik|Ismailarilik]] ([[User talk:Ismailarilik|talk]]) 17:44, 25 February 2025 (UTC)
::Didn't close... I think the notice should be removed then. [[User:Ismailarilik|Ismailarilik]] ([[User talk:Ismailarilik|talk]]) 17:51, 25 February 2025 (UTC)

== <s>In relation to NetworkManager/Privacy</s> ==

[[NetworkManager/Privacy]] does not seem all that fleshed out or necessary to warrant its own subpage. Specifically due to the fact that 3 out of the 4 (sub)sections do nothing but link back to the main [[NetworkManager]] page. I suggest the absorption of the subpage into the main page and instead of merging [[NetworkManager#Configuring MAC address randomization]] into the /Privacy subpage we could merge it to [[MAC address spoofing#NetworkManager]] as it lists all the MAC address specific guides/notes there. [[User:TheKnightSky|TheKnightSky]] ([[User talk:TheKnightSky|talk]]) 12:16, 8 May 2026 (UTC)

:Also, the only section that exists is [[NetworkManager/Privacy#Encrypted network keyphrases]], which should either be merged into/with or have alongside [[NetworkManager#Encrypted Wi-Fi passwords]] as Gnome keyring and mostly everything it talks about is already mentioned there. [[User:TheKnightSky|TheKnightSky]] ([[User talk:TheKnightSky|talk]]) 14:42, 9 May 2026 (UTC)
:I have 0 memory of why I flagged the page other that probably seeing possible duplication: please do what you think is best as far as merging goes :)
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 17:16, 9 May 2026 (UTC)
::Hi, thank you! I've made all the necessary changes. I do not have permissions to remove the page [[NetworkManager/Privacy]] so I've added the remove tag. Please check if the changes are all valid and up to the quality expected as this was pretty big of a change :) [[User:TheKnightSky|TheKnightSky]] ([[User talk:TheKnightSky|talk]]) 04:10, 10 May 2026 (UTC)

:::Thanks! Looks good at a glance, but I'll let anyone chime in if they know more than me and see something I missed. I've turned the page into a redirect, we don't delete pages with a history. Closing :) --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 08:48, 10 May 2026 (UTC)

NetworkManager/Privacy

2026-05-10T08:47:46Z

Erus Iluvatar: Page has a history, we don't delete those: turning it to a redirect

#REDIRECT [[NetworkManager]]

User talk:Erus Iluvatar

2026-05-09T19:34:12Z

Erus Iluvatar: /* Username change */ re, close

== Thank you ==

Thank you for your recent edit on [[Pipewire]]. I am new to ArchWiki and missed the correct formatting. Thanks for fixing it. Cheers! [[User:Darksaber|Darksaber]] ([[User talk:Darksaber|talk]])

: Don't worry, everyone has to start somewhere ;). If you want to read before future contributions, look at [[ArchWiki:Contributing#Resources]]. --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 13:23, 11 March 2022 (UTC)

== Minor edit mark ==

Thank you for your contributions to the wiki. Please mark your edits as [[Wikipedia:Wikipedia:Minor edit|minor]] when necessary, so readers can filter them with "non-minor edits" filter. Thank you. -- [[User:Thmeiov|Thmeiov]] ([[User talk:Thmeiov|talk]]) 12:17, 14 March 2022 (UTC)

: You're right, I should be more careful on this. Thank you for reminding me ! --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 12:30, 14 March 2022 (UTC)

== Thanks for the edits on the Virt-Manager page ==
Thanks for the recent edits you made im pretty new to ArchWiki/MediaWiki and suck formatting so thanks for fixing my bad formating
[[User:ShinobuNarusaka|ShinobuNarusaka]] ([[User talk:ShinobuNarusaka|talk]])

: Hi ! Thank you for contributing a new page on a subject you're comfortable with. Don't worry, practice makes perfect. To double check your content before future contributions, look at [[ArchWiki:Contributing#Resources]]. --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 05:56, 27 March 2022 (UTC)

== $include Readline question ==
Hi, thanks for your work. I've seen that you have added a space in [[Readline#History]]. `man bash` (and some blogs) have no space in "$include /etc/inputrc". Do you have any reference? --[[User:Marzal|Marzal]] ([[User talk:Marzal|talk]]) 22:19, 14 April 2022 (UTC)

: Hi, thanks for pointing out my mistake: I had read the section too quickly and concluded this line was missing a space between the prompt and the command, but this is not the case. I've reverted my edit, sorry for the confusion. --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 03:43, 15 April 2022 (UTC)

== Thanks for improving the edit ==

Thanks for correcting the info, and naming it the 5000 series rather than Ryzen 9 or 5. AMD Ryzen series are even more ambiguous than Intel. AMD Ryzen 5xxx series processor could be Ryzen 5(5600x), Ryzen 9(5950x), or Ryzen 7(5800x). Currently using Ryzen 9 5950x and Ryzen 9 5900x on two of my desktops, on Windows they consume 100 watts less power and my current linux setup, so was looking into that article and was thinking of making the switch from Pop OS to Arch Linux.
{{Unsigned|2022-06-17T04:56:21|Gagan0123}}

: Hi! I saw the ambiguousness of the existing wording when finishing to revert your edit, so instead of having more people tripping on it I tried to make it better :)
: Good luck on your journey ! --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 05:28, 17 June 2022 (UTC)

== Signature is unknown trust ==

Thanks for the edits! They made it easier to find the solution. --[[User:Topcat01|Topcat01]] ([[User talk:Topcat01|talk]])

: Credit where credit is due: [[User:Lahwaacz]] did 99.99% of the work, I've only fixed a capitalization issue. --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 20:26, 29 July 2022 (UTC)

== [[Unified Extensible Firmware Interface/Secure Boot]] ==

Hi Erus Iluvatar, thank you for improving my contributions to the [[Unified Extensible Firmware Interface/Secure Boot]] article! Especially the formatting.

Do you think it is necessary to include an explanation what all the "basic" GRUB modules are doing, in the first code block? I couldn't find any good documentation about all these modules, I only found [https://www.linux.org/threads/understanding-the-various-grub-modules.11142/ this thread on linux.org], which doesn't have all modules however and is already outdated.
The [https://www.gnu.org/software/grub/manual/grub/grub.html official GNU GRUB manual] has '''no documentation at all''' about the modules.

Do you think dividing the list of GRUB modules into these three parts, as done in the official Ubuntu build script, is meaningful, or is it arbitrarily / nonsensical?

Thank you in advance for an answer!

[[User:DasMenschy|DasMenschy]] ([[User talk:DasMenschy|talk]]) 12:30, 28 August 2022 (UTC)

: Hi! First of all, thank ''you'' for creating the content in the first place!
: Regarding the creation of a dedicated section about GRUB modules: if you are motivated to create it, an explanation on GRUB modules would probably be a great fit for the [[GRUB]] page. I'm not sure where exactly it could fit though. Depending on the length, maybe creating [[GRUB/Modules]] could be appropriate? From a quick search in the page right now, nowhere do we explain what a "GRUB module" actually is even though we refer to them roughly 20 times!
: Regarding the split into three parts: as for every classification, it ''is'' arbitrary, but nothing ever is truly neutrally written anyway :P It is logical given the reference material, and IMO feels like a good starting point for a reader trying to set up [[Secure Boot]] without wanting to include every existing modules.
: Thank you again for your contributions.
:--[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 12:43, 28 August 2022 (UTC)

== Template:Archive in user pages ==

Hi

I saw your [[Special:Diff/706716/746378 |edits]] about Archive template in user pages, I put those following the discussion [https://bbs.archlinux.org/viewtopic.php?id=271949 here] because I didn't know of a better way to delete them. What's the proper way to get rid of those then ? Thanks ! (Bonne journée !)

-- [[User:Cvlc|Cvlc]] ([[User talk:Cvlc|talk]]) 15:01, 16 September 2022 (UTC)

: Hi!
: You're completely right to have followed the advice of [[User:Lahwaacz]] on that, I am not allowed to delete pages as a simple maintainer, I'll try to catch an [[Administrator]] to remove those.
: Do you also want the [[User:Cvlc/Storage Layout and Alignment]] and [[User:Cvlc/Sector Size]] redirects deleted too?
: As for a generic way to delete pages, as far as I know it is not possible even for you own pages… I'll see if we can document this properly somewhere.
: --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 15:11, 16 September 2022 (UTC)

== You were right about /var filling up. ==

After testing for 2 weeks straight and installing/uninstalling random packages, it turns out that {{ic|/var}} does in fact fill all the way up non-stop. Maybe that won't happen for a regular user because they wouldn't be spamming packages, but that's IMO enough for me to leave behind my suggestion of removing it off the Wiki, but yet again the decision is up to you whether it should stay on [[Partitioning]] or not. [[User:Cont999|Cont999]] ([[User talk:Cont999|talk]]) 19:50, 20 September 2022 (UTC)

: I'm a little relieved to see that I was not completely missing the mark on the usage of {{ic|/var}} :P
: I'll be waiting for the result of the ongoing discussion at [[Talk:Partitioning#Separate /var]]: IMO keeping the sections as is should be good enough, but maybe a better wording on their actual relevance (or absence thereof) for a common setup can be achieved.
: --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 20:05, 20 September 2022 (UTC)

== Thanks! ==

Thank you for the improvements you made to the pages I created! [[User:Steffo|Steffo]] ([[User talk:Steffo|talk]]) 02:27, 21 September 2022 (UTC)

: And thank '''you''' for creating the pages in the first place: I'm just trying to get the form to compliment the content :)
: --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 05:46, 21 September 2022 (UTC)

== Thanks for the wiki page edits! ==

I intend [[User:Pongo1231/Arch on Steam Deck]] to be documentation of getting the Steam Deck UI fully working in Arch (alongside some opinionated sections like the Btrfs section), neither of which would obviously be a fit for [[Steam Deck]]. Of course I welcome any contributions to the page. :) -- [[User:Pongo1231|Pongo1231]] ([[User talk:Pongo1231|talk]]) 22:14, 26 October 2022 (UTC)

: Thanks ! I was going to link to it in a forum exchange but it was referring to the now inexistant section of the official page, and I saw a few things I would have modified if the page was an official one, so I figured it would be good to update your guide, I'm glad you're OK with it :)
: --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 05:11, 27 October 2022 (UTC)

== Thanks for signing my message ==

Thanks for signing my previously unsigned message, I'm new to this wiki and didn't know about this policy! [[User:Bean box69420|Bean box69420]] ([[User talk:Bean box69420|talk]]) 20:53, 20 December 2022 (UTC)

:No problem, glad I could help :) --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 20:59, 20 December 2022 (UTC)

== ThinkPad Z13 ==

Thanks for the revisions on my initial post. I also had not noticed the laptop guidelines earlier. The accessibility details about BIOS and beep codes, instructions for adding wacom file for the stylus, etc. should get added tonight or tomorrow. Soon, I plan to reformat, completely reset the BIOS, and reinstall Arch, so that should be a good opportunity to notice anything platform-specific that needs extra attention. I'll also bring anything notable in from the Lenovo Forums, as there are active discussions about current bugs and when/where to expect a fix. Take care! —[[User:PennRobotics|PennRobotics]] 15:26, 21 February 2023 (UTC)

:Well, thank '''you''' for adding the content in the first place! I'm just helping formatting things uniformly to help readability as a whole :)
:Don't feel rushed to add things, take all the time you need and don't hesitate to add to the dedicated page on a subject (e.g. [[Tablet PC#Stylus]]) if they are not providing the correct generic information or are unclear. Platform specific stuff should stay on the laptop page though.
:--[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 16:29, 21 February 2023 (UTC)

== Acer Swift 3 ==

Thank you so much for pointing out what I was missing in [[Acer Swift 3 SF314-512]]. I am new to this wiki and did read the guidelines but missed the requirement on some sections. If you don't mind, any further revisions would be appreciated. [[User:0xlogn|0xlogn]] ([[User talk:0xlogn|talk]]) 21:43, 21 February 2023 (UTC)

:I'm happy to have been helpful :)
:Props for reading the guidelines, but there's always things that slip between the cracks: it still happens to me sometimes ^^
:Do you want me to flag what I see as missing on the page or would you prefer that I list them here? (I'm going to sleep right now, will continue our exchange tomorrow)
:--[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 21:51, 21 February 2023 (UTC)

:: Either way is fine for me. Might as well flag it on the page in the case that I don't get back to it. [[User:0xlogn|0xlogn]] ([[User talk:0xlogn|talk]]) 22:13, 21 February 2023 (UTC)

:::[[Special:Diff/768330|Done]] :)
:::Thank you again for your contribution! --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 07:19, 22 February 2023 (UTC)

:::: I can't seem to find the webcam or bluetooth in {{ic|lspci}} or {{ic|lsusb}}. Also, I ''know'' that {{ic|Fn+F8}} is a logout key, but I don't know how to trap the key and determine what it sends. Also (added/adding) the footnotes from the function keys table now. --[[User:0xlogn|0xlogn]] ([[User talk:0xlogn|talk]]) 16:34, 22 February 2023 (UTC)

::::: Thanks again :)
::::: If the [http://linux-hardware.org/?probe=4e92800709 hardware probe] is right, Bluetooth should be visible through USB: {{ic|8087:0033}}, the webcam should appear as a PCI device: {{ic|8086:465d}}.
::::: For the keys, maybe try with a minimal environment like {{Pkg|twm}} to avoid a possible interference from your desktop environment. See [[Help:Laptop page guidelines#Capturing function keys]] if it's being caught by ''systemd-logind'' instead.
::::: --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 17:31, 22 February 2023 (UTC)

:::::: Both of those IDs from the probe were correct. I was expecting a more detailed description than {{ic|Intel Corp.}} (bluetooth) and {{ic|Intel Corporation Device}} (webcam).
:::::: I'll try to do the key in a little bit. Thank you!
:::::: --[[User:0xlogn|0xlogn]] ([[User talk:0xlogn|talk]]) 17:50, 22 February 2023 (UTC)

:::::::Thanks a bunch for double checking, I agree that the name used by ''lspci'' or ''lsusb'' is sometimes weird (e.g. some network card don't appear with their dedicated model number since they are close enough to an older one).
:::::::Take all the time you need, your page is already miles ahead of most "historical" ones (i.e. those created before having the laptop guidelines in place) :) --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 22:02, 22 February 2023 (UTC)

== Thanks! ==

Thanks for reviewing my changes on the [[Lenovo_Yoga_7i]] page, you definitely improved the presentation of the information a lot. Plus you helped me understand the mkinitcpio warnings too. My first time editing Arch Wiki went great!

[[User:Ask|Ask]] ([[User talk:Ask|talk]]) 23:50, 28 February 2023 (UTC)

:Thank ''you'' for taking the time to double check things with me :) --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 06:35, 1 March 2023 (UTC)

== Edits on the Dell G15 5525 Page ==

Hi, thanks for your review of the Dell G15 5525 Page! It is my first contribution to the wiki, and even though I read the guidelines, I have missed some recommendations. I updated the page, please let me know if there is any other info I should add!

{{Unsigned|2023-03-10T22:06:25|Verge36}}

:Hi! Thank ''you'' very much for your contribution. As I had written in my edit summary, the very few things that were missing were minor details: I'm happy to see you came back and fixed everything :)
:I've removed the style flag, but I also adjusted the hardware table, the PCI ID you had added for the microphone seems to be for an audio co-processor that is GPU-related (from the [https://www.kernelconfig.io/config_snd_soc_amd_acp6x kernel config] summary, it's related to "Yellow Carp" which is the codename for the Rembrandt family). I also used a [[Template:Yes]] for audio, since even if an unapproved kernel patch is needed, it's a simple addition to a list of hardware quirks, so nothing that should have unintended effect and the hardware works with the patch, so we can't say the support is "partial" as it's [[Help:Laptop page guidelines#Adding hardware information|for parts that still do not work correctly with applied modifications]].
:Once again, a huge thanks, many hardware pages get much less polish than what you made!
:Edit: You might also want to add an entry into [[Laptop/Dell#G15]] to sum up the hardware support for your model :)
:--[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 22:20, 10 March 2023 (UTC)

== Thanks for tidying up ==

Thanks for sweeping up my half-asleep scrawl! Especially the battery part, I remembered that last and stuffed it in without checking the rest of the wiki first :D.

Much appreciated.

{{Unsigned|2023-03-27T07:21:26|Muesli4brekkies}}

:You're welcome :P
:Thank you for taking the time to create the page, I've flagged a few things that are missing, I'll let you get to them when you find time :)
:--[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 07:30, 27 March 2023 (UTC)

== Sorry for messing up and thank you ==

Hi, sorry for messing up the [[VirtualBox/Install Arch Linux as a guest]] page. I read the page twice and didnt see that the stuff which I added was already on the page, i must have been pretty tired, sorry! And thank you.

[[User:DexyStorm|DexyStorm]] ([[User talk:DexyStorm|talk]]) 10:21, 18 April 2023 (UTC)

:Don't worry, if you did not see it it's probably because if was not at the best place in the logical reading order of the page, thanks for trying to improve the page anyway :)
:--[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 10:59, 18 April 2023 (UTC)

== Thank you for making my first Arch wiki's edit experience so amazing! ==

Thanks for helping fix the format in [[Lenovo ThinkPad X1 Carbon (Gen 11)]]. I want to let you know that your help really makes my first edit in Arch wiki a really amazing experience. I was surprised to see my first page can really help others! I will continue to contribute other pages (and of course, I will pay attention to the format next time).

{{Unsigned|2023-07-29T13:19:00|1arch}}

:I'm glad to see my edits have helped :)
:Don't sweat too much on formatting, it's an easy fruit to pick for anyone, while adding content is less trivial.
:Thank '''you''' for contributing !
:--[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 16:47, 29 July 2023 (UTC)

== Thanks for fixing my first wiki edit! ==
Thanks a lot for fixing [https://wiki.archlinux.org/index.php?title=Emacs&diff=prev&oldid=786364 my first edit] by doing the right thing and extending the relevant section at the Emacs wiki instead!

I'm active on on multiple plumbing-layer linux projects, so I have a baseline to compare contributions experience to... and still, you made my first-hand experience amazing ;)
--[[User:Darwi|Darwi]] ([[User talk:Darwi|talk]]) 20:57, 29 August 2023 (UTC)

:Thank '''you''' for adding the content in the first place! To be honest, at first I was trying to see how to make your solution work on more than GNOME, and stumbled upon the EmacsWiki page with exactly the complementary information ^^
:I'm happy to see the solution I chose of having all the content in an external page was OK for you :)
: --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 06:06, 30 August 2023 (UTC)

== Thanks for warm welcome ==

Hey Erus!

Thanks for your edit over my changes in [[Laptop/Other]]. I wanted to note as many things as possible as I recently ordered this magnificent device, and find that other people can't get it up and running.

--[[User:Michal.dev|Michal.dev]] ([[User talk:Michal.dev|talk]]) 11:43, 24 September 2023 (UTC)

:Thank ''you'' for the content addition :)
:It reminds me that I really should update the table template (proposal at [[Template talk:Laptops table header#Add definitions to headers]]) to have a somewhere that documents what's expected in each column :P
:--[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 12:01, 24 September 2023 (UTC)

:: That would be great, or some kind of an instruction how to put the information properly. Anyway, a reference on which device user has tested Arch would be also usable, I guess. In case there was a regression introduced on one package or another that prevents the device from working etc, user would have source of information. Maybe we should also think about having something like ''device pages'' like people from i.e. Lineage OS have, which version of kernel, from version... till... . IDK, just pondering :) --[[User:Michal.dev|Michal.dev]] ([[User talk:Michal.dev|talk]]) 07:31, 25 September 2023 (UTC)

:::Usually, only the model name and the date of the test is enough for most cases (e.g. saying it works with X processor is unnecessary, as the X+1 processor that was not tested is also likely to work, same for the kernel version which very rarely has regressions).
:::In the rare cases where there ''is'' a regression, we try to have it documented in a central point, e.g. [[Bluetooth#CSR dongle 0a12:0001]].
:::For the dedicated pages, we have [[Help:Laptop page guidelines]] to create them, and I hope we never have to add information on a specific page with "X is supported from kernel version X to Y", as devices in the PC world should rarely become unsupported at the kernel level.
:::--[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 08:42, 25 September 2023 (UTC)

:::: Sure! I've just added my [[Chuwi MiniBook X (2023)]] :). I will update it, as long as I find new issues and workarounds. It's a magnificent device. The one that I wanted - small, but powerful, and supporting (at least paritally :P) Linux / Android. It has it quirks (i.e. factory Windows 11 Installation did not recognize internal Wi-Fi. It can be no-go for "end-user".
:::: However, sometimes old devices fall off the tree, but I believe those must be ancient one...
:::: Anyway, I know that Arch is probably not the best distro for beginner (yet), but I hope my edits will ease it, at least a little :).
:::: BTW. LOOOOOOOVE your nickname ;).
::::--[[User:Michal.dev|Michal.dev]] ([[User talk:Michal.dev|talk]]) 14:09, 25 September 2023 (UTC)

:::::Thanks :) --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 17:07, 25 September 2023 (UTC)

== Thanks for styling my topic on zram ==

Hi Erus,

Thanks, I didn't know the wiki constructs like <nowiki>{{hc| ... | ... }}</nowiki>. Now I learned something new. They are apparently templates. Is there a guide on which templates to use when on the arch wiki?

Also thanks for correcting my stupid typo I missed when proof reading. [[User:Rohoog|Rohoog]] ([[User talk:Rohoog|talk]]) 17:14, 17 October 2023 (UTC)

:Hi :)
:Happy to see my style and wording edit was well received!
:You can take a look at [[Help:Style]] and the various pages in the Help namespace :)
:Always glad to be helpful :D
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 19:11, 17 October 2023 (UTC)

== Thanks for the BIOS flashing edits ==

First of all, thanks for all the style fixes to my section on getting a BIOS exe to work under Linux! I'm still pretty new to the Arch Wiki and I shouldn't have written it like a blog post.

To be honest though, I don't know how portable that advice is, which is why I set it aside as its own vendor-specific subsection. First of all, the innoextract step only applies to installers---ones that were made by a very specific installer set up tool. Second, the TDK extract step only applies to Phoenix TDK formatted firmwares. After all, it's just a firmware dev kit. When I search online for systems that have a Phoenix TDK BIOS, Lenovo is the only vendor that shows up. Third, the UEFI capsule format is also not a universal standard. Moreover, the firmware "device" itself might not be supported through <code>fwupd</code>.

Given how hacky the solution was for my one individual laptop, I don't know if it really deserves its own authoritative section with advice for other BIOS ''.exe''<nowiki/>'s. [[User:Xenia|Xenia]] ([[User talk:Xenia|talk]]) 23:47, 10 November 2023 (UTC)

:Thank you for warning me, I had mistakenly assumed that since fwupdtool could be used with the UEFI capsule, your advice could be generalized to other vendors.
:I'll move it back as a Lenovo-only solution.
:Thanks again for adding the information in the first place!
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 06:54, 11 November 2023 (UTC)

== OVMF examples ==

I thought at first that you were only referring to my use of templating to include the user page, but I realised after subst'ing the page that you also were probably referring to the links to the other user subpages I made. I wanted to share the research and workarounds I made but didn't want them littering up an already unwieldy page. I can have another go at making the section for the Examples page a self-contained thing with as much relevant information as possible, but linking to the subpages I made for each different section feels important for clarity and I'm not sure how best to include that info. I appreciate the correction and the link to the style guide and hope to find a way my information can be included for future users. [[User:Alydev|Alydev]] ([[User talk:Alydev|talk]]) 13:35, 13 February 2024 (UTC)

:Hi!
:Given the sub-pages are mostly configuration files, these would probably be better as a single external link, e.g. on a dedicated repository from your GitHub while the explanations would still fit in [[PCI passthrough via OVMF/Examples]]?
:P.S.: Thanks a bunch for wanting to share with others all the while trying to avoid cluttering an already huge page.
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 15:12, 13 February 2024 (UTC)
::I formatted the section for the Examples page and moved code snippets to GitHub. My primary anxiety in arranging things the way I did originally was avoiding link rot; I see the Arch wiki as a resource of Linux knowledge, and linking to external sites serving as effectively no more than a pastebin would seem to defeat this goal.
::On writing the new section for the Examples page I did consider converting the markdown document from GitHub and putting it at [[PCI_passthrough_via_OVMF/Examples/Alydev]], as then it would be in the wiki namespace and not the user namespace. But that felt a bit cheeky. [[User:Alydev|Alydev]] ([[User talk:Alydev|talk]]) 16:03, 13 February 2024 (UTC)
:::The configuration info could also be generalised and applied to the relevant wiki pages, now I think about it. I'll make a note and see if I can adapt them for that purpose. [[User:Alydev|Alydev]] ([[User talk:Alydev|talk]]) 16:06, 13 February 2024 (UTC)
::::Thanks again for the quick update :)
::::Looking through the page, most other entries seem to already have chosen either a code hosting platform or a pastebin to host the details, with only two of them being dead: if you're afraid GitHub could disappear, you can request an account on https://gitlab.archlinux.org/ and host things there :P
::::Thanks for avoiding the cheeky solution :)
::::If you have the time, updating the relevant pages would be awesome!
::::-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 17:13, 13 February 2024 (UTC)

== Your revert of [[Special:Diff/815771|my change to the system maintenance page]] ==

Hello, while I can understand that your revert may make support easier, I do not agree that this is enough reason to withhold the method I posted completely from Arch users, because I think it expands the range of application in which Arch can be used.

* A part of the Arch userbase is experts that do not request support from the community.
* The forum, a place where a lot of community support happens, already has a sticky post that says in all-caps that the system needs to be up to date. I think the community support places are the right place to publish the conditions needed to get support, instead of the wiki trying to anticipate something about the reader.
* Most people should be able to deduce that if you set your mirror to yesterday, your system is per definition not up to date.

How about adding a note like this to make it obvious?
{{Note|Do not ask for support with this configuration. By setting your mirror to yesterday your system will never be completely up to date, which is a requirement for getting support.}}
[[User:Squarewave|Squarewave]] ([[User talk:Squarewave|talk]]) 06:37, 3 September 2024 (UTC)

:Experts that do not request support can already put two and two together when reading [[Arch Linux Archive#How to restore all packages to a specific date]]. I'm also using [[User:Erus Iluvatar/Install#/etc/pacman.d/mirrorlist|something similar]] on my end, but having this hack or anything close to it documented in [[System maintenance]] would imply it has some official status, which it has not. As [[Arch Linux Archive]] explains, the archive is intended for troubleshooting, not daily use.
:As a side note, the snapshots for the archive are made without checking if the official mirror is in a coherent state or not: in some rare cases, they happen just as a rebuild is being uploaded and can be missing packages (possibly all of them, from memory the [https://archive.archlinux.org/repos/2022/02/01/core/ 2022-02-01 snapshot] is empty).
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 07:34, 3 September 2024 (UTC)
::Ok, thanks for the explanation.
::[[User:Squarewave|Squarewave]] ([[User talk:Squarewave|talk]]) 14:49, 3 September 2024 (UTC)

== I messed up, thanks for fixing ==

I accidentally edited the page for the XPS 9315 instead of XPS 9340... sorry about that. I see that you're cleaning up after me, thank you :3 [[User:AdlaiN|AdlaiN]] ([[User talk:AdlaiN|talk]]) 15:39, 23 February 2025 (UTC)

:Mistakes happen, happy to see my job is appreciated :P [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 16:52, 23 February 2025 (UTC)

== Could you look at this comment? ==

Hey Erus. Could you look at my comment there: https://wiki.archlinux.org/title/Talk:AWK#c-Ismailarilik-20250316093200-Lahwaacz-20250315211100

It is about my latest changes and I am willing to change myself WRT your comments. That comment might not be the place for it but I didn't wanna break the context. [[User:Ismailarilik|Ismailarilik]] ([[User talk:Ismailarilik|talk]]) 09:37, 16 March 2025 (UTC)

:Your rationale sounds fine to me, don't worry about being too disruptive, if needed we'd have no issue raising it in your talk page :)
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 13:13, 16 March 2025 (UTC)

== Explicit Anchor on PrusaSlicer page ==

Note that by undoing my explicit anchor you are breaking a code feature we are working on: https://gitlab.archlinux.org/archlinux/packaging/packages/prusa-slicer/-/merge_requests/4

I understand that section headers already provide implicit anchors but we really need one that does persist any reformatting and changing section titles. And you stated this page requires substantial changes, thus we need to rely on a persistent anchor. Should you know a better way to achieve this I am open for a suggestion. [[User:Schiele|Schiele]] ([[User talk:Schiele|talk]]) 19:08, 30 April 2025 (UTC)

:There are no persistent anchors. If something in the wiki gets changed then references to it will need to be updated. In the worst case, you'll simply land on the top of the page and will need to look through the whole page for the relevant information. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 05:02, 1 May 2025 (UTC)
::Well, technically there are persistent anchors the way I did them. And I didn't invent this approach but took it from the official MediaWiki help page https://www.mediawiki.org/wiki/Help:Links. So if you are saying we cannot use this feature this is not a technical limitation but a policy limitation. Given that I experienced the Arch community to be a very technical community I would at least like to understand the rationale behind this policy since it is technically unpractical to make new package releases each time we want to improve the Wiki page. And while it is true that worst case the user will end up at the top of the page. But this creates unnecessarily bad user experience. Wouldn't we have a better option that would be acceptable but given that we technically have a better option but just disallow it by policy it would be useful to provide the rationale for making the user experience worse here.
::Since I am definitely not a Wiki expert I was asking for better alternatives that I simply might not be aware of. But just rejecting the solution I found without providing neither a rationale nor an alternative feels a bit disturbing to be honest. [[User:Schiele|Schiele]] ([[User talk:Schiele|talk]]) 06:36, 1 May 2025 (UTC)
:::We don't use a good chunk of mediawiki features, persistent anchors is one of them. Would having a note at the top of the page highlighting the proper bug reporting etiquette be an acceptable solution? I can't find an other example quickly, but it's probably not the only software where upstream requires testing with their packaging before accepting a bug report. [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 06:45, 1 May 2025 (UTC)
::::So the background on the feature was that there is a menu item in the upstream software to report issues with the software. Originally this points to the bug reporting system of the vendor (Prusa). Their team however gets frustrated when people report bugs not coming from their official binary. Since in Arch we build our own binary this created tensions between the Arch maintainers and the Prusa development team since they feel that we redirect our users to their team even for issues that we might have produced by our way of packaging. So it is not purely about etiquette but to give our users the best possible way to report their bugs to the correct audience. In the end we want to spend our effort in maintaining good software packages and not in fighting a war with the software vendor's development team.
::::I fear if we make it only slightly harder for the user to find the correct information there are chances that they simply don't read the information at all. If we really can't use persistent anchors would then maybe a sub page be the right approach or is this another feature we don't use by policy?
::::Getting back to the policy question: I understand that we might want to have policies to make the overall quality of the Wiki better. The part that I don't understand is why there are policies (like not using persistent anchors) where apparently nobody can't provide the rationale behind. I personally still fail to see how not using them improves the overall quality of the Wiki? Being a solution-oriented nature this is something I have difficulties to understand: Why do we impose restrictions on us, when the restriction does not provide any benefit we can reason about but actually makes the overall user experience worse? I mean we are very proud about the overall quality of the ArchWiki, so why are we preventing a usability improvement here without having a reason? [[User:Schiele|Schiele]] ([[User talk:Schiele|talk]]) 07:06, 1 May 2025 (UTC)
:::::The rationale for not using manual anchors is because we don't need them. Broken section links get fixed after a bot flags them.
:::::Why don't you simply use the Arch package issue tracker URL instead? That's where people are expected to report issues with the package.
::::: -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 07:15, 1 May 2025 (UTC)
::::::It seems you have a very Wiki-centristic view. For sure you would detect broken links coming from _within_ the Wiki but you would never detect broken links coming from outside, which is exactly what persistent links are useful for. I don't see why you are not considering links from outside the Wiki when you say that we don't need this feature? I consider the Wiki a value for the Arch community and a lot of pages are even so good that they provide value even to users of other distributions. I think we shouldn't consider the Wiki just as a value for it's own sake since in my opinion we drastically undervalue it that way.
::::::I thought about redirecting everything to our own tracking system but then we would receive _all_ the reports, including them about bugs that users could reproduce in the upstream software unrelated to our packaging and therefore could be rightfully reported to the upstream vendor, offloading the package maintainers. That's why I thought documenting the approach to verify a problem with the upstream binary and reporting to the right audience is a good way forward. That's how I described the approach in the page. [[User:Schiele|Schiele]] ([[User talk:Schiele|talk]]) 07:26, 1 May 2025 (UTC)
:::::::One additional idea that came to my mind that might solve this problem in a different way: How about creating a special entry page like PrusaSlicer/BugReporting or something like this, that just redirects to the corresponding section of the main page automatically. While that seems unnecessarily complicated to me it at least provides good user experience without violating your policy and a broken link in the redirect you could then detect with the bot.
:::::::Is that a solution you would prefer? [[User:Schiele|Schiele]] ([[User talk:Schiele|talk]]) 07:35, 1 May 2025 (UTC)
:::::::Some packages already contain links to the wiki. If they get outdated, someone eventually fixes it. This really isn't as big of an issue as you're making it out to be.
:::::::We're not going to create special anchors or subpages just for an article about one single package.
:::::::This is not the first package with an upstream that's hostile to distro packaging. Though another one I know didn't have a wiki article.
::::::: -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 07:46, 1 May 2025 (UTC)
::::::::Ok, got it. Could you at least check whether my current section title for the issue reporting section is good according to how you generally want to have it named? I want to prevent that right after establishing the link I have to change it again. [[User:Schiele|Schiele]] ([[User talk:Schiele|talk]]) 08:19, 1 May 2025 (UTC)
:::::::::It should use sentence case. See [[Help:Style#Section headings]]. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 16:03, 1 May 2025 (UTC)

== Thanks ==

Thanks for the help on the GPD MicroPC 2 page. I'm utter trash at wiki formatting, and working on the page for (obviously) informational sake since early backers only got them on Friday and want to help people can get Linux working great on it. Certainly appreciate it [[User:MoistGoat|MoistGoat]] ([[User talk:MoistGoat|talk]]) 03:54, 3 September 2025 (UTC)

:Honestly for someone new to MediaWiki formatting, it's far from "utter trash" :D
:Keep up the good work, style and such I can fix, while the content can only be written by someone who owns the hardware :)
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 06:55, 3 September 2025 (UTC)

== Thanks ==

Hey,

Thanks for the [https://wiki.archlinux.org/index.php?title=Discord&diff=0&oldid=858436 corrections] on the discord page, I'm still pretty new with the wiki so yeah, thanks! [[User:Noxie|Noxie]] ([[User talk:Noxie|talk]]) 11:04, 22 December 2025 (UTC)

:And thank ''you'' for coming back and improving your solution!
:Always happy to see my work appreciated :)
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 11:21, 22 December 2025 (UTC)

== Thank you and happy New Year! ==

As a freshman and a non-native English speaker. Thank you for correcting on my last 2 edits, the first "GPGME error: No data:" made me realize I haven't find the right article until your mention, causing repetition (Should I delete my edits directly?), while the second "Kernel panic example: missing initramfs" made me realize I messed things up (Though this is the first time I saw a blue screen on Linux and learned a lot to solve the issuse without reinstall the whole system). Honestly, I learned a lot during my reading and writing on Arch, I will keep learning and make Arch Linux be part of my life.

Happy New Year!

[[User:Yuantianbao|Yuantianbao]] ([[User talk:Yuantianbao|talk]]) 01:01, 30 December 2025 (UTC)

:I won't take credit for @[[User:Lahwaacz|Lahwaacz]]: he's the one who flagged your first addition for merging to the existing section :) I don't think it deserves deletion, the page you had picked is far from illogical, we'll just keep a single version of the solution in one of the pages and link there from the other to help discoverability.
::
:No worries about the second change I reverted: the general idea of fixing an issue and sharing the solution to everyone is laudable, though in this specific instance it seemed excessive to me, as the issue should be apparent before rebooting ([[mkinitcpio]] will print error messages that should then make it trivial to troubleshoot root cause).
::
:I too wish you a happy new year and plenty more on Arch ;)
::
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 08:18, 30 December 2025 (UTC)

== Thank you! <3 ==

Thank you so much for the excellent adjustments in [[Lm sensors#MSI MAG B650/Z890 TOMAHAWK WIFI (MS-7D75/MS-7E32) /MAG B550 MORTAR WIFI (MS-7C94)]].

KISS <3 [[User:Damachine|Damachine]] ([[User talk:Damachine|talk]]) 19:11, 11 February 2026 (UTC)

:I'm happy they were well received! A thank in return for having added the content, I mostly make sure the form helps it :)
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 19:37, 11 February 2026 (UTC)

== Question regarding recent edits to Plasma Login Manager ==

Hi Erus,

Thanks for your recent formatting cleanups on the Plasma Login Manager page. I'm trying to make sure I fully understand the wiki standards for future contributions (that was my very first one), and I was hoping you could clarify a couple of the guidelines you referenced in your edit summary.

First, regarding the placement: you mentioned that new entries go at the bottom. I combed through <code>Help:Style</code> to read up on this, but I couldn't seem to find that specific rule anywhere. My thought process for placing the "Custom wallpaper plugin" section higher up was simply logical flow: changing the background is typically the very first users do with their login screen, whereas features like auto-login seem quite a bit more niche. Are sections strictly ordered chronologically by when they were added, or is there a specific guideline for prioritizing core system mechanics over aesthetic configuration?

Secondly, regarding the formatting: you noted that a numbered list wasn't needed for this short set of steps. That's good to know! Just so I can get it right in the future, is there a general threshold in the style guide for when to use ordered lists versus standard prose?

Thanks for taking the time to clarify! [[User:Prod. EGO|Prod. EGO]] ([[User talk:Prod. EGO|talk]]) 17:15, 9 March 2026 (UTC)

:Hi :) First of all a big thank you for your first contribution as our Wiki would not be so well furnished nor well regarded if it only relied on a few regulars like me :P
::
:I must admit I was mostly working from memory on the ordering, and re-reading the section it's better in this case to go with the logical order, please do a manual/partial revert to restore the placement.
:Where chronological order is more customary (but as you point out, undocumented) is for subsections in "Troubleshooting" as it helps ensure the same issue does not get added multiple times or with multiple solutions. Even for that, some pages with numerous troubleshooting sections end up being sorted by topic.
::
:Regarding the usage of list, I try to avoid any of them whenever possible (though to be completely transparent, in this case what reminded me to avoid it was encountering [[Template:hc#Known issue]]). In particular, numbered lists should be reserved for steps that cannot be ordered differently (e.g. [[Installation guide#Boot the live environment]]: can't get to the boot loader menu until you've selected the boot device).
:My personal threshold is around five steps '''and''' that the list helps readability: i.e. cutting a five sentence paragraph into five short steps does not "feel" right, but [[Toshiba Satellite L300#BIOS upgrade]] is probably more readable than a blob of text.
::
:I should have noted in my summary that I was being "opinionated" in my edit (I try to extend the advice from [[Help:Style#Language register]] to the general layout of the sections: I often ask myslef how I would expect a printed book on the topic to look to decide on formatting), don't hesitate reach out to anyone if you're unsure when a followup change they made is a fix to strictly abide by the guidelines or if it's more a case of trying to get the text flow in line with their personal preferences :D
::
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 20:01, 9 March 2026 (UTC)
::Hi Erus,
::Thanks for the warm welcome and the detailed explanation!
::I went ahead and did a manual revert to restore the placement of the "Custom wallpaper plugin" section so it flows logically again. I also made sure not to reintroduce the ordered list, as your reasoning for keeping it as standard prose makes perfect sense for such a short set of steps.
::I really appreciate the extra context on how troubleshooting sections are typically ordered and your personal threshold for using lists. It helps a lot to understand the thought process behind the wiki's formatting choices, especially given I am brand new to making contributions. I'll definitely be sure to reach out if I run into any confusing edits in the future!
::Thanks again for your help and guidance. 🙂 [[User:Prod. EGO|Prod. EGO]] ([[User talk:Prod. EGO|talk]]) 20:22, 9 March 2026 (UTC)

== <s>Might need additional fix</s> ==

https://wiki.archlinux.org/index.php?title=Plasma_Login_Manager&diff=prev&oldid=870441

changing `$ sudo` to `#` changes the behavior of `~` as well `$USER`.

The former copies /home/exampleuser/.face.icon to /var/lib/AccountsService/icons/exampleuser

The latter copies /root/.face.icon to /var/lib/AccountsService/icons/root [[User:Bitwaba|Bitwaba]] ([[User talk:Bitwaba|talk]]) 10:16, 6 April 2026 (UTC)

:Thanks for the heads up, I've replaced both with a pseudo-variable in [[Special:Diff/870666]], closing :) --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 12:01, 6 April 2026 (UTC)

== <s>Regarding NetworkManager/Privacy Merge status</s> ==

Hi! I am reaching out regarding your status tag added on 23 March 2024 to merge [[NetworkManager#Configuring MAC address randomization]] into [[NetworkManager/Privacy]].

I've created a talk page discussion at [[Talk:NetworkManager#In relation to NetworkManager/Privacy]] with my stance on this. Also I've created a talk page discussion at [[Help talk:Template#Have editors create the talk page discussions for Status templates: Merge and Move]]. I would like for you to review these both and share your thoughts on the same. Thanks! [[User:TheKnightSky|TheKnightSky]] ([[User talk:TheKnightSky|talk]]) 12:49, 8 May 2026 (UTC)

:Hi, I'll look into both tomorrow :) [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 18:24, 8 May 2026 (UTC)
::Sounds good! Take your time! [[User:TheKnightSky|TheKnightSky]] ([[User talk:TheKnightSky|talk]]) 05:14, 9 May 2026 (UTC)

:::Replied in both, thank '''you''' for working on making our pages better. Closing :) --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 17:17, 9 May 2026 (UTC)

== <s>Username change</s> ==

I want to change my username to "syrupderg". I could not find an option to change it from user settings. [[User:Birbkeks|Birbkeks]] ([[User talk:Birbkeks|talk]]) 17:43, 9 May 2026 (UTC)

:The user "Birbkeks" has been renamed to "Syrupderg". Closing :) --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 19:34, 9 May 2026 (UTC)

User:Syrupderg

2026-05-09T19:33:51Z

Erus Iluvatar: Erus Iluvatar moved page User:Birbkeks to User:Syrupderg without leaving a redirect: Automatically moved page while renaming the user "Birbkeks" to "Syrupderg"

kuş.

Localization/Arabic

2026-05-09T17:21:19Z

Erus Iluvatar: /* Fonts */ Fix qahiri package

[[Category:Localization]]
[[ar:Localization (العربية)/Arabic]]
This article describes how to set up Arabic language environment.

== Applications ==

* [[Locale]] article explains how to set up system or user locale.
* [[Bidirectional text]] article lists Bidi support status in applications.
* [[Xorg/Keyboard configuration#Frequently used XKB options|Keyboard layout]]: set it by {{ic|setxkbmap ara,us}}. Check the article for more info.
* [https://github.com/linuxscout/ayaspell Ayaspell] offers spellchecking extensions. Can be installed system-wide by {{AUR|hunspell-ar}}.
* [[Aspell]]: install {{AUR|aspell-ar}}
* [[Dict]]: For Arabic dictionaries install {{AUR|dict-freedict-eng-ara}}, {{AUR|dict-freedict-ara-eng}}.
* [[Islamic tools]]: for Hijri date conversion.
* [[LibreOffice]]: set up [[LibreOffice#Bidirectional support|Bidi support]]. If you are not using a system-wide Arabic dictionary, Ayaspell extension can be installed from ''Tools > Language > More Dictionaries Online > Arabic''. For language pack, install {{Pkg|libreoffice-still-ar}} for the stable branch and {{Pkg|libreoffice-fresh-ar}} for Libreoffice fresh.
* {{pkg|tesseract}}: for OCR detection, the default data package {{Pkg|tesseract-data-ara}} is mostly inaccurate. Try {{AUR|tesseract-data-best-ara}} see [https://github.com/tesseract-ocr/tesseract/issues/2047].
* [[Thunderbird]]: install {{Pkg|thunderbird-i18n-ar}} for language pack.
* [[Firefox]]: install {{Pkg|firefox-i18n-ar}} for language pack.
* [[dwm]]: see [[Dwm#Arabic Letter-shaping]]

=== Shell and Terminal ===

* [[st]]: see [[St#Arabic shaping support]]
* [[mlterm]]: see [[Mlterm#Render Arabic script in Xft]] and [[Mlterm#Arabic script rendering when using fixed width fonts]]
* [[bash]]: enables by default "combining characters" ([https://unicode.org/L2/L2014/14109-inline-chars.pdf 1]) feature, which merges diacritics with previous character.
* [[zsh]]: to properly display diacritics add {{ic|setopt COMBINING_CHARS}} to your {{ic|.zshrc}}.

=== Vim ===

* See [[Vim#Bidirectional support]] for setting up Bidi support.
* Since Vim does not map Arabic characters given by input method, motion commands do not work. A possible workaround is to set keymap within Vim without changing X11 keymap. This can be done {{ic|set keymap{{=}}arabic}}, then switching between layouts via {{ic|Ctrl-^}}, or by manually set langmap in {{ic|vimrc}}:
set langmap=ضصثقفغعهخحجد;qwertyuiop[],شسيبل;asdfg,اتنمكط;hjkl\;',ئءؤرلا;zxcvb,ىةوزظ;nm،./,لآB,آN,'M,؟?,ِA,ٍS,لأG,أH,ـJ,،K,ًW,ُE,ٌR,لإT,إY,÷I,×O,؛P

== Fonts ==

Check [[Font configuration/Examples#Arabic]] for setting up font configuration. Persian fonts like {{AUR|vazirmatn-fonts}} also include support for Arabic letters. A list of Persian fonts can be checked from [[Fonts#Persian]].

Multi-script (extended Arabic script) fonts:

* {{Pkg|noto-fonts}} - Google Noto fonts includes ''Noto Kufi Arabic'', ''Noto Sans Arabic'', and ''Noto Kufi Arabic''. Use {{AUR|noto-fonts-ar}} for installing these only.
* {{Pkg|ttf-ibm-plex}}
* {{AUR|ttf-sil-harmattan}}
* {{Pkg|ttf-dejavu}} - Includes the monospace ''DejaVu Sans Mono''' font.
* {{AUR|ttf-arabeyes-fonts}} — Collection of free Arabic fonts that includes:
** [https://fonts.qurancomplex.gov.sa/ KACST fonts]
** [[Wikipedia:Thuluth|Thuluth script font]]
** Thabit: monospace font
** Decorative: AlArabiya, AlBattar, AlHor, and others.

Sans-Serif:

* {{AUR|ttf-markazi-text-variable}}
* {{AUR|ttf-rubik}}
* {{AUR|ttf-tajawal}}
* {{AUR|ttf-ubuntu-arabic}}

Monospace:

* {{Pkg|ttf-cascadia-code}} - A monospaced font by Microsoft that includes programming ligatures.
* {{AUR|vazir-code-fonts}} - Persian font with good monospace support for Arabic.
* {{AUR|otf-kawkab-mono}}
* {{AUR|ttf-amiri-typewriter}} - Typewriter Naskh font based on Amiri

Bitmap:

* [https://sourceforge.net/projects/arabeyes/files/Fonts/ae_fonts/ Arabeyes bitmap font]

[[Wikipedia:Naskh_(script)|Naskh]] (~Serif):

* {{Pkg|ttf-scheherazade-new}} — Unicode Arabic font from SIL (Alternative for Traditional Arabic font)
* {{AUR|ttf-amiri}} — A classical Arabic typeface in Naskh style pioneered by Amiria Press. Its Latin characters are based on Crimson ({{Pkg|otf-crimson}}) [https://fontsinuse.com/typefaces/82634/amiri] [https://github.com/skosch/Crimson]
* {{AUR|ttf-qurancomplex-fonts}} — Fonts by King Fahd Glorious Quran Printing Complex in al-Madinah al-Munawwarah
* {{AUR|ttf-sil-lateef}} — Unicode Arabic font from [[wikipedia:SIL_International|SIL]]

[[Wikipedia:Ruq%27ah_script|Ruq'ah]], [[Wikipedia:Kufic|Kufic]] (~Sans-Serif):

* {{AUR|ttf-aref-ruqaa}} - Ruq'ah typeface.
* {{AUR|ttf-cairo}}
* {{AUR|ttf-mada-variable}}
* {{AUR|ttf-raqq}} - A manuscript Kufic typeface.
* {{AUR|ttf-reem-kufi}}
* {{AUR|ttf-qahiri}}

== Kashida justification ==
Kashida justification could be applied either to single letters or in-between letters. For more information, see [https://asibahi.github.io/thoughts/practical-arabic-justification/].

* [[LibreOffice]]: [https://bugs.documentfoundation.org/show_bug.cgi?id=164522 single-letter Kashida not supported]. In-between-letter Kashida is supported by applying paragraph justification.
* [[LaTeX]]: [https://github.com/latex3/babel/issues/317 single-letter Kashida not supported]. In-between-letter Kashida can be applied using {{ic|justification{{=}}kashida}} option in Babel package. The following is a sample preamble:

\usepackage[
english,
bidi=basic,
]{babel}
\babelprovide[
import, main,
justification = kashida,
transforms = kashida.plain
]{arabic}
\babelfont[arabic]{rm}{Scheherazade New}

* typst: [https://github.com/typst/typst/issues/195 Unsupported]

== Tips and tricks ==

* Disable URL encoding for links containing Arabic characters. See [[Character encoding#URL encoding]].

== Troubleshooting ==

Common issues may be solved by checking [[Locale#Troubleshooting]] and [[Character encoding#Troubleshooting]] first. For problems related to letter-shaping or text direction, check [[Bidi]].

=== XKB Lam Alif problem ===

[[X keyboard layout]] sends [[Wikipedia:Arabic_alphabet#Ligatures|Arabic ligature]] glyphs as a single glyph. For example, Laa+Alif ligature "لا" (U+0644, U+0627) is sent as "ﻻ" (U+FEFB), and similarly for (ﻷ، ﻵ، ﻹ). This is due to a [https://www.freedesktop.org/wiki/Software/XKeyboardConfig/XKB2Dreams known limitation] in xkb which does not allow mapping a key to more than one character. To solve this problem, run a supported input method. The input method workaround takes advantage of [[Wikipedia:Compose_key|Compose Sequences]]. For a technical reading on this, check [https://avidseeker.github.io/lam-alif/]. These are confirmed to work:

* [[IBus]]: supported since [https://github.com/ibus/ibus/releases/tag/1.5.28 v1.5.28].
* {{Pkg|ibus-typing-booster}}: supported since [https://github.com/mike-fabian/ibus-typing-booster/issues/379 2.19.0]

For a more lightweight option, you can use [[Xim]]. Add the following to your [[environment variables]]:

XIM=none
XIM_PROGRAM=/bin/true
XIM_ARGS=
GTK_IM_MODULE=xim
QT_IM_MODULE=xim
SHORT_DESC="X compose table"

Alternatively, you can use [https://salsa.debian.org/input-method-team/im-config/-/blob/devel/im-config?ref_type=heads IM config wrapper script]: {{ic|im-config -n xim}}.

Since QT-based programs do not have this issue, it is enough to add {{ic|export GTK_IM_MODULE{{=}}xim}} to {{ic|~/.xsessionrc}} or {{ic|~/.xprofile}}. The issue is also fixed for [https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/6358 GTK4].

{{Tip|If input method is used, then XCompose table offers additional Arabic letters like: گ، ڤ، چ، پ, quotes «», as well as [[Wikipedia:Zero-width non-joiner]], by pressing the {{ic|AltGr}} key. The default compose table is located in {{ic|/usr/share/X11/xkb/symbols/ara}}.}}

=== Fix Arabic legibility when using Noto Fonts ===

If Arabic characters are rendered in an unexpected font (e.g: Nastaliq, Urdu font, etc.), see [[Font configuration/Examples#Excluding Arabic script from other languages]].

== See also ==

* [[Bidirectional text]]
* [[Islamic tools]]
* [https://arabeyes.org ArabEyes Project]

List of applications/Internet

2026-05-09T17:19:42Z

Erus Iluvatar: /* Firefox spin-offs */ Fix broken midori package

[[Category:Internet applications]]
[[Category:Lists of software]]
[[es:List of applications (Español)/Internet]]
[[hu:List of applications (Magyar)/Internet]]
[[ja:アプリケーション一覧/インターネット]]
[[pl:List of applications (Polski)/Internet]]
[[zh-hans:List of applications/Internet]]
{{List of applications navigation}}

== Network connection ==

=== Network managers ===

See [[Network configuration#Network managers]].

=== VPN clients ===

* {{App|GlobalProtect-openconnect|A GlobalProtect VPN client (GUI) for Linux, based on OpenConnect and built with Qt5, supports SAML auth mode.|https://github.com/yuezk/GlobalProtect-openconnect/|{{Pkg|globalprotect-openconnect}}}}
* {{App|Libreswan|A free software implementation of the most widely supported and standardized VPN protocol based on ("IPsec") and the Internet Key Exchange ("IKE").|https://libreswan.org/|{{AUR|libreswan}}}}
* {{App|[[Mullvad]]|A GUI client for the Mullvad VPN service |https://mullvad.net/|{{Pkg|mullvad-vpn}}}}
* {{App|[[Nebula]]|A mesh VPN network|https://nebula.defined.net/docs/|{{Pkg|nebula}}}}
* {{App|[[NetworkManager]]|Supports a variety of protocols (e.g. MS, Cisco, Fortinet) via a plugin system.|https://wiki.gnome.org/Projects/NetworkManager/VPN|{{Pkg|networkmanager}}}}
* {{App|[[OpenConnect]]|Supports Cisco and Juniper VPNs.|https://www.infradead.org/openconnect/|{{Pkg|openconnect}}}}
* {{App|[[ProtonVPN]]|VPN provider that uses the OpenVPN and WireGuard protocol.|https://protonvpn.com/|{{Pkg|proton-vpn-gtk-app}}}}
* {{App|[[Openswan]]|IPsec-based VPN Solution.|https://www.openswan.org/|{{AUR|openswan}}}}
* {{App|[[OpenVPN]]|To connect to OpenVPN VPNs.|https://openvpn.net/|{{Pkg|openvpn}}}}
* {{App|[[PPTP Client]]|To connect to PPTP VPNs, like Microsoft VPNs (MPPE). (insecure)|https://pptpclient.sourceforge.net/|{{Pkg|pptpclient}}}}
* {{App|RiseupVPN|A GUI client for the Riseup VPN service from riseup.net.|https://riseup.net/en/vpn/ | {{AUR|riseup-vpn}} or {{AUR|riseup-vpn-configurator}} }}
* {{App|[[Rosenpass]]|Hybrid security against quantum computers for WireGuard by adding a post-quantum-secure key exchange|https://rosenpass.eu/|{{Pkg|rosenpass}}}}
* {{App|[[strongSwan]]|IPsec-based VPN Solution.|https://www.strongswan.org/|{{Pkg|strongswan}}}}
* {{App|[[tinc]]|tinc is a free VPN daemon.|https://www.tinc-vpn.org/|{{Pkg|tinc}}}}
* {{App|vopono|OpenVPN and WireGuard wrapper to launch applications with VPN tunnels in network namespaces.|https://github.com/jamesmcm/vopono|{{AUR|vopono}}}}
* {{App|vpnc|To connect to Cisco 3000 VPN Concentrators.|https://www.unix-ag.uni-kl.de/~massar/vpnc/|{{Pkg|vpnc}}}}
* {{App|[[WireGuard]]|Next generation secure network tunnel.|https://www.wireguard.com/|{{Pkg|wireguard-tools}}}}

=== Proxy servers ===

* {{App|Brook|Proxy focusing on strong encryption and being undetectable.|https://txthinking.github.io/brook/|{{Pkg|brook}}}}
* {{App|Dante|SOCKS server and SOCKS client, implementing [[RFC:1928]] and related standards.|https://www.inet.no/dante/|{{Pkg|dante}}}}
* {{App|Geph|A modular Internet censorship circumvention system designed specifically to deal with national filtering.|https://geph.io/en/|{{AUR|geph4-client}}}}
* {{App|hiddify|Multiplatform chain proxy client based on {{AUR|sing-box}}.|https://github.com/hiddify/hiddify-next|{{AUR|hiddify}}}}
* {{App|[[NaïveProxy]]|A Proxy using Chrome's network stack to camouflage traffic with strong censorship resistence and low detectablility.|https://github.com/klzgrad/naiveproxy|{{AUR|naiveproxy}}}}
* {{App|[[Privoxy]]|Non-caching web proxy with advanced filtering capabilities for enhancing privacy, modifying web page data and HTTP headers, controlling access, and removing ads and other obnoxious Internet junk.|https://www.privoxy.org/|{{Pkg|privoxy}}}}
* {{App|[[Shadowsocks]]|Secure socks5 proxy, designed to protect your Internet traffic.|https://shadowsocks.org/|{{Pkg|shadowsocks-rust}}}}
* {{App|[[Squid]]|Caching proxy for the Web supporting HTTP, HTTPS, FTP, and more.|https://www.squid-cache.org/|{{Pkg|squid}}}}
* {{App|[[Stunnel]]|A server and client to add and remove TLS encryption to TCP data flow.|https://www.stunnel.org/|{{Pkg|stunnel}}}}
* {{App|Throne|Cross-platform GUI proxy utility (Empowered by {{AUR|sing-box}}).|https://github.com/throneproj/Throne|{{AUR|throne}}}}
* {{App|Tinyproxy|Lightweight HTTP/HTTPS proxy daemon.|https://tinyproxy.github.io/|{{Pkg|tinyproxy}}}}
* {{App|[[Trojan]]|An unidentifiable mechanism that helps you bypass GFW.|https://trojan-gfw.github.io/trojan/|{{Pkg|trojan}}}}
* {{App|[[V2Ray]]|V2Ray is the core of Project V, which is a set of tools to help you build your own privacy network over the internet.|https://www.v2fly.org/en_US/|{{Pkg|v2ray}}}}
* {{App|V2RayN|A GUI client for Windows, Linux and macOS, support {{AUR|xray}} and {{AUR|sing-box}} cores and others.|https://github.com/2dust/v2rayN|{{AUR|v2rayN}}}}
* {{App|[[Varnish]]|High-performance HTTP accelerator.|https://varnish-cache.org/|{{Pkg|varnish}}}}
* {{App|Wireproxy|[[WireGuard]] client that exposes itself as a SOCKS5 proxy.|https://github.com/pufferffish/wireproxy|{{Pkg|wireproxy}}}}
* {{App|XX-Net|Easy to use web proxy tool.|https://github.com/XX-net/XX-Net/|{{AUR|xx-net}}}}
* {{App|Ziproxy|Forwarding (non-caching) compressing HTTP proxy server.|https://ziproxy.sourceforge.net/|{{Pkg|ziproxy}}}}

=== Anonymizing networks ===

* {{App|Arti|Rust implementation of the Tor anonymizing overlay network.|https://gitlab.torproject.org/tpo/core/arti|{{Pkg|arti}}}}
* {{App|[[GNUnet]]|Framework for secure peer-to-peer networking.|https://gnunet.org/|CLI: {{AUR|gnunet}}, GUI: {{AUR|gnunet-gtk}}}}
* {{App|Hyphanet|An encrypted network without censorship, previously named Freenet.|https://www.hyphanet.org/|{{AUR|hyphanet}}}}
* {{App|[[I2P]]|Distributed anonymous network.|https://geti2p.net/|{{Pkg|i2pd}}, {{AUR|i2p}}}}
* {{App|Lantern|Peer-to-peer internet censorship circumvention software.|https://getlantern.org/|{{AUR|lantern-bin}}}}
* {{App|Lokinet|Anonymous, decentralized and IP based overlay network for the internet.|https://lokinet.org/|{{AUR|lokinet}}}}
* {{App|[[Tor]]|Anonymizing overlay network.|https://www.torproject.org/|{{Pkg|tor}}}}

=== Network tunnels ===

* {{App|6tunnel|Tunnels IPv6 connections for IPv4-only applications.|https://github.com/wojtekka/6tunnel/|{{Pkg|6tunnel}}}}
* {{App|iodine|Tunnel IPv4 data through a DNS server.|https://code.kryo.se/iodine/|{{Pkg|iodine}}}}
* {{App|isatapd|Creates and maintains an ISATAP tunnel ([[RFC:5214]]).|http://www.saschahlusiak.de/linux/isatap.htm|{{Pkg|isatapd}}}}
* {{App|Ping Tunnel|A tool for reliably tunneling TCP connections over ICMP echo request and reply packets.|https://www.cs.uit.no/~daniels/PingTunnel/|{{Pkg|ptunnel}}}}
* {{App|Tuntox|Tunnel TCP connections over the Tox protocol.|https://github.com/gjedeer/tuntox/|{{Pkg|tuntox}}}}

=== Deep packet inspection circumvention ===

Tools to avoid censorship, bandwidth throttle without anonymization. See [[Wikipedia:Deep packet inspection]], [[Wikipedia:Internet censorship circumvention]] for an introduction to the topic.

* {{App|Bypass DPI|A simple software using SOCKS5, written in C and targeted at Russian censorship.|https://github.com/hufrea/byedpi|{{AUR|byedpi}}}}
* {{App|Cloak|A pluggable transport that works alongside traditional proxy tools like [[OpenVPN]], written in Go.|https://github.com/cbeuw/Cloak|{{AUR|cloak-obfuscation}}}}
* {{App|DPI Tunnel|An HTTP/transparent proxy, written in C++ and targeted at Russian censorship.|https://github.com/txtsd/DPITunnel|{{AUR|dpitunnel}}}}
* {{App|Green Tunnel|An anti-censorship utility using SOCKS5, written in nodejs and targeted at Iranian censorship.|https://github.com/SadeghHayeri/GreenTunnel|{{AUR|green-tunnel}}}}
* {{App|hysteria|A powerful, lightning fast and censorship resistant proxy that masquerades as standard HTTP/3 traffic. Supports SOCKS5, TUN, and TCP/UDP forwarding. Written in Go.|https://hysteria.network/|{{AUR|hysteria}}}}
* {{App|naiveproxy|A proxy using Chrome's network stack to camouflage traffic as normal HTTPS, making it highly resistant to DPI. Written in C++.|https://github.com/klzgrad/naiveproxy|{{AUR|naiveproxy}}}}
* {{App|Psiphon|An open-source Internet censorship circumvention system that uses SSH tunneling and obfuscation to bypass firewalls. Includes both client and server components.|https://github.com/Psiphon-Labs/psiphon-tunnel-core|{{AUR|psiphon-console-client}}, {{AUR|psiphon-server}}}}
* {{App|SpoofDPI|A simple and fast tool using SOCKS5, written in Go.|https://github.com/xvzc/SpoofDPI|{{AUR|spoofdpi}}}}
* {{App|zapret|A Netfilter queue mode or SOCKS5/transparent proxy, written in C and targeted at Russian censorship.|https://github.com/bol-van/zapret|{{AUR|zapret-git}}}}

=== Speedtest tools ===

* {{App|cloudflarespeedtest|Test Cloudflare CDN latency and speed to find the fastest IP.|https://github.com/XIU2/CloudflareSpeedTest|{{AUR|cloudflarespeedtest-bin}}}}
* {{App|LibreSpeed|Open source speedtest with graphical GTK client.|https://librespeed.org/|{{AUR|speedtest-librespeed}}}}
* {{App|nperf|Wide-area network speed test application.|https://www.nperf.com/|{{AUR|nperf-gui-appimage}}}}
* {{App|SpeedTest++|Unofficial speedtest.net CLI using raw TCP for better accuracy.|https://github.com/taganaka/SpeedTest|{{AUR|speedtest++}}}}
* {{App|speedtest-cli|Command-line interface for testing internet bandwidth using speedtest.net servers.|https://github.com/sivel/speedtest-cli|{{Pkg|speedtest-cli}}}}

=== Network monitoring and diagnostics tools ===

* {{App|bandwhich|Terminal bandwidth utilization tool showing usage by process, connection, and remote IP/hostname.|https://github.com/imsnif/bandwhich |{{Pkg|bandwhich}}}}
* {{App|dog|Modern command-line DNS client alternative to dig with colored output and JSON support.|https://dns.lookup.dog/ |{{Pkg|dog}}}}
* {{App|flent|The Fleet Network Tester for measuring bufferbloat and latency under load.|https://flent.org/ |{{AUR|flent}}}}
* {{App|gping|Ping with a real-time graph visualization of latency to multiple hosts.|https://github.com/orf/gping |{{Pkg|gping}}}}
* {{App|hyperfine|Command-line benchmarking tool, useful for comparing network response times.|https://github.com/sharkdp/hyperfine |{{Pkg|hyperfine}}}}
* {{App|netsniff-ng|High-performance Linux network packet sniffer and analyzer toolkit.|http://netsniff-ng.org/ |{{Pkg|netsniff-ng}}}}
* {{App|oha|HTTP load generator with TUI showing detailed timing breakdown (DNS, TCP, TLS, TTFB).|https://github.com/hatoo/oha |{{Pkg|oha}}}}
* {{App|ooniprobe-cli|Official OONI Probe CLI for detecting internet censorship, website blocking, and traffic manipulation.|https://ooni.org/ |{{AUR|ooniprobe-cli}}}}
* {{App|sniffnet|Network traffic monitoring with TUI/GUI, statistics by protocol, and per-host analysis.|https://github.com/GyulyVGC/sniffnet |{{Pkg|sniffnet}}}}
* {{App|tcping|TCP connectivity checker that bypasses ICMP blocks for port-specific diagnostics.|https://github.com/zhengxiaowai/tcping|{{AUR|tcping}}}}
* {{App|termshark|Terminal UI for tshark, providing a Wireshark-like interface in the terminal.|https://termshark.io/ |{{Pkg|termshark}}}}
* {{App|trippy|A network diagnostic tool combining traceroute and ping with an interactive TUI.|https://github.com/fujiapple852/trippy |{{Pkg|trippy}}}}

== Web browsers ==

See also: [[Wikipedia:Comparison of web browsers]]

=== Console ===

* {{App|[[Wikipedia:Browsh|browsh]]|A fully-modern text-based browser. Runs as a frontend to headless Firefox.|https://www.brow.sh/|{{AUR|browsh}}}}
* {{App|Carbonyl|A Chromium based browser built to run in a terminal.|https://fathy.fr/carbonyl|{{AUR|carbonyl}}}}
* {{App|Chawan|A web browser for your terminal.|https://sr.ht/~bptato/chawan/|{{Pkg|chawan}}}}
* {{App|[[ELinks]]|Advanced and well-established feature-rich text mode web browser with mouse wheel scroll support, frames and tables, extensible with Lua & Guile (links fork).|http://elinks.or.cz/|{{Pkg|elinks}}}}
* {{App|[[Wikipedia:Links (web browser)|Links]]|Graphics and text mode web browser. Includes a console version similar to Lynx.|https://links.twibright.com/|{{Pkg|links}}}}
* {{App|[[Wikipedia:Lynx (web browser)|Lynx]]|Text browser for the World Wide Web.|https://lynx.invisible-island.net/|{{Pkg|lynx}}}}
* {{App|[[w3m]]|Pager/text-based web browser. It has vim-like keybindings, and is able to display images.|https://salsa.debian.org/debian/w3m|{{Pkg|w3m}}}}

=== Graphical ===

==== Gecko-based ====

See also: [[Wikipedia:Gecko (software)]]

* {{App|[[Firefox]]|Extensible browser from Mozilla based on Gecko with fast rendering.|https://www.firefox.com/en-US/|{{Pkg|firefox}}}}
* {{App|[[Wikipedia:SeaMonkey|SeaMonkey]]|Continuation of the Mozilla Internet Suite.|https://www.seamonkey-project.org/|{{AUR|seamonkey}}}}

===== Firefox spin-offs =====

* {{App|[[Wikipedia:Floorp|Floorp]]|Firefox-based browser developed by a community of students in Japan.|https://floorp.app/|{{AUR|floorp}}}}
* {{App|[[Wikipedia:GNU IceCat|GNU IceCat]]|A customized build of Firefox ESR distributed by the GNU Project, stripped of non-free components and with additional privacy extensions. Release cycle may be delayed compared to Mozilla Firefox.|https://www.gnu.org/software/gnuzilla/|{{AUR|icecat}}}}
* {{App|Konform Browser|A customized build of Firefox ESR focused on security, privacy and freedom. Originally based on LibreWolf.|https://codeberg.org/konform-browser|{{AUR|konform-browser}}}}
* {{App|[[Wikipedia:LibreWolf|LibreWolf]]|A fork of Firefox, focused on privacy, security and freedom.|https://librewolf.net/|{{AUR|librewolf}}}}
* {{App|[[Wikipedia:Midori (web browser)|Midori]]|Light, fast and secure browser.|https://github.com/goastian/midori-desktop|{{AUR|midori-bin}}}}
* {{App|[[Wikipedia:Mullvad Browser|Mullvad Browser]]|Privacy-focused web browser developed by Mullvad VPN and the Tor Project based on Firefox ESR.|https://mullvad.net/en/browser|{{AUR|mullvad-browser}}}}
* {{App|[[Tor]] Browser Launcher|Securely and easily download, verify, install, and launch Tor Browser. Tor Browser is a fork of Firefox ESR with the ability to access Onion domains, plus additional privacy modifications.|https://gitlab.torproject.org/tpo/applications/torbrowser-launcher|{{Pkg|torbrowser-launcher}}}}
* {{App|[[Wikipedia:Waterfox|Waterfox]]|Fork of Mozilla Firefox featuring some privacy, usability, and speed enhancements.|https://www.waterfox.com/|{{AUR|waterfox}}}}
* {{App|[[Wikipedia:Zen Browser|Zen Browser]]|An experimental, performance-optimized fork of Firefox focused on customizability and design with additional features.|https://zen-browser.app/|{{AUR|zen-browser}}}}

==== Blink-based ====

See also: [[Wikipedia:Blink (web engine)]]

* {{App|[[Chromium]]|Web browser developed by Google. Chromium is the open-source project behind Google Chrome.|https://www.chromium.org/Home/|{{Pkg|chromium}}}}

===== Privacy-focused Chromium spin-offs =====

* {{App|[[Wikipedia:Brave (web browser)|Brave]]|A web browser with a built-in advertisement and tracker blocking mechanism.|https://brave.com/|{{AUR|brave-bin}}}}
* {{App|Cromite|Cromite is a Chromium fork based on Bromite (Currently unmaintained) with built-in support for ad blocking and an eye for privacy. See its [https://github.com/uazo/cromite/blob/master/docs/FEATURES.md list of features].|https://github.com/uazo/cromite|{{AUR|cromite-bin}}}}
* {{App|Helium|A browser based on Ungoogled Chromium with multiple layouts, !bangs in the address bar and a Chrome Web Store proxy.|https://helium.computer/|{{AUR|helium-browser}}}}
* {{App|Thorium|Thorium develops a periodically synchronized fork of the Chromium browser, expanded with additional patches to optimize performance, improve usability and enhance security. According to the developers' tests Thorium is 8-40% ahead of the regular Chromium, mainly due to the inclusion of additional optimizations during compilation.|https://thorium.rocks/|{{AUR|thorium-browser-bin}}}}
* {{App|[[Wikipedia:Ungoogled Chromium|Ungoogled Chromium]]|Modifications to Google Chromium for removing Google integration and enhancing privacy, control, and transparency.|https://github.com/ungoogled-software/ungoogled-chromium|{{AUR|ungoogled-chromium}}}}
* {{App|[[Wikipedia:Ungoogled Chromium|Ungoogled Chromium]] (Widevine)|The same as the regular version, but with the ability to access DRM-protected content.|https://github.com/ungoogled-software/ungoogled-chromium|{{AUR|ungoogled-chromium-widevine-bin}}}}

===== Proprietary Chromium spin-offs =====

* {{App|[[Wikipedia:Google Chrome|Google Chrome]]|Proprietary web browser developed by Google.|https://www.google.com/chrome/|{{AUR|google-chrome}}}}
* {{App|[[Wikipedia:Microsoft Edge|Microsoft Edge]]|Proprietary web browser developed by Microsoft.|https://www.microsoft.com/en-us/edge/|{{AUR|microsoft-edge-stable-bin}}}}
* {{App|[[Wikipedia:Opera (web browser)|Opera]]|Proprietary browser developed by Opera Software.|https://www.opera.com/opera|{{AUR|opera}}}}
* {{App|[[Wikipedia:Opera (web browser)#Opera GX|Opera GX]]|Proprietary "gaming-oriented" alternative to the regular Opera browser. Also developed by Opera Software.|https://www.opera.com/gx|{{AUR|opera-gx}}}}
* {{App|[[Wikipedia:SlimBrowser|Slimjet]]|Fast, smart and powerful proprietary browser based on Chromium.|https://www.slimjet.com/|{{AUR|slimjet}}}}
* {{App|[[Wikipedia:SRWare Iron|SRWare Iron]]|Light-weight proprietary browser based on Chromium.|https://www.srware.net/iron/|{{AUR|srware-iron-bin}}}}
* {{App|[[Vivaldi]]|An advanced proprietary browser made with the power user in mind.|https://vivaldi.com/|{{Pkg|vivaldi}}}}
* {{App|[[Wikipedia:Yandex Browser|Yandex Browser]]|Proprietary browser that combines a minimal design with sophisticated technology to make the web faster, safer, and easier.|https://browser.yandex.com/|{{AUR|yandex-browser}}}}

===== Browsers based on Qt WebEngine =====

{{Note|''qt5-webengine''–based browsers were removed from the list, because it is today considered insecure and outdated.}}

* {{App|Angelfish|Web browser for Plasma Mobile. Part of {{Grp|kde-network}}.|https://apps.kde.org/angelfish/|{{Pkg|angelfish}}}}
* {{App|[[Wikipedia:Dooble|Dooble]]|Colorful Web browser.|https://textbrowser.github.io/dooble/|{{AUR|dooble}}}}
* {{App|[[Wikipedia:Eric Python IDE|Eric]]|QtWebEngine-based HTML browser, part of the eric6 development toolset, can be launched with the {{ic|eric6_browser}} command.|https://eric-ide.python-projects.org/|{{AUR|eric}}}}
* {{App|[[Wikipedia:Falkon|Falkon]]|Web browser based on QtWebEngine, written in Qt framework. Part of {{Grp|kde-network}}.|https://falkon.org/|{{Pkg|falkon}}}}
* {{App|Fiery|A convergent web browser. Part of {{Grp|maui}}.|https://mauikit.org/apps/|{{Pkg|fiery}}}}
* {{App|[[Wikipedia:Konqueror|Konqueror]]|Web browser based on Qt toolkit and Qt WebEngine. Part of {{Grp|kde-network}}.|https://apps.kde.org/konqueror/|{{Pkg|konqueror}}}}
* {{App|[[qutebrowser]]|A keyboard-driven, [[vim]]-like browser based on PyQt5 and QtWebEngine.|https://qutebrowser.org/|{{Pkg|qutebrowser}}}}

===== Browsers based on Electron =====

* {{App|Catalyst|A minimal FOSS web browser with no data collection.|https://getcatalyst.eu.org/|{{AUR|catalyst-browser-bin}}}}
* {{App|Franz|Messaging browser for WhatsApp, Facebook Messenger, Slack, Telegram and many other web services.|https://meetfranz.com/|{{AUR|franz}}}}
* {{App|Ferdium|A GPL-licensed alternative to Franz, forked from Franz.|https://ferdium.org/|{{AUR|ferdium}}}}
* {{App|Min|A fast, minimal browser that protects your privacy. It includes an interface designed to minimize distractions.|https://minbrowser.org/|{{AUR|min}}}}
* {{App|Vieb|Minimalist Electron-based browser with Vim-inspired keybindings and a built-in ad-blocker.|https://vieb.dev/|{{AUR|vieb}}}}

==== Browsers based on WebKitGTK ====

See also: [[Wikipedia:WebKit]]

{{Note|''webkitgtk, webkitgtk2, qt5-webkit'' and ''qtwebkit''–based browsers were removed from the list, because these are today considered insecure and outdated. More information is available [https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-updates/ here] and [https://blogs.gnome.org/mcatanzaro/2022/11/04/stop-using-qtwebkit/ here].}}

Most of these support ad-blocking via [https://github.com/jun7/wyebadblock wyebadblock].

* {{App|[[Badwolf]]|A minimalist privacy-focused browser.|https://hacktivis.me/projects/badwolf|{{AUR|badwolf}}}}
* {{App|Eolie|Simple web browser for GNOME.|https://wiki.gnome.org/Apps/Eolie|{{Pkg|eolie}}}}
* {{App|[[GNOME Web]]|Browser which uses the WebKitGTK rendering engine. Part of {{Grp|gnome}}.|https://apps.gnome.org/Epiphany/|{{Pkg|epiphany}}}}
* {{App|[[Luakit]]|Fast, small, webkit based browser framework extensible by Lua.|https://luakit.github.io/|{{Pkg|luakit}}}}
* {{App|[[Nyxt]]|Keyboard-oriented, infinitely extensible browser designed for power users. It has familiar key-bindings (Emacs, VI, CUA) and features fuzzy searching between tabs, multiple selections, history as a tree and more.|https://nyxt.atlas.engineer/|{{Pkg|nyxt}}}}
* {{App|[[surf]]|Lightweight WebKit-based browser, which follows the [https://suckless.org/philosophy suckless philosophy] (basically, the browser itself is a single C source file).|https://surf.suckless.org/|{{AUR|surf}}}}
* {{App|Surfer|Simple keyboard based web browser, written in C. It supports custom JS-scripts.|https://github.com/nihilowy/surfer|{{AUR|surfer-git}}}}
* {{App|Tangram|Integration of web applications into the desktop, specifically GNOME.|https://apps.gnome.org/Tangram/|{{Pkg|tangram}}}}
* {{App|Vimb|A Vim-like web browser written in C that is inspired by Pentadactyl and Vimprobable. It includes a manpage and a howto for common configurations. It supports custom JS-scripts, dark mode and handles geolocation requests.|https://fanglingsu.github.io/vimb/|{{Pkg|vimb}}}}
* {{App|wyeb|A vim-like web browser inspired by dwb and luakit with Adblock.|https://github.com/jun7/wyeb|{{AUR|wyeb-git}}}}

==== Goanna-based ====

See also: [[Wikipedia:Goanna (software)]]

* {{App|[[Wikipedia:Basilisk (web browser)|Basilisk]]|A XUL-based web browser, similar in design to Firefox, aimed at providing a fully functional browsing experience with a classic interface.|https://basilisk-browser.org/|{{AUR|basilisk}}}}
* {{App|[[Wikipedia:Pale Moon (web browser)|Pale Moon]]|A Firefox fork focussing on speed, with a pre-Firefox 29 interface. Uses [[Wikipedia:Goanna (software)|Goanna]] layout engine, a fork of Gecko. Firefox add-ons may not be compatible. Without support for newer Firefox features such as WebExtensions, cache2, e10s, and OTMC. Many of the old 93,598 versions of 19,450 Firefox add-ons created by 14,274 developers over the past 15 years using XUL/XPCOM technology in the [https://github.com/JustOff/ca-archive Classic Add-ons Archive] still work.|https://www.palemoon.org/|{{AUR|palemoon}}}}

==== Servo-based ====

* {{App|[[Wikipedia:Servo (software)|Servo]]|Web browser rendering engine written in Rust, with WebGL and WebGPU support, and adaptable to desktop, mobile, and embedded applications.|https://servo.org/|{{AUR|servo}}}}
* {{App|Verso|Experimental web browser based on Servo experimenting with multi-view and multi-window and building UI elements entirely from Servo.|https://gitlab.com/verso-browser/verso|{{AUR|verso-git}}}}

==== Other ====

* {{App|[[Dillo]]|Small, fast graphical web browser built on [[Wikipedia:Fltk|FLTK]]. Uses its own layout engine.|https://dillo-browser.org/|{{Pkg|dillo}}}}
* {{App|[[Wikipedia:Ladybird (web browser)|Ladybird]]|Web browser built from scratch using the [[Wikipedia:SerenityOS|SerenityOS]] LibWeb engine.|https://ladybird.org/|{{AUR|ladybird}}}}
* {{App|[[Wikipedia:NetSurf|NetSurf]]|Featherweight browser written in C, notable for its slowly developing JavaScript support and fast rendering through its own layout engine.|https://www.netsurf-browser.org/|{{Pkg|netsurf}}}}

=== Gemini browsers ===

See also: [[Wikipedia:Gemini (protocol)#Software]]

* {{App|Amfora|Terminal browser for the Gemini protocol.|https://github.com/makeworld-the-better-one/amfora|{{Pkg|amfora}}}}
* {{App|Bombabillo|Non-web client for the terminal, supporting Gopher, Gemini and much more.|https://bombadillo.colorfield.space/|{{AUR|bombadillo}}}}
* {{App|Castor|Graphical client for the Gemini, Gopher, and Finger protocols, written in Rust with GTK.|https://git.sr.ht/~julienxx/castor|{{AUR|castor}}}}
* {{App|Geopard|A graphical gemini client written in rust, using the gtk4 toolkit.|https://github.com/ranfdev/Geopard|{{AUR|geopard}}}}
* {{App|Kristall|Qt-based Gemini browser.|https://github.com/MasterQ32/kristall|{{AUR|kristall}}}}
* {{App|Lagrange|Desktop GUI client for browsing Gemini space, offering modern conveniences familiar from web browsers.|https://gmi.skyjake.fi/lagrange|{{AUR|lagrange}}}}
* {{App|Telescope|w3m-like browser for Gemini.|https://telescope-browser.org/|{{AUR|telescope}}}}

== Web servers ==

A [[Wikipedia:Web server|web server]] serves HTML web pages and other files via HTTP to clients like [[:Category:Web browser|web browsers]].
The major web servers can be interfaced with programs to serve dynamic content ([[web applications]]).

See also: [[:Category:Web server]], [[Wikipedia:Comparison of web server software]]

* {{App|[[Apache HTTP Server]]|A high performance Unix-based HTTP server.|https://httpd.apache.org/|{{Pkg|apache}}}}
* {{App|[[Caddy]]|HTTP/3 web server with automatic HTTPS.|https://caddyserver.com/|{{Pkg|caddy}}}}
* {{App|[[Hiawatha]]|Secure and advanced web server.|https://hiawatha.leisink.net/|{{AUR|hiawatha}}}}
* {{App|[[Lighttpd]]|A secure, fast, compliant and very flexible web-server.|https://www.lighttpd.net/|{{Pkg|lighttpd}}}}
* {{App|[[nginx]]|Lightweight HTTP server and IMAP/POP3 proxy server.|https://nginx.org/|{{Pkg|nginx}}}}
* {{App|sthttpd|Supported fork of the thttpd web server.|https://github.com/blueness/sthttpd|{{AUR|sthttpd}}}}
* {{App|Traefik|A modern reverse proxy and load balancer that makes deploying microservices easy.|https://traefik.io/traefik/|{{Pkg|traefik}}}}
* {{App|yaws|Web server/framework written in Erlang.|https://erlyaws.github.io/|{{AUR|yaws}}}}

=== Static web servers ===

* {{App|Apache Traffic Server|Fast, scalable and extensible HTTP/1.1 and HTTP/2 compliant caching proxy server.|https://trafficserver.apache.org/|{{AUR|trafficserver}}}}
* {{App|darkhttpd|A small and secure static web server, written in C, does not support HTTPS or Auth.|https://unix4lyfe.org/darkhttpd/|{{Pkg|darkhttpd}}}}
* {{App|http.server|[[Python]] standard library module, which can be used from the command-line, but due to security considerations not recommended for production.|https://docs.python.org/library/http.server.html|{{Pkg|python}}}}
* {{App|[[miniserve]]|Rust alternative to darkhttpd with UTF-8, optional HTTP authentication, file uploading, and more.|https://github.com/svenstaro/miniserve|{{Pkg|miniserve}}}}
* {{App|quark|An extremely small and simple http get-only web server. It only serves static pages on a single host.|https://tools.suckless.org/quark/|{{AUR|quark-git}}}}
* {{App|serve|Static file serving and directory listing.|https://github.com/zeit/serve|{{AUR|nodejs-serve}}}}
* {{App|Webfs|Simple and instant web server for mostly static content.|https://linux.bytesex.org/misc/webfs.html|{{AUR|webfs}}}}

=== Specialized web servers ===

* {{App|chezdav|WebDAV server that allows to share a particular directory.|https://wiki.gnome.org/phodav|{{Pkg|phodav}}}}
* {{App|LibreKitten|Block-based programming language based off Scratch that includes a web server extension.|https://librekitten.org|{{AUR|librekitten-cli-bin}}}}
* {{App|Mongoose|Embedded web server library, supports WebSocket and MQTT.|https://github.com/cesanta/mongoose|{{AUR|mongoose}}}}
* {{App|OnionShare|Lets you securely and anonymously send and receive files. It works by starting a web server, making it accessible as a Tor onion service, and generating an unguessable web address so others can download files from you, or upload files to you.|https://onionshare.org/|{{Pkg|onionshare}}}}
* {{App|Transfer More|A minimalist open-source upload HTTP server to store and share files temporarily, written in Crystal, and based on Kemal.|https://up.sceptique.eu/|{{AUR|transfer-more}}}}
* {{App|VServer|GTK application, which opens an http server in the selected folder and shares your files.|https://github.com/bcedu/ValaSimpleHTTPServer|{{AUR|vserver-git}}}}
* {{App|webhook|Small server for creating HTTP endpoints (hooks)|https://github.com/adnanh/webhook|{{Pkg|webhook}}}}
* {{App|Woof|An ad-hoc single file webserver; Web Offer One File.|http://www.home.unix-ag.org/simon/woof.html|{{AUR|woof}}}}

=== WSGI servers ===

* {{App|Gunicorn|A Python WSGI HTTP Server for UNIX.|https://gunicorn.org/|{{Pkg|gunicorn}}}}
* {{App|[[uWSGI]]|A fast, self-healing and developer/sysadmin-friendly application container server written in C.|https://uwsgi-docs.readthedocs.io/|{{Pkg|uwsgi}}}}
* {{App|Waitress|A WSGI server for Python 3.|https://github.com/Pylons/waitress|{{Pkg|python-waitress}}}}

Apache also supports WSGI with [[mod_wsgi]].

=== Performance testing ===

* {{App|httperf|Can generate various HTTP workloads, written in C.|https://github.com/httperf/httperf|{{AUR|httperf-git}}}}
* {{App|httping|A "ping"-like tool for HTTP requests|https://www.vanheusden.com/httping/|{{Pkg|httping}}}}
* {{App|http_load|A webserver performance testing tool, runs in a single process.|https://www.acme.com/software/http_load/{{Dead link|2025|03|15|status=SSL error}}|{{AUR|http_load}}}}
* {{App|siege|An HTTP regression testing and benchmarking utility.|https://www.joedog.org/siege-home/|{{Pkg|siege}}}}
* {{App|vegeta|HTTP load testing tool, written in Go.|https://github.com/tsenart/vegeta|{{Pkg|vegeta}}}}
* {{App|Web Bench|Benchmarking tool, uses fork() for simulating multiple clients.|http://home.tiscali.cz/~cz210552/webbench.html|{{AUR|webbench}}}}

== File sharing ==

=== Download managers ===

See also: [[Wikipedia:Comparison of download managers]]

==== Console ====

* {{App|[[aria2]]|Lightweight download utility that supports HTTP/S, FTP, SFTP, BitTorrent and Metalink. It can run as a daemon controlled via a built-in JSON-RPC or XML-RPC interface.|https://aria2.github.io/|{{Pkg|aria2}}}}
* {{App|Axel|Featherweight command line download accelerator sitting at under 250kB on disk. Supports HTTP/S and FTP.|https://github.com/eribertomota/axel|{{Pkg|axel}}}}
* {{App|[[cURL]]|A URL retrieval utility and library. Supports HTTP, FTP and SFTP.|https://curl.haxx.se/|{{Pkg|curl}}}}
* {{App|Gtuber|Fetch media info from websites (bilibili, lbry, niconico, reddit, twitch, youtube). Includes a command-line downloader ({{ic|gtuber-dl}}) and a GStreamer plugin, which is used automatically when you try playing video from website that Gtuber can handle in your GStreamer based application.|https://github.com/Rafostar/gtuber|{{AUR|gtuber}}}}
* {{App|HTTPie|Human-friendly command-line HTTP client for the API era.|https://github.com/httpie/httpie|{{Pkg|httpie}}}}
* {{App|[[Wikipedia: dargahamn.net | dargahamn.net ]]|An easy-to-use offline browser utility. It allows you to download a World Wide Web site from the Internet to a local directory, building recursively all directories, getting HTML, images, and other files from the server to your computer.|https://www. dargahamn.net .com/|{{Pkg| dargahamn.net }}}}
* {{App|[[Wikipedia:Lftp|LFTP]]|Sophisticated file transfer program. Supports HTTP, FTP, SFTP, FISH, and BitTorrent.|https://lftp.yar.ru/|{{Pkg|lftp}}}}
* {{App|Plowshare|A set of command-line tools designed for managing file-sharing websites (aka Hosters).|https://github.com/mcrapet/plowshare|{{AUR|plowshare}}}}
* {{App|[[Wikipedia:RTMPDump|RTMPDump]]|Download FLV videos through RTMP (Adobe's proprietary protocol for Flash video players)|http://rtmpdump.mplayerhq.hu/|{{Pkg|rtmpdump}}}}
* {{App|snarf|Command-line URL retrieval tool. Supports HTTP and FTP.|https://www.xach.com/snarf/|{{AUR|snarf}}}}
* {{App|[[Streamlink]]|Launch streams from various streaming services in a custom video player or save them to a file.|https://streamlink.github.io/|{{Pkg|streamlink}}}}
* {{App|[[Wikipedia:Streamripper|Streamripper]]|Records and splits streaming mp3 into tracks.|https://streamripper.sourceforge.net/|{{AUR|streamripper}}}}
* {{App|[[Wget]]|A network utility to retrieve files from the Web. Supports HTTP and FTP.|https://www.gnu.org/software/wget/|{{Pkg|wget}}}}
* {{App|yewtube|Terminal-based YouTube player and downloader.|https://github.com/mps-youtube/yewtube|{{AUR|yewtube}}}}
* {{App|You-Get|Download media contents (videos, audios, images) from the Web.|https://you-get.org/|{{AUR|you-get}}}}
* {{App|youtube-dl|Download videos from YouTube and many other web sites.|https://rg3.github.io/youtube-dl/|{{AUR|youtube-dl}}}}
* {{App|youtube-viewer|Command line utility for viewing YouTube videos.|https://github.com/trizen/youtube-viewer|{{AUR|youtube-viewer}}}}
* {{App|[[yt-dlp]]|A youtube-dl fork with additional features and fixes.|https://github.com/yt-dlp/yt-dlp|{{Pkg|yt-dlp}}}}
* {{App|ytfzf|A POSIX script to find and watch youtube videos from the terminal.|https://github.com/pystardust/ytfzf|{{Pkg|ytfzf}}}}

==== Graphical ====

* {{App|ClipGrab|Downloader and converter for YouTube, Vimeo and many other online video sites.|https://clipgrab.org/|{{AUR|clipgrab}}}}
* {{App|FatRat|Qt based download manager with support for HTTP, FTP, SFTP, BitTorrent and Metalink.|https://github.com/LubosD/fatrat|{{AUR|fatrat-git}}}}
* {{App|Forklift|Simple GUI for youtube-dl using PyGObject.|https://github.com/Johnn3y/Forklift|{{AUR|forklift-git}}}}
* {{App|gtk-youtube-viewer|GTK utility for viewing YouTube videos. See optional dependencies for the GUI.|https://github.com/trizen/youtube-viewer|{{AUR|youtube-viewer}}}}
* {{App|[[Wikipedia:Wget#GWget|Gwget]]|Download manager for GNOME. Supports HTTP and FTP.|https://gitlab.gnome.org/Archive/gwget|{{AUR|gwget}}}}
* {{App|Gydl|GUI wrapper around the already existing youtube-dl program to download content from sites like YouTube.|https://github.com/JannikHv/gydl|{{AUR|gydl-git}}}}
* {{App|Gyre|GTK3 downloader for videos from Coub.|https://github.com/HelpSeeker/Gyre|{{AUR|gyre}}}}
* {{App|[[JDownloader]]|Java-based downloader for one-click hosting sites.|https://jdownloader.org/|{{AUR|jdownloader2}}}}
* {{App|[[Wikipedia:KGet|KGet]]|Download manager for KDE. Supports HTTP, FTP, BitTorrent and Metalink. Part of {{Grp|kde-network}}.|https://apps.kde.org/kget/|{{Pkg|kget}}}}
* {{App|MegaBasterd|Yet another unofficial MEGA downloader/uploader/streaming suite.|https://github.com/tonikelope/megabasterd|{{AUR|megabasterd-bin}}}}
* {{App|Motrix|Full-featured download manager that supports downloading HTTP, FTP, BitTorrent, Magnet, etc. Based on the [https://electronjs.org/ Electron] platform.|https://motrix.app/|{{AUR|motrix}}}}
* {{App|Persepolis|Graphical front-end for aria2 download manager with lots of features. Supports HTTP and FTP.|https://persepolisdm.github.io/|{{Pkg|persepolis}}}}
* {{App|[[pyLoad]]|Downloader written in Python and designed to be extremely lightweight, easily extensible and fully manageable via web.|https://pyload.net/|{{AUR|pyload-ng}}}}
* {{App|Steadyflow|Simple download manager for GNOME. Supports HTTP and FTP.|https://launchpad.net/steadyflow|{{Pkg|steadyflow}}}}
* {{App|Streamtuner2|Internet radio station and video browser. It simply lists stations in categories from different directories and launches your preferred media apps for playback.|https://sourceforge.net/projects/streamtuner2/|{{AUR|streamtuner2}}}}
* {{App|uGet|GTK download manager featuring download classification and HTML import. Supports HTTP, FTP, BitTorrent, Metalink, YouTube and Mega.|https://ugetdm.com/|{{Pkg|uget}}}}
* {{App|Varia|GTK frontend for aria2c and yt-dlp.|https://github.com/giantpinkrobots/varia|{{AUR|varia}}}}
* {{App|Video Downloader|GTK application to download videos from websites like YouTube and many others (based on youtube-dl).|https://github.com/Unrud/video-downloader|{{AUR|video-downloader}}}}
* {{App|Xtreme Download Manager|Powerful tool to increase download speed up-to 500%. Supports HTTP and FTP. Video grabber works in a general way and is not limited to certain websites.|https://subhra74.github.io/xdm/|{{AUR|xdman}}}}
* {{App|youtubedl-gui|Simple-to-use graphical interface for youtube-dl.|https://github.com/JaGoLi/ytdl-gui|{{AUR|youtubedl-gui}}}}

=== LAN file transfer ===

See also: [[#LAN messengers]]

* {{App|LAN Share|Cross-platform local area network file transfer application, built using Qt GUI framework. It can be used to transfer a whole folder, one or more files, large or small immediately without any additional configuration.|https://github.com/abdularis/LAN-Share|{{AUR|lanshare}}}}
* {{App|LocalSend|Cross-platform app to securely share files and messages with nearby devices over the local network without needing an internet connection.|https://localsend.org/|{{AUR|localsend}}}}
* {{App|Magic Wormhole|Command-line tool {{ic|wormhole}} to securely transfer data between computers.|https://github.com/magic-wormhole/magic-wormhole|{{Pkg|magic-wormhole}}}}
* {{App|NitroShare|Cross-platform network file transfer application, built using Qt GUI framework. It is designed to make transferring files from one device to another on the local network extremely simple.|https://nitroshare.net/|{{AUR|nitroshare}}}}
* {{App|Teleport|Native GTK3 application to effortlessly share files on the local network.|https://gitlab.gnome.org/jsparber/teleport|{{AUR|teleport-share-git}}}}
* {{App|Warp|Securely send files to each other via the internet or local network by exchanging a word-based code. It uses the Magic Wormhole protocol.|https://apps.gnome.org/Warp/|{{Pkg|warp}}}}
* {{App|Warpinator|GTK application to share files across the LAN.|https://github.com/linuxmint/warpinator|{{Pkg|warpinator}}}}

=== Cloud storage servers ===

* {{App|copyparty|Lightweight and portable file server with extensive protocol, media playback and file management support.|https://github.com/9001/copyparty|{{Pkg|copyparty}}}}
* {{App|[[Cozy]]|A personal cloud you can hack, host and delete.|https://cozy.io/|{{Pkg|cozy-stack}}}}
* {{App|[[Nextcloud]]|A cloud server to store your files centrally on a hardware controlled by you.|https://nextcloud.com|{{Pkg|nextcloud}}}}
* {{App|[[Pydio]]|Mature open source web application for file sharing and synchronization.|https://pydio.com/|{{AUR|pydio}}}}
* {{App|Seafile|An online file storage and collaboration tool with advanced support for file syncing, privacy protection and teamwork.|https://www.seafile.com/|{{AUR|seafile-server}}}}

=== Cloud synchronization clients ===

{{Tip|<nowiki></nowiki>
* Some [[synchronization and backup programs]] provide direct support for some cloud-storage services.
* Some [[FUSE#List of FUSE filesystems|FUSE filesystems]] provide a way to mount cloud-storage as a filesystem. Google Drive can be accessed also by {{Pkg|kio-gdrive}} for KIO-based applications (like [[Dolphin]]).
* See [[Data-at-rest encryption#Cloud-storage optimized]] to achieve zero-knowledge (client-side transparent encryption) storage on any third-party cloud service.
}}

==== Multi-protocol clients ====

* {{App|CloudCross|Synchronize local files and folders with many cloud providers. Mail.ru Cloud, Yandex Disk, Google Drive, OneDrive and Dropbox support is available.|https://github.com/MasterSoft24/CloudCross|{{AUR|cloudcross}}}}
* {{App|Rclone|Multi-provider sync, copy, and mount client.|https://rclone.org/|{{Pkg|rclone}}}}
* {{App|Rclone Browser|GUI client for Rclone.|https://github.com/kapitainsky/RcloneBrowser|{{AUR|rclone-browser}}}}

==== Google Drive clients ====

* {{App|DriveSync|Command line utility that synchronizes your Google Drive files with a local folder on your machine.|https://github.com/MStadlmeier/drivesync|{{AUR|drivesync}}}}
* {{App|gdrive|Command line utility for interacting with Google Drive.|https://github.com/prasmussen/gdrive|{{AUR|gdrive}}}}
* {{App|Google Drive OCamlFUSE|A FUSE filesystem for Google Drive, written in OCaml.|https://github.com/astrada/google-drive-ocamlfuse|{{AUR|google-drive-ocamlfuse}}}}
* {{App|Grive|Google Drive client with support for new Drive REST API and partial sync.|https://github.com/vitalif/grive2|{{AUR|grive}}}}
* {{App|[[Insync]]|Unofficial proprietary Google Drive desktop client.|https://www.insynchq.com/|{{AUR|insync}}}}

==== Other synchronization clients ====

* {{App|aws-cli|CLI for Amazon Web Services, including efficient file transfers to and from Amazon S3.|https://aws.amazon.com/cli/|{{Pkg|aws-cli}}}}
* {{App|Backblaze B2|Backblaze B2 open-source command-line client.|https://www.backblaze.com/b2/cloud-storage.html|{{AUR|backblaze-b2}}}}
* {{App|Baidu Netdisk|Proprietary client for cloud storage service launched by Baidu (formerly Baidu Cloud).|https://pan.baidu.com|{{AUR|baidunetdisk-bin}}}}
* {{App|[[Cozy]] Drive|Desktop client for Cozy.|https://cozy-labs.github.io/cozy-desktop/|{{Pkg|cozy-desktop}}}}
* {{App|[[Dropbox]]|Proprietary desktop client for Dropbox.|https://www.dropbox.com/|{{AUR|dropbox}}}}
* {{App|[[Wikipedia:Mega (service)|Mega]] Sync Client|Proprietary (though [https://github.com/meganz/MEGAsync/blob/master/LICENCE.md source-available]) desktop client to sync files with Mega.|https://mega.nz/|CLI: {{AUR|megacmd}}, GUI: {{AUR|megasync}}}}
* {{App|Megatools|Unofficial CLI for Mega.|https://megatools.megous.com/|{{AUR|megatools}}}}
* {{App|[[Nextcloud]] Client|Desktop client for Nextcloud.|https://nextcloud.com/|{{Pkg|nextcloud-client}}}}
* {{App|Nutstore|Proprietary desktop client for Nutstore.|https://www.jianguoyun.com/|{{AUR|nutstore}}}}
* {{App|OneDrive|Fork of the unofficial CLI for [https://onedrive.live.com/about/ OneDrive].|https://github.com/abraunegg/onedrive|{{AUR|onedrive-abraunegg}}}}
* {{App|[[Wikipedia:ownCloud|ownCloud]] Desktop Client|Desktop syncing client for ownCloud.|https://owncloud.com/client/|{{Pkg|owncloud-client}}}}
* {{App|pCloud Drive|Proprietary desktop syncing client for pCloud. Based on the [https://electronjs.org/ Electron] platform.|https://www.pcloud.com/download-free-online-cloud-file-storage.html|{{AUR|pcloud-drive}}}}
* {{App|[[Pydio]]Sync|Desktop client for Pydio.|https://pydio.com/|{{AUR|pydio-sync}}}}
* {{App|S3cmd|Unofficial CLI for Amazon S3.|https://s3tools.org/s3cmd|{{Pkg|s3cmd}}}}
* {{App|Seafile Client|GUI client for Seafile.|https://www.seafile.com/|{{AUR|seafile-client}}}}
* {{App|[[Wikipedia:SpiderOak|SpiderOak]] One|Proprietary client for SpiderOak One.|https://spideroak.com/|{{AUR|spideroak-one}}}}
* {{App|[[Wikipedia:Synology|Synology]] Drive|Proprietary GUI client to sync and share files between a centralized Synology NAS and multiple client computers.|https://www.synology.com/|{{AUR|synology-drive}}}}
* {{App|[[Wikipedia:Tresorit|Tresorit]]|Proprietary desktop syncing client for Tresorit.|https://tresorit.com/download|{{AUR|tresorit}}}}
* {{App|Versiobit|Desktop file sync client with versioning and end-to-end encryption.|https://versiobit.com|{{AUR|versiobit}}}}
* {{App|[[Yandex Disk]]|Proprietary CLI for Yandex Disk.|https://disk.yandex.ru/|{{AUR|yandex-disk}}}}

=== FTP ===

==== FTP clients ====

See also: [[Wikipedia:Comparison of FTP client software]]

* {{App|[[CurlFtpFS]]|is a filesystem for accessing FTP hosts based on FUSE and libcurl.|https://curlftpfs.sourceforge.net/|{{Pkg|curlftpfs}}}}
* {{App|[[Wikipedia:FileZilla|FileZilla]]|Fast and reliable FTP, FTPS and SFTP client.|https://filezilla-project.org/|{{Pkg|filezilla}}}}
* {{App|ftp|Simple ftp client provided by GNU Inetutils|https://www.gnu.org/software/inetutils/manual/inetutils.html#ftp-invocation|{{Pkg|inetutils}}}}
* {{App|lftp|Sophisticated command line based FTP client|https://lftp.yar.ru/|{{Pkg|lftp}}}}
* {{App|ncftp|A set of free application programs implementing FTP.|https://www.ncftp.com/|{{Pkg|ncftp}}}}
* {{App|[[Wikipedia:tnftp|tnftp]]|FTP client with several advanced features for [[Wikipedia:NetBSD|NetBSD]].|https://freshmeat.sourceforge.net/projects/tnftp|{{Pkg|tnftp}}}}

Some file managers like [[Dolphin]], [[GNOME Files]] and [[Thunar]] also provide FTP functionality.

==== FTP servers ====

See also: [[Wikipedia:List of FTP server software]]

* {{App|bftpd|Small, easy-to-configure FTP server|https://bftpd.sourceforge.net/|{{Pkg|bftpd}}}}
* {{App|ftpd|Simple ftp server provided by GNU Inetutils|https://www.gnu.org/software/inetutils/manual/inetutils.html#ftpd-invocation|{{Pkg|inetutils}}}}
* {{App|proFTPd|A secure and configurable FTP server|http://www.proftpd.org/|{{AUR|proftpd}}}}
* {{App|[[Pure-FTPd]]|Free (BSD-licensed), secure, production-quality and standard-compliant FTP server.|https://www.pureftpd.org/project/pure-ftpd/|{{AUR|pure-ftpd}}}}
* {{App|[[vsftpd]]|Lightweight, stable and secure FTP server for UNIX-like systems.|https://security.appspot.com/vsftpd.html|{{Pkg|vsftpd}}}}

=== BitTorrent clients ===

Some [[#Download managers|download managers]] are also able to connect to the BitTorrent network: [[Aria2]], [[Wikipedia:Lftp|LFTP]], FatRat, [[Wikipedia:KGet|KGet]], [[Wikipedia:MLDonkey|MLDonkey]], uGet.

See also: [[Wikipedia:Comparison of BitTorrent clients]]

==== Console ====

* {{App|Ctorrent|CTorrent is a BitTorrent client implemented in C++ to be lightweight and quick.|http://www.rahul.net/dholmes/ctorrent/|{{AUR|enhanced-ctorrent}}}}
* {{App|[[Deluge]]|BitTorrent client with multiple user interfaces in a client/server model. This package includes a console client.|https://deluge-torrent.org/|{{Pkg|deluge}}}}
* {{App|peerflix|Streaming torrent client for node.js.|https://github.com/mafintosh/peerflix|{{AUR|peerflix}}}}
* {{App|[[rTorrent]]|Simple and lightweight ncurses BitTorrent client.|https://rakshasa.github.io/rtorrent/|{{Pkg|rtorrent}}}}
* {{App|[[Transmission]] CLI|Simple and easy-to-use BitTorrent client with a daemon version and multiple front-ends. This package includes backend, daemon, command-line interface, and a Web UI interface.|https://transmissionbt.com/|{{Pkg|transmission-cli}}}}

==== Graphical ====

* {{App|[[Deluge]] (GTK interface)|User-friendly BitTorrent client written in Python using GTK.|https://deluge-torrent.org/|{{Pkg|deluge-gtk}}}}
* {{App|Fragments|Easy to use BitTorrent client for the GNOME desktop environment.|https://apps.gnome.org/Fragments/|{{Pkg|fragments}}}}
* {{App|[[Wikipedia:FrostWire|FrostWire]]|Easy to use cloud downloader, BitTorrent client and media player.|https://www.frostwire.com/|{{AUR|frostwire}}}}
* {{App|Gopeed|Modern download manager built with Golang and Flutter that supports HTTP, BitTorrent, Magnet protocol.|https://gopeed.com/|{{AUR|gopeed-bin}}}}
* {{App|[[Ktorrent]]|Feature-rich BitTorrent client for KDE. Part of {{Grp|kde-network}}.|https://apps.kde.org/ktorrent/|{{Pkg|ktorrent}}}}
* {{App|PikaTorrent|Pick a Torrent, stream and download on all your devices.|https://www.pikatorrent.com/|{{AUR|pikatorrent-bin}}, {{AUR|pikatorrent-git}}}}
* {{App|Powder Player|Hybrid between a streaming BitTorrent client and a player. Based on the [https://electronjs.org/ Electron] platform.|https://powder.media/|{{AUR|powder-player-bin}}}}
* {{App|[[qBittorrent]]|Open source (GPLv2) BitTorrent client with an integrated torrent search engine that strongly resembles µTorrent.|https://www.qbittorrent.org/|{{Pkg|qbittorrent}}}}
* {{App|[[Wikipedia:Tixati|Tixati]]|Proprietary peer-to-peer file sharing program that uses the popular BitTorrent protocol.|https://tixati.com/|{{AUR|tixati}}}}
* {{App|[[Transmission]]|Simple and easy-to-use BitTorrent client with a daemon version and multiple front-ends.|https://transmissionbt.com/|GTK: {{Pkg|transmission-gtk}}, Qt: {{Pkg|transmission-qt}}}}
* {{App|[[Transmission]] Remote|GTK client for remote management of the Transmission BitTorrent client, using its HTTP RPC protocol.|https://github.com/transmission-remote-gtk/transmission-remote-gtk|{{Pkg|transmission-remote-gtk}}}}
* {{App|Tremotesf|Qt client for remote management of the Transmission BitTorrent client, using its HTTP RPC protocol.|https://github.com/equeim/tremotesf2|{{AUR|tremotesf}}}}
* {{App|[[Wikipedia:Tribler|Tribler]]|4th generation file sharing system BitTorrent client.|https://www.tribler.org|{{AUR|tribler-bin}}}}
* {{App|[[Wikipedia:Vuze|Vuze]]|Feature-rich BitTorrent client written in Java (formerly Azureus).|https://www.vuze.com/|{{AUR|vuze}}}}
* {{App|WebTorrent Desktop|Streaming BitTorrent application. Based on the [https://electronjs.org/ Electron] platform.|https://webtorrent.io/desktop/|{{AUR|webtorrent-desktop}}}}

=== Other P2P networks ===

See also: [[Wikipedia:Comparison of file-sharing applications]]

* {{App|[[aMule]]|Well-known eDonkey/Kad client with a daemon version and GTK, web, and CLI front-ends.|https://www.amule.org/|{{Pkg|amule}}}}
* {{App|EiskaltDC++|Direct Connect and ADC client.|https://github.com/eiskaltdcpp/eiskaltdcpp|GTK: {{AUR|eiskaltdcpp-gtk}}, Qt: {{AUR|eiskaltdcpp-qt}}}}
* {{App|[[Wikipedia:gtk-gnutella|gtk-gnutella]]|GTK server/client for the Gnutella peer-to-peer network.|https://gtk-gnutella.sourceforge.net/|{{AUR|gtk-gnutella}}}}
* {{App|[[IPFS]]|IPFS is a P2P Network capable of sharing and receiving files.|https://ipfs.io/|{{Pkg|kubo}}}}
* {{App|KaMule|KDE graphical front-end for aMule.|https://github.com/nihui/kamule/|{{AUR|kamule}}}}
* {{App|LBRY|Browser and wallet for LBRY, the decentralized, user-controlled content marketplace. Based on the [https://electronjs.org/ Electron] platform.|https://lbry.io/|{{AUR|lbry-desktop}}}}
* {{App|lbt|Small set of command-line tools for LBRY.|https://gitlab.com/gardenappl/lbt|{{AUR|lbt}}}}
* {{App|[[Wikipedia:MLDonkey|MLDonkey]]|Multi-protocol P2P client that supports HTTP, FTP, BitTorrent, Direct Connect, eDonkey and FastTrack.|https://mldonkey.sourceforge.net/|{{AUR|mldonkey}}}}
* {{App|ncdc|Modern and lightweight Direct Connect and ADC client with a friendly ncurses interface.|https://dev.yorhel.nl/ncdc|{{AUR|ncdc}}}}
* {{App|Nicotine+|A graphical client for the Soulseek P2P network.|https://github.com/Nicotine-Plus/nicotine-plus|{{Pkg|nicotine+}}}}
* {{App|Send Anywhere|Proprietary file sharing service where users can directly share digital content in real time. Based on the [https://electronjs.org/ Electron] platform.|https://send-anywhere.com/|{{AUR|sendanywhere}}}}

=== Pastebin services ===

See also: [[Wikipedia:Pastebin]]

Pastebin services are often used to quote text or images while collaborating and troubleshooting. Pastebin clients provide a convenient way to post from the command line.

{{Warning|{{ic|pastebin.com}} has a bad reputation due to its history of hosting malware, plus it requires JavaScript and displays advertisements. It is wise '''not''' to use that service and prefer alternatives listed below.}}

==== Without a dedicated client ====

Some services can be used with more general command line tool such as [[cURL]]. For extensions, such as line numbers, more command line tools can be used such as {{ic|cat -n}}.

* [https://0x0.st/ 0x0.st] is a file hosting service. Usage examples are:
:{{bc|1=$ ''command'' {{!}} curl -F 'file=@-' <nowiki>https://0x0.st</nowiki>}} or upload a file: {{bc|1=$ curl -F 'file=@''path/to/file''' <nowiki>https://0x0.st</nowiki>}}
:{{Note|Read the instructions on the website for further options such as file removal tokens, expiration, and private URLs.}}
* [https://paste.c-net.org/ paste.c-net.org] accepts HTTP requests and works with [[nc]].
* [https://privatebin.info/ privatebin.info] is a minimalist, open-source online pastebin service where the server has zero knowledge of stored data. It focuses on decentralized hosting and has a [https://privatebin.info/directory/ directory of public instances].
* [https://termbin.com termbin.com] works with [[nc]].

==== Dedicated clients ====

* {{App|Fb-client|Client for the [https://paste.xinu.at/ paste.xinu.at] pastebin.|https://paste.xinu.at|{{Pkg|fb-client}}}}
* {{App|Gist|Command-line interface for the [https://gist.github.com/ gist.github.com] pastebin service.|https://github.com/defunkt/gist|{{Pkg|gist}}}}
* {{App|imgur|A CLI client which can upload image to [https://imgur.com imgur.com] image sharing service.|https://github.com/tremby/imgur.sh|{{AUR|imgur.sh}}}}
* {{App|Pastebinit|Really small Python script that acts as a Pastebin client (see {{ic|pastebinit -l}} for the list of servers).|https://launchpad.net/pastebinit|{{Pkg|pastebinit}}}}
* {{App|ruby-haste|Client for [https://hastebin.com/ hastebin.com].|https://github.com/seejohnrun/haste-client|{{AUR|ruby-haste}}}}
* {{App|Wgetpaste|Bash script that automates pasting to a number of pastebin services.|http://wgetpaste.zlin.dk/|{{Pkg|wgetpaste}}}}

== Communication ==

=== Email clients ===

See also: [[Wikipedia:Comparison of email clients]]

==== Console ====

* {{App|[[aerc]]|Work in progress asynchronous email client.|https://sr.ht/~rjarry/aerc|{{Pkg|aerc}}}}
* {{App|alot|An experimental terminal MUA based on [https://notmuchmail.org/ notmuch mail]. It is written in python using the [https://urwid.org/ urwid] toolkit.|https://github.com/pazz/alot|{{Pkg|alot}}}}
* {{App|[[Alpine]]|Fast, easy-to-use and Apache-licensed email client based on [[Wikipedia:Pine (email client)|Pine]].|https://alpineapp.email/|{{AUR|alpine}}}}
* {{App|himalaya|Himalaya CLI is written in Rust, based on email-lib.|https://github.com/pimalaya/himalaya|{{Pkg|himalaya}}}}
* {{App|mu/mu4e|Email indexer (mu) and client for emacs (mu4e). Xapian based for fast searches.|https://www.djcbsoftware.nl/code/mu/mu4e.html|{{AUR|mu}}}}
* {{App|[[Mutt]]|Small but very powerful text-based mail client.|http://www.mutt.org/|{{Pkg|mutt}}}}
* {{App|[[Mutt|NeoMutt]]|Command line mail reader (or MUA). It is a fork of Mutt with added features.|https://neomutt.org/|{{Pkg|neomutt}}}}
* {{App|[[nmh]]|A modular mail handling system.|https://www.nongnu.org/nmh/|{{AUR|nmh}}}}
* {{App|[[notmuch]]|A fast mail indexer built on top of ''xapian''.|https://notmuchmail.org/|{{Pkg|notmuch}}}}
* {{App|sendemail|A lightweight command line SMTP email client written in Perl.|http://caspian.dotconf.net/menu/Software/SendEmail/|{{AUR|sendemail}}}}
* {{App|[[S-nail]]|a mail processing system with a command syntax reminiscent of ''ed'' with lines replaced by messages. Provides the functionality of [[Wikipedia:mailx|mailx]].|https://www.sdaoden.eu/code.html#s-mailx|{{Pkg|s-nail}}}}
* {{App|[[Sup]]|CLI mail client with very fast searching, tagging, threading and GMail like operation.|https://sup-heliotrope.github.io/|{{AUR|sup}}}}
* {{App|swaks|Swiss Army Knife SMTP; Command line SMTP testing, including TLS and AUTH, can be used to send emails.|https://jetmore.org/john/code/swaks/|{{Pkg|swaks}}}}
* {{App|Wanderlust|Email client and news reader for Emacs.|https://github.com/wanderlust/wanderlust/|{{Pkg|wanderlust}}}}

==== Graphical ====

* {{App|Balsa|Simple and light email client for GNOME.|https://pawsa.fedorapeople.org/balsa/|{{Pkg|balsa}}}}
* {{App|Betterbird|Fork of thunderbird.|https://www.betterbird.eu/|{{AUR|betterbird-bin}}}}
* {{App|[[Wikipedia:Claws Mail|Claws Mail]]|Lightweight GTK-based email client and news reader.|https://www.claws-mail.org/|{{Pkg|claws-mail}}}}
* {{App|ElectronMail|Unofficial desktop application for several end-to-end encrypted email providers (like ProtonMail, Tutanota). Based on the [https://electronjs.org/ Electron] platform.|https://github.com/vladimiry/ElectronMail|{{AUR|electronmail-bin}}}}
* {{App|[[Evolution]]|Mature and feature-rich e-mail client that is part of the GNOME project. Part of {{Grp|gnome-extra}}.|https://gitlab.gnome.org/GNOME/evolution/-/wikis/home|{{Pkg|evolution}}}}
* {{App|Geary|Simple desktop mail client built in [[Wikipedia:Vala (programming language)|Vala]]. Part of {{Grp|gnome-extra}}.|https://wiki.gnome.org/Apps/Geary|{{Pkg|geary}}}}
* {{App|[[Wikipedia:Kmail|Kmail]]|Mature and feature-rich email client. Part of {{Grp|kde-pim}}.|https://kontact.kde.org/components/kmail/|{{Pkg|kmail}}}}
* {{App|Mailspring|Fork of [[Wikipedia:Nylas Mail|Nylas Mail]] by one of the original authors. The paid "Pro" version requires a Mailspring ID and has extra features like snooze, send later. Based on the [https://electronjs.org/ Electron] platform.|https://getmailspring.com/|{{AUR|mailspring}}}}
* {{App|[[Wikipedia:SeaMonkey#Mail|SeaMonkey Mail & Newsgroups]]|Email client included in the SeaMonkey suite.|https://www.seamonkey-project.org/|{{AUR|seamonkey}}}}
* {{App|[[Thunderbird]]|Feature-rich email client from Mozilla written in GTK.|https://www.thunderbird.net/|{{Pkg|thunderbird}}}}
* {{App|Tutanota|Email client for Tutanota mail service. Based on the [https://electronjs.org/ Electron] platform.|https://tutanota.com/|{{AUR|tutanota-desktop}}}}

==== Web-based ====

* {{App|[[Nextcloud]] Mail|An email webapp for NextCloud.|https://github.com/nextcloud/mail|{{Pkg|nextcloud-app-mail}}}}
* {{App|[[Roundcube]]|Browser-based multilingual IMAP client webapp with a native application-like user interface.|https://roundcube.net/|{{Pkg|roundcubemail}}}}
* {{App|SquirrelMail|Webmail for Nuts!|https://squirrelmail.org/|{{AUR|squirrelmail}}}}

=== Mail notifiers ===

* {{App|Ayatana Webmail|Webmail notifications and actions for any desktop.|https://tari.in/www/software/ayatana-webmail/{{Dead link|2025|08|15|status=404}}|{{AUR|ayatana-webmail}}}}
* {{App|Bubblemail|New and Unread mail notification service for local mailboxes, pop, imap, and gnome online accounts. A fork of Mailnag.|http://bubblemail.free.fr/|{{AUR|bubblemail}}}}
* {{App|Gnubiff|Mail notification program that checks for mail and displays headers when new mail has arrived.|https://gnubiff.sourceforge.net/|{{Pkg|gnubiff}}}}
* {{App|Mailnag|Extensible mail notification daemon.|https://github.com/pulb/mailnag|{{Pkg|mailnag}}}}

=== Mail servers ===

See [[Mail server]].

* {{App|DavMail|POP/IMAP/SMTP/Caldav/Carddav/LDAP exchange gateway allowing users to use any mail/calendar client with an Exchange server.|https://davmail.sourceforge.net/|{{AUR|davmail}}}}
* {{App|Modoboa|A modular mail hosting and management platform, written in Python.|https://modoboa.org/|{{AUR|modoboa}}}}

=== Mail retrieval agents ===

See also: [[Wikipedia:Mail retrieval agent]]

* {{App|[[fdm]]|Program to fetch and deliver mail.|https://github.com/nicm/fdm|{{Pkg|fdm}}}}
* {{App|[[Wikipedia:Fetchmail|Fetchmail]]|A remote-mail retrieval utility.|https://www.fetchmail.info/|{{Pkg|fetchmail}}}}
* {{App|[[getmail]]|A POP3/IMAP4 mail retriever with reliable Maildir and command delivery.|http://pyropus.ca/software/getmail/|{{AUR|getmail}}}}
* {{App|hydroxide|A third-party, open-source ProtonMail CardDAV, IMAP and SMTP bridge|https://github.com/emersion/hydroxide|{{AUR|hydroxide}}}}
* {{App|imapsync|IMAP synchronisation, sync, copy or migration tool|https://imapsync.lamiral.info/|{{Pkg|imapsync}}}}
* {{App|[[isync]]|IMAP and MailDir mailbox synchronizer|https://isync.sourceforge.net/|{{Pkg|isync}}}}
* {{App|mpop|A small, fast POP3 client suitable as a fetchmail replacement|https://marlam.de/mpop/|{{Pkg|mpop}}}}
* {{App|[[OfflineIMAP]]|Synchronizes emails between two repositories.|https://www.offlineimap.org/|{{Pkg|offlineimap}}}}
* {{App|vomit|Rust utility to sync between Maildir mailbox and IMAP mailbox|https://git.sr.ht/~bitfehler/vomit-sync/tree/master/item/cli/README.md|{{AUR|vsync}} (sync-only part of {{AUR|vomit}} mail tookit)}}

=== Instant messaging clients ===

See also: [[Wikipedia:Comparison of instant messaging clients]], [[Wikipedia:Comparison of VoIP software]]

This section lists all client software with [[Wikipedia:Instant messaging|instant messaging]] support.

==== Multi-protocol clients ====

{{Note|All messengers that support several networks by means of direct connections to them belong to this section.}}

The number of networks supported by these clients is very large but they (like any multi-protocol clients) usually have very limited or no support for network-specific features.

===== Console =====

* {{App|[[Bitlbee|BitlBee]]|IRC gateway to popular chat networks.|https://bitlbee.org/|{{AUR|bitlbee}}}}
* {{App|Finch|Ncurses-based chat client that uses libpurple and supports all its protocols (Bonjour, Gadu-Gadu, Groupwise, IRC, SIMPLE, XMPP, Zephyr).|https://developer.pidgin.im/wiki/Using%20Finch|{{AUR|finch}}}}
* {{App|[[WeeChat]]|Modular, lightweight ncurses-based IRC client. A variety of other protocols are supported through plugins.|https://weechat.org/|{{Pkg|weechat}}}}

===== Graphical =====

* {{App|[[Wikipedia:Jitsi|Jitsi]]|Audio/video VoIP phone and instant messenger written in Java that supports protocols such as SIP, XMPP, IRC and many other useful features.|https://jitsi.org/|{{AUR|jitsi}}}}
* {{App|Lith|WeeChat Relay client, allowing to connect to a running WeeChat instance from anywhere.|https://lith.app/|{{AUR|lith-git}}}}
* {{App|[[Pidgin]]|Multi-protocol instant messaging client with audio support that uses libpurple and supports all its protocols (Bonjour, Gadu-Gadu, Groupwise, IRC, SIMPLE, XMPP, Zephyr).|https://pidgin.im/|{{AUR|pidgin}}}}
* {{App|[[Wikipedia:Smuxi|Smuxi]]|Cross-platform IRC client that also supports XMPP.|https://smuxi.im/|{{AUR|smuxi}}}}
* {{App|[[Thunderbird]]|Feature-rich email client supports instant messaging and chat using IRC and XMPP.|https://www.thunderbird.net/|{{Pkg|thunderbird}}}}
* {{App|glowing-bear-electron|A web client for WeeChat|https://glowing-bear.org/|{{AUR|glowing-bear-electron}}}}

==== IRC clients ====

See also: [[Wikipedia:Comparison of Internet Relay Chat clients]]

===== Console =====

* {{App|[[Wikipedia:BitchX|BitchX]]|Console-based IRC client developed from the popular [[Wikipedia:ircII|ircII]].|https://bitchx.sourceforge.net/|{{AUR|bitchx-git}}}}
* {{App|catgirl|TLS-only terminal IRC client.|https://git.causal.agency/catgirl|{{AUR|catgirl}}}}
* {{App|ERC|Powerful, modular and extensible IRC client for [[Emacs]].|https://savannah.gnu.org/projects/erc/|included with {{Pkg|emacs}}}}
* {{App|[[ii]]|Featherweight IRC client, literally {{ic|tail -f}} the conversation and {{ic|echo}} back your replies to a file.|https://tools.suckless.org/ii/|{{AUR|ii}}}}
* {{App|ircii|Oldest maintained IRC client which lays claim to being small and fast owing to its reduced feature set.|http://www.eterna23.net/ircii/|{{AUR|ircii}}}}
* {{App|[[Irssi]]|Highly-configurable ncurses-based IRC client.|https://irssi.org/|{{Pkg|irssi}}}}
* {{App|pork|Programmable, ncurses-based IRC client that mostly looks and feels like ircII.|http://dev.ojnk.net/|{{Pkg|pork}}}}
* {{App|ScrollZ|Advanced IRC client based on [[Wikipedia:ircII|ircII]].|https://www.scrollz.info/|{{AUR|scrollz}}}}
* {{App|senpai|An IRC client that works best with bouncers (e.g. {{Pkg|soju}}): no logs are kept, history is fetched from the server via [https://ircv3.net/specs/extensions/chathistory CHATHISTORY], networks are fetched from the server via [https://git.sr.ht/~emersion/soju/tree/master/item/doc/ext/bouncer-networks.md bouncer-networks].
|https://sr.ht/~delthas/senpai/|{{Pkg|senpai}}}}
* {{App|sic|Extremely simple IRC client, similar to [[Wikipedia:Ii (IRC client)|ii]].|https://tools.suckless.org/sic/|{{AUR|sic}}}}
* {{App|tiny|an IRC client written in Rust with a clutter-free interface|https://github.com/osa1/tiny|{{Pkg|tiny}}}}

===== Graphical =====

* {{App|[[Wikipedia:ChatZilla|ChatZilla]]|Clean, easy to use and highly extensible Internet Relay Chat (IRC) client, built on the Mozilla platform using [[Wikipedia:XULRunner|XULRunner]]. Included in the [[Wikipedia:SeaMonkey|SeaMonkey]] suite.|http://chatzilla.hacksrus.com/|{{AUR|seamonkey}}}}
* {{App|Halloy|An open-source IRC client written in Rust, with the iced GUI library.|https://halloy.squidowl.org/|{{Pkg|halloy}}}}
* {{App|[[HexChat]]|Fork of XChat for Linux and Windows.|https://hexchat.github.io/|{{AUR|hexchat}}}}
* {{App|[[Wikipedia:Konversation|Konversation]]|Qt-based IRC client for the KDE desktop. Part of {{Grp|kde-network}}.|https://konversation.kde.org/|{{Pkg|konversation}}}}
* {{App|[[Wikipedia:KVIrc|KVIrc]]|Qt-based IRC client featuring extensive themes support.|https://kvirc.net/|{{Pkg|kvirc}}}}
* {{App|Loqui|GTK IRC client.|https://loqui.sunnyone.org/|{{AUR|loqui}}}}
* {{App|LostIRC|Simple GTK IRC client with tab-autocompletion, multiple server support, logging and others.|https://lostirc.sourceforge.net|{{AUR|lostirc}}}}
* {{App|Polari|Simple IRC client by the GNOME project. Part of {{Grp|gnome-extra}}.|https://apps.gnome.org/Polari/|{{Pkg|polari}}}}
* {{App|[[Quassel]]|Modern, cross-platform, distributed IRC client.|https://quassel-irc.org/|KDE: {{Pkg|quassel-monolithic}}, Qt: {{Pkg|quassel-monolithic-qt}}}}
* {{App|Srain|Modern, beautiful IRC client written in GTK 3.|https://srain.silverrainz.me|{{AUR|srain}}}}
* {{App|Thelounge|Modern self-hosted web IRC client|https://thelounge.chat/|{{AUR|thelounge}}}}

==== XMPP clients ====

See also: [[Wikipedia:XMPP]]

===== Console =====

* {{App|Freetalk|Console-based XMPP client.|https://www.gnu.org/software/freetalk/|{{AUR|freetalk}}}}
* {{App|jabber.el|Minimal XMPP client for [[Emacs]].|https://emacs-jabber.sourceforge.net/|{{AUR|emacs-jabber}}}}
* {{App|MCabber|Small XMPP console client, includes features: SSL, PGP, MUC, OTR and UTF8.|https://mcabber.com/|{{Pkg|mcabber}}}}
* {{App|Poezio|XMPP client with IRC feeling|https://poez.io/|{{AUR|poezio}}}}
* {{App|Profanity|A console based XMPP client inspired by Irssi.|https://profanity-im.github.io/|{{Pkg|profanity}}}}

===== Graphical =====

* {{App|Converse.js|Web-based XMPP chat client written in JavaScript.|https://conversejs.org/|{{AUR|conversejs}}}}
* {{App|Dino|A modern, easy to use XMPP client, with PGP and OMEMO support.|https://dino.im/|{{Pkg|dino}}}}
* {{App|[[Gajim]]|XMPP client with audio support written in Python using GTK.|https://gajim.org/|{{Pkg|gajim}}}}
* {{App|Kaidan|A simple, user-friendly Jabber/XMPP client providing a modern user interface using Kirigami and QtQuick.|https://www.kaidan.im/|{{Pkg|kaidan}}}}
* {{App|Libervia (Salut à Toi)|Web frontend for Salut à Toi, multi-purpose XMPP client|https://libervia.org/|{{AUR|libervia-web-hg}}}}
* {{App|Nextcloud JavaScript XMPP Client|Chat app for Nextcloud with XMPP, end-to-end encryption, video calls, file transfer & group chat.|https://github.com/nextcloud/jsxc.nextcloud|{{AUR|nextcloud-app-jsxc}}}}
* {{App|[[Wikipedia:Psi (instant messaging client)|Psi]]|Qt-based XMPP client.|https://psi-im.org/|{{Pkg|psi}}}}
* {{App|[[Wikipedia:Spark (XMPP client)|Spark]]|Cross-platform real-time XMPP collaboration client optimized for business and organizations.|https://www.igniterealtime.org/projects/spark/|{{AUR|spark}}}}
* {{App|Swift|XMPP client written in C++ with Qt and Swiften.|https://swift.im/|{{AUR|swift-im}}}}
* {{App|[[Wikipedia:Tkabber|Tkabber]]|Easy to hack feature-rich XMPP client by the author of the ejabberd XMPP server.|https://tkabber.jabber.ru/|{{AUR|tkabber}}}}
* {{App|Vacuum IM|Full-featured crossplatform XMPP client.|https://github.com/Vacuum-IM/vacuum-im|{{AUR|vacuum-im}}}}

==== SIP clients ====

See also: [[Wikipedia:List of SIP software#Clients]]

* {{App|baresip|portable and modular SIP User-Agent with audio and video support.|https://github.com/baresip/baresip|{{Pkg|baresip}}}}
* {{App|[[Wikipedia:Blink (SIP client)|Blink]]|State of the art, easy to use SIP client.|https://icanblink.com/|{{AUR|blink}}}}
* {{App|Calls|Simple, elegant phone dialer and call handler for GNOME. It can be used with a cellular modem for plain old telephone calls as well as VoIP calls using the SIP protocol.|https://gitlab.gnome.org/GNOME/calls|{{Pkg|gnome-calls}}}}
* {{App|Jami|SIP-compatible softphone and instant messenger for the decentralized Jami network. Formerly known as Ring and SFLphone.|https://jami.net/|{{Pkg|jami-qt}}}}
* {{App|[[Wikipedia:Linphone|Linphone]]|VoIP phone application (SIP client) for communicating freely with people over the internet, with voice, video, and text instant messaging.|https://www.linphone.org/|{{AUR|linphone-desktop}}}}
* {{App|[[Wikipedia:Twinkle (software)|Twinkle]]|Qt softphone for VoIP and IM communication using SIP.|http://twinkle.dolezel.info/|{{AUR|twinkle}}}}
* {{App|Zoiper|Proprietary SIP and IAX2 VoIP softphone|https://zoiper.com|{{AUR|zoiper-bin}}}}

==== Matrix clients ====

See also: [[Matrix]], [https://matrix.org/clients/ Matrix Clients]

* {{App|Chatty|Simple to use SMS and Matrix messaging application.|https://gitlab.gnome.org/World/Chatty|{{Pkg|chatty}}}}
* {{App|Cinny|Cinny is a matrix client focusing primarily on simple, elegant and secure interface. The desktop app is made with [https://github.com/tauri-apps/tauri Tauri].|https://github.com/cinnyapp/cinny-desktop|{{AUR|cinny-desktop}}}}
* {{App|Element|Glossy Matrix client with an emphasis on performance and usability. Web application and desktop application based on the [https://electronjs.org/ Electron] platform.|https://element.io/|{{Pkg|element-web}}, {{Pkg|element-desktop}}}}
* {{App|FluffyChat|Multi-platform Matrix client with a simple and clean UI written in Dart/Flutter.|https://fluffychat.im/|{{AUR|fluffychat}}}}
* {{App|Fractal|Matrix client for GNOME written in Rust.|https://wiki.gnome.org/Apps/Fractal|{{Pkg|fractal}}}}
* {{App|Gomuks|Terminal Matrix client written in Go using [https://github.com/tulir/mautrix-go mautrix] and [https://github.com/tulir/mauview mauview].|https://maunium.net/go/gomuks|{{Pkg|gomuks}}}}
* {{App|iamb|A terminal-based Matrix client with Vim keybindings written in Rust.|https://github.com/ulyssa/iamb|{{Aur|iamb}}}}
* {{App|Moment|A fancy, customizable, keyboard-operable Matrix chat client for encrypted and decentralized communication. Written in Qt/QML + Python with nio, fork of the now-abandoned Mirage.|https://mx-moment.xyz/|{{AUR|moment}}}}
* {{App|Neochat|KDE client for the Matrix protocol. Part of {{Grp|kde-network}}.|https://apps.kde.org/neochat/|{{Pkg|neochat}}}}
* {{App|nheko|Desktop client for the Matrix protocol.|https://github.com/Nheko-Reborn/nheko|{{Pkg|nheko}}}}
* {{App|Quaternion|Qt5-based IM client for the Matrix protocol.|https://github.com/QMatrixClient/Quaternion|{{AUR|quaternion}}}}
* {{App|QuickMedia|A rofi inspired native client for web services. Supports Matrix and several other sites.|https://git.dec05eba.com/QuickMedia/about/|{{AUR|quickmedia}}}}
* {{App|SchildiChat|Matrix client based on Element with a more traditional instant messaging experience. Based on the [https://electronjs.org/ Electron] platform.|https://schildi.chat/|{{AUR|schildichat-desktop-eol}}}}
* {{App|Spectral|Qt5-based Glossy cross-platform client for Matrix.|https://gitlab.com/spectral-im/spectral|{{AUR|spectral-matrix}}}}
* {{App|Syphon|Privacy-centric cross-platform Matrix client with E2EE support, currently in alpha.|https://github.com/syphon-org/syphon|{{AUR|syphon-bin}}}}

==== Tox clients ====

See also: [[Tox]], [https://wiki.tox.chat/clients Comparison of Tox clients]

* {{App|ratox|FIFO based tox client.|https://git.z3bra.org/ratox/file/README.html|{{AUR|ratox-git}}}}
* {{App|Toxic|ncurses-based Tox client|https://github.com/Jfreegman/toxic|{{Pkg|toxic}}}}
* {{App|Venom|a modern Tox client for the GNU/Linux desktop|https://github.com/naxuroqa/Venom|{{AUR|venom}}}}
* {{App|µTox|Lightweight Tox client.|https://github.com/uTox/uTox|{{Pkg|utox}}}}

==== LAN messengers ====

See also: [[Avahi#Link-Local (Bonjour/Zeroconf) chat]], [[Wikipedia:Comparison of LAN messengers]]

* {{App|BeeBEEP|Secure LAN Messenger.|https://www.beebeep.net/|{{AUR|beebeep}}}}
* {{App|iptux|LAN communication software, compatible with IP Messenger.|https://github.com/iptux-src/iptux|{{Pkg|iptux}}}}

==== P2P messaging clients ====

See also: [[Ring]], [[Tox]]

* {{App|[[Wikipedia:Briar (software)|Briar]]|Briar is a messaging application designed for activists, journalists, and anyone else who needs a safe, easy and robust way to communicate.|https://briarproject.org/|{{AUR|briar-desktop}}, {{AUR|briar-headless}}}}
* {{App|Manyverse|Modern decentralized messaging and sharing application built on top of Secure Scuttlebutt (SSB).|https://gitlab.com/staltz/manyverse|{{AUR|manyverse-bin}}}}
* {{App|Patchwork|Decentralized messaging and sharing application built on top of Secure Scuttlebutt (SSB). Based on the [https://electronjs.org/ Electron] platform.|https://github.com/ssbc/patchwork|{{AUR|ssb-patchwork}}}}
* {{App|Poncho Wonky|Decentralized messaging and sharing application built on top of Secure Scuttlebutt (SSB). Based on the [https://electronjs.org/ Electron] platform. Maintained, updated Fork of Patchwork|https://github.com/soapdog/patchwork/|{{AUR|poncho-wonky}}}}
* {{App|RetroShare|Serverless encrypted instant messenger with filesharing, chatgroups, mail.|https://retroshare.cc/|{{AUR|retroshare}}}}
* {{App|[[Wikipedia:Ricochet (software)|Ricochet]]|Anonymous peer-to-peer instant messaging system built on [[Tor]] hidden services.|https://www.ricochetrefresh.net/|{{AUR|ricochet-refresh}}}}

==== Chatmail clients ====

* {{App|Delta Chat|A privacy oriented [https://chatmail.at/ chatmail] application. Based on the [https://electronjs.org/ Electron] platform.|https://delta.chat/|{{Pkg|deltachat-desktop}}}}
* {{App|Parla|A [https://chatmail.at/ chatmail] application for the [[GNOME]] desktop. Based on the [[GTK]] framework.|https://github.com/trufae/parla/|{{Pkg|parla}}}}

==== Other IM clients ====

* {{App|Caprine|Unofficial Facebook Messenger app. Based on the [https://electronjs.org/ Electron] platform.|https://github.com/sindresorhus/caprine|{{AUR|caprine}}}}
* {{App|Chatterino|Chat client for Twitch chat.|https://chatterino.com/|{{AUR|chatterino2}}}}
* {{App|[[Discord]]|Proprietary all-in-one voice and text chat application for gamers that’s free and works on both your desktop and phone. Based on the [https://electronjs.org/ Electron] platform.|https://discordapp.com/|{{Pkg|discord}}}}
* {{App|Flare|Unofficial Signal client based on GTK.|https://gitlab.com/schmiddi-on-mobile/flare|{{AUR|flare}}}}
* {{App|[[Wikipedia:Gitter|Gitter]]|Communication product for communities and teams on GitLab and GitHub.|https://gitter.im/|{{AUR|gitter-bin}}}}
* {{App|[[Wikipedia:Jitsi|Jitsi]] Meet|Desktop application for Jitsi Meet. Based on the [https://electronjs.org/ Electron] platform.|https://github.com/jitsi/jitsi-meet-electron|{{AUR|jitsi-meet-desktop}}}}
* {{App|Kotatogram Desktop|Experimental fork of Telegram Desktop.|https://kotatogram.github.io/|{{AUR|kotatogram-desktop}}}}
* {{App|Matterhorn|Console client for the Mattermost chat system.|https://github.com/matterhorn-chat/matterhorn|{{AUR|matterhorn}}}}
* {{App|[[Mattermost]] Desktop|Desktop application for Mattermost. Based on the [https://electronjs.org/ Electron] platform.|https://github.com/mattermost/desktop|{{Pkg|mattermost-desktop}}}}
* {{App|[[Mumble]]|Voice chat application similar to TeamSpeak.|https://www.mumble.info/|{{Pkg|mumble}}}}
* {{App|Paper Plane|Chat over Telegram on a modern and elegant client.|https://github.com/paper-plane-developers/paper-plane|{{AUR|paper-plane}}}}
* {{App|[[QQ]]|Proprietary instant messaging software developed by Tencent (imitating ICQ).|https://im.qq.com/|{{AUR|linuxqq}}}}
* {{App|Rocket.Chat Desktop|Desktop application for Rocket.Chat. Based on the [https://electronjs.org/ Electron] platform.|https://github.com/RocketChat/Rocket.Chat.Electron|{{AUR|rocketchat-desktop}}}}
* {{App|Ruqola|Rocket.Chat client for the KDE desktop.|https://apps.kde.org/ruqola/|{{AUR|ruqola}}}}
* {{App|Session Desktop|Onion routing based messenger. Based on the [https://electronjs.org/ Electron] platform.|https://getsession.org/|{{AUR|session-desktop}}}}
* {{App|[[Wikipedia:Signal (software)|Signal]] Desktop|Desktop application for Signal private messenger. Based on the [https://electronjs.org/ Electron] platform.|https://github.com/signalapp/Signal-Desktop|{{Pkg|signal-desktop}}}}
* {{App|[[Wikipedia:Slack (software)|Slack]]|Proprietary Slack client for desktop. Based on the [https://electronjs.org/ Electron] platform.|https://slack.com/|{{AUR|slack-desktop}}}}
* {{App|teams-for-linux|Unofficial Microsoft Teams for Linux client. Based on the [https://electronjs.org/ Electron] platform.|https://github.com/IsmaelMartinez/teams-for-linux|{{AUR|teams-for-linux}}}}
* {{App|[[TeamSpeak]]|Proprietary VoIP application with gamers as its target audience.|https://www.teamspeak.com/|{{Pkg|teamspeak3}}}}
* {{App|[[TeamTalk]]|Proprietary VoIP application with video chat, file and desktop sharing. Desktop sharing does not appear to be working in Linux though. AUR package is server only, but client is built in the make process.|https://bearware.dk|{{AUR|teamtalk}}}}
* {{App|[[Telegram]] Desktop|Official Telegram desktop client.|https://desktop.telegram.org/|{{Pkg|telegram-desktop}}}}
* {{App|[[Wikipedia:Viber|Viber]]|Proprietary cross-platform IM and VoIP software.|https://www.viber.com/products/linux/|{{AUR|viber}}}}
* {{App|[[Wikipedia:WeChat|WeChat]]|Tencent WeChat Client.|https://linux.weixin.qq.com/|{{AUR|wechat}}}}
* {{App|[[Wikipedia:Wire (software)|Wire]]|Modern, private messenger. Based on the [https://electronjs.org/ Electron] platform.|https://wire.com/|{{AUR|wire-desktop}}}}
* {{App|[[Zoom Meetings|Zoom]]|Proprietary video conferencing, online meetings and group messaging application.|https://zoom.us/|{{AUR|zoom}}}}
* {{App|[[Wikipedia:Zulip|Zulip]]|Desktop client for Zulip group chat. Based on the [https://electronjs.org/ Electron] platform.|https://zulipchat.com/apps/linux|{{AUR|zulip-desktop}}}}

=== Instant messaging servers ===

See also: [[Wikipedia:Comparison of instant messaging protocols]]

==== IRC servers ====

* {{App|Ergo|A modern and simple to set up IRC server written in Go. Combines the features of an IRCd, a services framework, and a bouncer.|https://ergo.chat/|{{AUR|ergochat}}}}
* {{App|[[InspIRCd]]|A stable, modern and lightweight IRC daemon.|https://www.inspircd.org/|{{AUR|inspircd}}}}
* {{App|IRCD-Hybrid|A lightweight, high-performance internet relay chat daemon.|https://www.ircd-hybrid.org/|{{AUR|ircd-hybrid}}}}
* {{App|miniircd|A small and configuration free IRC server, suitable for private use.|https://github.com/jrosdahl/miniircd|{{AUR|miniircd-git}}}}
* {{App|ngIRCd|A free, portable and lightweight Internet Relay Chat server for small or private networks.|https://ngircd.barton.de/|{{AUR|ngircd}}}}
* {{App|Solanum|Solanum is the upcoming IRCd for unified networks that is being worked on by a collaboration of Libera Chat and OFTC staff.|https://solanum.chat/|{{AUR|solanum-ircd-git}}}}
* {{App|[[UnrealIRCd]]|Open Source IRC Server.|https://www.unrealircd.org/|{{Pkg|unrealircd}}}}

==== XMPP servers ====

* {{App|Ejabberd|Robust, scalable and extensible XMPP Server written in Erlang|https://www.ejabberd.im/|{{Pkg|ejabberd}}}}
* {{App|Jabberd2|An XMPP server written in the C language and licensed under the GNU General Public License. It was inspired by jabberd14.|https://jabberd2.org/|{{AUR|jabberd2}}}}
* {{App|[[Openfire]]|An XMPP IM multiplatform server written in Java|https://www.igniterealtime.org/projects/openfire/|{{Pkg|openfire}}}}
* {{App|[[Prosody]]|An XMPP server written in the [https://www.lua.org/ Lua] programming language. Prosody is designed to be lightweight and highly extensible. It is licensed under a permissive [https://prosody.im/source/mit MIT license].|https://prosody.im/|{{Pkg|prosody}}}}

==== SIP servers ====

See also: [[Wikipedia:List of SIP software#Servers]]

* {{App|[[Asterisk]]|A complete PBX solution.|https://www.asterisk.org/|{{AUR|asterisk}}}}
* {{App|Kamailio|SIP server for large VoIP and real-time communication platforms.|https://www.kamailio.org/|{{AUR|kamailio}}}}
* {{App|openSIPS|SIP proxy/server for voice, video, IM, presence and any other SIP extensions.|https://opensips.org/|{{Pkg|opensips}}}}
* {{App|Repro|An open-source, free SIP server.|https://www.resiprocate.org/About_Repro{{Dead link|2025|04|05|status=404}}|{{AUR|repro}}}}
* {{App|[[Wikipedia:Yate (telephony engine)|Yate]]|Advanced, mature, flexible telephony server that is used for VoIP and fixed networks, and for traditional mobile operators and MVNOs.|https://yate.ro/|{{Pkg|yate}}}}

==== Other IM servers ====

* {{App|[[Mattermost]]|Open source private cloud server, Slack-alternative.|https://github.com/mattermost/mattermost-server|{{Pkg|mattermost}}}}
* {{App|[[Murmur]]|The voice chat application server for Mumble.|https://www.mumble.info/|{{Pkg|mumble-server}}}}
* {{App|Nextcloud Talk|Video- and audio-conferencing app for Nextcloud.|https://github.com/nextcloud/spreed|{{Pkg|nextcloud-app-spreed}}}}
* {{App|Rocket.Chat|Web chat server, developed in JavaScript, using the Meteor fullstack framework.|https://github.com/RocketChat/Rocket.Chat|{{AUR|rocketchat-server}}}}
* {{App|[[Matrix|Synapse]]|Reference homeserver for the Matrix protocol.|https://github.com/matrix-org/synapse|{{Pkg|matrix-synapse}}}}
* {{App|[[TeamSpeak]] Server|Proprietary VoIP conference server.|https://teamspeak.com/|{{Pkg|teamspeak3-server}}}}
* {{App|uMurmur|Minimalistic Mumble server.|https://umurmur.net/|{{Pkg|umurmur}}}}

=== Collaborative software ===

See also: [[Wikipedia:Collaborative software]]

* {{App|[[SOGo]]|Groupware server built around OpenGroupware.org (OGo) and the SOPE application server.|https://sogo.nu/|{{AUR|sogo}}}}

=== Link shortening servers ===

* {{App|microbin|A tiny, self-contained, configurable paste bin and URL shortener written in Rust.|https://github.com/szabodanika/microbin|{{AUR|microbin}}}}
* {{App|shlink|Self-proclaimed definitive self-hosted URL shortener.|https://shlink.io/|{{AUR|shlink}}}}
* {{App|YOURLS|A self-hosted link shortening service written in PHP.|https://yourls.org/|{{AUR|yourls}}}}

== News, RSS, and blogs ==

=== News aggregators ===

[[Web feed]]s aggregators. Some [[#Email clients|email clients]] are also able to act as news aggregator: [[Wikipedia:Claws Mail|Claws Mail]] RSSyl plugin, [[Evolution]], [[Wikipedia:SeaMonkey#Mail|SeaMonkey Mail & Newsgroups]], [[Thunderbird]].

See also: [[Wikipedia:Comparison of feed aggregators]]

==== Console ====

* {{App|Bulletty|Pretty TUI RSS reader that locally stores articles as markdown.|https://bulletty.croci.dev/|{{Pkg|bulletty}}}}
* {{App|[[Wikipedia:Canto (news aggregator)|Canto]]|Ncurses RSS aggregator.|https://github.com/themoken/canto-curses|{{Pkg|canto-curses}}}}
* {{App|Ditch The Bell|A highly configurable Linux-based desktop notifier for RSS/Atom feeds.|https://github.com/eschermoore/ditchthebell|{{AUR|dtbell-git}}}}
* {{App|feed2imap-go|[https://github.com/feed2imap/feed2imap feed2imap] reimplemented in Go that aggregating RSS/Atom/jsonfeed into folders of your IMAP mailbox.|https://github.com/Necoro/feed2imap-go|{{AUR|feed2imap-go}}}}
* {{App|[[Wikipedia:Gnus|Gnus]]|Email, NNTP and RSS client for Emacs.|https://www.gnus.org/|{{Pkg|emacs}}}}
* {{App|[[Newsboat]]|Ncurses RSS aggregator with layout and keybinding similar to the [[Mutt]] email client.|https://newsboat.org/|{{Pkg|newsboat}}}}
* {{App|[[Newsraft]]|Feed reader with ncurses user interface. It is greatly inspired by [[Newsboat]] and tries to be its lightweight counterpart. |https://codeberg.org/newsraft/newsraft/|{{AUR|newsraft}}}}
* {{App|Rawdog|"RSS Aggregator Without Delusions Of Grandeur" that parses RSS/CDF/Atom feeds into a static HTML page of articles in chronological order.|https://offog.org/code/rawdog/|{{AUR|rawdog}}}}
* {{App|rss2email|Aggregating your RSS/Atom feed into your IMAP/Maildir mailbox as a cronjob.|https://github.com/rss2email/rss2email|{{Pkg|rss2email}}}}
* {{App|sfeed|Crontab oriented shell-scriptable feed aggregator setup with an RSS/Atom parser utility plus a simple ncurses reader.|https://codemadness.org/sfeed-simple-feed-parser.html|{{AUR|sfeed}}}}
* {{App|Snownews|Text mode RSS news reader.|https://sourceforge.net/projects/snownews/|{{AUR|snownews}}}}

==== Graphical ====

* {{App|[[Wikipedia:Kontact#News feed aggregator|Akregator]]|News aggregator for KDE, part of {{Grp|kde-pim}}.|https://apps.kde.org/akregator/|{{Pkg|akregator}}}}
* {{App|Alligator|Kirigami-based RSS/Atom feed reader for mobile devices. Part of {{Grp|kde-network}}.|https://apps.kde.org/alligator/|{{Pkg|alligator}}}}
* {{App|Feeds|An RSS/Atom feed reader for GNOME.|https://gfeeds.gabmus.org/|{{Pkg|gfeeds}}}}
* {{App|Fluent Reader|Modern desktop RSS reader built with React and Fluent UI. Based on the [https://electronjs.org/ Electron] platform.|https://hyliu.me/fluent-reader/|{{AUR|fluent-reader}}}}
* {{App|HackUp|Read Hacker News from the desktop.|https://github.com/mdh34/hackup|{{AUR|hackup-git}}}}
* {{App|[[Wikipedia:Liferea|Liferea]]|GTK news aggregator for online news feeds and weblogs.|https://lzone.de/liferea/|{{Pkg|liferea}}}}
* {{App|Newsflash|Modern feed reader designed for the GNOME desktop. The spiritual successor to FeedReader.|https://apps.gnome.org/NewsFlash/|{{Pkg|newsflash}}}}
* {{App|Raven|Simple desktop RSS reader made using VueJS. Based on the [https://electronjs.org/ Electron] platform.|https://ravenreader.app/|{{AUR|raven-reader}}}}
* {{App|RSS Guard|Very tiny RSS and ATOM news reader developed using Qt framework.|https://github.com/martinrotter/rssguard|{{Pkg|rssguard}}}}
* {{App|Tickr|GTK-based RSS Reader that displays feeds as a smooth scrolling line on your desktop, as known from TV stations.|https://www.open-tickr.net/|{{AUR|tickr}}}}

==== Graphical, Web-based ====

* {{App|[[Nextcloud]] News|RSS/Atom feed reader for Nextcloud.|https://github.com/nextcloud/news|{{Pkg|nextcloud-app-news}}}}
* {{App|selfoss|The new multipurpose RSS reader, live stream, mashup, aggregation web application.|https://selfoss.aditu.de/|{{AUR|selfoss}}}}
* {{App|[[Tiny Tiny RSS]]|Web-based news feed (RSS/Atom) aggregator.|https://tt-rss.org/|{{Pkg|tt-rss}}}}

=== Podcast clients ===

Some media players are also able to act as podcast client: [[Amarok]], Cantata, [[Wikipedia:Clementine (software)|Clementine]], Goggles Music Manager, [[Wikipedia:Rhythmbox|Rhythmbox]], [[VLC media player]]. [[Wikipedia:git-annex|git-annex]] can also [https://git-annex.branchable.com/tips/downloading_podcasts/ function as podcatcher].

See also: [[Wikipedia:List of podcatchers]]

==== Console ====

* {{App|castero|A TUI podcast client for the terminal.|https://github.com/xgi/castero|{{AUR|castero-git}}}}
* {{App|castget|Simple, command-line RSS enclosure downloader, primarily intended for automatic, unattended downloading of podcasts.|https://castget.johndal.com/|{{Pkg|castget}}}}
* {{App|gpo|Text mode interface of gPodder.|https://gpodder.github.io/|{{Pkg|gpodder}}}}
* {{App|Greg|A command-line podcast aggregator.|https://github.com/manolomartinez/greg|{{AUR|greg-git}}}}
* {{App|pcd|A minimal podcast client written in go|https://github.com/kvannotten/pcd|{{AUR|pcd}}}}

==== Graphical ====

* {{App|gPodder|Podcast client and media aggregator (GTK interface).|https://gpodder.github.io/|{{Pkg|gpodder}}}}
* {{App|Kasts|Convergent podcast application that looks good on desktop and mobile. Part of {{Grp|kde-multimedia}}.|https://apps.kde.org/kasts/|{{Pkg|kasts}}}}
* {{App|Pocket Casts|Electron wrapper around the Pocket Casts web app with support for MPRIS (media controls).|https://pocketcasts.com/|{{AUR|pocket-casts-linux}}}}
* {{App|Podcasts|Podcast client for the GNOME desktop written in Rust.|https://apps.gnome.org/Podcasts/|{{Pkg|gnome-podcasts}}}}
* {{App|Vocal|Simple podcast client for the Modern Desktop (GTK).|https://vocalproject.net/|{{AUR|vocal}}}}

=== Usenet newsreaders ===

Some [[#Email clients|email clients]] are also able to act as Usenet newsreader: [[Wikipedia:Claws Mail|Claws Mail]], [[Evolution]], [[Mutt|NeoMutt]], [[Wikipedia:SeaMonkey#Mail|SeaMonkey Mail & Newsgroups]], [[Wikipedia:Sylpheed|Sylpheed]], [[Thunderbird]].

See also: [[Wikipedia:List of Usenet newsreaders]], [[Wikipedia:Comparison of Usenet newsreaders]]

==== Console ====

* {{App|nn|Alternative more user-friendly (curses-based) Usenet newsreader for UNIX.|http://www.nndev.org/|{{AUR|nn}}}}
* {{App|[[Wikipedia:slrn|slrn]]|Text-based news client.|https://www.slrn.org/|{{AUR|slrn}}}}
* {{App|[[Wikipedia:Tin (newsreader)|tin]]|A cross-platform threaded NNTP and spool based UseNet newsreader.|http://tin.org/|{{AUR|tin}}}}
* {{App|trn|A text-based Threaded Usenet newsreader.|https://trn.sourceforge.net/|{{AUR|trn}}}}

==== Graphical ====

* {{App|[[NZBGet]]|Usenet binary downloader for .nzb files with web and CLI interface.|https://nzbget.net/|{{Pkg|nzbget}}}}
* {{App|[[Wikipedia:Pan (newsreader)|Pan]]|GTK Usenet newsreader that's good at both text and binaries.|https://gitlab.gnome.org/GNOME/pan|{{Pkg|pan}}}}
* {{App|[[SABnzbd]]|An open-source binary newsreader webapp written in Python.|https://sabnzbd.org/|{{AUR|sabnzbd}}}}
* {{App|XRN|Usenet newsreader for X Window System.|https://www.mit.edu/people/jik/software/xrn.html|{{AUR|xrn}}}}

=== Microblogging clients ===

* {{App|Choqok|Microblogging client for KDE that supports Mastodon, Pump.io and GNU social.|https://choqok.kde.org/|{{AUR|choqok-git}}}}
* {{App|Dianara|Pump.io client written in Qt.|https://jancoding.wordpress.com/dianara/|{{AUR|dianara}}}}
* {{App|Lemmy-UI|Official web app for lemmy.|https://github.com/LemmyNet/lemmy-ui|{{AUR|lemmy-ui}}}}
* {{App|Liftoff|A mobile and desktop lemmy client written in flutter.|https://github.com/liftoff-app/liftoff|{{AUR|liftoff-bin}}}}
* {{App|Mikutter|Simple, powerful Mastodon client using GTK and Ruby.|https://mikutter.hachune.net/|{{AUR|mikutter}}}}
* {{App|Pumpa|Pump.io client written in C++ and Qt.|https://pumpa.branchable.com/|{{AUR|pumpa-git}}}}
* {{App|Tokodon|Mastodon client for KDE. Part of {{Grp|kde-network}}.|https://apps.kde.org/tokodon/|{{Pkg|tokodon}}}}
* {{App|Toot|CLI and TUI tool for interacting with Mastodon instances.|https://github.com/ihabunek/toot|{{Pkg|toot}}}}
* {{App|Tuba|GTK4 client for Mastodon.|https://apps.gnome.org/Tuba/|{{Pkg|tuba}}}}
* {{App|Whalebird|Mastodon client application. Based on the [https://electronjs.org/ Electron] platform.|https://whalebird.social/|{{AUR|whalebird}}}}

=== Blog engines ===

See also: [[Wikipedia:Blog software]], [[Wikipedia:List of content management systems]]

{{Note|Content managers, social networks, and blog publishers overlap in many functions.}}

* {{App|[[Diaspora]]|A distributed privacy aware social network.|https://diasporafoundation.org|{{AUR|diaspora-mysql}} or {{AUR|diaspora-postgresql}}}}
* {{App|[[Drupal]]|A PHP-based content management platform.|https://www.drupal.org/|{{Pkg|drupal}}}}
* {{App|[[Joomla]]|A php Content Management System (CMS) which enables you to build websites and powerful online applications.|https://www.joomla.org/|{{AUR|joomla}}}}
* {{App|[[Wordpress]]|Blog tool and publishing platform.|https://wordpress.org/|{{Pkg|wordpress}}}}

=== Static site generators ===

* {{App|Hexo|Fast, simple and powerful blog framework.|https://hexo.io/|{{AUR|hexo-cli}}}}
* {{App|Hugo|Hugo is a static HTML and CSS website generator written in Go. It is optimized for speed, ease of use, and configurability.|https://gohugo.io/|{{Pkg|hugo}}}}
* {{App|Jekyll|Static blog engine, written in Ruby, which supports Markdown, textile and other formats.|https://jekyllrb.com/|{{Pkg|jekyll}}}}
* {{App|Nikola|Static site generator written in Python, with incremental rebuilds and multiple markup formats.|https://getnikola.com/|{{Pkg|nikola}}}}
* {{App|Pelican|Static site generator, powered by Python.|https://getpelican.com/|{{Pkg|pelican}}}}
* {{App|Zola|An opinionated static site generator, written in Rust.|https://www.getzola.org/|{{Pkg|zola}}}}

=== Gallery software ===

* {{App|fgallery|A static photo gallery generator with no frills that has a stylish, minimalist look.|https://www.thregr.org/wavexx/software/fgallery/|{{AUR|fgallery}}}}
* {{App|jAlbum|A freeware cross-platform software for managing and creating digital photo albums or galleries.|https://jalbum.net/en/|{{AUR|jalbum}}}}
* {{App|jolly|A tool for statically generating galleries from images.|https://gitlab.com/prior99/jolly|{{AUR|jolly}}}}
* {{App|llgal|An easy and fast on-line gallery generator based on iGal.|http://bgoglin.free.fr/llgal/|{{AUR|llgal}}}}
* {{App|Photoview|A photo gallery for self-hosted personal servers.|https://photoview.github.io/|{{AUR|photoview}}}}
* {{App|Piwigo|A web application to manage your collection of photos, and other medias.|https://piwigo.org/|{{AUR|piwigo}}}}
* {{App|revela|A static web image gallery generator.|https://sr.ht/~yaroslav/revela/|{{AUR|revela}}}}
* {{App|Sigal|A simple static gallery generator.|http://sigal.saimon.org/en/latest/|{{Pkg|sigal}}}}
* {{App|thumbsup|A static web galleries for all your photos and videos.|https://thumbsup.github.io/|{{AUR|nodejs-thumbsup}}}}
* {{App|ZenphotoCMS|A CMS for selfhosted, gallery focused websites.|https://www.zenphoto.org/|{{AUR|zenphoto}}}}

== Remote desktop ==

See also: [[Wikipedia:Remote desktop software]], [[Wikipedia:Comparison of remote desktop software]], [https://remotedesktop.google.com/ Chrome Remote Desktop] (for a web browser-based solution)

=== Remote desktop clients ===

* {{App|[[Wikipedia:AnyDesk|AnyDesk]]|Proprietary remote desktop software.|https://anydesk.com/|{{AUR|anydesk-bin}}}}
* {{App|GNOME Connections|Remote desktop client for GNOME. Supports RDP and VNC. Part of {{Grp|gnome}}.|https://apps.gnome.org/Connections/|{{Pkg|gnome-connections}}}}
* {{App|GVncViewer|Simple VNC Client on Gtk-VNC. Run with {{ic|gvncviewer}}.|https://wiki.gnome.org/Projects/gtk(2d)vnc|{{Pkg|gtk-vnc}}}}
* {{App|[[Wikipedia:KRDC|KRDC]]|Remote Desktop Client for KDE. Supports RDP and VNC. Part of {{Grp|kde-network}}.|https://apps.kde.org/krdc/|{{Pkg|krdc}}}}
* {{App|[[Remmina]]|Remote desktop client written in GTK. Supports RDP, VNC, SPICE, X2Go and SSH.|https://remmina.org/|{{Pkg|remmina}}}}
* {{App|Remote Viewer|Simple remote display client. Supports SPICE and VNC.|https://virt-manager.org/|{{Pkg|virt-viewer}}}}
* {{App|RustDesk|A remote desktop software, open source, written in Rust.|https://rustdesk.com|{{AUR|rustdesk}}}}
* {{App|Sunlogin Remote Control|Proprietary software that supports remote control of mobile devices, Windows, Mac, Linux and other systems. It uses its own proprietary protocol.|https://sunlogin.oray.com/en/about/about{{Dead link|2025|04|05|status=404}}|{{AUR|sunloginclient}}}}
* {{App|[[Wikipedia:TeamViewer|TeamViewer]]|Proprietary remote desktop client. It uses its own proprietary protocol.|https://www.teamviewer.com/|{{AUR|teamviewer}}}}
* {{App|ToDesk|Proprietary remote desktop client that suits for remote teamwork. It uses its own proprietary protocol.|https://www.todesk.com/|{{AUR|todesk-bin}}}}
* {{App|[[Wikipedia:Vinagre|Vinagre]]|Remote desktop viewer for GNOME. Supports RDP, VNC, SPICE and SSH.|https://wiki.gnome.org/Apps/Vinagre|{{AUR|vinagre}}}}
* {{App|[[TigerVNC|vncviewer (TigerVNC)]]|VNC viewer for X.|https://tigervnc.org/|{{Pkg|tigervnc}}}}
* {{App|[[X2Go]] Client|A graphical client (Qt5) for the X2Go system that uses the [[w:NX technology|NX technology]] protocol.|https://wiki.x2go.org/doku.php|{{AUR|x2goclient}}}}
* {{App|xfreerdp|FreeRDP X11 client. Run with {{ic|xfreerdp3}}.|https://www.freerdp.com/|{{Pkg|freerdp}}}}

=== Remote desktop servers ===

* {{App|freerdp-shadow-cli3|A utility for sharing an X display via RDP.|https://www.freerdp.com/|{{Pkg|freerdp}}}}
* {{App|GNOME Remote Desktop|A remote desktop server for GNOME. Supports RDP and VNC. Part of {{Grp|gnome}}.|https://gitlab.gnome.org/GNOME/gnome-remote-desktop|{{Pkg|gnome-remote-desktop}}}}
* {{App|kmsvnc|A VNC server for DRM/KMS capable GNU/Linux devices.|https://github.com/isjerryxiao/kmsvnc|{{AUR|kmsvnc}}}}
* {{App|KRdp|A limited RDP server for KDE.|https://invent.kde.org/plasma/krdp|{{Pkg|krdp}}}}
* {{App|Krfb|VNC server for KDE. Part of {{Grp|kde-network}}.|https://apps.kde.org/krfb/|{{Pkg|krfb}}}}
* {{App|MeshCentral|Device management server for files, terminal access and remote desktop into Linux (X11), macOS and Windows.|https://meshcentral.com/|{{AUR|meshcentral}}}}
* {{App|[[NoMachine]]|Proprietary remote desktop server and client based on [[w:NX technology|NX
technology]].|https://nomachine.com/|{{AUR|nomachine}}}}
* {{App|wayvnc|VNC server for wlroots based wayland compositors (such as {{Pkg|sway}}).|https://github.com/any1/wayvnc|{{Pkg|wayvnc}}}}
* {{App|[[TigerVNC|x0vncserver (TigerVNC)]]|VNC Server for X displays.|https://tigervnc.org/|{{Pkg|tigervnc}}}}
* {{App|[[x11vnc]]|VNC server for real X displays.|http://www.karlrunge.com/x11vnc/|{{Pkg|x11vnc}}}}
* {{App|[[X2Go]] Server|An open source remote desktop software that uses the [[w:NX technology|NX technology]] protocol.|https://wiki.x2go.org/doku.php|{{AUR|x2goserver}}}}
* {{App|[[Xpra]]|A multi-platform screen and application forwarding system.|https://xpra.org/|{{Pkg|xpra}}}}
* {{App|[[Xrdp]]|A daemon that supports RDP. It uses Xvnc, X11rdp or xorgxrdp as a backend.|https://www.xrdp.org/|{{AUR|xrdp}}}}

User talk:Erus Iluvatar

2026-05-09T17:17:47Z

Erus Iluvatar: /* Regarding NetworkManager/Privacy Merge status */ re, close

Talk:NetworkManager

2026-05-09T17:16:17Z

Erus Iluvatar: /* In relation to NetworkManager/Privacy */ Reply

== Correct/Updated dnsmasq with NetworkManager ==

So I just set this up to enable ad blocking on my laptop regardless of which network I connect to. So far it seems to be working. This config presented on the site dns=none and so forth does not work as desired.
create me:
{{hc|/etc/NetworkManager/dnsmasq.d/dnsmasq.conf|2=
resolv-file=/run/NetworkManager/no-stub-resolv.conf
strict-order
interface=lo
cache-size=1000
conf-file=/etc/NetworkManager/dnsmasq-shared.d/bad_domains.txt #https://github.com/notracking/hosts-blocklists (https://raw.githubusercontent.com/notracking/hosts-blocklists/master/domains.txt)
addn-hosts=/etc/NetworkManager/dnsmasq-shared.d/bad_hostnames.txt #https://github.com/notracking/hosts-blocklists (https://raw.githubusercontent.com/notracking/hosts-blocklists/master/hostnames.txt)
domain-needed
bogus-priv
}}
edit me:
{{hc|/etc/NetworkManager/NetworkManager.conf|2=
# Configuration file for NetworkManager.
# See "man 5 NetworkManager.conf" for details.
[main]
dns=dnsmasq
}}
I'm created by NetworkManager, just FYI of what I contain:
{{hc|/run/NetworkManager/no-stub-resolv.conf |2=
# Generated by NetworkManager
nameserver DHCP_PROVIDED_DNS_1
nameserver DHCP_PROVIDED_DNS_2
nameserver DHCP_PROVIDED_DNS_3
}}

[[User:Glenntanner3|Glenntanner3]] ([[User talk:Glenntanner3|talk]]) 13:54, 1 November 2019 (UTC)!

{{Unsigned|16:06, 31 October 2019 (UTC)|Glenntanner3}}

:That looks overcomplicated. This should work:
{{hc|/etc/NetworkManager/conf.d/dns.conf|2=
[main]
dns=dnsmasq
}}

{{hc|/etc/NetworkManager/dnsmasq.d/dnsmasq.conf|2=
cache-size=1000
conf-file=/etc/NetworkManager/dnsmasq-shared.d/bad_domains.txt
}}

:You don't need to include {{ic|/run/NetworkManager/no-stub-resolv.conf}}, NetworkManager will send the DNS server addresses to dnsmasq over dbus.
: -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 11:08, 1 November 2019 (UTC)

:Explanation for parameters:
I'll try to make this update correct. Didn't know, or expect, that username wouldn't be added and i'm kind of surprised this isn't designed to be indepent messages. Updated what I had before to match your better formatting.

From what I just tested resolv-file=/run/NetworkManager/no-stub-resolv.conf is required, commented it out->restarted NM->ping google->fail; dbus didn't seem to do it.

I also included interface lo to prevent external usage of my laptop being used for DNS.

I used NetworkManager.conf as it already existed, no need to create more that the minimum number of new configuration files.

domain-needed and bogus-priv are recommended for safety.

conf-file and addn-hosts are for ad domain blocking, should have mentioned; those can be excluded but perhaps should be mentioned.

Set this up to work around need for pihole at work or any network i'm connected to. But the documentation I found to be lacking.

[[User:Glenntanner3|Glenntanner3]] ([[User talk:Glenntanner3|talk]]) 13:54, 1 November 2019 (UTC)!

:If the DNS servers are not send over dbus, then something is broken on your end, check {{ic|journalctl -u NetworkManager.service}}. It should contain {{ic|dnsmasq[#]: setting upstream servers from DBus}} and {{ic|dnsmasq[#]: using nameserver ''address''#''port''(via ''interface'')}}.
:I tested with:
{{hc|/etc/NetworkManager/conf.d/dns.conf|2=
[main]
dns=dnsmasq
}}

{{hc|/etc/NetworkManager/dnsmasq.d/dnsmasq.conf|2=
cache-size=1500
conf-file=/etc/NetworkManager/dnsmasq-shared.d/bad_domains.txt
addn-hosts=/etc/NetworkManager/dnsmasq-shared.d/bad_hostnames.txt
domain-needed
bogus-priv
}}

:And everything works correctly for me.
: -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 07:25, 2 November 2019 (UTC)

== Network configuration in related articles ==

Currently, [[Network configuration]] and [[Wireless network configuration]] are listed in the related articles. Some time ago, information wired-connection specifics moved to [[Network configuration/Ethernet]] and wireless-connection specifics moved to [[Network configuration/Wireless]].

Should it list only [[Network configuration]], or all three [[Network configuration]], [[Network configuration/Ethernet]] and [[Network configuration/Wireless]] ?
-- [[User:Josephgbr|Josephgbr]] ([[User talk:Josephgbr|talk]]) 00:04, 12 November 2019 (UTC)

== Warn about that nm-applet installs libappindicator-gtk3 which breaks several applications? ==

Nm-applet installs libappindicator-gtk3 as a dependency. Some applications like blueman-tray as well as all electron-based applications use libappindicator if pressent in system. This breaks functionality in the tray area for all this applications (left mouse click stop to work and other clik/menu related issues).

This is clearly not an issue with nm-applet (maybe even not with libappindicator since nm-applet's tra icon seems to work properly) but nm-applet is one of the few applications that installs libappindicator as their dependency.

Edit: just figured out that if the nm-applet is started with "--indicator", if also has the same tray issues as described above.

[[User:Micw|Micw]] ([[User talk:Micw|talk]]) 09:31, 7 January 2021 (UTC)

== Use dispatcher to automatically toggle wireless depending on LAN cable being plugged in ==

The script, as it currently stands, will cause networking to be disabled if the network cable is disconnected while the computer is off.

If I plug in a LAN cable, the command ''nmcli radio wifi off'' is run.
Thats good, but later I turn off the computer to take it with me, and then I unplug the LAN cable. When I turn it back on, still without LAN cable (intending to use Wi-Fi), my LAN_interface is "unavailable", and will not receive any network events, i.e. "$1" in the script will never be the LAN interface name, and so the command ''nmcli radio wifi on'' will never be run, and my wifi radio remains off.

The command to turn it back on can be run manually, of course, and the LAN cable can be disconnected before power off, which will also turn it on - but the best solution would be to foolproof the script.

I'm not sure what would be the best way to go about it, though, but a bit of testing tells me that after the radio is off and the LAN cable is out, I will receive two network events on boot:
* none (action: hostname)
* <empty> (action: connectivity-change)
I believe the hostname action happens only when the hostname changes, and will normally happen only on boot, so maybe that can be a place to start?
Maybe add to the front of the script something like:
if [ "$1" = "none" ]; then
if [ "$(nmcli -g GENERAL.STATE device show LAN_interface)" = "20 (unavailable)" ]; then
nmcli radio wifi on
fi
fi
Or, maybe better, disconnect it form the hostname action and just run the unavailability test first, no matter what $1 and $2 is? It's not going take much CPU anyway - the network events seems to happen only on actual changes, so not very often.

Edit: I added a failsafe in an else clause to the event check.
It will be run on all events that are not related to the LAN Interface, so it's not elegant, but I don't know how else to pick up the non-event that you have no network.

[[User:Ferdinand|Ferdinand]] ([[User talk:Ferdinand|talk]]) 18:21, 17 August 2021 (UTC)

:I know I'm late to the party but I do agree with the other comment (as exactly this happened to me today). The interface does change when connected to, for example, a docking station with the ethernet cable plugged into it (which has a different interface name than the LAN) and the command no longer recognizes it. I would suggest doing a check based on <code>nmcli -t -f TYPE,STATE device | grep "ethernet:connected"</code> instead. The failsafe check could then look like
:<code>elif [ -n "$(nmcli -t -f TYPE,STATE device | grep "ethernet:connected")" ]; then...</code>
:This whole script shouldn't depend on the interface name (eno1, enp0s etc. which could change), but rather on the type of the connection (ethernet or wifi) which is what we really care about. But that's for another day. [[User:DuckyDuck|DuckyDuck]] ([[User talk:DuckyDuck|talk]]) 00:05, 15 January 2026 (UTC)

:We should also use "nmcli dev | grep "ethernet" | grep -w "connected"" instead of "LAN_Interface" because the name of the interface might change when using different docking stations or tongles. But I am too bad at scripting to make this change.

:[[User:Utini2000|Utini2000]]

== NetworkManager-wait-online ==
Updated the section, to be coherent with [[Systemd-networkd#systemd-networkd-wait-online]]. Most of the section however might be better off in [[NetworkManager#Troubleshooting]]. --[[User:Cvlc|Cvlc]] ([[User talk:Cvlc|talk]]) 23:01, 22 September 2021 (UTC)

== Share internet connection via Bluetooth ==

Currently there is method to share internet connection via WiFi and Ethernet but there is no mentioning on internet sharing via Bluetooth. I guess it would be nice to have one?

[[User:Pickfire|Pickfire]] ([[User talk:Pickfire|talk]]) 01:33, 2 March 2022 (UTC)

== iwd backend doesn't support mac spoofing ==

https://bbs.archlinux.org/viewtopic.php?pid=2063573#p2063573
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1111

This is not mentioned in https://iwd.wiki.kernel.org/networkmanager (or it iwd wiki) and will rather silently fail, so https://wiki.archlinux.org/title/NetworkManager#Configuring_MAC_address_randomization could mention it to prevent unpleasant surprises.

[[User:Seth|Seth]] ([[User talk:Seth|talk]]) 13:44, 23 October 2022 (UTC)

:The same arch forums thread mentions that the iwd needs to be configured at /etc/iwd/main.conf as it doesn't respect NM's configs. This has been my experience as well. So mac spoofing does work but not through NM.
:In my testing I've also come to understand a key quirk of iwd's spoofing modes. The options disabled and once, work intuitively. The man page wording for network mode is "If AddressRandomization is set to network, the MAC address is randomized on each connection to a network. The MAC is generated based on the SSID and permanent address of the adapter. This allows the same MAC to be generated each time connecting to a given SSID while still hiding the permanent address."
:In practice with network, it generates a mac address per UNIQUE network connection or SSID, not every subsequent reconnection to an existing/known network. Hence it is better to use the once mode, and have sudo systemctl restart iwd, for your mac spoofing needs.
:I'll be adding this as a subsection to iwd and link the NM page to it. [[User:TheKnightSky|TheKnightSky]] ([[User talk:TheKnightSky|talk]]) 07:18, 8 May 2026 (UTC)

== Should configuration examples be added? ==

[[ConnMan#Connecting_to_eduroam_(802.1X)|ConnMan has configuration examples]], as well as [[Wpa_supplicant#Configuration|wpa_supplicant.]] Would it be good to add examples of slightly more complex setups to this page as well, [https://github.com/wylermr/NetworkManager-WPA2-Enterprise-Setup/blob/master/skeleton like this one]? There are some external tools that generate configs mentioned at [[Network_configuration/Wireless#eduroam|Network_configuration/Wireless]], but sometimes a quick reference is useful.
{{Unsigned|05:02, 18 January 2023 (UTC)|Dryya}}

== Fixes for automatic VPN dispatcher script ==

First contribution to the wiki after many years of reference! I used the script in [[NetworkManager#Use_dispatcher_to_connect_to_a_VPN_after_a_network_connection_is_established|5.2.5]] but upon network connection my VPN got stuck in an activation<->deactivation loop. After some troubleshooting I found that the script was running multiple times for some reason - I'm not sure if this is specific to my system or a more general bug. I fixed this dispatcher script to check if the VPN connection is not active before connecting to it (line 9):

{{hc|#!/bin/sh|2=
VPN_NAME="your vpn name"
ESSID="your essid"

interface=$1 status=$2
case $status in
up|vpn-down)
if iwgetid | grep -qs ":\"$ESSID\""; then
if !(nmcli connection show --active | grep "$VPN_NAME"); then
nmcli connection up id "$VPN_NAME";
fi
fi
;;
esac
}}

This fixed the issue for me, if anyone else can confirm this behavior on their setup I can incorporate this into the main article.
[[User:Accellarando|Accellarando]] ([[User talk:Accellarando|talk]]) 02:37, 11 June 2024 (UTC)

:Is there any reason to use the iwgetid? The dispatcher script receives the ''CONNECTION_ID'' variable which is the name the connection profile.
:So this is simpler and works fine:
{{hc|/etc/NetworkManager/dispatcher.d/vpn-up|<nowiki>
#!/bin/bash

STATUS=$2

CONN_NAME="connection_name"
VPN_NAME="vpn_name"

if [ "$CONNECTION_ID" = "$CONN_NAME" ]; then
case "$STATUS" in
up)
nmcli connection up "$VPN_NAME"
;;
down)
nmcli connection down "$VPN_NAME"
;;
esac
fi
</nowiki>}}

:(Sorry, couldn't figure out how to format the codeblock correctly in a reply to a comment) [[User:Zwog|Zwog]] ([[User talk:Zwog|talk]]) 07:09, 22 January 2026 (UTC)
::hi Zwog! I wasn't familiar with those NetworkManager variables, that solution does look more elegant to me. I used iwgetid while troubleshooting the issues I came across, so no practical reason for iwgetid over the NM shell variables. I'm no NM expert so I'll defer page editing to someone with more experience with scripting the dispatcher. :) [[User:Accellarando|Accellarando]] ([[User talk:Accellarando|talk]]) 20:26, 22 January 2026 (UTC)

== Remove unnecessary section 8.22 ==

The remove notice at the beginning of this section seems fair. I agree with the removal. Should I do it?

BTW, the reference: https://wiki.archlinux.org/title/NetworkManager#OpenVPN_connections_fail_with_%22secrets:_failed_to_request_VPN_secrets%22_warn [[User:Ismailarilik|Ismailarilik]] ([[User talk:Ismailarilik|talk]]) 13:23, 25 February 2025 (UTC)

:See [[User talk:Andreymal#libnma]] for details — [[User:Andreymal|andreymal]] ([[User talk:Andreymal|talk]]) 13:40, 25 February 2025 (UTC)
::Fair enough. Closing... [[User:Ismailarilik|Ismailarilik]] ([[User talk:Ismailarilik|talk]]) 17:44, 25 February 2025 (UTC)
::Didn't close... I think the notice should be removed then. [[User:Ismailarilik|Ismailarilik]] ([[User talk:Ismailarilik|talk]]) 17:51, 25 February 2025 (UTC)

== In relation to NetworkManager/Privacy ==

[[NetworkManager/Privacy]] does not seem all that fleshed out or necessary to warrant its own subpage. Specifically due to the fact that 3 out of the 4 (sub)sections do nothing but link back to the main [[NetworkManager]] page. I suggest the absorption of the subpage into the main page and instead of merging [[NetworkManager#Configuring MAC address randomization]] into the /Privacy subpage we could merge it to [[MAC address spoofing#NetworkManager]] as it lists all the MAC address specific guides/notes there. [[User:TheKnightSky|TheKnightSky]] ([[User talk:TheKnightSky|talk]]) 12:16, 8 May 2026 (UTC)

:Also, the only section that exists is [[NetworkManager/Privacy#Encrypted network keyphrases]], which should either be merged into/with or have alongside [[NetworkManager#Encrypted Wi-Fi passwords]] as Gnome keyring and mostly everything it talks about is already mentioned there. [[User:TheKnightSky|TheKnightSky]] ([[User talk:TheKnightSky|talk]]) 14:42, 9 May 2026 (UTC)
:I have 0 memory of why I flagged the page other that probably seeing possible duplication: please do what you think is best as far as merging goes :)
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 17:16, 9 May 2026 (UTC)

Help talk:Template

2026-05-09T17:13:32Z

Erus Iluvatar: /* Have editors create the talk page discussions for Status templates: Merge and Move */ Reply

== Should administrative templates be translated? ==

I have coincidentally encountered a stub page ([[Яндекс Диск (Русский)]], now deleted) with wrong localized title, which was marked for deletion using a localized template, [[Template:Deletion (Русский)]]. This was obviously wrong, because the page was not listed under [[Special:WhatLinksHere/Template:Deletion]], which is the list which is systematically checked.

I admit that localized "administrative templates" can be useful for coordinating the effort of a translation team, and having English messages on localized pages might be considered ugly, but there are considerable downsides in splitting the [[Special:WhatLinksHere]] by language this way.

Another step deeper, maybe we should put together a list of templates that should not be translated?

-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 19:59, 10 September 2014 (UTC)

:I think what you're saying makes sense (and a lot) only for [[Template:Deletion]]; the admins (like any other user) can't expand, merge or update articles written in languages they don't speak, right? :) What other templates were you thinking about? -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 10:43, 11 September 2014 (UTC)

::True, every other [[Help:Template#Article status templates|article status template]] could be used in localized form by the maintenance team. Regardless, there will always be fragmentation of the [[Special:WhatLinksHere]]: for example when fulfilling the [[ArchWiki:requests|requests]], it is common to use English message (and template) on localized pages if the editor does not speak the language. This should be definitely considered by the translation teams.
::Personally, I find it strange that [[Template:Out of date|outdated]] or [[Template:Accuracy|inaccurate]] content from English pages can be spread by translation (see [https://wiki.archlinux.org/index.php?title=Bluetooth_Mouse_(%D0%A0%D1%83%D1%81%D1%81%D0%BA%D0%B8%D0%B9)&diff=next&oldid=334522#.D0.90.D0.B2.D1.82.D0.BE.D0.BC.D0.B0.D1.82.D0.B8.D1.87.D0.B5.D1.81.D0.BA.D0.B8_.D0.BF.D0.BE.D0.B4.D0.BA.D0.BB.D1.8E.D1.87.D0.B0.D1.82.D1.8C_.D0.BC.D1.8B.D1.88.D1.8C_.D0.BF.D1.80.D0.B8_.D0.B7.D0.B0.D0.B3.D1.80.D1.83.D0.B7.D0.BA.D0.B5]).
::-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 11:36, 11 September 2014 (UTC)

:::About the first point on "fragmentation" of WLH pages, do you mean that it inevitably happens that some localized articles are marked with localized templates and some with English templates? In what cases is it possible that somebody adds a status template to an article without being able to understand its language? And if (s)he does, is that really the right thing to do? And if it is, maybe we could recommend to use the localized version of the template even if the message is then written in English?
:::About the second point on template "spreading", I don't find it "strange" if it happens when somebody translates from an article that is marked with such status template: he's adding the localized template not only to remind to the team that the article contains outdated content, but also to notify all non-contributing readers about possible inaccuracies. But maybe I haven't understood what you meant exactly?
:::Just to come back to the original topic, isn't it a good thing that the WLH pages for the English status templates are not (ideally) "polluted" by non-English articles? (Doesn't apply to Template:Deletion, I know)
:::-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 14:33, 12 September 2014 (UTC)

::::For example when fulfilling [[ArchWiki:Requests]], there is often some unique keyword or phrase to identify the relevant section, even in localized pages. Google translate can be used to ''partially'' understand the surrounding text, even if the translation is grammatically incorrect. This makes it pretty easy to mark the section with English message (translating the message from English would be risky, the grammar mistakes might alter the meaning), which I think is an improvement (any warning should be better than none). Using a localized template in this case would require checking if such template exists, and even if it does, combining localized template and English message is even more weird.
::::About fragmentation and using localized ''article status templates'' generally, its advantage is that it filters out other languages in the WLH lists, but this only partial (the global list will always contain some localized pages, unless we want to create the necessary templates for each language and do some mass cleanup, and the localized lists will not point out localized pages marked with global templates). The disadvantage is that global maintenance, if only marking as outdated as per [[ArchWiki:Requests]], will be harder.
::::-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 21:51, 12 September 2014 (UTC)

:::::Ok, of course each solution has pros and cons (will we need a summary table for this issue too?): honestly I wouldn't find it too weird if a localized template had an English message, which could also be translated afterwards by somebody else. Yes, adding a localized status template requires a bit more typing, sometimes even copy-pasting if there are non-Latin chars in the language name: this could be mitigated in the future by [[Help talk:i18n#Language namespace(s) in place of suffixes?]]; I understand this could effectively discourage adding status templates to translations. On the other hand, a bot would be able to convert the templates to the proper localized versions very easily, so that's a task that could be performed periodically (it could be used to check also other templates). And yes, having a translated version for each template would be required if we enforced such a policy. Finally, let's not forget that localized templates would be more useful to casual readers than English templates.
:::::-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 05:03, 14 September 2014 (UTC)

::::About the template spreading, it is safe to assume that [[Template:Poor writing]] will never be translated. Instead, the translator will probably fix the English article prior to translating it, which is happening ''a lot'', even when the style issues are not marked with a template, and this is absolutely great. On the other hand, I have never noticed any other ''article status template'' being resolved during translation. Admittedly, sometimes it is best to just translate the inaccurate content along with the template, or the translator might be unable to resolve it, but in terms of statistics I think that I should have noticed at least some effort by now.
::::-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 21:51, 12 September 2014 (UTC)

:::::Well, [[Template:Poor writing]] does have a translation already with some backtransclusions, I'm not sure if you'd delete it (I wouldn't). -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 05:03, 14 September 2014 (UTC)

::As the discussion about other [[Help:Template#Article status templates|article status templates]] is getting slightly off-topic, let's take a list of one item for now, [[Template:Deletion]]. How do we mark it as non-translatable? The translated versions could then be redirected to the English template and deleted when there are no backlinks. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 22:01, 12 September 2014 (UTC)

:::I think the [https://docs.python.org/3.4/glossary.html#term-eafp EAFP] approach is better in this case, I can think of 2 implementations:
:::# Create a redirect for each Template:Deletion_(Language) title and protect them from editing with an exhaustive justification in the summary (this solution would A) be more consistent with the usage of the other status templates and B) allow us grouping the backtransclusions of Template:Deletion by language in its WLH page).
:::# Redirect the existing translations temporarily, convert them all with a bot, then delete them and finally protect all the Template:Deletion_(Language) titles from creation with an exhaustive justification in the summary.
:::I prefer 1), do you agree/disagree or have additional options?
:::-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 05:08, 14 September 2014 (UTC)

== Template "nowrap" ==

I would like to ask for opinions about adding a wiki template like [https://en.wikipedia.org/wiki/Template:Nowrap Wikipedia's "nowrap"].

Although there are already some alternative solutions available for specific cases (e.g. {{ic|&nbsp;}} for non-breaking space, {{ic|&#8209;}} for non-breaking hyphen), the "nowrap" template (and/or other similar templates) covers additional cases.

For example, you might find one line of text presented as ending with the word {{ic|package}} and the same sentence continues in the next line, presented as starting with {{ic|(s)}}. By using the "nowrap" template on this expression, you get {{ic|package(s)}} all together, either at the end of one line or at the beginning of the next one, but never separated in 2 lines.

This is just an example. Other cases can be (more) relevant (too). Obviously, the "nowrap" template can also be used instead of (multiple) non-breaking spaces and non-breaking hyphens.

Without a "nowrap" (or similar) template, the alternatives are either to not care about these things, or to use one of the following (please note that some alternatives might be more appropriate than others):

{{bc|
1=This text will not wrap.
Some sentence... package(s) and the sentence continues.
}}
{{bc|
1=This text will not wrap.
Some sentence... package(s) and the sentence continues.
}}

The "nowrap" template also has some "alias" (or redirection) names in Wikipedia, or we could use a new different name for this same template.

Is this kind of situation worth a template for the ArchLinux wiki? Any thoughts? [[User:Ady|Ady]] ([[User talk:Ady|talk]]) 15:39, 27 March 2016 (UTC)

:I don't know, it seems a bit overcomplicated to me... What browser are you using that wraps "package(s)" at the parenthesis? At least Firefox correctly interprets it as a single word, since I do believe that these cases should be handled by the browser. The same goes for e.g. "package-s". Can you give more examples where this template would be needed (and would be a clearly better solution than using non-breaking spaces etc.)? — [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 06:57, 30 March 2016 (UTC)

::Hmm, perhaps I have not used the best example - I know I have seen this "package(s)" example somewhere, but currently I cannot recall where / when exactly.
::I should point out that users could see an unwanted (word) wrapping, depending on the width of the wiki text area (e.g. screen resolution, web browser's zoom, fonts...).
::As for "better" (or common) examples, please see [https://en.wikipedia.org/wiki/Wikipedia:NOWRAP] for brevity.
::BTW, using space characters and hyphens are the (most) common word-separators in certain languages, but not in all of them (e.g. CJK languages), so a "nowrap" template might be even more helpful in some translated wiki pages than in the English ones.
::I want to be clear. I am also not completely sure this type of template is "essential" for the ArchLinux wiki. It is potentially helpful; the question would be whether it is worth it. [[User:Ady|Ady]] ([[User talk:Ady|talk]]) 02:51, 31 March 2016 (UTC)

:::I see, I should have been more specific, but what I meant with "more examples" is existing samples of the ArchWiki (in any language) where such template would improve the page rendering and/or the source text. To put it in other words: after creating the template, where exactly is it going to be used?
:::In general I'm against creating templates (or Categories, etc.) "just in case they come in handy one day", although in this case I admit the idea can make somewhat sense, so if you really feel you want to create the template, I won't object further, maybe somebody else will find good uses for it and we'll start appreciating its existence ^^
:::— [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 03:23, 31 March 2016 (UTC)

::::I am a contributor to other wiki sites (in addition to the ArchLinux wiki). As editor(s) of wiki text, it is usually recommended to be aware that readers might use very different setups. While I/we might not see a certain behavior in the presentation of the wiki text / page, others might.
::::Although the ArchLinux wiki would not (need to) consider older versions of web browsers (or web browsers being used in non-Linux OSes), I am used to test the results of my editions with at least a couple of different setups.
::::I found a [https://www.cs.tut.fi/~jkorpela/html/nobr.html web page] about word wrapping in HTML that might be of interest to (some) wiki editors. Some notes about it:
::::* Most of its content mentions Internet Explorer, but it also mentions Firefox, Opera and others.
::::* In theory, it is somewhat outdated (at the time of this writing, its last update was during 2013).
::::* In spite of its date, I am convinced that at least some of the issues are still relevant (with potential improvements and regressions in each new version / variant of web browser).
::::* The part of that web page that is relevant to our discussion here is that there are several alternative methods so to achieve the desired wrapping result, whether it is about preventing word-wrapping, imposing word-wrapping, or allowing optional wrapping at certain specific positions within an expression / word.
::::Some of the simpler alternatives, (probably with a varying degree of effective results): {{ic|&nbsp;}}, {{ic|&#8209;}}, {{ic|&#xfeff;}}, {{ic|&#8288;}}, {{ic|wbc}}, and for generic wiki text, a "nowrap" (or, one of its alias names, "nobr") templates.
::::The advantage of a "nowrap" template over its non-template alternatives is that it is more generic; editors can avoid having to use different tricks according to the specific character (space, hyphen, minus sign, em/en dash...) and it covers potential cases that have no alternative or that would make the source of the wiki text less-readable.
::::So, without a "nowrap" template, I guess that most of the relevant cases in Latin-like languages would be covered by some non-template alternative, or by using the full "span style expression". Although perhaps there might be some cases in which a "nowrap" template would not have an alternative in Latin-like languages, I am also ''guessing'' that such (few?) cases would probably not be worth a template in the ArchLinux wiki.
::::But then there are the CJK languages, in which wrapping styles / rules might be more important / complex than some form of "hyphen" and/or space characters.
::::Maybe [[User:Fengchao]] and/or other members that are fluent in CJK languages might have a different / relevant perspective?
::::— [[User:Ady|Ady]] ([[User talk:Ady|talk]]) 13:40, 1 April 2016 (UTC)

== Forum link ==

:Moved from [[Talk:Bash/Functions]] -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 11:13, 23 October 2015 (UTC)

The article has two types of forum links:

*[https://bbs.archlinux.org/viewtopic.php?id=30155 BBS#30155] (intro, as in [[Template:Bug]]) and
*https://bbs.archlinux.org/viewtopic.php?id=101010 (section [[Bash/Functions#Kingbash|#Kingbash]])

Which one is right again? --'''[[User:Det|Det]][[User talk:Det|talk]]''' 11:44, 24 July 2015 (UTC)

:Full URLs should be avoided, see [[Help:Style#Hypertext_metaphor]], otherwise I know of no recommended wording for forum links. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 12:13, 24 July 2015 (UTC)

::That section doesn't actually even talk about external links, while [[Help:Editing#External links]] says ''"just type the full URL"'', but also that ''"it is often more useful to make the link display something other than the URL"''. --'''[[User:Det|Det]][[User talk:Det|talk]]''' 16:04, 24 July 2015 (UTC)

:::This was already mentioned somewhere some time ago, I don't remember where nor when, anyway [https://wiki.archlinux.org/index.php?title=Special%3ALinkSearch&target=https%3A%2F%2Fbbs.archlinux.org%2Fviewtopic.php] would seem to justify the creation of a [[Template:BBS]], just like we have [[Template:Bug]]. — [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 15:18, 25 July 2015 (UTC)

::::The problem with a BBS template is that links to the full thread have simple query string {{ic|1=?id=''number''}}, whereas links to posts have {{ic|1=?pid=''number''#''number''}}. There would have to be two different templates, which would get confusing very quickly.
::::There are more problems with existing links to the BBS: from looking at the list you posted, there are many links specifying the page number in the query string ({{ic|1=p=''num''}}), but FluxBB has variable/configurable number of posts per page. The links should point to either the full thread (first page), or a specific post.
:::: -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 15:31, 25 July 2015 (UTC)

:::::Like with links to bugs, a bbs url has to be pasted and manually modified anyway, but most of the times the conversion to [[Template:Bug]] ends up being done by a bot, which would be able to use two different BBS templates appropriately.
:::::I see 5 types of viewtopic.php links:
:::::# {{ic|1=?id=''number''}}: these could be changed to [[Template:BBSid]] instances.
:::::# {{ic|1=?id=''number''&p=''number''}}: when {{ic|''number''}} is {{ic|1}}, they could drop it and use [[Template:BBSid]]; otherwise they should point to a post as you say and use a [[Template:BBSpid]] template (we could publish a list of such links for manual fixing, since the correct post has to be found by a human, a bot can't do it).
:::::# {{ic|1=?pid=''number''}}: these could be changed to [[Template:BBSpid]] instances, the link fragment is the same as {{ic|''number''}} with a prefixed {{ic|p}}, so it's easy to add using the same template argument.
:::::# {{ic|1=?pid=''number''#p''number''}}: these could be changed to [[Template:BBSpid]] instances, {{ic|''number''}} needs to be specified only once.
:::::# {{ic|1=?t=''number''}}: these seem to be all broken, so they should be marked as dead, or fixed.
:::::I've chosen [[Template:BBSid]] and [[Template:BBSpid]] instead of e.g. [[Template:BBSthread]] and [[Template:BBSpost]] thinking that it would be easier to get their relation to the url when used manually, but I'm still quite undecided (provided that we actually decide to introduce the new templates).
:::::— [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 04:27, 26 July 2015 (UTC)

::::::3. and 4. are identical (btw. haven't you confused their descriptions a little?), except that 3. only opens the page with the given post (based on the user's posts-per-page setting), but stays at the top of the page, whereas 4. points directly to the post (the {{ic|#p''number''}} is the trick to do it). So 3. should also never be used, but it's trivial to transform it to 4. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 09:50, 26 July 2015 (UTC)

:::::::Of course, I was reasoning from a bot's point of view, which would indeed see 3. and 4. as different cases. My description of 3. was assuming that the need for a fragment was obvious (hence the mention of how easy it is to add it even if it's not in the original link), but what's important is that you seem to have understood anyhow :P — [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 10:44, 26 July 2015 (UTC)

::::::::I agree on using only PID and ID. If you're linking to a page, you most likely should link to a PID. To distinguish between both, you could use {{ic|##}} for PID and {{ic|#}} for ID.
::::::::I don't have suggestions on automating the implementation. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 11:18, 23 October 2015 (UTC)

== New Template Application ==

I was thinking a new template could be added for application pages that would give quick info on a package. It would be right floated like "related articles". I made a quick example here: [[User:Meskarune/package]] but it could use more work on the format/syntax. [[User:Meskarune|Meskarune]] ([[User talk:Meskarune|talk]]) 20:17, 23 January 2017 (UTC)

:I don't see the point of this. You want to know the package name? Look in ''Installation''. The website and description? Should be linked in the intro. systemd service, user & group and man pages should be under ''Usage''. Config paths & examples under ''Configuration''. –[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 05:43, 2 January 2018 (UTC)

::The point of the sidebar table is that people will not have to go searching through lots of text for important information. If you only want to quickly know the service file and config file on Arch without reading through all the text on the wiki it would be in an easy to find place. Obviously its just some extra "eye candy" if you will that people could choose to use.
::
::The larger issue I was trying to address was the lack of strict standardization for pages on packages.
::
::The idea is that the content, and specific order of sections for package pages should be standardized with certain sections being required. For example, install and configuration. This will increase the quality of package pages on the wiki and enable scripts to be able to automatically mark issues such as lacking an install section. This isn't just about a template for a table, it is about having more specific standards for package pages as well in order to help people write them easier and increase over all quality and decrease maintenance time.
::
::My proposal is that the example page I wrote should be the standard format for all pages on packages on the wiki.[[User:Meskarune|Meskarune]] ([[User talk:Meskarune|talk]]) 19:39, 9 August 2018 (UTC)

:::If you want to find out services / configuration files / man pages of a package without reading an article, you can just grep {{ic|pacman -Ql}} for {{ic|/system/}}, {{ic|/etc/}} and {{ic|/man/}}. Your sidebar duplicates information and would thus increase the cost of maintenance (unnecessarily so). We already have [[Help:Style#Standard_sections|standard sections]]. I don't think that we need to require some sections / have a strict order for all standard sections. We don't need a dedicated example article, we got enough actual articles to serve as an example. --[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 05:06, 10 August 2018 (UTC)
::::I put together code for the info box: https://wiki.archlinux.org/index.php/User:Meskarune/Template:application first time writing a template, it was a good learning experience if anything else. I originally got the idea from wikipedia info boxes.
::::
::::Anyways, I don't propose that the info box be required for every package page, but on certain ones it would be very useful, for things like web servers, email servers, etc it is very common for people to go to the wiki page first, then go to upstream docs/bug trackers after, so having a small list would be helpful, and I think if people want to add them to such pages, the maintenance is not much since upstream doesn't often change. As for man page links, I often have the arch wiki on my phone while doing things on a computer without a GUI, and it is honestly useful to have man page links so its easier to read something on a phone while doing something in a TTY. I don't know how common that use case is, but I can't be the only one. It would also be useful for people who are visually impaired because finding links in text is difficult with a screen reader, and voice commands on phones are better than they are on linux.
::::
::::And as for the "standard sections" in the style guide, "installation" wasn't even on there until you added it after this discussion started. (and I am grateful you took the time to do that) Part of the reason for my original suggestion of having more standard sections was because there was a lack. I also still believe that having certain sections required for packages will increase quality and consistency of the pages over time and lower maintenance because scripts can automatically tag any page under category:package if it is lacking installation or configuration. But that is of course up to y'all to decide about that. I really don't have the time/energy to argue about this if no one else thinks more standardization is a good idea.[[User:Meskarune|Meskarune]] ([[User talk:Meskarune|talk]]) 23:39, 11 August 2018 (UTC)
''[Moved from [[ArchWiki talk:Administrators#Package page style guide/template]]. --[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 13:07, 9 August 2018 (UTC)]''

I wrote a style guide/example template for package wiki pages. I wanted to get some feedback on it and possibly see if this couldn't be adopted as a standard on the wiki. This is the page: [[User:Meskarune/package]]

Maybe a wiki template could be created for the application info table sidebar thingy, this way it is faster/easier to add.

I think this would help improve the quality of package pages and help users get useful information faster. --[[User:Meskarune|Meskarune]] ([[User talk:Meskarune|talk]]) 20:37, 8 August 2018 (UTC)

== Creation of package search templates ==

We have got [[Template:Pkg]], [[Template:AUR]] and [[Template:man]] but package searches are still linked using external links, e.g.:

<pre>
[https://www.archlinux.org/packages/?q=thunderbird-i18n language pack]
[https://aur.archlinux.org/packages/?K=android-platform- older versions]
</pre>

I am therefore pondering whether we should create {{ic|<nowiki>{{Pkg?|foo}}</nowiki>}} → [https://www.archlinux.org/packages/?q=foo PKG?foo] and {{ic|<nowiki>{{AUR?|foo}}</nowiki>}} → [https://aur.archlinux.org/packages/?K=foo AUR?foo].

Pros:

* readers can identify package search links just by looking at them
* dedicated templates make the markup more readable and semantic

Cons:

* it further complicates [[Help:Reading#Formatting]]

While [[Template:AUR?]] already exists it's deprecated and produced "{{AUR?|foo}}", so there should be no problem in changing it.

The question is if it's worth it to create two templates for ~35 pages. What do you guys think?

--[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 08:15, 20 May 2018 (UTC)

:It can be worth it, but how easy would it be to use the template, compared to the current link-like usage? You've taken your examples out of their context, [[Thunderbird]] and [[Android]], but there they are naturally inserted with an alternative link label, and as far as I remember this happens pretty much everywhere a package-search link is used.
:Perhaps this hypothetical template should still allow - if not even force - an alternative label (I don't like the [https://www.archlinux.org/packages/?q=foo PKG?foo] rendering too much anyway), but then in that case why not create dedicated interwiki links instead? We can do it easily from [[Special:Interwiki]].
:-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 15:49, 22 May 2018 (UTC)

::If the links require an alternative label, wrapping it with a template does not make much sense. Also, there are so few of such links and still there are similar cases that would require a manual link - e.g. the language pack links in [[Firefox#Installing]] which link to the ''pkgbase'' listings. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 16:50, 22 May 2018 (UTC)

::What about the following interwiki prefixes?
::{{bc|aur → https://aur.archlinux.org/packages/$1 pkg → https://www.archlinux.org/packages/$1}}--[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 08:03, 24 May 2018 (UTC)

:::So now you want to replace the [[Template:Pkg]] and [[Template:AUR]] templates with interwiki links? That does not address the package search problem, unless you're about to write <nowiki>[[aur:?q=foo]]</nowiki>. It would also remove the special formatting of the package links, so that's no from me. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 09:30, 26 May 2018 (UTC)

::::I obviously don't want to replace [[Template:Pkg]] and [[Template:AUR]]. I left out the query parameters to make it flexible.--[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 09:47, 26 May 2018 (UTC)

:::::In that case the purpose of the interwiki links would not be well defined, the {{ic|1=?q=}} string (which is an implementation detail) would have to be written manually on every page, and the alternative label would have to be used to make the link less ugly. Anyway, templates are much more flexible than interwiki links so let's either use templates or interwiki links which are as simple as possible. But before discussing the implementation details, we should agree on whether the use case is worth the effort or not. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 10:52, 26 May 2018 (UTC)

::::::Given the relatively limited number of applications, I wouldn't go as far as adding another template to our toolbox, but an interwiki link is such a simple thing that as I said I'd be in favor of setting up.
::::::I wouldn't like "flexible" interwiki links either, however, I'd rather go for:
aur → https://aur.archlinux.org/packages/?K=$1
pkg → https://www.archlinux.org/packages/?q=$1
::::::So the examples in the OP would become:
<pre>
[[aur:android-platform-|older versions]]
[[pkg:thunderbird-i18n|language pack]]
</pre>
::::::I'm not 100% sure about the prefixes though, I wish we could use {{ic|aur?}} and {{ic|pkg?}} or similar...
::::::-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 17:09, 26 May 2018 (UTC)

:::::::I meant the question is if it's worth doing it some other way instead of using the external links. External and interwiki links look the same and with the alternative label interwiki links don't save as much typing (one could even say that the URL, which is not very long in this case, can be copy-pasted completely which makes it easier to use). There are also other similar cases (like the pkgbase links above) which would require external links anyway. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 22:08, 26 May 2018 (UTC)

::::::::Well, of course I don't have a mathematical answer to that question, I can only say that interwiki links look neater to me in the source text, and since those search URLs are resources directly provided by Arch Linux, it makes sense ''to me'' to give them a shortcut, but yeah, more than a typing advantage it's a ''personal'' aesthetic preference over which I won't argue much more than this :)
::::::::Just to complete my reply, the full links could still be copy-pasted from the rendered pages; copy-pasting when editing the source text shouldn't be affected, because if you want to create a similar type of link, it doesn't matter if it's in the interwiki or the external-link form, although interwiki links are easier to just type than copy-paste. Interwiki links for split packages would be less useful and easy to use indeed.
::::::::Also, about the rendered looks, I want to remind that if we want we can specifically style (standard) package-search links however we like, whether they are created with external or interwiki links, but in the latter case we can target them specifically thanks to the ''extiw'' class.
::::::::-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 15:23, 27 May 2018 (UTC)

== Creation of Template:Info ==

I think we have got enough articles about [[GNU]] software to warrant a template for [[Info manual]]s, analogous to [[Template:man]].

gnu.org hosts HTML [[Info manual]]s for apparently most GNU packages, generally in the form of {{ic|<nowiki>https</nowiki>://www.gnu.org/software/''package''/manual/html_node/''node''.html}}.

I created [[User:Larivact/drafts/Template:Info]] as a draft, only to realize that gnu.org replaces spaces with dashes, meaning, like [[Template talk:Hc#hc breaks in lists]], this template would require [[mw:Extension:StringFunctions]].

--[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 11:21, 15 August 2018 (UTC)

:Not only that, it also encodes characters like dashes: [https://www.gnu.org/software/coreutils/manual/html_node/Special-built_002din-utilities.html] -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 11:47, 15 August 2018 (UTC)

::Well spotted, so: {{bc|' ' -> '_' '-' -> '_002d' '/' -> '_002f'}} should cover most cases. --[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 12:13, 15 August 2018 (UTC)

:::And I guess every other "blacklisted" character has to be encoded as {{ic|_}} + {{ic|''4-digit hex code''}}... So what's the full blacklist?
:::As for StringFunctions, that's a [https://phabricator.wikimedia.org/T8455#110965 dead-end solution].
:::-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 12:47, 15 August 2018 (UTC)

::::It's not a blacklist it's a whitelist, anything not {{ic|[A-Za-z0-9 ]}} is encoded, see [https://svn.savannah.gnu.org/viewvc/texinfo/trunk/tp/Texinfo/Convert/NodeNameNormalization.pm?view=markup#l114].
::::Yeah Lua/[[mw:Extension:Scribunto]] would allow for more readable code and correct templates. --[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 13:06, 15 August 2018 (UTC)
::::I opened [[ArchWiki talk:Administrators#Scribunto]]. --[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 17:34, 18 August 2018 (UTC)

== More inline-style templates ==

I would like to create more templates for inline-flagging of some style problems, similarly to [[Template:Dead link]] or [[Template:Broken section link]]:

* [[Template:Avoid implicit link]] (for {{ic|<nowiki>[[...|here]]</nowiki>}}, {{ic|<nowiki>[[...|above]]</nowiki>}}, {{ic|<nowiki>[[...|below]]</nowiki>}} etc.)
* [[Template:Avoid external link]] (for external links to Wikipedia, AUR packages etc.)
* [[Template:Citation needed]] or [[Template:Reference needed]]
* [[Template:Language register]] (could be used with arguments, e.g. {{ic|<nowiki>{{Language register|too informal}}</nowiki>}}, {{ic|<nowiki>{{Language register|avoid acronyms}}</nowiki>}}, etc.)

Some of them could be applied (semi)automatically with a bot. Maybe you can also think of more problems that could be marked similarly.

-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 10:25, 23 February 2020 (UTC)

:I don't see much need for [[Template:Language register]] since it would usually apply to whole paragraphs or the entire article instead of some phrase/word as [[Template:Dead link]]. I think [[Template:Style]] fully covers that case. I'm also somewhat skeptical of a bot's ability to apply it accurately, but maybe I'm mistaken about that.
:I do like the other proposed templates. I think [[Template:Citation needed]]/[[Template:Reference needed]] in particular would be very useful. It could ease the burden when flagging questionable claims, unlike [[Template:Expansion]] or [[Template:Accuracy]] which require a detailed "reason".
: -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 14:27, 23 February 2020 (UTC)

::I think [[Template:Language register]] would be useful for phrases explicitly mentioned in [[Help:Style#Language register]], e.g. "at the time of writing". They occur frequently and using [[Template:Style]] is usually an overkill, especially if the phrase appears inside a [[template:note|note]] or a list. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 15:33, 23 February 2020 (UTC)

:::Simpler alternative (possibly too simplistic): make only one new generic inline Style template, and clarify the reason with its argument case by case. Of course it will mix all cases together in its WhatLinksHere page, but so does [[Template:Style]]. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 15:47, 16 March 2020 (UTC)

::::I wouldn't like to add too much text to inline templates, because the wikicode would become too chaotic. Even <nowiki>{{avoid implicit link}}</nowiki> is shorter than <nowiki>{{inline style|avoid implicit link}}</nowiki>, and the former can even include a link to the relevant section in [[Help:Style]]. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 09:59, 21 March 2020 (UTC)

:::::No worries, I'm fine either way, maybe you can only start with the templates that can be applied with a bot, since for a human it might be just equally easy to directly fix links, acronyms, abbreviations etc. than flag them with a template. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 11:31, 21 March 2020 (UTC)
:As far as I understand, we are quite happy with <code><nowiki>{{Style|…}}</nowiki></code> and its friends. I want to close this stale topic. — [[User:Andrei Korshikov|Andrei Korshikov]] ([[User talk:Andrei Korshikov|talk]]) 16:21, 13 August 2025 (UTC)
::Actually, I would like to revisit this topic at some point. [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 18:40, 14 August 2025 (UTC)
:::👍 [[User:Andrei Korshikov|Andrei Korshikov]] ([[User talk:Andrei Korshikov|talk]]) 18:54, 14 August 2025 (UTC)

== Suggest using user page sandbox ==

Everyone using [[Template:Sandbox]] has following disadvantages:

* Only one user can edit it at a time.
* Breaks previous drafts and talks.

Instead of everyone using [[Template:Sandbox]] I propose suggesting to copy whole template to [[User:Exampleuser/Template]] and testing there. Also you can test template without saving the page, which you can't do on already created template page.

[[Template:Template]] and [[Help:Template#Creation]] would need to be updated, possibly first should link to latter instead of [[Template:Sandbox]]. Instead of creating template in main namespace instructions should suggest creating it in user page, then start new discussion on [[Help:Template]] to introduce it to the wiki.

-- [[User:Svito|Svito]] ([[User talk:Svito|talk]]) 00:12, 13 May 2020 (UTC)

:If people move or archive or delete their personal sandbox page, the drafts and talks will break anyway. And there were not many cases in the past where multiple users wanted to edit the template sandbox at the same time. Using just one template sandbox is good in at least one way: it helps to push things forward faster, because otherwise it would block other things. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 08:39, 13 May 2020 (UTC)

::Only admins can delete pages. And only users that were breaking our draft templates were [[User:Larivact]] which quit wiki and myself which I stopped doing because its pointless and because it breaks old talks. I don't see how [[Template:Sandbox]] helps push things faster. Obviously you would only save new version of template if you wanted to discuss it with other editors (which by default is slow because you have to wait for other people), and for previewing any non-existent page on wiki is faster, because you can preview without saving. Also if you want to draft many templates you should create [[Template:Sandbox2]] and the like, which [[User:Kynikos]] did and bloats our template space (why not name it [[Template:Command]] if we decided we allow creating draft templates in main template namespace), which we use to figure out optimal amount of templates we wish to maintain and update. -- [[User:Svito|Svito]] ([[User talk:Svito|talk]]) 16:41, 13 May 2020 (UTC)

::My main point as long as you need at least 2 different version of same or different templates, [[Template:Sandbox]] is not good enough. Other option would be just have resulting html directly inside draft pages, which is even uglier and harder to update without using extra tools like sed. -- [[User:Svito|Svito]] ([[User talk:Svito|talk]]) 16:45, 13 May 2020 (UTC)

:::I've thought about this a little, it may make sense to me, how would you patch [[Template:Template]] and [[Help:Template#Creation]]? I've moved [[Template:Sandbox2]]. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 16:41, 19 May 2020 (UTC)

== "Help:Template" or "Help:Templates"? ==

Singular or plural?..

"Template" is about what template is: it is useful for template creators (mostly, wiki admins).

"Templates" are about "template list" ([[Help:Template#List of templates]]). Wiki contributors are interested in them.

I think our page is named after [[Wikipedia:Template]], but, hey, that page is all about what the template is—compare it with [[mw:Templates]].

To be clear: I want to rename this page from "Template" to "Templates": ordinary users don't care what template is, but how to use them.

-- [[User:Andrei Korshikov|Andrei Korshikov]] ([[User talk:Andrei Korshikov|talk]]) 14:55, 1 August 2025 (UTC)

:I'm for renaming the page. — [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 18:58, 7 August 2025 (UTC)
:I have no strong opinion either way, if it feels clearer to everyone let's go. [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 16:24, 23 August 2025 (UTC)

== Have editors create the talk page discussions for Status templates: Merge and Move ==

The templates Merge and Move have an optional parameter of a talk page discussion. If the editors who make either of these two specific tags, also add the talk page topic atleast in brief they would be subscribed to that specific conversation. However if the editors only add the template to a subsection of a page other editors would have to make said topic page and then reach out to the original editor via their user talk page or other contact methods just to include them or get their perspectives, which could be an avoided waste of space of their user talk page space.

I suggest having a sentence in [[Help:Template#Status]] saying something along the lines of, "Please create a topic discussion when using Merge or Move templates so as to be subscribed to any ongoing discussions where needed".
This is more of QOL/best practices kind of change than a hard requirement change. Please let me know your thoughts on this. [[User:TheKnightSky|TheKnightSky]] ([[User talk:TheKnightSky|talk]]) 12:40, 8 May 2026 (UTC)

:The subscription to individual discussion topics is a weird feature, it is not necessary to get notifications. Many people who add these templates already have the page (and thus its talk page too) on their watchlist and get email notifications for all edits. Subscribing to discussions would mean duplicate notifications. Furthermore, you can mention people like @[[User:TheKnightSky|TheKnightSky]] to get their attention from anywhere. — [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 09:56, 9 May 2026 (UTC)
::You are right, that aspect makes sense.
::However regarding linking to the user page, I had thoroughly read the [[Help:Editing]], and [[Help:Template]] and [https://www.mediawiki.org/wiki/Help:Templates Help:Templates], and there was no mention of this notifying the user, much less this being described in them. The notification I received for this reply was along the lines of "
::‪Lahwaacz‬ mentioned you on ‪Help talk:Template‬ in "‪Have editors create the talk page discussions for...‬".
::The subscription to individual discussion topics is a weird feature, it is not necessary to get notifications. Many people who add these templates...
::", this was the only notification, there was no "Lahwaacz replied in xyz" for this.
::But on the other hand for a separate notification, "
::‪Lahwaacz‬ mentioned you on the talk page of user ‪Lahwaacz.bot‬ in "‪Marking bot edits as minor edit‬".
::Taking this discussion in a new course, I think minor edits still should be labelled as minor edits but not for the purposes as email notifications...
::", where I was not mentioned using my user page, but you had replied to my text.
::And another point for "
::‪Lahwaacz‬ replied in "‪Marking bot edits as minor edit‬".
::Of course in an ideal world they should be marked as minor edits, but it is not possible due to MediaWiki bugs, namely Notifications stop after bot...
::", which was an expected notification behaviour for a reply.
::By your logic I should have received 2 pings for this reply, unless in the backend multiple notifications for the same action is prohibited, which contradicts itself given that I got 2 notifications for the "Mayking bot edits" thread and only 1 for this even when mentioned by name, which also isn't described anywhere I could find. And im exclusively talking about the notifications on the webpage, not via email. [[User:TheKnightSky|TheKnightSky]] ([[User talk:TheKnightSky|talk]]) 12:44, 9 May 2026 (UTC)
:::If you enabled email notifications and added this page to your watchlist, you would have received 2 emails for a single edit, I think. — [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 13:20, 9 May 2026 (UTC)
::::Nope. Just checked. Single mail for the reply that has user page at 9:56 am UTC [[User:TheKnightSky|TheKnightSky]] ([[User talk:TheKnightSky|talk]]) 13:29, 9 May 2026 (UTC)
:Not all administrative templates need to have a discussion: if no one is against the change or if the person who suggested it does not follow through when someone disagrees, anyone can enact the change or remove the contested template accordingly.
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 17:13, 9 May 2026 (UTC)

User talk:Erus Iluvatar

2026-05-08T18:24:47Z

Erus Iluvatar: /* Regarding NetworkManager/Privacy Merge status */ Reply

== Thank you ==

Thank you for your recent edit on [[Pipewire]]. I am new to ArchWiki and missed the correct formatting. Thanks for fixing it. Cheers! [[User:Darksaber|Darksaber]] ([[User talk:Darksaber|talk]])

: Don't worry, everyone has to start somewhere ;). If you want to read before future contributions, look at [[ArchWiki:Contributing#Resources]]. --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 13:23, 11 March 2022 (UTC)

== Minor edit mark ==

Thank you for your contributions to the wiki. Please mark your edits as [[Wikipedia:Wikipedia:Minor edit|minor]] when necessary, so readers can filter them with "non-minor edits" filter. Thank you. -- [[User:Thmeiov|Thmeiov]] ([[User talk:Thmeiov|talk]]) 12:17, 14 March 2022 (UTC)

: You're right, I should be more careful on this. Thank you for reminding me ! --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 12:30, 14 March 2022 (UTC)

== Thanks for the edits on the Virt-Manager page ==
Thanks for the recent edits you made im pretty new to ArchWiki/MediaWiki and suck formatting so thanks for fixing my bad formating
[[User:ShinobuNarusaka|ShinobuNarusaka]] ([[User talk:ShinobuNarusaka|talk]])

: Hi ! Thank you for contributing a new page on a subject you're comfortable with. Don't worry, practice makes perfect. To double check your content before future contributions, look at [[ArchWiki:Contributing#Resources]]. --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 05:56, 27 March 2022 (UTC)

== $include Readline question ==
Hi, thanks for your work. I've seen that you have added a space in [[Readline#History]]. `man bash` (and some blogs) have no space in "$include /etc/inputrc". Do you have any reference? --[[User:Marzal|Marzal]] ([[User talk:Marzal|talk]]) 22:19, 14 April 2022 (UTC)

: Hi, thanks for pointing out my mistake: I had read the section too quickly and concluded this line was missing a space between the prompt and the command, but this is not the case. I've reverted my edit, sorry for the confusion. --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 03:43, 15 April 2022 (UTC)

== Thanks for improving the edit ==

Thanks for correcting the info, and naming it the 5000 series rather than Ryzen 9 or 5. AMD Ryzen series are even more ambiguous than Intel. AMD Ryzen 5xxx series processor could be Ryzen 5(5600x), Ryzen 9(5950x), or Ryzen 7(5800x). Currently using Ryzen 9 5950x and Ryzen 9 5900x on two of my desktops, on Windows they consume 100 watts less power and my current linux setup, so was looking into that article and was thinking of making the switch from Pop OS to Arch Linux.
{{Unsigned|2022-06-17T04:56:21|Gagan0123}}

: Hi! I saw the ambiguousness of the existing wording when finishing to revert your edit, so instead of having more people tripping on it I tried to make it better :)
: Good luck on your journey ! --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 05:28, 17 June 2022 (UTC)

== Signature is unknown trust ==

Thanks for the edits! They made it easier to find the solution. --[[User:Topcat01|Topcat01]] ([[User talk:Topcat01|talk]])

: Credit where credit is due: [[User:Lahwaacz]] did 99.99% of the work, I've only fixed a capitalization issue. --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 20:26, 29 July 2022 (UTC)

== [[Unified Extensible Firmware Interface/Secure Boot]] ==

Hi Erus Iluvatar, thank you for improving my contributions to the [[Unified Extensible Firmware Interface/Secure Boot]] article! Especially the formatting.

Do you think it is necessary to include an explanation what all the "basic" GRUB modules are doing, in the first code block? I couldn't find any good documentation about all these modules, I only found [https://www.linux.org/threads/understanding-the-various-grub-modules.11142/ this thread on linux.org], which doesn't have all modules however and is already outdated.
The [https://www.gnu.org/software/grub/manual/grub/grub.html official GNU GRUB manual] has '''no documentation at all''' about the modules.

Do you think dividing the list of GRUB modules into these three parts, as done in the official Ubuntu build script, is meaningful, or is it arbitrarily / nonsensical?

Thank you in advance for an answer!

[[User:DasMenschy|DasMenschy]] ([[User talk:DasMenschy|talk]]) 12:30, 28 August 2022 (UTC)

: Hi! First of all, thank ''you'' for creating the content in the first place!
: Regarding the creation of a dedicated section about GRUB modules: if you are motivated to create it, an explanation on GRUB modules would probably be a great fit for the [[GRUB]] page. I'm not sure where exactly it could fit though. Depending on the length, maybe creating [[GRUB/Modules]] could be appropriate? From a quick search in the page right now, nowhere do we explain what a "GRUB module" actually is even though we refer to them roughly 20 times!
: Regarding the split into three parts: as for every classification, it ''is'' arbitrary, but nothing ever is truly neutrally written anyway :P It is logical given the reference material, and IMO feels like a good starting point for a reader trying to set up [[Secure Boot]] without wanting to include every existing modules.
: Thank you again for your contributions.
:--[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 12:43, 28 August 2022 (UTC)

== Template:Archive in user pages ==

Hi

I saw your [[Special:Diff/706716/746378 |edits]] about Archive template in user pages, I put those following the discussion [https://bbs.archlinux.org/viewtopic.php?id=271949 here] because I didn't know of a better way to delete them. What's the proper way to get rid of those then ? Thanks ! (Bonne journée !)

-- [[User:Cvlc|Cvlc]] ([[User talk:Cvlc|talk]]) 15:01, 16 September 2022 (UTC)

: Hi!
: You're completely right to have followed the advice of [[User:Lahwaacz]] on that, I am not allowed to delete pages as a simple maintainer, I'll try to catch an [[Administrator]] to remove those.
: Do you also want the [[User:Cvlc/Storage Layout and Alignment]] and [[User:Cvlc/Sector Size]] redirects deleted too?
: As for a generic way to delete pages, as far as I know it is not possible even for you own pages… I'll see if we can document this properly somewhere.
: --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 15:11, 16 September 2022 (UTC)

== You were right about /var filling up. ==

After testing for 2 weeks straight and installing/uninstalling random packages, it turns out that {{ic|/var}} does in fact fill all the way up non-stop. Maybe that won't happen for a regular user because they wouldn't be spamming packages, but that's IMO enough for me to leave behind my suggestion of removing it off the Wiki, but yet again the decision is up to you whether it should stay on [[Partitioning]] or not. [[User:Cont999|Cont999]] ([[User talk:Cont999|talk]]) 19:50, 20 September 2022 (UTC)

: I'm a little relieved to see that I was not completely missing the mark on the usage of {{ic|/var}} :P
: I'll be waiting for the result of the ongoing discussion at [[Talk:Partitioning#Separate /var]]: IMO keeping the sections as is should be good enough, but maybe a better wording on their actual relevance (or absence thereof) for a common setup can be achieved.
: --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 20:05, 20 September 2022 (UTC)

== Thanks! ==

Thank you for the improvements you made to the pages I created! [[User:Steffo|Steffo]] ([[User talk:Steffo|talk]]) 02:27, 21 September 2022 (UTC)

: And thank '''you''' for creating the pages in the first place: I'm just trying to get the form to compliment the content :)
: --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 05:46, 21 September 2022 (UTC)

== Thanks for the wiki page edits! ==

I intend [[User:Pongo1231/Arch on Steam Deck]] to be documentation of getting the Steam Deck UI fully working in Arch (alongside some opinionated sections like the Btrfs section), neither of which would obviously be a fit for [[Steam Deck]]. Of course I welcome any contributions to the page. :) -- [[User:Pongo1231|Pongo1231]] ([[User talk:Pongo1231|talk]]) 22:14, 26 October 2022 (UTC)

: Thanks ! I was going to link to it in a forum exchange but it was referring to the now inexistant section of the official page, and I saw a few things I would have modified if the page was an official one, so I figured it would be good to update your guide, I'm glad you're OK with it :)
: --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 05:11, 27 October 2022 (UTC)

== Thanks for signing my message ==

Thanks for signing my previously unsigned message, I'm new to this wiki and didn't know about this policy! [[User:Bean box69420|Bean box69420]] ([[User talk:Bean box69420|talk]]) 20:53, 20 December 2022 (UTC)

:No problem, glad I could help :) --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 20:59, 20 December 2022 (UTC)

== ThinkPad Z13 ==

Thanks for the revisions on my initial post. I also had not noticed the laptop guidelines earlier. The accessibility details about BIOS and beep codes, instructions for adding wacom file for the stylus, etc. should get added tonight or tomorrow. Soon, I plan to reformat, completely reset the BIOS, and reinstall Arch, so that should be a good opportunity to notice anything platform-specific that needs extra attention. I'll also bring anything notable in from the Lenovo Forums, as there are active discussions about current bugs and when/where to expect a fix. Take care! —[[User:PennRobotics|PennRobotics]] 15:26, 21 February 2023 (UTC)

:Well, thank '''you''' for adding the content in the first place! I'm just helping formatting things uniformly to help readability as a whole :)
:Don't feel rushed to add things, take all the time you need and don't hesitate to add to the dedicated page on a subject (e.g. [[Tablet PC#Stylus]]) if they are not providing the correct generic information or are unclear. Platform specific stuff should stay on the laptop page though.
:--[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 16:29, 21 February 2023 (UTC)

== Acer Swift 3 ==

Thank you so much for pointing out what I was missing in [[Acer Swift 3 SF314-512]]. I am new to this wiki and did read the guidelines but missed the requirement on some sections. If you don't mind, any further revisions would be appreciated. [[User:0xlogn|0xlogn]] ([[User talk:0xlogn|talk]]) 21:43, 21 February 2023 (UTC)

:I'm happy to have been helpful :)
:Props for reading the guidelines, but there's always things that slip between the cracks: it still happens to me sometimes ^^
:Do you want me to flag what I see as missing on the page or would you prefer that I list them here? (I'm going to sleep right now, will continue our exchange tomorrow)
:--[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 21:51, 21 February 2023 (UTC)

:: Either way is fine for me. Might as well flag it on the page in the case that I don't get back to it. [[User:0xlogn|0xlogn]] ([[User talk:0xlogn|talk]]) 22:13, 21 February 2023 (UTC)

:::[[Special:Diff/768330|Done]] :)
:::Thank you again for your contribution! --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 07:19, 22 February 2023 (UTC)

:::: I can't seem to find the webcam or bluetooth in {{ic|lspci}} or {{ic|lsusb}}. Also, I ''know'' that {{ic|Fn+F8}} is a logout key, but I don't know how to trap the key and determine what it sends. Also (added/adding) the footnotes from the function keys table now. --[[User:0xlogn|0xlogn]] ([[User talk:0xlogn|talk]]) 16:34, 22 February 2023 (UTC)

::::: Thanks again :)
::::: If the [http://linux-hardware.org/?probe=4e92800709 hardware probe] is right, Bluetooth should be visible through USB: {{ic|8087:0033}}, the webcam should appear as a PCI device: {{ic|8086:465d}}.
::::: For the keys, maybe try with a minimal environment like {{Pkg|twm}} to avoid a possible interference from your desktop environment. See [[Help:Laptop page guidelines#Capturing function keys]] if it's being caught by ''systemd-logind'' instead.
::::: --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 17:31, 22 February 2023 (UTC)

:::::: Both of those IDs from the probe were correct. I was expecting a more detailed description than {{ic|Intel Corp.}} (bluetooth) and {{ic|Intel Corporation Device}} (webcam).
:::::: I'll try to do the key in a little bit. Thank you!
:::::: --[[User:0xlogn|0xlogn]] ([[User talk:0xlogn|talk]]) 17:50, 22 February 2023 (UTC)

:::::::Thanks a bunch for double checking, I agree that the name used by ''lspci'' or ''lsusb'' is sometimes weird (e.g. some network card don't appear with their dedicated model number since they are close enough to an older one).
:::::::Take all the time you need, your page is already miles ahead of most "historical" ones (i.e. those created before having the laptop guidelines in place) :) --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 22:02, 22 February 2023 (UTC)

== Thanks! ==

Thanks for reviewing my changes on the [[Lenovo_Yoga_7i]] page, you definitely improved the presentation of the information a lot. Plus you helped me understand the mkinitcpio warnings too. My first time editing Arch Wiki went great!

[[User:Ask|Ask]] ([[User talk:Ask|talk]]) 23:50, 28 February 2023 (UTC)

:Thank ''you'' for taking the time to double check things with me :) --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 06:35, 1 March 2023 (UTC)

== Edits on the Dell G15 5525 Page ==

Hi, thanks for your review of the Dell G15 5525 Page! It is my first contribution to the wiki, and even though I read the guidelines, I have missed some recommendations. I updated the page, please let me know if there is any other info I should add!

{{Unsigned|2023-03-10T22:06:25|Verge36}}

:Hi! Thank ''you'' very much for your contribution. As I had written in my edit summary, the very few things that were missing were minor details: I'm happy to see you came back and fixed everything :)
:I've removed the style flag, but I also adjusted the hardware table, the PCI ID you had added for the microphone seems to be for an audio co-processor that is GPU-related (from the [https://www.kernelconfig.io/config_snd_soc_amd_acp6x kernel config] summary, it's related to "Yellow Carp" which is the codename for the Rembrandt family). I also used a [[Template:Yes]] for audio, since even if an unapproved kernel patch is needed, it's a simple addition to a list of hardware quirks, so nothing that should have unintended effect and the hardware works with the patch, so we can't say the support is "partial" as it's [[Help:Laptop page guidelines#Adding hardware information|for parts that still do not work correctly with applied modifications]].
:Once again, a huge thanks, many hardware pages get much less polish than what you made!
:Edit: You might also want to add an entry into [[Laptop/Dell#G15]] to sum up the hardware support for your model :)
:--[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 22:20, 10 March 2023 (UTC)

== Thanks for tidying up ==

Thanks for sweeping up my half-asleep scrawl! Especially the battery part, I remembered that last and stuffed it in without checking the rest of the wiki first :D.

Much appreciated.

{{Unsigned|2023-03-27T07:21:26|Muesli4brekkies}}

:You're welcome :P
:Thank you for taking the time to create the page, I've flagged a few things that are missing, I'll let you get to them when you find time :)
:--[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 07:30, 27 March 2023 (UTC)

== Sorry for messing up and thank you ==

Hi, sorry for messing up the [[VirtualBox/Install Arch Linux as a guest]] page. I read the page twice and didnt see that the stuff which I added was already on the page, i must have been pretty tired, sorry! And thank you.

[[User:DexyStorm|DexyStorm]] ([[User talk:DexyStorm|talk]]) 10:21, 18 April 2023 (UTC)

:Don't worry, if you did not see it it's probably because if was not at the best place in the logical reading order of the page, thanks for trying to improve the page anyway :)
:--[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 10:59, 18 April 2023 (UTC)

== Thank you for making my first Arch wiki's edit experience so amazing! ==

Thanks for helping fix the format in [[Lenovo ThinkPad X1 Carbon (Gen 11)]]. I want to let you know that your help really makes my first edit in Arch wiki a really amazing experience. I was surprised to see my first page can really help others! I will continue to contribute other pages (and of course, I will pay attention to the format next time).

{{Unsigned|2023-07-29T13:19:00|1arch}}

:I'm glad to see my edits have helped :)
:Don't sweat too much on formatting, it's an easy fruit to pick for anyone, while adding content is less trivial.
:Thank '''you''' for contributing !
:--[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 16:47, 29 July 2023 (UTC)

== Thanks for fixing my first wiki edit! ==
Thanks a lot for fixing [https://wiki.archlinux.org/index.php?title=Emacs&diff=prev&oldid=786364 my first edit] by doing the right thing and extending the relevant section at the Emacs wiki instead!

I'm active on on multiple plumbing-layer linux projects, so I have a baseline to compare contributions experience to... and still, you made my first-hand experience amazing ;)
--[[User:Darwi|Darwi]] ([[User talk:Darwi|talk]]) 20:57, 29 August 2023 (UTC)

:Thank '''you''' for adding the content in the first place! To be honest, at first I was trying to see how to make your solution work on more than GNOME, and stumbled upon the EmacsWiki page with exactly the complementary information ^^
:I'm happy to see the solution I chose of having all the content in an external page was OK for you :)
: --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 06:06, 30 August 2023 (UTC)

== Thanks for warm welcome ==

Hey Erus!

Thanks for your edit over my changes in [[Laptop/Other]]. I wanted to note as many things as possible as I recently ordered this magnificent device, and find that other people can't get it up and running.

--[[User:Michal.dev|Michal.dev]] ([[User talk:Michal.dev|talk]]) 11:43, 24 September 2023 (UTC)

:Thank ''you'' for the content addition :)
:It reminds me that I really should update the table template (proposal at [[Template talk:Laptops table header#Add definitions to headers]]) to have a somewhere that documents what's expected in each column :P
:--[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 12:01, 24 September 2023 (UTC)

:: That would be great, or some kind of an instruction how to put the information properly. Anyway, a reference on which device user has tested Arch would be also usable, I guess. In case there was a regression introduced on one package or another that prevents the device from working etc, user would have source of information. Maybe we should also think about having something like ''device pages'' like people from i.e. Lineage OS have, which version of kernel, from version... till... . IDK, just pondering :) --[[User:Michal.dev|Michal.dev]] ([[User talk:Michal.dev|talk]]) 07:31, 25 September 2023 (UTC)

:::Usually, only the model name and the date of the test is enough for most cases (e.g. saying it works with X processor is unnecessary, as the X+1 processor that was not tested is also likely to work, same for the kernel version which very rarely has regressions).
:::In the rare cases where there ''is'' a regression, we try to have it documented in a central point, e.g. [[Bluetooth#CSR dongle 0a12:0001]].
:::For the dedicated pages, we have [[Help:Laptop page guidelines]] to create them, and I hope we never have to add information on a specific page with "X is supported from kernel version X to Y", as devices in the PC world should rarely become unsupported at the kernel level.
:::--[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 08:42, 25 September 2023 (UTC)

:::: Sure! I've just added my [[Chuwi MiniBook X (2023)]] :). I will update it, as long as I find new issues and workarounds. It's a magnificent device. The one that I wanted - small, but powerful, and supporting (at least paritally :P) Linux / Android. It has it quirks (i.e. factory Windows 11 Installation did not recognize internal Wi-Fi. It can be no-go for "end-user".
:::: However, sometimes old devices fall off the tree, but I believe those must be ancient one...
:::: Anyway, I know that Arch is probably not the best distro for beginner (yet), but I hope my edits will ease it, at least a little :).
:::: BTW. LOOOOOOOVE your nickname ;).
::::--[[User:Michal.dev|Michal.dev]] ([[User talk:Michal.dev|talk]]) 14:09, 25 September 2023 (UTC)

:::::Thanks :) --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 17:07, 25 September 2023 (UTC)

== Thanks for styling my topic on zram ==

Hi Erus,

Thanks, I didn't know the wiki constructs like <nowiki>{{hc| ... | ... }}</nowiki>. Now I learned something new. They are apparently templates. Is there a guide on which templates to use when on the arch wiki?

Also thanks for correcting my stupid typo I missed when proof reading. [[User:Rohoog|Rohoog]] ([[User talk:Rohoog|talk]]) 17:14, 17 October 2023 (UTC)

:Hi :)
:Happy to see my style and wording edit was well received!
:You can take a look at [[Help:Style]] and the various pages in the Help namespace :)
:Always glad to be helpful :D
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 19:11, 17 October 2023 (UTC)

== Thanks for the BIOS flashing edits ==

First of all, thanks for all the style fixes to my section on getting a BIOS exe to work under Linux! I'm still pretty new to the Arch Wiki and I shouldn't have written it like a blog post.

To be honest though, I don't know how portable that advice is, which is why I set it aside as its own vendor-specific subsection. First of all, the innoextract step only applies to installers---ones that were made by a very specific installer set up tool. Second, the TDK extract step only applies to Phoenix TDK formatted firmwares. After all, it's just a firmware dev kit. When I search online for systems that have a Phoenix TDK BIOS, Lenovo is the only vendor that shows up. Third, the UEFI capsule format is also not a universal standard. Moreover, the firmware "device" itself might not be supported through <code>fwupd</code>.

Given how hacky the solution was for my one individual laptop, I don't know if it really deserves its own authoritative section with advice for other BIOS ''.exe''<nowiki/>'s. [[User:Xenia|Xenia]] ([[User talk:Xenia|talk]]) 23:47, 10 November 2023 (UTC)

:Thank you for warning me, I had mistakenly assumed that since fwupdtool could be used with the UEFI capsule, your advice could be generalized to other vendors.
:I'll move it back as a Lenovo-only solution.
:Thanks again for adding the information in the first place!
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 06:54, 11 November 2023 (UTC)

== OVMF examples ==

I thought at first that you were only referring to my use of templating to include the user page, but I realised after subst'ing the page that you also were probably referring to the links to the other user subpages I made. I wanted to share the research and workarounds I made but didn't want them littering up an already unwieldy page. I can have another go at making the section for the Examples page a self-contained thing with as much relevant information as possible, but linking to the subpages I made for each different section feels important for clarity and I'm not sure how best to include that info. I appreciate the correction and the link to the style guide and hope to find a way my information can be included for future users. [[User:Alydev|Alydev]] ([[User talk:Alydev|talk]]) 13:35, 13 February 2024 (UTC)

:Hi!
:Given the sub-pages are mostly configuration files, these would probably be better as a single external link, e.g. on a dedicated repository from your GitHub while the explanations would still fit in [[PCI passthrough via OVMF/Examples]]?
:P.S.: Thanks a bunch for wanting to share with others all the while trying to avoid cluttering an already huge page.
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 15:12, 13 February 2024 (UTC)
::I formatted the section for the Examples page and moved code snippets to GitHub. My primary anxiety in arranging things the way I did originally was avoiding link rot; I see the Arch wiki as a resource of Linux knowledge, and linking to external sites serving as effectively no more than a pastebin would seem to defeat this goal.
::On writing the new section for the Examples page I did consider converting the markdown document from GitHub and putting it at [[PCI_passthrough_via_OVMF/Examples/Alydev]], as then it would be in the wiki namespace and not the user namespace. But that felt a bit cheeky. [[User:Alydev|Alydev]] ([[User talk:Alydev|talk]]) 16:03, 13 February 2024 (UTC)
:::The configuration info could also be generalised and applied to the relevant wiki pages, now I think about it. I'll make a note and see if I can adapt them for that purpose. [[User:Alydev|Alydev]] ([[User talk:Alydev|talk]]) 16:06, 13 February 2024 (UTC)
::::Thanks again for the quick update :)
::::Looking through the page, most other entries seem to already have chosen either a code hosting platform or a pastebin to host the details, with only two of them being dead: if you're afraid GitHub could disappear, you can request an account on https://gitlab.archlinux.org/ and host things there :P
::::Thanks for avoiding the cheeky solution :)
::::If you have the time, updating the relevant pages would be awesome!
::::-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 17:13, 13 February 2024 (UTC)

== Your revert of [[Special:Diff/815771|my change to the system maintenance page]] ==

Hello, while I can understand that your revert may make support easier, I do not agree that this is enough reason to withhold the method I posted completely from Arch users, because I think it expands the range of application in which Arch can be used.

* A part of the Arch userbase is experts that do not request support from the community.
* The forum, a place where a lot of community support happens, already has a sticky post that says in all-caps that the system needs to be up to date. I think the community support places are the right place to publish the conditions needed to get support, instead of the wiki trying to anticipate something about the reader.
* Most people should be able to deduce that if you set your mirror to yesterday, your system is per definition not up to date.

How about adding a note like this to make it obvious?
{{Note|Do not ask for support with this configuration. By setting your mirror to yesterday your system will never be completely up to date, which is a requirement for getting support.}}
[[User:Squarewave|Squarewave]] ([[User talk:Squarewave|talk]]) 06:37, 3 September 2024 (UTC)

:Experts that do not request support can already put two and two together when reading [[Arch Linux Archive#How to restore all packages to a specific date]]. I'm also using [[User:Erus Iluvatar/Install#/etc/pacman.d/mirrorlist|something similar]] on my end, but having this hack or anything close to it documented in [[System maintenance]] would imply it has some official status, which it has not. As [[Arch Linux Archive]] explains, the archive is intended for troubleshooting, not daily use.
:As a side note, the snapshots for the archive are made without checking if the official mirror is in a coherent state or not: in some rare cases, they happen just as a rebuild is being uploaded and can be missing packages (possibly all of them, from memory the [https://archive.archlinux.org/repos/2022/02/01/core/ 2022-02-01 snapshot] is empty).
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 07:34, 3 September 2024 (UTC)
::Ok, thanks for the explanation.
::[[User:Squarewave|Squarewave]] ([[User talk:Squarewave|talk]]) 14:49, 3 September 2024 (UTC)

== I messed up, thanks for fixing ==

I accidentally edited the page for the XPS 9315 instead of XPS 9340... sorry about that. I see that you're cleaning up after me, thank you :3 [[User:AdlaiN|AdlaiN]] ([[User talk:AdlaiN|talk]]) 15:39, 23 February 2025 (UTC)

:Mistakes happen, happy to see my job is appreciated :P [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 16:52, 23 February 2025 (UTC)

== Could you look at this comment? ==

Hey Erus. Could you look at my comment there: https://wiki.archlinux.org/title/Talk:AWK#c-Ismailarilik-20250316093200-Lahwaacz-20250315211100

It is about my latest changes and I am willing to change myself WRT your comments. That comment might not be the place for it but I didn't wanna break the context. [[User:Ismailarilik|Ismailarilik]] ([[User talk:Ismailarilik|talk]]) 09:37, 16 March 2025 (UTC)

:Your rationale sounds fine to me, don't worry about being too disruptive, if needed we'd have no issue raising it in your talk page :)
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 13:13, 16 March 2025 (UTC)

== Explicit Anchor on PrusaSlicer page ==

Note that by undoing my explicit anchor you are breaking a code feature we are working on: https://gitlab.archlinux.org/archlinux/packaging/packages/prusa-slicer/-/merge_requests/4

I understand that section headers already provide implicit anchors but we really need one that does persist any reformatting and changing section titles. And you stated this page requires substantial changes, thus we need to rely on a persistent anchor. Should you know a better way to achieve this I am open for a suggestion. [[User:Schiele|Schiele]] ([[User talk:Schiele|talk]]) 19:08, 30 April 2025 (UTC)

:There are no persistent anchors. If something in the wiki gets changed then references to it will need to be updated. In the worst case, you'll simply land on the top of the page and will need to look through the whole page for the relevant information. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 05:02, 1 May 2025 (UTC)
::Well, technically there are persistent anchors the way I did them. And I didn't invent this approach but took it from the official MediaWiki help page https://www.mediawiki.org/wiki/Help:Links. So if you are saying we cannot use this feature this is not a technical limitation but a policy limitation. Given that I experienced the Arch community to be a very technical community I would at least like to understand the rationale behind this policy since it is technically unpractical to make new package releases each time we want to improve the Wiki page. And while it is true that worst case the user will end up at the top of the page. But this creates unnecessarily bad user experience. Wouldn't we have a better option that would be acceptable but given that we technically have a better option but just disallow it by policy it would be useful to provide the rationale for making the user experience worse here.
::Since I am definitely not a Wiki expert I was asking for better alternatives that I simply might not be aware of. But just rejecting the solution I found without providing neither a rationale nor an alternative feels a bit disturbing to be honest. [[User:Schiele|Schiele]] ([[User talk:Schiele|talk]]) 06:36, 1 May 2025 (UTC)
:::We don't use a good chunk of mediawiki features, persistent anchors is one of them. Would having a note at the top of the page highlighting the proper bug reporting etiquette be an acceptable solution? I can't find an other example quickly, but it's probably not the only software where upstream requires testing with their packaging before accepting a bug report. [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 06:45, 1 May 2025 (UTC)
::::So the background on the feature was that there is a menu item in the upstream software to report issues with the software. Originally this points to the bug reporting system of the vendor (Prusa). Their team however gets frustrated when people report bugs not coming from their official binary. Since in Arch we build our own binary this created tensions between the Arch maintainers and the Prusa development team since they feel that we redirect our users to their team even for issues that we might have produced by our way of packaging. So it is not purely about etiquette but to give our users the best possible way to report their bugs to the correct audience. In the end we want to spend our effort in maintaining good software packages and not in fighting a war with the software vendor's development team.
::::I fear if we make it only slightly harder for the user to find the correct information there are chances that they simply don't read the information at all. If we really can't use persistent anchors would then maybe a sub page be the right approach or is this another feature we don't use by policy?
::::Getting back to the policy question: I understand that we might want to have policies to make the overall quality of the Wiki better. The part that I don't understand is why there are policies (like not using persistent anchors) where apparently nobody can't provide the rationale behind. I personally still fail to see how not using them improves the overall quality of the Wiki? Being a solution-oriented nature this is something I have difficulties to understand: Why do we impose restrictions on us, when the restriction does not provide any benefit we can reason about but actually makes the overall user experience worse? I mean we are very proud about the overall quality of the ArchWiki, so why are we preventing a usability improvement here without having a reason? [[User:Schiele|Schiele]] ([[User talk:Schiele|talk]]) 07:06, 1 May 2025 (UTC)
:::::The rationale for not using manual anchors is because we don't need them. Broken section links get fixed after a bot flags them.
:::::Why don't you simply use the Arch package issue tracker URL instead? That's where people are expected to report issues with the package.
::::: -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 07:15, 1 May 2025 (UTC)
::::::It seems you have a very Wiki-centristic view. For sure you would detect broken links coming from _within_ the Wiki but you would never detect broken links coming from outside, which is exactly what persistent links are useful for. I don't see why you are not considering links from outside the Wiki when you say that we don't need this feature? I consider the Wiki a value for the Arch community and a lot of pages are even so good that they provide value even to users of other distributions. I think we shouldn't consider the Wiki just as a value for it's own sake since in my opinion we drastically undervalue it that way.
::::::I thought about redirecting everything to our own tracking system but then we would receive _all_ the reports, including them about bugs that users could reproduce in the upstream software unrelated to our packaging and therefore could be rightfully reported to the upstream vendor, offloading the package maintainers. That's why I thought documenting the approach to verify a problem with the upstream binary and reporting to the right audience is a good way forward. That's how I described the approach in the page. [[User:Schiele|Schiele]] ([[User talk:Schiele|talk]]) 07:26, 1 May 2025 (UTC)
:::::::One additional idea that came to my mind that might solve this problem in a different way: How about creating a special entry page like PrusaSlicer/BugReporting or something like this, that just redirects to the corresponding section of the main page automatically. While that seems unnecessarily complicated to me it at least provides good user experience without violating your policy and a broken link in the redirect you could then detect with the bot.
:::::::Is that a solution you would prefer? [[User:Schiele|Schiele]] ([[User talk:Schiele|talk]]) 07:35, 1 May 2025 (UTC)
:::::::Some packages already contain links to the wiki. If they get outdated, someone eventually fixes it. This really isn't as big of an issue as you're making it out to be.
:::::::We're not going to create special anchors or subpages just for an article about one single package.
:::::::This is not the first package with an upstream that's hostile to distro packaging. Though another one I know didn't have a wiki article.
::::::: -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 07:46, 1 May 2025 (UTC)
::::::::Ok, got it. Could you at least check whether my current section title for the issue reporting section is good according to how you generally want to have it named? I want to prevent that right after establishing the link I have to change it again. [[User:Schiele|Schiele]] ([[User talk:Schiele|talk]]) 08:19, 1 May 2025 (UTC)
:::::::::It should use sentence case. See [[Help:Style#Section headings]]. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 16:03, 1 May 2025 (UTC)

== Thanks ==

Thanks for the help on the GPD MicroPC 2 page. I'm utter trash at wiki formatting, and working on the page for (obviously) informational sake since early backers only got them on Friday and want to help people can get Linux working great on it. Certainly appreciate it [[User:MoistGoat|MoistGoat]] ([[User talk:MoistGoat|talk]]) 03:54, 3 September 2025 (UTC)

:Honestly for someone new to MediaWiki formatting, it's far from "utter trash" :D
:Keep up the good work, style and such I can fix, while the content can only be written by someone who owns the hardware :)
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 06:55, 3 September 2025 (UTC)

== Thanks ==

Hey,

Thanks for the [https://wiki.archlinux.org/index.php?title=Discord&diff=0&oldid=858436 corrections] on the discord page, I'm still pretty new with the wiki so yeah, thanks! [[User:Noxie|Noxie]] ([[User talk:Noxie|talk]]) 11:04, 22 December 2025 (UTC)

:And thank ''you'' for coming back and improving your solution!
:Always happy to see my work appreciated :)
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 11:21, 22 December 2025 (UTC)

== Thank you and happy New Year! ==

As a freshman and a non-native English speaker. Thank you for correcting on my last 2 edits, the first "GPGME error: No data:" made me realize I haven't find the right article until your mention, causing repetition (Should I delete my edits directly?), while the second "Kernel panic example: missing initramfs" made me realize I messed things up (Though this is the first time I saw a blue screen on Linux and learned a lot to solve the issuse without reinstall the whole system). Honestly, I learned a lot during my reading and writing on Arch, I will keep learning and make Arch Linux be part of my life.

Happy New Year!

[[User:Yuantianbao|Yuantianbao]] ([[User talk:Yuantianbao|talk]]) 01:01, 30 December 2025 (UTC)

:I won't take credit for @[[User:Lahwaacz|Lahwaacz]]: he's the one who flagged your first addition for merging to the existing section :) I don't think it deserves deletion, the page you had picked is far from illogical, we'll just keep a single version of the solution in one of the pages and link there from the other to help discoverability.
::
:No worries about the second change I reverted: the general idea of fixing an issue and sharing the solution to everyone is laudable, though in this specific instance it seemed excessive to me, as the issue should be apparent before rebooting ([[mkinitcpio]] will print error messages that should then make it trivial to troubleshoot root cause).
::
:I too wish you a happy new year and plenty more on Arch ;)
::
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 08:18, 30 December 2025 (UTC)

== Thank you! <3 ==

Thank you so much for the excellent adjustments in [[Lm sensors#MSI MAG B650/Z890 TOMAHAWK WIFI (MS-7D75/MS-7E32) /MAG B550 MORTAR WIFI (MS-7C94)]].

KISS <3 [[User:Damachine|Damachine]] ([[User talk:Damachine|talk]]) 19:11, 11 February 2026 (UTC)

:I'm happy they were well received! A thank in return for having added the content, I mostly make sure the form helps it :)
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 19:37, 11 February 2026 (UTC)

== Question regarding recent edits to Plasma Login Manager ==

Hi Erus,

Thanks for your recent formatting cleanups on the Plasma Login Manager page. I'm trying to make sure I fully understand the wiki standards for future contributions (that was my very first one), and I was hoping you could clarify a couple of the guidelines you referenced in your edit summary.

First, regarding the placement: you mentioned that new entries go at the bottom. I combed through <code>Help:Style</code> to read up on this, but I couldn't seem to find that specific rule anywhere. My thought process for placing the "Custom wallpaper plugin" section higher up was simply logical flow: changing the background is typically the very first users do with their login screen, whereas features like auto-login seem quite a bit more niche. Are sections strictly ordered chronologically by when they were added, or is there a specific guideline for prioritizing core system mechanics over aesthetic configuration?

Secondly, regarding the formatting: you noted that a numbered list wasn't needed for this short set of steps. That's good to know! Just so I can get it right in the future, is there a general threshold in the style guide for when to use ordered lists versus standard prose?

Thanks for taking the time to clarify! [[User:Prod. EGO|Prod. EGO]] ([[User talk:Prod. EGO|talk]]) 17:15, 9 March 2026 (UTC)

:Hi :) First of all a big thank you for your first contribution as our Wiki would not be so well furnished nor well regarded if it only relied on a few regulars like me :P
::
:I must admit I was mostly working from memory on the ordering, and re-reading the section it's better in this case to go with the logical order, please do a manual/partial revert to restore the placement.
:Where chronological order is more customary (but as you point out, undocumented) is for subsections in "Troubleshooting" as it helps ensure the same issue does not get added multiple times or with multiple solutions. Even for that, some pages with numerous troubleshooting sections end up being sorted by topic.
::
:Regarding the usage of list, I try to avoid any of them whenever possible (though to be completely transparent, in this case what reminded me to avoid it was encountering [[Template:hc#Known issue]]). In particular, numbered lists should be reserved for steps that cannot be ordered differently (e.g. [[Installation guide#Boot the live environment]]: can't get to the boot loader menu until you've selected the boot device).
:My personal threshold is around five steps '''and''' that the list helps readability: i.e. cutting a five sentence paragraph into five short steps does not "feel" right, but [[Toshiba Satellite L300#BIOS upgrade]] is probably more readable than a blob of text.
::
:I should have noted in my summary that I was being "opinionated" in my edit (I try to extend the advice from [[Help:Style#Language register]] to the general layout of the sections: I often ask myslef how I would expect a printed book on the topic to look to decide on formatting), don't hesitate reach out to anyone if you're unsure when a followup change they made is a fix to strictly abide by the guidelines or if it's more a case of trying to get the text flow in line with their personal preferences :D
::
:-- [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 20:01, 9 March 2026 (UTC)
::Hi Erus,
::Thanks for the warm welcome and the detailed explanation!
::I went ahead and did a manual revert to restore the placement of the "Custom wallpaper plugin" section so it flows logically again. I also made sure not to reintroduce the ordered list, as your reasoning for keeping it as standard prose makes perfect sense for such a short set of steps.
::I really appreciate the extra context on how troubleshooting sections are typically ordered and your personal threshold for using lists. It helps a lot to understand the thought process behind the wiki's formatting choices, especially given I am brand new to making contributions. I'll definitely be sure to reach out if I run into any confusing edits in the future!
::Thanks again for your help and guidance. 🙂 [[User:Prod. EGO|Prod. EGO]] ([[User talk:Prod. EGO|talk]]) 20:22, 9 March 2026 (UTC)

== <s>Might need additional fix</s> ==

https://wiki.archlinux.org/index.php?title=Plasma_Login_Manager&diff=prev&oldid=870441

changing `$ sudo` to `#` changes the behavior of `~` as well `$USER`.

The former copies /home/exampleuser/.face.icon to /var/lib/AccountsService/icons/exampleuser

The latter copies /root/.face.icon to /var/lib/AccountsService/icons/root [[User:Bitwaba|Bitwaba]] ([[User talk:Bitwaba|talk]]) 10:16, 6 April 2026 (UTC)

:Thanks for the heads up, I've replaced both with a pseudo-variable in [[Special:Diff/870666]], closing :) --[[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 12:01, 6 April 2026 (UTC)

== Regarding NetworkManager/Privacy Merge status ==

Hi! I am reaching out regarding your status tag added on 23 March 2024 to merge [[NetworkManager#Configuring MAC address randomization]] into [[NetworkManager/Privacy]].

I've created a talk page discussion at [[Talk:NetworkManager#In relation to NetworkManager/Privacy]] with my stance on this. Also I've created a talk page discussion at [[Help talk:Template#Have editors create the talk page discussions for Status templates: Merge and Move]]. I would like for you to review these both and share your thoughts on the same. Thanks! [[User:TheKnightSky|TheKnightSky]] ([[User talk:TheKnightSky|talk]]) 12:49, 8 May 2026 (UTC)

:Hi, I'll look into both tomorrow :) [[User:Erus Iluvatar|Erus Iluvatar]] ([[User talk:Erus Iluvatar|talk]]) 18:24, 8 May 2026 (UTC)

Testing (Español)

2026-05-08T18:23:36Z

Erus Iluvatar: Fix broken redirect

#REDIRECT [[Official repositories (Español)#Repositorios de prueba]]

Community repository (Español)

2026-05-08T18:22:55Z

Erus Iluvatar: Archive forgotten redirect

#REDIRECT [[ArchWiki:Archive]]
[[Category:Archive]]

GNOME (Français)/Gedit (Français)

2026-05-07T13:35:50Z

Erus Iluvatar: Fix previous edit

[[Category:GNOME (Français)]]
[[Category:Text editors (Français)]]
[[de:Gedit]]
[[en:Gedit]]
[[es:GNOME (Español)/Gedit]]
[[ja:GNOME/Gedit]]
[[ru:GNOME (Русский)/Gedit]]
[[zh-hans:GNOME/Gedit]]
{{TranslationStatus (Français)|GNOME/Gedit|2026-05-07|873235}}
[[Wikipedia:fr:gedit|gedit]] est un éditeur de texte à usage général pour GNOME.

== Installation ==

[[Installez]] le paquet {{Pkg|gedit}}.

Pour des caractéristiques supplémentaires, installez le paquet {{Pkg|gedit-plugins}}.

Gedit peut utiliser plusieurs dictionnaires de vérification orthographique, voir [[Language checking]].

== Configuration ==

=== Ne pas terminer les fichiers par une nouvelle ligne ===

Si vous voulez vous assurer que Gedit ne termine pas les fichiers par une nouvelle ligne, exécutez ce qui suit:

$ gsettings set org.gnome.gedit.preferences.editor ensure-trailing-newline false

=== Enregistrer les versions de sauvegarde des fichiers modifiés ===

Si vous le souhaitez, Gedit peut créer une copie des sauvegardes d'un fichier modifié (le contenu du fichier de sauvegarde sera le même que le contenu du fichier d'origine avant que la modification ne soit effectuée) puis enregistrez. Le nom du fichier de sauvegarde sera le même que le nom du fichier d'origine mais suffixé d'un symbole ~. Par conséquent, pour le fichier nommé {{ic|file1}}, la copie de sauvegarde porterait le nom {{ic|file1~}}. Les fichiers de sauvegarde sont masqués par défaut.

Pour activer ce comportement, accédez au panneau ''Preferences'' de Gedit (pour les utilisateurs de GNOME Shell, cela peut être trouvé dans le menu général de Gedit). Dans le panneau ''Preferences'', cliquez sur l'onglet ''Editeur'' et cochez l'option ''Créer une copie de sauvegarde des fichiers avant de les enregistrer.''

=== Coloration syntaxique ===

Gedit est installé de base avec plusieurs caractéristiques syntaxique grâce à {{Pkg|gtksourceview4}}, donc cette section présente des exceptions.

==== PKGBUILD ====

[[Installez]] {{AUR|gtksourceview4-pkgbuild}} pour obtenir une coloration syntaxique dans [[PKGBUILD (Français)|PKGBUILDs]].

== Voir égalemment ==

* [https://wiki.gnome.org/Apps/Gedit Apps/Gedit - GNOME Wiki!]

GNOME (Français)/Gedit (Français)

2026-05-07T13:35:36Z

Erus Iluvatar: Multiple minor style fixes + Template:TranslationStatus

[[Category:GNOME (Français)]]
[[Category:Text editors (Français)]]
[[de:Gedit]]
[[en:Gedit]]
[[es:GNOME (Español)/Gedit]]
[[ja:GNOME/Gedit]]
[[ru:GNOME (Русский)/Gedit]]
[[zh-hans:GNOME/Gedit]]
{{TranslationStatus (Français)|GNOME/Gedit|873235|2026-05-07}}
[[Wikipedia:fr:gedit|gedit]] est un éditeur de texte à usage général pour GNOME.

== Installation ==

[[Installez]] le paquet {{Pkg|gedit}}.

Pour des caractéristiques supplémentaires, installez le paquet {{Pkg|gedit-plugins}}.

Gedit peut utiliser plusieurs dictionnaires de vérification orthographique, voir [[Language checking]].

== Configuration ==

=== Ne pas terminer les fichiers par une nouvelle ligne ===

Si vous voulez vous assurer que Gedit ne termine pas les fichiers par une nouvelle ligne, exécutez ce qui suit:

$ gsettings set org.gnome.gedit.preferences.editor ensure-trailing-newline false

=== Enregistrer les versions de sauvegarde des fichiers modifiés ===

Si vous le souhaitez, Gedit peut créer une copie des sauvegardes d'un fichier modifié (le contenu du fichier de sauvegarde sera le même que le contenu du fichier d'origine avant que la modification ne soit effectuée) puis enregistrez. Le nom du fichier de sauvegarde sera le même que le nom du fichier d'origine mais suffixé d'un symbole ~. Par conséquent, pour le fichier nommé {{ic|file1}}, la copie de sauvegarde porterait le nom {{ic|file1~}}. Les fichiers de sauvegarde sont masqués par défaut.

Pour activer ce comportement, accédez au panneau ''Preferences'' de Gedit (pour les utilisateurs de GNOME Shell, cela peut être trouvé dans le menu général de Gedit). Dans le panneau ''Preferences'', cliquez sur l'onglet ''Editeur'' et cochez l'option ''Créer une copie de sauvegarde des fichiers avant de les enregistrer.''

=== Coloration syntaxique ===

Gedit est installé de base avec plusieurs caractéristiques syntaxique grâce à {{Pkg|gtksourceview4}}, donc cette section présente des exceptions.

==== PKGBUILD ====

[[Installez]] {{AUR|gtksourceview4-pkgbuild}} pour obtenir une coloration syntaxique dans [[PKGBUILD (Français)|PKGBUILDs]].

== Voir égalemment ==

* [https://wiki.gnome.org/Apps/Gedit Apps/Gedit - GNOME Wiki!]

GNOME/Gedit

2026-05-07T13:31:48Z

Erus Iluvatar: Fix fr link

[[Category:GNOME]]
[[Category:Text editors]]
[[de:Gedit]]
[[es:GNOME (Español)/Gedit]]
[[fr:GNOME (Français)/Gedit]]
[[ja:GNOME/Gedit]]
[[ru:GNOME (Русский)/Gedit]]
[[zh-hans:GNOME/Gedit]]
[[Wikipedia:gedit|gedit]] is a general-purpose text editor for GNOME.

== Installation ==

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

For additional features, install the {{Pkg|gedit-plugins}} package.

Gedit can use multiple spell checking dictionaries, see [[Language checking]].

== Configuration ==

=== Do not end files with a new line ===

If you want to ensure that gedit does not end files with a newline, execute the following:

$ gsettings set org.gnome.gedit.preferences.editor ensure-trailing-newline false

=== Save backup versions of edited files ===

If desired, gedit can create a backup copy of an edited file - the contents of the backup file will be the same as the contents of the original file before the edit was made and then saved. The backup file's name will be the same as original file's name but suffixed with a ~ symbol. Hence, for the file called {{ic|file1}} the backup copy would have the name {{ic|file1~}}. Backup files are hidden by default.

To enable this behaviour, access gedit's Preferences panel (for GNOME Shell users, this can be found in gedit's global menu). In the preferences panel, click on the ''Editor'' tab and tick the option ''Create a backup copy of files before saving.''

=== Syntax highlighting ===

Gedit comes out-of-box with several syntax highlight thanks to {{Pkg|gtksourceview4}}, so this section show exceptions.

==== PKGBUILD ====

[[Install]] {{AUR|gtksourceview4-pkgbuild}} to have syntax highlight in [[PKGBUILD]]s.

== See also ==

* [https://wiki.gnome.org/Apps/Gedit Apps/Gedit - GNOME Wiki!]

Gedit (Français)

2026-05-07T13:31:24Z

Erus Iluvatar: Erus Iluvatar moved page Gedit (Français) to GNOME (Français)/Gedit (Français): Help:I18n#Page titles

#REDIRECT [[GNOME (Français)/Gedit (Français)]]

GNOME (Français)/Gedit (Français)

2026-05-07T13:31:24Z

Erus Iluvatar: Erus Iluvatar moved page Gedit (Français) to GNOME (Français)/Gedit (Français): Help:I18n#Page titles

[[Category:GNOME (Français)]]
[[Category:Text editors (Français)]]
[[de:Gedit]]
[[en:Gedit]]
[[es:GNOME (Español)/Gedit]]
[[ja:GNOME/Gedit]]
[[ru:GNOME (Русский)/Gedit]]
[[zh-hans:GNOME/Gedit]]
[[Wikipedia:gedit|gedit]] est un éditeur de texte à usage général pour GNOME.

== Installation ==

[[Installer]] le paquet {{Pkg|gedit}}.

Pour des caractéristiques supplémentaires, installer le paquet {{Pkg|gedit-plugins}}.

Gedit peut utiliser plusieurs dictionnaires de vérification orthographique, voir [[Language checking]].

== Configuration ==

=== Ne terminez pas un fichier par une nouvelle ligne ===

Si vous voulez vous assurer que Gedit ne termine pas les fichiers par une nouvelle ligne, exécutez ce qui suit:

$ gsettings set org.gnome.gedit.preferences.editor ensure-trailing-newline false

=== Enregistrer les versions de sauvegarde des fichiers modifiés ===

Si vous le souhaitez, Gedit peut créer une copie des sauvegardes d'un fichier modifié (le contenu du fichier de sauvegarde sera le même que le contenu du fichier d'origine avant que la modification ne soit effectuée) puis enregistrez. Le nom du fichier de sauvegarde sera le même que le nom du fichier d'origine mais suffixé d'un symbole ~. Par conséquent, pour le fichier nommé {{ic|file1}}, la copie de sauvegarde porterait le nom {{ic|file1~}}. Les fichiers de sauvegarde sont masqués par défaut.

Pour activer ce comportement, accédez au panneau ''Preferences'' de Gedit (pour les utilisateurs de GNOME Shell, cela peut être trouvé dans le menu général de Gedit). Dans le panneau ''Preferences'', cliquez sur l'onglet ''Editeur'' et cochez l'option ''Créer une copie de sauvegarde des fichiers avant de les enregistrer.''

=== Coloration syntaxique ===

Gedit est installé de base avec plusieurs caractéristiques syntaxique grâce à {{Pkg|gtksourceview4}}, donc cette section présente des exceptions.

==== PKGBUILD ====

[[Installer]] {{AUR|gtksourceview4-pkgbuild}} pour obtenir une coloration syntaxique dans [[PKGBUILD]]s.

== Voir égalemment ==

* [https://wiki.gnome.org/Apps/Gedit Apps/Gedit - GNOME Wiki!]

Mask

2026-05-06T06:51:08Z

Erus Iluvatar: Undo revision 873114 by Bend1010 (talk) - All systemctl redirects point to the same place, Help:Reading does not need to be listing all possible commands for readers to infer the usage pattern

#redirect [[Help:Reading#Control of systemd units]]

Laptop/Dell

2026-05-05T16:17:34Z

Erus Iluvatar: /* Latitude */ Update date entry

[[Category:Dell]]
{{Laptops navigation}}

== Software ==

[[Wikipedia:Dell|Dell]] offers in-house Linux support for a subset of hardware, contributing to the {{ic|dell-smm-hwmon}} [[kernel module]] (refer to it's documentation here[https://docs.kernel.org/hwmon/dell-smm-hwmon.html]) and providing native Linux utilities to control hardware on supported devices. These utilities include:

* {{pkg|libsmbios}} a suite of programs for controlling hardware. Key programs include:
** {{ic|smbios-battery-ctl}}: Get and set battery charge configuration
** {{ic|smbios-keyboard-ctl}}: Control keyboard backlight illumination and light sensors
** {{ic|smbios-lcd-brightness}}: Set separate screen brightness for battery and mains
** {{ic|smbios-sys-info}}: Get and set service, asset and property tags
** {{ic|smbios-thermal-ctl}}: Get and set thermal modes - usually balanced, cool-bottom, quiet, and performance
** {{ic|smbios-wireless-ctl}}: Get and control the status of radio hardware
* {{aur|dell-command-configure}} ({{ic|cctk}}) enables BIOS configuration from userland. On some devices this is the only method for configuring and persisting custom battery charge behaviour.

ACPI {{ic|platform_profiles}} are natively supported on newer kernels which enables setting thermal modes without Dell specific software.[https://web.git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=for-next&id=996ad412981024a9bb90991ab195685d37187bbd]

Dell also makes firmware updates for some devices available via the [[fwupd|Linux Vendor firmware Service (LVFS)]].

== Accessibility ==

* The firmware is graphical and has a tightly-packed simple text menu (with expandable categories) on the left, with fairly small text.
* All the settable options are in a large pane on the right, again.
* ''Apply'' must be clicked to make any changes.
* The touch screen and the touchpad work in the firmware, and the tabulation and arrow keys also allow cursoring around the different options and buttons.
** The {{ic|Tab}} key alternates between three zones: the menu at the left, the settings pane at the right, and the ''Apply'', ''Restore Settings'', and ''Exit'' buttons. The arrow keys must then be used to cursor around the items within each of those zones.
* The firmware contains many radio buttons and checkboxes, but these are only in the right pane.

== Model list ==

=== Alienware ===

{{Laptops table header}}
| Alienware M11x || 2012-02-28 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{-}} || {{Y|Untested}} || ||
|-
| Alienware M14xR2 || 2013-06-15 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || ||
|-
|}

=== Inspiron ===

{{Laptops table header}}
| Inspiron 13 2-in-1 (5368) || 2016-12-20 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| [[Dell Inspiron 13 (5378)|Inspiron 13 2-in-1 (5378)]] || 2023-10-14 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| Inspiron 13 (5391) || 2021-03-30 || {{Yes}} || {{Yes}}* || {{-}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || {{Y|Untested: Fingerprint reader}} || *Needs {{ic|1=snd_hda_intel.dmic_detect=0}}
|-
| Inspiron 13 (7348) || 2021-05-28 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{G|Hibernate: Untested}} || ||
|-
| Inspiron 13 (7370) || 2017-12 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Y|Partial*}} || [https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1641290 Fingerprint reader is unsupported].|| *Does not wake up after closing the screen lid. {{ic|Fn}} [https://bugzilla.kernel.org/show_bug.cgi?id=198393 Wireless toggle does not work]
|-
| Inspiron 14 (3420) || 2016-09-03 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{G|Hibernate: Untested}} || || Requires {{Pkg|broadcom-wl-dkms}}
|-
| Inspiron 14 (5425) || 2023-01-18 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|SD card reader: Untested}} ||
|-
| Inspiron 14 2-in-1 (7425) || 2022-01-24 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}* || {{Yes}} || || *Fingerprint reader and Bluetooth cause system to hang on wake from sleep, need to add scripts to shutdown on sleep and restart on wake.
|-
| Inspiron 14 Plus (7430) || 2023-03 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{G|Yes* Hibernate:Untested}} || {{Y|Fingerprint reader: Untested}} || HDMI always turn on NVIDIA, but monitor through thunderbolt can work with Intel only. Sound works better with pipewire.
|-
| Inspiron 14 (7490) || 2023-08-28 || {{G|HDMI untested}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{G|Yes* Hibernate:Untested}} || {{Y|SD card reader: Untested}} || Requires AHCI to be [https://github.com/foremind/Dell-Inspiron-7490-OpenCore/tree/main/Fix-BIOS-Settings manually enabled]
|-
| Inspiron 15 (3511) || 2026-01-30 || {{G|Untested: Dedicated GPU, HDMI, DisplayPort}} || {{Yes}} || {{-}} || {{G|[[Network configuration/Wireless#rtl8821ce|Yes*]]}} || {{Y|Untested}} || {{Yes}} || {{Y|Untested: Thunderbolt, SD card reader}} || S3 sleep is not supported
|-
| Inspiron 15 (3521) || 2025-07-06 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| Inspiron 15 (3525) || 2023-08-08 || {{G|HDMI untested}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{G|Yes* Hibernate:Untested}} || || *[https://github.com/jfredrickson/disable-c6 Disabling C6 states] fixes closing the lid and suspending
|-
| [[Dell Inspiron 3593|Inspiron 15 (3593)]] || 2024-11-09 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| Inspiron 15 (5515) || 2021-07-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Partial}}* || {{Yes}} || || * Not reliable, needs restarting or running {{ic|modprobe -r btusb && modprobe btusb}} as root when having issues.
|-
| Inspiron 15R (5521) || 2022-09-26 || {{G|HDMI untested}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|SD card reader: Untested}} || Function keys need to be manually assigned.
|-
| Inspiron 15 (5547) || 2016-01-25 || {{G|AMD GPU: Untested}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|SD card reader: Untested}} ||
|-
| Inspiron 15 (5559) || 2021-07-19 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || ||
|-
| Inspiron 15 (5566) || 2020-09-24 || {{G|HDMI untested}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|SD card reader: Untested}} ||
|-
| Inspiron 15 (5567) || 2020-04-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Dell Inspiron 5575|Inspiron 15 (5575)]] || 2019-12-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: HDMI SD card reader}} ||
|-
| Inspiron 15 (7537) || 2016-06-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | Volume up / down button needs some modifying to work all other buttons work with drivers that come with the kernel. ACPI battery is not detected on bootup and requires you to plug in and out the AC adapter.
|-
| Inspiron 15 (7548) || 2015-05 || {{G|HDMI untested}} || {{Y|Untested}} || {{-}} || {{Yes}} || {{Yes}} || {{G|Hibernate: Untested}} || {{Y|SD card reader: Untested}} || If the kernel [https://bbs.archlinux.org/viewtopic.php?id=200763 panics] during bootup replace the 'keyboard'-hook with the specific module.
|-
| Inspiron 15 (7559) || 2016-08 || {{Yes}}* || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || *[https://github.com/Bumblebee-Project/bbswitch/issues/140 bumblebee with issue]
|-
| Inspiron 15 (7566) || 2025-03 || {{Yes}} || {{Yes}}* || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || *Subwoofer requires channel remapping via HDAJackRetask.
|-
| Inspiron 15 (7570) || 2021-10-27 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | USB-C DisplayPort alt-mode tested with a Dell P2721Q monitor. 65W of power, USB hub and Video delivered over USB-C work well. Rare issues with the monitor sometimes losing the video connection when switching users or logging out (on resolution changes). The power and USB keep working though.
|-
| [[Dell Inspiron 7586|Inspiron 15 (7586)]] || 2019-07-01 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{G|Hibernate: Untested}} || {{Y|Webcam: Untested}} || Fingerprint reader works with proprietary driver.
|-
| [[Dell Inspiron 15 (7590)|Inspiron 15 (7590)]] || 2020-02 || {{Yes}} || {{Y|Partial*}} || {{-}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Y|Thunderbolt: Untested}} || *See dedicated page
|-
| Inspiron 16 (5620) || 2024-03-15 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Fingerprint Reader: Working SD card: Not tested}} ||
|-
| [[Dell Inspiron 16 Plus (7620)|Inspiron 16 Plus (7620)]] || 2022-08-08 || {{Yes}} || {{Y|Only bottom speakers work}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Finger print reader: It works if it is used only in one operating system}} ||
|-
| [[Dell Inspiron 16 2-in-1 (7620)|Inspiron 16 2-in-1 (7620)]] || 2022-12-12 || {{Yes}} || {{Y|Only bottom speakers work}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| Inspiron 15 (5590) || 2026-02-25 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
|}

=== Latitude ===

{{Laptops table header}}
| Latitude D620 || 2007-05-17 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Y|Untested: Smart card reader}} ||
|-
| Latitude D630 || 2015-12-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{-}} || {{Y|Untested}} || ||
|-
| Latitude D820 || 2007-05-17 || {{Yes}} || {{Yes}} || {{Yes}} ||{{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| Latitude D830 || 2007-08-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| Latitude 3540 || 2022-06-28 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | Flaky Bluetooth coexistence with Wi-Fi
|-
| Latitude E5400 || 2021-11-11 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || Bluetooth LED does not glow. ||
|-
| Latitude 5290 2-in-1 || 2022-05 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Y|Power off: OK}} || {{Y|Untested: Webcam Fingerprint sensor}} ||
|-
| Latitude 5490 || 2022-02 || {{Yes}} || {{Yes}}* || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Hibernate: Untested**}} || Random Screen flicker with ''i915 [drm] *ERROR* CPU pipe A FIFO underrun'' in kernel logs. Solved with {{ic|1=intel_idle.max_cstate=4}} || *[[Laptop#Audio mute LED|audio mute LED]] use {{ic|1=model=mute-led-gpio}} **[https://bbs.archlinux.org/viewtopic.php?pid=1902231#p1902231 Kernel panic on suspend] solved with {{ic|1=acpi_enforce_resources=lax i915.enable_dc=0}}
|-
| Latitude E5500 || 2016-03-01 || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || ||
|-
| Latitude E5520 || 2024-01-15 || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || || Buggy SD card reader 
CPU would sometimes get stuck at minimum frequency, fixed with [[Lenovo ThinkPad T480#CPU stuck at minimum frequency]]
|-
| [[Dell Latitude E5430|Latitude E5430]] || 2016-02-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| Latitude E5540 || 2016-02-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || ||
|-
| Latitude E5570 || 2017-02-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || || BIOS may report incorrect RAM size, OK on UEFI.
|-
| Latitude E5580 || 2018-07-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| Latitude E5401 || 2019-10 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Hibernate: Untested}} || {{Y|Untested: Webcam Thunderbolt}} || Poor thermal design (i7 i7-9850H CPU @ 2.60GHz)
|-
| Latitude E5270 || 2023-10-11 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|Fingerprint reader}}
|-
| Latitude E6220 || 2016-02-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{R|Fingerprint reader}} ||
|-
| Latitude E6230 || 2018-12 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{-}} || {{G|Hibernate: Untested}} || RFID reader requires [https://blog.g3rt.nl/enable-dell-nfc-contactless-reader.html enabling RFID radio] Touchpad (alps a10) shaky ||
|-
| Latitude E6410 || 2018-06-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{Y|Partial*}} || Fingerprint Sensor not functioning, no drivers seem to exist || *Suspension on closing the lid not working right
|-
| Latitude E6410 (BIOS A16)|| 2018-08-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || SD card reader is unreliable. For advanced touchpad functionality see [[Touchpad Synaptics]] ||
|-
| Latitude E6420 || 2011-08-19 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{R|Fingerprint reader NFC (BCM5880)}} ||
|-
| Latitude E6430 || 2018-12 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{G|Hibernate: Untested}} || colspan=2 | Touchpad shaky, use {{Pkg|pcsc-tools}} for smartcards and [https://blog.g3rt.nl/enable-dell-nfc-contactless-reader.html enable] NFC/RFID if needed.
|-
| Latitude E6530 || 2014-10-01 || {{Yes}}* || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || *If Optimus is enabled, output is VGA only, otherwise HDMI works when NVIDIA GPU is disabled in BIOS.
|-
| [[Dell Latitude E7270|Latitude E7270]] || 2017-01-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}}* || || *After UEFI update High suspend usage with power share port active
|-
| [[Dell Latitude 7370|Latitude 7370]] || 2026-05-05 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || ||
|-
| Latitude 7390 ( 2-in-1 ) || 2019-02-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Dell Latitude E7440|Latitude E7440]] || 2019-05-11 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [https://www.dell.com/us/business/p/latitude-e7450-ultrabook/pd?oc=cal147w7pf2 Latitude E7450] || 2016-03-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Y|Partial*}} || Modem: No Synaptics touchpad + stick. || *Hibernate does not work
|-
| Latitude E7470 || 2021-01-25 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Dell Latitude 3500|Latitude 3500]] || 2020-10-28 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Fingerprint reader works with proprietary driver. || See linked article for more details
|-
| Latitude 5580 || 2017-11-06 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}* || || *Needs BIOS update (with [[fwupd]]) to avoid occasional black screen when resuming
|-
| Latitude 5420 || 2023-04-20 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Fingerprint reader works with proprietary {{AUR|libfprint-2-tod1-broadcom}} ||
|-
| Latitude 5520 || 2024-03-24 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Fingerprint reader works with proprietary {{AUR|libfprint-2-tod1-broadcom}} ||
|-
| Latitude 7280 || 2024-05-07 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|No: Fingerprint reader NFC reader}} ||
|-
| Latitude 7420 || 2020-10 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}}* || || *See: https://github.com/intel/thermal_daemon/issues/341
|-
| Latitude 7430 || 2026-01-30 || {{G|Untested: HDMI, DisplayPort}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Yes: Fingerprint reader (with proprietary driver {{AUR|libfprint-2-tod1-broadcom}}) Untested: SIM card reader, Thunderbolt}} || S3 sleep is not supported When resuming from hibernation, system freezes a lot unless swap is disabled after resumption
|-
| Latitude 7480 || 2019-11-07 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{R|No: IR Webcam Fingerprint reader}} ||
|-
| [[Dell Latitude 7490|Latitude 7490]] || 2019-05-11 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| Latitude 5511 || 2020-10 || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || colspan=2 | Fix freezes with {{ic|1=nvme_core.default_ps_max_latency_us=0}}
|-
| [[Dell Latitude 3420|Latitude 3420]] || 2022-02-04 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}}|| {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || ||
|-
| Latitude 7450 || 2025-07-08 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || Webcam does not work. Shows up as multiple inpu6 devices|| Fingerprint reader requires {{AUR|libfprint-2-tod1-broadcom-cv3plus}}.
|-
| Latitude 3310 || 2024-11-05 || {{Yes}} || {{Yes}} || {{G|Yes*}} || {{Yes}} || {{Yes}} || {{Yes}} || {{ic|modprobe r8169}} needs to be run for functionality within the Ethernet port (Ethernet through USB works automatically) ||
|}

=== Precision ===

{{Laptops table header}}
| Precision M4800 || 2024-08-23 || {{Yes}}* || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}** || {{Yes}}*** || colspan=2 | *{{ic|nomodeset}} ''may'' be required to boot. **{{AUR|broadcom-bt-firmware-git}} needed. ***[[power-profiles-daemon]] required
|-
| Precision M6700 || 2017-01-01 || {{Yes}} || {{G|HDMI audio: Untested}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || colspan=2 | Occasional GPU freezes with "GPU has fallen off the bus" errors since kernel 4.14.15-1 and NVIDIA 387.34
|-
| Precision 7710 || 2017-11-01 || {{Yes}} || {{G|HDMI audio: Untested}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || colspan=2 | Suspend works without hard drive password. {{ic|xcalib -a -i}} is very slow. kernel≥5.12.9 or nvidia≥465.24.02-5 causes no display to be seen after X launches. DFP-2 shows as disconnected.
|-
| Precision 7760 || 2024-05-06 || {{Yes}} || {{G|HDMI audio: Untested}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan=2 | S3 Sleep is disabled in ACPI, can be re-enabled by injecting modified ACPI [[DSDT]] via acpi_override. Edit the dsdt.dsl file to remove the if statement for S3 state. However many ACPI errors result from this.
|-
| Precision 7780 || 2024-09-12 || {{Yes}} || {{G|HDMI audio: Untested}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Hibernation: Untested}} || colspan=2 | S3 Sleep is disabled in ACPI; modified ACPI [[DSDT]] untested.
|-
| Precision 5510 || 2020-04-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Hibernation: Untested}} || colspan=2 | Essentially the same device as the [[Dell XPS 15 (9550)]]
|-
| Precision 3530 || 2020-07-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Hibernation: Untested}} || colspan=2 | You need to disable early microcode loading. Upgrade Thunderbolt controller to latest firmware from Windows and optionally disable Thunderbolt security within the BIOS (e.g. for TB16 docking station).
|-
| Precision 3531 || 2017-08-27 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{-}} || {{Y|Untested}} || || Needs {{ic|1=snd-hda-intel.model=laptop}}
|-
| Precision 5520 || 2018-02-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Hibernation: Untested}} || colspan=2 | Essentially the same device as the [[Dell XPS 15 (9560)]]
|-
| Precision 5530 || 2023-02-21 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}* || {{Yes}} || colspan=2 | *Needs occasional driver reloads with {{ic|modprobe btusb}}. Need to change sleep state as per [[Dell XPS 15 (9570)]].
|-
| [[Dell Precision 5570|Precision 5570]] || 2022-05-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| Precision 5760 || 2023-12-24 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|}

=== Pro ===

{{Laptops table header}}
| Pro 14 Plus (PB14250) || 2026-03-11 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|No: Webcam*}} || - Fingerprint needs libfprint-tod (see [[Fprint#Installation|fprint page]])
- *The webcam should work with a custom kernel patch (IPU7)
|}

=== Studio ===

{{Laptops table header}}
| Studio 1749 || 2013-01-04 || {{Yes}} || {{Yes}}* || {{Yes}} || {{Yes}} || {{-}} || {{G|Hibernate: Untested}} || || *Add {{ic|1=options snd-hda-intel index=0 model=dell-m6-dmic}} to {{ic|/etc/modprobe.d/alsa-base.conf}}
|-
| Studio XPS M1640 || 2009-08 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| Studio 1555 || 2013-04-30 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || ||
|}

=== Vostro ===

{{Laptops table header}}
| Vostro 1310 || 2009-06-24 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Unknow}} || {{Yes}} || ||
|-
| Vostro 1320 || 2009-12-04 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan="2" {{Y|Fingerprint reader: Untested, should work like [[Dell XPS M1330#Fingerprint reader]]}}
|-
| Vostro 1000 || 2011-03-28 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || || Add {{ic|1=hpet=disable}} if resume does not work after suspend
|-
| Vostro 5481 || 2019-11-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| Vostro 3360 || 2017-11-21 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || ||
|-
| Vostro 3583 || 2019-12-21 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || Reload {{ic|ath10k_pci}} after resuming from sleep if Wi-Fi stops working
|-
| Vostro 3530 || 2023-01-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || ||
|-
| Vostro 3560 || 2020-02-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| Vostro 5590 || 2021-01-23 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}}|| ||
|-
| Vostro 7500 || 2020-10-16 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{-}} || {{Yes}} || {{-}} || {{Y|Untested}} || {{R|No: Finger print scanner}} ||
|-
| Vostro 7620 || 2022-09-05 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Y|Untested}} || {{Yes}} || {{Y|Untested}} || {{Y|Untested}} || Fingerprint reader requires {{Pkg|libfprint}} ||
|}

=== XPS ===

{{Laptops table header}}
| XPS L322 || 2013-03 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || colspan=2 | ALPS Touchpad recognized only as PS/2 mouse, two-finger scroll, finger tap-to-click, etc... does not work.
|-
| [[Dell XPS M1330|XPS M1330]] || 2021-01 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}* || || *''acpi_cpufreq'' see: [https://bbs.archlinux.org/viewtopic.php?id=44500 forums]
|-
| [[Dell XPS 13 (9333)|XPS 13 (9333)]] || 2016-16-16 || {{Yes}} || {{Yes}} || {{-}} || {{Y|Untested}} || {{Y|Untested}} || {{Y|Untested}} || ||
|-
| [[Dell XPS 13 (9310)|XPS 13 (9310)]] || 2016-16-16 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Dell XPS 13 (9315)|XPS 13 (9315)]] || 2022-11-26 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|Webcam: no}} ||
|-
| [[Dell XPS 13 (9343)|XPS 13 (9343)]] || 2016-16-16 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Dell XPS 13 (9350)|XPS 13 (9350)]] || 2016-11-16 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || || Apply firmware updates
|-
| [[Dell XPS 13 (9360)|XPS 13 (9360)]] || 2016-11-16 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Dell XPS 13 (9370)|XPS 13 (9370)]] || 2018-05-29 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Dell XPS 13 (9380)|XPS 13 (9380)]] || 2020-06-19 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Dell XPS 13 2-in-1 (9365)|XPS 13 2-in-1 (9365)]] || 2017-10-22 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Dell XPS 13 (7390)|XPS 13 (7390)]] || 2019-12-21 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested: Fingerprint sensor}} ||
|-
| [[Dell XPS 13 (9350) 2024|XPS 13 (9350) 2024]] || 2025-06-10 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || IR camera not work || Apply firmware updates
|-
| [[Dell XPS 13 2-in-1 (7390)|XPS 13 2-in-1 (7390)]] || 2019-09-01 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|No: Camera, Fingerprint Sensor}} || System freezes on boot. See device page for fix.
|-
| [[Dell XPS 15|XPS 15]] || 2016-11-17 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Dell XPS 17 (9700)|XPS 17 (9700)]] || 2020-09-18 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Dell XPS 17 (9710)|XPS 17 (9710)]] || 2023-04-23 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || || Touchpad input may sometimes feel slow, potential fix is to update the touchpad driver in Windows. See [[Dell XPS 17 (9710)#Touchpad]]
|-
| XPS 13 2-in-1 (9310) || 2021-03-24 || {{Yes}} || {{Yes}} || {{-}} || {{Yes}} || {{Yes}} || {{Yes}} || colspan="2" | Fingerprint reader {{ic|27c6:532d}} unsupported, other model needs {{AUR|libfprint-tod-git}} or {{AUR|libfprint-2-tod1-xps9300-bin}}
|}

=== G3 ===

{{Laptops table header}}
| G3 15 3590 || 2020-19-10 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || [[CUDA]] is not working with Linux 5.9 || Works well with {{AUR|optimus-manager-git}}, follow their [https://github.com/Askannz/optimus-manager/wiki/A-guide--to-power-management-options#configuration-1--built-in-power-management-inside-the-nvidia-driver page on power management].
|}

=== G5 ===

{{Laptops table header}}
| [[Dell G5 5590-9340|G5 5590-9340]] || 2020-08-20 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{R|No: Fingerprint reader*}} || *drivers might be extracted from Ubuntu image of this laptop
|}

=== G7 ===

{{Laptops table header}}
| G7 7700 || 2022-05-17 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Hibernate: Untested}} || {{R|No: Fingerprint reader}} || No fine backlight control, no RGB control
|}

=== G15 ===

{{Laptops table header}}
| G15 5511 || 2025-10-18 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || {{AUR|awcc-git}} can be used for lights and fans control
|-
| G15 5515 AMD EDITION || 2022-02-12 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || || Touchpad disables randomly on boot, create {{hc|/etc/modprobe.d/i2c-touchpad.conf|softdep i2c_hid pre: pinctrl_amd}}
|-
| G15 5520 NVIDIA || 2022-08-30 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Hibernation: No}} || ||
|-
| [[Dell G15 5525|G15 5525]] || 2023-03-10 || {{Yes}} || {{Yes}}* || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ||
|-
| [[Dell G15 5530|G15 5530]] || 2025-08-09 || {{Yes}} || {{G|[[Sound Open Firmware|Yes*]]}} || {{Yes}} || {{Yes}} || {{Yes}} || {{G|Hibernation: Untested}} || || {{AUR|awcc-git}} can be used for lights and fans control

|}

=== G16 ===

{{Laptops table header}}
| G16 7630 || 2023-01-03 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Y|Untested}} || {{Yes}} || || {{AUR|awcc-git}} works fine for fan control and G-Mode. Screen brightness control works through {{pkg|brightnessctl}}
|}

Flatpak

2026-05-05T16:06:44Z

Erus Iluvatar: /* Installation */ flag last addition for accuracy + minor fix Template:Pkg casing

[[Category:Development]]
[[de:Flatpak]]
[[es:Flatpak]]
[[hu:Flatpak]]
[[ja:Flatpak]]
[[pt:Flatpak]]
[[zh-hans:Flatpak]]
{{Related articles start}}
{{Related|Bubblewrap}}
{{Related|Distrobox}}
{{Related|Snap}}
{{Related articles end}}
From the project [https://github.com/flatpak/flatpak/blob/master/README.md README]:

:[https://flatpak.org Flatpak] is a system for building, distributing and running sandboxed desktop applications on Linux.

From {{man|1|flatpak}}:

:Flatpak is a tool for managing applications and the runtimes they use. In the Flatpak model, applications can be built and distributed independently from the host system they are used on, and they are isolated from the host system ('sandboxed') to some degree, at runtime.
:Flatpak uses [https://netmodule-linux.readthedocs.io/en/latest/gettingstarted/3_ostree.html?highlight=ostree OSTree] to distribute and deploy data. The repositories it uses are OSTree repositories and can be manipulated with the ostree utility. Installed runtimes and applications are OSTree checkouts.

{{Warning|
* Many Flatpak applications available on [https://flathub.org/ Flathub] are not effectively sandboxed by default [https://hanako.codeberg.page]. Do not rely on the provided process isolation without first reviewing the related Flatpak permission manifest for common sandbox escape issues. You can remove problematic permissions (see [[#Permission management]]), but this can break some functionality.
* Running untrusted code is never safe; sandboxing cannot change this.
}}

{{Note|For the contrary opinion, read [https://web.archive.org/web/20230315002817/http://kmkeen.com/maintainers-matter/ Maintainers Matter].}}

== Installation ==

[[Install]] the {{Pkg|flatpak}} package. If you want to build Flatpaks, install {{Pkg|flatpak-builder}} too.

{{Accuracy|Upstream suggests rebooting without explaining ''why'' it is necessary, it is likely that simply logging out then back in would be enough.}}

To complete setup, restart your system, see [https://flatpak.org/setup/Arch link]

=== Desktop integration ===

For Flatpak applications to interact with your desktop (i.e. allow applications to open URLs, share your screen and more), make sure to set up the [[xdg-desktop-portal]]. Depending on the implementation for your desktop, there is a confirmation dialog before the application is able to access some portals.

=== Application management ===

* {{App|COSMIC Store|COSMIC frontend to Flatpak.|https://github.com/pop-os/cosmic-store|{{Pkg|cosmic-store}}}}
* {{App|Discover|KDE frontend to Flatpak which helps you find and install applications, games, and tools. Part of {{Grp|plasma}}.|https://apps.kde.org/discover/|{{Pkg|discover}}}}
* {{App|GNOME Software|GNOME frontend to Flatpak which lets you install and update applications and system extensions. Part of {{Grp|gnome}}.|https://apps.gnome.org/Software/|{{Pkg|gnome-software}}}}

=== Permission management ===

* {{App|Flatpak Permissions Management KCM|KDE Configuration Module that allows changing what permissions have been granted to installed Flatpak applications. Part of {{Grp|plasma}}.|https://invent.kde.org/plasma/flatpak-kcm|{{Pkg|flatpak-kcm}}}}
* {{App|Flatseal|Graphical utility to review and modify permissions from your Flatpak applications.|https://github.com/tchx84/Flatseal|{{Pkg|flatseal}}}}
* {{App|malcontent (Parental Controls)|Implements support for restricting the type of content accessible to non-administrator accounts. Part of {{Grp|gnome}}.|https://gitlab.freedesktop.org/pwithnall/malcontent|{{Pkg|malcontent}}}}

== Managing repositories ==

{{Note|By default, every Flatpak command works system-wide, i.e. packages are installed for all users of the computer; also by default, Flatpak requires the user to supply the root password. If the user is part of the {{ic|wheel}} group and [https://github.com/flatpak/flatpak/issues/3001#issuecomment-2098981907 not connected via SSH], flatpak will regard this user as a system-administrator and not prompt for root password when installing packages system-wide. To install packages and work with repositories for a single user (with no need of superuser rights) you can add the option {{ic|--user}} to each command. If you want, for example, to add a repository only visible to you, you should execute {{ic|flatpak remote-add --user ''name'' ''location''}}.}}

See also [https://docs.flatpak.org/en/latest/using-flatpak.html#basic-commands Basic commands].

=== Add a repository ===

To add a remote Flatpak repository do:

$ flatpak remote-add ''name'' ''location''

where ''name'' is the name for the new remote, and ''location'' is the path or URL for the repository.

The installation of Flatpak will, by default, add the official [https://flathub.org/ Flathub repository] as a system-wide installation. To add the official repository with a per-user configuration:

$ flatpak remote-add --if-not-exists --user flathub <nowiki>https://dl.flathub.org/repo/flathub.flatpakrepo</nowiki>

=== Delete a repository ===

To delete a remote Flatpak repository do:

$ flatpak remote-delete ''name''

where ''name'' is the name of the remote repository to be deleted.

=== List repositories ===

To list all the added repositories do:

$ flatpak remotes

=== Set repository priorities ===

To change the default priority of ''Flathub'' repo to ''3'':

$ flatpak remote-modify --prio=3 flathub

=== Change the repository subset ===

To select ''verified'' subset of Flathub repo:

$ flatpak remote-modify --subset=verified flathub

Refer to the documentation for the desired Flatpak repository to find the available subsets and their descriptions.

== Managing runtimes and applications ==

{{Note|If remotes have been added with a [[#Add a repository|per-user]] configuration, the {{ic|--user}} option can be appended to the following flatpak commands. For example, to install a package visible only to you, run {{ic| flatpak install --user ''package-name''}}.}}

=== Search for a remote runtime or application ===

You can proceed to search for a package with {{ic|flatpak search ''packagename''}}, e.g. to look for the package {{ic|libreoffice}} with the {{ic|flathub}} remote configured:

{{hc|$ flatpak search libreoffice|
Application ID Version Branch Remotes Description
org.libreoffice.LibreOffice stable flathub The LibreOffice productivity suite
}}

=== List all available runtimes and applications ===

To list all available runtimes and applications in a remote repository named ''remote'' do:

$ flatpak remote-ls ''remote''

=== Install a runtime or application ===

To install a runtime or application do:

$ flatpak install ''remote'' ''name''

where ''remote'' is the name of the remote repository, and ''name'' is the name of the application or runtime to install.

{{Tip|You can use partial identifiers {{ic|flatpak install ''partial-name''}} (for example {{ic|flatpak install libreoffice}}).}}

To install an application from a ''.flatpak'' file do:

$ flatpak install ''name''.flatpak

=== List installed runtimes and applications ===

To list installed runtimes and applications do:

$ flatpak list

=== Run applications ===

Binaries are available in {{ic|/var/lib/flatpak/exports/bin}}, which is automatically added to $PATH by {{ic|/etc/profile.d/flatpak-bindir.sh}}. You may have to re-login to apply the change.

Flatpak applications can also be run with the command line:

$ flatpak run ''name''

=== Update a runtime or application ===

List runtimes and applications that have updates available:

$ flatpak remote-ls --updates

To update a runtime or application named ''name'' do:

$ flatpak update ''name''

To update all applications and runtimes:

$ flatpak update

==== Automatic updates via systemd ====

{{Warning|It is generally not a good idea to run unattended updates via systemd, as the applications can get new permissions without the user aware of the changes. See [https://ejona.ersoft.org/archive/2024/03/02/flatpak-perms-upgrade/ this blogpost] for examples.}}

To update your system runtimes and applications automatically, create the following files:

{{hc|/etc/systemd/system/flatpak-update.service|2=
[Unit]
Description=Update Flatpak
After=network-online.target
Wants=network-online.target

[Service]
Type=oneshot
ExecStart=/usr/bin/flatpak update --noninteractive --assumeyes

[Install]
WantedBy=multi-user.target
}}

{{hc|/etc/systemd/system/flatpak-update.timer|2=
[Unit]
Description=Update Flatpak

[Timer]
OnBootSec=2m
OnActiveSec=2m
OnUnitInactiveSec=24h
OnUnitActiveSec=24h
AccuracySec=1h
RandomizedDelaySec=10m

[Install]
WantedBy=timers.target
}}

Afterwards, do a [[daemon-reload]] and [[enable/start]] the {{ic|flatpak-update.timer}} [[Systemd#Using units|unit]].

{{Note|
* This guide is for system Flatpak installations which are the default in Flatpak. For user Flatpak installations:
** Create the above files in the {{ic|/etc/systemd/user/}} directory.
** Add the {{ic|--user}} flag in {{ic|ExecStart}} line in {{ic|flatpak-update.service}}.
** Run the {{ic|systemctl}} commands with the {{ic|--user}} flag.
}}

=== Uninstall a runtime or application ===

To uninstall a runtime or application named ''name'' do:

$ flatpak uninstall ''name''

To delete app data from {{ic|~/.var/app}} and from the permission store while uninstalling, use:

$ flatpak uninstall --delete-data ''name''

{{Tip|You can uninstall unused Flatpak "refs" (aka orphans with no application/runtime) with {{ic|flatpak uninstall --unused}}.}}

=== Downgrade a runtime or application ===

To downgrade a runtime or application, first look for the associated commit ID:

$ flatpak remote-info --log ''remote'' ''name''

Where ''remote'' is the repository (such as {{ic|flathub}}), and ''name'' is the name of the application or runtime. Then, deploy the commit:

$ flatpak update --commit=''commit'' ''name''

where ''commit'' is the commit for the desired version, and ''name'' is as before.

This procedure can also be used to selectively upgrade a package to a desired version that is not the latest version.

To exclude {{ic|flatpak update}} from updating this package, see [[#Prevent updates to a runtime or application]].

=== Prevent updates to a runtime or application ===

To prevent automatic and manual updates to a runtime or application, use the {{ic|flatpak mask}} command:

$ flatpak mask ''name''

This also prevents selective upgrades and downgrades.

To reverse the mask and re-enable updates, use {{ic|flatpak mask --remove}}:

$ flatpak mask --remove ''name''

=== Add Flatpak .desktop files to your menu ===

Flatpak expects window managers to respect the [[XDG Base Directory#System directories|XDG_DATA_DIRS]] environment [[variable]] to discover applications. This variable is set by the script {{ic|/etc/profile.d/flatpak.sh}}. Updating the environment may require restarting the session. If the launcher does not support {{ic|XDG_DATA_DIRS}}, you can edit the list of directories scanned and add these to it:

~/.local/share/flatpak/exports/share/applications
/var/lib/flatpak/exports/share/applications

This is known to be necessary in [[Awesome]].

=== View sandbox permissions of application ===

Flatpak applications come with predefined sandbox rules which define the resources and file system paths the application is allowed to access.
To view the specific application permissions do:

$ flatpak info --show-permissions ''name''

The reference of the sandbox permission names can be found on [https://docs.flatpak.org/en/latest/sandbox-permissions.html official Flatpak documentation].

=== Override sandbox permissions of applications ===

If you find the predefined permissions of the application too lax or too restrictive you can change to anything you want using {{ic|flatpak override}} command.
For example:

$ flatpak override --nofilesystem=home ''name''

This will prevent the application access to your home folder.

Every type of permission, such as device, filesystem or socket, has a command line option that allows that particular permission and a separate option that denies permission. For example, in case of device access {{ic|1=--device=''device_name''}} allows access, {{ic|1=--nodevice=''device_name''}} denies the permission to access device.

For all permission types commands consult the manual page: {{man|1|flatpak-override}}

Permission overrides can be reset to defaults with command:

$ flatpak override --reset ''name''

''Flatseal'' is a GUI permissions manager which offers simple point-and-click permissions operations. In KDE Plasma, ''Flatpak Permissions Management KCM'' provides a similar GUI for the system settings application: ''System Settings > Applications > Flatpak Permission Settings''.

== Creating a custom base runtime ==

{{Expansion|This can certainly be improved. It also has problems with D-Bus for GNOME apps.}}

{{Warning|If you want to release your software to the public as a Flatpak, an Arch-based runtime is unsuitable: packages should use common runtime when possible, then users will not need to download and install different runtimes again and again. In this case, you will want to follow [https://docs.flatpak.org official documentation] to integrate your software into the proper Flatpak ecosystem using the [https://flatpak.org/runtimes.html common runtimes].}}

{{Note|
* You may want to use an untrusted, unprivileged user account for bundling untrusted software because the software is not sandboxed during app and runtime creation.
* When distributing bundles to others, you may be legally obliged to provide the source code of some of the bundled software upon request. You may want to use [[ABS]] to build these packages from source.
}}

You can create a custom Arch-based base runtime and base SDK for Flatpak using pacman. You can then use it for building and packaging applications. This is an alternative for personal use to the default {{ic|org.freedesktop.BasePlatform}} and {{ic|org.freedesktop.BaseSdk}} runtimes.

In addition to {{Pkg|flatpak}}, you need to have installed {{Pkg|fakeroot}} and for pacman hooks support also {{Pkg|fakechroot}}.

First, start by creating a directory for building the runtime and possibly applications.

$ mkdir ''myflatpakbuilddir''
$ cd ''myflatpakbuilddir''

You can then prepare a directory for building the runtime base platform. The files subdirectory will contain what will later be the {{ic|/usr}} directory in the sandbox. Therefore you will need to create symbolic links so the default {{ic|/usr/share}} etc. from Arch can still be accessed at the usual path.

$ mkdir -p ''myruntime''/files/var/lib/pacman
$ touch ''myruntime''/files/.ref
$ ln -s /usr/usr/share ''myruntime''/files/share
$ ln -s /usr/usr/include ''myruntime''/files/include
$ ln -s /usr/usr/local ''myruntime''/files/local

Make your host OS fonts available to the Arch runtime:

$ mkdir -p ''myruntime''/files/usr/share/fonts
$ ln -s /run/host/fonts ''myruntime''/files/usr/share/fonts/flatpakhostfonts

You need and may want to adapt your {{ic|pacman.conf}} before installing packages to the runtime. Copy {{ic|/etc/pacman.conf}} to your build directory and then make the following changes:

* Remove the {{ic|CheckSpace}} option so pacman will not complain about errors finding the root filesystem for checking disk space.
* Remove any undesired custom repositories and {{ic|IgnorePkg}}, {{ic|IgnoreGroup}}, {{ic|NoUpgrade}} and {{ic|NoExtract}} settings that are needed only for the host system.

Now install the packages for the runtime.

$ fakechroot fakeroot pacman -Syu --root ''myruntime''/files --dbpath ''myruntime''/files/var/lib/pacman --config pacman.conf base
$ mv pacman.conf ''myruntime''/files/etc/pacman.conf

Set up the [[Locale|locales]] to be used by editing {{ic|''myruntime''/files/etc/locale.gen}}. Then regenerate the runtime’s locales.

$ fakechroot chroot ''myruntime''/files locale-gen

The base SDK can be created from the base runtime with added applications needed for building packages and running pacman.

$ cp -r ''myruntime'' mysdk
$ fakechroot fakeroot pacman -S --root mysdk/files --dbpath mysdk/files/var/lib/pacman --config mysdk/files/etc/pacman.conf base-devel fakeroot fakechroot --needed

Insert metadata about runtime and SDK.

{{hc|''myruntime''/metadata|2=
[Runtime]
name=org.mydomain.BasePlatform
runtime=org.mydomain.BasePlatform/x86_64/2016-06-26
sdk=org.mydomain.BaseSdk/x86_64/2016-06-26
}}

{{hc|mysdk/metadata|2=
[Runtime]
name=org.mydomain.BaseSdk
runtime=org.mydomain.BasePlatform/x86_64/2016-06-26
sdk=org.mydomain.BaseSdk/x86_64/2016-06-26
}}

Add base runtime and SDK to a local repository in the current directory. You may want to give them appropriate commit messages such as “My Arch base runtime” and “My Arch base SDK”.

$ ostree init --mode archive-z2 --repo=.
$ EDITOR="nano -w" ostree commit -b runtime/org.mydomain.BasePlatform/x86_64/2016-06-26 --tree=dir=''myruntime''
$ EDITOR="nano -w" ostree commit -b runtime/org.mydomain.BaseSdk/x86_64/2016-06-26 --tree=dir=mysdk
$ ostree summary -u

Install the runtime and SDK.

$ flatpak remote-add --user --no-gpg-verify myarchos file://$(pwd)
$ flatpak install --user myarchos org.mydomain.BasePlatform 2016-06-26
$ flatpak install --user myarchos org.mydomain.BaseSdk 2016-06-26

=== Creating apps with pacman ===

As an alternative to building applications [https://flatpak.org/developer.html the usual way], we can use pacman to create a containerized version of the regular Arch packages. Note that {{ic|/usr}} is read-only when creating apps, so we can not use Arch’s packages when building an app. To create a real app with pacman, we can either

* use pacman to create a runtime containing all dependencies
* and compile the app ourselves [https://flatpak.org/developer.html as usual] or perhaps using pacman with a custom [[PKGBUILD]] tailored to Flatpak which uses {{ic|1=--prefix=/app}} for the {{ic|configure}} script,

or we can
* use pacman to create a runtime containing the app installed with pacman
* and create a dummy app to launch it.

For doing the latter, first create a runtime using pacman such as this one for {{Pkg|gedit}}. The runtime is first initialized and prepared for use with pacman.

$ flatpak build-init -w geditruntime org.mydomain.geditruntime org.mydomain.BaseSdk org.mydomain.BasePlatform 2016-06-26
$ flatpak build geditruntime sed -i "s/^#Server/Server/g" /etc/pacman.d/mirrorlist
$ flatpak build geditruntime ln -s /usr/var/lib /var/lib
$ flatpak build geditruntime fakeroot pacman-key --init
$ flatpak build geditruntime fakeroot pacman-key --populate

Then the package is installed. The host’s network connection must be made available to pacman.

$ flatpak build --share=network geditruntime fakechroot fakeroot pacman --root /usr -S gedit

You can test the installation before finishing the runtime (without proper sandboxing).

$ flatpak build --socket=x11 geditruntime gedit

Now finish building the runtime and export it to a new local repository. pacman’s GnuPG keys have permissions that may interfere and need to be removed first.

$ flatpak build geditruntime rm -r /etc/pacman.d/gnupg
$ flatpak build-finish geditruntime
$ sed -i "s/\[Application\]/\[Runtime\]/;s/runtime=org.mydomain.BasePlatform/runtime=org.mydomain.geditruntime/" geditruntime/metadata
$ flatpak build-export -r geditrepo geditruntime

Then create a dummy app.

$ flatpak build-init geditapp org.gnome.gedit org.mydomain.BaseSdk org.mydomain.geditruntime

Now finish the dummy app. You can fine-tune the app’s access permissions when sandboxed by giving additional options when finishing the build. For possible options see the [[#See also|Flatpak documentation]] and the [https://gitlab.gnome.org/GNOME/gnome-apps-nightly/tree/master GNOME manifest files]. Alternatively, adapt {{ic|geditapp/metadata}} to your needs after finishing the build but before exporting. When the metadata file is complete, export the app to the repository.

$ flatpak build-finish geditapp --socket=x11 ''[possibly other options]'' --command=gedit
$ flatpak build-export geditrepo geditapp

Install it along with the runtime.

$ flatpak --user remote-add --no-gpg-verify geditrepo geditrepo
$ flatpak install --user geditrepo org.mydomain.geditruntime
$ flatpak install --user geditrepo org.gnome.gedit
$ flatpak run org.gnome.gedit

== Troubleshooting ==

=== Flatpak does not run on the linux-hardened kernel ===

The {{Pkg|linux-hardened}} kernel sets {{ic|kernel.unprivileged_userns_clone}} to {{ic|0}}, so only privileged users can create new user namespaces.

One method to fix this is to [[install]] {{pkg|bubblewrap-suid}}. This package provides a version of {{man|1|bwrap}} with the {{ic|setuid}} bit enabled, allowing bubblewrap elevate itself and create new namespaces.

Alternatively, set {{ic|kernel.unprivileged_userns_clone}} to {{ic|1}} using {{man|8|sysctl}}, allowing unprivileged users to create new user namespaces:

# sysctl kernel.unprivileged_userns_clone=1

{{Warning|Using this kernel parameter value has negative security implications. See [[Security#Sandboxing applications]] for further information.}}

To make this change persist across reboots, add a configuration file to {{man|5|sysctl.d}}:

{{hc|/etc/sysctl.d/flatpak.conf|2=
kernel.unprivileged_userns_clone=1
}}

For more information, see the note in [[Bubblewrap#Installation]].

=== Failed to connect to Wayland display ===

If the application doesn't properly open and you get messages such as {{ic|Failed to connect to Wayland display: No such file or directory}} on {{ic|flatpak run}}: This may be because some other setting such as {{ic|ELECTRON_OZONE_PLATFORM_HINT{{=}}"auto"}} makes the Flatpak application choose Wayland while access to Wayland isn't whitelisted for this application.

This can be fixed by whitelisting access to {{ic|socket{{=}}wayland}} with e.g. Flatseal.

=== xdg-desktop-portal is failing to start ===

If you are starting X with [[Xinit#xinitrc|manually-configured run commands]], ensure you are including all essential components of the reference `xinitrc`. One of which sources a script which runs an update of the environment used for D-Bus session services.

systemctl --user import-environment DISPLAY XAUTHORITY
if command -v dbus-update-activation-environment >/dev/null 2>&1; then
dbus-update-activation-environment DISPLAY XAUTHORITY
fi

=== Flatpak applications not picking up the default system theme ===

There is no ideal way to apply system themes in Flatpak apps as mentioned in the Flatpak documentation [https://docs.flatpak.org/en/latest/desktop-integration.html?highlight=theme#applying-themes] [https://docs.flatpak.org/en/latest/desktop-integration.html?highlight=theme#theming]. The easiest solution is using themes that are available in Flathub. However [https://web.archive.org/web/20230106121332/https://itsfoss.com/flatpak-app-apply-theme/ there is a workaround] which can be used to apply themes to your Flatpak apps. {{AUR|stylepak-git}} automates this workaround.

=== "File not found" error when Open local HTML pages in Firefox ===

By default, the Flatpak version of Firefox will display a "File not found" error page when opening a local HTML. This is because [[#Override sandbox permissions of applications|permission must be granted]] to the app for accessing the folder containing the file.

However, note that when granting permission to access the entire Home folder, Firefox will then check for an existing profile in {{ic|~/.mozilla}} and load it instead of those previously in use from the sandboxed folder {{ic|~/.var/app/org.mozilla.firefox/cache/mozilla/}}. If your previous session's tabs and browsing history is missing after changing a permission (e.g. with Flatseal), either modify the permission to exclude access to {{ic|~/.mozilla}}, or consider copying the profile from {{ic|~/.var/app/org.mozilla.firefox/cache/mozilla/}} to {{ic|~/.mozilla}}.

=== Links fail to open on wlroots-based compositors ===

Flatpak applications that attempt to open URIs make use of the {{ic|org.freedesktop.portal.OpenURI.OpenURI}} [[D-Bus]] interface exposed by [[xdg-desktop-portal]]. The [https://github.com/emersion/xdg-desktop-portal-wlr/issues/42 xdg-desktop-portal-wlr backend] does not support this call and therefore you will need an additional backend to fill the gap, for example {{Pkg|xdg-desktop-portal-gtk}}.

=== Applications do not use the correct cursor theme ===

There is no single standard to set the cursor properly. Some programs only need read access to the cursors directory, others also rely on other mechanisms. For [[GTK]] applications, ensure that {{Pkg|xdg-desktop-portal-gtk}} is installed.

Otherwise, the following overrides should work for most common desktop applications.

$ flatpak -u override --filesystem=/usr/share/icons/:ro
$ flatpak -u override --filesystem=/home/$USER/.icons/:ro
$ flatpak -u override --filesystem=xdg-config/gtk-3.0:ro
$ flatpak -u override --env=XCURSOR_PATH=~/.icons

In some cases you may also need to override the environment variables {{ic|XCURSOR_THEME}} and {{ic|XCURSOR_SIZE}}:

$ flatpak -u override --env=XCURSOR_THEME=Adwaita
$ flatpak -u override --env=XCURSOR_SIZE=24

See [https://github.com/flatpak/flatpak/issues/709 this discussion] for additional details.

Apparently it is not possible anymore to enable access to applications to directories under {{ic|/usr/}}. The following hints at this when launching a program:
{{hc|$ flatpak run com.spotify.Client|
F: Not sharing "/usr/share/icons" with sandbox: Path "/usr" is reserved by Flatpak
}}
One possible workaround would be to manually copy your icon theme from {{ic|/usr/share/icons}} to {{ic|/home/$USER/.icons/}}.

=== Flatpak Qt applications do not use Gnome Adwaita dark theme ===

If you switched your theme to Adwaita-dark and Flatpak Qt applications still use the light version, install the required KStyle:

# flatpak install flathub org.kde.KStyle.Adwaita

=== Permission denied error when running Flatpak applications ===

Flatpak applications will not run if the mount point that contains the folder in which the application is stored, typically {{ic|/var/lib/flatpak/}} for system wide installations, and {{ic|~/.local/share/flatpak/}} for user-specific installations, is mounted with the {{ic|noexec}} option.

With {{ic|noexec}} set you will get errors such as this:

$ bwrap: execvp ldconfig: Permission denied
$ error: ldconfig failed, exit status 256

== See also ==

* [https://github.com/flatpak/flatpak/wiki Official wiki on GitHub]
* [[Wikipedia:Flatpak]]
* [https://wiki.gnome.org/Projects/SandboxedApps Gnome SandboxedApps]
* [https://community.kde.org/Guidelines_and_HOWTOs/Flatpak KDE Testing Runtime and Applications]

GameMode

2026-05-04T07:55:55Z

Erus Iluvatar: /* Configuration */ Replace HTML tag with newlines

[[Category:Gaming]]
[[ja:Gamemode]]
[[pl:GameMode]]
[[zh-hans:GameMode]]
{{Related articles start}}
{{Related|MangoHud}}
{{Related articles end}}

[https://github.com/FeralInteractive/gamemode GameMode] is a daemon and library combo for Linux that allows games to request a set of optimisations be temporarily applied to the host OS and/or a game process.

== Installation ==

Enable the [[multilib]] repository and [[install]] {{Pkg|gamemode}} and {{Pkg|lib32-gamemode}} since many old games are 32-bit-only.

Add yourself to the {{ic|gamemode}} [[user group]]. Without it, the GameMode user daemon will not have rights to change CPU governor or the niceness of processes.

== Configuration ==

GameMode is configured via the following files, which are read and then merged in the following order:

# {{ic|/etc/gamemode.ini}} for system-wide configuration;
# {{ic|$XDG_CONFIG_HOME/gamemode.ini}} for user-local configuration;
# {{ic|./gamemode.ini}} for directory-local configuration.

{{Tip|FeralInteractive's GitHub repository contains an [https://github.com/FeralInteractive/gamemode/blob/master/example/gamemode.ini example configuration file].}}

{{Note|
{{ic|/usr/share/gamemode/gamemode.ini}} should not be created by users, as it is reserved for manual configuration by package maintainers. See {{man|7|file-hierarchy}} for more details.

The Arch Linux official packages do not include such file[https://github.com/FeralInteractive/gamemode/blob/c54d6d4243b0dd0afcb49f2c9836d432da171a2b/meson.build#L197-L200][https://gitlab.archlinux.org/archlinux/packaging/packages/gamemode/-/blob/4d3e60ac2bfd06fa58373c4e061f689ff5e981f6/PKGBUILD#L42][https://gitlab.archlinux.org/archlinux/packaging/packages/lib32-gamemode/-/blob/2ac9dc463fc3ebca36fb1cae39d7828e65137394/PKGBUILD#L41]; the defaults are sourced from the software's code defaults[https://github.com/FeralInteractive/gamemode/blob/c54d6d4243b0dd0afcb49f2c9836d432da171a2b/daemon/gamemode-config.c#L373-L385], which have the same values as the [https://github.com/FeralInteractive/gamemode/blob/master/example/gamemode.ini example configuration file].
}}

=== Renicing ===

GameMode can optionally adjust the priority of game processes (see {{man|1|renice}}) beyond the regular user lower limit of {{ic|0}}.

This is controlled by the following configuration option:

{{bc|1=
[general]
renice=0
}}

Unlike renicing a process with the {{ic|renice}} command, GameMode uses a positive value then negates it before applying it to the process. For example, a value of {{ic|10}} will renice the game process to {{ic|-10}}.

=== Overclocking ===

GameMode can optionally overclock your GPU when it is running, but requires special configuration on part of the user.

Independently of the used GPU, the {{ic|apply_gpu_optimizations}} and {{ic|gpu_device}} configuration options must be set appropriately.

{{Note|Settings in {{ic|[gpu]}} will not be applied if they are specified in {{ic|$XDG_CONFIG_HOME/gamemode.ini}} or {{ic|./gamemode.ini}}, as those are considered "unsafe" config files. These settings will have to be specified in {{ic|/etc/gamemode.ini}} to take effect. See the [https://github.com/FeralInteractive/gamemode#Configuration Configuration section] on FeralInteractive's GitHub page.}}

==== AMD ====

To alter the performance level of AMD GPUs, [[AMDGPU#Overclocking|overclocking]] must be manually enabled, and the {{ic|amd_performance_level}} configuration option must be set.

==== NVIDIA ====

To alter the performance level of NVIDIA GPUs, [[NVIDIA/Tips and tricks#Enabling overclocking in nvidia-settings|overclocking]] must be manually enabled, and the {{ic|nv_powermizer_mode}}, {{ic|nv_core_clock_mhz_offset}}, and the {{ic|nv_mem_clock_mhz_offset}} configuration options must be set.

== Usage ==

=== Test configuration ===

Verify if the settings in the configuration file are working:

$ gamemoded -t

=== Run a single game ===

To run a game with GameMode start it like this:

$ gamemoderun ./game

==== Use with MangoHud ====

See [[MangoHud#Use with GameMode]]

=== Verify that GameMode is running ===

When you have started your game you can verify that GameMode is running with the command:

$ gamemoded -s

{{Note|The {{ic|gamemoded.service}} user unit is started on demand by [[dbus]] [https://github.com/FeralInteractive/gamemode/pull/62].}}

=== Run a single Steam game ===

To make [[Steam]] start a game with GameMode, set its [[Steam#Launch options|launch command]]:

gamemoderun %command% [additional launch options]

=== Run Steam with GameMode ===

To avoid having to change launch options for all Steam games, you may launch [[Steam]] directly with GameMode:

$ gamemoderun steam

The downside of this approach is that GameMode will be running for as long as the Steam process is open, instead of only when a game is opened.

== Troubleshooting ==

=== Renicing fails when set to less than -10 ===

By default, GameMode provides [[PAM]] limits that allow changing the scheduling priority up to a maximum of {{ic|-10}}. If the {{ic|renice}} setting in the configuration file is set to an unsupported value, renicing of the process will fail entirely.

You can adjust the requested value or adjust the maximum scheduling priority GameMode can set by editing {{ic|/etc/security/limits.d/10-gamemode.conf}}. The example below configures {{ic|-19}} as the maximum scheduling priority GameMode can set:

{{hc|/etc/security/limits.d/10-gamemode.conf|2=
@gamemode - nice -19
}}

List of applications/Internet

2026-05-04T07:54:05Z

Erus Iluvatar: Undo revision 872963 by TheSleuth (talk) - Removed italics, it was applied to links too which goes against Help:Style/Formatting and punctuation#Links and it feels unnecessary and out of place with the other pages

[[Category:Internet applications]]
[[Category:Lists of software]]
[[es:List of applications (Español)/Internet]]
[[hu:List of applications (Magyar)/Internet]]
[[ja:アプリケーション一覧/インターネット]]
[[pl:List of applications (Polski)/Internet]]
[[zh-hans:List of applications/Internet]]
{{List of applications navigation}}

== Network connection ==

=== Network managers ===

See [[Network configuration#Network managers]].

=== VPN clients ===

* {{App|GlobalProtect-openconnect|A GlobalProtect VPN client (GUI) for Linux, based on OpenConnect and built with Qt5, supports SAML auth mode.|https://github.com/yuezk/GlobalProtect-openconnect/|{{Pkg|globalprotect-openconnect}}}}
* {{App|Libreswan|A free software implementation of the most widely supported and standardized VPN protocol based on ("IPsec") and the Internet Key Exchange ("IKE").|https://libreswan.org/|{{AUR|libreswan}}}}
* {{App|[[Mullvad]]|A GUI client for the Mullvad VPN service |https://mullvad.net/|{{Pkg|mullvad-vpn}}}}
* {{App|[[Nebula]]|A mesh VPN network|https://nebula.defined.net/docs/|{{Pkg|nebula}}}}
* {{App|[[NetworkManager]]|Supports a variety of protocols (e.g. MS, Cisco, Fortinet) via a plugin system.|https://wiki.gnome.org/Projects/NetworkManager/VPN|{{Pkg|networkmanager}}}}
* {{App|[[OpenConnect]]|Supports Cisco and Juniper VPNs.|https://www.infradead.org/openconnect/|{{Pkg|openconnect}}}}
* {{App|[[ProtonVPN]]|VPN provider that uses the OpenVPN and WireGuard protocol.|https://protonvpn.com/|{{Pkg|proton-vpn-gtk-app}}}}
* {{App|[[Openswan]]|IPsec-based VPN Solution.|https://www.openswan.org/|{{AUR|openswan}}}}
* {{App|[[OpenVPN]]|To connect to OpenVPN VPNs.|https://openvpn.net/|{{Pkg|openvpn}}}}
* {{App|[[PPTP Client]]|To connect to PPTP VPNs, like Microsoft VPNs (MPPE). (insecure)|https://pptpclient.sourceforge.net/|{{Pkg|pptpclient}}}}
* {{App|RiseupVPN|A GUI client for the Riseup VPN service from riseup.net.|https://riseup.net/en/vpn/ | {{AUR|riseup-vpn}} or {{AUR|riseup-vpn-configurator}} }}
* {{App|[[Rosenpass]]|Hybrid security against quantum computers for WireGuard by adding a post-quantum-secure key exchange|https://rosenpass.eu/|{{Pkg|rosenpass}}}}
* {{App|[[strongSwan]]|IPsec-based VPN Solution.|https://www.strongswan.org/|{{Pkg|strongswan}}}}
* {{App|[[tinc]]|tinc is a free VPN daemon.|https://www.tinc-vpn.org/|{{Pkg|tinc}}}}
* {{App|vopono|OpenVPN and WireGuard wrapper to launch applications with VPN tunnels in network namespaces.|https://github.com/jamesmcm/vopono|{{AUR|vopono}}}}
* {{App|vpnc|To connect to Cisco 3000 VPN Concentrators.|https://www.unix-ag.uni-kl.de/~massar/vpnc/|{{Pkg|vpnc}}}}
* {{App|[[WireGuard]]|Next generation secure network tunnel.|https://www.wireguard.com/|{{Pkg|wireguard-tools}}}}

=== Proxy servers ===

* {{App|Brook|Proxy focusing on strong encryption and being undetectable.|https://txthinking.github.io/brook/|{{Pkg|brook}}}}
* {{App|Dante|SOCKS server and SOCKS client, implementing [[RFC:1928]] and related standards.|https://www.inet.no/dante/|{{Pkg|dante}}}}
* {{App|Geph|A modular Internet censorship circumvention system designed specifically to deal with national filtering.|https://geph.io/en/|{{AUR|geph4-client}}}}
* {{App|hiddify|Multiplatform chain proxy client based on {{AUR|sing-box}}.|https://github.com/hiddify/hiddify-next|{{AUR|hiddify}}}}
* {{App|[[NaïveProxy]]|A Proxy using Chrome's network stack to camouflage traffic with strong censorship resistence and low detectablility.|https://github.com/klzgrad/naiveproxy|{{AUR|naiveproxy}}}}
* {{App|[[Privoxy]]|Non-caching web proxy with advanced filtering capabilities for enhancing privacy, modifying web page data and HTTP headers, controlling access, and removing ads and other obnoxious Internet junk.|https://www.privoxy.org/|{{Pkg|privoxy}}}}
* {{App|[[Shadowsocks]]|Secure socks5 proxy, designed to protect your Internet traffic.|https://shadowsocks.org/|{{Pkg|shadowsocks-rust}}}}
* {{App|[[Squid]]|Caching proxy for the Web supporting HTTP, HTTPS, FTP, and more.|https://www.squid-cache.org/|{{Pkg|squid}}}}
* {{App|[[Stunnel]]|A server and client to add and remove TLS encryption to TCP data flow.|https://www.stunnel.org/|{{Pkg|stunnel}}}}
* {{App|Throne|Cross-platform GUI proxy utility (Empowered by {{AUR|sing-box}}).|https://github.com/throneproj/Throne|{{AUR|throne}}}}
* {{App|Tinyproxy|Lightweight HTTP/HTTPS proxy daemon.|https://tinyproxy.github.io/|{{Pkg|tinyproxy}}}}
* {{App|[[Trojan]]|An unidentifiable mechanism that helps you bypass GFW.|https://trojan-gfw.github.io/trojan/|{{Pkg|trojan}}}}
* {{App|[[V2Ray]]|V2Ray is the core of Project V, which is a set of tools to help you build your own privacy network over the internet.|https://www.v2fly.org/en_US/|{{Pkg|v2ray}}}}
* {{App|V2RayN|A GUI client for Windows, Linux and macOS, support {{AUR|xray}} and {{AUR|sing-box}} cores and others.|https://github.com/2dust/v2rayN|{{AUR|v2rayN}}}}
* {{App|[[Varnish]]|High-performance HTTP accelerator.|https://varnish-cache.org/|{{Pkg|varnish}}}}
* {{App|Wireproxy|[[WireGuard]] client that exposes itself as a SOCKS5 proxy.|https://github.com/pufferffish/wireproxy|{{Pkg|wireproxy}}}}
* {{App|XX-Net|Easy to use web proxy tool.|https://github.com/XX-net/XX-Net/|{{AUR|xx-net}}}}
* {{App|Ziproxy|Forwarding (non-caching) compressing HTTP proxy server.|https://ziproxy.sourceforge.net/|{{Pkg|ziproxy}}}}

=== Anonymizing networks ===

* {{App|Arti|Rust implementation of the Tor anonymizing overlay network.|https://gitlab.torproject.org/tpo/core/arti|{{Pkg|arti}}}}
* {{App|[[GNUnet]]|Framework for secure peer-to-peer networking.|https://gnunet.org/|CLI: {{AUR|gnunet}}, GUI: {{AUR|gnunet-gtk}}}}
* {{App|Hyphanet|An encrypted network without censorship, previously named Freenet.|https://www.hyphanet.org/|{{AUR|hyphanet}}}}
* {{App|[[I2P]]|Distributed anonymous network.|https://geti2p.net/|{{Pkg|i2pd}}, {{AUR|i2p}}}}
* {{App|Lantern|Peer-to-peer internet censorship circumvention software.|https://getlantern.org/|{{AUR|lantern-bin}}}}
* {{App|Lokinet|Anonymous, decentralized and IP based overlay network for the internet.|https://lokinet.org/|{{AUR|lokinet}}}}
* {{App|[[Tor]]|Anonymizing overlay network.|https://www.torproject.org/|{{Pkg|tor}}}}

=== Network tunnels ===

* {{App|6tunnel|Tunnels IPv6 connections for IPv4-only applications.|https://github.com/wojtekka/6tunnel/|{{Pkg|6tunnel}}}}
* {{App|iodine|Tunnel IPv4 data through a DNS server.|https://code.kryo.se/iodine/|{{Pkg|iodine}}}}
* {{App|isatapd|Creates and maintains an ISATAP tunnel ([[RFC:5214]]).|http://www.saschahlusiak.de/linux/isatap.htm|{{Pkg|isatapd}}}}
* {{App|Ping Tunnel|A tool for reliably tunneling TCP connections over ICMP echo request and reply packets.|https://www.cs.uit.no/~daniels/PingTunnel/|{{Pkg|ptunnel}}}}
* {{App|Tuntox|Tunnel TCP connections over the Tox protocol.|https://github.com/gjedeer/tuntox/|{{Pkg|tuntox}}}}

=== Deep packet inspection circumvention ===

Tools to avoid censorship, bandwidth throttle without anonymization. See [[Wikipedia:Deep packet inspection]], [[Wikipedia:Internet censorship circumvention]] for an introduction to the topic.

* {{App|Bypass DPI|A simple software using SOCKS5, written in C and targeted at Russian censorship.|https://github.com/hufrea/byedpi|{{AUR|byedpi}}}}
* {{App|Cloak|A pluggable transport that works alongside traditional proxy tools like [[OpenVPN]], written in Go.|https://github.com/cbeuw/Cloak|{{AUR|cloak-obfuscation}}}}
* {{App|DPI Tunnel|An HTTP/transparent proxy, written in C++ and targeted at Russian censorship.|https://github.com/txtsd/DPITunnel|{{AUR|dpitunnel}}}}
* {{App|Green Tunnel|An anti-censorship utility using SOCKS5, written in nodejs and targeted at Iranian censorship.|https://github.com/SadeghHayeri/GreenTunnel|{{AUR|green-tunnel}}}}
* {{App|hysteria|A powerful, lightning fast and censorship resistant proxy that masquerades as standard HTTP/3 traffic. Supports SOCKS5, TUN, and TCP/UDP forwarding. Written in Go.|https://hysteria.network/|{{AUR|hysteria}}}}
* {{App|naiveproxy|A proxy using Chrome's network stack to camouflage traffic as normal HTTPS, making it highly resistant to DPI. Written in C++.|https://github.com/klzgrad/naiveproxy|{{AUR|naiveproxy}}}}
* {{App|Psiphon|An open-source Internet censorship circumvention system that uses SSH tunneling and obfuscation to bypass firewalls. Includes both client and server components.|https://github.com/Psiphon-Labs/psiphon-tunnel-core|{{AUR|psiphon-console-client}}, {{AUR|psiphon-server}}}}
* {{App|SpoofDPI|A simple and fast tool using SOCKS5, written in Go.|https://github.com/xvzc/SpoofDPI|{{AUR|spoofdpi}}}}
* {{App|zapret|A Netfilter queue mode or SOCKS5/transparent proxy, written in C and targeted at Russian censorship.|https://github.com/bol-van/zapret|{{AUR|zapret-git}}}}

=== Speedtest tools ===

* {{App|cloudflarespeedtest|Test Cloudflare CDN latency and speed to find the fastest IP.|https://github.com/XIU2/CloudflareSpeedTest|{{AUR|cloudflarespeedtest-bin}}}}
* {{App|LibreSpeed|Open source speedtest with graphical GTK client.|https://librespeed.org/|{{AUR|speedtest-librespeed}}}}
* {{App|nperf|Wide-area network speed test application.|https://www.nperf.com/|{{AUR|nperf-gui-appimage}}}}
* {{App|SpeedTest++|Unofficial speedtest.net CLI using raw TCP for better accuracy.|https://github.com/taganaka/SpeedTest|{{AUR|speedtest++}}}}
* {{App|speedtest-cli|Command-line interface for testing internet bandwidth using speedtest.net servers.|https://github.com/sivel/speedtest-cli|{{Pkg|speedtest-cli}}}}

=== Network monitoring and diagnostics tools ===

* {{App|bandwhich|Terminal bandwidth utilization tool showing usage by process, connection, and remote IP/hostname.|https://github.com/imsnif/bandwhich |{{Pkg|bandwhich}}}}
* {{App|dog|Modern command-line DNS client alternative to dig with colored output and JSON support.|https://dns.lookup.dog/ |{{Pkg|dog}}}}
* {{App|flent|The Fleet Network Tester for measuring bufferbloat and latency under load.|https://flent.org/ |{{AUR|flent}}}}
* {{App|gping|Ping with a real-time graph visualization of latency to multiple hosts.|https://github.com/orf/gping |{{Pkg|gping}}}}
* {{App|hyperfine|Command-line benchmarking tool, useful for comparing network response times.|https://github.com/sharkdp/hyperfine |{{Pkg|hyperfine}}}}
* {{App|netsniff-ng|High-performance Linux network packet sniffer and analyzer toolkit.|http://netsniff-ng.org/ |{{Pkg|netsniff-ng}}}}
* {{App|oha|HTTP load generator with TUI showing detailed timing breakdown (DNS, TCP, TLS, TTFB).|https://github.com/hatoo/oha |{{Pkg|oha}}}}
* {{App|ooniprobe-cli|Official OONI Probe CLI for detecting internet censorship, website blocking, and traffic manipulation.|https://ooni.org/ |{{AUR|ooniprobe-cli}}}}
* {{App|sniffnet|Network traffic monitoring with TUI/GUI, statistics by protocol, and per-host analysis.|https://github.com/GyulyVGC/sniffnet |{{Pkg|sniffnet}}}}
* {{App|tcping|TCP connectivity checker that bypasses ICMP blocks for port-specific diagnostics.|https://github.com/zhengxiaowai/tcping|{{AUR|tcping}}}}
* {{App|termshark|Terminal UI for tshark, providing a Wireshark-like interface in the terminal.|https://termshark.io/ |{{Pkg|termshark}}}}
* {{App|trippy|A network diagnostic tool combining traceroute and ping with an interactive TUI.|https://github.com/fujiapple852/trippy |{{Pkg|trippy}}}}

== Web browsers ==

See also: [[Wikipedia:Comparison of web browsers]]

=== Console ===

* {{App|[[Wikipedia:Browsh|browsh]]|A fully-modern text-based browser. Runs as a frontend to headless Firefox.|https://www.brow.sh/|{{AUR|browsh}}}}
* {{App|Carbonyl|A Chromium based browser built to run in a terminal.|https://fathy.fr/carbonyl|{{AUR|carbonyl}}}}
* {{App|Chawan|A web browser for your terminal.|https://sr.ht/~bptato/chawan/|{{Pkg|chawan}}}}
* {{App|[[ELinks]]|Advanced and well-established feature-rich text mode web browser with mouse wheel scroll support, frames and tables, extensible with Lua & Guile (links fork).|http://elinks.or.cz/|{{Pkg|elinks}}}}
* {{App|[[Wikipedia:Links (web browser)|Links]]|Graphics and text mode web browser. Includes a console version similar to Lynx.|http://links.twibright.com/|{{Pkg|links}}}}
* {{App|[[Wikipedia:Lynx (web browser)|Lynx]]|Text browser for the World Wide Web.|https://lynx.invisible-island.net/|{{Pkg|lynx}}}}
* {{App|[[w3m]]|Pager/text-based web browser. It has vim-like keybindings, and is able to display images.|https://salsa.debian.org/debian/w3m|{{Pkg|w3m}}}}

=== Graphical ===

==== Gecko-based ====

See also: [[Wikipedia:Gecko (software)]]

* {{App|[[Firefox]]|Extensible browser from Mozilla based on Gecko with fast rendering.|https://mozilla.com/firefox|{{Pkg|firefox}}}}
* {{App|[[Wikipedia:SeaMonkey|SeaMonkey]]|Continuation of the Mozilla Internet Suite.|https://www.seamonkey-project.org/|{{AUR|seamonkey}}}}

===== Firefox spin-offs =====

* {{App|[[Wikipedia:Floorp|Floorp]]|Firefox-based browser developed by a community of students in Japan.| https://floorp.ablaze.one|{{AUR|floorp}}}}
* {{App|[[Wikipedia:GNU IceCat|GNU IceCat]]|A customized build of Firefox ESR distributed by the GNU Project, stripped of non-free components and with additional privacy extensions. Release cycle may be delayed compared to Mozilla Firefox.|https://www.gnu.org/software/gnuzilla/|{{AUR|icecat}}}}
* {{App|Konform Browser|A customized build of Firefox ESR focused on security, privacy and freedom. Originally based on LibreWolf.|https://codeberg.org/konform-browser|{{AUR|konform-browser}}}}
* {{App|[[Wikipedia:LibreWolf|LibreWolf]]|A fork of Firefox, focused on privacy, security and freedom.|https://librewolf.net/|{{AUR|librewolf}}}}
* {{App|[[Wikipedia:Midori (web browser)|Midori]]|Light, fast and secure browser.|https://github.com/goastian/midori-desktop|{{AUR|midori}}}}
* {{App|[[Wikipedia:Mullvad Browser|Mullvad Browser]]|Privacy-focused web browser developed by Mullvad VPN and the Tor Project based on Firefox ESR.|https://mullvad.net/en/browser|{{AUR|mullvad-browser}}}}
* {{App|[[Tor]] Browser Launcher|Securely and easily download, verify, install, and launch Tor Browser. Tor Browser is a fork of Firefox ESR with the ability to access Onion domains, plus additional privacy modifications.|https://gitlab.torproject.org/tpo/applications/torbrowser-launcher|{{Pkg|torbrowser-launcher}}}}
* {{App|[[Wikipedia:Waterfox|Waterfox]]|Fork of Mozilla Firefox featuring some privacy, usability, and speed enhancements.|https://www.waterfox.com/|{{AUR|waterfox}}}}
* {{App|[[Wikipedia:Zen Browser|Zen Browser]]|An experimental, performance-optimized fork of Firefox focused on customizability and design with additional features.|https://www.zen-browser.app/|{{AUR|zen-browser}}}}

==== Blink-based ====

See also: [[Wikipedia:Blink (web engine)]]

* {{App|[[Chromium]]|Web browser developed by Google. Chromium is the open-source project behind Google Chrome.|https://www.chromium.org/|{{Pkg|chromium}}}}

===== Privacy-focused Chromium spin-offs =====

* {{App|[[Wikipedia:Brave (web browser)|Brave]]|Web browser with built-in advertisement and tracker blocking mechanism.|https://brave.com/|{{AUR|brave-bin}}}}
* {{App|Cromite|Cromite is a Chromium fork based on Bromite (Currently unmaintained) with built-in support for ad blocking and an eye for privacy. See [https://github.com/uazo/cromite/blob/master/docs/FEATURES.md List of features].|https://www.cromite.org/|{{AUR|cromite-bin}}}}
* {{App|Helium|A browser based on Ungoogled Chromium with multiple layouts, !bangs in the address bar and a Chrome Web Store proxy.|https://helium.computer/|{{AUR|helium-browser}}}}
* {{App|Thorium|Thorium develops a periodically synchronized fork of the Chromium browser, expanded with additional patches to optimize performance, improve usability and enhance security. According to the developers' tests Thorium is 8-40% ahead of the regular Chromium, mainly due to the inclusion of additional optimizations during compilation.|https://thorium.rocks/|{{AUR|thorium-browser-bin}}}}
* {{App|[[Wikipedia:Ungoogled Chromium|Ungoogled Chromium]]|Modifications to Google Chromium for removing Google integration and enhancing privacy, control, and transparency.|https://github.com/ungoogled-software/ungoogled-chromium|{{AUR|ungoogled-chromium}}}}
* {{App|[[Wikipedia:Ungoogled Chromium|Ungoogled Chromium]] (Widevine)|The same as the regular version, but with the ability to access DRM-protected content.|https://github.com/ungoogled-software/ungoogled-chromium|{{AUR|ungoogled-chromium-widevine-bin}}}}

===== Proprietary Chromium spin-offs =====

* {{App|[[Wikipedia:Google Chrome|Google Chrome]]|Proprietary web browser developed by Google.|https://www.google.com/chrome/|{{AUR|google-chrome}}}}
* {{App|[[Wikipedia:Microsoft Edge|Microsoft Edge]]|Proprietary web browser developed by Microsoft.|https://www.microsoft.com/edge/|{{AUR|microsoft-edge-stable-bin}}}}
* {{App|[[Wikipedia:Opera (web browser)|Opera]]|Proprietary browser developed by Opera Software.|https://www.opera.com/opera|{{AUR|opera}}}}
* {{App|[[Wikipedia:Opera (web browser)#Opera GX|Opera GX]]|Proprietary "gaming-oriented" alternative to the regular Opera browser. Also developed by Opera Software.|https://www.opera.com/gx|{{AUR|opera-gx}}}}
* {{App|[[Wikipedia:SlimBrowser|Slimjet]]|Fast, smart and powerful proprietary browser based on Chromium.|https://www.slimjet.com/|{{AUR|slimjet}}}}
* {{App|[[Wikipedia:SRWare Iron|SRWare Iron]]|Light-weight proprietary browser based on Chromium.|https://www.srware.net/iron/|{{AUR|srware-iron-bin}}}}
* {{App|[[Vivaldi]]|An advanced proprietary browser made with the power user in mind.|https://vivaldi.com/|{{Pkg|vivaldi}}}}
* {{App|[[Wikipedia:Yandex Browser|Yandex Browser]]|Proprietary browser that combines a minimal design with sophisticated technology to make the web faster, safer, and easier.|https://browser.yandex.com/|{{AUR|yandex-browser}}}}

===== Browsers based on Qt WebEngine =====

{{Note|''qt5-webengine''–based browsers were removed from the list, because it is today considered insecure and outdated.}}

* {{App|Angelfish|Web browser for Plasma Mobile. Part of {{Grp|kde-network}}.|https://apps.kde.org/angelfish/|{{Pkg|angelfish}}}}
* {{App|[[Wikipedia:Dooble|Dooble]]|Colorful Web browser.|https://textbrowser.github.io/dooble/|{{AUR|dooble}}}}
* {{App|[[Wikipedia:Eric Python IDE|Eric]]|QtWebEngine-based HTML browser, part of the eric6 development toolset, can be launched with the {{ic|eric6_browser}} command.|https://eric-ide.python-projects.org/|{{AUR|eric}}}}
* {{App|[[Wikipedia:Falkon|Falkon]]|Web browser based on QtWebEngine, written in Qt framework. Part of {{Grp|kde-network}}.|https://falkon.org/|{{Pkg|falkon}}}}
* {{App|Fiery|A convergent web browser. Part of {{Grp|maui}}.|https://mauikit.org/apps/|{{Pkg|fiery}}}}
* {{App|[[Wikipedia:Konqueror|Konqueror]]|Web browser based on Qt toolkit and Qt WebEngine. Part of {{Grp|kde-network}}.|https://apps.kde.org/konqueror/|{{Pkg|konqueror}}}}
* {{App|[[qutebrowser]]|A keyboard-driven, [[vim]]-like browser based on PyQt5 and QtWebEngine.|https://qutebrowser.org/|{{Pkg|qutebrowser}}}}

===== Browsers based on Electron =====

* {{App|Catalyst|A minimal FOSS web browser with no data collection.|https://getcatalyst.eu.org|{{AUR|catalyst-browser-bin}}}}
* {{App|Franz|Messaging browser for WhatsApp, Facebook Messenger, Slack, Telegram and many other web services.|https://meetfranz.com/|{{AUR|franz}}}}
* {{App|Ferdium|A GPL-licensed alternative to Franz, forked from Franz.|https://ferdium.org/|{{AUR|ferdium}}}}
* {{App|Min|A fast, minimal browser that protects your privacy. It includes an interface designed to minimize distractions.|https://minbrowser.org/|{{AUR|min}}}}
* {{App|Vieb|Minimalist Electron-based browser with Vim-inspired keybindings and a built-in ad-blocker.|https://vieb.dev|{{AUR|vieb}}}}

==== Browsers based on WebKitGTK ====

See also: [[Wikipedia:WebKit]]

{{Note|''webkitgtk, webkitgtk2, qt5-webkit'' and ''qtwebkit''–based browsers were removed from the list, because these are today considered insecure and outdated. More info [https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-updates/ here] and [https://blogs.gnome.org/mcatanzaro/2022/11/04/stop-using-qtwebkit/ here].}}

Most of these support ad-blocking via [https://github.com/jun7/wyebadblock wyebadblock].
* {{App|[[Badwolf]]|A minimalist privacy-focused browser.|https://hacktivis.me/projects/badwolf|{{AUR|badwolf}}}}
* {{App|Eolie|Simple web browser for GNOME.|https://wiki.gnome.org/Apps/Eolie|{{Pkg|eolie}}}}
* {{App|[[GNOME Web]]|Browser which uses the WebKitGTK rendering engine. Part of {{Grp|gnome}}.|https://apps.gnome.org/Epiphany/|{{Pkg|epiphany}}}}
* {{App|[[Luakit]]|Fast, small, webkit based browser framework extensible by Lua.|https://luakit.github.io/|{{Pkg|luakit}}}}
* {{App|[[Nyxt]]|Keyboard-oriented, infinitely extensible browser designed for power users. It has familiar key-bindings (Emacs, VI, CUA) and features fuzzy searching between tabs, multiple selections, history as a tree and more.|https://nyxt.atlas.engineer/|{{Pkg|nyxt}}}}
* {{App|[[surf]]|Lightweight WebKit-based browser, which follows the [https://suckless.org/philosophy suckless philosophy] (basically, the browser itself is a single C source file).|https://surf.suckless.org/|{{AUR|surf}}}}
* {{App|Surfer|Simple keyboard based web browser, written in C. It supports custom JS-scripts.|https://github.com/nihilowy/surfer|{{AUR|surfer-git}}}}
* {{App|Tangram|Integration of web applications into the desktop, specifically GNOME.|https://apps.gnome.org/Tangram/|{{Pkg|tangram}}}}
* {{App|Vimb|A Vim-like web browser written in C that is inspired by Pentadactyl and Vimprobable. It includes a manpage and a howto for common configurations. It supports custom JS-scripts, dark mode and handles geolocation requests.|https://fanglingsu.github.io/vimb/|{{Pkg|vimb}}}}
* {{App|wyeb|A vim-like web browser inspired by dwb and luakit with Adblock.|https://github.com/jun7/wyeb|{{AUR|wyeb-git}}}}

==== Goanna-based ====

See also: [[Wikipedia:Goanna (software)]]

* {{App|[[Wikipedia:Basilisk (web browser)|Basilisk]]|A XUL-based web browser, similar in design to Firefox, aimed at providing a fully functional browsing experience with a classic interface.|https://basilisk-browser.org/|{{AUR|basilisk}}}}
* {{App|[[Wikipedia:Pale Moon (web browser)|Pale Moon]]|A Firefox fork focussing on speed, with a pre-Firefox 29 interface. Uses [[Wikipedia:Goanna (software)|Goanna]] layout engine, a fork of Gecko. Firefox add-ons may not be compatible. Without support for newer Firefox features such as WebExtensions, cache2, e10s, and OTMC. Many of the old 93,598 versions of 19,450 Firefox add-ons created by 14,274 developers over the past 15 years using XUL/XPCOM technology in the [https://github.com/JustOff/ca-archive Classic Add-ons Archive] still work.|https://www.palemoon.org/|{{AUR|palemoon}}}}

==== Servo-based ====

* {{App|[[Wikipedia:Servo (software)|Servo]]|Web browser rendering engine written in Rust, with WebGL and WebGPU support, and adaptable to desktop, mobile, and embedded applications.|https://servo.org/|{{AUR|servo}}}}
* {{App|Verso|Experimental web browser based on Servo experimenting with multi-view and multi-window and building UI elements entirely from Servo.|https://github.com/versotile-org/verso/|{{AUR|verso-git}}}}

==== Other ====

* {{App|[[Dillo]]|Small, fast graphical web browser built on [[Wikipedia:Fltk|FLTK]]. Uses its own layout engine.|https://dillo-browser.org/|{{Pkg|dillo}}}}
* {{App|[[Wikipedia:Ladybird (web browser)|Ladybird]]|Web browser built from scratch using the [[Wikipedia:SerenityOS|SerenityOS]] LibWeb engine.|https://ladybird.org/|{{AUR|ladybird}}}}
* {{App|[[Wikipedia:Links (web browser)|Links]]|Graphics and text mode web browser. Includes a graphical X-window/framebuffer version with CSS, image rendering, pull-down menus. It can be launched with the {{ic|xlinks -g}} command.|http://links.twibright.com/|{{Pkg|links}}}}
* {{App|[[Wikipedia:NetSurf|NetSurf]]|Featherweight browser written in C, notable for its slowly developing JavaScript support and fast rendering through its own layout engine.|https://www.netsurf-browser.org/|{{Pkg|netsurf}}}}

=== Gemini browsers ===

See also: [[Wikipedia:Gemini (protocol)#Software]]

* {{App|Amfora|Terminal browser for the Gemini protocol.|https://github.com/makeworld-the-better-one/amfora|{{Pkg|amfora}}}}
* {{App|Bombabillo|Non-web client for the terminal, supporting Gopher, Gemini and much more.|https://bombadillo.colorfield.space/|{{AUR|bombadillo}}}}
* {{App|Castor|Graphical client for the Gemini, Gopher, and Finger protocols, written in Rust with GTK.|https://git.sr.ht/~julienxx/castor|{{AUR|castor}}}}
* {{App|Geopard|A graphical gemini client written in rust, using the gtk4 toolkit.|https://github.com/ranfdev/Geopard|{{AUR|geopard}}}}
* {{App|Kristall|Qt-based Gemini browser.|https://github.com/MasterQ32/kristall|{{AUR|kristall}}}}
* {{App|Lagrange|Desktop GUI client for browsing Gemini space, offering modern conveniences familiar from web browsers.|https://gmi.skyjake.fi/lagrange|{{AUR|lagrange}}}}
* {{App|Telescope|w3m-like browser for Gemini.|https://www.telescope-browser.org/{{Dead link|2025|08|15|status=SSL error}}|{{AUR|telescope}}}}

== Web servers ==

A [[Wikipedia:Web server|web server]] serves HTML web pages and other files via HTTP to clients like [[:Category:Web browser|web browsers]].
The major web servers can be interfaced with programs to serve dynamic content ([[web applications]]).

See also: [[:Category:Web server]], [[Wikipedia:Comparison of web server software]]

* {{App|[[Apache HTTP Server]]|A high performance Unix-based HTTP server.|https://httpd.apache.org/|{{Pkg|apache}}}}
* {{App|[[Caddy]]|HTTP/3 web server with automatic HTTPS.|https://caddyserver.com/|{{Pkg|caddy}}}}
* {{App|[[Hiawatha]]|Secure and advanced web server.|https://hiawatha.leisink.net/|{{AUR|hiawatha}}}}
* {{App|[[Lighttpd]]|A secure, fast, compliant and very flexible web-server.|https://www.lighttpd.net/|{{Pkg|lighttpd}}}}
* {{App|[[nginx]]|Lightweight HTTP server and IMAP/POP3 proxy server.|https://nginx.org/|{{Pkg|nginx}}}}
* {{App|sthttpd|Supported fork of the thttpd web server.|https://github.com/blueness/sthttpd|{{AUR|sthttpd}}}}
* {{App|Traefik|A modern reverse proxy and load balancer that makes deploying microservices easy.|https://traefik.io/traefik/|{{Pkg|traefik}}}}
* {{App|yaws|Web server/framework written in Erlang.|https://erlyaws.github.io/|{{AUR|yaws}}}}

=== Static web servers ===

* {{App|Apache Traffic Server|Fast, scalable and extensible HTTP/1.1 and HTTP/2 compliant caching proxy server.|https://trafficserver.apache.org/|{{AUR|trafficserver}}}}
* {{App|darkhttpd|A small and secure static web server, written in C, does not support HTTPS or Auth.|https://unix4lyfe.org/darkhttpd/|{{Pkg|darkhttpd}}}}
* {{App|http.server|[[Python]] standard library module, which can be used from the command-line, but due to security considerations not recommended for production.|https://docs.python.org/library/http.server.html|{{Pkg|python}}}}
* {{App|[[miniserve]]|Rust alternative to darkhttpd with UTF-8, optional HTTP authentication, file uploading, and more.|https://github.com/svenstaro/miniserve|{{Pkg|miniserve}}}}
* {{App|quark|An extremely small and simple http get-only web server. It only serves static pages on a single host.|https://tools.suckless.org/quark/|{{AUR|quark-git}}}}
* {{App|serve|Static file serving and directory listing.|https://github.com/zeit/serve|{{AUR|nodejs-serve}}}}
* {{App|Webfs|Simple and instant web server for mostly static content.|https://linux.bytesex.org/misc/webfs.html|{{AUR|webfs}}}}

=== Specialized web servers ===

* {{App|chezdav|WebDAV server that allows to share a particular directory.|https://wiki.gnome.org/phodav|{{Pkg|phodav}}}}
* {{App|LibreKitten|Block-based programming language based off Scratch that includes a web server extension.|https://librekitten.org|{{AUR|librekitten-cli-bin}}}}
* {{App|Mongoose|Embedded web server library, supports WebSocket and MQTT.|https://github.com/cesanta/mongoose|{{AUR|mongoose}}}}
* {{App|OnionShare|Lets you securely and anonymously send and receive files. It works by starting a web server, making it accessible as a Tor onion service, and generating an unguessable web address so others can download files from you, or upload files to you.|https://onionshare.org/|{{Pkg|onionshare}}}}
* {{App|Transfer More|A minimalist open-source upload HTTP server to store and share files temporarily, written in Crystal, and based on Kemal.|https://up.sceptique.eu/|{{AUR|transfer-more}}}}
* {{App|VServer|GTK application, which opens an http server in the selected folder and shares your files.|https://github.com/bcedu/ValaSimpleHTTPServer|{{AUR|vserver-git}}}}
* {{App|webhook|Small server for creating HTTP endpoints (hooks)|https://github.com/adnanh/webhook|{{Pkg|webhook}}}}
* {{App|Woof|An ad-hoc single file webserver; Web Offer One File.|http://www.home.unix-ag.org/simon/woof.html|{{AUR|woof}}}}

=== WSGI servers ===

* {{App|Gunicorn|A Python WSGI HTTP Server for UNIX.|https://gunicorn.org/|{{Pkg|gunicorn}}}}
* {{App|[[uWSGI]]|A fast, self-healing and developer/sysadmin-friendly application container server written in C.|https://uwsgi-docs.readthedocs.io/|{{Pkg|uwsgi}}}}
* {{App|Waitress|A WSGI server for Python 3.|https://github.com/Pylons/waitress|{{Pkg|python-waitress}}}}

Apache also supports WSGI with [[mod_wsgi]].

=== Performance testing ===

* {{App|httperf|Can generate various HTTP workloads, written in C.|https://github.com/httperf/httperf|{{AUR|httperf-git}}}}
* {{App|httping|A "ping"-like tool for HTTP requests|https://www.vanheusden.com/httping/|{{Pkg|httping}}}}
* {{App|http_load|A webserver performance testing tool, runs in a single process.|https://www.acme.com/software/http_load/{{Dead link|2025|03|15|status=SSL error}}|{{AUR|http_load}}}}
* {{App|siege|An HTTP regression testing and benchmarking utility.|https://www.joedog.org/siege-home/|{{Pkg|siege}}}}
* {{App|vegeta|HTTP load testing tool, written in Go.|https://github.com/tsenart/vegeta|{{Pkg|vegeta}}}}
* {{App|Web Bench|Benchmarking tool, uses fork() for simulating multiple clients.|http://home.tiscali.cz/~cz210552/webbench.html|{{AUR|webbench}}}}

== File sharing ==

=== Download managers ===

See also: [[Wikipedia:Comparison of download managers]]

==== Console ====

* {{App|[[aria2]]|Lightweight download utility that supports HTTP/S, FTP, SFTP, BitTorrent and Metalink. It can run as a daemon controlled via a built-in JSON-RPC or XML-RPC interface.|https://aria2.github.io/|{{Pkg|aria2}}}}
* {{App|Axel|Featherweight command line download accelerator sitting at under 250kB on disk. Supports HTTP/S and FTP.|https://github.com/eribertomota/axel|{{Pkg|axel}}}}
* {{App|[[cURL]]|A URL retrieval utility and library. Supports HTTP, FTP and SFTP.|https://curl.haxx.se/|{{Pkg|curl}}}}
* {{App|Gtuber|Fetch media info from websites (bilibili, lbry, niconico, reddit, twitch, youtube). Includes a command-line downloader ({{ic|gtuber-dl}}) and a GStreamer plugin, which is used automatically when you try playing video from website that Gtuber can handle in your GStreamer based application.|https://github.com/Rafostar/gtuber|{{AUR|gtuber}}}}
* {{App|HTTPie|Human-friendly command-line HTTP client for the API era.|https://github.com/httpie/httpie|{{Pkg|httpie}}}}
* {{App|[[Wikipedia: dargahamn.net | dargahamn.net ]]|An easy-to-use offline browser utility. It allows you to download a World Wide Web site from the Internet to a local directory, building recursively all directories, getting HTML, images, and other files from the server to your computer.|https://www. dargahamn.net .com/|{{Pkg| dargahamn.net }}}}
* {{App|[[Wikipedia:Lftp|LFTP]]|Sophisticated file transfer program. Supports HTTP, FTP, SFTP, FISH, and BitTorrent.|https://lftp.yar.ru/|{{Pkg|lftp}}}}
* {{App|Plowshare|A set of command-line tools designed for managing file-sharing websites (aka Hosters).|https://github.com/mcrapet/plowshare|{{AUR|plowshare}}}}
* {{App|[[Wikipedia:RTMPDump|RTMPDump]]|Download FLV videos through RTMP (Adobe's proprietary protocol for Flash video players)|http://rtmpdump.mplayerhq.hu/|{{Pkg|rtmpdump}}}}
* {{App|snarf|Command-line URL retrieval tool. Supports HTTP and FTP.|https://www.xach.com/snarf/|{{AUR|snarf}}}}
* {{App|[[Streamlink]]|Launch streams from various streaming services in a custom video player or save them to a file.|https://streamlink.github.io/|{{Pkg|streamlink}}}}
* {{App|[[Wikipedia:Streamripper|Streamripper]]|Records and splits streaming mp3 into tracks.|https://streamripper.sourceforge.net/|{{AUR|streamripper}}}}
* {{App|[[Wget]]|A network utility to retrieve files from the Web. Supports HTTP and FTP.|https://www.gnu.org/software/wget/|{{Pkg|wget}}}}
* {{App|yewtube|Terminal-based YouTube player and downloader.|https://github.com/mps-youtube/yewtube|{{AUR|yewtube}}}}
* {{App|You-Get|Download media contents (videos, audios, images) from the Web.|https://you-get.org/|{{AUR|you-get}}}}
* {{App|youtube-dl|Download videos from YouTube and many other web sites.|https://rg3.github.io/youtube-dl/|{{AUR|youtube-dl}}}}
* {{App|youtube-viewer|Command line utility for viewing YouTube videos.|https://github.com/trizen/youtube-viewer|{{AUR|youtube-viewer}}}}
* {{App|[[yt-dlp]]|A youtube-dl fork with additional features and fixes.|https://github.com/yt-dlp/yt-dlp|{{Pkg|yt-dlp}}}}
* {{App|ytfzf|A POSIX script to find and watch youtube videos from the terminal.|https://github.com/pystardust/ytfzf|{{Pkg|ytfzf}}}}

==== Graphical ====

* {{App|ClipGrab|Downloader and converter for YouTube, Vimeo and many other online video sites.|https://clipgrab.org/|{{AUR|clipgrab}}}}
* {{App|FatRat|Qt based download manager with support for HTTP, FTP, SFTP, BitTorrent and Metalink.|https://github.com/LubosD/fatrat|{{AUR|fatrat-git}}}}
* {{App|Forklift|Simple GUI for youtube-dl using PyGObject.|https://github.com/Johnn3y/Forklift|{{AUR|forklift-git}}}}
* {{App|gtk-youtube-viewer|GTK utility for viewing YouTube videos. See optional dependencies for the GUI.|https://github.com/trizen/youtube-viewer|{{AUR|youtube-viewer}}}}
* {{App|[[Wikipedia:Wget#GWget|Gwget]]|Download manager for GNOME. Supports HTTP and FTP.|https://gitlab.gnome.org/Archive/gwget|{{AUR|gwget}}}}
* {{App|Gydl|GUI wrapper around the already existing youtube-dl program to download content from sites like YouTube.|https://github.com/JannikHv/gydl|{{AUR|gydl-git}}}}
* {{App|Gyre|GTK3 downloader for videos from Coub.|https://github.com/HelpSeeker/Gyre|{{AUR|gyre}}}}
* {{App|[[JDownloader]]|Java-based downloader for one-click hosting sites.|https://jdownloader.org/|{{AUR|jdownloader2}}}}
* {{App|[[Wikipedia:KGet|KGet]]|Download manager for KDE. Supports HTTP, FTP, BitTorrent and Metalink. Part of {{Grp|kde-network}}.|https://apps.kde.org/kget/|{{Pkg|kget}}}}
* {{App|MegaBasterd|Yet another unofficial MEGA downloader/uploader/streaming suite.|https://github.com/tonikelope/megabasterd|{{AUR|megabasterd-bin}}}}
* {{App|Motrix|Full-featured download manager that supports downloading HTTP, FTP, BitTorrent, Magnet, etc. Based on the [https://electronjs.org/ Electron] platform.|https://motrix.app/|{{AUR|motrix}}}}
* {{App|Persepolis|Graphical front-end for aria2 download manager with lots of features. Supports HTTP and FTP.|https://persepolisdm.github.io/|{{Pkg|persepolis}}}}
* {{App|[[pyLoad]]|Downloader written in Python and designed to be extremely lightweight, easily extensible and fully manageable via web.|https://pyload.net/|{{AUR|pyload-ng}}}}
* {{App|Steadyflow|Simple download manager for GNOME. Supports HTTP and FTP.|https://launchpad.net/steadyflow|{{Pkg|steadyflow}}}}
* {{App|Streamtuner2|Internet radio station and video browser. It simply lists stations in categories from different directories and launches your preferred media apps for playback.|https://sourceforge.net/projects/streamtuner2/|{{AUR|streamtuner2}}}}
* {{App|uGet|GTK download manager featuring download classification and HTML import. Supports HTTP, FTP, BitTorrent, Metalink, YouTube and Mega.|https://ugetdm.com/|{{Pkg|uget}}}}
* {{App|Varia|GTK frontend for aria2c and yt-dlp.|https://github.com/giantpinkrobots/varia|{{AUR|varia}}}}
* {{App|Video Downloader|GTK application to download videos from websites like YouTube and many others (based on youtube-dl).|https://github.com/Unrud/video-downloader|{{AUR|video-downloader}}}}
* {{App|Xtreme Download Manager|Powerful tool to increase download speed up-to 500%. Supports HTTP and FTP. Video grabber works in a general way and is not limited to certain websites.|https://subhra74.github.io/xdm/|{{AUR|xdman}}}}
* {{App|youtubedl-gui|Simple-to-use graphical interface for youtube-dl.|https://github.com/JaGoLi/ytdl-gui|{{AUR|youtubedl-gui}}}}

=== LAN file transfer ===

See also: [[#LAN messengers]]

* {{App|LAN Share|Cross-platform local area network file transfer application, built using Qt GUI framework. It can be used to transfer a whole folder, one or more files, large or small immediately without any additional configuration.|https://github.com/abdularis/LAN-Share|{{AUR|lanshare}}}}
* {{App|LocalSend|Cross-platform app to securely share files and messages with nearby devices over the local network without needing an internet connection.|https://localsend.org/|{{AUR|localsend}}}}
* {{App|Magic Wormhole|Command-line tool {{ic|wormhole}} to securely transfer data between computers.|https://github.com/magic-wormhole/magic-wormhole|{{Pkg|magic-wormhole}}}}
* {{App|NitroShare|Cross-platform network file transfer application, built using Qt GUI framework. It is designed to make transferring files from one device to another on the local network extremely simple.|https://nitroshare.net/|{{AUR|nitroshare}}}}
* {{App|Teleport|Native GTK3 application to effortlessly share files on the local network.|https://gitlab.gnome.org/jsparber/teleport|{{AUR|teleport-share-git}}}}
* {{App|Warp|Securely send files to each other via the internet or local network by exchanging a word-based code. It uses the Magic Wormhole protocol.|https://apps.gnome.org/Warp/|{{Pkg|warp}}}}
* {{App|Warpinator|GTK application to share files across the LAN.|https://github.com/linuxmint/warpinator|{{Pkg|warpinator}}}}

=== Cloud storage servers ===

* {{App|copyparty|Lightweight and portable file server with extensive protocol, media playback and file management support.|https://github.com/9001/copyparty|{{Pkg|copyparty}}}}
* {{App|[[Cozy]]|A personal cloud you can hack, host and delete.|https://cozy.io/|{{Pkg|cozy-stack}}}}
* {{App|[[Nextcloud]]|A cloud server to store your files centrally on a hardware controlled by you.|https://nextcloud.com|{{Pkg|nextcloud}}}}
* {{App|[[Pydio]]|Mature open source web application for file sharing and synchronization.|https://pydio.com/|{{AUR|pydio}}}}
* {{App|Seafile|An online file storage and collaboration tool with advanced support for file syncing, privacy protection and teamwork.|https://www.seafile.com/|{{AUR|seafile-server}}}}

=== Cloud synchronization clients ===

{{Tip|<nowiki></nowiki>
* Some [[synchronization and backup programs]] provide direct support for some cloud-storage services.
* Some [[FUSE#List of FUSE filesystems|FUSE filesystems]] provide a way to mount cloud-storage as a filesystem. Google Drive can be accessed also by {{Pkg|kio-gdrive}} for KIO-based applications (like [[Dolphin]]).
* See [[Data-at-rest encryption#Cloud-storage optimized]] to achieve zero-knowledge (client-side transparent encryption) storage on any third-party cloud service.
}}

==== Multi-protocol clients ====

* {{App|CloudCross|Synchronize local files and folders with many cloud providers. Mail.ru Cloud, Yandex Disk, Google Drive, OneDrive and Dropbox support is available.|https://github.com/MasterSoft24/CloudCross|{{AUR|cloudcross}}}}
* {{App|Rclone|Multi-provider sync, copy, and mount client.|https://rclone.org/|{{Pkg|rclone}}}}
* {{App|Rclone Browser|GUI client for Rclone.|https://github.com/kapitainsky/RcloneBrowser|{{AUR|rclone-browser}}}}

==== Google Drive clients ====

* {{App|DriveSync|Command line utility that synchronizes your Google Drive files with a local folder on your machine.|https://github.com/MStadlmeier/drivesync|{{AUR|drivesync}}}}
* {{App|gdrive|Command line utility for interacting with Google Drive.|https://github.com/prasmussen/gdrive|{{AUR|gdrive}}}}
* {{App|Google Drive OCamlFUSE|A FUSE filesystem for Google Drive, written in OCaml.|https://github.com/astrada/google-drive-ocamlfuse|{{AUR|google-drive-ocamlfuse}}}}
* {{App|Grive|Google Drive client with support for new Drive REST API and partial sync.|https://github.com/vitalif/grive2|{{AUR|grive}}}}
* {{App|[[Insync]]|Unofficial proprietary Google Drive desktop client.|https://www.insynchq.com/|{{AUR|insync}}}}

==== Other synchronization clients ====

* {{App|aws-cli|CLI for Amazon Web Services, including efficient file transfers to and from Amazon S3.|https://aws.amazon.com/cli/|{{Pkg|aws-cli}}}}
* {{App|Backblaze B2|Backblaze B2 open-source command-line client.|https://www.backblaze.com/b2/cloud-storage.html|{{AUR|backblaze-b2}}}}
* {{App|Baidu Netdisk|Proprietary client for cloud storage service launched by Baidu (formerly Baidu Cloud).|https://pan.baidu.com|{{AUR|baidunetdisk-bin}}}}
* {{App|[[Cozy]] Drive|Desktop client for Cozy.|https://cozy-labs.github.io/cozy-desktop/|{{Pkg|cozy-desktop}}}}
* {{App|[[Dropbox]]|Proprietary desktop client for Dropbox.|https://www.dropbox.com/|{{AUR|dropbox}}}}
* {{App|[[Wikipedia:Mega (service)|Mega]] Sync Client|Proprietary (though [https://github.com/meganz/MEGAsync/blob/master/LICENCE.md source-available]) desktop client to sync files with Mega.|https://mega.nz/|CLI: {{AUR|megacmd}}, GUI: {{AUR|megasync}}}}
* {{App|Megatools|Unofficial CLI for Mega.|https://megatools.megous.com/|{{AUR|megatools}}}}
* {{App|[[Nextcloud]] Client|Desktop client for Nextcloud.|https://nextcloud.com/|{{Pkg|nextcloud-client}}}}
* {{App|Nutstore|Proprietary desktop client for Nutstore.|https://www.jianguoyun.com/|{{AUR|nutstore}}}}
* {{App|OneDrive|Fork of the unofficial CLI for [https://onedrive.live.com/about/ OneDrive].|https://github.com/abraunegg/onedrive|{{AUR|onedrive-abraunegg}}}}
* {{App|[[Wikipedia:ownCloud|ownCloud]] Desktop Client|Desktop syncing client for ownCloud.|https://owncloud.com/client/|{{Pkg|owncloud-client}}}}
* {{App|pCloud Drive|Proprietary desktop syncing client for pCloud. Based on the [https://electronjs.org/ Electron] platform.|https://www.pcloud.com/download-free-online-cloud-file-storage.html|{{AUR|pcloud-drive}}}}
* {{App|[[Pydio]]Sync|Desktop client for Pydio.|https://pydio.com/|{{AUR|pydio-sync}}}}
* {{App|S3cmd|Unofficial CLI for Amazon S3.|https://s3tools.org/s3cmd|{{Pkg|s3cmd}}}}
* {{App|Seafile Client|GUI client for Seafile.|https://www.seafile.com/|{{AUR|seafile-client}}}}
* {{App|[[Wikipedia:SpiderOak|SpiderOak]] One|Proprietary client for SpiderOak One.|https://spideroak.com/|{{AUR|spideroak-one}}}}
* {{App|[[Wikipedia:Synology|Synology]] Drive|Proprietary GUI client to sync and share files between a centralized Synology NAS and multiple client computers.|https://www.synology.com/|{{AUR|synology-drive}}}}
* {{App|[[Wikipedia:Tresorit|Tresorit]]|Proprietary desktop syncing client for Tresorit.|https://tresorit.com/download|{{AUR|tresorit}}}}
* {{App|Versiobit|Desktop file sync client with versioning and end-to-end encryption.|https://versiobit.com|{{AUR|versiobit}}}}
* {{App|[[Yandex Disk]]|Proprietary CLI for Yandex Disk.|https://disk.yandex.ru/|{{AUR|yandex-disk}}}}

=== FTP ===

==== FTP clients ====

See also: [[Wikipedia:Comparison of FTP client software]]

* {{App|[[CurlFtpFS]]|is a filesystem for accessing FTP hosts based on FUSE and libcurl.|https://curlftpfs.sourceforge.net/|{{Pkg|curlftpfs}}}}
* {{App|[[Wikipedia:FileZilla|FileZilla]]|Fast and reliable FTP, FTPS and SFTP client.|https://filezilla-project.org/|{{Pkg|filezilla}}}}
* {{App|ftp|Simple ftp client provided by GNU Inetutils|https://www.gnu.org/software/inetutils/manual/inetutils.html#ftp-invocation|{{Pkg|inetutils}}}}
* {{App|lftp|Sophisticated command line based FTP client|https://lftp.yar.ru/|{{Pkg|lftp}}}}
* {{App|ncftp|A set of free application programs implementing FTP.|https://www.ncftp.com/|{{Pkg|ncftp}}}}
* {{App|[[Wikipedia:tnftp|tnftp]]|FTP client with several advanced features for [[Wikipedia:NetBSD|NetBSD]].|https://freshmeat.sourceforge.net/projects/tnftp|{{Pkg|tnftp}}}}

Some file managers like [[Dolphin]], [[GNOME Files]] and [[Thunar]] also provide FTP functionality.

==== FTP servers ====

See also: [[Wikipedia:List of FTP server software]]

* {{App|bftpd|Small, easy-to-configure FTP server|https://bftpd.sourceforge.net/|{{Pkg|bftpd}}}}
* {{App|ftpd|Simple ftp server provided by GNU Inetutils|https://www.gnu.org/software/inetutils/manual/inetutils.html#ftpd-invocation|{{Pkg|inetutils}}}}
* {{App|proFTPd|A secure and configurable FTP server|http://www.proftpd.org/|{{AUR|proftpd}}}}
* {{App|[[Pure-FTPd]]|Free (BSD-licensed), secure, production-quality and standard-compliant FTP server.|https://www.pureftpd.org/project/pure-ftpd/|{{AUR|pure-ftpd}}}}
* {{App|[[vsftpd]]|Lightweight, stable and secure FTP server for UNIX-like systems.|https://security.appspot.com/vsftpd.html|{{Pkg|vsftpd}}}}

=== BitTorrent clients ===

Some [[#Download managers|download managers]] are also able to connect to the BitTorrent network: [[Aria2]], [[Wikipedia:Lftp|LFTP]], FatRat, [[Wikipedia:KGet|KGet]], [[Wikipedia:MLDonkey|MLDonkey]], uGet.

See also: [[Wikipedia:Comparison of BitTorrent clients]]

==== Console ====

* {{App|Ctorrent|CTorrent is a BitTorrent client implemented in C++ to be lightweight and quick.|http://www.rahul.net/dholmes/ctorrent/|{{AUR|enhanced-ctorrent}}}}
* {{App|[[Deluge]]|BitTorrent client with multiple user interfaces in a client/server model. This package includes a console client.|https://deluge-torrent.org/|{{Pkg|deluge}}}}
* {{App|peerflix|Streaming torrent client for node.js.|https://github.com/mafintosh/peerflix|{{AUR|peerflix}}}}
* {{App|[[rTorrent]]|Simple and lightweight ncurses BitTorrent client.|https://rakshasa.github.io/rtorrent/|{{Pkg|rtorrent}}}}
* {{App|[[Transmission]] CLI|Simple and easy-to-use BitTorrent client with a daemon version and multiple front-ends. This package includes backend, daemon, command-line interface, and a Web UI interface.|https://transmissionbt.com/|{{Pkg|transmission-cli}}}}

==== Graphical ====

* {{App|[[Deluge]] (GTK interface)|User-friendly BitTorrent client written in Python using GTK.|https://deluge-torrent.org/|{{Pkg|deluge-gtk}}}}
* {{App|Fragments|Easy to use BitTorrent client for the GNOME desktop environment.|https://apps.gnome.org/Fragments/|{{Pkg|fragments}}}}
* {{App|[[Wikipedia:FrostWire|FrostWire]]|Easy to use cloud downloader, BitTorrent client and media player.|https://www.frostwire.com/|{{AUR|frostwire}}}}
* {{App|Gopeed|Modern download manager built with Golang and Flutter that supports HTTP, BitTorrent, Magnet protocol.|https://gopeed.com/|{{AUR|gopeed-bin}}}}
* {{App|[[Ktorrent]]|Feature-rich BitTorrent client for KDE. Part of {{Grp|kde-network}}.|https://apps.kde.org/ktorrent/|{{Pkg|ktorrent}}}}
* {{App|PikaTorrent|Pick a Torrent, stream and download on all your devices.|https://www.pikatorrent.com/|{{AUR|pikatorrent-bin}}, {{AUR|pikatorrent-git}}}}
* {{App|Powder Player|Hybrid between a streaming BitTorrent client and a player. Based on the [https://electronjs.org/ Electron] platform.|https://powder.media/|{{AUR|powder-player-bin}}}}
* {{App|[[qBittorrent]]|Open source (GPLv2) BitTorrent client with an integrated torrent search engine that strongly resembles µTorrent.|https://www.qbittorrent.org/|{{Pkg|qbittorrent}}}}
* {{App|[[Wikipedia:Tixati|Tixati]]|Proprietary peer-to-peer file sharing program that uses the popular BitTorrent protocol.|https://tixati.com/|{{AUR|tixati}}}}
* {{App|[[Transmission]]|Simple and easy-to-use BitTorrent client with a daemon version and multiple front-ends.|https://transmissionbt.com/|GTK: {{Pkg|transmission-gtk}}, Qt: {{Pkg|transmission-qt}}}}
* {{App|[[Transmission]] Remote|GTK client for remote management of the Transmission BitTorrent client, using its HTTP RPC protocol.|https://github.com/transmission-remote-gtk/transmission-remote-gtk|{{Pkg|transmission-remote-gtk}}}}
* {{App|Tremotesf|Qt client for remote management of the Transmission BitTorrent client, using its HTTP RPC protocol.|https://github.com/equeim/tremotesf2|{{AUR|tremotesf}}}}
* {{App|[[Wikipedia:Tribler|Tribler]]|4th generation file sharing system BitTorrent client.|https://www.tribler.org|{{AUR|tribler-bin}}}}
* {{App|[[Wikipedia:Vuze|Vuze]]|Feature-rich BitTorrent client written in Java (formerly Azureus).|https://www.vuze.com/|{{AUR|vuze}}}}
* {{App|WebTorrent Desktop|Streaming BitTorrent application. Based on the [https://electronjs.org/ Electron] platform.|https://webtorrent.io/desktop/|{{AUR|webtorrent-desktop}}}}

=== Other P2P networks ===

See also: [[Wikipedia:Comparison of file-sharing applications]]

* {{App|[[aMule]]|Well-known eDonkey/Kad client with a daemon version and GTK, web, and CLI front-ends.|https://www.amule.org/|{{Pkg|amule}}}}
* {{App|EiskaltDC++|Direct Connect and ADC client.|https://github.com/eiskaltdcpp/eiskaltdcpp|GTK: {{AUR|eiskaltdcpp-gtk}}, Qt: {{AUR|eiskaltdcpp-qt}}}}
* {{App|[[Wikipedia:gtk-gnutella|gtk-gnutella]]|GTK server/client for the Gnutella peer-to-peer network.|https://gtk-gnutella.sourceforge.net/|{{AUR|gtk-gnutella}}}}
* {{App|[[IPFS]]|IPFS is a P2P Network capable of sharing and receiving files.|https://ipfs.io/|{{Pkg|kubo}}}}
* {{App|KaMule|KDE graphical front-end for aMule.|https://github.com/nihui/kamule/|{{AUR|kamule}}}}
* {{App|LBRY|Browser and wallet for LBRY, the decentralized, user-controlled content marketplace. Based on the [https://electronjs.org/ Electron] platform.|https://lbry.io/|{{AUR|lbry-desktop}}}}
* {{App|lbt|Small set of command-line tools for LBRY.|https://gitlab.com/gardenappl/lbt|{{AUR|lbt}}}}
* {{App|[[Wikipedia:MLDonkey|MLDonkey]]|Multi-protocol P2P client that supports HTTP, FTP, BitTorrent, Direct Connect, eDonkey and FastTrack.|https://mldonkey.sourceforge.net/|{{AUR|mldonkey}}}}
* {{App|ncdc|Modern and lightweight Direct Connect and ADC client with a friendly ncurses interface.|https://dev.yorhel.nl/ncdc|{{AUR|ncdc}}}}
* {{App|Nicotine+|A graphical client for the Soulseek P2P network.|https://github.com/Nicotine-Plus/nicotine-plus|{{Pkg|nicotine+}}}}
* {{App|Send Anywhere|Proprietary file sharing service where users can directly share digital content in real time. Based on the [https://electronjs.org/ Electron] platform.|https://send-anywhere.com/|{{AUR|sendanywhere}}}}

=== Pastebin services ===

See also: [[Wikipedia:Pastebin]]

Pastebin services are often used to quote text or images while collaborating and troubleshooting. Pastebin clients provide a convenient way to post from the command line.

{{Warning|{{ic|pastebin.com}} has a bad reputation due to its history of hosting malware, plus it requires JavaScript and displays advertisements. It is wise '''not''' to use that service and prefer alternatives listed below.}}

==== Without a dedicated client ====

Some services can be used with more general command line tool such as [[cURL]]. For extensions, such as line numbers, more command line tools can be used such as {{ic|cat -n}}.

* [https://0x0.st/ 0x0.st] is a file hosting service. Usage examples are:
:{{bc|1=$ ''command'' {{!}} curl -F 'file=@-' <nowiki>https://0x0.st</nowiki>}} or upload a file: {{bc|1=$ curl -F 'file=@''path/to/file''' <nowiki>https://0x0.st</nowiki>}}
:{{Note|Read the instructions on the website for further options such as file removal tokens, expiration, and private URLs.}}
* [https://paste.c-net.org/ paste.c-net.org] accepts HTTP requests and works with [[nc]].
* [https://privatebin.info/ privatebin.info] is a minimalist, open-source online pastebin service where the server has zero knowledge of stored data. It focuses on decentralized hosting and has a [https://privatebin.info/directory/ directory of public instances].
* [https://termbin.com termbin.com] works with [[nc]].

==== Dedicated clients ====

* {{App|Fb-client|Client for the [https://paste.xinu.at/ paste.xinu.at] pastebin.|https://paste.xinu.at|{{Pkg|fb-client}}}}
* {{App|Gist|Command-line interface for the [https://gist.github.com/ gist.github.com] pastebin service.|https://github.com/defunkt/gist|{{Pkg|gist}}}}
* {{App|imgur|A CLI client which can upload image to [https://imgur.com imgur.com] image sharing service.|https://github.com/tremby/imgur.sh|{{AUR|imgur.sh}}}}
* {{App|Pastebinit|Really small Python script that acts as a Pastebin client (see {{ic|pastebinit -l}} for the list of servers).|https://launchpad.net/pastebinit|{{Pkg|pastebinit}}}}
* {{App|ruby-haste|Client for [https://hastebin.com/ hastebin.com].|https://github.com/seejohnrun/haste-client|{{AUR|ruby-haste}}}}
* {{App|Wgetpaste|Bash script that automates pasting to a number of pastebin services.|http://wgetpaste.zlin.dk/|{{Pkg|wgetpaste}}}}

== Communication ==

=== Email clients ===

See also: [[Wikipedia:Comparison of email clients]]

==== Console ====

* {{App|[[aerc]]|Work in progress asynchronous email client.|https://sr.ht/~rjarry/aerc|{{Pkg|aerc}}}}
* {{App|alot|An experimental terminal MUA based on [https://notmuchmail.org/ notmuch mail]. It is written in python using the [https://urwid.org/ urwid] toolkit.|https://github.com/pazz/alot|{{Pkg|alot}}}}
* {{App|[[Alpine]]|Fast, easy-to-use and Apache-licensed email client based on [[Wikipedia:Pine (email client)|Pine]].|https://alpineapp.email/|{{AUR|alpine}}}}
* {{App|himalaya|Himalaya CLI is written in Rust, based on email-lib.|https://github.com/pimalaya/himalaya|{{Pkg|himalaya}}}}
* {{App|mu/mu4e|Email indexer (mu) and client for emacs (mu4e). Xapian based for fast searches.|https://www.djcbsoftware.nl/code/mu/mu4e.html|{{AUR|mu}}}}
* {{App|[[Mutt]]|Small but very powerful text-based mail client.|http://www.mutt.org/|{{Pkg|mutt}}}}
* {{App|[[Mutt|NeoMutt]]|Command line mail reader (or MUA). It is a fork of Mutt with added features.|https://neomutt.org/|{{Pkg|neomutt}}}}
* {{App|[[nmh]]|A modular mail handling system.|https://www.nongnu.org/nmh/|{{AUR|nmh}}}}
* {{App|[[notmuch]]|A fast mail indexer built on top of ''xapian''.|https://notmuchmail.org/|{{Pkg|notmuch}}}}
* {{App|sendemail|A lightweight command line SMTP email client written in Perl.|http://caspian.dotconf.net/menu/Software/SendEmail/|{{AUR|sendemail}}}}
* {{App|[[S-nail]]|a mail processing system with a command syntax reminiscent of ''ed'' with lines replaced by messages. Provides the functionality of [[Wikipedia:mailx|mailx]].|https://www.sdaoden.eu/code.html#s-mailx|{{Pkg|s-nail}}}}
* {{App|[[Sup]]|CLI mail client with very fast searching, tagging, threading and GMail like operation.|https://sup-heliotrope.github.io/|{{AUR|sup}}}}
* {{App|swaks|Swiss Army Knife SMTP; Command line SMTP testing, including TLS and AUTH, can be used to send emails.|https://jetmore.org/john/code/swaks/|{{Pkg|swaks}}}}
* {{App|Wanderlust|Email client and news reader for Emacs.|https://github.com/wanderlust/wanderlust/|{{Pkg|wanderlust}}}}

==== Graphical ====

* {{App|Balsa|Simple and light email client for GNOME.|https://pawsa.fedorapeople.org/balsa/|{{Pkg|balsa}}}}
* {{App|Betterbird|Fork of thunderbird.|https://www.betterbird.eu/|{{AUR|betterbird-bin}}}}
* {{App|[[Wikipedia:Claws Mail|Claws Mail]]|Lightweight GTK-based email client and news reader.|https://www.claws-mail.org/|{{Pkg|claws-mail}}}}
* {{App|ElectronMail|Unofficial desktop application for several end-to-end encrypted email providers (like ProtonMail, Tutanota). Based on the [https://electronjs.org/ Electron] platform.|https://github.com/vladimiry/ElectronMail|{{AUR|electronmail-bin}}}}
* {{App|[[Evolution]]|Mature and feature-rich e-mail client that is part of the GNOME project. Part of {{Grp|gnome-extra}}.|https://gitlab.gnome.org/GNOME/evolution/-/wikis/home|{{Pkg|evolution}}}}
* {{App|Geary|Simple desktop mail client built in [[Wikipedia:Vala (programming language)|Vala]]. Part of {{Grp|gnome-extra}}.|https://wiki.gnome.org/Apps/Geary|{{Pkg|geary}}}}
* {{App|[[Wikipedia:Kmail|Kmail]]|Mature and feature-rich email client. Part of {{Grp|kde-pim}}.|https://kontact.kde.org/components/kmail/|{{Pkg|kmail}}}}
* {{App|Mailspring|Fork of [[Wikipedia:Nylas Mail|Nylas Mail]] by one of the original authors. The paid "Pro" version requires a Mailspring ID and has extra features like snooze, send later. Based on the [https://electronjs.org/ Electron] platform.|https://getmailspring.com/|{{AUR|mailspring}}}}
* {{App|[[Wikipedia:SeaMonkey#Mail|SeaMonkey Mail & Newsgroups]]|Email client included in the SeaMonkey suite.|https://www.seamonkey-project.org/|{{AUR|seamonkey}}}}
* {{App|[[Thunderbird]]|Feature-rich email client from Mozilla written in GTK.|https://www.thunderbird.net/|{{Pkg|thunderbird}}}}
* {{App|Tutanota|Email client for Tutanota mail service. Based on the [https://electronjs.org/ Electron] platform.|https://tutanota.com/|{{AUR|tutanota-desktop}}}}

==== Web-based ====

* {{App|[[Nextcloud]] Mail|An email webapp for NextCloud.|https://github.com/nextcloud/mail|{{Pkg|nextcloud-app-mail}}}}
* {{App|[[Roundcube]]|Browser-based multilingual IMAP client webapp with a native application-like user interface.|https://roundcube.net/|{{Pkg|roundcubemail}}}}
* {{App|SquirrelMail|Webmail for Nuts!|https://squirrelmail.org/|{{AUR|squirrelmail}}}}

=== Mail notifiers ===

* {{App|Ayatana Webmail|Webmail notifications and actions for any desktop.|https://tari.in/www/software/ayatana-webmail/{{Dead link|2025|08|15|status=404}}|{{AUR|ayatana-webmail}}}}
* {{App|Bubblemail|New and Unread mail notification service for local mailboxes, pop, imap, and gnome online accounts. A fork of Mailnag.|http://bubblemail.free.fr/|{{AUR|bubblemail}}}}
* {{App|Gnubiff|Mail notification program that checks for mail and displays headers when new mail has arrived.|https://gnubiff.sourceforge.net/|{{Pkg|gnubiff}}}}
* {{App|Mailnag|Extensible mail notification daemon.|https://github.com/pulb/mailnag|{{Pkg|mailnag}}}}

=== Mail servers ===

See [[Mail server]].

* {{App|DavMail|POP/IMAP/SMTP/Caldav/Carddav/LDAP exchange gateway allowing users to use any mail/calendar client with an Exchange server.|https://davmail.sourceforge.net/|{{AUR|davmail}}}}
* {{App|Modoboa|A modular mail hosting and management platform, written in Python.|https://modoboa.org/|{{AUR|modoboa}}}}

=== Mail retrieval agents ===

See also: [[Wikipedia:Mail retrieval agent]]

* {{App|[[fdm]]|Program to fetch and deliver mail.|https://github.com/nicm/fdm|{{Pkg|fdm}}}}
* {{App|[[Wikipedia:Fetchmail|Fetchmail]]|A remote-mail retrieval utility.|https://www.fetchmail.info/|{{Pkg|fetchmail}}}}
* {{App|[[getmail]]|A POP3/IMAP4 mail retriever with reliable Maildir and command delivery.|http://pyropus.ca/software/getmail/|{{AUR|getmail}}}}
* {{App|hydroxide|A third-party, open-source ProtonMail CardDAV, IMAP and SMTP bridge|https://github.com/emersion/hydroxide|{{AUR|hydroxide}}}}
* {{App|imapsync|IMAP synchronisation, sync, copy or migration tool|https://imapsync.lamiral.info/|{{Pkg|imapsync}}}}
* {{App|[[isync]]|IMAP and MailDir mailbox synchronizer|https://isync.sourceforge.net/|{{Pkg|isync}}}}
* {{App|mpop|A small, fast POP3 client suitable as a fetchmail replacement|https://marlam.de/mpop/|{{Pkg|mpop}}}}
* {{App|[[OfflineIMAP]]|Synchronizes emails between two repositories.|https://www.offlineimap.org/|{{Pkg|offlineimap}}}}
* {{App|vomit|Rust utility to sync between Maildir mailbox and IMAP mailbox|https://git.sr.ht/~bitfehler/vomit-sync/tree/master/item/cli/README.md|{{AUR|vsync}} (sync-only part of {{AUR|vomit}} mail tookit)}}

=== Instant messaging clients ===

See also: [[Wikipedia:Comparison of instant messaging clients]], [[Wikipedia:Comparison of VoIP software]]

This section lists all client software with [[Wikipedia:Instant messaging|instant messaging]] support.

==== Multi-protocol clients ====

{{Note|All messengers that support several networks by means of direct connections to them belong to this section.}}

The number of networks supported by these clients is very large but they (like any multi-protocol clients) usually have very limited or no support for network-specific features.

===== Console =====

* {{App|[[Bitlbee|BitlBee]]|IRC gateway to popular chat networks.|https://bitlbee.org/|{{AUR|bitlbee}}}}
* {{App|Finch|Ncurses-based chat client that uses libpurple and supports all its protocols (Bonjour, Gadu-Gadu, Groupwise, IRC, SIMPLE, XMPP, Zephyr).|https://developer.pidgin.im/wiki/Using%20Finch|{{AUR|finch}}}}
* {{App|[[WeeChat]]|Modular, lightweight ncurses-based IRC client. A variety of other protocols are supported through plugins.|https://weechat.org/|{{Pkg|weechat}}}}

===== Graphical =====

* {{App|[[Wikipedia:Jitsi|Jitsi]]|Audio/video VoIP phone and instant messenger written in Java that supports protocols such as SIP, XMPP, IRC and many other useful features.|https://jitsi.org/|{{AUR|jitsi}}}}
* {{App|Lith|WeeChat Relay client, allowing to connect to a running WeeChat instance from anywhere.|https://lith.app/|{{AUR|lith-git}}}}
* {{App|[[Pidgin]]|Multi-protocol instant messaging client with audio support that uses libpurple and supports all its protocols (Bonjour, Gadu-Gadu, Groupwise, IRC, SIMPLE, XMPP, Zephyr).|https://pidgin.im/|{{AUR|pidgin}}}}
* {{App|[[Wikipedia:Smuxi|Smuxi]]|Cross-platform IRC client that also supports XMPP.|https://smuxi.im/|{{AUR|smuxi}}}}
* {{App|[[Thunderbird]]|Feature-rich email client supports instant messaging and chat using IRC and XMPP.|https://www.thunderbird.net/|{{Pkg|thunderbird}}}}
* {{App|glowing-bear-electron|A web client for WeeChat|https://glowing-bear.org/|{{AUR|glowing-bear-electron}}}}

==== IRC clients ====

See also: [[Wikipedia:Comparison of Internet Relay Chat clients]]

===== Console =====

* {{App|[[Wikipedia:BitchX|BitchX]]|Console-based IRC client developed from the popular [[Wikipedia:ircII|ircII]].|https://bitchx.sourceforge.net/|{{AUR|bitchx-git}}}}
* {{App|catgirl|TLS-only terminal IRC client.|https://git.causal.agency/catgirl|{{AUR|catgirl}}}}
* {{App|ERC|Powerful, modular and extensible IRC client for [[Emacs]].|https://savannah.gnu.org/projects/erc/|included with {{Pkg|emacs}}}}
* {{App|[[ii]]|Featherweight IRC client, literally {{ic|tail -f}} the conversation and {{ic|echo}} back your replies to a file.|https://tools.suckless.org/ii/|{{AUR|ii}}}}
* {{App|ircii|Oldest maintained IRC client which lays claim to being small and fast owing to its reduced feature set.|http://www.eterna23.net/ircii/|{{AUR|ircii}}}}
* {{App|[[Irssi]]|Highly-configurable ncurses-based IRC client.|https://irssi.org/|{{Pkg|irssi}}}}
* {{App|pork|Programmable, ncurses-based IRC client that mostly looks and feels like ircII.|http://dev.ojnk.net/|{{Pkg|pork}}}}
* {{App|ScrollZ|Advanced IRC client based on [[Wikipedia:ircII|ircII]].|https://www.scrollz.info/|{{AUR|scrollz}}}}
* {{App|senpai|An IRC client that works best with bouncers (e.g. {{Pkg|soju}}): no logs are kept, history is fetched from the server via [https://ircv3.net/specs/extensions/chathistory CHATHISTORY], networks are fetched from the server via [https://git.sr.ht/~emersion/soju/tree/master/item/doc/ext/bouncer-networks.md bouncer-networks].
|https://sr.ht/~delthas/senpai/|{{Pkg|senpai}}}}
* {{App|sic|Extremely simple IRC client, similar to [[Wikipedia:Ii (IRC client)|ii]].|https://tools.suckless.org/sic/|{{AUR|sic}}}}
* {{App|tiny|an IRC client written in Rust with a clutter-free interface|https://github.com/osa1/tiny|{{Pkg|tiny}}}}

===== Graphical =====

* {{App|[[Wikipedia:ChatZilla|ChatZilla]]|Clean, easy to use and highly extensible Internet Relay Chat (IRC) client, built on the Mozilla platform using [[Wikipedia:XULRunner|XULRunner]]. Included in the [[Wikipedia:SeaMonkey|SeaMonkey]] suite.|http://chatzilla.hacksrus.com/|{{AUR|seamonkey}}}}
* {{App|Halloy|An open-source IRC client written in Rust, with the iced GUI library.|https://halloy.squidowl.org/|{{Pkg|halloy}}}}
* {{App|[[HexChat]]|Fork of XChat for Linux and Windows.|https://hexchat.github.io/|{{AUR|hexchat}}}}
* {{App|[[Wikipedia:Konversation|Konversation]]|Qt-based IRC client for the KDE desktop. Part of {{Grp|kde-network}}.|https://konversation.kde.org/|{{Pkg|konversation}}}}
* {{App|[[Wikipedia:KVIrc|KVIrc]]|Qt-based IRC client featuring extensive themes support.|https://kvirc.net/|{{Pkg|kvirc}}}}
* {{App|Loqui|GTK IRC client.|https://loqui.sunnyone.org/|{{AUR|loqui}}}}
* {{App|LostIRC|Simple GTK IRC client with tab-autocompletion, multiple server support, logging and others.|https://lostirc.sourceforge.net|{{AUR|lostirc}}}}
* {{App|Polari|Simple IRC client by the GNOME project. Part of {{Grp|gnome-extra}}.|https://apps.gnome.org/Polari/|{{Pkg|polari}}}}
* {{App|[[Quassel]]|Modern, cross-platform, distributed IRC client.|https://quassel-irc.org/|KDE: {{Pkg|quassel-monolithic}}, Qt: {{Pkg|quassel-monolithic-qt}}}}
* {{App|Srain|Modern, beautiful IRC client written in GTK 3.|https://srain.silverrainz.me|{{AUR|srain}}}}
* {{App|Thelounge|Modern self-hosted web IRC client|https://thelounge.chat/|{{AUR|thelounge}}}}

==== XMPP clients ====

See also: [[Wikipedia:XMPP]]

===== Console =====

* {{App|Freetalk|Console-based XMPP client.|https://www.gnu.org/software/freetalk/|{{AUR|freetalk}}}}
* {{App|jabber.el|Minimal XMPP client for [[Emacs]].|https://emacs-jabber.sourceforge.net/|{{AUR|emacs-jabber}}}}
* {{App|MCabber|Small XMPP console client, includes features: SSL, PGP, MUC, OTR and UTF8.|https://mcabber.com/|{{Pkg|mcabber}}}}
* {{App|Poezio|XMPP client with IRC feeling|https://poez.io/|{{AUR|poezio}}}}
* {{App|Profanity|A console based XMPP client inspired by Irssi.|https://profanity-im.github.io/|{{Pkg|profanity}}}}

===== Graphical =====

* {{App|Converse.js|Web-based XMPP chat client written in JavaScript.|https://conversejs.org/|{{AUR|conversejs}}}}
* {{App|Dino|A modern, easy to use XMPP client, with PGP and OMEMO support.|https://dino.im/|{{Pkg|dino}}}}
* {{App|[[Gajim]]|XMPP client with audio support written in Python using GTK.|https://gajim.org/|{{Pkg|gajim}}}}
* {{App|Kaidan|A simple, user-friendly Jabber/XMPP client providing a modern user interface using Kirigami and QtQuick.|https://www.kaidan.im/|{{Pkg|kaidan}}}}
* {{App|Libervia (Salut à Toi)|Web frontend for Salut à Toi, multi-purpose XMPP client|https://libervia.org/|{{AUR|libervia-web-hg}}}}
* {{App|Nextcloud JavaScript XMPP Client|Chat app for Nextcloud with XMPP, end-to-end encryption, video calls, file transfer & group chat.|https://github.com/nextcloud/jsxc.nextcloud|{{AUR|nextcloud-app-jsxc}}}}
* {{App|[[Wikipedia:Psi (instant messaging client)|Psi]]|Qt-based XMPP client.|https://psi-im.org/|{{Pkg|psi}}}}
* {{App|[[Wikipedia:Spark (XMPP client)|Spark]]|Cross-platform real-time XMPP collaboration client optimized for business and organizations.|https://www.igniterealtime.org/projects/spark/|{{AUR|spark}}}}
* {{App|Swift|XMPP client written in C++ with Qt and Swiften.|https://swift.im/|{{AUR|swift-im}}}}
* {{App|[[Wikipedia:Tkabber|Tkabber]]|Easy to hack feature-rich XMPP client by the author of the ejabberd XMPP server.|https://tkabber.jabber.ru/|{{AUR|tkabber}}}}
* {{App|Vacuum IM|Full-featured crossplatform XMPP client.|https://github.com/Vacuum-IM/vacuum-im|{{AUR|vacuum-im}}}}

==== SIP clients ====

See also: [[Wikipedia:List of SIP software#Clients]]

* {{App|baresip|portable and modular SIP User-Agent with audio and video support.|https://github.com/baresip/baresip|{{Pkg|baresip}}}}
* {{App|[[Wikipedia:Blink (SIP client)|Blink]]|State of the art, easy to use SIP client.|https://icanblink.com/|{{AUR|blink}}}}
* {{App|Calls|Simple, elegant phone dialer and call handler for GNOME. It can be used with a cellular modem for plain old telephone calls as well as VoIP calls using the SIP protocol.|https://gitlab.gnome.org/GNOME/calls|{{Pkg|gnome-calls}}}}
* {{App|Jami|SIP-compatible softphone and instant messenger for the decentralized Jami network. Formerly known as Ring and SFLphone.|https://jami.net/|{{Pkg|jami-qt}}}}
* {{App|[[Wikipedia:Linphone|Linphone]]|VoIP phone application (SIP client) for communicating freely with people over the internet, with voice, video, and text instant messaging.|https://www.linphone.org/|{{AUR|linphone-desktop}}}}
* {{App|[[Wikipedia:Twinkle (software)|Twinkle]]|Qt softphone for VoIP and IM communication using SIP.|http://twinkle.dolezel.info/|{{AUR|twinkle}}}}
* {{App|Zoiper|Proprietary SIP and IAX2 VoIP softphone|https://zoiper.com|{{AUR|zoiper-bin}}}}

==== Matrix clients ====

See also: [[Matrix]], [https://matrix.org/clients/ Matrix Clients]

* {{App|Chatty|Simple to use SMS and Matrix messaging application.|https://gitlab.gnome.org/World/Chatty|{{Pkg|chatty}}}}
* {{App|Cinny|Cinny is a matrix client focusing primarily on simple, elegant and secure interface. The desktop app is made with [https://github.com/tauri-apps/tauri Tauri].|https://github.com/cinnyapp/cinny-desktop|{{AUR|cinny-desktop}}}}
* {{App|Element|Glossy Matrix client with an emphasis on performance and usability. Web application and desktop application based on the [https://electronjs.org/ Electron] platform.|https://element.io/|{{Pkg|element-web}}, {{Pkg|element-desktop}}}}
* {{App|FluffyChat|Multi-platform Matrix client with a simple and clean UI written in Dart/Flutter.|https://fluffychat.im/|{{AUR|fluffychat}}}}
* {{App|Fractal|Matrix client for GNOME written in Rust.|https://wiki.gnome.org/Apps/Fractal|{{Pkg|fractal}}}}
* {{App|Gomuks|Terminal Matrix client written in Go using [https://github.com/tulir/mautrix-go mautrix] and [https://github.com/tulir/mauview mauview].|https://maunium.net/go/gomuks|{{Pkg|gomuks}}}}
* {{App|iamb|A terminal-based Matrix client with Vim keybindings written in Rust.|https://github.com/ulyssa/iamb|{{Aur|iamb}}}}
* {{App|Moment|A fancy, customizable, keyboard-operable Matrix chat client for encrypted and decentralized communication. Written in Qt/QML + Python with nio, fork of the now-abandoned Mirage.|https://mx-moment.xyz/|{{AUR|moment}}}}
* {{App|Neochat|KDE client for the Matrix protocol. Part of {{Grp|kde-network}}.|https://apps.kde.org/neochat/|{{Pkg|neochat}}}}
* {{App|nheko|Desktop client for the Matrix protocol.|https://github.com/Nheko-Reborn/nheko|{{Pkg|nheko}}}}
* {{App|Quaternion|Qt5-based IM client for the Matrix protocol.|https://github.com/QMatrixClient/Quaternion|{{AUR|quaternion}}}}
* {{App|QuickMedia|A rofi inspired native client for web services. Supports Matrix and several other sites.|https://git.dec05eba.com/QuickMedia/about/|{{AUR|quickmedia}}}}
* {{App|SchildiChat|Matrix client based on Element with a more traditional instant messaging experience. Based on the [https://electronjs.org/ Electron] platform.|https://schildi.chat/|{{AUR|schildichat-desktop-eol}}}}
* {{App|Spectral|Qt5-based Glossy cross-platform client for Matrix.|https://gitlab.com/spectral-im/spectral|{{AUR|spectral-matrix}}}}
* {{App|Syphon|Privacy-centric cross-platform Matrix client with E2EE support, currently in alpha.|https://github.com/syphon-org/syphon|{{AUR|syphon-bin}}}}

==== Tox clients ====

See also: [[Tox]], [https://wiki.tox.chat/clients Comparison of Tox clients]

* {{App|ratox|FIFO based tox client.|https://git.z3bra.org/ratox/file/README.html|{{AUR|ratox-git}}}}
* {{App|Toxic|ncurses-based Tox client|https://github.com/Jfreegman/toxic|{{Pkg|toxic}}}}
* {{App|Venom|a modern Tox client for the GNU/Linux desktop|https://github.com/naxuroqa/Venom|{{AUR|venom}}}}
* {{App|µTox|Lightweight Tox client.|https://github.com/uTox/uTox|{{Pkg|utox}}}}

==== LAN messengers ====

See also: [[Avahi#Link-Local (Bonjour/Zeroconf) chat]], [[Wikipedia:Comparison of LAN messengers]]

* {{App|BeeBEEP|Secure LAN Messenger.|https://www.beebeep.net/|{{AUR|beebeep}}}}
* {{App|iptux|LAN communication software, compatible with IP Messenger.|https://github.com/iptux-src/iptux|{{Pkg|iptux}}}}

==== P2P messaging clients ====

See also: [[Ring]], [[Tox]]

* {{App|[[Wikipedia:Briar (software)|Briar]]|Briar is a messaging application designed for activists, journalists, and anyone else who needs a safe, easy and robust way to communicate.|https://briarproject.org/|{{AUR|briar-desktop}}, {{AUR|briar-headless}}}}
* {{App|Manyverse|Modern decentralized messaging and sharing application built on top of Secure Scuttlebutt (SSB).|https://gitlab.com/staltz/manyverse|{{AUR|manyverse-bin}}}}
* {{App|Patchwork|Decentralized messaging and sharing application built on top of Secure Scuttlebutt (SSB). Based on the [https://electronjs.org/ Electron] platform.|https://github.com/ssbc/patchwork|{{AUR|ssb-patchwork}}}}
* {{App|Poncho Wonky|Decentralized messaging and sharing application built on top of Secure Scuttlebutt (SSB). Based on the [https://electronjs.org/ Electron] platform. Maintained, updated Fork of Patchwork|https://github.com/soapdog/patchwork/|{{AUR|poncho-wonky}}}}
* {{App|RetroShare|Serverless encrypted instant messenger with filesharing, chatgroups, mail.|https://retroshare.cc/|{{AUR|retroshare}}}}
* {{App|[[Wikipedia:Ricochet (software)|Ricochet]]|Anonymous peer-to-peer instant messaging system built on [[Tor]] hidden services.|https://www.ricochetrefresh.net/|{{AUR|ricochet-refresh}}}}

==== Chatmail clients ====

* {{App|Delta Chat|A privacy oriented [https://chatmail.at/ chatmail] application. Based on the [https://electronjs.org/ Electron] platform.|https://delta.chat/|{{Pkg|deltachat-desktop}}}}
* {{App|Parla|A [https://chatmail.at/ chatmail] application for the [[GNOME]] desktop. Based on the [[GTK]] framework.|https://github.com/trufae/parla/|{{Pkg|parla}}}}

==== Other IM clients ====

* {{App|Caprine|Unofficial Facebook Messenger app. Based on the [https://electronjs.org/ Electron] platform.|https://github.com/sindresorhus/caprine|{{AUR|caprine}}}}
* {{App|Chatterino|Chat client for Twitch chat.|https://chatterino.com/|{{AUR|chatterino2}}}}
* {{App|[[Discord]]|Proprietary all-in-one voice and text chat application for gamers that’s free and works on both your desktop and phone. Based on the [https://electronjs.org/ Electron] platform.|https://discordapp.com/|{{Pkg|discord}}}}
* {{App|Flare|Unofficial Signal client based on GTK.|https://gitlab.com/schmiddi-on-mobile/flare|{{AUR|flare}}}}
* {{App|[[Wikipedia:Gitter|Gitter]]|Communication product for communities and teams on GitLab and GitHub.|https://gitter.im/|{{AUR|gitter-bin}}}}
* {{App|[[Wikipedia:Jitsi|Jitsi]] Meet|Desktop application for Jitsi Meet. Based on the [https://electronjs.org/ Electron] platform.|https://github.com/jitsi/jitsi-meet-electron|{{AUR|jitsi-meet-desktop}}}}
* {{App|Kotatogram Desktop|Experimental fork of Telegram Desktop.|https://kotatogram.github.io/|{{AUR|kotatogram-desktop}}}}
* {{App|Matterhorn|Console client for the Mattermost chat system.|https://github.com/matterhorn-chat/matterhorn|{{AUR|matterhorn}}}}
* {{App|[[Mattermost]] Desktop|Desktop application for Mattermost. Based on the [https://electronjs.org/ Electron] platform.|https://github.com/mattermost/desktop|{{Pkg|mattermost-desktop}}}}
* {{App|[[Mumble]]|Voice chat application similar to TeamSpeak.|https://www.mumble.info/|{{Pkg|mumble}}}}
* {{App|Paper Plane|Chat over Telegram on a modern and elegant client.|https://github.com/paper-plane-developers/paper-plane|{{AUR|paper-plane}}}}
* {{App|[[QQ]]|Proprietary instant messaging software developed by Tencent (imitating ICQ).|https://im.qq.com/|{{AUR|linuxqq}}}}
* {{App|Rocket.Chat Desktop|Desktop application for Rocket.Chat. Based on the [https://electronjs.org/ Electron] platform.|https://github.com/RocketChat/Rocket.Chat.Electron|{{AUR|rocketchat-desktop}}}}
* {{App|Ruqola|Rocket.Chat client for the KDE desktop.|https://apps.kde.org/ruqola/|{{AUR|ruqola}}}}
* {{App|Session Desktop|Onion routing based messenger. Based on the [https://electronjs.org/ Electron] platform.|https://getsession.org/|{{AUR|session-desktop}}}}
* {{App|[[Wikipedia:Signal (software)|Signal]] Desktop|Desktop application for Signal private messenger. Based on the [https://electronjs.org/ Electron] platform.|https://github.com/signalapp/Signal-Desktop|{{Pkg|signal-desktop}}}}
* {{App|[[Wikipedia:Slack (software)|Slack]]|Proprietary Slack client for desktop. Based on the [https://electronjs.org/ Electron] platform.|https://slack.com/|{{AUR|slack-desktop}}}}
* {{App|teams-for-linux|Unofficial Microsoft Teams for Linux client. Based on the [https://electronjs.org/ Electron] platform.|https://github.com/IsmaelMartinez/teams-for-linux|{{AUR|teams-for-linux}}}}
* {{App|[[TeamSpeak]]|Proprietary VoIP application with gamers as its target audience.|https://www.teamspeak.com/|{{Pkg|teamspeak3}}}}
* {{App|[[TeamTalk]]|Proprietary VoIP application with video chat, file and desktop sharing. Desktop sharing does not appear to be working in Linux though. AUR package is server only, but client is built in the make process.|https://bearware.dk|{{AUR|teamtalk}}}}
* {{App|[[Telegram]] Desktop|Official Telegram desktop client.|https://desktop.telegram.org/|{{Pkg|telegram-desktop}}}}
* {{App|[[Wikipedia:Viber|Viber]]|Proprietary cross-platform IM and VoIP software.|https://www.viber.com/products/linux/|{{AUR|viber}}}}
* {{App|[[Wikipedia:WeChat|WeChat]]|Tencent WeChat Client.|https://linux.weixin.qq.com/|{{AUR|wechat}}}}
* {{App|[[Wikipedia:Wire (software)|Wire]]|Modern, private messenger. Based on the [https://electronjs.org/ Electron] platform.|https://wire.com/|{{AUR|wire-desktop}}}}
* {{App|[[Zoom Meetings|Zoom]]|Proprietary video conferencing, online meetings and group messaging application.|https://zoom.us/|{{AUR|zoom}}}}
* {{App|[[Wikipedia:Zulip|Zulip]]|Desktop client for Zulip group chat. Based on the [https://electronjs.org/ Electron] platform.|https://zulipchat.com/apps/linux|{{AUR|zulip-desktop}}}}

=== Instant messaging servers ===

See also: [[Wikipedia:Comparison of instant messaging protocols]]

==== IRC servers ====

* {{App|Ergo|A modern and simple to set up IRC server written in Go. Combines the features of an IRCd, a services framework, and a bouncer.|https://ergo.chat/|{{AUR|ergochat}}}}
* {{App|[[InspIRCd]]|A stable, modern and lightweight IRC daemon.|https://www.inspircd.org/|{{AUR|inspircd}}}}
* {{App|IRCD-Hybrid|A lightweight, high-performance internet relay chat daemon.|https://www.ircd-hybrid.org/|{{AUR|ircd-hybrid}}}}
* {{App|miniircd|A small and configuration free IRC server, suitable for private use.|https://github.com/jrosdahl/miniircd|{{AUR|miniircd-git}}}}
* {{App|ngIRCd|A free, portable and lightweight Internet Relay Chat server for small or private networks.|https://ngircd.barton.de/|{{AUR|ngircd}}}}
* {{App|Solanum|Solanum is the upcoming IRCd for unified networks that is being worked on by a collaboration of Libera Chat and OFTC staff.|https://solanum.chat/|{{AUR|solanum-ircd-git}}}}
* {{App|[[UnrealIRCd]]|Open Source IRC Server.|https://www.unrealircd.org/|{{Pkg|unrealircd}}}}

==== XMPP servers ====

* {{App|Ejabberd|Robust, scalable and extensible XMPP Server written in Erlang|https://www.ejabberd.im/|{{Pkg|ejabberd}}}}
* {{App|Jabberd2|An XMPP server written in the C language and licensed under the GNU General Public License. It was inspired by jabberd14.|https://jabberd2.org/|{{AUR|jabberd2}}}}
* {{App|[[Openfire]]|An XMPP IM multiplatform server written in Java|https://www.igniterealtime.org/projects/openfire/|{{Pkg|openfire}}}}
* {{App|[[Prosody]]|An XMPP server written in the [https://www.lua.org/ Lua] programming language. Prosody is designed to be lightweight and highly extensible. It is licensed under a permissive [https://prosody.im/source/mit MIT license].|https://prosody.im/|{{Pkg|prosody}}}}

==== SIP servers ====

See also: [[Wikipedia:List of SIP software#Servers]]

* {{App|[[Asterisk]]|A complete PBX solution.|https://www.asterisk.org/|{{AUR|asterisk}}}}
* {{App|Kamailio|SIP server for large VoIP and real-time communication platforms.|https://www.kamailio.org/|{{AUR|kamailio}}}}
* {{App|openSIPS|SIP proxy/server for voice, video, IM, presence and any other SIP extensions.|https://opensips.org/|{{Pkg|opensips}}}}
* {{App|Repro|An open-source, free SIP server.|https://www.resiprocate.org/About_Repro{{Dead link|2025|04|05|status=404}}|{{AUR|repro}}}}
* {{App|[[Wikipedia:Yate (telephony engine)|Yate]]|Advanced, mature, flexible telephony server that is used for VoIP and fixed networks, and for traditional mobile operators and MVNOs.|https://yate.ro/|{{Pkg|yate}}}}

==== Other IM servers ====

* {{App|[[Mattermost]]|Open source private cloud server, Slack-alternative.|https://github.com/mattermost/mattermost-server|{{Pkg|mattermost}}}}
* {{App|[[Murmur]]|The voice chat application server for Mumble.|https://www.mumble.info/|{{Pkg|mumble-server}}}}
* {{App|Nextcloud Talk|Video- and audio-conferencing app for Nextcloud.|https://github.com/nextcloud/spreed|{{Pkg|nextcloud-app-spreed}}}}
* {{App|Rocket.Chat|Web chat server, developed in JavaScript, using the Meteor fullstack framework.|https://github.com/RocketChat/Rocket.Chat|{{AUR|rocketchat-server}}}}
* {{App|[[Matrix|Synapse]]|Reference homeserver for the Matrix protocol.|https://github.com/matrix-org/synapse|{{Pkg|matrix-synapse}}}}
* {{App|[[TeamSpeak]] Server|Proprietary VoIP conference server.|https://teamspeak.com/|{{Pkg|teamspeak3-server}}}}
* {{App|uMurmur|Minimalistic Mumble server.|https://umurmur.net/|{{Pkg|umurmur}}}}

=== Collaborative software ===

See also: [[Wikipedia:Collaborative software]]

* {{App|[[SOGo]]|Groupware server built around OpenGroupware.org (OGo) and the SOPE application server.|https://sogo.nu/|{{AUR|sogo}}}}

=== Link shortening servers ===

* {{App|microbin|A tiny, self-contained, configurable paste bin and URL shortener written in Rust.|https://github.com/szabodanika/microbin|{{AUR|microbin}}}}
* {{App|shlink|Self-proclaimed definitive self-hosted URL shortener.|https://shlink.io/|{{AUR|shlink}}}}
* {{App|YOURLS|A self-hosted link shortening service written in PHP.|https://yourls.org/|{{AUR|yourls}}}}

== News, RSS, and blogs ==

=== News aggregators ===

[[Web feed]]s aggregators. Some [[#Email clients|email clients]] are also able to act as news aggregator: [[Wikipedia:Claws Mail|Claws Mail]] RSSyl plugin, [[Evolution]], [[Wikipedia:SeaMonkey#Mail|SeaMonkey Mail & Newsgroups]], [[Thunderbird]].

See also: [[Wikipedia:Comparison of feed aggregators]]

==== Console ====

* {{App|Bulletty|Pretty TUI RSS reader that locally stores articles as markdown.|https://bulletty.croci.dev/|{{Pkg|bulletty}}}}
* {{App|[[Wikipedia:Canto (news aggregator)|Canto]]|Ncurses RSS aggregator.|https://github.com/themoken/canto-curses|{{Pkg|canto-curses}}}}
* {{App|Ditch The Bell|A highly configurable Linux-based desktop notifier for RSS/Atom feeds.|https://github.com/eschermoore/ditchthebell|{{AUR|dtbell-git}}}}
* {{App|feed2imap-go|[https://github.com/feed2imap/feed2imap feed2imap] reimplemented in Go that aggregating RSS/Atom/jsonfeed into folders of your IMAP mailbox.|https://github.com/Necoro/feed2imap-go|{{AUR|feed2imap-go}}}}
* {{App|[[Wikipedia:Gnus|Gnus]]|Email, NNTP and RSS client for Emacs.|https://www.gnus.org/|{{Pkg|emacs}}}}
* {{App|[[Newsboat]]|Ncurses RSS aggregator with layout and keybinding similar to the [[Mutt]] email client.|https://newsboat.org/|{{Pkg|newsboat}}}}
* {{App|[[Newsraft]]|Feed reader with ncurses user interface. It is greatly inspired by [[Newsboat]] and tries to be its lightweight counterpart. |https://codeberg.org/newsraft/newsraft/|{{AUR|newsraft}}}}
* {{App|Rawdog|"RSS Aggregator Without Delusions Of Grandeur" that parses RSS/CDF/Atom feeds into a static HTML page of articles in chronological order.|https://offog.org/code/rawdog/|{{AUR|rawdog}}}}
* {{App|rss2email|Aggregating your RSS/Atom feed into your IMAP/Maildir mailbox as a cronjob.|https://github.com/rss2email/rss2email|{{Pkg|rss2email}}}}
* {{App|sfeed|Crontab oriented shell-scriptable feed aggregator setup with an RSS/Atom parser utility plus a simple ncurses reader.|https://codemadness.org/sfeed-simple-feed-parser.html|{{AUR|sfeed}}}}
* {{App|Snownews|Text mode RSS news reader.|https://sourceforge.net/projects/snownews/|{{AUR|snownews}}}}

==== Graphical ====

* {{App|[[Wikipedia:Kontact#News feed aggregator|Akregator]]|News aggregator for KDE, part of {{Grp|kde-pim}}.|https://apps.kde.org/akregator/|{{Pkg|akregator}}}}
* {{App|Alligator|Kirigami-based RSS/Atom feed reader for mobile devices. Part of {{Grp|kde-network}}.|https://apps.kde.org/alligator/|{{Pkg|alligator}}}}
* {{App|Feeds|An RSS/Atom feed reader for GNOME.|https://gfeeds.gabmus.org/|{{Pkg|gfeeds}}}}
* {{App|Fluent Reader|Modern desktop RSS reader built with React and Fluent UI. Based on the [https://electronjs.org/ Electron] platform.|https://hyliu.me/fluent-reader/|{{AUR|fluent-reader}}}}
* {{App|HackUp|Read Hacker News from the desktop.|https://github.com/mdh34/hackup|{{AUR|hackup-git}}}}
* {{App|[[Wikipedia:Liferea|Liferea]]|GTK news aggregator for online news feeds and weblogs.|https://lzone.de/liferea/|{{Pkg|liferea}}}}
* {{App|Newsflash|Modern feed reader designed for the GNOME desktop. The spiritual successor to FeedReader.|https://apps.gnome.org/NewsFlash/|{{Pkg|newsflash}}}}
* {{App|Raven|Simple desktop RSS reader made using VueJS. Based on the [https://electronjs.org/ Electron] platform.|https://ravenreader.app/|{{AUR|raven-reader}}}}
* {{App|RSS Guard|Very tiny RSS and ATOM news reader developed using Qt framework.|https://github.com/martinrotter/rssguard|{{Pkg|rssguard}}}}
* {{App|Tickr|GTK-based RSS Reader that displays feeds as a smooth scrolling line on your desktop, as known from TV stations.|https://www.open-tickr.net/|{{AUR|tickr}}}}

==== Graphical, Web-based ====

* {{App|[[Nextcloud]] News|RSS/Atom feed reader for Nextcloud.|https://github.com/nextcloud/news|{{Pkg|nextcloud-app-news}}}}
* {{App|selfoss|The new multipurpose RSS reader, live stream, mashup, aggregation web application.|https://selfoss.aditu.de/|{{AUR|selfoss}}}}
* {{App|[[Tiny Tiny RSS]]|Web-based news feed (RSS/Atom) aggregator.|https://tt-rss.org/|{{Pkg|tt-rss}}}}

=== Podcast clients ===

Some media players are also able to act as podcast client: [[Amarok]], Cantata, [[Wikipedia:Clementine (software)|Clementine]], Goggles Music Manager, [[Wikipedia:Rhythmbox|Rhythmbox]], [[VLC media player]]. [[Wikipedia:git-annex|git-annex]] can also [https://git-annex.branchable.com/tips/downloading_podcasts/ function as podcatcher].

See also: [[Wikipedia:List of podcatchers]]

==== Console ====

* {{App|castero|A TUI podcast client for the terminal.|https://github.com/xgi/castero|{{AUR|castero-git}}}}
* {{App|castget|Simple, command-line RSS enclosure downloader, primarily intended for automatic, unattended downloading of podcasts.|https://castget.johndal.com/|{{Pkg|castget}}}}
* {{App|gpo|Text mode interface of gPodder.|https://gpodder.github.io/|{{Pkg|gpodder}}}}
* {{App|Greg|A command-line podcast aggregator.|https://github.com/manolomartinez/greg|{{AUR|greg-git}}}}
* {{App|pcd|A minimal podcast client written in go|https://github.com/kvannotten/pcd|{{AUR|pcd}}}}

==== Graphical ====

* {{App|gPodder|Podcast client and media aggregator (GTK interface).|https://gpodder.github.io/|{{Pkg|gpodder}}}}
* {{App|Kasts|Convergent podcast application that looks good on desktop and mobile. Part of {{Grp|kde-multimedia}}.|https://apps.kde.org/kasts/|{{Pkg|kasts}}}}
* {{App|Pocket Casts|Electron wrapper around the Pocket Casts web app with support for MPRIS (media controls).|https://pocketcasts.com/|{{AUR|pocket-casts-linux}}}}
* {{App|Podcasts|Podcast client for the GNOME desktop written in Rust.|https://apps.gnome.org/Podcasts/|{{Pkg|gnome-podcasts}}}}
* {{App|Vocal|Simple podcast client for the Modern Desktop (GTK).|https://vocalproject.net/|{{AUR|vocal}}}}

=== Usenet newsreaders ===

Some [[#Email clients|email clients]] are also able to act as Usenet newsreader: [[Wikipedia:Claws Mail|Claws Mail]], [[Evolution]], [[Mutt|NeoMutt]], [[Wikipedia:SeaMonkey#Mail|SeaMonkey Mail & Newsgroups]], [[Wikipedia:Sylpheed|Sylpheed]], [[Thunderbird]].

See also: [[Wikipedia:List of Usenet newsreaders]], [[Wikipedia:Comparison of Usenet newsreaders]]

==== Console ====

* {{App|nn|Alternative more user-friendly (curses-based) Usenet newsreader for UNIX.|http://www.nndev.org/|{{AUR|nn}}}}
* {{App|[[Wikipedia:slrn|slrn]]|Text-based news client.|https://www.slrn.org/|{{AUR|slrn}}}}
* {{App|[[Wikipedia:Tin (newsreader)|tin]]|A cross-platform threaded NNTP and spool based UseNet newsreader.|http://tin.org/|{{AUR|tin}}}}
* {{App|trn|A text-based Threaded Usenet newsreader.|https://trn.sourceforge.net/|{{AUR|trn}}}}

==== Graphical ====

* {{App|[[NZBGet]]|Usenet binary downloader for .nzb files with web and CLI interface.|https://nzbget.net/|{{Pkg|nzbget}}}}
* {{App|[[Wikipedia:Pan (newsreader)|Pan]]|GTK Usenet newsreader that's good at both text and binaries.|https://gitlab.gnome.org/GNOME/pan|{{Pkg|pan}}}}
* {{App|[[SABnzbd]]|An open-source binary newsreader webapp written in Python.|https://sabnzbd.org/|{{AUR|sabnzbd}}}}
* {{App|XRN|Usenet newsreader for X Window System.|https://www.mit.edu/people/jik/software/xrn.html|{{AUR|xrn}}}}

=== Microblogging clients ===

* {{App|Choqok|Microblogging client for KDE that supports Mastodon, Pump.io and GNU social.|https://choqok.kde.org/|{{AUR|choqok-git}}}}
* {{App|Dianara|Pump.io client written in Qt.|https://jancoding.wordpress.com/dianara/|{{AUR|dianara}}}}
* {{App|Lemmy-UI|Official web app for lemmy.|https://github.com/LemmyNet/lemmy-ui|{{AUR|lemmy-ui}}}}
* {{App|Liftoff|A mobile and desktop lemmy client written in flutter.|https://github.com/liftoff-app/liftoff|{{AUR|liftoff-bin}}}}
* {{App|Mikutter|Simple, powerful Mastodon client using GTK and Ruby.|https://mikutter.hachune.net/|{{AUR|mikutter}}}}
* {{App|Pumpa|Pump.io client written in C++ and Qt.|https://pumpa.branchable.com/|{{AUR|pumpa-git}}}}
* {{App|Tokodon|Mastodon client for KDE. Part of {{Grp|kde-network}}.|https://apps.kde.org/tokodon/|{{Pkg|tokodon}}}}
* {{App|Toot|CLI and TUI tool for interacting with Mastodon instances.|https://github.com/ihabunek/toot|{{Pkg|toot}}}}
* {{App|Tuba|GTK4 client for Mastodon.|https://apps.gnome.org/Tuba/|{{Pkg|tuba}}}}
* {{App|Whalebird|Mastodon client application. Based on the [https://electronjs.org/ Electron] platform.|https://whalebird.social/|{{AUR|whalebird}}}}

=== Blog engines ===

See also: [[Wikipedia:Blog software]], [[Wikipedia:List of content management systems]]

{{Note|Content managers, social networks, and blog publishers overlap in many functions.}}

* {{App|[[Diaspora]]|A distributed privacy aware social network.|https://diasporafoundation.org|{{AUR|diaspora-mysql}} or {{AUR|diaspora-postgresql}}}}
* {{App|[[Drupal]]|A PHP-based content management platform.|https://www.drupal.org/|{{Pkg|drupal}}}}
* {{App|[[Joomla]]|A php Content Management System (CMS) which enables you to build websites and powerful online applications.|https://www.joomla.org/|{{AUR|joomla}}}}
* {{App|[[Wordpress]]|Blog tool and publishing platform.|https://wordpress.org/|{{Pkg|wordpress}}}}

=== Static site generators ===

* {{App|Hexo|Fast, simple and powerful blog framework.|https://hexo.io/|{{AUR|hexo-cli}}}}
* {{App|Hugo|Hugo is a static HTML and CSS website generator written in Go. It is optimized for speed, ease of use, and configurability.|https://gohugo.io/|{{Pkg|hugo}}}}
* {{App|Jekyll|Static blog engine, written in Ruby, which supports Markdown, textile and other formats.|https://jekyllrb.com/|{{Pkg|jekyll}}}}
* {{App|Nikola|Static site generator written in Python, with incremental rebuilds and multiple markup formats.|https://getnikola.com/|{{Pkg|nikola}}}}
* {{App|Pelican|Static site generator, powered by Python.|https://getpelican.com/|{{Pkg|pelican}}}}
* {{App|Zola|An opinionated static site generator, written in Rust.|https://www.getzola.org/|{{Pkg|zola}}}}

=== Gallery software ===

* {{App|fgallery|A static photo gallery generator with no frills that has a stylish, minimalist look.|https://www.thregr.org/wavexx/software/fgallery/|{{AUR|fgallery}}}}
* {{App|jAlbum|A freeware cross-platform software for managing and creating digital photo albums or galleries.|https://jalbum.net/en/|{{AUR|jalbum}}}}
* {{App|jolly|A tool for statically generating galleries from images.|https://gitlab.com/prior99/jolly|{{AUR|jolly}}}}
* {{App|llgal|An easy and fast on-line gallery generator based on iGal.|http://bgoglin.free.fr/llgal/|{{AUR|llgal}}}}
* {{App|Photoview|A photo gallery for self-hosted personal servers.|https://photoview.github.io/|{{AUR|photoview}}}}
* {{App|Piwigo|A web application to manage your collection of photos, and other medias.|https://piwigo.org/|{{AUR|piwigo}}}}
* {{App|revela|A static web image gallery generator.|https://sr.ht/~yaroslav/revela/|{{AUR|revela}}}}
* {{App|Sigal|A simple static gallery generator.|http://sigal.saimon.org/en/latest/|{{Pkg|sigal}}}}
* {{App|thumbsup|A static web galleries for all your photos and videos.|https://thumbsup.github.io/|{{AUR|nodejs-thumbsup}}}}
* {{App|ZenphotoCMS|A CMS for selfhosted, gallery focused websites.|https://www.zenphoto.org/|{{AUR|zenphoto}}}}

== Remote desktop ==

See also: [[Wikipedia:Remote desktop software]], [[Wikipedia:Comparison of remote desktop software]], [https://remotedesktop.google.com/ Chrome Remote Desktop] (for a web browser-based solution)

=== Remote desktop clients ===

* {{App|[[Wikipedia:AnyDesk|AnyDesk]]|Proprietary remote desktop software.|https://anydesk.com/|{{AUR|anydesk-bin}}}}
* {{App|GNOME Connections|Remote desktop client for GNOME. Supports RDP and VNC. Part of {{Grp|gnome}}.|https://apps.gnome.org/Connections/|{{Pkg|gnome-connections}}}}
* {{App|GVncViewer|Simple VNC Client on Gtk-VNC. Run with {{ic|gvncviewer}}.|https://wiki.gnome.org/Projects/gtk(2d)vnc|{{Pkg|gtk-vnc}}}}
* {{App|[[Wikipedia:KRDC|KRDC]]|Remote Desktop Client for KDE. Supports RDP and VNC. Part of {{Grp|kde-network}}.|https://apps.kde.org/krdc/|{{Pkg|krdc}}}}
* {{App|[[Remmina]]|Remote desktop client written in GTK. Supports RDP, VNC, SPICE, X2Go and SSH.|https://remmina.org/|{{Pkg|remmina}}}}
* {{App|Remote Viewer|Simple remote display client. Supports SPICE and VNC.|https://virt-manager.org/|{{Pkg|virt-viewer}}}}
* {{App|RustDesk|A remote desktop software, open source, written in Rust.|https://rustdesk.com|{{AUR|rustdesk}}}}
* {{App|Sunlogin Remote Control|Proprietary software that supports remote control of mobile devices, Windows, Mac, Linux and other systems. It uses its own proprietary protocol.|https://sunlogin.oray.com/en/about/about{{Dead link|2025|04|05|status=404}}|{{AUR|sunloginclient}}}}
* {{App|[[Wikipedia:TeamViewer|TeamViewer]]|Proprietary remote desktop client. It uses its own proprietary protocol.|https://www.teamviewer.com/|{{AUR|teamviewer}}}}
* {{App|ToDesk|Proprietary remote desktop client that suits for remote teamwork. It uses its own proprietary protocol.|https://www.todesk.com/|{{AUR|todesk-bin}}}}
* {{App|[[Wikipedia:Vinagre|Vinagre]]|Remote desktop viewer for GNOME. Supports RDP, VNC, SPICE and SSH.|https://wiki.gnome.org/Apps/Vinagre|{{AUR|vinagre}}}}
* {{App|[[TigerVNC|vncviewer (TigerVNC)]]|VNC viewer for X.|https://tigervnc.org/|{{Pkg|tigervnc}}}}
* {{App|[[X2Go]] Client|A graphical client (Qt5) for the X2Go system that uses the [[w:NX technology|NX technology]] protocol.|https://wiki.x2go.org/doku.php|{{AUR|x2goclient}}}}
* {{App|xfreerdp|FreeRDP X11 client. Run with {{ic|xfreerdp3}}.|https://www.freerdp.com/|{{Pkg|freerdp}}}}

=== Remote desktop servers ===

* {{App|freerdp-shadow-cli3|A utility for sharing an X display via RDP.|https://www.freerdp.com/|{{Pkg|freerdp}}}}
* {{App|GNOME Remote Desktop|A remote desktop server for GNOME. Supports RDP and VNC. Part of {{Grp|gnome}}.|https://gitlab.gnome.org/GNOME/gnome-remote-desktop|{{Pkg|gnome-remote-desktop}}}}
* {{App|kmsvnc|A VNC server for DRM/KMS capable GNU/Linux devices.|https://github.com/isjerryxiao/kmsvnc|{{AUR|kmsvnc}}}}
* {{App|KRdp|A limited RDP server for KDE.|https://invent.kde.org/plasma/krdp|{{Pkg|krdp}}}}
* {{App|Krfb|VNC server for KDE. Part of {{Grp|kde-network}}.|https://apps.kde.org/krfb/|{{Pkg|krfb}}}}
* {{App|MeshCentral|Device management server for files, terminal access and remote desktop into Linux (X11), macOS and Windows.|https://meshcentral.com/|{{AUR|meshcentral}}}}
* {{App|[[NoMachine]]|Proprietary remote desktop server and client based on [[w:NX technology|NX
technology]].|https://nomachine.com/|{{AUR|nomachine}}}}
* {{App|wayvnc|VNC server for wlroots based wayland compositors (such as {{Pkg|sway}}).|https://github.com/any1/wayvnc|{{Pkg|wayvnc}}}}
* {{App|[[TigerVNC|x0vncserver (TigerVNC)]]|VNC Server for X displays.|https://tigervnc.org/|{{Pkg|tigervnc}}}}
* {{App|[[x11vnc]]|VNC server for real X displays.|http://www.karlrunge.com/x11vnc/|{{Pkg|x11vnc}}}}
* {{App|[[X2Go]] Server|An open source remote desktop software that uses the [[w:NX technology|NX technology]] protocol.|https://wiki.x2go.org/doku.php|{{AUR|x2goserver}}}}
* {{App|[[Xpra]]|A multi-platform screen and application forwarding system.|https://xpra.org/|{{Pkg|xpra}}}}
* {{App|[[Xrdp]]|A daemon that supports RDP. It uses Xvnc, X11rdp or xorgxrdp as a backend.|https://www.xrdp.org/|{{AUR|xrdp}}}}