Created attachment 130048 [details]
details from bibisect-41max
(0) Download test.odt attached to tdf#104795.
(1) Open test.odt from the command line. Program displays Writer
(2) Take menu options File > Properties and navigate to tab General.
Program displays dialog Properties with property "Digitally
Observed : The time of digital signature is 00:00:00.
Expected : The time of Digital Signature should be 23:06:31.
Alternatively, the time should not be shown at all.
Note for comparison that the time of day of the signature is included
in dialog "Digital Signatures" accessible via the button <Digital
Signatures> on this tab or via menu options File > "Digital
I see this behaviour in daily build
Build ID: ea860d52ade14b4a16289c81a0f8586799c6617f
CPU Threads: 2; OS Version: Linux 4.8; UI Render: default; VCL: x11;
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master,
Locale: en-CA (en_CA.utf8); Calc: group
and in a range of about 14 commits in bibisect-41max:
commit s-h date
-------- -------- -------------------
good b0245924 5aaaf069 2013-04-18 19:03:10
bad aee0ea18 824caac7 2013-04-18 21:29:29
I am setting keywords regression, bibisected.
Setting importance minor because this seems to be the only bug report
in 3-1/2 years.
Adding keyword needsDevEval, just a guess that this might not be too
hard to fix.
Do not worry about the !!br0ken!! email address in tab General: it has
already been reported in tdf#104795.
After ignoring the assertion failures reported in tdf#105011, I also
see the zero time-of-day in
Build ID: 0c565095983b0cc8b96a78012c611b7a03962204
CPU Threads: 2; OS Version: Windows 6.0; UI Render: default;
TinderBox: Win-x86@39, Branch:master, Time: 2016-12-16_01:40:04
Locale: en-CA (en_CA); Calc: group
so I am setting O/S = All.
Confirmed with same steps in:
LO 22.214.171.124.alpha0+ Build ID: 5903235d57acb13d9d5286d23b443a01aeab9a3c
CPU Threads: 2; OS Version: Windows 6.1; UI Render: default;
TinderBox: Win-x86@42, Branch:master, Time: 2016-12-19_00:08:35
Locale: fr-FR (fr_FR); Calc: CL
and Windows 7 Home.
All my wishes for this new year,
I do not know how to map source hash 5aaaf069 to a LibreOffice version
number, but I think that current master cannot be right.
(In reply to Terrence Enger from comment #4)
> I do not know how to map source hash 5aaaf069 to a LibreOffice version
> number, but I think that current master cannot be right.
oh, I didn't read this part: and in a range of about 14 commits in bibisect-41max...
Probably regression from 9830fd36dbdb72c79703b0c61efc027fba793c5a
Regression introduced in range https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=5aaaf0694b6e3213685563fc3bc90d19b10f5c75..824caac79d983ad1aa93a6ec51558d7edb6f2a7d
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
still repro in LO 126.96.36.199
reproducible with LO 188.8.131.52 but no longer with:
Version: 184.108.40.206 (x64)
Build ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win;
Locale: de-DE (de_DE); UI-Language: en-US
I too see the expected time of signature in local build of master from
2019-07-15. I am setting status VERIFIED WORKSFORME.