*'''compiz-decorator-gtk''' - This decorator is included in the {{AUR|compiz-pure}}, {{AUR|compiz}} and {{AUR|compiz-xfce}} packages. If you are installing the {{AUR|compiz-core}} package you can install ''compiz-decorator-gtk'' seperately from the {{AUR|compiz-decorator-gtk-no-gnome}} package. For those installing the 0.9.x branch, ''compiz-decorator-gtk'' is included in the {{AUR|compiz-bzr}} and {{AUR|compiz-dev}} packages. This decorator can use Metacity or Cairo themes.

*'''compiz-decorator-gtk''' - This decorator is included in the {{AUR|compiz-pure}}, {{AUR|compiz}} and {{AUR|compiz-xfce}} packages. If you are installing the {{AUR|compiz-core}} package you can install ''compiz-decorator-gtk'' seperately from the {{AUR|compiz-decorator-gtk-no-gnome}} package. For those installing the 0.9.x branch, ''compiz-decorator-gtk'' is included in the {{AUR|compiz-bzr}} and {{AUR|compiz-dev}} packages. This decorator can use Metacity or Cairo themes.

−

*'''kde-window-decorator''' - The {{AUR|compiz}} package contains both the ''compiz-decorator-gtk'' and ''kde-window-decorator'' window decorators. The kde-window-decorator requires the {{pkg|kdebase-workspace}} package which pulls in a number of KDE dependencies. Therefore it may not be the best solution in non KDE environments. If you are installing the 0.9x branch and wish to use the ''kde-window-decorator'' modify the [[PKGBUILD]] of the package you are using and set {{ic|KDEWINDOWDECORATOR}} to {{ic|"on"}}. This decorator uses the current Kwin theme.

+

*'''kde-window-decorator''' - The {{AUR|compiz}} package contains both the ''compiz-decorator-gtk'' and ''kde-window-decorator'' window decorators. The kde-window-decorator requires the {{pkg|kdebase-workspace}} package which pulls in a number of KDE dependencies. Therefore it may not be the best solution in non KDE environments. If you are installing the 0.9.x branch and wish to use the ''kde-window-decorator'' modify the [[PKGBUILD]] of the package you are using and set {{ic|KDEWINDOWDECORATOR}} to {{ic|"on"}}. This decorator uses the current Kwin theme.

== Starting the window decorator ==

== Starting the window decorator ==

Revision as of 11:02, 29 January 2014

Compiz is a compositing window manager. It can replace the native window managers in desktop environments such as MATE and KDE. The first version of Compiz was released in 2006. In September 2006 several changes proposed for Compiz were rejected by the Compiz team. This led to the formation of Beryl - a fork of Compiz. In 2007 the Compiz and Beryl communities merged and Compiz was split into two projects: 'compiz-core' (the window manager) and 'compiz-fusion' (the decorator and plugins). In 2009 the two projects merged into a single unified project and the 'fusion' name was dropped. There are currently two branches of Compiz: the older 0.8.x branch which is written in C and the newer 0.9.x branch which is written in C++.

Installation

As of May 2013 Compiz is no longer available in the Official repositories. There are a number of packages in the AUR which can provide a full Compiz experience. The packages listed in this section are known to provide a working Compiz configuration. Other Compiz packages are also available.

Note: There is some debate over which branch is considered stable. Canonical declared the 0.9.x branch to be stable from version 0.9.7 onwards but some maintain that 0.9.x is a development branch and that 0.8.x is still the stable version until a 1.x branch is released.

Installing the 0.9.x branch

Install one of the following two packages:

compiz-devAUR - This package provides the latest stable release of the 0.9.x branch. It includes the window manager, decorator, settings panel and plugins.

compiz-bzrAUR - This package provides the latest development version of the 0.9.x branch. It includes the window manager, decorator, settings panel and plugins.

compizAUR - This package contains the Compiz window manager and both the compiz-decorator-gtk and kde-window-decorator window decorators.

compiz-xfceAUR - This package includes the Compiz window manager, compiz-decorator-gtk, settings panel and plugins. It is optimised for the Xfce desktop. The packages below are not required if you install this package.

fusion-iconAUR - a tray applet that starts compiz and can load different window managers and decorators during a session

compiz-mateAUR - a plugin for greater integration with the MATE desktop

Note:

