Max Katz

See https://github.com/AvaloniaUI/Avalonia/discussions/9291#discussioncomment-3991602

No, it wasn't fixed in SkiaSharp 3.0

Avalonia doesn't handle shaders, and it fails in custom renderer code directly using Skia, so I don't think there is much we can do.

@darinkes this.InvalidateVisual() is normally the way to invalidate visual after you changed Path/Segments.

I think there was an idea to add more pixel formats to support srgb. Like this one https://github.com/AvaloniaUI/Avalonia/pull/9923

Having an additional option parameter makes sense, yes. Even though It makes templates more complex.

I am not a X11 expert, but it might be null, when XKeysymToString returns empty buffer: https://github.com/AvaloniaUI/Avalonia/blob/d2023a94e8410f9a88314e3404158c9e311fef3c/src/Avalonia.X11/X11Window.Ime.cs#L233-L237 If there is no better X11 API, we might not have much room...

@DamianSuess @KubeRoot @christophwille please let me know if you need any help with this upgrade. Although, I am wondering if it might be better to recreate this project from latest...

I believe it was fixed after https://github.com/AvaloniaUI/Avalonia/pull/11552 Let me know if it's still reproducible

> I think that a better approach is to specify multiple TargetFrameworks and use #IF blocks It would be a better approach by default, if there was "net6.0-linux" tfm. Otherwise...