On Wed, Dec 11, 2013 at 4:00 PM, Terrence Enger <ten...@iseries-guru.com> wrote:
> Several times along the way, I have resorted to the extreme measure of
> deleting the directory with the bibisect repository and extracting it
> again from the tarfile. That is perhaps the ultimate repair.
Yes, that is the most drastic approach :-) In most cases we hopefully
can avoid needing to take that step!
Many of the bibisect woes that we've encountered in the past have been
tracked back to interactions with other running instances of soffice
(often touching the same user profile). Things I would try include
- Shutting down all versions of Libre/Open Office
- Checking again ("ps aux|grep "office")
- Restarting the computer
To avoid these types of interactions in the future, I suggest using a
wrapper script (not checked-in, but located in the same directory as
the bibisect repo). Here's one I cooked up based on Miroslaw's
suggestions (I'm in the process of getting it added to the buildbot
repo):
http://testing.eagleeyet.net/~qubit/bibisect/run-libreoffice.sh
Cheers,
--R
_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
