Invoking UNOPKG GUI in a command prompt under MS Windows, without having LibreOffice running and leaving it with the cancel button leaves a lock file in $(user)\LibreOffice\3 This lock file notifies LibreOffice that a second instance of LO is running, which is wrong. This lock file should be erased upon leaving UNOPKG GUI in ways of leaving it. Issue occurs in branch 3.5 as welll (tested in 3.5.4.2)
Hello Olivier, *, I can confirm it with Debian Testing AMD64 and LODev Version 3.6.0.0.beta3 (Build ID: 3e2b862) with installed Germanophone Lang as well as Help pack ... :( HTH Thomas.
Hello Olivier, *, still a problem with LO Version 3.6.0.2 (Build ID: 815c576) and installed Germanophone Help- as well as Lang pack under Debian Testing AMD64 ... :( I am changing the status to "New", so someone else will have a look at it ... ;) HTH Thomas.
*** Bug 51844 has been marked as a duplicate of this bug. ***
crashes in 3-6, looks good in 4-0. Seems that 37cc83e594fa8ca131fc5fb98506287b7daedffd fixes this. I'll hack up a stab at a 3-6 backport
Stephan Bergmann committed a patch related to this issue. It has been pushed to "libreoffice-3-6": http://cgit.freedesktop.org/libreoffice/core/commit/?id=547a3d8f98d0b3db0e0553edcab760b3a80ede51&g=libreoffice-3-6 Resolves: fdo#51638 In "unopkg gui" dispose component context from DeInitVCL It will be available in LibreOffice 3.6.5. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.