Difference between revisions of "Compiz"

From ArchWiki
Jump to: navigation, search
(As a standalone window manager)
(General cleanups)
Line 23: Line 23:
 
== Requirements ==
 
== 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]].
+
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.
  
 
== Installation ==
 
== Installation ==
  
Install [https://aur.archlinux.org/packages.php?K=compiz packages], available in [[AUR]] (known up to date packages: {{AUR|compiz-bzr}}).
+
Install [https://aur.archlinux.org/packages.php?K=compiz packages], available in [[AUR]].
  
 
=== Initial configuration ===
 
=== Initial configuration ===
  
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".
+
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.
+
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 {{ic|emerald}} as your default window decorator type:
  
To set '''emerald''' as your default window-decorator type:
 
 
  $ emerald --replace
 
  $ emerald --replace
To set the '''kde-window-decorator''' as an alternative to Emerald type:
+
 
 +
To set the {{ic|kde-window-decorator}} as an alternative to Emerald type:
 +
 
 
  $ kde4-window-decorator --replace
 
  $ kde4-window-decorator --replace
To set the '''compiz-decorator-gtk''' as an alternative to Emerald type:
+
 
 +
To set the {{ic|compiz-decorator-gtk}} as an alternative to Emerald type:
 +
 
 
  $ gtk-window-decorator --replace
 
  $ 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.}}
