On Mon, 2016-11-21 at 10:04 +0100, Dario Faggioli wrote:
> On Sat, 2016-11-19 at 12:56 +0200, Pasi Kärkkäinen wrote:
> > 2) It'd good to create an upstream Wayland bugreport and
> > investigate
> > more about why cirrus is broken with Wayland.
> > 
> Sure, I can do that.
> 
An update.

The discussion here has gone on a bit:
https://bugzilla.redhat.com/show_bug.cgi?id=1227770

The conclusion seems to be that:
"cirrus (virtual) hardware is simply to old to run wayland."

And so this is (and will very likely remain) a 'WONTFIX' for cirrus, at
least on Fedora.

I've also opened a thread on wayland-devel mailing list:
https://lists.freedesktop.org/archives/wayland-devel/2016-November/0318
56.html

There, I learned that Wayland is not the component to blame, as Wayland
is the protocol. So, in our case, the 'bug' is most likely in
gnome-shell / Mutter.

That's not a good thing, though. In fact, just to cite a few sentences
from the thread:

"Packed 24bpp is going to be pain, not least because I don't know of
any clients which render in packed-24"

"The 24bpp paths in pretty much everything are also badly untested, so
that's asking for trouble."

"you will need to test and fix every single Wayland compositor out
there."

"I really think you'd be far far better off trying to figure out how to
move off the legacy Cirrus emulation as soon as you can."

So, we can try seeing if I manage to get some logs out of Mutter to
figure out the actual bug more precisely _but_, considering all that
people have said both here and in the other forums, I think it would be
better to spend that time figuring out how to switch (and document this
for 4.8 and previous version, of course).

Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)