tryone144 / compton

A compositor for X11.

Compton

Compton is a compositor for X, and a fork of xcompmgr-dana.

This branch includes a new blur method: The multi-pass dual_kawase blur! Use it with the --blur-method dual_kawase and --blur-strength LEVEL options. Only works with the glx backend!

Deprecation Notice

This fork contains more of a proof-of-concept than a polished implementation of the dual-filter kawase blur. As you may have noticed, the development on compton seems to have halted. picom is a compton-fork that is actively maintained and has superseeded compton in most distributions already. As of Aug, 31st 2020, picom comes with a better optimized and polished implementation of the dual-filter kawase blur, that will be part of the next regular release (v9).

This fork will most likely not receive any future improvements or fixes. I strongly suggest you give picom a try, unless you absolutely have to use compton.

---

I was frustrated by the low amount of standalone lightweight compositors. Compton was forked from Dana Jansens' fork of xcompmgr and refactored. I fixed whatever bug I found, and added features I wanted. Things seem stable, but don't quote me on it. I will most likely be actively working on this until I get the features I want. This is also a learning experience for me. That is, I'm partially doing this out of a desire to learn Xlib.

Changes from xcompmgr:

• OpenGL backend (--backend glx), in addition to the old X Render backend.
• Inactive window transparency (-i) / dimming (--inactive-dim).
• Titlebar/frame transparency (-e).
• Menu transparency (-m, thanks to Dana).
• shadows are now enabled for argb windows, e.g. terminals with transparency
• removed serverside shadows (and simple compositing) to clean the code, the only option that remains is clientside shadows
• configuration files (see the man page for more details)
• colored shadows (--shadow-[red/green/blue])
• a new fade system
• VSync support (not always working)
• Blur of background of transparent windows, window color inversion (bad in performance)
• Some more options...

Fixes from the original xcompmgr:

• fixed a segfault when opening certain window types
• fixed a memory leak caused by not freeing up shadows (from the freedesktop repo)
• fixed the conflict with chromium and similar windows
• many more

Building

Dependencies:

B for build-time

R for runtime

