0.32.0 release fails to start/open due to glfw error 65544

[xmers]

Describe the bug After the 0.32.0 release, kitty fails to open, either by clicking on the icon or attempting to execute it from another terminal.

To Reproduce

1. Upgrade to the new release
2. Double-clicking the kitty desktop icon produces no response.
3. From another terminal, running the kitty command, the below error is thrown.

Screenshots

~  kitty -v
kitty 0.32.0 created by Kovid Goyal

~  kitty
[destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 875713345
[019 14:14:27.520528] [glfw error 65544]: Wayland: fatal display error: Protocol error

~  kitty --debug-gl
Creating window at size: 1185x1234 and scale 1
GL version string: '3.1.0 NVIDIA 545.29.06' Detected version: 3.1
CSD: old.size: 0x0 new.size: 1185x1234 needs_update: 1 size_changed: 1 buffer_destroyed: 0
Created decoration buffers at scale: 1 vertical_height: 1270 horizontal_width: 1209
top-level configure event: size: 0x0 states: 
CSD: old.size: 1185x1234 new.size: 1185x1234 needs_update: 0 size_changed: 0 buffer_destroyed: 0
final window content size: 1185x1234 resized: 0
Setting window geometry in configure event: x=0 y=-24 1185x1258
CSD: old.size: 1185x1234 new.size: 1185x1234 needs_update: 1 size_changed: 0 buffer_destroyed: 1
Created decoration buffers at scale: 1 vertical_height: 1270 horizontal_width: 1209
CSD: old.size: 1185x1234 new.size: 1185x1234 needs_update: 0 size_changed: 0 buffer_destroyed: 0
Waiting for swap to commit: swap has happened
[destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 875713345
Calling wl_pointer_set_cursor in setCursorImage with surface: 0x555612e630c0
[019 14:16:24.934781] [glfw error 65544]: Wayland: fatal display error: Protocol error

Environment details

~  hostnamectl | egrep -i 'operating|kernel'
    Operating System: Fedora Linux 39 (Workstation Edition)
              Kernel: Linux 6.6.11-200.fc39.x86_64

~  kitty --config NONE
[destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 875713345
[019 14:27:59.356143] [glfw error 65544]: Wayland: fatal display error: Protocol error

Sys logs

Jan 19 14:33:29 gnome-shell[2383]: WL: error in client communication (pid 30227)
Jan 19 14:34:17 gnome-shell[2383]: WL: error in client communication (pid 31959)

[kovidgoyal]

This has nothing to do with kitty. It's an incompatibility between NVIDIA drivers and Wayland. Upstream bug report: https://github.com/NVIDIA/egl-wayland/issues/85 This bug is exposed in kitty 0.32 because now kitty explicitly asks for SRGB output buffers, to ensure color rendering is correct. See https://github.com/kovidgoyal/kitty/commit/97f5cad3352ee38588b8c5e81988e239bba58a64

Use linux_display_server x11 in kitty.conf to use XWayland or better yet, just switch back to X and be headache free.

Alternately, hold off updating kitty until the NVIDIA bug is fixed.

[solopasha]

Where did you install the package from? Does the crash happen with 0.31.0? I'm curious if I should push it to the stable fedora 39 repo or not... (and it works fine for me, NVIDIA 545.29.06 kde plasma wayland).

[songww]

I have the same problem on debian sid, 0.32 with nightly doesn't work, but 0.31 is fine.

[kovidgoyal]

Then that will be because your system is not providing an SRGB output buffer which kitty now explicitly requests. See https://github.com/kovidgoyal/kitty/commit/97f5cad3352ee38588b8c5e81988e239bba58a64

As I said, use the X11 backend. Presumably earlier your system was happily not providing an sRGB output buffer which means colors would have been incorrect.

[ondrejj]

Same problem here. Using gnome+wayland+kitty 0.32. After downgrade to kitty-0.31 everything works again. Manual downgrade to Xwayland is not a solution for me.

[kovidgoyal]

Then stick to kitty 0.31 until you can upgrade the rest of your software stack.

[kovidgoyal]

And this is the upstream bug report, follow up there: https://github.com/NVIDIA/egl-wayland/issues/85

[ondrejj]

Same problem with latest kitty 0.32.1:

<home:pts0:~>$ rpm -q kitty
kitty-0.32.1-1.fc40.x86_64
<home:pts0:~>$ kitty 
[destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 875713345
[026 16:12:53.246878] [glfw error 65544]: Wayland: fatal display error: Chyba protokolu
<home:pts0:~>$ 

Looks like still not fixed. :-(

[kovidgoyal]

You will need to followup upstream then. There is only so much I can do to workaround the insanity that is Wayland.

[pierrot-lc]

And this is the upstream bug report, follow up there: NVIDIA/egl-wayland#85

The issue is now fixed in the 550.60 drivers.

[officiallymarky]

And this is the upstream bug report, follow up there: NVIDIA/egl-wayland#85

The issue is now fixed in the 550.60 drivers.

Should it be fixed in 555.58.02 as well?

[pierrot-lc]

Should it be fixed in 555.58.02 as well?

Yes it is fixed in 555.

[officiallymarky]

Should it be fixed in 555.58.02 as well?

Yes it is fixed in 555.

I'm still getting the message about srgb with wayland.

[kovidgoyal]

Yes, the actual issue in the drivers isn't fixed, it just doesn't prevent kitty from starting anymore.

[jknedlik]

Hi! I do get the very same error when using my amd rx 550 and the newest amd drivers.

[kovidgoyal]

And? Your drives don't support sRGB colors, you need to report the issue to your driver's developers.

[officiallymarky]

Yes, the actual issue in the drivers isn't fixed, it just doesn't prevent kitty from starting anymore.

Ahh, thanks! Didn't know it didn't launch before. I was using an old version of Kitty which I just realized so I upgraded and started to notice it when using some functions of kitten.