monitor=,3840x2160@60,auto,4
bind=ALT,RETURN,exec,/usr/bin/systemd-run --user --collect --service-type=exec --slice=kitty --setenv=WAYLAND_DISPLAY=$WAYLAND_DISPLAY /usr/bin/kitty --single-instance --instance-group=kitty
- Expected outcome
kitty pops
- Noted outcome
Aug 10 10:08:50 asus systemd[852]: Starting /usr/bin/kitty --single-instance --instance-group=kitty...
Aug 10 10:08:50 asus systemd[852]: Started /usr/bin/kitty --single-instance --instance-group=kitty.
Aug 10 10:08:50 asus Hyprland[1772]: Set keyboard focus to surface 1e6384c0, with wind
Aug 10 10:08:50 asus Hyprland[2025]: Running as unit: run-r5cc54e36155a4a64a3795a9bdbf8a33d.service
Aug 10 10:08:50 asus Hyprland[1772]: 00:00:47.799 [INFO] [wayland] error in client communication (pid 1789)
Aug 10 10:08:50 asus kitty[1789]: wl_surface@34: error 2: Buffer size (958x538) is not divisible by scale (4)
Aug 10 10:08:50 asus Hyprland[1772]: ow name: zsh
Aug 10 10:08:50 asus Hyprland[1772]: Enabling TextInput on no IME!
Aug 10 10:08:50 asus Hyprland[1772]: Committing TextInput on no IME!
Aug 10 10:08:50 asus Hyprland[1772]: Committing TextInput on no IME!
Aug 10 10:08:50 asus Hyprland[1772]: Committing TextInput on no IME!
Aug 10 10:08:50 asus Hyprland[1772]: Destroying workspace ID 1
why are you scaling up 4 times, what’s wrong with you
This error now happens nearly every time
imvis opened. Something like this:Since it’s not a cursor surface, this still triggers the bug despite the existing workaround in wlr_compositor.c. One could add a wlroots patch that just avoids that if entirely, but obviously it’d be better to get this fixed in wlroots itself.
I’m not sure if other apps are affected.
Same issue appears right after upgrading Hyprland from 0.35.0-2 to 0.37.0-1. 0.36.0 is not tested because it was not packaged in Archlinux official repos. Maybe will test it later.
Upd 24.04.04: Git bisect’ed from v0.35.0 to v0.37.0, the following commit seems to be the first bad commit that produced
imv’s crash.I am experiencing the same issue. In my case, I tracked it down to the fact that kitty stores a cached window-size:
And this window size does not take into account the scale factor. If I remove that file, kitty launches fine. I’m also going to update the linked issue with this information and then see if I can configure kitty to avoid this behavior.
closing per https://github.com/hyprwm/wlroots-hyprland/pull/9
since hyprland has now forked wlroots, can we apply the patch that @TheSunCat mentioned downstream? @vaxerski i don’t think it will be fixed upstream at wlroots since wlroots would rather report this as an error, because it is indeed a violation of protocols from the app’s part as i understand it see discussions at https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/733#note_1738935 and https://gitlab.freedesktop.org/wayland/wayland/-/issues/194 however, since many apps are having this problem (kitty, imv, wezterm to name a few), it may be worth it to patch a workaround here for hyprland, provided that this patch doesn’t break other things, until these apps have fixed it. the patch would simply be reverting this commit: https://gitlab.freedesktop.org/wlroots/wlroots/-/commit/18595000f3a21502fd60bf213122859cc348f9af
in the case of wlroots, in wlroots. Well, unless a compositor ditches the wlroots’ cursor impl
This needs to be fixed in the compositor and more generally in the wayland cursor library. applications can do nothing about it. The commit you linked to has nothing to do with this.
I can second this. I have two monitors: the 2k monitor (at 1.0 scaling) doesn’t suffer from this problem, but when I put any work on the native laptop screen (at 1.2 scaling), lots of applications would crash, including pop-up dialogs from dolphin.
This crash happens often but not consistently with:
As of recently I have noticed it happening more often. Is there anything I can do to help get this fixed or at least work around it for now? It is difficult to use Hyprland knowing many programs can and will instantly crash and lose unsaved work. This does not happen in Sway with the same scaling options.
Based on the information provided in the kitty issue, this may well be an issue with hyprland and not in kitty itself.
Set your kitty config to be a prime number, then launch kitty with the attempt to use that resolution. It tries to resize to that number multiplied by the scale and it fails with this Wayland error: