Manjaro - User contributions [en]

Main Page

2024-05-10T18:08:44Z

Oguzkagan: small change

<center style="background-color:#455A64; border-radius:5px; box-shadow:0 3px 6px rgba(0,0,0,0.04),0 3px 6px rgba(0,0,0,0.0575);">[[File:Block-logo.png|center|100px]]</center>

<languages/>
<translate>
==Getting Started== 
</translate>
<div class="home-grid">
<div id="home-overview" class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Overview</translate></h3>
<div class="home-link-button"><translate> [[Special:MyLanguage/Manjaro|Manjaro Overview]]</translate></div>
<div class="home-card-label"><translate> Various articles to answer all your questions!</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Using Manjaro for Beginners|Using Manjaro]]</translate></div>
<div class="home-card-label"><translate> New to Manjaro? Start here for an overview!</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Using Manjaro for Windows users|Coming From Windows]]</translate></div>
<div class="home-card-label"><translate> Go here if you're a Windows user trying Linux or Manjaro!</translate></div>
</div>
<div id="home-support" class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Online and Support</translate></h3>
<div class="home-link-button"><translate> [[Special:MyLanguage/Manjaro Online|Manjaro Online]]</translate></div>
<div class="home-card-label"><translate> Our forum, Twitter, Reddit, and Facebook accounts.</translate></div>
<div class="home-link-button"><translate> [https://matrix.to/#/#Manjaro:matrix.org Manjaro Matrix Group]</translate></div>
<div class="home-card-label"><translate> Come talk with us on Matrix. If you want support, there is a forum...</translate></div>
</div>

<div id="home-getman" class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Get Manjaro</translate></h3>
<div class="home-link-button"><translate> [[Special:MyLanguage/Download Manjaro|Download Manjaro]]</translate></div>
<div class="home-card-label"><translate> Where to find the latest and greatest Manjaro releases.</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Check a Downloaded ISO Image For Errors|Check a Downloaded ISO Image For Errors]]</translate></div>
<div class="home-card-label"><translate> Check your Manjaro download for errors in Linux and Windows.</translate></div>
</div>

<div id="home-install" class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Installation</translate></h3>
<div class="home-link-button"><translate> [[Special:MyLanguage/Burn an ISO File|Burn an ISO File]]</translate></div>
<div class="home-card-label"><translate> Burn Manjaro to CD/DVD or USB stick in Linux and Windows.</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Installation Guides|Install Manjaro]]</translate></div>
<div class="home-card-label"><translate> Installation and partitioning guides for beginners and experienced users.</translate></div>
</div>

</div>
<translate>
==Customization and Configuration== 
</translate>
<div class="home-grid">
<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Boot / Startup</translate></h3>
<div class="home-link-button"><translate> [[Special:MyLanguage/BIOS and UEFI|BIOS and UEFI]]</translate></div>
<div class="home-card-label"><translate> How to enable virtualisation, run Manjaro on Windows 10 systems, and more!</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Display Managers / Login Screens|Display Managers / Login Screens]]</translate></div>
<div class="home-card-label"><translate> Install, configure, or even bypass MDM, GDM, SDDM, LXDM, and SLiM.</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Fstab - Use SystemD automount|Fstab - Use SystemD automount]]</translate></div>
<div class="home-card-label"><translate> SystemD and /etc/fstab options for device mounting.</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Make GRUB menu & boot-up/down fonts bigger|Larger GRUB, Boot, and Shutdown Fonts]]</translate></div>
<div class="home-card-label"><translate> How to increase the size of boot, shutdown, and GRUB menu fonts.</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> DEs / WMs</translate></h3>
<div class="home-link-button"><translate> [[Special:MyLanguage/Basic Tips for conky|Conky - Basic Tips]]</translate></div>
<div class="home-card-label"><translate> Conky can display a lot of useful information on your desktop.</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Desktop Environments|Desktop Environments and Window Managers]]</translate></div>
<div class="home-card-label"><translate> Install popular desktops and apply a range of desktop-specific configuration.</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Set all Qt app's to use GTK+ font & theme settings|Set all Qt apps to use GTK+ font & theme settings]]</translate></div>
<div class="home-card-label"><translate> Ensure QT apps match GTK+ DE/WM theming.</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Set all Java apps to use GTK+ font & theme settings|Set all Java apps to use GTK+ font & theme settings]]</translate></div>
<div class="home-card-label"><translate> Ensure Java apps match GTK+ DE/WM theming.</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Software Management</translate></h3>
<div class="home-link-button"><translate> [[Repositories and Servers|Repositories and Servers]]</translate></div>
<div class="home-card-label"><translate> Change repositories, find the fastest mirrors, etc.</translate></div>
<div class="home-link-button"><translate> [[Pacman|Pacman]]</translate></div>
<div class="home-card-label"><translate> Instructions for using the '''Pac'''kage '''Man'''ager and more.</translate></div>
<div class="home-link-button"><translate> [[Graphical Software Managers|Graphical Software Managers]]</translate></div>
<div class="home-card-label"><translate> There's a range of user-friendly software managers available.</translate></div>
<div class="home-link-button"><translate> [[Arch User Repository|Arch User Repository]]</translate></div>
<div class="home-card-label"><translate> Learn about and use the AUR.</translate></div>
<div class="home-link-button"><translate> [[Flatpak|Flatpak]]</translate></div>
<div class="home-card-label"><translate> Extend your software library using Flatpaks</translate></div>
<div class="home-link-button"><translate> [[Snap|Snap]]</translate></div>
<div class="home-card-label"><translate> Install and manage Snaps on Manjaro</translate></div>
<div class="home-link-button"><translate> [[Software Applications|Software Applications]]</translate></div>
<div class="home-card-label"><translate> A collection of tips and configurations for many applications.</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Hardware / MSM</translate></h3>
<div class="home-link-button"><translate> [[Manjaro Settings Manager|Manjaro Settings Manager]]</translate></div>
<div class="home-card-label"><translate> MSM can set your Language, User Account, Kernel, Time and Date, Graphics Card Drivers, and more.</translate></div>
<div class="home-link-button"><translate> [[Manjaro Hardware Detection|Manjaro Hardware Detection]]</translate></div>
<div class="home-card-label"><translate> Kernels and Drivers.(mhwd)</translate></div>
<div class="home-link-button"><translate> [[Graphical Software Managers|Graphical Software Managers]]</translate></div>
<div class="home-card-label"><translate> There's a range of user-friendly software managers available.</translate></div>
<div class="home-link-button"><translate> [[Configure Graphics Cards|Configure Graphics Cards]]</translate></div>
<div class="home-card-label"><translate> View, install, remove, or reinstall GPU drivers and much more.</translate></div>
<div class="home-link-button"><translate> [[Power Management|Power Management]]</translate></div>
<div class="home-card-label"><translate> Got the power? No? Then optimise it!</translate></div>
<div class="home-link-button"><translate> [[Printing|Printing]]</translate></div>
<div class="home-card-label"><translate> Enable printing and add printers.</translate></div>
<div class="home-link-button"><translate> [[Wacom Tablet And Pen|Wacom Tablet And Pen]]</translate></div>
<div class="home-card-label"><translate> Configuring tablets and pens.</translate></div>
<div class="home-link-button"><translate> [[Manjaro-ARM|Manjaro-ARM]]</translate></div>
<div class="home-card-label"><translate> Tips specific to ARM systems</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Network / Internet</translate></h3>
<div class="home-link-button"><translate> [[Internet Browsers|Internet Browsers]]</translate></div>
<div class="home-card-label"><translate> Security, Customization, and Configuration.</translate></div>
<div class="home-link-button"><translate> [[Firewalls and Security|Firewalls and Security]]</translate></div>
<div class="home-card-label"><translate> Firewalls and Security on Manjaro</translate></div>
<div class="home-link-button"><translate> [[Sync dynamic IP with openDNS service via ddclient|Sync dynamic IP with openDNS service via ddclient]]</translate></div>
<div class="home-card-label"><translate> Solution for update dynamic IP for openDNS service.</translate></div>
<div class="home-link-button"><translate> [[Keyboard and Mouse Sharing|Keyboard and Mouse Sharing]]</translate></div>
<div class="home-card-label"><translate> Use a mouse and keyboard across multiple machines & operating systems.</translate></div>
<div class="home-link-button"><translate> [[Networking|Networking]]</translate></div>
<div class="home-card-label"><translate> Managing networking</translate></div>
<div class="home-link-button"><translate> [[Using Samba in your File Manager|Using Samba in your File Manager]]</translate></div>
<div class="home-card-label"><translate> How to setup Samba share in your network.</translate></div>
<div class="home-link-button"><translate> [[Sharing files with Python|Sharing files with Python]]</translate></div>
<div class="home-card-label"><translate> Using Python's built-in network capabilities to share files.</translate></div>
<div class="home-link-button"><translate> [[Using autofs (automount) with NFS|Using autofs (automount) with NFS]]</translate></div>
<div class="home-card-label"><translate> One of the many ways to mount shares.</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> System / Misc</translate></h3>
<div class="home-link-button"><translate> [[Manjaro Polkit Rules|Manjaro Polkit Rules]]</translate></div>
<div class="home-card-label"><translate> The policykity rules implemented by Manjaro</translate></div>
<div class="home-link-button"><translate> [[Add a Storage Partition & Modify your System to Suit|Add a Storage Partition & Modify your System to Suit]]</translate></div>
<div class="home-card-label"><translate> How to shrink and add a partition & make Manjaro know where & what it is.</translate></div>
<div class="home-link-button"><translate> [[Aliases in .bashrc|Aliases in .bashrc]]</translate></div>
<div class="home-card-label"><translate> Shortcuts for your terminal.</translate></div>
<div class="home-link-button"><translate> [[Developer Tools|Developer Tools]]</translate></div>
<div class="home-card-label"><translate> Set of tools used by Manjaro developers and advanced users.</translate></div>
<div class="home-link-button"><translate> [[File Systems|File Systems]]</translate></div>
<div class="home-card-label"><translate> Information on different file systems, how they work, and how to use them.</translate></div>
<div class="home-link-button"><translate> [[Swap|Managing Swap]]</translate></div>
<div class="home-card-label"><translate> All about swap space</translate></div>
<div class="home-link-button"><translate> [[Limit the size of .log files & the journal|Management of the Systemd Journal & of .log files]]</translate></div>
<div class="home-card-label"><translate> Manage Systemd's Journal & syslog-ng's /var/log/*log files.</translate></div>
<div class="home-link-button"><translate> [[Linux Security|Linux Security]]</translate></div>
<div class="home-card-label"><translate> Information on root and superuser passwords.</translate></div>
<div class="home-link-button"><translate> [[How to mount Windows (NTFS) filesystem due to hibernation|How to mount Windows (NTFS) filesystem due to hibernation]]</translate></div>
<div class="home-card-label"><translate> Solutions & workarounds for various Windows versions.</translate></div>
<div class="home-link-button"><translate> [[Keyboard_Shortcuts|Keyboard Shortcuts]]</translate></div>
<div class="home-card-label"><translate> Set custom keyboard bindings.</translate></div>
<div class="home-link-button"><translate> [[Viewing and editing configuration files|Viewing and editing configuration files]]</translate></div>
<div class="home-card-label"><translate> How to view and edit files in each Manjaro edition.</translate></div>
</div>
</div>

<translate>
==Troubleshooting== 
</translate>

<div class="home-grid">
<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Boot / Startup</translate></h3>
<div class="home-link-button"><translate> [[Restore the GRUB Bootloader|Restore the GRUB Bootloader]]</translate></div>
<div class="home-card-label"><translate> Can't boot Manjaro? You may be able to repair rather than reinstall!</translate></div>
<div class="home-link-button"><translate> [[Preserve Manjaro Bootloader|Preserve Manjaro Bootloader]]</translate></div>
<div class="home-card-label"><translate> Prevent Manjaro's GRUB from being overridden.</translate></div>
<div class="home-link-button"><translate> [[Kernel Fails to Load (pata_acpi error)|Kernel Fails to Load / "Unable to Find Device" Error]]</translate></div>
<div class="home-card-label"><translate> Solution for a problem that affects certain computers using JMicron chips.</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Desktop</translate></h3>
<div class="home-link-button"><translate> [[Various screen tearing fixes|Various screen tearing fixes]]</translate></div>
<div class="home-card-label"><translate> Hopefully one of these tips will fix your screen tearing problem.</translate></div>
<div class="home-link-button"><translate> [[DMenu - warning: no locale support|DMenu - warning: no locale support]]</translate></div>
<div class="home-card-label"><translate> A fix for the "no locale support" error in dmenu.</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Software Management</translate></h3>
<div class="home-link-button"><translate> [[pacman troubleshooting|Common Issues and Pacman Troubleshooting]]</translate></div>
<div class="home-card-label"><translate> Troubleshooting common issues related to pacman</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Hardware</translate></h3>
<div class="home-link-button"><translate> [[Reactivating the Backlight|Screen Brightness is too Dark or Dim]]</translate></div>
<div class="home-card-label"><translate> The solution for an issue that particularly affects some makes of laptops</translate></div>
<div class="home-link-button"><translate> [[Did X.server recognise your monitor correctly?|Did X.server recognise your monitor correctly?]]</translate></div>
<div class="home-card-label"><translate> A quick test in the Terminal</translate></div>
<div class="home-link-button"><translate> [[ALSA|Advanced Linux Sound Architecture (ALSA)]]</translate></div>
<div class="home-card-label"><translate> Troubleshooting common issues related to ALSA</translate></div>
</div>
</div>

<translate>
==More== 
</translate>
<div class="home-grid">
<div class="home-card home-card-col2 home-card-row3">
<div class="home-link-button"><translate> [//www.mediawiki.org/wiki/Help:Contents User's Guide]</translate></div>
<div class="home-card-label"><translate> Full user guide on every aspect of Wiki authorship and maintenance.</translate></div>
<div class="home-link-button"><translate> [[Basic Submission Rules|Basic Submission Rules]]</translate></div>
<div class="home-card-label"><translate> How to create an account, and the dos and do-nots for Wiki contributors.</translate></div>
<div class="home-link-button"><translate> [[Contributing|Contributing]]</translate></div>
<div class="home-card-label"><translate> The starting point for those willing to contribute to the wiki.</translate></div>
<div class="home-link-button"><translate> [https://wiki.manjaro.org/index.php?title=Category:Contents_Page{{#translation:}} Contents]</translate></div>
<div class="home-card-label"><translate> For a page containing a list of all Wiki guides and tutorials sorted alphabetically</translate></div>
</div>
</div>

[[Category:Top level{{#translation:}}]]

Printing

2023-01-16T18:52:30Z

Oguzkagan: removed dead link

<languages/>
__TOC__

<translate>
= Overview = 


Printing is undertaken through the use of [http://en.wikipedia.org/wiki/CUPS CUPS] (previously an acronym for '''C'''ommon '''U'''nix '''P'''rinting '''S'''ystem). This is a popular open source printing system used in most Linux distributions due to its ease of use.

= Installing the Printer Software = 


First, install the {{ic|manjaro-printer}} package using your favorite package manager or by using the command:
{{UserCmd|command=pamac install manjaro-printer}}


Note that you may need to add yourself to the {{ic|sys}} group. To do this, use the command:
{{UserCmd|command=sudo gpasswd -a your_username sys}}

= Enabling Printing Capabilities = 


Once the necessary software has been installed, to start and enable printing capabilities, enter the following commands:
{{UserCmd|command=sudo systemctl enable --now cups.service}}
{{UserCmd|command=sudo systemctl enable --now cups.socket}}
{{UserCmd|command=sudo systemctl enable --now cups.path}}


If easy detection of network printers is needed (not all editions have avahi installed and running) the following service can be installed & started:


{{UserCmd|command=pamac install avahi}}
{{UserCmd|command=sudo systemctl enable --now avahi-daemon.service}}


At this point you should be ready to configure a printer

=Managing Printers= 

==Managing Printers with HP Device Manager== 
[[File:Hplip.png|left|375px]]


If have a printer made by HP, the easiest way to manage it is with the HP Device Manager({{ic|hp-toolbox}}). It is wizard based and handles automatic detection and setup of your printer locally or across a network.


You can run it by selecting '''HP Device Manager''' from the menu or with the command {{ic|hp-toolbox}}.


<br clear="all" />

==Managing Printers with CUPS== 


Another way to add a printer is to use CUPS directly. Assuming CUPS has been enabled (and started), upon connecting a printer, it should be automatically detected and configured for you to use. The process itself should take only about a minute. However, if the automatic detection and configuration doesn't seem to work, then your printer can be manually set up with relative ease. There are two methods to do so:


* '''Webpage Interface''': CUPS provides an webpage interface that will open in your default web browser to configure your printer. This interface also provides access to further information about CUPS, as well as on-line help.


* '''Desktop Interface''': A standard desktop wizard is also available, which should be instantly familiar to those who have configured a printer before, whether using Linux or another operating system such as windows. Note that you may need to install your DE's printer config package using your favorite package manager or by using one of the following commands.
GNOME:
{{UserCmd|command=pamac install system-config-printer}}
KDE:
{{UserCmd|command=pamac install print-manager}}

===CUPS Webpage Interface=== 


[[File:CUPSweb.png|thumb|left|375px]]


To access the webpage interface, select '''Manage Printing''' from your desktop menu. The interface will automatically open in your default web browser. Alternatively, you can also open your choice of web browser, and enter the following into the address bar:


http://localhost:631/


{{BoxSuccess|Tip|You can also just click the address provided above to access the CUPS web interface!}}
<br clear="all" />

===CUPS Desktop Interface Part 1: The Automatic Method=== 


[[File:CUPS1.png|thumb|left|375px]]


'''1. Add your printer'''. Ensuring that your printer is properly connected and switched on, select '''Print Settings''' from your desktop menu. Once the ''Print Settings'' window has opened, click '''+ add''' to add a new printer.
<br clear="all" />


[[File:CUPS2.png|thumb|left|375px]]


'''2. Select your printer name'''. Once the ''New Printer'' window has opened, under the '''Select Device''' heading, find the name of your printer and click to highlight it. If your printer is listed more than once, check the description on the right to ensure your selection is not for another function, such as scanning or faxing.


'''3. Select your printer connection'''. Under the '''Connection''' heading, click to highlight your printer's connection method. As illustrated, this will usually always be 'USB'.
<br clear="all" />


[[File:CUPS3.png|thumb|left|375px]]


'''4. Install your printer driver'''. Once your printer name and connection have been highlighted, click the '''Forward''' button and CUPS will automatically search for the available drivers for it. In most instances, once the appropriate driver has been found it will be automatically installed, and the set-up process will have completed.


Otherwise, if the process did not succeed, it will be necessary to click the forward button again in order chose the appropriate driver yourself.
<br clear="all" />

===CUPS Desktop Interface Part 2: The Manual Method=== 


[[File:CUPS4.png|thumb|left|375px]]


{{BoxSuccess|Tip|CUPS will usually help you out by showing recommended choices for each step.}}


'''1. Select your printer make'''. If the Automatic method did not automatically find and install an appropriate driver for your printer, then clicking the forward button again will present the ''Chose Driver'' window. The first step is to select the make of your printer. As illustrated, as an HP printer is to be installed, the recommended choice of ''HP'' has been highlighted by clicking on it.


Once your make of printer has been highlighted, click the forward button to proceed to the next step.
<br clear="all" />


[[File:CUPS5.png|thumb|left|375px]]


'''2. Select your printer model'''. Under the left-heading '''models''', select the specific model of your printer. As illustrated, as the printer model to be installed in this instance is a Model 2210, the recommended choice of ''PSC 2210'' has been highlighted by clicking on it.


'''3. Select your printer driver'''. At last! Under the right-heading '''Drivers''', select the appropriate driver for your printer. As illustrated, the recommended printer driver has been clicked to highlight it. '''It is advised that you also select whatever driver is recommended for you'''.


Once your printer model and driver have been highlighted, click the forward button to proceed to the next step.
<br clear="all" />


[[File:CUPS6.png|thumb|left|375px]]


'''4. Choose your printer name, description (optional), and location (optional)'''. Unless you want to change something, it will not be necessary to make any amendments here.


If you are happy with the information provided - or have made the desired changes - click the '''Apply''' button to complete the process.
<br clear="all" />


[[File:CUPS7.png|thumb|left|375px]]


'''5. Configure your printer'''. Having clicked the Apply button in the previous step, your printer's properties will be displayed. By selecting the categories on the right-hand side, you can view information and amend your printer's settings if you wish. '''The standard settings will be fine for most people, so unless you have something specific in mind, there will be nothing you need to do'''.


'''6. Test your printer'''. Although optional, this step is highly recommended! Click the '''Print Test Page''' button to ensure that your printer is set up and working properly.


{{BoxSuccess|Tip|Your printer properties can be accessed - and changed - at any time by selecting the '''Print Settings''' option from your menu, and then double-clicking your printer's icon.}}


That's it! Now click the '''OK''' button to close the window and start using your printer.
<br clear="all" />

===Modifying an Installed Printer=== 


To configure an installed printer at any time:


'''1.''' select the '''Print Settings''' option from your desktop menu, and


'''2.''' double-click the printer's icon.


The configuration window will appear. Select any of the categories on the left-hand side of the window to view the appropriate information and make any desired changes. Once complete, click the '''Apply''' and then '''OK''' buttons to confirm and save your changes, or click the '''Cancel''' button to close the window without making any changes.

===Removing an Installed Printer=== 


If for any reason you wish to remove a printer (e.g. to reinstall it), select the '''Print Settings''' option from your menu, right-click your printer's icon, and then select '''delete'''. You will need to confirm your decision to delete the printer, as well as enter your password to complete the task.

= Disabling Printing Capabilities = 


If for any reason you wish to disable CUPS (e.g. in order to use an alternative printing system), open your terminal and enter the following command:
{{UserCmd|command=sudo systemctl disable --now cups.service}}
{{UserCmd|command=sudo systemctl disable --now cups.socket}}
{{UserCmd|command=sudo systemctl disable --now cups.path}}

= Specific printers/scanners that are known to work = 


{| class="wikitable"
|-
! Brand !! Type !! Print !! Scan !! Description how to set up !! Issues & Solutions !! More info !!
|-
| Canon || mp 280 || Yes, via network|| Yes, only local || CUPS and manjaro-printer || Remote scanning
|-
| Canon || Pixma MX535 || Yes, via network|| Yes, via network || Manjaro printer detects remote printer as mx530. scanner needs scangearmp2-sane-git to function properly || Needs avahi and in my case ipv6 for some reason to be able to 'see' the printer (@hanzel on the forum)
|-
| Canon || PIXMA TR4522 || || || Needs: cnijfilter2 or cnijfilter2-bin from the [[Arch_User_Repository|AUR]] || || [https://forum.manjaro.org/t/installing-a-canon-pixma-tr4522/78221 forum post]
|-
| Canon || PIXMA TS5120 || Yes|| Yes || Scanner seems to work after CUPS and manjaro-printer, printing requires cnijfilter and selecting Canon TS5100 series drivers|| Needs: cnijfilter2 or cnijfilter2-bin from the [[Arch_User_Repository|AUR]] || ||
|-
| Epson|| WF-3825 driver || || || Needs: epson-inkjet-printer-escpr2 [[Arch_User_Repository|AUR]] || || [https://forum.manjaro.org/t/epson-wf-3825-driver/77910/5 Forum post]
|-
| Canon || Pixma Pro-100 || Yes, via network and local || Not a feature || manjaro-printer || Takes a moment to start printing, just be patient
|-
| Canon || ISensys || LBP223dw || Yes || || || [https://forum.manjaro.org/t/installation-canon-i-sensys-lbp223dw/80306 forum post]
|-
| Canon || Pixma E4270 || Yes via Network || not tested || Needs: cnijfilter2 or cnijfilter2-bin from the [[Arch_User_Repository|AUR]] || || [https://forum.manjaro.org/t/canon-pixma-e4270/86212 forum post]
|-
| Canon || Pixma G2100 || Yes || Yes || Plug& play || || [https://forum.manjaro.org/t/does-canon-printers-well-supported/87040/5 forum post]
|-
| Epson || ET-M1120 || Yes, via Network || Not a feature || manjaro-printer and system-config-printer || Needs: epson-inkjet-printer-escpr and epson-inkjet-printer-escpr2 in [[Arch_User_Repository|AUR]] and then patch from pacman


|}


Table made from suggestion [https://forum.manjaro.org/t/printer-overview-and-functionality-on-manjaro/79794 here]

</translate>

[[Category:Contents Page{{#translation:}}]]

Add a Storage Partition & Modify your System to Suit

2023-01-16T18:40:20Z

Oguzkagan: removed dead link

<languages/>
__TOC__
<translate>
==Introduction== 
My storage system was OK when I initially devised it, as it happens, the years have gone by & it had become inefficient & a bit messy. So, time for a makeover. So I spent some hours reorganizing my partitions - 11 -> 12 hours of GParted work. During this time I removed the /swap partition; enlarged my '''/''' partition, it still had ~2GB of free space which should have been fine for the way I use my system.


A '''/swapfile''' [[https://wiki.manjaro.org/index.php/Swap#Using_a_Swapfile]] is to replace the /swap partition (see the previous link for the simple how-to on how to create a /swapfile). My /swapfile was located in the '''/''' partition.


I also shrunk my /home partition as near as small as I could with the size of the data it was holding, so that I could then create a new partition where that data will reside in future.


I had to create a new partition, then reboot into Manjaro, where I moved all of my personal storage data over to the new partition. Then reboot the '''GParted live CD''' & shrink my /home down to 20GB, which is far larger than it needs to be in my new layout, but I have the disk space to spare, so why not? (I could always change it with GParted in the future if I had to.)


My system then needed to be configured to work with these changes as I will go into below.

===The new partition layout=== 
/boot - 102MB ext2 (half full)
/ - 20GB ext4 (carries the 4GB /swapfile & still has 5GB free)
/home - 20GB ext4 (12GB free)
/bdata - 892GB ext4

==Manipulating the Partitions== 
{{BoxDanger|Working with partitions|Modifying an existing partition table may cause loss of data. '''Always''' ensure adequate backup to external storage}}
Boot Manjaro from a live ISO and use Gparted to delete /swap & to modify the size of all (bar /boot) of the partitions on the 1TB (931.51GB formatted) drive. I had to, delete, shrink, move, expand, create (reboot & move my personal data across from /home to the new /bdata , then reboot GParted) shrink, expand.


As previously mentioned, this took 11 -> 12 hours. The larger the partition & the more data involved the longer it takes to process a partition.

==Modifying the system to suit these changes== 
I had to comment out the call for mounting the /swap partition in /etc/fstab , change the path buttons in Worker (I'm probably the only one reading this that uses the wonderful Worker, so, for all that statement is worth...) to suit the new partition layout. For anyone doing the same thing you need to think about anything that you may have done that needs to be reconfigured to use these new paths (more on this later).


Then in the Terminal I used the blkid command to get the UUID of the new /bdata partition so I could add a call to it into the /etc/fstab :


[handy@jarmano ~]$ blkid
/dev/sda1: UUID="41c2c2b3-5ad8-43bc-9bf0-84d3b429127d" TYPE="ext2"
/dev/sda2: LABEL="big.data" UUID="9fe95af9-529e-4f68-b83c-7fa9e7fb3ba1" TYPE="ext4"
/dev/sda3: LABEL="my.system" UUID="6dfe5e6b-86b9-4301-b385-8cc3816ada8c" TYPE="ext4"
/dev/sda4: LABEL="my.home" UUID="b993339d-dbb3-4fbd-adb4-e61baf43cd7f" TYPE="ext4"
/dev/sdb1: LABEL="store" UUID="05e6f212-4003-430b-a7d9-a53d98fad0b5" TYPE="ext4" PARTUUID="8cb60e1f-8d16-4d9c-bccc-3a2cd5396836"


As you may have noticed, the new partition was given the /dev/sda2: spot (which once belonged to /swap)


I Copied the UUID for the new partition into /etc/fstab & created a call for this new partition, like so:
{{File|file=/etc/fstab|content=<pre>...
UUID=9fe95af9-529e-4f68-b83c-7fa9e7fb3ba1 /data/bdata ext4 defaults 0 1
...
</pre>}}


Then as root I made the directory /mnt/bdata , so that the new partition is accessible. You can do this in the Terminal like so (replace <directory.name> with the name you want to call your new partition:
{{RootCmd|command=mkdir -p /data<directory.name>}}


Due to GParted doing its work with root permissions we need to change the ownership (owner:group) of the new partition, which we do by modifying the ownership of the directory name (that was created in the last command above) from root:root to <user.name>:users. To do that use the following Terminal command:
{{RootCmd|command=chown <user.name>:users /data/<new.partition's.name>}}

==Configure the system to use new default storage directories== 


Firstly, I had to check both the ~/.bash_profile & the /etc/profile files & modify the '''PATH''' variables where I had added paths that were now incorrect. Most users here won't have changed anything in these two files, though it is just too easy to do, to not check them for safeties sake. When looking at these files, check the PATH line for anything that relates to your moved storage directories. You probably won't have any differences unless you added them. These lines in my files follow, you will see where I have replaced the original paths with /mnt/bdata :


{{File|
file=~/.bash_profile|
content=<pre>PATH=$PATH:/mnt/bdata/scripts
export PATH
PATH=$PATH:~/games/ut2004
export PATH
PATH=$PATH:~/games/ut2004/System
export PATH</pre>}}


{{File|
file=/etc/profile|
content=<pre># Set our default path
PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/mnt/bdata/scripts:"
export PATH</pre>}}


Then I needed to change the paths for what are considered to be the standard default /home/<user>/ storage directories - Downloads, Video, Music & so on. I had previously changed these paths, also, I don't want to use capital letters in the beginning of their names.


If you have more than one user account on your system, then it would be best to use & edit:
{{UserCmd|command=nano ~/.config/user-dirs.conf}}


If the above file doesn't exist, create it. Then copy mine (just below), editing it to suit your system/desires. Having only one user account on my Manjaro setup, I delete the previously mentioned file (if it existed anyway) & modify:


{{RootCmd|command=nano /etc/xdg/user-dirs.defaults}}


As its settings, under these circumstances (not having a ~/.config/user-dirs.conf ) will be global. Mine edited file follows:


{{File|
file=~/.config/user-dirs.conf|
content=<pre># Default settings for user directories customised by handy :->
#
# The values are relative pathnames from the home directory and
# will be translated on a per-path-element basis into the users locale
DESKTOP=desktop
DOWNLOAD=/data/bdata/downloads
DOCUMENTS=/data/bdata/documents
MUSIC=/data/bdata/music
PICTURES=/data/bdata/pictures
VIDEOS=/data/bdata/videos</pre>
}}


Once you have done this, check that you don't have new (likely empty) default directories in your ~/ that were created by the above file(s) on boot. Any such void files should be deleted after you have modified either the ''user'' based '''~/.config/user-dirs.conf''' or the ''root'' based '''/etc/xdg/user-dirs.defaults''' files. '''~/.bashrc''' may need some paths changed as well, depending on what you call from it.


I also had to tell qBittorent, Firefox (& the few other browsers I'm testing) where their particular download directories had moved to. Any other applications that were set to save data into the documents, or any other directory that has moved (or been created as a default, in either of the two directories above) will need to have their config's modified too. & so it goes...

==Creating a /swapfile== 
Now, if you do choose to not have a /swap partition but you would still like to have swap space (which of course you can choose to easily have at any time in the future), then there is a very functional option available to you called a /swapfile.
</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:Storage{{#translation:}}]]

Using autofs (automount) with NFS

2023-01-16T18:40:01Z

Oguzkagan: removed dead link

<languages/>
__TOC__
<translate>
=Autofs – Automount (en)= 


[[File:Manjaro-logo.png|left]]


<br clear="all"/>

=Autofs= 
Autofs is a program which makes it possible to mount external devices on demand. Other ways of mounting can be done with the use of a manual command for a temporary mount, or by using the /etc/fstab file if you want to mount a device permanently.


Autofs can be used to mount:
*USB-flash-disks
*external hard disks
*network attached storage devices
*CD-ROM / DVD / BlueRay and so on.


Autofs mounts these devices in local folders. When you want, or a program you use wants, to read from or write to the device, autofs will do that in those local folders.
When you work a lot with mounted systems you will love the way this is done.


Some people believe that since autofs is not maintained heavily it won’t exist much longer, but think about this: why do you need to maintain a program which already does what it is supposed to do?


Another way of mounting on the fly is described on this wiki page: Fstab - Use SystemD automount [https://wiki.manjaro.org/index.php?title=Fstab_-_Use_SystemD_automount]

=Installation= 
At the time of writing, the autofs version number was 5.1.3-1. It can be installed from the standard Manjaro repositories using Octopi, Pamac or Pacman.
When you want to use autofs with nfs you need one extra package and that is nfs-utils. So, install that as well. The description calls it:
''support programs for the network filesystem''

=Testing the mounts= 
Before you will install and setup autofs it is a good thing to test if you can mount the device you want to mount.


Let’s find out first what you can mount. The nfs-utils package has a nice command for that: showmount:


'''showmount -e 192.168.1.9'''


When the device is on the output will be something like:


'''Export list for 192.168.1.9:'''
'''/HDD1 *'''


There is a disk called HDD1 in the device on address 192.168.1.9.


Remark: ''You do need to know the IP-address of the device to use showmount.''


Now let’s mount it to our local folder /mnt:


‘’’sudo mount -t nfs 192.168.1.9:/HDD1 /mnt’’’


Type ‘ls /mnt’ to find out what is on the disk you just mounted.
When you see contents the mount has succeeded and we can now continue with the configuration of autofs.

=Terminal commands= 
Commands you can use are:


'''sudo systemctl enable autofs''' ''Command to enable autofs so it can be started either manually or at next boot''


'''sudo systemctl start autofs''' ''Command to manually start autofs''


'''sudo systemctl restart autofs''' ''Command to manually restart autofs''


'''sudo systemctl stop autofs''' ''Command to manually stop autofs''


'''sudo systemctl status autofs''' ''Command to read the status of autofs''


When autofs is running this is the output of the status command:


'''sudo systemctl status autofs'''
● autofs.service - Automounts filesystems on demand
Loaded: loaded (/usr/lib/systemd/system/autofs.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2017-12-02 07:13:22 CET; 1h 9min ago
Process: 1069 ExecStart=/usr/bin/automount $OPTIONS --pid-file /run/autofs.pid (code=exited, status=0/SUCCESS)
Main PID: 1089 (automount)
Tasks: 5 (limit: 4915)
CGroup: /system.slice/autofs.service
└─1089 /usr/bin/automount --pid-file /run/autofs.pid
Dec 02 07:13:22 Desktop-Jan systemd[1]: Starting Automounts filesystems on demand...
Dec 02 07:13:22 Desktop-Jan automount[1089]: -
Dec 02 07:13:22 Desktop-Jan systemd[1]: Started Automounts filesystems on demand.


After a stop it looks like this:


'''sudo systemctl status autofs'''
● autofs.service - Automounts filesystems on demand
Loaded: loaded (/usr/lib/systemd/system/autofs.service; enabled; vendor preset: disabled)
Active: inactive (dead) since Sat 2017-12-02 08:27:27 CET; 1s ago
Process: 1069 ExecStart=/usr/bin/automount $OPTIONS --pid-file /run/autofs.pid (code=exited, status=0/SUCCESS)
Main PID: 1089 (code=exited, status=0/SUCCESS)
Dec 02 07:13:22 Desktop-Jan systemd[1]: Starting Automounts filesystems on demand...
Dec 02 07:13:22 Desktop-Jan automount[1089]: -
Dec 02 07:13:22 Desktop-Jan systemd[1]: Started Automounts filesystems on demand.
Dec 02 08:27:26 Desktop-Jan systemd[1]: Stopping Automounts filesystems on demand...
Dec 02 08:27:27 Desktop-Jan systemd[1]: Stopped Automounts filesystems on demand.

=Configuration= 
After installation we need to configure a few files specific to what we need and want. These files are placed in the folder: '''/etc/autofs'''.
In fact there are 2 files needed: auto.master and auto.<any name you like>.
Since /etc/autofs is a folder owned by root you need root privileges to write and/or edit them.


In auto.master we write:
* the base folder where mounts are connected to the local filesystem
* the name of the file in which the mount can be configured
* a timeout value (time after which the mount is automatically unmounted when not needed anymore)
* ghost, an option which places empty folders in the base folder to make it possible, after the time-out, to mount the device again.


A typical line in the auto.master file can look like this:


'''/mnt /etc/autofs/auto.NAS1 --timeout=10 --ghost'''


When you have more than one external device you want to mount using autofs you can do 2 things:


* write an extra line in the auto.master file for each device. For example:


'''/mnt /etc/autofs/auto.NAS1 --timeout=10 --ghost'''


'''/mnt /etc/autofs/auto.NAS2 --timeout=10 --ghost'''


and create extra config files for each device, or


* use 1 line in the auto.master file using 1 config file for all devices and write more than 1 line in this config file. This is totally up to you.


I use this:


''/etc/autofs/auto.master:''


'''/mnt /etc/autofs/auto.shares --time-out=5 --ghost'''


''/etc/autofs/auto.shares:''


'''NAS-Seagate -fstype=nfs,rw,soft,retry=0 Seagate:/shares/Folder1'''


'''NAS-WD -fstype=nfs,rw,soft,retry=0 WD:/nfs/Public'''


This way I have one master file which, with one line, controls the base of the system and one file which controls all my shares. But again, this is totally up to you.

=Explanation of auto.master= 
This file is created when you install the autofs package. You will need to edit it to make it work for you. The complete file looks like this when created:


# key [ -mount-options-separated-by-comma ] location
# For details of the format look at autofs(5).
#
#/misc /etc/auto.misc
#
# NOTE: mounts done from a hosts map will be mounted with the
# "nosuid" and "nodev" options unless the "suid" and "dev"
# options are explicitly given.
#
#/net -hosts
#
# Include central master map if it can be found using
# nsswitch sources.
#
# Note that if there are entries for /net or /misc (as
# above) in the included master map any keys that are the
# same will not be seen as the first read key seen takes
# precedence.
#
#/net -hosts -nosuid
+auto.master


Add your line or lines just before the last visible line: +auto.master


After that line an empty line should exist or the configuration will not succeed, so place the cursor after +auto.master and click on ENTER.


Format of the line you add:


''base-folder name_of_share_file options''.


In my example this is:


'''/mnt /etc/autofs/auto.shares --time-out=5 --ghost'''


'''''NOTE: Make sure the used filename in the auto.master file should be exactly the same as the name of the file you use, including the path.'''''


The base folder can be /. In this case it is written as: /-
You use direct addressing now. The address you write in the shares file (see next paragraph) becomes the complete address.
When you write the name of a folder in the master file you use indirect addressing:
the complete path is now the sum of the path in the master file + the one in the shares file.

=Explanation of auto.shares= 
This file can have any extention name you like. Make it a descriptive one to easily find it, especially when you use more than one.
The line or lines in this file are all built according to this template:


''name_of_sub-folder options source''


(separated with at least one space)


After mounting the external device can be found in the following directory structure:


'''/base-folder/sub-folder'''


You define the base folder in the auto.master file (first item in the line) and the sub-folder is defined in the auto.xxxx file (also first item on the line)


My shares are mounted at: /mnt/NAS-WD and /mnt/NAS-Seagate.


/mnt is the base-folder (from auto.master) and both NAS folders are written in the shares file.


Options you can use are plenty. See the man pages for autofs, automount and nfs.
The ones I used here work for me. They take care of the following:


*'''-fstype=nfs'''
The used filesystem is nfs (Network File System), a file-system used much in Linux environments.


*'''rw'''
The mount is readable and writable. If you only need read access then use ro (read only)


*'''soft'''
If the server fails an I/O error is given, but the file-manager keeps running. When you use hard instead of soft, it hangs till the connection has been re-established.


*'''retry=0'''
This makes sure that mount stops immediately when the server is not reachable. If not, mount will keep trying for 2 minutes to reach the server and block the program which wants to reach the server.

=Remarks= 


* It is said that when you make a change in the shares file, the change will be active straight away. When changing the master file you need to restart the autofs.service like this:


'''sudo systemctl restart autofs''' ''It is advisable to also restart after changing the shares file, just to be sure.''


* The permissions of both the master and the share file(s) should be 644. That means Read/Write permission for user, Read for group and Read for others.


* Test if the system works. First example is the result when nothing is mounted, in the second example you see the result when the NAS-WD is mounted:


$ /etc/autofs > '''sudo ps -A|grep "nfs\|rpc"'''


240 ? 00:00:00 rpcbind
23222 ? 00:00:00 rpciod
23227 ? 00:00:00 nfsiod

$ /etc/autofs > '''cd /mnt/NAS-WD''' ''Change directory to the mount''


$ /mnt/NAS-WD > '''sudo ps -A|grep "nfs\|rpc"'''


240 ? 00:00:00 rpcbind
23222 ? 00:00:00 rpciod
23227 ? 00:00:00 nfsiod
29106 ? 00:00:00 rpc.statd


There are many webpages about autofs, with and without nfs. Just google it and you will find many different ways of setting it up. The way described here works for me and is pretty easy to setup.
</translate>

[[Category:Contents Page{{#translation:}}]]

Did X.server recognise your monitor correctly?

2023-01-16T18:37:17Z

Oguzkagan: removed dead link

<languages/>
__TOC__
<translate>
= A Quick Test to Validate these X.server Settings:= 


It is certainly worthwhile checking that the X.server has recognised your monitor correctly. If the X.server can't recognise your monitor or incorrectly recognises your monitor your display will not be optimal.

==The Test:== 


Enter the following command in the Terminal:


{{UserCmd|command=xdpyinfo | grep -B2 resolution}}


These are the results from my machine; fortunately they are correct:


{{UserCmdOutput|command=xdpyinfo | grep -B2 resolution|result=
<pre>
screen #0:
dimensions: 1920x1200 pixels (524x321 millimeters)
resolution: 93x95 dots per inch
</pre>
}}


'''Note:''' If you are running more than one monitor, this test will most likely provide results that are created by combining the monitors that you have connected to your machine & treating them as though they are one monitor!


So you may need to do some arithmetic, OR, of course you could just connect one monitor at a time for the test. ;)


<br clear="all"/>

==What if the X.server got it wrong?== 


If the X.server can't work out what your screen size is it will set your DPI at the default of 75 x 75. If so, you will need to manually create a file like so:


{{UserCmd|command=touch /etc/X11/xorg.conf.d/90-monitor.conf}}


to which you must add the pertinent details ''(see below)''.

==Getting Your Monitor's Specifications:== 


Probably the easiest way to get the required details is from the technical specifications supplied in the monitor's manual.


If you don't have the manual, you can search for the specifications of your monitor online; most maker's have a section on their sites for archived manuals.


There are also other sites out there that carry such information.

==What do I do with the Specifications:== 


Enter the following into the Terminal to call your favourite text editor as root & create an initially empty file with the right path & name:


{{UserCmd|command=sudo <text.editor.name> /etc/X11/xorg.conf.d/90-monitor.conf}}


Then copy the following into your editor's blank page:


'''/etc/X11/xorg.conf.d/90-monitor.conf'''


Section "Monitor"
Identifier "Monitor0"
DisplaySize 286 179 # In millimeters
EndSection


You '''MUST''' replace the '''DisplaySize''' numbers with the ones for your monitor.


After you have done that, save the file & reboot. The next time X starts the X.server will have calculated your DPI values from the numbers that you put in the '''DisplaySize''' line above.


To test that the X.server has done what it has supposed to do & also that there were no typo's, run the test from the start of this wiki again.

==What if I can't find the Manufacturer's Specifations?== 


You can measure your monitor & input the numbers that way, though your measurements will most likely be different than manufacturer's.


If you can't find the manufacturer's specifications on the web, have a look at this page as you still have options available to you: [https://wiki.archlinux.org/index.php/Xorg#Display_Size_and_DPI]

</translate>

[[Category:Contents Page{{#translation:}}]]

Preserve Manjaro Bootloader

2023-01-16T18:36:48Z

Oguzkagan: removed dead link

<languages/>
__TOC__

<translate>
= Introduction = 
This is not to get back or to restore your Manjaro bootloader. To restore your Manjaro bootloader, see [https://wiki.manjaro.org/index.php?title=Restore_the_GRUB_Bootloader this].


This is to prevent your working Manjaro bootloader being overridden by other OS bootloaders. This can happen when the other OS updates its grub (not update-grub). And due to Manjaro's implementation of intel-ucode, other OS bootloader cannot boot Manjaro OS, hence this tutorial.

= Bios-legacy systems = 
Boot up all other linux OS and at their terminals, do


{{UserCmd|command=sudo grub-install --force /dev/sdxy}}


where /dev/sdxy is the other OS partition. Note some OS's need command 'grub2-install'.


When installing a new linux OS, at their installer, always select "installing bootloader to partition". We can also choose not to install bootloader, but selecting 'to partition' (Manjaro calls this 'to system') is good enough and is preferable to have a bootloader installed at every OS.


If you choose to uninstall Manjaro later on, remember to make the other OS bootloader as default before uninstalling.

= UEFI systems = 
At any linux OS terminal, see output of


{{UserCmd|command=efibootmgr}}


It will give an output like this:
{{UserCmdOutput|command=efibootmgr|result=
<pre>
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0002,0004,0005,0008
Boot0001* manjaro
Boot0002* ubuntu
Boot0004* UEFI: WDC WD10PURX
Boot0005* Hard Drive
Boot0008* Systemd Boot Manager
</pre>
}}


Make sure Manjaro bootorder is at the beginning as above: "BootOrder: 0001,0002,0004,0005,0008"
If it is not, reorder such that it is, like this:


{{UserCmd|command=sudo efibootmgr -o 0001,0002,0004,0005,0008}}


Whenever we install another OS, it will be at the top of that bootorder; and we will need to reorder such that Manjaro is again at the top. And we can do that at that install livecd media itself. If we forget, we can do it after installation at any OS. For UEFI, we can still select Manjaro to boot at boot-setup (one of F8 ~ F12).


That alone should be sufficient for most UEFI systems.
However in some situations (and reported in some topics here), it is not (possibly due to firmware issues). The above steps do not ensure that Manjaro bootorder will be booted up. In these cases, one extra command is required.


{{UserCmd|command=sudo cp /boot/grub/x86_64-efi/core.efi /boot/efi/EFI/boot/bootx64.efi}}


Or, if done at livecd (or another OS) and mounted / partition to /mnt and /boot/efi partition to /mnt/boot/efi


{{UserCmd|command=sudo cp /mnt/boot/grub/x86_64-efi/core.efi /mnt/boot/efi/EFI/boot/bootx64.efi}}


Copying /boot/efi/EFI/Manjaro/grubx64.efi instead of /boot/grub/x86_64-efi/core.efi can also accomplish the same thing because /boot/efi/EFI/Manjaro/grubx64.efi is itself a copy of /boot/grub/x86_64-efi/core.efi


So doing this is also an alternative.


{{UserCmd|command=sudo cp /boot/efi/EFI/Manjaro/grubx64.efi /boot/efi/EFI/boot/bootx64.efi}}


Doing this extra command where the extra command is not needed does not seem to harm the system.

= A fallback alternative = 
(Both bios-legacy and uefi)


We can despite our efforts, still use the other OS grub to boot Manjaro, and might come in useful, particularly if the above methods seems daunting. Or if we are stuck not being able to get to Manjaro bootloader.


At the other OS grub 2 system, create a custom.cfg file


{{UserCmd|command=sudo touch /boot/grub/custom.cfg}}


Some OS's like Suse, Fedora, Mageia uses directory in /boot/grub2 not /boot/grub, so do so accordingly.
Then add the following in the newly created custom.cfg. No need to update-grub or change /etc/default/grub and will stand (persist) grub-installs or update-grubs. And of course persists to any new Manjaro kernel. Note this entry/entries will not be shown in their grub.cfg.


{{File|file=/boot/grub/custom.cfg|content=
<pre>
menuentry "Manjaro - configfile " {
insmod part_gpt
part part_msdos
insmod ext2
search --no-floppy --fs-uuid --set=root xxxxxxxxxxxxxxxxxxxxxxxx
configfile /boot/grub/grub.cfg
}
</pre>
}}


btrfs will need additional tweeks (rootflag=subvolume=@)
</translate>

[[Category:Contents Page{{#translation:}}]]

Limit the size of .log files & the journal

2023-01-16T18:36:19Z

Oguzkagan: removed dead link

<languages/>
__TOC__
<translate>
= Introduction = 


Note: 18-Feb-17: Updated the Journal section
& created a Support page in the forum.
12-Feb-14: Improved Journal section.
24-Mar-14: Tidied content of page &
added content to the next section.


Log files & the systemd journal do the same thing in different ways. They keep a record of everything that happens on your computer system. This makes it possible to understand what is going right & what is going wrong. As an example, if your system had been infiltrated by an ssh attack, this could be verified in the log/journal. So these log files are good for more than tracking troublesome hardware, or driver problems, badly written network manager code or the plethora of other problems that the complex & dynamic GNU/Linux system has to deal with.


These logs are an absolute blessing, as not all systems have them, & those server administrators who do have them sould be very grateful, as they can be the bread & butter of what they do.


Generally, only server administrators have use for logs that go back any length of time. Few users who run distros on their desktop, notebook, netbook and such machines, have need to keep such huge log files or histories going back for many months or even years on their system. They are a waste of space & also makes viewing your log files more cumbersome.


<br clear="all"/>

==== The first topic on this page will briefly cover the '''systemd journal''' ==== 


The systemd journal has taken the place of log files though it will happily run in parallel with the standard type log files. These are still created & maintained by default in Arch & Manjaro. If you delete syslog-ng & all of the /var/log/*log files on reboot you will find that some log files will be automatically created again. On my machine after having deleted syslog-ng & all of the /var/log/*.log files (except for the Xorg.0.log files), my machine now has the following (wtmp & btmp are created on boot by the /etc/logrotate.conf file) contents in my /var/log/ :


journal/
squid/
Xorg.0.log
Xorg.0.log.old
btmp
faillog
lastlog
pacman.log
wtmp


<br clear="all"/>

==== The second topic will cover handling log files ==== 


This topic will go into far more depth, covering the use of the '''logrotate''' command, '''logrotate.conf''', the '''/etc/cron.daily cron.weekly cron.monthly cron.yearly''', and some ways to run created scripts, plus a mention of the '''crontab''' method of running a script also. I'll try to make this section accessible to as many people as possible, which means this will be a long page.


<br clear="all"/>

= The journal & the logs duplicate the same information = 


You can read the text of the log files in a text editor, or using the '''cat''', '''more''', '''less''' & such commands as you would on any other text file. The journal on the other hand requires the '''journalctl''' command to be able to access its contents. The following is a good way to read the journal:


sudo journalctl


<br clear="all"/>

=Read this its important= 


Note: '''etc/systemd/journald.conf.d/*.conf'''
overrides the file '''journald.conf'''


'''man journald.conf'''


When packages need to customize the configuration, they can install configuration snippets in
/usr/lib/systemd/*.conf.d/. Files in /etc/ are reserved for the local administrator, who may use
this logic to override the configuration files installed by vendor packages. The main configuration
file is read before any of the configuration directories, and has the lowest precedence; entries in
a file in any configuration directory override entries in the single configuration file. Files in
the *.conf.d/ configuration subdirectories are sorted by their filename in lexicographic order,
regardless of which of the subdirectories they reside in. If multiple files specify the same option,
the entry in the file with the lexicographically latest name takes precedence. It is recommended to
prefix all filenames in those subdirectories with a two-digit number and a dash, to simplify the
ordering of the files.


What that means is that you can create configuration files '''.conf''' in the '''/etc/systemd/journald.conf.d/''' directory, with suitable names of your choice. The content of these files take precedence over any other settings or configurations in systemd. Please bear that in mind when you read the following? In my cumbersome way I've tried to make it all too obvious...


<br clear="all"/>

== How to set a maximum size limit for the journal == 


There is usually no need to interfere with the maximum size of the journal, as it has been built to monitor the amount of free space on the partition where it exists & will shrink itself by deleting the oldest entries when a shortage of space demands it.


Use your favorite text editor with root privileges, (starting it with '''sudo''' will do the job).


Note: the name '''size'''.conf is user created.


With your text editor create a file called '''size.conf''' in the following location '''/etc/systemd/journald.conf.d/size.conf''' The following sets the maximum file size to a 50 MB limit for the '''/var/log/journal''' . ''(The SystemMaxUse=250M is for use with logrotate, which is looked at in the 2nd section of this page. Talk to papajoke on the forum if you need help with logrotate & systemd.)''


[Journal]
SystemMaxUse=250M
SystemMaxFileSize=50M


You can also limit the content of the journal by specifying the level of the data to be added to the journal. This is done by creating & editing the file '''/etc/systemd/journald.conf.d/level.conf'''


Note: the name '''level'''.conf is user created.


[Journal]
# not save all levels but only 0 to 4
MaxLevelStore=warning


<br clear="all"/>

=The Journalctl command - a quick reference [http://www.freedesktop.org/software/systemd/man/journalctl.html]= 


Note: Following are few pointers on things
you can do to make using journalctl quicker,
easier & more effective, on your system.

==You don't have to use "sudo" with journalctl== 


Add your '''user''' to '''adm''' group. This gives your <user> full use of the '''journalctl''' command. No more need to use sudo.
Swap "handy" for your username in the following:

# usermod -a -G adm handy

==See the whole line of the journalctl output text== 


You can pipe the output of journalctl to a file or to a text display tool like "More" or "Less", as follows:

$ journalctl -b -p err|less

Doing so, gives you a means of avoiding the truncation of output which some system displays configurations may experience.

===Use a ~/.bashrc alias to make this easy=== 


I use the following ~/.bashrc alias:

alias errors="journalctl -b -p err|less"

On entering '''errors''' in the Terminal, all errors or worse since the last boot are sent to (piped) to the Terminal based text display tool called '''Less''' which wraps the text output of the journalctl command. Apart from anything else, it makes the errors more useful for anyone reading them in the forum!


Type '''Q''' (upper or lower case) to close "Less".

=== Access to full journal containing info from the system & users: === 


$ journalctl

=== Live view, shows the last 10 lines of the journal & all content as it happens: === 


$ journalctl -f

== Basic filtering: == 

=== Shows all output to the journal since the last boot:=== 


$ journalctl -b

=== Shows all output with priority level ERROR & worse, since last boot: === 


$ journalctl -b -p err


Following is the above command with its output sent to a file called '''-ERRORS''' in your ''/home/<user>'' directory. Having the '''-''' at the beginning of the name should cause the file to be shown at the top of the list of files when viewing the contents of your '''~/''' (''/home/<user>'') directory. This command makes it easy to copy the contents of the -ERRORS file, & then paste it to the forum. Doing so allows us to display ALL of the command's output instead of only being able to cut & paste the truncated lines from our terminal:


$ Journalctl -b -p err > -ERRORS

== Filtering based on time: == 

=== Since yesterday: === 


$ journalctl --since=yesterday

=== Give a specific time period: === 


$ journalctl --since=2012-10-15 --until="2011-10-16 23:59:59"

=== Pick a specific service & time period: === 


$ journalctl -u httpd --since=00:00 --until=9:30

== Point journalctl at specific devices, services, binaries == 

=== Look at a specific device: === 


$ journalctl /dev/sdc

=== Check on a binary: === 


$ journalctl /usr/sbin/vpnc

=== Check on the interlieved output from two specifics: === 


$ journalctl /usr/sbin/vpnc /usr/sbin/dhclient

=== Show all systemd units that have been started in your journal: === 


$ journalctl -F _SYSTEMD_UNIT


You can then interrogate the journal specifying any of those units.

== A summation == 


The Systemd Journal is capable of advanced functions beyond what has been mentioned here. The above is very good food for thought for people that are wondering if they need to be running '''syslog-ng''' or the like that creates most of the '''/var/log/*log''' files on their systems.


By experimenting with the above commands one can make an informed decision for themselves, though as mentioned at the beginning of the Journal section, Arch & therefore Manjaro still run both the new systemd journal & the old style log file system in parallel. So if you find the /var/log/*log files to be redundant & you want to be rid of them, various methods would be effective.


As of this writing I'm running my system with '''syslog-ng''' (& its dependency) deleted. I deleted all of the log files from the /var/log directory (leaving any that are in their own sub-directories), except for Xorg.0.log , Xorg.0.old , lastlog , btmp & wtmp, (pacman.log turned up when pacman was used, depending on what you have installed on your system, you may have applications that create their own logs - which can be turned off - too). (Note: These days I'm systemd free as I've been very happily using the OpenRC init system instead.)


<br clear="all"/>

= Managing /var/log/* files = 

== Introducing Logrotate & friends == 


What is this Logrotate? [http://linux.die.net/man/8/logrotate] logrotate is a powerful tool used to manage the log files created by system processes. It can be instructed to automatically compress, rename in a variety of ways, remove logs, to do all of this & more in a way that maximizes the convenience of logs & conserves your system's resources. An enormous amount of control is available to users including running scripts on your rotated files.


A problem I face in trying to make this article about logrotate as simple as possible is that logrotate can be called in so many ways, & these ways are not mutually exclusive.


For example, logrotate can be called to run on a file, or multiple files in any combination or multiple of '''hourly, daily, weekly, monthly & yearly''', via scripts placed in the /etc/ in the already existing directories '''hourly daily weekly monthly''' the '''yearly''' directory can be added if required. '''crontab''' [http://www.adminschoice.com/crontab-quick-reference/] can be used to run logrotate or scripts as complex as a person needs. logrotate can be combined with other tools in anyway that a user can come up with to process these rotated files at any time & frequency.

<br clear="all"/>
==== The scope of this article ==== 


That said, much of the power of logrotate is for the benefit of those administering servers & will not be dealt with in the following. Though what we will deal with can be used on more than just our log files. We can use logrotate to backup any other files that we choose. I will expand on this at a later date.


<br clear="all"/>

== /etc/logrotate.conf & /etc/logrotate.d == 


The logrotate.conf configuration file largely dictates logrotate's behaviour, it holds global settings, but most of the work that logrotate does is via script files stored in the '''/etc/logrotate.d''' directory, which take precedence over the global settings held in logrotate.conf.


Applications such as Apache, MySQL, Cups & others, put scripts into the /etc/logrotate.d directory to manage their log files.


If you manually run the command '''sudo logrotate''', you will be presented with its usage template. logrotate needs you to specify the path to the script that you want it to use, including the logrotate.conf file which one may think due to its name would be automatically read, it is not.


To run logrotate & the logrotate.conf file you use the following command line:


logrotate /etc/logrotate.conf

<br clear="all"/>
=== Can I store & run my script files elsewhere? === 

A line exists in logrotate.conf that tells logrotate to run all of the scripts that exist in /etc/logrotate.d


include /etc/logrotate.d


We can use the '''include''' command in logrotate.conf to add other directories or use another directory instead of logrotate.d if we have reason to. Be careful what you do as there are files placed into the logrotate.d directory by other programs.

<br clear="all"/>
=== My settings in logrotate.conf don't effect all of the .log files? === 


Script files that are called via the logrotate.conf file take precedence over the global settings in logrotate.conf . That means that if you call a script from logrotate.conf that is located in the /etc/logrotate.d directory, then that script is more powerful than any of the global setting in logrotate.conf .


I use a script '''/etc/logrotate.d/rotate.logs''' that is set to work on all *.log files, & it does. The two that don't get rotated are called '''faillog''' & '''lastlog''' , apart from not having the '''.log''' file extension, these two files are not normal log files, they are accessed via terminal commands of the same name.


<br clear="all"/>

=== Can I store my scripts where I want? === 


Some applications such as Apache cups, drop scripts into /etc/logrotate.d to aid in their own self maintenance. We can use a location of our choosing for these or other scripts if we want. We just have to call its path in the /etc/logrotate.conf file, the same way, as shown in the following example:


include /home/handy/.config/mylogrotate


Apart from adding our own scripts to /etc/logrotate.d (or any other path that we have chosen to include), we can also add scripts into any of the previously mentioned '''/etc/ cron.hourly cron.daily cron.weekly cron.monthly''' folders. OR we can add a script into any of these folders that suit our needs that runs the logrotate /etc/logrotate.conf command which will have the logrotate.conf file, direct logrotate to the default /etc/logrotate.d directory where we have our script(s). OR to another directory where we have our script & have included the path in logrotate.conf . whew!


So you can see there are a variety of ways to call logrotate (let alone use it).


<br clear="all"/>

== Some uses for Logrotate == 


For example, script block below does the following, listed line by line:


* '''/var/log/*.log {''' specifies the file or the files as this example uses a wild card that says all files ending in .log , the '''{''' starts the list of commands that will be used on the file(s) just specified.


* '''daily''' Here we are saying cycle these commands daily, we can also say weekly, monthly, yearly (or specify other times with crontab)[http://www.adminschoice.com/crontab-quick-reference/].


* '''size''' is where we can place a size limit that will cause a file to be rotated. I placed a '''1M''' one megabyte size limit in the example.


* '''dateext''' this puts the date of the rotation on the new copy, so it would use this format: '''<file.name>.log-20130815'''


* '''rotate 7''' means keep 7 of our daily (in this script) backups, delete the oldest when it would become the 8th.


* '''compress''' is obvious, it uses gzip by default & adds a .gz extension to your file, which will make it look like this: <file.name>.log.1.gz you can choose other compression methods, I'm not going into that here.


* '''delaycompress''' tells logrotate to compress the newly rotated file in the next cycle. This has advantages in ease of access & also if the file is still being written to by a process after it has been rotated.


* '''copytruncate''' this is a great option, as it copies the contents of the file to a new new file <file.name>.log.1 & then deletes the contents of the original file. You can have no permission problems crop up when you do it this way.


* '''notifempty''' do nothing if the file is empty, which makes good logical sense.


* '''missingok''' if the file does not exist, give no error.


* '''}''' this curly bracket closes the block of commands.


/var/log/*.log {
daily
size 1M
dateext
rotate 7
compress
delaycompress
copytruncate
notifempty
missingok
}


The above script can be used as is, it does not need to be made executable, it just needs to be put somewhere that logrotate will see (in this example) every day.


We can use the above script block as a template, easily removing parts & modifying its relatively simple settings. It can be duplicated in a script with each script block specifying custom settings tailored for individual files.


<br clear="all"/>

== An Example that you can modify to suit == 


I'll show how I have my system set (at the time of this writing), you can use the information already given on this page & other available on the web to fine tune your set up to suit your needs (if you have the need anyway).

=== Firstly - Be sure this file is here /etc/cron.daily/logrotate === 

#!/bin/sh

# nicenesses range from -20 (most favorable scheduling) to 19 (least favorable)
NICE=19

# 0 for none, 1 for real time, 2 for best-effort, 3 for idle
IONICE_CLASS=2

# 0-7 (for IONICE_CLASS 1 and 2 only), 0=highest, 7=lowest
IONICE_PRIORITY=7

CMD_LOGROTATE="/usr/bin/logrotate /etc/logrotate.conf"

if [ -x /usr/bin/nice ]; then
CMD_LOGROTATE="/usr/bin/nice -n ${NICE:-19} ${CMD_LOGROTATE}"
fi

if [ -x /usr/bin/ionice ]; then
CMD_LOGROTATE="/usr/bin/ionice -c ${IONICE_CLASS:-2} -n ${IONICE_PRIORITY:-7} ${CMD_LOGROTATE}"
fi

${CMD_LOGROTATE}

exit 0

<br clear="all"/>
=== Secondly - Create /etc/logrotate.d/rotate.logs using the following === 


## rotate all /var/log files with names ending in log
/var/log/*log {
## cycle through these commands once per day
daily
## keep the results of 7 cycles
rotate 7
## use gzip to compress each rotated (copied) log file
compress
## compress the file on the next cycle
delaycompress
## copy the contents of the log file to a new file <name>.log.1
## & then delete the contents of the original log file
copytruncate
## do nothing to empty files
notifempty
## create no errors if a file is missing
missingok
## after the files have been rotated run the following command
}


<br clear="all"/>

=== A Summary of the above example thus far === 


The First step puts a file into '''/etc/cron.daily''' which is an easy way to add the script to a daily cron job. Which means that script will be run everyday.


It basically runs this command:


logrotate /etc/logrotate.conf


As logrotate.conf goes through its list of commands it calls this one:


include /etc/logrotate.d


Which means that any scripts that are inside of '''/etc/logrotate.d''' are also run.


This brings us to the second step (above), where we created '''/etc/logrotate.d/rotate.logs''' . This script will be run everyday. The comments I added to the rotate.logs file above give a general idea of what it does. You can delete, modify & add to that script, but do it carefully.

=== The effect of running /etc/logrotate.d/rotate.logs everyday === 


Is that any file in /var/log that had '''log''' at the end of its name will be processed by the commands in the '''rotate.logs''' script. This will back up these files to a new file '''<name>.log.1''' & empty the original file to size 0. Any previous copies with '''<name>.log.<number>''' will have their numbers bumped up one, until the day when they would have been given an 8, that is the day that they are deleted.


As well as this rotating (copying) & renaming of files, all files will be compressed in gzip format on the next rotation. Which means that you always have the current file & yesterdays file in /var/log in uncompressed format.


No files that are empty will be processed, & a file being missing will throw no errors.


<br clear="all"/>
</translate>

[[Category:Contents Page{{#translation:}}]]

Swap

2023-01-16T18:35:46Z

Oguzkagan: removed dead link

<languages />
<br />
__TOC__

<translate>
=Overview= 


Swap space is used to extend the amount of memory(RAM) available for running programs.</translate>
* <translate> Without swap space, if you run out of memory, applications ''will'' be terminated up to and including the entire system crashing.</translate>
* <translate> With swap space available to the system, the kernel can take less frequently accessed memory pages from inactive applications / services and write them to disk ("swapping" them), allowing more actual RAM to be available for active applications.</translate>

<translate> There are three different ways in which swap can be managed in Manjaro:</translate>
* <translate> A swap partition</translate>
* <translate> A swap file</translate>
* <translate> zswap</translate>

<translate> This article tries to be as comprehensive as possible but even more information can be found in the [[<tvar|link>Swap#See_Also</>|articles linked below]]</translate>
<translate>
=Do I Need Swap= 


That is a question that cannot be answered without having a look at your configuration and even with plenty of available memory, it is often used as a safety net or even sometimes due to specific application requirements so have a look at the following non-exhaustive list:</translate>
* <translate> If you use hibernation: ''yes, you need swap!''</translate>
* <translate> If you have services that are not always active, but are still running all the time: ''yes, you need swap!''</translate>
* <translate> If you have an application that allocates virtual memory directly for temporary storage instead of RAM: ''yes, you need swap!''</translate>
* <translate> If you have an application that has a memory leak: ''yes, you need swap!''</translate>
* <translate> If you have a server with 1TB of RAM that you're using as a desktop without applications allocating virtual memory or having memory leaks: ''No, you don't need swap!''</translate>
<translate>
=How Much Swap do I Need= 


The amount of swap you need is highly variable based on ''your'' specific applications and workload. There is no universal formula on swap size without monitoring usage over a period of time. A reasonable place to start would be:</translate>
* <translate> For less then 4GB of physical memory (RAM), it's highly recommended that the swap space should, as a base minimum, be equal to the amount of RAM. Also, it's recommended that the swap space is maximum twice the amount of RAM depending upon the amount of disk space available for the system because of diminishing returns.</translate>
* <translate> For more modern systems (>4GB), your swap space should be at a minimum be ROUNDUP(SQRT(RAM)) I.E. the square root of your RAM size rounded up to the next GB. '''However, if you use hibernation''', you need a minimum of physical memory (RAM) size '''plus''' ROUNDUP(SQRT(RAM)). The maximum, is again twice the amount of RAM, again because of diminishing returns.</translate>
* <translate> The only downside to having more swap space than you will actually use, is the disk space you will be reserving for it cannot be used for application or system data.</translate>

<translate> The "diminishing returns" means that if you need more swap space than twice your RAM size, you would be better off adding more RAM as Hard Disk Drive (HDD) access is about 10³ slower then RAM access, so something that would take 1 second, suddenly takes more than 15 minutes! And on a Solid State Drive (SSD) the same operation that took 1 second in RAM will still take about 1 minute on that SSD!</translate>

<translate>
Taking into account all of the above, this brings us to the following table:
(last 3 columns denote swap space)</translate>

<translate> RAM No hibernation With Hibernation Maximum</translate>
1GB 1GB 2GB 2GB
2GB 2GB 3GB 4GB
3GB 3GB 5GB 6GB
4GB 4GB 6GB 8GB

<translate> RAM No hibernation With Hibernation Maximum</translate>
5GB 2GB 7GB 10GB
6GB 2GB 8GB 12GB
8GB 3GB 11GB 16GB
12GB 3GB 15GB 24GB
16GB 4GB 20GB 32GB
24GB 5GB 29GB 48GB
32GB 6GB 38GB 64GB
64GB 8GB 72GB 128GB
128GB 11GB 139GB 256GB
256GB 16GB 272GB 512GB
512GB 23GB 535GB 1TB
1TB 32GB 1056GB 2TB
2TB 46GB 2094GB 4TB
4TB 64GB 4160GB 8TB
8TB 91GB 8283GB 16TB
{{note|<translate> The largest server one of the authors of this wiki article has ever installed had, indeed, 8TB of RAM and even that machine has the above swap settings, so why not your machine?</translate>}}
<translate>
=Displaying Swap Information= 


The command {{ic|swapon}} will display your current swap information. For example:</translate>
swapon
NAME TYPE SIZE USED PRIO
/dev/sda7 partition 20G 44.3M -2

<translate> The following script will:</translate>
* <translate> show whether zswap is active or not and if active, give zswap parameters if run with the {{ic|sudo}} command</translate>
* <translate> display a list of all applications / services that take up swap and how much they take up in descending order</translate>

#!/bin/bash
#Check whether running as root
if [ "$(whoami)" = 'root' ]; then
dmesg | grep "zswap:" | grep --silent "load"
if [ $? -eq 0 ]; then
# zswap is active
echo "zswap information:"
grep --recursive --color=none . /sys/kernel/debug/zswap/
read -n 1 -s -r -p "Press any key to continue"
else
echo "[warning] zwap not active. Continuing"
fi
else
echo "[warning] Not running as root: skipping zswap info"
fi
for szFile in /proc/*/status ; do
awk '/VmSwap|Name/{printf $2 "\t" $3}END{ print "" }' "$szFile"
done | sort --key 2 --numeric --reverse | more
<translate>
=Using a Swap Partition= 


A swap partition is the traditional way of managing swap. In this scenario, a dedicated partition (or partitions) are created for holding swap.</translate>
<translate>
==Creating and Enabling a Swap Partition== 


To create a swap partition, you need enough unallocated disk space to create an additional partition. If you do not have enough space, skip to the next section [[<tvar|link>#Using_a_Swapfile</>|#Using_a_Swapfile]]. A swap partition can be created in any disk management / partition management tool and should be set as type {{ic|linuxswap}}.</translate>

<translate> Once you have a swap partition you will need to initialize the swap partition with {{ic|mkswap}}. For example, if your swap partition is {{ic|/dev/sda3}}, you could use the command:</translate>
sudo mkswap /dev/sda3

<translate> Next we need to enable the swap partition with the {{ic|swapon}} command. Following our example above this could be done with:</translate>
sudo swapon /dev/sda3

<translate> In order to ensure that the swap is enabled at boot we can add an entry to {{ic|/etc/fstab}}. It is best to use the UUID instead of the device name for this purpose. You can add the line to fstab manually or using the command:</translate>
sudo bash -c "echo UUID=$(lsblk -no UUID /dev/sda3) none swap defaults 0 0 >> /etc/fstab"

<translate> If you would like to have more than one swap partition, simply repeat the steps above for any additional partitions.</translate>

{{note|<translate> Be sure to replace /dev/sda3 in the above commands with your actual swap partition.</translate>}}
{{tip|<translate> ''If you're using a HDD'' (spinning rust) put the swap partition *at the beginning of the disk* as the speed of the disk is higher on the inside tracks. On an SSD this doesn't matter.</translate>}}
<translate>

=Using a Swapfile= 


Using a swap partition has one major disadvantage: Changing the size of swap or adding swap requires repartitioning the disk. In current Linux kernels, it is possible to use a swap file instead of a dedicated partition and as from kernel 2.6 onwards there is no performance difference any more between the two.</translate>

<translate>
==Creating and Enabling a Static Swapfile== 
</translate>
{{tip|<translate>
There is no reason you can't have both a swap partition and a swapfile. This is an easy way to add more swap without repartitioning.
</translate>}}

<translate>
First create and intialize the file to hold the swap. For example, to create a 4GB swapfile, you could use the command:
</translate>

sudo dd if=/dev/zero of=/swapfile bs=1M count=4096 status=progress

<translate>
Set the appropriate permissions on the file. It should be readable and writable only by {{ic|root}}. This can be done with the command:
</translate>

sudo chmod 600 /swapfile

<translate>
Next we need to format and enable the swapfile:
</translate>

sudo mkswap /swapfile

sudo swapon /swapfile

<translate>
In order to ensure that the swap is enabled at boot we can add an entry to {{ic|/etc/fstab}}. You can add the line to fstab manually or using the command:
</translate>

sudo bash -c "echo /swapfile none swap defaults 0 0 >> /etc/fstab"

<translate>

==Swapfiles on BTRFS== 


As of kernel 5.0 and higher, swapfiles are supported on btfrs. They still require some special handling in addition to the above steps.</translate>

<translate> Prior to running the {{ic|dd}} step above, you should run these commands:</translate>
sudo truncate -s 0 /swapfile
sudo chattr +C /swapfile
sudo btrfs property set /swapfile compression none

<translate> These commands create an empty swapfile, disable COW for that file and ensure that compression is disabled.</translate>

{{tip|<translate>
To stay compatible with Timeshift, it is necessary to create the swapfile outside the root subvolume "@".
<tvar|RootCmd>{{RootCmd|command=btrfs subvolume create /@swapfile}}</>
Just replace /swapfile with /@swapfile/swapfile.
</translate>}}

<translate>

==Swapfiles on ZFS== 


zfs doesn't support swapfiles, however you can achieve a similar benefit using a zvol as a swap volume.


Detailed instructions on how to accomplish this can be found in this [<tvar|link>https://github.com/zfsonlinux/pkg-zfs/wiki/HOWTO-use-a-zvol-as-a-swap-device</> ZoL guide].
</translate>
<translate>
=Automated Swap Management with systemd-swap= 
</translate>
{{note|<translate> Using systemd-swap with on btrfs/zfs or with hibernation support requires special handling beyond the scope of this article</translate>}}

<translate> It is possible to automatically manage the size of your swapfile using {{ic|systemd-swap}}. It can create swap files dynamically based on memory needs. It is also an easy way to enable/manage [[<tvar|link>#Using_zswap_with_systemd-swap</>|zswap]]</translate>

<translate>
==Installing and Configuring systemd-swap== 


First, install and enable {{ic|systemd-swap}}:</translate>
pamac install systemd-swap
sudo systemctl enable systemd-swap.service

<translate> Next enable dynamic swap management by creating a file {{ic|/etc/systemd/swap.conf.d/myswap.conf}} with the following parameters:</translate>
zswap_enabled=0
zram_enabled=0
swapfc_enabled=1

<translate> If you would prefer a single command to create this file you could use:</translate>
sudo bash -c 'echo -e "zswap_enabled=0\nzram_enabled=0\nswapfc_enabled=1" > /etc/systemd/swap.conf.d/myswap.conf'

<translate>
==Remove Other Swap== 


In order for systemd-swap to be effective you need to remove any traditional swap devices you have.</translate>

<translate> To display your current swap devices you can use the command {{ic|swapon}}. For example, my test machine displays the following:</translate>
swapon
NAME TYPE SIZE USED PRIO
/swapfile file 4G 0B -2
/dev/sda3 partition 8.4G 0B -3

<translate> In this example there are two swap devices. A swapfile and a swap partition. To turn them off we can use the command {{ic|swapoff}}.</translate>
sudo swapoff /swapfile
sudo swapoff /dev/sda3

<translate>
Next we need to remove them.
The swap partition will need to be deleted using your favorite partitioning tool. You can remove the swapfile by simply deleting it.</translate>
sudo rm /swapfile

<translate> We need to also remove any lines related to swap from {{ic|/etc/fstab}}. Edit the file with an [[<tvar|link>Special:MyLanguage/Viewing_and_editing_configuration_files</>|appropriate text editor]] and remove or comment out the lines for the swap space. In the example above, we would remove these lines:</translate>
UUID=c2430cf1-8ea9-4422-a5c5-5a38779194c3 swap swap defaults,noatime 0 2
/swapfile none swap defaults 0 0

<translate>
With hibernation configured it will also be necessary to edit {{ic|/etc/default/grub}}. Find and remove option {{ic|<nowiki>resume=UUID=...</nowiki>}} or replace the UUID with a new proper value. In the example above, we would remove this text:
resume=UUID=c2430cf1-8ea9-4422-a5c5-5a38779194c3
Then run:
sudo update-grub
If removing hibernation entirely then also delete {{ic|resume}} from the {{ic|HOOKS}} line in {{ic|/etc/mkinitcpio.conf}} and run:
sudo mkinitcpio -P
</translate>

<translate> Next reboot. After the reboot, when running {{ic|swapon}} you should see something similiar to the following:</translate>
NAME TYPE SIZE USED PRIO
/var/lib/systemd-swap/swapfc/1 file 512M 0B -2

<translate> systemd-swap will add and remove swapfiles as your memory usage dictates.</translate>

{{note|<translate> If you don't delete your existing swap partition it will be automatically activated by systemd even though you have removed it from fstab</translate>}}

<translate>

==Using zswap with systemd-swap== 


zswap is compressed swap kept in RAM. zswap keeps the most frequently used pages in RAM and writes less frequently used pages to the swap space on disk. In many workloads, this will result in increased swap performance and less wear and tear on SSDs.


To enable zswap with systemd-swap, simply alter the instructions above and set Linux Kernel parameter zswap_enabled=1</translate>
<translate>
=Tuning & Performance Considerations= 


Although swap seems like a great way to expand memory, excessive swap use will cause severe performance degradation, as mentioned before.</translate>

<translate> There are couple of parameters that can be used to tune swap utilization. These are swappiness and vfs_cache_pressure. To see your current settings for these you can use the following commands:</translate>
cat /proc/sys/vm/swappiness
cat /proc/sys/vm/vfs_cache_pressure

<translate> {{ic|swappiness}} controls how likely a page is to be transferred to swap. This value represents the percentage of the free memory before activating swap. The lower the value, the less swapping is used and the more memory pages are kept in physical memory where:</translate>
* <translate> 0 disables swap</translate>
* <translate> 60 is the default value which is ideal for a server that is memory-starved and running a lot of services</translate>
* <translate> 100 is very aggressive swapping.</translate>

<translate> For ''most'' desktop computers the recommended value is 10: Theoretically, this means to only start swapping when RAM usage reaches around 90 percent.</translate>

<translate> {{ic|vfs_cache_pressure}} used to be a percentage value that controls the tendency of the kernel to ''reclaim'' the memory which is used for caching of directory and inode objects with a default value of 100 on Kernels <5.4. On Kernels >=5.4 can be increased beyond 100.</translate> <translate> Increasing this value will increase the rate in which these objects are removed from the RAM cache. Decreasing it will allow these objects to be cached in memory longer, consuming additional RAM over time.</translate> <translate> Depending on your specific workload, increasing or decreasing this value too far can have significant negative impacts on system performance.</translate> <translate> Experimentation is needed to find the appropriate balance and the default value is reasonable. In general, it is more common to optimize swappiness before experimenting with vfs_cache_pressure.</translate>

<translate> To set these values you can use the command {{ic|sysctl}}. For example, to set the swappiness value to 10 you could use:</translate>
sudo sysctl vm.swappiness=10

'''<translate> There is no preset defined answer on the optimal values for these parameters.</translate>''' <translate> Experimentation is needed to find the optimum configuration for your specific hardware and workload.</translate>

<translate>
=See Also= 
</translate>
* <translate> The Arch Wiki page on [<tvar|link>https://wiki.archlinux.org/index.php/Swap</> swap]</translate>
* <translate> The Arch Wiki page on [<tvar|link>https://wiki.archlinux.org/index.php/Zswap</> zswap]</translate>
* <translate> The Linux kernel documentation on [<tvar|link>https://www.kernel.org/doc/Documentation/vm/zswap.txt</> zswap]</translate>
* <translate> The Linux kernel documentation on [<tvar|link>https://www.kernel.org/doc/Documentation/sysctl/vm.txt</> swappiness and vfs_cache_pressure]</translate>
* <translate> The [<tvar|link>https://github.com/Nefelim4ag/systemd-swap</> systemd-swap page]</translate>
* <translate> The ZFS on Linux guide on [<tvar|link>https://github.com/zfsonlinux/pkg-zfs/wiki/HOWTO-use-a-zvol-as-a-swap-device</> Swap Volumes]</translate>

[[Category:Contents Page{{#translation:}}]]

Linux Security

2023-01-16T18:35:11Z

Oguzkagan: removed dead link

<languages/>
__TOC__

<translate>
=Overview= 


System security is a complicated topic that individuals study for many years. It would be impractical to impart even a fraction of that knowledge in a Wiki article. What this page will attempt to do is provide a primer in the most basic elements of Linux security and identify common pitfalls for beginners

=Users= 


User accounts are used to log into the system and provide one of the basic building blocks for permissions. You could loosely categorize users into a few categories:
* Regular user accounts like the one created for you during install.
* Accounts used to run specific processes. These users are often named after the service they run. For example the {{ic|dbus}} users is user to run the master dbus process.
* The {{ic|root}} account.


The root account is an administrator or superuser account. This account to everything in the system and be used with extreme care. In most cases, it shouldn't be used at all. Instead use {{ic|sudo}}.

=sudo= 


The command {{ic|sudo}} lets you run a command as the root user without actually switching to the root user. In many cases this is safer than using the root user directly as only a single command is being run as root. For example, your normal user account would not be able the file {{ic|/etc/fstab}} because it is owned by root. However, you can edit it with sudo like this:
sudo nano /etc/fstab


When you run this command, you will be asked for a password, this will be the password of your normal user account.<br />
For more information about editing configuration files owned as root see [[Viewing_and_editing_configuration_files|this article on configuration files]].

==sudo vs su== 


While {{ic|sudo}} and {{ic|su}} look similar and both involve root access they are very different. {{ic|sudo}} runs a single command as another user and requests the password of your normal user account. {{ic|su}} lets you *become* root and requests the password of the root user. In general, it is usually safer to use sudo than to use su.


{{warning|Never run a graphical program as root or with sudo, it should only be used with command line programs}}

==Why am I Asked for a Password== 


Sometimes you will take an action in the terminal or through a GUI application and will get prompted for your password. This is because the action you are trying to take cannot be completed by you user and requires elevated rights. Whenever you get a password prompt like this it is important to pause and think if the action you are taking *should* be asking for elevated rights before entering your password.


{{Note|Usually these password prompts will be looking for the password of your normal user account but occasionally they will need the password of the root account}}

=Changing Passwords= 


To change the password of the user account you are logged in as you can use the command:
passwd


To change the password of a different user on the same system you can use sudo:
sudo passwd USERNAME

=Groups= 


Users on a Linux system are commonly arranged in groups. A user group is a convenient way of assigning more users access to a common task like sound, media, printing and mounting of removable drives etc.


A list of the current groups can be seen on the system with the command:
getent group | awk -F : '{print $1}'


To see which groups a given user belongs to use the command
groups USERNAME

==Primary Groups== 


A user can be a member of any number of groups but they have only one primary group. The primary group is the group used when files are created.

=File Permissions= 


At the most basic level, files are designated as '''r'''ead, '''w'''rite or e'''x'''ecute to the '''u'''ser(owner), the '''g'''roup and '''o'''ther. To understand how this works let's look at a real world example.


To get the permissions on the file we can use the command {{ic|ls -l}}.
ls -l /etc/fstab
-rw-r--r-- 1 root root 539 Dec 26 23:07 /etc/fstab


That first group of letters and dashes indicate the permissions. It is 10 characters long and the dashes indicate a lack of permissions.


* The first character "-", represents the file type, "-" indicates that it is a normal files.
* The next three characters "rw-" indicate the permissions for the user or owner of the file. In this case reading and writing are allowed but not executing.
* The next three characters "rw-" indicate the permissions for members of the group who owns the file. In this case reading and writing are allowed but not executing.
* The next three characters "r--" indicate the permissions for other users. In this case reading is allowed but not writing or executing.


From more detailed information on how file permissions are broken down take a look at [https://en.wikipedia.org/wiki/File_system_permissions#Traditional_Unix_permissions this Wikipedia article]

==Changing File Permissions== 


The command {{ic|chmod}} can be used to change permissions on a file or directory. It is probably easier to demonstrate than explain.


Add read rights to the user(owner) of the file
chmod u+r filename


Remove execute rights to members of the group owner of filename
chmod g-x filename


Set the rights for the other group to read only
chmod o=r filename


Of course, in normal use you would combine everything like this:
chmod u+rw,g=r,o-rwx filename


This adds read and write to the owner, set the group as read only and remove read, write and execute from other users


The chmod command can do a lot more than that. For more information take a look at [https://en.wikipedia.org/wiki/Chmod Wikipedia's chmod reference]

=Firewalls= 


The [[Firewalls]] article has a full description of the Firewall solutions available on Manjaro.

=File Integrity Monitoring= 


Your first line of defense should always be security practices that prevent an intrusion such as firewalls, intrusion prevention systems and keeping your system patched and up-to-date. However, it is also useful to try to ensure that your system has not been compromised. One way to help with this is by using a file integrity monitoring solution. These solutions work by comparing the checksums or the files on your system to their previous versions and alerting about changes.


An open source tool which provides this service is [https://aide.github.io/ AIDE](Advanced Intrusion Detection Environment. You can install it with the command:


pamac install aide

=Sandboxing= 


A '''Sandbox''' is a security mechanism for separating running programs, usually in an effort to mitigate system failures or software vulnerabilities from spreading.


One method of sandboxing is using Firejail. Please the [[Firejail|Firejail Wiki page]] for more information on installing and configuring Firejail.
</translate>

[[Category:Contents Page{{#translation:}}]]

Add a Storage Partition & Modify your System to Suit

2023-01-16T18:34:26Z

Oguzkagan: removed dead link

<languages/>
__TOC__
<translate>
==Introduction== 
My storage system was OK when I initially devised it, as it happens, the years have gone by & it had become inefficient & a bit messy. So, time for a makeover. So I spent some hours reorganizing my partitions - 11 -> 12 hours of GParted work. During this time I removed the /swap partition; enlarged my '''/''' partition, it still had ~2GB of free space which should have been fine for the way I use my system.


A '''/swapfile''' [[https://wiki.manjaro.org/index.php/Swap#Using_a_Swapfile]] is to replace the /swap partition (see the previous link for the simple how-to on how to create a /swapfile). My /swapfile was located in the '''/''' partition.


I also shrunk my /home partition as near as small as I could with the size of the data it was holding, so that I could then create a new partition where that data will reside in future.


I had to create a new partition, then reboot into Manjaro, where I moved all of my personal storage data over to the new partition. Then reboot the '''GParted live CD''' & shrink my /home down to 20GB, which is far larger than it needs to be in my new layout, but I have the disk space to spare, so why not? (I could always change it with GParted in the future if I had to.)


My system then needed to be configured to work with these changes as I will go into below.

===The new partition layout=== 
/boot - 102MB ext2 (half full)
/ - 20GB ext4 (carries the 4GB /swapfile & still has 5GB free)
/home - 20GB ext4 (12GB free)
/bdata - 892GB ext4

==Manipulating the Partitions== 
{{BoxDanger|Working with partitions|Modifying an existing partition table may cause loss of data. '''Always''' ensure adequate backup to external storage}}
Boot Manjaro from a live ISO and use Gparted to delete /swap & to modify the size of all (bar /boot) of the partitions on the 1TB (931.51GB formatted) drive. I had to, delete, shrink, move, expand, create (reboot & move my personal data across from /home to the new /bdata , then reboot GParted) shrink, expand.


As previously mentioned, this took 11 -> 12 hours. The larger the partition & the more data involved the longer it takes to process a partition.

==Modifying the system to suit these changes== 
I had to comment out the call for mounting the /swap partition in /etc/fstab , change the path buttons in Worker (I'm probably the only one reading this that uses the wonderful Worker, so, for all that statement is worth...) to suit the new partition layout. For anyone doing the same thing you need to think about anything that you may have done that needs to be reconfigured to use these new paths (more on this later).


Then in the Terminal I used the blkid command to get the UUID of the new /bdata partition so I could add a call to it into the /etc/fstab :


[handy@jarmano ~]$ blkid
/dev/sda1: UUID="41c2c2b3-5ad8-43bc-9bf0-84d3b429127d" TYPE="ext2"
/dev/sda2: LABEL="big.data" UUID="9fe95af9-529e-4f68-b83c-7fa9e7fb3ba1" TYPE="ext4"
/dev/sda3: LABEL="my.system" UUID="6dfe5e6b-86b9-4301-b385-8cc3816ada8c" TYPE="ext4"
/dev/sda4: LABEL="my.home" UUID="b993339d-dbb3-4fbd-adb4-e61baf43cd7f" TYPE="ext4"
/dev/sdb1: LABEL="store" UUID="05e6f212-4003-430b-a7d9-a53d98fad0b5" TYPE="ext4" PARTUUID="8cb60e1f-8d16-4d9c-bccc-3a2cd5396836"


As you may have noticed, the new partition was given the /dev/sda2: spot (which once belonged to /swap)


I Copied the UUID for the new partition into /etc/fstab & created a call for this new partition, like so:
{{File|file=/etc/fstab|content=<pre>...
UUID=9fe95af9-529e-4f68-b83c-7fa9e7fb3ba1 /data/bdata ext4 defaults 0 1
...
</pre>}}


Then as root I made the directory /mnt/bdata , so that the new partition is accessible. You can do this in the Terminal like so (replace <directory.name> with the name you want to call your new partition:
{{RootCmd|command=mkdir -p /data<directory.name>}}


Due to GParted doing its work with root permissions we need to change the ownership (owner:group) of the new partition, which we do by modifying the ownership of the directory name (that was created in the last command above) from root:root to <user.name>:users. To do that use the following Terminal command:
{{RootCmd|command=chown <user.name>:users /data/<new.partition's.name>}}

==Configure the system to use new default storage directories== 


Firstly, I had to check both the ~/.bash_profile & the /etc/profile files & modify the '''PATH''' variables where I had added paths that were now incorrect. Most users here won't have changed anything in these two files, though it is just too easy to do, to not check them for safeties sake. When looking at these files, check the PATH line for anything that relates to your moved storage directories. You probably won't have any differences unless you added them. These lines in my files follow, you will see where I have replaced the original paths with /mnt/bdata :


{{File|
file=~/.bash_profile|
content=<pre>PATH=$PATH:/mnt/bdata/scripts
export PATH
PATH=$PATH:~/games/ut2004
export PATH
PATH=$PATH:~/games/ut2004/System
export PATH</pre>}}


{{File|
file=/etc/profile|
content=<pre># Set our default path
PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/mnt/bdata/scripts:"
export PATH</pre>}}


Then I needed to change the paths for what are considered to be the standard default /home/<user>/ storage directories - Downloads, Video, Music & so on. I had previously changed these paths, also, I don't want to use capital letters in the beginning of their names.


If you have more than one user account on your system, then it would be best to use & edit:
{{UserCmd|command=nano ~/.config/user-dirs.conf}}


If the above file doesn't exist, create it. Then copy mine (just below), editing it to suit your system/desires. Having only one user account on my Manjaro setup, I delete the previously mentioned file (if it existed anyway) & modify:


{{RootCmd|command=nano /etc/xdg/user-dirs.defaults}}


As its settings, under these circumstances (not having a ~/.config/user-dirs.conf ) will be global. Mine edited file follows:


{{File|
file=~/.config/user-dirs.conf|
content=<pre># Default settings for user directories customised by handy :->
#
# The values are relative pathnames from the home directory and
# will be translated on a per-path-element basis into the users locale
DESKTOP=desktop
DOWNLOAD=/data/bdata/downloads
DOCUMENTS=/data/bdata/documents
MUSIC=/data/bdata/music
PICTURES=/data/bdata/pictures
VIDEOS=/data/bdata/videos</pre>
}}


Once you have done this, check that you don't have new (likely empty) default directories in your ~/ that were created by the above file(s) on boot. Any such void files should be deleted after you have modified either the ''user'' based '''~/.config/user-dirs.conf''' or the ''root'' based '''/etc/xdg/user-dirs.defaults''' files. '''~/.bashrc''' may need some paths changed as well, depending on what you call from it.


I also had to tell qBittorent, Firefox (& the few other browsers I'm testing) where their particular download directories had moved to. Any other applications that were set to save data into the documents, or any other directory that has moved (or been created as a default, in either of the two directories above) will need to have their config's modified too. & so it goes...

==Creating a /swapfile== 
Now, if you do choose to not have a /swap partition but you would still like to have swap space (which of course you can choose to easily have at any time in the future), then there is a very functional option available to you called a /swapfile. For simple information on how to set one up, have a look over here: [https://wiki.manjaro.org/index.php?title=Add_a_/swapfile]
</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:Storage{{#translation:}}]]

Wacom Tablet And Pen

2023-01-16T18:33:27Z

Oguzkagan: removed dead link

<languages/>
__TOC__
<translate>
==Tablets and Pen displays (wacom but not only)== 

==Different Desktop Environments== 

===Cinnamon, Gnome and Budgie=== 
The only thing that is needed to install aside from the default installer is the package <code>xf86-input-wacom</code>.

===KDE Plasma 5=== 
The package <code>xf86-input-wacom</code> will be automatically installed when installing the <code>kcm-wacomtablet</code> from community repository.


This will add Tablet Settings interface/configuration in the System Settings + the needed background services for KDE Plasma Framework.

===XFCE and probably MATE=== 
There is a workaround proposed by [https://github.com/achadwick/gsdwacom4xfce achadwick] and works just fine. They use the Gnome settings interface.

==Known Issues== 

===Slow drag in File Manager=== 
Slow drag in File Manager and very slow interaction of Tools and Brushes in Krita. \
The resolution is to modify the <code>10-evdev.conf</code> in <code>/usr/share/X11/xorg.conf.d/10-evdev.conf</code>


There might be necessary to make a symlink of it like this:
sudo ln -s /usr/share/X11/xorg.conf.d/10-evdev.conf /etc/X11/xorg.conf.d/10-evdev.conf


<pre>
~ >>> cat /etc/X11/xorg.conf.d/10-evdev.conf
#
# Catch-all evdev loader for udev-based systems
# We don't simply match on any device since that also adds accelerometers
# and other devices that we don't really want to use. The list below
# matches everything but joysticks.


Section "InputClass"
Identifier "evdev pointer catchall"
MatchIsPointer "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection


#Section "InputClass"
# Identifier "evdev keyboard catchall"
# MatchIsKeyboard "on"
# MatchDevicePath "/dev/input/event*"
# Driver "evdev"
#EndSection


#Section "InputClass"
# Identifier "evdev touchpad catchall"
# MatchIsTouchpad "on"
# MatchDevicePath "/dev/input/event*"
# Driver "evdev"
#EndSection


#Section "InputClass"
# Identifier "evdev tablet catchall"
# MatchIsTablet "on"
# MatchDevicePath "/dev/input/event*"
# Driver "evdev"
#EndSection


#Section "InputClass"
# Identifier "evdev touchscreen catchall"
# MatchIsTouchscreen "on"
# MatchDevicePath "/dev/input/event*"
# Driver "evdev"
#EndSection
</pre>

===Gnome DE=== 
In Gnome, if someone wants to use the GDM theme of a custom gnome-shell theme to have a consistent look trough login/log-out/lock-screen, the settings for mapping the buttons will render a blank overlay with no options.


'''Resolutions''':


* Use the default <code>gnome-shell</code>, <code>adwaita</code> and <code>gdm</code>
* Use the modified <code>manjaro-gnome-maia-theme</code>

===The device is not recognized=== 


The device is not recognized, the xinput doesn’t list it, etc, that is most likely due to a not supported device, no specific ID in the <code>/usr/share/libwacom/</code> for it.


A possible resolution is to install the <code>input-wacom-dkms</code> making sure that the headers for the kernel are installed too, then manually adding the modules to load.


It will not provide a functionality if the modules are not loaded, and still relies in the <code>xf86-input-wacom</code>, <code>libwacom</code> and the Graphical interface for Tablet settings.


Of course the <code>xsetwacom</code> commands work too, but the purpose is to have a GUI for settings and avoid any confusing/miss-passed settings from terminal.

===KDE Plasma 5=== 


In KDE Plasma 5 the <code>kcm-wacomtablet</code> recognizes the pen and tablet but the pen (Stylus) doesn’t draw. By default there are no settings for them, the resolution is:
# Set the mode to Absolute Mode in the tablet tab and the Area to the desired screen.
# To the Stylus tab set the Eraser and Tip to where the slider passes slightly the letter T from the word Soft.
# The Raw Sample to the level 5
# The Suppress Rate to the level 2
# Edit the pressure curve to be slightly curved downwards.
# Set Button 3 to Right Mouse Button Click
# Set Button 2 to Middle Mouse Button Click
# Set Button 1 to Left Mouse Button Click
# '''DO NOT''' check Tap to execute action
# Click '''Apply''' button, '''disconnect''' and '''reconnect''' the tablet and it should work.
From this point all the settings can be changed and have also the Express Buttons personalized, and calibrate the pen to the screen area.


The settings are stored in <code>~/.config/tabletprofilesrc</code>

===Mixed configurations=== 


Mixed configurations due to use of <code>xsetwacom</code> commands and other tools. Resolution is to undo all and start with the GUI Settings.

==More information== 
* Manjaro Forum [https://forum.manjaro.org/search?q=wacom%20order%3Alatest_topic Search for Wacom]
* Github [https://github.com/Zeioth/XFCE-Wacom-Settings Zeioth/XFCE-Wacom-Settings]
</translate>

[[Category:Contents Page{{#translation:}}]]

Wacom Tablet And Pen

2023-01-16T18:32:31Z

Oguzkagan: removed dead link

<languages/>
__TOC__
<translate>
==Tablets and Pen displays (wacom but not only)== 

==Different Desktop Environments== 

===Cinnamon, Gnome and Budgie=== 
The only thing that is needed to install aside from the default installer is the package <code>xf86-input-wacom</code>.

===KDE Plasma 5=== 
The package <code>xf86-input-wacom</code> will be automatically installed when installing the <code>kcm-wacomtablet</code> from community repository.


This will add Tablet Settings interface/configuration in the System Settings + the needed background services for KDE Plasma Framework.

===XFCE and probably MATE=== 
There is a workaround proposed by [https://github.com/achadwick/gsdwacom4xfce achadwick] and works just fine. They use the Gnome settings interface.

==Known Issues== 

===Slow drag in File Manager=== 
Slow drag in File Manager and very slow interaction of Tools and Brushes in Krita. \
The resolution is to modify the <code>10-evdev.conf</code> in <code>/usr/share/X11/xorg.conf.d/10-evdev.conf</code>


There might be necessary to make a symlink of it like this:
sudo ln -s /usr/share/X11/xorg.conf.d/10-evdev.conf /etc/X11/xorg.conf.d/10-evdev.conf


<pre>
~ >>> cat /etc/X11/xorg.conf.d/10-evdev.conf
#
# Catch-all evdev loader for udev-based systems
# We don't simply match on any device since that also adds accelerometers
# and other devices that we don't really want to use. The list below
# matches everything but joysticks.


Section "InputClass"
Identifier "evdev pointer catchall"
MatchIsPointer "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection


#Section "InputClass"
# Identifier "evdev keyboard catchall"
# MatchIsKeyboard "on"
# MatchDevicePath "/dev/input/event*"
# Driver "evdev"
#EndSection


#Section "InputClass"
# Identifier "evdev touchpad catchall"
# MatchIsTouchpad "on"
# MatchDevicePath "/dev/input/event*"
# Driver "evdev"
#EndSection


#Section "InputClass"
# Identifier "evdev tablet catchall"
# MatchIsTablet "on"
# MatchDevicePath "/dev/input/event*"
# Driver "evdev"
#EndSection


#Section "InputClass"
# Identifier "evdev touchscreen catchall"
# MatchIsTouchscreen "on"
# MatchDevicePath "/dev/input/event*"
# Driver "evdev"
#EndSection
</pre>

===Gnome DE=== 
In Gnome, if someone wants to use the GDM theme of a custom gnome-shell theme to have a consistent look trough login/log-out/lock-screen, the settings for mapping the buttons will render a blank overlay with no options.


'''Resolutions''':


* Use the default <code>gnome-shell</code>, <code>adwaita</code> and <code>gdm</code>
* Use the modified <code>manjaro-gnome-maia-theme</code>

===The device is not recognized=== 


The device is not recognized, the xinput doesn’t list it, etc, that is most likely due to a not supported device, no specific ID in the <code>/usr/share/libwacom/</code> for it.


A possible resolution is to install the <code>input-wacom-dkms</code> making sure that the headers for the kernel are installed too, then manually adding the modules to load.


It will not provide a functionality if the modules are not loaded, and still relies in the <code>xf86-input-wacom</code>, <code>libwacom</code> and the Graphical interface for Tablet settings.


Of course the <code>xsetwacom</code> commands work too, but the purpose is to have a GUI for settings and avoid any confusing/miss-passed settings from terminal.

===KDE Plasma 5=== 


In KDE Plasma 5 the <code>kcm-wacomtablet</code> recognizes the pen and tablet but the pen (Stylus) doesn’t draw. By default there are no settings for them, the resolution is:
# Set the mode to Absolute Mode in the tablet tab and the Area to the desired screen.
# To the Stylus tab set the Eraser and Tip to where the slider passes slightly the letter T from the word Soft.
# The Raw Sample to the level 5
# The Suppress Rate to the level 2
# Edit the pressure curve to be slightly curved downwards.
# Set Button 3 to Right Mouse Button Click
# Set Button 2 to Middle Mouse Button Click
# Set Button 1 to Left Mouse Button Click
# '''DO NOT''' check Tap to execute action
# Click '''Apply''' button, '''disconnect''' and '''reconnect''' the tablet and it should work.
From this point all the settings can be changed and have also the Express Buttons personalized, and calibrate the pen to the screen area.


The settings are stored in <code>~/.config/tabletprofilesrc</code>

===Mixed configurations=== 


Mixed configurations due to use of <code>xsetwacom</code> commands and other tools. Resolution is to undo all and start with the GUI Settings.

==More information== 
* Manjaro Forum [https://forum.manjaro.org/search?q=wacom%20order%3Alatest_topic Search for Wacom]
* Manjaro Forum [https://forum.manjaro.org/t/very-slow-drag-and-drop-on-plasma-5/42099/2?u=bogdancovaciu Very slow drag and drop on Plasma 5]
* Manjaro Forum [https://forum.manjaro.org/t/no-wacom-effort-from-the-manjaro-team/22040/23?u=bogdancovaciu No Wacom effort from the Manjaro Team]
* Github [https://github.com/Zeioth/XFCE-Wacom-Settings Zeioth/XFCE-Wacom-Settings]
</translate>

[[Category:Contents Page{{#translation:}}]]

Configure Graphics Cards

2023-01-16T18:31:22Z

Oguzkagan: removed dead link

<languages/>
__TOC__
<translate>
= Overview = 


{{note|The mhwd command is still ''under development'', and at present is only able to install drivers for graphics cards connected internally via pci.}}


Where installing the full version of Manjaro (i.e. complete with a pre-installed desktop environment, codecs, and software applications), the mhwd command will be automatically run by the GUI and CLI installer to automatically detect your graphics card and install the most appropriate driver for it. '''Whether free or proprietary drivers are installed will depend on your initial choice of using free or nonfree graphics drivers to boot up'''.
Otherwise, it will be necessary to run the mhwd command manually as part of the post-installation process for the minimalistic '''NET-Edition''' of Manjaro.


'''For Beginners, it is recommended to use "Hardware Detection" in [[Manjaro Settings Manager]] to change or install new graphics drivers.'''<br />
For intermediate and advanced users, it is also possible to use the mhwd command to install, re-install, and remove installed graphics drivers at any time, as illustrated below.

= Automated Identification and Installation = 


This is the recommended method for the detection and installation of graphics drivers. The syntax for the automated installation method is:


{{UserCmd|command=sudo mhwd -a [pci or usb connection] [free or nonfree drivers] 0300}}


A breakdown of the command used for the automated method is as follows:


* '''-a''': Automatically detect and install the appropriate driver
* '''[pci or usb]''': Install the appropriate driver for devices connected internally via pci, or externally via usb (again, mhwd currently only supports pci connections at this stage in its development)
* '''[free or nonfree]''': Install either free drivers (e.g. provided by the Linux community), or nonfree drivers (e.g. provided by hardware manufacturers)
* '''0300''': Identify that a driver is to be installed for a graphics card (0300 is the ID for graphics cards. As the mhwd command develops, new ids will be used for other hardware devices).


For example, the following command would result in the automatic detection and installation of the best available '''proprietary driver''' for a pci-connected graphics card:


{{UserCmd|command=sudo mhwd -a pci nonfree 0300}}


Otherwise, the following command would result in the automatic detection and installation of the best available '''free driver''' for a pci-connected graphics card:


{{UserCmd|command=sudo mhwd -a pci free 0300}}

= Manual Identification and Installation = 


Taking a do-it-yourself approach is itself relatively easy and straightforward using the mhwd command. This should be undertaken in two stages:


'''1.''' Identify the appropriate driver to be installed, and then


'''2.''' Install the driver


{{tip| Just ensure that you have identified and are indeed about to install the correct driver for your particular graphics card!}}

== Identifying Available Drivers == 


Prior to manually installing a graphics driver, it will be necessary to identify what drivers are available for your system. To list the appropriate drivers available, the basic syntax is:


{{UserCmd|command=mhwd -l [optional: detailed view] [optional: --pci or --usb connection]}}


Using this command without the additional options will list basic information for all the available drivers for devices connected to your system. '''All drivers graphics card drivers will have the prefix (video-) in their name'''. The basic information provided for all listed drivers will be:


* Name
* Version
* Free or proprietary, and
* PCI or USB connection


A more detailed list of installed drivers can be obtained by entering:


{{UserCmd|command=mhwd -l -d}}


A detailed list will provide the following information:


* Name
* Version
* PCI or USB connection
* Description
* Priority
* Free or proprietary
* Dependencies
* Conflicts
* Class ID (e.g. '0300' for graphics card drivers), and
* Vendor ID


In addition, using the ''--pci'' filter in the following example will list detailed information for only the drivers available for devices (e.g. graphics cards) using an internal PCI connection:


{{UserCmd|command=mhwd -l -d --pci}}

== Installing a Driver == 


To install a driver for a graphics card, the syntax is:


{{UserCmd|command=sudo mhwd -i pci [name of driver]}}


A breakdown of the command used to manually install a driver is as follows:


* '''-i''': Install a driver
* '''[pci]''': Install a driver for a device connected internally via pci (e.g. graphics cards)
* '''[name of driver]''': The name of the driver to be installed


For example, to install the proprietary nvidia graphics card driver, the following command would be used:


{{UserCmd|command=sudo mhwd -i pci video-nvidia}}

== Force Reinstall a Driver == 


{{warning|use this command with care!}}


To force the re-installation of an existing driver without removing it first, the syntax is:


{{UserCmd|command=sudo mhwd -f -i pci [name of driver]}}


For example, to force the re-installation of a previously installed nvidia graphics card driver, the following command would be used:


{{UserCmd|command=sudo mhwd -f -i pci video-nvidia}}

= Removing an Installed Driver = 


On occasion it may be necessary to remove an installed graphics card driver. Similarly to manually installing a graphics card driver, two steps should be undertaken for removal:


'''1.''' Identify the installed driver


'''2.''' Remove the identified driver


After all, it would be somewhat difficult to remove an installed driver if you don't know what it's called!

== Identifying Installed Drivers == 


To identify and list Manjaro's installed drivers - including the graphics driver to be removed, the syntax is:


{{UserCmd|command=mhwd -li [optional: detailed view] [optional: pci or usb devices only]}}


Using this command without the additional options will list the basic information of all the drivers currently installed on your system. '''Once again, all drivers for graphics cards will have the prefix (video-) in their name'''. As with listing drivers available for your system, the ''-d'' option used in the following command will list detailed information:


{{UserCmd|command=mhwd -li -d}}


This information may prove useful to determine any otherwise unforeseen consequences or problems upon removing a driver. And again, it is also possible to filter your list of installed drivers by whether they are used on hardware connected via pci or usb. In this instance, a detailed list will be generated only for installed drivers used on hardware with a PCI connection:


{{UserCmd|command=mhwd -li -d --pci}}


One other way of reporting drivers installed andin use is using the {{ic|inxi}} tool.


{{UserCmd|command=inxi -G}}


{{note|The mhwd profile 'video-linux' corresponds to the latest opensource driver availablefor your hardware.}}
{{note|The mhwd profile 'video-vesa' is a generic fallback driver which should not be used in the vast majority of cases.}}

== Removing Installed Drivers == 


{{warning|use this command with care!}}


To remove an installed driver, the syntax is:


{{UserCmd|command=sudo mhwd -r [pci or usb] [name of driver]}}


For example, to remove the installed driver for a nvidia graphics card (connected internally via pci), the following command would be used:


{{UserCmd|command=sudo mhwd -r pci video-nvidia}}

= Checking configuration = 


You can check configuration with:
{{UserCmd|command=sudo mhwd-gpu --check}}
{{UserCmd|command=mhwd-gpu --status}}


And if needed fix issues with:
{{UserCmd|command=sudo mhwd-gpu --setmod}}
{{UserCmd|command=sudo mhwd-gpu --setxorg [PATH]}}


Make sure the path to xorg config file is valid.


Note about ati, xorg file and login artifacts or kicad: if you get artifacts upon logging in or if kicad rendering and zooming is slow, try adding [Option "EXAPixmaps" "off"] in the "Device" section of xorg config file. See [https://wiki.archlinux.org/title/ATI#Performance_and/or_artifacts_issues_when_using_EXA here.]

=Dual GPU= 

==PRIME GPU offloading== 


If your hardware includes more than one GPU card you can make use of PRIME offloading. PRIME is a technology used to manage hybrid graphics found on recent desktops and laptops (Optimus for NVIDIA, AMD Dynamic Switchable Graphics for Radeon). PRIME detects both cards and automatically selects Intel card by default; using the more powerful discrete graphics card, when called, for more demanding applications.


In Manjaro this will automatically be available for hybrid graphics systems using intel/modesetting for the integrated card and free drivers (AMDGPU or Nouveau) for the dGPU.


You may choose to run a program with a specific GPU, prepending the application's command with ''DRI_PRIME=x'', where ''x'' is the card priority number.


For example, to run an application using the second card prepend the application command with '''DRI_PRIME=1'''


{{UserCmd|command=DRI_PRIME=1 glxspheres64}}


To use the 1st card (usually when the CPU has an embedded GPU, this is used)


{{UserCmd|command=DRI_PRIME=0 glxspheres64}}


If you want to always run some application with the discrete gpu, you may copy that application's .desktop file to {{ic|~/.local/share/applications/}} and edit the "Exec" property


{{UserCmd|command=Exec=DRI_PRIME=1 inkscape}}


Some applications (usually games like steam) may have an embedded option to specify the command line, where it is preferred to use this way.


For example, in Steam, select a game - that you want to run using your discrete Nvidia card - from the Library page of the Steam client, right-click, and select Properties.
Click the SET LAUNCH OPTIONS... button and specify for the command line options followed by the default launch hook %command%.


DRI_PRIME=1 %command%


To use the dGPU by default see '''[https://wiki.archlinux.org/index.php/PRIME#Reverse_PRIME Reverse Prime]'''

= NVIDIA Proprietary (non-free) drivers = 


If you have a Nvidia card, you have the option to use the proprietary (closed source = non-free) drivers instead of the open source (free) nouveau driver.


For Legacy/older nvidia cards, Manjaro maintains older drivers for compatibility. In these cases the driver name is different, instead of nvidia it is nvidia-390xx or nvidia340xx, whether in nvidia-only or bumblebee mhwd driver configuration.


When you install the non-free driver, mhwd includes a Nvidia utility "Nvidia Settings Utility" that can help you configure several settings. You can find this utility in your GUI Applications Menu or start it from a terminal


{{UserCmd|command=sudo nvidia-settings}}


If you are using bumblebee, the nvidia utility needs a special command


{{UserCmd|command=sudo optirun -b none nvidia-settings -c :8}}

==Nvidia Optimus== 
For Optimus laptops or dual GPU hardware with intel and nvidia GPUs, you have three options to utilize the card driver usage at your preference or your hardware capabilities.


'''[[#nvidia-prime|PRIME]] (mhwd default)'''


'''[[#Bumblebee|Bumblebee]]'''


When you install Manjaro with the non-free option selected from Grub menu, or when you use automatic driver installation, PRIME or bumblebee is installed by default, depending on support for your GPU, PRIME being preferred. In these cases, the mhwd driver is named "video-hybrid-intel-nvidia-***xx-prime" or "video-hybrid-intel-nvidia-***xx-bumblebee".

==Configure The Resolution/Refresh Rate== 


{{warning|The method provided does not currently work for the Cinnamon Edition. As soon as a solution is found, then this article will be updated.}}


'''1.''' Start nvidia-settings utility


'''2.''' Change resolution and refresh rate in 'X Server Display Configuration' tab.


'''3.''' Hit the 'Save to X Configuration File' button and save to '''/etc/X11/mhwd.d/nvidia.conf'''


'''4.''' Now start your terminal and enter the following command to complete the process:


{{UserCmd|command=sudo mhwd-gpu --setmod nvidia --setxorg /etc/X11/mhwd.d/nvidia.conf}}

==Configure X Screen settings (OpenGL Settings, Antialiasing, X Server XVideo)== 


'''1.''' Start nvidia-settings utility


'''2.''' Change settings in X Server XVideo Settings, OpenGL and Antialiasing, in the 'X Screen' tab.


'''3.''' Click on 'nvidia-settings configuration' tab and click on the 'Save Current Configuration' button.


'''4.''' Save the .nvidia-settings-rc to the default location specified ('''/home/[your account name]''')


'''5.''' Edit the .xinitrc file with your preferred text editor. For example, if you use gedit, run this in your terminal:


{{UserCmd|command=gedit ~/.xinitrc}}


'''6.''' Once opened, add the following line into the configuration file:


{{UserCmd|command=exec nvidia-settings --load-config-only}}


'''7.''' Save and exit.

==Nvidia settings for special cases == 


In case your monitor is not entering powersave mode (DPMS), try adding `Option "HardDPMS" "true"` in your Xorg monitor section. For example:


Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "Unknown"
ModelName "BenQ ZOWIE XL LCD"
HorizSync 30.0 - 160.0
VertRefresh 56.0 - 144.0
Option "DPMS"
Option "HardDPMS" "true"
EndSection


After forum [https://forum.manjaro.org/t/display-does-not-go-to-powersave/84004/5 issue]

==nvidia-prime== 


Manjaro also offers an easy way to use PRIME with proprietary Nvidia drivers.<br>
Simply select and install an 'nvidia-prime' profile through MSM or mhwd (such as ''video-hybrid-intel-nvidia-440xx-prime'') and ensure the package ''nvidia-prime'' is installed.


Then to use the discrete Nvidia card it works the same as [[#PRIME_GPU_offloading|PRIME offloading]] above but uses a different command. Prepend the application command with '''prime-run'''. For example:


{{UserCmd|command=prime-run glxspheres64}}

==Bumblebee== 


Bumblebee configuration is mainly developed to help minimize laptop battery consumption, since Nvidia usually consumes significant power, while Intel cards are more power efficient. So, bumblebee detects both cards and automatically selects Intel card by default and can use the Nvidia for more demanding applications.
For an application to use the Nvidia card, prepend the application command with optirun or primusrun. For example:


{{UserCmd|command=optirun glxspheres64}}
{{UserCmd|command=primusrun inkscape}}


If you want to specifically run some application with the nvidia driver, you may edit that application's .desktop file "Exec" property, or run it in terminal like this


Exec=primusrun chromium


Some applications (usually games like steam) may have an embedded option to specify the command line, where it is preferred to use this way.


For example, in Steam, select a game - that you want to run using your discrete Nvidia card - from the Library page of the Steam client, right-click, and select Properties.
Click the SET LAUNCH OPTIONS... button and specify for the command line options followed by the default launch hook %command%.

primusrun %command%

= See also = 


* [[Manjaro Hardware Detection Overview]]

= Easier way = 


You may use a GUI version of mhwd in [[Manjaro Settings Manager#Hardware Detection]]
: With this tool you can:
: - install graphic driver
: - switch graphic driver


https://www.youtube.com/watch?v=UAFGukpEIJw

= How to check the driver = 


{{UserCmd|command=glxinfo | grep OpenGL}}


Example output command:


'''Nvidia driver''' ( proprietary driver )


{{UserCmdOutput|command=glxinfo | grep OpenGL|result= OpenGL vendor string: NVIDIA Corporation<br> OpenGL renderer string: GeForce GTX 660/PCIe/SSE2<br> OpenGL core profile version string: 4.3.0 NVIDIA 331.49<br> OpenGL core profile shading language version string: 4.30 NVIDIA via Cg compiler<br> OpenGL core profile context flags: (none)<br> OpenGL core profile profile mask: core profile<br> OpenGL core profile extensions:<br> OpenGL version string: 4.4.0 NVIDIA 331.49<br> OpenGL shading language version string: 4.40 NVIDIA via Cg compiler<br> OpenGL context flags: (none)<br> OpenGL profile mask: (none)<br> OpenGL extensions:}}


'''Nouveau''' , '''Gallium''' from '''Mesa''' ( open source driver )


{{UserCmdOutput|command=glxinfo | grep OpenGL|result= OpenGL vendor string: nouveau<br> OpenGL renderer string: Gallium 0.4 on NVE6<br> OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.5<br> OpenGL core profile shading language version string: 1.40<br> OpenGL core profile context flags: (none)<br> OpenGL core profile extensions:<br> OpenGL version string: 3.0 Mesa 9.2.5<br> OpenGL shading language version string: 1.30<br> OpenGL context flags: (none)<br> OpenGL extensions:}}


'''Intel''' driver from '''Mesa''' ( open driver )


{{UserCmdOutput|command=glxinfo | grep OpenGL|result= OpenGL vendor string: Intel Open Source Technology Center<br> OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Desktop<br> OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.0.6<br> OpenGL core profile shading language version string: 3.30<br> OpenGL core profile context flags: (none)<br> OpenGL core profile profile mask: core profile<br> OpenGL core profile extensions:<br> OpenGL version string: 3.0 Mesa 11.0.6<br> OpenGL shading language version string: 1.30<br> OpenGL context flags: (none)<br> OpenGL extensions:<br> OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.0.6<br> OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00<br> OpenGL ES profile extensions:}}

</translate>
[[Category:Contents Page]]

Configure Graphics Cards

2023-01-16T18:30:49Z

Oguzkagan: removed dead link

<languages/>
__TOC__
<translate>
= Overview = 


{{note|The mhwd command is still ''under development'', and at present is only able to install drivers for graphics cards connected internally via pci.}}


Where installing the full version of Manjaro (i.e. complete with a pre-installed desktop environment, codecs, and software applications), the mhwd command will be automatically run by the GUI and CLI installer to automatically detect your graphics card and install the most appropriate driver for it. '''Whether free or proprietary drivers are installed will depend on your initial choice of using free or nonfree graphics drivers to boot up'''.
Otherwise, it will be necessary to run the mhwd command manually as part of the post-installation process for the minimalistic '''NET-Edition''' of Manjaro.


'''For Beginners, it is recommended to use "Hardware Detection" in [[Manjaro Settings Manager]] to change or install new graphics drivers.'''<br />
For intermediate and advanced users, it is also possible to use the mhwd command to install, re-install, and remove installed graphics drivers at any time, as illustrated below.

= Automated Identification and Installation = 


This is the recommended method for the detection and installation of graphics drivers. The syntax for the automated installation method is:


{{UserCmd|command=sudo mhwd -a [pci or usb connection] [free or nonfree drivers] 0300}}


A breakdown of the command used for the automated method is as follows:


* '''-a''': Automatically detect and install the appropriate driver
* '''[pci or usb]''': Install the appropriate driver for devices connected internally via pci, or externally via usb (again, mhwd currently only supports pci connections at this stage in its development)
* '''[free or nonfree]''': Install either free drivers (e.g. provided by the Linux community), or nonfree drivers (e.g. provided by hardware manufacturers)
* '''0300''': Identify that a driver is to be installed for a graphics card (0300 is the ID for graphics cards. As the mhwd command develops, new ids will be used for other hardware devices).


For example, the following command would result in the automatic detection and installation of the best available '''proprietary driver''' for a pci-connected graphics card:


{{UserCmd|command=sudo mhwd -a pci nonfree 0300}}


Otherwise, the following command would result in the automatic detection and installation of the best available '''free driver''' for a pci-connected graphics card:


{{UserCmd|command=sudo mhwd -a pci free 0300}}

= Manual Identification and Installation = 


Taking a do-it-yourself approach is itself relatively easy and straightforward using the mhwd command. This should be undertaken in two stages:


'''1.''' Identify the appropriate driver to be installed, and then


'''2.''' Install the driver


{{tip| Just ensure that you have identified and are indeed about to install the correct driver for your particular graphics card!}}

== Identifying Available Drivers == 


Prior to manually installing a graphics driver, it will be necessary to identify what drivers are available for your system. To list the appropriate drivers available, the basic syntax is:


{{UserCmd|command=mhwd -l [optional: detailed view] [optional: --pci or --usb connection]}}


Using this command without the additional options will list basic information for all the available drivers for devices connected to your system. '''All drivers graphics card drivers will have the prefix (video-) in their name'''. The basic information provided for all listed drivers will be:


* Name
* Version
* Free or proprietary, and
* PCI or USB connection


A more detailed list of installed drivers can be obtained by entering:


{{UserCmd|command=mhwd -l -d}}


A detailed list will provide the following information:


* Name
* Version
* PCI or USB connection
* Description
* Priority
* Free or proprietary
* Dependencies
* Conflicts
* Class ID (e.g. '0300' for graphics card drivers), and
* Vendor ID


In addition, using the ''--pci'' filter in the following example will list detailed information for only the drivers available for devices (e.g. graphics cards) using an internal PCI connection:


{{UserCmd|command=mhwd -l -d --pci}}

== Installing a Driver == 


To install a driver for a graphics card, the syntax is:


{{UserCmd|command=sudo mhwd -i pci [name of driver]}}


A breakdown of the command used to manually install a driver is as follows:


* '''-i''': Install a driver
* '''[pci]''': Install a driver for a device connected internally via pci (e.g. graphics cards)
* '''[name of driver]''': The name of the driver to be installed


For example, to install the proprietary nvidia graphics card driver, the following command would be used:


{{UserCmd|command=sudo mhwd -i pci video-nvidia}}

== Force Reinstall a Driver == 


{{warning|use this command with care!}}


To force the re-installation of an existing driver without removing it first, the syntax is:


{{UserCmd|command=sudo mhwd -f -i pci [name of driver]}}


For example, to force the re-installation of a previously installed nvidia graphics card driver, the following command would be used:


{{UserCmd|command=sudo mhwd -f -i pci video-nvidia}}

= Removing an Installed Driver = 


On occasion it may be necessary to remove an installed graphics card driver. Similarly to manually installing a graphics card driver, two steps should be undertaken for removal:


'''1.''' Identify the installed driver


'''2.''' Remove the identified driver


After all, it would be somewhat difficult to remove an installed driver if you don't know what it's called!

== Identifying Installed Drivers == 


To identify and list Manjaro's installed drivers - including the graphics driver to be removed, the syntax is:


{{UserCmd|command=mhwd -li [optional: detailed view] [optional: pci or usb devices only]}}


Using this command without the additional options will list the basic information of all the drivers currently installed on your system. '''Once again, all drivers for graphics cards will have the prefix (video-) in their name'''. As with listing drivers available for your system, the ''-d'' option used in the following command will list detailed information:


{{UserCmd|command=mhwd -li -d}}


This information may prove useful to determine any otherwise unforeseen consequences or problems upon removing a driver. And again, it is also possible to filter your list of installed drivers by whether they are used on hardware connected via pci or usb. In this instance, a detailed list will be generated only for installed drivers used on hardware with a PCI connection:


{{UserCmd|command=mhwd -li -d --pci}}


One other way of reporting drivers installed andin use is using the {{ic|inxi}} tool.


{{UserCmd|command=inxi -G}}


{{note|The mhwd profile 'video-linux' corresponds to the latest opensource driver availablefor your hardware.}}
{{note|The mhwd profile 'video-vesa' is a generic fallback driver which should not be used in the vast majority of cases.}}

== Removing Installed Drivers == 


{{warning|use this command with care!}}


To remove an installed driver, the syntax is:


{{UserCmd|command=sudo mhwd -r [pci or usb] [name of driver]}}


For example, to remove the installed driver for a nvidia graphics card (connected internally via pci), the following command would be used:


{{UserCmd|command=sudo mhwd -r pci video-nvidia}}

= Checking configuration = 


You can check configuration with:
{{UserCmd|command=sudo mhwd-gpu --check}}
{{UserCmd|command=mhwd-gpu --status}}


And if needed fix issues with:
{{UserCmd|command=sudo mhwd-gpu --setmod}}
{{UserCmd|command=sudo mhwd-gpu --setxorg [PATH]}}


Make sure the path to xorg config file is valid.


Note about ati, xorg file and login artifacts or kicad: if you get artifacts upon logging in or if kicad rendering and zooming is slow, try adding [Option "EXAPixmaps" "off"] in the "Device" section of xorg config file. See [https://wiki.archlinux.org/title/ATI#Performance_and/or_artifacts_issues_when_using_EXA here.]

=Dual GPU= 

==PRIME GPU offloading== 


If your hardware includes more than one GPU card you can make use of PRIME offloading. PRIME is a technology used to manage hybrid graphics found on recent desktops and laptops (Optimus for NVIDIA, AMD Dynamic Switchable Graphics for Radeon). PRIME detects both cards and automatically selects Intel card by default; using the more powerful discrete graphics card, when called, for more demanding applications.


In Manjaro this will automatically be available for hybrid graphics systems using intel/modesetting for the integrated card and free drivers (AMDGPU or Nouveau) for the dGPU.


You may choose to run a program with a specific GPU, prepending the application's command with ''DRI_PRIME=x'', where ''x'' is the card priority number.


For example, to run an application using the second card prepend the application command with '''DRI_PRIME=1'''


{{UserCmd|command=DRI_PRIME=1 glxspheres64}}


To use the 1st card (usually when the CPU has an embedded GPU, this is used)


{{UserCmd|command=DRI_PRIME=0 glxspheres64}}


If you want to always run some application with the discrete gpu, you may copy that application's .desktop file to {{ic|~/.local/share/applications/}} and edit the "Exec" property


{{UserCmd|command=Exec=DRI_PRIME=1 inkscape}}


Some applications (usually games like steam) may have an embedded option to specify the command line, where it is preferred to use this way.


For example, in Steam, select a game - that you want to run using your discrete Nvidia card - from the Library page of the Steam client, right-click, and select Properties.
Click the SET LAUNCH OPTIONS... button and specify for the command line options followed by the default launch hook %command%.


DRI_PRIME=1 %command%


To use the dGPU by default see '''[https://wiki.archlinux.org/index.php/PRIME#Reverse_PRIME Reverse Prime]'''

= NVIDIA Proprietary (non-free) drivers = 


If you have a Nvidia card, you have the option to use the proprietary (closed source = non-free) drivers instead of the open source (free) nouveau driver.


For Legacy/older nvidia cards, Manjaro maintains older drivers for compatibility. In these cases the driver name is different, instead of nvidia it is nvidia-390xx or nvidia340xx, whether in nvidia-only or bumblebee mhwd driver configuration.


When you install the non-free driver, mhwd includes a Nvidia utility "Nvidia Settings Utility" that can help you configure several settings. You can find this utility in your GUI Applications Menu or start it from a terminal


{{UserCmd|command=sudo nvidia-settings}}


If you are using bumblebee, the nvidia utility needs a special command


{{UserCmd|command=sudo optirun -b none nvidia-settings -c :8}}

==Nvidia Optimus== 
For Optimus laptops or dual GPU hardware with intel and nvidia GPUs, you have three options to utilize the card driver usage at your preference or your hardware capabilities.


'''[[#nvidia-prime|PRIME]] (mhwd default)'''


'''[[#Bumblebee|Bumblebee]]'''


When you install Manjaro with the non-free option selected from Grub menu, or when you use automatic driver installation, PRIME or bumblebee is installed by default, depending on support for your GPU, PRIME being preferred. In these cases, the mhwd driver is named "video-hybrid-intel-nvidia-***xx-prime" or "video-hybrid-intel-nvidia-***xx-bumblebee".

==Configure The Resolution/Refresh Rate== 


{{warning|The method provided does not currently work for the Cinnamon Edition. As soon as a solution is found, then this article will be updated.}}


'''1.''' Start nvidia-settings utility


'''2.''' Change resolution and refresh rate in 'X Server Display Configuration' tab.


'''3.''' Hit the 'Save to X Configuration File' button and save to '''/etc/X11/mhwd.d/nvidia.conf'''


'''4.''' Now start your terminal and enter the following command to complete the process:


{{UserCmd|command=sudo mhwd-gpu --setmod nvidia --setxorg /etc/X11/mhwd.d/nvidia.conf}}

==Configure X Screen settings (OpenGL Settings, Antialiasing, X Server XVideo)== 


'''1.''' Start nvidia-settings utility


'''2.''' Change settings in X Server XVideo Settings, OpenGL and Antialiasing, in the 'X Screen' tab.


'''3.''' Click on 'nvidia-settings configuration' tab and click on the 'Save Current Configuration' button.


'''4.''' Save the .nvidia-settings-rc to the default location specified ('''/home/[your account name]''')


'''5.''' Edit the .xinitrc file with your preferred text editor. For example, if you use gedit, run this in your terminal:


{{UserCmd|command=gedit ~/.xinitrc}}


'''6.''' Once opened, add the following line into the configuration file:


{{UserCmd|command=exec nvidia-settings --load-config-only}}


'''7.''' Save and exit.

==Nvidia settings for special cases == 


In case your monitor is not entering powersave mode (DPMS), try adding `Option "HardDPMS" "true"` in your Xorg monitor section. For example:


Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "Unknown"
ModelName "BenQ ZOWIE XL LCD"
HorizSync 30.0 - 160.0
VertRefresh 56.0 - 144.0
Option "DPMS"
Option "HardDPMS" "true"
EndSection


After forum [https://forum.manjaro.org/t/display-does-not-go-to-powersave/84004/5 issue]

==nvidia-prime== 


Manjaro also offers an easy way to use PRIME with proprietary Nvidia drivers.<br>
Simply select and install an 'nvidia-prime' profile through MSM or mhwd (such as ''video-hybrid-intel-nvidia-440xx-prime'') and ensure the package ''nvidia-prime'' is installed.


Then to use the discrete Nvidia card it works the same as [[#PRIME_GPU_offloading|PRIME offloading]] above but uses a different command. Prepend the application command with '''prime-run'''. For example:


{{UserCmd|command=prime-run glxspheres64}}

==Bumblebee== 


Bumblebee configuration is mainly developed to help minimize laptop battery consumption, since Nvidia usually consumes significant power, while Intel cards are more power efficient. So, bumblebee detects both cards and automatically selects Intel card by default and can use the Nvidia for more demanding applications.
For an application to use the Nvidia card, prepend the application command with optirun or primusrun. For example:


{{UserCmd|command=optirun glxspheres64}}
{{UserCmd|command=primusrun inkscape}}


If you want to specifically run some application with the nvidia driver, you may edit that application's .desktop file "Exec" property, or run it in terminal like this


Exec=primusrun chromium


Some applications (usually games like steam) may have an embedded option to specify the command line, where it is preferred to use this way.


For example, in Steam, select a game - that you want to run using your discrete Nvidia card - from the Library page of the Steam client, right-click, and select Properties.
Click the SET LAUNCH OPTIONS... button and specify for the command line options followed by the default launch hook %command%.

primusrun %command%


If you have problems with a bumblebee setup, refer to this [https://forum.manjaro.org/t/bumblebee-troubleshooting-20181229/40584 Forum Tutorial] for advice.

= See also = 


* [[Manjaro Hardware Detection Overview]]

= Easier way = 


You may use a GUI version of mhwd in [[Manjaro Settings Manager#Hardware Detection]]
: With this tool you can:
: - install graphic driver
: - switch graphic driver


https://www.youtube.com/watch?v=UAFGukpEIJw

= How to check the driver = 


{{UserCmd|command=glxinfo | grep OpenGL}}


Example output command:


'''Nvidia driver''' ( proprietary driver )


{{UserCmdOutput|command=glxinfo | grep OpenGL|result= OpenGL vendor string: NVIDIA Corporation<br> OpenGL renderer string: GeForce GTX 660/PCIe/SSE2<br> OpenGL core profile version string: 4.3.0 NVIDIA 331.49<br> OpenGL core profile shading language version string: 4.30 NVIDIA via Cg compiler<br> OpenGL core profile context flags: (none)<br> OpenGL core profile profile mask: core profile<br> OpenGL core profile extensions:<br> OpenGL version string: 4.4.0 NVIDIA 331.49<br> OpenGL shading language version string: 4.40 NVIDIA via Cg compiler<br> OpenGL context flags: (none)<br> OpenGL profile mask: (none)<br> OpenGL extensions:}}


'''Nouveau''' , '''Gallium''' from '''Mesa''' ( open source driver )


{{UserCmdOutput|command=glxinfo | grep OpenGL|result= OpenGL vendor string: nouveau<br> OpenGL renderer string: Gallium 0.4 on NVE6<br> OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.5<br> OpenGL core profile shading language version string: 1.40<br> OpenGL core profile context flags: (none)<br> OpenGL core profile extensions:<br> OpenGL version string: 3.0 Mesa 9.2.5<br> OpenGL shading language version string: 1.30<br> OpenGL context flags: (none)<br> OpenGL extensions:}}


'''Intel''' driver from '''Mesa''' ( open driver )


{{UserCmdOutput|command=glxinfo | grep OpenGL|result= OpenGL vendor string: Intel Open Source Technology Center<br> OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Desktop<br> OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.0.6<br> OpenGL core profile shading language version string: 3.30<br> OpenGL core profile context flags: (none)<br> OpenGL core profile profile mask: core profile<br> OpenGL core profile extensions:<br> OpenGL version string: 3.0 Mesa 11.0.6<br> OpenGL shading language version string: 1.30<br> OpenGL context flags: (none)<br> OpenGL extensions:<br> OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.0.6<br> OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00<br> OpenGL ES profile extensions:}}

</translate>
[[Category:Contents Page]]

Set all Java apps to use GTK+ font & theme settings

2023-01-16T18:29:44Z

Oguzkagan: removed dead link

<languages/>
__TOC__

{{SectionTemplate|<translate> Introduction</translate>|2=
<translate>

This fix makes your Java apps use your GTK+ theme (colours & such) & your chosen font settings. Here is how it looks like:


{{FlexSideContainerTemplate|
[[File:Java_default_look.png|thumb|none|400px|Before the fix]]
|
[[File:Java_GTK_look.png|thumb|none|400px|After the fix]]
|1|1}}
</translate>}}

{{SectionTemplate|<translate> How do you do it?</translate>|2=
<translate>

Set the variable '''_JAVA_OPTIONS''' by running this command in a terminal:


export _JAVA_OPTIONS="-Dawt.useSystemAAFontSettings=on -Dswing.aatext=true -Dswing.defaultlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel -Dswing.crossplatformlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel ${_JAVA_OPTIONS}"


First test to see if the outcome is what you expect by running your Java app from the same terminal window.


If the result looks good to you, let us make the changes permanent:


Append the above definition of the '''_JAVA_OPTIONS''' variable to '''~/.profile''' (for your user only) or '''/etc/profile.d/90-java_ops.sh''' (system-wide). In both cases, if the file does not exist, create it.
</translate>
}}

{{SectionTemplate|<translate> See Also</translate>|
<translate>

* [http://askubuntu.com/questions/21886/how-can-i-get-a-java-apps-to-use-the-gtk-theme How can I get a java apps to use the GTK+ theme?(askubuntu)]
</translate>
[[Category:Contents Page{{#translation:}}]]

Desktop Environments and Window Managers

2023-01-16T18:28:42Z

Oguzkagan: changed dead link

<languages/>
__TOC__

{{SectionTemplate|<translate> General</translate>|
<translate>

A desktop environment (DE) is an implementation of the desktop metaphor made of a bundle of programs which share a common graphical user interface (GUI).<br />
It is sometimes described as a graphical shell.


With manjaro you can use many desktop environments. Both Official and Community ISO's of various DE's are available.<br />
You can download them here:
</translate>

{{FlexSideContainerTemplate|
<translate>

* [https://manjaro.org/download/ Official Editions]
:''Including: Gnome, KDE, and XFCE.''
</translate>
|
<translate>

* [https://manjaro.org/download/ Community Editions]
:''Including: Budgie, Cinnamon, i3, Mate and Sway.''
</translate>
|1|1}}

<translate>

If you are feeling adventurous and want to install additional DEs or WMs you can reference these guides:


* [[Special:MyLanguage/Install Desktop Environments|Install Desktop Environments and Window Managers]]
:''Choose from a wide selection available in our repositories!''
</translate>

}}



{{SectionTemplate|
<translate> [[File:awesome-logo.png|left|36px]]</translate>
<translate> Awesome</translate>|
{{FlexSideContainerTemplate|
<translate>

Slim and snappy tiling window manager with the focus on resource efficiency suitable for power users. This edition is supported by the Manjaro community and comes with Awesome, a highly configurable, next generation framework window manager for X. Awesome is a slim and snappy tiling window manager with the focus on resource efficiency.
</translate>
|[[File: Awesome-wm-18.png|450px]]}}
|}}



{{SectionTemplate|
<translate> [[File:budgie-logo.png|left|36px]]</translate>
<translate> Budgie</translate>|
{{FlexSideContainerTemplate|
<translate>

* [[Special:MyLanguage/Budgie|Budgie]]
: ''The main Budgie article''
</translate>|[[File: Budgie-de-18.jpg|450px]]}}
|}}



{{SectionTemplate|
<translate> [[File:cinnamon-logo.png|left|36px]]</translate>
<translate> Cinnamon</translate>|
{{FlexSideContainerTemplate|
<translate>

For people who look for a traditional desktop with modern technology.


This edition is supported by the Manjaro community and comes with Cinnamon, a desktop based on modern technology that keeps known and proven concepts.
</translate>
|[[File: Cinnamon-de-18.png|450px]]}}
|}}



{{SectionTemplate|
<translate> [[File:Deepin-logo.png|left|36px]]</translate>
<translate> Deepin</translate>|
{{FlexSideContainerTemplate|
<translate>

* [[Special:MyLanguage/Deepin|Deepin]]
: ''The main Deepin article''
</translate>
|[[File: Deepin-de-18.jpg|450px]]}}
|}}





{{SectionTemplate|
<translate> [[File:Desktop-environment-gnome.png|left|36px]]</translate>
<translate> Gnome</translate>|
{{FlexSideContainerTemplate|
<translate>

* [[Special:MyLanguage/GNOME|GNOME]]
: ''The main GNOME article''
</translate>
|[[File: Gnome-de-18.jpg|450px]]}}
|}}



{{SectionTemplate|
<translate> [[File:i3-logo.png|left|36px]]</translate>
<translate> i3</translate>|
{{FlexSideContainerTemplate|
<translate>

Lightweight tiling window manager, famous for its efficiency with screen space and keyboard controlled workflow. The ideal environment for text and terminal focused usage.


This edition is supported by the Manjaro community and comes with i3, a tiling window manager.


I3 is an extremely lightweight tiling window manager, famous for its efficiency with screen space and keyboard controlled workflow. The ideal environment for text and terminal focused usage.
</translate>
|[[File: i3-wm-18.png|450px]]}}
|}}



{{SectionTemplate|
<translate> [[File:About_kde.png|left|36px]]</translate>
<translate> KDE</translate>|
{{FlexSideContainerTemplate|
<translate>

* [[Special:MyLanguage/KDE|KDE]]
: ''The main KDE article''


* [[Special:MyLanguage/Dolphin|Dolphin File Manager]]
: ''All about the Dolphin file manager''
</translate>
|[[File: KDE-de-18.jpg|450px]]}}
|}}



{{SectionTemplate|
<translate> [[File:lxde-logo.png|left|36px]]</translate>
<translate> LXDE</translate>|
{{FlexSideContainerTemplate|
<translate>

Lightweight desktop build using the GTK toolkit


Manjaro LXDE provides a lightweight GTK desktop environment. In addition to LXDE itself it comes with Manjaro Hello and the integrated Application utility, providing quick access to popular applications. Additionally the Kvantum theme manager is provided to provide consistent theming for both QT and GTK applications.


This edition is supported by the Manjaro community and uses Openbox Window Manager.
</translate>
|[[File: lxde-de-17.png|450px]]}}
|}}


{{SectionTemplate|
<translate> [[File:lxqt-logo.png|left|36px]]</translate>
<translate> LXQt</translate>|
{{FlexSideContainerTemplate|
<translate>

* [[Special:MyLanguage/LXQt|LXQt]]
: ''The main LXQt article''


* [[Special:MyLanguage/List of Qt Applications|List of Qt Application]]
: ''Extensive list of Qt4 and Qt5 applications.''


* [[Special:MyLanguage/PCmanFM-Qt|PCmanFM-Qt]]
: ''PCManFM-Qt, the LXQt file browser''
</translate>
|[[File: lxqt-de-18.png|450px]]}}
|}}



{{SectionTemplate|
<translate> [[File:mate-logo.png|left|36px]]</translate>
<translate> MATE</translate>|
{{FlexSideContainerTemplate|
<translate>

For people who look for a traditional experience


This edition is supported by the Manjaro community and comes with Mate, a desktop environment that continues the legacy of traditional user experience while carefully improving and modernizing it when needed.
</translate>
|[[File: Mate-de-18.png|450px]]}}
|}}


{{SectionTemplate|
<translate> [[File:openbox-logo.png|left|36px]]</translate>
<translate> Openbox</translate>|
{{FlexSideContainerTemplate|
<translate>

* [[Special:MyLanguage/Openbox|Openbox]]
: ''Openbox, the customizable standards-based Window Manager''
</translate>
|[[File: Openbox-wm-18.jpg|450px]]}}
|}}



{{SectionTemplate|
<translate> [[File:Sway_logo.png|left|36px]]</translate>
<translate> Sway</translate>|
{{FlexSideContainerTemplate|
<translate>

For wayland fanatics and ⌨ keyboard enthusiasts.


This edition is supported by the Manjaro community and comes with Sway. Sway is a tiling Wayland compositor based on wlroots.


Please refer to the manjaro sway github repository for downloads, issues, frequently asked questions and if you’d like to contribute.
</translate>
|[[File: Sway_desktop.png|450px]]}}
|}}



{{SectionTemplate|
<translate> [[File:Start-here-xfce.png|left|36px]]</translate>
<translate> XFCE</translate>|
{{FlexSideContainerTemplate|
<translate>

* [[Special:MyLanguage/Keyboard_Shortcuts#Keyboard_Shortcuts_in_XFCE|Making Keyboard Shortcuts for Frequently Used Applications]]
: ''Become a keyboard ninja to speed things up!''


* [[Special:MyLanguage/Using Compton for a tear-free experience in Xfce|Using Compton for a tear-free experience in Xfce]]
: ''For those who are facing screen tearing issues.''


* [[Special:MyLanguage/Volume Stuck on Mute (XFCE Desktop)|Volume Stuck on Mute (XFCE Desktop)]]
: ''Two possible solutions for an issue that affects some users of the XFCE desktop environment.''


* [[Special:MyLanguage/Improve Font Rendering|Improve Font Rendering]]
: ''A way to optimise font rendering.''
</translate>
|[[File: xfce-de-18.jpg|450px]]}}
|}}

[[Category:Contents Page{{#translation:}}]]
[[Category:Desktop{{#translation:}}]]

Burn an ISO File

2023-01-16T18:27:16Z

Oguzkagan: removed dead link

<languages/>
__TOC__
<translate>
==Overview== 
As outlined in the '''[[Special:MyLanguage/Download Manjaro| Download Manjaro page]]''', an ISO is not simply a 'drag and drop' or 'copy and paste' duplication of Manjaro's installation files. It is in fact a copy of the raw computer code that makes up the files themselves. This is why it is necessary to use a '''software burning application''' to 'burn' an ISO file, that is, convert its raw code into the files onto a physical medium such as a DVD or USB flashdrive / datastick in order to use it. Once burned / converted, the files on that medium can then be used to run Manjaro directly without having to install it to your system (referred to as ''Live-CD or Live-USB'' mode), and/or install Manjaro on your system. Again however, it will not be necessary to to burn an ISO if you intend on running Manjaro in a virtual machine environment using Oracle's Virtualbox. This is because Virtualbox is able to read ISO files directly as ''virtual disks''.
{{BoxInfo|note|Manjaro will not have full functionality when run in Live-CD mode. For example, you will not be able to save any changes to the system, or install updates or new applications.}}

===Burning to CD/DVD in Linux=== 
{{BoxSuccess|tip|It is strongly recommended to select the slowest speed available when burning to disc in order minimise the possibility of corruption during the burning process.}}


Several different software burning applications - if not already installed - should be available for installation from your distribution's Software Center / Software Manager / Package Manager / repositories. Popular burners include ''XFBurn'', ''K3b'', and ''Brasero''. Which one you may choose is entirely down to personal choice. However, a guide to burning your downloaded Manjaro ISO using Brasero has been provided below:
[[file:Brasero.png|thumb|left|375px]]


'''1.''' Insert a Blank CD/DVD (use a DVD if burning an ISO for anything other than the NET Edition)


'''2.''' Start the Brasero software burner


'''3.''' Click the '''Burn Image - Burn an existing CD/DVD image to disc''' button to open the ''Image Burning Setup'' window.


'''4.''' Click the button beneath the title '''Select a disc image to write''' to open up your file manager. Locate and double-click the downloaded ISO file to load it. Upon automatically returning to the ''Image Burning Setup'' window, note that the ISO file is now listed as the disc image to write.


'''5.''' Underneath the title '''Select a disc to write to''' the blank CD/DVD inserted should already have been automatically listed. Otherwise, click the button to select it manually.


'''6.''' Click the '''properties''' button to open the ''properties window'', and then click the button beneath the title '''Burning Speed'''. Again, it is strongly recommended to select the slowest speed available. Once selected, click the '''Close''' button.


'''7.''' Click the '''Burn''' button to start the burning process. If necessary, follow any on-screen instructions provided.

===Burning to a CD/DVD in Windows=== 
In Windows 7 and later, support for burning an ISO to DVD is built-in. Simply right click on the on .iso file and select "Burn disk image". This will bring up a series of dialogues to walk you through the process.


For Windows Vista or older versions of Windows you will need to download 3rd party software. Several free software burner applications are available for Windows. One such tool is DeepBurner. The portable version can be downloaded from [https://pendriveapps.com/deepburner-portable/ here].

===Writing to a USB Stick in Linux=== 
This section describes how to write a Linux ISO file to USB.


Windows ISO files are notoriously difficult and requires special attention.

===Using the Terminal=== 
To burn the iso on an usb stick, enter the following command in a terminal :


{{UserCmd|command=sudo dd bs=4M if=/path/to/manjaro.iso of=/dev/sd[drive letter] status=progress oflag=sync}}


Where [drive letter] is the letter of your removable device. Please note that it is the '''device''' (e.g. /dev/sdb), and '''not''' the partition number (e.g. /dev/sdb1).


To find which drive letter it might be write:


{{UserCmd|command=sudo fdisk -l}}


{{BoxWarning|Warning|Not all ISO are isohybrid ! However you can create isohybrid ISO. If you use very old hardware and rare, may not support isohybrid. Isohybrid created for UEFI should work with "Legacy mode", without support UEFI not will work on UEFI. Before use USB stick check Bios/UEFI settings, USB should start first. If isohybrid not working for you with uefi, try create isohybrid for own use without this option.}}

===How you can check ISO=== 
{{UserCmd|command=fdisk -l}}


: Example:


{{UserCmd|command=fdisk -l manjaro-mate-15.12-x86_64.iso
Disk manjaro-mate-15.12-x86_64.iso: 7,5 GiB, 8006074368 bytes, 15636864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000}}


{{UserCmd|command=fdisk -l manjaro-xfce-16.08-x86_64.iso
Disk manjaro-xfce-16.08-x86_64.iso: 1,5 GiB, 1561657344 bytes, 3050112 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x06c2dccb
.
Device Boot Start End Sectors Size Id Type
manjaro-xfce-16.08-x86_64.iso1 * 0 3050111 3050112 1,5G 0 Empty
manjaro-xfce-16.08-x86_64.iso2 224 63711 63488 31M ef EFI (FAT-12/16/32)}}


: Isohybrid have 2 partitions, you can check also with gparted after burn the iso on an usb stick.

===How create isohybrid=== 
{{UserCmd|command=isohybrid -v /path/to/name.iso}}


: or for UEFI
{{UserCmd|command=isohybrid --uefi -v output.iso}}


: More in http://www.syslinux.org/wiki/index.php?title=Isohybrid

===Using a Burning Application=== 
====ImageWriter====
ImageWriter should be available for installation from your distribution's Software Center / Software Manager / Package Manager / repositories. Once Imagewriter has been downloaded and installed, ensure that your USB stick is plugged in before starting it.


A brief guide to writing the Manjaro .ISO image has been provided:


'''1.''' Click on the centre icon


'''2.''' Navigate to where the ISO image has been saved and select it


'''3.''' Ensure that your USB device has been selected from the drop-down menu


'''4.''' Click on the '''Write''' button


'''5.''' After the '''Write''' process has finished, reboot your system

===Writing to a USB Stick in Windows=== 
====Using Rufus====
[http://rufus.ie/ Rufus] Rufus is a utility that helps format and create bootable USB flash drives, such as USB keys/pendrives, memory sticks, etc.


When you use Rufus to write a Manjaro Live ISO to USB you must select DD mode when prompted to use standard or DD mode.


See its website for more details: [http://rufus.ie/]

===Writing to a USB Stick on a Macintosh=== 


As a Unix variant, macOS uses a similar approach to Linux. All commands below should be run in the '''Terminal''' application. Commands using '''sudo''' may prompt for your password; this is expected.


After you've inserted your USB drive, identify it using '''diskutil''':
{{UserCmd|command=diskutil list}}
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk1 1000.0 GB disk0s2
/dev/disk3 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *7.8 GB disk3
1: Windows_NTFS MYUSBDRIVE 7.8 GB disk3s1


Note the identifier '''disk3s1''' in this example.


Unmount the drive with the command:
{{UserCmd|command=sudo diskutil unmount /dev/disk3s1}}
Volume MYUSBDRIVE on disk3s1 unmounted


Now you can use '''dd''' to write to the raw device:
{{UserCmd|command=sudo dd bs=4M if=Desktop/manjaro-i3-21.2.3-220205-linux515.iso of=/dev/disk3}}
787+1 records in
787+1 records out
3303161856 bytes transferred in 2470.782563 secs (1336889 bytes/sec)


The USB drive can now be removed from the computer and used to boot Manjaro.

==See Also== 
* '''[[Special:MyLanguage/Download Manjaro| Download Manjaro]]'''
* '''[[Special:MyLanguage/Check a Downloaded ISO Image For Errors| Check a Downloaded ISO Image For Errors]]'''
* '''[[Special:MyLanguage/Installation Guides| Installation Guide]]'''
</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ISO{{#translation:}}]]

Make GRUB menu & boot-up/down fonts bigger

2023-01-16T18:26:27Z

Oguzkagan: removed dead link

<languages/>
__TOC__
{{BoxWarning|<translate> Warning</translate>|<translate>

This page is outdated. If you have checked or updated this page and found the content to be suitable, please remove this notice. 2020-12-06</translate>}}
{{BoxInfo|1=<translate> Note</translate>|
2=<translate>

12-Feb-17 : We used to have to, but now we no longer need to, add consolefonts to the end of the HOOKS= line in our mkinitcpio.conf file.


As the collection of all the X.Org Server protocol headers formerly
distributed as separate, standalone packages have been rolled up into
Xorgproto: [https://www.phoronix.com/scan.php?page=news_item&px=Xorgproto-Debut-Release] So if you have used this how-to to enlarge your boot up/down
process fonts, you should edit your /etc/mkinitcpio.conf file & remove
consolefonts from the end of the HOOKS= line.


If you don't make this suggested edit, it won't cause you any problems,
besides seeing an error message saying (roughly) that consolefonts can't
be found, whenever you upgrade your kernel via the terminal.
</translate>}}

{{SectionTemplate|
1=<translate> Introduction</translate>|
2=<translate> If you use a high DPI resolution '''&''' you want to more easily read your display during the boot process (both up & down), '''&''' you '''don't''' have an extremely fast booting system (use SSD & the like), then this page will show you how to make both the GRUB menu fonts larger & how to change the console font used in the display of the boot up/down processes. This is all primarily for those users that place some value in being able to see/read the boot up/down displays, when they are live. The how-to endeavors to cater to both SystemD & OpenRC users.</translate>
}}

{{SectionTemplate|
1=<translate> What are we going to do here</translate>|
2=<translate>
This how-to is really a two in one, as the first part is about enlarging the font used by the GRUB menu & the early phase of the boot process up until the GPU driver loads.


The second part is about first identifying the GPU module to load, & then using the Kernel Mode Setting (KMS) ability of the Linux kernel to instruct it to load modules extremely early in the boot process. Which is what we will do with the GPU module via the /etc/mkinitcpio.conf file. Then finishing off that process by rebuilding the initial ramdisk image.


After that we need to find where the consolefonts directory is & if need be clone the /usr/share/kbd/consolefonts directory to /usr/share/consolefonts. After that we need to choose a font, though I'll endeavor to make that as quick & painless as possible. Then we need to tell the /etc/conf.d/consolefont file what that font is, save & reboot to a new situation where we are able to actually read the text as it goes by. That's the plan.</translate>
}}

{{SectionTemplate|
1=<translate> Give GRUB & the boot process up to the GPU module load a larger font</translate>|
2=<translate>

This one requires you to choose a font that you like (mono fonts are easiest to read), I chose DejaVuSansMono20 & here is the command line that creates this font in a GRUB compatible format, in the size that you have chosen & places it in the newly created /boot/grub/fonts directory (its a long command & it is ALL on one line):


sudo grub-mkfont --output=/boot/grub/fonts/DejaVuSansMono20.pf2 \ --size=20 /usr/share/fonts/TTF/dejavu/DejaVuSansMono.ttf


Then we need to open the /etc/default/grub file in our text editor as root (use sudo) & add the following line (or lines if your like me & have a bad memory):


##==========================_HANDY_==========================================
# More readable font on high dpi screen, generated with the following
# 2 lines on ONE line, terminal command (ignore the error messages it works!:
# sudo grub-mkfont --output=/boot/grub/fonts/DejaVuSansMono24.pf2 \
# --size=24 /usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf
##===========================================================================

GRUB_FONT=/boot/grub/fonts/DejaVuSansMono18.pf2


Save the edited file & then enter the following at the Terminal prompt:


sudo update-grub


Having done that, if you reboot the GRUB menu will be bigger & so will a shortish portion of the boot process, up until the GPU driver kernel module is loaded, where you'll go back to the default console font.
</translate>
}}

{{SectionTemplate|
1=<translate> Use KMS to load the GPU kernel module early in the boot process</translate>|
2=<translate>

Use sudo & load /etc/mkinitcpio.conf into your text editor & find the '''MODULES=""''' line very near the top of file. Here you will have to put your GPU module name, the three choices that I can show you here are:


'''Intel on-board''' (at least all of the intel CPU's that carry a GPU/CPU):


MODULES=(i915)


'''AMD/ATi''':


MODULES=(radeon/amdgpu)


'''nVidia free''':


MODULES=(nouveau)


'''nVidia proprietary''':


MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)


If your MODULES= line has any other modules on it already, just add your new one with a space separating it from the previous one.


You can save & close the file.


For our next trick, we have to identify which kernel branch you are using. Most people will be using an older; more recent; or the most recent, version of the "normally" supported kernel. Such shows itself in the /boot directory like so:


initramfs-linux-fallback.img
initramfs-linux.img
vmlinuz-linux


& would therefore use the following command to rebuild their Init Ramdisk Image:


sudo mkinitcpio -p linux


For those that are using the/a Linux Long Term Support kernel then their identifying /boot files will look like this:


initramfs-linux-lts-fallback.img
initramfs-linux-lts.img
vmlinuz-linux-lts


& would therefore use the following command to rebuild their linux-lts Init Ramdisk Image:


sudo mkinitcpio -p linux-lts


For those using more exotic kernels, you already know how to modify the above command to suit.


For Manjaro users that are using multiple kernels, you are going to need to edit multiple mkinitcpio.conf files that are named to suit each of your kernels. I don't have to bother with that on Artix (Arch/OpenRC), for better & worse. Again, your /boot directory will tell you what to do (as shown in the differences in the examples above).
</translate>
}}

{{SectionTemplate|
1=<translate> Use the /usr/share/consolefonts directory to enlarge your boot up/down font</translate>|
2=
{{note|<translate> I look forward to cleaning up this section.</translate>}}
<translate>
On Artix, I had to copy the /usr/share/kbd/consolefonts/ directory into /usr/share/consolefonts . Whether I could have used the /usr/share/kbd/consolefonts directory in place or not I don't know (I didn't try). The /etc/conf.d/consolefont file uses the /usr/share/consolefonts path, so I made one.


So the first thing that you have to do (before I find out from someone in the Manjaro forum where the consolefonts directory exists) is see whether you have to clone the directory from /usr/share/kbd/ to /usr/share/ or not. After that is sorted, then you need to choose a font. You won't like doing that. Here is a link to an old page (far fewer suitable fonts & its still too many)


Take my advice & use '''ter-132b''' this is a font that is large enough for my 15" 1440p display. I expect that it would be great on a 24" 1080p display. If it is too big, you can use a smaller number as will be easily seen in your consolefonts directory.


To tell the kernel to use the chosen custom console font you will need to open the /etc/conf.d/consolefont file & comment out (use the '''#''' at the start of the line) any line that says:


consolefont=


Then add your own line. This is what I did:


consolefont="ter-132b"


You need to make no other edits to this file, so close it.


Now from what I can make out on the ArchWiki font page: [https://wiki.archlinux.org/index.php/Fonts#Console_fonts] The above how-to should work on SystemD, as is. I will check on the Manjaro forum & if & where needed modify this page (there shouldn't be much in it as both systemd & openrc use the same kernel).


For Artix (Arch/OpenRC) users, you would need to just once use the following command:


sudo rc-update add consolefont boot


Hopefully I haven't forgotten anything, as this is has been a multi-step process & I lost power & a good deal of the wiki page some time ago & had to do it twice! ;)


This page is still a work in progress & will be polished up as soon
as I'm given the info' that I need via the Manjaro forum. ;)</translate>
}}

[[Category:Contents Page{{#translation:}}]]
[[Category:Outdated Page{{#translation:}}]]

Using Manjaro for Windows users

2023-01-16T18:24:51Z

Oguzkagan: dead link

[[File:Page Under Construction.jpg|thumb|center|Page under construction]]

__TOC__

Remember when you installed your very first Windows, added bells and whistles and then couldn’t see the wood for the trees any more and had to re-install???
Well, ''you’re in the same situation now:'' '''You’re a N00b again! Embrace it!''' 😇

I know right now you’re thinking: ''Why is this so much more difficult than Windows?''
Whereas in 6 months time, you’ll be like: ''Why can't I make Windows jump through fiery hoops like I do with Linux???''

== Windows has drives, Linux has a hierarchical file system ==
So Windows has drives:
* The C:-drive generally contains Windows and sometimes data
* The D:-drive (if present) contains data and hardly ever contains Windows itself.
* The maximum number of drives is 26 (A-Z)
* All drives that contain a known file system are always [[mounted]] automatically.

On the other hand, Linux has ''one huge file system:''
* with an unlimited number of partitions (not disks, not drives!) ¹
* you can mount any partition of a disk anywhere in the file system! (Repeating that you cannot mount a disk, only a partition under Linux!)
* you can find the official documentation on the Linux File System Hierarchy Standard (FHS) in HTML / PDF / Text format here: [https://refspecs.linuxfoundation.org/FHS_3.0/index.html FHS] '''Homework assignment #1: read that!''' 😁
* No, really: read it!
* OK, you didn't read it; here's the [[FHS summary]] 😜

{{note|Partitions are not automatically mounted in Linux!}}
''Huh? That sounds dumb! Why doesn't Linux mount partitions automatically???''
That's because the Manjaro installer will ''manually'' mount only the absolute minimum number of partitions to get your system up and running!
I.E. It will manually mount:
* / (always)
* /home (if you created such a partition)
* /boot/efi (If you have an UEFI system instead of a BIOS system)

''and it will leave any other partitions alone to ensure you don’t mess them up!''
I.E. If you have a dual-boot system, Manjaro will not mount your Windows D: drive automatically!

If you want to have any other partitions available at every boot, you should read about [[fstab]].

== Linux has multiple GUIs ==
Windows has ''only one'' Graphical User Interface ([https://en.wikipedia.org/wiki/Graphical_user_interface GUI]) depending on its version whereas,
Linux has different Desktop Environments (DE) :
* XFCE: Lightweight, simple, best for beginning users
* KDE: lots of bells and whistles, good for recent and powerful hardware ''and people who like to tinker!'' 🛠️
* Gnome: Simple, the default for lots of distributions
* Cinnamon: <s>Gnome like it should be</s> Beefed-up Gnome with more bells and whistles.
* LXDE: comparatively low resource requirements. This makes it especially suitable for use on <s>older</s> resource-constrained computers.
* I3: Great for power users that need non-overlapping titling windows.

And all of the above come with their own:
* File Manager
* System Settings (Known to you as "Control Panel")
* Partition Manager (except XFCE: they need one of the others to be installed)
{{note|The above is less important on modern computers and has become more a matter of taste than functionality}}

'''What you should remember is that mixing and matching DE's is not wise!'''
More specifically:
* Don't install the Gnome Editor (`gedit`) on KDE but use `kate` instead because `gedit` will pull in a ton of libraries (and functionality) of Gnome which will bloat your system.
* Don't install 2 DEs for one user:
* You ''can'' have different DEs on a single computer
* Each user can have their own DE
* '''Having 2 DEs for one user is a recipe for disaster as one single configuration file might be used by 2 DEs for wildly different functionality''' and untangling this Gordian knot will be so complex that a reinstall is always easier.

'''Remember:''' ''You're a N00b again! You're going to re-install'' '''at least once!''' (Unless you're smarter than the authors of this article... 😁)

== Linux has multiple file systems ==
Windows has one file system: NTFS (and if you include the DOS FAT file system it has two. **²**)

Linux has:
* [https://en.wikipedia.org/wiki/Ext2 EXT2], [https://en.wikipedia.org/wiki/Ext3 EXT3], [https://en.wikipedia.org/wiki/Ext4 EXT4]: If you're unsure, take EXT4 as that is the newest member of that family and the most used Linux File System (FS) on desktops.
* [https://en.wikipedia.org/wiki/Btrfs BtrFS]: "Better FS" is good for servers or if you have a beefy computer and want FS resilience
* [http://en.wikipedia.org/wiki/ReiserFS ReiserFS]
* [http://en.wikipedia.org/wiki/ZFS ZFS]
* ''And even more than you'll ever need''
* ''And guess what?'' Linux can also read and write to [https://en.wikipedia.org/wiki/NTFS NTFS] 👍 although it cannot do CHKDSKs, defrag such volumes nor can it change its permissions 👎 , so *before* you finally wipe Windows from your machine,''please, please, please'' first convert any NTFS volumes to EXT4 or any other Linux FS you're comfortable with!

{{note|And remember to `mount` (see above) file systems before you access them, because your file manager *might* automount them read-only for you (which is not always what you want/need)😊}}

== Linux has multiple kernels ==
Windows has different versions and each version has its own kernel. So basically Windows has one kernel for Windows 8, one for Windows 10 another for Windows 11, ...
(One of the authors of this wiki distinctly remember saying about Windows Version 1.0: ''Huh, what a piece of crap, that'll go nowhere! Let me buy SideKick instead!'' and history proved him wrong...) 😁

Linux can have multiple [https://en.wikipedia.org/wiki/Kernel_(operating_system) kernel]s and please remember that:
* LTS = Long Term Support = ultra-stable
* Stable = Stable ''Development'' Kernel
* RC = Release ''Candidate'' = '''''Unstable''''' development kernel
* Keep an eye out on the End Of Life (EOL) dates for LTS kernels [https://www.kernel.org/category/releases.html here] and for non-LTS kernels [https://www.kernel.org here]

It's always a good idea to have ''at least one'' Long Term Support (LTS) kernel installed

It's always a good idea to have ''at least one'' '''fall-back kernel''' installed. E.G. In the case of 5.10 LTS, that would be 5.4 LTS; in the case of 5.14 Stable, that would be 5.10 LTS; ...

It's '''only''' a good idea to have a non-LTS kernel installed if:
* you have very new hardware and none of the LTS kernels work for you. [["What should I be aware of if I'm not on an LTS kernel?"]]
* you're a developer and want to test your applications with the latest ''but not necessarily greatest'' kernels out there.
* the whole point of having Manjaro is to test out new things like new kernels and filing bugs with the developers that don't have your technical knowledge.
* to install different kernels, use the `kernel` [https://en.wikipedia.org/wiki/Graphical_user_interface GUI] program or the `mhwd-kernel` [https://en.wikipedia.org/wiki/Command-line_interface CLI] program.
* E.G. to install the latest LTS kernel at the time of this writing execute:

mhwd-kernel --install linux510

{{note|To compare this to Windows would be to say that if Windows were Linux it would allow you to run the Windows 11 shell on the Windows XP kernel or the other way around or any other bizarre combination *you as the administrator* wanted!👏}}

== Linux doesn’t have a registry! ==
OK, OK: the Gnome DE (Desktop Environment, see above) has something called "the dconf database" which is similar to but different from the registry, mostly used for the DE itself whereas most applications will still use config files. (see below)
All other DEs have config files, 'just like all Windows versions prior to Windows 95':
* system config files are located in `/etc`
* user config files are in `~/.config`:
* `~` is an abbreviation for "your home directory"
* `.config` is a ''hidden'' directory: (I.E. Any directory starting with a `.` is hidden and you probably have to press <kbd>Ctrl</kbd>+<kbd>H</kbd> in your DE's File Manager to see these.)
* Application config files ''can reside somewhere else'' though that happens rarely..

== What’s the difference between BIOS and UEFI? ==
All that good stuff is explained in our [[BIOS_and_UEFI]] section.

== The terminal is your best friend! ==
== This is how you install software in Linux ==
== The Community side of Linux ==
=== Linux is a self-help OS ===
=== You're part of a community now! ===
=== What is this 'Upstream' and 'Downstream" business? ===
== Other tips and tricks ==



<translate>

<tvar|usercmd1>{{UserCmd|command=1.example command should be here}}</>
<tvar|usercmd2>{{UserCmd|command=2.example command should be here}}</>





<tvar|usercmdoutput1>{{UserCmdOutput|command=command|result=<pre>result</pre>}}</>
</translate>



=See Also=
[https://refspecs.linuxfoundation.org/FHS_3.0/index.html FHS] The Official documentation by the Linux Foundation (Yeah: where Linus Torvalds lives) 😊

[[Category:Contents Page{{#translation:}}]]

Installation Guides

2023-01-16T18:13:21Z

Oguzkagan: removed outdated guides

<languages/>
__TOC__
{{SectionTemplate|
<translate> [[File:BigManjaroIcon.png|left|36px]]</translate>
<translate> Overview</translate>|

<translate>

{{BoxSuccess|tip|For best results, please ensure that Manjaro is connected to the internet prior to starting the installation process.}}
</translate>

<translate>

Installation guides for every release of Manjaro have been provided below for both beginners and experienced users. These guides may also be used to install Manjaro as a main operating system, or within a virtual machine environment using '''[https://www.virtualbox.org/ Oracle's Virtualbox]'''. Rebooting your computer (or starting your virtual machine) after connecting your installation media should be sufficient to start the process. If you find that your computer continues to boot into your existing operating system despite this, then check that:


* The ISO Download and/or installation media has not been corrupted, and that
* Your disc drive or USB flash-drive, depending on which you are using to install, is listed higher up in the boot order than your hard drive, which means that it will be booted from first.


Checking and amending your boot order, if necessary, will require either going into your computer's ''BIOS settings'', if installing Manjaro as your main operating system,
or into Virtualbox's ''System Settings'' if installing in a virtual machine.</translate>

<translate>

{{BoxInfo|note|If you already have an existing /home partition be sure to read [[Partitioning_Overview_and_Existing_Partition_Tables#Where_Using_an_Existing_Linux_Partition_Table|this section]] of the wiki first}}</translate>
}}

{{SectionTemplate|
1=<translate> Guides</translate>|
2={{FlexSideContainerTemplate|
<translate>


* [[UEFI - Install Guide]]
: ''If your machine's motherboard runs UEFI/EFI you should read this guide. ''


* [[Important hidden .dot files in your home partition]]
: ''These files can save your time when reinstalling or installing a new distro.''|


* [[Partitioning Overview and Existing Partition Tables]]
: ''Basic overview of partition structure, & useful pointers re. existing partitions. Look here if you have an existing /home partition for options re. your existing config files''.


* [[cfdisk Basic Partitioning Scenarios]]
: ''How to create two or three partition schemes to install Manjaro''.
</translate>
|1|1}}
}}

{{SectionTemplate|
<translate> [[File:Chmsee-icon.png|left|36px]]</translate>
<translate> See Also</translate>|
<translate>

* '''[[Download Manjaro]]'''
* '''[[Check a Downloaded ISO Image For Errors]]'''
* '''[[Burn an ISO File]]''' </translate>}}

[[Category:Contents Page{{#translation:}}]]

"What should I be aware of if I'm not on an LTS kernel?"

2022-12-03T17:22:36Z

Oguzkagan: removed emoji

<languages/>
<translate>
== What should I be aware of if I'm not on an LTS kernel? == 
* "Stable"and "Release Candidate" (RC) kernels are *Development* kernels
* They have the newest, shiniest features but are not as rock-solid as LTS kernels
* These kernels become End of Life (EOL) much quicker than LTS kernels, so you should keep an eye on:
1. The Manjaro #announcements
OR
2. Linus Torvald's [https://kernel.org kernel page] to know when your shiny new genie will go "poof" back into its bottle. 🧞 🪔
* If you're on a RC kernel, update frequently and stay on that kernel once it becomes stable
* If you're on a Stable kernel, install a higher version Stable kernel ''the moment it gets releases as '''Stable''''' (so don't jump on the RC kernel bandwagon: these are ''less stable than what you've got already'')
* Shut down or reboot your machine at least once per day. (Like Windows: that's as unstable as a RC Linux kernel) 😂
* '''Manjaro is one of the few distros that supports Stable and RC kernels''' so live with a bit of frustration if things go a bit wonky every now and then and certainly don't install Ubuntu or Mint or RHEL as they will just not support any of this.
</translate>


[[Category:Contents page{{#translation:}}]]

MediaWiki:Citizen-footer-desc

2022-07-31T07:44:23Z

Oguzkagan: changed copyright text

Main Page

2022-07-23T15:22:55Z

Oguzkagan: Marked this version for translation

<center style="background-color:#455A64; border-radius:5px; box-shadow:0 3px 6px rgba(0,0,0,0.04),0 3px 6px rgba(0,0,0,0.0575);">[[File:Block-logo.png|center|100px]]</center>

<languages/>
<translate>
==Getting Started== 
</translate>
<div class="home-grid">
<div id="home-overview" class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Overview</translate></h3>
<div class="home-link-button"><translate> [[Special:MyLanguage/Manjaro|Manjaro Overview]]</translate></div>
<div class="home-card-label"><translate> Various articles to answer all your questions!</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Using Manjaro for Beginners|Using Manjaro]]</translate></div>
<div class="home-card-label"><translate> New to Manjaro? Start here for an overview!</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Using Manjaro for Windows users|Coming From Windows]]</translate></div>
<div class="home-card-label"><translate> Go here if you're a Windows user trying Linux or Manjaro!</translate></div>
</div>
<div id="home-support" class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Online and Support</translate></h3>
<div class="home-link-button"><translate> [[Special:MyLanguage/Manjaro Online|Manjaro Online]]</translate></div>
<div class="home-card-label"><translate> Our forum, Twitter, Reddit, and Facebook accounts.</translate></div>
<div class="home-link-button"><translate> [https://t.me/manjaro_official Manjaro Telegram]</translate></div>
<div class="home-card-label"><translate> Come talk with us on Telegram. If you want support, there is a forum...</translate></div>
</div>

<div id="home-getman" class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Get Manjaro</translate></h3>
<div class="home-link-button"><translate> [[Special:MyLanguage/Download Manjaro|Download Manjaro]]</translate></div>
<div class="home-card-label"><translate> Where to find the latest and greatest Manjaro releases.</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Check a Downloaded ISO Image For Errors|Check a Downloaded ISO Image For Errors]]</translate></div>
<div class="home-card-label"><translate> Check your Manjaro download for errors in Linux and Windows.</translate></div>
</div>

<div id="home-install" class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Installation</translate></h3>
<div class="home-link-button"><translate> [[Special:MyLanguage/Burn an ISO File|Burn an ISO File]]</translate></div>
<div class="home-card-label"><translate> Burn Manjaro to CD/DVD or USB stick in Linux and Windows.</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Installation Guides|Install Manjaro]]</translate></div>
<div class="home-card-label"><translate> Installation and partitioning guides for beginners and experienced users.</translate></div>
</div>

</div>
<translate>
==Customization and Configuration== 
</translate>
<div class="home-grid">
<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Boot / Startup</translate></h3>
<div class="home-link-button"><translate> [[Special:MyLanguage/BIOS and UEFI|BIOS and UEFI]]</translate></div>
<div class="home-card-label"><translate> How to enable virtualisation, run Manjaro on Windows 10 systems, and more!</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Display Managers / Login Screens|Display Managers / Login Screens]]</translate></div>
<div class="home-card-label"><translate> Install, configure, or even bypass MDM, GDM, SDDM, LXDM, and SLiM.</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Fstab - Use SystemD automount|Fstab - Use SystemD automount]]</translate></div>
<div class="home-card-label"><translate> SystemD and /etc/fstab options for device mounting.</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Make GRUB menu & boot-up/down fonts bigger|Larger GRUB, Boot, and Shutdown Fonts]]</translate></div>
<div class="home-card-label"><translate> How to increase the size of boot, shutdown, and GRUB menu fonts.</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> DEs / WMs</translate></h3>
<div class="home-link-button"><translate> [[Special:MyLanguage/Basic Tips for conky|Conky - Basic Tips]]</translate></div>
<div class="home-card-label"><translate> Conky can display a lot of useful information on your desktop.</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Desktop Environments|Desktop Environments and Window Managers]]</translate></div>
<div class="home-card-label"><translate> Install popular desktops and apply a range of desktop-specific configuration.</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Set all Qt app's to use GTK+ font & theme settings|Set all Qt apps to use GTK+ font & theme settings]]</translate></div>
<div class="home-card-label"><translate> Ensure QT apps match GTK+ DE/WM theming.</translate></div>
<div class="home-link-button"><translate> [[Special:MyLanguage/Set all Java apps to use GTK+ font & theme settings|Set all Java apps to use GTK+ font & theme settings]]</translate></div>
<div class="home-card-label"><translate> Ensure Java apps match GTK+ DE/WM theming.</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Software Management</translate></h3>
<div class="home-link-button"><translate> [[Repositories and Servers|Repositories and Servers]]</translate></div>
<div class="home-card-label"><translate> Change repositories, find the fastest mirrors, etc.</translate></div>
<div class="home-link-button"><translate> [[Pacman|Pacman]]</translate></div>
<div class="home-card-label"><translate> Instructions for using the '''Pac'''kage '''Man'''ager and more.</translate></div>
<div class="home-link-button"><translate> [[Graphical Software Managers|Graphical Software Managers]]</translate></div>
<div class="home-card-label"><translate> There's a range of user-friendly software managers available.</translate></div>
<div class="home-link-button"><translate> [[Arch User Repository|Arch User Repository]]</translate></div>
<div class="home-card-label"><translate> Learn about and use the AUR.</translate></div>
<div class="home-link-button"><translate> [[Flatpak|Flatpak]]</translate></div>
<div class="home-card-label"><translate> Extend your software library using Flatpaks</translate></div>
<div class="home-link-button"><translate> [[Snap|Snap]]</translate></div>
<div class="home-card-label"><translate> Install and manage Snaps on Manjaro</translate></div>
<div class="home-link-button"><translate> [[Software Applications|Software Applications]]</translate></div>
<div class="home-card-label"><translate> A collection of tips and configurations for many applications</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Hardware / MSM</translate></h3>
<div class="home-link-button"><translate> [[Manjaro Settings Manager|Manjaro Settings Manager]]</translate></div>
<div class="home-card-label"><translate> MSM can set your Language, User Account, Kernel, Time and Date, Graphics Card Drivers, and more.</translate></div>
<div class="home-link-button"><translate> [[Manjaro Hardware Detection|Manjaro Hardware Detection]]</translate></div>
<div class="home-card-label"><translate> Kernels and Drivers.(mhwd)</translate></div>
<div class="home-link-button"><translate> [[Graphical Software Managers|Graphical Software Managers]]</translate></div>
<div class="home-card-label"><translate> There's a range of user-friendly software managers available.</translate></div>
<div class="home-link-button"><translate> [[Configure Graphics Cards|Configure Graphics Cards]]</translate></div>
<div class="home-card-label"><translate> View, install, remove, or reinstall GPU drivers and much more.</translate></div>
<div class="home-link-button"><translate> [[Power Management|Power Management]]</translate></div>
<div class="home-card-label"><translate> Got the power? No? Then optimise it!</translate></div>
<div class="home-link-button"><translate> [[Printing|Printing]]</translate></div>
<div class="home-card-label"><translate> Enable printing and add printers.</translate></div>
<div class="home-link-button"><translate> [[Wacom Tablet And Pen|Wacom Tablet And Pen]]</translate></div>
<div class="home-card-label"><translate> Configuring tablets and pens.</translate></div>
<div class="home-link-button"><translate> [[Manjaro-ARM|Manjaro-ARM]]</translate></div>
<div class="home-card-label"><translate> Tips specific to ARM systems</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Network / Internet</translate></h3>
<div class="home-link-button"><translate> [[Internet Browsers|Internet Browsers]]</translate></div>
<div class="home-card-label"><translate> Security, Customization, and Configuration.</translate></div>
<div class="home-link-button"><translate> [[Firewalls and Security|Firewalls and Security]]</translate></div>
<div class="home-card-label"><translate> Firewalls and Security on Manjaro</translate></div>
<div class="home-link-button"><translate> [[Sync dynamic IP with openDNS service via ddclient|Sync dynamic IP with openDNS service via ddclient]]</translate></div>
<div class="home-card-label"><translate> Solution for update dynamic IP for openDNS service.</translate></div>
<div class="home-link-button"><translate> [[Keyboard and Mouse Sharing|Keyboard and Mouse Sharing]]</translate></div>
<div class="home-card-label"><translate> Use a mouse and keyboard across multiple machines & operating systems.</translate></div>
<div class="home-link-button"><translate> [[Networking|Networking]]</translate></div>
<div class="home-card-label"><translate> Managing networking</translate></div>
<div class="home-link-button"><translate> [[Using Samba in your File Manager|Using Samba in your File Manager]]</translate></div>
<div class="home-card-label"><translate> How to setup Samba share in your network.</translate></div>
<div class="home-link-button"><translate> [[Sharing files with Python|Sharing files with Python]]</translate></div>
<div class="home-card-label"><translate> Using Python's built-in network capabilities to share files.</translate></div>
<div class="home-link-button"><translate> [[Using autofs (automount) with NFS|Using autofs (automount) with NFS]]</translate></div>
<div class="home-card-label"><translate> One of the many ways to mount shares.</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> System / Misc</translate></h3>
<div class="home-link-button"><translate> [[Manjaro Polkit Rules|Manjaro Polkit Rules]]</translate></div>
<div class="home-card-label"><translate> The policykity rules implemented by Manjaro</translate></div>
<div class="home-link-button"><translate> [[Add a Storage Partition & Modify your System to Suit|Add a Storage Partition & Modify your System to Suit]]</translate></div>
<div class="home-card-label"><translate> How to shrink and add a partition & make Manjaro know where & what it is.</translate></div>
<div class="home-link-button"><translate> [[Aliases in .bashrc|Aliases in .bashrc]]</translate></div>
<div class="home-card-label"><translate> Shortcuts for your terminal.</translate></div>
<div class="home-link-button"><translate> [[Developer Tools|Developer Tools]]</translate></div>
<div class="home-card-label"><translate> Set of tools used by Manjaro developers and advanced users.</translate></div>
<div class="home-link-button"><translate> [[File Systems|File Systems]]</translate></div>
<div class="home-card-label"><translate> Information on different file systems, how they work, and how to use them.</translate></div>
<div class="home-link-button"><translate> [[Swap|Managing Swap]]</translate></div>
<div class="home-card-label"><translate> All about swap space</translate></div>
<div class="home-link-button"><translate> [[Limit the size of .log files & the journal|Management of the Systemd Journal & of .log files]]</translate></div>
<div class="home-card-label"><translate> Manage Systemd's Journal & syslog-ng's /var/log/*log files.</translate></div>
<div class="home-link-button"><translate> [[Linux Security|Linux Security]]</translate></div>
<div class="home-card-label"><translate> Information on root and superuser passwords.</translate></div>
<div class="home-link-button"><translate> [[How to mount Windows (NTFS) filesystem due to hibernation|How to mount Windows (NTFS) filesystem due to hibernation]]</translate></div>
<div class="home-card-label"><translate> Solutions & workarounds for various Windows versions.</translate></div>
<div class="home-link-button"><translate> [[Keyboard_Shortcuts|Keyboard Shortcuts]]</translate></div>
<div class="home-card-label"><translate> Set custom keyboard bindings.</translate></div>
<div class="home-link-button"><translate> [[Viewing and editing configuration files|Viewing and editing configuration files]]</translate></div>
<div class="home-card-label"><translate> How to view and edit files in each Manjaro edition.</translate></div>
</div>
</div>

<translate>
==Troubleshooting== 
</translate>

<div class="home-grid">
<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Boot / Startup</translate></h3>
<div class="home-link-button"><translate> [[Restore the GRUB Bootloader|Restore the GRUB Bootloader]]</translate></div>
<div class="home-card-label"><translate> Can't boot Manjaro? You may be able to repair rather than reinstall!</translate></div>
<div class="home-link-button"><translate> [[Preserve Manjaro Bootloader|Preserve Manjaro Bootloader]]</translate></div>
<div class="home-card-label"><translate> Prevent Manjaro's GRUB from being overridden.</translate></div>
<div class="home-link-button"><translate> [[Kernel Fails to Load (pata_acpi error)|Kernel Fails to Load / "Unable to Find Device" Error]]</translate></div>
<div class="home-card-label"><translate> Solution for a problem that affects certain computers using JMicron chips.</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Desktop</translate></h3>
<div class="home-link-button"><translate> [[Various screen tearing fixes|Various screen tearing fixes]]</translate></div>
<div class="home-card-label"><translate> Hopefully one of these tips will fix your screen tearing problem.</translate></div>
<div class="home-link-button"><translate> [[DMenu - warning: no locale support|DMenu - warning: no locale support]]</translate></div>
<div class="home-card-label"><translate> A fix for the "no locale support" error in dmenu.</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Software Management</translate></h3>
<div class="home-link-button"><translate> [[pacman troubleshooting|Common Issues and Pacman Troubleshooting]]</translate></div>
<div class="home-card-label"><translate> Troubleshooting common issues related to pacman</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate> Hardware</translate></h3>
<div class="home-link-button"><translate> [[Reactivating the Backlight|Screen Brightness is too Dark or Dim]]</translate></div>
<div class="home-card-label"><translate> The solution for an issue that particularly affects some makes of laptops</translate></div>
<div class="home-link-button"><translate> [[Did X.server recognise your monitor correctly?|Did X.server recognise your monitor correctly?]]</translate></div>
<div class="home-card-label"><translate> A quick test in the Terminal</translate></div>
<div class="home-link-button"><translate> [[ALSA|Advanced Linux Sound Architecture (ALSA)]]</translate></div>
<div class="home-card-label"><translate> Troubleshooting common issues related to ALSA</translate></div>
</div>
</div>

<translate>
==More== 
</translate>
<div class="home-grid">
<div class="home-card home-card-col2 home-card-row3">
<div class="home-link-button"><translate> [//www.mediawiki.org/wiki/Help:Contents User's Guide]</translate></div>
<div class="home-card-label"><translate> Full user guide on every aspect of Wiki authorship and maintenance.</translate></div>
<div class="home-link-button"><translate> [[Basic Submission Rules|Basic Submission Rules]]</translate></div>
<div class="home-card-label"><translate> How to create an account, and the dos and do-nots for Wiki contributors.</translate></div>
<div class="home-link-button"><translate> [[Contributing|Contributing]]</translate></div>
<div class="home-card-label"><translate> The starting point for those willing to contribute to the wiki.</translate></div>
<div class="home-link-button"><translate> [https://wiki.manjaro.org/index.php?title=Category:Contents_Page{{#translation:}} Contents]</translate></div>
<div class="home-card-label"><translate> For a page containing a list of all Wiki guides and tutorials sorted alphabetically</translate></div>
</div>
</div>

[[Category:Top level{{#translation:}}]]

Main Page

2022-07-23T15:22:05Z

Oguzkagan: added translate tags

<center style="background-color:#455A64; border-radius:5px; box-shadow:0 3px 6px rgba(0,0,0,0.04),0 3px 6px rgba(0,0,0,0.0575);">[[File:Block-logo.png|center|100px]]</center>

<languages/>
<translate>
==Getting Started==
</translate>
<div class="home-grid">
<div id="home-overview" class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate>Overview</translate></h3>
<div class="home-link-button"><translate>[[Special:MyLanguage/Manjaro|Manjaro Overview]]</translate></div>
<div class="home-card-label"><translate>Various articles to answer all your questions!</translate></div>
<div class="home-link-button"><translate>[[Special:MyLanguage/Using Manjaro for Beginners|Using Manjaro]]</translate></div>
<div class="home-card-label"><translate>New to Manjaro? Start here for an overview!</translate></div>
<div class="home-link-button"><translate>[[Special:MyLanguage/Using Manjaro for Windows users|Coming From Windows]]</translate></div>
<div class="home-card-label"><translate>Go here if you're a Windows user trying Linux or Manjaro!</translate></div>
</div>
<div id="home-support" class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate>Online and Support</translate></h3>
<div class="home-link-button"><translate>[[Special:MyLanguage/Manjaro Online|Manjaro Online]]</translate></div>
<div class="home-card-label"><translate>Our forum, Twitter, Reddit, and Facebook accounts.</translate></div>
<div class="home-link-button"><translate>[https://t.me/manjaro_official Manjaro Telegram]</translate></div>
<div class="home-card-label"><translate>Come talk with us on Telegram. If you want support, there is a forum...</translate></div>
</div>

<div id="home-getman" class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate>Get Manjaro</translate></h3>
<div class="home-link-button"><translate>[[Special:MyLanguage/Download Manjaro|Download Manjaro]]</translate></div>
<div class="home-card-label"><translate>Where to find the latest and greatest Manjaro releases.</translate></div>
<div class="home-link-button"><translate>[[Special:MyLanguage/Check a Downloaded ISO Image For Errors|Check a Downloaded ISO Image For Errors]]</translate></div>
<div class="home-card-label"><translate>Check your Manjaro download for errors in Linux and Windows.</translate></div>
</div>

<div id="home-install" class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate>Installation</translate></h3>
<div class="home-link-button"><translate>[[Special:MyLanguage/Burn an ISO File|Burn an ISO File]]</translate></div>
<div class="home-card-label"><translate>Burn Manjaro to CD/DVD or USB stick in Linux and Windows.</translate></div>
<div class="home-link-button"><translate>[[Special:MyLanguage/Installation Guides|Install Manjaro]]</translate></div>
<div class="home-card-label"><translate>Installation and partitioning guides for beginners and experienced users.</translate></div>
</div>

</div>
<translate>
==Customization and Configuration==
</translate>
<div class="home-grid">
<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate>Boot / Startup</translate></h3>
<div class="home-link-button"><translate>[[Special:MyLanguage/BIOS and UEFI|BIOS and UEFI]]</translate></div>
<div class="home-card-label"><translate>How to enable virtualisation, run Manjaro on Windows 10 systems, and more!</translate></div>
<div class="home-link-button"><translate>[[Special:MyLanguage/Display Managers / Login Screens|Display Managers / Login Screens]]</translate></div>
<div class="home-card-label"><translate>Install, configure, or even bypass MDM, GDM, SDDM, LXDM, and SLiM.</translate></div>
<div class="home-link-button"><translate>[[Special:MyLanguage/Fstab - Use SystemD automount|Fstab - Use SystemD automount]]</translate></div>
<div class="home-card-label"><translate>SystemD and /etc/fstab options for device mounting.</translate></div>
<div class="home-link-button"><translate>[[Special:MyLanguage/Make GRUB menu & boot-up/down fonts bigger|Larger GRUB, Boot, and Shutdown Fonts]]</translate></div>
<div class="home-card-label"><translate>How to increase the size of boot, shutdown, and GRUB menu fonts.</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate>DEs / WMs</translate></h3>
<div class="home-link-button"><translate>[[Special:MyLanguage/Basic Tips for conky|Conky - Basic Tips]]</translate></div>
<div class="home-card-label"><translate>Conky can display a lot of useful information on your desktop.</translate></div>
<div class="home-link-button"><translate>[[Special:MyLanguage/Desktop Environments|Desktop Environments and Window Managers]]</translate></div>
<div class="home-card-label"><translate>Install popular desktops and apply a range of desktop-specific configuration.</translate></div>
<div class="home-link-button"><translate>[[Special:MyLanguage/Set all Qt app's to use GTK+ font & theme settings|Set all Qt apps to use GTK+ font & theme settings]]</translate></div>
<div class="home-card-label"><translate>Ensure QT apps match GTK+ DE/WM theming.</translate></div>
<div class="home-link-button"><translate>[[Special:MyLanguage/Set all Java apps to use GTK+ font & theme settings|Set all Java apps to use GTK+ font & theme settings]]</translate></div>
<div class="home-card-label"><translate>Ensure Java apps match GTK+ DE/WM theming.</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate>Software Management</translate></h3>
<div class="home-link-button"><translate>[[Repositories and Servers|Repositories and Servers]]</translate></div>
<div class="home-card-label"><translate>Change repositories, find the fastest mirrors, etc.</translate></div>
<div class="home-link-button"><translate>[[Pacman|Pacman]]</translate></div>
<div class="home-card-label"><translate>Instructions for using the '''Pac'''kage '''Man'''ager and more.</translate></div>
<div class="home-link-button"><translate>[[Graphical Software Managers|Graphical Software Managers]]</translate></div>
<div class="home-card-label"><translate>There's a range of user-friendly software managers available.</translate></div>
<div class="home-link-button"><translate>[[Arch User Repository|Arch User Repository]]</translate></div>
<div class="home-card-label"><translate>Learn about and use the AUR.</translate></div>
<div class="home-link-button"><translate>[[Flatpak|Flatpak]]</translate></div>
<div class="home-card-label"><translate>Extend your software library using Flatpaks</translate></div>
<div class="home-link-button"><translate>[[Snap|Snap]]</translate></div>
<div class="home-card-label"><translate>Install and manage Snaps on Manjaro</translate></div>
<div class="home-link-button"><translate>[[Software Applications|Software Applications]]</translate></div>
<div class="home-card-label"><translate>A collection of tips and configurations for many applications</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate>Hardware / MSM</translate></h3>
<div class="home-link-button"><translate>[[Manjaro Settings Manager|Manjaro Settings Manager]]</translate></div>
<div class="home-card-label"><translate>MSM can set your Language, User Account, Kernel, Time and Date, Graphics Card Drivers, and more.</translate></div>
<div class="home-link-button"><translate>[[Manjaro Hardware Detection|Manjaro Hardware Detection]]</translate></div>
<div class="home-card-label"><translate>Kernels and Drivers.(mhwd)</translate></div>
<div class="home-link-button"><translate>[[Graphical Software Managers|Graphical Software Managers]]</translate></div>
<div class="home-card-label"><translate>There's a range of user-friendly software managers available.</translate></div>
<div class="home-link-button"><translate>[[Configure Graphics Cards|Configure Graphics Cards]]</translate></div>
<div class="home-card-label"><translate>View, install, remove, or reinstall GPU drivers and much more.</translate></div>
<div class="home-link-button"><translate>[[Power Management|Power Management]]</translate></div>
<div class="home-card-label"><translate>Got the power? No? Then optimise it!</translate></div>
<div class="home-link-button"><translate>[[Printing|Printing]]</translate></div>
<div class="home-card-label"><translate>Enable printing and add printers.</translate></div>
<div class="home-link-button"><translate>[[Wacom Tablet And Pen|Wacom Tablet And Pen]]</translate></div>
<div class="home-card-label"><translate>Configuring tablets and pens.</translate></div>
<div class="home-link-button"><translate>[[Manjaro-ARM|Manjaro-ARM]]</translate></div>
<div class="home-card-label"><translate>Tips specific to ARM systems</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate>Network / Internet</translate></h3>
<div class="home-link-button"><translate>[[Internet Browsers|Internet Browsers]]</translate></div>
<div class="home-card-label"><translate>Security, Customization, and Configuration.</translate></div>
<div class="home-link-button"><translate>[[Firewalls and Security|Firewalls and Security]]</translate></div>
<div class="home-card-label"><translate>Firewalls and Security on Manjaro</translate></div>
<div class="home-link-button"><translate>[[Sync dynamic IP with openDNS service via ddclient|Sync dynamic IP with openDNS service via ddclient]]</translate></div>
<div class="home-card-label"><translate>Solution for update dynamic IP for openDNS service.</translate></div>
<div class="home-link-button"><translate>[[Keyboard and Mouse Sharing|Keyboard and Mouse Sharing]]</translate></div>
<div class="home-card-label"><translate>Use a mouse and keyboard across multiple machines & operating systems.</translate></div>
<div class="home-link-button"><translate>[[Networking|Networking]]</translate></div>
<div class="home-card-label"><translate>Managing networking</translate></div>
<div class="home-link-button"><translate>[[Using Samba in your File Manager|Using Samba in your File Manager]]</translate></div>
<div class="home-card-label"><translate>How to setup Samba share in your network.</translate></div>
<div class="home-link-button"><translate>[[Sharing files with Python|Sharing files with Python]]</translate></div>
<div class="home-card-label"><translate>Using Python's built-in network capabilities to share files.</translate></div>
<div class="home-link-button"><translate>[[Using autofs (automount) with NFS|Using autofs (automount) with NFS]]</translate></div>
<div class="home-card-label"><translate>One of the many ways to mount shares.</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate>System / Misc</translate></h3>
<div class="home-link-button"><translate>[[Manjaro Polkit Rules|Manjaro Polkit Rules]]</translate></div>
<div class="home-card-label"><translate>The policykity rules implemented by Manjaro</translate></div>
<div class="home-link-button"><translate>[[Add a Storage Partition & Modify your System to Suit|Add a Storage Partition & Modify your System to Suit]]</translate></div>
<div class="home-card-label"><translate>How to shrink and add a partition & make Manjaro know where & what it is.</translate></div>
<div class="home-link-button"><translate>[[Aliases in .bashrc|Aliases in .bashrc]]</translate></div>
<div class="home-card-label"><translate>Shortcuts for your terminal.</translate></div>
<div class="home-link-button"><translate>[[Developer Tools|Developer Tools]]</translate></div>
<div class="home-card-label"><translate>Set of tools used by Manjaro developers and advanced users.</translate></div>
<div class="home-link-button"><translate>[[File Systems|File Systems]]</translate></div>
<div class="home-card-label"><translate>Information on different file systems, how they work, and how to use them.</translate></div>
<div class="home-link-button"><translate>[[Swap|Managing Swap]]</translate></div>
<div class="home-card-label"><translate>All about swap space</translate></div>
<div class="home-link-button"><translate>[[Limit the size of .log files & the journal|Management of the Systemd Journal & of .log files]]</translate></div>
<div class="home-card-label"><translate>Manage Systemd's Journal & syslog-ng's /var/log/*log files.</translate></div>
<div class="home-link-button"><translate>[[Linux Security|Linux Security]]</translate></div>
<div class="home-card-label"><translate>Information on root and superuser passwords.</translate></div>
<div class="home-link-button"><translate>[[How to mount Windows (NTFS) filesystem due to hibernation|How to mount Windows (NTFS) filesystem due to hibernation]]</translate></div>
<div class="home-card-label"><translate>Solutions & workarounds for various Windows versions.</translate></div>
<div class="home-link-button"><translate>[[Keyboard_Shortcuts|Keyboard Shortcuts]]</translate></div>
<div class="home-card-label"><translate>Set custom keyboard bindings.</translate></div>
<div class="home-link-button"><translate>[[Viewing and editing configuration files|Viewing and editing configuration files]]</translate></div>
<div class="home-card-label"><translate>How to view and edit files in each Manjaro edition.</translate></div>
</div>
</div>

<translate>
==Troubleshooting==
</translate>

<div class="home-grid">
<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate>Boot / Startup</translate></h3>
<div class="home-link-button"><translate>[[Restore the GRUB Bootloader|Restore the GRUB Bootloader]]</translate></div>
<div class="home-card-label"><translate>Can't boot Manjaro? You may be able to repair rather than reinstall!</translate></div>
<div class="home-link-button"><translate>[[Preserve Manjaro Bootloader|Preserve Manjaro Bootloader]]</translate></div>
<div class="home-card-label"><translate>Prevent Manjaro's GRUB from being overridden.</translate></div>
<div class="home-link-button"><translate>[[Kernel Fails to Load (pata_acpi error)|Kernel Fails to Load / "Unable to Find Device" Error]]</translate></div>
<div class="home-card-label"><translate>Solution for a problem that affects certain computers using JMicron chips.</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate>Desktop</translate></h3>
<div class="home-link-button"><translate>[[Various screen tearing fixes|Various screen tearing fixes]]</translate></div>
<div class="home-card-label"><translate>Hopefully one of these tips will fix your screen tearing problem.</translate></div>
<div class="home-link-button"><translate>[[DMenu - warning: no locale support|DMenu - warning: no locale support]]</translate></div>
<div class="home-card-label"><translate>A fix for the "no locale support" error in dmenu.</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate>Software Management</translate></h3>
<div class="home-link-button"><translate>[[pacman troubleshooting|Common Issues and Pacman Troubleshooting]]</translate></div>
<div class="home-card-label"><translate>Troubleshooting common issues related to pacman</translate></div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header"><translate>Hardware</translate></h3>
<div class="home-link-button"><translate>[[Reactivating the Backlight|Screen Brightness is too Dark or Dim]]</translate></div>
<div class="home-card-label"><translate>The solution for an issue that particularly affects some makes of laptops</translate></div>
<div class="home-link-button"><translate>[[Did X.server recognise your monitor correctly?|Did X.server recognise your monitor correctly?]]</translate></div>
<div class="home-card-label"><translate>A quick test in the Terminal</translate></div>
<div class="home-link-button"><translate>[[ALSA|Advanced Linux Sound Architecture (ALSA)]]</translate></div>
<div class="home-card-label"><translate>Troubleshooting common issues related to ALSA</translate></div>
</div>
</div>

<translate>
==More==
</translate>
<div class="home-grid">
<div class="home-card home-card-col2 home-card-row3">
<div class="home-link-button"><translate>[//www.mediawiki.org/wiki/Help:Contents User's Guide]</translate></div>
<div class="home-card-label"><translate>Full user guide on every aspect of Wiki authorship and maintenance.</translate></div>
<div class="home-link-button"><translate>[[Basic Submission Rules|Basic Submission Rules]]</translate></div>
<div class="home-card-label"><translate>How to create an account, and the dos and do-nots for Wiki contributors.</translate></div>
<div class="home-link-button"><translate>[[Contributing|Contributing]]</translate></div>
<div class="home-card-label"><translate>The starting point for those willing to contribute to the wiki.</translate></div>
<div class="home-link-button"><translate>[https://wiki.manjaro.org/index.php?title=Category:Contents_Page{{#translation:}} Contents]</translate></div>
<div class="home-card-label"><translate>For a page containing a list of all Wiki guides and tutorials sorted alphabetically</translate></div>
</div>
</div>

[[Category:Top level{{#translation:}}]]

MediaWiki:Common.css

2022-07-15T16:22:37Z

Oguzkagan:

/* CSS placed here will be applied to all skins */
/*@import url("https://cdn.jsdelivr.net/npm/uikit@3.7.1/dist/css/uikit.min.css");*/
@import url( 'https://fonts.googleapis.com/css?family=Comfortaa|Noto+Serif ');
h1, h2, h3, h4, h5, h6{
border: none !important;
}
hr {
height:0px;
}
html, body{
height:0px !important;
}
#mw-panel .portal .body ul {
padding-left: 0px !important;
}
.firstHeading{
margin-top: 10px !important;
}
#content h1,
#content h2 {
font-family: "Comfortaa", serif;
}
pre, code, .mw-code{
color: gray;
border-radius: 5px;
}
.mw-pt-languages{
border-radius: 5px;
}
.home-card {
position:relative;
padding:15px;
background:var(--color-surface-1);
border-radius:8px;
box-shadow:0 3px 6px rgba(0,0,0,0.04),0 3px 6px rgba(0,0,0,0.0575);
font-size:0.875rem
}
.home-card-label {
color:var(--color-base--subtle);
font-size:0.8125rem;
letter-spacing:0.75px
}
h3.home-card-header {
margin-top:0;
font-size:1rem
}
.home-grid {
display:grid;
grid:auto-flow dense/repeat(auto-fit,minmax(9.375rem,1fr));
grid-auto-rows:minmax(3rem,auto);
grid-gap:0.625rem
}
.home-card-col2 {
grid-column:span 2
}
.home-card-row3 {
grid-row:span 3
}
.home-link-button {
display:flex;
margin-top:15px;
}
.home-link-button a {
flex-grow:1;
padding:0.3rem 0.6rem;
border:1px solid;
border-color:var(--border-color-base);
background:var(--background-color-framed);
border-radius:8px;
color:var(--color-base--emphasized)
}
.home-link-button a:hover {
background:var(--background-color-framed--hover)
}
.home-link-button a:active {
background:var(--background-color-framed--active)
}
.mw-pt-languages-list a{
padding:0.3rem 0.6rem;
border:1px solid;
border-color:var(--border-color-base);
background:var(--background-color-framed);
border-radius:8px;
color:var(--color-base--emphasized);
line-height:2;
}

Main Page

2022-07-15T16:17:30Z

Oguzkagan: home v1

<center style="background-color:#455A64; border-radius:5px; box-shadow:0 3px 6px rgba(0,0,0,0.04),0 3px 6px rgba(0,0,0,0.0575);">[[File:Block-logo.png|center|100px]]</center>

<languages/>
<translate>
==Getting Started==
<div class="home-grid">
<div id="home-overview" class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header">Overview</h3>
<div class="home-link-button">[[Special:MyLanguage/Manjaro|Manjaro Overview]]</div>
<div class="home-card-label">Various articles to answer all your questions!</div>
<div class="home-link-button">[[Special:MyLanguage/Using Manjaro for Beginners|Using Manjaro]]</div>
<div class="home-card-label">New to Manjaro? Start here for an overview!</div>
<div class="home-link-button">[[Special:MyLanguage/Using Manjaro for Windows users|Coming From Windows]]</div>
<div class="home-card-label">Go here if you're a Windows user trying Linux or Manjaro!</div>
</div>
<div id="home-support" class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header">Online and Support</h3>
<div class="home-link-button">[[Special:MyLanguage/Manjaro Online|Manjaro Online]]</div>
<div class="home-card-label">Our forum, Twitter, Reddit, and Facebook accounts.</div>
<div class="home-link-button">[https://t.me/manjaro_official Manjaro Telegram]</div>
<div class="home-card-label">Come talk with us on Telegram. If you want support, there is a forum...</div>
</div>

<div id="home-getman" class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header">Get Manjaro</h3>
<div class="home-link-button">[[Special:MyLanguage/Download Manjaro|Download Manjaro]]</div>
<div class="home-card-label">Where to find the latest and greatest Manjaro releases.</div>
<div class="home-link-button">[[Special:MyLanguage/Check a Downloaded ISO Image For Errors|Check a Downloaded ISO Image For Errors]]</div>
<div class="home-card-label">Check your Manjaro download for errors in Linux and Windows.</div>
</div>

<div id="home-install" class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header">Installation</h3>
<div class="home-link-button">[[Special:MyLanguage/Burn an ISO File|Burn an ISO File]]</div>
<div class="home-card-label">Burn Manjaro to CD/DVD or USB stick in Linux and Windows.</div>
<div class="home-link-button">[[Special:MyLanguage/Installation Guides|Install Manjaro]]</div>
<div class="home-card-label">Installation and partitioning guides for beginners and experienced users.</div>
</div>

</div>

==Customization and Configuration== 

<div class="home-grid">
<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header">Boot / Startup</h3>
<div class="home-link-button">[[Special:MyLanguage/BIOS and UEFI|BIOS and UEFI]]</div>
<div class="home-card-label">How to enable virtualisation, run Manjaro on Windows 10 systems, and more!</div>
<div class="home-link-button">[[Special:MyLanguage/Display Managers / Login Screens|Display Managers / Login Screens]]</div>
<div class="home-card-label">Install, configure, or even bypass MDM, GDM, SDDM, LXDM, and SLiM.</div>
<div class="home-link-button">[[Special:MyLanguage/Fstab - Use SystemD automount|Fstab - Use SystemD automount]]</div>
<div class="home-card-label">SystemD and /etc/fstab options for device mounting.</div>
<div class="home-link-button">[[Special:MyLanguage/Make GRUB menu & boot-up/down fonts bigger|Larger GRUB, Boot, and Shutdown Fonts]]</div>
<div class="home-card-label">How to increase the size of boot, shutdown, and GRUB menu fonts.</div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header">DEs / WMs</h3>
<div class="home-link-button">[[Special:MyLanguage/Basic Tips for conky|Conky - Basic Tips]]</div>
<div class="home-card-label">Conky can display a lot of useful information on your desktop.</div>
<div class="home-link-button">[[Special:MyLanguage/Desktop Environments|Desktop Environments and Window Managers]]</div>
<div class="home-card-label">Install popular desktops and apply a range of desktop-specific configuration.</div>
<div class="home-link-button">[[Special:MyLanguage/Set all Qt app's to use GTK+ font & theme settings|Set all Qt apps to use GTK+ font & theme settings]]</div>
<div class="home-card-label">Ensure QT apps match GTK+ DE/WM theming.</div>
<div class="home-link-button">[[Special:MyLanguage/Set all Java apps to use GTK+ font & theme settings|Set all Java apps to use GTK+ font & theme settings]]</div>
<div class="home-card-label">Ensure Java apps match GTK+ DE/WM theming.</div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header">Software Management</h3>
<div class="home-link-button">[[Repositories and Servers|Repositories and Servers]]</div>
<div class="home-card-label">Change repositories, find the fastest mirrors, etc.</div>
<div class="home-link-button">[[Pacman|Pacman]]</div>
<div class="home-card-label">Instructions for using the '''Pac'''kage '''Man'''ager and more.</div>
<div class="home-link-button">[[Graphical Software Managers|Graphical Software Managers]]</div>
<div class="home-card-label">There's a range of user-friendly software managers available.</div>
<div class="home-link-button">[[Arch User Repository|Arch User Repository]]</div>
<div class="home-card-label">Learn about and use the AUR.</div>
<div class="home-link-button">[[Flatpak|Flatpak]]</div>
<div class="home-card-label">Extend your software library using Flatpaks</div>
<div class="home-link-button">[[Snap|Snap]]</div>
<div class="home-card-label">Install and manage Snaps on Manjaro</div>
<div class="home-link-button">[[Software Applications|Software Applications]]</div>
<div class="home-card-label">A collection of tips and configurations for many applications</div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header">Hardware / MSM</h3>
<div class="home-link-button">[[Manjaro Settings Manager|Manjaro Settings Manager]]</div>
<div class="home-card-label">MSM can set your Language, User Account, Kernel, Time and Date, Graphics Card Drivers, and more.</div>
<div class="home-link-button">[[Manjaro Hardware Detection|Manjaro Hardware Detection]]</div>
<div class="home-card-label">Kernels and Drivers.(mhwd)</div>
<div class="home-link-button">[[Graphical Software Managers|Graphical Software Managers]]</div>
<div class="home-card-label">There's a range of user-friendly software managers available.</div>
<div class="home-link-button">[[Configure Graphics Cards|Configure Graphics Cards]]</div>
<div class="home-card-label">View, install, remove, or reinstall GPU drivers and much more.</div>
<div class="home-link-button">[[Power Management|Power Management]]</div>
<div class="home-card-label">Got the power? No? Then optimise it!</div>
<div class="home-link-button">[[Printing|Printing]]</div>
<div class="home-card-label">Enable printing and add printers.</div>
<div class="home-link-button">[[Wacom Tablet And Pen|Wacom Tablet And Pen]]</div>
<div class="home-card-label">Configuring tablets and pens.</div>
<div class="home-link-button">[[Manjaro-ARM|Manjaro-ARM]]</div>
<div class="home-card-label">Tips specific to ARM systems</div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header">Network / Internet</h3>
<div class="home-link-button">[[Internet Browsers|Internet Browsers]]</div>
<div class="home-card-label">Security, Customization, and Configuration.</div>
<div class="home-link-button">[[Firewalls and Security|Firewalls and Security]]</div>
<div class="home-card-label">Firewalls and Security on Manjaro</div>
<div class="home-link-button">[[Sync dynamic IP with openDNS service via ddclient|Sync dynamic IP with openDNS service via ddclient]]</div>
<div class="home-card-label">Solution for update dynamic IP for openDNS service.</div>
<div class="home-link-button">[[Keyboard and Mouse Sharing|Keyboard and Mouse Sharing]]</div>
<div class="home-card-label">Use a mouse and keyboard across multiple machines & operating systems.</div>
<div class="home-link-button">[[Networking|Networking]]</div>
<div class="home-card-label">Managing networking</div>
<div class="home-link-button">[[Using Samba in your File Manager|Using Samba in your File Manager]]</div>
<div class="home-card-label">How to setup Samba share in your network.</div>
<div class="home-link-button">[[Sharing files with Python|Sharing files with Python]]</div>
<div class="home-card-label">Using Python's built-in network capabilities to share files.</div>
<div class="home-link-button">[[Using autofs (automount) with NFS|Using autofs (automount) with NFS]]</div>
<div class="home-card-label">One of the many ways to mount shares.</div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header">System / Misc</h3>
<div class="home-link-button">[[Manjaro Polkit Rules|Manjaro Polkit Rules]]</div>
<div class="home-card-label">The policykity rules implemented by Manjaro</div>
<div class="home-link-button">[[Add a Storage Partition & Modify your System to Suit|Add a Storage Partition & Modify your System to Suit]]</div>
<div class="home-card-label">How to shrink and add a partition & make Manjaro know where & what it is.</div>
<div class="home-link-button">[[Aliases in .bashrc|Aliases in .bashrc]]</div>
<div class="home-card-label">Shortcuts for your terminal.</div>
<div class="home-link-button">[[Developer Tools|Developer Tools]]</div>
<div class="home-card-label">Set of tools used by Manjaro developers and advanced users.</div>
<div class="home-link-button">[[File Systems|File Systems]]</div>
<div class="home-card-label">Information on different file systems, how they work, and how to use them.</div>
<div class="home-link-button">[[Swap|Managing Swap]]</div>
<div class="home-card-label">All about swap space</div>
<div class="home-link-button">[[Limit the size of .log files & the journal|Management of the Systemd Journal & of .log files]]</div>
<div class="home-card-label">Manage Systemd's Journal & syslog-ng's /var/log/*log files.</div>
<div class="home-link-button">[[Linux Security|Linux Security]]</div>
<div class="home-card-label">Information on root and superuser passwords.</div>
<div class="home-link-button">[[How to mount Windows (NTFS) filesystem due to hibernation|How to mount Windows (NTFS) filesystem due to hibernation]]</div>
<div class="home-card-label">Solutions & workarounds for various Windows versions.</div>
<div class="home-link-button">[[Keyboard_Shortcuts|Keyboard Shortcuts]]</div>
<div class="home-card-label">Set custom keyboard bindings.</div>
<div class="home-link-button">[[Viewing and editing configuration files|Viewing and editing configuration files]]</div>
<div class="home-card-label">How to view and edit files in each Manjaro edition.</div>
</div>

</div>

==Troubleshooting==

<div class="home-grid">
<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header">Boot / Startup</h3>
<div class="home-link-button">[[Restore the GRUB Bootloader|Restore the GRUB Bootloader]]</div>
<div class="home-card-label">Can't boot Manjaro? You may be able to repair rather than reinstall!</div>
<div class="home-link-button">[[Preserve Manjaro Bootloader|Preserve Manjaro Bootloader]]</div>
<div class="home-card-label">Prevent Manjaro's GRUB from being overridden.</div>
<div class="home-link-button">[[Kernel Fails to Load (pata_acpi error)|Kernel Fails to Load / "Unable to Find Device" Error]]</div>
<div class="home-card-label">Solution for a problem that affects certain computers using JMicron chips.</div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header">Desktop</h3>
<div class="home-link-button">[[Various screen tearing fixes|Various screen tearing fixes]]</div>
<div class="home-card-label">Hopefully one of these tips will fix your screen tearing problem.</div>
<div class="home-link-button">[[DMenu - warning: no locale support|DMenu - warning: no locale support]]</div>
<div class="home-card-label">A fix for the "no locale support" error in dmenu.</div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header">Software Management</h3>
<div class="home-link-button">[[pacman troubleshooting|Common Issues and Pacman Troubleshooting]]</div>
<div class="home-card-label">Troubleshooting common issues related to pacman</div>
</div>

<div class="home-card home-card-col2 home-card-row3">
<h3 class="home-card-header">Hardware</h3>
<div class="home-link-button">[[Reactivating the Backlight|Screen Brightness is too Dark or Dim]]</div>
<div class="home-card-label">The solution for an issue that particularly affects some makes of laptops</div>
<div class="home-link-button">[[Did X.server recognise your monitor correctly?|Did X.server recognise your monitor correctly?]]</div>
<div class="home-card-label">A quick test in the Terminal</div>
<div class="home-link-button">[[ALSA|Advanced Linux Sound Architecture (ALSA)]]</div>
<div class="home-card-label">Troubleshooting common issues related to ALSA</div>
</div>

</div>

==More==

<div class="home-grid">
<div class="home-card home-card-col2 home-card-row3">
<div class="home-link-button">[//www.mediawiki.org/wiki/Help:Contents User's Guide]</div>
<div class="home-card-label">Full user guide on every aspect of Wiki authorship and maintenance.</div>
<div class="home-link-button">[[Basic Submission Rules|Basic Submission Rules]]</div>
<div class="home-card-label">How to create an account, and the dos and do-nots for Wiki contributors.</div>
<div class="home-link-button">[[Contributing|Contributing]]</div>
<div class="home-card-label">The starting point for those willing to contribute to the wiki.</div>
<div class="home-link-button">[https://wiki.manjaro.org/index.php?title=Category:Contents_Page{{#translation:}} Contents]</div>
<div class="home-card-label">For a page containing a list of all Wiki guides and tutorials sorted alphabetically</div>
</div>

</div>
__TOC__
</translate>

[[Category:Top level{{#translation:}}]]

MediaWiki:Common.css

2022-07-15T16:16:11Z

Oguzkagan:

/* CSS placed here will be applied to all skins */
/*@import url("https://cdn.jsdelivr.net/npm/uikit@3.7.1/dist/css/uikit.min.css");*/
@import url( 'https://fonts.googleapis.com/css?family=Comfortaa|Noto+Serif ');
h1, h2, h3, h4, h5, h6{
border: none !important;
}
hr {
height:0px;
}
html, body{
height:0px !important;
}
#mw-panel .portal .body ul {
padding-left: 0px !important;
}
.firstHeading{
margin-top: 10px !important;
}
#content h1,
#content h2 {
font-family: "Comfortaa", serif;
}
pre, code, .mw-code{
color: gray;
border-radius: 5px;
}
.mw-pt-languages{
border-radius: 5px;
}
.home-card {
position:relative;
padding:15px;
background:var(--color-surface-1);
border-radius:8px;
box-shadow:0 3px 6px rgba(0,0,0,0.04),0 3px 6px rgba(0,0,0,0.0575);
font-size:0.875rem
}
.home-card-label {
color:var(--color-base--subtle);
font-size:0.8125rem;
letter-spacing:0.75px
}
h3.home-card-header {
margin-top:0;
font-size:1rem
}
.home-grid {
display:grid;
grid:auto-flow dense/repeat(auto-fit,minmax(9.375rem,1fr));
grid-auto-rows:minmax(3rem,auto);
grid-gap:0.625rem
}
.home-card-col2 {
grid-column:span 2
}
.home-card-row3 {
grid-row:span 3
}
.home-link-button {
display:flex;
margin-top:5px;
}
.home-link-button a {
flex-grow:1;
padding:0.3rem 0.6rem;
border:1px solid;
border-color:var(--border-color-base);
background:var(--background-color-framed);
border-radius:8px;
color:var(--color-base--emphasized)
}
.home-link-button a:hover {
background:var(--background-color-framed--hover)
}
.home-link-button a:active {
background:var(--background-color-framed--active)
}

File:Block-logo.png

2022-07-15T16:09:42Z

Oguzkagan:

MediaWiki:Common.css

2022-07-15T15:11:08Z

Oguzkagan:

/* CSS placed here will be applied to all skins */
/*@import url("https://cdn.jsdelivr.net/npm/uikit@3.7.1/dist/css/uikit.min.css");*/
@import url( 'https://fonts.googleapis.com/css?family=Comfortaa|Noto+Serif ');
h1, h2, h3, h4, h5, h6{
border: none !important;
}
hr {
height:0px;
}
html, body{
height:0px !important;
}
#mw-panel .portal .body ul {
padding-left: 0px !important;
}
.firstHeading{
margin-top: 10px !important;
}
#content h1,
#content h2 {
font-family: "Comfortaa", serif;
}
pre, code, .mw-code{
color: gray;
border-radius: 5px;
}
.mw-pt-languages{
border-radius: 5px;
}
.home-card {
position:relative;
padding:15px;
background:var(--color-surface-1);
border-radius:8px;
box-shadow:0 3px 6px rgba(0,0,0,0.04),0 3px 6px rgba(0,0,0,0.0575);
font-size:0.875rem
}
.home-card-label {
color:var(--color-base--subtle);
font-size:0.8125rem;
letter-spacing:0.75px
}
h3.home-card-header {
margin-top:0;
font-size:1rem
}
.home-grid {
display:grid;
grid:auto-flow dense/repeat(auto-fit,minmax(9.375rem,1fr));
grid-auto-rows:minmax(3rem,auto);
grid-gap:0.625rem
}
.home-card-col2 {
grid-column:span 2
}
.home-card-row3 {
grid-row:span 3
}
.home-link-button {
display:flex
}
.home-link-button a {
flex-grow:1;
padding:0.3rem 0.6rem;
border:1px solid;
border-color:var(--border-color-base);
background:var(--background-color-framed);
border-radius:12px;
color:var(--color-base--emphasized)
}
.home-link-button a:hover {
background:var(--background-color-framed--hover)
}
.home-link-button a:active {
background:var(--background-color-framed--active)
}

MediaWiki:Common.css

2022-07-15T14:53:26Z

Oguzkagan:

MediaWiki:Common.css

2022-07-15T14:44:16Z

Oguzkagan: home css

MediaWiki:Common.css

2022-07-15T14:40:05Z

Oguzkagan: test class

Pamac

2022-01-22T11:09:02Z

Oguzkagan: removed warning

<languages/>
__TOC__

<translate>
=Overview= 


Pamac (Add/Remove Software) is Manjaro's Package Manager. It is based on libalpm with AUR and Appstream support. It focuses on providing an easy to use interface while still providing a powerful set of features.


[[File:Pamac-gtk-main.png|center|800px]]

=Installing Pamac= 


Pamac is pre-installed on many Manjaro Editions but if your system does not have it it can be easily installed. Pamac comes in several different packages:
* {{ic|pamac-gtk}} - The GTK version of pamac. Includes a tray icon for many desktops.
* {{ic|pamac-cli}} - The command line version of pamac.
* {{ic|pamac-tray-appindicator}} - A tray icon for KDE plasma


These packages can be installed using pacman. For example, to install the GTK version, you can use the command:
sudo pacman -Syu pamac-gtk


{{tip|Both the GTK and Qt Pamac packages will automatically install the CLI version as well}}

=Using the Pamac GUI= 

==Installing Software== 


[[File:Pamac-gtk-optional-deps.png|left|thumb|400px]]


To install packages simply check check the box next to the packages. Once you have selected all the packages all the packages you want to install, click the Apply button at the bottom of the page.


If any of the packages have optional dependencies(packages that enable additional functionality) you will see a window like the one to the left which allows to select the ones you would like to install.
<div style="clear: both"></div>
[[File:Pamac-gtk-transaction-summary.png|left|thumb|400px]]


After you have selected optional dependencies, you should see a windows similar to the one pictured on the left. This lists all the packages that will be installed, upgraded or removed by the action. Once you have reviewed the list, press the Apply button to install the packages.


You may notice this list has more packages than you selected in the GUI. This is because many packages also have dependencies which are packages that must be installed in order for the software you selected to function properly. You may also notice that packages are being removed even though you didn't select any packages to remove. This is happening in the example to the left where you can see {{ic|clutter}} and {{ic|cogl}} are being removed. They are being removed because they conflict with {{ic|deepin-clutter}} and {{ic|deepin-cogl}} which provide the same functionality.
<div style="clear: both"></div>

==Removing Software== 


[[File:Pamac-gtk-remove-summary.png|left|thumb|400px]]


Removing software is as simple as unchecking the packages you want to remove and clicking the Apply button at the bottom of the page.


Once you do you should see a screen similar to the one on the left which lists all the packages that are about to be removed. You may notice this list contains more packages than you selected. This is because when you remove a package that other packages depend on, those packages are also removed.


{{warning|It is extremely important to carefully review the Transaction Summary before accepting the package removal. Some packages have many packages which depend on them and you don't want to inadvertently remove your whole Desktop Environment}}
<div style="clear: both"></div>

==Preferences== 


You can access the preferences by clicking on the three dots in the upper right corner and selecting preferences.


[[File:Pamac-gtk-preferences-general.png|left|thumb|400px]]


The General tab of preferences contains several settings, most of which are self explanatory.


* Remove unrequired dependencies - This removes dependencies which are no longer required by any package
* Check available disk space - Checks to ensure you have sufficient disk space available before downloading and installing packages
* Maximum parallel downloads - The number of concurrent downloads allowed
* Enable downgrade - This allows packages to be downgraded as well as upgraded. This is important when [[Switching_Branches|switching branches]].
* Check for updates - Disabling this will stop Pamac from looking for updates. In most cases, turning this off on a [[The Rolling Release Development Model|rolling release]] distro like Manjaro is a bad idea.
* Ignore updates for - This is a list of packages that you don't want to be upgraded. This is inherently dangerous practice and should only be used by advanced users.


{{warning|Ignoring updates for individual packages will leave you in an unsupported "partial upgrade" state. It is common for innocuous looking ignored packages to leave your system unbootable}}
<div style="clear: both"></div>


{{warning|'''DISCLAIMER:''' AUR scripts are created for Arch Linux by Arch Linux Users. AUR packages are user-produced content. These PKGBUILDs are completely unofficial and have not been thoroughly vetted. Any use of the provided files is at your own risk.}}


[[File:Pamac-gtk-preferences-aur.png|left|thumb|400px]]


Pamac is also capable of using scripts from the [[Arch User Repository|Arch User Repository(AUR)]] to install or update packages. Please carefully read the considerations in the [[Arch User Repository|linked page]] prior to enabling support for AUR.


If you enable AUR support, you may also select, "Check for updates from AUR" so software you install from AUR won't become outdated. An alternative is creating an account on AURweb and subscribe to notifications for the scripts you are using on a permanent basis.


Checking for "development package" updates will allow updates on *-git packages which are built from the latest source code to also be updated.


The "Build directory" is where AUR packages will be built. Using "tmp" usually will provide the best performance but very large packages may fail to build. In this case, select somewhere with more available space.
<div style="clear: both"></div>
[[File:Pamac-gtk-preferences-cache.png|left|thumb|400px]]


When Pamac installs packages, it keeps a copy of all the old packages you have downloaded. This cache can be very useful if you have to download packages in an emergency. However, left unchecked, this cache will grow very large over time. These preferences allow your cache to be automatically managed based on your preferences.


The first option allows you to set a number for how many copies of each package are retained. In other words, if you have downloaded 25 versions of firefox over the life of your install and you set this number to "3", only the most recent 3 versions will be retained. Unless you are very short on disk space, it is recommended to set this to at least 2.


By selecting "Remove only the versions of uninstalled packages" pamac will retain all versions of packages you still have installed.
<div style="clear: both"></div>

=Using the Pamac CLI= 


Pamac also includes a fully functional CLI for when you don't have a functional GUI or for those that prefer to manager packages that way.

==Locating and Installing Packages== 


To search for available packages you can use the command {{ic|pamac search}}. For example, to search the repos for packages containing the word smplayer:
<pre>pamac search smplayer
smplayer [Installed] 19.5.0-1 community
Media player with built-in codecs that can play virtually all video and audio formats
smplayer-skins [Installed] 1:15.2.0-2 community
Skins for SMPlayer
smplayer-themes [Installed] 1:18.6.0-1 community
Themes for SMPlayer</pre>


As you can see, this will also show you which packages are already installed. If you would like to search both the repos and [[Arch_User_Repository|AUR]] you add {{ic|-a}} like this:
<pre>pamac search -a smplayer
smplayer [Installed] 19.5.0-1 community
Media player with built-in codecs that can play virtually all video and audio formats
smplayer-skins [Installed] 1:15.2.0-2 community
Skins for SMPlayer
smplayer-themes [Installed] 1:18.6.0-1 community
Themes for SMPlayer
papirus-smplayer-theme-git 20181024-2 AUR
Papirus theme for SMPlayer (git version)
smplayer-svn 17.12.0.r8852-1 AUR
Advanced front-end for MPlayer/MPV
smplayer-svn-notitlebar 18.3.0.r8982M-1 AUR
Advanced front-end for MPlayer/MPV + Patch to disable titlebar in compact mode
smplayer-skins-svn 15.2.0.r8852-1 AUR
Skins for SMPlayer
smplayer-themes-svn 17.3.0.r8852-1 AUR
Themes for SMPlayer
smplayer-qt4 18.5.0-1 AUR
Complete front-end for MPlayer/MPV (Qt4)
rosa-media-player-plugin 1.0-2 AUR
The new multimedia player(based on SMPlayer) with clean and elegant UI (mozilla plugin only).
smplayer-theme-faenza (Out of Date: 09/15/2017) 2-2 AUR
Normal, dark and silver faenza theme for smplayer.
umplayer 0.98.2-2 AUR
An alternative to SMPlayer</pre>


Once you have identified the packages you wish to install you can install them with command {{ic|pamac install}}. For example, if we wanted to install {{ic|smplayer}} and {{ic|smplayer-themes}} we could use the command:
pamac install smplayer smplayer-themes


{{tip|When using install pamac will check to see if packages are installed and only install the ones not already installed}}


If you want to install packages from [[Arch_User_Repository|AUR]] you use the command {{ic|pamac build}}. Sticking with the above example, if you decided you wanted to install {{ic|umplayer}} instead you could the command:
pamac build umplayer

==Removing Packages== 


The command {{ic|pamac remove}} can be used to uninstall packages installed from the repos or [[Arch_User_Repository|AUR]]. For example if you wanted to remove all the packages installed above you could use the command:
pamac remove smplayer smplayer-themes umplayer


{{warning|It is extremely important to carefully review the list of packages pamac presents before confirming. Some packages have many packages which depend on them and you don't want to inadvertently remove your whole Desktop Environment}}

==Identifying Installed Packages== 


To display a list of all installed packages you can use the command:
pamac list -i

==Displaying Detailed Package Information== 


To display detailed information on a package that is in the repos or installed on your system use the command {{ic|pamac info}}. Keeping with our example:
pamac info smplayer


If you also would like to check packages in [[Arch_User_Repository|AUR]] you could use:
pamac info -a smplayer

==Updating the System== 


To check if updates are available you can use the command:
pamac checkupdates -a


To update all installed packages installed from the repos or [[Arch_User_Repository|AUR]] you can use the command:
pamac upgrade -a


{{tip|pamac update and pamac upgrade are exactly the same. You can use them interchangably.}}

==Dealing with Orphaned Packages== 


To check to see if there any orphaned packages(packages which are no longer needed) installed you can use:
pamac list -o


To remove all orphans use the command:
pamac remove -o

==Cleaning the Cache== 


When pamac installs packages, it keeps a copy of all the old packages you have downloaded. This cache can be very useful if you have to install older packages in an emergency. However, left unchecked, this cache will grow very large over time.


Otherwise, to clear the cache completely, enter the following command (and use with care):
pamac clean


A safer way to remove old package cache files is to remove all packages except for the latest three package versions using:
pamac clean --keep 3

==Other Useful Pamac Functions== 


To see which package owns a certain file on your system, use the command {{ic|pamac search -f}}. For example:
pamac search -f /usr/bin/smplayer


To force a package to be installed even if it is already installed use {{ic|pamac reinstall}}. For example:
pamac reinstall smplayer

</translate>
[[Category:Contents Page{{#translation:}}]]

Virt-manager

2021-12-25T09:19:13Z

Oguzkagan: Marked this version for translation

<languages/>
__TOC__
<translate>
= Overview = 


[[file:topbar_logo.png|left]]
<br clear="all" />
{{tip|Have you heard about Virtualbox to virtualize operating systems like Linux and Windows or Mac? It 'a good software, but not the only one! Don't forget VMware, Gnome Boxes and ...virt-manager. }}


----


'''[https://virt-manager.org/ Virt-manager]''' uses '''[http://libvirt.org/ libvirt]''' and it's a manager of many '''[https://libvirt.org/drivers.html hypervisors]''', including the one that we want to use here: QEMU/KVM.


----


<br clear="all" />


'''Why do I need to virtualize?'''


* To learn about a new O.S.


* To configure a hardware that has a setup only for that operating system


* To use a software that only works on another

= I want to know more = 


[[file:Hypervisor_1.png|left]]
<br clear="all" />
1. '''[https://en.wikipedia.org/wiki/Virtualization Virtualization]'''
<br clear="all" />
2. '''[https://en.wikipedia.org/wiki/Hypervisor Hypervisor]'''
<br clear="all" />
3. '''[https://en.wikipedia.org/wiki/Virtual_machine Virtual machine]'''
<br clear="all" />

= What we absolutely must know = 
<br clear="all" />
1. What is my CPU. Identify it and make sure it's at least a quad core. '''TAKE A LOOK AT''' '''[http://www.cpu-world.com/CPUs/CPU.html CPU-World]'''
<br clear="all" />
2. Check if the 'virtualization parameters' are enabled on BIOS using
LC_ALL=C lscpu | grep Virtualization
3. How much memory I have. Check the RAM and verify that is at least 4GB.
<br clear="all" />
4. The amount of free space on my hard drive. The virtual machine can use a disk image file so extra partitions are not necessary.
{{note|You can also use raw partition specific for virtual machines. See [https://wiki.archlinux.org/title/Partitioning partitioning] for more information}}
5. The minimum hardware requirements of the operating system you want to install as a virtual machine.
<br clear="all" />

= Install virt-manager, qemu and all dependencies= 
<br clear="all" />
From terminal:
sudo pacman -S virt-manager qemu vde2 iptables-nft dnsmasq bridge-utils openbsd-netcat edk2-ovmf swtpm
Enable and start service
sudo systemctl enable libvirtd.service
sudo systemctl start libvirtd.service
Add user to ''libvirt'' group to use the '''system'''-level virtual machines (qemu:///system)
sudo usermod -a -G libvirt $USER
{{note|
# You don't need this step to run system-level virtual machines. However, virt-manager will prompt for sudoer's password when launch if the user is not in the ''libvirt'' group
# You can also create '''user'''-level virtual machines (qemu:///session) and use without sudoer's privelige. However, some features such as [https://libvirt.org/kbase/virtiofs.html VirtioFS file sharing] may be unavailable in qemu:///session}}

= Using Virt-Manager for guest creation= 
<br clear="all" />
0. Prepare installation image. If you're going to install Windows, prepare the [https://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers Virtio driver] image too.
{{tip|You can also find the [https://aur.archlinux.org/packages/virtio-win virtio-win] package in AUR. The image is located in '''/var/lib/libvirt/images''', which is the default [https://libvirt.org/storage.html#StorageBackendDir directory pool] of qemu:///system}}
<br clear="all" />
1. Launch menu Virtual Machine Manager. It should already have a [https://libvirt.org/drvlxc.html LXC] connection. You can disconnect and remove it if you don't use LXC.
<br clear="all" />
2. Go to File, choose Add Connection and choose hypervisor QEMU/KVM, or QEMU/KVM user session if you don't want '''system'''-level virtual machines. Click on connect.
<br clear="all" />
3. You need directory pools to store the disk images of virtual machines or the ISO file of CD/DVD. Double click qemu/kvm, go on storage and add by clicking + the path to the folder where you have the iso and the folder where create the virtual machine.
<br clear="all" />
{{tip|My advice: use a different partition than the root. In case you need to reinstall your operating system you don't lose the VM that already ready-to-start.}}
4. Click on create a new virtual machine: select '''Local install media (ISO image or CDROM)''', and select the installation ISO image and OS type (if not detected).
<br clear="all" />
5. How many CPU assign and how much memory? (check the recommended requirements of O.S. that you are installing)
<br clear="all" />
6. Create the file system of the virtual machine by selecting '''Select or create custom storage''' and click '''Manage...'''. Under your desired directory pool, create the volume of the virtual machine (default in qcow2 format). How many GB? Check the recommended requirements O.S. you install.
<br clear="all" />
7.Assign a name to the machine and flag '''customize configuration before install'''. You have access to the screen with all the hardware that will be virtualized, do a check if there is all that is needed to initialize and launch the installer.
<br clear="all" />
8. In ''Overview'', change the firmware to UEFI for future-proof capacity.
<br clear="all" />
9. Change the type of SATA Disk 1 (the disk image of the creating virtual machine) to ''virtio'' for better performance. Change discard mode to ''unmap'', and then apply the change. You should notice the device name would change from SATA Disk 1 to VirtIO Disk 1.
{{warning| If you're installing Windows, make sure to create a new SATA CDROM device and select the '''virtio-win''' image as the media, so that the Windows Installer can load the driver to recognize the disk. The virtio storage driver should be located at somewhere like ''E:\viostor\w10\amd64''}}
10. Set the NIC type to virtio too for better network performance.
{{note| If you're installing Windows, once the system if ready, make sure to install all the virtio drivers so that your virtIO network can work normally}}
11. Add TPM chip, select '''TIS''' model through '''Emulated device''' backend.
<br clear="all" />
12. Add a watchdog to reboot the guest when it hangs. Leave the settings as default.
<br clear="all" />
13. And a hardware RNG, to get entropy from the host.
<br clear="all" />
14. Click on the top to start installation.
<br clear="all" />
{{warning|'''All these steps are visible on youtube.''' '''[https://youtu.be/DiUG_hlLk3c >>> PLAY THIS] [[File:YouTube_1.png|thumb|center|300px]]'''}}

==Install guest additions== 
Once the VM is started and running you have to install the [https://www.spice-space.org/download.html spice guest tools].
<br clear="all" />
For Windows is a single package: spice-guest-tools-xxxx.exe
<br clear="all" />
For linux are: spice-vdagent and xf86-video-qxl. If you visrtualize a linux distro you can install them with their package manager
<br clear="all" />
Visit: '''[http://www.spice-space.org/download.html Spice download]'''

==Tune the display settings== 
The default model of display card is QXL. If your virtual machine is Linux system, you can change it to virtio and enable 3D acceleration for better graphic performance.
<br clear="all" />
Windows virtual machine, however doesn't support virtio display yet. Nevertheless, we can increase its VGA memory from the default 16 MB to 64 MB to allow higher display resolution and slightly better 2D graphical performance.
<br clear="all" />
To do so, we need to edit the XML file of the virtual machine.
# In virt-manager, go to edit > preference, and check '''Enable XML edit'''.
# In virtual machine details, go to display card. Under the XML tab, change the value of '''vgamem''' to 65536, then apply the change.
<br clear="all" />

==File sharing between host and guest== 
For Linux guests, Virtio-FS and 9p are available for file sharing. See [https://wiki.archlinux.org/title/Libvirt#Sharing_data_between_host_and_guest ArchWiki] for more information.
<br clear="all" />
For Windows guest, the easiest way to share file between host and guest is through [https://wiki.manjaro.org/index.php/Using_Samba_in_your_File_Manager SAMBA].
# Create a SAMBA usershare
# In Windows guest, enter '''\\192.168.122.1''' in the file explorer, and you should be able to see the usershare on your host.
# Map that SAMBA usershare to a new drive, and connect to it with the appropriate credential. That's it.
Check [https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_virtualization/sharing-files-between-the-host-and-its-virtual-machines_configuring-and-managing-virtualization#sharing-files-between-the-host-and-windows-virtual-machines_sharing-files-between-the-host-and-its-virtual-machines this article] for more information.
<br clear="all" />

==Optimize vCPU== 
Check [https://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/ch25s06.html this article] to customize vCPU topology for better performance.
<br clear="all" />
For example, my CPU has 1 socket, 8 cores, and 16 threads in total. The automatic topology assigns 4 sockets, 1 core, and 1 thread to my guest. After changing it to 1 socket, 4 cores, and 1 thread, the performance increases significantly.
<br clear="all" />

= References = 


'''[https://virt-manager.org/ Virt-manager]'''
<br clear="all" />
'''[http://libvirt.org/ Libvirt]'''
<br clear="all" />
'''[http://wiki.qemu.org/Main_Page Qemu]'''
<br clear="all" />
'''[https://en.wikipedia.org/wiki/X86_virtualization x86 virtualization]'''
<br clear="all" />
'''[http://ark.intel.com/Products/VirtualizationTechnology Intel-vt]'''
<br clear="all" />
'''[http://www.amd.com/en-gb/innovations/software-technologies/processors-for-business/virtualization Amd-v]'''
<br clear="all" />
</translate>
[[Category:Contents Page{{#translation:}}]]

Swap

2021-12-25T09:18:18Z

Oguzkagan: Marked this version for translation

<languages />
<br />
__TOC__

<translate>
=Overview= 


Swap space is used to extend the amount of memory(RAM) available for running programs.</translate>
* <translate> Without swap space, if you run out of memory, applications ''will'' be terminated up to and including the entire system crashing.</translate>
* <translate> With swap space available to the system, the kernel can take less frequently accessed memory pages from inactive applications / services and write them to disk ("swapping" them), allowing more actual RAM to be available for active applications.</translate>

<translate> There are three different ways in which swap can be managed in Manjaro:</translate>
* <translate> A swap partition</translate>
* <translate> A swap file</translate>
* <translate> zswap</translate>

<translate> This article tries to be as comprehensive as possible but even more information can be found in the [[<tvar|link>Special:MyLanguage/#See_Also</>|articles linked below]]</translate>
<translate>
=Do I Need Swap= 


That is a question that cannot be answered without having a look at your configuration and even with plenty of available memory, it is often used as a safety net or even sometimes due to specific application requirements so have a look at the following non-exhaustive list:</translate>
* <translate> If you use hibernation: ''yes, you need swap!''</translate>
* <translate> If you have services that are not always active, but are still running all the time: ''yes, you need swap!''</translate>
* <translate> If you have an application that allocates virtual memory directly for temporary storage instead of RAM: ''yes, you need swap!''</translate>
* <translate> If you have an application that has a memory leak: ''yes, you need swap!''</translate>
* <translate> If you have a server with 1TB of RAM that you're using as a desktop without applications allocating virtual memory or having memory leaks: ''No, you don't need swap!''</translate>
<translate>
=How Much Swap do I Need= 


The amount of swap you need is highly variable based on ''your'' specific applications and workload. There is no universal formula on swap size without monitoring usage over a period of time. A reasonable place to start would be:</translate>
* <translate> For less then 4GB of physical memory (RAM), it's highly recommended that the swap space should, as a base minimum, be equal to the amount of RAM. Also, it's recommended that the swap space is maximum twice the amount of RAM depending upon the amount of disk space available for the system because of diminishing returns.</translate>
* <translate> For more modern systems (>4GB), your swap space should be at a minimum be ROUNDUP(SQRT(RAM)) I.E. the square root of your RAM size rounded up to the next GB. '''However, if you use hibernation''', you need a minimum of physical memory (RAM) size '''plus''' ROUNDUP(SQRT(RAM)). The maximum, is again twice the amount of RAM, again because of diminishing returns.</translate>
* <translate> The only downside to having more swap space than you will actually use, is the disk space you will be reserving for it cannot be used for application or system data.</translate>

<translate> The "diminishing returns" means that if you need more swap space than twice your RAM size, you would be better off adding more RAM as Hard Disk Drive (HDD) access is about 10³ slower then RAM access, so something that would take 1 second, suddenly takes more then 15 minutes! And on a Solid State Drive (SSD) the same operation that took 1 second in RAM will still take about 1 minute on that SSD!</translate>

<translate>
Taking into account all of the above, this brings us to the following table:
(last 3 columns denote swap space)</translate>

<translate> RAM No hibernation With Hibernation Maximum</translate>
1GB 1GB 2GB 2GB
2GB 2GB 3GB 4GB
3GB 3GB 5GB 6GB
4GB 4GB 6GB 8GB

<translate> RAM No hibernation With Hibernation Maximum</translate>
5GB 2GB 7GB 10GB
6GB 2GB 8GB 12GB
8GB 3GB 11GB 16GB
12GB 3GB 15GB 24GB
16GB 4GB 20GB 32GB
24GB 5GB 29GB 48GB
32GB 6GB 38GB 64GB
64GB 8GB 72GB 128GB
128GB 11GB 139GB 256GB
256GB 16GB 272GB 512GB
512GB 23GB 535GB 1TB
1TB 32GB 1056GB 2TB
2TB 46GB 2094GB 4TB
4TB 64GB 4160GB 8TB
8TB 91GB 8283GB 16TB
{{note|<translate> The largest server one of the authors of this wiki article has ever installed had, indeed, 8TB of RAM and even that machine has the above swap settings, so why not your machine?</translate>}}
<translate>
=Displaying Swap Information= 


The command {{ic|swapon}} will display your current swap information. For example:</translate>
swapon
NAME TYPE SIZE USED PRIO
/dev/sda7 partition 20G 44.3M -2

<translate> The following script will:</translate>
* <translate> show whether zswap is active or not and if active, give zswap parameters if run with the {{ic|sudo}} command</translate>
* <translate> display a list of all applications / services that take up swap and how much they take up in descending order</translate>

#!/bin/bash
#Check whether running as root
if [ "$(whoami)" = 'root' ]; then
dmesg | grep "zswap:" | grep --silent "load"
if [[ $? -eq 0 ]]; then
# zswap is active
echo "zswap information:"
grep --recursive --color=none . /sys/kernel/debug/zswap/
read -n 1 -s -r -p "Press any key to continue"
else
echo "[warning] zwap not active. Continuing"
fi
else
echo "[warning] Not running as root: skipping zswap info"
fi
for szFile in /proc/*/status ; do
awk '/VmSwap|Name/{printf $2 "\t" $3}END{ print "" }' "$szFile"
done | sort --key 2 --numeric --reverse | more
<translate>
=Using a Swap Partition= 


A swap partition is the traditional way of managing swap. In this scenario, a dedicated partition (or partitions) are created for holding swap.</translate>
<translate>
==Creating and Enabling a Swap Partition== 


To create a swap partition, you need enough unallocated disk space to create an additional partition. If you do not have enough space, skip to the next section [[<tvar|link>Special:MyLanguage/#Using_a_swap_file</>|#Using_a_swap_file]]. A swap partition can be created in any disk management / partition management tool and should be set as type {{ic|linuxswap}}.</translate>

<translate> Once you have a swap partition you will need to initialize the swap partition with {{ic|mkswap}}. For example, if your swap partition is {{ic|/dev/sda3}}, you could use the command:</translate>
sudo mkswap /dev/sda3

<translate> Next we need to enable the swap partition with the {{ic|swapon}} command. Following our example above this could be done with:</translate>
sudo swapon /dev/sda3

<translate> In order to ensure that the swap is enabled at boot we can add an entry to {{ic|/etc/fstab}}. It is best to use the UUID instead of the device name for this purpose. You can add the line to fstab manually or using the command:</translate>
sudo bash -c "echo UUID=$(lsblk -no UUID /dev/sda3) none swap defaults 0 0 >> /etc/fstab"

<translate> If you would like to have more than one swap partition, simply repeat the steps above for any additional partitions.</translate>

{{note|<translate> Be sure to replace /dev/sda3 in the above commands with your actual swap partition.</translate>}}
{{tip|<translate> ''If you're using a HDD'' (spinning rust) put the swap partition *at the beginning of the disk* as the speed of the disk is higher on the inside tracks. On an SSD this doesn't matter.</translate>}}
<translate>
=Using a Swapfile= 


Using a swap partition has one major disadvantage: Changing the size of swap or adding swap requires repartitioning the disk. In current Linux kernels, it is possible to use a swap file instead of a dedicated partition and as from kernel 2.6 onwards there is no performance difference any more between the two.</translate>

<translate>
==Creating and Enabling a Static Swapfile== 
</translate>
{{tip|<translate>
There is no reason you can't have both a swap partition and a swapfile. This is an easy way to add more swap without repartitioning.
</translate>}}

<translate>
First create and intialize the file to hold the swap. For example, to create a 4GB swapfile, you could use the command:
</translate>

sudo dd if=/dev/zero of=/swapfile bs=1M count=4096 status=progress

<translate>
Set the appropriate permissions on the file. It should be readable and writable only by {{ic|root}}. This can be done with the command:
</translate>

sudo chmod 600 /swapfile

<translate>
Next we need to format and enable the swapfile:
</translate>

sudo mkswap /swapfile

sudo swapon /swapfile

<translate>
In order to ensure that the swap is enabled at boot we can add an entry to {{ic|/etc/fstab}}. You can add the line to fstab manually or using the command:
</translate>

sudo bash -c "echo /swapfile none swap defaults 0 0 >> /etc/fstab"

<translate>

==Swapfiles on BTRFS== 


As of kernel 5.0 and higher, swapfiles are supported on btfrs. They still require some special handling in addition to the above steps.</translate>

<translate> Prior to running the {{ic|fallocate}} step above, you should run these commands:</translate>
sudo truncate -s 0 /swapfile
sudo chattr +C /swapfile
sudo btrfs property set /swapfile compression none

<translate> These commands create an empty swapfile, disable COW for that file and ensure that compression is disabled.</translate>

{{tip|<translate>
To stay compatible with Timeshift, it is necessary to create the swapfile outside the root subvolume "@".
<tvar|RootCmd>{{RootCmd|command=btrfs subvolume create /@swapfile}}</>
Just replace /swapfile with /@swapfile/swapfile.
</translate>}}

<translate>

==Swapfiles on ZFS== 


zfs doesn't support swapfiles, however you can achieve a similar benefit using a zvol as a swap volume.


Detailed instructions on how to accomplish this can be found in this [<tvar|link>https://github.com/zfsonlinux/pkg-zfs/wiki/HOWTO-use-a-zvol-as-a-swap-device</> ZoL guide].
</translate>
<translate>
=Automated Swap Management with systemd-swap= 
</translate>
{{note|<translate> Using systemd-swap with on btrfs/zfs or with hibernation support requires special handling beyond the scope of this article</translate>}}

<translate> It is possible to automatically manage the size of your swapfile using {{ic|systemd-swap}}. It can create swap files dynamically based on memory needs. It is also an easy way to enable/manage [[<tvar|link>#Using_zswap_with_systemd-swap</>|zswap]]</translate>

<translate>
==Installing and Configuring systemd-swap== 


First, install and enable {{ic|systemd-swap}}:</translate>
pamac install systemd-swap
sudo systemctl enable systemd-swap.service

<translate> Next enable dynamic swap management by creating a file {{ic|/etc/systemd/swap.conf.d/myswap.conf}} with the following parameters:</translate>
zswap_enabled=0
zram_enabled=0
swapfc_enabled=1

<translate> If you would prefer a single command to create this file you could use:</translate>
sudo bash -c 'echo -e "zswap_enabled=0\nzram_enabled=0\nswapfc_enabled=1" > /etc/systemd/swap.conf.d/myswap.conf'

<translate>
==Remove Other Swap== 


In order for systemd-swap to be effective you need to remove any traditional swap devices you have.</translate>

<translate> To display your current swap devices you can use the command {{ic|swapon}}. For example, my test machine displays the following:</translate>
swapon
NAME TYPE SIZE USED PRIO
/swapfile file 4G 0B -2
/dev/sda3 partition 8.4G 0B -3

<translate> In this example there are two swap devices. A swapfile and a swap partition. To turn them off we can use the command {{ic|swapoff}}.</translate>
sudo swapoff /swapfile
sudo swapoff /dev/sda3

<translate>
Next we need to remove them.
The swap partition will need to be deleted using your favorite partitioning tool. You can remove the swapfile by simply deleting it.</translate>
sudo rm /swapfile

<translate> We need to also remove any lines related to swap from {{ic|/etc/fstab}}. Edit the file with an [[<tvar|link>Special:MyLanguage/Viewing_and_editing_configuration_files</>|appropriate text editor]] and remove or comment out the lines for the swap space. In the example above, we would remove these lines:</translate>
UUID=c2430cf1-8ea9-4422-a5c5-5a38779194c3 swap swap defaults,noatime 0 2
/swapfile none swap defaults 0 0

<translate>
With hibernation configured it will also be necessary to edit {{ic|/etc/default/grub}}. Find and remove option {{ic|<nowiki>resume=UUID=...</nowiki>}} or replace the UUID with a new proper value. In the example above, we would remove this text:
resume=UUID=c2430cf1-8ea9-4422-a5c5-5a38779194c3
Then run:
sudo update-grub
If removing hibernation entirely then also delete {{ic|resume}} from the {{ic|HOOKS}} line in {{ic|/etc/mkinitpcio.conf}} and run:
sudo mkinitpcio -P
</translate>

<translate> Next reboot. After the reboot, when running {{ic|swapon}} you should see something similiar to the following:</translate>
NAME TYPE SIZE USED PRIO
/var/lib/systemd-swap/swapfc/1 file 512M 0B -2

<translate> systemd-swap will add and remove swapfiles as your memory usage dictates.</translate>

{{note|<translate> If you don't delete your existing swap partition it will be automatically activated by systemd even though you have removed it from fstab</translate>}}

<translate>

==Using zswap with systemd-swap== 


zswap is compressed swap kept in RAM. zswap keeps the most frequently used pages in RAM and writes less frequently used pages to the swap space on disk. In many workloads, this will result in increased swap performance and less wear and tear on SSDs.


To enable zswap with systemd-swap, simply alter the instructions above and set Linux Kernel parameter zswap_enabled=1</translate>
<translate>
=Tuning & Performance Considerations= 


Although swap seems like a great way to expand memory, excessive swap use will cause severe performance degradation, as mentioned before.</translate>

<translate> There are couple of parameters that can be used to tune swap utilization. These are swappiness and vfs_cache_pressure. To see your current settings for these you can use the following commands:</translate>
cat /proc/sys/vm/swappiness
cat /proc/sys/vm/vfs_cache_pressure

<translate> {{ic|swappiness}} controls how likely a page is to be transferred to swap. This value represents the percentage of the free memory before activating swap. The lower the value, the less swapping is used and the more memory pages are kept in physical memory where:</translate>
* <translate> 0 disables swap</translate>
* <translate> 60 is the default value which is ideal for a server that is memory-starved and running a lot of services</translate>
* <translate> 100 is very aggressive swapping.</translate>

<translate> For ''most'' desktop computers the recommended value is 10: Theoretically, this means to only start swapping when RAM usage reaches around 90 percent.</translate>

<translate> {{ic|vfs_cache_pressure}} used to be a percentage value that controls the tendency of the kernel to ''reclaim'' the memory which is used for caching of directory and inode objects with a default value of 100 on Kernels <5.4. On Kernels >=5.4 can be increased beyond 100.</translate> <translate> Increasing this value will increase the rate in which these objects are removed from the RAM cache. Decreasing it will allow these objects to be cached in memory longer, consuming additional RAM over time.</translate> <translate> Depending on your specific workload, increasing or decreasing this value too far can have significant negative impacts on system performance.</translate> <translate> Experimentation is needed to find the appropriate balance and the default value is reasonable. In general, it is more common to optimize swappiness before experimenting with vfs_cache_pressure.</translate>

<translate> To set these values you can use the command {{ic|sysctl}}. For example, to set the swappiness value to 10 you could use:</translate>
sudo sysctl vm.swappiness=10

'''<translate> There is no preset defined answer on the optimal values for these parameters.</translate>''' <translate> Experimentation is needed to find the optimum configuration for your specific hardware and workload.</translate>

<translate>
=See Also= 
</translate>
* <translate> The Arch Wiki page on [<tvar|link>https://wiki.archlinux.org/index.php/Swap</> swap]</translate>
* <translate> The Arch Wiki page on [<tvar|link>https://wiki.archlinux.org/index.php/Zswap</> zswap]</translate>
* <translate> The Linux kernel documentation on [<tvar|link>https://www.kernel.org/doc/Documentation/vm/zswap.txt</> zswap]</translate>
* <translate> The Linux kernel documentation on [<tvar|link>https://www.kernel.org/doc/Documentation/sysctl/vm.txt</> swappiness and vfs_cache_pressure]</translate>
* <translate> The openSUSE guide to [<tvar|link>https://doc.opensuse.org/documentation/leap/tuning/html/book.sle.tuning/cha.tuning.memory.html</> tuning memory]</translate>
* <translate> The [<tvar|link>https://github.com/Nefelim4ag/systemd-swap</> systemd-swap page]</translate>
* <translate> The ZFS on Linux guide on [<tvar|link>https://github.com/zfsonlinux/pkg-zfs/wiki/HOWTO-use-a-zvol-as-a-swap-device</> Swap Volumes]</translate>

[[Category:Contents Page{{#translation:}}]]

Printing

2021-12-25T09:17:11Z

Oguzkagan: Marked this version for translation

<languages/>
__TOC__

<translate>
= Overview = 


Printing is undertaken through the use of [http://en.wikipedia.org/wiki/CUPS CUPS] (previously an acronym for '''C'''ommon '''U'''nix '''P'''rinting '''S'''ystem). This is a popular open source printing system used in most Linux distributions due to its ease of use.

= Installing the Printer Software = 


First, install the {{ic|manjaro-printer}} package using your favorite package manager or by using the command:
pamac install manjaro-printer


Note that you may need to add yourself to the {{ic|sys}} group. To do this, us the command:
sudo gpasswd -a yourusername sys

= Enabling Printing Capabilities = 


Once the necessary software has been installed, to start and enable printing capabilities, enter the following commands:
sudo systemctl enable --now cups.service
sudo systemctl enable --now cups.socket
sudo systemctl enable --now cups.path


At this point you should be ready to configure a printer

=Managing Printers= 

==Managing Printers with HP Device Manager== 
[[File:Hplip.png|left|375px]]


If have a printer made by HP, the easiest way to manage it is with the HP Device Manager({{ic|hp-toolbox}}). It is wizard based and handles automatic detection and setup of your printer locally or across a network.


You can run it by selecting '''HP Device Manager''' from the menu or with the command {{ic|hp-toolbox}}.


<br clear="all" />

==Managing Printers with CUPS== 


Another way to add a printer is to use CUPS directly. Assuming CUPS has been enabled (and started), upon connecting a printer, it should be automatically detected and configured for you to use. The process itself should take only about a minute. However, if the automatic detection and configuration doesn't seem to work, then your printer can be manually set up with relative ease. There are two methods to do so:


* '''Webpage Interface''': CUPS provides an webpage interface that will open in your default web browser to configure your printer. This interface also provides access to further information about CUPS, as well as on-line help.


* '''Desktop Interface''': A standard desktop wizard is also available, which should be instantly familiar to those who have configured a printer before, whether using Linux or another operating system such as windows. Note that you may need to install the {{ic|system-config-printer}} package using your favorite package manager or by using the command:
pamac install system-config-printer.

===CUPS Webpage Interface=== 


[[File:CUPSweb.png|thumb|left|375px]]


To access the webpage interface, select '''Manage Printing''' from your desktop menu. The interface will automatically open in your default web browser. Alternatively, you can also open your choice of web browser, and enter the following into the address bar:


http://localhost:631/


{{tip|You can also just click the address provided above to access the CUPS web interface!}}
<br clear="all" />

===CUPS Desktop Interface Part 1: The Automatic Method=== 


[[File:CUPS1.png|thumb|left|375px]]


'''1. Add your printer'''. Ensuring that your printer is properly connected and switched on, select '''Print Settings''' from your desktop menu. Once the ''Print Settings'' window has opened, click '''+ add''' to add a new printer.
<br clear="all" />


[[File:CUPS2.png|thumb|left|375px]]


'''2. Select your printer name'''. Once the ''New Printer'' window has opened, under the '''Select Device''' heading, find the name of your printer and click to highlight it. If your printer is listed more than once, check the description on the right to ensure your selection is not for another function, such as scanning or faxing.


'''3. Select your printer connection'''. Under the '''Connection''' heading, click to highlight your printer's connection method. As illustrated, this will usually always be 'USB'.
<br clear="all" />


[[File:CUPS3.png|thumb|left|375px]]


'''4. Install your printer driver'''. Once your printer name and connection have been highlighted, click the '''Forward''' button and CUPS will automatically search for the available drivers for it. In most instances, once the appropriate driver has been found it will be automatically installed, and the set-up process will have completed.


Otherwise, if the process did not succeed, it will be necessary to click the forward button again in order chose the appropriate driver yourself.
<br clear="all" />

===CUPS Desktop Interface Part 2: The Manual Method=== 


[[File:CUPS4.png|thumb|left|375px]]


{{tip|CUPS will usually help you out by showing recommended choices for each step.}}


'''1. Select your printer make'''. If the Automatic method did not automatically find and install an appropriate driver for your printer, then clicking the forward button again will present the ''Chose Driver'' window. The first step is to select the make of your printer. As illustrated, as an HP printer is to be installed, the recommended choice of ''HP'' has been highlighted by clicking on it.


Once your make of printer has been highlighted, click the forward button to proceed to the next step.
<br clear="all" />


[[File:CUPS5.png|thumb|left|375px]]


'''2. Select your printer model'''. Under the left-heading '''models''', select the specific model of your printer. As illustrated, as the printer model to be installed in this instance is a Model 2210, the recommended choice of ''PSC 2210'' has been highlighted by clicking on it.


'''3. Select your printer driver'''. At last! Under the right-heading '''Drivers''', select the appropriate driver for your printer. As illustrated, the recommended printer driver has been clicked to highlight it. '''It is advised that you also select whatever driver is recommended for you'''.


Once your printer model and driver have been highlighted, click the forward button to proceed to the next step.
<br clear="all" />


[[File:CUPS6.png|thumb|left|375px]]


'''4. Choose your printer name, description (optional), and location (optional)'''. Unless you want to change something, it will not be necessary to make any amendments here.


If you are happy with the information provided - or have made the desired changes - click the '''Apply''' button to complete the process.
<br clear="all" />


[[File:CUPS7.png|thumb|left|375px]]


'''5. Configure your printer'''. Having clicked the Apply button in the previous step, your printer's properties will be displayed. By selecting the categories on the right-hand side, you can view information and amend your printer's settings if you wish. '''The standard settings will be fine for most people, so unless you have something specific in mind, there will be nothing you need to do'''.


'''6. Test your printer'''. Although optional, this step is highly recommended! Click the '''Print Test Page''' button to ensure that your printer is set up and working properly.


{{tip|Your printer properties can be accessed - and changed - at any time by selecting the '''Print Settings''' option from your menu, and then double-clicking your printer's icon.}}


That's it! Now click the '''OK''' button to close the window and start using your printer.
<br clear="all" />

===Modifying an Installed Printer=== 


To configure an installed printer at any time:


'''1.''' select the '''Print Settings''' option from your desktop menu, and


'''2.''' double-click the printer's icon.


The configuration window will appear. Select any of the categories on the left-hand side of the window to view the appropriate information and make any desired changes. Once complete, click the '''Apply''' and then '''OK''' buttons to confirm and save your changes, or click the '''Cancel''' button to close the window without making any changes.

===Removing an Installed Printer=== 


If for any reason you wish to remove a printer (e.g. to reinstall it), select the '''Print Settings''' option from your menu, right-click your printer's icon, and then select '''delete'''. You will need to confirm your decision to delete the printer, as well as enter your password to complete the task.

= Disabling Printing Capabilities = 


If for any reason you wish to disable CUPS (e.g. in order to use an alternative printing system), open your terminal and enter the following command:
sudo systemctl disable --now cups.service
sudo systemctl disable --now cups.socket
sudo systemctl disable --now cups.path

= Specific printers/scanners that are known to work = 


{| class="wikitable"
|-
! Brand !! Type !! Print !! Scan !! Description how to set up !! Issues & Solutions !! More info !!
|-
| Canon || mp 280 || Yes, via network|| Yes, only local || CUPS and manjaro-printer || Remote scanning
|-
| Canon || Pixma MX535 || Yes, via network|| Yes, via network || Manjaro printer detects remote printer as mx530 & scanner and sets them up with no specific driver.|| Needs avahi and in my case ipv6 for some reason to be able to 'see' the printer (@hanzel on the forum)
|-
| Canon || PIXMA TR4522 || || || Needs: cnijfilter2 or cnijfilter2-bin from the [[Arch_User_Repository|AUR]] || || [https://forum.manjaro.org/t/installing-a-canon-pixma-tr4522/78221 forum post]
|-
| Canon || PIXMA TS5120 || Yes|| Yes || Scanner seems to work after CUPS and manjaro-printer, printing requires cnijfilter and selecting Canon TS5100 series drivers|| Needs: cnijfilter2 or cnijfilter2-bin from the [[Arch_User_Repository|AUR]] || ||
|-
| Epson|| WF-3825 driver || || || Needs: epson-inkjet-printer-escpr2 [[Arch_User_Repository|AUR]] || || [https://forum.manjaro.org/t/epson-wf-3825-driver/77910/5 Forum post]
|-
| Canon || Pixma Pro-100 || Yes, via network and local || Not a feature || manjaro-printer || Takes a moment to start printing, just be patient
|-
| Canon || ISensys || LBP223dw || Yes || || || [https://forum.manjaro.org/t/installation-canon-i-sensys-lbp223dw/80306 forum post]
|-
| Canon || Pixma E4270 || Yes via Network || not tested || Needs: cnijfilter2 or cnijfilter2-bin from the [[Arch_User_Repository|AUR]] || || [https://forum.manjaro.org/t/canon-pixma-e4270/86212 forum post]
|-
| Canon || Pixma G2100 || Yes || Yes || Plug& play || || [https://forum.manjaro.org/t/does-canon-printers-well-supported/87040/5 forum post]


|}


Table made from suggestion [https://forum.manjaro.org/t/printer-overview-and-functionality-on-manjaro/79794 here]

</translate>

[[Category:Contents Page{{#translation:}}]]

Pamac

2021-12-25T09:16:47Z

Oguzkagan: Marked this version for translation

<languages/>
__TOC__

<translate>
=Overview= 


Pamac (Add/Remove Software) is Manjaro's Package Manager. It is based on libalpm with AUR and Appstream support. It focuses on providing an easy to use interface while still providing a powerful set of features.


[[File:Pamac-gtk-main.png|center|800px]]

=Installing Pamac= 


Pamac is pre-installed on many Manjaro Editions but if your system does not have it it can be easily installed. Pamac comes in several different packages:
* {{ic|pamac-gtk}} - The GTK version of pamac. Includes a tray icon for many desktops.
* {{ic|pamac-cli}} - The command line version of pamac.
* {{ic|pamac-tray-appindicator}} - A tray icon for KDE plasma


These packages can be installed using pacman. For example, to install the GTK version, you can use the command:
sudo pacman -Syu pamac-gtk


{{tip|Both the GTK and Qt Pamac packages will automatically install the CLI version as well}}

=Using the Pamac GUI= 

==Installing Software== 


[[File:Pamac-gtk-optional-deps.png|left|thumb|400px]]


To install packages simply check check the box next to the packages. Once you have selected all the packages all the packages you want to install, click the Apply button at the bottom of the page.


If any of the packages have optional dependencies(packages that enable additional functionality) you will see a window like the one to the left which allows to select the ones you would like to install.
<div style="clear: both"></div>
[[File:Pamac-gtk-transaction-summary.png|left|thumb|400px]]


After you have selected optional dependencies, you should see a windows similar to the one pictured on the left. This lists all the packages that will be installed, upgraded or removed by the action. Once you have reviewed the list, press the Apply button to install the packages.


You may notice this list has more packages than you selected in the GUI. This is because many packages also have dependencies which are packages that must be installed in order for the software you selected to function properly. You may also notice that packages are being removed even though you didn't select any packages to remove. This is happening in the example to the left where you can see {{ic|clutter}} and {{ic|cogl}} are being removed. They are being removed because they conflict with {{ic|deepin-clutter}} and {{ic|deepin-cogl}} which provide the same functionality.
<div style="clear: both"></div>

==Removing Software== 


[[File:Pamac-gtk-remove-summary.png|left|thumb|400px]]


Removing software is as simple as unchecking the packages you want to remove and clicking the Apply button at the bottom of the page.


Once you do you should see a screen similar to the one on the left which lists all the packages that are about to be removed. You may notice this list contains more packages than you selected. This is because when you remove a package that other packages depend on, those packages are also removed.


{{warning|It is extremely important to carefully review the Transaction Summary before accepting the package removal. Some packages have many packages which depend on them and you don't want to inadvertently remove your whole Desktop Environment}}
<div style="clear: both"></div>

==Preferences== 


You can access the preferences by clicking on the three dots in the upper right corner and selecting preferences.


[[File:Pamac-gtk-preferences-general.png|left|thumb|400px]]


The General tab of preferences contains several settings, most of which are self explanatory.


* Remove unrequired dependencies - This removes dependencies which are no longer required by any package
* Check available disk space - Checks to ensure you have sufficient disk space available before downloading and installing packages
* Maximum parallel downloads - The number of concurrent downloads allowed
* Enable downgrade - This allows packages to be downgraded as well as upgraded. This is important when [[Switching_Branches|switching branches]].
* Check for updates - Disabling this will stop Pamac from looking for updates. In most cases, turning this off on a [[The Rolling Release Development Model|rolling release]] distro like Manjaro is a bad idea.
* Ignore updates for - This is a list of packages that you don't want to be upgraded. This is inherently dangerous practice and should only be used by advanced users.


{{warning|Ignoring updates for individual packages will leave you in an unsupported "partial upgrade" state. It is common for innocuous looking ignored packages to leave your system unbootable}}
<div style="clear: both"></div>


{{warning|'''DISCLAIMER:''' AUR scripts are created for Arch Linux by Arch Linux Users. AUR packages are user-produced content. These PKGBUILDs are completely unofficial and have not been thoroughly vetted. Any use of the provided files is at your own risk.}}


[[File:Pamac-gtk-preferences-aur.png|left|thumb|400px]]


Pamac is also capable of using scripts from the [[Arch User Repository|Arch User Repository(AUR)]] to install or update packages. Please carefully read the considerations in the [[Arch User Repository|linked page]] prior to enabling support for AUR.


If you enable AUR support, you may also select, "Check for updates from AUR" so software you install from AUR won't become outdated. An alternative is creating an account on AURweb and subscribe to notifications for the scripts you are using on a permanent basis.


Checking for "development package" updates will allow updates on *-git packages which are built from the latest source code to also be updated.


The "Build directory" is where AUR packages will be built. Using "tmp" usually will provide the best performance but very large packages may fail to build. In this case, select somewhere with more available space.
<div style="clear: both"></div>
[[File:Pamac-gtk-preferences-cache.png|left|thumb|400px]]


When Pamac installs packages, it keeps a copy of all the old packages you have downloaded. This cache can be very useful if you have to download packages in an emergency. However, left unchecked, this cache will grow very large over time. These preferences allow your cache to be automatically managed based on your preferences.


The first option allows you to set a number for how many copies of each package are retained. In other words, if you have downloaded 25 versions of firefox over the life of your install and you set this number to "3", only the most recent 3 versions will be retained. Unless you are very short on disk space, it is recommended to set this to at least 2.


By selecting "Remove only the versions of uninstalled packages" pamac will retain all versions of packages you still have installed.
<div style="clear: both"></div>

=Using the Pamac CLI= 


Pamac also includes a fully functional CLI for when you don't have a functional GUI or for those that prefer to manager packages that way.


{{warning|Never use sudo with pamac. It will ask for escalated rights if it needs them}}

==Locating and Installing Packages== 


To search for available packages you can use the command {{ic|pamac search}}. For example, to search the repos for packages containing the word smplayer:
<pre>pamac search smplayer
smplayer [Installed] 19.5.0-1 community
Media player with built-in codecs that can play virtually all video and audio formats
smplayer-skins [Installed] 1:15.2.0-2 community
Skins for SMPlayer
smplayer-themes [Installed] 1:18.6.0-1 community
Themes for SMPlayer</pre>


As you can see, this will also show you which packages are already installed. If you would like to search both the repos and [[Arch_User_Repository|AUR]] you add {{ic|-a}} like this:
<pre>pamac search -a smplayer
smplayer [Installed] 19.5.0-1 community
Media player with built-in codecs that can play virtually all video and audio formats
smplayer-skins [Installed] 1:15.2.0-2 community
Skins for SMPlayer
smplayer-themes [Installed] 1:18.6.0-1 community
Themes for SMPlayer
papirus-smplayer-theme-git 20181024-2 AUR
Papirus theme for SMPlayer (git version)
smplayer-svn 17.12.0.r8852-1 AUR
Advanced front-end for MPlayer/MPV
smplayer-svn-notitlebar 18.3.0.r8982M-1 AUR
Advanced front-end for MPlayer/MPV + Patch to disable titlebar in compact mode
smplayer-skins-svn 15.2.0.r8852-1 AUR
Skins for SMPlayer
smplayer-themes-svn 17.3.0.r8852-1 AUR
Themes for SMPlayer
smplayer-qt4 18.5.0-1 AUR
Complete front-end for MPlayer/MPV (Qt4)
rosa-media-player-plugin 1.0-2 AUR
The new multimedia player(based on SMPlayer) with clean and elegant UI (mozilla plugin only).
smplayer-theme-faenza (Out of Date: 09/15/2017) 2-2 AUR
Normal, dark and silver faenza theme for smplayer.
umplayer 0.98.2-2 AUR
An alternative to SMPlayer</pre>


Once you have identified the packages you wish to install you can install them with command {{ic|pamac install}}. For example, if we wanted to install {{ic|smplayer}} and {{ic|smplayer-themes}} we could use the command:
pamac install smplayer smplayer-themes


{{tip|When using install pamac will check to see if packages are installed and only install the ones not already installed}}


If you want to install packages from [[Arch_User_Repository|AUR]] you use the command {{ic|pamac build}}. Sticking with the above example, if you decided you wanted to install {{ic|umplayer}} instead you could the command:
pamac build umplayer

==Removing Packages== 


The command {{ic|pamac remove}} can be used to uninstall packages installed from the repos or [[Arch_User_Repository|AUR]]. For example if you wanted to remove all the packages installed above you could use the command:
pamac remove smplayer smplayer-themes umplayer


{{warning|It is extremely important to carefully review the list of packages pamac presents before confirming. Some packages have many packages which depend on them and you don't want to inadvertently remove your whole Desktop Environment}}

==Identifying Installed Packages== 


To display a list of all installed packages you can use the command:
pamac list -i

==Displaying Detailed Package Information== 


To display detailed information on a package that is in the repos or installed on your system use the command {{ic|pamac info}}. Keeping with our example:
pamac info smplayer


If you also would like to check packages in [[Arch_User_Repository|AUR]] you could use:
pamac info -a smplayer

==Updating the System== 


To check if updates are available you can use the command:
pamac checkupdates -a


To update all installed packages installed from the repos or [[Arch_User_Repository|AUR]] you can use the command:
pamac upgrade -a


{{tip|pamac update and pamac upgrade are exactly the same. You can use them interchangably.}}

==Dealing with Orphaned Packages== 


To check to see if there any orphaned packages(packages which are no longer needed) installed you can use:
pamac list -o


To remove all orphans use the command:
pamac remove -o

==Cleaning the Cache== 


When pamac installs packages, it keeps a copy of all the old packages you have downloaded. This cache can be very useful if you have to install older packages in an emergency. However, left unchecked, this cache will grow very large over time.


Otherwise, to clear the cache completely, enter the following command (and use with care):
pamac clean


A safer way to remove old package cache files is to remove all packages except for the latest three package versions using:
pamac clean --keep 3

==Other Useful Pamac Functions== 


To see which package owns a certain file on your system, use the command {{ic|pamac search -f}}. For example:
pamac search -f /usr/bin/smplayer


To force a package to be installed even if it is already installed use {{ic|pamac reinstall}}. For example:
pamac reinstall smplayer

</translate>
[[Category:Contents Page{{#translation:}}]]

Pacman troubleshooting

2021-12-25T09:16:36Z

Oguzkagan: Marked this version for translation

<languages/>
__TOC__
<translate>
= Software Installation = 


Various issues relating to the download and installation of software packages from the Manjaro repositories are dealt with here.

== "Unrecognized archive format" Error == 


It has ocurred more than once, an update is issuing these messages in a seemingly never ending stream.
[https://forum.manjaro.org/t/pacman-could-not-open-file-sync-files/20046 Pacman could not open file: sync files]


error: could not open file /var/lib/pacman/sync/core.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/extra.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/community.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/multilib.db: Unrecognized archive format


The error relates to a mismatch in the information contained in the db files at the mentioned location and the db files at the first mirror in your mirrorlist. Pacman checks a package in the database and sees if the signature file matches the one in the database. If it does not, then pacman will say the package is corrupted.


While it sometimes is possible to fix the issue simply by deleting the files and the running a pacman update it far from every time.

=== One recipe for fixing this === 


It is mandatory to ensure that the keyrings is current. By ensuring the keyrings are in shape and then redownloading the databases we reestablish the chain of trust between the keyrings and the packages.


'''You will have to find the correct names by looking at'''
Browse [https://mirror.netzspielplatz.de/manjaro/packages/pool/overlay https://mirror.netzspielplatz.de/manjaro/packages/pool/overlay] for the current manjaro-keyring
and
Browse [https://mirror.netzspielplatz.de/manjaro/packages/pool/sync https://mirror.netzspielplatz.de/manjaro/packages/pool/sync] for the current archlinux-keyring


'''Replace yyyymmdd and x with the info found at the above links'''


sudo pacman -U https://mirror.netzspielplatz.de/manjaro/packages/pool/overlay/manjaro-keyring-yyyymmdd-x-any.pkg.tar.xz
sudo pacman -U https://mirror.netzspielplatz.de/manjaro/packages/pool/sync/archlinux-keyring-yyyymmdd-x-any.pkg.tar.xz


'''Remove your faulty databases'''
sudo rm -f /var/lib/pacman/sync/*
'''Download the databases and update the system'''
sudo pacman -Syyu

== "Unable to lock database" Error == 


When downloading and installing software from the repositories, a special database lock file will be created in order to ensure that the current installation process is the only one running at that time. Otherwise, attempting to install multiple files from multiple sources simultaneously may corrupt the downloaded files, cause file conflicts - or worse still - damage your system. Once the installation has been completed, the lock file will then be automatically deleted. This error may therefore occur due to two possible reasons:


* Another installation is still taking place and has not yet finished, or
* A previous installation attempt had not finished properly (e.g. due to being aborted early)


It is therefore wise to first check to ensure that another installation is not (or had not been) in process at the time of the error. When satisfied that this is not the case, then the database lock file can be manually deleted. To do so, open up the terminal and enter the following command:


sudo rm /var/lib/pacman/db.lck


Once done, you should now be able to successfully re-attempt your intended installation.

== Errors about Keys == 


We all have our own unique signatures which are used to authenticate who we are and to prevent fraudulent or even malicious activities by others. This is also the case with software packages available from the software repositories. They all contain encrypted codes (signature keys) unique to their developers to ensure that they are authentic and not malicious in nature.


During the installation process, once any software packages have been downloaded, your system will first check their signature keys to ensure that they are authentic prior to actually installing them. If a signature key cannot be verified for any reason, then the installation process will be aborted. This problem will usually occur due to:


* one or more signature keys contained in your system's database being revoked, changed, corrupted, or out of date
* one or more software packages not having been signed off properly when placed in a repository


Where a package has not been signed off properly before being placed in a repository, it will be the responsibility of the developer(s) to correct this. However, as this problem will be more than likely due to a problem with your system's verification of a signiture key, this can be solved in three easy steps. Working net connection is required. Once you have opened your terminal:


{{Warning|The following commands only work, when your system time is set correctly! }}


<s>'''1. Remove old (and possibly broken) keys''' by entering this command:

sudo rm -r /etc/pacman.d/gnupg


'''2. Reinstall keyrings including the latest keys''':


sudo pacman -Sy gnupg archlinux-keyring manjaro-keyring


'''2. Initialize the pacman keyring''':


sudo pacman-key --init


'''4. Load the signature keys''':


sudo pacman-key --populate archlinux manjaro


'''5. Refresh and update the signature keys''':


sudo pacman-key --refresh-keys


'''6. Clear out the software packages downloaded during the aborted installation''' (optional):


sudo pacman -Sc</s>


{{BoxInfo|Info|Improved version added, since it doesn't work that way above. The packages are signed and since '''/etc/pacman.d/gnupg''' has been removed, it cannot be installed due the check. Instead editing the '''/etc/pacman.conf''' and lowering the SigLevel, it would be better installing the keyrings without a check manually to overcome this problem.}}


'''1. Remove old (and possibly broken) keys''' by entering this command:

sudo rm -r /etc/pacman.d/gnupg


'''2. Initialize the pacman keyring''':

sudo pacman-key --init


'''3. Download the packages:'''
{{BoxInfo|Info| GPG check errors can be ignored, since it only downloads the keyring packages.}}

mkdir -pv $HOME/.cache/pkg/ && sudo pacman -Syw archlinux-keyring manjaro-keyring --cachedir $HOME/.cache/pkg/


'''4. Remove the signatures:'''
{{BoxInfo|Info| Signatures must be removed to avoid the automatic check of the packages.}}

rm -f $HOME/.cache/pkg/*.sig


'''5. Install the downloaded packages manually:
{{BoxInfo|Info|This will also trigger the populate process.}}
sudo pacman -U $HOME/.cache/pkg/*.tar.zst


'''6. Clear out the software packages downloaded during the aborted installation''' (optional):
{{warning|The above command clears the pacman cache completely, and one will not be able to downgrade to a previous version of a package if required. Instead packages that are causing signing errors can be removed individually when upgrading.}}

sudo pacman -Sc

'''7. Remove the custom package folder:''' (optional):

sudo rm -Rf $HOME/.cache/pkg/


After that try running '''sudo pacman -Syu''' to see if the errors were resolved.

== Conflicting files - ''FILENAME'' exists in filesystem == 


'''If you cant can't install or update a package because of an error like this:'''


error: could not prepare transaction
error: failed to commit transaction (conflicting files)
libname: /insert/file/name/here exists in filesystem
Errors occurred, no packages were upgraded.


Then the package manager, pacman, has detected an unexpected file that already exists on the disk.


'''Why is this happening?'''


By design pacman will '''not''' overwrite files that already exist. This is a design feature, not a flaw - package managers are designed to keep track of installed files.


This issue normally happens because you've manually added, copied, or created a file. It can also happen when you install software using a downloaded executable, run a make install, or use a third-party package system such as conda. It also occurs when you install an AUR package which installs files that conflict with a repo package.


When using a third-party installer you should always specify an alternative installation location, such as under your home directory, or under /opt or /usr/local/. Never install directly under / or /usr.


'''How can I fix this?'''


The first step is to identify which, if any, package owns the file. This can be easily done with:


pacman -Qo /path/to/file


If this identifies a conflicting package you can decide to remove it with pacman -R. If no package is identified you can delete the file (or move it to a backup location).


'''Where can I read more?'''


This post was inspired by (and adapted from):


https://wiki.archlinux.org/title/Pacman#%22Failed_to_commit_transaction_(conflicting_files)%22_error


The above post also has links to further reading.

== "Configuration file...not recognized" Error == 


Manjaro's package manager - '''[[pacman]]''' - uses a file called ''mirrorlist'' to tell it the internet addresses of the Manjaro servers in order to download updates and software applications from them. This error will therefore occur if one or more server addresses contained in the mirrorlist file have not been listed properly, resulting in pacman being unable to connect to them. Another tell-tale sign is that this problem will also be encountered immediately after:


* Installing Manjaro and editing the mirrorlist file during installation, or
* Editing the mirrorlist file at a later time.


See the [[Change to a Different Download Server]] guide for more detailed information on how to correctly select and enable another Manjaro server for downloading.

== "GPGME error: No data" Error == 


The most likely cause of this issue is that an error or corruption has been detected by ''pacman'' in one or more software packages being downloaded. Package signatures and checksums are used to verify the validity of downloaded software, and should they fail, the installation attempt will be aborted to protect your system until the matter is resolved.

=== Option 1: Basic Resolution === 


To resolve this issue, first follow the basic procedure provided below. If this does not work, then there is a more comprehensive procedure available.


1. Download the package databases and update your system:


sudo pacman -Syyu


2. Clear out the software packages downloaded during the aborted installation by entering the command:


sudo pacman -Sc


3. Re-attempt the aborted download.

=== Option 2: Comprehensive Resolution === 


If the basic proceedure still does not resolve the matter, further steps are available:


1. Resynchronise with the Manjaro servers to ensure that everything is up to date by entering the command:


sudo pacman -Syy


2. Refresh and update the signature keys by entering the command:


sudo pacman-key --refresh-keys


3. Reload the signature keys by entering the command:


sudo pacman-key --populate archlinux manjaro


4. Clear out the software packages downloaded during the aborted installation by entering the command:


sudo pacman -Sc


5. Re-attempt the aborted download.


If the error still persists, then it is recommended to '''[[Change to a Different Download Server]]'''.

== "keyserver refresh failed: No dirmngr" Error == 


Try running the following command:


sudo dirmngr </dev/null

= See Also = 


* '''[[Change to a Different Download Server]]'''
* '''[[Pacman-mirrors|Reference Guide for pacman-mirrors]]'''
* '''[https://wiki.archlinux.org/index.php/Pacman#Troubleshooting Arch wiki for more comprehensive troubleshooting]'''
</translate>
[[Category:Contents Page{{#translation:}}]]

Important hidden .dot files in your home partition

2021-12-25T09:14:33Z

Oguzkagan: Marked this version for translation

<languages/>
__TOC__
<translate>

=What's a hidden <.dot> file?= 


They are files & directories with a "'''.'''" dot in front of them. Placing a "'''.'''" dot in front of a file or directory tells the operating system that such files & directories are to be hidden from view in file managers, file requesters & such. File managers & other applications can usually be set to view these normally hidden files. These hidden files & directories usually contain configuration files of some sort.


These hidden files will be referred to as ''<.dot>'' files in this article.

=Why is it worth knowing about these <.dot> files?= 


* These files contain settings/configuration information that will often need to be modified


* It is well worthwhile knowing which <.dot> directories & files in your ~/ directory are valuable in saving you time & effort if you have to reinstall Manjaro due to a hardware failure, corrupt data, user error...


* If you are coming from, or going to another distro, this can be extremely valuable knowledge. As again, these <.dot> files can save you an enormous amount of time & effort in configuring your system to be just the way you like it. More on this to come.


* This knowledge can also be used to backup important config files, some of which can have had many, many hours of work in them.

=So, what do these <.dot> files in my /home do?= 
{{note|<.dot> files are hidden by default. You usually need to enable them in your file manager or by using '''ls -A'''}}


Looking in your '''~''' directory can identify any folders that have configuration or other customised data for our system, including the DE/WM and applications.


Some examples of these are; panels, trays, clocks, text editors, image viewers, pdf viewers & other applications. A quick look in your '''~/.config''' directory will make this clear.

=A reference to key <.dot> files= 


The following represent some of the most common types of <.dot> files that are found directly in your home folder. This is not an extensive list but represents some of the most common items.


Whether the files are important or not cannot be judged in this article - it depends on how much time you have spent on customizing your configuration files. Some window managers can only be configured using these files - in that case they become important. Or you have a collection of scripts in ~/.local/bin - they have become important as they - often - represent a great amount of work.

==Directories== 


'''.cache''' - Contains cached application files. Keep an eye on this folder as sometimes application caches can grow over time.


'''.config''' - This is where most modern applications keep user specific configuartion. This is the first place you should look for application related configuration files.
Also, it is worth noting that any config files in this directory will have absolutely no effect if the program that they belong to is not installed on your machine. ''So orphan config files pose absolutely no danger''.


'''.local''' - Holds a user specific version of '''/usr/local'''. Most notably application launchers can be found in '''.local/share/applications'''


'''.local/bin''' - Folder for your own scripts - included in your PATH


'''.mozilla''' - Configuration data for Firefox


'''.thunderbird''' - Configuration and mailboxes for Thunderbird


'''.ssh''' - ssh keys, known hosts and other per user ssh configuration


'''.steam''' - Data, config and game files for Valve's Steam platform


'''.gnupg''' - database for encrypting and signing using GnuPG - your private keys are here as well

==Files== 


'''.bash_profile & .bashrc''' - Per user configuration for '''bash'''


'''.xinitrc''' - If it is present in a user's home directory, startx and xinit execute it. Otherwise startx will run the default /etc/X11/xinit/xinitrc.


'''.zshrc''' - Per user configuration for '''zsh'''


'''.netrc''' - Configurations for accessing e.g. ftp servers

=Re-using /home= 


People often get into trouble due to their keeping their old /home partition for a couple of prime reasons:


:'''1.''' Permission problems (if they are using a different user name for example).


:'''2.''' They have a mixture of hidden <.dot> files from multiple distros in '''/home'''


Before trying to re-use an existing '''/home''' be sure to review this section of the [[Partitioning_Overview_and_Existing_Partition_Tables#Where_Using_an_Existing_Linux_Partition_Table|Partioning Wiki Page]]


{{note|If you happen to have any important hidden <.dot> files before you use the above linked to Manjaro method; know that they will be overwritten.}}


When coping <.dot> files from one '''/home''' to another, it is important to be selective, especially when doing so between different distros or different versions of the same distro. For example, it is unwise to copy an entire '''~/.config''' over but perfectly safe to bring over many of the files within it on an application by application basis.

</translate>
[[Category:Contents Page{{#translation:}}]]

Firewalls

2021-12-25T09:12:43Z

Oguzkagan: Marked this version for translation

<languages/>
__TOC__

<translate>
=Overview= 


Running a local firewall is almost always a good practice. Even when you are behind a network firewall, a local firewall protects you from threats on the inside of your network.

=UFW= 


UFW stands for Uncomplicated FireWall, and is a program for managing a netfilter firewall. It provides a command line interface and aims to be uncomplicated and easy to use. UFW is far simpler than iptables and a good place to start unless you have very specialized needs.

==Installing UFW== 


You can install the {{ic|ufw}} package using you favorite package manager or the command:
<tvar|usercmd1>{{UserCmd|command=pamac install ufw}}</>


Once UFW is installed you need to start and enable it using the commands:
<tvar|usercmd2>{{UserCmd|command=sudo systemctl enable ufw.service}}</>
<tvar|usercmd3>{{UserCmd|command=sudo ufw enable}}</>


{{warning|Don't enable both iptables.service and ufw.service}}

==Adding Rules== 


To view the current configuration you can use the command {{ic|ufw status}}. Here is what it looks like in a new install:


<tvar|usercmdoutput1>{{UserCmdOutput|command=sudo ufw status verbose|result=
<pre>Status: active
Logging: on (low)
Default: deny (incoming), allow (outgoing), disabled (routed)
New profiles: skip</pre>
}}</>


This indicates that it will block all incoming traffic and allow all outgoing traffic. This is a good starting point for most desktop systems. However, often we will want to allow some incoming traffic. This can be done with the command {{ic|ufw allow}}. For example, if we want to allow incoming ssh traffic so we can connect to the machine from other machines on the network we could use the command:
<tvar|usercmd4>{{UserCmd|command=sudo ufw allow ssh}}</>


If we wanted to also tcp connections to a local webserver on a non-standard https port, 8443. We could use the command:
<tvar|usercmd5>{{UserCmd|command=sudo ufw allow in 8443/tcp}}</>


{{tip|When you don't specify "in" or "out", "in" is assumed}}

==UFW and Applications== 


You may notice a difference in the above two commands. When we built the rules for ssh we used the name and for https we used the port number, 8443. This is because UFW has a small database of applications it knows the ports for. You can see the list with the command:
<tvar|usercmd5>{{UserCmd|command=sudo ufw app list}}</>


For applications on the list you can add them by name. If you want to review the configuration for one of the applications, you can use the command {{ic|ufw app info}}. For example, to the configuration for ssh:


<tvar|usercmdoutput2>{{UserCmdOutput|command=sudo ufw app info SSH|result=
<pre>Profile: SSH
Title: SSH server
Description: SSH server

Port:
22/tcp</pre>
}}</>


{{tip|When using ufw app the commands are case sensitive but when adding rules they are not}}


Some additional preconfigured applications can be added by installing the package {{ic|ufw-extras}} with your favorite package manager or the command:
<tvar|usercmd7>{{UserCmd|command=pamac install ufw-extras}}</>

==Removing Rules== 


Rules can be removed with the {{ic|ufw delete}} command. For example, to delete our 8443 rules we could use the command:
<tvar|usercmd8>{{UserCmd|command=sudo ufw delete allow 8443/tcp}}</>


You can also delete them by number. This is easier if you have a numbered list which you can see with the command:


<tvar|usercmdoutput3>{{UserCmdOutput|command=sudo ufw status numbered|result=
<pre>Status: active
To Action From
-- ------ ----
[ 1] 22 ALLOW IN Anywhere
[ 2] 22 (v6) ALLOW IN Anywhere (v6)
</pre>}}</>


Now if we wanted to stop allowing ssh on ipv6 we could use the command:
<tvar|usercmd9>{{UserCmd|command=sudo ufw delete 2}}</>

==GUFW== 
[[File:gufw.jpg|thumb|left|240px]]


Prefer to use GUI applications and still want to manage your firewall? No problem. GUFW is a GTK front-end for UFW that aims to make managing a Linux firewall as accessible and easy as possible. It features pre-sets for common ports and p2p applications.


If it is not installed already gufw can be installed from the repos:
<tvar|usercmdA>{{UserCmd|command=pamac install gufw}}</>


It will now be available in the menu as '''Firewall Configuration''' or by running {{ic|gufw}} directly.
<div style="clear: both"></div>

=iptables= 


iptables is included as part of the Linux kernel. iptables is significantly more complicated than using a tool like UFW. As a result, a full tutorial on iptables is beyond the scope of this wiki. Using iptables on Manjaro should be the same for every distribution of Linux so there is plenty of available documentation. Some of this is linked [[Firewalls#See_Also|below]]. Here are some basics to get you started.


To enable loading rules on startup you can use the command:
<tvar|usercmdB>{{UserCmd|command=sudo systemctl enable iptables.service}}</>


This will load the rules from the file {{ic|/etc/iptables/iptables.rules}}.


To display the currently loaded rules:
<tvar|usercmdC>{{UserCmd|command=sudo iptables -L}}</>


To save the current rules to a file
<tvar|usercmdD>{{UserCmd|command=sudo sh -c "iptables-save > /etc/iptables/iptables.rules"}}</>


To load the rules from a file
<tvar|usercmdE>{{UserCmd|command=sudo sh -c "iptables-restore > /etc/iptables/iptables.rules"}}</>


To allow ssh connections
<tvar|usercmdF>{{UserCmd|command=sudo iptables -A INPUT -p tcp --dport 22 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT}}</>
<tvar|usercmdG>{{UserCmd|command=sudo iptables -A OUTPUT -p tcp --sport 22 -m conntrack --ctstate ESTABLISHED -j ACCEPT}}</>

=See Also= 
* The Arch Wiki on [https://wiki.archlinux.org/index.php/Ufw UFW]
* The [https://help.ubuntu.com/community/UFW UFW website]
* The [http://gufw.org/ GUFW website]
* The [https://linux.die.net/man/8/iptables iptables man page]
* The Arch Wiki on [https://wiki.archlinux.org/index.php/iptables iptables]
* The Debian Wiki on [https://wiki.debian.org/iptables iptables]
</translate>

[[Category:Contents Page{{#translation:}}]]
[[Category:Security{{#translation:}}]]

Encfs

2021-12-25T09:08:50Z

Oguzkagan: Marked this version for translation

<languages/>
__TOC__
<translate>
==Introduction== 


Encfs is an encryption program that is suitable for encrypting content on an already installed system. It can be used for encrypting your /home or you can make smaller private directories that can hold your encrypted data.
You can encrypt Dropbox with it and that has the advantage over Truecrypt that it does not require reserved valuable space that Truecrypt does (as of 05 2014 [http://truecrypt.sourceforge.net/index.html| Truecrypt is considered unsafe]).


Encfs does not reserve a space on your HD and simply grows and shrinks with the files you put in there.


The one thing that can seem a bit confusing about it is that you need to make two directories (folders) to make it work: one encrypted and one un-encrypted.


''Why would we need an un-encrypted folder that contains the data we want to encrypt; is that not the mother of all security flaws?''


''The entire point with encryption is that the encrypted data should not be accessible in an un-encrypted form; right?''


The way Encfs works is that the un-encrypted directory is the mount point for the encrypted content.


If you do not mount it ''nothing'' will be visible. And to mount it; you need to enter a given password.


{{BoxWarning|Warning: [https://wiki.archlinux.org/title/EncFS#Installation EncFS - ArchWiki] says:|
A [https://defuse.ca/audits/encfs.htm security review (February 2014)] of encfs discovered a number of security issues in the stable release 1.7.4 (June 2014). Please consider the report and the references in it for updated information before using the release. [https://forum.manjaro.org/t/encfs-is-not-so-safe/84983/2 see@forum] }}

==Installing== 
Encfs is in the community repo so you can simply install it with your favorite package manager or by using:
pamac install encfs

==Using it - encrypting== 


We want to make a directory that we would call
.secret
to keep our encrypted stuff, and we would make the mount point
secret
To achieve this, we run the following command in a terminal:
encfs ~/.secret ~/secret
You may also create the directories ~/.secret and ~/secret manually.

===First time run=== 
This will create the hidden directory '''.secret''' and the mount point '''secret''' the first time you run it. Just answer yes to the prompts - twice. You need to use the full path.
During first time run you will also be prompted for the encryption mode; '''x''' for expert or '''p''' for paranoia mode. We will pick '''p''' which is a good mode.


Next you will be prompted for your password. Make it long and hard to crack but don't forget it - if you do; there is no way of recovering your data.


Confirm the password and that's it you are finished.

===Regular use=== 


We have created the directory '''~/.secret''' that will contain the encrypted data and we have made it a hidden directory because we will never enter anything in it and the content will all be unreadable.


The content of '''~/.secret''' will only be readable when mounted in the other directory we created: '''~/secret'''
The only difference between the two is the "."
'''~/secret''' will be the working directory where you put the files you want encrypted.
To mount the directory we enter the command:
encfs ~/.secret ~/secret
You may call your directories something completely different than .secret and secret; it is up to you. Enter the password and start entering content into ~/secret.


''We never enter data into ~/.secret - that is why we have hidden it with a "."''


To unmount ~/secret we enter the command:


fusermount -u ~/secret


If you check the content of ~/secret now; it will be completely empty. In order to see the content again you need to mount again with


encfs ~/.secret ~/secret
and enter the password.
This will mount secret as a disk you can do a simple
df
to check if '''secret''' is mounted

==Encrypting Dropbox== 
One of the strong points of Encfs is that it does not reserve a lot of valuable space. This makes it suitable for encrypting Dropbox content.
There is no such thing as 100% security in the cloud, so remember that some things simply do not belong there.<br>
Keeping that in mind - we create a folder under ~/Dropbox that we call '''encrypted''' and we create a mount point that we call '''Dropbox_unencrypted'''.
We can create the directories manually or let enfcs auto generate them:
encfs ~/Dropbox/encrypted ~/Dropbox_unencrypted
Just like under any first time run you accept the creation of the directories with a "y" -twice and pick "p" for paranoid mode.
Then you enter the password.


To access the Dropbox from another computer repeat the exact same procedure there and enter exactly the same password.


That is all there is to it - your jiberish unreadable data will now be on the web (in the cloud) in the Dropbox/encrypted folder.<br>
It will only be readable to you after you have mounted '''~/Dropbox_unencrypted''' on your local computer.
You will also have the synced '''~/Dropbox/encrypted''' folder on your computer , and that will be as unreadable as the content on the web.<br>
As we have seen above; this content will only be visible when you mount it in ~/Dropbox_unencrypted.<br>
Again; do not put any content in ~/Dropbox/encrypted: All the content there will be added after you have mounted the working directory - '''~/Dropbox_unencrypted'''.
To test it you can unmount it with
fusermount -u ~/Dropbox_unencrypted
and re-mount it with
encfs ~/Dropbox/encrypted ~/Dropbox_unencrypted
at wich time you will be prompted for the password.

==GUI helpers== 
To mount and un-mount there are helpers in AUR that can make the handling easier.


* cryptkeeper - A Linux system tray applet that manages EncFS encrypted folders
* kencfs - GUI frontend for encfs. Create, mount, umount and delete your encrypted fs
* encfsui - Encrypted filesystem encfs GUI wrapper
</translate>

[[Category:Contents Page{{#translation:}}]]

GRUB/Restore the GRUB Bootloader

2021-12-25T09:06:41Z

Oguzkagan: Marked this version for translation

<languages/>
__TOC__
<translate>
==Overview== 
In order to load the operating system, a Linux-capable boot loader such as GRUB, rEFInd or Syslinux needs to be installed to the Master Boot Record (MBR) or the GUID Partition Table (GPT) of the media containing the Operating System. Installations created using Manjaro ISO defaults to GRUB.


For various reasons - it happens the bootloader get's corrupted, erased or misconfigured resulting to a black screen with a failure message during boot, like '''No boot loaders found in /dev/...'''. To restore system operation without re-installing your OS or losing your data you will need to use your Manjaro installation media, such as, a CD/DVD or USB Flashdrive.
{{BoxSecondary|Archlinux Boot Process|More information about the boot process on Archlinux based distributions is available at [https://wiki.archlinux.org/index.php/Arch_boot_process Archwiki]}}

==Preparation== 
Identify the type of system you are attempted to resque as the commands involved are slightly different.
* BIOS/MBR/GPT system
* EFI/GPT system

==Load Manjaro Installation Media== 
{{BoxSecondary|System Boot Override|To override system boot order the vendor has a dedicated key. Most laptop keyboard has multiple use for the function keys and the primary function may be reversed. In such case a <kbd>Fn</kbd> key must be used with the function key. If you don't know consult your system documentation. Manjaro ISO default usernames and passwords
<table>
<tr><th>Default Username</th><th>Default Password</th></tr>
<tr><td>manjaro</td><td>manjaro</td></tr>
<tr><td>root</td><td>manjaro</td></tr>
</table>
}}

==Identify partitions== 
To identify your partitions and their designated use you need to run a partition manager. Depending on environment there is various tools. GTK based ISO offers GpartEd, QT based ISO offers KParted and common to all is the CLI tools.
{{UserCmd|command=lsblk -o PATH,PTTYPE,PARTTYPE,FSTYPE,PARTTYPENAME}}
More comprehensive information can be found using {{ic|fdisk}} (requires superuser) and you can limit the probed device e.g. ''/dev/sda'' or ''/dev/nvme0n1''
{{UserCmd|command=sudo fdisk -l /dev/sda}}
The clues to look for is ''mbr'' vs. ''gpt'' and the presence of a small partition - usually the first - formatted with the ''vfat'' filesystem followed by a larger partition formatted as ''ext4''.


{{Important|This document and the content should '''never''' be used as a copy/paste resource. The remainder of this document will use pseudo names and partition numbering. Devices will be referred as '''/dev/sdy''' and partitions referred as '''/dev/sdyA''' and you will have to subtitute those with the real values from your system.}}

==Use root context== 
When you have loaded the live ISO - depending on environment - open a terminal and switch to ''root'' context. Use above mentioned root:password combination.
{{UserCmd|command=su}}

==Chroot environment== 
Chroot is a method to restrict various tasks to a restricted area e.g. package installation and other system maintenance tasks. Follow the [https://wiki.archlinux.org/index.php/Change_Root link] to read more about chroot on the Arch wiki.
===Identify system partitions===
From the above we assume you have identified the relevant partitions on your system and this document will refer the partitions as follows. Partitions not needed for this kind of maintenance has intentionally been left out (e.g. ''home'', ''swap'').
{|
|-
! Partition !! Usage !! Comment
|-
| {{ic|/dev/sdyA}} || EFI system || Required for EFI system and mounted on ''/boot/efi''
|-
| {{ic|/dev/sdyB}} || boot || Optional but mounted on ''/boot'' The primary use is when GRUB cannot write to ''/'' (eg. ''f2fs'')
|-
| {{ic|/dev/sdyC}} || root || Required and for the root filesystem and mounted on ''/'' - usually formatted using ''ext4''
|}
{{Important|If your system is a BIOS/MBR system there is no efi partition. If your system is a BIOS/GPT system you will find an unformatted partion size 1-32MB of the bios boot partition type.}}

===Use manjaro-chroot=== 
Manjaro deploys a script called {{ic|manjaro-chroot}} takes an optional argument which will search the visible devices - scan the partitions for signs of an operating system. If more than one Linux operating system is found you will get a choice of which system to chroot otherwise the file ''/etc/fstab'' from the system is used to mount the partitions and chroot into this system.This script is only available in live iso by default but you can get it in an installed system by installing {{Ic|manjaro-tools-base}} package.
{{RootCmd|command=pamac install manjaro-tools-base}}
{{RootCmd|command=manjaro-chroot -a}}

===Manual chroot=== 
(Unnecessary if you have used {{ic|manjaro-chroot}})
Mount the partitions using the designated temporary mountpoint and '''always''' start with ''root''


{{RootCmd|command=mount /dev/sdyC /mnt}}
{{Important|With a [[Btrfs|BTRFS filesystem]], you should note that the subvolumes must be mounted. That would be in such a case:{{RootCmd|command=mount -o subvol=@ /dev/sdyC /mnt}}}}
Then - if applicable - mount ''boot''
{{RootCmd|command=mount /dev/sdyB /mnt/boot}}
Then - if applicable - mount ''efi''
{{RootCmd|command=mount /dev/sdyA /mnt/boot/efi}}
Create the chroot environment and use bash as shell
{{RootCmd|command=manjaro-chroot /mnt /bin/bash}}

==Reinstall GRUB== 
One possible cause why you are reading this document - is an unfinished update - which in turn can be caused by several situations - situation we will not dive into. To fix what ever caused this you should run a full system update including grub to ensure everything is in place.
{{RootCmd|command=pacman -Syu grub}}
When the transaction as completed continue below using the section matching your system
===BIOS System===
On a BIOS/GPT system there is no MBR and therefore no place to store the loader. The GPT partition specification allows for an unformatted partition of the BIOS boot partition type (0xEF02). The size of this partition can be as small as 1 mebibyte. The Calamares installer uses a fixed size of 32 mebibyte. On a BIOS/MBR system a part of the bootloader is written to the Master Boot Record for the primary disk.


The device is the '''disk''' ('''not a partition''')
{{RootCmd|command=grub-install --force --target=i386-pc --recheck --boot-directory=/boot /dev/sdy}}
Make sure the grub configuration is up-to-date
{{RootCmd|command=grub-mkconfig -o /boot/grub/grub.cfg}}

===EFI System=== 
{{Important|You need to be in chroot for this procedure.}}
Reinstall grub
{{RootCmd|command=grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck}}
Update the grub configuration
{{RootCmd|command=grub-mkconfig -o /boot/grub/grub.cfg}}


{{BoxWarning|EFI grub install messages|EFI variables are not supported on this system.}}
Verify the existance of an EFI system partition
{{RootCmd|command=lsblk -o PATH,PTTYPE,PARTTYPE,FSTYPE,PARTTYPENAME}}
Verify the efi filesystem is loaded
{{RootCmd|command=ls /sys/firmware/efi}}
Exit chroot
{{RootCmd|command=exit}}
Try loading the efi filesystem
{{RootCmd|command=modprobe efivarfs}}
Re-enter chroot
{{RootCmd|command=manjaro-chroot /mnt /bin/bash}}
Then mount the efi filesystem
{{RootCmd|command=mount -t efivarfs efivarfs /sys/firmware/efi/efivars}}
Verify the efi filesystem is loaded
{{RootCmd|command=ls /sys/firmware/efi}}
If successfull re-run above installation commands

==Troubleshooting== 
=== Arch Linux is not recognized ===
If Arch Linux wasn't recognized after an update-grub then probably your Arch installation is missing the package lsb-release.

==See also== 
* [http://wiki.manjaro.org/index.php?title=UEFI_-_Install_Guide UEFI Install Guide]
* [https://wiki.archlinux.org/index.php/GRUB GRUB on Arch wiki]
</translate>
[[Category:Contents Page{{#translation:}}]]

Arch User Repository

2021-12-25T09:06:00Z

Oguzkagan: Marked this version for translation

<languages/>
__TOC__
<translate>
==Overview== 
{{BoxWarning|Use the AUR at your own risk!|'''No support''' will be provided by the Manjaro team for any issues that may arise relating to software installations from the AUR. When Manjaro is updated, AUR packages might stop working. '''This is not a Manjaro issue'''}}
Although Manjaro is very close to Arch Linux and mostly compatible —being based on Arch Linux itself— it is not possible to access their official repositories for use in Manjaro. Instead, Manjaro uses its own repositories in order to ensure that any software packages that are accessible, such as system updates and applications, have been fully tested to be compatible and stable before release. It is still possible to access additional software packages from the ''[https://wiki.archlinux.org/index.php/AUR Arch User Repository]'' (AUR).


The AUR is managed by the Arch Linux user community itself. Although this repository is unofficial, software packages first placed here can eventually make their way into Arch Linux's official (community) repository if they become popular enough.


'''AUR, as a community maintained repository, present potential risks and problems.'''


Possible risks using AUR packages:


* Multiple versions of the same packages.
* Out of date packages.
* Broken or only partially working packages.
* Improperly configured packages which download unnecessary dependencies, or do not download necessary dependencies, or both.
* Malicious packages (although extremely rare).


As such, although much of the software packages provided by the AUR should work, do not expect the installation process to always be quite as straight-forward as when you are using the official Manjaro repositories.


On occasion, it may be necessary to manually identify and install dependencies yourself (such as, after an aborted installation attempt).


'''Again, there is no guarantee that any installed software will work properly, if at all.'''


{{Important|You should become familiar with the manual build process in order to be prepared to troubleshoot problems.}}

==Accessing the AUR== 
===Using GUI [[Pamac]]===
Open Pamac - the name in menu is ''Add/Remove Software'' and navigate to the Preferences page. You will be required to enter your password to access it.At Preferences page → select the Third Party tab → and move the slider to enable AUR support. Be sure you have the necessary files for building applications from source
{{UserCmd|command=pamac install base-devel git}}

===Using commandline [[Pamac]]=== 
{{Important|It is '''strongly''' recommended to follow this link [https://aur.archlinux.org/ AUR website] and examine the relevant page(s) for any and all software intended to be installed.}}
These pages contain comments from both existing users and package developers, which may provide valuable information (such as, warnings and/or solutions to problems). To search for and install software packages from the AUR, the syntax is:
{{UserCmd|command=pamac search -a [software package name]}}


For example, if wishing to install ''Google Chrome'' - first follow this link to '''[https://aur.archlinux.org/packages/?K=google-chrome all Google Chrome build scripts]''' and verify which package you want to build.Or you can ask pamac - for ''Google Chrome'' candidates. Just use the search command and ''Google Chrome'' as the query. Look over the results or narrow the search parameters - just remember pamac cannot tell you of any issues with build scripts - only the relevant page. E.g. following this link to the '''[https://aur.archlinux.org/packages/google-chrome buildscript for Google Chrome]'''
{{UserCmd|command=pamac search Google Chrome}}


In the example we choose the standard version of ''Google Chrome''. To build the ''google-chrome'' package with '''pamac''' enter the following and press enter
{{UserCmd|command=pamac build google-chrome}}


You will be presented with the outcome of the chosen build with all dependencies and you will be asked a couple of questions.
# Query to edit build files. This is a precaution to verify that the build scripts does not contain malicious actions.
# Query to continue download and install dependencies then download the sources, build and install the app.
# You will be asked for your password before anything happens.

===Using GUI [[Octopi]]=== 
See [[Octopi#Accessing_the_AUR|this guide]] for enabling AUR support in Octopi.

===Installing from the AUR by hand=== 

====Manual==== 
To do that follow the steps given below:
* Be sure you have the necessary files for building applications from source


{{UserCmd|command=pamac install base-devel git}}
* Clone the PKGBUILD
{{UserCmd|command=git clone <nowiki>https://aur.archlinux.org/google-chrome.git</nowiki>}}
* Change directory to cloned folder
{{UserCmd|command=cd google-chrome}}
* To make/compile the package, run:
{{UserCmd|command=makepkg -s}}
This will build the package and pull in any dependencies needed. ''Note: it won't pull a dependency from the AUR, only from the Manjaro Repos.''. If you list the folder content
{{UserCmd|command=ls}}
you'll probably find a few new files. You're interested in the one that ends with .pkg.tar.zst
* The final event is running $sudo pacman -U on that file
{{UserCmd|command=sudo pacman -U google-chrome-ver.rel.bugfix.build-pkgrel.pkg.zst}}
And you've done it...the safest way to install from the AUR. This is essentially what most install scripts do for you.


''Note:'' Instead of using ''sudo pacman -U google-chrome-ver.rel.bugfix.build-pkgrel.pkg.zst'' can also use:
{{UserCmd|command=makepkg -i}}
''Note:'' To combine above steps into one:
{{UserCmd|command=makepkg -is}}

===Upgrading the packages installed from the AUR=== 
The following command will upgrade '''all''' packages on the system including AUR builds
{{UserCmd|command=pamac upgrade -a}}

==See Also== 
* [http://wiki.manjaro.org/index.php?title=Pacman Pacman]
* [http://wiki.manjaro.org/index.php?title=Pacman_Tips Pacman Tips]


[[Category:Contents Page{{#translation:}}]]
[[Category:Software Management{{#translation:}}]]
</translate>

Improve Font Rendering

2021-12-25T09:05:28Z

Oguzkagan: Marked this version for translation

<languages/>
__TOC__
<translate>

==How to improve font rendering with your installed fonts== 


A little configuration maybe required to render the fonts in an optimal manner. Follow the steps illustrated below.


''1. Create the global fontconfig setting file /etc/fonts/local.conf''


{{UserCmd|command=sudo nano /etc/fonts/local.conf}}


Paste the following content in the file


<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<match target="font">
<edit name="antialias" mode="assign">
<bool>true</bool>
</edit>
<edit name="hinting" mode="assign">
<bool>true</bool>
<edit mode="assign" name="rgba">
<const>rgb</const>
</edit>
<edit mode="assign" name="hintstyle">
<const>hintslight</const>
</edit>
<edit mode="assign" name="lcdfilter">
<const>lcddefault</const>
</edit>
</match>
</fontconfig>


After that save the file.


''2. Create backup of ~/.Xresources file:''
{{UserCmd|command=cp ~/.Xresources ~/.Xresources.bak}}


If the .Xresources file has not been already created and you get the error


'''''"cp: cannot stat ‘~/.Xresources’: No such file or directory"''''', then skip to step No. 3.


''3. Open/Create ~/.Xresources file in text editor:''
{{UserCmd|command=nano ~/.Xresources}}


If the following is not already present, paste at the end of the file or edit existing values:


Xft.antialias: 1
Xft.hinting: 1
Xft.rgba: rgb
Xft.hintstyle: hintslight
Xft.lcdfilter: lcddefault


Save changes to the file.


''4. Run the following command in terminal:''
{{UserCmd|command=xrdb -merge ~/.Xresources}}


''5. Make sure that ''Anti aliasing is '''On''', Hinting is set to '''Slight''''' and RGBA (subpixel) order is set to '''rgb''' in System Settings (Appearance).''


''6. Create symbolic links with some available presets from /usr/share/fontconfig/conf.avail/ to /etc/fonts/conf.d/''


{{UserCmd|command=sudo ln -s /usr/share/fontconfig/conf.avail/10-sub-pixel-rgb.conf /etc/fonts/conf.d/}}


{{UserCmd|command=sudo ln -s /usr/share/fontconfig/conf.avail/10-hinting-slight.conf /etc/fonts/conf.d/}}


{{UserCmd|command=sudo ln -s /usr/share/fontconfig/conf.avail/11-lcdfilter-default.conf /etc/fonts/conf.d/}}


''7. Set preferred serif, sans-serif and monospace fonts (optional)''


Create local fontconfig folder and setting file


{{UserCmd|command=mkdir -p ~/.config/fontconfig/}}


{{UserCmd|command=nano ~/.config/fontconfig/fonts.conf}}


Paste the following content in the file


<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<alias>
<family>serif</family>
<prefer>
<family>Liberation Serif</family>
</prefer>
</alias>
<alias>
<family>sans-serif</family>
<prefer>
<family>Liberation Sans</family>
</prefer>
</alias>
<alias>
<family>sans</family>
<prefer>
<family>Liberation Sans</family>
</prefer>
</alias>
<alias>
<family>monospace</family>
<prefer>
<family>Liberation Mono</family>
</prefer>
</alias>
<alias>
<family>mono</family>
<prefer>
<family>Liberation Mono</family>
</prefer>
</alias>
</fontconfig>


''8. Finally enable freetype2 infinality mode and reboot your computer.''


add line to end of freetype2 config file and then rebuild fontconfig cache


{{UserCmd| command=sudo nano /etc/profile.d/freetype2.sh}}


{{UserCmd| command=export FREETYPE_PROPERTIES="truetype:interpreter-version=38"}}


{{UserCmd|command=sudo fc-cache -fv}}

==See Also== 


[https://wiki.archlinux.org/index.php/Font_Configuration The Arch Wiki]

</translate>
[[Category:Contents Page{{#translation:}}]]

Main Page

2021-11-10T18:27:29Z

Oguzkagan: removed some links

<center>[[File:Main page logo.png|center|300px]]</center>

<languages/>
<translate>
==Getting Started== 
{{FlexSideContainerTemplate|
===Overview===
* '''[[Manjaro|Manjaro Overview]]'''
: ''Various articles to answer all your questions!''
* '''[[Using Manjaro for Beginners|Using Manjaro]]'''
: ''New to Manjaro? Start here for an overview! ''
* '''[[Using Manjaro for Windows users|Coming From Windows]]'''
: ''Go here if you're a Windows user trying Linux or Manjaro! ''
|
===Online and Support===
* '''[[Manjaro Online|Manjaro Online]]'''
: ''Our forum, Twitter, Reddit, and Facebook accounts.''
* '''[https://t.me/manjaro_official Manjaro Telegram]'''
: ''Additional direct support for Manjaro users.''
|1|1}}

{{FlexSideContainerTemplate|
===Get Manjaro=== 
* '''[[Download Manjaro|Download Manjaro]]'''
: ''Where to find the latest and greatest Manjaro releases.''
* '''[[Check a Downloaded ISO Image For Errors|Check a Downloaded ISO Image For Errors]]'''
: ''Check your Manjaro download for errors in Linux and Windows.''
|
===Installation===
* '''[[Burn an ISO File|Burn an ISO File]]'''
: ''Burn Manjaro to CD/DVD or USB stick in Linux and Windows.''
* '''[[Installation Guides|Install Manjaro]]'''
: ''Installation and partitioning guides for beginners and experienced users.''
|1|1}}

==Customization and Configuration== 

{{FlexSideContainerTemplate|
===Boot / Startup=== 
* '''[[BIOS and UEFI|BIOS and UEFI]]'''
: ''How to enable virtualisation, run Manjaro on Windows 10 systems, and more!''
* '''[[Display Managers / Login Screens|Display Managers / Login Screens]]'''
: ''Install, configure, or even bypass MDM, GDM, SDDM, LXDM, and SLiM.''
* '''[[Fstab - Use SystemD automount|Fstab - Use SystemD automount]]'''
: ''SystemD and /etc/fstab options for device mounting.''
* '''[[Make GRUB menu & boot-up/down fonts bigger|Larger GRUB, Boot, and Shutdown Fonts]]'''
: ''How to increase the size of boot, shutdown, and GRUB menu fonts.''
|
===DEs / WMs===
* '''[[Basic Tips for conky|Conky - Basic Tips]]'''
: ''Conky can display a lot of useful information on your desktop. ''
* '''[[Desktop Environments|Desktop Environments and Window Managers]]'''
: ''Install popular desktops and apply a range of desktop-specific configuration.''
* '''[[Set all Qt app's to use GTK+ font & theme settings|Set all Qt apps to use GTK+ font & theme settings]]'''
: ''Ensure QT apps match GTK+ DE/WM theming.''
* '''[[Set all Java apps to use GTK+ font & theme settings|Set all Java apps to use GTK+ font & theme settings]]'''
: ''Ensure Java apps match GTK+ DE/WM theming.''
|1|1}}

{{FlexSideContainerTemplate|
===Software Management=== 
* '''[[Repositories and Servers|Repositories and Servers]]'''
: ''Change repositories, find the fastest mirrors, etc.''
* '''[[Pacman|Pacman]]'''
: ''Instructions for using the '''Pac'''kage '''Man'''ager and more.''
* '''[[Graphical Software Managers|Graphical Software Managers]]'''
: ''There's a range of user-friendly software managers available''!
* '''[[Arch User Repository|Arch User Repository]]'''
: ''Learn about and use the AUR.''
* '''[[Flatpak|Flatpak]]'''
: ''Extend your software library using Flatpaks''
* '''[[Snap|Snap]]'''
: ''Install and manage Snaps on Manjaro''
* '''[[Software Applications|Software Applications]]'''
: ''A collection of tips and configurations for many applications''
|
===Hardware / MSM===
* '''[[Manjaro Settings Manager|Manjaro Settings Manager]]'''
: ''MSM can set your Language, User Account, Kernel, Time and Date, Graphics Card Drivers, and more.''
* '''[[Manjaro Hardware Detection|Manjaro Hardware Detection]]'''
: ''Kernels and Drivers.(mhwd)''
* '''[[Configure Graphics Cards|Configure Graphics Cards]]'''
: ''View, install, remove, or reinstall GPU drivers and much more.''
* '''[[Power Management|Power Management]]'''
: ''Got the power? No? Then optimise it!''
* '''[[Printing|Printing]]'''
: ''Enable printing and add printers.''
* '''[[Wacom Tablet And Pen|Wacom Tablet And Pen]]'''
: ''Configuring tablets and pens.''
* '''[[Manjaro-ARM|Manjaro-ARM]]'''
: ''Tips specific to ARM systems''
|1|1}}

{{FlexSideContainerTemplate|
===Network / Internet=== 
* '''[[Internet Browsers|Internet Browsers]]'''
: ''Security, Customization, and Configuration.''
* '''[[Firewalls and Security|Firewalls and Security]]'''
: ''Firewalls and Security on Manjaro''
* '''[[Sync dynamic IP with openDNS service via ddclient|Sync dynamic IP with openDNS service via ddclient]]'''
: ''Solution for update dynamic IP for openDNS service.''
* '''[[Keyboard and Mouse Sharing|Keyboard and Mouse Sharing]]'''
: ''Use a mouse and keyboard across multiple machines & operating systems.''
* '''[[Networking|Networking]]'''
: ''Managing networking''
* '''[[Using Samba in your File Manager|Using Samba in your File Manager]]'''
: ''How to setup Samba share in your network.''
* '''[[Sharing files with Python|Sharing files with Python]]'''
: ''Using Python's built-in network capabilities to share files.''
* '''[[Using autofs (automount) with NFS|Using autofs (automount) with NFS]]'''
: ''One of the many ways to mount shares.''
|
===System / Misc===
* '''[[Manjaro Polkit Rules|Manjaro Polkit Rules]]'''
: ''The policykity rules implemented by Manjaro''
* '''[[Add a Storage Partition & Modify your System to Suit|Add a Storage Partition & Modify your System to Suit]]'''
: ''How to shrink and add a partition & make Manjaro know where & what it is.''
* '''[[Aliases in .bashrc|Aliases in .bashrc]]'''
: ''Shortcuts for your terminal.''
* '''[[Developer Tools|Developer Tools]]'''
: ''Set of tools used by Manjaro developers and advanced users.''
* '''[[File Systems|File Systems]]'''
: ''Information on different file systems, how they work, and how to use them.''
* '''[[Swap|Managing Swap]]'''
: ''All about swap space''
* '''[[Limit the size of .log files & the journal|Management of the Systemd Journal & of .log files]]'''
: ''Manage Systemd's Journal & syslog-ng's /var/log/*log files.''
* '''[[Linux Security|Linux Security]]'''
: ''Information on root and superuser passwords.''
* '''[[How to mount Windows (NTFS) filesystem due to hibernation|How to mount Windows (NTFS) filesystem due to hibernation]]'''
: ''Solutions & workarounds for various Windows versions.''
* '''[[Keyboard_Shortcuts|Keyboard Shortcuts]]'''
: ''Set custom keyboard bindings.''
* '''[[Viewing and editing configuration files|Viewing and editing configuration files]]'''
: ''How to view and edit files in each Manjaro edition.''
|1|1}}

==Troubleshooting== 
{{FlexSideContainerTemplate|
===Boot / Startup===
* [[Restore the GRUB Bootloader|Restore the GRUB Bootloader]]
: ''Can't boot Manjaro? You may be able to repair rather than reinstall!''
* [[Preserve Manjaro Bootloader|Preserve Manjaro Bootloader]]
: ''Prevent Manjaro's GRUB from being overridden.''
* [[Kernel Fails to Load (pata_acpi error)|Kernel Fails to Load / "Unable to Find Device" Error]]
: ''Solution for a problem that affects certain computers using JMicron chips.''
|
===Desktop===
* [[Various screen tearing fixes|Various screen tearing fixes]]
: ''Hopefully one of these tips will fix your screen tearing problem.''
* [[DMenu - warning: no locale support|DMenu - warning: no locale support]]
: ''A fix for the "no locale support" error in dmenu.''
|1|1}}

{{FlexSideContainerTemplate|
===Software Management=== 
* [[pacman troubleshooting|Common Issues and Pacman Troubleshooting]]
: ''Troubleshooting common issues related to pacman''.
|
===Hardware===
* [[Reactivating the Backlight|Screen Brightness is too Dark or Dim]]
: ''The solution for an issue that particularly affects some makes of laptops''.
* [[Did X.server recognise your monitor correctly?|Did X.server recognise your monitor correctly?]]
: ''A quick test in the Terminal''.
* [[ALSA|Advanced Linux Sound Architecture (ALSA)]]
: ''Troubleshooting common issues related to ALSA''.
|1|1}}

==More== 


* [//www.mediawiki.org/wiki/Help:Contents User's Guide]
: ''Full user guide on every aspect of Wiki authorship and maintenance.''
* [[Basic Submission Rules|Basic Submission Rules]]
: ''How to create an account, and the dos and do-nots for Wiki contributors.''
* [[Contributing|Contributing]]
: ''The starting point for those willing to contribute to the wiki.''
* [https://wiki.manjaro.org/index.php?title=Category:Contents_Page{{#translation:}} Contents]
: ''For a page containing a list of all Wiki guides and tutorials sorted alphabetically''


{{FlexSideContainerTemplate|
{{FlexBoxTemplate|What's New - The Latest Changes|{{Special:RecentChanges/days=100,limit=12,hidebots}}|Actual there are '''{{NUMBEROFARTICLES}}''' articles here, waiting for you.}}|


__TOC__|
9|
1}}
</translate>

[[Category:Top level{{#translation:}}]]

Template:Key press/core

2021-11-05T16:17:57Z

Oguzkagan: edited style

<kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; border-radius: 0.2em; box-shadow: 0.1em 0.2em 0.2em #ddd;padding: 5px; font-family: inherit; font-size: 0.85em;">{{#switch:{{lc:{{{1}}}}}
| caps lock = ⇪ Caps Lock
| [[caps lock]] = ⇪ [[Caps Lock]]
| shift = ⇧ Shift
| [[shift key|shift]] = ⇧ [[Shift key|Shift]]
| enter = ↵ Enter
| [[enter key|enter]] = ↵ [[Enter key|Enter]]
| cmd = ⌘ Cmd
| [[cmd key|cmd]]
| [[command key|cmd]] = ⌘ [[Command key|Cmd]]
| command = ⌘ Command
| [[cmd key|command]]
| [[command key|command]] = |⌘ [[Command key|Command]]
| opt = ⌥ Opt
| [[opt key|opt]]
| [[option key|opt]] = ⌥ [[Option key|Opt]]
| option = ⌥ Option
| [[option key]]
| [[opt key|option]]
| [[option key|option]] = ⌥ [[Option key|Option]]
| tab = Tab ↹
| [[tab key|tab]] = [[Tab key|Tab]] ↹
| backspace = ← Backspace
| [[backspace]] = ← [[Backspace]]
| win = ⊞ Win
| [[win key|win]]
| [[windows key|win]] = ⊞ [[Windows key|Win]]
| menu = ≣ Menu
| [[menu key|menu]] = ≣ [[Menu key|Menu]]
| up = ↑
| [[arrow keys|up]] = [[Arrow keys|↑]]
| down = ↓
| [[arrow keys|down]] = [[Arrow keys|↓]]
| left = ←
| [[arrow keys|left]] = [[Arrow keys|←]]
| right = →
| [[arrow keys|right]] = [[Arrow keys|→]]
| *
| asterisk = <nowiki>*</nowiki>
| #
| hash = <nowiki>#</nowiki>
| [[#]] = [[Number sign|#]]
| :
| colon = <nowiki>:</nowiki>
| [[:]] = [[Colon (punctuation)|:]]
| pipe = <nowiki>|</nowiki>
| [[|]] = [[Pipe symbol|<nowiki>|</nowiki>]]
| ;
| semicolon = <nowiki>;</nowiki>
| [[;]] = [[Semi-colon|<nowiki>;</nowiki>]]
| equals = <nowiki>=</nowiki>


| l-up
| l up = L↑
| l-down
| l down = L↓
| l-left
| l left = L←
| l-right
| l right = L→
| l-ne
| l ne = L↗
| l-se
| l se = L↘
| l-nw
| l nw = L↖
| l-sw
| l sw = L↙

| r-up
| r up = R↑
| r-down
| r down = R↓
| r-left
| r left = R←
| r-right
| r right = R→
| r-ne
| r ne = R↗
| r-se
| r se = R↘
| r-nw
| r nw = R↖
| r-sw
| r sw = R↙


| ps x
| ex = ×
| ps c
| circle = ○
| ps s
| square = □
| ps t
| triangle = △


| c-up
| c up = C↑
| c-down
| c down = C↓
| c-left
| c left = C←
| c-right
| c right = C→
| c-ne
| c ne = C↗
| c-se
| c se = C↘
| c-nw
| c nw = C↖
| c-sw
| c sw = C↙


| #default = {{{1}}}
}}</kbd><noinclude>
Docs can be found at [https://www.mediawiki.org/wiki/Template:Key_press/doc mediawiki page.]
</noinclude>

Template:Key press/core

2021-11-05T16:16:07Z

Oguzkagan: edited style

<kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; border-radius: 0.2em; box-shadow: 0.1em 0.2em 0.2em #ddd; background-color: #f9f9f9; background-image: -moz-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -o-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -webkit-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: linear-gradient(to bottom, #eee, #f9f9f9, #eee); padding: 5px; font-family: inherit; font-size: 0.85em;">{{#switch:{{lc:{{{1}}}}}
| caps lock = ⇪ Caps Lock
| [[caps lock]] = ⇪ [[Caps Lock]]
| shift = ⇧ Shift
| [[shift key|shift]] = ⇧ [[Shift key|Shift]]
| enter = ↵ Enter
| [[enter key|enter]] = ↵ [[Enter key|Enter]]
| cmd = ⌘ Cmd
| [[cmd key|cmd]]
| [[command key|cmd]] = ⌘ [[Command key|Cmd]]
| command = ⌘ Command
| [[cmd key|command]]
| [[command key|command]] = |⌘ [[Command key|Command]]
| opt = ⌥ Opt
| [[opt key|opt]]
| [[option key|opt]] = ⌥ [[Option key|Opt]]
| option = ⌥ Option
| [[option key]]
| [[opt key|option]]
| [[option key|option]] = ⌥ [[Option key|Option]]
| tab = Tab ↹
| [[tab key|tab]] = [[Tab key|Tab]] ↹
| backspace = ← Backspace
| [[backspace]] = ← [[Backspace]]
| win = ⊞ Win
| [[win key|win]]
| [[windows key|win]] = ⊞ [[Windows key|Win]]
| menu = ≣ Menu
| [[menu key|menu]] = ≣ [[Menu key|Menu]]
| up = ↑
| [[arrow keys|up]] = [[Arrow keys|↑]]
| down = ↓
| [[arrow keys|down]] = [[Arrow keys|↓]]
| left = ←
| [[arrow keys|left]] = [[Arrow keys|←]]
| right = →
| [[arrow keys|right]] = [[Arrow keys|→]]
| *
| asterisk = <nowiki>*</nowiki>
| #
| hash = <nowiki>#</nowiki>
| [[#]] = [[Number sign|#]]
| :
| colon = <nowiki>:</nowiki>
| [[:]] = [[Colon (punctuation)|:]]
| pipe = <nowiki>|</nowiki>
| [[|]] = [[Pipe symbol|<nowiki>|</nowiki>]]
| ;
| semicolon = <nowiki>;</nowiki>
| [[;]] = [[Semi-colon|<nowiki>;</nowiki>]]
| equals = <nowiki>=</nowiki>


| l-up
| l up = L↑
| l-down
| l down = L↓
| l-left
| l left = L←
| l-right
| l right = L→
| l-ne
| l ne = L↗
| l-se
| l se = L↘
| l-nw
| l nw = L↖
| l-sw
| l sw = L↙

| r-up
| r up = R↑
| r-down
| r down = R↓
| r-left
| r left = R←
| r-right
| r right = R→
| r-ne
| r ne = R↗
| r-se
| r se = R↘
| r-nw
| r nw = R↖
| r-sw
| r sw = R↙


| ps x
| ex = ×
| ps c
| circle = ○
| ps s
| square = □
| ps t
| triangle = △


| c-up
| c up = C↑
| c-down
| c down = C↓
| c-left
| c left = C←
| c-right
| c right = C→
| c-ne
| c ne = C↗
| c-se
| c se = C↘
| c-nw
| c nw = C↖
| c-sw
| c sw = C↙


| #default = {{{1}}}
}}</kbd><noinclude>
Docs can be found at [https://www.mediawiki.org/wiki/Template:Key_press/doc mediawiki page.]
</noinclude>

Template:Key press/core

2021-11-05T16:14:46Z

Oguzkagan: edited style

<kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; border-radius: 0.2em; background-color: #f9f9f9;padding: 5px; font-family: inherit; font-size: 0.85em;">{{#switch:{{lc:{{{1}}}}}
| caps lock = ⇪ Caps Lock
| [[caps lock]] = ⇪ [[Caps Lock]]
| shift = ⇧ Shift
| [[shift key|shift]] = ⇧ [[Shift key|Shift]]
| enter = ↵ Enter
| [[enter key|enter]] = ↵ [[Enter key|Enter]]
| cmd = ⌘ Cmd
| [[cmd key|cmd]]
| [[command key|cmd]] = ⌘ [[Command key|Cmd]]
| command = ⌘ Command
| [[cmd key|command]]
| [[command key|command]] = |⌘ [[Command key|Command]]
| opt = ⌥ Opt
| [[opt key|opt]]
| [[option key|opt]] = ⌥ [[Option key|Opt]]
| option = ⌥ Option
| [[option key]]
| [[opt key|option]]
| [[option key|option]] = ⌥ [[Option key|Option]]
| tab = Tab ↹
| [[tab key|tab]] = [[Tab key|Tab]] ↹
| backspace = ← Backspace
| [[backspace]] = ← [[Backspace]]
| win = ⊞ Win
| [[win key|win]]
| [[windows key|win]] = ⊞ [[Windows key|Win]]
| menu = ≣ Menu
| [[menu key|menu]] = ≣ [[Menu key|Menu]]
| up = ↑
| [[arrow keys|up]] = [[Arrow keys|↑]]
| down = ↓
| [[arrow keys|down]] = [[Arrow keys|↓]]
| left = ←
| [[arrow keys|left]] = [[Arrow keys|←]]
| right = →
| [[arrow keys|right]] = [[Arrow keys|→]]
| *
| asterisk = <nowiki>*</nowiki>
| #
| hash = <nowiki>#</nowiki>
| [[#]] = [[Number sign|#]]
| :
| colon = <nowiki>:</nowiki>
| [[:]] = [[Colon (punctuation)|:]]
| pipe = <nowiki>|</nowiki>
| [[|]] = [[Pipe symbol|<nowiki>|</nowiki>]]
| ;
| semicolon = <nowiki>;</nowiki>
| [[;]] = [[Semi-colon|<nowiki>;</nowiki>]]
| equals = <nowiki>=</nowiki>


| l-up
| l up = L↑
| l-down
| l down = L↓
| l-left
| l left = L←
| l-right
| l right = L→
| l-ne
| l ne = L↗
| l-se
| l se = L↘
| l-nw
| l nw = L↖
| l-sw
| l sw = L↙

| r-up
| r up = R↑
| r-down
| r down = R↓
| r-left
| r left = R←
| r-right
| r right = R→
| r-ne
| r ne = R↗
| r-se
| r se = R↘
| r-nw
| r nw = R↖
| r-sw
| r sw = R↙


| ps x
| ex = ×
| ps c
| circle = ○
| ps s
| square = □
| ps t
| triangle = △


| c-up
| c up = C↑
| c-down
| c down = C↓
| c-left
| c left = C←
| c-right
| c right = C→
| c-ne
| c ne = C↗
| c-se
| c se = C↘
| c-nw
| c nw = C↖
| c-sw
| c sw = C↙


| #default = {{{1}}}
}}</kbd><noinclude>
Docs can be found at [https://www.mediawiki.org/wiki/Template:Key_press/doc mediawiki page.]
</noinclude>

Test page

2021-11-05T16:09:00Z

Oguzkagan: keypress test

<languages/>

example icon : <i data-feather="airplay"></i>

key press test {{key press|Ctrl|Alt|Del}}

Template:Key press

2021-11-05T16:08:17Z

Oguzkagan: updated docs

{{key press/core|{{{1|}}}}}{{#if:{{{2|}}}|{{{chain first|{{{chain|+}}}}}}{{key press/core|{{{2}}}}}}}{{#if:{{{3|}}}|{{{chain second|{{{chain|+}}}}}}{{key press/core|{{{3}}}}}}}{{#if:{{{4|}}}|{{{chain third|{{{chain|+}}}}}}{{key press/core|{{{4}}}}}}}{{#if:{{{5|}}}|{{{chain fourth|{{{chain|+}}}}}}{{key press/core|{{{5}}}}}}}{{#if:{{{6|}}}|{{{chain fifth|{{{chain|+}}}}}}{{key press/core|{{{6}}}}}}}{{#if:{{{7|}}}|{{{chain sixth|{{{chain|+}}}}}}{{key press/core|{{{7}}}}}}}{{#if:{{{8|}}}|{{{chain seventh|{{{chain|+}}}}}}{{key press/core|{{{8}}}}}}}{{#if:{{{9|}}}|{{{chain eighth|{{{chain|+}}}}}}{{key press/core|{{{9}}}}}}}{{#if:{{{10|}}}|{{{chain ninth|{{{chain|+}}}}}}{{key press/core|{{{10}}}}}}}{{#if:{{{11|}}}|[[Category:Wikipedia keypress template parameter needs fixing]]}}<noinclude>
Docs can be found at [https://www.mediawiki.org/wiki/Template:Key_press/doc mediawiki page.]

</noinclude>