https://bugs.documentfoundation.org/show_bug.cgi?id=121293
Michael Weghorn <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Whiteboard| |target:6.3.0
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #11 from Michael Weghorn <[email protected]> ---
This is now fixed with the following commit
commit e770bacc85a0eec96de77068d61b03f374b3cdec
Author: Jan-Marek Glogowski <[email protected]>
Date: Sun Jun 2 21:01:33 2019 +0000
Qt5 workaround modal change after show bug
The presentation minimizer dialog calls setVisible before execute.
This results in the dialog being shown before setting the modality
in execute. And this triggers a bug in the Qt / Xcb stack (gtk is
fine because it directly uses XSendEvent to change the state).
The result is an unmapped, modal dialog window: it's invisible and
blocks the GUI. Qt believes it's show; isVisible() returns true.
And my ~/.xsession-errors shows a "qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow) ... major code: 18 (ChangeProperty)" with an
invalid resource id, according to 'xwininfo -tree -root'.
You can find the window resource of the minimizer by its name in
the full root tree and its unmapped state with 'xwininfo -id'.
I originally thought of a Scheduler bug so enabled debug output
for it. This is already responsible for a delay long enough to
prevent the bug often. Same for doing an additional hide() and
show() sequence. In the end I went with a fixed delay, but that
is just a guess. In theory we could check the mapped state via
Xlib in Qt's show event and manually map it using XMapWindow and
the winId...
I also noted that the minimizer leaks, as there are multiple new
presenter resources after each show and hide...
Change-Id: I2060918aa9c63d385ebb2ffee9e7a3e4196ea766
Reviewed-on: https://gerrit.libreoffice.org/73462
Tested-by: Jenkins
Reviewed-by: Michael Weghorn <[email protected]>
Reviewed-by: Jan-Marek Glogowski <[email protected]>
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
