To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=80816
------- Additional comments from [EMAIL PROTECTED] Thu Sep 20 20:22:26 +0000 2007 ------- This is a show stopper, folks--this should never have been released with such a major flaw. Sure, us geeks can get around it, but don't we want non-geeks to use OOo as well? And suggesting users disable security (other than for debugging) is a non-starter! This should be targeted for 2.3.1, and SHOULD have been fixed in 2.3.0. (How can I recommend anybody try OpenOffice.org when it won't run as installed?) With a little help from http://www.oooforum.org/forum/viewtopic.phtml?p=246394 I discovered that executing the following command (as root) in directory /opt/openoffice.org2.3/program is a work-around: chcon -t texrel_shlib_t *.so --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
