Since I updated to Libreoffice Version: 7.0.4.2 I cannot open my Password protected .odt file anymore. Everytime it stated wrong password. Version: 7.0.4.2 Build ID: 00(Build:2) CPU threads: 8; OS: Linux 5.9; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded I could open the same password-protected file on a Win10 system running Libreoffice 5.2.3.3 x64. On this System I saved the file as password protected again, and secondarily saved it without the password protection under a different name. Going back to my Fedora Libreoffice Version: 7.0.4.2 installation I could not open the newly saved password protected .odt file, stating wrong password. I then successfully opened the non password-protected file on Fedora Libreoffice Version: 7.0.4.2, and saved it as password protected. I could then open this file without being asked for a password.
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Created attachment 168318 [details] Password protected with LO Version: 7.0.3.1 Fedora Linux 5.9 I have newly created the document "20201219_PWprotectedSample.odt" and password protected it (Password = testpw) with LO Version: 7.0.3.1 on Fedora Linux 5.9. I can open it by the password (Password = testpw) with LO Version: 7.0.3.1 on Fedora Linux 5.9. I can open it by the password (Password = testpw) with LO Version: 7.0.3.1 on Win10 latest update. I CANNOT open it with LO Version: 7.0.4.2 on Fedora Linux 5.9. Eveytime I enter the password (Password = testpw) it states wrong password and fails to open.
Test file, "20201219_PW_sample.odt" created and password protected with: LO Version: 7.0.4.2 Build ID: 00(Build:2) CPU threads: 8; OS: Linux 5.9; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded *(Password = testpw) If I open it on the same system it opens without asking a password This file also opens correctly without asking a password with: LO Version: 7.0.3.1 (x64) Build ID: d7547858d014d4cf69878db179d326fc3483e082 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded
Created attachment 168321 [details] Password protected with LO Version: 7.0.4.2 Fedora Linux 5.9 Test file, "20201219_PW_sample.odt" created and password protected with: LO Version: 7.0.4.2 Build ID: 00(Build:2) CPU threads: 8; OS: Linux 5.9; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded *(Password = testpw) If I open it on the same system it opens without asking a password This file opens correctly without asking a password with: LO Version: 7.0.3.1 (x64) Build ID: d7547858d014d4cf69878db179d326fc3483e082 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded
New finding After a new kernel update I rebooted my Fedora33 system and miraculously I do not experience any worries regarding password protection anymore. The update was from kernel 5.9.14-200.fc33.x86_64 to kernel 5.9.15-200.fc33.x86_64. Accompanying the kernel updates there were other included updates, of which I would have to research. I cannot trace if it was the kernel update, other updates, or solely the reboot. If you need further information on the updates that I carried out in the meantime which could have led to the cure, please provide me with dnf commands that you need for information. From my user point of view all is well and the case can be closed. Sorry for any inconvenience.
(In reply to rettuas@web.de from comment #5) > New finding > After a new kernel update I rebooted my Fedora33 system and miraculously I > do not experience any worries regarding password protection anymore. > The update was from kernel 5.9.14-200.fc33.x86_64 to kernel > 5.9.15-200.fc33.x86_64. Accompanying the kernel updates there were other > included updates, of which I would have to research. > I cannot trace if it was the kernel update, other updates, or solely the > reboot. > If you need further information on the updates that I carried out in the > meantime which could have led to the cure, please provide me with dnf > commands that you need for information. > From my user point of view all is well and the case can be closed. Sorry for > any inconvenience. good to hear. Let's close this as RESOLVED NOTOURBUG