Protocol error 2 on object wl_surface@...

[christo-auer]

Hey, thanks for this great project!

I am using wpaperd 1.3.0 on nix with a pretty standard configuration:

[any]
path = "..."

[default]
duration = "15m"
mode = "center"

[default.transition.directional-wipe]
direction = [1, -0.7]
smoothness = 0.5

I am running wpaperd on sway (swayfx version 0.5.3 (based on sway 1.11.0)). Whenever wpaperd runs it consumes 100% CPU and permanently spits out:

Protocol error 2 on object wl_surface@...

After a reboot, it works for some time until I resume from sleep. Any ideas?

[yegorius]

Same problem here, but for me it doesn't work even after a reboot. Running on Arch Linux (CachyOS) sway 1.12-3.1 with config:

[default]
duration = "30m"
mode = "center"
group = 1

[any]
path = "$HOME/Pictures/Wallpapers"
recursive = false

[christo-auer]

Yes, I couldn't get it to work either: CPU consumption is always 100%. I reverted to a static wallpaper (using stylix).

[mstoeckl]

The 100% CPU after a Wayland protocol error is probably caused by: Smithay/calloop-wayland-source#8 .

To determine what the original protocol error was, it may help to post the logs that are output when wpaperd is run with environment variable WAYLAND_DEBUG=1. (Minus the many repeating error messages.)

[thkoch2001]

I see "Protocol error 2" and 100% CPU regularly when docking my laptop and thus having 3 outputs. Restarting wpaperd however solves it for me. The log says:

wl_surface#24: error 2: Buffer size (1371x857) is not divisible by scale (2)
Protocol error 2 on object wl_surface@24

I try to tune my kanshi config now because I also believe that my use of scale and positioning might be responsible for some flickering at the screen margins.

[danyspin97]

Hello everyone! Can you please try with the git version and see if this bug has been fixed? Thank you1

[christo-auer]

Just compiled and tried the latest commit 483225, same error and 100% CPU when opening my laptop display:

Protocol error 2 on object wl_surface@22

Have to manually stop wpaperd

[yegorius]

Compiled git commit 483225a and still have 100% CPU.

[danyspin97]

Thanks for the feedback, I'll go back and try to fix this issue.