Description: On gtk3 env, after following step, application crash. On kf5 env, this bug could not be confirmed. If my description is uncleared, please see screencast. Steps to Reproduce: 1. open impress 2. close properties on sidebar 3. insert table 4. select table 5. click Table icon on foot bar and close 6. click Border Style icon on foot bar and close 7. click Border Color icon on foot bar and close 8. click Borders(Shift to overwrite) icon on foot bar and close 9. click Fill Color icon on foot bar and close 10. click Optimize icon on foot bar and close 11. Open properties on sidebar Actual Results: after step 11, application crash Expected Results: not crash Reproducible: Always User Profile Reset: Yes Additional Info: I confirm this version Version: 7.1.0.0.alpha0+ Build ID: 83aa172697c11a9550c27a28f8e62b523ec7086d CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3 Locale: en-US (C); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-09-10_21:26:34 Calc: threaded
Created attachment 165502 [details] ScreenCast if my description is uncleared, please see screen cast
The attached screencast shows Calc not Impress.
Created attachment 165509 [details] ScreenCast(True)
Sorry to attach differ screencast screencast about this bug is posted "2020-09-15 08:09 UTC"
Reproduced in Version: 7.1.0.0.alpha0+ Build ID: 6f1e02c96b887750f974c187a82ecd6236e6a435 CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded doesn't crash if the dropdown list from the table toolbar are not displayed first
On pc Debian x86-64 with master sources updated today + enable-dbgutil + gtk3, I don't reproduce this.
Created attachment 165510 [details] gdbtrace I try to get back trace. As first challenge, this bug may not be apposite.
Could you give a try to a recent LO version 7.2.7 or 7.3.4 + try to apply this https://wiki.documentfoundation.org/QA/FirstSteps ?
Dear sawakaze, 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
Dear sawakaze, 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-FollowUp