[Development] Enabling xcb-native-painting feature in CI

[Jean-Michaël Celerier]

I still use it and I still am in that case! It's incredibly useful
when performing remote edits on e.g. Raspberry Pis with low wifi
quality, nothing else works.

On Mon, Oct 27, 2025 at 5:24 AM Lars Knoll via Development
<development at qt-project.org> wrote:
>
> We re-added back for a specific large customer at that time, who was using Qt/X11 over low bandwidth connections and where the image based painting was not performing well enough.
>
> It's a long time ago, so I don't quite remember who the customer was. But I doubt that they still have the same problem today, so I would also go for removing it.
>
> Cheers,
> Lars
>
> On 27 Oct 2025, at 09:56, Eirik Aavitsland via Development <development at qt-project.org> wrote:
>
>
> +1 for removing it. It was only added in Qt 5 on Lars’ request to solve some very specific usecase that nobody remembers anymore. It has no future.
>
> - Eirik Aa.
>
>
> Confidential
>
> From: Development <development-bounces at qt-project.org> on behalf of Thiago Macieira <thiago.macieira at intel.com>
> Date: Saturday, 25 October 2025 at 18:42
> To: development at qt-project.org <development at qt-project.org>
> Subject: Re: [Development] Enabling xcb-native-painting feature in CI
>
> On Saturday, 25 October 2025 08:59:40 Pacific Daylight Time Albert Astals Cid
> wrote:
> > Removing it was going to be my initial suggestion, but after speaking to the
> > opensuse packagers it seems there is some use for it
> >
> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.opensuse.org%2Fshow_bug.cgi%3Fid%3D1214915&data=05%7C02%7C%7C8fb6825610764d67cd8e08de13e58746%7C20d0b167794d448a9d01aaeccc1124ac%7C0%7C0%7C638970073737388485%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=c67q4ycfU6Qc83H2589NUUl6QYMzQ%2Fnk%2BBAgwevn12k%3D&reserved=0
> >
> > Yes, i know the bug mentions qt5 but i would assume it potentially applies
> > for qt6 too.
>
> The problem is that it's dangerous, as it seems no one is building this and
> testing it. The only changes to it since it was revived in 2017 appear to be
> build and issue fixes. I suppose that if anyone reported issues with it in
> JIRA, we wouldn't be able to fix and would close the bug report as "you've used
> an experimental feature, you accepted the risk"
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Principal Engineer - Intel Data Center Group
> --
> Development mailing list
> Development at qt-project.org
> https://lists.qt-project.org/listinfo/development
>
>
> --
> Development mailing list
> Development at qt-project.org
> https://lists.qt-project.org/listinfo/development