+
{{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". These can be enabled with {{ic|ccsm}}.}}
  
 
== Additional software ==
 
== Additional software ==
Line 55: Line 60:
  
 
* {{AUR|ccsm}} (CompizConfig settings manager) - GUI application that lets you configure all of Compiz's plugins
 
* {{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
+
* {{AUR|fusion-icon}} - offers a tray icon and a nice way to start Compiz, start CCSM and change the Window Manager/Decorator
  
 
== Starting Compiz Fusion ==
 
== Starting Compiz Fusion ==
Line 68: Line 73:
 
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.
 
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):
+
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
 
  $ 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.
+
'''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") ===
 
=== Manually (without "fusion-icon") ===
Line 78: Line 83:
 
  $ compiz --replace ccp &
 
  $ compiz --replace ccp &
  
A quick overview over common compiz command-line options:
+
A quick overview over common Compiz command-line options:
 
* {{ic|--indirect-rendering}}: use indirect-rendering (AIGLX)
 
* {{ic|--indirect-rendering}}: use indirect-rendering (AIGLX)
 
* {{ic|--loose-binding}}: can help performance issues (NVIDIA?)
 
* {{ic|--loose-binding}}: can help performance issues (NVIDIA?)
 
* {{ic|--replace}}: replace current window-manager
 
* {{ic|--replace}}: replace current window-manager
* {{ic|--keep-window-hints}}: keep the gnome window-manager gconf-settings for available viewports, ...
+
* {{ic|--keep-window-hints}}: keep the gnome window manager gconf-settings for available viewports
 
* {{ic|--sm-disable}}: disable session-management
 
* {{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.
+
* {{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 ===
 
=== 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.}}
+
{{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)====
 
==== Use System Settings (easiest)====
Line 110: Line 115:
 
==== Autostart with "fusion-icon" ====
 
==== Autostart with "fusion-icon" ====
  
Add a symbolic link, that points to the fusion-icon executable, in your KDE Autostart directory:
+
Add a symbolic link, that points to {{ic|fusion-icon}}, in your KDE Autostart directory:
 
  $ ln -s /usr/bin/fusion-icon ~/.kde4/Autostart/fusion-icon
 
  $ ln -s /usr/bin/fusion-icon ~/.kde4/Autostart/fusion-icon
  
Next time KDE is started, it will load fusion-icon automatically.
+
Next time KDE is started, it will load {{ic|fusion-icon}} automatically.
  
 
==== Autostart link without "fusion-icon" ====
 
==== Autostart link without "fusion-icon" ====
  
{{Warning|Do '''not''' create {{ic|compiz.desktop}} if you intend to install {{pkg|compiz-decorator-gtk}}; it will create a file conflict.}}
+
{{Warning|Do '''not''' create {{ic|compiz.desktop}} if you intend to install {{AUR|compiz-decorator-gtk}}; it will create a file conflict.}}
  
 
* Append a desktop entry in the KDE Autostart directory. If it doesn't exist already (it should), create it:
 
* Append a desktop entry in the KDE Autostart directory. If it doesn't exist already (it should), create it:
Line 152: Line 157:
 
==== Export KDEWM without "fusion-icon" (preferred) ====
 
==== 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.
+
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
 
  $ 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:
+
{{Note|If this line doesn't work, make sure the {{AUR|fusion-icon}} package is installed and then use this line instead:
 +
 
 
  $ echo "fusion-icon &" > /usr/bin/compiz-fusion
 
  $ echo "fusion-icon &" > /usr/bin/compiz-fusion
 +
 
Be sure to complete the whole method before trying this substitute.}}
 
Be sure to complete the whole method before trying this substitute.}}
  
Ensure that {{ic|/usr/bin/compiz-fusion}} has executable ('''+x''') permissions.
+
Ensure that {{ic|/usr/bin/compiz-fusion}} has executable ({{ic|+x}}) permissions.
  $ chmod a+x /usr/bin/compiz-fusion
+
 
 +
  $ chmod +x /usr/bin/compiz-fusion
  
 
Choose one of the following:
 
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.
+
1) For your user only:
: {{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.
+
{{hc|~/.kde4/env/compiz.sh|2=
: {{bc|1=KDEWM="compiz-fusion"}}
+
KDEWM="compiz-fusion"
 +
}}
 +
 
 +
2) System-wide:
 +
 
 +
{{hc|/etc/kde/env/compiz.sh|2=
 +
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:
 
* If that still doesn't work, yet another alternate way to accomplish the above method is to include the line:
  export KDEWM="compiz-fusion"
+
 
 +
  $ export KDEWM="compiz-fusion"
 +
 
 
in your user's {{ic|~/.bashrc}} file.
 
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:
 
* 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"
+
 
 +
  $ export KDEWM="/usr/local/bin/compiz-fusion"
 
}}
 
}}
  
 
=== GNOME ===
 
=== GNOME ===
  
If you have installed [[GNOME3]] with gnome-shell, either enable forced Fallback mode (System Info > Graphics) or simply uninstall gnome-shell.
+
If you have installed [[GNOME3]] with gnome-shell, either enable forced Fallback mode (''System Info'' > ''Graphics'') or simply uninstall {{pkg|gnome-shell}}.
{{Note|Fallback mode is not necessary if you choose the Compiz/Cairo-Dock session method below.}}
+
{{Note|Fallback mode is not necessary if you choose the Compiz/Cairo Dock session method below.}}
  
 
==== Alternate Session for GNOME (preferred method for experienced Compiz/Dock users) ====
 
==== Alternate Session for GNOME (preferred method for experienced Compiz/Dock users) ====
  
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.
+
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.
  
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).
+
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 should work fine).
  
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:
+
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:
* 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 Application Menu icon to Cairo Dock and remember its key-bindings.
 +
* Remap Application Menu key-bindings to {{ic|ALT+F1}} and {{ic|ALT+F2}}, for convenience.
 
* Add Clock, WiFi, NetSpeed icons to the dock as applicable.
 
* Add Clock, WiFi, NetSpeed icons to the dock as applicable.
 
* Add Log-out icon:
 
* Add Log-out icon:
** Set the command for logout to "gnome-session-quit --logout"
+
** Set the command for logout to {{ic|gnome-session-quit --logout}}
** Set the command for shutdown to "gnome-session-quit --power-off"
+
** Set the command for shutdown to {{ic|gnome-session-quit --power-off}}
* Add the Notification Area Old (systray) icon to Cairo-Dock.
+
* Add the Notification Area Old (systray) icon to Cairo Dock.
  
 
==== Autostart (without "fusion-icon") (preferred method) ====
 
==== Autostart (without "fusion-icon") (preferred method) ====
Line 202: Line 221:
 
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.
 
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.
  
'''1)'''If the following file doesn't already exist (it should), create it {{ic|/usr/share/applications/compiz.desktop}} containing the following:
+
1) If the following file doesn't already exist (it should), create it  
  
[Desktop Entry]
+
{{hc|/usr/share/applications/compiz.desktop|2=
Type=Application
+
[Desktop Entry]
Encoding=UTF-8
+
Type=Application
Name=Compiz
+
Encoding=UTF-8
Exec=/usr/bin/compiz ccp  #Make sure ccp is included so that Compiz loads your previous settings.
+
Name=Compiz
NoDisplay=true
+
Exec=/usr/bin/compiz ccp  #Make sure ccp is included so that Compiz loads your previous settings.
# name of loadable control center module
+
NoDisplay=true
X-GNOME-WMSettingsModule=compiz
+
# name of loadable control center module
# autostart phase
+
X-GNOME-WMSettingsModule=compiz
##-> the folloing line cause gnome-session warning and slow startup, so try not to enable this
+
# autostart phase
# X-GNOME-Autostart-Phase=WindowManager  
+
##-> the following line cause gnome-session warning and slow startup, so try not to enable this
X-GNOME-Provides=windowmanager
+
# X-GNOME-Autostart-Phase=WindowManager  
# name we put on the WM spec check window
+
X-GNOME-Provides=windowmanager
X-GNOME-WMName=Compiz
+
# name we put on the WM spec check window
# back compat only
+
X-GNOME-WMName=Compiz
X-GnomeWMSettingsLibrary=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.}}
 
{{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.}}
Line 227: Line 248:
 
  Exec=/usr/bin/compiz ccp --indirect-rendering
 
  Exec=/usr/bin/compiz ccp --indirect-rendering
  
or
+
or:
  
  Exec=/usr/bin/compiz --replace --sm-disable --ignore-desktop-hints ccp --indirect-rendering
+
  Exec=/usr/bin/compiz --replace --sm-disable --ignore-desktop-hints ccp --indirect-rendering:
  
Instead of
+
Instead of:
  
 
  Exec=/usr/bin/compiz ccp
 
  Exec=/usr/bin/compiz ccp
  
 
Some Users noticed a "lag" of 4-10 seconds when loging in from a login manager. The solution is to change the command to:
 
Some Users noticed a "lag" of 4-10 seconds when loging in from a login manager. The solution is to change the command to:
 +
 
  Exec=bash -c 'compiz ccp decoration --sm-client-id $DESKTOP_AUTOSTART_ID'
 
  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.
 
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.
  
Line 244: Line 267:
  
 
  gconftool-2 --set -t string /desktop/gnome/session/required_components/windowmanager compiz
 
  gconftool-2 --set -t string /desktop/gnome/session/required_components/windowmanager compiz
 
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.
 
 
gconftool-2 --set -t string /desktop/gnome/applications/window_manager/current /usr/bin/compiz
 
gconftool-2 --set -t string /desktop/gnome/applications/window_manager/default /usr/bin/compiz
 
  
 
==== Autostart (without "fusion-icon") (with GNOME fallback mode session) ====
 
==== Autostart (without "fusion-icon") (with GNOME fallback mode session) ====
  
Edit file {{ic|/usr/share/gnome-session/sessions/gnome-fallback.session}}:
+
Do the following
 
+
{{hc|/usr/share/gnome-session/sessions/gnome-fallback.session|2=
Replace your windows manager (gnome-shell,metacity...) with ''compiz'' in '''RequiredComponents''' line.
+
RequiredComponents=''compiz'';gnome-settings-daemon;
 
+
RequiredProviders=windowmanager;notifications;
Change ''DefaultProvider-windowmanager'' line to ''DefaultProvider-windowmanager=compiz''
+
DefaultProvider-windowmanager=''compiz''
 
+
DefaultProvider-notifications=notification-daemon
Here is part of my {{ic|gnome-fallback.session}}:
+
}}
 
+
RequiredComponents=compiz;gnome-settings-daemon;
+
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.
+
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) ====
+
 
+
This is a way that works if you use GDM (and I'd assume KDM too).
+
 
+
Make a file called /usr/local/bin/compiz-start-boot with the contents:
+
#!/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:
+
[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.
+
  
 
==== Autostart (with "fusion-icon") ====
 
==== Autostart (with "fusion-icon") ====
  
To start Compiz fusion automatically when starting a session go to System > Preferences > Startup Applications. In the Startup Programs tab, click the Add button.
+
To start Compiz Fusion automatically when starting a session go to ''System'' > ''Preferences'' > ''Startup Applications''. In the ''Startup Programs'' tab, click the ''Add'' button.
  
You will now see the Add Startup Program dialogue. Fill it in as follows.
+
You will now see the ''Add Startup Program'' dialogue. Fill it in as follows.
  
 
Name:
 
Name:
Line 300: Line 290:
 
Comment:  (Put anything you like or leave blank.)
 
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.
+
{{Note|You can also use {{ic|compiz --replace ccp}} instead of the Fusion Icon to load Compiz.
  
The ccp value will tell compiz to load your previous Compiz settings as configured with CompizConfig Settings Manager ('''ccsm''').}}
+
The ccp value will tell compiz to load your previous Compiz settings as configured with CompizConfig Settings Manager ({{ic|ccsm}}.}}
  
 
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.
 
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 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.
+
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.
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.}}
+
$ 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.}}
  
 
=== Mate desktop ===
 
=== Mate desktop ===
Line 316: Line 307:
  
 
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 :
 
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 :
* 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
 
* on Mate 1.6 and higher, edit the following gsettings value
  gsettings set org.mate.session.required-components windowmanager compiz
+
 
 +
  $ gsettings set org.mate.session.required-components windowmanager compiz
  
 
=== XFCE ===
 
=== XFCE ===
Line 351: Line 339:
 
   </property>
 
   </property>
  
{{Note|The ccp value will tell compiz to load your previous Compiz settings as configured with CompizConfig Settings Manager (ccsm).}}
+
{{Note|The ccp value will tell Compiz to load your previous Compiz settings as configured with CompizConfig Settings Manager (ccsm).}}
  
 
To prevent the default session from being overwritten you may also add this:
 
To prevent the default session from being overwritten you may also add this:
Line 361: Line 349:
 
   </property>
 
   </property>
  
To remove the existing sessions, run:
+
To remove the existing sessions:
 +
 
 
  $ rm -r ~/.cache/sessions
 
  $ rm -r ~/.cache/sessions
  
Line 371: Line 360:
 
This will load Xfwm first then replace it with Compiz.
 
This will load Xfwm first then replace it with Compiz.
  
Open the XFCE Settings Manager & then Sessions & Startup. Click the Application Autostart tab.
+
Open ''XFCE Settings Manager'' > ''Sessions & Startup'' > ''Application Autostart'':
  
Add
 
 
   (Name:) Compiz Fusion
 
   (Name:) Compiz Fusion
  
 
   (Command:) fusion-icon
 
   (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).}}
+
{{Note|You can also use {{ic|compiz --replace ccp}} instead of the Fusion Icon to load Compiz. The {{ic|ccp}} value will tell compiz to load your previous Compiz settings as configured with CompizConfig Settings Manager (ccsm).}}
  
 
===== Method 2 =====
 
===== Method 2 =====
Line 384: Line 372:
 
Edit the file {{ic|~/.config/xfce4-session/xfce4-session.rc}} (settings in this file is used in preference).
 
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}}.
+
Or to make the change for all Xfce users:
  
Add the following
+
{{hc|/etc/xdg/xfce4-session/xfce4-session.rc|2=
[Failsafe Session]
+
[...]
Client0_Command=fusion-icon
+
[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.
 
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
+
To prevent the default session from being overwritten you may also add:
[General]
+
 
AutoSave=false
+
{{hc|/etc/xdg/xfce4-session/xfce4-session.rc|2=
SaveOnExit=false
+
[General]
 +
AutoSave=false
 +
SaveOnExit=false
 +
}}
  
 
To remove the existing sessions
 
To remove the existing sessions
  rm -R ~/.cache/sessions
+
 
 +
  $ rm -r ~/.cache/sessions/
  
 
===== Method 3 =====
 
===== Method 3 =====
  
 
Check if this file exists:
 
Check if this file exists:
 +
 
  ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml
 
  ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml
  
 
If not, do:
 
If not, do:
 +
 
  cp /etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml
 
  cp /etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml
  
Line 431: Line 425:
  
 
finally remove old xfce4 sessions:
 
finally remove old xfce4 sessions:
 +
 
  $ rm -r ~/.cache/sessions/
 
  $ rm -r ~/.cache/sessions/
  
Line 466: Line 461:
  
 
To add a root menu similar to that in Openbox, Fluxbox, Blackbox etc. you must install the package {{AUR|compiz-deskmenu}}.
 
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.
+
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 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 {{ic|Ctrl+Space}}.
  
If it still does not work, enter the Viewport Switcher menu, and change "Plugin for initiate action" to 'commands', and "Action name for initiate" to run_command0_key.
+
If it still does not work, enter the Viewport Switcher menu, and change "Plugin for initiate action" to 'commands', and "Action name for initiate" to {{ic|run_command0_key}}.
  
 
An alternative is to use {{AUR|mygtkmenu}}, also in [[AUR]].
 
An alternative is to use {{AUR|mygtkmenu}}, also in [[AUR]].
Line 476: Line 471:
 
==== Allow users to shutdown/reboot ====
 
==== 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.
+
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 ==
 
== Miscellaneous ==
Line 486: Line 481:
 
=== Using gtk-window-decorator ===
 
=== 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.
+
In order to use gtk-window-decorator, install the package {{AUR|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 ===
 
=== gconf: additional Compiz configurations ===
Line 494: Line 489:
 
  $ 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.
+
Note that now compiz-core isn't built with gconf support; It is now built with gconf support through {{ic|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''.
+
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.
+
"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 ===
 
=== 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
+
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 {{ic|~/.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 {{ic|xfce4-session.xml}} file look like this
  
 
  <property name="Client0_Command" type="array">
 
  <property name="Client0_Command" type="array">
Line 516: Line 511:
 
  LIBGL_ALWAYS_INDIRECT=1 compiz --sm-disable --ignore-desktop-hints ccp --indirect-rendering
 
  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.
+
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 ==
 
== Tips and tricks ==
Line 526: Line 521:
 
  ''wm_name'' --replace
 
  ''wm_name'' --replace
  
with kwin, metacity or xfwm4 instead of ''wm_name''.
+
with {{ic|kwin}}, {{ic|metacity}} or {{ic|xfwm4}} instead of {{ic|wm_name}}.
  
 
=== Keyboard shortcuts ===
 
=== Keyboard shortcuts ===
Line 538: Line 533:
 
* Resize window = {{ic|Alt+Right 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''').
+
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.
  
 
== Troubleshooting ==
 
== Troubleshooting ==
  
{{Out of date}}
+
{{Out of date|-}}
  
 
=== Missing GLX_EXT_texture_from_pixmaps ===
 
=== Missing GLX_EXT_texture_from_pixmaps ===
Line 553: Line 548:
 
  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 Fusion's binary was compiled against Mesa's OpenGL library rather than ATI's OpenGL library (which is what you are using).
  
 
copy the library into a directory to keep it because ATI's drivers will over write it.   
 
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
+
  
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:  
+
Once you have it copied, you can reinstall your fglrx drivers.  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 :
+
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:
  
  LIBGL_ALWAYS_INDIRECT=1 compiz --replace ccp &
+
LIBGL_ALWAYS_INDIRECT=1 compiz --replace ccp &
  
 
(Workaround tested on the following card : ATI Technologies Inc Radeon R250 [Mobility FireGL 9000] (rev 02))
 
(Workaround tested on the following card : ATI Technologies Inc Radeon R250 [Mobility FireGL 9000] (rev 02))
Line 582: Line 576:
 
=== Compiz starts, but no effects are visible ===
 
=== Compiz starts, but no effects are visible ===
  
If you have installed compiz-decorator-gtk:
+
If you have installed {{ic|compiz-decorator-gtk}}:
 
Check if GConf schema was correctly installed:  
 
Check if GConf schema was correctly installed:  
  gconftool-2 -R /apps/compiz/plugins | grep plugins
+
 
 +
$ 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!!!):  
 
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.}}
+
$ 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.}}
  
 
=== Compiz starts, but gtk-window-decorator does not ===
 
=== Compiz starts, but gtk-window-decorator does not ===
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.
+
It is a configuration problem for gconf and gconfd. You may try removing {{ic|~/.gconf/}}. This will erase your Compiz settings, so be sure to reconfigure.
Finally exec as user:
+
Finally as user:
  
  gconftool-2 --install-schema-file=/usr/share/gconf/schemas/compiz-decorator-gtk.schemas
+
$ gconftool-2 --install-schema-file=/usr/share/gconf/schemas/compiz-decorator-gtk.schemas
  
 
=== Compiz appears to start, but there are no window borders ===
 
=== Compiz appears to start, but there are no window borders ===
  
When you run fusion-icon from commandline, you get output like this:
+
When running Fusion Icon from terminal, you get output like this:
  
* Detected Session: gnome
+
{{hc|$ fusion-icon|2=
* Searching for installed applications...
+
* Detected Session: gnome
* NVIDIA on Xorg detected, exporting: __GL_YIELD=NOTHING
+
* Searching for installed applications...
* Using the GTK Interface
+
* NVIDIA on Xorg detected, exporting: __GL_YIELD=NOTHING
* Metacity is already running
+
* Using the GTK Interface
* Setting window manager to Compiz
+
* Metacity is already running
... executing: compiz --replace --sm-disable --ignore-desktop-hints ccp
+
* Setting window manager to Compiz
compiz (core) - Warn: No GLXFBConfig for depth 32
+
... 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
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.
+
}}
 
+
----
+
  
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.
+
You may also try adding ''Option "AddARGBGLXVisuals" "True"'' and ''Option "DisableGLXRootClipping" "True"'' to your "Screen" section, if you are using the NVIDIA binary driver. If you used any other Options elsewhere in {{ic|/etc/X11/xorg.conf.d/}} to get Compiz working and still have no luck, try commenting them out and using only the aformentioned ARGBGLXVisuals and GLXRootClipping Options.
  
{{Note|Check that "Window decoration", "Move" and "Resize" plugins are enabled with Compiz Settings Manager or gconf-editor.}}
+
{{Note|Check that "Window decoration", "Move" and "Resize" plugins are enabled with Compiz Settings Manager or {{Pkg|gconf-editor}}.}}
  
With gconf-editor you can easly enable "Window decoration", "Move" and "Resize" plugins.
+
With  {{ic|gconf-editor}} you can easly enable "Window decoration", "Move" and "Resize" plugins.
  
 
  $ gconf-editor
 
  $ gconf-editor
  
Navigate to ''apps > compiz > general > allscreens > options''.
+
Navigate to ''apps'' > ''compiz'' > ''general'' > ''allscreens'' > ''options''.
  
 
Add/Edit "active_plugins" Key (Name: active_plugins, Type: List, List type: String).
 
Add/Edit "active_plugins" Key (Name: active_plugins, Type: List, List type: String).
Line 632: Line 627:
 
Add "decoration", "move", and "resize" to the list.
 
Add "decoration", "move", and "resize" to the list.
  
----
+
Another way to fix this:
  
'''Another way to fix this''':
+
* Launch {{ic|ccsm}}.
* Launch '''ccsm'''.
+
* Find '''Window Decoration''' and make sure it is enabled.
* Find '''windows decoration''' and make sure it is enabled.
+
 
* Now click on it, to edit the options.
 
* Now click on it, to edit the options.
* If the entry behind '''command''' is empty, put the value '''gtk-window-decorator''' there.
+
* If the entry behind '''command''' is empty, use {{ic|gtk-window-decorator}} or {{ic|kde-window-decorator}} or {{ic|emerald}}.
** Alternatives are '''kde-window-decorator''' and '''emerald'''
+
* Close CCSM and the borders should now appear.
* Click '''Back''' and '''Close'''
+
* If all went well, the borders should appear.
+
  
 
=== Compiz starts and borders appear, but windows won't move ===
 
=== Compiz starts and borders appear, but windows won't move ===
  
Be sure you have the "Move Window" plugin installed and enabled in the Compiz settings manager.
+
Be sure you have the "Move Window" plugin installed and enabled in the CompizConfig Settings Manager.
  
 
=== Blank screen on resume from suspend-to-ram using the NVIDIA binary drivers ===
 
=== Blank screen on resume from suspend-to-ram using the NVIDIA binary drivers ===
Line 651: Line 643:
 
If you receive a blank screen with a responsive cursor upon resume, try disabling sync to vblank:
 
If you receive a blank screen with a responsive cursor upon resume, try disabling sync to vblank:
  
  gconftool -s /apps/compiz/general/screen0/options/sync_to_vblank-t boolean false
+
  $ gconftool -s /apps/compiz/general/screen0/options/sync_to_vblank-t boolean false
  
=== fusion-icon doesn't start ===
+
=== Fusion Icon doesn't start ===
  
 
If you get an output like this from the command line:
 
If you get an output like this from the command line:
$ fusion-icon
+
{{hc|$ fusion-icon|
  * Detected Session: gnome
+
* Detected Session: gnome
  * Searching for installed applications...
+
* Searching for installed applications...
Traceback (most recent call last):
+
Traceback (most recent call last):
  File "/usr/bin/fusion-icon", line 57, in <module>
+
  File "/usr/bin/fusion-icon", line 57, in <module>
    from FusionIcon.interface import choose_interface
+
    from FusionIcon.interface import choose_interface
  File "/usr/lib/python2.5/site-packages/FusionIcon/interface.py", line 23, in <module>
+
  File "/usr/lib/python2.5/site-packages/FusionIcon/interface.py", line 23, in <module>
    import start
+
    import start
  File "/usr/lib/python2.5/site-packages/FusionIcon/start.py", line 36, in <module>
+
  File "/usr/lib/python2.5/site-packages/FusionIcon/start.py", line 36, in <module>
    config.check()
+
    config.check()
  File "/usr/lib/python2.5/site-packages/FusionIcon/util.py", line 362, in check
+
  File "/usr/lib/python2.5/site-packages/FusionIcon/util.py", line 362, in check
    os.makedirs(self.config_folder)
+
    os.makedirs(self.config_folder)
  File "/usr/lib/python2.5/os.py", line 172, in makedirs
+
  File "/usr/lib/python2.5/os.py", line 172, in makedirs
    mkdir(name, mode)
+
    mkdir(name, mode)
OSError: [Errno 13] Permission denied: '/home/andy/.config/compiz'
+
OSError: [Errno 13] Permission denied: '/home/andy/.config/compiz'
 +
}}
 +
 
 +
the problem is with the permission on {{ic|~/.config/compiz/}}. To fix it, use:
  
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)
+
  # chown -R <username> /home/<username>/.config/compiz/
  chown <username> /home/<username>/.config/compiz
+
  
 
=== Choppy animations, even though everything configured correctly ===
 
