[SOLVED] Cairo Dock has black background after opening STK with Picom

miguel04685 · 2024-11-21 23:17:11

[miguel@archmiguel ~]$ cat ~/.config/picom/picom.conf
#################################
#             Shadows           #
#################################

# 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.
#
# Can be set per-window using rules.
#
# Default: false
shadow = false;

# The blur radius for shadows, in pixels.
#
# Default: 12
shadow-radius = 12;

# The opacity of shadows.
#
# Range: 0.0 - 1.0
# Default: 0.75
# shadow-opacity = .75

# The left offset for shadows, in pixels.
#
# Default: -15
shadow-offset-x = -15;

# The top offset for shadows, in pixels.
#
# Default: -15
shadow-offset-y = -15;

# Hex string color value of shadow. Formatted like "#RRGGBB", e.g. "#C0FFEE".
#
# Default: #000000
# shadow-color = "#000000"

# Crop shadow of a window fully on a particular monitor to that monitor. This is
# currently implemented using the X RandR extension.
#
# Default: false
# crop-shadow-to-monitor = false


#################################
#           Fading              #
#################################

# Fade windows in/out when opening/closing and when opacity changes,
# unless no-fading-openclose is used. Can be set per-window using rules.
#
# Default: false
fading = true;

# Opacity change between steps while fading in. (0.01 - 1.0, defaults to 0.028)
fade-in-step = 0.03;

# Opacity change between steps while fading out. (0.01 - 1.0, defaults to 0.03)
fade-out-step = 0.03;

# The time between steps in fade step, in milliseconds. (> 0, defaults to 10)
# fade-delta = 10

# Do not fade on window open/close.
# no-fading-openclose = false

# Do not fade destroyed ARGB windows with WM frame. Workaround of bugs in Openbox, Fluxbox, etc.
# no-fading-destroyed-argb = false


#################################
#   Transparency / Opacity      #
#################################

# Opacity of window titlebars and borders.
#
# Range: 0.1 - 1.0
# Default: 1.0 (disabled)

# Use fixed inactive dim value, instead of adjusting according to window opacity.
#
# Default: false
# inactive-dim-fixed = true

#################################
#           Corners             #
#################################

# Sets the radius of rounded window corners. When > 0, the compositor will
# round the corners of windows. Does not interact well with
# `transparent-clipping`.
#
# Default: 0 (disabled) 

#################################
#            Blur               #
#################################

# Parameters for background blurring, see BLUR section in the man page for more information.
# blur-method =
# blur-size = 12
#
# blur-deviation = false
#
# blur-strength = 5

# Blur background of semi-transparent / ARGB windows.
# Can be set per-window using rules.
#
# Default: false
# blur-background = false

# Blur background of windows when the window frame is not opaque.
# Implies:
#    blur-background
#
# Default: false
# blur-background-frame = false

# Use fixed blur strength rather than adjusting according to window opacity.
#
# Default: false
# blur-background-fixed = false


# Specify the blur convolution kernel, with the following format:
# example:
#   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";
# Can also be a pre-defined kernel, see the man page.
#
# Default: ""

#################################
#       General Settings        #
#################################

# Enable remote control via D-Bus. See the man page for more details.
#
# Default: false
# dbus = true

# Daemonize process. Fork to background after initialization. Causes issues with certain (badly-written) drivers.
# daemon = false

# Specify the backend to use: `xrender`, `glx`, or `egl`.
#
# Default: "xrender"
backend = "xrender"

# Use higher precision during rendering, and apply dither when presenting the
# rendered screen. Reduces banding artifacts, but may cause performance
# degradation. Only works with OpenGL.
dithered-present = false;

# Enable/disable VSync.
#
# Default: false
vsync = true;

# Try to detect windows with rounded corners and don't consider them
# shaped windows. The accuracy is not very high, unfortunately.
#
# Has nothing to do with `corner-radius`.
#
# Default: false
detect-rounded-corners = true;

# Detect '_NET_WM_WINDOW_OPACITY' on client windows, useful for window managers
# not passing '_NET_WM_WINDOW_OPACITY' of client windows to frame windows.
#
# Default: false
detect-client-opacity = true;

# Use EWMH '_NET_ACTIVE_WINDOW' to determine currently focused window,
# rather than listening to 'FocusIn'/'FocusOut' event. May be more accurate,
# provided that the WM supports it.
#
# Default: false
# use-ewmh-active-win = false

