Summary: | Image gone after undo multiple times (track changes involved) | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Telesto <telesto> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | deepoose2011, jgfarias42, vmiklos |
Priority: | medium | Keywords: | bibisected, bisected, regression |
Version: | 6.3.0.4 release | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 105948 | ||
Attachments: |
Example file
File with missing frame |
Description
Telesto
2020-09-26 15:40:37 UTC
Appears to be OK with 6.0 Created attachment 165873 [details]
Example file
Confirmed. I'm attaching the resulting file, with the missing frame. The issue also happens on version 6.3. Version: 7.1.0.0.alpha0+ Build ID: 7aaa9ef2e5edaf468f116449776433e98fb1a2f3 CPU threads: 8; OS: Linux 5.7; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-10-09_22:58:32 Calc: threaded Version: 6.3.2.2 Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c CPU threads: 8; OS: Linux 5.7; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded Created attachment 166274 [details]
File with missing frame
Regression introduced by : https://git.libreoffice.org/core/commit/27894be916d5d03ee820e757d2f4abbf21d54615 commit 27894be916d5d03ee820e757d2f4abbf21d54615 [log] author Miklos Vajna <vmiklos@collabora.com> Mon Mar 25 21:36:02 2019 +0100 committer Miklos Vajna <vmiklos@collabora.com> Tue Mar 26 09:15:24 2019 +0100 tree c3b75b7d1dd9446c2ec600e257fe8d3acbe8b46b parent c49583e9a005276b9393c2393ea79b92816e07f3 [diff] Bisected with : bibisect-win32-6.3 Adding CC: to Miklos Vajna This is already good on master. Reverse-bibisecting with linux-64-7.2 points out 0e6d963fbca16f98a3dbb6ef2fee3736a89d055b as the fix, so closing as a duplicate of bug 138141. *** This bug has been marked as a duplicate of bug 138141 *** |