I opened two ODT files. When I closed the second file, a segmentation fault occurred. [New Thread 0x7fffb6f26700 (LWP 6773)] [Thread 0x7fffb6f26700 (LWP 6773) exited] [New Thread 0x7fffb6f26700 (LWP 6774)] [Thread 0x7fffb6f26700 (LWP 6774) exited] [New Thread 0x7fffb6f26700 (LWP 6775)] [Thread 0x7fffb6f26700 (LWP 6775) exited] [New Thread 0x7fffb6f26700 (LWP 6776)] [Thread 0x7fffc172e700 (LWP 6772) exited] [New Thread 0x7fffc172e700 (LWP 6777)] [Thread 0x7fffc172e700 (LWP 6777) exited] [New Thread 0x7fffc172e700 (LWP 6794)] [Thread 0x7fffc172e700 (LWP 6794) exited] [New Thread 0x7fffc172e700 (LWP 6795)] [New Thread 0x7fffb53ac700 (LWP 6796)] [New Thread 0x7fffb4bab700 (LWP 6797)] [Thread 0x7fffc172e700 (LWP 6795) exited] [New Thread 0x7fffc172e700 (LWP 6798)] [Thread 0x7fffc172e700 (LWP 6798) exited] [New Thread 0x7fffc172e700 (LWP 6799)] Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault. 0x00007ffff5034dd4 in SfxShell::SetDisableFlags(unsigned long) () from /opt/libreoffice5.2/program/libmergedlo.so Regards.
Things to known : 1. This issue occurred also with one file. 2. When I copied this file to another folder, all works fine. 3. when I open in command line mode as : libreoffice thefile.odt all works fine. 3. When I open the file clicking on icon in Thunar, LO asks to update old styles, I answer yes or no, I closed the file without saving the changes. LO crashes. The name of the file is : Travail en cours et corrigés exercices.odt.
When the file is opened waiting my answer for the updating of the styles, I did in a terminal : ps ax I got : /opt/libreoffice5.2/program/soffice.bin --writer file:///home/alain/Documents/Travail/2015-2016/Cours/TS2D-ETT/A58-a-photovolta%C3%AFque%20prep%20%C3%A9tude%20en%20cours/Travail%20en%20cours%20et%20corrig%C3%A9s%20exercices.odt --splash-pipe=5 So, note that the file name was encoded in URL mode. But it was the same when I copied in another folder and then all worked fine.
Could you try getting a backtrace as described here? https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace
Created attachment 128488 [details] Backtrace (In reply to Aron Budea from comment #3) I installed LO 5.2.3 final Build ID: d54a8868f08a7b39642414cf2c8ef2f228f780cf. It has the same issue. Backtrace joined.
Note that for all these files, LO ask the permission to update the styles as it could not find the file ODT after opening. Perhaps it is a path issue somewhere in the source related with the URL scheme?
Also for all these files it ask to save the change (but I have not done changes). It crashed if I save or not. But note that if I reopened the file clicking on the icon in the start panel, all work fine. In this last case : ps ax 7360 ? Sl 0:00 /opt/libreoffice5.2/program/oosplash --writer file:///home/alain/Documents/Travail/2016-2017/Cours/TS2D-ETT/A58-photovolta%C3%AFque%20et%20%C3%A9nergie%20grise/1%20%C3%A9nergie%20grise%20du%20photovolta%C3%AFque.odt 7405 ? Sl 0:02 /opt/libreoffice5.2/program/soffice.bin Note that the URL does not exist now with soffice.bin launching unlike with thunar launching.
This issue seems to be linked with symbolic link. All the files that do crashed Libreoffice, are in a folder called through a symbolic link. For ex: The working folder: /mnt/60084ec9-9eba-45fc-b8e1-c82d69db9818/Work/2016-2017/Curse/TRUDU-ETT/A37-énergie\ électrique-thermique/puissance électrique en sinusoïdal v7.odt
(sorry for the previous post) This issue seems to be related with linux symbolic links. All the files that do crashed Libreoffice, are in a folder called through a symbolic link. For example: The working folder: /mnt/60084ec9-9eba-45fc-b8e1-c82d69db9818/Work/2016-2017/Curse/TRUDU-ETT/A37-énergie\ électrique-thermique/puissance électrique en sinusoïdal v7.odt The link: Documents/Work -> /mnt/60084ec9-9eba-45fc-b8e1-c82d69db9818/Work So the file is open trough the following path in Thunar: /home/alain/Documents/Work/2016-2017/Curse/TRUDU-ETT/A37-énergie\ électrique-thermique/puissance électrique en sinusoïdal v7.odt LO says wrongly that the styles are changed. On closing, LO crashes. If the file is opened through /mnt/60084ec9-9eba-45fc-b8e1-c82d69db9818/Work/2016-2017/Curse/TRUDU-ETT/A37-énergie\ électrique-thermique/puissance électrique en sinusoïdal v7.odt, all work fine. If I save this file without any change through the symbolic link and if I quit LO, after reopening, all work fine. If I copy the folder in /home/alain/ or elsewhere without any link, all worked fine. Summary: This bug is about path with Linux symbolic links. This bug seems to be about a (styles?) path perhaps saved in the ODT file.
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-20170531
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-20170628