flathub / org.wezfurlong.wezterm

https://flathub.org/apps/details/org.wezfurlong.wezterm
4 stars 2 forks source link

wl_surface@71: error 2: Buffer size (12x1081) must be an integer multiple of the buffer_scale (2). #15

Closed almereyda closed 11 months ago

almereyda commented 11 months ago

The .desktop file that comes with this package comes with an execution command, which crashes wezterm in wl_surface.

$ rg --pcre2 '(?<=^Exec=).*$' -o /var/lib/flatpak/exports/share/applications/org.wezfurlong.wezterm.desktop
7:/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=wezterm org.wezfurlong.wezterm start --cwd .
$ /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=wezterm org.wezfurlong.wezterm start --cwd .
wl_surface@71: error 2: Buffer size (12x1081) must be an integer multiple of the buffer_scale (2).
23:48:16.361  ERROR  wezterm_gui > running message loop: error during event_q.dispatch protocol_error=Some(ProtocolError { code: 2, object_id: 71, object_interface: "wl_surface", message: "" }): Protocol error (os error 71); terminating

Running the flatpak without any specified, and supposedly default parameters, does not invoke the crash:

$ flatpak run wezterm

After doing that a few times, running the earlier command also worked again, up until a point.

It then, for example, crashes when resizing with Super + LRUD

grafik

And then it doesn't do it again, for some time.

This happens when executed from kitty in zsh on GNOME 44 in Fedora 38 with onboard Intel graphics.

These seem related:

wez commented 11 months ago

I don't own this repo (the flathub org does, and I only have limited permissions here, sufficient to publish to flathub). I prefer to track issues in the main wezterm repo. This particular issue sounds like a duplicate of other wayland related issues. If you feel that this is a different, new issue, then please open a new issue in the wezterm repo. I'm going to close this one as I can't effectively track and triage issues from this particular flathub repo.

almereyda commented 11 months ago

Thanks for the explanation. I thought there would be a different maintainer from the community, who could pick up from here. I will file this again upstream, if it occurs again.