Created attachment 126080 [details] Sample ods file where deleting a column causes a crash and recovery cycle * When: Always * What: Calc crashes and enters recovery mode for the current work file. * How: Delete a column * How to reproduce: 1. Open a new calc spreadsheet. 2. Select any column and delete it. * Expected result: Column should be deleted and rightmost columns shifted left. * Actual result: Calc program immediately crashes and enters document recovery. Following recovery the original column in file is deleted.
On pc Debian x86-64 with LO Debian package 5.1.4 with the file you attached, I don't reproduce this. Could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#GNU.2FLinux) and give a new try? If you still reproduce this, could you retrieve a backtrace? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace)
Created attachment 126083 [details] strace log
Calc still crashes whenever a column is removed. Resulting strace.log.gz attached above. $ sudo /opt/libreoffice5.1/program/soffice --strace [sudo] password for byrnejb_hll: ** (soffice:11843): WARNING **: Invalidate all children called ** (soffice:11843): WARNING **: Unknown event notification 37 pure virtual method called terminate called without an active exception
(In reply to James B. Byrne from comment #2) > Created attachment 126083 [details] > strace log I talked about "backtrace" not "strace" (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace)
this bug looks similar to the crashes I am having. https://bugs.documentfoundation.org/show_bug.cgi?id=101957 I have attached a gdb trace to case 101957
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-20170328
running 'libreoffice5.3 --backtrace' from a gnome2 destop terminal session produces no visible output or application window after 45 minutes. Exactly how long is this supposed to take before one can perform the test? $ libreoffice5.3 --backtrace GNU gdb (GDB) Red Hat Enterprise Linux (7.2-90.el6) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /opt/libreoffice5.3/program/soffice.bin...(no debugging symbols found)...done. log will be saved as gdbtrace.log, this will take some time, patience... PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 19350 byrnejb_ 20 0 846m 76m 43m R 99.5 0.5 40:27.25 soffice.bin This is blocking running version 4.3 of LibreOffice as well as noticeably slowing everything else. None of the 5.x rpm packages that I downloaded from LibreOffice provide a working calc program and at times 5.3 will enter into an endless recovery loop following a crash.
On pc Debian testing x86-64, libreoffice --backtrace shows this on console: " GNU gdb (Debian 7.12-6) 7.12.0.20161007-git ... <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/lib/libreoffice/program/soffice.bin...(no debugging symbols found)...done. log will be saved as gdbtrace.log, this will take some time, patience... " then LO starts right away. BTW I noticed in your strace file some path including root + libreoffice. Did you install LO with package repository manager from RedHat + do you use non root user to test?
(In reply to Julien Nabet from comment #8) > On pc Debian testing x86-64, libreoffice --backtrace shows this on console: > " > GNU gdb (Debian 7.12-6) 7.12.0.20161007-git > ... > <http://www.gnu.org/software/gdb/documentation/>. > For help, type "help". > Type "apropos word" to search for commands related to "word"... > Reading symbols from /usr/lib/libreoffice/program/soffice.bin...(no > debugging symbols found)...done. > log will be saved as gdbtrace.log, this will take some time, patience... > " > > then LO starts right away. I had to kill it after two hours with no visible activity. I am attaching the gdbtrace.log file produced. > > BTW I noticed in your strace file some path including root + libreoffice. > Did you install LO with package repository manager from RedHat + do you use > non root user to test? I have tried both at different times. The --backtrace was first attempted using a non-privileged user and the program would not start. The second time I performed the test as root and could not get the program to fail. However, opening as a non-priviledged user the same file used during the root user testing caused LOo to crash as soon as any editing was attempted on the spreadsheet. The versions of LOo later than 4.3, which is the last provided by RedHat/CentOS for the v6 release, were all installed using YUM from packages obtained directly from the Document Foundation's website.
Created attachment 132257 [details] backtrace as non-priviledged user
Created attachment 132258 [details] LOo calc failure --backtrace I retried the test as root using a more complicated calc spreadsheet and was able to reliably crash LOo-5.3 whenever I inserted a new sheet. The terminal seesion displayed this: # libreoffice5.3 --backtrace GNU gdb (GDB) Red Hat Enterprise Linux (7.2-90.el6) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /opt/libreoffice5.3/program/soffice.bin...(no debugging symbols found)...done. log will be saved as gdbtrace.log, this will take some time, patience... pure virtual method called terminate called without an active exception The resulting gdbtrace.log is attached.
(In reply to James B. Byrne from comment #9) >... > The versions of LOo later than 4.3, which is the last provided by > RedHat/CentOS for the v6 release, were all installed using YUM from packages > obtained directly from the Document Foundation's website. Re reading this part, did you check Linux prerequisites for LO: " glibc2 version 2.5 or higher gtk version 2.10.4 or higher Gnome 2.16 or higher, with the gail 1.8.6 and at-spi 1.7 packages (required for support for assistive technology [AT] tools), or another compatible GUI (such as KDE, among others) " (see https://www.libreoffice.org/get-help/system-requirements/)
(In reply to Julien Nabet from comment #12) > Re reading this part, did you check Linux prerequisites for LO: > " > glibc2 version 2.5 or higher > gtk version 2.10.4 or higher > Gnome 2.16 or higher, with the gail 1.8.6 and at-spi 1.7 packages (required > for support for assistive technology [AT] tools), or another compatible GUI > (such as KDE, among others) > " > (see https://www.libreoffice.org/get-help/system-requirements/) No. I expect that any dependencies are specified in the srpm spec file and that the installer checks that the target system meets those requirements. Since yum/rpm installed the LOo packages without error I infer that the package prerequisites were met.
(In reply to James B. Byrne from comment #13) > (In reply to Julien Nabet from comment #12) > > Re reading this part, did you check Linux prerequisites for LO: > > " > > glibc2 version 2.5 or higher > > gtk version 2.10.4 or higher > > Gnome 2.16 or higher, with the gail 1.8.6 and at-spi 1.7 packages (required > > for support for assistive technology [AT] tools), or another compatible GUI > > (such as KDE, among others) > > " > > (see https://www.libreoffice.org/get-help/system-requirements/) > > No. I expect that any dependencies are specified in the srpm spec file and > that the installer checks that the target system meets those requirements. > Since yum/rpm installed the LOo packages without error I infer that the > package prerequisites were met. You're right but just in case the spec file has some bugs, could you provide versions of quoted components?
This is the system that LOo is running on. I can see that glibc is older than the required version so I gather that the problem likely lies therein. Linux 2.6.32 glibc-static 2.12 gtk2 2.24.23 gnome-desktop 2.28.2 gdm 2.30 (at-spi) free -h . . . Mem: 15G df -h . . . 32G 15G 15G 51% / xrandr . . . Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 lshw . . . *-cpu product: Intel(R) Core(TM)2 Quad CPU Q8400 @ 2.66GHz
(In reply to James B. Byrne from comment #15) > This is the system that LOo is running on. I can see that glibc is older > than the required version so I gather that the problem likely lies therein. The glibc version is fine, 2.12 is newer than 2.5 :) https://sourceware.org/glibc/wiki/Glibc%20Timeline
Seems no one else has this problem, *AND* it seems to occur for the reporter only if LibreOffice is run as root, which is not recommended anyway.. and it's for an old release. I'm closing this bug after a year in UNCONFIRMED status.