The workaround worked for me too.
On a side note if i start /usr/lib/openoffice/program/soffice.bin -writer (or -impress, etc...), I get the error again.
Maybe what got bug is some permission inside the module(?) that launches an app directly. It apparently got blocked for the user that made the update only...
Maybe someone more experienced then me could look deeper into this?
I think the solution could be really close.
The workaround worked for me too. openoffice/ program/ soffice. bin -writer (or -impress, etc...), I get the error again.
On a side note if i start /usr/lib/
Maybe what got bug is some permission inside the module(?) that launches an app directly. It apparently got blocked for the user that made the update only...
Maybe someone more experienced then me could look deeper into this?
I think the solution could be really close.