Manjaro - User contributions [en]

Manjaro IRC

2023-05-26T17:41:28Z

Bogdancovaciu:

<languages/>
__TOC__
<translate>
= What is IRC? = 


'''#manjaro IRC''' is a place to provide additional direct support to Manjaro users.


You can connect to the '''#manjaro''' channel on '''irc.libera.chat'''.
* Frequent users will probably prefer an ''IRC client'' like ''Weechat'', ''Hexchat'', or ''Konversation''
* One-time users will probably prefer a web-based chat, such as https://web.libera.chat/#manjaro


It's not a replacement for the forum, but supplements it with direct community support. Sometimes it is quiet and sometimes busy, but we will try to help.


Also, sometimes the reason it is busy is that the conversation has gone off-topic!


For further issues that can't be solved on IRC there is always the Forum.
<br clear="all"/>

= How do I use Manjaro IRC? = 


Connect to #manjaro on irc.libera.chat using one of methods noted above.


When you are logged in, into the standard IRC client you have an name like Manjarouser.
The #manjaro channel now requires you to use a [[#How_to_Register_a_User_Name|registered user name]]. If you do not, you will be re-directed to #manjaro-unregistered.


You can change temporarily your nick with:


/nick [your nickname]


For example, to set your nick as "John", you would enter the following:


/nick John


The only rule of the IRC Channel is to be friendly. Just be your friendly self, and you'll find a lot of other friendly people to socialize with and receive support from.

= Asking questions on IRC = 


#Ask the question. You don't need to ask for permission to ask, or to find out if anyone is willing to answer the question.
#Make sure you have time to wait for an answer (10 minutes is a bare minimum). If you don't get an answer, it's likely people don't know, are in the middle of writing one or didn't notice your question.
#Try to be concise with your question.
#Even if you see a lot of people listed on the channel, this doesn't mean that they are actually present.
#When sending reports (especially multi-line reports) please use an Pastebin service like pastebin.com<br clear="all"/>

== How to Register a User Name == 


0. '''Choose a user name or nick'''.


The user name should consist only of the letters from A-Z, the numbers from 0-9 and certain symbols such as "_" and "-". It may have a maximum of 16 characters. To do so, enter the following command into the text field, where you would normally enter comments:
/nick [your nickname]


1. '''Register your nick / user name'''.


Type the following command and replace "your_password" with a password that will be easy to remember, and replace "your_email_address" with your email address.
/msg nickserv register your_password your_email_address


2. '''Check your e-mail and verify your account'''.


: After you register, you will not be able to identify to NickServ until you have verified your registration. To do this, check your email for an account verification code.


3. '''Type the command that Libera.Chat asks you to type'''.


: Press the Enter key to fully confirm.

== Secure your nick name == 


Its possible someone using your nick.


please set :


'''/msg NickServ SET ENFORCE ON'''


Then no one can abuse your nick directly
Make sure your client got configure right


you can always do manually with :


'''/msg NickServ IDENTIFY account password'''


