Hi all,
first of all, I apologize, because this does not seem to be a problem
with OOo, but merely with the configuration of our linux system. Still,
you might have a hint.
We use the OOoBean within a Java application, connecting through a named
pipe. When the connection is started OOo won't show in the Java frame.
After some timeout an ConnectionException get's thrown and another
soffice.bin process is getting started. The number of soffice.bin
processes increases. This happens right before the second OSL_Pipe....
file is created in /tmp.
The problem does not exist when I log in as root. So it obviously is
some kind of user restriction that causes this - but other applications
work. Even starting OOo as "normal user" is working.
Is there anybody who might give an hint?
Your help would be greatly appreciated
Cheers
Harald
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
