Gentoo Forums :: View topic - freeze with picom (not solved)

freeze with picom (not solved)

View unanswered posts
View posts from last 24 hours

Gentoo Forums Forum Index

Other Things Gentoo

View previous topic :: View next topic

Author

Message

tom2374
n00b
n00b

Joined: 10 May 2025
Posts: 24

Posted: Sun Jun 08, 2025 2:05 pm Post subject: freeze with picom (not solved)

i use dwm, no matter what fork I use, animations still freeze sometimes, I thought it was a driver issue, I have AMD, but it is already installed and I didn't compile the kernel, my laptop should easily handle such animations, what could be the problem? Last edited by tom2374 on Tue Jun 10, 2025 4:10 am; edited 1 time in total

yaslam
Tux's lil' helper

Joined: 08 May 2024
Posts: 87
Location: Scotland, UK

Posted: Mon Jun 09, 2025 10:44 am Post subject: Re: freeze with picom

tom2374 wrote:

i use dwm, no matter what fork I use, animations still freeze sometimes, I thought it was a driver issue, I have AMD, but it is already installed and I didn't compile the kernel, my laptop should easily handle such animations, what could be the problem?

Hi, could you post your picom config file and laptop specs?
I use picom also on a desktop PC with an AMD GPU and I get no such issues. I also use picom on my laptop which uses a quite old Intel IGPU (i5 3210m, Intel HD Graphics 4000) and the animations are smooth on there too.
_________________
CPU: 6-core AMD Ryzen 5 5600 (-MT MCP-) speed/min/max: 2363/550/4468 MHz
Kernel: 6.12.21-gentoo-yaslam x86_64 Up: 4h 39m Mem: 6.64/31.27 GiB (21.2%)
Storage: 2.72 TiB (83.4% used) Procs: 400 Shell: fish inxi: 3.3.35

tom2374
n00b
n00b

Joined: 10 May 2025
Posts: 24

Posted: Mon Jun 09, 2025 11:39 am Post subject:

hi, this picom.conf

Code:

#active-opacity = 0.8;
#################################
# Animations #
#################################
# requires https://github.com/jonaburg/picom
# (These are also the default values)
transition-length = 3000
transition-pow-x = 0.1
transition-pow-y = 0.1
transition-pow-w = 0.1
transition-pow-h = 0.1
size-transition = true
transition-exclude = [
#"class_g = 'TelegramDesktop'",
]

#################################
# Corners #
#################################
# requires: https://github.com/sdhand/compton or https://github.com/jonaburg/picom
corner-radius = 10;
rounded-corners-exclude = [
#"window_type = 'normal'",
"class_g = 'awesome'",
"class_g = 'URxvt'",
"class_g = 'XTerm'",
"class_g = 'Alacritty'",
"class_g = 'Polybar'",
"class_g = 'code-oss'",
#"class_g = 'TelegramDesktop'",
"class_g = 'Thunderbird'"
];
round-borders = 1;
round-borders-exclude = [
#"class_g = 'TelegramDesktop'",
];

#################################
# 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.
#
# shadow = false
shadow = false;

# The blur radius for shadows, in pixels. (defaults to 12)
# shadow-radius = 12
shadow-radius = 7;

# The opacity of shadows. (0.0 - 1.0, defaults to 0.75)
# shadow-opacity = .75

# The left offset for shadows, in pixels. (defaults to -15)
# shadow-offset-x = -15
shadow-offset-x = -7;

# The top offset for shadows, in pixels. (defaults to -15)
# shadow-offset-y = -15
shadow-offset-y = -7;

# Avoid drawing shadows on dock/panel windows. This option is deprecated,
# you should use the *wintypes* option in your config file instead.
#
# no-dock-shadow = false

# Don't draw shadows on drag-and-drop windows. This option is deprecated,
# you should use the *wintypes* option in your config file instead.
#
# no-dnd-shadow = false

# Red color value of shadow (0.0 - 1.0, defaults to 0).
# shadow-red = 0

# Green color value of shadow (0.0 - 1.0, defaults to 0).
# shadow-green = 0

# Blue color value of shadow (0.0 - 1.0, defaults to 0).
# shadow-blue = 0

# 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.
#
# shadow-ignore-shaped = ''

# Specify a list of conditions of windows that should have no shadow.
#
# examples:
# shadow-exclude = "n:e:Notification";
#
# shadow-exclude = []
shadow-exclude = [
"name = 'Notification'",
"class_g = 'Conky'",
"class_g ?= 'Notify-osd'",
"class_g = 'Cairo-clock'",
"class_g = 'slop'",
"class_g = 'Polybar'",
"_GTK_FRAME_EXTENTS@:c"
];

# 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.
#
# shadow-exclude-reg = ""

# Crop shadow of a window fully on a particular Xinerama screen to the screen.
# xinerama-shadow-crop = false

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

# Fade windows in/out when opening/closing and when opacity changes,
# unless no-fading-openclose is used.
# fading = false
fading = true;

# Opacity change between steps while fading in. (0.01 - 1.0, defaults to 0.028)
# fade-in-step = 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
fade-out-step = 0.03;

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

# Specify a list of conditions of windows that should not be faded.
# don't need this, we disable fading for all normal windows with wintypes: {}
fade-exclude = [
"class_g = 'slop'" # maim
]

# 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 inactive windows. (0.1 - 1.0, defaults to 1.0)

# Opacity of window titlebars and borders. (0.1 - 1.0, disabled by default)
# frame-opacity = 1.0
frame-opacity = 0.7;
# Default opacity for dropdown menus and popup menus. (0.0 - 1.0, defaults to 1.0)
# menu-opacity = 1.0
# menu-opacity is depreciated use dropdown-menu and popup-menu instead.

#If using these 2 below change their values in line 510 & 511 aswell
popup_menu = { opacity = 0.8; }
dropdown_menu = { opacity = 0.8; }

# Let inactive opacity set by -i override the '_NET_WM_OPACITY' values of windows.
# inactive-opacity-override = true
#inactive-opacity-override = true;

# Default opacity for active windows. (0.0 - 1.0, defaults to 1.0)
inactive-opacity = 0.7;
active-opacity = 0.7;
mark-wmwin-focused = false;
mark-ovredir-focused= false;
# Dim inactive windows. (0.0 - 1.0, defaults to 0.0)
#inactive-dim = 0.5;

# Specify a list of conditions of windows that should always be considered focused.
# focus-exclude = []
focus-exclude = [
"class_g = 'Cairo-clock'",
"class_g = 'Bar'", # lemonbar
"class_g = 'slop'" # maim
];

# Use fixed inactive dim value, instead of adjusting according to window opacity.
# inactive-dim-fixed = 1.0

# 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.
# example:
# opacity-rule = [ "80:class_g = 'URxvt'" ];
#
# opacity-rule = []
opacity-rule = [
"100:class_g = 'Thunderbird'",
];

#################################
# Background-Blurring #
#################################

# Parameters for background blurring, see the *BLUR* section for more information.
# blur-method =
# blur-size = 12
#
# blur-deviation = false

# 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 = true;

# 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-frame = false;

# Use fixed blur strength rather than adjusting according to window opacity.
# 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";
#
# blur-kern = ''
# blur-kern = "3x3box";

blur: {
# requires: https://github.com/ibhagwan/picom
method = "kawase";
#method = "kernel";
strength = 7;
# deviation = 1.0;
# kernel = "11x11gaussian";
background = false;
background-frame = false;
background-fixed = false;
kern = "3x3box";
}

# Exclude conditions for background blur.
blur-background-exclude = [
#"window_type = 'dock'",
#"window_type = 'desktop'",
#"class_g = 'URxvt'",
#
# prevents picom from blurring the background
# when taking selection screenshot with `main`
# https://github.com/naelstrof/maim/issues/130
"class_g = 'slop'",
"_GTK_FRAME_EXTENTS@:c"
];

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

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

# Specify the backend to use: `xrender`, `glx`, or `xr_glx_hybrid`.
# `xrender` is the default one.
#
experimental-backends = true;
backend = "glx";
#backend = "xrender";

# Enable/disable VSync.
# vsync = false
vsync = true

# Enable remote control via D-Bus. See the *D-BUS API* section below for more details.
# dbus = false

# Try to detect WM windows (a non-override-redirect window with no
# child that has 'WM_STATE') and mark them as active.
#
# mark-wmwin-focused = false
mark-wmwin-focused = true;

# Mark override-redirect windows that doesn't have a child window with 'WM_STATE' focused.
# mark-ovredir-focused = false

# Try to detect windows with rounded corners and don't consider them
# shaped windows. The accuracy is not very high, unfortunately.
#
# detect-rounded-corners = false
detect-rounded-corners = true;

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

# Specify refresh rate of the screen. If not specified or 0, picom will
# try detecting this with X RandR extension.
#
# refresh-rate = 60
refresh-rate = 0

# Limit picom to repaint at most once every 1 / 'refresh_rate' second to
# boost performance. This should not be used with
# vsync drm/opengl/opengl-oml
# as they essentially does sw-opti's job already,
# unless you wish to specify a lower refresh rate than the actual value.
#
# sw-opti =

# 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.
#
# 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. paint-on-overlay may make the flickering less obvious.
#
# unredir-if-possible = false

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

# Conditions of windows that shouldn't be considered full-screen for unredirecting screen.
# unredir-if-possible-exclude = []

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

# Use 'WM_CLIENT_LEADER' to group windows, and consider windows in the same
# group focused at the same time. 'WM_TRANSIENT_FOR' has higher priority if
# detect-transient is enabled, too.
#
# detect-client-leader = false
detect-client-leader = true

# 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.
#
# resize-damage = 1

# Specify a list of conditions of windows that should be painted with inverted color.
# Resource-hogging, and is not well tested.
#
# invert-color-include = []

# 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-stencil = false

# 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.
#
# glx-no-rebind-pixmap = false

# 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.
# The opposing option is use-damage
#
# no-use-damage = false
#use-damage = true (Causing Weird Black semi opaque rectangles when terminal is opened)
#Changing use-damage to false fixes the problem
use-damage = false

# 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.
#
# xrender-sync-fence = false

# 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.
#
# glx-fshader-win = ''

# Force all windows to be painted with blending. Useful if you
# have a glx-fshader-win that could turn opaque pixels transparent.
#
# 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.
#
# 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)
#
# max-brightness = 1.0

# Make transparent windows clip other windows like non-transparent windows do,
# instead of blending on top of them.
#
# transparent-clipping = false

# 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-level = "debug"
log-level = "info";

# 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'

# Show all X errors (for debugging)
# show-all-xerrors = false

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

# Window type settings
#
# 'WINDOW_TYPE' is one of the 15 window types defined in EWMH standard:
# "unknown", "desktop", "dock", "toolbar", "menu", "utility",
# "splash", "dialog", "normal", "dropdown_menu", "popup_menu",
# "tooltip", "notification", "combo", and "dnd".
#
# Following per window-type options are available: ::
#
# fade, shadow:::
# Controls window-type-specific shadow and fade settings.
#
# opacity:::
# Controls default opacity of the window type.
#
# focus:::
# Controls whether the window of this type is to be always considered focused.
# (By default, all window types except "normal" and "dialog" has this on.)
#
# full-shadow:::
# Controls whether shadow is drawn under the parts of the window that you
# normally won't be able to see. Useful when the window has parts of it
# transparent, and you want shadows in those areas.
#
# redir-ignore:::
# Controls whether this type of windows should cause screen to become
# redirected again after been unredirected. If you have unredir-if-possible
# set, and doesn't want certain window to cause unnecessary screen redirection,
# you can set this to `true`.
#
wintypes:
{
normal = { fade = false; shadow = false; }
tooltip = { fade = true; shadow = true; opacity = 0.75; focus = true; full-shadow = false; };
dock = { shadow = false; }
dnd = { shadow = false; }
popup_menu = { opacity = 0.8; }
dropdown_menu = { opacity = 0.8; }
};

for activation picom I use

Code:

picom -b --animations --animation-window-mass 0.5 --animation-for-open-window zoom --animation-stiffness-tag-change 350 --backend glx &

this laptop specs

Code:

Digma EVE A5820 Ryzen 3 3200U 16Gb SSD512Gb AMD Radeon Vega 3 15.6" IPS FHD (1920x1080) Windows 11 Pro black WiFi BT Cam 4500mAh (DN15R3-ADXW01)

Thank you for helping

yaslam
Tux's lil' helper

Joined: 08 May 2024
Posts: 87
Location: Scotland, UK

Posted: Mon Jun 09, 2025 2:18 pm Post subject:

I tried your configuration on my laptop, and it runs very smoothly.

You should fix these warnings that I seen when running your config:

Code:

[ 09/06/25 15:05:02.135 parse_config_libconfig WARN ] The refresh-rate option has been deprecated. Please remove it from your configuration file. If you encounter any problems without this feature, please feel free to open a bug report
[ 09/06/25 15:05:02.135 c2_parse_target WARN ] Type specifier is deprecated. Type "c" specified on target "_GTK_FRAME_EXTENTS" will be ignored, you can remove it.
[ 09/06/25 15:05:02.135 c2_parse_target WARN ] Type specifier is deprecated. Type "c" specified on target "_GTK_FRAME_EXTENTS" will be ignored, you can remove it.
[ 09/06/25 15:05:02.135 parse_config_libconfig WARN ] Invalid blur method kawase, ignoring.

Also, when I ran the command you gave to start picom, I got invalid argument errors. I am using this version of picom: x11-misc/picom-12.5::gentoo, you may want to check if you are using the same version as me. You can also try changing the backend from glx to xrender or xr_glx_hybrid, it could help, but depends on your hardware. A newer Ryzen like yours should be able to handle the glx backend, but it doesn't hurt to try the others.
_________________
CPU: 6-core AMD Ryzen 5 5600 (-MT MCP-) speed/min/max: 2363/550/4468 MHz
Kernel: 6.12.21-gentoo-yaslam x86_64 Up: 4h 39m Mem: 6.64/31.27 GiB (21.2%)
Storage: 2.72 TiB (83.4% used) Procs: 400 Shell: fish inxi: 3.3.35

tom2374
n00b
n00b

Joined: 10 May 2025
Posts: 24

Posted: Mon Jun 09, 2025 2:56 pm Post subject:

I have already tried to change glx to xrender or xr_glx_hybrid, it does not work. And these errors do not affect the work of the pikom ( I fixed them but it didn't help.). I must say that it is mainly the zoom animation that freezes, this happens once every 8-10 openings, and your animations are always smooth or do they sometimes hang?

yaslam
Tux's lil' helper

Joined: 08 May 2024
Posts: 87
Location: Scotland, UK

Posted: Mon Jun 09, 2025 4:11 pm Post subject:

tom2374 wrote:

I have already tried to change glx to xrender or xr_glx_hybrid, it does not work. And these errors do not affect the work of the pikom ( I fixed them but it didn't help.). I must say that it is mainly the zoom animation that freezes, this happens once every 8-10 openings, and your animations are always smooth or do they sometimes hang?

I have just retried your configuration on my laptop and even with multiple windows open, moving the windows around etc.. I cannot see any freezing of the animations.

Could you please post the version of picom you are using?
_________________
CPU: 6-core AMD Ryzen 5 5600 (-MT MCP-) speed/min/max: 2363/550/4468 MHz
Kernel: 6.12.21-gentoo-yaslam x86_64 Up: 4h 39m Mem: 6.64/31.27 GiB (21.2%)
Storage: 2.72 TiB (83.4% used) Procs: 400 Shell: fish inxi: 3.3.35

tom2374
n00b
n00b

Joined: 10 May 2025
Posts: 24

Posted: Mon Jun 09, 2025 4:21 pm Post subject:

picom version:

Code:

[I] x11-misc/picom
Available versions: 12.5^t **9999*l^t {dbus +doc +drm opengl pcre test}
Installed versions: 12.5^t(01:34:02 PM 05/17/2025)(dbus doc drm opengl pcre -test)
Homepage: https://github.com/yshui/picom
Description: A lightweight compositor for X11 (previously a compton fork)

which fork picom you use?

yaslam
Tux's lil' helper

Joined: 08 May 2024
Posts: 87
Location: Scotland, UK

Posted: Mon Jun 09, 2025 4:30 pm Post subject:

tom2374 wrote:

picom version:

Code:

which fork picom you use?

No fork, I am using the official picom in the ::gentoo repository.
_________________
CPU: 6-core AMD Ryzen 5 5600 (-MT MCP-) speed/min/max: 2363/550/4468 MHz
Kernel: 6.12.21-gentoo-yaslam x86_64 Up: 4h 39m Mem: 6.64/31.27 GiB (21.2%)
Storage: 2.72 TiB (83.4% used) Procs: 400 Shell: fish inxi: 3.3.35

tom2374
n00b
n00b

Joined: 10 May 2025
Posts: 24

Posted: Mon Jun 09, 2025 4:34 pm Post subject:

so did you understand something from the version or is everything ok with it? I think I understood what can be done, once I had a peak using 2.5% of the CPU and if it uses the CPU like that then the animations don't freeze, however usually it reduces the CPU consumption which is why the animations freeze again, do you know the command so that the process always uses 2.5% of the CPU?

yaslam
Tux's lil' helper

Joined: 08 May 2024
Posts: 87
Location: Scotland, UK

Posted: Mon Jun 09, 2025 4:40 pm Post subject:

tom2374 wrote:

so did you understand something from the version or is everything ok with it?

As far as I am concerned, I have used this version on both my desktop and laptop for months now, and I do not have any issues.

tom2374 wrote:

I think I understood what can be done, once I had a peak using 2.5% of the CPU and if it uses the CPU like that then the animations don't freeze, however usually it reduces the CPU consumption which is why the animations freeze again, do you know the command so that the process always uses 2.5% of the CPU?

I don't think that is possible.

To rule out the configuration, you could perhaps try my picom configuration and see if any freezing occurs: https://paste.leenucks.xyz/?8eab93077b69e4fa#vdja26VdGnKyy1MqRBUTcbqtQQk8FfvnHimS8AZVHEM
_________________
CPU: 6-core AMD Ryzen 5 5600 (-MT MCP-) speed/min/max: 2363/550/4468 MHz
Kernel: 6.12.21-gentoo-yaslam x86_64 Up: 4h 39m Mem: 6.64/31.27 GiB (21.2%)
Storage: 2.72 TiB (83.4% used) Procs: 400 Shell: fish inxi: 3.3.35

tom2374
n00b
n00b

Joined: 10 May 2025
Posts: 24

Posted: Mon Jun 09, 2025 4:55 pm Post subject:

I used your config, but apparently there were only more freezes and sometimes animations stopped playing altogether when changing work areas

tom2374
n00b
n00b

Joined: 10 May 2025
Posts: 24

Posted: Tue Jun 10, 2025 5:06 am Post subject:

thank you, thanks to you I realized that the problem was in the config, it was necessary to change vsync = true to vsync = false . the zoom animation now does not freeze at all, but the animation of moving between workspaces now looks jerky and not good, maybe someone knows how to apply this setting only to zoom or is there some similar setting (I doubt that at least something like this exists, but suddenly)

yaslam
Tux's lil' helper

Joined: 08 May 2024
Posts: 87
Location: Scotland, UK

Posted: Tue Jun 10, 2025 10:08 am Post subject:

tom2374 wrote:

thank you, thanks to you I realized that the problem was in the config, it was necessary to change vsync = true to vsync = false .

Your welcome.

tom2374 wrote:

the zoom animation now does not freeze at all, but the animation of moving between workspaces now looks jerky and not good, maybe someone knows how to apply this setting only to zoom or is there some similar setting (I doubt that at least something like this exists, but suddenly)

The vsync option can only be set globally and not per-animation. I am not aware of any similar settings.
_________________
CPU: 6-core AMD Ryzen 5 5600 (-MT MCP-) speed/min/max: 2363/550/4468 MHz
Kernel: 6.12.21-gentoo-yaslam x86_64 Up: 4h 39m Mem: 6.64/31.27 GiB (21.2%)
Storage: 2.72 TiB (83.4% used) Procs: 400 Shell: fish inxi: 3.3.35

tom2374
n00b
n00b

Joined: 10 May 2025
Posts: 24

Posted: Tue Jun 10, 2025 11:17 am Post subject:

ok

Display posts from previous:

	Gentoo Forums Forum Index Other Things Gentoo	All times are GMT
Page 1 of 1

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Copyright 2001-2025 Gentoo Foundation, Inc. Designed by Kyle Manna © 2003; Style derived from original subSilver theme. | Hosting by Gossamer Threads Inc. © | Powered by phpBB 2.0.23-gentoo-p11 © 2001, 2002 phpBB Group
Privacy Policy