Bad image output when using kitty protocol with width and height specified

[CarterLi]

What Operating System(s) are you seeing this problem on?

Linux Wayland

Which Wayland compositor or X11 Window manager(s) are you using?

Mutter

WezTerm version

20230828-220414-99c96139

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

Yes, and I updated the version box above to show the version of the nightly that I tried

Describe the bug

To Reproduce

echo -e "\e_Ga=T,f=100,t=f,c=20,r=10;$(realpath ./OpenSuse.png | tr -d '\n' | base64)\e\\"

Image used:

Configuration

no config

Expected Behavior

Works like kitty

Logs

No response

Anything else?

Specifying width and height does work fine with iterm image protocol

[CarterLi]

Another issue: if you display an image file multiple times, the next image hides the previous one.

EDIT: Found #3918

[wez]

This should be resolved now in main.

It typically takes about an hour before commits are available as nightly builds for all platforms. Linux builds are the fastest to build and are often available within about 20 minutes. Windows and macOS builds take a bit longer.

Please take a few moments to try out the fix and let me know how that works out. You can find the nightly downloads for your system in the wezterm installation docs.

If you prefer to use packages provided by your distribution or package manager of choice and don't want to replace that with a nightly download, keep in mind that you can download portable packages (eg: a .dmg file on macOS, a .zip file on Windows and an .AppImage file on Linux) that can be run without permanently installing or replacing an existing package, and can then simply be deleted once you no longer need them.

If you are eager and can build from source then you may be able to try this out more quickly.

[CarterLi]

I can confirm the fix. Thanks.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.