Summary: | EDITING: CRASH when undo leads to a deleted style | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Rainer Bielefeld Retired <LibreOffice> |
Component: | Libreoffice | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | critical | ||
Priority: | medium | CC: | bfo.bugmail, bugs, jmadero.dev, jorendc, LibreOffice, michael.meeks, thb |
Version: | Inherited From OOo | ||
Hardware: | Other | ||
OS: | All | ||
See Also: | https://issues.apache.org/ooo/show_bug.cgi?id=120015 | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 44446 | ||
Attachments: | MacOS X log file for crash with bug 51253, LibreOffice 3.5.4.2 |
Description
Rainer Bielefeld Retired
2012-06-20 02:34:35 UTC
NEW due to AOOo Bug @Thorsten: Please set Status to ASSIGNED and add yourself to "Assigned To" if you accept this Bug Created attachment 63307 [details] MacOS X log file for crash with bug 51253, LibreOffice 3.5.4.2 I have tried to reproduce this bug with LibreOffice 3.5.4.2 on MacOS X 10.6.8, in order to get a MacOS log file which may include some information which could be helpful to track this issue down. The crash happened as advertised ;-) You will find the log file attached. Hope it helps ... https://issues.apache.org/ooo/show_bug.cgi?id=120015 status: RESOLVED FIXED patches available Can we mark this as resolved then? (In reply to comment #4) > Can we mark this as resolved then? No; it's fixed in AOO, but not (yet) in LibO -- just read comment #3 ;-) Moving to 3.6 MAB as we're closing the 3.5 tracker. This bug still appears in master built a few days ago Also reproducible using writer. Therefore I change component from 'Presentation' to 'LibreOffice'. Can we cherry-pick the AOO patch? fixed in master, Thorsten to review for -4-0. Thanks for filing ! :-) Fix pushed to -4-0 as well: http://cgit.freedesktop.org/libreoffice/core/commit/?id=f57fbde51a16d3d7f73eba67420a506d82e16cda |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.