Bug 139189 - PDF signing does not work with SolidWorks files
Summary: PDF signing does not work with SolidWorks files
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
6.0.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: implementationError
Depends on:
Blocks: Digital-Signatures
  Show dependency treegraph
 
Reported: 2020-12-23 14:54 UTC by StV5303
Modified: 2024-09-08 03:16 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
Example file that resist signing (40.52 KB, application/pdf)
2020-12-23 14:59 UTC, StV5303
Details

Note You need to log in before you can comment on or make changes to this bug.
Description StV5303 2020-12-23 14:54:26 UTC
Description:
Digital signing does not work for PDFs produced by SolidWorks. Works fine for any other PDFs that I have.

Steps to Reproduce:
1) Menu File - Open - Digital Signatures - Sign an existing PDF
2) Select a PDF produced by SolidWorks. The file opens in DRAW, with 2 buttons in info bar: Edit document and Sign document.
3) Click on Sign document. The Digital signatures dialog opens.
4) Click on Sign document. The Select certificate dialog opens.
5) Select the certificate, click OK

Actual Results:
Nothing happens.

Expected Results:
The document should be signed.


Reproducible: Always


User Profile Reset: No



Additional Info:
Archlinux
Version: 7.0.4.2
Build ID: 00(Build:2)
CPU threads: 6; OS: Linux 5.9; UI render: default; VCL: gtk3
Locale: ru-RU (ru_RU.UTF-8); ИП: ru-RU
7.0.4-1
Calc: CL
Comment 1 StV5303 2020-12-23 14:59:10 UTC
Created attachment 168453 [details]
Example file that resist signing

I cleared it with Metadata anonymisation toolkit.
Some original metainfo:
    CreatorTool: SOLIDWORKS 2018 SP5.0 (2018316)
    Producer: SOLIDWORKS PDF Publisher
    creator: SOLIDWORKS 2018 SP5.0 (2018316)
    format: PDF-1.4
    producer: SOLIDWORKS PDF Publisher
Comment 2 Timur 2022-09-08 14:52:30 UTC
Repro 6.0 and 7.5+ in Windows.
Comment 3 QA Administrators 2024-09-08 03:16:33 UTC
Dear StV5303,

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 https://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://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug