https://wiki.archlinux.org/api.php?action=feedcontributions&user=CabronDeOz&feedformat=atomArchWiki - User contributions [en]2024-03-29T13:33:26ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=VirtualBox&diff=247076VirtualBox2013-02-11T18:30:36Z<p>CabronDeOz: /* Loading Kernel Modules */ Ran into problems running with bridged networking, added solution.</p>
<hr />
<div>[[Category:Emulators]]<br />
[[Category:Virtualization]]<br />
[[cs:VirtualBox]]<br />
[[de:VirtualBox]]<br />
[[es:VirtualBox]]<br />
[[fr:VirtualBox]]<br />
[[hu:VirtualBox]]<br />
[[it:VirtualBox]]<br />
[[ja:VirtualBox]]<br />
[[pt:VirtualBox]]<br />
[[ru:VirtualBox]]<br />
[[zh-CN:VirtualBox]]<br />
{{Article summary start}}<br />
{{Article summary text|This article is about basic usage of VirtualBox, including running the VirtualBox software within an Arch ''host'', and running an Arch ''guest'' inside a VirtualBox virtual machine.}}<br />
{{Article summary heading|Required software}}<br />
{{Article summary link|VirtualBox|https://www.virtualbox.org}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|VirtualBox Extras}}<br />
{{Article summary wiki|PhpVirtualBox}}<br />
{{Article summary wiki|VirtualBox Arch Linux Guest On Physical Drive}}<br />
{{Article summary wiki|Advanced VirtualBox Networking}}<br />
{{Article summary wiki|Installing Arch Linux from VirtualBox}}<br />
{{Article summary wiki|Moving an existing install into (or out of) a virtual machine}}<br />
{{Article summary end}}<br />
<br />
'''VirtualBox''' is a virtual PC emulator like [[VMware]]. It is in constant development and new features are implemented all the time. e.g. version 2.2 introduced OpenGL 3D acceleration support for Linux and Solaris guests. It has a [[Qt]] GUI interface, as well as headless and [[Wikipedia:SDL|SDL]] command line tools for managing and running virtual machines. It includes ''guest additions'' for some guest operating systems, which integrate functions of the guest and host systems, including sharing files, the clipboard, video acceleration and a “seamless” window integration mode.<br />
<br />
{{Wikipedia|VirtualBox}}<br />
<br />
== Installation on host ==<br />
<br />
The basic GPL-licensed VirtualBox suite can be [[pacman|installed]] with the {{Pkg|virtualbox}} package, found in the [[official repositories]]. You will need to install {{pkg|virtualbox-host-modules}} separately, if it is not installed with the the {{Pkg|virtualbox}} package, which contains the precompiled modules for the stock archlinux kernel. For custom kernels, read [[#Hosts running a custom kernel|the section below]].<br />
<br />
In order to use the graphical interface, based on [[Qt]] ({{ic|VirtualBox}} command), you will also need to install the {{Pkg|qt}} package. This is not required for the simpler SDL-only GUI ({{ic|VBoxSDL}} command) nor for the {{ic|VBoxHeadless}} command.<br />
<br />
If you are using the {{pkg|linux-lts}} kernel you should install also the {{pkg|virtualbox-host-modules-lts}} package.<br />
<br />
=== Hosts running a custom kernel ===<br />
<br />
VirtualBox works just fine with custom kernels such as [[Linux-ck]] ''without'' the need to keep any of the official ARCH kernel packages on the system. The trick to keeping pacman from bringing down the ARCH kernel packages is to install virtualbox with the {{Pkg|virtualbox-host-dkms}} package, which contains the source for the virtualbox kernel modules. See {{Bug|26721}} for further explanations.<br />
<br />
Once {{Pkg|virtualbox-host-dkms}} is installed, simply generate the kernel modules for your custom kernel by running:<br />
<br />
# dkms install vboxhost/<virtualbox-host-source version> -k <your custom kernel's version>/<your architecture><br />
<br />
Which for the lazy is the command:<br />
<br />
# dkms install vboxhost/$(pacman -Q virtualbox|awk {'print $2'}|sed 's/\-.\+//') -k $(uname -rm|sed 's/\ /\//')<br />
<br />
and load it:<br />
<br />
# modprobe vboxdrv<br />
<br />
{{Note|(Not working currently) To load/compile virtualbox modules automatically at startup you can install and add {{pkg|dkms}} in your DAEMONS array.}}<br />
<br />
==== Automatic re-compilation of the virtualbox host modules with every update of any kernel====<br />
<br />
This is possible thanks to {{AUR|vboxhost-hook}} from the [[AUR]]. In '''vboxhost-hook''', the 'automatic re-compilation' functionality is done by a '''vboxhost hook''' on [[mkinitcpio]] after forcing to update the '''linux-headers''' package. You will need to add 'vboxhost' to the HOOKS array in /etc/mkinitcpio.conf, as well as 'linux-headers' and your custom kernel(s) headers to the SyncFirst array in /etc/pacman.conf for this to work.<br />
<br />
The hook will call the '''dkms''' command to update the virtualbox host modules for the version of your new kernel.<br />
<br />
{{Note|If you are using this functionality it's '''important''' to look at the installation process of the linux (or any other kernel) package. vboxhost hook will tell you if anything goes wrong.}}<br />
<br />
== Setup ==<br />
<br />
Add the desired username to the '''vboxusers''' [[group]]. Everything may work fine without this step but shared folders and possibly some other optional stuff require it to work. The new group does not automatically apply to existing sessions; the user has to log in again or start a new environment with a command like {{Ic|newgrp}} or {{Ic|sudo -u ''username'' -s}}.<br />
<br />
# gpasswd -a ''username'' vboxusers<br />
<br />
=== Loading Kernel Modules ===<br />
VirtualBox running on Linux uses its own [[kernel modules]], including a mandatory one called '''vboxdrv''', which must be loaded before virtual machines can run. It can be automatically loaded when Arch Linux starts up, or it can be loaded manually when necessary.<br />
<br />
To load the VirtualBox driver at startup, add a file with the {{ic|*.conf}} suffix in the {{ic|/etc/[[Kernel_modules#Loading|modules-load.d]]}} directory (e.g. ''virtualbox.conf'') that reads "vboxdrv":<br />
<br />
# tee /etc/modules-load.d/virtualbox.conf <<< "vboxdrv"<br />
<br />
{{Note|You may need to update the kernel modules db in order to avoid 'no such file or directory' error when loading vboxdrv. Run: {{ic|depmod -a}}.}}<br />
<br />
To load the module manually:<br />
<br />
# modprobe vboxdrv<br />
<br />
To start the VirtualBox graphical manager:<br />
<br />
$ VirtualBox<br />
<br />
To ensure full functionality of bridged networking, ensure that the following modules are also loaded:<br />
<br />
vboxnetadp vboxnetflt vboxpci<br />
<br />
Either load them using a file in /etc/modules-load.d or load them manually using {{ic|modprobe}}.<br />
<br />
=== Guest additions disc ===<br />
<br />
The {{ic|virtualbox}} package also suggests installing {{Pkg|virtualbox-guest-iso}} on the host (Arch Linux) running VirtualBox. It is a disc image that can be used to install the guest additions onto guest systems. Make it available to the (running) guest by going to Devices and clicking "Install Guest Additions... Host+D". Then run the guest additions installation from inside the guest.<br />
<br />
=== Booting a live disc ===<br />
<br />
Click the 'New' button to create a new virtual environment. Name it appropriately and select Operating System type and version. Select base memory size (note: most operating systems will need at least 512&nbsp;MB to function properly). Create a new hard disk image (a hard disk image is a file that will contain the operating system's filesystem and files).<br />
<br />
When the new image has been created, click 'Settings', then CD/DVD-ROM, check 'Mount CD/DVD Drive' then select an ISO image.<br />
<br />
=== Starting virtual machines with a service ===<br />
<br />
See [[Systemd/Services#VirtualBox_virtual_machines]] for details on how to setup a systemd service for each virtual machine.<br />
<br />
=== Advanced setup ===<br />
<br />
See [[VirtualBox Extras]] for advanced configuration.<br />
<br />
== Arch Linux guests ==<br />
<br />
Installing Arch under VirtualBox is straightforward, and additions should be installed through pacman (not through "Install Guest Additions" in VirtualBox, or from a mounted ISO image).<br />
<br />
=== Install the Guest Additions ===<br />
<br />
Install the {{Pkg|virtualbox-guest-utils}} package:<br />
<br />
# pacman -S virtualbox-guest-utils<br />
Manually load the modules with:<br />
<br />
# modprobe -a vboxguest vboxsf vboxvideo<br />
<br />
Create a {{ic|*.conf}} file (e.g. {{ic|virtualbox.conf}}) in {{ic|/etc/modules-load.d/}} with these lines:<br />
<br />
{{hc|/etc/modules-load.d/virtualbox.conf|<br />
vboxguest<br />
vboxsf<br />
vboxvideo}}<br />
<br />
=== Automatic re-compilation of the virtualbox guest modules with every update of any kernel ===<br />
<br />
This is possible thanks to {{AUR|vboxguest-hook}} from the [[AUR]]. In '''vboxguest-hook''', the 'automatic re-compilation' functionality is done by a '''vboxguest hook''' on [[mkinitcpio]] after forcing to update the '''linux-headers''' package. You will need to add 'vboxguest' to the HOOKS array in /etc/mkinitcpio.conf, as well as 'linux-headers' and your custom kernel(s) headers to the SyncFirst array in /etc/pacman.conf for this to work.<br />
<br />
The hook will call the '''dkms''' command to update the virtualbox guest modules for the version of your new kernel.<br />
<br />
{{Note|If you are using this functionality it's '''important''' to look at the installation process of the linux (or any other kernel) package. vboxguest hook will tell you if anything goes wrong.}}<br />
<br />
=== Start the sharing services ===<br />
After installing {{Pkg|virtualbox-guest-utils}} above, you should start {{ic|VBoxClient-all}} to start services for sharing the clipboard, resizing the screen, etc.<br />
* If you are running something that launches {{Ic|/etc/xdg/autostart/vboxclient.desktop}}, such as GNOME or KDE, then nothing needs to be done. <br />
* If you use {{Ic|.xinitrc}} to launch things instead, you must add the following to your {{Ic|.xinitrc}} before launching your WM.<br />
<br />
# VBoxClient-all &<br />
<br />
=== Using USB webcam / microphone ===<br />
<br />
{{Note|You will need to have VirtualBox extension pack installed before following the steps below. See [[VirtualBox_Extras#Extension_pack]] for details.}}<br />
<br />
# Make sure the virtual machine is not running and your webcam / microphone is not being used.<br />
# Bring up the main VirtualBox window and go to settings for Arch machine. Go to USB section.<br />
# Make sure "Enable USB Controller" is selected. Also make sure that "Enable USB 2.0 (EHCI) Controller" is selected too.<br />
# Click the "Add filter from device" button (the cable with the '+' icon).<br />
# Select your USB webcam/microphone device from the list.<br />
# Now click OK and start your VM.<br />
<br />
=== Using Arch under Virtualbox EFI mode ===<br />
<br />
My experience with this configuration was pretty terrible, but it does work.<br />
<br />
''UPD. Using efibootmgr has the same effect as using VirtualBox boot menu (see the note below): settings [https://www.virtualbox.org/ticket/11177 disappear] after VM shutdown.'' First, {{ic|efibootmgr}} does *not* work. It will appear to work, but all changes it makes appear to be overwritten on reboot. After performing a standard UEFI/GPT installation, reboot and you should get dumped to the EFI shell. Type exit and you will get a menu. Select the Boot Management Manager, Boot Options, Add Boot Option. Use the file browser to find the grub efi file and select it. Add a label if you want. Afterwards, select Change Boot Order from the menu, use arrow keys to select your Arch option, and + to move it up to the top. GRUB should boot by default now.<br />
<br />
Other options are: 1) move your loader to \EFI\boot\bootx64.efi, 2) create \stratup.nsh script, which executes desirable loader, like this:<br />
<br />
{{hc|\startup.nsh|<br />
HD16a0a1:\EFI\refind\refindx64.efi}}<br />
<br />
Here I'm using consistent mapping name (HD16a0a1). It's probably a good idea, because they do survive configuration changes.<br />
<br />
{{Note|Another useful way to get back to the EFI menu after autobooting is working is to press the {{Keypress|C}} key inside GRUB and type {{ic|exit}}. Obviously, this will only work with {{ic|grub-efi}}, not {{ic|grub-bios}}.<br><br />
Regenerating the {{ic|grub.cfg}} file may also be required to fix broken UUIDs. Check with the {{ic|lsblk -f}} command that they match.<br><br />
Yet another useful way to get to VirtualBox boot menu is pressing F12 right after starting virtual machine. It comes in handy when using rEFInd + EFISTUB, for example.}}<br />
<br />
== Shared Folders as Arch Linux Guest ==<br />
<br />
Shared folders are managed via the VirtualBox program on the host. They may be added, auto-mounted and made read-only from there. Creating a shared folder from the VirtualBox program in the host locates that folder in {{Ic|/media/sf_''SHAREDFOLDERNAME''}}. At this time an additional step is needed to have that folder created in the Arch Guest because Arch use a package for Guest Additions. To create and access this shared folder from the Arch Guest, this must also be done at the command line after installing the Guest Additions package(s) from pacman:<br />
<br />
# groupadd vboxsf<br />
# gpasswd -a $USER vboxsf<br />
<br />
If you wish, a symbolic link may be made to another folder in your home directory for easy access. As an example, if a shared folder named "Dropbox" was created in the VirtualBox program on the host machine, then /media/sf_Dropbox is automatically created in the guest so this could be done:<br />
<br />
$ ln -s /media/sf_Dropbox/* ~/dropbox<br />
<br />
The .run script provided in the Guest Additions iso does this for you, however, Arch does not recommend using that script so this step must be done manually. The instructions for it were found here: (pastebin: [http://pastebin.com/6cUE3kjF]) .<br />
<br />
If shared folders are not auto-mounted, try [https://bbs.archlinux.org/viewtopic.php?id=70780 manually mount] or read the next section.<br />
<br />
To prevent startup problems when you're using [[systemd]], you should add {{ic|1=comment=systemd.automount}} to your {{ic|/etc/fstab}}. This way, they are mounted only when you access those mountpoints and not during startup. Otherwise your system might become unusable after a kernel upgrade (if you install your guest additions manually).<br />
<br />
desktop /media/desktop vboxsf uid=user,gid=group,rw,dmode=700,fmode=600,comment=systemd.automount 0 0<br />
<br />
Don't waste your time to test the {{ic|nofail}} option. {{ic|mount.vboxsf}} is not able to handle this (2012-08-20).<br />
<br />
desktop /media/desktop vboxsf uid=user,gid=group,rw,dmode=700,fmode=600,nofail 0 0<br />
<br />
=== Synchronise guest date with host ===<br />
<br />
To keep sync date and time, make sure you have {{Pkg|virtualbox-guest-utils}} installed in your host (see [[#Install the Guest Additions|previous section]]). Then run<br />
# systemctl enable vboxservice.service<br />
<br />
To enable the service for next boot. To start immediately, run<br />
# systemctl start vboxservice.service<br />
<br />
You also need run this daemon in order to use auto-mounting feature of shared folders that are mentioned above.<br />
<br />
== Troubleshooting ==<br />
<br />
=== USB subsystem is not working on the host or guest ===<br />
<br />
Sometimes the usb subsystem is not auto-detected resulting in an error or in a not visible USB drive on the host, even when the user is in the '''vboxusers''' group. See this topic [https://bbs.archlinux.org/viewtopic.php?id=125785] for details.<br />
<br />
{{Note|In linux 3.5 and later usbfs was dropped. The /etc/fstab method is no longer working. Please use the USB subsystem method}}<br />
<br />
====fstab method====<br />
Adding an entry in {{Ic|/etc/fstab}} should resolve this issue:<br />
<br />
none /proc/bus/usb usbfs auto,busgid=108,busmode=0775,devgid=108,devmode=664 0 0<br />
<br />
====USB subsystem method====<br />
USB subsystem will work if you add<br />
<br />
VBOX_USB=usbfs<br />
<br />
to {{Ic|~/.bashrc}} and reboot your system or open a new bash instance.<br />
<br />
=== Failed to create the host-only network interface ===<br />
<br />
To be able to create a Host-Only Network Adapter or a Bridged Network Adapter the kernel modules {{ic|vboxnetadp}} and {{ic|vboxnetflt}} need to be loaded. It's possible to load these kernel modules manually with<br />
<br />
# modprobe -a vboxnetadp vboxnetflt<br />
<br />
To load them automatically at boot, add a new line for each module to {{ic|/etc/modules-load.d/virtualbox.conf}}:<br />
<br />
vboxdrv<br />
vboxnetadp<br />
vboxnetflt<br />
<br />
{{Note|These used to be added to the {{ic|MODULES}} array in {{ic|/etc/rc.conf}}. This is now deprecated.}}<br />
<br />
More information in [https://bbs.archlinux.org/viewtopic.php?id=130581 this] topic.<br />
<br />
=== WinXP: Bit-depth cannot be greater than 16 ===<br />
<br />
If you are running at 16-bit color depth, then the icons may appear fuzzy/choppy. However, upon attempting to change the color depth to a higher level, the system may restrict you to a lower resolution or simply not enable you to change the depth at all. To fix this, run {{ic|regedit}} add the following key to the Virtual Windows XP registry:<br />
<br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services]<br />
"ColorDepth"=dword:00000004<br />
<br />
Then update the color depth in the desktop properties window. If nothing happens, force the screen to redraw through some method (i.e. {{Keypress|Host+F}} to redraw/enter full screen).<br />
<br />
=== Mounting .vdi Images ===<br />
<br />
This just work with '''static''' size vdi images! '''Dynamic size won't''' be easy mountable! First we need one information from your .vdi image:<br />
<br />
$ VBoxManage internalcommands dumphdinfo Arch_64min.vdi |grep offData<br />
Header: offBlocks=4096 offData=69632<br />
<br />
Now, '''add to your''' {{ic|offData}} 32256. e.g. 32256 + 69632 = 101888<br />
<br />
Now you can mount your vdi image:<br />
<br />
# mount -t ext4 -o rw,noatime,noexec,loop,offset=101888 Arch_64min.vdi /mnt/<br />
<br />
=== Startup problems because of mount failures ===<br />
<br />
If you experience problems in a [[systemd]] setup after a kernel upgrade, you should start the system with ''init=/bin/bash'' (if the emergency shell doesn't work for you).<br />
<br />
root=/dev/mapper/vg_main-lv_root ro vga=792 resume=/dev/mapper/vg_main-lv_swap init=/bin/bash<br />
<br />
Then mount the ''root''-filesystem with write access:<br />
<br />
# mount / -o remount,rw<br />
<br />
Change /etc/fstab according to [[VirtualBox#Shared Folders as Arch Linux Guest]]. Then exec systemd with in the bash shell:<br />
<br />
# exec /bin/systemd<br />
<br />
=== Copy&Paste not working on Arch Linux Guest ===<br />
<br />
Since updating {{ic|virtualbox-guest-additions}} to version {{ic|4.2.0-2}} copy&paste from Host OS to Arch Linux Guest stopped working. It seems to be due to {{ic|VBoxClient-all}} requiring ''root'' access. In previous versions adding ''VBoxClient-all &'' to ''~/.xinitrc'' was sufficient to make copy&paste work. Update ''~/.xinitrc'' to match {{ic|sudo VBoxClient-all &}} and add the line {{ic|, NOPASSWD: /usr/bin/VBoxClient-all}} to your username in the sudoers file and restart X. It should all work again. The line in the sudoers file should look similar to this:<br />
<br />
# Allow sudo for user 'you' and let him run VBoxClient-all without requiring a password<br />
you ALL = PASSWD: ALL, NOPASSWD: /usr/bin/VBoxClient-all<br />
<br />
{{Note|Use {{ic|visudo}} to edit the sudoers file. This will check for syntax errors when saving.}}<br />
<br />
=== Mouse is resetting to (0,0) randomly and frequently ===<br />
<br />
Due to xorg [https://bugs.freedesktop.org/show_bug.cgi?id=54353 bug 54353] (and related bug reports discussed within), the VirtualBox mouse device will frequently reset to the upper left corner of the screen.<br />
<br />
The workaround suggested in the bug discussion can be applied by adding a script to {{ic|/etc/X11/xinit/xinitrc.d}} with:<br />
<br />
for Z in $(xinput list | sed '/\(master\|slave \) \<pointer\>/!d;s/.*id=\([0-9]\+\).*/\1/'); do<br />
xinput set-prop $Z "Coordinate Transformation Matrix" 0.500000, 0.000000, 0.000000, 0.000000, 0.500000, 0.000000, 0.000000, 0.000000, 0.500000<br />
xinput set-prop $Z "Coordinate Transformation Matrix" 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000<br />
done<br />
<br />
By changing the matrix's value and changing it back to its original value, the internal condition that triggers this bug is avoided.<br />
<br />
=== Use Serial port in guest OS ===<br />
Check you permission in Serial port<br />
$ /bin/ls -l /dev/ttyS*<br />
crw-rw---- 1 root uucp 4, 64 Feb 3 09:12 /dev/ttyS0<br />
crw-rw---- 1 root uucp 4, 65 Feb 3 09:12 /dev/ttyS1<br />
crw-rw---- 1 root uucp 4, 66 Feb 3 09:12 /dev/ttyS2<br />
crw-rw---- 1 root uucp 4, 67 Feb 3 09:12 /dev/ttyS3<br />
<br />
Add you user in '''uucp''' group.<br />
# gpasswd -a YOURUSER uucp <br />
and relogon.<br />
<br />
=== Abort on resume ===<br />
There is a known bug that causes abort on resume: https://www.virtualbox.org/ticket/11289. The workaround is simple: always use Host+q or the menu to close the VM.<br />
<br />
== External links ==<br />
<br />
* [http://www.virtualbox.org/manual/UserManual.html VirtualBox User Manual]</div>CabronDeOzhttps://wiki.archlinux.org/index.php?title=Wine&diff=246703Wine2013-02-07T15:52:48Z<p>CabronDeOz: /* Using WINEARCH */ Spelling.</p>
<hr />
<div>[[Category:Wine]]<br />
[[cs:Wine]]<br />
[[de:Wine]]<br />
[[es:Wine]]<br />
[[fr:Wine]]<br />
[[it:Wine]]<br />
[[ja:Wine]]<br />
[[ru:Wine]]<br />
[[zh-CN:Wine]]<br />
[[zh-TW:Wine]]<br />
{{Article summary start}}<br />
{{Article summary text|[[Wikipedia:Wine (software)|Wine]] is a ''compatibility layer'' capable of running Microsoft Windows applications on Unix-like operating systems. Programs running in Wine act as native programs would, without the performance/memory penalties of an emulator.}}<br />
<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Steam}}<br />
{{Article summary wiki|CrossOver}}<br />
{{Article summary end}}<br />
<br />
See the [http://www.winehq.org/ official project home] and [http://wiki.winehq.org/ wiki] pages for longer introduction. <br />
<br />
== Installation ==<br />
{{Warning| If you can access a file or resource with your user account, programs running in Wine can too. Wine prefixes are not [[wikipedia:Sandbox_%28computer_security%29|sandboxes]]. Consider using [[wikipedia:Virtualization|virtualization]] if security is important.}}<br />
<br />
Wine is constantly updated and available in the <nowiki>[</nowiki>[[community]]] repository for i686 and in <nowiki>[</nowiki>[[multilib]]] for x86_64:<br />
<br />
# pacman -S wine<br />
<br />
You may also require {{pkg|wine_gecko}}, if your applications make use of Internet Explorer:<br />
<br />
# pacman -S wine_gecko<br />
<br />
or [http://wiki.winehq.org/Mono Mono] for .NET applications. The package {{AUR|wine-mono}} available in the [[AUR]], which will place the installer in {{ic|/usr/share/wine/mono/}} for Wine to autodetect (thus preventing Wine from redownloading the installer for every new prefix).<br />
<br />
'''Architectural differences'''<br />
<br />
The default Wine is 32-bit, as is the i686 Arch package. As such, it is unable to execute any 64-bit Windows applications (which are still fairly rare at this point anyway).<br />
<br />
The Wine package for x86_64, however, is currently built with {{ic| --enable-win64}}. This activates the Wine version of [[Wikipedia:WoW64|WoW64]]. <br />
*In Windows, this complicated subsystem allows the user to use 32-bit and 64-bit Windows programs concurrently and even in the same directory. <br />
*In Wine, the user will have to make separate directories/prefixes. The support for this feature in Wine is currently experimental and users are recommended to use a win32 {{ic|WINEPREFIX}}. See [http://wiki.winehq.org/Wine64 Wine64] for specific information on this.<br />
<br />
To summarize, using the Arch 64-bit Wine package with {{ic|1=WINEARCH=win32}} should have the same behaviour as using the i686 Wine package.<br />
<br />
{{Note| If you run into problems with {{ic|winetricks}} or programs with a 64-bit environment, try creating a new 32-bit {{ic|WINEPREFIX}}. See below: [[#Using_WINEARCH]]}}<br />
<br />
== Configuration ==<br />
By default, Wine stores its configuration files and installed Windows programs in {{ic|~/.wine}}. This directory is commonly called a "Wine prefix" or "Wine bottle" It is created/updated automatically whenever you run a Windows program or one of Wine's bundled programs such as {{ic|winecfg}}. The prefix directory also contains a tree which your Windows programs will see as {{ic | C:\}} (C-drive)<br />
<br />
You can override the location Wine uses for a prefix with the {{ic|WINEPREFIX}} environment variable. This is useful if you want to use separate configurations for different Windows programs. <br />
<br />
For example, if you run one program with: {{ic |1= $ env WINEPREFIX=~/.win-a wine program-a.exe}}, and another with {{ic |1= $ env WINEPREFIX=~/.win-b wine program-b.exe}}, the two programs will each have separate "C:\" and registries.<br />
<br />
To create a default prefix without running a Windows program or other GUI tool you can use:<br />
$ env WINEPREFIX=~/.customprefix wineboot -u<br />
<br />
Configuring Wine is typically accomplished using:<br />
* [http://wiki.winehq.org/winecfg winecfg] is a GUI configuration tool for Wine. You can run it from a console window with: {{ic|$ winecfg}}, or {{ic|1=$ WINEPREFIX=~/.some_prefix winecfg}}.<br />
<br />
* [http://wiki.winehq.org/control control.exe] is Wine's implementation of Windows' Control Panel which can be accessed with: {{ic|$ wine control}}<br />
<br />
* [http://wiki.winehq.org/regedit regedit] is Wine's registry editing tool. If winecfg and the Control Panel were not enough, see [http://wiki.winehq.org/UsefulRegistryKeys WineHQ's article on Useful Registry Keys]<br />
<br />
=== Using WINEARCH ===<br />
If you are using wine from [multilib], you will notice that {{ic|winecfg}} will get you a 64-bit wine environment by default. You can change this behavior using the {{ic|WINEARCH}} environment variable. Rename your {{ic|~/.wine}} directory and create a new wine environment by running: <br />
{{ic |1=$ WINEARCH=win32 winecfg}} This will get you a 32-bit wine environment. Not setting {{ic|WINEARCH}} will get you a 64-bit one.<br />
<br />
You can combine this with {{ic|WINEPREFIX}} to make a separate win32 and win64 environment:<br />
$ WINEARCH=win32 WINEPREFIX=~/win32 winecfg <br />
$ WINEPREFIX=~/win64 winecfg<br />
<br />
{{Note|During prefix creation, the 64-bit version of wine treats all folders as 64-bit prefixes and will not create a 32-bit in any existing folder. To create a 32-bit prefix you have to let wine create the folder specified in {{ic|WINEPREFIX}}.}}<br />
<br />
You can also use winetricks and {{ic|WINEARCH}} in one command for installing something from winetricks like this (using Steam as an example):<br />
env WINEARCH=win32 WINEPREFIX=~/.local/share/wineprefixes/steam winetricks steam<br />
{{Tip| You can make variables like WINEPREFIX or WINEARCH constant by using [[Bash#Shell_and_environment_variables|~/.bashrc]]. }}<br />
{{Note|You do not have create the steam subdirectory in the {{ic|wineprefixes}} directory, it will create for you. See the Bottles section below for more information.}}<br />
<br />
=== Graphics Drivers ===<br />
For most games, Wine requires high performance accelerated graphics drivers. This likely means using proprietary binary drivers from [[Nvidia]] or [[ATI|Amd/ATI]]. [[Intel]] drivers should mostly work as well as they are going to out of the box.<br />
<br />
A good sign that your drivers are inadequate or not properly configured is when Wine reports the following in your terminal window:<br />
Direct rendering is disabled, most likely your OpenGL drivers have not been installed correctly<br />
<br />
For x86-64 systems, additional 32-bit [multilib] or [[AUR]] packages are required:<br />
<br />
* '''NVIDIA''': {{ic|# pacman -S lib32-nvidia-utils}} For older cards search the AUR for [https://aur.archlinux.org/packages.php?K=lib32-nvidia-utils lib32-nvidia-utils] (e.g. -173xx).<br />
<br />
* '''NVIDIA (using nouveau-dri)''': {{ic|# pacman -S lib32-nouveau-dri}} <br />
<br />
* '''Intel''': {{ic|# pacman -S lib32-intel-dri}} Run Wine with: {{ic|1=LIBGL_DRIVERS_PATH=/usr/lib32/xorg/modules/dri}}<br />
<br />
* '''AMD/ATI''': {{ic|# pacman -S lib32-ati-dri}} For ATI's proprietary drivers: {{ic|# pacman -S {{Pkg|lib32-catalyst-utils}}}}. <s>install {{AUR|lib32-catalyst-utils}} from the AUR</s> <br />
<br />
{{Note|You might need to restart X after having installed the correct library.}}<br />
<br />
=== Sound ===<br />
By default sound issues may arise when running Wine applications. Ensure only one sound device is selected in {{ic|winecfg}}. Currently, the [[Alsa]] driver is the most supported.<br />
<br />
If you want to use [[Alsa]] driver in Wine, and are using x86_64, you'll need to install the {{Pkg|lib32-alsa-lib}}. If you are also using PulseAudio, you will need to install {{Pkg|lib32-libpulse}}.<br />
<br />
If you want to use [[OSS]] driver in Wine, you will need to install the {{Pkg|lib32-alsa-oss}} package. The OSS driver in the kernel will not suffice.<br />
<br />
If {{ic|winecfg}} '''still''' fails to detect the audio driver (Selected driver: (none)), [http://wiki.jswindle.com/index.php/Wine_Registry#Configuring_Sound configure it via the registry].<br />
<br />
Games that use advanced sound systems may require installations of {{Pkg|lib32-openal}}.<br />
<br />
=== Other libraries ===<br />
<br />
Some applications (e.g. Office 2003) require ability to parse HTML or XML (they use MSXML library), in such case you need to install {{Pkg|lib32-libxml2}}.<br />
<br />
Applications that play music may require {{Pkg|lib32-mpg123}}.<br />
<br />
For application that use native image manipulation libraries installation of {{Pkg|lib32-giflib}} and {{Pkg|lib32-libpng}} may be required.<br />
<br />
For encryption support on x86_64 you need to install {{Pkg|lib32-gnutls}}.<br />
<br />
===Fonts===<br />
<br />
If Wine applications are not showing easily readable fonts, you may not have Microsoft's Truetype fonts installed. See [[MS Fonts]]. If this does not help, try running {{ic|winetricks allfonts}}.<br />
<br />
After running such programs, kill all wine servers and run {{ic|winecfg}}. Fonts should be legible now.<br />
<br />
If the fonts look somehow smeared, import the following text file into the Wine registry with [http://wiki.winehq.org/regedit regedit]:<br />
[HKEY_CURRENT_USER\Software\Wine\X11 Driver]<br />
"ClientSideWithRender"="N"<br />
<br />
=== Desktop Launcher Menus ===<br />
By default, installation of Wine does not create desktop menus/icons for the software which comes with Wine (e.g. for {{ic|winecfg}}, {{ic|winebrowser}}, etc). However, installing Windows programs with Wine, in most cases, should result in the appropriate menu/desktop icons being created. For example, if the installation program (e.g. {{ic|setup.exe}}) would normally add an icon to your Desktop or "Start Menu" on Windows, then Wine should create corresponding freedesktop.org style {{ic|.desktop}} files for launching your programs with Wine.<br />
<br />
{{Tip|If menu items were ''not'' created while installing software or have been lost, [http://wiki.winehq.org/winemenubuilder winemenubuilder] may be of some use.}}<br />
<br />
If you wish to add on to the menu to create an Ubuntu-like Wine sub-menu, then follow these instructions:<br />
<br />
==== Creating Menu Entries ====<br />
First, install a Windows program using Wine to create the base menu. After the base menu is created, you can start to add the menu entries. In GNOME, right-click on the desktop and select {{ic|"Create Launcher..."}}. The steps might be different for KDE/Xfce. Make three launchers using these settings:<br />
'''Type''': Application<br />
'''Name''': Configuration<br />
'''Command''': winecfg<br />
'''Comment''': Configure the general settings for Wine<br />
<br />
'''Type''': Application<br />
'''Name''': Uninstall Programs<br />
'''Command''': wine uninstaller<br />
'''Comment''': Uninstall Windows programs under Wine properly<br />
<br />
'''Type''': Application<br />
'''Name''': Browse C:\<br />
'''Command''': wine winebrowser c:\\<br />
'''Comment''': Browse the files in the virtual Wine C:\ drive<br />
Now that you have these three launchers on your desktop, it is time to put them into the menu. But, first you should change the launchers to dynamically change icons when a new icon set is installed. To do this, open the launchers that you just made in your favorite text editor. Change the following settings to these new values:<br />
<br />
{{ic|Configuration}} launcher:<br />
Icon[en_US]=wine-winecfg<br />
Icon=wine-winecfg<br />
{{ic|Uninstall Programs}} launcher:<br />
Icon[en_US]=wine-uninstaller<br />
Icon=wine-uninstaller<br />
{{ic|Browse C:\}} launcher:<br />
Icon[en_US]=wine-winefile<br />
Icon=wine-winefile<br />
If these settings produce a ugly/non-existent icon, it means that there are no icons for these launchers in the icon set that you have enabled. You should replace the icon settings with the explicit location of the icon that you want. Clicking the icon in the launcher's properties menu will have the same effect. A great icon set that supports these shortcuts is [http://www.gnome-look.org/content/show.php/GNOME-colors?content=82562 GNOME-colors].<br />
<br />
Now that you have the launchers fully configured, now it is time to put them in the menu. Copy them into {{ic|~/.local/share/applications/wine/}}.<br />
<br />
Wait a second, they are not in the menu yet! There is one last step. Create the following text file: {{hc|~/.config/menus/applications-merged/wine-utilities.menu|<nowiki><br />
<!DOCTYPE Menu PUBLIC "-//freedesktop//DTD Menu 1.0//EN"<br />
"http://www.freedesktop.org/standards/menu-spec/menu-1.0.dtd"><br />
<Menu><br />
<Name>Applications</Name><br />
<Menu><br />
<Name>wine-wine</Name><br />
<Directory>wine-wine.directory</Directory><br />
<Include><br />
<Filename>wine-Configuration.desktop</Filename><br />
</Include><br />
<Include><br />
<Filename>wine-Browse C:\.desktop</Filename><br />
</Include><br />
<Include><br />
<Filename>wine-Uninstall Programs.desktop</Filename><br />
</Include><br />
</Menu><br />
</Menu><br />
</nowiki>}}<br />
Go check in the menu and there should be the minty fresh options waiting to be used!<br />
<br />
==== Remove Wine Launcher Menus in Gnome3 ====<br />
System wide launcher menus are located in {{ic|/usr/share/applications/}}. Remove the program's ".desktop" entry to remove the launcher system wide.<br />
<br />
If this does not solve the problem, it is likely the wine launchers are located in<br />
{{ic|~/.local/share/applications/wine/Programs/}}. In the directories corresponding to the program files are the ".desktop" launcher files. Remove these files to remove the launchers. Remove the entire program's directory to easily remove the launcher files.<br />
<br />
==== KDE 4 Menu Fix[https://bugs.launchpad.net/ubuntu/+source/wine/+bug/263041] ====<br />
The Wine menu items may appear in {{ic|"Lost & Found"}} instead of the Wine menu in KDE 4. This is because {{ic|kde-applications.menu}} is missing the {{ic|MergeDir}} option.<br />
<br />
Edit {{ic|/etc/xdg/menus/kde-applications.menu}}<br />
<br />
At the end of the file add {{ic|<MergeDir>applications-merged</MergeDir>}} after {{ic|<DefaultMergeDirs/>}}, it should look like this:<br />
<Menu><br />
<Include><br />
<And><br />
<Category>KDE</Category><br />
<Category>Core</Category><br />
</And><br />
</Include><br />
<DefaultMergeDirs/><br />
'''<MergeDir>applications-merged</MergeDir>'''<br />
<MergeFile>applications-kmenuedit.menu</MergeFile><br />
</Menu><br />
<br />
Alternatively you can create a symlink to a folder that KDE does see:<br />
ln -s ~/.config/menus/applications-merged ~/.config/menus/kde-applications-merged<br />
<br />
This has the added bonus that an update to KDE won't change it, but is per user instead of system wide.<br />
<br />
== Running Windows Applications ==<br />
{{Warning|Do not run or install Wine applications as root! See [http://wiki.winehq.org/FAQ#run_as_root Running Wine as root] for the official statement.}}<br />
To run a windows application:<br />
$ wine <path to exe><br />
<br />
To install using an MSI installer, use the included msiexec utility:<br />
$ msiexec installername.msi<br />
<br />
== Tips and Tricks ==<br />
{{Tip|In addition to the links provided in the beginning of the article the following may be of interest:<br />
* [http://appdb.winehq.org/ The Wine Application Database (AppDB)] - Information about running specific Windows applications (Known issues, ratings, guides, etc tailored to specific applications)<br />
* [http://forum.winehq.org/ The WineHQ Forums] - A great place to ask questions ''after'' you have looked through the FAQ and AppDB<br />
}}<br />
<br />
These tools will assist in the installation of typical Windows components. In most cases they should be used as a last effort, as it may severely alter your wine configuration.<br />
<br />
=== Installing Microsoft Office ===<br />
<br />
A small tweak is needed to install the office suite. Follow these steps to accomplish it:<br />
<br />
$ WINEARCH=win32 WINEPREFIX=/path/to/wineprefix winecfg<br />
# pacman -S winetricks<br />
$ winetricks msxml3 # For MS Office 2007<br />
$ winetricks msxml3 msxml6 # For MS Office 2010<br />
$ wine /path/to/office_cd/setup.exe<br />
<br />
For additional info, see the [http://appdb.winehq.org/appview.php?iVersionId=4992 WineHQ] article.<br />
<br />
=== OpenGL Modes ===<br />
Many games have an OpenGL mode which ''may'' perform better than their default DirectX mode. While the steps to enable OpenGL rendering is ''application specific'', many games accept the {{Ic|-opengl}} parameter.<br />
$ wine /path/to/3d_game.exe -opengl<br />
<br />
You should of course refer to your application's documentation and Wine's [http://appdb.winehq.org AppDB] for such application specific information.<br />
<br />
=== Using Wine as an interpreter for Win16/Win32 binaries ===<br />
It is also possible to tell the kernel to use wine as an interpreter for all Win16/Win32 binaries.<br />
The process for setting this up depends on whether you boot using [[systemd]] or [[initscripts]].<br />
<br />
==== Systemd ====<br />
Tell the kernel how to interpret Win16 and Win32 binaries:<br />
echo ':DOSWin:M::MZ::/usr/bin/wine:' > /proc/sys/fs/binfmt_misc/register<br />
To make the setting permanent, create a configuration file in {{ic|/etc/tmpfiles.d}} with the following contents:<br />
{{hc|/etc/tmpfiles.d/enable-doswin-exe.conf|<br />
w /proc/sys/fs/binfmt_misc/register - - - - :DOSWin:M::MZ::/usr/bin/wine:}}<br />
<br />
Note that, in contrast to initscripts,<br />
systemd will automatically mount {{ic|/proc/sys/fs/binfmt_misc}} on use by default.<br />
Thus adding the tmpfiles rule should be sufficient for most users.<br />
<br />
For more info on tmpfiles, see [[Systemd#Temporary_files]].<br />
<br />
==== Initscripts ====<br />
First mount the {{ic|binfmt_misc}} filesystem:<br />
# mount -t binfmt_misc none /proc/sys/fs/binfmt_misc<br />
Or you can add this line to your {{ic|/etc/fstab}}:<br />
none /proc/sys/fs/binfmt_misc binfmt_misc defaults 0 0<br />
Then, tell the kernel how to interpret Win16 and Win32 binaries:<br />
echo ':DOSWin:M::MZ::/usr/bin/wine:' > /proc/sys/fs/binfmt_misc/register<br />
You can add this line to {{ic|/etc/rc.local}} to make this setting permanent.<br />
In this case you may want to ignore stderr to avoid error messages when changing runlevels:<br />
{ echo ':DOSWin:M::MZ::/usr/bin/wine:' > /proc/sys/fs/binfmt_misc/register; } 2>/dev/null<br />
<br />
==== Test the Setup ====<br />
Now try to run a Windows program:<br />
chmod 755 exefile.exe<br />
./exefile.exe<br />
<br />
If all went well, exefile.exe should run.<br />
<br />
=== Wineconsole ===<br />
<br />
Often you may need to run {{ic|.exes}} to patch game files, for example a widescreen mod for an old game, and running the {{ic|.exe}} normally through wine might yield nothing happening. In this case, you can open a terminal and run the following command:<br />
<br />
$ wineconsole cmd<br />
<br />
Then navigate to the directory and run the {{ic|.exe}} file from there.<br />
<br />
=== Winetricks ===<br />
[http://wiki.winehq.org/winetricks Winetricks] is a script to allow one to install base requirements needed to run Windows programs. Installable components include DirectX 9.x, MSXML (required by Microsoft Office 2007 and Internet Explorer), Visual Runtime libraries and many more.<br />
<br />
You can install {{pkg|winetricks}} via [[pacman]] or use the {{AUR|winetricks-svn}} package available in the [[AUR]]. Then run it with:<br />
$ winetricks<br />
<br />
== Third-party interfaces ==<br />
These have their own sites, and are not supported in the Wine forums.<br />
=== CrossOver ===<br />
[http://www.codeweavers.com/about/ CrossOver] Has its own [[CrossOver|wiki page]].<br />
=== PlayOnLinux/PlayOnMac ===<br />
[http://www.playonlinux.com/ PlayOnLinux] is a graphical Windows and DOS program manager. It contains scripts to assist the configuration and running of programs, it can manage multiple Wine versions and even use a specific version for each executable (eg. because of regressions). If you need to know which Wine version works best for a certain game, try the [http://appdb.winehq.org/ Wine Application Database]. You can find the {{Pkg|playonlinux}} package in [[community]].<br />
<br />
=== PyWinery ===<br />
[http://code.google.com/p/pywinery/ PyWinery] is a graphical and simple wine-prefix manager which allows you to launch apps and manage configuration of separate prefixes, also have a button to open winetricks in the same prefix, to open prefix dir, {{ic|winecfg}}, application uninstaller and wineDOS. You can install [https://aur.archlinux.org/packages.php?ID=48382 PyWinery from AUR]. It is especially useful for having differents settings like DirectX games, office, programming, etc, and choose which prefix to use before you open an application or file.<br />
<br />
It's recommended using winetricks by default to open {{ic|.exe}} files, so you can choose between any wine configuration you have.<br />
<br />
=== Q4wine ===<br />
[http://q4wine.brezblock.org.ua/ Q4Wine] is a graphical wine-prefix manager which allows you to manage configuration of prefixes. Notably it allows exporting QT themes into the wine configuration so that they can integrate nicely. You can find the {{Pkg|q4wine}} package in [[multilib]].<br />
<br />
== External Resources ==<br />
* [http://www.winehq.com/ Official Wine Website]<br />
* [http://appdb.winehq.org/ Wine Application Database]<br />
* [http://linuxgamingtoday.wordpress.com/2008/02/16/quick-tips-to-speed-up-your-gaming-in-wine/ Advanced configuring your gfx card and OpenGL settings on wine; Speed up wine]<br />
* [http://wiki.gotux.net/code:perl:fileinfo FileInfo] - Find Win32 PE/COFF headers in EXE/DLL/OCX files under linux/unix environment.</div>CabronDeOzhttps://wiki.archlinux.org/index.php?title=MATE&diff=246472MATE2013-02-05T20:41:35Z<p>CabronDeOz: /* GTK3 Applications Not Properly Styled */ Spelling correction.</p>
<hr />
<div>[[Category:Desktop environments]]<br />
[[es:MATE]]<br />
[[it:MATE]]<br />
[[ja:MATE]]<br />
[[ko:MATE]]<br />
[[ru:MATE]]<br />
[[zh-CN:MATE]]<br />
{{Article summary start}}<br />
{{Article summary text|What is MATE and how to get it.}}<br />
{{Article summary heading|Required software}}<br />
{{Article summary link|MATE|http://mate-desktop.org}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|GNOME}}<br />
{{Article summary end}}<br />
<br />
The '''MATE Desktop Environment''' is a fork of GNOME 2 that aims to provide an attractive and intuitive desktop to Linux users using traditional metaphors. For more information, see [https://bbs.archlinux.org/viewtopic.php?id=121162 this forum thread.]<br />
<br />
== Obtaining ==<br />
<br />
MATE is currently developed on [https://github.com/mate-desktop GitHub].<br />
Stable packages with release-based version numbering are hosted on http://repo.mate-desktop.org/archlinux/.<br />
<br />
== Installation ==<br />
<br />
To install the stable version of MATE via [[pacman]] add the following lines to your {{ic|/etc/pacman.conf}}:<br />
<br />
{{bc|<nowiki><br />
[mate]<br />
Server = http://repo.mate-desktop.org/archlinux/$arch<br />
</nowiki>}}<br />
<br />
Run<br />
<br />
# pacman -Syy<br />
<br />
and then<br />
<br />
# pacman -S mate<br />
<br />
It might also be of interest to people to install certain packages from the '''mate-extras''' group (most being counterparts to packages in the {{Grp|gnome-extra}} group):<br />
<br />
# pacman -S mate-extras<br />
<br />
You are very likely to get file conflicts when installing. Simply rename the offending files or install with the {{ic|--force}} flag. You will also require [[dbus]].<br />
<br />
{{note|Currently, many MATE packages do not provide, conflict with or replace any GNOME packages.}}<br />
<br />
== Starting ==<br />
<br />
=== Manually ===<br />
<br />
In order to start MATE manually, you must add<br />
<br />
exec mate-session<br />
<br />
to your {{ic|[[xinitrc|~/.xinitrc]]}} file and then run<br />
<br />
$ startx<br />
<br />
{{note|See [[xinitrc]] for details, such as preserving the logind (and/or consolekit) session.}}<br />
<br />
=== Automatically at boot time ===<br />
<br />
See [[Display Manager]] and [[Start X at Boot]] for details.<br />
<br />
==== GDM (Old) ====<br />
<br />
If you are using {{AUR|gdm-old}} from the AUR, simply select the MATE session from the Sessions list. For your first time launching MATE, make sure to click "Just this session" when prompted.<br />
<br />
==== [[LightDM]], [[GDM]] & [[LXDM]] ====<br />
<br />
Just select MATE from the Sessions list. Works well.<br />
<br />
==== MATE Display Manager ====<br />
<br />
The MATE Display Manager (MDM) is the MATE desktop's counterpart to the GNOME Display Manager (GDM). It's package 'mate-display-manager' has been found in the '''mate-extra''' group or in the AUR package {{AUR|mate-display-manager}}. It has worked relatively the same as GDM does/did; unfortunately, the subproject is currently in flux, and MDM is not now (2012/07/01) available.<br />
<br />
==== [[KDM]] ====<br />
<br />
In order to be able to launch MATE from [[KDM]], the [[KDE]] Display Manager, you have to edit the KDM configuration.<br />
As root, edit the <code>/usr/share/config/kdm/kdmrc</code> configuration file. Find the '''SessionsDir''' parameter and add <code>/usr/share/xsessions</code> to the list.<br />
It should then look like this:<br />
<br />
SessionsDirs=/usr/share/config/kdm/sessions,/usr/share/apps/kdm/sessions,/usr/share/xsessions<br />
<br />
Restart KDM and select the "MATE session" from the list.<br />
<br />
==== [[SLIM]] ====<br />
<br />
Just fоllow the [[SLIM]] tutorial to know how to install and how to copy and use the .xinitrc file. And just add this line to the .xinitrc file :<br />
exec mate-session<br />
<br />
== Applications ==<br />
<br />
It is important to note that many GNOME core applications are rebranded for MATE, as per the licensing terms. Here is a simple Rosetta Stone of GNOME -> MATE applications. <br />
<br />
* Nautilus is renamed '''Caja'''<br />
* Metacity is renamed '''Marco'''<br />
* Gconf is renamed '''Mate-conf''' <br />
* Gedit is renamed '''Pluma'''<br />
* Eye of GNOME is renamed '''Eye of MATE''' <br />
* Evince is renamed '''Atril''' <br />
* File Roller is renamed '''Engrampa''' <br />
* GNOME Terminal is renamed '''MATE Terminal''' <br />
<br />
Other applications and core components prefixed with GNOME (such as GNOME Panel, GNOME Menus etc) have simply had the prefix renamed "MATE" and become MATE Panel and MATE Menus.<br />
<br />
Not all of the GNOME extra applications (built for GTK2) have been forked yet. The following extra applications '''are''' available in MATE:<br />
<br />
* Totem (mate-video-player)<br />
* GNOME Panel applets (mate-applets)<br />
<br />
If you are using NetworkManager to connect to the internet, you can install {{AUR|network-manager-applet-gtk2}} from the AUR for a GTK2 nm-applet. You will need to modify the PKGBUILD to depend on mate-bluetooth rather than gnome-bluetooth to prevent a recursive dependency on gnome-desktop.<br />
<br />
== Known issues ==<br />
<br />
=== Qt Applications are not styled ===<br />
<br />
You may find that Qt4 applications are not inheriting the GTK2 theme like they should. This can be fixed easily by running qtconfig and setting GTK+ as GUI style under System ⇒ Preferences ⇒ QT4 Settings.<br />
<br />
=== Evolution Email Not Working ===<br />
<br />
Please see [[Evolution#Using_Evolution_Outside_Of_Gnome]].<br />
<br />
=== GTK3 Applications Not Properly Styled ===<br />
<br />
If you notice that applications such as [[Rhythmbox]] do not have styling applied to them, try [https://aur.archlinux.org/packages/clearlooks-phenix-gtk-theme-git/ Clearlooks Phenix] theme.<br />
<br />
== Troubleshooting ==<br />
<br />
=== User Switch ===<br />
<br />
If you are not using MDM (Mate Display Manager) user switch is disabled, to enable create the symbolic links.<br />
<br />
==== [[LightDM]] ====<br />
<br />
# ln -s /usr/lib/lightdm/lightdm/gdmflexiserver /usr/bin/mdmflexiserver<br />
<br />
==== [[GDM]] ====<br />
<br />
# ln -s /usr/bin/gdmflexiserver /usr/bin/mdmflexiserver</div>CabronDeOzhttps://wiki.archlinux.org/index.php?title=MATE&diff=246470MATE2013-02-05T20:07:00Z<p>CabronDeOz: Felt it necessary to include information about a Clearlooks Fenix theme which works with GTK2 and 3 apps.</p>
<hr />
<div>[[Category:Desktop environments]]<br />
[[es:MATE]]<br />
[[it:MATE]]<br />
[[ja:MATE]]<br />
[[ko:MATE]]<br />
[[ru:MATE]]<br />
[[zh-CN:MATE]]<br />
{{Article summary start}}<br />
{{Article summary text|What is MATE and how to get it.}}<br />
{{Article summary heading|Required software}}<br />
{{Article summary link|MATE|http://mate-desktop.org}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|GNOME}}<br />
{{Article summary end}}<br />
<br />
The '''MATE Desktop Environment''' is a fork of GNOME 2 that aims to provide an attractive and intuitive desktop to Linux users using traditional metaphors. For more information, see [https://bbs.archlinux.org/viewtopic.php?id=121162 this forum thread.]<br />
<br />
== Obtaining ==<br />
<br />
MATE is currently developed on [https://github.com/mate-desktop GitHub].<br />
Stable packages with release-based version numbering are hosted on http://repo.mate-desktop.org/archlinux/.<br />
<br />
== Installation ==<br />
<br />
To install the stable version of MATE via [[pacman]] add the following lines to your {{ic|/etc/pacman.conf}}:<br />
<br />
{{bc|<nowiki><br />
[mate]<br />
Server = http://repo.mate-desktop.org/archlinux/$arch<br />
</nowiki>}}<br />
<br />
Run<br />
<br />
# pacman -Syy<br />
<br />
and then<br />
<br />
# pacman -S mate<br />
<br />
It might also be of interest to people to install certain packages from the '''mate-extras''' group (most being counterparts to packages in the {{Grp|gnome-extra}} group):<br />
<br />
# pacman -S mate-extras<br />
<br />
You are very likely to get file conflicts when installing. Simply rename the offending files or install with the {{ic|--force}} flag. You will also require [[dbus]].<br />
<br />
{{note|Currently, many MATE packages do not provide, conflict with or replace any GNOME packages.}}<br />
<br />
== Starting ==<br />
<br />
=== Manually ===<br />
<br />
In order to start MATE manually, you must add<br />
<br />
exec mate-session<br />
<br />
to your {{ic|[[xinitrc|~/.xinitrc]]}} file and then run<br />
<br />
$ startx<br />
<br />
{{note|See [[xinitrc]] for details, such as preserving the logind (and/or consolekit) session.}}<br />
<br />
=== Automatically at boot time ===<br />
<br />
See [[Display Manager]] and [[Start X at Boot]] for details.<br />
<br />
==== GDM (Old) ====<br />
<br />
If you are using {{AUR|gdm-old}} from the AUR, simply select the MATE session from the Sessions list. For your first time launching MATE, make sure to click "Just this session" when prompted.<br />
<br />
==== [[LightDM]], [[GDM]] & [[LXDM]] ====<br />
<br />
Just select MATE from the Sessions list. Works well.<br />
<br />
==== MATE Display Manager ====<br />
<br />
The MATE Display Manager (MDM) is the MATE desktop's counterpart to the GNOME Display Manager (GDM). It's package 'mate-display-manager' has been found in the '''mate-extra''' group or in the AUR package {{AUR|mate-display-manager}}. It has worked relatively the same as GDM does/did; unfortunately, the subproject is currently in flux, and MDM is not now (2012/07/01) available.<br />
<br />
==== [[KDM]] ====<br />
<br />
In order to be able to launch MATE from [[KDM]], the [[KDE]] Display Manager, you have to edit the KDM configuration.<br />
As root, edit the <code>/usr/share/config/kdm/kdmrc</code> configuration file. Find the '''SessionsDir''' parameter and add <code>/usr/share/xsessions</code> to the list.<br />
It should then look like this:<br />
<br />
SessionsDirs=/usr/share/config/kdm/sessions,/usr/share/apps/kdm/sessions,/usr/share/xsessions<br />
<br />
Restart KDM and select the "MATE session" from the list.<br />
<br />
==== [[SLIM]] ====<br />
<br />
Just fоllow the [[SLIM]] tutorial to know how to install and how to copy and use the .xinitrc file. And just add this line to the .xinitrc file :<br />
exec mate-session<br />
<br />
== Applications ==<br />
<br />
It is important to note that many GNOME core applications are rebranded for MATE, as per the licensing terms. Here is a simple Rosetta Stone of GNOME -> MATE applications. <br />
<br />
* Nautilus is renamed '''Caja'''<br />
* Metacity is renamed '''Marco'''<br />
* Gconf is renamed '''Mate-conf''' <br />
* Gedit is renamed '''Pluma'''<br />
* Eye of GNOME is renamed '''Eye of MATE''' <br />
* Evince is renamed '''Atril''' <br />
* File Roller is renamed '''Engrampa''' <br />
* GNOME Terminal is renamed '''MATE Terminal''' <br />
<br />
Other applications and core components prefixed with GNOME (such as GNOME Panel, GNOME Menus etc) have simply had the prefix renamed "MATE" and become MATE Panel and MATE Menus.<br />
<br />
Not all of the GNOME extra applications (built for GTK2) have been forked yet. The following extra applications '''are''' available in MATE:<br />
<br />
* Totem (mate-video-player)<br />
* GNOME Panel applets (mate-applets)<br />
<br />
If you are using NetworkManager to connect to the internet, you can install {{AUR|network-manager-applet-gtk2}} from the AUR for a GTK2 nm-applet. You will need to modify the PKGBUILD to depend on mate-bluetooth rather than gnome-bluetooth to prevent a recursive dependency on gnome-desktop.<br />
<br />
== Known issues ==<br />
<br />
=== Qt Applications are not styled ===<br />
<br />
You may find that Qt4 applications are not inheriting the GTK2 theme like they should. This can be fixed easily by running qtconfig and setting GTK+ as GUI style under System ⇒ Preferences ⇒ QT4 Settings.<br />
<br />
=== Evolution Email Not Working ===<br />
<br />
Please see [[Evolution#Using_Evolution_Outside_Of_Gnome]].<br />
<br />
=== GTK3 Applications Not Properly Styled ===<br />
<br />
If you notice that applications such as [[Rhythmbox]] do not have styling applied to them, try [https://aur.archlinux.org/packages/clearlooks-phenix-gtk-theme-git/ Clearlooks Fenix] theme.<br />
<br />
== Troubleshooting ==<br />
<br />
=== User Switch ===<br />
<br />
If you are not using MDM (Mate Display Manager) user switch is disabled, to enable create the symbolic links.<br />
<br />
==== [[LightDM]] ====<br />
<br />
# ln -s /usr/lib/lightdm/lightdm/gdmflexiserver /usr/bin/mdmflexiserver<br />
<br />
==== [[GDM]] ====<br />
<br />
# ln -s /usr/bin/gdmflexiserver /usr/bin/mdmflexiserver</div>CabronDeOz