OS CentOS-6.8 L00 v.5.3.0 installed from rpms Symptom. When editing an ODF BASE or CALC docyument LOo will frequently crash and enter document recovery. When the document is recovered LOo frequently immediately crashes when any further editing is attempted. LOo then enters essentially an endless loop of crash and recovery. This behaviour was first encountered with LOo 5.0. It is present in 5.1 and 5.2. as well as 5.3 We currently use 4.3.7.2 which is the last version that we know of that works without this problem.
Hello James, Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Did you try to rename your LO directory profile? (see https://wiki.documentfoundation.org/UserProfile#GNU.2FLinux) Would it be possible you retrieve a backtrace? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace)
Created attachment 131254 [details] A minimal Calc ODS which crashes whenever I try to move a column The attached file is a minimal ods which will cause 5.3 to crash if I try and move the column with data. Or insert a column before it. It may take a couple of tries before the crash happens but it inevitably occurs. If run libreoffice5.3 from the command line this is what I see when it fails: $ libreoffice5.3 (soffice:7341): GLib-GObject-CRITICAL **: g_object_unref: assertion `object->ref_count > 0' failed
I can't reproduce it in Version: 5.4.0.0.alpha0+ Build ID: 880033edde516fc30225005245253293a6a58ba4 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk2; Locale: ca-ES (ca_ES.UTF-8); Calc: group Please, try to rename your profile directory as mentioned in comment 2.
btw, is OpenCL enabled? Tools - Options - OpenCL?
I had already renamed .config/libreoffice to .config/libreoffice.old_2 . That did not change the observed behaviour. I have no idea what OpenCL is.
OpenCL Not Used
Could you please try to provide a backtrace as mentioned in comment 2? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the backtrace is provided.
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-20170830
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-20170929