https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #8 from Jan-Marek Glogowski <glo...@fbihome.de> --- Created attachment 179388 --> https://bugs.documentfoundation.org/attachment.cgi?id=179388&action=edit Weston with two outputs, one scaled and LO kf5 running. I've found that I can run Bullsyeye Weston in a two screen setup with one scaled window via weston.ini: [core] xwayland=true [output] name=X1 mode=800x600 scale=2 [output] name=X2 mode=1024x768 and weston -c $PWD/weston.ini --output-count=2 This works for LO gtk3, but kf5 is broken, interestingly just on the non-scaled screen, the other looks almost correct. But for whatever reason the start center image is tiny on 200%. It looks like LO has cached the larger fonts and scaling when moving the window form 2x to non-scaling. gtk3 is also "interesting", because it changes the layout of the windows near the border and even resizes it. That's still when completely on one screen. Maximizing the main LO window on the scaled screen crashes LO with just Qt stuff in the backtrace (and also crashes gtk3), but works for the non-scaled screen. A kate window is maximizable on both screens and moving it between both screens works fine, so the kf5 LO should be able to work correct; but kf5 has additional Wayland libs; not sure they must be used explicitly or not. I've tried to find a way to flush the graphics cache somehow from the screen change handler to no avail in the end. -- You are receiving this mail because: You are the assignee for the bug.