For further info see [https://libera.chat/guides/registration Libera.Chat user registration]

== Trolling == 


IRC is a well-known chat protocol frequently used by trolls, if you encounter a troll please notify a moderator.
In case the troll is sending you private messages, you can set +Rg on your nick, so only registered users can chat with you privately.
If you wish to set this mode, it can be done with:


''' /mode (yournick) +Rg '''


stops messages from troll that is unregistered. so, no users that is unregistered can harm you.


If the troll is registered, you can ignore the troll with the command:


do also : ''/ns info (troll-nick)'' to get information over the registered name.


''' /ignore (troll-nick-registered name) '''

= Configuring an IRC client = 


With pidgin hexchat and konversation you can a good go to irc.


Please see the following on how to configure for your client for Sasl: [https://libera.chat/guides/sasl]

= Manjaro IRC is multilingual = 


It is always a good idea to look for IRC channels in your region too.


* #manjaro = Main IRC Channel
* #manjaro-br = Brasil IRC Channel
* #manjaro-de = German IRC Channel
* #manjaro-es = Spanish IRC Channel
* #manjaro-fi = Finnish IRC Channel
* #manjaro-fr = French IRC Channel
* #manjaro-it = Italian IRC Channel
* #manjaro-jp = Japanese IRC Channel
* #manjaro-nl = Dutch / Belgian IRC channel
* #manjaro-ru = Russian IRC Channel
* #linuxpark = Turkish IRC Channel
* #manjaro-talk = Manjaro off-topic channel, is optional in use.
* #manjaro-openrc = OpenRC support Manjaro
* ##manjaro-ops = channel admin is there and leave a message about issues on channel


Please support those channels !
<br clear="all"/>

= Logging = 


If there is some issues and you could catch a operator.
There is some logging you can find some logs back !


check this :


* Link removed.

=See also= 


[[Manjaro-irc-support-guidelines|IRC Support Guidelines]]
</translate>

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

Install Desktop Environments

2022-07-15T09:53:52Z

Bogdancovaciu: Fixed also KDE Plasma theme install command.

<languages/>
__TOC__

<translate>
= Overview = 


There are several Desktop Environments and Window Managers available for Manjaro, each with their own unique style, interface, and features. Furthermore, it is possible to install multiple environments if desired, which can be selected at the login screen at any time. Users are not restricted to whatever comes pre-installed with a particular flavour of Manjaro.

= Desktop Environments = 


It is worth noting that a Desktop Environment(DE) is not a single entity; it is actually a collection of different components that work together. This commonly includes a:


* '''window manager''' to display, move and resize application windows
* '''file manager''' to visually browse, copy and access files, etc.
* '''background provider''' to display wallpapers, etc.
* '''panel''' to provide a menu and to display information such as the time
* '''settings/configuration manager''' to change the look of the environment


And so on. Most desktop environments will also come with their own preferred applications, in addition to various widgets, addons, and extensions to provide extra features. As such, upon entering the commands provided below in your terminal to download and install a desktop environment, you may be prompted to choose from a selection of components provided for it. '''To install a full desktop environment''' - complete with its own preferred file manager, applications, and so on


Where additional (and optional) extras for a desktop environment are available, the terminal commands to obtain these have also been provided.


Some important information about installing the Manjaro settings packages:
* The Manjaro settings packages contain the theming and settings to make the desktop the same as in the Manjaro ISOs
* They have the naming convention manjaro-<desktop>-settings i.e. manjaro-xfce-settings
* They share files so you can only have one at a time installed.
* If you are coming from gnome you must remove the meta package '''manjaro-gnome-assets''' before you can install the settings package for another desktop

==The Risks of Using Multiple DEs== 


Installing multiple DEs is not without risks. Here are some things that can pop-up when running more than one DE:
* The settings packages overlap so you can only have one DE pre-configured with the Manjaro theming. The others will need to have the theming applied manually.
* You can end up with more than one instance of similar applications. For example, it is common to end up with 2 Bluetooth managers. It takes some tweaking to get a single manager working in multiple DEs
* Sometimes two different DEs will share the same configuration files causing strange things to happen, especially with theming


These risks are greatly reduced by using a different user account for each DE.


In summary, running multiple DEs is possible and a great way to enjoy Manjaro but it requires a willingness to troubleshoot and work through minor problems. If you are the type of person who wants everything to "just work" out of the box, running multiple DEs might not be for you.

== XFCE == 


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


'''[http://xfce.org/ XFCE]''' is a lightweight and versatile desktop environment that utilises a classic drop-down or pop-up menu to access applications. It is also compatible with '''[[Compiz_and_Emerald|Compiz]]'''. A little time and effort will also be required to properly customise the desktop to suit personal taste. A 64 bit installation of Manjaro running XFCE uses about 390MB of memory. As of version 18, Manjaro has moved to the gtk3 version of XFCE.

====== Install a basic XFCE environment ====== 


sudo pacman -S xfce4-gtk3 xfce4-goodies xfce4-terminal network-manager-applet xfce4-notifyd-gtk3 xfce4-whiskermenu-plugin-gtk3 tumbler engrampa

====== Optional: Install and use LightDM, the recommended display manager for XFCE ====== 
sudo pacman -S lightdm lightdm-gtk-greeter lightdm-gtk-greeter-settings
sudo systemctl enable lightdm.service --force
edit '''/etc/lightdm/lightdm.conf''', under [Seat:*] replace the greeter-session setting with '''greeter-session=lightdm-gtk-greeter'''

====== Optional: Install the Manjaro configuration and theming for XFCE ====== 
sudo pacman -S manjaro-xfce-settings manjaro-settings-manager


To configure LightDM to match the official iso replace the contents of /etc/lightdm/lightdm-gtk-greeter.conf with
[greeter]
background = /usr/share/backgrounds/illyria-default-lockscreen.jpg
font-name = Cantarell Bold 12
xft-antialias = true
icon-theme-name = Papirus
screensaver-timeout = 60
theme-name = Matcha-azul
cursor-theme-name = xcursor-breeze
show-clock = false
default-user-image = #avatar-default
xft-hintstyle = hintfull
position = 50%,center 50%,center
clock-format =
panel-position = bottom
indicators = ~host;~spacer;~clock;~spacer;~language;~session;~a11y;~power

====== Create a new user for the new desktop environment ====== 
sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

== KDE Plasma 5 == 
[[File: KDEPlasmaDE.png|thumb|left|375px]]


'''[http://www.kde.org/ The KDE community]''' offers [https://www.kde.org/plasma-desktop Plasma], a feature-rich and versatile desktop environment that provides several different styles of menu to access applications. Its default window manager is kwin, but is also compatible with '''[[Compiz_and_Emerald|Compiz]]'''. An excellent built-in interface to easily access and install new themes, widgets, etc, from the internet is also worth mentioning. A 64 bit installation of Manjaro running KDE uses about 455MB of memory.

====== Install a basic KDE Plasma environment ====== 


sudo pacman -S plasma kio-extras

====== Optional: Install KDE applications ====== 


To install a full set of K* applications use '''kde-applications'''. This will be ~300 packages(including dependencies)

sudo pacman -S kde-applications

====== Optional: Install and use [https://wiki.manjaro.org/index.php?title=Install_Display_Managers#SDDM SDDM], the recommended display manager for KDE ====== 


SDDM is installed as a dependency of plasma. To enable it

systemctl enable sddm.service --force
systemctl reboot

====== Optional: Install the Manjaro configuration and theming for plasma ====== 

sudo pacman -S manjaro-kde-settings sddm-breath-theme manjaro-settings-manager-knotifier manjaro-settings-manager-kcm


Open plasma settings, go to Startup & Shutdown->Login Screen and select "Breath"


Alternatively, the newer themes may be installed with:


sudo pacman -S plasma5-themes-breath

====== Create a new user for the new desktop environment ====== 

sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

== Gnome 3 == 
[[File: Gnome-de-18.jpg|thumb|left|375px]]


'''[http://www.gnome.org/ Gnome 3]''' is an intuitive desktop environment that utilises a tablet or smartphone style interface to access applications. It is not compatible with compiz. Although Gnome is very easy to learn and use, its customisation options are quite limited, and it can be difficult to configure. A 64 bit installation of Manjaro running Gnome uses about 447MB of memory.

====== Install a basic gnome environment ====== 


sudo pacman -S gnome

====== Optional: To install extra themes, games, and features ====== 


sudo pacman -S gnome-extra

====== Optional: Install and use GDM, the recommended display manager for gnome ====== 


GDM is installed as a dependency of gnome, to enable it

systemctl enable gdm.service --force

====== Optional: Install the Manjaro configuration and theming for gnome ====== 

sudo pacman -S manjaro-gnome-settings manjaro-settings-manager

====== Create a new user for the new desktop environment ====== 
sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

== Budgie == 
[[File: budgie.jpg|thumb|left|375px]]


The '''[https://github.com/solus-project/budgie-desktop Budgie Desktop]''' is a modern desktop designed to keep out the way of the user. It features heavy integration with the GNOME stack in order for an enhanced experience. A 64 bit installation of Manjaro running budgie uses about 632MB of memory.

====== Install a basic budgie environment ====== 


sudo pacman -S budgie-desktop network-manager-applet gnome-control-center gnome-screensaver

====== Optional: Install additional commonly used components ====== 
sudo pacman -S gnome-terminal nautilus budgie-extras dconf-editor

====== Optional: Install and use LightDM, the recommended display manager for budgie ====== 

sudo pacman -S lightdm lightdm-slick-greeter lightdm-settings
systemctl enable lightdm.service --force
edit ''/etc/lightdm/lightdm.conf'', under '''[Seat:*]''' replace the greeter-session setting with '''greeter-session=lightdm-slick-greeter'''

====== Optional: Install the Manjaro configuration and theming for budgie ====== 

sudo pacman -S manjaro-budgie-settings manjaro-settings-manager papirus-maia-icon-theme


To configure LightDM to match the official iso replace the contents of /etc/lightdm/slick-greeter.conf with
[Greeter]
background=/usr/share/backgrounds/manjaro-budgie/manjaro-budgie.jpg
theme-name=Matcha-sea
icon-theme-name=Papirus-Maia
draw-grid=false

====== Create a new user for the new desktop environment ====== 

sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

== Cinnamon == 
[[File: Cinnamon screenshot.jpeg|thumb|left|375px]]


'''[http://cinnamon.linuxmint.com/ Cinnamon]''' is a desktop environment based on Gnome 3 that utilises a large panel-style menu to access applications. It is not compatible with compiz. Despite being based on Gnome, it has more customisation options and is easier to configure. Users of Windows Vista or Windows 7 may find Cinnamon's interface comfortably familiar. A 64 bit installation of Manjaro running Cinnamon uses about 665MB of memory.

====== Install a basic cinnamon environment ====== 


sudo pacman -S cinnamon

====== Optional: Install additional commonly used components ====== 

sudo pacman -S cinnamon-wallpapers cinnamon-sounds gnome-terminal parcellite

====== Optional: Install and use LightDM, the recommended display manager for cinnamon ====== 

sudo pacman -S lightdm lightdm-slick-greeter lightdm-settings
systemctl enable lightdm.service --force


Then edit ''/etc/lightdm/lightdm.conf'', under '''[Seat:*]''' replace the greeter-session setting with '''greeter-session=lightdm-slick-greeter'''

====== Optional: Install the Manjaro configuration and theming for cinnamon ====== 

sudo pacman -S manjaro-cinnamon-settings adapta-maia-theme kvantum-manjaro


To configure LightDM to match the community edition replace the contents of /etc/lightdm/slick-greeter.conf with
[Greeter]
background=/usr/share/backgrounds/greeter_default.jpg
background-color=#263138
draw-grid=false
theme-name=Adapta-Nokto-Eta-Maia
icon-theme-name=Papirus-Dark-Maia
font-name='Cantarell 11'
xft-antialias=true
xft-hintstyle=hintfull
enable-hidpi=auto


Set the Manjaro logo on the panel by right-clicking on the menu and clicking configure. Select "Use a custom icon and label". Select the Manjaro icon.

====== Create a new user for the new desktop environment ====== 
sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

== Deepin == 
[[File: deepin.jpg|thumb|left|375px]]
The '''[https://www.deepin.org/en/dde/ Deepin Desktop]''' is an elegant, easy to use desktop. It is lightly configurable. A 64 bit installation of Manjaro running deepin uses about 525MB of memory.

====== Install a basic deepin environment ====== 


sudo pacman -S deepin

====== Optional: Install the deepin applications suite ====== 

sudo pacman -S deepin-extra

====== Optional: Install and use LightDM, the recommended display manager for deepin====== 

sudo pacman -S lightdm
systemctl enable lightdm.service --force


Then edit ''/etc/lightdm/lightdm.conf'', under '''[Seat:*]''' replace the greeter-session setting with '''greeter-session=lightdm-deepin-greeter'''

====== Optional: Install the Manjaro configuration and theming for deepin ====== 

sudo pacman -S deepin-manjaro

====== Create a new user for the new desktop environment ====== 

sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

== Enlightenment == 
{{note|There is not currently a Manjaro settings package for Enlightenment|}}
[[File: E20-Green_Onix_760.png|thumb|left|375px]]


'''[http://www.enlightenment.org/ Enlightenment]''', sometimes known simply as E, is a lightweight desktop environment known for its configurability and tools for creating beautiful user interfaces using its Enlightenment Foundation Libraries (EFL). E started in 1997 as a stacking windows manager, emerging as a desktop environment with development release 0.17. E does not come with a broad array of tools by default, which can be an advantage for experienced users who want to customize their installation, and a disadvantage for users with little or no experience of Linux. E uses a few unique terms, for example referring to panels as “shelves”. A 64-bit installation of E uses about 160M of memory.

====== Install a basic E environment ====== 

sudo pacman -S enlightenment

====== Optional: Install and use Entrance, the recommended display manager for E ====== 
Entrance is available from the AUR in the package '''entrance-git'''. Information on how to install packages from AUR can be found '''[https://wiki.manjaro.org/index.php/Arch_User_Repository here]'''.

$ sudo pacman -S --asdeps meson
$ pamac build entrance-git
$ sudo systemctl enable entrance.service --force

====== Optional: Install Manjaro themes for E ====== 
sudo pacman -S enlightenment-manjaro-themes

====== Create a new user for the new desktop environment ====== 
sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

== LXDE == 


{{Note|Installing LXDE will also result in installing ''Openbox'' as its default window manager. The LXDM display manager will also be downloaded, although it will be necessary to enable this yourself if you wish to replace your existing display manager.}}
[[File: lxde17.1.11.jpg|thumb|left|375px]]


'''[http://lxde.org/ LXDE]''' is a super-lightweight desktop environment that is very similar to XFCE, with the exception that it is not compatible with Compiz. As with XFCE, LXDE is also a somewhat basic desktop environment, lacking some modern features that would be expected, such as a search-bar to find applications and files. However, it is also an excellent choice for less powerful computers.

====== Install a basic lxde environment ====== 


sudo pacman -S lxde network-manager-applet

====== Optional: Install and use LightDM, the recommended display manager for lxde ====== 

sudo pacman -S lightdm lightdm-gtk-greeter lightdm-gtk-greeter-settings
systemctl enable lightdm.service --force

====== Optional: Install the Manjaro configuration and theming for lxde ====== 

sudo pacman -S manjaro-lxde-logout-banner manjaro-lxde-xfce4-notifyd manjaro-lxde-xfce4-volumed-pulse manjaro-settings-manager manjaro-settings-manager-notifier manjaro-lxde-settings arc-maia-icon-theme kvantum-manjaro


To configure LightDM to match the community edition replace the contents of /etc/lightdm/lightdm-gtk-greeter.conf with
[greeter]
background = /usr/share/backgrounds/lxde-breath.png
font-name = Cantarell 12
xft-antialias = true
icon-theme-name = Arc-Maia
screensaver-timeout = 60
theme-name = Adapta-Eta-Maia
cursor-theme-name = xcursor-breeze
show-clock = false
default-user-image = #avatar-default
xft-hintstyle = hintfull
position = 50%,center 50%,center
clock-format =
panel-position = bottom

====== Create a new user for the new desktop environment ====== 

sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

== LXQt == 


[[File: Lxqt-de-18.png|thumb|left|375px]]


The '''[https://lxqt.org/ LXQt Desktop Environment]''' LXQt is a lightweight Qt desktop environment. It will not get in your way. It will not hang or slow down your system. It is focused on being a classic desktop with a modern look and feel. A 64 bit installation of Manjaro running lxqt uses about 250MB of memory.

====== Install a basic LXQt environment ====== 
sudo pacman -S lxqt xscreensaver

====== Install and use LightDM, the recommended display manager for LXQt ====== 
sudo pacman -S lightdm lightdm-slick-greeter lightdm-settings light-locker
systemctl enable lightdm.service --force
edit /etc/lightdm/lightdm.conf, under [Seat:*] replace the greeter-session setting with greeter-session=lightdm-slick-greeter

====== Optional: Install the Manjaro configuration and theming for LXQt ====== 
sudo pacman -S manjaro-lxqt-extra-settings manjaro-openbox-adapta-maia papirus-maia-icon-theme

====== Create a new user for the new desktop environment ====== 
sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

== MATE == 


[[File: mate.jpg|thumb|left|375px]]


The '''[https://mate-desktop.org/ MATE Desktop]''' Environment is the continuation of GNOME 2. It provides an intuitive and attractive desktop environment using traditional metaphors for Linux and other Unix-like operating systems. MATE is under active development to add support for new technologies while preserving a traditional desktop experience. A 64 bit installation of Manjaro running MATE uses about 378MB of memory.

====== Install a basic mate environment ====== 


sudo pacman -S mate network-manager-applet

====== Optional: Install mate applications and configuration tools ====== 
sudo pacman -S mate-extra dconf-editor

====== Optional: Install and use LightDM, the recommended display manager for mate ====== 
sudo pacman -S lightdm lightdm-slick-greeter lightdm-settings
systemctl enable lightdm.service --force
edit '''/etc/lightdm/lightdm.conf''', under [Seat:*] replace the greeter-session setting with '''greeter-session=lightdm-slick-greeter'''

====== Optional: Install the Manjaro configuration and theming for mate ====== 
sudo pacman -S manjaro-mate-settings arc-maia-icon-theme papirus-maia-icon-theme manjaro-settings-manager manjaro-settings-manager-notifier


To configure LightDM to match the community edition replace the contents of /etc/lightdm/slick-greeter.conf with
[Greeter]
background=/usr/share/backgrounds/manjaro-mate/manjaro-mate.jpg
theme-name=Adapta-Nokto-Maia
icon-theme-name=Arc-Maia
draw-grid=false

====== Create a new user for the new desktop environment ====== 
sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

= Window Managers = 


{{note|By nature, building your own desktop environment from a Window Manager will take substantially more time and effort than simply downloading a pre-defined desktop environment.}}


{{warning|The images provided below are purely for illustrative purposes only. You will have you put in the necessary time and effort to configure them.}}


Although Desktop Environments commonly provide a good range of customisation options to suit personal taste and preference, they may still be seen as somewhat restrictive or controlled in the sense that they merely allow for the personalisation of their pre-defined components. However, certain Window Managers empower users to take a 'do it yourself' approach in order to create their own desktop environments. In essence, they may be used as a foundation on which to build upon, as literally every component and every aspect of the desktop is under the direct control and choice of the user. An environment may be as elaborate or as minimalistic as desired, and it is even possible to mix and match various components from other desktop environments.


Therefore extremely powerful and versatile, these window managers also carry the additional benefit of being faster and more resource efficient than pre-defined desktop environments. Interestingly, the super-lightweight LXDE environment is itself built on the Openbox window manager. There are two types of Window Manager: '''Stacking''' and '''Tiling'''. These names denote how application windows will behave on your desktop.

== Stacking Window Managers == 


'''Stacking window managers''' are by far the most popular, and essentially allow application windows to be moved freely around the screen, which may overlap - or 'stack' - upon one another, hence the name. All popular desktop environments (e.g. XFCE, KDE, Gnome, etc.) use stacking window Managers.

=== Openbox === 


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


'''[http://openbox.org/ Openbox]''' is by far the most popular Window Manager available. Due to its popularity there is excellent documentation available, as well as a good choice of additional themes that may be downloaded. '''To install Openbox, enter the command:'''


sudo pacman -S openbox


To install a logout script, configuration application, menu-editor, and extra themes for Openbox, enter the following command:


sudo pacman -S oblogout obconf lxappearance-obconf-gtk3 obmenu openbox-themes-extra

====== Optional: Install the Manjaro configuration, theming, and tools for Openbox ====== 


sudo pacman -S oblogout-manjaro manjaro-openbox-config manjaro-openbox-scripts manjaro-openbox-fonts matcha-gtk-theme
<br clear="all" />

=== FluxBox === 


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


'''[http://fluxbox.org/ FluxBox]''' is another popular Window Manager. It is particularly notable for providing some features not seen in Openbox, such as ''tabbing'', which allows for windows to be grouped together. '''To install FluxBox, enter the command''':


sudo pacman -S fluxbox

====== Optional: Install the newsfetcher and workspace pager for Fluxbox ====== 


sudo pacman -S fbnews fluxter

====== Optional: Install the Manjaro configuration, theming, and tools for Fluxbox ====== 


sudo pacman -S fbmenu-manjaro oblogout-manjaro artwork-fluxbox fluxboxtheme-manjaro
<br clear="all" />

=== IceWM === 


[[File: icewm2.jpg|thumb|left|375px]]


'''[https://www.ice-wm.org/ IceWM]''' is a Window Manager notable for perhaps being closer to a full desktop environment than Openbox or FluxBox. This includes providing a panel complete with menu, in addition to a workspace switcher. '''To install IceWM, enter the command''':


sudo pacman -S icewm


To install a suite of tools and themes specifically for IceWM, enter the command:


sudo pacman -S icewm-utils icewm-themes
<br clear="all" />

== Tiling Window Managers == 


'''Tiling window managers''' - as the name would suggest - tile application windows; each will have their own place on the screen, just like conventional tiles do not overlap. However, unlike conventional tiling, these window managers are usually very flexible, and allow for a multitude of different tiling patterns to suit personal taste and preference. Where stacking window managers focus on using the mouse for navigation, tiling window managers focus on the utilisation of the keyboard instead. As such, they can be much faster to use.

=== Awesome === 


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


'''[http://awesome.naquadah.org/ Awesome]''' is a popular tiling Window Manager, notable for using the '''Lua''' language for configuration. '''To install Awesome, enter the command''':


sudo pacman -S awesome


To install some extra widgets for Awesome, enter the command:


sudo pacman -S vicious


Alternatively you can install the [[Awesome Community Edition]].
<br clear="all" />

=== i3 === 


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


'''[http://i3wm.org/ i3]''' is arguably the most popular tiling window manager available, and notable for using a single, completely self-contained configuration file. '''To install i3, enter the command''':


sudo pacman -S i3-wm


To install a status bar and screen-locker for i3, enter the command:


sudo pacman -S i3lock i3status
<br clear="all" />

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:Editions{{#translation:}}]]

Install Desktop Environments

2022-07-15T05:03:04Z

Bogdancovaciu: Minor changes removing from commands the packages that do not exist anymore

<languages/>
__TOC__

<translate>
= Overview = 


There are several Desktop Environments and Window Managers available for Manjaro, each with their own unique style, interface, and features. Furthermore, it is possible to install multiple environments if desired, which can be selected at the login screen at any time. Users are not restricted to whatever comes pre-installed with a particular flavour of Manjaro.

= Desktop Environments = 


It is worth noting that a Desktop Environment(DE) is not a single entity; it is actually a collection of different components that work together. This commonly includes a:


* '''window manager''' to display, move and resize application windows
* '''file manager''' to visually browse, copy and access files, etc.
* '''background provider''' to display wallpapers, etc.
* '''panel''' to provide a menu and to display information such as the time
* '''settings/configuration manager''' to change the look of the environment


And so on. Most desktop environments will also come with their own preferred applications, in addition to various widgets, addons, and extensions to provide extra features. As such, upon entering the commands provided below in your terminal to download and install a desktop environment, you may be prompted to choose from a selection of components provided for it. '''To install a full desktop environment''' - complete with its own preferred file manager, applications, and so on


Where additional (and optional) extras for a desktop environment are available, the terminal commands to obtain these have also been provided.


Some important information about installing the Manjaro settings packages:
* The Manjaro settings packages contain the theming and settings to make the desktop the same as in the Manjaro ISOs
* They have the naming convention manjaro-<desktop>-settings i.e. manjaro-xfce-settings
* They share files so you can only have one at a time installed.
* If you are coming from gnome you must remove the meta package '''manjaro-gnome-assets''' before you can install the settings package for another desktop

==The Risks of Using Multiple DEs== 


Installing multiple DEs is not without risks. Here are some things that can pop-up when running more than one DE:
* The settings packages overlap so you can only have one DE pre-configured with the Manjaro theming. The others will need to have the theming applied manually.
* You can end up with more than one instance of similar applications. For example, it is common to end up with 2 Bluetooth managers. It takes some tweaking to get a single manager working in multiple DEs
* Sometimes two different DEs will share the same configuration files causing strange things to happen, especially with theming


These risks are greatly reduced by using a different user account for each DE.


In summary, running multiple DEs is possible and a great way to enjoy Manjaro but it requires a willingness to troubleshoot and work through minor problems. If you are the type of person who wants everything to "just work" out of the box, running multiple DEs might not be for you.

== XFCE == 


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


'''[http://xfce.org/ XFCE]''' is a lightweight and versatile desktop environment that utilises a classic drop-down or pop-up menu to access applications. It is also compatible with '''[[Compiz_and_Emerald|Compiz]]'''. A little time and effort will also be required to properly customise the desktop to suit personal taste. A 64 bit installation of Manjaro running XFCE uses about 390MB of memory. As of version 18, Manjaro has moved to the gtk3 version of XFCE.

====== Install a basic XFCE environment ====== 


sudo pacman -S xfce4-gtk3 xfce4-goodies xfce4-terminal network-manager-applet xfce4-notifyd-gtk3 xfce4-whiskermenu-plugin-gtk3 tumbler engrampa

====== Optional: Install and use LightDM, the recommended display manager for XFCE ====== 
sudo pacman -S lightdm lightdm-gtk-greeter lightdm-gtk-greeter-settings
sudo systemctl enable lightdm.service --force
edit '''/etc/lightdm/lightdm.conf''', under [Seat:*] replace the greeter-session setting with '''greeter-session=lightdm-gtk-greeter'''

====== Optional: Install the Manjaro configuration and theming for XFCE ====== 
sudo pacman -S manjaro-xfce-settings manjaro-settings-manager


To configure LightDM to match the official iso replace the contents of /etc/lightdm/lightdm-gtk-greeter.conf with
[greeter]
background = /usr/share/backgrounds/illyria-default-lockscreen.jpg
font-name = Cantarell Bold 12
xft-antialias = true
icon-theme-name = Papirus
screensaver-timeout = 60
theme-name = Matcha-azul
cursor-theme-name = xcursor-breeze
show-clock = false
default-user-image = #avatar-default
xft-hintstyle = hintfull
position = 50%,center 50%,center
clock-format =
panel-position = bottom
indicators = ~host;~spacer;~clock;~spacer;~language;~session;~a11y;~power

====== Create a new user for the new desktop environment ====== 
sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

== KDE Plasma 5 == 
[[File: KDEPlasmaDE.png|thumb|left|375px]]


'''[http://www.kde.org/ The KDE community]''' offers [https://www.kde.org/plasma-desktop Plasma], a feature-rich and versatile desktop environment that provides several different styles of menu to access applications. Its default window manager is kwin, but is also compatible with '''[[Compiz_and_Emerald|Compiz]]'''. An excellent built-in interface to easily access and install new themes, widgets, etc, from the internet is also worth mentioning. A 64 bit installation of Manjaro running KDE uses about 455MB of memory.

====== Install a basic KDE Plasma environment ====== 


sudo pacman -S plasma kio-extras

====== Optional: Install KDE applications ====== 


To install a full set of K* applications use '''kde-applications'''. This will be ~300 packages(including dependencies)

sudo pacman -S kde-applications

====== Optional: Install and use [https://wiki.manjaro.org/index.php?title=Install_Display_Managers#SDDM SDDM], the recommended display manager for KDE ====== 


SDDM is installed as a dependency of plasma. To enable it

systemctl enable sddm.service --force
systemctl reboot

====== Optional: Install the Manjaro configuration and theming for plasma ====== 

sudo pacman -S manjaro-kde-settings sddm-breath-theme manjaro-settings-manager-knotifier manjaro-settings-manager-kcm


Open plasma settings, go to Startup & Shutdown->Login Screen and select "Breath"


Alternatively, the newer themes may be installed with:


sudo pacman -S breath2-icon-themes breath2-wallpaper plasma5-themes-breath2 sddm-breath2-theme

====== Create a new user for the new desktop environment ====== 

sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

== Gnome 3 == 
[[File: Gnome-de-18.jpg|thumb|left|375px]]


'''[http://www.gnome.org/ Gnome 3]''' is an intuitive desktop environment that utilises a tablet or smartphone style interface to access applications. It is not compatible with compiz. Although Gnome is very easy to learn and use, its customisation options are quite limited, and it can be difficult to configure. A 64 bit installation of Manjaro running Gnome uses about 447MB of memory.

====== Install a basic gnome environment ====== 


sudo pacman -S gnome

====== Optional: To install extra themes, games, and features ====== 


sudo pacman -S gnome-extra

====== Optional: Install and use GDM, the recommended display manager for gnome ====== 


GDM is installed as a dependency of gnome, to enable it

systemctl enable gdm.service --force

====== Optional: Install the Manjaro configuration and theming for gnome ====== 

sudo pacman -S manjaro-gnome-settings manjaro-settings-manager

====== Create a new user for the new desktop environment ====== 
sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

== Budgie == 
[[File: budgie.jpg|thumb|left|375px]]


The '''[https://github.com/solus-project/budgie-desktop Budgie Desktop]''' is a modern desktop designed to keep out the way of the user. It features heavy integration with the GNOME stack in order for an enhanced experience. A 64 bit installation of Manjaro running budgie uses about 632MB of memory.

====== Install a basic budgie environment ====== 


sudo pacman -S budgie-desktop network-manager-applet gnome-control-center gnome-screensaver

====== Optional: Install additional commonly used components ====== 
sudo pacman -S gnome-terminal nautilus budgie-extras dconf-editor

====== Optional: Install and use LightDM, the recommended display manager for budgie ====== 

sudo pacman -S lightdm lightdm-slick-greeter lightdm-settings
systemctl enable lightdm.service --force
edit ''/etc/lightdm/lightdm.conf'', under '''[Seat:*]''' replace the greeter-session setting with '''greeter-session=lightdm-slick-greeter'''

====== Optional: Install the Manjaro configuration and theming for budgie ====== 

sudo pacman -S manjaro-budgie-settings manjaro-settings-manager papirus-maia-icon-theme


To configure LightDM to match the official iso replace the contents of /etc/lightdm/slick-greeter.conf with
[Greeter]
background=/usr/share/backgrounds/manjaro-budgie/manjaro-budgie.jpg
theme-name=Matcha-sea
icon-theme-name=Papirus-Maia
draw-grid=false

====== Create a new user for the new desktop environment ====== 

sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

== Cinnamon == 
[[File: Cinnamon screenshot.jpeg|thumb|left|375px]]


'''[http://cinnamon.linuxmint.com/ Cinnamon]''' is a desktop environment based on Gnome 3 that utilises a large panel-style menu to access applications. It is not compatible with compiz. Despite being based on Gnome, it has more customisation options and is easier to configure. Users of Windows Vista or Windows 7 may find Cinnamon's interface comfortably familiar. A 64 bit installation of Manjaro running Cinnamon uses about 665MB of memory.

====== Install a basic cinnamon environment ====== 


sudo pacman -S cinnamon

====== Optional: Install additional commonly used components ====== 

sudo pacman -S cinnamon-wallpapers cinnamon-sounds gnome-terminal parcellite

====== Optional: Install and use LightDM, the recommended display manager for cinnamon ====== 

sudo pacman -S lightdm lightdm-slick-greeter lightdm-settings
systemctl enable lightdm.service --force


Then edit ''/etc/lightdm/lightdm.conf'', under '''[Seat:*]''' replace the greeter-session setting with '''greeter-session=lightdm-slick-greeter'''

====== Optional: Install the Manjaro configuration and theming for cinnamon ====== 

sudo pacman -S manjaro-cinnamon-settings adapta-maia-theme kvantum-manjaro


To configure LightDM to match the community edition replace the contents of /etc/lightdm/slick-greeter.conf with
[Greeter]
background=/usr/share/backgrounds/greeter_default.jpg
background-color=#263138
draw-grid=false
theme-name=Adapta-Nokto-Eta-Maia
icon-theme-name=Papirus-Dark-Maia
font-name='Cantarell 11'
xft-antialias=true
xft-hintstyle=hintfull
enable-hidpi=auto


Set the Manjaro logo on the panel by right-clicking on the menu and clicking configure. Select "Use a custom icon and label". Select the Manjaro icon.

====== Create a new user for the new desktop environment ====== 
sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

== Deepin == 
[[File: deepin.jpg|thumb|left|375px]]
The '''[https://www.deepin.org/en/dde/ Deepin Desktop]''' is an elegant, easy to use desktop. It is lightly configurable. A 64 bit installation of Manjaro running deepin uses about 525MB of memory.

====== Install a basic deepin environment ====== 


sudo pacman -S deepin

====== Optional: Install the deepin applications suite ====== 

sudo pacman -S deepin-extra

====== Optional: Install and use LightDM, the recommended display manager for deepin====== 

sudo pacman -S lightdm
systemctl enable lightdm.service --force


Then edit ''/etc/lightdm/lightdm.conf'', under '''[Seat:*]''' replace the greeter-session setting with '''greeter-session=lightdm-deepin-greeter'''

====== Optional: Install the Manjaro configuration and theming for deepin ====== 

sudo pacman -S deepin-manjaro

====== Create a new user for the new desktop environment ====== 

sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

== Enlightenment == 
{{note|There is not currently a Manjaro settings package for Enlightenment|}}
[[File: E20-Green_Onix_760.png|thumb|left|375px]]


'''[http://www.enlightenment.org/ Enlightenment]''', sometimes known simply as E, is a lightweight desktop environment known for its configurability and tools for creating beautiful user interfaces using its Enlightenment Foundation Libraries (EFL). E started in 1997 as a stacking windows manager, emerging as a desktop environment with development release 0.17. E does not come with a broad array of tools by default, which can be an advantage for experienced users who want to customize their installation, and a disadvantage for users with little or no experience of Linux. E uses a few unique terms, for example referring to panels as “shelves”. A 64-bit installation of E uses about 160M of memory.

====== Install a basic E environment ====== 

sudo pacman -S enlightenment

====== Optional: Install and use Entrance, the recommended display manager for E ====== 
Entrance is available from the AUR in the package '''entrance-git'''. Information on how to install packages from AUR can be found '''[https://wiki.manjaro.org/index.php/Arch_User_Repository here]'''.

$ sudo pacman -S --asdeps meson
$ pamac build entrance-git
$ sudo systemctl enable entrance.service --force

====== Optional: Install Manjaro themes for E ====== 
sudo pacman -S enlightenment-manjaro-themes

====== Create a new user for the new desktop environment ====== 
sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

== LXDE == 


{{Note|Installing LXDE will also result in installing ''Openbox'' as its default window manager. The LXDM display manager will also be downloaded, although it will be necessary to enable this yourself if you wish to replace your existing display manager.}}
[[File: lxde17.1.11.jpg|thumb|left|375px]]


'''[http://lxde.org/ LXDE]''' is a super-lightweight desktop environment that is very similar to XFCE, with the exception that it is not compatible with Compiz. As with XFCE, LXDE is also a somewhat basic desktop environment, lacking some modern features that would be expected, such as a search-bar to find applications and files. However, it is also an excellent choice for less powerful computers.

====== Install a basic lxde environment ====== 


sudo pacman -S lxde network-manager-applet

====== Optional: Install and use LightDM, the recommended display manager for lxde ====== 

sudo pacman -S lightdm lightdm-gtk-greeter lightdm-gtk-greeter-settings
systemctl enable lightdm.service --force

====== Optional: Install the Manjaro configuration and theming for lxde ====== 

sudo pacman -S manjaro-lxde-logout-banner manjaro-lxde-xfce4-notifyd manjaro-lxde-xfce4-volumed-pulse manjaro-settings-manager manjaro-settings-manager-notifier manjaro-lxde-settings arc-maia-icon-theme kvantum-manjaro


To configure LightDM to match the community edition replace the contents of /etc/lightdm/lightdm-gtk-greeter.conf with
[greeter]
background = /usr/share/backgrounds/lxde-breath.png
font-name = Cantarell 12
xft-antialias = true
icon-theme-name = Arc-Maia
screensaver-timeout = 60
theme-name = Adapta-Eta-Maia
cursor-theme-name = xcursor-breeze
show-clock = false
default-user-image = #avatar-default
xft-hintstyle = hintfull
position = 50%,center 50%,center
clock-format =
panel-position = bottom

====== Create a new user for the new desktop environment ====== 

sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

== LXQt == 


[[File: Lxqt-de-18.png|thumb|left|375px]]


The '''[https://lxqt.org/ LXQt Desktop Environment]''' LXQt is a lightweight Qt desktop environment. It will not get in your way. It will not hang or slow down your system. It is focused on being a classic desktop with a modern look and feel. A 64 bit installation of Manjaro running lxqt uses about 250MB of memory.

====== Install a basic LXQt environment ====== 
sudo pacman -S lxqt xscreensaver

====== Install and use LightDM, the recommended display manager for LXQt ====== 
sudo pacman -S lightdm lightdm-slick-greeter lightdm-settings light-locker
systemctl enable lightdm.service --force
edit /etc/lightdm/lightdm.conf, under [Seat:*] replace the greeter-session setting with greeter-session=lightdm-slick-greeter

====== Optional: Install the Manjaro configuration and theming for LXQt ====== 
sudo pacman -S manjaro-lxqt-extra-settings manjaro-openbox-adapta-maia papirus-maia-icon-theme

====== Create a new user for the new desktop environment ====== 
sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

== MATE == 


[[File: mate.jpg|thumb|left|375px]]


The '''[https://mate-desktop.org/ MATE Desktop]''' Environment is the continuation of GNOME 2. It provides an intuitive and attractive desktop environment using traditional metaphors for Linux and other Unix-like operating systems. MATE is under active development to add support for new technologies while preserving a traditional desktop experience. A 64 bit installation of Manjaro running MATE uses about 378MB of memory.

====== Install a basic mate environment ====== 


sudo pacman -S mate network-manager-applet

====== Optional: Install mate applications and configuration tools ====== 
sudo pacman -S mate-extra dconf-editor

====== Optional: Install and use LightDM, the recommended display manager for mate ====== 
sudo pacman -S lightdm lightdm-slick-greeter lightdm-settings
systemctl enable lightdm.service --force
edit '''/etc/lightdm/lightdm.conf''', under [Seat:*] replace the greeter-session setting with '''greeter-session=lightdm-slick-greeter'''

====== Optional: Install the Manjaro configuration and theming for mate ====== 
sudo pacman -S manjaro-mate-settings arc-maia-icon-theme papirus-maia-icon-theme manjaro-settings-manager manjaro-settings-manager-notifier


To configure LightDM to match the community edition replace the contents of /etc/lightdm/slick-greeter.conf with
[Greeter]
background=/usr/share/backgrounds/manjaro-mate/manjaro-mate.jpg
theme-name=Adapta-Nokto-Maia
icon-theme-name=Arc-Maia
draw-grid=false

====== Create a new user for the new desktop environment ====== 
sudo useradd -mG lp,network,power,sys,wheel <username>
sudo passwd <username>


<br clear="all" />

= Window Managers = 


{{note|By nature, building your own desktop environment from a Window Manager will take substantially more time and effort than simply downloading a pre-defined desktop environment.}}


{{warning|The images provided below are purely for illustrative purposes only. You will have you put in the necessary time and effort to configure them.}}


Although Desktop Environments commonly provide a good range of customisation options to suit personal taste and preference, they may still be seen as somewhat restrictive or controlled in the sense that they merely allow for the personalisation of their pre-defined components. However, certain Window Managers empower users to take a 'do it yourself' approach in order to create their own desktop environments. In essence, they may be used as a foundation on which to build upon, as literally every component and every aspect of the desktop is under the direct control and choice of the user. An environment may be as elaborate or as minimalistic as desired, and it is even possible to mix and match various components from other desktop environments.


Therefore extremely powerful and versatile, these window managers also carry the additional benefit of being faster and more resource efficient than pre-defined desktop environments. Interestingly, the super-lightweight LXDE environment is itself built on the Openbox window manager. There are two types of Window Manager: '''Stacking''' and '''Tiling'''. These names denote how application windows will behave on your desktop.

== Stacking Window Managers == 


'''Stacking window managers''' are by far the most popular, and essentially allow application windows to be moved freely around the screen, which may overlap - or 'stack' - upon one another, hence the name. All popular desktop environments (e.g. XFCE, KDE, Gnome, etc.) use stacking window Managers.

=== Openbox === 


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


'''[http://openbox.org/ Openbox]''' is by far the most popular Window Manager available. Due to its popularity there is excellent documentation available, as well as a good choice of additional themes that may be downloaded. '''To install Openbox, enter the command:'''


sudo pacman -S openbox


To install a logout script, configuration application, menu-editor, and extra themes for Openbox, enter the following command:


sudo pacman -S oblogout obconf lxappearance-obconf-gtk3 obmenu openbox-themes-extra

====== Optional: Install the Manjaro configuration, theming, and tools for Openbox ====== 


sudo pacman -S oblogout-manjaro manjaro-openbox-config manjaro-openbox-scripts manjaro-openbox-fonts matcha-gtk-theme
<br clear="all" />

=== FluxBox === 


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


'''[http://fluxbox.org/ FluxBox]''' is another popular Window Manager. It is particularly notable for providing some features not seen in Openbox, such as ''tabbing'', which allows for windows to be grouped together. '''To install FluxBox, enter the command''':


sudo pacman -S fluxbox

====== Optional: Install the newsfetcher and workspace pager for Fluxbox ====== 


sudo pacman -S fbnews fluxter

====== Optional: Install the Manjaro configuration, theming, and tools for Fluxbox ====== 


sudo pacman -S fbmenu-manjaro oblogout-manjaro artwork-fluxbox fluxboxtheme-manjaro
<br clear="all" />

=== IceWM === 


[[File: icewm2.jpg|thumb|left|375px]]


'''[https://www.ice-wm.org/ IceWM]''' is a Window Manager notable for perhaps being closer to a full desktop environment than Openbox or FluxBox. This includes providing a panel complete with menu, in addition to a workspace switcher. '''To install IceWM, enter the command''':


sudo pacman -S icewm


To install a suite of tools and themes specifically for IceWM, enter the command:


sudo pacman -S icewm-utils icewm-themes
<br clear="all" />

== Tiling Window Managers == 


'''Tiling window managers''' - as the name would suggest - tile application windows; each will have their own place on the screen, just like conventional tiles do not overlap. However, unlike conventional tiling, these window managers are usually very flexible, and allow for a multitude of different tiling patterns to suit personal taste and preference. Where stacking window managers focus on using the mouse for navigation, tiling window managers focus on the utilisation of the keyboard instead. As such, they can be much faster to use.

=== Awesome === 


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


'''[http://awesome.naquadah.org/ Awesome]''' is a popular tiling Window Manager, notable for using the '''Lua''' language for configuration. '''To install Awesome, enter the command''':


sudo pacman -S awesome


To install some extra widgets for Awesome, enter the command:


sudo pacman -S vicious


Alternatively you can install the [[Awesome Community Edition]].
<br clear="all" />

=== i3 === 


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


'''[http://i3wm.org/ i3]''' is arguably the most popular tiling window manager available, and notable for using a single, completely self-contained configuration file. '''To install i3, enter the command''':


sudo pacman -S i3-wm


To install a status bar and screen-locker for i3, enter the command:


sudo pacman -S i3lock i3status
<br clear="all" />

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:Editions{{#translation:}}]]

Pacman troubleshooting

2021-12-17T13:22:04Z

Bogdancovaciu:

<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:}}]]

Make GRUB menu & boot-up/down fonts bigger

2021-12-17T04:56:33Z

Bogdancovaciu:

<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): [https://alexandre.deverteuil.net/pages/consolefonts/]


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:}}]]

Wacom Tablet And Pen

2021-12-10T12:53:28Z

Bogdancovaciu:

<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/t/tablets-and-pen-displays/43643 Wacom Thread]
* 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:}}]]

