Bug 54280 - Graphic background to frame
Summary: Graphic background to frame
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.6.1.2 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-30 19:14 UTC by echarpie3
Modified: 2014-02-02 02:00 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Document described in description (2.81 MB, application/vnd.oasis.opendocument.text)
2012-08-30 19:14 UTC, echarpie3
Details
Version 4 pdf Printout (Page 1 only) (1.59 MB, application/pdf)
2013-05-19 16:34 UTC, Joel Madero
Details
Version 3.6.0.0.alpha1 Printout (1.59 MB, application/pdf)
2013-05-19 16:35 UTC, Joel Madero
Details

Note You need to log in before you can comment on or make changes to this bug.
Description echarpie3 2012-08-30 19:14:06 UTC
Created attachment 66368 [details]
Document described in description

When a graphic is placed within a frame and transparency is set at 75% the graphic does not render correctly at 100% view and does not print correctly. It looks as if it has interference from other graphics on the page or other frames within the frame. An example document is attached.  We upgraded from ver. 3.3 to 3.6. In 3.3 this document printed correctly. The cover page has a graphic as the background of the frame at 75% transparency and does not render at 100% view or print correctly.
Comment 1 Joel Madero 2013-05-19 16:29:47 UTC
Okay so what I did was I used 3.6 alpha and 4.0.3.3 release and opened the same document. I printed these to pdf - I see very slight differences but not sure what the real problem is.

Attached you'll see my two PDF's. I'm going to mark this as NEEDINFO - please let me know what I'm looking for (ie. what section of the document, and then what exact problem). Then mark the bug as UNCONFIRMED and I will try to triage the bug.

Thanks!
Comment 2 Joel Madero 2013-05-19 16:34:47 UTC
Created attachment 79530 [details]
Version 4 pdf Printout (Page 1 only)
Comment 3 Joel Madero 2013-05-19 16:35:24 UTC
Created attachment 79531 [details]
Version 3.6.0.0.alpha1 Printout
Comment 4 QA Administrators 2013-12-22 21:58:47 UTC
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 INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

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!


Warm Regards,
QA Team
Comment 5 QA Administrators 2014-02-02 02:00:42 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO