Description: For several versions now, LO still crashes when the symbol/special character button/feature is used! Really, guys? Is it so complicated to fix this? This problem has been bugging us for many versions now, so no use to really deliberate on it, I guess. I'm using Ubuntu 18.04, completely up-to-date, on a Lenovo Ideapad. Everything else is working fine. Steps to Reproduce: 1. Start operating system 2. Start LO writer, calc or any other. 3. Open a new or existing document 4. Click the symbol/special character button/feature. Actual Results: LO will crash and will show an error-message and advises you to start LO in safe-mode. Expected Results: The symbol/special character menu should open. Reproducible: Always User Profile Reset: No Additional Info:
Thank you for reporting the bug. I am unable to replicate the bug in a recent master build and in the version described in the bug report. Can you please provide more information about your LibreOffice environment? To find this information, go to the "Help" menu in LibreOffice and select the "About LibreOffice" option. I have attached mine as an example: Version: 7.0.0.0.alpha0+ Build ID: 4ff12ba6f4639c73587f2bb58afcc3ca6fb30105 CPU threads: 1; OS: Linux 5.3; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-01-24_21:09:14 Locale: es-ES (en_US.UTF-8); UI-Language: en-US Calc: threaded The VCL may be an issue. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once you have provided additional information.
On Win10 with LO 6.3.4, I don't reproduce this. On pc Debian testing x86-64 with LO Debian package 6.4.0.2, with gtk3, gen or kf5 rendering, I don't reproduce this too. Did you install any specific fonts? If yes, could you disable them for the test? Also, could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps ? Finally, if you still reproduce this, would it be possible you retrieve a backtrace? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace)
Dear arjanl, 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 arjanl, 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