Public bug reported:
PPA containing a more recent GTK+:
https://launchpad.net/~attente/+archive/ubuntu/gtk-mir
Under U8, GTK+ windows don't render when the width and height are both
>= 479.
If the app starts at a size larger than that, the window will initially
appear entirely black.
Once resized < 479 in either dimension, the window will render properly.
After that, when resizing larger than 478x478, the window only upscales
the most recent framebuffer contents.
I haven't 100% confirmed that this is not GTK+. However:
- This bug does not occur when tested with miral-shell
- GTK+ is receiving configure events for surface resizes
- GTK+ is re-creating cairo surfaces that match the larger size
- GTK+ is still calling mir_buffer_stream_swap_buffers_sync at larger sizes
- I don't think this specific 478/479 number is coming from GTK+, the
initial/min/max sizes aren't that close to it
** Affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1662602
Title:
GTK+ windows don't render when larger than 478x478
Status in unity8 package in Ubuntu:
New
Bug description:
PPA containing a more recent GTK+:
https://launchpad.net/~attente/+archive/ubuntu/gtk-mir
Under U8, GTK+ windows don't render when the width and height are both
>= 479.
If the app starts at a size larger than that, the window will
initially appear entirely black.
Once resized < 479 in either dimension, the window will render
properly.
After that, when resizing larger than 478x478, the window only
upscales the most recent framebuffer contents.
I haven't 100% confirmed that this is not GTK+. However:
- This bug does not occur when tested with miral-shell
- GTK+ is receiving configure events for surface resizes
- GTK+ is re-creating cairo surfaces that match the larger size
- GTK+ is still calling mir_buffer_stream_swap_buffers_sync at larger sizes
- I don't think this specific 478/479 number is coming from GTK+, the
initial/min/max sizes aren't that close to it
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1662602/+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
