Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

Just to report back on this, the bug was identified as a duplicate, but, it looks like it helped with resolving the issue and it will be fixed in an upcoming update to the 4.0.x branch.

Thanks to the users on this list as well as the devs who worked on getting it fixed! Big thanks also for the user(s) who submitted files for the devs to test with, this goes a long way in helping getting bugs fixed quicker.

Just a reminder that we could use all the help possible in QA (quality assurance) to help in the bug reporting process. If you are interested, join the QA list, there are many different types of tasks that can be easily done by volunteers and some not that time-consuming. You can find out more about QA here:



Thanks Mark for promoting the team - we can definitely still use the help. That site doesn't even list everything that we have going on. Whether you have programming skills or not - we have plenty of things that need done, everything from basic wiki cleanup to helping improve our bug submission assistant and more technical things like automating unit tests.

Remember we have a North America QA casual chat this Friday at noon PST (UTC - 7) - if you're in N. America and have 5-10 minutes a week even to do minor tasks - please join us on freenode @


To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.