So, this might be due to differing radeon_surface layouts based on the RADEON_SURF_SCANOUT flag.
tvoss can apparently reproduce this, and it goes away when he *doesn't* add the SCANOUT flag to the gbm bo in Mir¹. XMir never sets RADEON_SURF_SCANOUT, so it's plausible that this is the issue. ¹: Luckily, it appears that this buffer still happens to be scanoutable ☺ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1218815 Title: [radeon] Graphic glitches and screen corruption (vertical lines) on XMir surfaces only To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1218815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
