# Compiz

Related articles

- Compiz Configuration
- Window manager
- Desktop environment
- Xfce
- MATE
- Unity

According to Wikipedia:

  Compiz is a compositing window manager for the X Window System, using 3D graphics hardware to create fast compositing desktop effects for window management. Effects, such as a minimization animation or a cube workspace, are implemented as loadable plugins.

## Installation

As of May 2013, Compiz is no longer available in the official repositories. Packages for installing both the 0.9 and 0.8 series are available in the AUR. The two series are not parallel installable - trying to install packages from both series will lead to conflicts.

### Installing the 0.9 series

Tip: From Compiz 0.9.8 onwards, all Compiz components (e.g. CCSM, Plugins) are developed and distributed as a single project. This means that a single package can provide all of the Compiz components.

Install one of the following three packages:

- compiz-core-devel - This package provides the latest milestone release of the 0.9 series, (window manager, CCSM, plugins and gtk-window-decorator are included).
- compiz-core-bzr - This package provides the latest development version of the 0.9 series, (window manager, CCSM, plugins and gtk-window-decorator are included).
- compiz-ubuntu - This package provides a snapshot of the latest development version with patches for optimal integration with the Unity desktop, (window manager, CCSM, plugins and gtk-window-decorator are included).

The following packages are optional:

- emerald0.9 - A standalone window decorator for Compiz.
- emerald-git - A standalone window decorator for Compiz, (git version).
- emerald-themes - Extra themes for the Emerald decorator.

### Installing the 0.8 series

Install one of the following four packages/package groups:

- compiz-core - This package provides the window manager.
- compiz-gtk-standalone - This package provides the window manager and the gtk-window-decorator.
- compiz-xfce - This package is a meta package which provides a Compiz install with optimal settings for the Xfce desktop. It depends on compiz-gtk-standalone.
- compiz-core-mate and compiz-decorator-gtk - These two packages are part of the compiz-mate base package - a package which provides a Compiz install with optimal settings for the MATE desktop. The former package provides the window manager and the latter package provides the gtk-window-decorator.

The following packages provide CCSM and the Compiz plugins. It is strongly recommended that you install these packages:

- ccsm - The CompizConfig Settings Manager, a settings panel for Compiz.
- compizconfig-python - Compizconfig bindings for python (required by CCSM).
- libcompizconfig - Compiz configuration system library (required by compizconfig-python).
- compiz-fusion-plugins-main - Core plugins for Compiz.
- compiz-fusion-plugins-extra - Extra plugins for Compiz.
- compiz-bcop - Compiz option code generator (required by all compiz-fusion-plugins).

The following packages are optional:

- compiz-fusion-plugins-unsupported - Unsupported plugins for Compiz.
- fusion-icon - A tray applet that starts Compiz and can load different window managers and decorators during a session.
- simple-ccsm - Provides a simplified mode for configuring settings in CCSM.
- emerald - A standalone window decorator for Compiz.
- emerald-themes - Extra themes for the Emerald decorator.

### Setting the default window decorator

Tip: For information on selecting and managing themes, see: Compiz Configuration#Window decoration themes.
Note: Currently, no package provides the kde-window-decorator by default. To install it, you will need to edit the PKGBUILD of the package you used to install Compiz and enable the relevant option. Once you have done so, rebuild and then reinstall the Compiz package.

The window decorator is the program which provides windows with borders. Unlike window managers such as mutter, Kwin or Xfwm which provide just one decorator, users of Compiz have a choice of three: Emerald, gtk-window-decorator and kde-window-decorator.

Firstly, ensure that you have installed the decorator you wish to use with Compiz - see the Installation section above. Then start CCSM - you can do this by running the `ccsm` command in a terminal. In the settings panel, navigate to the 'Effects' section and ensure that the 'Window Decoration' plugin is ticked. Now click on the 'Window Decoration' button and in the 'Command' field enter the relevant command for your decorator:

- `emerald`

- `gtk-window-decorator`

- `kde4-window-decorator`

