Description: Sometimes my LibreOffice has problem with own initialization, but when it successful (only via terminal) and I try open one of LibreOffice files created in last days it crashes - in terminal I see a message (soffice:1993): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed or (soffice:2349): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed Using Xfce DE on Manjaro Linux. Other components (and apps) of my OS works fine. Actual Results: crashes Expected Results: opening and giving chance for editing Reproducible: Always User Profile Reset: Yes Additional Info: User-Agent: Mozilla/5.0 (X11; Linux i686; rv:54.0) Gecko/20100101 Firefox/54.0
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.)
Created attachment 134360 [details] sample odt file causing problem
On pc Debian x86-64 with master sources updated today, I don't reproduce the crash with gtk or gtk3 rendering. 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, would it be possible you attach a backtrace (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace)?
I can't reproduce it in Version: 5.3.3.2 Build ID: 1:5.3.3~rc2-0ubuntu0.16.10.1~lo0 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; Layout Engine: new; Locale: ca-ES (ca_ES.UTF-8); Calc: group Please, also share the information from Help - About LibreOffice
Created attachment 134384 [details] backtrace
Information from Help -> About LibreOffice: Wersja: 5.3.4.2 Build ID: 5.3.4-1 Wątki CPU: 2; Wersja OS: Linux 4.9; UI Render: domyślny; VCL: gtk3; Układ silnika:nowy; Ustawienia regionalne: pl-PL (pl_PL.UTF-8); Calc: group Problem have appeared after updating LO from 5.3.3 to 5.3.4 version. New profile do not solve a problem. Thanks for your help!
Ok for the profile, so now you can try to retrieve a backtrace (by typing "c" when Java related)
Comment on attachment 134384 [details] backtrace Just Java "expected" segfault, not a bt.
Argh, my previous comment hadn't been added! Here it is: " it's not a real bt: Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault. 0xa22058c9 in ?? () from /usr/lib/jvm/java-8-openjdk/jre/lib/i386/server/libjvm.so In this type of segfault, you just have to type "c" (without quotes) and enter key. "
Created attachment 134387 [details] backtrace for Oracle Java I've changed OpenJRE for Oracle Java in LO settings and see what happened. Is this a simple bug related with Java or bug related with LO Java managing?
Created attachment 134415 [details] backtrace after disabling Java in LO After disabling in LO Tools->Options...->Advanced->"Use Java environment" my LO is once again stable (does not crash). I'm attaching backtrace for disabled Java in LO.
Stack is empty. I can't help here sorry.
Can you make it crash with a fresh master build http://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@70-TDF/current/ https://wiki.documentfoundation.org/Installing_in_parallel/Linux
Please, check comment 13
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-20180102
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-20180129