• libx11 (B,R)
• libxcomposite (B,R)
• libxdamage (B,R)
• libxfixes (B,R)
• libXext (B,R)
• libxrender (B,R)
• libXrandr (B,R)
• libXinerama (B,R) (Can be disabled with NO_XINERAMA at compile time)
• pkg-config (B)
• make (B)
• xproto / x11proto (B)
• sh (R)
• xprop,xwininfo / x11-utils (R)
• libpcre (B,R) (Can be disabled with NO_REGEX_PCRE at compile time)
• libconfig (B,R) (Can be disabled with NO_LIBCONFIG at compile time)
• libdrm (B) (Can be disabled with NO_VSYNC_DRM at compile time)
• libGL (B,R) (Can be disabled with NO_VSYNC_OPENGL at compile time)
• libdbus (B,R) (Can be disabled with NO_DBUS at compile time)
• asciidoc (B) (and docbook-xml-dtd-4.5, libxml-utils, libxslt, xsltproc, xmlto, etc. if your distro doesn't pull them in)

How to build

To build, make sure you have the dependencies above:

# Make the main program
$ make
# Make the man pages
$ make docs
# Install
$ make install

(Compton does include a _CMakeLists.txt in the tree, but we haven't decided whether we should switch to CMake yet. The Makefile is fully usable right now.)

Known issues

• Our FAQ covers some known issues.

• VSync does not work too well. You may check the VSync Guide for how to get (possibly) better effects.

• If --unredir-if-possible is enabled, when compton redirects/unredirects windows, the screen may flicker. Using --paint-on-overlay minimizes the problem from my observation, yet I do not know if there's a cure.

• compton may not track focus correctly in all situations. The focus tracking code is experimental. --use-ewmh-active-win might be helpful.

• The performance of blur under X Render backend might be pretty bad. OpenGL backend could be faster.

• With --blur-background you may sometimes see weird lines around damaged area. --resize-damage YOUR_BLUR_RADIUS might be helpful in the case.

Usage

Please refer to the Asciidoc man pages (man/compton.1.asciidoc & man/compton-trans.1.asciidoc) for more details and examples.

Note a sample configuration file compton.sample.conf is included in the repository.

Support

• Bug reports and feature requests should go to the "Issues" section above.

• Our (semi?) official IRC channel is #compton on FreeNode.

• Some information is available on the wiki, including FAQ, VSync Guide, and Performance Guide.

License

Although compton has kind of taken on a life of its own, it was originally an xcompmgr fork. xcompmgr has gotten around. As far as I can tell, the lineage for this particular tree is something like:

• Keith Packard (original author)
• Matthew Hawn
• ...
• Dana Jansens
• chjj and richardgv

Not counting the tens of people who forked it in between.

Compton is distributed under MIT license, as far as I (richardgv) know. See LICENSE for more info.

compton's Issues

xrandr multihead setup not working

Hello,

Switching monitors using xrandr doesn't work correctly when I'm running this compton fork.
I'm running arch on a laptop and when I want to switch to an external monitor using xrandr --output HDMI1 --primary --mode 2560x1440 --pos 0x0 --output VIRTUAL1 --off --output eDP1 --off the output breaks.

But running this command from my .xinitrc works.

screenshot laptop (works)
screenshot extermal (broken)

I posted this Issue in the archlinux forum and someone suggestet this:

the problem is w/ either your WM or compositor not catching the geometry change (and thus eg. not updating glViewport() for a GL compositor)

When I use the official compton version (from the arch repo) or disable compton everything works fine.

Platform: Arch Linux 5.0.2

GPU, drivers, and screen setup:
Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Graphics Controller,
xf86-video-intel 1:2.99.917+863+g6afed33b-1 (driver),
Laptop screen + external Monitor configured with xrandr

My compton config

Compton command:
compton -b --xrender-sync-fence --blur-background --blur-method kawase --blur-strength 10
or
compton -b --xrender-sync-fence

Won't install aur package

Auto-merging src/picom.c
CONFLICT (content): Merge conflict in src/picom.c
Auto-merging src/config.h
Auto-merging src/config.c
error: could not apply a31ee33... Add new blur_method dual_kawase
Resolve all conflicts manually, mark them as resolved with
"git add/rm <conflicted_files>", then run "git rebase --continue".
You can instead skip this commit: run "git rebase --skip".
To abort and get back to the state before "git rebase", run "git rebase --abort".
Could not apply a31ee33... Add new blur_method dual_kawase
==> ERROR: A failure occurred in prepare().
Aborting...
==> ERROR: Makepkg was unable to build picom-tryone-git.

Some windows are not displayed after reloading i3

Hi,

I was not sure if I should post this issue here or at the compton-git repo. I am using arch with i3 and wanted to apply blur in combination with transparency. Everything works fine, but if I reload i3 (mod+Shift+r) windows are not properly displayed anymore. The same occurs with the normal compton package. To test if this a general problem for my configuration I installed xcompmgr and there is no problem. Also compton outputs a lot of Bad Window erros. After killing the compton process all windows are displayed but obviously without transparency. Starting the process again leads to the same problem.
I could not determine which applications are affected since e.g. firefox is displayed on one workspace but not on another.

Feature request: blur whitelist option

Would be nice to have an option to define which windows have blur transparency instead of having to blacklist everything else.

Can't make Kawase blur work

Hi tryone144,

Thank you for the great work, to try out kawase blur on top of compton I am moved to your fork. This is no urgent matter, so please take your time.

Platform: Arch Linux with i3-gaps
Terminal: Urxvt
Compton version: compton-tryone-git 0.1_beta2.95.g241bbc5-1 (built from AUR)
Compton configuration: https://pastebin.com/WNaDnCt0
.Xresources: https://pastebin.com/xgAqw81M

Kawase blur is not working with package installed. Tried to reinstall, no joy. At this stage I can only get the translucency work by changing the RGBA value.

Disapearing notifications after turning on kwargs blur

Notification gone completly after running with kwargs blur and glx. Any ideas how to fix it?

shadow-exclude = [
	"name = 'Notification'",
	"class_g = 'Conky'",
	"class_g ?= 'Notify-osd'",
	"class_g = 'Cairo-clock'",
	"_GTK_FRAME_EXTENTS@:c"
];

I was trying this without success

Disassociate Fade and Blur

Hello @tryone144 thanks for your work on this, it's Awesome.

However I noticed that If I use blurred background with the Fade-in/Fade-out feature It's don't work properly in my opinion.

Because today Fade-out feature basically change the opacity from the current level to 0 making the Client transparent while the blur feature make a transparent Client blurred.

The result is that all the fade-in or the fade-out create blur which could be a valid option but the problem here is that the blur "appear" or "disappear" instantly at entrance or exit of Client which break for me the use of the fading feature which is supposed to be a gentle transition.

Instead I would prefer that the opacity of the fading feature is independant of the opacity of the Client. It's mean that a blurred Client fading-out will appear less and less blurred and more an more transparent and would disappear gently.

Maybe it's already possible Im not a pro in Compton...

Please let me konw of what you are thinking about it.

Thanks in advance.

No blur on experimental branch

Platform: Void Linux glibc

GPU, drivers, and screen setup: laptop screen , intel integrated graphics

Compton version: feature/dual_kawase branch, picom (vgit-c67d7)

Compton configuration: simple config for testing

inactive-opacity = 0.6;
active-opacity = 0.8;

blur-method = "dual_kawase";
blur-strength = 6.9;

backend = "glx";

Steps of reproduction

Install experimental branch from source. Run via "picom --experimental-backends" with above configuration.

Expected behavior

Pretty blurred windows

Current Behavior & Other details

Windows are only transparent with no blur. I have tried configuring it only with command line flags (i.e picom --experimental-backends --blur-method dual_kawase --backend glx), and dropping in other peoples configs for this branch and still have no blur only transparency.

Cannot install on ubuntu 19.10

meson --buildtype=release . build

The Meson build system
Version: 0.51.2
Source dir: /home/anuj/Desktop/compton
Build dir: /home/anuj/Desktop/compton/build
Build type: native build
Project name: picom
Project version: 7
C compiler for the host machine: cc (gcc 9.2.1 "cc (Ubuntu 9.2.1-9ubuntu2) 9.2.1 20191008")
Build machine cpu family: x86_64
Build machine cpu: x86_64
Program git found: YES (/usr/bin/git)
Has header "stdc-predef.h" : YES
Compiler for C supports arguments -Wall: YES
Compiler for C supports arguments -Wcast-function-type: YES
Compiler for C supports arguments -Wignored-qualifiers: YES
Compiler for C supports arguments -Wmissing-parameter-type: YES
Compiler for C supports arguments -Wnonnull: YES
Compiler for C supports arguments -Wshadow: YES
Compiler for C supports arguments -Wno-type-limits -Wtype-limits: YES
Compiler for C supports arguments -Wold-style-declaration: YES
Compiler for C supports arguments -Woverride-init: YES
Compiler for C supports arguments -Wsign-compare: YES
Compiler for C supports arguments -Wtype-limits: YES
Compiler for C supports arguments -Wuninitialized: YES
Compiler for C supports arguments -Wshift-negative-value: YES
Compiler for C supports arguments -Wunused-but-set-parameter: YES
Compiler for C supports arguments -Wunused-parameter: YES
Compiler for C supports arguments -Wimplicit-fallthrough: YES
Compiler for C supports arguments -Wno-unknown-warning-option -Wunknown-warning-option: NO
Compiler for C supports arguments -Wno-missing-braces -Wmissing-braces: YES
Compiler for C supports arguments -Wconversion: YES
Compiler for C supports arguments -Wempty-body: YES

|Executing subproject test.h method meson
|
|Project name: test.h
|Project version: undefined
|C compiler for the host machine: cc (gcc 9.2.1 "cc (Ubuntu 9.2.1-9ubuntu2) 9.2.1 20191008")
|Build targets in project: 0
|Subproject test.h finished.

Found pkg-config: /home/linuxbrew/.linuxbrew/bin/pkg-config (0.29.2)
Did not find CMake 'cmake'
Found CMake: NO
Run-time dependency libev found: NO (tried pkgconfig and cmake)
Library ev found: YES
Library m found: YES
Run-time dependency x11 found: NO (tried pkgconfig)

src/meson.build:27:1: ERROR: Dependency "x11" not found, tried pkgconfig

A full log can be found at /home/anuj/Desktop/compton/build/meson-logs/meson-log.txt

Build docs failed on Linux Mint 18.3

Platform: Linux Mint 18.3 (Based on Ubuntu 16.04).

GPU, drivers, and screen setup: A Lenovo G400 laptop with Intel GPU.

Compton version: Both latest release version and the dual_kawase branch from git.

Steps of reproduction

$ make 

finished with a bunch of warnings

$ make docs

failed with this Error

a2x --format manpage man/compton.1.asciidoc
  File "/usr/bin/a2x", line 76
    print '%s: %s' % (PROG,msg)
                 ^
SyntaxError: invalid syntax
Makefile:146: recipe for target 'man/compton.1' failed
make: *** [man/compton.1] Error 1

gcc is v6.5.0

Cannot initiate compton

Installed from the AUR package. Having problem to initiate. When attempted to launch from the terminal, it returns

$ compton --config ~/.config/compton.conf
glx_hasglxext(): Missing GLX extension GLX_EXT_texture_from_pixmap.

config has been given here.

Tried overriding the config file parameters with

compton --blur-background --blur-method kawase --blur-strength 5 --glx-no-rebind-pixmap false --glx-use-copysubbuffermesa true

Which shows,

get_cfg(): compton doesn't accept positional arguments.

glxinfo | grep -i opengl shows,

OpenGL vendor string: X.Org
OpenGL renderer string: AMD HAINAN (DRM 2.50.0, 5.4.30-1-lts, LLVM 9.0.1)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 20.0.4
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.5 (Compatibility Profile) Mesa 20.0.4
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.0.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

Neither directory contains a build file meson.build

I'm trying to build, i clone and cd into directory but even with meson/ninja and all the dependencies installed, it gives me this error

dual_kawase creating weird blur box around Firefox utility menu

Platform: Archlinux 64-bit, i3-gaps, X11.

GPU, drivers, and screen setup: Integrated Intel, Single monitor (Laptop).

Compton version: picom-tryone-git 1325_Next.44.g7e31e28_2020.03.07-1 from AUR

Compton configuration: https://pastebin.com/XBCdJ0LD

Steps of reproduction

I executed picom using the following command:
picom --experimental-backends --blur-method dual_kawase --blur-strength 10

Executing with only picom with no arguments won't produce this issue. But I'll lose dual_kawase blur.

Expected behavior

No weird blur border.

Current Behavior & Other details

A weird blur border is surrounding the utility window.

Remove Darkening Around Kawase'd Windows

Platform

Arch Linux

GPU, drivers, and screen setup

Intel Graphics, xf86-video-intel

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) Ivybridge Mobile  (0x166)
    Version: 19.3.2
    Accelerated: yes
    Video memory: 1536MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.2
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.0
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile 
OpenGL core profile version string: 4.2 (Core Profile) Mesa 19.3.2
OpenGL core profile shading language version string: 4.20
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.0 Mesa 19.3.2
OpenGL shading language version string: 1.30
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.3.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

Environment

Awesome Window Manager

picom version

picom feature/dual_kawase vgit-f92eb

Configuration:

# Shadow
shadow = false;
shadow-radius = 7;
shadow-offset-x = -7;
shadow-offset-y = -7;
log-level = "warn";
# log-file = "/path/to/your/log/file";
shadow-opacity = 0.0;
# shadow-red = 0.0;
# shadow-green = 0.0;
# shadow-blue = 0.0;
shadow-exclude = [
	"name = 'Notification'",
	"class_g = 'Conky'",
	"class_g ?= 'Notify-osd'",
	"class_g = 'Cairo-clock'",
	"_GTK_FRAME_EXTENTS@:c"
];
# shadow-exclude = "n:e:Notification";
# shadow-exclude-reg = "x10+0+0";
# xinerama-shadow-crop = true;

# Opacity
# inactive-opacity = 0.8;
# active-opacity = 0.8;
# frame-opacity = 0.7;
# inactive-opacity-override = false;
# inactive-dim = 0.2;
# inactive-dim-fixed = true;

blur: {
  method = "dual_kawase";
  strength = 2.0;
  # deviation = 1.0;
  # kernel = "11x11gaussian";
}

# blur-background = true;
# blur-background-frame = true;
blur-kern = "3x3box";
# blur-kern = "5,5,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1";
# blur-background-fixed = true;
blur-background-exclude = [
	"window_type = 'dock'",
	"window_type = 'desktop'",
	"_GTK_FRAME_EXTENTS@:c"
];
# opacity-rule = [ "80:class_g = 'URxvt'" ];

# max-brightness = 0.66

# Fading
fading = true;
# fade-delta = 30;
fade-in-step = 0.03;
fade-out-step = 0.03;
# no-fading-openclose = true;
# no-fading-destroyed-argb = true;
fade-exclude = [ ];

# Other
backend = "glx";
mark-wmwin-focused = true;
mark-ovredir-focused = true;
# use-ewmh-active-win = true;
detect-rounded-corners = true;
detect-client-opacity = true;
refresh-rate = 0;
vsync = true;
# sw-opti = true;
# unredir-if-possible = true;
# unredir-if-possible-delay = 5000;
# unredir-if-possible-exclude = [ ];
focus-exclude = [ "class_g = 'Cairo-clock'" ];
detect-transient = true;
detect-client-leader = true;
invert-color-include = [ ];
# resize-damage = 1;

# GLX backend
# glx-no-stencil = true;
# glx-no-rebind-pixmap = true;
# xrender-sync-fence = true;
use-damage = true;

# Window type settings
wintypes:
{
  tooltip = { fade = true; shadow = false; opacity = 0.75; focus = true; full-shadow = false; };
  dock = { shadow = false; }
  dnd = { shadow = false; }
  popup_menu = { opacity = 0.8; }
  dropdown_menu = { opacity = 0.8; }
};

Steps of reproduction

1. Enable the blur using the blur:{ .. } just like in my config above.
2. Add opacity effect to terminals.
3. Remove gaps or move two blurred transparent window next to each other

Expected behavior

There's should be no darkening between the blurred windows

Current Behavior

There are some darkening around the blurred terminals

Other details

If I set the blur method to none, the dark borders disappeared. But even setting the blur strength to 0.0, it still appears.
Earlier, I found out that the shadow-like effect shows when if there is --experimental-backends

With that being said, my question is: Is there a way to disable this effect?
Launching picom by:

picom -b --experimental-backends --dbus --config picom.conf 

Config file location

Where is the configuration file location? On ~/.config/compton there's nothing (more like the folder doesn't even exist).