For the changes to take effect immediately, you may wish to add the `--replace` switch to the end of the command. Otherwise, just log out and log in again and your preferred decorator will have been set. Be aware that using the `--replace` switch after the decorator command in CCSM could cause a screen flicker on login.

## Starting Compiz

### Enabling important plugins

Before starting Compiz, you should activate some plugins to provide basic window manager behaviour or else you will have no ability to drag, scale or close any windows. Important plugins are listed below:

- Window Decoration - provides window borders (discussed in the section above)
- Move Window
- Resize Window
- Place Windows - configure window placement options
- Application Switcher - provides an Alt+Tab switcher (there are numerous alternative application switcher plugins e.g. 'Shift Switcher,' 'Static Application Switcher' etc. Not all of them use the Alt+Tab keybinding).
- OpenGL - (only visible in CCSM 0.9).
- Composite - (only visible in CCSM 0.9).

To be able to switch to different viewports you will need to enable one of the following:

- Desktop Cube & Rotate Cube - provides the spinning cube with each side being a different viewport
- Desktop Wall - viewports are arranged next to each other (animation is similar to the workspace switching animation in Cinnamon and GNOME Shell.)
- Expo - creates a view of all viewports and windows when the mouse is moved into the top left corner (this plugin can be used on its own or in conjunction with either of the two previous plugins)

### Compiz startup commands

You can start Compiz using the following command:

    $ compiz --replace ccp &

Tip: If the `compiz --replace ccp &` command does not work when entered in a run dialog, try running the command without the ampersand: `compiz --replace ccp`.

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 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.

#### Using fusion-icon

You can launch fusion-icon with the following command:

    $ fusion-icon

To ensure that fusion-icon then starts Compiz, right click on the icon in the panel and go to 'select window manager'. Choose 'Compiz' if it isn't selected already.

Most of the methods below that autostart Compiz in a desktop environment can also be used to autostart fusion-icon which can then start Compiz. For the method you are using, just replace the command to start Compiz (usually `compiz --replace ccp &`) with `fusion-icon`.

### Autostarting Compiz in a desktop environment

#### KDE4

##### Use System Settings

Go to: System Settings > Default Applications > Window Manager > Use a different window manager and select Compiz.

If you need to run Compiz with custom options and switches select "Compiz custom", then create a script called `compiz-kde-launcher` and add to it the commands you wish to use to start Compiz. See the example below:

    /usr/local/bin/compiz-kde-launcher

    #!/bin/bash
    LIBGL_ALWAYS_INDIRECT=1
    compiz --replace ccp &
    wait

Then make it executable:

    $ chmod +x /usr/local/bin/compiz-kde-launcher

##### Autostart link

Note:

- Do not create the `compiz.desktop` file if you intend to install the gtk-window-decorator as it may create a file conflict.
- If `compiz.desktop` already exists, you may have to add `--replace` and/or `ccp` to the `Exec` variable.

Append a desktop entry in the KDE Autostart directory. If it doesn't exist already, create it:

    ~/.kde4/Autostart/compiz.desktop

    [Desktop Entry]
    Type=Application
    Encoding=UTF-8
    Name=Compiz
    Exec=/usr/bin/compiz ccp --replace
    NoDisplay=true
    # name of loadable control center module
    X-GNOME-WMSettingsModule=compiz
    # autostart phase
    X-GNOME-Autostart-Phase=WindowManager
    X-GNOME-Provides=windowmanager
    # name we put on the WM spec check window
    X-GNOME-WMName=Compiz
    # back compat only
    X-GnomeWMSettingsLibrary=compiz

##### Export KDEWM

As root you must create a short script. This will allow you to load Compiz with extra switches.

Create a file with the command to start Compiz plus any additional switches you may wish to use as well. See the example below:

    /usr/bin/startcompiz

    compiz --replace ccp &

Note: You do not have to call the script startcompiz. Just ensure that the name of your script does not conflict with any executable files already in the `/usr/bin` directory.

Ensure that your script is executable:

    # chmod +x /usr/bin/startcompiz

Now you need to create the file that will load the script you created in `/usr/bin`

1) For your user only:

    ~/.kde4/env/startcompiz.sh

    KDEWM="compiz"

2) System-wide:

    /etc/kde/env/startcompiz.sh

    KDEWM="compiz"

Note:

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

    $ export KDEWM="startcompiz"

  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/startcompiz"

#### GNOME

##### GNOME Shell & Cinnamon

GNOME Shell is implemented as a plugin of the mutter window manager. Likewise, the Cinnamon shell is implemented as a plugin of the muffin window manager. This means that it is impossible to use either GNOME Shell or Cinnamon with Compiz or any other window manager.

##### Unity

Ensure that the 'Ubuntu Unity Plugin' is enabled in CCSM in order for Unity to start successfully. This plugin will only be visible in CCSM if Unity is successfully installed.

##### Alternate Session for GNOME (Cairo dock and Compiz)

The gnome-session-compiz package can be used to add an additional session in a display manager. Simply select the 'gnome-session-compiz' option in your display manager.

Ensure that Compiz and Cairo Dock (Taskbar/Panel) have been configured correctly.

In CCSM, ensure that a window decorator is selected and the necessary plugins for window management have been enabled. See Compiz#Enabling important plugins.

See below for recommended Cairo dock configuration:

- Add Application Menu icon to Cairo Dock and remember its key-bindings.
- Remap Application Menu key-bindings to `Alt+F1` and `Alt+F2`, for convenience.
- Add Clock, WiFi, NetSpeed icons to the dock as applicable.
- Add Log-out icon:
  - Set the command for logout to `gnome-session-quit --logout`
  - Set the command for shutdown to `gnome-session-quit --power-off`
- Add the Notification Area Old (systray) icon to Cairo Dock.

##### GNOME Flashback

See GNOME Flashback#Alternative window manager.

#### MATE

##### Using GSettings

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

    $ gsettings set org.mate.session.required-components windowmanager compiz

##### Using mate-session-properties

Note: If this method is used, Marco will start first and will then be replaced by Compiz.

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.

#### Xfce

##### Modifying the default (Failsafe) session

To configure the default session (known as the Failsafe session) of Xfce, use `xfconf-query`:

     xfconf-query -c xfce4-session -p /sessions/Failsafe/Client0_Command -t string -t string -s compiz -s ccp

or alternatively edit one of the following files:

- User: `~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml`
- Systemwide: `/etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml`:

Note: If the xfce4-session.xml file does not exist in `~/.config/xfce4/xfconf/xfce-perchannel-xml` then you will need to edit the file in `/etc/xdg/xfce4/xfconf/xfce-perchannel-xml`

Replace the Xfwm startup command,

     <property name="Client0_Command" type="array">
       <value type="string" value="xfwm4"/>
     </property>

with the following:

     <property name="Client0_Command" type="array">
       <value type="string" value="compiz"/>
       <value type="string" value="ccp"/>
     </property>

To prevent the default session from being overwritten you may also want to add this:

     <property name="general" type="empty">
       ...
       ...
       <property name="SaveOnExit" type="bool" value="false"/>
     </property>

Then remove the existing sessions:

    $ rm -r ~/.cache/sessions

Now you will need to log out. Ensure that the 'Save session for future logins' option in the logout dialogue is unticked or the edit will not take effect. Log in again and Compiz should start. Once you are sure Compiz is running, you can tick the 'Save session for future logins' option again.

##### Starting Compiz from a restored Xfce session

Note: If you clear your saved sessions then you will need to run through the steps of this method again.

By default, Xfce saves its sessions on logout which means that running applications will be restored on login. Therefore, to ensure that Compiz is autostarted with each session, you merely need to ensure that Compiz is running when you logout. To do so, hit `Alt+F2` to start the Xfce run dialog. Then run the command to start Compiz: `compiz --replace ccp &`. Then you just need to logout. When logging out, ensure that the "Save session for future logins" option in the Xfce logout dialog is ticked. You should find that Compiz is autostarted in all future sessions.

##### Using Xfce application autostart

Note: If this method is used, Xfwm will start first and will then be replaced by Compiz.

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.

Tip: When using this method, it is advisable to disable saved sessions otherwise Compiz will be started twice at login which could lead to problems such as the `Alt+F4` keybinding not working. To disable saved sessions, open the 'Session and Startup' menu entry, click on the 'Session' tab and click the 'Clear saved sessions' button. Then, untick the 'Save session for future logins' option in the Xfce logout dialog.

#### LXDE & LXQt

The session files of LXDE and LXQt can be edited to start an alternative window manager (such as Compiz) with the session.

- For LXDE, see the following section: LXDE#Replacing the default window manager.
- For LXQt, see the following section: LXQt#Replacing the default window manager.

## Using Compiz as a standalone window manager

### Starting the session with a display manager

A standalone Compiz session can be started from a display manager. For most display manager's (LightDM, LXDM, GDM etc) all that's required is to create a .desktop file in `/usr/share/xsessions` defining the Compiz session. See the article for your display manager to check if this is the case.

Firstly, create the `/usr/share/xsessions` directory if it does not already exist. Then create the .desktop file. A basic example is provided below:

    /usr/share/xsessions/compiz.desktop

    [Desktop Entry]
    Version=1.0
    Name=Compiz
    Comment=Start a standalone Compiz session
    Exec=compiz ccp
    Type=Application

Then just choose 'Compiz' from your sessions list and log in.

Note: Some display managers are stricter than others regarding the syntax of .desktop files. If a Compiz option does not appear in your display manager's session menu you will need to edit your .desktop file to make it compatible. The example above should work in most cases.

#### Autostarting programs when using a display manager

One way in which you could start programs with your Compiz session, when it is started from a display manager, is to use an xprofile file. The xprofile file is similar in syntax to xinitrc - it can contain commands for programs you wish to start with your session. Most display managers will parse commands from an xprofile file by default.

Alternatively, you could use Compiz's 'Session Management' plugin. This plugin will save running programs on exit and restore them when the session is next started. Simply enable the 'Session Management' plugin in CCSM}.

### Starting the session with startx

To start Compiz with the `startx` command, add the following line to your `~/.xinitrc` file:

    ~/.xinitrc

    exec compiz ccp

You can also use fusion icon as shown below:

    ~/.xinitrc

    exec fusion-icon

You can autostart additional programs (such as a panel) by adding the relevant command to your `~/.xinitrc` file. Below is an example of a `~/.xinitrc` file which starts Compiz, the tint2 panel and the Cairo dock.

    ~/.xinitrc

    tint2 &
    cairo-dock &
    exec compiz ccp

See the xinitrc article for more details.

### Add a root menu

To add a root menu similar to that in Openbox and other standalone window managers you can install the compiz-boxmenu package. This program is a fork of compiz-deskmenu. Among the changes that the fork introduces are the addition of some extra features such as a window list and a recent documents list.

After installing the compiz-boxmenu package, copy the config files to your home directory as shown below:

    # cp -R /etc/xdg/compiz /home/username/.config
    # chown -R username:group /home/username/.config/compiz

where `username` is your username and `group` is the primary group for your user.

Then, open CCSM, navigate to the 'Commands' plugin and in 'Command line 0' enter the command `compiz-boxmenu`. In the 'Key Bindings' tab, set 'Run command 0' to `Control+Space` (you can use the 'Grab key combination' option to simplify this process.)

Now navigate to the 'Viewport Switcher' plugin and click on the 'Desktop-based Viewport Switching' tab. Change the 'Plugin for initiate action' to `core` and change 'Action name for initiate' to `run_command0_key`.

You should now find that a menu appears when you click `Control+Space`. To launch a graphical menu editor, click on the 'Edit' option or run `compiz-boxmenu-editor` in a terminal. If you would prefer to edit your menu manually, open the following file in your favourite editor: `~/.config/compiz/boxmenu/menu.xml`. For your changes to take effect, you must click the 'Reload' option in your menu.

Warning: Whilst `Control+Space` is the default keybinding for `compiz-boxmenu` you can assign the menu to other keybindings or mousebindings as well. Take extreme care if doing so as Compiz bindings will take precedence over keybindings of all other programs. For instance, if you assign `compiz-boxmenu` to `Button3` then you may lose right click functionality in all programs. If the keybinding/mousebinding you are attempting to create has any conflicts, `cssm` will notify you.

### Allow users to shutdown/reboot

An unprivileged user should be able to execute commands such as `systemctl poweroff` and `systemctl reboot`. You could assign a keyboard shortcut to one of these commands using the 'Commands' plugin in CCSM. Alternatively, you could create a launcher for one of these commands in compiz-boxmenu - see above. For more detailed information on shutting down see the following article: Allow users to shutdown.

### Utilities

#### Panels & docks

There are a number of panels and docks available in Arch however only a few are compatible with Compiz's viewports. They are listed below:

- xfce4-panel
- mate-panel
- perlpanel
- gnome-panel
- cairo-dock

Note: Other panels and docks can be run with Compiz however their desktop pagers will show only one virtual desktop and all window buttons will be shown in all viewports regardless of which viewport the window happens to be in.

#### Run dialog

- mate-panel provides a run dialog. To enable it, see the following section: Compiz#MATE Panel.
- gnome-panel provides a run dialog. To enable it, see the following section: Compiz#GNOME Panel.
- lxpanel provides a run dialog. To enable it, see the following section: Compiz#LXDE Panel.

Note: The panels mentioned above must be running in order to use their respective run dialogs.

Alternatively you could install one of the following:

- xfce4-appfinder - use the following command to launch a run dialog: `xfce4-appfinder --collapsed`
- bbrun - use the following command to launch a run dialog: `bbrun -w`
- gmrun - use the following command to launch a run dialog: `gmrun`
- fbrun - use the following command to launch a run dialog: `fbrun`

In each case, simply map the command to `Alt+F2` (or a key combination of your choice) via the 'Commands' plugin in CCSM.

## Tips and tricks

### Restoring the native window manager

You can switch back to your desktop environment's default window manager with the following command:

    wm_name --replace

with `kwin`, `metacity` or `xfwm4` instead of `wm_name`.

### Enabling the Alt+F2 run dialog

#### GNOME Panel

Enable the 'Gnome Compatibility' plugin in CCSM.

#### MATE Panel

There are two ways to enable MATE Panel's run dialog in Compiz. You can either:

- Enable the 'Gnome Compatibility' plugin in CCSM.
- Map the command below to the `Alt+F2` key combination using the 'Commands' plugin in CCSM.

    mate-panel --run-dialog

#### LXDE Panel

Map the command below to the `Alt+F2` key combination using the 'Commands' plugin in CCSM.

    lxpanelctl run

#### Xfce Appfinder

When Compiz is used in an Xfce session, the run dialog (provided by xfce4-appfinder) should work without intervention. If you are using Xfce Appfinder in a standalone Compiz session, see the following section: Compiz#Run dialog.

#### Other run dialogs

See the following section: Compiz#Run dialog.

## Troubleshooting

### Missing GLX_EXT_texture_from_pixmaps

#### On ATI cards (first solution)

You may 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.

Firstly, 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

Then you can reinstall your fglrx drivers. Now start Compiz as shown below:

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

#### On ATI cards (second solution)

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

    LIBGL_ALWAYS_INDIRECT=1 compiz --replace ccp &

(Workaround tested on the following card : ATI Technologies Inc Radeon R250 [Mobility FireGL 9000] (rev 02))

#### On Intel chips

Firstly, check that you're using the intel driver as opposed to i810. Then, run the following command to run Compiz (This must be used every time).

    LIBGL_ALWAYS_INDIRECT=true compiz --replace --sm-disable ccp &

### Compiz starts without window borders with NVIDIA binary drivers

Firstly, ensure that your window decorator settings are configured correctly - see the following: Compiz#Starting the window decorator. If window borders still do not start try adding Option "AddARGBGLXVisuals" "True" and Option "DisableGLXRootClipping" "True" to your "Screen" section in `/etc/X11/xorg.conf.d/20-nvidia.conf`. If window borders still do not load and you have used other Options elsewhere in `/etc/X11/xorg.conf.d/` 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. To do so, open CCSM, navigate to the 'OpenGL' plugin and untick the 'Sync to VBlank' option.

### Poor performance from capable graphics cards

NVIDIA and Intel chips: 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.

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/20-nvidia.conf`, and then restarting your computer:

    Option "DynamicTwinView" "False"

### Screen flicks with NVIDIA card

To fix this behaviour create the file below:

    /etc/modprobe.d/nvidia.conf

    options nvidia NVreg_RegistryDwords="PerfLevelSrc=0x2222"

### Compiz effects not working (GConf backend)

If you have installed the gtk-window-decorator, check if the GConf schema was correctly installed:

    $ gconftool-2 -R /apps/compiz/plugins | grep plugins

Make sure that all plugins are listed. If they are not, try to install the Compiz schema manually (do not run this command as root):

    $ gconftool-2 --install-schema-file=/usr/share/gconf/schemas/compiz-decorator-gtk.schemas

### fusion-icon fails to start

If you get an output like this from the command line:

    $ fusion-icon

    * Detected Session: gnome
    * Searching for installed applications...
    Traceback (most recent call last):
      File "/usr/bin/fusion-icon", line 57, in <module>
        from FusionIcon.interface import choose_interface
      File "/usr/lib/python2.5/site-packages/FusionIcon/interface.py", line 23, in <module>
        import start
      File "/usr/lib/python2.5/site-packages/FusionIcon/start.py", line 36, in <module>
        config.check()
      File "/usr/lib/python2.5/site-packages/FusionIcon/util.py", line 362, in check
        os.makedirs(self.config_folder)
      File "/usr/lib/python2.5/os.py", line 172, in makedirs
        mkdir(name, mode)
    OSError: [Errno 13] Permission denied: '/home/andy/.config/compiz'

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

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

### Alt+F4 keybinding not working (Xfce)

See the following section: Compiz#Using Xfce application autostart.

### Emerald refuses to start (crashes with a segfault)

You may find that Emerald fails to start with your Compiz session and attempting to start it from a terminal gives you the following output (or something similar):

    Segmentation fault (core dumped)

In this case, the solution is to reset the Emerald theme settings:

    $ rm -rf ~/.emerald/theme

Emerald should now start successfully.

### No system bell when Compiz is running

You may find that the system bell (such as the drip sound played when pressing backspace at the beginning of a line in GNOME or MATE Terminal) will not sound if Compiz is running. See the following upstream bug report.

For Pulseaudio users the following workaround is available:

Append the following lines

    load-sample-lazy bell /usr/share/sounds/freedesktop/stereo/bell.oga
    load-module module-x11-bell sample=bell

to your `/etc/pulse/default.pa` file and then restart Pulseaudio.

### Compiz crashes when enabling the Gnome Compatibility plugin (GSettings backend)

If you are using the GSettings backend, you may find that Compiz crashes if you try to enable the 'Gnome Compatibility' plugin. In order to enable this plugin whilst using the GSettings backend you need to open CCSM and navigate to 'Preferences.' Under the header 'Integration' untick the box labelled 'Enable integration into the desktop environment.' After unticking this option, you should find it possible to enable the 'Gnome Compatibility' plugin.

## Known issues

### Xfce panel window buttons are not refreshed when a window changes viewport

You may find that if you right click on a window title and choose an option such as 'Move to Workspace Right' then the window will move but the window button will still be visible in the viewport the window moved from until you switch viewports. See the following upstream bug report.

### Compiz crashes when enabling the D-Bus plugin

The D-Bus plugin will cause Compiz to crash if enabled in conjunction with certain other plugins such as the Cube plugin. See the following upstream bug report.

## See also

- Compiz in Launchpad
- Compiz Home, including wiki and forum (website and wiki are unmaintained)
- Troubleshooting - Compiz Wiki, (wiki is unmaintained)

Categories:

- Eye candy
- Stacking WMs