# 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.
#
# Default: false
unredir-if-possible = true

# Delay before unredirecting the window, in milliseconds.
#
# Default: 0.
# unredir-if-possible-delay = 0

# Use 'WM_TRANSIENT_FOR' to group windows, and consider windows
# in the same group focused at the same time.
#
# Default: false
detect-transient = true;

# 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.
#
# Default: false
detect-client-leader = true

# Use of damage information for rendering. This cause the only the part of the
# screen that has actually changed to be redrawn, instead of the whole screen
# every time. Should improve performance.
#
# Default: false
use-damage = true;

# Use X Sync fence to wait for the completion of rendering of other windows,
# before using their content to render the current screen.
#
# Required for explicit sync drivers, such as nvidia.
#
# Default: false
xrender-sync-fence = true

# GLX backend: Use specified GLSL fragment shader for rendering window
# contents. Read the man page for a detailed explanation of the interface.
#
# Can be set per-window using rules.
#
# window-shader-fg = "default"

# Force all windows to be painted with blending. Useful if you
# have a `window-shader-fg` that could turn opaque pixels transparent.
#
# Default: false
# force-win-blend = false

# Do not use EWMH to detect fullscreen windows.
# Reverts to checking if a window is fullscreen based only on its size and coordinates.
#
# Default: false
# no-ewmh-fullscreen = false

# 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 (disabled)
# max-brightness = 1.0

# Make transparent windows clip other windows like non-transparent windows do,
# instead of blending on top of them. e.g. placing a transparent window on top
# of another window will cut a "hole" in that window, and show the desktop background
# underneath.
#
# Default: false
#transparent-clipping = true

# Set the log level. Possible values are:
#  "trace", "debug", "info", "warn", "error"
# in increasing level of importance. Case insensitive.
# 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.
#
# Default: "warn"
# log-level = "warn";

# 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.
#
# log-file = "/path/to/your/log/file"

# Write process ID to a file.
# write-pid-path = "/path/to/your/log/file"

# Rule-based per-window options.
#
# See WINDOW RULES section in the man page for how these work.
rules: ({
  match = "window_type = 'tooltip'";
  fade = false;
  shadow = true;
  opacity = 0.75;
  full-shadow = false;
}, {
  match = "window_type = 'dock'    || "
          "window_type = 'desktop' || "
          "_GTK_FRAME_EXTENTS@";
  blur-background = false;
}, {
  match = "window_type != 'dock'";
  # shader = "my_shader.frag";
}, {
  match = "window_type = 'dock' || "
          "window_type = 'desktop'";
  corner-radius = 0;
}, {
  match = "name = 'Notification'   || "
          "class_g = 'Conky'       || "
          "class_g ?= 'Notify-osd' || "
          "class_g = 'Cairo-clock' || "
          "_GTK_FRAME_EXTENTS@";
  shadow = false;
})

# `@include` directive can be used to include additional configuration files.
# Relative paths are search either in the parent of this configuration file
# (when the configuration is loaded through a symlink, the symlink will be
# resolved first). Or in `$XDG_CONFIG_HOME/picom/include`.
#
# @include "extra.conf"
[miguel@archmiguel ~]$

Also, here is a video:
https://imgur.com/a/SDxdeWI

What I find weird is that this problem doesn't happen when using Xcompmgr compositor

Last edited by miguel04685 (2024-11-23 20:46:34)

seth · 2024-11-22 08:11:59

STK likely blocks the compositor, the game runs maximized but in windowed mode, the black bar is the uncomposited dock and its struts constrain the area of the maximized window.
The likely most desirable approach would be to run STK in fullscreen mode anyway?

miguel04685 · 2024-11-23 18:30:29

STK is already on Fullscreen mode, what I find weird is that on xcompmgr there are not any problems with the Cairo Dock while Picom has problems

seth · 2024-11-23 18:38:36

STK is already on Fullscreen mode

Then why is there a titlebar?

what I find weird is that on xcompmgr there are not any problems with the Cairo Dock while Picom has problems

https://man.archlinux.org/man/extra/picom/picom.1.en - see --unredir-if-possible
I'd assume STK runs into that somehow™

miguel04685 · 2024-11-23 18:42:45

I also have that flag enabled, you can see on the configuration file

