My approval of this is contingent on them providing documentation (including release notes) for this.

+1

+1

"Byte-Swapped" sounds very confusing though, and I've never heard of the term before. Even a technical, non-xorg-specific term like "foreign-endian" would be clearer here, IMO ...

+1

+1

I agree that a more verbose message would be nice. You could even stuff a hyperlink to the Change page in the message: after all, those extra few bytes don't matter for anything, but they would immediately point people in the right direction.

Considering this is an upstream MR, I don't think a link to a Fedora Change would be appropriate, but I like where you're thinking.

+1

+1

Comments are welcome in these issues (and especially in the devel mailing list threads, which have better community visibility), but please refrain from voting if you are not a current FESCo member. It makes tabulating the official vote totals harder.

That error message is in general a bit of an issue. There's a facility for returning it but in the end it's just unceremoniously and unconditionally dumped to stderr by libxcb. There's no way for an app to hook into it. I have updated it in the upstream PR again now, it now reads as Prohibited client endianess, see the Xserver man page

+1

Thanks for the error message update too, Peter.

After a week, the vote is
APPROVED (+6,0,-0)

Announced.