Hi, On Fri, Sep 18, 2009 at 12:52:20PM +0200, Francesco Paolo Lovergine wrote: > Well, I found casually the same problem while upgrading to current > version. At least for me I had an OOo instance running _while_ doing > an upgrade (oowriter), with both a .doc and a native document open.
Of course that shoudldn't be done. > It crashed (just by pointing and clicking into the native document) > and then the postinst just succeeded. Some locking problem? Maybe. > Anyway I would be defensive and asking for closing ALL instances > of OOo while upgrading... Geeeee, a windows-style request, isn't it? When would you print such message? After the new version already is unpacked? In the preinst of whatever random OOo package? And should you fail then if soffice.bin is running? With your scanrio in the first paragraph, doing it like iceweasel after install is too late. In any case imho it should be obvious that it's safer to quit the app you are running *before* upgrading and that you *might* experience problems if you don't... Grüße/Regards, Rene -- .''`. René Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' r...@debian.org | GnuPG-Key ID: D03E3E70 `- Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70 -- To UNSUBSCRIBE, email to debian-openoffice-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
