I use Libreoffice, both .odt and .ods files. Many times I make a budget in ods and paste it in the odt. In the last month, it's not letting me save modified files... ironically, it only lets me save them as .xslx or .docx (!!)
Would it be possible to provide reproduction steps with a sample spreadsheet attached? (if the issue is consistently reproducible after certain steps) I'm afraid only then we're able to investigate this bug further.
Created attachment 127094 [details] Error example I open a new (blank) .odt file, I insert our logo (.jpg), I insert a table and when I try to save it, that's the error
Okay, so I tried with a random jpeg image (like the error image in the attachment), then tried adding a table with different ways, but could always save the file. If the table is coming from Calc, a simple paste produces an embedded Calc object, pasting as formatted text (RTF) looked the closest to what's in the attached image. Still, didn't get any errors during saving (I used LO 5.2.0.4). Since I'm obviously doing something differently, could you give more detailed steps?
Hello Aron, Thank you for your interest and help. A co-worker told me that I should try uninstalling and (re)installing libreoffice. I did it and now it's working as it should. I guess it was an error while instalation or something like that. Anyway, it seems to be fixed right now. I'm glad for it, that's a very good program that I use a lot and I really would have hated to have to use (microsoft) office again. Thanks and best regards
Hi! I'm glad the issue got resolved with a reinstall, thanks for the update. Closing the report as WORKSFORME, then.
*** Bug 101858 has been marked as a duplicate of this bug. ***
https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg Critical is for core functions, major for particular docs.
Hannot, in additon to https://bugs.documentfoundation.org/show_bug.cgi?id=101858#c1 : this can be solved only if reproduced. This may have been solved with LO 5.2.4 or not, OR you can go back to LO 5.1.6. If you are willing to help solve this, then you can additionally: - get http://tdf.io/siguiexe to run parallel LO (extract without installation) - use procdump all the time in order to get a dump Procdump is part of free and useful Sysinternaly Suite. It can be run manually after LO start or better via simple batch file like attachment 129814 [details], that is used instead of LO icon to start LO. Dump is then analyzed with https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg . If you can't do it yourself, just upload dump somewhere (if more that 10 MB and can fit here.) If not, this may be closed as Invalid.
Dear Bug Submitter, 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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/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 MassPing-NeedInfo-Ping-20170628
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA 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 our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20170727