Description: For more details see attached document (including screenshots)! I am using Ubuntu 18.04.1 with LO Version: 6.0.7.3 I have been using seahorse to generate a new pgp-key The Password I selected here was AundO_0-9. I opened a little docum.odt containing some text and saved it with encryption I press save I am offered certificates I select the certificat created before and press encrypt. Now I have the following files: I close LO-window with docu.pgp.odt, I try to reopen docum-pgp. I am prompted for a password. I enter the password given for passphrase „AundO_0-9“ but alas this is not accepted. I use again seahorse, select the certificate and try to change the passphrase. I do not get an error when I give „AundO_0-9“ for current passphrase and I am allowed to enter (twice) a new passphrase – so i think I verified the password. What is wrong? Steps to Reproduce: 1. see description and attached file 2. 3. Actual Results: unable to reopen encrypted file Expected Results: file should be open for processing Reproducible: Always User Profile Reset: No Additional Info: I was not able to search the bug database today - I did report that to the webmaster...:-( Version: 6.0.7.3 Build ID: 1:6.0.7-0ubuntu0.18.04.8 CPU threads: 4; OS: Linux 4.18; UI render: default; VCL: gtk3; Locale: de-DE (en_US.UTF-8); Calc: group
Created attachment 152994 [details] step by step instructions including screenshots
Heinrich, 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 tried to update. Ubuntu updater clearly states that there is no newer Software available for LO in the ubuntu repositories. Unfortunately I am not very familiar with updates bypassing ubuntu. May I ask you to try to reproduce the bug based on the evidence that the misbehaviour was found in the latest LO version released to the ubuntu community?
Heinrich, do you use a newer version of LO now, so you're a le to retest now. Unfortunately it seems that nobody else could reproduce your problem. 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 Heinrich Hartl, 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
I am responding late to need info. But I was expecting a new LO-Version with the next Ubuntu LTS Version. 20.04.1 is out now but is still not offered for do release-upgrade. SO I decided to set up a dedicated newly installed Ubuntu 20.04.1 Laptop to reproduce the bug. Unfortunately the bug seems to persist with LO 6.4.4.2 part of Ubunto 20.04.1.
Created attachment 164541 [details] Instructions to reproduce bug with Ubuntu 20.04.1 and LO 6.4.4.2
Thank you for the report, Heinrich. I tested it with a recent build of master, and couldn't reproduce. Using Seahorse 3.36 on Ubuntu 20.04. The steps I used: 1. create new GPG key with Seahorse, using the same password you provided 2. create document in Writer, save with GPG encryption using the newly created key 3. close Writer 4. open the document again, fill in the password when prompted Results: I can open the file. Am I missing something in my steps? Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 1dd4a80fa076bedb3a82821517036bad8dd79857 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-07-26_22:41:19 Calc: threaded
(In reply to stragu from comment #8) > Am I missing something in my steps? => Status NEEDINFO > > Version: 7.3.0.0.alpha0+ / LibreOffice Community > Build ID: 1dd4a80fa076bedb3a82821517036bad8dd79857 > CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 > Locale: en-AU (en_AU.UTF-8); UI: en-US > TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: > 2021-07-26_22:41:19 > Calc: threaded Heinrich, could you please retest with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? Ypu also can try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/current.html You can install it alongside the standard version. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build.
Dear Heinrich Hartl, 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