Bug#681185: libreoffice: Opening a document when LO is already running returns too early

[Rene Engelhard <rene@debian.org>]

Hi,

On Fri, Jul 06, 2012 at 10:32:26AM +0200, Matthias Urlichs wrote:
> This sequence often fails:
> 
> $ libreoffice &
> $ libreoffice /tmp/something.odt; rm /tmp/something.odt

And why are you doing that then? Sorry, I'd understand it in the second
case, but...

What happens without that first "libreoffice &"?

> This is because the second command signals LO to open the document and then
> returns immediately, instead of waiting for the file to be actually opened.

Of course it tells the already running process to open the file. What else?
There is _no_ "different libreoffice instances".

> This is bad because some email programs open attachments that way (mutt for   
> instance). In effect, I cannot open an LO attachment from within mutt;        
> instead I have to store it to /tmp  and then open it, manually. 

I *think* it's ooplash.bins fault. In OOo times we had a patch which
prevented this by inventing a new option -no-oosplash (used in .mime)
which we didn't take over for LO apparently.

And now it's too late for wheezy so it'll probably be only fixed for
wheezy+1...

Regards,

Rene