Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index


I'm using Ubuntu 14.04 LTS with the Unity DE. I honestly don't recall the actual things I was doing when it crashed, other than I was using Writer (which I use 95% of the time). If I recall, it happened a lot when I had multiple files open, and it nearly always happened when I tried to open an ".odt" file directly from "Files," the Ubuntu file manager, rather than going through the LO "Open File" dialogs.

Before uninstalling, I did some online searching and found many others who were experiencing frequent crashing with 5.0.x. I just figured it wasn't yet ready for prime time.

As for config files, when I installed 5.0.x, it recognized my custom settings and templates from 4.4.x, so it must have imported at least some of them.

At any rate, I'm generally happy with


On 01/04/2016 07:19 PM, Tim---Kracked_P_P---webmaster wrote:

What system are you using that gives you the daily crashes?

I agree with Tom that soon the current 5.0.x line will be turned into the "still" version line. I am running both 4.x.x and 5.0.x between my different dual booting Win10 partitions and my Ubuntu 14.xx/15.xx partitions and single OS systems.

I have not experienced any crashing, except for some very large and complex files. Maybe I do not use my LO version[s] as much as you do, but I am not getting your type of crashing.

So it could be something in your system that may not like LO, or it may just be that there is a corruption in the config files. If I remember correctly, 4.x and 5.x use different config file folders.

Yes, I still recommend 4.x to people, but since that like is coming to its end, I will have to decide if 5.0.x is ready "enough" for me to point clients and family to it.

Tim L.

On 01/04/2016 03:39 PM, Virgil Arrington wrote:
For what it's worth, I had downloaded the "fresh" branch a few weeks ago. I think it was version 5.0.3 (or 4). I experienced daily crashes with it. I got so frustrated that I completely uninstalled it and went back to the trusty "still" version. My current plan is to not go near version 5 until I find that version 4 fails to complete my work.

I would recommend that the download cite default to the "still" branch. If I had been a complete noob and had this experience with the default "fresh" branch, I'd be looking for a different solution altogether.


On 01/04/2016 02:17 PM, Tom Davies wrote:
Hi :)
This mailing list usually recommends the "Still" branch rather than
the "Fresh" branch.

The "Still" branch has usually had enough "Service Packs" to fix
almost any problems that people may have had with the "Fresh" branch.
  The "Fresh" branch is the default download offered on the official
website.  It helps the least geeky people and complete noobs to get
the version with the newest features and the most problems. The
"Still" branch has all the features almost anyone is ever likely to
need, it is extremely robust and reliable - so we give people the
other version because it's more interesting and flashy.

However the "Fresh" branch has just had it's 4th "Service Pack" and so
it's about due to be named the new "Still" branch.  It's about the
time that many of us on this mailing list move our clients and
"mission critical" machines onto this branch and start getting excited
about the prospect of having an entirely new branch to try out.

Good luck and regards from
Tom :)

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.