Description: I have 2 monitors, M1 (primary) and M2. M1 is not scaled (100%) while M2 is scaled 125%. When I open LibreOffice on M2, everything is fine. However, if I open it on M1 (unscaled), the buttons and dialogs are grossly overscaled (an accidental use of the 125% scaling factor on M1 would not nearly account for the gross miscalculation). Steps to Reproduce: 1. Have 2 monitors and a Wayland desktop 2. Set 125% scaling on one monitor 3. Open or move LibreOffice to the unscaled monitor Actual Results: Interface elements hugely overblown Expected Results: Proper interface sizing/scaling Reproducible: Always User Profile Reset: No Additional Info: .
Created attachment 182081 [details] Screenshot
Created attachment 182082 [details] System specs
Created attachment 182083 [details] Libre info window
FC36 Version: 7.3.4.2 Build ID: 30(Build:2) CPU threads: 8; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded (See attached screenshots for more details)
Update: Flatpak v 7.4.0.3 does not suffer from the oversizing problem, but top menubar buttons, ruler, and document type font are quite prominently blurry on the 100% display. Right menubar is crisp as it should.
Created attachment 182096 [details] v 7.4.0.3 - Flatpak VCL gtk3
With the gtk3 VCL, buttons sharpen up if I resize the window, but not the document typefont, it seems, that keeps an eerie bluriness in all weather.
It would appear to me that with the gtk3 VCL, even if the app runs on the 100% primary monitor, the document is raster-rendered at 1/125% then scaled up to 100%...
(In reply to dinumarina from comment #7) > With the gtk3 VCL, buttons sharpen up if I resize the window, but not the > document typefont, it seems, that keeps an eerie bluriness in all weather. The gtk3 + Wayland blurry font is reported in bug 140388. Regarding kf5 + wayland, I think your issue is already reported in bug 147216. Thank you! *** This bug has been marked as a duplicate of bug 147216 ***
*** This bug has been marked as a duplicate of bug 141578 ***