It's certainly a bug in Mir and not the client apps. Whether it's a bug in libmirclient or libmirserver and friends I think is not relevant.
But good news: We're looking at solving Mir's woes with EGL vs pixel format soon. In the new APIs we're releasing this year, Mir will use EGL more natively and not require that you know or specify the pixel format for that. So with some luck, the bug might go away without any additional effort. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: Triaged Status in mir package in Ubuntu: Confirmed Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_8888 to mir_pixel_format_rgba_8888 is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_8888. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
