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

2013-06-15 Thread Antos Andras
Version 1:3.5.4+dfsg2-0+deb7u2 in wheezy works well. Thanks you for the fix. Andras -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

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

2013-04-05 Thread Rene Engelhard
On Wed, Apr 03, 2013 at 08:57:51PM +0200, Antos Andras wrote: I hope the fixed 3.6.2 version gets in testing or stable soon. testing? Yes, when I upload it (well, 4.x most probably) after wheezy release. stable? For sure with jessie in ~3 years... (but I might *try* to get the fix[1] into a

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

2013-04-05 Thread Antos Andras
On Fri, 5 Apr 2013, Rene Engelhard wrote: I might *try* to get the fix[1] into a stable update which is needed anyway due to other stuff which missed the time in before it became impossible to to do it (see #703602). And it'll be in wheezy-backports... That is great. Thanks for your work.

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

2013-04-03 Thread Antos Andras
Package: libreoffice-common Version: 1:3.5.4+dfsg-4 Followup-For: Bug #681185 I just confirm this bug. As a consequence, it is also impossible to open two office attachments from alpine after each other. I hope the fixed 3.6.2 version gets in testing or stable soon. Regards, Andras Antos --

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

2012-07-12 Thread Matthias Urlichs
Hi, Rene Engelhard: $ 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... Doesn't matter. Maybe the user is editing the next Great American Novel at the time; the point is that LO is

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

2012-07-12 Thread Rene Engelhard
On Thu, Jul 12, 2012 at 09:03:12AM +0200, Matthias Urlichs wrote: I *think* it's ooplash.bins fault. This is not a splash screen problem. Wrong. soffice(.sh) calls oosplash.bin. $ tail -n 2 /usr/bin/soffice # oosplash does the rest: forcing pages in, javaldx etc. are exec $VALGRINDCHECK

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

2012-07-12 Thread Rene Engelhard
On Thu, Jul 12, 2012 at 10:27:23AM +0200, Rene Engelhard wrote: I *think* it's ooplash.bins fault. This is not a splash screen problem. Wrong. soffice(.sh) calls oosplash.bin. $ tail -n 2 /usr/bin/soffice # oosplash does the rest: forcing pages in, javaldx etc. are exec

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

2012-07-12 Thread Matthias Urlichs
Hi, Rene Engelhard: On Thu, Jul 12, 2012 at 09:03:12AM +0200, Matthias Urlichs wrote: I *think* it's ooplash.bins fault. This is not a splash screen problem. Wrong. soffice(.sh) calls oosplash.bin. Unfortunately, the name oosplash.bin strongly suggests to people that its main

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

2012-07-11 Thread Matthias Urlichs
Package: libreoffice Version: 1:3.5.4-5 Severity: normal This sequence often fails: $ libreoffice $ libreoffice /tmp/something.odt; rm /tmp/something.odt This is because the second command signals LO to open the document and then returns immediately, instead of waiting for the file to be

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

2012-07-11 Thread Rene Engelhard
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