Description: Dump below: kernel: soffice.bin[32497]: segfault at 7f2bf6ab0000 ip 00007f2bfd1f6c33 sp 00007ffc38cba310 error 7 in ld-2.26.so[7f2bfd1eb000+25000] Oct 18 15:18:15 - systemd[1]: Created slice system-systemd\x2dcoredump.slice. -- Subject: Unit system-systemd\x2dcoredump.slice has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit system-systemd\x2dcoredump.slice has finished starting up. -- -- The start-up result is RESULT. Oct 18 15:18:15 - systemd[1]: Started Process Core Dump (PID 32498/UID 0). -- Subject: Unit systemd-coredump@0-32498-0.service has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-coredump@0-32498-0.service has finished starting up. -- -- The start-up result is RESULT. Oct 18 15:18:15 - systemd-coredump[32499]: Process 32497 (soffice.bin) of user 1000 dumped core. Stack trace of thread 32497: #0 0x00007f2bfd1f6c33 _dl_relocate_object (ld-linux-x86-64.so.2) #1 0x00007f2bfd1eef27 dl_main (ld-linux-x86-64.so.2) #2 0x00007f2bfd203af3 _dl_sysdep_start (ld-linux-x86-64.so.2) #3 0x00007f2bfd1ecdf8 _dl_start (ld-linux-x86-64.so.2) #4 0x00007f2bfd1ebf38 _start (ld-linux-x86-64.so.2) -- Subject: Process 32497 (soffice.bin) dumped core -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: man:core(5) -- -- Process 32497 (soffice.bin) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Oct 18 15:18:25 - kernel: soffice.bin[32561]: segfault at 7f365d660000 ip 00007f3663da6c33 sp 00007fff54223e80 error 7 in ld-2.26.so[7f3663d9b000+25000] Oct 18 15:18:25 - systemd[1]: Started Process Core Dump (PID 32562/UID 0). -- Subject: Unit systemd-coredump@1-32562-0.service has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-coredump@1-32562-0.service has finished starting up. -- -- The start-up result is RESULT. I saved my work on writer and then did a quick forced terminate on libreoffice. It is the equivalent of pressing ctrl+C on a running script. Then i hibernated computer after a few minutes. When coming out of hibernation and trying to open libreoffice, it would show the libreoffice splash for a split microsecond before disappearing and crashing. This has happened previously, but i didn't report, just did a reboot and reinstalled libreoffice after a while and it worked. I tried to reset my user profile, it did no good. Steps to Reproduce: 1.Use a terminal to open libreoffice 2.write some stuff into writer and save but dont close 3.Ctrl+C in the terminal 4.hibernate and unhibernate 5.run libreoffice command in terminal Actual Results: Still crashed. Expected Results: Libreoffice would not start up. Reproducible: Didn't try User Profile Reset: Yes Additional Info: OS - Arch linux, package manager pacman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0
So, you just reproduced it once, or you can reproduce it systematically? I can't reproduce it in Version: 5.4.2.2 Build ID: 1:5.4.2~rc2-0ubuntu0.17.04.1~lo2 CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; Locale: es-ES (ca_ES.UTF-8); Calc: group
(In reply to Xisco Faulí from comment #1) > So, you just reproduced it once, or you can reproduce it systematically? > > I can't reproduce it in > > Version: 5.4.2.2 > Build ID: 1:5.4.2~rc2-0ubuntu0.17.04.1~lo2 > CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; > Locale: es-ES (ca_ES.UTF-8); Calc: group I reproduced it multiple times by random, each time it was after i exited hibernation. I cannot pinpoint where exactly it failed after. To clarify, in the Arch linux repos, the extra/libreoffice-fresh version was the one that crashed. I have since uninstalled that one and am using the extra/libreoffice-still branch, and that hasn't crashed yet so far. So i am guessing some new feauture in the fresh branch isn't working with my setup.
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-20180502
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-20180530