Difference between revisions of "Compiz (日本語)"

From ArchWiki
Jump to: navigation, search
(synchronized interlanguage links with the other wikis)
(10 intermediate revisions by 5 users not shown)
Line 1: Line 1:
[[Category:Eye candy (English)]]
+
[[Category:Eye candy (日本語)]]
[[Category:Stacking WMs (English)]]
+
[[Category:Stacking WMs (日本語)]]
{{i18n|Compiz}}
+
[[de:Compiz-fusion]]
 +
[[el:Compiz]]
 +
[[en:Compiz]]
 +
[[es:Compiz]]
 +
[[fr:Compiz]]
 +
[[it:Compiz]]
 +
[[pl:Compiz]]
 +
[[pt:Compiz]]
 +
[[ru:Compiz]]
 +
[[tr:Compiz]]
 +
[[zh-CN:Compiz]]
 +
Compiz is a [[Wikipedia:compositing window manager|コンポジットなウインドウマネージャーです。]]. Compiz それ自身が1つのウインドウマネージャーであり、[[Openbox]], [[Fluxbox]], [[Enlightenment]]のような他のウインドウマネージャーと同時に動作させることはできません。 - 現在利用しているウインドウマネージャーを使用したまま、いくつかのデスクトップ効果を得たいユーザーは Compiz の代わりに[[Xcompmgr]] を利用してみるとよいかもしれません。
  
Compiz is a [[Wikipedia:コンポジットな効果を取り入れたウインドウマネージャーです。|compositing window manager]]. It provides its own window manager, so it cannot be used simultaneously with other window managers such as [[Openbox]], [[Fluxbox]], [[Enlightenment]] - users who want to keep their current window managers and add some effects to it may wish to try [[Xcompmgr]] instead.
+
== インストレーション ==
 +
基本的なインストールは [community] リポジトリで行うことができます。
  
== Installation ==
+
=== [community] リポジトリからのインストール===
Basic installation can be done using the [community] repo.
+
 
+
=== Install from [community] ===
+
 
Make sure the [community] repository is enabled in {{ic|/etc/pacman.conf}}.
 
Make sure the [community] repository is enabled in {{ic|/etc/pacman.conf}}.
  
Line 22: Line 31:
 
Users who wish to select the packages individually may consult the following list:
 
Users who wish to select the packages individually may consult the following list:
  
