Description: In Writer, if I open a locked .odt document and then want to Save As for a fresh copy for editing, alt-f does not open the File menu. I have to mouse to the File menu. I should be able to Save As with alt-f alt-a and no mousing. This is a usability issue for speedy touch-typists who learn faster keystroke commands and who will see this as a computer defect. I have not checked Calc etc. or whether the original file being write-protected makes a difference. Steps to Reproduce: 1. Outside of LO, such as in a file manager, lock an .odt document. It can be a blank. 2. In the file manager, open the document. 3. Go to Writer. 4. Type alt-f, so you can open the File menu, to do a Save As, to make a fresh copy for editing. Actual Results: It fails. I have to mouse to the File menu. Expected Results: I should be able to Save As with alt-f alt-a and no mousing. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: This is a usability issue for speedy touch-typists who learn faster keystroke commands and who will see this as a computer defect. The problem does not occur if I open the file from within Writer using the Open command or by selecting its image on Writer's desktop (or whatever you call the display of previously-opened docs). I have not checked Calc etc. Help > About: "Build ID: 6.2.7.1-1.fc30"/"CPU threads: 2; OS: Linux 5.2; UI render: default; VCL: gtk3;"/"Locale: en-US (en_US.UTF-8); UI-Language: en-US" Apparently, OpenGL is enabled. Tools > Options > LibreOffice > View does not list it but terminal output includes this: "OpenGL version string: 2.1 Mesa 19.1.7"
Nick, 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. Change to RESOLVED WORKSFORME, if the problem went away.
I keep my distro (Fedora 30 Linux) evergreen and LO is up to 6.2.7.1 on that distro, which is the version still offered at LibreOffice.org as only "slightly older". I don't want to risk instability and have to roll back, but perhaps someone else would like to test in 6.3.2 or a developer's version. Meanwhile, I'll leave the status at needinfo. In my opening post, I meant to take out the description as better covered in the other sections (STR, actual, expected, etc.). My fault; sorry. I can't edit the post.
[Automated Action] NeedInfo-To-Unconfirmed
Dear Nick Levinson, 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 Nick Levinson, 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
I'm setting as fixed. Somehow, the problem is gone. Maybe a newer version fixed it.
WORKSFORME ist correct in such a Case.