On Fri, Jul 27, 2012 at 6:08 PM, Jürgen Schmidt <[email protected]> wrote: > On 7/27/12 12:03 PM, Jürgen Schmidt wrote: >> On 7/27/12 11:18 AM, zhangjf wrote: >>> On Fri, Jul 27, 2012 at 4:35 PM, Jürgen Schmidt >>> <[email protected]> wrote: >>>> On 7/27/12 5:24 AM, Yan Ji wrote: >>>>> It's really a serious problem and regress since last build. So I propose >>>>> it as release blocker. Anyone will take look this bug? >>>>> >>> >>>> >>>> yes it is indeed a blocker issue. Have you test or verified this issue >>>> on trunk as well? >>>> >>>> Juergen >>>> >>> >>> As I remember, it doesn't work on trunk as well. >> >> mmh, really, seems that I have missed this. That's of course even more >> worse because I thought the issue is fixed trunk as well. >> > > Ok I was confused and mixed it with > https://issues.apache.org/ooo/show_bug.cgi?id=119366 > > I remembered that we had fixed a problem with passwords but this is of > course a different problem ... > > Seems to be a useful test case for our automated GUI testing. Creating a > document - save with password - close and load again. >
+100. It is definitely the case which automation and BVT test can cover, so to report regression bugs earlier. zhangjf > Juergen > >> Juergen >> >>> zhangjf >>> >>>> >>>>> Thanks & Best Regards, Yan Ji >>>>> >>>>> On Jul 27, 2012, at 9:41 AM, [email protected] wrote: >>>>> >>>>>> Yan Ji <[email protected]> has asked for 3.4.1_release_blocker: >>>>>> Bug 120385: [Regression]Fail to load and save document with password >>>>>> https://issues.apache.org/ooo/show_bug.cgi?id=120385 >>>>>> >>>>>> >>>>>> ------- Additional Comments from Yan Ji <[email protected]> >>>>>> Build: AOO 3.4.1_r1365887 >>>>>> OS: All >>>>>> >>>>>> Steps: >>>>>> 1. Launch AOO and new Text Document >>>>>> 2. Input some content >>>>>> 3. Save the document with password >>>>>> >>>>>> Defect: An error dialog popup said >>>>>> Error saving the document Untitled 1: >>>>>> General Error. >>>>>> General input/output error. >>>>>> >>>>>> Note if open a document with password a dialog said the document is >>>>>> corrupt. >>>>>> Please refer to the snapshot. >>>>>> >>>>>> This problem doesn't exist in last 3.4.1 build rev 1364591 >>>>> >>>>> >>>> >> >
