Bug 75071

Created attachment 94181 [details]
My monthly income

Will not print correctly and recepient cannot open

Hi, document opens fine for me and prints fine too.

Is this bug still valid / reproducible with the latest LO release?  Currently 4.2.0.4: http://www.libreoffice.org/download/

Please also try resetting your user profile and let us know if that helps: https://wiki.documentfoundation.org/UserProfile

Should this be still reproducible for you with the latest LO release please set this bug back to UNCONFIRMED. Should this issue be solved set it to WORKSFORME.

Setting to NEEDINFO until more detail is provided. Make sure to give LO version (also make sure to try out the latest release), Operating system, printer model and all the details needed to reproduce this problem.

THANK YOU FOR A QUICK RESPONSE
MY PROBLEM HAS BEEN RECTIFIED. AFTER READING INFORMATION ON MY HP PRINTER
IT WAS SUGGESTED TO CLEAN CARTRIDGES THAT BECOME CLOGGED.I PROCEEDED WITH
THIS METHOD AND APPARENTLY THAT WAS MY PROBLEM WHICH I NEVER ENCOUNTERED
BEFORE
THANK YOU


On Mon, Feb 17, 2014 at 2:42 AM, <bugzilla-daemon@freedesktop.org> wrote:

>  Foss <foss@openmailbox.org> changed bug 75071<https://bugs.freedesktop.org/show_bug.cgi?id=75071>
>  What Removed Added  Status UNCONFIRMED NEEDINFO  Summary RECEPIENT
> CANNOT OPEN Recipient can't open document, printing problems as well  Ever
> confirmed   1
>
>  *Comment # 2 <https://bugs.freedesktop.org/show_bug.cgi?id=75071#c2> on
> bug 75071 <https://bugs.freedesktop.org/show_bug.cgi?id=75071> from Foss
> <foss@openmailbox.org> *
>
> Hi, document opens fine for me and prints fine too.
>
> Is this bug still valid / reproducible with the latest LO release?  Currently4.2.0.4: http://www.libreoffice.org/download/
>
> Please also try resetting your user profile and let us know if that helps:https://wiki.documentfoundation.org/UserProfile
>
> Should this be still reproducible for you with the latest LO release please set
> this bug back to UNCONFIRMED. Should this issue be solved set it to WORKSFORME.
>
> Setting to NEEDINFO until more detail is provided. Make sure to give LO version
> (also make sure to try out the latest release), Operating system, printer model
> and all the details needed to reproduce this problem.
>
>  ------------------------------
> You are receiving this mail because:
>
>    - You reported the bug.
>
>

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

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