Difference between revisions of "Compiz"

From ArchWiki
Jump to: navigation, search
m (Installing the 0.8 series: update packaging: compiz-gtk-standalone replaced with compiz-gtk)
 
(825 intermediate revisions by 17 users not shown)
Line 1: Line 1:
 
[[Category:Eye candy]]
 
[[Category:Eye candy]]
 
[[Category:Stacking WMs]]
 
[[Category:Stacking WMs]]
 +
[[de:Compiz-fusion]]
 
[[el:Compiz]]
 
[[el:Compiz]]
 
[[es:Compiz]]
 
[[es:Compiz]]
Line 11: Line 12:
 
[[tr:Compiz]]
 
[[tr:Compiz]]
 
[[zh-CN:Compiz]]
 
[[zh-CN:Compiz]]
{{Out of date|Since Compiz has been moved to the AUR [https://mailman.archlinux.org/pipermail/arch-dev-public/2013-May/024956.html], some links to packages still need to be added or updated and links to groups need to be replaced.}}
+
{{Related articles start}}
{{Article summary start}}
+
{{Related|Compiz configuration}}
{{Article summary wiki|Compiz Configuration}}
+
{{Related|Window manager}}
{{Article summary wiki|Xcompmgr}}
+
{{Related|Desktop environment}}
{{Article summary wiki|Cairo Compmgr}}
+
{{Related|Xfce}}
{{Article summary end}}
+
{{Related|MATE}}
 +
{{Related articles end}}
  
Compiz is a [[Wikipedia:Compositing window manager|compositing window manager]]. It cannot be used simultaneously with other window managers such as [[Openbox]], [[Fluxbox]], or [[Enlightenment]].  Users who want to keep their current window managers and add some effects to it may wish to try [[Xcompmgr]] instead.
+
According to [[Wikipedia:Compiz|Wikipedia]]:
 
+
: Compiz is a [[Wikipedia:Compositing window manager|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.
== Requirements ==
+
 
+
Users of major [[DE]]s can make good use of {{AUR|compiz-manager}}, performing brief requirements checking and switching to fallback WM in case of errors. Discovering setup and hardware issues can also be done with {{AUR|compiz-check}} script available in [[AUR]].
+
  
 
== Installation ==
 
== Installation ==
  
Install [https://aur.archlinux.org/packages.php?K=compiz packages], available in [[AUR]] (known up to date packages: {{AUR|compiz-bzr}}).
+
As of May 2013, Compiz is [https://mailman.archlinux.org/pipermail/arch-dev-public/2013-May/024956.html 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.'''
  
=== Initial configuration ===
+
=== Installing the 0.9 series ===
 
+
While 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. Depending on what packages you have downloaded you can choose among several window decorators. The most common ones are Emerald, kde-window-decorator, and gtk-window-decorator. The emerald decorator has the advantage that it fits better to compiz's screen handling and offers transparency effects. To set your default window decorator type the following command string in the "Window Decoration" plugin's settings under the field "Command".
+
 
+
Ensure that the "Window decorator" plugin is enabled in ccsm's "effects" tab, the "command" field is filled in to start a decorator.
+
 
+
To set '''emerald''' as your default window-decorator type:
+
$ emerald --replace
+
To set the '''kde-window-decorator''' as an alternative to Emerald type:
+
kde4-window-decorator --replace
+
To set the '''compiz-decorator-gtk''' as an alternative to Emerald type:
+
$ gtk-window-decorator --replace
+
 
+
{{Note|'''Activate important plugins:''' there is high possibility that you will want to activate a few plugins that provide basic window manager behavior 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. ''ccsm'' command may be used to achieve this. Simply put check marks next to those plugins to activate them.}}
+
 
+
== Additional software ==
+
 
+
=== Decorators ===
+
 
+
* {{App|[[Emerald]]|Compiz's own window decorator with few dependencies. (Note: Works but is buggy and no longer maintained)|http://www.compiz.org|{{AUR|emerald}}}}
+
* {{App|compiz-decorator-gtk, compiz-decorator-kde|Alternatives to Emerald, using your desktop environment's configuration backends and looks.|http://www.compiz.org|{{AUR|compiz-bzr}}}}
+
 
+
=== Other ===
+
 
+
* {{AUR|ccsm}} (CompizConfig settings manager) - GUI application that lets you configure all of Compiz's plugins
+
* {{AUR|fusion-icon}} - offers a tray icon and a nice way to start compiz, start ccsm and change the WM / Window Decorator
+
 
+
== Starting Compiz Fusion ==
+
 
+
=== Manually (with "fusion-icon") ===
+
 
+
Launch the Compiz Fusion tray icon:
+
$ fusion-icon
+
 
+
See [[General Troubleshooting#Session permissions]] if you get some permission related errors.
+
 
+
Right click on the icon in the panel and go to 'select window manager'. Choose "Compiz" if it isn't selected already, and you should be set.
+
 
+
If this fails you can start compiz-fusion by using the following additional command to replace your default window decorator with Compiz's window decorator (Emerald):
+
$ emerald --replace
+
 
+
'''Again, note:''' If you want to use compiz window decorations make sure you have the "Window Decoration" plugin marked in the compiz settings through ccsm.
+
 
+
=== Manually (without "fusion-icon") ===
+
 
+
Launch Compiz with the following command (which replaces your current window manager):
+
$ compiz --replace ccp &
+
 
+
A quick overview over common compiz command-line options:
+
* {{ic|--indirect-rendering}}: use indirect-rendering (AIGLX)
+
* {{ic|--loose-binding}}: can help performance issues (NVIDIA?)
+
* {{ic|--replace}}: replace current window-manager
+
* {{ic|--keep-window-hints}}: keep the gnome window-manager gconf-settings for available viewports, ...
+
* {{ic|--sm-disable}}: disable session-management
+
* {{ic|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.
+
 
+
=== KDE4 ===
+
 
+
{{Note|The first and last methods will load Compiz-Fusion as the default window manager instead of KWin. This is faster than loading Compiz with 'fusion-icon' because it avoids loading two window managers at startup. This also prevents that annoying black screen flicker you might see using other methods (when KWin switches to Compiz on KDE's desktop loading screens).  The downside is that if Compiz crashes, it may be more difficult to recover your desktop.}}
+
 
+
==== Use System Settings (easiest)====
+
 
+
Go to: ''System Settings > Default Applications > Window Manager > Use a different window manager''
+
 
+
'''''If''''' you need to run compiz with custom options select "Compiz custom" (when you run {{ic|fusion-icon}} from a terminal you can see the command line with which compiz was started).
+
Create a file called "compiz-kde-launcher" in {{ic|/usr/local/bin}}. Then make the file executable: {{ic|chmod +x /usr/bin/compiz-kde-launcher}}.
+
 
+
For example:
+
{{hc|/usr/local/bin/compiz-kde-launcher|
+
#!/bin/bash
+
LIBGL_ALWAYS_INDIRECT=1
+
compiz --replace ccp &
+
wait
+
}}
+
 
+
==== Autostart with "fusion-icon" ====
+
 
+
Add a symbolic link, that points to the fusion-icon executable, in your KDE Autostart directory:
+
$ ln -s /usr/bin/fusion-icon ~/.kde4/Autostart/fusion-icon
+
 
+
Next time KDE is started, it will load fusion-icon automatically.
+
 
+
==== Autostart link without "fusion-icon" ====
+
 
+
{{Warning|Do '''not''' create '''compiz.desktop''' if you intend to install compiz-decorator-gtk; it will create a file conflict.}}
+
 
+
* Append a desktop entry in the KDE Autostart directory. If it doesn't already exist (it should), create the file {{ic|~/.kde4/Autostart/compiz.desktop}} with the following:
+
 
+
[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
+
 
+
{{Note|If '''compiz.desktop''' already exists, you may have to add {{ic|--replace}} and/or {{ic|ccp}} to the Exec variable. Without {{ic|--replace}}, Compiz won't load since it will detect another window manager already loaded. Without {{ic|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.}}
+
 
+
* If you want to use the optional {{ic|fusion-icon}} application, launch '''fusion-icon'''. If you log out normally with '''fusion-icon''' running, KDE should restore your session and launch '''fusion-icon''' the next time you log in if this setting is enabled. If it doesn't appear to be working, ensure you have the following line in {{ic|~/.kde4/share/config/ksmserverrc}}:
+
 
+
loginMode=restorePreviousLogout
+
 
+
{{Note|This is a KDE specific setting that will allow you to restore other apps next time you log in, not just fusion-icon.}}
+
 
+
==== Export KDEWM without "fusion-icon" (preferred) ====
+
 
+
As root you must create a short script by doing the following in your terminal.  This will allow you to load compiz with the switches because doing it directly via {{ic|1=export KDEWM="compiz --replace ccp --sm-disable"}} doesn't seem to work.
+
$ echo "compiz --replace ccp --sm-disable &" > /usr/bin/compiz-fusion
+
 
+
{{Note|If this line doesn't work, make sure the '''fusion-icon''' package is installed and then use this line instead:
+
$ echo "fusion-icon &" > /usr/bin/compiz-fusion
+
Be sure to complete the whole method before trying this substitute.}}
+
 
+
Ensure that {{ic|/usr/bin/compiz-fusion}} has executable ('''+x''') permissions.
+
$ chmod a+x /usr/bin/compiz-fusion
+
 
+
Choose one of the following:
+
 
+
:1) Compiz for your user only > Edit the file {{ic|~/.kde4/env/compiz.sh}} and add the following line so KDE will load compiz (via the script you just created) instead of loading KWin.
+
: {{bc|1=KDEWM="compiz-fusion"}}
+
 
+
:2) Compiz system wide > Edit the file {{ic|/etc/kde/env/compiz.sh}} and add the following line so KDE will load compiz (via the script you just created) instead of loading KWin.
+
: {{bc|1=KDEWM="compiz-fusion"}}
+
  
 
{{Note|
 
{{Note|
* If that still doesn't work, yet another alternate way to accomplish the above method is to include the line:
+
* From Compiz 0.9.8 onwards, all Compiz components are developed and distributed as a single project. This means that a single package can provide all of the Compiz components.
export KDEWM="compiz-fusion"
+
* To have ''emerald-themes'' with ''emerald0.9'', first install {{AUR|emerald0.9}} and then install {{AUR|emerald-themes}}. Doing the opposite will resolve the wrong dependencies and cause conflicts.}}
in your user's {{ic|~/.bashrc}} file.
+
* If you optionally use the {{ic|/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 ===
+
Required:
 +
* {{App|Compiz|OpenGL compositing window manager with CCSM, Plugins and GTK Window Decorator.|https://launchpad.net/compiz|{{AUR|compiz}}}}
  
If you have installed [[GNOME3]] with gnome-shell, either enable forced Fallback mode (System Info > Graphics) or simply uninstall gnome-shell.
+
Optional:
{{Note|Fallback mode is not necessary if you choose the Compiz/Cairo-Dock session method below.}}
+
* {{App|Emerald|A standalone window decorator for Compiz.|http://www.compiz.org/|{{AUR|emerald0.9}}}}
 +
* {{App|Emerald Themes|Extra themes for the Emerald window decorator.|http://www.northfield.ws/projects/compiz/|{{AUR|emerald-themes}}}}
 +
* {{App|Fusion Icon|A tray applet for starting Compiz and switching window managers and decorators on the fly.|https://github.com/kozec/fusion-icon-gtk3|{{AUR|fusion-icon0.9}}}}
  
==== Alternate Session for GNOME (preferred method for experienced Compiz/Dock users) ====
+
=== Installing the 0.8 series ===
  
The {{AUR|gnome-session-compiz}} can be used to add an additional menu entry in the GNOME session login dialog. This method does not require foced fallback mode and/or modifications to sensitive system files/settings. Also, you can switch between GNOME Shell and Compiz/Cairo-Dock between sessions. If you can't get it working, you can always go back to your original GNOME session.
+
{{Note|The {{AUR|compiz-core}} package does not provide the GTK Window Decorator by default. Users of this package should use {{AUR|emerald}} for [[#Window decoration]]. Alternatively, use {{AUR|compiz-gtk}} for a Compiz Core package that also provides GTK Window Decorator.}}
  
For this method to work, Compiz and Cairo-Dock (Taskbar/Panel) may have to be [[#Configuration|configured initially]] for fresh accounts, from another working session (ccsm in GNOME Shell worked fine for me).
+
Required:
 +
* {{App|Compiz Core|OpenGL compositing window manager.|http://www.northfield.ws/projects/compiz/|{{AUR|compiz-core}}, {{AUR|compiz-gtk}}}}
  
This method completely replaces the GNOME's window manager and panel (they are not launched at all, rather than being replaced or killed later). So, before actually switching to this alternate session, you may want to configure corresponding/alternate features of the original panel application in Cairo-Dock:
+
Highly recommended:
* Add Application Menu icon to Cairo-Dock and remember its key-bindings.
+
* {{App|CompizConfig Settings Manager|Graphical settings manager for Compiz.|http://www.northfield.ws/projects/compiz/|{{AUR|ccsm}}}}
* Remap Application Menu key-bindings to ALT+F1 and ALT+F2, for convenience.
+
* {{App|Compiz Fusion Plugins Main|Main plugins collection for Compiz.|http://www.northfield.ws/projects/compiz/|{{AUR|compiz-fusion-plugins-main}}}}
* Add Clock, WiFi, NetSpeed icons to the dock as applicable.
+
* {{App|Compiz Fusion Plugins Extra|Extra plugins collection for Compiz.|http://www.northfield.ws/projects/compiz/|{{AUR|compiz-fusion-plugins-extra}}}}
* 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.
+
  
==== Autostart (without "fusion-icon") (preferred method) ====
+
Optional:
 +
* {{App|Compiz Fusion Plugins Experimental|Experimental Compiz plugins.|http://www.northfield.ws/projects/compiz/|{{AUR|compiz-fusion-plugins-experimental}}}}
 +
* {{App|Emerald|A standalone window decorator for Compiz.|http://www.northfield.ws/projects/compiz/|{{AUR|emerald}}}}
 +
* {{App|Emerald Themes|Extra themes for the Emerald window decorator.|http://www.northfield.ws/projects/compiz/|{{AUR|emerald-themes}}}}
 +
* {{App|Fusion Icon|A tray applet for starting Compiz and switching window managers and decorators on the fly.|http://www.compiz.org/|{{AUR|fusion-icon}}}}
  
This Method makes use of the [http://standards.freedesktop.org/desktop-entry-spec/latest/ Desktop Entry Specification] to specify a Compiz Desktop Entry and of the GConf default windowmanager setting. Thanks to the Desktop Entry you should be able to select Compiz as a windowmanager out of GDM.
+
== Starting Compiz ==
  
'''1)'''If the following file doesn't already exist (it should), create it {{ic|/usr/share/applications/compiz.desktop}} containing the following:
+
=== Enabling important plugins ===
  
[Desktop Entry]
+
{{Tip|Depending on which package you installed Compiz from, some of these plugins may already be activated.}}
Type=Application
+
Encoding=UTF-8
+
Name=Compiz
+
Exec=/usr/bin/compiz ccp  #Make sure ccp is included so that Compiz loads your previous settings.
+
NoDisplay=true
+
# name of loadable control center module
+
X-GNOME-WMSettingsModule=compiz
+
# autostart phase
+
##-> the folloing line cause gnome-session warning and slow startup, so try not to enable this
+
# 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
+
  
{{Note| If {{ic|compiz.desktop}} already exists, you must make sure that the "ccp" is included in the Exec variable. Having "ccp" included simply tells Compiz to load your previous settings, otherwise you won't have any functionality.}}
+
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:
  
If the above doesn't work (in most cases it does), for example if you notice some issues with windows refreshing or low performance, try:
+
* Window Decoration - provides window borders, see [[#Window decoration]].
 +
* Move Window.
 +
* Resize Window.
 +
* Place Windows - configure window placement options.
 +
* Application Switcher - provides an {{ic|Alt+Tab}} switcher - there are numerous alternative application switcher plugins, for example: Shift Switcher, Static Application Switcher and more. Not all of them use the {{ic|Alt+Tab}} keybinding.
 +
 +
To be able to switch to different [[Compiz configuration#Workspaces and Viewports|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 - the 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.
  
Exec=/usr/bin/compiz ccp --indirect-rendering
+
==== Window decoration ====
  
or
+
{{Tip|For information on selecting and managing themes, see: [[Compiz configuration#Window decoration themes]].}}
  
Exec=/usr/bin/compiz --replace --sm-disable --ignore-desktop-hints ccp --indirect-rendering
+
The window decorator is the program which provides windows with borders. Unlike window managers such as Kwin or [[Xfwm]] which provide just one decorator, users of Compiz have a choice of three: GTK Window Decorator, KDE Window Decorator and Emerald. The GTK Window Decorator and the KDE Window Decorator are included in the Compiz source and can be optionally compiled whilst building Compiz. Emerald, on the other hand, is a separate, standalone decorator. The ''Window Decoration'' plugin in CCSM must be ticked otherwise no window decorator will be started.
  
Instead of
+
;Choosing the decorator
 +
The window decorator that will be started is specified under CCSM -> ''Effects'' -> ''Window Decoration'' -> ''Command''. The command can be one of the following executables: ''emerald'', ''gtk-window-decorator'', ''kde4-window-decorator''. Use the {{ic|--replace}} switch, e.g. {{ic|emerald --replace}}, if specifying the decorator executable on its own is not sufficient.
  
Exec=/usr/bin/compiz ccp
+
{{Tip|In Compiz 0.9, the decorator command is set to ''compiz-decorator'' by default. This is a script which will search for the ''emerald'', ''gtk-window-decorator'' and ''kde4-window-decorator'' executables in that order and start the first one that it finds.}}
  
Some Users noticed a "lag" of 4-10 seconds when loging in from a login manager. The solution is to change the command to:
+
=== Compiz startup ===
Exec=bash -c 'compiz ccp decoration --sm-client-id $DESKTOP_AUTOSTART_ID'
+
as noted [https://bbs.archlinux.org/viewtopic.php?pid=655237#p655237 in the forum]. You can also add the extra parameters as described above if needed.
+
  
'''2)''' Set some GConf parameters using the gconftool-2 command in a terminal window or do it visually with Configuration Editor (gconf-editor). The following outlines using the command line method, but you can also see which keys to change using gconf-editor:
+
{{Note|Some Compiz versions may require you to manually load the CCP plugin on startup: {{ic|compiz --replace ccp}} [http://blog.northfield.ws/compiz-release-announcement-0-8-12/]}}
  
{{Note| Since those parameters apply to a given user, you '''must''' logout from the root account and log in as that other user before proceeding with the next steps. GConf will fail, if called from a root account.}}
+
You can start Compiz using the following command:
 +
$ compiz --replace
  
gconftool-2 --set -t string /desktop/gnome/session/required_components/windowmanager compiz
+
See {{ic|compiz --help}} for more options.
  
The following are optional and in most cases not necessary (the respective keys are deprecated since GNOME 2.12). But iny any case, if the above didn't succeed the next two statements are still valid and should be tried.
+
==== Fusion Icon ====
  
gconftool-2 --set -t string /desktop/gnome/applications/window_manager/current /usr/bin/compiz
+
{{Tip|When [[#Autostarting Compiz in a desktop environment]] ''fusion-icon'' can be set as the default command instead of ''compiz''.}}
gconftool-2 --set -t string /desktop/gnome/applications/window_manager/default /usr/bin/compiz
+
  
==== Autostart (without "fusion-icon") (with GNOME fallback mode session) ====
+
To start Compiz using Fusion Icon, execute the command below:
 +
$ fusion-icon
  
Edit file {{ic|/usr/share/gnome-session/sessions/gnome-fallback.session}}:
+
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 is not selected already.
  
Replace your windows manager (gnome-shell,metacity...) with ''compiz'' in '''RequiredComponents''' line.
+
=== Autostarting Compiz in a desktop environment ===
  
Change ''DefaultProvider-windowmanager'' line to ''DefaultProvider-windowmanager=compiz''
+
See [[Desktop environment#Custom window manager]].
  
Here is part of my {{ic|gnome-fallback.session}}:
+
== Using Compiz as a standalone window manager ==
  
RequiredComponents=compiz;gnome-settings-daemon;
+
=== Starting the session with a display manager ===
RequiredProviders=windowmanager;notifications;
+
DefaultProvider-windowmanager=compiz
+
DefaultProvider-notifications=notification-daemon
+
  
{{Note|I took out gnome-panel as I am using avant-window-navigator as my panel.
+
A standalone Compiz session can be started from a [[display manager]]. For most display manager's - [[LightDM]] for example - all that is required is to create a {{ic|.desktop}} file in {{ic|/usr/share/xsessions}} that executes ''compiz'' (with command line options if needed) or ''fusion-icon''. See the article for your display manager. See [[Desktop entries]] for information on creating a {{ic|.desktop}} file.
I'am using gnome3 fallback mode with compiz, make gtk-window-decorator start with compiz, and make avant-window-navigator start automatically.}}
+
  
==== Autostart (without "fusion-icon", Gnome prior to 2.24) ====
+
==== Autostarting programs when using a display manager ====
  
This is a way that works if you use GDM (and I'd assume KDM too).
+
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. Another option is for the {{ic|.desktop}} file in {{ic|/usr/share/xsessions}} to not execute ''compiz'' directly but to execute a script which starts the programs you wish to start and also starts Compiz.
  
Make a file called /usr/local/bin/compiz-start-boot with the contents:
+
=== Starting the session with startx ===
#!/bin/bash
+
export WINDOW_MANAGER="compiz ccp"
+
exec gnome-session
+
  
and make it executable ({{ic|chmod +x /usr/local/bin/compiz-start-boot}}). Next create the file {{ic|/etc/X11/sessions/Compiz.desktop}} containing the following:
+
A Compiz session can be started with ''startx''. Define either ''compiz'' or ''fusion-icon'' in your {{ic|.xinitrc}} file. See the [[xinitrc]] article for more details.
[Desktop Entry]
+
Version=1.0
+
Encoding=UTF-8
+
Name=Compiz on GNOME
+
Exec=/usr/local/bin/compiz-start-boot
+
Icon=
+
Type=Application
+
  
Select Compiz on Gnome as your session and you're good to go.
+
=== Add a root menu ===
  
==== Autostart (with "fusion-icon") ====
+
To add a root menu similar to that in [[Openbox]] and other standalone window managers install {{AUR|compiz-boxmenu}}. This program is a fork of {{AUR|compiz-deskmenu}}.
  
To start Compiz fusion automatically when starting a session go to System > Preferences > Startup Applications. In the Startup Programs tab, click the Add button.
+
Then copy the config files to your home directory as shown below:
  
You will now see the Add Startup Program dialogue. Fill it in as follows.
+
# cp -R /etc/xdg/compiz /home/''username''/.config
 +
# chown -R ''username'':''group'' /home/''username''/.config/compiz
  
Name:
+
where {{ic|username}} is your username and {{ic|group}} is the primary group for your user.
Compiz Fusion
+
Command:
+
fusion-icon
+
Comment:  (Put anything you like or leave blank.)
+
  
{{Note| You can also use "compiz --replace ccp" instead of "fusion-icon" to load compiz but there will be no fusion-icon.
+
Then, open CCSM, navigate to the ''Commands'' plugin and in ''Command line 0'' enter the command {{ic|compiz-boxmenu}}. In the ''Key Bindings'' tab, set ''Run command 0'' to {{ic|Control+Space}} or another key/mouse button combination of choice. Take care not to use a combination that is already used for other functionality.
  
The ccp value will tell compiz to load your previous Compiz settings as configured with CompizConfig Settings Manager ('''ccsm''').}}
+
Now navigate to the ''Viewport Switcher'' plugin and click on the ''Desktop-based Viewport Switching'' tab. Change the ''Plugin for initiate action'' to {{ic|core}} and change ''Action name for initiate'' to {{ic|run_command0_key}}.
  
When you're done hit the Add button. You should now see your startup program in the list in the Startup Programs tab. It must be checked to be enabled. You can uncheck it to disable Compiz on startup and switch back to Metacity.
+
You should now find that a menu appears when you click {{ic|Control+Space}}. To launch a graphical menu editor, click on the ''Edit'' option or run {{ic|compiz-boxmenu-editor}} in a terminal. If you would prefer to edit your menu manually, open the following file in your favourite editor: {{ic|~/.config/compiz/boxmenu/menu.xml}}. For your changes to take effect, you must click the ''Reload'' option in your menu.
  
You may also need to use the gconftool-2 command in a terminal window to set the following parameter, otherwise fusion-icon might not load the windows decorator.
+
=== Allow users to shutdown/reboot ===
gconftool-2 --type bool --set /apps/metacity/general/compositing_manager false
+
  
{{Note|This method will be slower due to the fact that Gnome will first load the default window manager (Metacity), then will launch fusion-icon which will load the Compiz window manager to replace Metacity. Essentially, it will take the amount of time that it takes to load two window manangers to get Compiz loaded. The first method is preferred and eliminates this issue.}}
+
An unprivileged user should be able to execute commands such as {{ic|systemctl poweroff}} and {{ic|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 {{AUR|compiz-boxmenu}} - see above. For more detailed information on shutting down see the following article: [[Allow users to shutdown]].
  
=== Mate desktop ===
+
== Tips and tricks ==
  
==== Autostart (without "fusion-icon") (preferred method) ====
+
=== Restoring the native window manager ===
  
As with Gnome, create a compiz.desktop file (see [[Compiz#Autostart_.28without_.22fusion-icon.22.29_.28Preferred_Method.29]]), then set Compiz as the default window manager :
+
You can switch back to your desktop environment's default window manager with the following command:
* on Mate prior to 1.6, edit the following mateconf entries (note: the last two are deprecated values):
+
mateconftool-2 --set -t string /desktop/mate/session/required_components/windowmanager compiz
+
mateconftool-2 --set -t string /desktop/mate/applications/window_manager/current /usr/bin/compiz
+
mateconftool-2 --set -t string /desktop/mate/applications/window_manager/default /usr/bin/compiz
+
  
* on Mate 1.6 and higher, edit the following gsettings value
+
  ''wm_name'' --replace
  gsettings set org.mate.session.required-components windowmanager compiz
+
  
=== XFCE ===
+
using ''kwin'', ''metacity'' or ''xfwm4'' for example instead of ''wm_name''.
  
==== XFCE autostart (without "fusion-icon") ====
+
=== Enabling the Alt+F2 run dialog ===
  
This method will start Compiz directly through the XFCE session manager without loading Xfwm.
+
;GNOME Panel
  
Please note the change to xml config files in XFCE newer than 4.2
+
Enable the ''Gnome Compatibility'' plugin in CCSM.
  
To install the session manager, install {{Pkg|xfce4-session}}.
+
;MATE Panel
  
Now we have to configure the default/failsafe session of XFCE.
+
There are two ways to enable MATE Panel's run dialog in Compiz. You can either:
  
Edit the {{ic|~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml}} or (to make the change for all XFCE users) {{ic|/etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml}}:
+
* Enable the ''MATE Compatibility'' plugin in CCSM (use the ''Gnome Compatibility'' plugin for older Compiz versions which lack the MATE plugin).
 +
* Map the command below to the {{ic|Alt+F2}} key combination using the ''Commands'' plugin in CCSM.
  
Replace the xfwm startup command,
+
mate-panel --run-dialog
  
  <property name="Client0_Command" type="array">
+
;LXDE Panel
    <value type="string" value="xfwm4"/>
+
  </property>
+
  
with the following:
+
Map the command below to the {{ic|Alt+F2}} key combination using the ''Commands'' plugin in CCSM.
  
  <property name="Client0_Command" type="array">
+
lxpanelctl run
    <value type="string" value="compiz"/>
+
    <value type="string" value="ccp"/>
+
  </property>
+
  
{{Note|The ccp value will tell compiz to load your previous Compiz settings as configured with CompizConfig Settings Manager (ccsm).}}
+
;Xfce Appfinder
  
To prevent the default session from being overwritten you may also add this:
+
When Compiz is used in an Xfce session, the run dialog (provided by {{Pkg|xfce4-appfinder}}) should work without intervention. If you are using Xfce Appfinder in a standalone Compiz session, map the command to the {{ic|Alt+F2}} key combination using the ''Commands'' plugin in CCSM.
  
  <property name="general" type="empty">
+
;Other run dialogs
    ...
+
    ...
+
    <property name="SaveOnExit" type="bool" value="false"/>
+
  </property>
+
  
To remove the existing sessions, run:
+
Map the command for a [[List of applications#Application launchers|run dialog]] of choice to the {{ic|Alt+F2}} key combination using the ''Commands'' plugin in CCSM.
$ rm -r ~/.cache/sessions
+
 
+
==== XFCE autostart (with "fusion-icon") ====
+
 
+
===== Method 1 =====
+
 
+
{{Note| This method is the least preferred since it loads both window managers. All the other XFCE methods only load Compiz without loading Xfwm.}}
+
This will load Xfwm first then replace it with Compiz.
+
 
+
Open the XFCE Settings Manager & then Sessions & Startup. Click the Application Autostart tab.
+
 
+
Add
+
  (Name:) Compiz Fusion
+
 
+
  (Command:) fusion-icon
+
 
+
{{Note|You can also use {{ic|compiz --replace ccp}} instead of '''fusion-icon''' to load Compiz but there will be no fusion-icon. The ''ccp'' value will tell compiz to load your previous Compiz settings as configured with CompizConfig Settings Manager (ccsm).}}
+
 
+
===== Method 2 =====
+
 
+
Edit the file {{ic|~/.config/xfce4-session/xfce4-session.rc}} (settings in this file is used in preference).
+
 
+
Or to make the change for all XFCE users, edit as root {{ic|/etc/xdg/xfce4-session/xfce4-session.rc}}.
+
 
+
Add the following
+
[Failsafe Session]
+
Client0_Command=fusion-icon
+
 
+
Comment out Client0_Command=xfwm4 if it exists.
+
 
+
This will cause xfce to load Compiz instead of Xfwm when the user has no existing sessions.
+
 
+
To prevent the default session from being overwritten you may also add
+
[General]
+
AutoSave=false
+
SaveOnExit=false
+
 
+
To remove the existing sessions
+
rm -R ~/.cache/sessions
+
 
+
===== Method 3 =====
+
 
+
Check if this file exists:
+
~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml
+
 
+
If not do:
+
cp /etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml
+
 
+
Then edit {{ic|~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml}}.
+
 
+
or (to make the changes for all xfce4 users) {{ic|/etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml}}:
+
 
+
Edit Client0_Command that it look like this:
+
<property name="Client0_Command" type="array">
+
    <value type="string" value="fusion-icon"/>
+
    <value type="string" value="--force-compiz"/>
+
</property>
+
if '''--force-compiz''' doesn't work use '''compiz --replace --sm-disable --ignore-desktop-hints ccp''' instead.
+
 
+
Add the '''SaveOnExit property''' if missing and set it to '''false''':
+
<property name="general" type="empty">
+
    <property name="FailsafeSessionName" type="string" value="Failsafe"/>
+
    <property name="SessionName" type="string" value="Default"/>
+
    <property name="SaveOnExit" type="bool" value="false"/>
+
  </property>
+
 
+
finally remove old xfce4 sessions:
+
rm -r ~/.cache/sessions
+
 
+
Now XFCE4 will load compiz instead of XFWM.
+
 
+
=== As a standalone window manager ===
+
 
+
The package compiz-core by itself is sufficient to start using compiz-fusion. However ccsm and emerald (or another window-decorator) are additional highly recommended packages. You may install fusion-icon, compiz-fusion-plugins-main, compiz-fusion-plugins-extra or any other package later on at any time.
+
 
+
To autostart compiz-fusion configure .xinitrc to launch compiz as:
+
{{hc|~/.xinitrc|<nowiki>
+
exec compiz ccp
+
</nowiki>}}
+
You can also add other [[Compiz_fusion#Manually_.28without_.22fusion-icon.22.29|command-line options]] to your .xinitrc
+
 
+
Or if using fusion-icon, configure .xinitrc as
+
{{hc|~/.xinitrc|<nowiki>
+
exec fusion-icon
+
</nowiki>}}
+
 
+
However chances are you will need additional apps (e.g a panel) for optimal usability. So to autostart such apps simply add them to your .xinitrc as:
+
{{hc|~/.xinitrc|<nowiki>
+
tint2 &
+
cairo-dock &
+
exec fusion-icon
+
</nowiki>}}
+
 
+
{{Note|Add a terminal-emulator to this autostart list while starting for the first time to help [[Compiz_fusion#Configuration|configure]] Compiz.}}
+
 
+
Feel free to use a different panel, tray, or start a whole bunch of applications with your session.
+
 
+
==== Add a root menu ====
+
 
+
To add a root menu similar to that in Openbox, Fluxbox, Blackbox etc. you must install the package {{AUR|compiz-deskmenu}}.
+
Upon a restart of Compiz-Fusion, 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 Commands tab, within the General Settings menu, ensure that there is a command to launch Compiz-Deskmenu, and the appropriate key binding is set to Control+Space.
+
 
+
If it still does not work, enter the Viewport Switcher menu, and change "Plugin for initiate action" to core (NOTE: for versions 0.8.2+ it's 'commands' instead of 'core'), and "Action name for initiate" to run_command0_key.
+
 
+
An alternative is to use {{AUR|mygtkmenu}}, also in [[AUR]].
+
 
+
==== Allow users to shutdown/reboot ====
+
 
+
Refer to [[Allow_Users_to_Shutdown|this]] wiki page. If using "The Modern way" of 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.
+
 
+
== Miscellaneous ==
+
 
+
=== Configuration  ===
+
 
+
[[Compiz#Configuration|You must do this so your windows function like you expect them to!]].
+
 
+
=== Using gtk-window-decorator ===
+
 
+
In order to use gtk-window-decorator, install the package ''compiz-decorator-gtk'' and select "GTK Window Decorator" instead of "Emerald" as your window decorator in fusion-icon or whatever other program you are using to configure compiz.
+
 
+
=== gconf: additional Compiz configurations ===
+
 
+
To achieve more satisfying results from Compiz, you can tweak its config with gconf-editor:
+
 
+
$ gconf-editor
+
 
+
Note that now compiz-core isn't built with gconf support; It is now built with gconf support through compiz-decorator-gtk. So, you need to install it if you want to use gconf-editor to edit your Compiz configuration.
+
The Compiz gconf configuration is located in in the key ''apps > compiz > general > allscreens > options''.
+
 
+
"Active plugins" is where you specify the plugins you would like to use. Simply edit the key and add a value(refer to the key ''apps > compiz > plugins'' to see possible values). Plugins I’ve found useful are screenshot, png, fade, and minimize. Please do not remove those enabled by default.
+
 
+
=== ATI R600/R700 notes ===
+
 
+
While using fusion-icon you shouldn't experience any problems because it takes care of everything for you, but if you are using one of the autostart methods that do not involve fusion-icon you will run into trouble.  For example when using the Xfce autostart method without fusion icon you must edit ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml per the instructions above.  However, if you follow the directions above explicity you will find that compiz does not load.  You must instead make your xfce4-session.xml file look like this
+
 
+
<property name="Client0_Command" type="array">
+
  <value type="string" value="LIBGL_ALWAYS_INDIRECT=1"/>
+
  <value type="string" value="compiz"/>
+
  <value type="string" value="--sm-disable"/>
+
  <value type="string" value="--ignore-desktop-hints"/>
+
  <value type="string" value="ccp"/>
+
  <value type="string" value="--indirect-rendering"/>
+
</property>
+
 
+
This example targeted Xfce specifically, but it can be adapted to any desktop environment.  It's just a matter of figuring out how to add it to the proper config file.  The key thing is the required command which if typed on a command line would look like this
+
 
+
LIBGL_ALWAYS_INDIRECT=1 compiz --sm-disable --ignore-desktop-hints ccp --indirect-rendering
+
 
+
This is how Xfce's session manager interprets the above XML code.  Notice that you do not need --replace because you are not first loading xfwm and then compiz.
+
 
+
== Tips and tricks ==
+
 
+
=== Fallback ===
+
 
+
If you are using [[KDE]], [[GNOME]] or [[XFCE]] and something is not right, for example you don’t see borders for your window, you can switch back to default DE window manager with this command:
+
 
+
''wm_name'' --replace
+
 
+
with kwin, metacity or xfwm4 instead of ''wm_name''.
+
 
+
=== Keyboard shortcuts ===
+
 
+
Default plugin keyboard shortcuts (plugins have to be activated!)
+
 
+
* Switch windows = {{ic|Alt+Tab}}.
+
* Switch to next desktops = {{ic|Ctrl+Alt+&larr;}}.
+
* Switch to previous desktop = {{ic|Ctrl+Alt+&rarr;}}.
+
* Move window = {{ic|Alt+Left click}}.
+
* Resize window = {{ic|Alt+Right click}}.
+
 
+
A more detailed list can be found under [http://wiki.compiz-fusion.org/CommonKeyboardShortcuts CommonKeyboardShortcuts] in the Compiz wiki or you can always just look at your plugin's configuration ('''ccsm''').
+
  
 
== Troubleshooting ==
 
== Troubleshooting ==
 
{{Out of date}}
 
  
 
=== Missing GLX_EXT_texture_from_pixmaps ===
 
=== Missing GLX_EXT_texture_from_pixmaps ===
Line 534: Line 191:
 
==== On ATI cards (first solution) ====
 
==== On ATI cards (first solution) ====
  
https://bbs.archlinux.org/viewtopic.php?id=50073
+
You may run into the following error when trying to run Compiz on an ATI card:
If you run into the following error when trying to run Compiz Fusion on an ATI card:
+
  
 
  Missing GLX_EXT_texture_from_pixmap
 
  Missing GLX_EXT_texture_from_pixmap
  
This is because Compiz Fusion's binary was compiled against Mesa's OpenGL library rather than ATI's OpenGL library (which is what you are using). Re-install libgl-dri (yes you will have to uninstall fglrx temporarily) to get Mesa's OpenGL library.  
+
This is because Compiz's binary was compiled against Mesa's OpenGL library rather than ATI's OpenGL library.
  
copy the library into a directory to keep it because ATI's drivers will over write it.  
+
Firstly, copy the library into a directory to keep it because ATI's drivers will over write it:  
 
   
 
   
  mkdir /lib/mesa
+
  $ install -Dm644 /usr/lib/libGL.so.1.2 /usr/lib/mesa/libGL.so.1.2
cp /usr/lib/libGL.so.1.2 /lib/mesa
+
Then you can reinstall your fglrx drivers.  Now start Compiz as shown below:  
 
+
Once you have it copied, you can reinstall your fglrx drivers (It should have been removed when you installed libgl-dri).  Now you can start Compiz Fusion using the following example syntax:  
+
 
   
 
   
  LD_PRELOAD=/lib/mesa/libGL.so.1.2 compiz --replace &
+
  LD_PRELOAD=/usr/lib/mesa/libGL.so.1.2 compiz --replace &
  
 
==== On ATI cards (second solution) ====
 
==== On ATI cards (second solution) ====
  
An other problem could arise with GLX_EXT_texture_from_pixmap, it is possible that the card could only render it indirectly, then you have to pass the option to your libgl like that :
+
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 &
+
LIBGL_ALWAYS_INDIRECT=1 compiz --replace &
  
(Workaround tested on the following card : ATI Technologies Inc Radeon R250 [Mobility FireGL 9000] (rev 02))
+
This workaround was tested on the following card : ATI Technologies Inc Radeon R250 [Mobility FireGL 9000] (rev 02).
  
 
==== On Intel chips ====
 
==== On Intel chips ====
  
First off, check that you're using the intel driver as opposed to i810. Then, run the following command to run Compiz (must use this every time.).
+
Firstly, check that you're using the intel driver as opposed to i810. Then, use the following command to start Compiz (this command must be used every time).
  LIBGL_ALWAYS_INDIRECT=true compiz --replace --sm-disable ccp &
+
  LIBGL_ALWAYS_INDIRECT=true compiz --replace --sm-disable &
If you then do not have borders, run:
+
emerald --replace
+
As at 17-Oct-07 the [http://wiki.compiz-fusion.org/Troubleshooting Compiz-Fusion Wiki] states: <i>"If you are using an Intel GMA card with AIGLX, you will need to start Compiz Fusion with LIBGL_ALWAYS_INDIRECT=1 appended.</i>"
+
  
=== Compiz starts, but no effects are visible ===
+
=== Compiz starts without window borders with NVIDIA binary drivers ===
  
If you have installed compiz-decorator-gtk:
+
Firstly, ensure that your window decorator settings are configured correctly - see [[#Window decoration]]. If window borders still do not start try adding ''Option "AddARGBGLXVisuals" "True"'' and ''Option "DisableGLXRootClipping" "True"'' to your "Screen" section in {{ic|/etc/X11/xorg.conf.d/20-nvidia.conf}}. If window borders still do not load and you have used other Options elsewhere in {{ic|/etc/X11/xorg.conf.d/}} try commenting them out and using only the aformentioned ARGBGLXVisuals and GLXRootClipping Options.
Check if GConf schema was correctly installed:
+
  gconftool-2 -R /apps/compiz/plugins | grep plugins
+
make sure that all plugins are listed (not only fade!). If not, try to install Compiz schema manually (do this as normal user, not as root!!!):
+
  gconftool-2 --install-schema-file=/usr/share/gconf/schemas/compiz-decorator-gtk.schemas
+
  
{{Note|Compiz basic plugins are not enabled by default. You should enable "Move Window", "Resize Window", and "Window decoration" plugins in settings manager from fusion-icon to have a usable window manager.}}
+
=== Blank screen on resume from suspend-to-ram with NVIDIA binary drivers ===
  
=== Compiz starts, but gtk-window-decorator does not ===
+
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.
It is a configuration problem for gconf and gconfd. I solved it by removing ".gconf" dir in my home, but I'm using KDE. If you are using Gnome you should enter your ".gconf" directory and remove all Compiz keys. This will erase your Compiz settings, so be sure to reconfigure.
+
Finally exec as user:
+
  
  gconftool-2 --install-schema-file=/usr/share/gconf/schemas/compiz-decorator-gtk.schemas
+
=== Poor performance from capable graphics cards ===
  
=== Compiz appears to start, but there are no window borders ===
+
'''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.
  
When you run fusion-icon from commandline, you get output like this:
+
'''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 {{ic|/etc/X11/xorg.conf.d/20-nvidia.conf}}, and then restarting your computer:
  
  * Detected Session: gnome
+
  Option "DynamicTwinView" "False"
* Searching for installed applications...
+
* NVIDIA on Xorg detected, exporting: __GL_YIELD=NOTHING
+
* Using the GTK Interface
+
* Metacity is already running
+
* Setting window manager to Compiz
+
... executing: compiz --replace --sm-disable --ignore-desktop-hints ccp
+
compiz (core) - Warn: No GLXFBConfig for depth 32
+
compiz (core) - Warn: No GLXFBConfig for depth 32
+
compiz (core) - Warn: No GLXFBConfig for depth 32
+
compiz (core) - Warn: No GLXFBConfig for depth 32
+
compiz (core) - Warn: No GLXFBConfig for depth 32
+
compiz (core) - Warn: No GLXFBConfig for depth 32
+
  
All you need to do is edit your {{ic|/etc/X11/xorg.conf}} and find the "Depth" directive inside the "Screen" section; change all occurences of this value to 24. This occured to me with my colour depth set to 16; but also happens when it is set to 32.
+
=== Screen flicks with NVIDIA card ===
  
----
+
To fix this behaviour create the file below:
 +
{{hc|/etc/modprobe.d/nvidia.conf|2=
 +
options nvidia NVreg_RegistryDwords="PerfLevelSrc=0x2222"
 +
}}
  
You may also try adding ''Option "AddARGBGLXVisuals" "True"'' & ''Option "DisableGLXRootClipping" "True"'' to your "Screen" section if you are using the NVIDIA binary driver. (Radeon, and the open 'nv' driver will not work with this option as far as I can tell.) If you used any other Options elsewhere in '''xorg.conf''' to get Compiz working and still have no luck, try commenting them out and using only the aformentioned ARGBGLXVisuals and GLXRootClipping Options.
+
=== Video tearing ===
  
{{Note|Check that "Window decoration", "Move" and "Resize" plugins are enabled with Compiz Settings Manager or gconf-editor.}}
+
If you experience video tearing when using Compiz, try enabling the ''Workarounds'' plugin in CCSM. Once enabled, ensure that the following options are enabled in Workarounds: ''Force complete redraw on initial damage'', ''Force full screen redraws (buffer swap) on repaint''.
  
With gconf-editor you can easly enable "Window decoration", "Move" and "Resize" plugins.
+
If you are using [[Intel graphics]] and the workaround above does not fix the video tearing, see [[Intel graphics#Tear-free video]].
  
$ gconf-editor
+
Also see, [[#Poor performance from capable graphics cards]].
  
Navigate to ''apps > compiz > general > allscreens > options''.
+
=== Compiz effects not working (GConf backend) ===
  
Add/Edit "active_plugins" Key (Name: active_plugins, Type: List, List type: String).
+
If you have installed the GTK Window Decorator, check if the GConf schema was correctly installed:  
  
Add "decoration", "move", and "resize" to the list.
+
$ 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):
  
'''Another way to fix this''':
+
$ gconftool-2 --install-schema-file=/usr/share/gconf/schemas/compiz-decorator-gtk.schemas
* Launch '''ccsm'''.
+
* Find '''windows decoration''' and make sure it is enabled.
+
* Now click on it, to edit the options.
+
* If the entry behind '''command''' is empty, put the value '''gtk-window-decorator''' there.
+
** Alternatives are '''kde-window-decorator''' and '''emerald'''
+
* Click '''Back''' and '''Close'''
+
* If all went well, the borders should appear.
+
  
=== Compiz starts and borders appear, but windows won't move ===
+
=== Fusion Icon fails to start ===
  
Be sure you have the "Move Window" plugin installed and enabled in the Compiz settings manager.
+
If you get an output like this from the command line:
 +
{{hc|$ 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'
 +
}}
  
=== Blank screen on resume from suspend-to-ram using the NVIDIA binary drivers ===
+
the problem is with the permission on {{ic|~/.config/compiz/}}. To fix it, use:
  
If you receive a blank screen with a responsive cursor upon resume, try disabling sync to vblank:
+
# chown -R ''username'' /home/''username''/.config/compiz/
  
gconftool -s /apps/compiz/general/screen0/options/sync_to_vblank-t boolean false
+
=== Alt+F4 keybinding not working (Xfce) ===
  
=== fusion-icon doesn't start ===
+
If Compiz replaces Xfwm4 at login, this can cause the {{ic|Alt+F4}} keybinding to become non-functional. To avoid this issue, ensure that only Compiz is started at login - see [[Xfce#Default window manager]].
  
If you get an output like this from the command line:
+
=== Emerald crashes when selecting a theme ===
$ 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 {{ic|~/.config/compiz}}. You have set the owner of a folder in your area as root. To change this, run (as root)
+
You may find that Emerald crashes when selecting certain themes (especially themes that use the legacy engine). If this occurs, select another theme in Emerald Theme Manager and then run the command {{ic|emerald --replace}}.
chown <username> /home/<username>/.config/compiz
+
  
=== Choppy animations, even though everything configured correctly ===
+
=== No system bell when Compiz is running ===
  
If everything is configured correctly but you still have poor performance on some effects, try disabling ''CCSM > General Options > Display Settings > Detect Refresh Rate'' and instead choose a value manually. Tested on both NVIDIA and Intel chips. Can work wonders.
+
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 [https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/537703 upstream bug report].
  
Alternatively, if your chip is NVIDIA and you are experiencing an inadequate refresh rate with "Detect Refresh Rate" enabled in Compiz, it's likely 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 xorg.conf file, and then restarting your computer:
+
[[PulseAudio]] users, as a workaround, can force PulseAudio to handle the system bell, see [[PulseAudio#X11 Bell Events]].
  
Option "DynamicTwinView" "False"
+
=== Compiz crashes when enabling the Gnome Compatibility plugin (GSettings backend) ===
  
Doing so will allow XrandR to accurately report the refresh rate to anything that detects it, including Compiz. You should be able to leave "Detect Refresh Rate" enabled and get excellent performance. Once again, this only applies to NVIDIA chips.
+
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.
  
=== Fix GNOME screenshot ===
+
=== Windows lose focus when unminimised ===
  
To re-enable gnome-screenshot (the default behavior caused by hitting {{ic|PrtScn}}) simply go to Settings Manager>Commands and map 'gnome-screenshot' to the 'PrtScn' key.  This is advantageous because you can also use the Compiz-Fusion 'Screenshot' plugin at the same time since the action that enables it is {{ic|Super+Button1}} thereby giving you two methods to do a screen capture (one of which gives a full screen capture in a single keystroke).
+
You may find that certain windows (such as a [[Chromium]] window) will lose focus when unminimised. See the following [https://bugs.launchpad.net/compiz/+bug/1328779 upstream bug report]. One possible solution is to enable the ''Keep previews of minimized windows'' option, located within the ''Workarounds'' plugin.
  
=== Get GNOME workspace switcher work with Compiz-Fusion ===
+
{{Note|If you use the Chrome/Chromium browser and you enable this workaround, you will need to ensure that the ''Use system title bar and borders'' option within Chrome is enabled. If Chrome's own titlebar is used with the ''Keep previews of minimized windows'' Compiz workaround then when Chrome is minimized, the desktop beneath will become unresponsive.}}
  
In older versions of Compiz, the Gnome Workspace Switcher applet would actually work with Compiz-Fusion (i.e. rotate cube/move plane etc.), but recent versions seem not to. This is due to a new feature introduced in Compiz, which allows real seperate workspaces. For example, if you have a desktop plane with four planes, and have four desktops enabled in Gnome, it sums up to a total of 16 different workspaces. Currently, there is no animation associated with "real" workspace changing. To get the Workspace Switcher work, set the following options in GConf:
+
=== Popout windows are offset when Compiz is running ===
  
/apps/compiz/general/screen0/options/number_of_desktops = '''1'''
+
You may find that popout windows for panels which are placed at the bottom of the screen are offset by a few pixels so that the window appears to float above the panel. This problem is known to affect Xfce and KDE and may affect other desktops as well. Listed below are a number of workarounds that might fix some cases.
/apps/compiz/general/screen0/options/hsize = 4 (this is an example)
+
/apps/compiz/general/screen0/options/vsize = 1 (this is an example)
+
  
=== Screen flicks with NVIDIA card ===
+
* Place the panel at the top of screen instead of the bottom - this should work in most cases.
 +
* Disable the ''Place Windows'' plugin - this works for the Xfce Whisker Menu plugin but may not work elsewhere.
 +
* Use fixed window placement to determine the window's position. This can be set from the ''Place Windows'' plugin. For instance, for the Whisker Menu, specify that the window with the title ''Whisker Menu'' should appear at (-1, -1).
 +
 
 +
For more information, see the following [https://bugs.launchpad.net/compiz/+bug/1419346 upstream bug report].
 +
 
 +
=== Alt-Tab switcher has no background (Emerald) ===
 +
 
 +
You may find that the {{ic|Alt-Tab}} switcher (provided by the staticswitcher or switcher plugins) has a completely transparent background when using Emerald as well. This can make it hard to differentiate window thumbnails from the desktop background behind them. As of [http://bazaar.launchpad.net/~compiz-team/compiz/0.9.12/revision/3975 revision 3975] a workaround is available. In CCSM, navigate to ''Application Switcher'' or ''Static Application Switcher'' depending on which plugin you are using. For the former, the ''Background'' settings are located under ''General'' and for the latter the settings are located under ''Appearance''. Once you have found the settings, ensure that the ''Set background color'' box is ticked. The default is a dark grey which can be optionally changed.
 +
 
 +
Alternatively, use GTK Window Decorator instead of Emerald or use a different window switcher altogether such as the shift switcher. Note that even if you are using the GTK Window Decorator, you can still change the background color as described above.
 +
 
 +
== Known issues ==
  
For fixing it, create /etc/modprobe.d/nvidia.conf file and add line:
+
=== Plugins in Compiz 0.8 are not present in Compiz 0.9 ===
options nvidia NVreg_RegistryDwords="PerfLevelSrc=0x2222"
+
  
=== Fix custom cursor theme on GNOME 2.30 ===
+
Many plugins that were popular in Compiz 0.8 (such as the Animations Add-On plugin) were disabled in Compiz versions 0.9.8 and above in order to complete [[Wikipedia:OpenGL ES|OpenGL ES]] support. Disabled plugins that receive patches for this issue may well be re-enabled in future releases. For more information, see the [https://launchpad.net/compiz/0.9.8/0.9.8.0 Compiz 0.9.8 release notes].
  
Create or edit /usr/share/icons/default/index.theme for default, or per user '''(non-root)''' ~/.icons/default/index.theme, and add this lines:
+
Likewise, Compiz Plugins Unsupported (a package which includes plugins such as ''Atlantis'') is unavailable in recent versions of Compiz 0.9. It has not been developed for the Compiz 0.9 series since Compiz 0.9.5 and no longer builds successfully.
  
[Icon Theme]
+
=== Xfce panel window buttons are not refreshed when a window changes viewport ===
#Name=''foo''
+
Name=''foo''
+
#Inherits=''foo''
+
Inherits=''foo''
+
[Desktop Entry]
+
Name[en_US]=index.theme
+
  
"Foo" is the name of the cursor theme.
+
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. This issue can be fixed by replacing {{Pkg|xfce4-panel}} with {{AUR|xfce4-panel-compiz}} which incorporates a patch for this issue. See the following [https://bugzilla.xfce.org/show_bug.cgi?id=10908 upstream bug report] for more information.
  
=== Screen artifacts on Firefox/Thunderbird ===
+
=== Compiz crashes when enabling the D-Bus plugin ===
  
{{Note|Altough this issue is not strictly related to Compiz, it has been added here due to popular misconception that Compiz itself may be the cause.}}
+
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 [https://bugs.launchpad.net/compiz/+bug/959395 upstream bug report].
  
Some users noticed a strange behavior with AMD/ATI Catalyst drivers starting from 10.6 release. Artifacts are visible mainly with Mozilla applications, where the GUI shows black spots of variable size. This is caused by different 2D acceleration tecnique introduced with Catalyst 10.6.
+
=== Workspace pager and window buttons issues ===
The problem can be fixed following the troubleshooting steps in the [[ATI_Catalyst#Black.2Fgrey.2Fwhite_boxes.2Fartifacts_mainly_in_firefox.2Fthunderbird|ATI Catalyst page]]
+
  
=== Setting the window manager back to Metacity after uninstall ===
+
Only a few [[List of applications#Taskbars / panels / docks|panels and docks]] are compatible with Compiz's [[Compiz configuration#Workspaces and Viewports|viewports]]. Incompatible panels and docks may display issues such as showing all window buttons in all workspaces or the workspace pager may only show one workspace available. The panels listed below are known to be compatible:
  
Removing Compiz with pacman does not set your window manager back to metacity. This can result in no window borders being drawn, an inability to minimize, and an inability to change the focus. To change it back, run the command "gconf-editor" in the terminal (install it if you do not have it already). Use this to set the value of the key {{ic|/desktop/gnome/session/required_components/window_manager}} from "compiz" to "metacity". Log out and back in for this change to take effect.
+
*{{Pkg|xfce4-panel}}
 +
*{{Pkg|mate-panel}}
 +
*{{Pkg|perlpanel}}
 +
*{{Pkg|gnome-panel}}
 +
*{{Pkg|cairo-dock}}
  
=== Context menu in applications (Firefox, ...?) disappears on mouseover ===
+
=== Xfce workspace switcher has wrong aspect ratio ===
  
Try disabling "focus stealing prevention" (general options).
+
When Compiz is used with Xfce Panel 4.11 and above, the workspace pager will use the width of only one workspace but will divide this space into ever smaller bars, according to how many viewports Compiz will specify. This issue can be fixed by replacing {{Pkg|xfce4-panel}} with {{AUR|xfce4-panel-compiz}} which incorporates a patch for this issue. For more information, see the following [https://bugzilla.xfce.org/show_bug.cgi?id=11697 upstream bug report].
  
=== See also ===
+
== See also ==
  
* [http://wiki.compiz.org/Troubleshooting Troubleshooting page] on compiz.org
+
* [https://launchpad.net/compiz Compiz in Launchpad]
* [http://compiz.org Compiz website], including wiki and forum
+
* [http://compiz.org Compiz Home], including wiki and forum (website and wiki are unmaintained)
 +
* [http://wiki.compiz.org/Troubleshooting Troubleshooting - Compiz Wiki], (wiki is unmaintained)

Latest revision as of 09:10, 19 April 2016

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.

Contents

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.

Installing the 0.9 series

Note:
  • From Compiz 0.9.8 onwards, all Compiz components are developed and distributed as a single project. This means that a single package can provide all of the Compiz components.
  • To have emerald-themes with emerald0.9, first install emerald0.9AUR and then install emerald-themesAUR. Doing the opposite will resolve the wrong dependencies and cause conflicts.

Required:

  • Compiz — OpenGL compositing window manager with CCSM, Plugins and GTK Window Decorator.
https://launchpad.net/compiz || compizAUR

Optional:

  • Emerald — A standalone window decorator for Compiz.
http://www.compiz.org/ || emerald0.9AUR
  • Emerald Themes — Extra themes for the Emerald window decorator.
http://www.northfield.ws/projects/compiz/ || emerald-themesAUR
  • Fusion Icon — A tray applet for starting Compiz and switching window managers and decorators on the fly.
https://github.com/kozec/fusion-icon-gtk3 || fusion-icon0.9AUR

Installing the 0.8 series

Note: The compiz-coreAUR package does not provide the GTK Window Decorator by default. Users of this package should use emeraldAUR for #Window decoration. Alternatively, use compiz-gtkAUR for a Compiz Core package that also provides GTK Window Decorator.

Required:

  • Compiz Core — OpenGL compositing window manager.
http://www.northfield.ws/projects/compiz/ || compiz-coreAUR, compiz-gtkAUR

Highly recommended:

  • CompizConfig Settings Manager — Graphical settings manager for Compiz.
http://www.northfield.ws/projects/compiz/ || ccsmAUR
  • Compiz Fusion Plugins Main — Main plugins collection for Compiz.
http://www.northfield.ws/projects/compiz/ || compiz-fusion-plugins-mainAUR
  • Compiz Fusion Plugins Extra — Extra plugins collection for Compiz.
http://www.northfield.ws/projects/compiz/ || compiz-fusion-plugins-extraAUR

Optional:

  • Compiz Fusion Plugins Experimental — Experimental Compiz plugins.
http://www.northfield.ws/projects/compiz/ || compiz-fusion-plugins-experimentalAUR
  • Emerald — A standalone window decorator for Compiz.
http://www.northfield.ws/projects/compiz/ || emeraldAUR
  • Emerald Themes — Extra themes for the Emerald window decorator.
http://www.northfield.ws/projects/compiz/ || emerald-themesAUR
  • Fusion Icon — A tray applet for starting Compiz and switching window managers and decorators on the fly.
http://www.compiz.org/ || fusion-iconAUR

Starting Compiz

Enabling important plugins

Tip: Depending on which package you installed Compiz from, some of these plugins may already be activated.

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, see #Window decoration.
  • Move Window.
  • Resize Window.
  • Place Windows - configure window placement options.
  • Application Switcher - provides an Alt+Tab switcher - there are numerous alternative application switcher plugins, for example: Shift Switcher, Static Application Switcher and more. Not all of them use the Alt+Tab keybinding.

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

Window decoration

Tip: For information on selecting and managing themes, see: Compiz configuration#Window decoration themes.

The window decorator is the program which provides windows with borders. Unlike window managers such as Kwin or Xfwm which provide just one decorator, users of Compiz have a choice of three: GTK Window Decorator, KDE Window Decorator and Emerald. The GTK Window Decorator and the KDE Window Decorator are included in the Compiz source and can be optionally compiled whilst building Compiz. Emerald, on the other hand, is a separate, standalone decorator. The Window Decoration plugin in CCSM must be ticked otherwise no window decorator will be started.

Choosing the decorator

The window decorator that will be started is specified under CCSM -> Effects -> Window Decoration -> Command. The command can be one of the following executables: emerald, gtk-window-decorator, kde4-window-decorator. Use the --replace switch, e.g. emerald --replace, if specifying the decorator executable on its own is not sufficient.

Tip: In Compiz 0.9, the decorator command is set to compiz-decorator by default. This is a script which will search for the emerald, gtk-window-decorator and kde4-window-decorator executables in that order and start the first one that it finds.

Compiz startup

Note: Some Compiz versions may require you to manually load the CCP plugin on startup: compiz --replace ccp [1]

You can start Compiz using the following command:

$ compiz --replace

See compiz --help for more options.

Fusion Icon

Tip: When #Autostarting Compiz in a desktop environment fusion-icon can be set as the default command instead of compiz.

To start Compiz using Fusion Icon, execute the command below:

$ 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 is not selected already.

Autostarting Compiz in a desktop environment

See Desktop environment#Custom 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 for example - all that is required is to create a .desktop file in /usr/share/xsessions that executes compiz (with command line options if needed) or fusion-icon. See the article for your display manager. See Desktop entries for information on creating a .desktop file.

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. Another option is for the .desktop file in /usr/share/xsessions to not execute compiz directly but to execute a script which starts the programs you wish to start and also starts Compiz.

Starting the session with startx

A Compiz session can be started with startx. Define either compiz or fusion-icon in your .xinitrc file. 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 install compiz-boxmenuAUR. This program is a fork of compiz-deskmenuAUR.

Then 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 or another key/mouse button combination of choice. Take care not to use a combination that is already used for other functionality.

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.

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-boxmenuAUR - see above. For more detailed information on shutting down see the following article: Allow users to shutdown.

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

using kwin, metacity or xfwm4 for example 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 MATE Compatibility plugin in CCSM (use the Gnome Compatibility plugin for older Compiz versions which lack the MATE plugin).
  • 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, map the command to the Alt+F2 key combination using the Commands plugin in CCSM.

Other run dialogs

Map the command for a run dialog of choice to the Alt+F2 key combination using the Commands plugin in CCSM.

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 &

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 &

This workaround was 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, use the following command to start Compiz (this command must be used every time).

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

Compiz starts without window borders with NVIDIA binary drivers

Firstly, ensure that your window decorator settings are configured correctly - see #Window decoration. 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 with 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"

Video tearing

If you experience video tearing when using Compiz, try enabling the Workarounds plugin in CCSM. Once enabled, ensure that the following options are enabled in Workarounds: Force complete redraw on initial damage, Force full screen redraws (buffer swap) on repaint.

If you are using Intel graphics and the workaround above does not fix the video tearing, see Intel graphics#Tear-free video.

Also see, #Poor performance from capable graphics cards.

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)

If Compiz replaces Xfwm4 at login, this can cause the Alt+F4 keybinding to become non-functional. To avoid this issue, ensure that only Compiz is started at login - see Xfce#Default window manager.

Emerald crashes when selecting a theme

You may find that Emerald crashes when selecting certain themes (especially themes that use the legacy engine). If this occurs, select another theme in Emerald Theme Manager and then run the command emerald --replace.

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.

PulseAudio users, as a workaround, can force PulseAudio to handle the system bell, see PulseAudio#X11 Bell Events.

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.

Windows lose focus when unminimised

You may find that certain windows (such as a Chromium window) will lose focus when unminimised. See the following upstream bug report. One possible solution is to enable the Keep previews of minimized windows option, located within the Workarounds plugin.

Note: If you use the Chrome/Chromium browser and you enable this workaround, you will need to ensure that the Use system title bar and borders option within Chrome is enabled. If Chrome's own titlebar is used with the Keep previews of minimized windows Compiz workaround then when Chrome is minimized, the desktop beneath will become unresponsive.

Popout windows are offset when Compiz is running

You may find that popout windows for panels which are placed at the bottom of the screen are offset by a few pixels so that the window appears to float above the panel. This problem is known to affect Xfce and KDE and may affect other desktops as well. Listed below are a number of workarounds that might fix some cases.

  • Place the panel at the top of screen instead of the bottom - this should work in most cases.
  • Disable the Place Windows plugin - this works for the Xfce Whisker Menu plugin but may not work elsewhere.
  • Use fixed window placement to determine the window's position. This can be set from the Place Windows plugin. For instance, for the Whisker Menu, specify that the window with the title Whisker Menu should appear at (-1, -1).

For more information, see the following upstream bug report.

Alt-Tab switcher has no background (Emerald)

You may find that the Alt-Tab switcher (provided by the staticswitcher or switcher plugins) has a completely transparent background when using Emerald as well. This can make it hard to differentiate window thumbnails from the desktop background behind them. As of revision 3975 a workaround is available. In CCSM, navigate to Application Switcher or Static Application Switcher depending on which plugin you are using. For the former, the Background settings are located under General and for the latter the settings are located under Appearance. Once you have found the settings, ensure that the Set background color box is ticked. The default is a dark grey which can be optionally changed.

Alternatively, use GTK Window Decorator instead of Emerald or use a different window switcher altogether such as the shift switcher. Note that even if you are using the GTK Window Decorator, you can still change the background color as described above.

Known issues

Plugins in Compiz 0.8 are not present in Compiz 0.9

Many plugins that were popular in Compiz 0.8 (such as the Animations Add-On plugin) were disabled in Compiz versions 0.9.8 and above in order to complete OpenGL ES support. Disabled plugins that receive patches for this issue may well be re-enabled in future releases. For more information, see the Compiz 0.9.8 release notes.

Likewise, Compiz Plugins Unsupported (a package which includes plugins such as Atlantis) is unavailable in recent versions of Compiz 0.9. It has not been developed for the Compiz 0.9 series since Compiz 0.9.5 and no longer builds successfully.

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. This issue can be fixed by replacing xfce4-panel with xfce4-panel-compizAUR which incorporates a patch for this issue. See the following upstream bug report for more information.

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.

Workspace pager and window buttons issues

Only a few panels and docks are compatible with Compiz's viewports. Incompatible panels and docks may display issues such as showing all window buttons in all workspaces or the workspace pager may only show one workspace available. The panels listed below are known to be compatible:

Xfce workspace switcher has wrong aspect ratio

When Compiz is used with Xfce Panel 4.11 and above, the workspace pager will use the width of only one workspace but will divide this space into ever smaller bars, according to how many viewports Compiz will specify. This issue can be fixed by replacing xfce4-panel with xfce4-panel-compizAUR which incorporates a patch for this issue. For more information, see the following upstream bug report.

See also