https://bugs.documentfoundation.org/show_bug.cgi?id=159369
--- Comment #2 from Michael Weghorn <[email protected]> --- I can reproduce this in a GNOME Wayland session on Debian testing. Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c479944eb4f9f5a22c7b248185f22c86ea85d12a CPU threads: 12; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded > As a workaround, as long as Xwayland is supported on the OS, one can force a > MetaWindowXwayland window for LibreOffice with e.g.: > > WAYLAND_DISPLAY= libreoffice7.6 I confirm that using GDK_BACKEND=x11 to force the x11 Gtk backend makes it work. (In reply to Stéphane Guillou (stragu) from comment #0) > Steps: > 1. Open a new Writer document, zoom it at about 310% > 2. Open GNOME's Universal Access settings > Zoom options, turned it on with > Magnification at e.g. 8× > 3. Type text into Writer FWIW, step 1) can also be skipped, i.e. it's unrelated to the internal zoom factor in LO. (In reply to Stéphane Guillou (stragu) from comment #1) > I think we can blame Wayland (and GNOME?) here, unfortunately. > The issue affects other applications and has been reported in > https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4112 > It makes sense as there are other issues related to Wayland being bad at > reporting window positions (is that correct, Michael?). > > The offset depends on the position/size of the window, and therefore is less > noticeable at lower zoom levels and when the window is maximised. To see > that, move the window toward the bottom-right of the screen and notice the > issue getting worse and worse. > > > Michael, can you confirm that this is unfortunately out of our hands? It's true that global/desktop coordinates/positions are not supported on Wayland any more, i.e. GNOME Mmagnifier can no longer query the position on screen directly from the application via AT-SPI. However, GNOME magnifier has been adapted to query window-relative positions from the application and calculate the global coords from that, see bug 149952 comment 2, so I'd expect that this should work when both, 1) the application reports correct window-relative coords (implemented in the context of tdf#149952) 2) GNOME magnifier correctly calculates the screen coordinates and moves to these then (or similar, whatever the exact mechanism within GNOME magnifier does) This sounds like it could be a bug in either 1) or 2). Since this worked OK in a quick test with Gedit, the problem might be 1), i.e. LO's window-relative coords still not being fully accurate after the changes done in the context of tdf#149952, but that would need further examination. (I've also commented on https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4112 accordingly) -- You are receiving this mail because: You are the assignee for the bug.
