Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have discovered at least four ways to crash LO cold dead.
Desktop PC, recently installed Ubuntu 16.04, uninstalled and freshly re-installed LO 5.1.6.2, including LO Base.
Renamed .config\libreoffice\4\user to ...\userOld.
open LO Write or Calc on Untitled 1.odt/ods, Tools, Macros, Run Macro, BOOM
open LO Write or Calc on Untitled 1.odt/ods, Tools, Customize, Keyboard, Category, LibreOffice Macros, BOOM
open LO Base, Select database (default), Finalize, Save as, Save, BOOM
this creates a file named New Database.odb in my home directory
double click on New Database.odb in my home directory (or any other .odb file), Tables, BOOM
BOOM → all open LO windows immediately close
Clicking any of my LO shortcuts brings up “LibreOffice 5”, LibreOffice Document Recovery, which then runs just fine.
This is really hurting me because I have a whole bunch of macro work to do. Any help?
I don't know if it is resolved. I don't use Base, or macros, but to prevent crashes on the Macro command or tab, I unchecked "use a Java runtime environment" under Options > Advanced. Obviously, that won't help someone using Base, but I don't know if macros need Java.
The "stack_guard_gap=1" kernel parameter fixed it all up for me.
I also found a thread in the Slackware forum that seems to identify the same problem. It was fixed there with a "stack_guard_gap=6" kernel parameter. That works well for me in Ubuntu 16.04 also.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.