LibreOffice shows the loading progress bar along the bottom of the screen, and right before the spreadsheet shows, the main window closes and the whole app crashes with a segfault and exits with status 139. Unfortunately, the document that causes the failure contains sensitive information, and soffice.bin hangs before even showing splash art when run under gdb.
Jacob: which Linux distrib do you use? Could you give a try to retrieve a bt by following this link https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace ?
Funtoo Linux. I have tried, but gdb locks up when LibreOffice crashes. Not sure why yet.
Created attachment 109251 [details] gdb trace w/o symbols Hey, it worked this time. I don't have debug symbols yet. I'll get that set up and try again tomorrow.
Thank you Jacob for your feedback. For devs: It seems the crash is triggered here: http://opengrok.libreoffice.org/xref/core/sc/source/core/data/conditio.cxx#2065 maRanges seems to be empty so when doing maRanges[0], it crashes. The next question is: may maRanges be empty? Jacob: On which env are you? (Windows, MacOs, Linux) Just for the test, could you give a try to last stable LO version 4.3.3 or master daily build, see http://dev-builds.libreoffice.org/daily/master/ ?
I am on Funtoo Linux. Should I try building from the git source?
Jacob: yes it could be useful since you can't attach your file. A good start here: https://wiki.documentfoundation.org/Development/BuildingOnLinux You should try to build master sources. Before all this, you must know that you may encounter some problem, see https://bugs.freedesktop.org/show_bug.cgi?id=85214
Created attachment 109352 [details] backtrace cut from master I was able to build master. Here's the new and improved trace.
Thank you Jacob for this interesting bt! Jacob: would it be possible you "sanitize" (see https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission) and then attach the file?
I can look into it but I do not think that would be possible. The document contains an extensive amount of private information.
Jacob: ok then. I put it at NEW since I don't have more questions and there's a backtrace. Kohei/Markus/Eike: one for you? I must recognize I don't know if it's normal or not that maRanges (see comment 4) is empty.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
Should be fixed with this https://cgit.freedesktop.org/libreoffice/core/commit/?id=9af8e14e67d354bb7736271a76a3dd8b6da78fd9 Indeed, we just return if maRanges is empty. Please give a try to a recent LO version (last one is 5.1.4)
(In reply to QA Administrators from comment #11) > ** Please read this message in its entirety before responding ** > > To make sure we're focusing on the bugs that affect our users today, > LibreOffice QA is asking bug reporters and confirmers to retest open, > confirmed bugs which have not been touched for over a year. > > There have been thousands of bug fixes and commits since anyone checked on > this bug report. During that time, it's possible that the bug has been > fixed, or the details of the problem have changed. We'd really appreciate > your help in getting confirmation that the bug is still present. > > If you have time, please do the following: > > Test to see if the bug is still present on a currently supported version of > LibreOffice (5.0.4 or later) > https://www.libreoffice.org/download/ > > If the bug is present, please leave a comment that includes the version of > LibreOffice and your operating system, and any changes you see in the bug > behavior > > the bug is NOT present, please set the bug's Status field to > RESOLVED-WORKSFORME and leave a short comment that includes your version of > LibreOffice and Operating System > > Please DO NOT > > Update the version field > Reply via email (please reply directly on the bug tracker) > Set the bug's Status field to RESOLVED - FIXED (this status has a particular > meaning that is not appropriate in this case) > > > If you want to do more to help you can test to see if your issue is a > REGRESSION. To do so: > > 1. Download and install oldest version of LibreOffice (usually 3.3 unless > your bug pertains to a feature added after 3.3) > > https://pornogratuitici.com/fr/category/246/Prise%20en%20levrette/popular/1/ > > 2. Test your bug > > 3. Leave a comment with your results. > > 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; > > 4b. If the bug was not present in 3.3 - add "regression" to keyword > > > Feel free to come ask questions or to say hello in our QA chat: > http://webchat.freenode.net/?channels=libreoffice-qa > > Thank you for your help! > > -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20 last libre office had same issue again