Picom linux что это
Обновлено: 04.07.2024
This is a development branch, bugs to be expected
This is forked from the original Compton because it seems to have become unmaintained.
The current battle plan of this fork is to refactor it to make the code possible to maintain, so potential contributors won't be scared away when they take a look at the code.
We also try to fix bugs.
You can leave your feedbacks or thoughts in the discussion tab.
The original README can be found here
Call for testers
This flag enables the refactored/partially rewritten backends.
Currently, new backends feature better vsync with the xrender backend and improved input lag with the glx backend (for non-NVIDIA users). The performance should be on par with the old backends.
New backend features will only be implemented on the new backends from now on, and the old backends will eventually be phased out after the new backends stabilize.
To test the new backends, add the --experimental-backends flag to the command you use to run picom. This flag is not available from the configuration file.
To report issues with the new backends, please state explicitly you are using the new backends in your report.
Since the inception of this fork, the existence of two compton repositories has caused some number of confusions. Mainly, people will report issues of this fork to the original compton, or report issues of the original compton here. Later, when distros started packaging this fork of compton, some wanted to differentiate the newer compton from the older version. They found themselves having no choice but to invent a name for this fork. This is less than ideal since this has the potential to cause more confusions among users.
Therefore, we decided to move this fork to a new name. Personally, I consider this more than justified since this version of compton has gone through significant changes since it was forked.
The criteria for a good name were
- Being short, so it's easy to remember.
- Pronounceability, again, helps memorability
- Searchability, so when people search the name, it's easy for them to find this repository.
Of course, choosing a name is never easy, and there is no apparent way to objectively evaluate the names. Yet, we have to solve the aforementioned problems as soon as possible.
In the end, we picked picom (a portmanteau of pico and composite ) as our new name. This name might not be perfect, but is what we will move forward with unless there's a compelling reason not to.
Following the deprecation process, migration to the new name will be broken into 3 steps:
- All mentions of compton will be updated to picom in the code base. compton will still be installed, but only as a symlink to picom . When picom is launched via the symlink, a warning message is printed, alerting the user to migrate. Similarly, the old configuration file names and dbus interface names will still be accepted but warned.
- 3 major releases after step 1, the warning messages will be prompted to error messages and picom will not start when launched via the symlink.
- 3 major releases after step 2, the symlink will be removed.
The dbus interface and service names are unchanged, so no migration needed for that.
Assuming you already have all the usual building tools installed (e.g. gcc, python, meson, ninja, etc.), you still need:
- libx11
- libx11-xcb
- libXext
- xproto
- xcb
- xcb-damage
- xcb-xfixes
- xcb-shape
- xcb-renderutil
- xcb-render
- xcb-randr
- xcb-composite
- xcb-image
- xcb-present
- xcb-xinerama
- xcb-glx
- pixman
- libdbus (optional, disable with the -Ddbus=false meson configure flag)
- libconfig (optional, disable with the -Dconfig_file=false meson configure flag)
- libGL (optional, disable with the -Dopengl=false meson configure flag)
- libpcre (optional, disable with the -Dregex=false meson configure flag)
- libev
- uthash
On Debian based distributions (e.g. Ubuntu), the needed packages are
On Fedora, the needed packages are
To build the documents, you need asciidoc
Built binary can be found in build/src
If you have libraries and/or headers installed at non-default location (e.g. under /usr/local/ ), you might need to tell meson about them, since meson doesn't look for dependencies there by default.
You can do that by setting the CPPFLAGS and LDFLAGS environment variables when running meson . Like this:
As an example, on FreeBSD, you might have to run meson with:
Default install prefix is /usr/local , you can change it with meson configure -Dprefix=<path> build
How to Contribute
You can look at the Projects page, and see if there is anything that interests you. Or you can take a look at the Issues.
Even if you don't want to contribute code, you can still contribute by compiling and running this branch, and report any issue you can find.
picom is a standalone compositor for Xorg, suitable for use with window managers that do not provide compositing. picom is a fork of compton, which is a fork of xcompmgr-dana, which in turn is a fork of xcompmgr.
This article or section is out of date.
Reason: Arch package is built from yshui repo, most of the options described here (like -d , vsync = opengl ) were deprecated. (Discuss in Talk:Picom)Contents
Installation
Install the picom package or picom-git AUR for the development version. For a Qt-based configuration GUI install compton-conf AUR or compton-conf-git AUR .
Configuration
The default configuration is available in /etc/xdg/picom.conf . For modifications, it can be copied to
To use another custom configuration file with picom, use the following command:
Disable shadows for some windows
The shadow-exclude option can disable shadows for windows if required. For currently disabled windows, see [1].
To disable shadows for menus add the following to wintypes in picom.conf :
Opacity
To set opacity (in effect transparency) for focused and unfocused windows (for example terminal emulators), add the following to your picom.conf :
Usage
picom may be manually enabled or disabled at any time during a session, or autostarted as a background process for sessions. There are also several optional arguments that may be used to tweak the compositing effects provided. These include:
- -b : Run as a background process for a session (e.g. when autostarting for a window manager such as Openbox)
- -c : Enable shadow effects
- -C : Disable shadow effects on panels and docks
- -G : Disable shadow effects for application windows and drag-and-drop objects
- --config : Use a specified configuration file
Many more options are available, including setting timings, displays to be managed, the opacity of menus, window borders, and inactive application menus. See picom(1) .
Note: If a different composite manager is running, it should be disabled before starting picom.To manually enable default compositing effects during a session, use the following command:
Alternatively, to disable all shadowing effects during a session, the -C and -G arguments must be added:
To autostart picom as a background process for a session, the -b argument can be used (may cause a display freeze):
To disable all shadowing effects, the -C and -G arguments must again be added:
Finally, this is an example where additional arguments that require values to be set have been used:
Multihead
If a multihead configuration is used without xinerama - meaning that X server is started with more than one screen - then picom will start on only one screen by default. It can be started on all screens by using the -d argument. For example, to run on X screen 0 in the background:
The above should work on all monitors, but if it does not try an older method that manually specifies each one:
Grayscale
It is possible to convert windows to grayscale by use of shaders.
As per picom(1) , start by editing the default shader from the picom's sources.
Then start picom by including the full text of the shader. The glx backend will also, probably, be necessary.
Troubleshooting
Recent versions of picom had some problem with DRI2 acceleration and exhibited severe flickering when DRI2 is in use (picom bug, mesa bug). This has been worked around and reported to be working, but may still affect some users. DRI3 is unaffected by this particular issue.
The use of compositing effects may on occasion cause issues such as visual glitches when not configured correctly for use with other applications and programs.
Conky
To disable shadows around Conky windows, have the following in
In the case this solution fail with blur effect, you can try this in
dwm and dmenu
dwm's statusbar is not detected by any of picom's functions to automatically exclude window manager elements. Neither dwm statusbar nor dmenu have a static window id. If you want to exclude it from inactive window transparency (or other), you will have to either patch a window class into the source code of each, or exclude by less precise attributes. The following example is with dwm's status on top, which allows a resolution independent of location exclusion:
Otherwise, where using a configuration file:
The override redirect property seems to be false for most windows- having this in the exclusion rule prevents other windows drawn in the upper left corner from being excluded (for example, when dwm statusbar is hidden, x0 y0 will match whatever is in dwm's master stack).
Firefox
To disable shadows for Firefox elements add the following to shadow-exclude in picom.conf :
See [2] for more information.
slock
Where inactive window transparency has been enabled (the -i argument when running as a command), this may provide troublesome results when also using slock. One solution is to amend the transparency to 0.2 . For example, where running picom arguments as a command:
Otherwise, where using a configuration file:
Alternatively, you may try to exclude slock by its window id, or by excluding all windows with no name.
Note: Some programs change their id for every new instance, but slock's appears to be static. Someone more knowledgeable will have to confirm that slock's id is in fact static- until then, use at your own risk.Exclude all windows with no name from picom using the following options:
Find your slock's window id by running the command:
Quickly click anywhere on the screen (before slock exits), then type your password to unlock. You should see the window id in the output:
Take the window id and exclude it from picom with:
Otherwise, where using a configuration file:
Flicker
Applies to fully maximized windows (in sessions without any panels) with the default picom.conf caused and resolved by the following option:
See [3] for more information.
Fullscreen tearing
Lag when using xft fonts
If you experience heavy lag when using Xft fonts in applications such as xterm or urxvt try:
or the xrender backend.
See [4] for more information.
Screen artifacts/screenshot issues when using AMD's Catalyst driver
Try running picom with:
to your picom.conf file.
See [5] for more information.
Tabbed windows (shadows and transparency)
When windows with transparency are tabbed, the underlying tabbed windows are still visible because of transparency. Each tabbed window also draws its own shadow resulting in multiple shadows.
Removing the multiple shadows issue can be done by adding the following to the already existing shadow-exclude list:
Not drawing underlying tabbed windows can be enabled by adding the following to your picom.conf :
Note that URxvt is the Xorg class name of your terminal. Change this if you use a different terminal. You can query a window's class by running the command xprop WM_CLASS and clicking the window.
See [6] for more information.
Warning: With i3 and kitty as terminal, doing this will currently (as of 04. June 19) freeze all hidden (tabbed) instances of kitty when you reload i3: [7]Unable to change the background color with xsetroot
Currently, picom is incompatible with xsetroot 's -solid option, a workaround is to use hsetroot to set the background color:
See [8] for more information.
Screentearing with NVIDIA's proprietary drivers
Try this setting in picom.conf :
Lag with Nvidia proprietary drivers and FullCompositionPipeline
Another option to reduce lag with the glx backend is to disable "allow flipping" [9] in nvidia settings (OpenGL section). This can also be done from the command line:
To load settings after reboot (see Autostarting) run
Xorg leaking GPU memory with Nvidia proprietary drivers
Slock after suspend
When using a systemd service to trigger slock on a suspend or hibernate action, one may find the screen unlocked for a few seconds after resume. To prevent, disable window fading:
Testing with old compton
Many issues are regressions from the old compton, which picom is a fork of. As a last resort you can try compton-old-git AUR and see if it helps.
picom is a compositor for X11, based on xcompmgr. In addition to shadows, fading and translucency, picom implements window frame opacity control, inactive window transparency, and shadows on argb windows.
picom is a fork of compton as it seems to have become unmaintained.
Другие пакеты, относящиеся к picom
- зависимости
- рекомендации
- предложения
- enhances
- dep: libc6 (>= 2.27) [riscv64] библиотека GNU C: динамически подключаемые библиотеки
также виртуальный пакет, предоставляемый libc6-udeb dep: libc6 (>= 2.29) [не alpha, ia64, riscv64, sh4] dep: libc6 (>= 2.31) [sh4] - dep: libc6.1 (>= 2.29) [alpha] библиотека GNU C: динамически подключаемые библиотеки
также виртуальный пакет, предоставляемый libc6.1-udeb dep: libc6.1 (>= 2.31) [ia64] - dep: libconfig9 parsing/manipulation of structured configuration files
- dep: libdbus-1-3 (>= 1.9.14) simple interprocess messaging system (library)
- dep: libev4 (>= 1:4.04) high-performance event loop library modelled after libevent
- dep: libgl1 работа с GL — поддержка старых программ
- dep: libpcre3 устаревшая библиотека поддержки регулярных выражений, совместимых с Perl5 — файлы времени исполнения
- dep: libpixman-1-0 (>= 0.25.2) библиотека для работы с пикселями в X и cairo
- dep: libx11-6 библиотека X11 для клиентской стороны
- dep: libx11-xcb1 (>= 2:1.6.12) библиотека интерфейса Xlib/XCB
- dep: libxcb-composite0 X C Binding, composite extension
- dep: libxcb-damage0 X C Binding, damage extension
- dep: libxcb-glx0 X C Binding, glx extension
- dep: libxcb-image0 (>= 0.2.1) utility libraries for X C Binding -- image
- dep: libxcb-present0 C-интерфейс графической системы X, расширение present
- dep: libxcb-randr0 (>= 1.10) X C Binding, randr extension
- dep: libxcb-render-util0 библиотеки утилит для X C Binding -- render-util
- dep: libxcb-render0 (>= 1.12) X C Binding, расширение для визуализации
- dep: libxcb-shape0 C-привязки для X, расширение shape
- dep: libxcb-sync1 C-интерфейс графической системы X, расширение sync
- dep: libxcb-xfixes0 C-интерфейс для графической системы X, расширение xfixes
- dep: libxcb-xinerama0 X C Binding, xinerama extension
- dep: libxcb1 (>= 1.9.2) С-интерфейс к Х-протоколу
- dep: python3 интерактивный высокоуровневый объектно-ориентированный язык (версия python3 по умолчанию)
Загрузка picom
| Архитектура | Размер пакета | В установленном виде | Файлы |
|---|---|---|---|
| alpha (неофициальный перенос) | 148,0 Кб | 451,0 Кб | [список файлов] |
| amd64 | 146,6 Кб | 399,0 Кб | [список файлов] |
| arm64 | 135,7 Кб | 387,0 Кб | [список файлов] |
| armel | 135,6 Кб | 374,0 Кб | [список файлов] |
| armhf | 134,9 Кб | 298,0 Кб | [список файлов] |
| hppa (неофициальный перенос) | 137,7 Кб | 367,0 Кб | [список файлов] |
| i386 | 158,3 Кб | 442,0 Кб | [список файлов] |
| ia64 (неофициальный перенос) | 184,4 Кб | 731,0 Кб | [список файлов] |
| m68k (неофициальный перенос) | 136,8 Кб | 382,0 Кб | [список файлов] |
| mips64el | 135,9 Кб | 445,0 Кб | [список файлов] |
| mipsel | 137,6 Кб | 413,0 Кб | [список файлов] |
| ppc64 (неофициальный перенос) | 153,6 Кб | 567,0 Кб | [список файлов] |
| ppc64el | 154,5 Кб | 503,0 Кб | [список файлов] |
| riscv64 (неофициальный перенос) | 134,3 Кб | 319,0 Кб | [список файлов] |
| s390x | 136,1 Кб | 411,0 Кб | [список файлов] |
| sh4 (неофициальный перенос) | 163,9 Кб | 356,0 Кб | [список файлов] |
| sparc64 (неофициальный перенос) | 126,5 Кб | 397,0 Кб | [список файлов] |
| x32 (неофициальный перенос) | 147,0 Кб | 382,0 Кб | [список файлов] |
Эта страница также доступна на следующих языках (Как установить язык по умолчанию):
Авторские права © 1997 - 2021 SPI Inc.; См. условия лицензии. Debian это торговый знак компании SPI Inc. Об этом сайте.
picom(1) Manual Page
picom - a compositor for X11
picom [OPTIONS]
picom is a compositor based on Dana Jansens' version of xcompmgr (which itself was written by Keith Packard). It includes some improvements over the original xcompmgr, like window frame opacity and inactive window transparency.
Get the usage text embedded in program code, which may be more up-to-date than this man page.
-r, --shadow-radius=RADIUS
The blur radius for shadows, in pixels. (defaults to 12)
-o, --shadow-opacity=OPACITY
The opacity of shadows. (0.0 - 1.0, defaults to 0.75)
-l, --shadow-offset-x=OFFSET
The left offset for shadows, in pixels. (defaults to -15)
-t, --shadow-offset-y=OFFSET
The top offset for shadows, in pixels. (defaults to -15)
-I, --fade-in-step=OPACITY_STEP
Opacity change between steps while fading in. (0.01 - 1.0, defaults to 0.028)
-O, --fade-out-step=OPACITY_STEP
Opacity change between steps while fading out. (0.01 - 1.0, defaults to 0.03)
-D, --fade-delta=MILLISECONDS
The time between steps in fade step, in milliseconds. (> 0, defaults to 10)
-m, --menu-opacity=OPACITY
Default opacity for dropdown menus and popup menus. (0.0 - 1.0, defaults to 1.0)
-c, --shadow
Enabled client-side shadows on windows. Note desktop windows (windows with _NET_WM_WINDOW_TYPE_DESKTOP) never get shadow, unless explicitly requested using the wintypes option.
-f, --fading
Fade windows in/out when opening/closing and when opacity changes, unless --no-fading-openclose is used.
-F
Equals to -f. Deprecated.
-i, --inactive-opacity=OPACITY
Opacity of inactive windows. (0.1 - 1.0, defaults to 1.0)
-e, --frame-opacity=OPACITY
Opacity of window titlebars and borders. (0.1 - 1.0, disabled by default)
-b, --daemon
Daemonize process. Fork to background after initialization. This option can only be set from the command line, setting this in the configuration file will have no effect.
--log-level
Set the log level. Possible values are "TRACE", "DEBUG", "INFO", "WARN", "ERROR", in increasing level of importance. Case doesn’t matter. If using the "TRACE" log level, it’s better to log into a file using --log-file, since it can generate a huge stream of logs.
--log-file
Set the log file. If --log-file is never specified, logs will be written to stderr. Otherwise, logs will to written to the given file, though some of the early logs might still be written to the stderr. When setting this option from the config file, it is recommended to use an absolute path.
--experimental-backends
Use the new, reimplemented version of the backends. The new backends are HIGHLY UNSTABLE at this point, you have been warned. This option is not available in the config file.
--show-all-xerrors
Show all X errors (for debugging).
--config PATH
Look for configuration file at the path. See CONFIGURATION FILES section below for where picom looks for a configuration file by default. Use /dev/null to avoid loading configuration file.
--write-pid-path PATH
Write process ID to a file. it is recommended to use an absolute path.
--shadow-color STRING
--shadow-red VALUE
Red color value of shadow (0.0 - 1.0, defaults to 0).
--shadow-green VALUE
Green color value of shadow (0.0 - 1.0, defaults to 0).
--shadow-blue VALUE
Blue color value of shadow (0.0 - 1.0, defaults to 0).
--inactive-opacity-override
Let inactive opacity set by -i override the _NET_WM_OPACITY values of windows.
--active-opacity OPACITY
Default opacity for active windows. (0.0 - 1.0, defaults to 1.0)
--inactive-dim VALUE
Dim inactive windows. (0.0 - 1.0, defaults to 0.0)
--corner-radius VALUE
Sets the radius of rounded window corners. When > 0, the compositor will round the corners of windows. Does not interact well with --transparent-clipping. (defaults to 0).
--rounded-corners-exclude CONDITION
Exclude conditions for rounded corners.
--mark-wmwin-focused
Try to detect WM windows (a non-override-redirect window with no child that has WM_STATE) and mark them as active.
--mark-ovredir-focused
Mark override-redirect windows that doesn’t have a child window with WM_STATE focused.
--no-fading-openclose
Do not fade on window open/close.
--no-fading-destroyed-argb
Do not fade destroyed ARGB windows with WM frame. Workaround of bugs in Openbox, Fluxbox, etc.
--shadow-ignore-shaped
Do not paint shadows on shaped windows. Note shaped windows here means windows setting its shape through X Shape extension. Those using ARGB background is beyond our control. Deprecated, use --shadow-exclude 'bounding_shaped' or --shadow-exclude 'bounding_shaped && !rounded_corners' instead.
--detect-rounded-corners
Try to detect windows with rounded corners and don’t consider them shaped windows. The accuracy is not very high, unfortunately.
--detect-client-opacity
Detect _NET_WM_OPACITY on client windows, useful for window managers not passing _NET_WM_OPACITY of client windows to frame windows.
--refresh-rate REFRESH_RATE
Specify refresh rate of the screen. If not specified or 0, picom will try detecting this with X RandR extension.
--vsync, --no-vsync
--use-ewmh-active-win
Use EWMH _NET_ACTIVE_WINDOW to determine currently focused window, rather than listening to FocusIn/FocusOut event. Might have more accuracy, provided that the WM supports it.
--unredir-if-possible
Unredirect all windows if a full-screen opaque window is detected, to maximize performance for full-screen windows. Known to cause flickering when redirecting/unredirecting windows.
--unredir-if-possible-delay MILLISECONDS
Delay before unredirecting the window, in milliseconds. Defaults to 0.
--unredir-if-possible-exclude CONDITION
Conditions of windows that shouldn’t be considered full-screen for unredirecting screen.
--shadow-exclude CONDITION
Specify a list of conditions of windows that should have no shadow.
--clip-shadow-above CONDITION
Specify a list of conditions of windows that should have no shadow painted over, such as a dock window.
--fade-exclude CONDITION
Specify a list of conditions of windows that should not be faded.
--focus-exclude CONDITION
Specify a list of conditions of windows that should always be considered focused.
--inactive-dim-fixed
Use fixed inactive dim value, instead of adjusting according to window opacity.
--detect-transient
Use WM_TRANSIENT_FOR to group windows, and consider windows in the same group focused at the same time.
--detect-client-leader
Use WM_CLIENT_LEADER to group windows, and consider windows in the same group focused at the same time. This usually means windows from the same application will be considered focused or unfocused at the same time.WM_TRANSIENT_FOR has higher priority if --detect-transient is enabled, too.
--blur-method, --blur-size, --blur-deviation, --blur-strength
Parameters for background blurring, see the BLUR section for more information.
--blur-background
Blur background of semi-transparent / ARGB windows. Bad in performance, with driver-dependent behavior. The name of the switch may change without prior notifications.
--blur-background-frame
Blur background of windows when the window frame is not opaque. Implies --blur-background. Bad in performance, with driver-dependent behavior. The name may change.
--blur-background-fixed
Use fixed blur strength rather than adjusting according to window opacity.
--blur-kern MATRIX
Specify the blur convolution kernel, with the following format:
In other words, the matrix is formatted as a list of comma separated numbers. The first two numbers must be integers, which specify the width and height of the matrix. They must be odd numbers. Then, the following width * height - 1 numbers specifies the numbers in the matrix, row by row, excluding the center element.
The elements are finite floating point numbers. The decimal pointer has to be . (a period), scientific notation is not supported.
The element in the center will either be 1.0 or varying based on opacity, depending on whether you have --blur-background-fixed. Yet the automatic adjustment of blur factor may not work well with a custom blur kernel.
A 7x7 Gaussian blur kernel (sigma = 0.84089642) looks like:
May also be one of the predefined kernels: 3x3box (default), 5x5box , 7x7box , 3x3gaussian , 5x5gaussian , 7x7gaussian , 9x9gaussian , 11x11gaussian . All Gaussian kernels are generated with sigma = 0.84089642 . If you find yourself needing to generate custom blur kernels, you might want to try the new blur configuration supported by the experimental backends (See BLUR and --experimental-backends).
Exclude conditions for background blur.
--resize-damage INTEGER
Resize damaged region by a specific number of pixels. A positive value enlarges it while a negative one shrinks it. If the value is positive, those additional pixels will not be actually painted to screen, only used in blur calculation, and such. (Due to technical limitations, with --use-damage, those pixels will still be incorrectly painted to screen.) Primarily used to fix the line corruption issues of blur, in which case you should use the blur radius value here (e.g. with a 3x3 kernel, you should use --resize-damage 1 , with a 5x5 one you use --resize-damage 2 , and so on). May or may not work with --glx-no-stencil. Shrinking doesn’t function correctly.
--invert-color-include CONDITION
Specify a list of conditions of windows that should be painted with inverted color. Resource-hogging, and is not well tested.
--opacity-rule OPACITY:'CONDITION'
Specify a list of opacity rules, in the format PERCENT:PATTERN , like 50:name *= "Firefox" . picom-trans is recommended over this. Note we don’t make any guarantee about possible conflicts with other programs that set _NET_WM_WINDOW_OPACITY on frame or client windows.
--shadow-exclude-reg GEOMETRY
Specify a X geometry that describes the region in which shadow should not be painted in, such as a dock window region. Use --shadow-exclude-reg x10+0-0 , for example, if the 10 pixels on the bottom of the screen should not have shadows painted on.
--xinerama-shadow-crop
Crop shadow of a window fully on a particular Xinerama screen to the screen.
--backend BACKEND
Specify the backend to use: xrender , glx , or xr_glx_hybrid . xrender is the default one.
xrender backend performs all rendering operations with X Render extension. It is what xcompmgr uses, and is generally a safe fallback when you encounter rendering artifacts or instability.
glx (OpenGL) backend performs all rendering operations with OpenGL. It is more friendly to some VSync methods, and has significantly superior performance on color inversion (--invert-color-include) or blur (--blur-background). It requires proper OpenGL 2.0 support from your driver and hardware. You may wish to look at the GLX performance optimization options below. --xrender-sync-fence might be needed on some systems to avoid delay in changes of screen contents.
xr_glx_hybrid backend renders the updated screen contents with X Render and presents it on the screen with GLX. It attempts to address the rendering issues some users encountered with GLX backend and enables the better VSync of GLX backends. --vsync-use-glfinish might fix some rendering issues with this backend.
GLX backend: Avoid using stencil buffer, useful if you don’t have a stencil buffer. Might cause incorrect opacity when rendering transparent content (but never practically happened) and may not work with --blur-background. My tests show a 15% performance boost. Recommended.
--glx-no-rebind-pixmap
GLX backend: Avoid rebinding pixmap on window damage. Probably could improve performance on rapid window content changes, but is known to break things on some drivers (LLVMpipe, xf86-video-intel, etc.). Recommended if it works.
--no-use-damage
Disable the use of damage information. This cause the whole screen to be redrawn everytime, instead of the part of the screen has actually changed. Potentially degrades the performance, but might fix some artifacts.
--xrender-sync-fence
Use X Sync fence to sync clients' draw calls, to make sure all draw calls are finished before picom starts drawing. Needed on nvidia-drivers with GLX backend for some users.
--glx-fshader-win SHADER
GLX backend: Use specified GLSL fragment shader for rendering window contents. See compton-default-fshader-win.glsl and compton-fake-transparency-fshader-win.glsl in the source tree for examples.
--force-win-blend
Force all windows to be painted with blending. Useful if you have a --glx-fshader-win that could turn opaque pixels transparent.
--dbus
Enable remote control via D-Bus. See the D-BUS API section below for more details.
--benchmark CYCLES
Benchmark mode. Repeatedly paint until reaching the specified cycles.
--benchmark-wid WINDOW_ID
Specify window ID to repaint in benchmark mode. If omitted or is 0, the whole screen is repainted.
--no-ewmh-fullscreen
Do not use EWMH to detect fullscreen windows. Reverts to checking if a window is fullscreen based only on its size and coordinates.
--max-brightness
Dimming bright windows so their brightness doesn’t exceed this set value. Brightness of a window is estimated by averaging all pixels in the window, so this could comes with a performance hit. Setting this to 1.0 disables this behaviour. Requires --use-damage to be disabled. (default: 1.0)
--transparent-clipping
Make transparent windows clip other windows like non-transparent windows do, instead of blending on top of them.
FORMAT OF CONDITIONS
Some options accept a condition string to match certain windows. A condition string is formed by one or more conditions, joined by logical operators.
Читайте также: