Bugzilla – Bug 1164885
LibreOffice and kde5: Impress presentation doesn't properly use dual-monitor
Last modified: 2020-02-25 21:44:52 UTC
Please have a look at https://bugs.documentfoundation.org/show_bug.cgi?id=119719 I suddenly have exactly the same problem on my OpenSUSE 15.1. The presentation layer and the presenter's management view is at the same monitor. It worked properly for years and suddenly it's broken here.
(In reply to Peer Heinlein from comment #0) > Please have a look at > > https://bugs.documentfoundation.org/show_bug.cgi?id=119719 I quickly skimmed through that, it seems that a change in Qt would be needed. Quoting: For the record: Qt 5.10 is needed for this to work, and the commit in the qtbase repository from which on this works (in conjunction with the LO fix) is this one: commit d7a9e08f0ada36ad8ad44651f27a76c9c74e3428 (HEAD) Author: Morten Johan Sørvig <morten.sorvig@qt.io> Date: Wed Apr 19 11:19:19 2017 +0200 Make QWindow::setVisible() work for widgets
Btw, bug#1148042 is apparently the same (but filed against LibreOffice, so we didn't see it).
*** Bug 1148042 has been marked as a duplicate of this bug. ***
A link to the mentioned commit: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=d7a9e08f0ada36ad8ad44651f27a76c9c74e3428 @Fabian: what do you think? Could this be backported to Leap 15.1's Qt? The LibreOffice bug report suggests it should be ok.
(In reply to Wolfgang Bauer from comment #4) > A link to the mentioned commit: > https://code.qt.io/cgit/qt/qtbase.git/commit/ > ?id=d7a9e08f0ada36ad8ad44651f27a76c9c74e3428 > > @Fabian: what do you think? > Could this be backported to Leap 15.1's Qt? > The LibreOffice bug report suggests it should be ok. It adds a new virtual method, so breaks (private) ABI. Unfortunately QWindowPrivate is used everywhere throughout Qt, like qtdeclarative or qt3d, so we'd have to rebuild everything using the private ABI if we backport this. Until Leap 15.2 is out I recommend using the gtk3_kde5 plugin again.
Well, then it's back to LibreOffice, I suppose... *** This bug has been marked as a duplicate of bug 1148042 ***