Description: Documents may contain form controls. It is also possible to define keyboard shortcuts that should allow to access the functions of the controls using the keyboard only. The attached document contains a button labelled "Do Nothing" that has no function. The letter "N" is marked with an underline as it should be possible to access this button using the keyboard shortcut Alt+N. This does not work due to bug 146906. The problem addressed here is that it is not possible to open this document using the Windows version of LibreOffice. Steps to Reproduce: Warning: Crash means that changes in _any_ open LibreOffice window may be lost, not just in the text document that causes the crash! Therefore close all other LibreOffice windows before trying this. Open the attached document using LibreOffice Writer in a Windows 7 environment. Actual Results: LibreOffice crashes. This event does not generate a crash report. Expected Results: Writer should open the document. You should see an empty document that contains a single button labelled "Do Nothing" where the letter "N" is underlined. Note: This works in Ubuntu 20.04 with LibreOffice version 6.4.7.2 Reproducible: Always User Profile Reset: No Additional Info: A variation of this theme is (Windows version only): Create a new empty text document. Open it in Writer and turn on the form design mode. Place a button on the document. Open the properties dialogue on this button. This dialogue contains a field that allows to change the text that the button displays. Place a tilde (~) character before some character of this text. LibreOffice crashes when it tries to accept the changes, e.g. when you select some other field in the dialogue. Version: 7.0.4.2 (x64) Build ID: dcf040e67528d9187c66b2379df5ea4407429775 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded
Created attachment 178677 [details] Textdocument containing a button with a keyboard shortcut. Causes Writer to crash (Windows only)
LO 6.4 and 7.0 branches are EOL like 7.1 branch too. Could you give a try at LO 7.2.5 or brand new LO 7.3.1 ? Also, you can try to apply this link: https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile
(In reply to Julien Nabet from comment #2) > LO 6.4 and 7.0 branches are EOL like 7.1 branch too. > Could you give a try at LO 7.2.5 or brand new LO 7.3.1 ? > Also, you can try to apply this link: > https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile Thank you for the hint. When I run LibreOffice with the --safe-mode switch I can open the file without crashing LibreOffice. I forgot to try this. A question remains: How can I find out what is wrong with my profile? I don't like the idea that I should delete the profile, reinstall all extensions, restore all my program code (Basic, Python), restore associations between my code and my icons, restore my toolbars and the keyboard shortcuts I defined, etc.
Without reading in detail the two meta tickets about user profile issues: bug 115518: [META] Old user profile causing problems when upgrading to new release bug 107636: [META] User profile (user data/settings) bugs and enhancements
No repro. Can open test document without crash using: Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 2bb10a827ac13d0caf009e8526ccd9f17dc71653 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: da-DK (da_DK); UI: pt-BR Calc: CL
(In reply to Albrecht Müller from comment #3) > (In reply to Julien Nabet from comment #2) > > LO 6.4 and 7.0 branches are EOL like 7.1 branch too. > > Could you give a try at LO 7.2.5 or brand new LO 7.3.1 ? > > Also, you can try to apply this link: > > https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile > > Thank you for the hint. When I run LibreOffice with the --safe-mode switch I > can open the file without crashing LibreOffice. I forgot to try this. > > A question remains: How can I find out what is wrong with my profile? I > don't like the idea that I should delete the profile, reinstall all > extensions, restore all my program code (Basic, Python), restore > associations between my code and my icons, restore my toolbars and the > keyboard shortcuts I defined, etc. First backup your LO directory profile. Then, you can try to undo from the most recent work you did/extension installed and test if you still reproduce this ; you may find the culprit. Of course, I know it can be tedious. Another thing you can try is to retrieve a bt (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace), it could provide some hints about the culprit.
Thank you for reporting the bug. it seems you're using an old version of LibreOffice. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Albrecht Müller, 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 Albrecht Müller, 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