miguel04685 · 2024-11-23 18:52:27

Well, I think it's better to switch back to Xcompmgr, I have just seen that Picom also gives me rendering problems with other programs.

seth · 2024-11-23 18:59:32

Yes, I saw that.
That's the point and key difference between xcompmgr and picom wrt. the perceived behavior.
Try to disable it.

The "odd" part would be if picom detects STK as fullscreen, but your WM doesn't.
Can you run

xprop

on STK?

miguel04685 · 2024-11-23 19:06:43

[miguel@archmiguel ~]$ xprop
_NET_WM_USER_TIME(CARDINAL) = 695143
_NET_WM_ICON_GEOMETRY(CARDINAL) = 248, 0, 200, 32
_NET_FRAME_EXTENTS(CARDINAL) = 2, 2, 32, 2
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_CLOSE, _NET_WM_ACTION_ABOVE, _NET_WM_ACTION_BELOW, _NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_MOVE, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_STICK
WM_STATE(WM_STATE):
		window state: Normal
		icon window: 0x389ca400
_NET_WM_DESKTOP(CARDINAL) = 0
_NET_WM_STATE(ATOM) = 
XdndAware(ATOM) = BITMAP
_NET_WM_NAME(UTF8_STRING) = "SuperTuxKart"
WM_NAME(STRING) = "SuperTuxKart"
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING
_NET_WM_BYPASS_COMPOSITOR(CARDINAL) = 1
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL
_NET_WM_PID(CARDINAL) = 1360
WM_LOCALE_NAME(STRING) = "C"
WM_CLASS(STRING) = "supertuxkart", "supertuxkart"
WM_HINTS(WM_HINTS):
		Client accepts input or input focus: True
		window id # of group leader: 0x1fe99240
WM_NORMAL_HINTS(WM_SIZE_HINTS):
		user specified location: 0, 16
		program specified minimum size: 1366 by 736
		program specified maximum size: 1366 by 736
WM_CLIENT_MACHINE(STRING) = "archmiguel"
_MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0x0, 0x1, 0x0, 0x0
[miguel@archmiguel ~]$

Do I need to do "xprop" command when using xcompmgr or when using Picom? Or it doesn't matter?

Last edited by miguel04685 (2024-11-23 19:10:05)

seth · 2024-11-23 19:13:38

Doesn't matter, what does is

_NET_WM_BYPASS_COMPOSITOR(CARDINAL) = 1
_NET_WM_STATE(ATOM) =

It bypassed the compositor and it's NOT "_NET_WM_STATE(ATOM) = _NET_WM_STATE_FULLSCREEN"
=> https://bbs.archlinux.org/viewtopic.php … 7#p2209797
You can scratch the "likely" etc. from there - it'S teh situation at hand.

miguel04685 · 2024-11-23 20:45:33

Wait, I have just found out that SuperTuxKart wasn't on fullscreen mode, sorry for saying that it was

miguel04685 · 2024-11-23 20:46:04

My problem has been solved, now the dock problem is gone

Arch Linux

#1 2024-11-21 23:17:11

[SOLVED] Cairo Dock has black background after opening STK with Picom

#2 2024-11-22 08:11:59

Re: [SOLVED] Cairo Dock has black background after opening STK with Picom

#3 2024-11-23 18:30:29

Re: [SOLVED] Cairo Dock has black background after opening STK with Picom

#4 2024-11-23 18:38:36

Re: [SOLVED] Cairo Dock has black background after opening STK with Picom

#5 2024-11-23 18:42:45

Re: [SOLVED] Cairo Dock has black background after opening STK with Picom

#6 2024-11-23 18:52:27

Re: [SOLVED] Cairo Dock has black background after opening STK with Picom

#7 2024-11-23 18:59:32

Re: [SOLVED] Cairo Dock has black background after opening STK with Picom

#8 2024-11-23 19:06:43

Re: [SOLVED] Cairo Dock has black background after opening STK with Picom

#9 2024-11-23 19:13:38

Re: [SOLVED] Cairo Dock has black background after opening STK with Picom

#10 2024-11-23 20:45:33

Re: [SOLVED] Cairo Dock has black background after opening STK with Picom

#11 2024-11-23 20:46:04

Re: [SOLVED] Cairo Dock has black background after opening STK with Picom

Board footer