Bug 119973 - OOXML: Signed Signature Line EMF has black background in Windows GDI and Linux GTK3
Summary: OOXML: Signed Signature Line EMF has black background in Windows GDI and Linu...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.1.0.0.beta1+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:emf
Depends on:
Blocks: Digital-Signature-Lines
  Show dependency treegraph
 
Reported: 2018-09-19 06:22 UTC by Samuel Mehrbrodt (allotropia)
Modified: 2022-10-29 03:38 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
screenshot (11.66 KB, image/png)
2018-09-19 06:22 UTC, Samuel Mehrbrodt (allotropia)
Details
bugdoc (7.70 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2018-11-13 10:49 UTC, Samuel Mehrbrodt (allotropia)
Details
budgoc (196.57 KB, application/vnd.oasis.opendocument.graphics)
2018-11-15 08:01 UTC, Samuel Mehrbrodt (allotropia)
Details
image.emf (177.25 KB, image/emf)
2018-11-15 08:33 UTC, Samuel Mehrbrodt (allotropia)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Samuel Mehrbrodt (allotropia) 2018-09-19 06:22:26 UTC
Created attachment 145007 [details]
screenshot

After signing a signature line in ooxml, the background turns black (see attached screenshot).

This is probably a result of converting SVG to EMF for OOXML.
Comment 1 Bartosz 2018-10-01 19:53:38 UTC
Please provide sample document where problems occur, and step by step instruction how to reproduce the issue.
Comment 2 Samuel Mehrbrodt (allotropia) 2018-11-13 10:49:13 UTC
1. Open attached document
2. Right click on the signature line, "Sign signature line"
3. Fill in your name, select a certificate, click "Sign"

Expected: Signature line is signed and has a transparent background.
Actual: Signature line is signed, but background is black (makes it unreadable)
Comment 3 Samuel Mehrbrodt (allotropia) 2018-11-13 10:49:28 UTC Comment hidden (obsolete)
Comment 4 Samuel Mehrbrodt (allotropia) 2018-11-14 14:42:01 UTC
This is merely a display problem in LO. When opening the emf file in Word, the image is shown correctly.
Comment 5 Samuel Mehrbrodt (allotropia) 2018-11-15 08:01:15 UTC
Created attachment 146646 [details]
budgoc

Attaching new bugdoc including an affected emf file.
No need to sign the document, just open this file to see the problem.
Comment 6 Samuel Mehrbrodt (allotropia) 2018-11-15 08:33:36 UTC
Created attachment 146648 [details]
image.emf
Comment 7 Samuel Mehrbrodt (allotropia) 2019-01-23 11:58:23 UTC
Found out that this only happens in debug mode.
Comment 8 Timur 2020-10-28 08:39:08 UTC
Repro Win LO 6.1 and 6.2 OpenGL, no repro 6.2 GDI, repro 7.1+ GDI, no repro Skia.
Repro GTK3, no repro Skia and GEN in Linux GTK3.
Comment 9 QA Administrators 2022-10-29 03:38:48 UTC
Dear Samuel Mehrbrodt (CIB),

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