=== Choppy animations, even though everything configured correctly ===
  
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.
+
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.
  
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:
+
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 {{ic|/etc/X11/xorg.conf.d/*.conf}}, and then restarting your computer:
  
 
  Option "DynamicTwinView" "False"
 
  Option "DynamicTwinView" "False"
Line 687: Line 681:
 
=== Fix GNOME screenshot ===
 
=== Fix GNOME screenshot ===
  
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).
+
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).
  
=== Get GNOME workspace switcher work with Compiz-Fusion ===
+
=== Get GNOME workspace switcher work with Compiz Fusion ===
  
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:
+
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:
  
 
  /apps/compiz/general/screen0/options/number_of_desktops = '''1'''
 
  /apps/compiz/general/screen0/options/number_of_desktops = '''1'''
  /apps/compiz/general/screen0/options/hsize = 4 (this is an example)
+
  /apps/compiz/general/screen0/options/hsize = '''4''' (this is an example)
  /apps/compiz/general/screen0/options/vsize = 1 (this is an example)
+
  /apps/compiz/general/screen0/options/vsize = '''1''' (this is an example)
  
 
=== Screen flicks with NVIDIA card ===
 
=== Screen flicks with NVIDIA card ===
  
For fixing it, create /etc/modprobe.d/nvidia.conf file and add line:
+
To fix it, create the following:
options nvidia NVreg_RegistryDwords="PerfLevelSrc=0x2222"
+
{{hc|/etc/modprobe.d/nvidia.conf|2=
 
+
options nvidia NVreg_RegistryDwords="PerfLevelSrc=0x2222"
=== Fix custom cursor theme on GNOME 2.30 ===
+
}}
 
+
Create or edit /usr/share/icons/default/index.theme for default, or per user '''(non-root)''' ~/.icons/default/index.theme, and add this lines:
+
 
+
[Icon Theme]
+
#Name=''foo''
+
Name=''foo''
+
#Inherits=''foo''
+
Inherits=''foo''
+
[Desktop Entry]
+
Name[en_US]=index.theme
+
 
+
"Foo" is the name of the cursor theme.
+
 
+
=== Screen artifacts on Firefox/Thunderbird ===
+
 
+
{{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.}}
+
 
+
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.
+
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 ===
 
=== Setting the window manager back to Metacity after uninstall ===
  
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.
+
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 {{ic|gconf-editor}}. 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 changes to take effect.
 
+
=== Context menu in applications (Firefox, ...?) disappears on mouseover ===
+
 
+
Try disabling "focus stealing prevention" (general options).
+
  
 
=== See also ===
 
=== See also ===

Revision as of 17:21, 6 October 2013

Template:Article summary start Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary end

Compiz is a 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.

Note: Since May 2013 Compiz has been dropped to the AUR.

Contents

Requirements

Users of major DEs can make good use of compiz-managerAUR, performing brief requirements checking and switching to fallback WM in case of errors.

Installation

Install packages, available in AUR.

Initial configuration

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". These can be enabled with ccsm.

Additional software

Decorators

  • Emerald — Compiz's own window decorator with few dependencies.
http://www.compiz.org || emeraldAUR
Note: Buggy and hasn't received changes since November 2010.
  • compiz-decorator-gtk, compiz-decorator-kde — Alternatives to Emerald, using your desktop environment's configuration backends and looks.
http://www.compiz.org || compiz-bzrAUR

Other

  • ccsmAUR (CompizConfig settings manager) - GUI application that lets you configure all of Compiz's plugins
  • fusion-iconAUR - offers a tray icon and a nice way to start Compiz, start CCSM and change the Window Manager/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:

  • --indirect-rendering: use indirect-rendering (AIGLX)
  • --loose-binding: can help performance issues (NVIDIA?)
  • --replace: replace current window-manager
  • --keep-window-hints: keep the gnome window manager gconf-settings for available viewports
  • --sm-disable: disable session-management
  • ccp: the "ccp" command loads the last configured settings from CCSM (CompizConfig Settings Manager) otherwise Compiz will load with no settings and you won't be able to do anything with your windows like dragging, maximizing/minimizing, or moving.

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", then create the following script:

/usr/local/bin/compiz-kde-launcher
#!/bin/bash
LIBGL_ALWAYS_INDIRECT=1
compiz --replace ccp &
wait

Then make it executable:

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

When running fusion-icon from a terminal you can see the command line with which Compiz was started.

Autostart with "fusion-icon"

Add a symbolic link, that points to fusion-icon, 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-gtkAUR; it will create a file conflict.
  • Append a desktop entry in the KDE Autostart directory. If it doesn't exist already (it should), 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
Note: If compiz.desktop already exists, you may have to add --replace and/or ccp to the Exec variable. Without --replace, Compiz won't load since it will detect another window manager already loaded. Without ccp, Compiz will not load any of the settings and plugins that you have enabled through CompizConfig Settings Manager (ccsm) and you won't be able to manipulate any of your windows.
  • If you want to use the optional Fusion Icon application, launch fusion-icon. If you log out normally with Fusion Icon running, KDE should restore your session and launch it the next time you log in, if you have the following enabled (also available in System Settings > Startup and Shutdown > Session Management > Restore previous session):
~/.kde4/share/config/ksmserverrc
[General]
[...]
loginMode=restorePreviousLogout
[...]

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 $ 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-iconAUR 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 /usr/bin/compiz-fusion has executable (+x) permissions.

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

Choose one of the following:

1) For your user only:

~/.kde4/env/compiz.sh
KDEWM="compiz-fusion"

2) System-wide:

/etc/kde/env/compiz.sh
KDEWM="compiz-fusion"
Note:
  • If that still doesn't work, yet another alternate way to accomplish the above method is to include the line:
$ export KDEWM="compiz-fusion"

in your user's ~/.bashrc file.

  • If you optionally use the /usr/local/bin directory it may not work. In that case you should export the script including the whole path:
$ export KDEWM="/usr/local/bin/compiz-fusion"

GNOME

If you have installed GNOME3 with gnome-shell, either enable forced Fallback mode (System Info > Graphics) or simply uninstall gnome-shell.

Note: Fallback mode is not necessary if you choose the Compiz/Cairo Dock session method below.

Alternate Session for GNOME (preferred method for experienced Compiz/Dock users)

The gnome-session-compizAUR 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.

For this method to work, Compiz and Cairo Dock (Taskbar/Panel) may have to be configured initially for fresh accounts, from another working session (CCSM in GNOME Shell should work fine).

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:

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

Autostart (without "fusion-icon") (preferred method)

This Method makes use of the 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.

1) If the following file doesn't already exist (it should), create it

/usr/share/applications/compiz.desktop
[Desktop Entry]
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 following 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 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.

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:

Exec=/usr/bin/compiz ccp --indirect-rendering

or:

Exec=/usr/bin/compiz --replace --sm-disable --ignore-desktop-hints ccp --indirect-rendering:

Instead of:

Exec=/usr/bin/compiz ccp

Some Users noticed a "lag" of 4-10 seconds when loging in from a login manager. The solution is to change the command to:

Exec=bash -c 'compiz ccp decoration --sm-client-id $DESKTOP_AUTOSTART_ID'

as noted 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: 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.
gconftool-2 --set -t string /desktop/gnome/session/required_components/windowmanager compiz

Autostart (without "fusion-icon") (with GNOME fallback mode session)

Do the following

/usr/share/gnome-session/sessions/gnome-fallback.session
RequiredComponents=compiz;gnome-settings-daemon;
RequiredProviders=windowmanager;notifications;
DefaultProvider-windowmanager=compiz
DefaultProvider-notifications=notification-daemon

Autostart (with "fusion-icon")

To start Compiz Fusion automatically when starting a session go to System > Preferences > Startup Applications. In the Startup Programs tab, click the Add button.

You will now see the Add Startup Program dialogue. Fill it in as follows.

Name:

Compiz Fusion

Command:

fusion-icon

Comment: (Put anything you like or leave blank.)

Note: You can also use compiz --replace ccp instead of the Fusion Icon to load Compiz. The ccp value will tell compiz to load your previous Compiz settings as configured with CompizConfig Settings Manager (ccsm.

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

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

Mate desktop

Autostart (without "fusion-icon") (preferred method)

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 :

  • on Mate 1.6 and higher, edit the following gsettings value
$ gsettings set org.mate.session.required-components windowmanager compiz

XFCE

XFCE autostart (without "fusion-icon")

This method will start Compiz directly through the XFCE session manager without loading Xfwm.

Please note the change to xml config files in XFCE newer than 4.2

To install the session manager, install xfce4-session.

Now we have to configure the default/failsafe session of XFCE.

Edit the ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml or (to make the change for all XFCE users) /etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml:

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>
Note: The ccp value will tell Compiz to load your previous Compiz settings as configured with CompizConfig Settings Manager (ccsm).

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

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

To remove the existing sessions:

$ 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 XFCE Settings Manager > Sessions & Startup > Application Autostart:

  (Name:) Compiz Fusion
  (Command:) fusion-icon
Note: You can also use compiz --replace ccp instead of the Fusion Icon to load Compiz. The ccp value will tell compiz to load your previous Compiz settings as configured with CompizConfig Settings Manager (ccsm).
Method 2

Edit the file ~/.config/xfce4-session/xfce4-session.rc (settings in this file is used in preference).

Or to make the change for all Xfce users:

/etc/xdg/xfce4-session/xfce4-session.rc
[...]
[Failsafe Session]
Client0_Command=fusion-icon

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:

/etc/xdg/xfce4-session/xfce4-session.rc
[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 ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml.

or (to make the changes for all xfce4 users) /etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml:

Edit Client0_Command to look like:

<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-coreAUR by itself is sufficient to start using Compiz Fusion. However ccsmAUR and emeraldAUR (or another window decorator) are additional highly recommended packages. fusion-iconAUR, compiz-fusion-plugins-mainAUR and compiz-fusion-plugins-extraAUR are also available.

To autostart Compiz Fusion configure .xinitrc to launch Compiz as:

~/.xinitrc
exec compiz ccp

You can also add other command-line options to your .xinitrc.

Or if using fusion-iconAUR:

~/.xinitrc
exec fusion-icon

However chances are you will need additional apps (e.g a panel) for optimal usability:

~/.xinitrc
tint2 &
cairo-dock &
exec fusion-icon
Note: Add a terminal-emulator to this autostart list while starting for the first time to help configure Compiz.

Add a root menu

To add a root menu similar to that in Openbox, Fluxbox, Blackbox etc. you must install the package compiz-deskmenuAUR. 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 Ctrl+Space.

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

An alternative is to use mygtkmenuAUR, also in AUR.

Allow users to shutdown/reboot

Refer to 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

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-gtkAUR 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 = Alt+Tab.
  • Switch to next desktops = Ctrl+Alt+←.
  • Switch to previous desktop = Ctrl+Alt+→.
  • Move window = Alt+Left click.
  • Resize window = Alt+Right click.

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

Troubleshooting

Tango-view-refresh-red.pngThis article or section is out of date.Tango-view-refresh-red.png

Reason: - (Discuss in Talk:Compiz#)

Missing GLX_EXT_texture_from_pixmaps

On ATI cards (first solution)

https://bbs.archlinux.org/viewtopic.php?id=50073 If you run into the following error when trying to run Compiz Fusion on an ATI card:

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

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

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

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

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

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:

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

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

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

If you then do not have borders, run:

emerald --replace

As at 17-Oct-07 the Compiz-Fusion Wiki states: "If you are using an Intel GMA card with AIGLX, you will need to start Compiz Fusion with LIBGL_ALWAYS_INDIRECT=1 appended."

Compiz starts, but no effects are visible

If you have installed compiz-decorator-gtk: 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.

Compiz starts, but gtk-window-decorator does not

It is a configuration problem for gconf and gconfd. You may try removing ~/.gconf/. This will erase your Compiz settings, so be sure to reconfigure. Finally as user:

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

Compiz appears to start, but there are no window borders

When running Fusion Icon from terminal, you get output like this:

$ fusion-icon
* Detected Session: gnome
* 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

You may also try adding Option "AddARGBGLXVisuals" "True" and Option "DisableGLXRootClipping" "True" to your "Screen" section, if you are using the NVIDIA binary driver. If you used any other Options elsewhere in /etc/X11/xorg.conf.d/ to get Compiz working and still have no luck, try commenting them out and using only the aformentioned ARGBGLXVisuals and GLXRootClipping Options.

Note: Check that "Window decoration", "Move" and "Resize" plugins are enabled with Compiz Settings Manager or gconf-editor.

With  gconf-editor you can easly enable "Window decoration", "Move" and "Resize" plugins.

$ gconf-editor

Navigate to apps > compiz > general > allscreens > options.

Add/Edit "active_plugins" Key (Name: active_plugins, Type: List, List type: String).

Add "decoration", "move", and "resize" to the list.

Another way to fix this:

  • Launch ccsm.
  • Find Window Decoration and make sure it is enabled.
  • Now click on it, to edit the options.
  • If the entry behind command is empty, use gtk-window-decorator or kde-window-decorator or emerald.
  • Close CCSM and the borders should now appear.

Compiz starts and borders appear, but windows won't move

Be sure you have the "Move Window" plugin installed and enabled in the CompizConfig Settings Manager.

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:

$ gconftool -s /apps/compiz/general/screen0/options/sync_to_vblank-t boolean false

Fusion Icon doesn't 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/

Choppy animations, even though everything configured correctly

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.

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 /etc/X11/xorg.conf.d/*.conf, and then restarting your computer:

Option "DynamicTwinView" "False"

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.

Fix GNOME screenshot

To re-enable gnome-screenshot (the default behavior caused by hitting 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 Super+Button1 thereby giving you two methods to do a screen capture (one of which gives a full screen capture in a single keystroke).

Get GNOME workspace switcher work with Compiz Fusion

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:

/apps/compiz/general/screen0/options/number_of_desktops = 1
/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

To fix it, create the following:

/etc/modprobe.d/nvidia.conf
options nvidia NVreg_RegistryDwords="PerfLevelSrc=0x2222"

Setting the window manager back to Metacity after uninstall

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 gconf-editor. Use this to set the value of the key /desktop/gnome/session/required_components/window_manager from "compiz" to "metacity". Log out and back in for changes to take effect.

See also