Issue still present in LibO 6.4.3.1.
I see the bug as still unconfirmed after more than one year. I wonder if it could be confirmed, given that the same issue has also been reported for redhat (https://bugzilla.redhat.com/show_bug.cgi?id=1581879)
Issue still present in LibO 6.4.3.1.
I see the bug as still unconfirmed after more than one year. I wonder if it could be confirmed, given that the same issue has also been reported for redhat (https:/ /bugzilla. redhat. com/show_ bug.cgi? id=1581879)