Description: After adding a note to some text, if the em dash is added by writing :---:, the program crashes. This includes other dashes, such as :--: and :-:. Steps to Reproduce: 1. Add a note by right-clicking some text and selecting "Insert Comment" 2. Type in :---: Actual Results: The program crashes. Expected Results: The :---: to be replaced with the em dash, just like in the normal text input. Reproducible: Always User Profile Reset: No Additional Info: I still haven't tested if this bug happens when changing the author name or with different characters other than the em dash and the :--:
No crash for me. Try in Safe mode in Help > Restart in Safe Mode Also please give us your version information in Help > About Libreoffice Version: 25.2.2.2 (X86_64) / LibreOffice Community Build ID: 7370d4be9e3cf6031a51beef54ff3bda878e3fac CPU threads: 8; OS: Linux 6.11; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Flatpak Calc: threaded
if I press Enter after :---: I get !!br0ken!! !!br0ken!! If I move the cursor then press Enter I get an em dash.. No crash.
Tested with Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 356f916d0e7dbab7f871c3feb19c6e1292c2a2f5 CPU threads: 16; OS: Linux 6.11; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Also with Version: 25.2.3.1 (X86_64) / LibreOffice Community Build ID: d8d1af5f77df955194e52baabe19324532ac8e8b CPU threads: 16; OS: Linux 6.11; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
:~/core/core$ git grep 'br0ken' include/rtl/ustrbuf.hxx: rtl_uString_newFromLiteral( &pData, "!!br0ken!!", 10, 0 ); // set to garbage include/rtl/ustrbuf.hxx: rtl_uString_newFromLiteral( &pData, "!!br0ken!!", 10, 0 ); // set to garbage include/rtl/ustring.hxx: rtl_uString_newFromLiteral( &pData, "!!br0ken!!", 10, 0 ); // set to garbage include/rtl/ustring.hxx: rtl_uString_newFromLiteral( &pData, "!!br0ken!!", 10, 0 ); // set to garbage sal/rtl/strtmpl.hxx: return newFromStr_WithLength(ppThis, "!!br0ken!!", 10); sw/qa/uitest/writer_tests7/tdf104795.py: # AssertionError: '12/19/2016, 23:06:31, timur.davletshin' != '12/19/2016, 00:00:00, !!br0ken!!'
Can not reproduce with Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 6869da60961a6213fc961c2ece371c0f18038cde CPU threads: 28; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Thought perhaps it was corrupt user copy of the autocorrect list (created per user in profile once user adds a 'New' entry to their list). Otherwise uses the default shared. Check Tools -> Options -> Paths for location of the acor*.dat file. Clean profile will use the language appropriate from the $ORIGIN/share directory. Simple rename of the acor*.dat (profile and share) does not crash. Just no substitution gets performed. Still need to know if profile reset clears it for OP.
Dear MherDelight, 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 MherDelight, 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