{{Box Note| For other desktop environments, please see the section on setting up Compiz as a standalone window manger [[Compiz#As_a_Standalone_Window_Manager|below]].}}
+
{{Note| For other desktop environments, please see the section on setting up Compiz as a standalone window manger [[Compiz#As_a_Standalone_Window_Manager|below]].}}
  
 
=== List of packages by group ===
 
=== List of packages by group ===
Line 44: Line 53:
  
 
;'Unsupported' Plugins:
 
;'Unsupported' Plugins:
:compiz-fusion-plugins-unsupport is available from the [http://aur.archlinux.org/packages.php?ID=14255 AUR]. It is versioned 0.8.4 but works fine with 0.8.6. It includes the 'Tile' plugin.
+
:compiz-fusion-plugins-unsupport is available from the [https://aur.archlinux.org/packages.php?ID=14255 AUR]. It is versioned 0.8.4 but works fine with 0.8.6. It includes the 'Tile' plugin.
  
 
=== Configuration ===
 
=== Configuration ===
{{Box RED|Activate important plugins!|
+
; Activate important plugins!
 
: Before you do anything else, 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 may be used to achieve this.  
 
: Before you do anything else, 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 may be used to achieve this.  
 
:Launch CompizConfig Settings Manager:
 
:Launch CompizConfig Settings Manager:
 
: {{bc|$ ccsm}}
 
: {{bc|$ ccsm}}
 
: Simply put check marks next to those plugins to activate them.
 
: Simply put check marks next to those plugins to activate them.
: Note: While the appearance of the windows and their contents is a function of [[GTK+]] and [http://en.wikipedia.org/wiki/Qt_(toolkit) 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".
+
: Note: While the appearance of the windows and their contents is a function of [[GTK+]] and [[wikipedia:Qt_(toolkit)|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".
 
; To set emerald as your default window-decorator type:
 
; To set emerald as your default window-decorator type:
 
: {{bc|emerald --replace}}
 
: {{bc|emerald --replace}}
Line 58: Line 67:
 
:{{bc|kde4-window-decorator --replace}}
 
:{{bc|kde4-window-decorator --replace}}
 
; To set the compiz-decorator-gtk as an alternative to Emerald type:
 
; To set the compiz-decorator-gtk as an alternative to Emerald type:
:{{bc|gtk-window-decorator --replace}}}}
+
:{{bc|gtk-window-decorator --replace}}
 
; Compatibility
 
; Compatibility
: The [http://forlong.blogage.de/entries/pages/Compiz-Check compiz-check] script runs several compiz-related tests and can help discovering setup and hardware issues. It is available from the [http://aur.archlinux.org/packages.php?ID=17163 aur].{{Box Note| compiz-check is at the moment unmaintained and out-of-date, it shows partly wrong results.}}
+
: The [http://forlong.blogage.de/entries/pages/Compiz-Check compiz-check] script runs several compiz-related tests and can help discovering setup and hardware issues. It is available from the [https://aur.archlinux.org/packages.php?ID=17163 aur].{{Note| compiz-check is at the moment unmaintained and out-of-date, it shows partly wrong results.}}
  
 
== Starting Compiz Fusion ==
 
== Starting Compiz Fusion ==
Line 99: Line 108:
  
 
Next time KDE is started, it will load fusion-icon automatically.
 
Next time KDE is started, it will load fusion-icon automatically.
{{Box Note| This method can also be slower due to the fact that KDE will first load the default window manager (KWin), then will launch fusion-icon which will load the Compiz window manager to replace KWin. Essentially, it will take the amount of time that it takes to load two window managers to get Compiz loaded. Read ahead to see other methods.}}
+
{{Note| This method can also be slower due to the fact that KDE will first load the default window manager (KWin), then will launch fusion-icon which will load the Compiz window manager to replace KWin. Essentially, it will take the amount of time that it takes to load two window managers to get Compiz loaded. Read ahead to see other methods.}}
  
 
==== Autostart (without "fusion-icon") ====
 
==== Autostart (without "fusion-icon") ====
Line 105: Line 114:
 
===== Method 1 - Autostart Link =====
 
===== Method 1 - Autostart Link =====
  
{{Box Note|DO NOT create compiz.desktop if you intend to install compiz-decorator-gtk; it will create a file conflict.}}
+
{{Note|DO NOT create compiz.desktop if you intend to install compiz-decorator-gtk; it will create a file conflict.}}
  
 
* You can ensure that Compiz Fusion will always start at login by appending a desktop entry to the KDE Autostart directory. If it doesn't already exist (it should), create the file {{ic|~/.kde/Autostart/compiz.desktop}} with the following contents:
 
* You can ensure that Compiz Fusion will always start at login by appending a desktop entry to the KDE Autostart directory. If it doesn't already exist (it should), create the file {{ic|~/.kde/Autostart/compiz.desktop}} with the following contents:
Line 125: Line 134:
 
  X-GnomeWMSettingsLibrary=compiz
 
  X-GnomeWMSettingsLibrary=compiz
  
{{Box Note| If {{ic|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.}}
+
{{Note| If {{ic|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.}}
{{Box Note| This method can also be slower due to the fact that KDE will first load the default window manager (KWin), then will launch fusion-icon which will load the Compiz window manager to replace KWin. Essentially, it will take the amount of time that it takes to load two window managers to get Compiz loaded. The next method eliminates this problem.}}
+
{{Note| This method can also be slower due to the fact that KDE will first load the default window manager (KWin), then will launch fusion-icon which will load the Compiz window manager to replace KWin. Essentially, it will take the amount of time that it takes to load two window managers to get Compiz loaded. The next method eliminates this problem.}}
  
 
* 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|~/.kde/share/config/ksmserverrc}}:
 
* 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|~/.kde/share/config/ksmserverrc}}:
  
 
  loginMode=restorePreviousLogout
 
  loginMode=restorePreviousLogout
{{Box Note| This is a KDE specific setting that will allow you to restore other apps next time you log in, not just fusion-icon.}}
+
{{Note| This is a KDE specific setting that will allow you to restore other apps next time you log in, not just fusion-icon.}}
  
 
===== Method 2 - export KDEWM (Preferred Method) =====
 
===== Method 2 - export KDEWM (Preferred Method) =====
  
{{Box Note| Using this method will load Compiz-Fusion as the default window manager instead of KWin from the start. This method is faster than automatically loading Compiz-Fusion with either of the two previous methods because it avoids loading KDE's default window manager (KWin) first. This method also prevents that annoying black screen flicker you might see using other methods (when kwin switches to Compiz on KDE's desktop loading screens).}}
+
{{Note| Using this method will load Compiz-Fusion as the default window manager instead of KWin from the start. This method is faster than automatically loading Compiz-Fusion with either of the two previous methods because it avoids loading KDE's default window manager (KWin) first. This method also prevents that annoying black screen flicker you might see using other methods (when kwin switches to Compiz on KDE's desktop loading screens).}}
  
 
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
  
{{Box 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 "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.}}
Line 155: Line 164:
 
: {{bc|1=KDEWM="compiz-fusion"}}
 
: {{bc|1=KDEWM="compiz-fusion"}}
  
{{Box Note| If the above method shall not work for any reason, try the replacement mentioned above.}}
+
{{Note| If the above method shall not work for any reason, try the replacement mentioned above.}}
{{Box Note| If that still doesn't work, yet another alternate way to accomplish the above method is to include the line
+
{{Note| If that still doesn't work, yet another alternate way to accomplish the above method is to include the line
 
{{bc|1=export KDEWM="compiz-fusion"}}
 
{{bc|1=export KDEWM="compiz-fusion"}}
 
in your user's {{ic|~/.bashrc}} file.}}
 
in your user's {{ic|~/.bashrc}} file.}}
{{Box Note| 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:
+
{{Note| 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:
 
{{bc|1=export KDEWM="/usr/local/bin/compiz-fusion"}}}}
 
{{bc|1=export KDEWM="/usr/local/bin/compiz-fusion"}}}}
  
Line 176: Line 185:
 
=== 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 gnome-shell.
{{Box 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 [http://aur.archlinux.org/packages.php?ID=49505 gnome-session-compiz package in AUR] 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 [https://aur.archlinux.org/packages.php?ID=49505 gnome-session-compiz package in AUR] 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 worked fine for me).
Line 213: Line 222:
 
  X-GnomeWMSettingsLibrary=compiz
 
  X-GnomeWMSettingsLibrary=compiz
  
{{Box 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.}}
  
 
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:
 
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:
Line 229: Line 238:
 
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:
 
{{bc|1=Exec=bash -c 'compiz ccp decoration --sm-client-id $DESKTOP_AUTOSTART_ID'}}
 
{{bc|1=Exec=bash -c 'compiz ccp decoration --sm-client-id $DESKTOP_AUTOSTART_ID'}}
as noted [http://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.
  
 
'''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:
 
'''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:
  
{{Box 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.}}
+
{{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
 
  gconftool-2 --set -t string /desktop/gnome/session/required_components/windowmanager compiz
Line 259: Line 268:
 
}}
 
}}
  
{{Box Note| I took out gnome-panel as I am using avant-window-navigator as my panel.
+
{{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.}}
 
I'am using gnome3 fallback mode with compiz, make gtk-window-decorator start with compiz, and make avant-window-navigator start automatically.}}
  
Line 294: Line 303:
 
Comment:  (Put anything you like or leave blank.)
 
Comment:  (Put anything you like or leave blank.)
  
{{Box 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 "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).}}
 
The ccp value will tell compiz to load your previous Compiz settings as configured with CompizConfig Settings Manager (ccsm).}}
Line 303: Line 312:
 
  gconftool-2 --type bool --set /apps/metacity/general/compositing_manager false
 
  gconftool-2 --type bool --set /apps/metacity/general/compositing_manager false
  
{{Box 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.}}
+
{{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.}}
  
 
=== XFCE ===
 
=== XFCE ===
Line 337: Line 346:
 
   </property>
 
   </property>
  
{{Box 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 362: Line 371:
 
   (Command:) fusion-icon
 
   (Command:) fusion-icon
  
{{Box 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 "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).}}
 
The ccp value will tell compiz to load your previous Compiz settings as configured with CompizConfig Settings Manager (ccsm).}}
  
{{Box Note| This method is the least preferred since it loads both window managers. All the other XFCE methods only load Compiz without loading Xfwm.}}
+
{{Note| This method is the least preferred since it loads both window managers. All the other XFCE methods only load Compiz without loading Xfwm.}}
  
 
=====Method 2:=====
 
=====Method 2:=====
Line 429: Line 438:
 
To autostart compiz-fusion configure .xinitrc to launch compiz as:
 
To autostart compiz-fusion configure .xinitrc to launch compiz as:
 
{{hc|~/.xinitrc|<nowiki>
 
{{hc|~/.xinitrc|<nowiki>
exec ck-launch-session compiz ccp
+
exec compiz ccp
 
</nowiki>}}
 
</nowiki>}}
You can also add other [https://wiki.archlinux.org/index.php/Compiz_fusion#Manually_.28without_.22fusion-icon.22.29 command-line options] to your .xinitrc
+
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
 
Or if using fusion-icon, configure .xinitrc as
 
{{hc|~/.xinitrc|<nowiki>
 
{{hc|~/.xinitrc|<nowiki>
exec ck-launch-session fusion-icon
+
exec fusion-icon
 
</nowiki>}}
 
</nowiki>}}
  
Line 442: Line 451:
 
tint2 &
 
tint2 &
 
cairo-dock &
 
cairo-dock &
exec ck-launch-session fusion-icon
+
exec fusion-icon
 
</nowiki>}}
 
</nowiki>}}
{{Note| Add a terminal-emulator to this autostart list while starting for the first time to help [https://wiki.archlinux.org/index.php/Compiz_fusion#Configuration configure] compiz.}}  
+
{{Note| Add a terminal-emulator to this autostart list while starting for the first time to help [[Compiz_fusion#Configuration|configure]] compiz.}}  
  
 
An alternative method, utilizing a simple script entitled '''start-fusion.sh''':
 
An alternative method, utilizing a simple script entitled '''start-fusion.sh''':
Line 472: Line 481:
 
And add it to .xinitrc, like this:
 
And add it to .xinitrc, like this:
 
{{hc|~/.xinitrc|<nowiki>
 
{{hc|~/.xinitrc|<nowiki>
exec ck-launch-session /path/to/file/start-fusion.sh
+
exec /path/to/file/start-fusion.sh
 
</nowiki>}}
 
</nowiki>}}
  
 
Feel free to use a different panel, tray, or start a whole bunch of applications with your session.
 
Feel free to use a different panel, tray, or start a whole bunch of applications with your session.
See [http://bbs.archlinux.org/viewtopic.php?id=51282 this forum thread] for more info.
+
See [https://bbs.archlinux.org/viewtopic.php?id=51282 this forum thread] for more info.
  
 
{{Note | Using a separate script instead of running everything from xinitrc is the only way to let all launching applications use ConsoleKit: see [[ConsoleKit#Running_several_applications_from_xinitrc|this article]].}}
 
{{Note | Using a separate script instead of running everything from xinitrc is the only way to let all launching applications use ConsoleKit: see [[ConsoleKit#Running_several_applications_from_xinitrc|this article]].}}
Line 489: Line 498:
 
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.
 
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 [http://aur.archlinux.org/packages.php?ID=29564 mygtkmenu], also in [[AUR]].
+
An alternative is to use {{AUR|mygtkmenu}}, also in [[AUR]].
  
 
==== Allow users to shutdown/reboot ====
 
==== Allow users to shutdown/reboot ====
Refer to [https://wiki.archlinux.org/index.php/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.
  
 
== Misc ==
 
== Misc ==
  
 
=== Configuration  ===
 
=== Configuration  ===
[https://wiki.archlinux.org/index.php/Compiz#Configuration You must do this so your windows function like you expect them to!]
+
[[Compiz#Configuration|You must do this so your windows function like you expect them to!]]
  
 
=== Using compiz-manager ===
 
=== Using compiz-manager ===

Revision as of 17:20, 23 February 2014

Compiz is a コンポジットなウインドウマネージャーです。. Compiz それ自身が1つのウインドウマネージャーであり、Openbox, Fluxbox, Enlightenmentのような他のウインドウマネージャーと同時に動作させることはできません。 - 現在利用しているウインドウマネージャーを使用したまま、いくつかのデスクトップ効果を得たいユーザーは Compiz の代わりにXcompmgr を利用してみるとよいかもしれません。

インストレーション

基本的なインストールは [community] リポジトリで行うことができます。

[community] リポジトリからのインストール

Make sure the [community] repository is enabled in /etc/pacman.conf.

If you want to install the entire compiz-fusion group, give The command

# pacman -S compiz-fusion

which will install EVERYTHING, but chances are you only want compiz for either Gnome or KDE, not both, so...

Run this if you want only the gtk-based packages (for Gnome) installed:

# pacman -S compiz-fusion-gtk

Or this if you want only kde-based packages (for K Desktop Environment) installed:

# pacman -S compiz-fusion-kde 

Users who wish to select the packages individually may consult the following list:

Note: For other desktop environments, please see the section on setting up Compiz as a standalone window manger below.

List of packages by group

Entire compiz-fusion group (compiz-fusion)
ccsm, compiz-core, compiz-fusion-plugins-extra, compiz-fusion-plugins-main, compizconfig-backend-gconf, compizconfig-backend-kconfig, emerald, emerald-themes, fusion-icon
KDE compiz-fusion group (compiz-fusion-kde)
ccsm, compiz-fusion-plugins-extra, compiz-fusion-plugins-main, compizconfig-backend-kconfig, emerald, emerald-themes, fusion-icon
GTK (Gnome) compiz-fusion group (compiz-fusion-gtk)
ccsm, compiz-fusion-plugins-extra, compiz-fusion-plugins-main, compizconfig-backend-gconf, emerald, emerald-themes, fusion-icon
Groupless
compiz-decorator-gtk, compiz-decorator-kde, compiz-manager
  • ccsm or "CompizConfig settings manager" is the GUI application that lets you configure all of Compiz's plugins.
  • Emerald is compiz's own window decorator with few dependencies. (Note: Works but is buggy and no longer maintained)
  • fusion-icon offers a tray icon and a nice way to start compiz, start ccsm and change the WM / Window Decorator.
  • compiz-manager is said to bring better session managing capabilities (needs confirmation!).
  • compiz-decorator-gtk and compiz-decorator-kde are alternatives to emerald and uses your desktop environment's configuration backends and looks.
'Unsupported' Plugins
compiz-fusion-plugins-unsupport is available from the AUR. It is versioned 0.8.4 but works fine with 0.8.6. It includes the 'Tile' plugin.

Configuration

Activate important plugins!
Before you do anything else, 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 may be used to achieve this.
Launch CompizConfig Settings Manager:
$ ccsm
Simply put check marks next to those plugins to activate them.
Note: 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".
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
Compatibility
The compiz-check script runs several compiz-related tests and can help discovering setup and hardware issues. It is available from the aur.
Note: compiz-check is at the moment unmaintained and out-of-date, it shows partly wrong results.

Starting Compiz Fusion

Manually (with "fusion-icon")

Launch the Compiz Fusion tray icon:

$ fusion-icon

Note: If it fails (almost never), you may try it with dbus-launch:

$ dbus-launch "fusion-icon"

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.

KDE

Autostart (with "fusion-icon")

Add a symbolic link, that points to the fusion-icon executable, in your KDE Autostart directory (generally located in ~/.kde/Autostart):

$ ln -s /usr/bin/fusion-icon ~/.kde/Autostart/fusion-icon

Next time KDE is started, it will load fusion-icon automatically.

Note: This method can also be slower due to the fact that KDE will first load the default window manager (KWin), then will launch fusion-icon which will load the Compiz window manager to replace KWin. Essentially, it will take the amount of time that it takes to load two window managers to get Compiz loaded. Read ahead to see other methods.

Autostart (without "fusion-icon")

Method 1 - Autostart Link
Note: DO NOT create compiz.desktop if you intend to install compiz-decorator-gtk; it will create a file conflict.
  • You can ensure that Compiz Fusion will always start at login by appending a desktop entry to the KDE Autostart directory. If it doesn't already exist (it should), create the file ~/.kde/Autostart/compiz.desktop with the following contents:
[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.
Note: This method can also be slower due to the fact that KDE will first load the default window manager (KWin), then will launch fusion-icon which will load the Compiz window manager to replace KWin. Essentially, it will take the amount of time that it takes to load two window managers to get Compiz loaded. The next method eliminates this problem.
  • 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 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 ~/.kde/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.
Method 2 - export KDEWM (Preferred Method)
Note: Using this method will load Compiz-Fusion as the default window manager instead of KWin from the start. This method is faster than automatically loading Compiz-Fusion with either of the two previous methods because it avoids loading KDE's default window manager (KWin) first. This method also prevents that annoying black screen flicker you might see using other methods (when kwin switches to Compiz on KDE's desktop loading screens).

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-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 /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 ~/.kde4/env/compiz.sh and add the following line so KDE will load compiz (via the script you just created) instead of loading KWin.
KDEWM="compiz-fusion"
2) Compiz system wide --> Edit the file /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.
KDEWM="compiz-fusion"
Note: If the above method shall not work for any reason, try the replacement mentioned above.
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.
Note: 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"
Method 3 - Use KDE 4 System Settings

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 fusion-icon from a terminal you can see the command line with which compiz was started). Create a file called "compiz-kde-launcher" in your /usr/bin directory. Then make the file executable: "chmod +x /usr/bin/compiz-kde-launcher". Here is an example for compiz-kde-launcher:

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

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-compiz package in AUR 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 worked fine for me).

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 containing the following:

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

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 gnome3 fallback mode session)

Edit file /usr/share/gnome-session/sessions/gnome-fallback.session:

Replace your windows manager (gnome-shell,metacity...) with compiz in RequiredComponents line.

Change DefaultProvider-windowmanager line to DefaultProvider-windowmanager=compiz

Here is part of my 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 (chmod +x /usr/local/bin/compiz-start-boot). Next create the file /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")

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

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.

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, run this command as root:

# pacman -S xfce4-session

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

Edit the following file

$ nano ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml

Or to make the change for all XFCE users (root access required)

# nano /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, run:

$ rm -r ~/.cache/sessions

Xfce autostart (with "fusion-icon")

Method 1:

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 "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: This method is the least preferred since it loads both window managers. All the other XFCE methods only load Compiz without loading Xfwm.
Method 2:

Edit the following file (settings in this file is used in preference)

nano ~/.config/xfce4-session/xfce4-session.rc

Or to make the change for all XFCE users (root access required)

# nano /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

and open it for edit:

nano ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml

or make the changes for all xfce4 users (needs root access):

# nano /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 dosen'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:

~/.xinitrc
exec compiz ccp

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

Or if using fusion-icon, configure .xinitrc as

~/.xinitrc
exec fusion-icon

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:

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

An alternative method, utilizing a simple script entitled start-fusion.sh:

start-fusion.sh
#!/bin/sh
# add more apps here if necessary or start another panel, tray like pypanel, bmpanel, stalonetray
xfce4-panel&
fusion-icon

If this script dosn't work for you, or you get issues with dbus utilize this script:

start-fusion.sh
#!/bin/sh
cd /home/<yourusername>
eval `dbus-launch --sh-syntax --exit-with-session`
/usr/bin/X :0.0 -br -audit 0 -nolisten tcp vt7 &
export DISPLAY=:0.0
sleep 1
compiz-manager decoration move resize > /tmp/compiz.log 2>&1 &
# add more apps here if necessary or start another panel, tray like pypanel, bmpanel, stalonetray
xfce4-panel&
fusion-icon

Make it executable

chmod +x start-fusion.sh

And add it to .xinitrc, like this:

~/.xinitrc
exec /path/to/file/start-fusion.sh

Feel free to use a different panel, tray, or start a whole bunch of applications with your session. See this forum thread for more info.

Note: Using a separate script instead of running everything from xinitrc is the only way to let all launching applications use ConsoleKit: see this article.

Add a root menu

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

Misc

Configuration

You must do this so your windows function like you expect them to!

Using compiz-manager

In order to use compiz-manager, you need to install it from community:

pacman -S compiz-manager

Compiz-manager, that is now installed in /usr/bin/compiz-manager, is a simple wrapper for Compiz and ALL of its options. For example, you can run

compiz-manager 

and see what the console returns for more info. You can use it in all the scripts that start Compiz. Very simple!

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.

Keyboard Shortcuts

Default plugin keyboard shortcuts (plugins have to be activated!)

  • Switch windows = Alt + Tab
  • Switch desktops on cube = Ctrl + Alt + Left/Right Arrow
  • 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 (ccsm).

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.

Troubleshooting

See this article.

See also