Problem description: Steps to reproduce: 1. Create an arbitrary line 2. edit points 3. create bezier curve from one of the points 4. save the document Current behavior: draw crashes immediately Expected behavior: draw should save the document. NOTE: any drawing can be made and saved, as long as there are NO bezier curves in the drawing. Operating System: Ubuntu Version: 3.5 all versions
On pc Debian x86-64 with 4.0.3 Debian package, I don't reproduce this. pretorix: LO 3.5 is quite old, could you give a try to a newer LO version? I don't know which Ubuntu version you have but you may find a newer LO version here: https://launchpad.net/~libreoffice/+archive/ppa
Created attachment 84630 [details] backtrace log after bezier curve save crash in LibreOffice Draw Steps that generated this log: 1) From terminal: LibreOffice4.1 --backtrace terminal message: ** (soffice:8721): WARNING **: Unknown type: GailWindow 2) Recovered last document (same behavior when open or new document) 3) Created a new polygon (same behavior if line instead of polygon) 4) Edit points 5) Selected a point and change to a Symmetric Transition (convert to bezier curve) 6) Save terminal message: terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc 7) LibreOffice crashes, file is not saved
I have suddenly started having this issue as well in LibreOffice 4.1.0.4 running in Fedora 19 x86-64. I've tried re-installing LibreOffice, installing earlier versions of LibreOffice (as early as 3.6), and installing OpenOffice (version 4.0), all with the same results. Curiously, I can save old documents that already have bezier curves, but as soon as I save after creating a new one the program crashes (instead of saving). I can even work around the problem by copying an old curve and modifying it. It also appears to be isolated to converting a polygon or line into a curve, and not when creating using the curve or freeform line tools. When running from a terminal I get the following warning on start: ** (soffice:8258): WARNING **: Unknown type: GailWindow The crash itself does not result in any additional information. However, if I run with --backtrace, I get the following in the terminal after the crash: terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc The previous comment includes the backtrace log file.
Comment on attachment 84630 [details] backtrace log after bezier curve save crash in LibreOffice Draw Mimetype fixed
Badfully, the method where it fails is 500 line size:-( Michael: here again, we'd need a daily build with debug symbols to propose to install. Any chance to see the TB (http://dev-builds.libreoffice.org/daily/master/Linux-Fedora17-x86_64@4-gcc-4.7-dbgutil/) build again? lmh.0013: the other way is you build LO by using this link: https://wiki.documentfoundation.org/Development/BuildingOnLinux after "./autogen.sh", add this line in "autogen.input" file: --enable-dbgutil
(In reply to comment #1) > On pc Debian x86-64 with 4.0.3 Debian package, I don't reproduce this. > > pretorix: LO 3.5 is quite old, could you give a try to a newer LO version? > I don't know which Ubuntu version you have but you may find a newer LO > version here: https://launchpad.net/~libreoffice/+archive/ppa I installed 4.1.0, and the problem still exists. Most probably there is a conflict with another package in Ubuntu. I can not reproduce the bug with LibreOffice in Windows 7 with Apache OpenOffice 3.0.
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
Whenever I try to save any of my documentation in the Coral Draw, it suddenly crashes down. Because of this error, I have lost some big designing projects. I believe to visit https://legitimate-writing-services.blogspot.com/2019/04/samedayessaycom-review.html whenever I need help with assignment. Any idea to solve that problem that is causing trouble in Coral Draw would be appreciated.