<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Print Preview crashes on signed document" href="https://bugs.documentfoundation.org/show_bug.cgi?id=117039#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Print Preview crashes on signed document" href="https://bugs.documentfoundation.org/show_bug.cgi?id=117039">bug 117039</a> from <a class="email" href="mailto:ftoth@telfort.nl" title="Ferry Toth <ftoth@telfort.nl>"> Ferry Toth</a> <pre>@Katerina I know how much testing is going on. But LibO is a big product, big testing is necessary. I don't want to offend any one, I think all bugs happen "apparently without sufficient testing". The question is how can we prevent these things from happening. What worries me that with each release bug reports explode. There was a time where there was a graph showing the number of open bugs... It's great that features get added and stuff gets improved. And I really appreciate all the work that goes into that. But there are people who actually *use* LibO and rely on existing functions to work. People who I convinced LibO is a better product than MS, who come to me to ask why it crashes when they click on the Print Preview button. And there seem to be areas (FileOpen dialog, e-mail merge, signing, pdf export, and with recent version even formatting of old documents that break when opening) where bugs appear at the same speed as they get fixed. Which is good and bad at the same time. (PS I don't think you want me to be your dude, I'm 51)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>