Comment 8 for bug 457141

Leandro, regarding your comments:

> Incomplete? Nice. What a beautiful example of bug handling. Two years ago the bug is posted, and confirmed. Ignored for two years. Nothing is done.

Bug reporting is a two way street, and not, "set it and forget it". No upstream link was posted, you could have done that. BTW, I am a volunteer who recently (few weeks ago) started working with OOo and LibreOffice bugs on Launchpad.

> Then it is asked for the bug reporter to try another software.

LibreOffice 3.3.1 in it's current form is OOo 3.3.1 rebranded with a few updates and enhancements, as the sources are 90%+ the same. That is why it was suggested.

> The bug does not occur on MSOffice, so I think we can consider it fixed.

Done.

> I'm sorry for the sarcasm

Honestly, I think your sarcasm is funny because I've been there! :D

> but two years ago I was proudly reporting every bug I found

Your welcome to continue reporting bugs, if OOo or LibreOffice bugs are found, I'll be glad to try to reproduce them.

> and this is the kind of answer I systematically got. I'm not a professional Linux/Ubuntu supporter, but as a programmer I know that testing new versions of the software do not solve previous bugs if those were not specifically addressed.

It doesn't hurt to test for for this bug being addressed, in software that has gone from OOo 3.1.1 to LibreOffice 3.3.1, a monumental update. There are countless examples on Launchpad where someone's bug did get addressed in OOo by updating to LibreOffice.

Thanks for your efforts, I hope things continue to evolve, because as a professional linux user I need all this working fine. But clearly reporting bug is not the best way to help.

> If your a professional linux user it is clear this is not MSFT, anonymously report the problem, forget about it, and if one is within a statistical anomoly the issue may get addressed. This is in full view of the world, feel free to take advantage by taking a more active approach to bug reporting! :D

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!