https://bugs.documentfoundation.org/show_bug.cgi?id=148908

Aron Budea <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.documentfounda
                   |                            |tion.org/show_bug.cgi?id=77
                   |                            |051,
                   |                            |https://bugs.documentfounda
                   |                            |tion.org/show_bug.cgi?id=15
                   |                            |4478
            Version|7.4.0.0 alpha0+             |7.2.3.2 release
           Keywords|bibisectRequest             |bibisected, bisected

--- Comment #11 from Aron Budea <[email protected]> ---
Let's keep this bug report focused on the RTF paste, and open a new one on any
issue concerning regular paste.

The crash during RTF paste got introduced by the 7.2 backport of the following
commit in 7.3, bibisected using bibisect-linux-64-7.2. Before that the RTF
paste was hanging, or was just taking a very long time, I haven't waited for it
to finish.

https://cgit.freedesktop.org/libreoffice/core/commit/?id=05f92eb1359c399c43d3bcbe8942034408fa23eb
author          László Németh <[email protected]>   2021-10-01 17:42:48
+0200
committer       László Németh <[email protected]>   2021-10-04 08:22:23
+0200

"tdf#77051 DOCX: fix user index and index entry support"

The crash is fixed since the following commit's 7.4 backport, reverse
bibisected using repo bibisect-linux-64-7.4. However, content is only pasted up
to ToC, and not further.

https://cgit.freedesktop.org/libreoffice/core/commit/?id=5431b756d45bebe74beaba2026704552ee6891f0
author          Jaume Pujantell <[email protected]> 2023-04-27
14:54:55 +0200
committer       Ashod Nakashian <[email protected]>     2023-05-03 12:42:31
+0200

"tdf#154478 fix comments empy after ToC"

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to