Config option for kawase blur?

Is there a way of specifying that I want to use kawase blur in compton.conf?
Currently I'm using command options but that's not very convenient.

Getting it up to date with origin

Hi there!

Any plans on merging the newest origin compton into it?

Seems like updates are two/one years ago, so there might have been some changes. As this compton fork gets some popularity nowadays in /r/unixporn, that might be for some folks. :>

Kawase blur distorted

Platform: Ubuntu Desktop 20.04 amd64

GPU, drivers, and screen setup: NVidia GTX 850M, nvidia-drivers 440.100, one monitor

Compton version: 241bbc5 from this repository

Compton configuration:

backend = "glx";

blur-background = true;
blur-background-frame = true;
blur-kern = "5x5gaussian";
blur-method = "kawase";
blur-strength = 12;
resize-damage = 12;

Steps of reproduction

I set transparency of my gnome terminal around 25%

Expected behavior

I expected to see smooth blur

Current Behavior & Other details

Blur is distorted

How can I fix it? Seems like my monitor depth is losing some bits, but I don't know exactly what it is. I just want smooth blur.
Thank you!

Picture in terminal

Hello @tryone144 , the compositor is so great.but I found It have a bug for display picture in terminal.
I tried other terminal, but it still doesn't work unless I run "killall compton". So I think it might be a compton's bug.
My configuration is the default file from your respository.
I'm sorry for my English expression to you 🤣 。

Compton Tryone only works once on install / reinstall

Platform: Arch Linux, 5.2.10-arch1-1-ARCH

Screen setup: two monitors (1280x720, 1920x1080) with xrandr

CPU: Intel i7-7500U (4) @ 3.500GHz
GPU: NVIDIA GeForce 940MX and Intel HD Graphics 620

Compton version: git-v0.1_beta2-95-g241bbc5-2018-02-22

Steps of reproduction and current behaviour

1. I git clone'd the compton-tryone-git AUR package and used makepkg -si to install it.
2. I used the command compton --backend glx --blur-background --blur-method kawase --blur-strength 8 and it worked, but ONLY for the terminal Compton Tryone was started in. In addition, any new terminals I open are not transparent or blurred.
3. If I Ctrl+C in the blurred terminal and try to start Compton again with the exact same command in step 2, nothing happens. All subsequent execution of the command in step 2 does nothing, even after logging out or rebooting...
4. ...EXCEPT if I uninstall compton-tryone-git and install the vanilla compton, and then reinstall compton-tryone-git with makepkg -si. But then I'm back at step 2 again and compton-tryone-git only works once.

It's almost as if reinstalling compton overwrites some settings that allows compton-tryone-git to work.

compton.conf file

This is a copy of the original file /etc/xdg/compton.conf, which I copied to ~/.config/compton/compton.conf and added the following:

opacity-rule = [
  "95:class_g = 'Termite' && focused",
  "90:class_g = 'Termite' && !focused"
];

I can confirm that Compton is reading this file.

remove blur from conky

Desktop: i3
Hi first of all I want to thank you for made this awesome program free, so let's go.
I have some conky scripts configured and I would like that conky stay transparent and do not apply blur. I want blur only my terminal.
So what I did to try achieve this?
I tried add in
blur-background-exclude=["class_g = 'Conky' ", "i:e:Conky"]; but without success, blur on conky scripts still there.
I suspect that the problem may reletated with conky because to display windows nicely in i3 I set window_type=override for all my conky scripts, and when I try search with xdotool the 'Conky' classname nothing returns to me in terminal, any tips to solve this???

All windows (and polybar) have very low opacity, blur doesn't always work. Restarting compton has weird results

Platform:
Arch 5.8.3-arch1-1

GPU, drivers, and screen setup:
i7 7700HQ, Nvidia GTX 1050, nvidia proprietary drivers 450.66-14, one laptop monitor, one monitor connected to HDMI, one connected to DisplayPort. Configured with xrandr. Running on bspwm.

Compton version:
git-v0.1_beta2-95-g241bbc5-2018-02-22

Compton configuration:
https://github.com/zjeffer/dotfiles/blob/master/compton/compton.conf

Started from bspwmrc, which is started from .xinitrc. X is started by LightDM.

Steps of reproduction

1. Boot bspwm with compton in bspwmrc.

Here it has a high chance that all windows including polybar will be very transparent. Even windows that aren't mentioned in the config. The cursor is fine.

