We'd really appreciate your help in getting confirmation that the bug is still present.
During that time, it's possible that the bug has been fixed, or the details of the problem have changed. There have been thousands of bug fixes and commits since anyone checked on this bug report.
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. ** Please read this message in its entirety before responding ** If you find the regression point it will be easier to identify the root of the issue and have a fix 4.4.0, 4.3.0, 4.2.0) to find the first release that did show the bug. 4.4.5, 4.3.5, 4.2.6) until you find the first version that doesn't show the bug then move forward and test the first release of each branch (i.e. I suggest testing the last version of each branch (i.e. What you can do to speedup the fixing is testing the bug with older releases in order to know if the issue has always been present or if it's a regression bug (it worked fine in a previous release and became a bug in a newer one).Īnd download some older LibO portable versions and retest. > Will someone be looking at fixing it? Is there a timeline on it? When another user is able to reproduce it the status is set to NEW which means that the bug is confirmed. when you report a bug the status is UNCONFIRMED. > Is this officially recognized as a bug now? > I've not tried reporting an bug to LibreOffice before, so I have no idea (In reply to john cantin from comment #8)
0 kommentar(er)
