It's been suggested we have an incorrect stride value for scanout
buffers (even when they're not being scanned out). That would certainly
agree with the screenshot in comment #5. So I think a fix is required
via mir_surface_get_current_buffer() ?...
_X_EXPORT int32_t
xmir_window_get_stride(xmir_window *xmir_win)
{
MirBufferPackage *package;
mir_surface_get_current_buffer(xmir_win->surface, &package);
return package->stride;
}
** Also affects: mir
Importance: Undecided
Status: New
** Changed in: mir
Status: New => Triaged
** Changed in: mir
Importance: Undecided => Critical
--
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
