Description: Several weeks ago after downloading the recent Manjaro updates Libre Office quit saving files. It wil update an existing file but will not create/save a new one. When I hit Save or Save As the dialog box opens. The File Name box has a suggested folder, Documents. I select ‘Documents’ either from the main display in the box or from the ‘title’box. Same result in the end. I then enter the file name. I have to first clear ‘Documents’ from the entry box. When I try to save the whole application locks. I have to kill it from the terminal. Nothing is saved. On the next ‘open’ there is the usual file recovery option after a crash. The recovered document is blank. An earlier version, 6.0, works fine in the Linux Mint OS. I am using Manjaro 4.16.18.1, Liberoffice build 6.1.0.2 version 6.1.0.3 Thanks Steps to Reproduce: 1.Open LibreOffice text or spreadsheet 2.Create document 3.Save Actual Results: LibreOffice locks and must use the terminal to kill it. Expected Results: Saved file in a new filename Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Version: 6.1.0.3 Build ID: 6.1.0-2 CPU threads: 2; OS: Linux 4.16; UI render: default; VCL: gtk3_kde5; Locale: en-US (en_US.UTF-8); Calc: group threaded Works in Safe Mode stopped hardware acceleration and reset user profile. No change.
First bug report would not allow me to select the proper version I used unspecified and it sent. Version is in report
Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
Did the reset. No change. On open of the SAVE dialog box DOCUMENTS appears in the NAME window. Any attempt to save in any matter results in a hung process. Terminal KILL procedure is required to close the application.
See "VCL: gtk3_kde5;" - this is Arch Linux making its users act as guinea pigs. Some bugs related to this have been fixed and the fixes will be in the 6.1.2 version. It is thankfully coming in roughly 2 weeks: https://wiki.documentfoundation.org/ReleasePlan/6.1#6.1.2_release
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 Ron, 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 Ron, 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