2. Launch some apps like Firefox and your terminal emulator. (for me Firefox doesn't have an opacity rule, but my terminal emulator does)

3. Restart compton using either a keyboard shortcut that reruns bspwmrc or use a terminal to kill compton, then start it.

In this step, most of the time it makes some windows have very low opacity, some windows have the desired opacity described in the opacity-rules. After 1 restart, polybar has the correct opacity.

Rarely, some windows can have blur. If that's the case, all windows opened from that point forward will also have blur

When everything has low opacity, opening new apps creates windows that have normal opacity.

4. Keep restarting compton. If at least 1 window has working blur (which happens very rarely), close all apps. All apps opened from now on should have the correct configuration. Sometimes everything works (opacity rules, shadows, etc) except for the blur.

Here are two images: top is with compton, bottom is without. As you can see, Firefox is very transparent in the first image, even though it isn't in the opacity-rules in compton.conf.

Expected behavior

Windows should have the correct opacity and blur described in compton.conf.

Other details

This started happening a couple of days ago, seemingly after I reinstalled a lightdm theme. It was installed manually a long time ago but I realized I could install it using pacman.

The next day I completely reinstalled Linux and deleted everything. I used the same config files and had the same exact problem. Is there something wrong with my config file?

picom (with dual kawase blur) crashes whenever i try to close a window

Platform: arch linux xfce4, on a laptop

GPU, drivers, and screen setup: nvidia geforce mx130

Picom version: 1417_Next.136.g7a3137b_2020.04.11-1 from aur

Picom configuration: https://pastebin.com/NfkB39wx

Steps of reproduction

config path is in ~/.config/picom/picom.conf, try to run it on autostart for xfwm but it crashes whenever i try to close a window, command is picom --experimental-backends

Expected behavior

will not crash and quit the program whenever i close a window (by clicking the x button on the upper right corner of the window)

Current Behavior & Other details

when i try to run it on a terminal and try to close a window, this error message shows:
[toby@tobyarch ~]$ picom --experimental-backends [ 06/17/2020 00:12:41.739 win_clear_flags WARN ] Flags cleared on a destroyed window 0x00c0373f (Terminal - toby@tobyarch:~) [ 06/17/2020 00:12:51.438 win_clear_flags WARN ] Flags cleared on a destroyed window 0x00c03a12 (Terminal - toby@tobyarch:~) [ 06/17/2020 00:13:00.179 win_clear_flags WARN ] Flags cleared on a destroyed window 0x00c00c35 (#╭ミ★・general - Discord) [ 06/17/2020 00:13:00.179 win_clear_flags WARN ] Flags cleared on a destroyed window 0x00c00c35 (#╭ミ★・general - Discord) [ 06/17/2020 00:13:00.181 win_clear_flags WARN ] Flags cleared on a destroyed window 0x00c00c35 (#╭ミ★・general - Discord) picom: ../src/backend/backend.c:270: paint_all_new: Assertion !(w->flags & WIN_FLAGS_SHADOW_NONE)' failed.
Aborted (core dumped)
`
i tried to open a blank terminal screen and close it, it closes normally. try to run it with a command and exited, it closes normally. however when i try to close discord, it crashed and aborted the program

unable to build for MPR due to warnings treated as errors in makepkg & makedeb

i am trying to include tryone144/compton into MPR(https://dur.hunterwittenborn.com/) and i have pkgbuild ready to deploy.
however the problem i am facing is that the build function in my pkgbuild get stopped due to warnings being treated as errors. more details are shown below.

1. here is my pkgbuild https://termbin.com/5nig
2. the problem is- while running the make command, the build() function is stopped as there are a bunch of warnings that pop up while running make, these warnings are treated as errors and the makepkg command stops the whole building process.
   https://termbin.com/ha8j<--- this is the error that happens
3. is it possible to rectify the code so as to remove the warnings in the build process?

Dramatically CPU usage on high resolutions (Blur operation)

Platform: Archlinux 5.9.10, i3wm

GPU, drivers, and screen setup: Nvidia Titan RTX, nvidia-drivers 455.45.01-2, one monitor 2560x1440 resolution

Compton version: git-v0.1_beta2-95-g241bbc5-2018-02-22 from aur

Compton configuration: default configuration with glx backend

Steps of reproduction

• open terminal with blured background
• open application like htop
• move arrows up and down to update window state
• watch your CPU dying =)

Expected behavior

CPU usage should not take half of system resources.

Current Behavior & Other details

CPU usage takes half of system resources on blur operation.

Won’t build on Arch AUR

Trying to install - getting this error in the PKGBUILD

==> Starting prepare()...
fatal: remote yshui already exists.
==> ERROR: A failure occurred in prepare().
Aborting...

Command 'makepkg --force' failed to execute.

Is it meant to refer back to the yshui repo??

no such file when make docs

Platform:
manjaro 20
GPU, drivers, and screen setup:
Graphics: Device-1: Intel UHD Graphics 630 driver: i915 v: kernel
Display: x11 server: X.Org 1.20.8 driver: intel unloaded: modesetting resolution: 1600x900~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 20.1.5

Compton version:
git-v0.1_beta2-95-g241bbc5-2018-02-22
Compton configuration:
Same with this repo no extra config yet.

Steps of reproduction

make # success

make docs 11:52:59
a2x --format manpage man/compton.1.asciidoc
make: a2x: No such file or directory
make: *** [Makefile:146: man/compton.1] Error 127

Expected behavior

files in man folder:

-rw-r--r-- 1 lizhe lizhe 1.4K 8月 26 11:48 CMakeLists.txt
-rw-r--r-- 1 lizhe lizhe 24K 8月 26 11:48 compton.1.asciidoc
-rw-r--r-- 1 lizhe lizhe 2.0K 8月 26 11:48 compton-trans.1.asciidoc

Where is the compton.1 file ?

Screen is blacked if monitor is powered on/off

Platform: Void Linux x86_64
GPU, drivers, and screen setup: NVidia GTX 1050 with Displayport (if that helps)

Compton version: git head on branch feature/dual_kawase (commit 75dd105)

Compton configuration: --experimental-backends --backend glx --blur-background --blur-method dual_kawase --blur-strength 7

Steps of reproduction

1. clone the repo
2. git checkout feature/dual_kawase
3. build it
4. run it with
5. turn off/unplug monitor
6. turn on monitor
   [screen is black]
7. hit ctrl-c to kill picom
8. watch as the screen comes back

Expected behavior

I can turn on and off my monitor and it will work

high I/O on experimental backends

Platform: Arch linux amd64

GPU, drivers, and screen setup: Intel UHD Graphics 620, laptop

Compton version: 1328_Next.47.g7eebdbc_2020.03.12-1

Compton configuration: https://pastebin.com/J9w4WUbU

Steps of reproduction

run picom with --experimental-backends
see iotop
picom is frequently on top
issue is not present without --experimental-backends

Expected behavior

no changes on io load on both run modes

Current Behavior & Other details

https://imgur.com/NhXJJqI

Blur kawase not working

Platform: Manjaro + i3-gaps
Compton version: git-v0.1_beta2-95-g241bbc5-2018-02-22
Compton configuration: https://pastebin.com/5PnZsXCQ
Terminal: Termite
I've no idea why it doesn't work.

Blur strength not working in config file

Platform: Arch

Compton version: picom-tryone-git 1361_0.1_beta2.1012.gc67d7d7_2020.03.31-1 from AUR

Compton configuration:

backend = "glx";
blur-method = "dual_kawase";
blur-strength = 1;

Steps of reproduction

Run:

picom --experimental-backends

Expected behavior

The blur strength is changed as specified in the config file.

Current Behavior & Other details

The blur strength is the same as the default behaviour.

When the blur-strength line is removed and added to the command then it works as expected.

Add the option to keep rendering a window, even if it is not visible or on the focused workspace

Hi

I was looking into obs-studio and noticed that the captured window is gone if I alt-tab from it. At first I thought it was an OBS Studio thing but then I read this issue on their repo, that points out that is supposed to be a Xcompositor behavior. And I figured that behavior generally makes a lot of sense, no need to compute something that is not visible. Except in the case that you still want it captured by some video recording software, for example.

I have no idea of how viable or hard this would be, but I think that option would be a pretty neat addition. I wasn't sure whether to post this question on the upstream compton, but I thought I should just suggest this on the fork I use.

What are your thoughts on it?

White windows with NVIDIA GPU

Platform: Xubuntu Desktop 19.10 amd64

GPU, drivers, and screen setup: NVidia 940MX, nvidia-drivers 435.21

Compton version: git-v0.1_beta2-95-g241bbc5-2018-02-22

Compton configuration: http://my.opendesktop.org/s/SpcapKgySxmHmzG

Steps of reproduction

Open some apps, like Rambox, Q4WINE, Ferdi and WINE apps in general too.

Expected behavior

Normal window behaviour.

Current Behavior & Other details

Those windows are randomly show white frame, without any content, if I minimize and restore, it's working.

It's not happening on Intel GPU.

dual_kawase causing segmentation fault

Hi everyone, thanks for the great work :)
I'm having trouble setting up the blur method for this fork. Some info from my system:

OS: Arch Linux x86_64
GPU: AMD ATI Radeon HD 8650G using open source radeon
Compton version: 1340_Next.59.g0cc7437_2020.03.18-1 from AUR
WM: i3-gaps

Relevant configuration from my picom.conf (the rest is default):

backend = "glx";
blur-background-fixed = false;
blur-background-exclude = [
    "window_type = 'dock'",
    "window_type = 'desktop'"
];

blur-method = "dual_kawase";
blur-strength = "4";

Steps of reproduction

Call picom from urxvt with this command picom --experimental-backends and move around in my system, for instance, call neofetch from urxvt.

Expected behavior

Awesome blur for my terminals and transparent windows.

Current Behavior & Other details

Blur works, but when I move around my terminals (call neofetch, vim, etc), picom crashes and throws Segmentation fault (core dumped). If i don't set a blur method or don't use experimental-backends, everything works fine.

Any help is much appreciated and if can proportionate more info, just ask for it.
Sincerely,
Jaime

AUR won't compile "compton-tryone144-git"

it just gives this error like this when I try to download it

$ yay -S compton-tryone-git                                                                                                     ↵ 1
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur:1]  compton-tryone-git-0.1_beta2.95.g241bbc5-1

  1 compton-tryone-git               (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> A
:: Deleting (1/1): /home/gorogorochan/.cache/yay/compton-tryone-git
:: (1/1) Downloaded PKGBUILD: compton-tryone-git
  1 compton-tryone-git               (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
:: (1/1) Parsing SRCINFO: compton-tryone-git
==> Making package: compton-tryone-git 0.1_beta2.95.g241bbc5-1 (Mon 01 Aug 2022 11:51:08 PM +03)
==> Retrieving sources...
  -> Cloning compton git repo...
Cloning into bare repository '/home/gorogorochan/.cache/yay/compton-tryone-git/compton'...
fatal: unable to connect to github.com:
github.com[0: 140.82.121.4]: errno=Connection timed out

==> ERROR: Failure while downloading compton git repo
    Aborting...
 -> error making: compton-tryone-git

I usually never have this issue while trying to compile stuff from the AUR...

Blurred border around windows

Ubuntu Desktop 19.10, Xfce 4.14

NVidia GTX 670, nvidia driver 440, one monitor

Latest version of kawase, without alpha hack

# Shadow
shadow = true;
no-dnd-shadow = true;
no-dock-shadow = true;
clear-shadow = true;
shadow-radius = 12;
shadow-offset-x = -10;
shadow-offset-y = -7;
shadow-opacity = 0.7;
# shadow-red = 0.0;
# shadow-green = 0.0;
# shadow-blue = 0.0;
shadow-exclude = [
	"name = 'Notification'",
	"class_g = 'Conky'",
	"class_g ?= 'Notify-osd'",
	"class_g = 'Cairo-clock'",
	"_GTK_FRAME_EXTENTS@:c"
];

#shadow-exclude = "n:e:Menu";
# shadow-exclude-reg = "x10+0+0";
# xinerama-shadow-crop = true;

# Opacity
menu-opacity = 0.8;
#menu-opacity-override = false;
#inactive-opacity = 0.8;
#active-opacity = 0.8;
active-opacity-override = true;
frame-opacity = 0.8;
inactive-opacity-override = false;
alpha-step = 0.06;
#inactive-dim = 0.2;
#inactive-dim-fixed = true;
#blur-background = true;
blur-background-frame = true;
blur-method = "kawase";
blur-strength = 10;
blur-background-fixed = false;
#blur-kern = "11x11gaussian";
#blur-kern = "5,5,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1";

blur-background-exclude = [
	"window_type = 'dock'",
	"window_type = 'desktop'"
];

#"_NET_WM_OPAQUE_REGION@:c",
#"_GTK_FRAME_EXTENTS@:c",
#opacity-rule = [ "80:class_g = 'URxvt'" ];

# Fading
fading = true;
# fade-delta = 30;
fade-in-step = 0.06;
fade-out-step = 0.04;
#no-fading-openclose = true;
#no-fading-destroyed-argb = true;
fade-exclude = [ ];

# Other
backend = "glx";
mark-wmwin-focused = true;
mark-ovredir-focused = true;
# use-ewmh-active-win = true;
detect-rounded-corners = true;
detect-client-opacity = true;
refresh-rate = 0;
vsync = "opengl-swc";
dbe = false;
paint-on-overlay = true;
# sw-opti = true;
# unredir-if-possible = true;
# unredir-if-possible-delay = 5000;
# unredir-if-possible-exclude = [ ];
focus-exclude = ["class_g = 'Cairo-clock'"];
detect-transient = true;
detect-client-leader = true;
invert-color-include = [ ];
# resize-damage = 1;

# GLX backend
#glx-no-stencil = false;
glx-copy-from-front = false;
# glx-use-copysubbuffermesa = true;
glx-no-rebind-pixmap = true;
glx-swap-method = "undefined";
# glx-use-gpushader4 = true;
# xrender-sync = true;
# xrender-sync-fence = true;

# Window type settings
wintypes:
{
 	tooltip = {fade = true; shadow = false; opacity = 0.75; focus = true; };
};

Many windows have a weird blurred transparent border around them. This is an example of a menu in Galculator. Most menus and tooltips have them, some top level windows also have it around the window. The width of the blurred margin seems to depends on what type of window it is.

I have tried disabling shadows in comptom.conf, I have tried removing shadows from the GTK theme I'm using (Qogir-dark) and I have tried changing blur exclude. However, none of these have fixed the problem so far. I have tried several settings for blur exclude. GTK_FRAME_EXTENTS, removes the blur from many windows entirely. _NET_WM_OPAQUE_REGION produces the same result as I have now.

My best guess is that it relates to the WM drawing shadows around the windows, specifically because the width of the border changes. I don't know if its the theme, the decorator, or compton drawing the shadows. None of them seem to make any difference. I cannot figure out how to make the blur stay inside the window, or turn these shadows off.

[Feature Request] Add ability to change blur strength externally

Awesome work you did with dual_kawase

I was wondering if changing the blur strength externally, through IPC for example, could be a wanted feature

Picom crashes with almost every window close/workspace change

Build is tryone144/compton@feature/dual_kawase rebased against yshui/picom@b652e8b

Crashes look to be caused by the assertion added in yshui/picom@a23bac7

Apr 05 21:45:26 frebib-PC.nerdhouse.io picom[35589]: picom: ../src/backend/backend.c:221: paint_all_new: Assertion `blur_opacity >= 0 && blur_opacity <= 1' failed.
Apr 05 21:45:26 frebib-PC.nerdhouse.io systemd[4272]: picom.service: Main process exited, code=dumped, status=6/ABRT
Apr 05 21:45:26 frebib-PC.nerdhouse.io systemd[4272]: picom.service: Failed with result 'core-dump'.
Apr 05 21:45:26 frebib-PC.nerdhouse.io systemd-coredump[35720]: Process 35589 (picom) of user 1000 dumped core.

                                                                Stack trace of thread 35589:
                                                                #0  0x00007f3427d4ace5 raise (libc.so.6 + 0x3bce5)
                                                                #1  0x00007f3427d34857 abort (libc.so.6 + 0x25857)
                                                                #2  0x00007f3427d34727 __assert_fail_base.cold (libc.so.6 + 0x25727)
                                                                #3  0x00007f3427d43426 __assert_fail (libc.so.6 + 0x34426)
                                                                #4  0x0000561193d4eb99 paint_all_new (picom + 0x35b99)
                                                                #5  0x0000561193d27d09 _draw_callback (picom + 0xed09)
                                                                #6  0x0000561193d28ab9 draw_callback (picom + 0xfab9)
                                                                #7  0x00007f34286bf033 ev_invoke_pending (libev.so.4 + 0x5033)
                                                                #8  0x00007f34286c2902 ev_run (libev.so.4 + 0x8902)
                                                                #9  0x0000561193d247f3 session_run (picom + 0xb7f3)
                                                                #10 0x00007f3427d36023 __libc_start_main (libc.so.6 + 0x27023)
                                                                #11 0x0000561193d25bfe _start (picom + 0xcbfe)

Config: https://gist.github.com/frebib/76790ba48c0a2f51b352f0be0c2b4fa1/raw

dual_kawase Blur does not work with --backend glx

Platform: ArcoLinuxB 20.4.10

GPU, drivers, and screen setup: Sapphire Pulse Radeon RX 5600 XT, rounded corners fork of i3wm, dual monitors set up with xrandr.

Compton version: vgit-c67d7

Compton configuration: https://pastebin.com/MWthVngz

Steps of reproduction

In i3, try using dual_kawase blur with glx backend.

Expected behavior

According to the README.md here at this fork, dual_kawase blur "only works with --experimental-backends and --backend glx". However, with glx set either at runtime through --backend or in the picom.conf config file, there is zero blur. Transparency still works, so picom itself does in fact launch, but there's no blur whatsoever.

Current Behavior & Other details

With --experimental-backends, dual_kawase DOES in fact "work," but there are so many glitches and artifacts and just plain ugliness, that it's unusable. Here are a couple examples, one is of a terminal, and another is of this very window I'm currently typing in:

Pretty much every window that doesn't have focus looks like this, and I've tried killing and restarting it multiple times. So I wanted to try glx as the backend to see if that helped. The glitches go away, but there's zero blur.

Blur appears to overlay on top of the original

Platform: Arch Linux, Linux kernel 5.5.8

GPU, drivers, and screen setup: AMD Radeon RX 480, mesa 19.3.4-2, two 1920x1080 monitors configured side-by-side with xrandr

Compton version: picom wgit-e0149 (latest build from the feature/dual_kawase branch)

Compton configuration: https://pastebin.com/Rw2h1cHF

Steps of reproduction

Launch picom with --experimental-backends, blur-background enabled, the blur method set to "dual_kawase", and the blur strength set to 5.0 or higher. This issue also occurs with box and gaussian methods and is visible with high enough strengths/deviations.

Expected behavior

This should blur the background entirely, similar to how it works with blur strength set to 2.0 but more intense.

Current Behavior & Other details

The blur effect appears to overlay on top of the original background giving it a sort of "glowing" effect as shown here. As the blur strength increases, this glow effect becomes more apparent.

I've tested this on Openbox and XFCE and they both have this issue.

Please rebase feature/dual_kawase against yshui/picom#next

Some Arch users are relying on this package, which rebases your feature branch against upstream head before building. https://aur.archlinux.org/packages/picom-tryone-git/
Until recently this has been fine, but this change yshui/picom@0fa0c35 is causing a merge conflict in the documentation.

If you'd rather not, I can open a PR to merge in upstream changes, but I think a rebase would be cleaner

Mpv blur issue

Platform: Arch linux

GPU, drivers, : NVidia GTX 970, nvidia-drivers 415.27

Compton version: compton-tryone-git 0.1_beta2.95.g241bbc5-1

Compton configuration:https://pastebin.com/WFzUs83L

Steps of reproduction

Launching mpv and playing videos.

Expected behavior

No transparency should be present.

Current Behavior & Other details

There is a transparent border on upper mpv window .
I have tried using opaque exclude rule but didn't work .

exclude screenshot tool from blur

I really like this compositor so far, as it finally allows me to achieve kawase blur, but I'm having a small issue where the screenshot tool also gets blurred when I launch it. I am aware of the blur_background_exclude option, but I'm not quite sure what attributes to pass it since I don't know what the WM_class of maim is, or if it even has one. I've tried both maim and Maim. I've also tried all the possible values for window_type.

Problem Description

Platform: Arch Linux with i3-gaps

GPU, drivers, and screen setup: Nvidia 1070Ti, dual monitor

Compton version: beta2-95-g241bbc5-2018-02-22

Compton configuration: see bottom of post

Steps of reproduction

Start the screenshot tool (in my case maim) with compton running.

Expected behavior

The screenshot selection does not get all blurred

Current Behavior & Other details

The entire screen is blurred when selecting region for screenshot. The screenshotted image still looks fine, however.

config:

blur-background=true;

backend = "glx";

blur-method = "kawase";

blur-strength = 10;

opacity-rule = [
    "85: class_g = 'Termite'",
    "85: class_g = 'discord'"
];

Update

I was able to get the effect I want by doing blur_background_exclude = "!(class_g = 'Termite' || <other things I want blurred>)", but would still like know if there's a way to specifically target maim.

--blur-strength do not change if value is changed.

Is just me or I not Understanding how this works?

Changing the value of --blur-strength to 50 per say should change the blur effect?

Heavy lags when mpv plays a video even with everything disabled

I am on the improved_fbo branch and when mpv plays a video or games are running the screen lags heavily when I drag something or resize a window. I put mpv into shadow-exclude, blur-background-exclude, focus-exclude, opacity-exclude and fade-exclude yet it did not change anything. Since the lags only occur while mpv is actually playing a video (not when it is paused, regardless how busy the screen is) it is rather obvious.
I am on Gentoo, Nvidia-415.27, and have tried it with an empty compton.conf.

This applies to both xrender and glx. Playing a video in Firefox does not make the screen lag.

Make branch `feature/dual_kawase` its own repo

It's a fork of picom, not compton, so I feel like that should be in its own repo, which is forked from yshui/picom instead of chjj/compton.

Edges preserving

Platform: Arch linux

GPU, drivers, and screen setup: Intel UHD Graphics 620, mesa 19.3.1-1, laptop screen and monitors configured side-by-side with xrandr (works the same with laptop screen only)

Compton version: bgit-f92eb from aur repo

Compton configuration: Written below

Steps of reproduction

Install picom from the aur repo, use dual_kawase blur method

Expected behavior

For some reason I can clearly see the edges of objects. I think that that should not be the case with blurring. Is that a bug or intended behavior?

Current Behavior & Other details

{
  method = "dual_kawase";
  strength = 20;
};

{
  method = "dual_kawase";
  strength = 1;
};

{
  method = "box";
  size = 20;
  deviation = 20.0;
};

"focused" and "!focused" reversed

Platform: Arch 5.4.14 amd64

Drivers: mesa, xf86-video-intel

WM: i3-gaps

Compton version: vgit-e0149 (picom-tryone latest)

Compton configuration: https://pastebin.com/AaHv0vp5

Steps of reproduction

In opacity-rule, the programs are considered focused when they are not, and considered not focused when they are.

opacity-rule = [
  "55:class_g = 'Termite' && focused",
  "85:class_g = 'Termite' && !focused",
  "75:class_g = 'code-oss' && focused",
  "90:class_g = 'code-oss' && !focused"
];

Therefore, I gave higher opacity to non focused programs, and lower opacity to focused programs.

Expected behavior

Focused programs should be focused, and non focused programs shouldn't. When using compton before, I didn't face this problem.

Current Behavior & Other details

I use --experimental-backend, but the issue exists also without the flag.

Contributing .deb package to apt repository?

Heya @tryone144 ! Thanks for sharing your fork of compton - I'm really loving it. I'll admit that it was quite the challenge to find the apt packages containing the deps I needed. So in order to save other Debian/Ubuntu users from the pain that I had to go through, I thought I'd contribute by putting together a nifty .deb package that compiles it easily for them.

Prebuilt binaries might work for other people too, but I'm not totally sure. I guess there's not really much I can ask you, other than for your permission.

"unrecognized option '--blur-strength'"

Platform: Example: Rasbian Buster arm64

GPU, drivers, and screen setup: Raspberry Pi

Compton version: vgit-f92eb

Compton configuration: Irrelevent since I'm running from commandline, but here it is anyways

Steps of reproduction

/usr/local/bin/compton  --experimental-backends --backend glx --blur-method dual_kawase --blur-strength 12

Expected behavior

I expected the background to be blurred like how the master branch is when using blur-strength=12 and blur-method=kawase. But hopefully with better performance, given how badly my Raspberry Pi 4b chokes

Current Behavior & Other details