https://bugs.documentfoundation.org/show_bug.cgi?id=145220
Jan-Marek Glogowski <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #175848|0 |1 is obsolete| | --- Comment #4 from Jan-Marek Glogowski <[email protected]> --- Created attachment 175853 --> https://bugs.documentfoundation.org/attachment.cgi?id=175853&action=edit Little terminal program dumping QScreen info with "no" output fix (In reply to Axel Braun from comment #2) > after installation of libreoffice-gtk3 I tried both options on the X1 (the > machine in trouble) and for both cases the result did not change. Hmm. That seems to prove it's not a problem with LO's Qt integration and no general Qt problem, because all three, Qt, Gtk and direct X11, produce the same error. You should have noticed, that LO looked at least very different for SAL_USE_VCLPLUGIN=gen (VCL: x11). The output from my qscreen program is strange (I fixed a little bug in the output, where "no:" wasn't correctly increased; no need to re-run it): (In reply to Axel Braun from comment #2) > ... (the machine in trouble) ... > docb@X1E:~> /tmp/qscreen/qscreen > Qt: 5.15.2 > > no: 0 - current > geometry: QRect(2156,0 1920x1080) > > no: 1 > geometry: QRect(0,0 1920x1080) (In reply to Axel Braun from comment #3) > And here is the output of the working machine: > docb@T520:~> /tmp/qscreen/qscreen > Qt: 5.15.2 > > no: 0 - current > geometry: QRect(1920,0 1600x900) > > no: 1 > geometry: QRect(0,0 1920x1080) For both setups the external HDMI monitor (no: 1) is left of the laptop (no: 0 / eDP and LVDS). Both external rectangles start at 0,0, but for whatever reason the offset of the broken laptop screen is at 2156,0 (the expected is 1920x0, like the working setup). So the configured layout is - from left to right: external HDMI (width: 1920) + 236 pixel nothing + laptop screen (width: 1920). This is also visible in the xrandr output in the KDE bug report. AFAIK nothing generally wrong, just unusual, but I guess it might be the reason why the positioning code in LO fails. Maybe someone else can emulate this setup. If there is no specific reason for the gap, I suggest you try to "fix" your monitor setup, so that they are right next to each other. That might workaround the bug more general. It would be interesting to know, if the gap of 236 pixels was somehow introduced by the KDE update. If that is the case, it suggests there might be a bug in KDE, maybe kwin / compositor related in the widest sense. I might not be able to fix this without the setup for direct debugging, so I hope someone else can reproduce and eventually fix this. I have to check, where the presentation window is actually positioned in the LO code. Quite possible it mixes up width and offset, as these tend to be identical. -- You are receiving this mail because: You are the assignee for the bug.
