| Summary: | All cross references become undefined | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Steve Kelem <steve> |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED INVALID | ||
| Severity: | major | CC: | andrew, jmadero.dev |
| Priority: | medium | ||
| Version: | 3.6.3.2 release | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
|
Description
Steve Kelem
2012-11-30 00:58:02 UTC
I am affected by both of these issues. But nevertheless these need to be reported separately, always use one bug report per issue (this way these can be tracked and closed separately, it's very unlikely someone is going to stab both of these problems at once). The cross-refernces part is somewhat related to this bug: https://bugs.freedesktop.org/show_bug.cgi?id=63553 Steve, consider keeping backups (based on how many changes you make). If you see this behaviour again, copy your latest backup to say "doc1.odt" and the damaged document without references to "doc2.odt". Open "doc1.odt" and use Edit > Compare Document To compare doc1.odt to doc2.odt This should add doc2.odt to doc1.odt with change tracking. This might be a faster way to restore. That said, if you can generate a reproducible situation, it would help them fix it. I know, very difficult. I had a hard crash bug affect me three times in a row (related to editing GUIs in the IDE). When I decided to open a bug report, I was not able to reproduce. Annoying. Unfortunately with the given information there isn't anything here that we can do - as comment 2 states - we understand this can be difficult but we can't fix the problem if we can't confirm it with reproducible steps. Dear Bug Submitter, Please read the entire message before proceeding. This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO |