Re: openoffice.org 2.2.1 on amd64
From: Oliver Lehmann <[EMAIL PROTECTED]> Subject: Re: openoffice.org 2.2.1 on amd64 Date: Wed, 27 Jun 2007 06:10:18 +0200 > Maho NAKATA wrote: > > > From: Oliver Lehmann <[EMAIL PROTECTED]> > > Subject: openoffice.org 2.2.1 on amd64 > > Date: Mon, 25 Jun 2007 18:09:02 +0200 > > > > > after updating my installed openoffice from 2.2.0 to 2.2.1 I'm now left > > > with an openoffice installation where I'm not able to save files. > > > > I'm sorry to hear that... > > I'm updated gcc 4.1 to the latest version and recompiled oo.org 2.2.1 - > now i can save files... Congratulations! then this is a bug of gcc4.2... -- Nakata Maho ([EMAIL PROTECTED]) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: openoffice.org 2.2.1 on amd64
Maho NAKATA wrote: > From: Oliver Lehmann <[EMAIL PROTECTED]> > Subject: openoffice.org 2.2.1 on amd64 > Date: Mon, 25 Jun 2007 18:09:02 +0200 > > > after updating my installed openoffice from 2.2.0 to 2.2.1 I'm now left > > with an openoffice installation where I'm not able to save files. > > I'm sorry to hear that... I'm updated gcc 4.1 to the latest version and recompiled oo.org 2.2.1 - now i can save files... -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: openoffice.org 2.2.1 on amd64
From: Oliver Lehmann <[EMAIL PROTECTED]> Subject: openoffice.org 2.2.1 on amd64 Date: Mon, 25 Jun 2007 18:09:02 +0200 > after updating my installed openoffice from 2.2.0 to 2.2.1 I'm now left > with an openoffice installation where I'm not able to save files. I'm sorry to hear that... > Everytime I try to save a file openoffice exits leaving a 0 byte file. > Do you intend to fix this? I'll now go and try to move back to 2.2.0 > which worked if it wouldn't take ages to compile... *SIGH* :( Currently my amd64 box is occupied...and even so I cannot check it because it is too tough. Your input is really appreciated. Thanks, -- Nakata Maho ([EMAIL PROTECTED]) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: openoffice.org 2.2.1 on amd64
On Monday 25 June 2007 19:09:02 Oliver Lehmann wrote: > Hi, > > after updating my installed openoffice from 2.2.0 to 2.2.1 I'm now left > with an openoffice installation where I'm not able to save files. > > Everytime I try to save a file openoffice exits leaving a 0 byte file. > Do you intend to fix this? I'll now go and try to move back to 2.2.0 > which worked if it wouldn't take ages to compile... *SIGH* I just tried this on my amd64/6-STABLE from a couple of days ago, and file saves are working fine here, at least the 4 or 5 I just tried. Andy -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] "In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates." -- anon | [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: openoffice.org 2.2.1 on amd64
Gary Jennejohn wrote: > Doesn't help. I also see that, when I ^Q out of e.g. swriter that the > window disappears but the process doesn't exit. I have to ^C out of > it. Here the window disappears, and the process is gone... -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: openoffice.org 2.2.1 on amd64
On Mon, 25 Jun 2007 18:41:16 +0200 "[LoN]Kamikaze" <[EMAIL PROTECTED]> wrote: > Oliver Lehmann wrote: > > Hi, > > > > after updating my installed openoffice from 2.2.0 to 2.2.1 I'm now > > left with an openoffice installation where I'm not able to save > > files. > > > > Everytime I try to save a file openoffice exits leaving a 0 byte > > file. Do you intend to fix this? I'll now go and try to move back > > to 2.2.0 which worked if it wouldn't take ages to compile... > > *SIGH* > > > > Greetings, Oliver > > > > Did you try the workaround for OO instabilities mentioned in previous > threads? > > OO_FORCE_DESKTOP=none or OO_FORCE_DESKTOP=kde > > in the environment. Doesn't help. I also see that, when I ^Q out of e.g. swriter that the window disappears but the process doesn't exit. I have to ^C out of it. --- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: openoffice.org 2.2.1 on amd64
Oliver Lehmann wrote: > Hi, > > after updating my installed openoffice from 2.2.0 to 2.2.1 I'm now left > with an openoffice installation where I'm not able to save files. > > Everytime I try to save a file openoffice exits leaving a 0 byte file. > Do you intend to fix this? I'll now go and try to move back to 2.2.0 > which worked if it wouldn't take ages to compile... *SIGH* > > Greetings, Oliver > Did you try the workaround for OO instabilities mentioned in previous threads? OO_FORCE_DESKTOP=none or OO_FORCE_DESKTOP=kde in the environment. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
openoffice.org 2.2.1 on amd64
Hi, after updating my installed openoffice from 2.2.0 to 2.2.1 I'm now left with an openoffice installation where I'm not able to save files. Everytime I try to save a file openoffice exits leaving a 0 byte file. Do you intend to fix this? I'll now go and try to move back to 2.2.0 which worked if it wouldn't take ages to compile... *SIGH* Greetings, Oliver -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
