If you Export in pdf hybrid with Signature with watermark, when it reopens there isn't flag.
Steps to Reproduce:
1.Create New Document;
2.File ->Export on format pdf,
3.Tab Generallabel watermark ->Signature with watermark->Insert Text ->”Confidencial”;
4.Label General->Check pdf Hybrid;
8.File ->Export on Format Pdf;
When it reopens there isn't flag.
On label General->Flag Signature with Watermark and text "Confidencial".
User Profile Reset: No
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
I can confirm that behavior in Linux too.
Build ID: 8672113ead4e403c55e31b1d9a3d1e0f3b299577
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk2;
Locale: it-IT (it_IT.UTF-8); Calc: group
Can you provide a sample document, to make easier and clearer this issue?
Created attachment 133729 [details]
I don't believe there is something visible in the file itself, but here it is :)
Moreover I've seen it's not necessary to close and reopen the document: if you just go to "Export as PDF" in the very next moment of a such exportation, you already won't find the watermark CheckBox flagged nor its text again.
I didn't try with other PDF options, but imagine to be working on a document for some days, and now and then you have to export it to let it evaluate to an external consultant or so. Everytime you should enable watermark and write its text...
Not blocking, obviously, but surely boring :)
Finally, you'll get the same behavior if saving in ODT as well.
Created attachment 133730 [details]
Few seconds of video may be more effective than many words :)
Dear Bug Submitter,
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:
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!
Dear Bug Submitter,
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