@Vasant
please do not mess up old bug reports
as indicated int the whiteboard and in previous comments the bug has been fixed since LibO 4.3.5 so if you experience the bug with 4.2.8 is just because you are using an obsolete LibO version
you should upgrade to latest LibO 4.4.5 or 5.0.2 releases
setting back status and version fields to correct values
@Vasant
please do not mess up old bug reports
as indicated int the whiteboard and in previous comments the bug has been fixed since LibO 4.3.5 so if you experience the bug with 4.2.8 is just because you are using an obsolete LibO version
you should upgrade to latest LibO 4.4.5 or 5.0.2 releases
setting back status and version fields to correct values