https://bugs.documentfoundation.org/show_bug.cgi?id=94677
--- Comment #9 from tommy27 <ba...@quipo.it> --- (In reply to john cantin from comment #8) > I've not tried reporting an bug to LibreOffice before, so I have no idea > what to expect. welcome on board :-) > Is this officially recognized as a bug now? yes. when you report a bug the status is UNCONFIRMED. when another user is able to reproduce it the status is set to NEW which means that the bug is confirmed. > Will someone be looking at fixing it? Is there a timeline on it? there's no timeline yet. 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). so I suggest going at this page: http://sourceforge.net/projects/winpenpack/files/X-LibreOffice/releases/ and download some older LibO portable versions and retest. I suggest testing the last version of each branch (i.e. 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. 4.4.0, 4.3.0, 4.2.0) to find the first release that did show the bug. if you find the regression point it will be easier to identify the root of the issue and have a fix -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