The compiz-mate and compiz-xfce packages are not required for Compiz to function in either desktop.

The 0.8.x branch has not been updated for some time and is unlikely to be updated in the future as all work is concentrated on the 0.9.x branch.

Installing a window decorator

Unlike window managers such as mutter, Kwin or Xfwm, Compiz does not provide a window decorator so you will need to install one yourself. Depending on which packages you used to install Compiz you may have a window decorator included already. There are three main decorators used with Compiz:

Emerald - This decorator can be installed from the emeraldAUR package in the AUR. It has a number of themes available and supports various effects. You may also wish to install the emerald-themesAUR package which contains a number of extra themes for emerald. If you are installing the 0.9.x branch from the compiz-bzrAUR package then install the emerald-gitAUR package to use Emerald with Compiz 0.9.x.

kde-window-decorator - The compizAUR package contains both the compiz-decorator-gtk and kde-window-decorator window decorators. The kde-window-decorator requires the kdebase-workspace package which pulls in a number of KDE dependencies. Therefore it may not be the best solution in non KDE environments. If you are installing the 0.9.x branch and wish to use the kde-window-decorator modify the PKGBUILD of the package you are using and set KDEWINDOWDECORATOR to "on". This decorator uses the current Kwin theme.

Starting the window decorator

Whist the appearance of the windows and their contents is a function of GTK+ and Qt, the frames around the windows are controlled by the Window Decoration plugin. To use it make sure you have a window decorator installed - see above. In a terminal enter ccsm. In the panel, ensure that the 'Window Decoration' plugin is enabled in CCSM's 'Effects' tab. Click on the 'Window Decoration' button and in the 'Command' field enter the relevant command for your decorator - see below:

To set emerald as your default window decorator use:

$ emerald --replace

The emerald-theme-manager command will open a GUI for managing Emerald themes.

To set the kde-window-decorator as your default window decorator use:

$ kde4-window-decorator --replace

To set compiz-decorator-gtk as your default window decorator use:

$ gtk-window-decorator --replace

Note:

You must activate important plugins to provide basic window manager behaviour or else you will have no ability to drag, scale or close any windows as soon as Compiz is activated. Among those plugins are 'Window Decoration' under 'Effects' and 'Move Window' & 'Resize Window' under 'Window Management.' These can be enabled with ccsm.

If you are using fusion-icon there is no need to set the command in CCSM as fusion-icon will do this automatically.

Starting Compiz

With fusion-icon

You can launch fusion-icon with the following command:

$ fusion-icon

To enable fusion-icon on startup you need to autostart it. Refer to the Autostarting article and your desktop environment's article for further instruction.

Right click on the icon in the panel and go to 'select window manager'. Choose 'Compiz' if it isn't selected already.

Note:

Using fusion-icon means that the native window manager will be loaded first which will then be replaced by Compiz.

It is uncertain whether fusion-icon is compatible with the 0.9.x branch.

Without fusion-icon

You can start Compiz using the following command:

$ compiz --replace ccp &

See below for desktop environment specific instructions on how to start Compiz automatically without fusion-icon.

A quick overview over common Compiz command-line options:

--indirect-rendering: use indirect-rendering (AIGLX)

--loose-binding: can help performance issues (NVIDIA?)

--replace: replace current window-manager

--keep-window-hints: keep the gnome window manager gconf-settings for available viewports

--sm-disable: disable session-management

ccp: the 'ccp' command loads the last configured settings from CCSM (CompizConfig Settings Manager) otherwise Compiz will load with no settings and you won't be able to do anything with your windows like dragging, maximizing/minimizing, or moving.

Starting Compiz automatically without fusion-icon

Methods which involve starting the native window manager and then replacing it with Compiz have been indicated as such.

Note: If compiz.desktop already exists, you may have to add --replace and/or ccp to the Exec variable. Without --replace, Compiz won't load since it will detect another window manager already loaded. Without ccp, Compiz will not load any of the settings and plugins that you have enabled through CompizConfig Settings Manager (ccsm) and you won't be able to manipulate any of your windows.

Export KDEWM

As root you must create a short script. This will allow you to load Compiz with extra switches as doing it directly via $ export KDEWM="compiz --replace ccp --sm-disable" may not work.

Create the file with the necessary text by using the command below:

$ echo "compiz --replace ccp --sm-disable &" > /usr/bin/compiz-fusion

Ensure that /usr/bin/compiz-fusion has executable (+x) permissions.

$ chmod +x /usr/bin/compiz-fusion

Choose one of the following:

1) For your user only:

~/.kde4/env/compiz.sh

KDEWM="compiz-fusion"

2) System-wide:

/etc/kde/env/compiz.sh

KDEWM="compiz-fusion"

Note:

If the above method does not work, an alternate approach is to include the line:

$ export KDEWM="compiz-fusion"

in your user's ~/.bashrc file.

If you optionally use the /usr/local/bin directory it may not work. In that case you should export the script including the whole path:

$ export KDEWM="/usr/local/bin/compiz-fusion"

GNOME

GNOME Shell

GNOME Shell is set up as a plugin of the mutter window manager. This means that it is impossible to use GNOME Shell with Compiz or any other window manager.

Warning: If you have another desktop environment installed alongside GNOME Shell and you are starting Compiz in that environment using a 'session-properties' dialogue or similar program ensure that the Compiz entry is disabled when using GNOME Shell as it could cause the shell to crash or freeze.

GNOME Flashback

Click on the add button and in the command section enter the compiz --replace ccp & command. The name and comment sections are unimportant and are just there to indicate what the entry does. Log out and log in again and Compiz should start.

Note:

This method will mean that metacity starts first and is then replaced by Compiz.

You can also use this method to start fusion-icon.

MATE

Using gsettings

Use the following gsettings command to change the default window manager from marco to Compiz.

Using mate-session-properties

Another approach is to start Compiz using mate-session-properties. In a terminal enter the command:

$ mate-session-properties

Click on the add button and in the command section enter the compiz --replace ccp & command. The name and comment sections are unimportant and are just there to indicate what the entry does. Log out and log in again and Compiz should start.

Note:

The first method will mean that only Compiz is started. The second method means that marco is started first and is then replaced by Compiz.

You can also use the second method to start fusion-icon.

Xfce

Modifying the failsafe session

To configure the default/failsafe session of Xfce, edit the ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml or (to make the change for all Xfce users) /etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml:

Tip: When logging out after this edit ensure that the 'Save session for future logins' option in the logout dialogue is unticked. Once Compiz has started you can then tick the option again.

Using Xfce Application Autostart

In the Xfce main menu navigate to 'Settings' and click on 'Session and Startup.' Click on the 'Application Autostart' tab. Click the add button and in the command section enter the compiz --replace ccp & command. The name and comment sections are unimportant and are just there to indicate what the entry does. Log out and log in again and Compiz should start.

Note:

The first method will mean that only Compiz is started. The second method means that xfwm4 is started first and is then replaced by Compiz.

You can also use the second method to start fusion-icon.

Using Compiz as a standalone window manager

To start Compix configure .xinitrc to launch Compiz as:

~/.xinitrc

exec compiz ccp

You can also use fusion icon as shown below:

~/.xinitrc

exec fusion-icon

However chances are you will need additional apps (e.g a panel) for optimal usability. Below is an example of a ~/.xinitrc file which starts Compiz (through fusion-icon), the tint2 panel and the Cairo dock.

~/.xinitrc

tint2 &
cairo-dock &
exec fusion-icon

Add a root menu

To add a root menu similar to that in Openbox and other standalone window managers you must install the package compiz-deskmenuAUR.
Upon a restart of Compiz, you should be able to middle click on your desktop to launch the menu.

If it does not automatically work, enter the CompizConfig Settings Manager, and in the Commands plugin section, within the 'General' tab, ensure that there is a command to launch Compiz-Deskmenu, and the appropriate key binding is set to Ctrl+Space.

If it still does not work, enter the Viewport Switcher menu, and change 'Plugin for initiate action' to 'commands', and 'Action name for initiate' to run_command0_key.

Allow users to shutdown/reboot

If you are using policykit you can add the command to CCSM > General > Commands and assign a short-cut key to it or alternatively you can use a launcher application. See here for further information.

Tips and tricks

Fallback

If you are using KDE, GNOME or Xfce and you are experiencing problems, for example you don’t see borders for your window, you can switch back to the default DE window manager with this command:

wm_name --replace

with kwin, metacity or xfwm4 instead of wm_name.

Keyboard shortcuts

Below is a list of the default keyboard shortcuts for Compiz. The 'Commands' plugin needs to be activated in the CCSM panel.

Switch windows = Alt+Tab.

Switch to next desktops = Ctrl+Alt+←.

Switch to previous desktop = Ctrl+Alt+→.

Move window = Alt+Left click.

Resize window = Alt+Right click.

A more detailed list can be found under CommonKeyboardShortcuts in the Compiz wiki or you can always just look at your plugin's configuration.

Enable window snapping in Compiz

If you want to compare two windows side by side by dragging them to the edges of the screen, similar to the 'Aero Snap' feature introduced in Windows 7, enable the 'Grid' plugin in ccsm. If you are using the 'Desktop Wall' or 'Rotate Cube' plugin then disable the 'Edge Flip' options in that plugin's section to ensure that windows do not move to the next desktop when dragged to the screen edge.

Tip: The plugin in ccsm labelled 'Snapping Windows' merely adds resistance to the edges of the screen. It does not resize windows that are dragged to the screen edge.

Troubleshooting

No Alt-F2 run dialog in MATE

If you are using Compiz in MATE follow the instructions below to restore the Alt-F2 run dialog.

Start ccsm. Ensure that the 'Commands' plugin is ticked. Click on the 'Commands' button and enter the following command in a free command line box e.g. 'Command line 0'

mate-panel --run-dialog

Then click on the 'Key Bindings' tab. Click on the button labelled 'Disabled' for the appropriate command line box e.g. if you entered the command in 'Command line 0' click the 'Disabled' box adjacent to 'Run command 0.' In the box that appears tick the 'Enabled' option. Then click the 'Grab key combination' button and hit Alt-F2. Click 'Ok.'

Tip: If the Alt-F2 run dialog window is always launched out of focus then start ccsm, click on 'General Options' and click on the 'Focus & Raise Behaviour' tab. Change the 'Focus Prevention Level' setting to 'Off.'

Missing GLX_EXT_texture_from_pixmaps

On ATI cards (first solution)

If you run into the following error when trying to run Compiz on an ATI card:

Missing GLX_EXT_texture_from_pixmap

This is because Compiz's binary was compiled against Mesa's OpenGL library rather than ATI's OpenGL library (which is what you are using).

copy the library into a directory to keep it because ATI's drivers will over write it.

$ install -Dm644 /usr/lib/libGL.so.1.2 /usr/lib/mesa/libGL.so.1.2

Once you have it copied, you can reinstall your fglrx drivers. Now you can start Compiz using the following example syntax:

LD_PRELOAD=/usr/lib/mesa/libGL.so.1.2 compiz --replace &

On ATI cards (second solution)

Another problem that could arise is with 'GLX_EXT_texture_from_pixmap.' it is possible that the card could only render it indirectly. If so, you have to pass the option to your libgl as shown below:

Compiz starts without window borders with NVIDIA binary drivers

Firstly ensure that you have configured the settings discussed here correctly. If window borders still do not start try adding Option "AddARGBGLXVisuals" "True" and Option "DisableGLXRootClipping" "True" to your "Screen" section in the config file if you are using the NVIDIA binary driver. If you used any other Options elsewhere in /etc/X11/xorg.conf.d/ to get Compiz working and still have no luck, try commenting them out and using only the aformentioned ARGBGLXVisuals and GLXRootClipping Options.

Blank screen on resume from suspend-to-ram using the NVIDIA binary drivers

If you receive a blank screen with a responsive cursor upon resume, try disabling sync to vblank:

the problem is with the permission on ~/.config/compiz/. To fix it, use:

# chown -R <username> /home/<username>/.config/compiz/

Poor performance from capable graphics cards

If everything is configured correctly but you still have poor performance with some effects, try disabling CCSM > General Options > Display Settings > Detect Refresh Rate and instead choose a value manually. This workaround has been tested on both NVIDIA and Intel chips.

NVIDIA Chips Only: The inadequate refresh rate with 'Detect Refresh Rate' may be due to an option called 'DynamicTwinView' being enabled by default which plays a factor in accurately reporting the maximum refresh rate that your card and display support. You can disable 'DynamicTwinView' by adding the following line to the "Device" or "Screen" section of your /etc/X11/xorg.conf.d/*.conf, and then restarting your computer: