Created attachment 182717 [details] How it looks like on the big screen Setup: - 14inch laptop, resolution: 2880x1800, 150% scale. This is the primary screen. - ultrawide screen, resolution: 2580x1080, 100% scale. - using wayland. Opening libreoffice calc (or writer, or impress) onto the external screen creates HUGE icons. They seem to be 2x in every direction as he original icons should be (compared to Mozilla Firefox icons). Moving all the window to the notebook screen scales the window and icons/buttons to their expected size. Interesting to see, that the switch between the "normal" and "toobig" size happens when the windows is fully moved to either of the screens. Moving it only partially retains the "size" from the previous screen. STEPS TO REPRODUCE 1. Two screen with different scale on wayland (I guess these are the trigger points) 2. Open LibreOffice Calc (it happens with Writer or Impress as well) OBSERVED RESULT Bad scale on the external screen, with 100% scale factor opposed to the original scale with 150% scale factor. Talking about good vs bad scale is based on comparison of the buttons/icons inside the window to icons/buttons in other apps on the same screen. I opened this issue: https://bugs.kde.org/show_bug.cgi?id=459736 where Nate said it seems like a libreoffice issue. LibreOffice version: 7.3.6-2 SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.9-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i7-11370H @ 3.30GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: TUXEDO Product Name: TUXEDO InfinityBook Pro 14 Gen6
Created attachment 182718 [details] How it should look like (notebook screen)
(In reply to Gergely HORVÁTH from comment #0) > STEPS TO REPRODUCE > 1. Two screen with different scale on wayland (I guess these are the trigger > points) Yes, that sounds like the trigger and this is therefore probably the same as tdf#141578. *** This bug has been marked as a duplicate of bug 141578 ***