https://bugs.documentfoundation.org/show_bug.cgi?id=140728
--- Comment #9 from Jan-Marek Glogowski <glo...@fbihome.de> ---
So I had a look at this, because I was fixing bug 140404 and was already in the
clipboard code. I can't repo any of the crashes with the steps on Debian buster
with current master, from any comment. But then there are more Klipper options,
like the sync of PRIMARY and CLIPBOARD, which might trigger other code. I
checked it doesn't trigger the fix for bug 140404, just in case.
Bug 140700 is about Calc and nothing in this bugs bt (attachment 170141)
indicates Calc and ~SwTransferable() already has equivalent code to the Calc
fix:
SwModule* pMod = SW_MOD();
if(pMod)
My current idea is, that these kind of bugs are triggered by the workaround for
bug 131533. We defer the real clipboard clear handling, but no LO code really
expects that. Everything is refcounted, so it should work.
And I can't repo the crash from bug 131533 anymore, if I revert that fix, but
the bug 131533 terminal message "QXcbClipboard::setMimeData: Cannot set X11
selection owner" still appears. That also shouldn't be a result from the fix
for bug 140700, because bug 131533 was involving Draw, but since I can't repo
and it has no attached bt...
So I thought to test Application::IsQuit to catch the shutdown and skip
deference, in this case, but that returns false on quit too. Seems
Application::Quit is called much later :-(
If someone can repo the crash and has a build, can you check, if
$ git revert 313081c0703c66918e95640c74cd57312a1e8bba
fixes the crash?
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
