Dominique Martinet

> when you change the screen solution or fullscreen state in the settings screen, you should get a confirmation dialog asking if you would like to keep the new settings...

I had uploaded a full WAYLAND_DEBUG=1 log in the issue, you can get it here: https://gaia.codewreck.org/local/tmp/kodi.wayland_debug.log Short version, this second cnfigure comes after further commits, so I'd tend to agree...

> From what I read there, I gather that this bug also triggers if we want to start full-screen and the compositor does not give us full-screen (at all), correct?...

Hello. I've been completely forgetting about this as I have a workaround (... which I also forgot how it works, running windowed then fullscreening? probably), but would you mind remind...

Thanks for the follow-up! It's been almost a year so I don't think there's any particular hurry at this point, take care of things that need taken care of and...

> @martinetd, can you rebase, i would like to test ? There is no conflict so you can just pull `refs/pull/20632/merge` anytime, which is a merge of this branch and...

> As mentioned in https://github.com/systemd/systemd/pull/24511: would love to see some analysis what the impact of this would be, regarding compat with downstreams and CIs... Choices I can see: - my...

> Updated to bump the minimum libbpf version to 0.7 because we already depend on the skeleton APIs from libbpf 0.7. hmm, I could just build with libbpf 0.3 from...

> I'll double check later today thanks! > On ubuntu I can also build with libbpf 0.5. If I inspect their libbpf so, I can see it includes symbols from...

Since direction seems to be going that way, I'll test this with nixos when I can find time :)