Build Manjaro ISOs with buildiso

2021-10-29T09:56:05Z

Bogdancovaciu:

<languages/>
__TOC__

<translate>
=Prerequisites= 


This is a detailed walkthrough of installation and configuration of the tools and build process.


It is a requirement to either download and install the latest version of [https://manjaro.org/get-manjaro Manjaro] or be running a well maintained Manjaro system. '''It is vital your system is updated''' with the latest available kernel and packages.

==Install Manjaro Tools== 


To get started you need to the following meta-package.


pamac install manjaro-tools-iso git


We will be working with the official XFCE to help you understand what you need to do.

=ISO profile= 
==Download the latest ISO profiles==


The latest profiles can be found in the Manjaro gitlab. You can download them directly using the command:
git clone https://gitlab.manjaro.org/profiles-and-settings/iso-profiles.git ~/iso-profiles

==ISO profile overview== 
The ISO profile for xfce can now be found at


~/iso-profiles/manjaro/xfce


Let's take a closer look at the XFCE profile folder (marked above):


'''desktop-overlay'''
live-overlay -> ../../shared/manjaro/live-overlay
'''Packages-Desktop'''
Packages-Live -> ../../shared/Packages-Live
Packages-Mhwd -> ../../shared/Packages-Mhwd
Packages-Root -> ../../shared/Packages-Root
'''profile.conf'''


* '''desktop-overlay''': After every successful installation of your ISO the files and folders in here will get copied over.
* ''live-overlay'': Similar to ''desktop-overlay''. Files and folders in here will only get copied over to the LiveCD of your ISO.
* '''Packages-Desktop''': This file contains packages for the ISO installation. All packages will also get installed on LiveCDs.
* ''Packages-Live'': This file contains packages, which will only get installed on the LiveCD.
* ''Packages-Mhwd'': This file contains Mhwd packages important to all Manjaro installations and LiveCDs.
* ''Packages-Root'': This file contains base packages important to all Manjaro installations and LiveCDs.
* '''profile.conf''' contains basic settings for your ISO installation and LiveCD.


As you have probably noticed, several are only symlinks to the <code>shared</code> ISO profile. It is good practice to never change files or folders in the <code>shared</code> ISO profile. If you ever want to change them, first copy them to your ISO profile folder and delete the symlink.


All folders and files specific to your ISO are '''in bold'''. You can change them to your liking.

==Modifying an ISO profile== 


The most common places to tweak and customize an ISO profile are the 3 folders marked above: ''desktop-overlay'', ''profile.conf'', ''Packages-Desktop'':

===desktop-overlay=== 


The ''desktop-overlay'' folder looks like this:


~/iso-profiles/manjaro/xfce/desktop-overlay/etc
├── fonts
│ └── conf.d
│ └── 70-no-bitmaps.conf -> /etc/fonts/conf.avail/70-no-bitmaps.conf
└── lightdm
└── lightdm-gtk-greeter.conf


Go to this directory.


~/iso-profiles/manjaro/xfce/desktop-overlay/etc/


Then create '''skel''' folder. This is where you can clone everything you see on your Desktop Screen to ISO.


After the ISO has been successfully installed all files and folder in ''desktop-overlay'' folder get copied over to the installed system. This includes settings/config files but also themes and backgrounds/pictures.


All files and folder in here will get copied to the home folder. Most hidden files and their structure in <code>~/iso-profiles/manjaro/xfce/desktop-overlay/etc/skel/</code> should be already familiar to you, because your home folder looks very similar.

===Clone Custom Wallpaper Desktop=== 


To clone your Custom Wallpaper Desktop. Open a New File Manager and go to this file.


~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-desktop.xml


Change all image directories to where your Custom Wallpaper was located at. For example:


/usr/share/backgrounds/<YOUR IMAGE HERE>

===Example=== 
<div class="toccolours mw-collapsible mw-collapsed">
<span style="color:green">A sample `xfce4-desktop.xml` can be viewed by unfolding this block</span>
<div class="mw-collapsible-content">


<pre>
<?xml version="1.0" encoding="UTF-8"?>

<channel name="xfce4-desktop" version="1.0">
<property name="backdrop" type="empty">
<property name="screen0" type="empty">
<property name="monitor0" type="empty">
<property name="image-path" type="string" value="'''/usr/share/backgrounds/<YOUR IMAGE HERE>'''"/>
<property name="last-image" type="string" value="'''/usr/share/backgrounds/<YOUR IMAGE HERE>'''"/>
<property name="last-single-image" type="string" value="'''/usr/share/backgrounds/<YOUR IMAGE HERE>'''"/>
<property name="image-style" type="int" value="5"/>
</property>
<property name="monitorVGA-0" type="empty">
<property name="workspace0" type="empty">
<property name="color-style" type="int" value="0"/>
<property name="image-style" type="int" value="5"/>
<property name="last-image" type="string" value="'''/usr/share/backgrounds/<YOUR IMAGE HERE>'''"/>
</property>
<property name="workspace1" type="empty">
<property name="color-style" type="int" value="0"/>
<property name="image-style" type="int" value="5"/>
<property name="last-image" type="string" value="'''/usr/share/backgrounds/<YOUR IMAGE HERE>'''"/>
</property>
</property>
</property>
</property>
<property name="desktop-icons" type="empty">
<property name="style" type="int" value="2"/>
<property name="file-icons" type="empty">
<property name="show-removable" type="bool" value="true"/>
</property>
<property name="icon-size" type="uint" value="32"/>
</property>
</channel>
</pre>
</div>
</div>


Go to this directory:


~/iso-profiles/manjaro/xfce/desktop-overlay/


Then create <code>usr/share/backgrounds</code> and place your Custom Wallpaper at this directory.


~/iso-profiles/manjaro/xfce/desktop-overlay/usr/share/backgrounds/

===profile.conf=== 
<div class="toccolours mw-collapsible mw-collapsed">
<span style="color:green">The full content of an example profile.conf can be viewed by unfolding this block. It is always best to use the latest version instead of copying this one.</span>
<div class="mw-collapsible-content">
<pre>
##########################################
###### use this file in the profile ######
##########################################


# use multilib packages; x86_64 only
# multilib="true"


displaymanager="lightdm"


# Set to false to disable autologin in the livecd
# autologin="true"


# nonfree mhwd drivers
# nonfree_mhwd="true"


# use extra packages as defined in pkglist to activate a full profile
#extra="true"


################ install ################


# unset defaults to given value
# efi_boot_loader="grub"


# configure calamares for netinstall
# netinstall="false"


# configure calamares to use chrootcfg instead of unpackfs
# chrootcfg="false"


# use geoip for localization
# geoip='true'


# unset defaults to given values
# names must match systemd service names
enable_systemd=('avahi-daemon' 'bluetooth' 'cronie' 'ModemManager' 'NetworkManager' 'org.cups.cupsd' 'tlp' 'tlp-sleep' 'ufw')
disable_systemd=('pacman-init')


# unset defaults to given values,
# names must match openrc service names
# enable_openrc=('acpid' 'bluetooth' 'elogind' 'cronie' 'cupsd' 'dbus' 'syslog-ng' 'NetworkManager')
# disable_openrc=()


# the same workgroup name if samba is used
# smb_workgroup=""


################# livecd #################


# unset defaults to given value
# hostname="manjaro"


# unset defaults to given value
# username="manjaro"


# unset defaults to given value
# password="manjaro"


# the login shell
# defaults to bash
# login_shell=/bin/bash


# unset defaults to given values
# addgroups="lp,network,power,wheel"


# unset defaults to given values
# names must match systemd service names
# services in enable_systemd array don't need to be listed here
# enable_systemd_live=('manjaro-live' 'mhwd-live' 'pacman-init' 'mirrors-live')


# unset defaults to given values,
# names must match openrc service names
# services in enable_openrc array don't need to be listed here
# enable_openrc_live=('manjaro-live' 'mhwd-live' 'pacman-init' 'mirrors-live')
</pre>
</div>
</div>


This config file contains setting options. All default settings are commented. If you want to change them, uncomment them (remove the <code>#</code> symbol in front) and change it.


The following settings are noteworthy:


* <code>multilib=</code> setting belongs to the <code>>multilib</code> flag in your package lists. multilib will install basic 32bit libraries on 64bit systems. This increases compatibility for 32bit applications on 64bit systems.
* <code>displaymanager=</code> sets the display / login manager your system uses. You need to list your display manager in your package list, too.
* <code>nonfree_xorg=</code> refers to proprietary graphics drivers.
* <code>netinstall=</code>: do not use
* <code>chrootcfg=</code>: do not use
* <code>kernel=</code> lets you set the installed kernel. Do '''not''' include any kernels in your package list! This setting is all you need.
* <code>enable_systemd=</code> let's you set systemd services, which get started on the installed system (and with a similar setting on the livecd).
* <code>enable_openrc=</code>: do not use

===Packages-Desktop=== 
<div class="toccolours mw-collapsible mw-collapsed">
<span style="color:green">An example `Packages-Desktop` file can be viewed by unfolding this block. It is always best to use the latest version instead of copying this one.</span>
<div class="mw-collapsible-content">
<pre>
## Network
avahi
networkmanager
networkmanager-openconnect
networkmanager-openvpn
networkmanager-pptp
networkmanager-vpnc
nss-mdns # NSS support for mDNS (optdepend for avahi)
ntp
mobile-broadband-provider-info
modemmanager
openresolv
openssh
samba
usb_modeswitch


## Libraries for Sound/Audio/Video
alsa-firmware
alsa-utils
ffmpeg
gst-libav
gst-plugins-bad
gst-plugins-base
gst-plugins-good
gst-plugins-ugly
libdvdcss
>multilib manjaro-alsa
manjaro-pulse
pulseaudio-bluetooth
pulseaudio-ctl
pulseaudio-zeroconf


## Connect Packages
android-tools
android-udev
gvfs
gvfs-afc
gvfs-gphoto2
gvfs-mtp
gvfs-nfs
gvfs-smb
mtpfs
udiskie
udisks2


## AUR Support/Development
# Missing base-devel packages
autoconf
automake
binutils
bison
fakeroot
flex
gcc
>multilib gcc-libs-multilib
>multilib gcc-multilib
libtool
m4
make
patch
pkg-config
>multilib lib32-flex
# Extra packages for AUR support
>extra git
>extra patchutils
>extra subversion


## Fonts
cantarell-fonts
# noto-fonts # default font
# noto-fonts-cjk # big package, ~76 mb compressed
# >extra noto-fonts-emoji
terminus-font
ttf-bitstream-vera # xfce4-terminal default Monospace
# ttf-dejavu # Installed as gnome-themes-standard dependency
>extra ttf-inconsolata
>extra ttf-indic-otf
>extra ttf-liberation
>extra ttf-droid


## Games
>extra steam-manjaro


## Package management
pamac
flatpak


## Java
>extra jdk8-openjdk
>extra jre8-openjdk-headless
>extra jre8-openjdk


## Printing
>extra cups
>extra cups-pdf
>extra cups-pk-helper
>extra ghostscript
>extra gsfonts
>extra gtk3-print-backends
>extra hplip
>extra splix
>extra system-config-printer


## Optional dependencies for hplip
>extra pyqt5-common # For hplip
>extra python-pillow # For hplip
>extra python-pip # For hplip
>extra python-pyqt5 # For hplip gui
>extra python-reportlab # For hplip


## Display manager
lightdm
lightdm-gtk-greeter
lightdm-gtk-greeter-settings
accountsservice # Enhanced user accounts handling


## GTK3
gtk3-classic
>multilib lib32-gtk3-classic


## XFCE Group
exo-gtk3
garcon-gtk3
thunar-gtk3
thunar-volman
tumbler
xfce4-appfinder-gtk3
xfce4-panel-gtk3
xfce4-power-manager-gtk3
xfce4-session-gtk3
xfce4-settings-gtk3
xfce4-terminal
xfconf-gtk3
xfdesktop-gtk3
xfwm4-gtk3


## XFCE Extras
blueman
ffmpegthumbnailer # tumbler - for video thumbnails
freetype2 # tumbler - for font thumbnails
gksu
gnome-keyring # fix wlan segfault
libgsf # tumbler - for ODF thumbnails
libopenraw # tumbler - for RAW thumbnails
light-locker
network-manager-applet
menulibre
orage
poppler-glib # tumbler - for PDF thumbnails
thunar-archive-plugin
file-roller
thunar-media-tags-plugin
# >extra xfce4-artwork
xfce4-battery-plugin
xfce4-clipman-plugin
>extra xfce4-cpufreq-plugin
>extra xfce4-cpugraph-plugin
# xfce4-datetime-plugin
>extra xfce4-dict
>extra xfce4-diskperf-plugin
>extra xfce4-fsguard-plugin
>extra xfce4-genmon-plugin
>extra xfce4-mailwatch-plugin
>extra xfce4-mount-plugin
>extra xfce4-mpc-plugin
>extra xfce4-netload-plugin
>extra xfce4-notes-plugin
xfce4-notifyd-gtk3
xfce4-screenshooter
>extra xfce4-sensors-plugin
>extra xfce4-smartbookmark-plugin
>extra xfce4-systemload-plugin
xfce4-taskmanager
>extra xfce4-time-out-plugin
>extra xfce4-timer-plugin
>extra xfce4-verve-plugin
>extra xfce4-wavelan-plugin
>extra xfce4-weather-plugin
xfce4-whiskermenu-plugin-gtk3
xfce4-xkb-plugin
xfce4-pulseaudio-plugin
pavucontrol


## Themes
>extra manjaro-wallpapers-18.0
>extra wallpapers-2018
gnome-icon-theme
gnome-themes-standard
grub-theme-manjaro
matcha-gtk-theme
xcursor-simpleandsoft
xcursor-vanilla-dmz-aa


## Applications
>extra catfish
dmidecode # optional dependency inxi
engrampa
>extra firefox
# >extra flashplugin
>extra galculator-gtk2
gcolor2
>extra gimp
gparted
gufw
>extra audacious
>extra hexchat
htop
qpdfview
inxi
>extra libreoffice-still
ms-office-online
manjaro-hello
manjaro-application-utility
manjaro-settings-manager
manjaro-settings-manager-notifier
>basic midori
>extra mlocate
mousepad
mugshot
>basic parole # media player
>extra pidgin
powertop
screenfetch
>extra poppler-data # CKJ support for pdf
>basic sylpheed # mail client
>extra thunderbird
>extra vlc
>extra viewnior
>extra xfburn
>extra yelp


# Optional dependencies engrampa
p7zip # 7Z and ARJ archive support
unace # ACE archive support
unrar # RAR archive support


## Documentation
manjaro-documentation-en


## Settings packages
>extra manjaro-xfce-gtk3-settings
>basic manjaro-xfce-gtk3-minimal-settings
manjaro-browser-settings


## Xorg Input Drivers
xf86-input-elographics
xf86-input-evdev
xf86-input-keyboard
xf86-input-libinput
xf86-input-mouse
xf86-input-void


## Xorg Server and Graphics
>multilib lib32-libva-intel-driver
>multilib lib32-libva-mesa-driver
>multilib lib32-libva-vdpau-driver
libva-intel-driver
libva-mesa-driver
libva-vdpau-driver
mesa-demos
>multilib lib32-mesa-demos
numlockx
xdg-user-dirs
xorg-server
xorg-twm
xorg-xinit
xorg-xkill


## Desktop Utils
perl-file-mimeinfo
xdg-utils
xdg-su


## Misc
manjaro-hotfixes


</pre>
</div>
</div>
This file contains a list of packages, which will get installed on your installed ISO (XFCE) '''and''' the LiveCD (the packages in Packages-Live file only get installled on the live ISO). This is a package list with Xfce specific packages (and packages you like to add to your custom Manjaro ISO) of multiple package lists in your ISO profile. The other package lists are more generic.


You can add or remove package names from this list as you like. You do not need to worry about dependencies when adding package names, just make sure the package name is spelled correctly and the package is available in the Manjaro repositories.


<code>#</code> marks a comment. The rest of the line after the <code>#</code> symbol gets ignored.

===Adding AUR packages=== 


If you want to add AUR packages to your ISO, you need to create a online repository and add it to a file '''user-repos.conf''' beside your '''profile.conf'''.


'''Only use your own http enabled repo.'''


[your-repo-name]
SigLevel = Optional TrustAll
Server = http://repo.server.tld/your-repo-name


The article [[Buildiso with AUR packages: Using buildpkg]] contains more detailed information on this process.

=manjaro-tools.conf= 


<code>manjaro-tools.conf</code> is the central configuration file for all tools part of ''manjaro-tools''. Only edit the general and the "buildiso" part to not exceed the scope of this tutorial. If you are not sure what and how to edit it, do '''not''' edit it. You can always use arguments with the <code>buildiso</code> command later.


By default, the systemwide config file is installed in


/etc/manjaro-tools/manjaro-tools.conf


Best practice is to leave the systemwide file untouched and copy the system wide config to your home directory here:


~/.config/manjaro-tools


If the userconfig is present, ''manjaro-tools''/''buildiso'' will load the userconfig values, however, if variables have been set in the systemwide config file, these values take precedence over the userconfig. Best practice is to leave the systemwide file untouched. By default it is commented and shows just initialization values done in code.

=Build your ISO= 
Build your ISO with the following command:
buildiso -p xfce
You need to specify the name of your ISO profile after the <code>-p</code> argument. In this case, it is <code>xfce</code>.


If the build process fails with an error, start it again.


'''Attention:''' The build process needs at least 10 minutes to complete or much longer when you are using HDDs, slow CPUs, or large ISOs.

When the build process finishes successfully, the ISO file and the package list will appear in this folder:
/var/cache/manjaro-tools/iso/
===Example:=== 
You can use arguments with the <code>buildiso</code> command for more build options:
buildiso -f -p xfce -b stable
* <code>-f</code> let's you specify if you want the full ISO. If omitted a minimal ISO will be build.
* <code>-b</code> let's you specify the branch. You can also set this in your <code>manjaro-tools.conf</code> file.
You can find other examples of builds using different arguments for ''buildiso'' [https://wiki.manjaro.org/index.php?title=Manjaro-tools#buildiso here].

=Cleaning your hard drive= 


After a successful or failed build, you can get rid of most data (the "raw" ISO with all downloaded packages) by deleting this folder:


sudo rm -r /var/lib/manjaro-tools/buildiso/


To clean your system of packages files of packages not installed on your system (this includes all the package files downloaded for your custom ISO):


paccache -ruk0


You can also manually look into


/var/cache/manjaro-tools/


and delete folders or files to your liking. If you want to delete all ISO images, package lists, and cached Xorg packages do:


sudo rm -r /var/cache/manjaro-tools/


Please remember that all these packages and files are saved for your convenience. If you clean your system like suggested above, you have to download '''all''' packages and build '''all''' images again the next time you want to build your own Manjaro ISO.


By default, your <code>manjaro-tools.conf</code> file is saved. If you want to delete it, use


rm -r ~/.config/manjaro-tools

=Tips & Tricks= 

==Building a minimal ISO== 
A minimal ISO is easy to create by modifying an entry in the profile.conf file. Find the section
<pre>
# use extra packages as defined in pkglist to activate a full profile
# extra="false"
extra="true"
</pre>
and remove the '''#''' mark in front of '''extra = "false"''' and add a '''#''' in front of '''extra = "true"'''.


If you prefer not to change this you can always use the '''-f''' with buildiso to build a full profile.

=See also= 
* Source: [https://gitlab.manjaro.org/profiles-and-settings/iso-profiles Manjaro Gitlab ISO Profiles] (master branch may be unstable - select the branch for latest release)
* Forum: [https://archived.forum.manjaro.org/t/how-to-create-your-own-manjaro-spin-with-manjaro-tools/1355 How to create your own Manjaro spin with Manjaro-Tools]
* Forum: [https://archived.forum.manjaro.org/t/howto-build-your-own-manjaro-spin/65821 Philip Müller shows how-to]
* Video: [https://youtu.be/B--je--m0VI Building Manjaro ISO by Philip Müller](Tutorial Video)
* Wiki: [[Buildiso with AUR packages: Using buildpkg]]
</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:Development{{#translation:}}]]
[[Category:ISO{{#translation:}}]]

Build Manjaro ISOs with buildiso

2021-10-29T09:54:35Z

Bogdancovaciu:

<languages/>
__TOC__

<translate>
=Prerequisites= 


This is a detailed walkthrough of installation and configuration of the tools and build process.


It is a requirement to either download and install the latest version of [https://manjaro.org/get-manjaro Manjaro] or be running a well maintained Manjaro system. '''It is vital your system is updated''' with the latest available kernel and packages.

==Install Manjaro Tools== 


To get started you need to the following meta-package.


pamac install manjaro-tools-iso git


We will be working with the official XFCE to help you understand what you need to do.

=ISO profile= 
==Download the latest ISO profiles==


The latest profiles can be found in the Manjaro gitlab. You can download them directly using the command:
git clone https://gitlab.manjaro.org/profiles-and-settings/iso-profiles.git ~/iso-profiles

==ISO profile overview== 
The ISO profile for xfce can now be found at


~/iso-profiles/manjaro/xfce


Let's take a closer look at the XFCE profile folder (marked above):


'''desktop-overlay'''
live-overlay -> ../../shared/manjaro/live-overlay
'''Packages-Desktop'''
Packages-Live -> ../../shared/Packages-Live
Packages-Mhwd -> ../../shared/Packages-Mhwd
Packages-Root -> ../../shared/Packages-Root
'''profile.conf'''


* '''desktop-overlay''': After every successful installation of your ISO the files and folders in here will get copied over.
* ''live-overlay'': Similar to ''desktop-overlay''. Files and folders in here will only get copied over to the LiveCD of your ISO.
* '''Packages-Desktop''': This file contains packages for the ISO installation. All packages will also get installed on LiveCDs.
* ''Packages-Live'': This file contains packages, which will only get installed on the LiveCD.
* ''Packages-Mhwd'': This file contains Mhwd packages important to all Manjaro installations and LiveCDs.
* ''Packages-Root'': This file contains base packages important to all Manjaro installations and LiveCDs.
* '''profile.conf''' contains basic settings for your ISO installation and LiveCD.


As you have probably noticed, several are only symlinks to the <code>shared</code> ISO profile. It is good practice to never change files or folders in the <code>shared</code> ISO profile. If you ever want to change them, first copy them to your ISO profile folder and delete the symlink.


All folders and files specific to your ISO are '''in bold'''. You can change them to your liking.

==Modifying an ISO profile== 


The most common places to tweak and customize an ISO profile are the 3 folders marked above: ''desktop-overlay'', ''profile.conf'', ''Packages-Desktop'':

===desktop-overlay=== 


The ''desktop-overlay'' folder looks like this:


~/iso-profiles/manjaro/xfce/desktop-overlay/etc
├── fonts
│ └── conf.d
│ └── 70-no-bitmaps.conf -> /etc/fonts/conf.avail/70-no-bitmaps.conf
└── lightdm
└── lightdm-gtk-greeter.conf


Go to this directory.


~/iso-profiles/manjaro/xfce/desktop-overlay/etc/


Then create '''skel''' folder. This is where you can clone everything you see on your Desktop Screen to ISO.


After the ISO has been successfully installed all files and folder in ''desktop-overlay'' folder get copied over to the installed system. This includes settings/config files but also themes and backgrounds/pictures.


All files and folder in here will get copied to the home folder. Most hidden files and their structure in <code>~/iso-profiles/manjaro/xfce/desktop-overlay/etc/skel/</code> should be already familiar to you, because your home folder looks very similar.

===Clone Custom Wallpaper Desktop=== 


To clone your Custom Wallpaper Desktop. Open a New File Manager and go to this file.


~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-desktop.xml


Change all image directories to where your Custom Wallpaper was located at. For example:


/usr/share/backgrounds/<YOUR IMAGE HERE>

===Example=== 
<div class="toccolours mw-collapsible mw-collapsed">
<span style="color:green">A sample `xfce4-desktop.xml` can be viewed by unfolding this block</span>
<div class="mw-collapsible-content">


<pre>
<?xml version="1.0" encoding="UTF-8"?>

<channel name="xfce4-desktop" version="1.0">
<property name="backdrop" type="empty">
<property name="screen0" type="empty">
<property name="monitor0" type="empty">
<property name="image-path" type="string" value="'''/usr/share/backgrounds/<YOUR IMAGE HERE>'''"/>
<property name="last-image" type="string" value="'''/usr/share/backgrounds/<YOUR IMAGE HERE>'''"/>
<property name="last-single-image" type="string" value="'''/usr/share/backgrounds/<YOUR IMAGE HERE>'''"/>
<property name="image-style" type="int" value="5"/>
</property>
<property name="monitorVGA-0" type="empty">
<property name="workspace0" type="empty">
<property name="color-style" type="int" value="0"/>
<property name="image-style" type="int" value="5"/>
<property name="last-image" type="string" value="'''/usr/share/backgrounds/<YOUR IMAGE HERE>'''"/>
</property>
<property name="workspace1" type="empty">
<property name="color-style" type="int" value="0"/>
<property name="image-style" type="int" value="5"/>
<property name="last-image" type="string" value="'''/usr/share/backgrounds/<YOUR IMAGE HERE>'''"/>
</property>
</property>
</property>
</property>
<property name="desktop-icons" type="empty">
<property name="style" type="int" value="2"/>
<property name="file-icons" type="empty">
<property name="show-removable" type="bool" value="true"/>
</property>
<property name="icon-size" type="uint" value="32"/>
</property>
</channel>
</pre>
</div>
</div>


Go to this directory:


~/iso-profiles/manjaro/xfce/desktop-overlay/


Then create <code>usr/share/backgrounds</code> and place your Custom Wallpaper at this directory.


~/iso-profiles/manjaro/xfce/desktop-overlay/usr/share/backgrounds/

===profile.conf=== 
<div class="toccolours mw-collapsible mw-collapsed">
<span style="color:green">The full content of an example profile.conf can be viewed by unfolding this block. It is always best to use the latest version instead of copying this one.</span>
<div class="mw-collapsible-content">
<pre>
##########################################
###### use this file in the profile ######
##########################################


# use multilib packages; x86_64 only
# multilib="true"


displaymanager="lightdm"


# Set to false to disable autologin in the livecd
# autologin="true"


# nonfree mhwd drivers
# nonfree_mhwd="true"


# use extra packages as defined in pkglist to activate a full profile
#extra="true"


################ install ################


# unset defaults to given value
# efi_boot_loader="grub"


# configure calamares for netinstall
# netinstall="false"


# configure calamares to use chrootcfg instead of unpackfs
# chrootcfg="false"


# use geoip for localization
# geoip='true'


# unset defaults to given values
# names must match systemd service names
enable_systemd=('avahi-daemon' 'bluetooth' 'cronie' 'ModemManager' 'NetworkManager' 'org.cups.cupsd' 'tlp' 'tlp-sleep' 'ufw')
disable_systemd=('pacman-init')


# unset defaults to given values,
# names must match openrc service names
# enable_openrc=('acpid' 'bluetooth' 'elogind' 'cronie' 'cupsd' 'dbus' 'syslog-ng' 'NetworkManager')
# disable_openrc=()


# the same workgroup name if samba is used
# smb_workgroup=""


################# livecd #################


# unset defaults to given value
# hostname="manjaro"


# unset defaults to given value
# username="manjaro"


# unset defaults to given value
# password="manjaro"


# the login shell
# defaults to bash
# login_shell=/bin/bash


# unset defaults to given values
# addgroups="lp,network,power,wheel"


# unset defaults to given values
# names must match systemd service names
# services in enable_systemd array don't need to be listed here
# enable_systemd_live=('manjaro-live' 'mhwd-live' 'pacman-init' 'mirrors-live')


# unset defaults to given values,
# names must match openrc service names
# services in enable_openrc array don't need to be listed here
# enable_openrc_live=('manjaro-live' 'mhwd-live' 'pacman-init' 'mirrors-live')
</pre>
</div>
</div>


This config file contains setting options. All default settings are commented. If you want to change them, uncomment them (remove the <code>#</code> symbol in front) and change it.


The following settings are noteworthy:


* <code>multilib=</code> setting belongs to the <code>>multilib</code> flag in your package lists. multilib will install basic 32bit libraries on 64bit systems. This increases compatibility for 32bit applications on 64bit systems.
* <code>displaymanager=</code> sets the display / login manager your system uses. You need to list your display manager in your package list, too.
* <code>nonfree_xorg=</code> refers to proprietary graphics drivers.
* <code>netinstall=</code>: do not use
* <code>chrootcfg=</code>: do not use
* <code>kernel=</code> lets you set the installed kernel. Do '''not''' include any kernels in your package list! This setting is all you need.
* <code>enable_systemd=</code> let's you set systemd services, which get started on the installed system (and with a similar setting on the livecd).
* <code>enable_openrc=</code>: do not use

===Packages-Desktop=== 
<div class="toccolours mw-collapsible mw-collapsed">
<span style="color:green">An example `Packages-Desktop` file can be viewed by unfolding this block. It is always best to use the latest version instead of copying this one.</span>
<div class="mw-collapsible-content">
<pre>
## Network
avahi
networkmanager
networkmanager-openconnect
networkmanager-openvpn
networkmanager-pptp
networkmanager-vpnc
nss-mdns # NSS support for mDNS (optdepend for avahi)
ntp
mobile-broadband-provider-info
modemmanager
openresolv
openssh
samba
usb_modeswitch


## Libraries for Sound/Audio/Video
alsa-firmware
alsa-utils
ffmpeg
gst-libav
gst-plugins-bad
gst-plugins-base
gst-plugins-good
gst-plugins-ugly
libdvdcss
>multilib manjaro-alsa
manjaro-pulse
pulseaudio-bluetooth
pulseaudio-ctl
pulseaudio-zeroconf


## Connect Packages
android-tools
android-udev
gvfs
gvfs-afc
gvfs-gphoto2
gvfs-mtp
gvfs-nfs
gvfs-smb
mtpfs
udiskie
udisks2


## AUR Support/Development
# Missing base-devel packages
autoconf
automake
binutils
bison
fakeroot
flex
gcc
>multilib gcc-libs-multilib
>multilib gcc-multilib
libtool
m4
make
patch
pkg-config
>multilib lib32-flex
# Extra packages for AUR support
>extra git
>extra patchutils
>extra subversion


## Fonts
cantarell-fonts
# noto-fonts # default font
# noto-fonts-cjk # big package, ~76 mb compressed
# >extra noto-fonts-emoji
terminus-font
ttf-bitstream-vera # xfce4-terminal default Monospace
# ttf-dejavu # Installed as gnome-themes-standard dependency
>extra ttf-inconsolata
>extra ttf-indic-otf
>extra ttf-liberation
>extra ttf-droid


## Games
>extra steam-manjaro


## Package management
pamac
flatpak


## Java
>extra jdk8-openjdk
>extra jre8-openjdk-headless
>extra jre8-openjdk


## Printing
>extra cups
>extra cups-pdf
>extra cups-pk-helper
>extra ghostscript
>extra gsfonts
>extra gtk3-print-backends
>extra hplip
>extra splix
>extra system-config-printer


## Optional dependencies for hplip
>extra pyqt5-common # For hplip
>extra python-pillow # For hplip
>extra python-pip # For hplip
>extra python-pyqt5 # For hplip gui
>extra python-reportlab # For hplip


## Display manager
lightdm
lightdm-gtk-greeter
lightdm-gtk-greeter-settings
accountsservice # Enhanced user accounts handling


## GTK3
gtk3-classic
>multilib lib32-gtk3-classic


## XFCE Group
exo-gtk3
garcon-gtk3
thunar-gtk3
thunar-volman
tumbler
xfce4-appfinder-gtk3
xfce4-panel-gtk3
xfce4-power-manager-gtk3
xfce4-session-gtk3
xfce4-settings-gtk3
xfce4-terminal
xfconf-gtk3
xfdesktop-gtk3
xfwm4-gtk3


## XFCE Extras
blueman
ffmpegthumbnailer # tumbler - for video thumbnails
freetype2 # tumbler - for font thumbnails
gksu
gnome-keyring # fix wlan segfault
libgsf # tumbler - for ODF thumbnails
libopenraw # tumbler - for RAW thumbnails
light-locker
network-manager-applet
menulibre
orage
poppler-glib # tumbler - for PDF thumbnails
thunar-archive-plugin
file-roller
thunar-media-tags-plugin
# >extra xfce4-artwork
xfce4-battery-plugin
xfce4-clipman-plugin
>extra xfce4-cpufreq-plugin
>extra xfce4-cpugraph-plugin
# xfce4-datetime-plugin
>extra xfce4-dict
>extra xfce4-diskperf-plugin
>extra xfce4-fsguard-plugin
>extra xfce4-genmon-plugin
>extra xfce4-mailwatch-plugin
>extra xfce4-mount-plugin
>extra xfce4-mpc-plugin
>extra xfce4-netload-plugin
>extra xfce4-notes-plugin
xfce4-notifyd-gtk3
xfce4-screenshooter
>extra xfce4-sensors-plugin
>extra xfce4-smartbookmark-plugin
>extra xfce4-systemload-plugin
xfce4-taskmanager
>extra xfce4-time-out-plugin
>extra xfce4-timer-plugin
>extra xfce4-verve-plugin
>extra xfce4-wavelan-plugin
>extra xfce4-weather-plugin
xfce4-whiskermenu-plugin-gtk3
xfce4-xkb-plugin
xfce4-pulseaudio-plugin
pavucontrol


## Themes
>extra manjaro-wallpapers-18.0
>extra wallpapers-2018
gnome-icon-theme
gnome-themes-standard
grub-theme-manjaro
matcha-gtk-theme
xcursor-simpleandsoft
xcursor-vanilla-dmz-aa


## Applications
>extra catfish
dmidecode # optional dependency inxi
engrampa
>extra firefox
# >extra flashplugin
>extra galculator-gtk2
gcolor2
>extra gimp
gparted
gufw
>extra audacious
>extra hexchat
htop
qpdfview
inxi
>extra libreoffice-still
ms-office-online
manjaro-hello
manjaro-application-utility
manjaro-settings-manager
manjaro-settings-manager-notifier
>basic midori
>extra mlocate
mousepad
mugshot
>basic parole # media player
>extra pidgin
powertop
screenfetch
>extra poppler-data # CKJ support for pdf
>basic sylpheed # mail client
>extra thunderbird
>extra vlc
>extra viewnior
>extra xfburn
>extra yelp


# Optional dependencies engrampa
p7zip # 7Z and ARJ archive support
unace # ACE archive support
unrar # RAR archive support


## Documentation
manjaro-documentation-en


## Settings packages
>extra manjaro-xfce-gtk3-settings
>basic manjaro-xfce-gtk3-minimal-settings
manjaro-browser-settings


## Xorg Input Drivers
xf86-input-elographics
xf86-input-evdev
xf86-input-keyboard
xf86-input-libinput
xf86-input-mouse
xf86-input-void


## Xorg Server and Graphics
>multilib lib32-libva-intel-driver
>multilib lib32-libva-mesa-driver
>multilib lib32-libva-vdpau-driver
libva-intel-driver
libva-mesa-driver
libva-vdpau-driver
mesa-demos
>multilib lib32-mesa-demos
numlockx
xdg-user-dirs
xorg-server
xorg-twm
xorg-xinit
xorg-xkill


## Desktop Utils
perl-file-mimeinfo
xdg-utils
xdg-su


## Misc
manjaro-hotfixes


</pre>
</div>
</div>
This file contains a list of packages, which will get installed on your installed ISO (XFCE) '''and''' the LiveCD (the packages in Packages-Live file only get installled on the live ISO). This is a package list with Xfce specific packages (and packages you like to add to your custom Manjaro ISO) of multiple package lists in your ISO profile. The other package lists are more generic.


You can add or remove package names from this list as you like. You do not need to worry about dependencies when adding package names, just make sure the package name is spelled correctly and the package is available in the Manjaro repositories.


<code>#</code> marks a comment. The rest of the line after the <code>#</code> symbol gets ignored.

===Adding AUR packages=== 


If you want to add AUR packages to your ISO, you need to create a online repository and add it to a file '''user-repos.conf''' beside your '''profile.conf'''.


'''Only use your own http enabled repo.'''


[your-repo-name]
SigLevel = Optional TrustAll
Server = http://repo.server.tld/your-repo-name


The article [[Buildiso with AUR packages: Using buildpkg]] contains more detailed information on this process.

=manjaro-tools.conf= 


<code>manjaro-tools.conf</code> is the central configuration file for all tools part of ''manjaro-tools''. Only edit the general and the "buildiso" part to not exceed the scope of this tutorial. If you are not sure what and how to edit it, do '''not''' edit it. You can always use arguments with the <code>buildiso</code> command later.


By default, the systemwide config file is installed in


/etc/manjaro-tools/manjaro-tools.conf


Best practice is to leave the systemwide file untouched and copy the system wide config to your home directory here:


~/.config/manjaro-tools


If the userconfig is present, ''manjaro-tools''/''buildiso'' will load the userconfig values, however, if variables have been set in the systemwide config file, these values take precedence over the userconfig. Best practice is to leave the systemwide file untouched. By default it is commented and shows just initialization values done in code.

=Build your ISO= 
Build your ISO with the following command:
buildiso -p xfce
You need to specify the name of your ISO profile after the <code>-p</code> argument. In this case, it is <code>xfce</code>.


If the build process fails with an error, start it again.


'''Attention:''' The build process needs at least 10 minutes to complete or much longer when you are using HDDs, slow CPUs, or large ISOs.

When the build process finishes successfully, the ISO file and the package list will appear in this folder:
/var/cache/manjaro-tools/iso/
===Example:=== 
You can use arguments with the <code>buildiso</code> command for more build options:
buildiso -f -p xfce -b stable
* <code>-f</code> let's you specify if you want the full ISO. If omitted a minimal ISO will be build.
* <code>-b</code> let's you specify the branch. You can also set this in your <code>manjaro-tools.conf</code> file.
You can find other examples of builds using different arguments for ''buildiso'' [https://wiki.manjaro.org/index.php?title=Manjaro-tools#buildiso here].

=Cleaning your hard drive= 


After a successful or failed build, you can get rid of most data (the "raw" ISO with all downloaded packages) by deleting this folder:


sudo rm -r /var/lib/manjaro-tools/buildiso/


To clean your system of packages files of packages not installed on your system (this includes all the package files downloaded for your custom ISO):


paccache -ruk0


You can also manually look into


/var/cache/manjaro-tools/


and delete folders or files to your liking. If you want to delete all ISO images, package lists, and cached Xorg packages do:


sudo rm -r /var/cache/manjaro-tools/


Please remember that all these packages and files are saved for your convenience. If you clean your system like suggested above, you have to download '''all''' packages and build '''all''' images again the next time you want to build your own Manjaro ISO.


By default, your <code>manjaro-tools.conf</code> file is saved. If you want to delete it, use


rm -r ~/.config/manjaro-tools

=Tips & Tricks= 

==Building a minimal ISO== 
A minimal ISO is easy to create by modifying an entry in the profile.conf file. Find the section
<pre>
# use extra packages as defined in pkglist to activate a full profile
# extra="false"
extra="true"
</pre>
and remove the '''#''' mark in front of '''extra = "false"''' and add a '''#''' in front of '''extra = "true"'''.


If you prefer not to change this you can always use the '''-f''' with buildiso to build a full profile.

=See also= 
* Source: [https://gitlab.manjaro.org/profiles-and-settings/iso-profiles Manjaro Gitlab ISO Profiles] (master branch may be unstable - select the branch for latest release)
* Forum: [https://archived.forum.manjaro.org/t/how-to-create-your-own-manjaro-spin-with-manjaro-tools/1355 How to create your own Manjaro spin with Manjaro-Tools]
* Forum: [https://forum.manjaro.org/t/howto-build-your-own-manjaro-spin/65821 Philip Müller shows how-to]
* Video: [https://youtu.be/B--je--m0VI Building Manjaro ISO by Philip Müller](Tutorial Video)
* Wiki: [[Buildiso with AUR packages: Using buildpkg]]
</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:Development{{#translation:}}]]
[[Category:ISO{{#translation:}}]]

Set all Qt app's to use GTK+ font & theme settings

2021-09-22T15:37:18Z

Bogdancovaciu:

<languages/>
__TOC__

{{SectionTemplate|<translate> Overview</translate>|
<translate>

When using a [[Desktop_Environments|Desktop Environment]] or Window Manager that doesn't allow for the settings of QT themes, you can set QT to use your GTK themes instead.
</translate>}}

{{SectionTemplate|
<translate>

Using qt5ct
</translate>
|2=
<translate>

{{note|In some Manjaro editions, this is already done for you by default}}


Install {{ic|qt5ct}} using your favorite package manager or the command:
{{UserCmd|command=pamac install qt5ct}}


Set environment variables in {{ic|~/.profile}} by adding or updating the following lines:
{{File|file=~/.profile|content=<pre>export QT_QPA_PLATFORMTHEME="qt5ct"</pre>}}


Run the application '''QT5 Configuration Manager''' from the menu or run the command {{ic|qt5ct}}.


Logout and login again to make the change effective
</translate>}}

{{SectionTemplate|<translate> See Also</translate>|
* [https://wiki.archlinux.org/index.php/Uniform_Look_for_Qt_and_GTK_Applications Arch Wiki]
* Matching [https://archived.forum.manjaro.org/t/wiki-set-all-qt-apps-to-use-your-gtk-theme-font-settings/17654 Forum Topic]|Chmsee-icon.png}}

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

Basic Tips for conky

2021-09-22T15:36:06Z

Bogdancovaciu: /* Configuration file */

<languages/>
__TOC__
<translate>
==Installation== 
Conky can be installed using the package manager
{{UserCmd|command=pamac install conky}}

===Configuration=== 
All file names starting with a dot <code>.</code> are hidden files. If you want to see hidden files in your file manager, you need to make them visible. In most file managers this will be available in the options.
====Configuration file====
The default configuration file is located in {{ic|/usr/share/doc/conky-1.11.5_pre/conky.conf}} where version are subject to change.
Conky do not create a local conky folder so you will have to create beforehand
{{UserCmd|command=mkdir -p ~/.config/conky}}
Then copy the default to home
{{UserCmd|command=cp /usr/share/doc/conky-1.11.5_pre/conky.conf ~/.config/conky/conky.conkyrc}}
The configuration file is a simple text file and the content written using [[https://www.lua.org/|LUA syntax]] and is split into two parts


* Configuration
* Text

===Conky configuration=== 
The first/upper part contains all the configuration settings for the entire conky. Things like the position of the conky on your screen, transparency settings, border settings, the default font and it's size, and how often your conky gets updated. The whole configuration belong between brackets like this
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.config = {
};</pre>
Some rules apply

* Every line end with <code>,</code>
* Non-boolean/numerical value should be placed between <code>'</code>
* Comment start with <code>--</code>
}}
===Examples=== 
'''1.''' This will set the default font color of your conky to white. Additionally, a <code>color1</code> gets set using a [http://html-color-codes.info/ Html Color Code]to a light blue:
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.config = {
...
default_color = 'white', -- White default color
color1 = '0ab1ff', -- Light blue
...
};</pre>
}}
'''2.''' This enables Xft, set the default font (LiberationMono), make it bold and set it's size (8):
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.config = {
...
use_xft = true,
font = 'LiberationMono:bold:size=8',
...
};</pre>
}}
'''3.''' In order to position your conky on your screen, modify these settings:
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.config = {
...
alignment = 'top_right', -- Conky gets placed in the top right corner of your desktop
gap_x 18, -- with a horizontal gap of 18 pixels (to your right screen edge)
gap_y 20, -- and a vertical gap of 20 pixels (to your top screen edge).
...
};</pre>
}}
'''4.''' In some case you can have multiple values for one setting, they will be separated by a coma:
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.config = {
...
own_window_hints = 'undecorated,sticky,skip_taskbar,skip_pager,below',
...
};</pre>
}}
Use the command: <code>man conky</code>, and look into the '''CONFIGURATION SETTINGS''' section to see every settings available.

===Conky text=== 
The second part contains the displayed conky code. Every code line corresponds to one displayed line on your desktop. There are a lot of available for displaying and modifying all kinds of information. Use the command: <code>man conky</code>, and look into the '''OBJECTS/VARIABLES''' section to see every objects/variables available.
{{Info|The lines in the '''conky.text''' section is printed exactly as is. E.g. if you create an empty line between sections - conky will display an empty line.}}

The whole code belong between these two double bracket:
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.text = [[
]];</pre>
}}
===Examples=== 
'''1.''' You can choose the color of your font using one of the following variables:
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.text = [[
...
${color}
${color1}
...
]];</pre>
}}


Every variable is marked with a <code>$</code> sign and by <code>{ }</code> brackets (only needed, if the variable contains more than one word).


'''2.''' You can call the default font (and it's size) with this command:
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.text = [[
...
$font
...
]];</pre>
}}
If you want a different font (DejaVuSerif) and font size (9) in your conky, use this command in your <code>.conkyrc</code> code:
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.text = [[
...
${font DejaVuSerif:size=9}
...
]];</pre>
}}
'''3.''' This code line displays the text "Kernel: " and the kernel you are using (using <code>$alignr</code> just yields a nicer formatting, it is not necessary: <code>$alignr</code> aligns all following text on the right of your conky):
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.text = [[
Kernel: ${alignr}${kernel}
]];</pre>
}}
'''4.''' This variable gives you the latest 3 manjaro blog entry titles (using rss). It checks for updates every 60 minutes.
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.text = [[
${rss http://manjaro.org/feed/ 60 item_titles 3}
]];</pre>
}}
'''5.''' Information about the root partition <code>/</code> of your manjaro installation is displayed using
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.text = [[
Root: ${alignr}${fs_used /} of ${fs_size /}
]];</pre>
}}
'''6.''' Instead of example 3, you can use the following code to display the exact same information:
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.text = [[
Kernel: ${alignr}${execi 3600 uname -r}
]];</pre>
}}

===execi=== 
The variable <code>${execi 3600 XXXX}</code> runs the <code>XXXX</code> bash code in your terminal every 3600 seconds and displays the result in your conky. The result of the <code>uname -r</code> bash command is your currently used kernel name.


Use any bash command instead of <code>XXXX</code> you can think of. The bash commands can be as long and complicated as you want.


Warning: Using complicated bash commands (e.g. which call other programs or use large files) with low intervals (e.g. <code>${execi 2 XXXX}</code> runs the <code>XXXX</code> code once every 2 seconds and displays it's result in your conky) can use a lot of hardware resources and/or make your computer unresponsive.

===Running conky=== 
If you want to display a conky on your desktop a {{ic|~/.config/conky/conky.conkyrc}} file with code in it is required. Next, open a terminal and run conky pointing to the file
{{UserCmd|command=conky -c ~/.config/conky/conky.conkyrc}}
or to run as background daemon
{{UserCmd|command=conky -d -c ~/.config/conky/conky.conkyrc}}


If you want to run conky automatically after each boot of your computer, you need to find out how to autostart a program. This depends on the Desktop Manager you are using. The next is examples of how to run conky from your system autostart folder/file/script/command.
<code>sleep 20</code> and <code>-p 20</code> delay the start of conky by 20 seconds after your Desktop Environment has started. Adjust this value to your liking.


{{UserCmd|command=conky -c ~/.config/conky/conky.conkyrc &}}
{{UserCmd|command=sleep 20 && conky -c ~/.config/conky/conky.conkyrc &}}


When you change the running conky configuration file - conky will reload. But if you changed one of your dependency scripts (e.g. because you changed a variable and want to see the consequences) you will have to reload conky
{{UserCmd|command=killall conky && conky -c ~/.config/config/conky.conkyrc}}

===Troubleshooting & Tips=== 

====Missing rings==== 


To be able to use LUA scripts to execute drawing functions like clock rings - you will a conky package compiled with LUA support. Either build the package the package {{ic|conky-lua}} from [[Arch_User_Repository|AUR]] or install the {{ic|conky-lua-nv}} from the official repo.

====Missing network information==== 
If network information is missing like download speed or network name (SSID), you need to replace the network interfaces in the configuration file with your network interface name. To get the names of your interfaces - open a terminal and execute
{{UserCmd|command=ip a | grep ' state UP' | cut -d' ' -f2 | cut -d':' -f1}}
Use the output from the command. Interface names starting with <code>en</code> is ethernet interface and names starting with <code>wl</code> is wireless interfaces. Replace all network interfaces names with (e.g. <code>wlan0</code>, <code>eth0</code>) in your <code>.conkyrc</code> text section with the interface name(s) you retrieved from the above command.

===Conky Manager=== 
An application named Conky manager exist but has not been updated for years and the configurations found in the package may work or they may not. You may install it - it can be a used as an inspiration but you should not rely on it. If you still think you it is a must have - you can build the package {{ic|conky-manager}} using [[Arch_User_Repository|AUR]]
{{UserCmd|command=pamac build conky-manager}}

==See Also== 
* The [https://github.com/brndnmtthws/conky/wiki Conky website]
* The [https://wiki.archlinux.org/index.php/conky Arch Wiki] page for Conky
</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:Applications{{#translation:}}]]

Fstab - Use SystemD automount

2021-09-22T14:34:52Z

Bogdancovaciu:

<languages/>
__TOC__
{{SectionTemplate|<translate> Introduction</translate>|
<translate>

I found a combination of systemd options (on the ArchWiki [https://wiki.archlinux.org/index.php/Systemd#Automount]) that can be used in the /etc/fstab when mounting storage devices --be they internal, external, or network shares.


The magic (to me) that these mount options bring is that if a network share or an external drive that is being called via /etc/fstab is not present, they save your machine from hanging for a minute or two during the boot process.


A device called this way via /etc/fstab is mounted the first time data is attempted to be accessed from it. Only on this first mount is there any (minor) noticeable delay, when compared to having the device mounted the "old" way.
</translate>}}

{{SectionTemplate|1=<translate> A suitable problem example</translate>|2=
<translate>

I have a ReadyNAS Duo v1, which is connected to my LAN. These days I quite often turn it off as it doesn't need to run perpetually.


A problem that this causes is that if I forget to comment out the NFS share(s) that I'm using from the /etc/fstab file, I have to wait for a minute or two during the boot process whilst the system repetitively tries to make a connection.


I attempted to get AutoFS [https://wiki.manjaro.org/index.php?title=Using_autofs_(automount)_with_NFS]to work for me. I got close but I just wasn't allowed to see the files on the NFS NAS share.


So then I found the following extremely simple & effective solution. (Wish I had of done this one first, as it would have saved me a couple of hours of a loosing battle!)
</translate>}}

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

Add the following to the beginning of the options section in your /etc/fstab, the numbers at the end are a time limit for how long it should try to make a connection before giving up & moving on:


{{File|file=/etc/fstab|content=<pre>noauto,x-systemd.automount,x-systemd.device-timeout=10</pre>}}


After I added the above to the following line in my fstab:


{{File|file=/etc/fstab|content=<pre>192.168.1.15:/media-2 /mnt/NAS-media-2 nfs noauto,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,hard,intr,noatime 0 0</pre>}}


I could boot Manjaro whilst the ReadyNAS' Cat-6 network cable was unplugged, & there was NO noticeable delay. After the system was booted, I plugged the cable in & then called the NFS share /media-2 in Worker & it read the drive & listed the contents.


After that I unplugged the drive, which had Worker (my file manager of choice) looking for it as I hadn't changed out of the the media-2 directory. When I plugged the cable back in, it took ~10 seconds or so & then Worker automatically re-listed the contents or this very large partition that has well over 2000 directories, each holding multiple files.
</translate>}}

{{SectionTemplate|1=<translate> Speed up your boot</translate>|2=
<translate>

If you have a very large /home & the boot process is held up when a scheduled fsck takes place (really not a big problem if you are using ext4), you can add the '''x-systemd.automount''' section to the options section of the line in your fstab for /home like so:


{{File|file=/etc/fstab|content=<pre>UUID=<id.number> /home noauto,x-systemd.automount,ext4 defaults 0 1</pre>}}


This will allow services that do not depend on /home to start while /home is checked by fsck. Mounting /home when it is first accessed, the kernel will buffer all file access to /home until it is ready.
</translate>}}

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

Installation Guides

2021-09-18T11:19:17Z

Bogdancovaciu:

<languages/>
__TOC__

{{SectionTemplate|
1=<translate> Overview</translate>|
2={{BoxSuccess|tip|<translate> 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>

{{BoxInfo|note|<translate> 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>}}
|
3=BigManjaroIcon.png
}}

{{SectionTemplate|
1=<translate> Manjaro Installation Guides</translate>|
2={{FlexSideContainerTemplate|
<translate>


* [https://manjaro.org/support/userguide/ Graphical Installation Guide]
: ''Including Automatic, Manual, BIOS, UEFI, and Dual-boot instructions''|


* [[Installation with Manjaro Architect]]
: ''Install a system using Manjaro Architect!''
</translate>
|1|1}}
}}

{{SectionTemplate|
1=<translate> Other 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> See Also</translate>|
* '''[[Download Manjaro]]'''
* '''[[Check a Downloaded ISO Image For Errors]]'''
* '''[[Burn an ISO File]]'''|Chmsee-icon.png}}

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

Check a Downloaded ISO Image For Errors

2021-09-18T11:17:41Z

Bogdancovaciu:

<languages/>
__TOC__

{{SectionTemplate|
1=<translate> Overview</translate>|
2=<translate>
Prior to burning your downloaded ISO image (or using it as a virtual disc in Virtualbox), it is '''strongly''' recommended that you first check that it hasn't been corrupted. The consequences of not doing so, especially if you intend on installing Manjaro as your main operating system, should be obvious, that is that a corrupted image will result in a corrupted installation.


To make the check, you must first download the appropriate ''checksum file'' from the same ''Sourceforge'' website folder as your chosen ISO image. A checksum file will have the same name as the ISO image that it is to be used with; the only difference is that it will end in either '''-sha1.sum''' or '''-sha256.sum'''. For example, the appropriate checksum files for the ''manjaro-xfce-0.8.1-x86_64.iso'' file (64 bit Manjaro release 0.8.1 with the XFCE desktop) would be:


* manjaro-xfce-0.8.1-x86_64'''-sha1.sum''', and/or
* manjaro-xfce-0.8.1-x86_64'''-sha256.sum'''</translate>|
3=BigManjaroIcon.png
}}

{{SectionTemplate|
1=<translate> SHA1 and SHA256</translate>|
2=<translate>
The 'sha' part of the checksum file name stands for <u>S</u>ecure <u>H</u>ash <u>A</u>lgorithm. This algorithm is used to generate a particular code unique to the downloaded ISO image. '''sha1''' and '''sha256''' are different versions of the algorithm that you can use to do this. Whilst sha1 is the most commonly used version, sha256 is a later and more secure version. Whichever you decide to use is entirely your choice. '''However, if you are unsure, then it is recommended to use sha256'''.


The checksum file itself is just a text document that contains a code that should match the code generated by the sha1 or sha256 algorithm. As such, if the code generated from the ISO file matches that contained in the checksum file, then the ISO is fine; otherwise, if the two codes don't match then it means that the ISO file has changed in some way, most likely due to being corrupted. You can think of it like someone using a secret password to identify who they are: if they provide the wrong password, then something is obviously amiss!


Don't worry if this all sounds a bit much, it's actually very straightforward and easy to use!</translate>
}}

{{SectionTemplate|
1=<translate> Checking in Linux</translate>|
2=<translate>

To check the integrity of your downloaded file, it will be necessary to first open the downloaded checksum file using a text editor such as ''Gedit''. Depending on whether you intend to use sha1 or sha256, ensure that you have downloaded and opened the appropriate checksum file, that is one ending in *.sha1sum or *.sha256sum respectively) as they will contain different codes. Once the checksum file has been opened and the code is visible, open up your terminal and change to the directory where your downloaded ISO is stored. For example, if your ISO file is located in the default ''Downloads'' folder, you would enter the following command:


{{UserCmd|command=cd Downloads}}


The command to then perform a checksum uses the following syntax:


[sha1sum or sha256sum] [ISO Image]


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


For example, the following command will use sha256 to generate a code from the 64 bit Manjaro XFCE 0.8.1 ISO. The code generated can then be compared to the code provided by the appropriate sha256 checksum file:


{{UserCmd|command=sha256sum manjaro-xfce-0.8.1-x86_64.iso}}


As illustrated, in this instance both codes match, thus confirming that the downloaded ISO file is correct. The following command would use sha1 to undertake exactly the same task:


{{UserCmd|command=sha1sum manjaro-xfce-0.8.1-x86_64.iso}}


When satisfied that both codes match, then it is safe to proceed to either burning the ISO to your chosen installation media, or using it immediately in Virtualbox. If the codes do not match, then it will be necessary to delete the ISO image and download it again.
</translate>
}}

{{SectionTemplate|
1=<translate> Checking in Windows</translate>|
2=<translate>

[[File: wincheck.jpg|thumb|left|375px]]


It will be necessary to download and install a checksum utility application. There are many tools which can provide sha1 and sha256 sums. One such tool is '''[https://github.com/tedsmith/quickhash Quick Hash]'''
</translate>
<br clear="all" />
}}

{{SectionTemplate|<translate> See Also</translate>|
* '''[[How-to verify GPG key of official .ISO images]]'''
* '''[[Download Manjaro]]'''
* '''[[Burn an ISO File]]'''
* '''[[Installation Guides]]'''|Chmsee-icon.png}}

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

Burn an ISO File

2021-09-18T11:14:38Z

Bogdancovaciu:

<languages/>
__TOC__
<translate>
==Overview== 
As outlined in the '''[[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. Read the forum post on [https://archived.forum.manjaro.org/t/howto-use-manjaro-to-create-a-bootable-windows-usb/92780 HowTo create a bootable Windows ISO]

===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.akeo.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.akeo.ie/]

==See Also== 
* '''[[Download Manjaro]]'''
* '''[[Check a Downloaded ISO Image For Errors]]'''
* '''[[Installation Guides]]'''
</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ISO{{#translation:}}]]

Download Manjaro

2021-09-18T11:11:29Z

Bogdancovaciu:

__TOC__
{{SectionTemplate|
1=<translate> Overview</translate>|
2=<translate> Manjaro installation images are available for download as ISO files. An ISO file is itself a literal copy of a disc image, although not in the same sense as a copy and paste duplication, rather it is a copy of the raw machine code that makes up the files and folders of that disc. This is why just copying an ISO file to a disc (or USB flashdrive) to begin installing it won't work; you'll need to use a ''disc burning application'' to translate that raw data into the files and folders. Instructions to do so for both Linux and Windows operating systems are provided below.</translate>|
3=BigManjaroIcon.png
}}

{{BoxInfo|note|<translate> There is an exception to this rule. If you intend on installing Manjaro in a virtual machine environment using '''[https://www.virtualbox.org/ Oracle's Virtualbox]''', then there will be no need to burn the image as Virtualbox will be able to read from the ISO file directly as a ''virtual disc''.</translate>}}

{{BoxInfo|note|<translate> Manjaro has no support for 32-bit systems.</translate>}}

{{SectionTemplate|<translate> Manjaro Editions</translate>|<translate> There are currently four Official Manjaro Editions: Gnome, KDE, Xfce and Architect. You can view a brief introduction at the [https://manjaro.org/get-manjaro/ Manjaro Official Webpage]</translate>

{{SubContentTemplate|<translate> Downloading an ISO image</translate>|
<translate>
On the OSDN download server, each Manjaro Edition has its own particular folder, which will contain a folder for each new ISO release. Each folder will also contain a torrent file for the ISO image, a list of the included packages, the build log file and the relevant ''checksum'' files, which can be used to check the integrity of your downloaded ISO file, to ensure that it has not been corrupted during download. A link to the guide on doing this has been provided below.


'''Stable Releases''' of Manjaro are intended to be used by the general public. As such, they will be the appropriate choice for the majority of users.


[https://osdn.net/projects/manjaro/storage/ Stable Releases]


'''Test Builds''' of Manjaro are intended to be used by developers and testers, in order to identify any bugs or issues to be addressed as their development continues towards the next stable release. '''These are not suitable nor intended for use by the general public as a main operating system'''; however, should you wish to try out a test build (preferably in a virtual machine) each current release have a look at the [https://forum.manjaro.org/tags/c/announcements/iso Forum Announcements].</translate>
|Application-x-iso.png|1}}

{{SubContentTemplate|<translate> Downloading Community Editions</translate>|
<translate>

There are also several Community releases for the most famous, or hardly known Display Environments, like Cinnamon, MATE, i3, Awesome, Deepin, Budgie, LxQt and Openbox.


You may find them at OSDN:


[https://osdn.net/projects/manjaro-community/storage/ Community]
</translate>
|Application-x-iso.png|1}}

|Start-here-manjaro.png}}

{{SectionTemplate|<translate>  See Also</translate>|
* '''[[Check a Downloaded ISO Image For Errors]]'''
* '''[[How-to verify GPG key of official .ISO images]]'''
* '''[[Burn an ISO File]]'''
* '''[[Installation Guides]]'''|Chmsee-icon.png}}

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

Vivaldi Browser

2021-09-18T11:00:31Z

Bogdancovaciu:

<languages/>
__TOC__

<translate>
=Overview= 


[https://vivaldi.com/ Vivaldi] is a chromium based browser which focuses on providing the ability to customize the browser to meet the end-users needs.


<br clear="all"/>

=Installing Vivaldi= 


Vivaldi is available from the manjaro repo.


To install the base Vivaldi you can use the command:
{{UserCmd|command=pamac install vivaldi}}


If you want to view DRM protected video content you will also need the proprietary widevine codec. This can be installed with
{{UserCmd|command=pamac build vivaldi-widevine}}


{{BoxInfo|note|If you also have Google Chrome package installed you can use the widevine plugin bundled with Chrome instead}}


Lastly, if you want to be able to play common media formats you will need the codecs.


You can install the package {{ic|vivaldi-ffmpeg-codecs}} with the command
{{UserCmd|command=pamac install vivaldi-ffmpeg-codecs}}

=Tips and Tricks= 

==Access Additional Settings== 


Vivaldi has a settings menu which offers extensive customization ability. However, not all things supported by Chromium are accessible via the menu. To access the underlying Chromium settings, put this in the address bar:
chrome://settings

==Using the Native File Dialogs on KDE/plasma== 


By default, Vivaldi will use the GTK file dialogs. If you are using plasma and would prefer native dialogs, you can install the package {{ic|kdialog}} using your favorite package manager or with the command:
{{UserCmd|command=pamac install kdialog}}

</translate>

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

Vivaldi Browser

2021-09-18T10:58:40Z

Bogdancovaciu:

<languages/>
__TOC__

<translate>
=Overview= 


[https://vivaldi.com/ Vivaldi] is a chromium based browser which focuses on providing the ability to customize the browser to meet the end-users needs.


<br clear="all"/>

=Installing Vivaldi= 


Vivaldi is available from the manjaro repo.


To install the base Vivaldi you can use the command:
{{UserCmd|command=pamac install vivaldi}}


If you want to view DRM protected video content you will also need the proprietary widevine codec. This can be installed with
{{UserCmd|command=pamac build vivaldi-widevine}}


{{BoxInfo|note|If you also have Google Chrome package installed you can use the widevine plugin bundled with Chrome instead}}


Lastly, if you want to be able to play common media formats you will need the codecs.


You can install the package {{ic|vivaldi-ffmpeg-codecs}} with the command
{{UserCmd|command=pamac install vivaldi-ffmpeg-codecs}}

=Tips and Tricks= 

==Access Additional Settings== 


Vivaldi has a settings menu which offers extensive customization ability. However, not all things supported by Chromium are accessible via the menu. To access the underlying Chromium settings, put this in the address bar:
chrome://settings

==Using the Native File Dialogs on KDE/plasma== 


By default, Vivaldi will use the GTK file dialogs. If you are using plasma and would prefer native dialogs, you can install the package {{ic|kdialog}} using your favorite package manager or with the command:
pamac install kdialog

</translate>

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

UEFI - Install Guide

2021-09-04T19:43:07Z

Bogdancovaciu: /* Dual booting with Windows */

= Introduction =

UEFI is the commonly agreed on name for both the EFI & UEFI
standards which merged. It does not include the old EFI v1,
or Apple's own non-standard version of EFI.

= Target computer =

The following guide aims to install Manjaro on a machine with UEFI enabled, Secure boot disabled, and using GUID Partition Table (GPT) disk(s).

For multi-boot, the EFI system partition which is already present (or will be created), can usually be shared amongst multiple Linux installs.

= The steps =

== Common ==

* 1. Download your preferred Manjaro version (XFCE, Openbox, Cinnamon, KDE, ...), must be 64-bits.

* 2. Burn the .iso to USB or DVD. See [[Burn_an_ISO_File]] for more details.

* 3. Check your BIOS, UEFI must be ON and Secure boot OFF.

* 4. Boot with your USB or DVD & use the rEFInd - Main Menu... to choose which GPU drivers you want to have installed, the open-source or proprietary:

* Boot Manjaro Linux ... (default) -
This chooses the ''open-source - free'' GPU drivers.
* Boot Manjaro Linux ... (nonfree) -
This option chooses the '''proprietary''' GPU drivers
from Nvidia or ATI.

=== Graphical Installer ===

{{BoxSuccess|tip|Since Manjaro-0.8.9, UEFI support is also provided in the Graphical Installer, so one can simply try the Graphical installer and skip the instructions given below for the CLI installer.}}

To use the Graphical Installer select the '''Install Manjaro''' option from the Manjaro Welcome screen or from the desktop.

For the ESP (EFI system partition) which will store the EFI Grub binary, a 512mb partition of type fat32 can be created in the partitioning step, and mounted to ''/boot/efi''

If you are dual booting then an EFI partition from a previous install can also be used.

=== CLI installer ===

* 5-b. Open terminal & enter:

{{UserCmd|command=sudo setup}}

* 6. Now, we are in the CLI Installer.

* 7. ''Choose 1.'' Set date and time - an easy intuitive configuration.

==== Disk preparation ====

{{BoxSuccess|tip|If your hard disk is already partitioned the way you want, then this step can be skipped.}}

* When you ''click 2.'' Partition Hard Drives,
you get a dialog saying "Do you want to use GUID
Partition Table (GPT)", '''choose Yes'''.
* Partition your disk(s) as you want (Instructions on
manually partitioning are beyond the scope of this
guide, some deatils are available [[Cfdisk_Basic_Partitioning_Scenarios|here]]).
* ''Important Step:'' Create a 50~250MB EFI Partition,
mine is 100MB (code: ef00)

==== Setting filesystem mount points ====

* After the partitioning is done, go to ''4. Set Filesystem''
''Mountpoints.''
* '''Important Step:''' Format the EFI Partition you
created as '''VFAT''' and mount on /boot/efi

{{BoxInfo|note|If you are re-using your EFI partition (that was created by Windows previously (or any other OS), then there is no need to format. Formatting will wipe the previous bootloader. Only mounting the EFI partition as '''/boot/efi''' is required in that case.}}

==== Installation ====

* 9. ''Choose 3.'' Install system and wait...

* 10. Now, go to ''4. Configure System'' and configure it the way you like (username, password, mirrorlist, system-name, ...).

* 11. When you are done, go to ''5. Install bootloader.'' Choose EFI_x86_64 > GRUB (2) UEFI x86_64, ''DON'T select BIOS GRUB.''

* 11.1 It will ask to format the EFI Partition you created earlier as FAT32, yes can be chosen.
{{BoxInfo|note|Formatting not required if reusing previous EFI partition.}}

* 12. If it gives a error in the final stages saying "efivars kernel module was not properly loaded", don't worry, the system will work fine!

* 13. If the installer asks you about copying grub/efi files to another folder in order to maintain compatibility in some systems, choose Yes.

* 14. ''Click 6.'' Quit

* 15. Shutdown, remove the DVD or USB, and boot. Your system should appear now!

= Switching from BIOS to UEFI =

1) You need to create an ''ESP (EFI System Partition)''.

It is a FAT32 partition which has the .efi files for booting, which you can create using gparted or gdisk. (Size at least 200-300 MiB.) Ensure the flags `boot` and `esp` are set on this partition.

You should also install/check whether following packages are present-

1. efibootmgr
2. dosfstools
3. grub

[[Pacman_Overview | (How to install packages)]]

2) Create the ''/boot/efi'' directory
{{UserCmd|command=sudo mkdir /boot/efi}}

3.) Mount the EFI partition as ''/boot/efi''
sudo mount /dev/sdXY /boot/efi
X = Alphabet of the drive = a,b,c ...
Y = Partition number of the EFI partition = 1,2,3,4...

Example - ''/dev/sda4''

4.) Install Grub according to UEFI
{{UserCmd|command=sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck}}

5.) Update Grub configuration file.
{{UserCmd|command=sudo update-grub}}

{{BoxInfo|note|If you get an error like:}}
path '/boot/grub' is not readable by Grub on boot. Installation is impossible. Aborting

Then you will need to [https://wiki.archlinux.org/index.php/Change_Root chroot] as described [[Restore_the_GRUB_Bootloader#Identify_and_Prepare_the_Installed_Partition.28s.29|here]], and then perform Step 5 again.

{{BoxInfo|note|If you get the following error:}}

EFI variables are not supported on this system.

then you could load the '''efivarfs''' module :
{{UserCmd|command=sudo modprobe efivarfs}}

'''See also'''

[[Restore the GRUB Bootloader]]

[https://forum.manjaro.org/t/using-livecd-v17-0-1-as-grub-to-boot-os-with-broken-bootloader/24916]

= Dual booting with Windows =

{{BoxSuccess|tip|Some manufactures EFI implementations cause GRUB not to be showed in the Boot Menu, or even if its there it can't be made default.}}

'''In such cases ''[http://www.rodsbooks.com/refind/index.html rEFInd]''''' can be used.

[[File:Refind.png]]

There are two ways to install rEFInd-

1.Install rEFInd from its website [http://www.rodsbooks.com/refind/installing.html] (detailed) or '''install using pacman'''''(preferred)''-
{{UserCmd|command=sudo pacman -S refind}}

Files will be present in /usr/share/refind .

2.Or using the instructions on the rEFInd website: [http://www.rodsbooks.com/refind/installing.html]

== Instructions ==

The '''refind-install''' command can be used to automatically install rEFInd (the EFI partition may need to be mounted for this to work). See the [https://wiki.archlinux.org/index.php/REFInd#Installation Arch wiki] for more details.

=== Manual install ===

Inside the refind folder ('''/usr/share/refind'''), copy the files and folders to-

/boot/efi/EFI/Boot/

{{BoxInfo|note|My ESP (EFI System Partition) is mounted at '''/boot/efi'''.}}

You need to copy these files to the Boot folder on your EFI partition, and the Boot folder itself will be present inside the EFI folder on the EFI Partition, so take note of it.

You can check which partition is your ESP using Gparted; find which partition is formatted as fat32 and has size around 200mb-1gb.

Can mount it as /boot/efi by

{{UserCmd|command=sudo mount /dev/sdXN /boot/efi}}
X=a,b,c...
N=1,2,3...
These depend on which partition your ESP is present which can be obtained via Gparted as mentioned earlier.

Now inside the /boot/efi/EFI/Boot/ folder, there should already be a file present-
bootx64.efi

You can '''''rename''''' it as ''windows.bootx64.efi''
Then you can rename ''refind_x64.efi'' to ''bootx64.efi''

The bootx64.efi files boot by default, hence rEFInd should now boot by default, and detect grubx64.efi(linux-manjaro) and efibootmgfw.efi (windows) automatically.

{{BoxInfo|note|A folder Manjaro (name could be some other also) containing the file ''grubx64.efi'' should also be present in '''/boot/efi/EFI/''' folder, which should contain the ''grubx64.efi'' file which will be used by rEFInd to boot Grub.}}

So it could be like-
/boot/efi/EFI/Manjaro/grubx64.efi

rEFInd would use this file for booting Manjaro.

If you do not have this file or folder, try-

{{UserCmd|command=sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Manjaro --recheck}}

to create '''/boot/efi/EFI/Manjaro/grubx64.efi'''

See also- [http://www.rodsbooks.com/refind/installing.html#naming http://www.rodsbooks.com/refind/installing.html#naming]

=== An alternative: chainloading via GRUB ===

An entry can be added to
{{File|file=/etc/grub.d/40_custom|
content=
<pre>
menuentry 'Windows8 (UEFI)' {
insmod ntfs
set root=(hd0,gpt4)
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
boot
}
</pre>
}}
In this case (hd0,4) or /dev/sda4 is the EFI System partition where the Windows bootloader is present.

After adding the above entry, running '''sudo update-grub''' updates the GRUB configuration file so that an entry named '''Windows8 (UEFI)''' is added to the GRUB boot menu.

Related Forum thread: [https://forum.manjaro.org/t/detecting-efi-files-and-booting-them-from-grub/38083]

The chainloading will fail on some hardware (Lenovo Ideapad 110) with the "invalid signature" message - the Refind method will still work.

= Extras =

== Using Rufus on Windows to create installation media ==

[http://rufus.akeo.ie/ Rufus] users can use the following settings:

* Click on the DVD icon and load your .iso
* In the menu left of the DVD icon, select DD Image
* Device: "choose your USB" (Attention: choose correctly,
the device selected here will be formatted!!!)
* Partition scheme: GPT partition scheme for UEFI computer
* File system: FAT32
* Cluster size: "Don't modify"
* Volume label: "Don't modify"
* Click Start, and you are done (takes 2~5 min to complete).

= Feedback =

Questions, suggestions, critics? Please post here: [http://forum.manjaro.org/]

= External Links =

Youtube video: https://www.youtube.com/watch?v=36tDZIXn3-k

[[Category:Contents Page]]

UEFI - Install Guide

2021-09-04T19:41:28Z

Bogdancovaciu: /* CLI installer */

= Introduction =

UEFI is the commonly agreed on name for both the EFI & UEFI
standards which merged. It does not include the old EFI v1,
or Apple's own non-standard version of EFI.

= Target computer =

The following guide aims to install Manjaro on a machine with UEFI enabled, Secure boot disabled, and using GUID Partition Table (GPT) disk(s).

For multi-boot, the EFI system partition which is already present (or will be created), can usually be shared amongst multiple Linux installs.

= The steps =

== Common ==

* 1. Download your preferred Manjaro version (XFCE, Openbox, Cinnamon, KDE, ...), must be 64-bits.

* 2. Burn the .iso to USB or DVD. See [[Burn_an_ISO_File]] for more details.

* 3. Check your BIOS, UEFI must be ON and Secure boot OFF.

* 4. Boot with your USB or DVD & use the rEFInd - Main Menu... to choose which GPU drivers you want to have installed, the open-source or proprietary:

* Boot Manjaro Linux ... (default) -
This chooses the ''open-source - free'' GPU drivers.
* Boot Manjaro Linux ... (nonfree) -
This option chooses the '''proprietary''' GPU drivers
from Nvidia or ATI.

=== Graphical Installer ===

{{BoxSuccess|tip|Since Manjaro-0.8.9, UEFI support is also provided in the Graphical Installer, so one can simply try the Graphical installer and skip the instructions given below for the CLI installer.}}

To use the Graphical Installer select the '''Install Manjaro''' option from the Manjaro Welcome screen or from the desktop.

For the ESP (EFI system partition) which will store the EFI Grub binary, a 512mb partition of type fat32 can be created in the partitioning step, and mounted to ''/boot/efi''

If you are dual booting then an EFI partition from a previous install can also be used.

=== CLI installer ===

* 5-b. Open terminal & enter:

{{UserCmd|command=sudo setup}}

* 6. Now, we are in the CLI Installer.

* 7. ''Choose 1.'' Set date and time - an easy intuitive configuration.

==== Disk preparation ====

{{BoxSuccess|tip|If your hard disk is already partitioned the way you want, then this step can be skipped.}}

* When you ''click 2.'' Partition Hard Drives,
you get a dialog saying "Do you want to use GUID
Partition Table (GPT)", '''choose Yes'''.
* Partition your disk(s) as you want (Instructions on
manually partitioning are beyond the scope of this
guide, some deatils are available [[Cfdisk_Basic_Partitioning_Scenarios|here]]).
* ''Important Step:'' Create a 50~250MB EFI Partition,
mine is 100MB (code: ef00)

==== Setting filesystem mount points ====

* After the partitioning is done, go to ''4. Set Filesystem''
''Mountpoints.''
* '''Important Step:''' Format the EFI Partition you
created as '''VFAT''' and mount on /boot/efi

{{BoxInfo|note|If you are re-using your EFI partition (that was created by Windows previously (or any other OS), then there is no need to format. Formatting will wipe the previous bootloader. Only mounting the EFI partition as '''/boot/efi''' is required in that case.}}

==== Installation ====

* 9. ''Choose 3.'' Install system and wait...

* 10. Now, go to ''4. Configure System'' and configure it the way you like (username, password, mirrorlist, system-name, ...).

* 11. When you are done, go to ''5. Install bootloader.'' Choose EFI_x86_64 > GRUB (2) UEFI x86_64, ''DON'T select BIOS GRUB.''

* 11.1 It will ask to format the EFI Partition you created earlier as FAT32, yes can be chosen.
{{BoxInfo|note|Formatting not required if reusing previous EFI partition.}}

* 12. If it gives a error in the final stages saying "efivars kernel module was not properly loaded", don't worry, the system will work fine!

* 13. If the installer asks you about copying grub/efi files to another folder in order to maintain compatibility in some systems, choose Yes.

* 14. ''Click 6.'' Quit

* 15. Shutdown, remove the DVD or USB, and boot. Your system should appear now!

= Switching from BIOS to UEFI =

1) You need to create an ''ESP (EFI System Partition)''.

It is a FAT32 partition which has the .efi files for booting, which you can create using gparted or gdisk. (Size at least 200-300 MiB.) Ensure the flags `boot` and `esp` are set on this partition.

You should also install/check whether following packages are present-

1. efibootmgr
2. dosfstools
3. grub

[[Pacman_Overview | (How to install packages)]]

2) Create the ''/boot/efi'' directory
{{UserCmd|command=sudo mkdir /boot/efi}}

3.) Mount the EFI partition as ''/boot/efi''
sudo mount /dev/sdXY /boot/efi
X = Alphabet of the drive = a,b,c ...
Y = Partition number of the EFI partition = 1,2,3,4...

Example - ''/dev/sda4''

4.) Install Grub according to UEFI
{{UserCmd|command=sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck}}

5.) Update Grub configuration file.
{{UserCmd|command=sudo update-grub}}

{{BoxInfo|note|If you get an error like:}}
path '/boot/grub' is not readable by Grub on boot. Installation is impossible. Aborting

Then you will need to [https://wiki.archlinux.org/index.php/Change_Root chroot] as described [[Restore_the_GRUB_Bootloader#Identify_and_Prepare_the_Installed_Partition.28s.29|here]], and then perform Step 5 again.

{{BoxInfo|note|If you get the following error:}}

EFI variables are not supported on this system.

then you could load the '''efivarfs''' module :
{{UserCmd|command=sudo modprobe efivarfs}}

'''See also'''

[[Restore the GRUB Bootloader]]

[https://forum.manjaro.org/t/using-livecd-v17-0-1-as-grub-to-boot-os-with-broken-bootloader/24916]

= Dual booting with Windows =

{{BoxSuccess|tip|Some manufactures EFI implementations cause GRUB not to be showed in the Boot Menu, or even if its there it can't be made default.}}

'''In such cases ''[http://www.rodsbooks.com/refind/index.html rEFInd]''''' can be used.

[[File:Refind.png]]

There are two ways to install rEFInd-

1.Install rEFInd from its website [http://www.rodsbooks.com/refind/installing.html] (detailed) or '''install using pacman'''''(preferred)''-
sudo pacman -S refind

Files will be present in /usr/share/refind .

2.Or using the instructions on the rEFInd website: [http://www.rodsbooks.com/refind/installing.html]

== Instructions ==

The '''refind-install''' command can be used to automatically install rEFInd (the EFI partition may need to be mounted for this to work). See the [https://wiki.archlinux.org/index.php/REFInd#Installation Arch wiki] for more details.

=== Manual install ===

Inside the refind folder ('''/usr/share/refind'''), copy the files and folders to-

/boot/efi/EFI/Boot/

{{BoxInfo|note|My ESP (EFI System Partition) is mounted at '''/boot/efi'''.}}

You need to copy these files to the Boot folder on your EFI partition, and the Boot folder itself will be present inside the EFI folder on the EFI Partition, so take note of it.

You can check which partition is your ESP using Gparted; find which partition is formatted as fat32 and has size around 200mb-1gb.

Can mount it as /boot/efi by

{{UserCmd|command=sudo mount /dev/sdXN /boot/efi}}
X=a,b,c...
N=1,2,3...
These depend on which partition your ESP is present which can be obtained via Gparted as mentioned earlier.

Now inside the /boot/efi/EFI/Boot/ folder, there should already be a file present-
bootx64.efi

You can '''''rename''''' it as ''windows.bootx64.efi''
Then you can rename ''refind_x64.efi'' to ''bootx64.efi''

The bootx64.efi files boot by default, hence rEFInd should now boot by default, and detect grubx64.efi(linux-manjaro) and efibootmgfw.efi (windows) automatically.

{{BoxInfo|note|A folder Manjaro (name could be some other also) containing the file ''grubx64.efi'' should also be present in '''/boot/efi/EFI/''' folder, which should contain the ''grubx64.efi'' file which will be used by rEFInd to boot Grub.}}

So it could be like-
/boot/efi/EFI/Manjaro/grubx64.efi

rEFInd would use this file for booting Manjaro.

If you do not have this file or folder, try-

{{UserCmd|command=sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Manjaro --recheck}}

to create '''/boot/efi/EFI/Manjaro/grubx64.efi'''

See also- [http://www.rodsbooks.com/refind/installing.html#naming http://www.rodsbooks.com/refind/installing.html#naming]

=== An alternative: chainloading via GRUB ===

An entry can be added to
{{File|file=/etc/grub.d/40_custom|
content=
<pre>
menuentry 'Windows8 (UEFI)' {
insmod ntfs
set root=(hd0,gpt4)
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
boot
}
</pre>
}}
In this case (hd0,4) or /dev/sda4 is the EFI System partition where the Windows bootloader is present.

After adding the above entry, running '''sudo update-grub''' updates the GRUB configuration file so that an entry named '''Windows8 (UEFI)''' is added to the GRUB boot menu.

Related Forum thread: [https://forum.manjaro.org/t/detecting-efi-files-and-booting-them-from-grub/38083]

The chainloading will fail on some hardware (Lenovo Ideapad 110) with the "invalid signature" message - the Refind method will still work.

= Extras =

== Using Rufus on Windows to create installation media ==

[http://rufus.akeo.ie/ Rufus] users can use the following settings:

* Click on the DVD icon and load your .iso
* In the menu left of the DVD icon, select DD Image
* Device: "choose your USB" (Attention: choose correctly,
the device selected here will be formatted!!!)
* Partition scheme: GPT partition scheme for UEFI computer
* File system: FAT32
* Cluster size: "Don't modify"
* Volume label: "Don't modify"
* Click Start, and you are done (takes 2~5 min to complete).

= Feedback =

Questions, suggestions, critics? Please post here: [http://forum.manjaro.org/]

= External Links =

Youtube video: https://www.youtube.com/watch?v=36tDZIXn3-k

[[Category:Contents Page]]

UEFI - Install Guide

2021-09-04T19:40:31Z

Bogdancovaciu: /* Switching from BIOS to UEFI */

= Introduction =

UEFI is the commonly agreed on name for both the EFI & UEFI
standards which merged. It does not include the old EFI v1,
or Apple's own non-standard version of EFI.

= Target computer =

The following guide aims to install Manjaro on a machine with UEFI enabled, Secure boot disabled, and using GUID Partition Table (GPT) disk(s).

For multi-boot, the EFI system partition which is already present (or will be created), can usually be shared amongst multiple Linux installs.

= The steps =

== Common ==

* 1. Download your preferred Manjaro version (XFCE, Openbox, Cinnamon, KDE, ...), must be 64-bits.

* 2. Burn the .iso to USB or DVD. See [[Burn_an_ISO_File]] for more details.

* 3. Check your BIOS, UEFI must be ON and Secure boot OFF.

* 4. Boot with your USB or DVD & use the rEFInd - Main Menu... to choose which GPU drivers you want to have installed, the open-source or proprietary:

* Boot Manjaro Linux ... (default) -
This chooses the ''open-source - free'' GPU drivers.
* Boot Manjaro Linux ... (nonfree) -
This option chooses the '''proprietary''' GPU drivers
from Nvidia or ATI.

=== Graphical Installer ===

{{BoxSuccess|tip|Since Manjaro-0.8.9, UEFI support is also provided in the Graphical Installer, so one can simply try the Graphical installer and skip the instructions given below for the CLI installer.}}

To use the Graphical Installer select the '''Install Manjaro''' option from the Manjaro Welcome screen or from the desktop.

For the ESP (EFI system partition) which will store the EFI Grub binary, a 512mb partition of type fat32 can be created in the partitioning step, and mounted to ''/boot/efi''

If you are dual booting then an EFI partition from a previous install can also be used.

=== CLI installer ===

* 5-b. Open terminal & enter:

$ sudo setup

* 6. Now, we are in the CLI Installer.

* 7. ''Choose 1.'' Set date and time - an easy intuitive configuration.

==== Disk preparation ====

{{BoxSuccess|tip|If your hard disk is already partitioned the way you want, then this step can be skipped.}}

* When you ''click 2.'' Partition Hard Drives,
you get a dialog saying "Do you want to use GUID
Partition Table (GPT)", '''choose Yes'''.
* Partition your disk(s) as you want (Instructions on
manually partitioning are beyond the scope of this
guide, some deatils are available [[Cfdisk_Basic_Partitioning_Scenarios|here]]).
* ''Important Step:'' Create a 50~250MB EFI Partition,
mine is 100MB (code: ef00)

==== Setting filesystem mount points ====

* After the partitioning is done, go to ''4. Set Filesystem''
''Mountpoints.''
* '''Important Step:''' Format the EFI Partition you
created as '''VFAT''' and mount on /boot/efi

{{BoxInfo|note|If you are re-using your EFI partition (that was created by Windows previously (or any other OS), then there is no need to format. Formatting will wipe the previous bootloader. Only mounting the EFI partition as '''/boot/efi''' is required in that case.}}

==== Installation ====

* 9. ''Choose 3.'' Install system and wait...

* 10. Now, go to ''4. Configure System'' and configure it the way you like (username, password, mirrorlist, system-name, ...).

* 11. When you are done, go to ''5. Install bootloader.'' Choose EFI_x86_64 > GRUB (2) UEFI x86_64, ''DON'T select BIOS GRUB.''

* 11.1 It will ask to format the EFI Partition you created earlier as FAT32, yes can be chosen.
{{BoxInfo|note|Formatting not required if reusing previous EFI partition.}}

* 12. If it gives a error in the final stages saying "efivars kernel module was not properly loaded", don't worry, the system will work fine!

* 13. If the installer asks you about copying grub/efi files to another folder in order to maintain compatibility in some systems, choose Yes.

* 14. ''Click 6.'' Quit

* 15. Shutdown, remove the DVD or USB, and boot. Your system should appear now!

= Switching from BIOS to UEFI =

1) You need to create an ''ESP (EFI System Partition)''.

It is a FAT32 partition which has the .efi files for booting, which you can create using gparted or gdisk. (Size at least 200-300 MiB.) Ensure the flags `boot` and `esp` are set on this partition.

You should also install/check whether following packages are present-

1. efibootmgr
2. dosfstools
3. grub

[[Pacman_Overview | (How to install packages)]]

2) Create the ''/boot/efi'' directory
{{UserCmd|command=sudo mkdir /boot/efi}}

3.) Mount the EFI partition as ''/boot/efi''
sudo mount /dev/sdXY /boot/efi
X = Alphabet of the drive = a,b,c ...
Y = Partition number of the EFI partition = 1,2,3,4...

Example - ''/dev/sda4''

4.) Install Grub according to UEFI
{{UserCmd|command=sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck}}

5.) Update Grub configuration file.
{{UserCmd|command=sudo update-grub}}

{{BoxInfo|note|If you get an error like:}}
path '/boot/grub' is not readable by Grub on boot. Installation is impossible. Aborting

Then you will need to [https://wiki.archlinux.org/index.php/Change_Root chroot] as described [[Restore_the_GRUB_Bootloader#Identify_and_Prepare_the_Installed_Partition.28s.29|here]], and then perform Step 5 again.

{{BoxInfo|note|If you get the following error:}}

EFI variables are not supported on this system.

then you could load the '''efivarfs''' module :
{{UserCmd|command=sudo modprobe efivarfs}}

'''See also'''

[[Restore the GRUB Bootloader]]

[https://forum.manjaro.org/t/using-livecd-v17-0-1-as-grub-to-boot-os-with-broken-bootloader/24916]

= Dual booting with Windows =

{{BoxSuccess|tip|Some manufactures EFI implementations cause GRUB not to be showed in the Boot Menu, or even if its there it can't be made default.}}

'''In such cases ''[http://www.rodsbooks.com/refind/index.html rEFInd]''''' can be used.

[[File:Refind.png]]

There are two ways to install rEFInd-

1.Install rEFInd from its website [http://www.rodsbooks.com/refind/installing.html] (detailed) or '''install using pacman'''''(preferred)''-
sudo pacman -S refind

Files will be present in /usr/share/refind .

2.Or using the instructions on the rEFInd website: [http://www.rodsbooks.com/refind/installing.html]

== Instructions ==

The '''refind-install''' command can be used to automatically install rEFInd (the EFI partition may need to be mounted for this to work). See the [https://wiki.archlinux.org/index.php/REFInd#Installation Arch wiki] for more details.

=== Manual install ===

Inside the refind folder ('''/usr/share/refind'''), copy the files and folders to-

/boot/efi/EFI/Boot/

{{BoxInfo|note|My ESP (EFI System Partition) is mounted at '''/boot/efi'''.}}

You need to copy these files to the Boot folder on your EFI partition, and the Boot folder itself will be present inside the EFI folder on the EFI Partition, so take note of it.

You can check which partition is your ESP using Gparted; find which partition is formatted as fat32 and has size around 200mb-1gb.

Can mount it as /boot/efi by

{{UserCmd|command=sudo mount /dev/sdXN /boot/efi}}
X=a,b,c...
N=1,2,3...
These depend on which partition your ESP is present which can be obtained via Gparted as mentioned earlier.

Now inside the /boot/efi/EFI/Boot/ folder, there should already be a file present-
bootx64.efi

You can '''''rename''''' it as ''windows.bootx64.efi''
Then you can rename ''refind_x64.efi'' to ''bootx64.efi''

The bootx64.efi files boot by default, hence rEFInd should now boot by default, and detect grubx64.efi(linux-manjaro) and efibootmgfw.efi (windows) automatically.

{{BoxInfo|note|A folder Manjaro (name could be some other also) containing the file ''grubx64.efi'' should also be present in '''/boot/efi/EFI/''' folder, which should contain the ''grubx64.efi'' file which will be used by rEFInd to boot Grub.}}

So it could be like-
/boot/efi/EFI/Manjaro/grubx64.efi

rEFInd would use this file for booting Manjaro.

If you do not have this file or folder, try-

{{UserCmd|command=sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Manjaro --recheck}}

to create '''/boot/efi/EFI/Manjaro/grubx64.efi'''

See also- [http://www.rodsbooks.com/refind/installing.html#naming http://www.rodsbooks.com/refind/installing.html#naming]

=== An alternative: chainloading via GRUB ===

An entry can be added to
{{File|file=/etc/grub.d/40_custom|
content=
<pre>
menuentry 'Windows8 (UEFI)' {
insmod ntfs
set root=(hd0,gpt4)
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
boot
}
</pre>
}}
In this case (hd0,4) or /dev/sda4 is the EFI System partition where the Windows bootloader is present.

After adding the above entry, running '''sudo update-grub''' updates the GRUB configuration file so that an entry named '''Windows8 (UEFI)''' is added to the GRUB boot menu.

Related Forum thread: [https://forum.manjaro.org/t/detecting-efi-files-and-booting-them-from-grub/38083]

The chainloading will fail on some hardware (Lenovo Ideapad 110) with the "invalid signature" message - the Refind method will still work.

= Extras =

== Using Rufus on Windows to create installation media ==

[http://rufus.akeo.ie/ Rufus] users can use the following settings:

* Click on the DVD icon and load your .iso
* In the menu left of the DVD icon, select DD Image
* Device: "choose your USB" (Attention: choose correctly,
the device selected here will be formatted!!!)
* Partition scheme: GPT partition scheme for UEFI computer
* File system: FAT32
* Cluster size: "Don't modify"
* Volume label: "Don't modify"
* Click Start, and you are done (takes 2~5 min to complete).

= Feedback =

Questions, suggestions, critics? Please post here: [http://forum.manjaro.org/]

= External Links =

Youtube video: https://www.youtube.com/watch?v=36tDZIXn3-k

[[Category:Contents Page]]

UEFI - Install Guide

2021-09-04T19:36:48Z

Bogdancovaciu: /* Manual install */

= Introduction =

UEFI is the commonly agreed on name for both the EFI & UEFI
standards which merged. It does not include the old EFI v1,
or Apple's own non-standard version of EFI.

= Target computer =

The following guide aims to install Manjaro on a machine with UEFI enabled, Secure boot disabled, and using GUID Partition Table (GPT) disk(s).

For multi-boot, the EFI system partition which is already present (or will be created), can usually be shared amongst multiple Linux installs.

= The steps =

== Common ==

* 1. Download your preferred Manjaro version (XFCE, Openbox, Cinnamon, KDE, ...), must be 64-bits.

* 2. Burn the .iso to USB or DVD. See [[Burn_an_ISO_File]] for more details.

* 3. Check your BIOS, UEFI must be ON and Secure boot OFF.

* 4. Boot with your USB or DVD & use the rEFInd - Main Menu... to choose which GPU drivers you want to have installed, the open-source or proprietary:

* Boot Manjaro Linux ... (default) -
This chooses the ''open-source - free'' GPU drivers.
* Boot Manjaro Linux ... (nonfree) -
This option chooses the '''proprietary''' GPU drivers
from Nvidia or ATI.

=== Graphical Installer ===

{{BoxSuccess|tip|Since Manjaro-0.8.9, UEFI support is also provided in the Graphical Installer, so one can simply try the Graphical installer and skip the instructions given below for the CLI installer.}}

To use the Graphical Installer select the '''Install Manjaro''' option from the Manjaro Welcome screen or from the desktop.

For the ESP (EFI system partition) which will store the EFI Grub binary, a 512mb partition of type fat32 can be created in the partitioning step, and mounted to ''/boot/efi''

If you are dual booting then an EFI partition from a previous install can also be used.

=== CLI installer ===

* 5-b. Open terminal & enter:

$ sudo setup

* 6. Now, we are in the CLI Installer.

* 7. ''Choose 1.'' Set date and time - an easy intuitive configuration.

==== Disk preparation ====

{{BoxSuccess|tip|If your hard disk is already partitioned the way you want, then this step can be skipped.}}

* When you ''click 2.'' Partition Hard Drives,
you get a dialog saying "Do you want to use GUID
Partition Table (GPT)", '''choose Yes'''.
* Partition your disk(s) as you want (Instructions on
manually partitioning are beyond the scope of this
guide, some deatils are available [[Cfdisk_Basic_Partitioning_Scenarios|here]]).
* ''Important Step:'' Create a 50~250MB EFI Partition,
mine is 100MB (code: ef00)

==== Setting filesystem mount points ====

* After the partitioning is done, go to ''4. Set Filesystem''
''Mountpoints.''
* '''Important Step:''' Format the EFI Partition you
created as '''VFAT''' and mount on /boot/efi

{{BoxInfo|note|If you are re-using your EFI partition (that was created by Windows previously (or any other OS), then there is no need to format. Formatting will wipe the previous bootloader. Only mounting the EFI partition as '''/boot/efi''' is required in that case.}}

==== Installation ====

* 9. ''Choose 3.'' Install system and wait...

* 10. Now, go to ''4. Configure System'' and configure it the way you like (username, password, mirrorlist, system-name, ...).

* 11. When you are done, go to ''5. Install bootloader.'' Choose EFI_x86_64 > GRUB (2) UEFI x86_64, ''DON'T select BIOS GRUB.''

* 11.1 It will ask to format the EFI Partition you created earlier as FAT32, yes can be chosen.
{{BoxInfo|note|Formatting not required if reusing previous EFI partition.}}

* 12. If it gives a error in the final stages saying "efivars kernel module was not properly loaded", don't worry, the system will work fine!

* 13. If the installer asks you about copying grub/efi files to another folder in order to maintain compatibility in some systems, choose Yes.

* 14. ''Click 6.'' Quit

* 15. Shutdown, remove the DVD or USB, and boot. Your system should appear now!

= Switching from BIOS to UEFI =

1) You need to create an ''ESP (EFI System Partition)''.

It is a FAT32 partition which has the .efi files for booting, which you can create using gparted or gdisk. (Size at least 200-300 MiB.) Ensure the flags `boot` and `esp` are set on this partition.

You should also install/check whether following packages are present-

1. efibootmgr
2. dosfstools
3. grub

[[Pacman_Overview | (How to install packages)]]

2) Create the ''/boot/efi'' directory
sudo mkdir /boot/efi

3.) Mount the EFI partition as ''/boot/efi''
sudo mount /dev/sdXY /boot/efi
X = Alphabet of the drive = a,b,c ...
Y = Partition number of the EFI partition = 1,2,3,4...

Example - ''/dev/sda4''

4.) Install Grub according to UEFI
sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck

5.) Update Grub configuration file.
sudo update-grub

'''Note-'''
If you get an error like
path '/boot/grub' is not readable by Grub on boot. Installation is impossible. Aborting

Then you will need to [https://wiki.archlinux.org/index.php/Change_Root chroot] as described [[Restore_the_GRUB_Bootloader#Identify_and_Prepare_the_Installed_Partition.28s.29|here]], and then perform Step 5 again.

If you get the following error :

EFI variables are not supported on this system.

then you could load the '''efivarfs''' module :
sudo modprobe efivarfs

'''See also'''

[[Restore the GRUB Bootloader]]

[https://forum.manjaro.org/t/using-livecd-v17-0-1-as-grub-to-boot-os-with-broken-bootloader/24916]

= Dual booting with Windows =

{{BoxSuccess|tip|Some manufactures EFI implementations cause GRUB not to be showed in the Boot Menu, or even if its there it can't be made default.}}

'''In such cases ''[http://www.rodsbooks.com/refind/index.html rEFInd]''''' can be used.

[[File:Refind.png]]

There are two ways to install rEFInd-

1.Install rEFInd from its website [http://www.rodsbooks.com/refind/installing.html] (detailed) or '''install using pacman'''''(preferred)''-
sudo pacman -S refind

Files will be present in /usr/share/refind .

2.Or using the instructions on the rEFInd website: [http://www.rodsbooks.com/refind/installing.html]

== Instructions ==

The '''refind-install''' command can be used to automatically install rEFInd (the EFI partition may need to be mounted for this to work). See the [https://wiki.archlinux.org/index.php/REFInd#Installation Arch wiki] for more details.

=== Manual install ===

Inside the refind folder ('''/usr/share/refind'''), copy the files and folders to-

/boot/efi/EFI/Boot/

{{BoxInfo|note|My ESP (EFI System Partition) is mounted at '''/boot/efi'''.}}

You need to copy these files to the Boot folder on your EFI partition, and the Boot folder itself will be present inside the EFI folder on the EFI Partition, so take note of it.

You can check which partition is your ESP using Gparted; find which partition is formatted as fat32 and has size around 200mb-1gb.

Can mount it as /boot/efi by

{{UserCmd|command=sudo mount /dev/sdXN /boot/efi}}
X=a,b,c...
N=1,2,3...
These depend on which partition your ESP is present which can be obtained via Gparted as mentioned earlier.

Now inside the /boot/efi/EFI/Boot/ folder, there should already be a file present-
bootx64.efi

You can '''''rename''''' it as ''windows.bootx64.efi''
Then you can rename ''refind_x64.efi'' to ''bootx64.efi''

The bootx64.efi files boot by default, hence rEFInd should now boot by default, and detect grubx64.efi(linux-manjaro) and efibootmgfw.efi (windows) automatically.

{{BoxInfo|note|A folder Manjaro (name could be some other also) containing the file ''grubx64.efi'' should also be present in '''/boot/efi/EFI/''' folder, which should contain the ''grubx64.efi'' file which will be used by rEFInd to boot Grub.}}

So it could be like-
/boot/efi/EFI/Manjaro/grubx64.efi

rEFInd would use this file for booting Manjaro.

If you do not have this file or folder, try-

{{UserCmd|command=sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Manjaro --recheck}}

to create '''/boot/efi/EFI/Manjaro/grubx64.efi'''

See also- [http://www.rodsbooks.com/refind/installing.html#naming http://www.rodsbooks.com/refind/installing.html#naming]

=== An alternative: chainloading via GRUB ===

An entry can be added to
{{File|file=/etc/grub.d/40_custom|
content=
<pre>
menuentry 'Windows8 (UEFI)' {
insmod ntfs
set root=(hd0,gpt4)
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
boot
}
</pre>
}}
In this case (hd0,4) or /dev/sda4 is the EFI System partition where the Windows bootloader is present.

After adding the above entry, running '''sudo update-grub''' updates the GRUB configuration file so that an entry named '''Windows8 (UEFI)''' is added to the GRUB boot menu.

Related Forum thread: [https://forum.manjaro.org/t/detecting-efi-files-and-booting-them-from-grub/38083]

The chainloading will fail on some hardware (Lenovo Ideapad 110) with the "invalid signature" message - the Refind method will still work.

= Extras =

== Using Rufus on Windows to create installation media ==

[http://rufus.akeo.ie/ Rufus] users can use the following settings:

* Click on the DVD icon and load your .iso
* In the menu left of the DVD icon, select DD Image
* Device: "choose your USB" (Attention: choose correctly,
the device selected here will be formatted!!!)
* Partition scheme: GPT partition scheme for UEFI computer
* File system: FAT32
* Cluster size: "Don't modify"
* Volume label: "Don't modify"
* Click Start, and you are done (takes 2~5 min to complete).

= Feedback =

Questions, suggestions, critics? Please post here: [http://forum.manjaro.org/]

= External Links =

Youtube video: https://www.youtube.com/watch?v=36tDZIXn3-k

[[Category:Contents Page]]

UEFI - Install Guide

2021-09-04T19:26:57Z

Bogdancovaciu:

= Introduction =

UEFI is the commonly agreed on name for both the EFI & UEFI
standards which merged. It does not include the old EFI v1,
or Apple's own non-standard version of EFI.

= Target computer =

The following guide aims to install Manjaro on a machine with UEFI enabled, Secure boot disabled, and using GUID Partition Table (GPT) disk(s).

For multi-boot, the EFI system partition which is already present (or will be created), can usually be shared amongst multiple Linux installs.

= The steps =

== Common ==

* 1. Download your preferred Manjaro version (XFCE, Openbox, Cinnamon, KDE, ...), must be 64-bits.

* 2. Burn the .iso to USB or DVD. See [[Burn_an_ISO_File]] for more details.

* 3. Check your BIOS, UEFI must be ON and Secure boot OFF.

* 4. Boot with your USB or DVD & use the rEFInd - Main Menu... to choose which GPU drivers you want to have installed, the open-source or proprietary:

* Boot Manjaro Linux ... (default) -
This chooses the ''open-source - free'' GPU drivers.
* Boot Manjaro Linux ... (nonfree) -
This option chooses the '''proprietary''' GPU drivers
from Nvidia or ATI.

=== Graphical Installer ===

{{BoxSuccess|tip|Since Manjaro-0.8.9, UEFI support is also provided in the Graphical Installer, so one can simply try the Graphical installer and skip the instructions given below for the CLI installer.}}

To use the Graphical Installer select the '''Install Manjaro''' option from the Manjaro Welcome screen or from the desktop.

For the ESP (EFI system partition) which will store the EFI Grub binary, a 512mb partition of type fat32 can be created in the partitioning step, and mounted to ''/boot/efi''

If you are dual booting then an EFI partition from a previous install can also be used.

=== CLI installer ===

* 5-b. Open terminal & enter:

$ sudo setup

* 6. Now, we are in the CLI Installer.

* 7. ''Choose 1.'' Set date and time - an easy intuitive configuration.

==== Disk preparation ====

{{BoxSuccess|tip|If your hard disk is already partitioned the way you want, then this step can be skipped.}}

* When you ''click 2.'' Partition Hard Drives,
you get a dialog saying "Do you want to use GUID
Partition Table (GPT)", '''choose Yes'''.
* Partition your disk(s) as you want (Instructions on
manually partitioning are beyond the scope of this
guide, some deatils are available [[Cfdisk_Basic_Partitioning_Scenarios|here]]).
* ''Important Step:'' Create a 50~250MB EFI Partition,
mine is 100MB (code: ef00)

==== Setting filesystem mount points ====

* After the partitioning is done, go to ''4. Set Filesystem''
''Mountpoints.''
* '''Important Step:''' Format the EFI Partition you
created as '''VFAT''' and mount on /boot/efi

{{BoxInfo|note|If you are re-using your EFI partition (that was created by Windows previously (or any other OS), then there is no need to format. Formatting will wipe the previous bootloader. Only mounting the EFI partition as '''/boot/efi''' is required in that case.}}

==== Installation ====

* 9. ''Choose 3.'' Install system and wait...

* 10. Now, go to ''4. Configure System'' and configure it the way you like (username, password, mirrorlist, system-name, ...).

* 11. When you are done, go to ''5. Install bootloader.'' Choose EFI_x86_64 > GRUB (2) UEFI x86_64, ''DON'T select BIOS GRUB.''

* 11.1 It will ask to format the EFI Partition you created earlier as FAT32, yes can be chosen.
{{BoxInfo|note|Formatting not required if reusing previous EFI partition.}}

* 12. If it gives a error in the final stages saying "efivars kernel module was not properly loaded", don't worry, the system will work fine!

* 13. If the installer asks you about copying grub/efi files to another folder in order to maintain compatibility in some systems, choose Yes.

* 14. ''Click 6.'' Quit

* 15. Shutdown, remove the DVD or USB, and boot. Your system should appear now!

= Switching from BIOS to UEFI =

1) You need to create an ''ESP (EFI System Partition)''.

It is a FAT32 partition which has the .efi files for booting, which you can create using gparted or gdisk. (Size at least 200-300 MiB.) Ensure the flags `boot` and `esp` are set on this partition.

You should also install/check whether following packages are present-

1. efibootmgr
2. dosfstools
3. grub

[[Pacman_Overview | (How to install packages)]]

2) Create the ''/boot/efi'' directory
sudo mkdir /boot/efi

3.) Mount the EFI partition as ''/boot/efi''
sudo mount /dev/sdXY /boot/efi
X = Alphabet of the drive = a,b,c ...
Y = Partition number of the EFI partition = 1,2,3,4...

Example - ''/dev/sda4''

4.) Install Grub according to UEFI
sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck

5.) Update Grub configuration file.
sudo update-grub

'''Note-'''
If you get an error like
path '/boot/grub' is not readable by Grub on boot. Installation is impossible. Aborting

Then you will need to [https://wiki.archlinux.org/index.php/Change_Root chroot] as described [[Restore_the_GRUB_Bootloader#Identify_and_Prepare_the_Installed_Partition.28s.29|here]], and then perform Step 5 again.

If you get the following error :

EFI variables are not supported on this system.

then you could load the '''efivarfs''' module :
sudo modprobe efivarfs

'''See also'''

[[Restore the GRUB Bootloader]]

[https://forum.manjaro.org/t/using-livecd-v17-0-1-as-grub-to-boot-os-with-broken-bootloader/24916]

= Dual booting with Windows =

{{BoxSuccess|tip|Some manufactures EFI implementations cause GRUB not to be showed in the Boot Menu, or even if its there it can't be made default.}}

'''In such cases ''[http://www.rodsbooks.com/refind/index.html rEFInd]''''' can be used.

[[File:Refind.png]]

There are two ways to install rEFInd-

1.Install rEFInd from its website [http://www.rodsbooks.com/refind/installing.html] (detailed) or '''install using pacman'''''(preferred)''-
sudo pacman -S refind

Files will be present in /usr/share/refind .

2.Or using the instructions on the rEFInd website: [http://www.rodsbooks.com/refind/installing.html]

== Instructions ==

The '''refind-install''' command can be used to automatically install rEFInd (the EFI partition may need to be mounted for this to work). See the [https://wiki.archlinux.org/index.php/REFInd#Installation Arch wiki] for more details.

=== Manual install ===

Inside the refind folder ('''/usr/share/refind'''), copy the files and folders to-

/boot/efi/EFI/Boot/

'''Note-'''

My ESP (EFI System Partition) is mounted at /boot/efi.

You need to copy these files to the Boot folder on your EFI partition, and the Boot folder itself will be present inside the EFI folder on the EFI Partition, so take note of it.

You can check which partition is your ESP using Gparted; find which partition is formatted as fat32 and has size around 200mb-1gb.

Can mount it as /boot/efi by

sudo mount /dev/sdXN /boot/efi
X=a,b,c...
N=1,2,3...
These depend on which partition your ESP is present which can be obtained via Gparted as mentioned earlier.

Now inside the /boot/efi/EFI/Boot/ folder, there should already be a file present-
bootx64.efi

You can '''''rename''''' it as ''windows.bootx64.efi''
Then you can rename ''refind_x64.efi'' to ''bootx64.efi''

The bootx64.efi files boot by default, hence rEFInd should now boot by default, and detect grubx64.efi(linux-manjaro) and efibootmgfw.efi (windows) automatically.

'''Note'''-

A folder Manjaro (name could be some other also) containing the file grubx64.efi should also be present in /boot/efi/EFI/ folder, which should contain the grubx64.efi file which will be used by rEFInd to boot Grub.

So it could be like-
/boot/efi/EFI/Manjaro/grubx64.efi

rEFInd would use this file for booting Manjaro.

If you do not have this file or folder, try-

sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Manjaro --recheck

to create '''/boot/efi/EFI/Manjaro/grubx64.efi'''

See also- [http://www.rodsbooks.com/refind/installing.html#naming http://www.rodsbooks.com/refind/installing.html#naming]

=== An alternative: chainloading via GRUB ===

An entry can be added to
{{File|file=/etc/grub.d/40_custom|
content=
<pre>
menuentry 'Windows8 (UEFI)' {
insmod ntfs
set root=(hd0,gpt4)
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
boot
}
</pre>
}}
In this case (hd0,4) or /dev/sda4 is the EFI System partition where the Windows bootloader is present.

After adding the above entry, running '''sudo update-grub''' updates the GRUB configuration file so that an entry named '''Windows8 (UEFI)''' is added to the GRUB boot menu.

Related Forum thread: [https://forum.manjaro.org/t/detecting-efi-files-and-booting-them-from-grub/38083]

The chainloading will fail on some hardware (Lenovo Ideapad 110) with the "invalid signature" message - the Refind method will still work.

= Extras =

== Using Rufus on Windows to create installation media ==

[http://rufus.akeo.ie/ Rufus] users can use the following settings:

* Click on the DVD icon and load your .iso
* In the menu left of the DVD icon, select DD Image
* Device: "choose your USB" (Attention: choose correctly,
the device selected here will be formatted!!!)
* Partition scheme: GPT partition scheme for UEFI computer
* File system: FAT32
* Cluster size: "Don't modify"
* Volume label: "Don't modify"
* Click Start, and you are done (takes 2~5 min to complete).

= Feedback =

Questions, suggestions, critics? Please post here: [http://forum.manjaro.org/]

= External Links =

Youtube video: https://www.youtube.com/watch?v=36tDZIXn3-k

[[Category:Contents Page]]

UEFI - Install Guide

2021-09-04T18:53:29Z

Bogdancovaciu:

= Introduction =

UEFI is the commonly agreed on name for both the EFI & UEFI
standards which merged. It does not include the old EFI v1,
or Apple's own non-standard version of EFI.

= Target computer =

The following guide aims to install Manjaro on a machine with UEFI enabled, Secure boot disabled, and using GUID Partition Table (GPT) disk(s).

For multi-boot, the EFI system partition which is already present (or will be created), can usually be shared amongst multiple Linux installs.

= The steps =

== Common ==

* 1. Download your preferred Manjaro version (XFCE, Openbox, Cinnamon, KDE, ...), must be 64-bits.

* 2. Burn the .iso to USB or DVD. See [[Burn_an_ISO_File]] for more details.

* 3. Check your BIOS, UEFI must be ON and Secure boot OFF.

* 4. Boot with your USB or DVD & use the rEFInd - Main Menu... to choose which GPU drivers you want to have installed, the open-source or proprietary:

* Boot Manjaro Linux ... (default) -
This chooses the ''open-source - free'' GPU drivers.
* Boot Manjaro Linux ... (nonfree) -
This option chooses the '''proprietary''' GPU drivers
from Nvidia or ATI.

=== Graphical Installer ===

{{BoxSuccess|tip|Since Manjaro-0.8.9, UEFI support is also provided in the Graphical Installer, so one can simply try the Graphical installer and skip the instructions given below for the CLI installer.}}

To use the Graphical Installer select the '''Install Manjaro''' option from the Manjaro Welcome screen or from the desktop.

For the ESP (EFI system partition) which will store the EFI Grub binary, a 512mb partition of type fat32 can be created in the partitioning step, and mounted to ''/boot/efi''

If you are dual booting then an EFI partition from a previous install can also be used.

=== CLI installer ===

* 5-b. Open terminal & enter:

$ sudo setup

* 6. Now, we are in the CLI Installer.

* 7. ''Choose 1.'' Set date and time - an easy intuitive configuration.

==== Disk preparation ====

{{BoxSuccess|tip|If your hard disk is already partitioned the way you want, then this step can be skipped.}}

* When you ''click 2.'' Partition Hard Drives,
you get a dialog saying "Do you want to use GUID
Partition Table (GPT)", '''choose Yes'''.
* Partition your disk(s) as you want (Instructions on
manually partitioning are beyond the scope of this
guide, some deatils are available [[Cfdisk_Basic_Partitioning_Scenarios|here]]).
* ''Important Step:'' Create a 50~250MB EFI Partition,
mine is 100MB (code: ef00)

==== Setting filesystem mount points ====

* After the partitioning is done, go to ''4. Set Filesystem''
''Mountpoints.''
* '''Important Step:''' Format the EFI Partition you
created as '''VFAT''' and mount on /boot/efi

{{BoxInfo|note|If you are re-using your EFI partition (that was created by Windows previously (or any other OS), then there is no need to format. Formatting will wipe the previous bootloader. Only mounting the EFI partition as '''/boot/efi''' is required in that case.}}

==== Installation ====

* 9. ''Choose 3.'' Install system and wait...

* 10. Now, go to ''4. Configure System'' and configure it the way you like (username, password, mirrorlist, system-name, ...).

* 11. When you are done, go to ''5. Install bootloader.'' Choose EFI_x86_64 > GRUB (2) UEFI x86_64, ''DON'T select BIOS GRUB.''

* 11.1 It will ask to format the EFI Partition you created earlier as FAT32, yes can be chosen.
{{BoxInfo|note|Formatting not required if reusing previous EFI partition.}}

* 12. If it gives a error in the final stages saying "efivars kernel module was not properly loaded", don't worry, the system will work fine!

* 13. If the installer asks you about copying grub/efi files to another folder in order to maintain compatibility in some systems, choose Yes.

* 14. ''Click 6.'' Quit

* 15. Shutdown, remove the DVD or USB, and boot. Your system should appear now!

= Switching from BIOS to UEFI =

1) You need to create an ''ESP (EFI System Partition)''.

It is a FAT32 partition which has the .efi files for booting, which you can create using gparted or gdisk. (Size at least 200-300 MiB.) Ensure the flags `boot` and `esp` are set on this partition.

You should also install/check whether following packages are present-

1. efibootmgr
2. dosfstools
3. grub

[[Pacman_Overview | (How to install packages)]]

2) Create the ''/boot/efi'' directory
sudo mkdir /boot/efi

3.) Mount the EFI partition as ''/boot/efi''
sudo mount /dev/sdXY /boot/efi
X = Alphabet of the drive = a,b,c ...
Y = Partition number of the EFI partition = 1,2,3,4...

Example - ''/dev/sda4''

4.) Install Grub according to UEFI
sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck

5.) Update Grub configuration file.
sudo update-grub

'''Note-'''
If you get an error like
path '/boot/grub' is not readable by Grub on boot. Installation is impossible. Aborting

Then you will need to [https://wiki.archlinux.org/index.php/Change_Root chroot] as described [[Restore_the_GRUB_Bootloader#Identify_and_Prepare_the_Installed_Partition.28s.29|here]], and then perform Step 5 again.

If you get the following error :

EFI variables are not supported on this system.

then you could load the '''efivarfs''' module :
sudo modprobe efivarfs

'''See also'''

[[Restore the GRUB Bootloader]]

[https://forum.manjaro.org/t/using-livecd-v17-0-1-as-grub-to-boot-os-with-broken-bootloader/24916]

= Dual booting with Windows =

{{BoxSuccess|tip|Some manufactures EFI implementations cause GRUB not to be showed in the Boot Menu, or even if its there it can't be made default.}}

'''In such cases ''[http://www.rodsbooks.com/refind/index.html rEFInd]''''' can be used.

[[File:Refind.png]]

There are two ways to install rEFInd-

1.Install rEFInd from its website [http://www.rodsbooks.com/refind/installing.html] (detailed) or '''install using pacman'''''(preferred)''-
sudo pacman -S refind

Files will be present in /usr/share/refind .

2.Or using the instructions on the rEFInd website: [http://www.rodsbooks.com/refind/installing.html]

== Instructions ==

The '''refind-install''' command can be used to automatically install rEFInd (the EFI partition may need to be mounted for this to work). See the [https://wiki.archlinux.org/index.php/REFInd#Installation Arch wiki] for more details.

=== Manual install ===

Inside the refind folder ('''/usr/share/refind'''), copy the files and folders to-

/boot/efi/EFI/Boot/

'''Note-'''

My ESP (EFI System Partition) is mounted at /boot/efi.

You need to copy these files to the Boot folder on your EFI partition, and the Boot folder itself will be present inside the EFI folder on the EFI Partition, so take note of it.

You can check which partition is your ESP using Gparted; find which partition is formatted as fat32 and has size around 200mb-1gb.

Can mount it as /boot/efi by

sudo mount /dev/sdXN /boot/efi
X=a,b,c...
N=1,2,3...
These depend on which partition your ESP is present which can be obtained via Gparted as mentioned earlier.

Now inside the /boot/efi/EFI/Boot/ folder, there should already be a file present-
bootx64.efi

You can '''''rename''''' it as ''windows.bootx64.efi''
Then you can rename ''refind_x64.efi'' to ''bootx64.efi''

The bootx64.efi files boot by default, hence rEFInd should now boot by default, and detect grubx64.efi(linux-manjaro) and efibootmgfw.efi (windows) automatically.

'''Note'''-

A folder Manjaro (name could be some other also) containing the file grubx64.efi should also be present in /boot/efi/EFI/ folder, which should contain the grubx64.efi file which will be used by rEFInd to boot Grub.

So it could be like-
/boot/efi/EFI/Manjaro/grubx64.efi

rEFInd would use this file for booting Manjaro.

If you do not have this file or folder, try-

sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Manjaro --recheck

to create '''/boot/efi/EFI/Manjaro/grubx64.efi'''

See also- [http://www.rodsbooks.com/refind/installing.html#naming http://www.rodsbooks.com/refind/installing.html#naming]

=== An alternative: chainloading via GRUB ===

An entry can be added to ''/etc/grub.d/40_custom''

menuentry 'Windows8 (UEFI)' {
insmod ntfs
set root=(hd0,gpt4)
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
boot
}

In this case (hd0,4) or /dev/sda4 is the EFI System partition where the Windows bootloader is present.

After adding the above entry, running '''sudo update-grub''' updates the GRUB configuration file so that an entry named '''Windows8 (UEFI)''' is added to the GRUB boot menu.

Related Forum thread: [https://forum.manjaro.org/t/detecting-efi-files-and-booting-them-from-grub/38083]

The chainloading will fail on some hardware (Lenovo Ideapad 110) with the "invalid signature" message - the Refind method will still work.

= Extras =

== Using Rufus on Windows to create installation media ==

[http://rufus.akeo.ie/ Rufus] users can use the following settings:

* Click on the DVD icon and load your .iso
* In the menu left of the DVD icon, select DD Image
* Device: "choose your USB" (Attention: choose correctly,
the device selected here will be formatted!!!)
* Partition scheme: GPT partition scheme for UEFI computer
* File system: FAT32
* Cluster size: "Don't modify"
* Volume label: "Don't modify"
* Click Start, and you are done (takes 2~5 min to complete).

= Feedback =

Questions, suggestions, critics? Please post here: [http://forum.manjaro.org/]

= External Links =

Youtube video: https://www.youtube.com/watch?v=36tDZIXn3-k

[[Category:Contents Page]]

LXQt with kwin

2021-09-04T18:46:35Z

Bogdancovaciu:

__TOC__

== Installation ==
{{BoxSuccess|tip|KWinFT (KWin Fast-Track) is a drop-in replacement for KWin. It is provided in the AUR helping with the transition from X11 to Wayland.}}
If you like to try KWinFT replace the kwin package name in the command below this line with '''kwinft'''.
{{UserCmd|command=pamac install kwin systemsettings}}

=== Optional: Remove OpenBox ===
If you had openbox installed, it can now be safely removed:
{{UserCmd|command=pamac remove openbox}}
(this will also remove obconf and any other dependencies)

As kwin comes with a builtin compositor you may want to remove compton/picom:
{{UserCmd|command=pamac remove compton picom}}
(this will also remove compton-conf and any other dependencies)
{{BoxInfo|note|Use of compton/picom with kwin is still possible. KDE's builtin compositor can be disabled in "KDE Systemsettings" (free choice!)}}

==Configuration==
# Open LXQt Session Settings
# Select '''kwin_x11''' as window manager
<Screenshot TBD>

Logout or reboot and enjoy LXQt with kwin!

===Global Keyboard Shortcuts===
Global shortcuts are managed by '''lxqt-globalkeys''' (LXQt settings -> Global Shortcuts):
<Screenshot TBD>
{{BoxDanger|warning|Mapping the Super_L/Super_R keys (<Meta> without a second key) can lead to unexpected behaviour and is not recommended!}}

{{BoxInfo|note|Some window manager specific shortcuts are managed by kwin (e.g. "Alt+Tab" for the task switcher). Those are fully transparent to lxqt-globalkeys and ''cannot'' be assigned/changed!}}

====Optional (WARNING - ADVANCED SECTION!): Configure kwin Shortcuts====
All kwin shortcuts are managed in '''~/.config/kglobalshortcutsrc'''.
{{BoxDanger|warning|Editing this file can lead to non-working keys! You have been warned!}}

Search for the shortcut of choice and edit it. Alternatives are separated by comma (e.g. '''Alt+Tab,Alt+Tab,…''').
{{BoxInfo|tip|Changes become effective on next login. (log out/in for testing)}}


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