Date: Tue, 01 Jan 2008 14:21:43 -0600 From: Stephen Montgomery-Smith <stephen@math.missouri.edu> To: Predrag Punosevac <punosevac@math.arizona.edu> Cc: Philipp Ost <pj@smo.de>, "O. Hartmann" <ohartman@mail.zedat.fu-berlin.de>, freebsd-questions@freebsd.org, freebsd-ports@freebsd.org Subject: Re: Problems with OpenOffice 2.3.1 on FreeBSD Message-ID: <477AA0D7.6060905@math.missouri.edu> In-Reply-To: <477A9DDF.7000906@math.arizona.edu> References: <477A3CFC.8030204@mail.zedat.fu-berlin.de> <477A50BE.7090202@smo.de> <477A9DDF.7000906@math.arizona.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Predrag Punosevac wrote: > Philipp Ost wrote: >> O. Hartmann wrote: >> [...] >>> Whenever I try to save a document in OO writer, OO gets stuck and I >>> have to kill it. The document gets saved, but I never can load it >>> again without rendering OO unusuable. Opening M$ Word docs or OO docs >>> doesn't matter. >> >> I have similar problems with OpenOffice 2.3.1 on FreeBSD/i386 (I'm >> running 7.0-PRE as of Dec 23). It's possible to save documents but >> exiting OOo hangs and I need to kill it. Firing up OOo once again, >> there's this "recovery stuff" which hangs also and eats up CPU time. >> Only way out: kill -9 $PID >> Opening a document via 'File -> Open -> ...' hangs also. .odt or .doc >> doesn't matter. >> >> >>> Any ideas? This is a serious situation to me, due to the need of a >>> properly working OO :-( >> >> No, perhaps using an other word processor (AbiWord, StarOffice). Or >> going back to OOo 2.3.0... >> >> >> Regards, >> Philipp >> _______________________________________________ >> freebsd-ports@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" > I am not an OpenOffice user but my 2c about the topic as the problem I > think underline more serous issue. > > The question is why is OpenOffice 2.3.1 included in the ports three so > quickly without making sure that things work properly. > BSD systems are genuinely known for their stability and code correctness > which is why most people decided to use them on the first place. > Rushing to include new software in the ports three without proper > testing is seriously going to damage usability of the whole OS. > In my understanding ports tree is supporting stable and the current > brunch. I am of the opinion that the ports three of the stable > branch should not include nothing but the rock solid and tested > software. The easiest way for me to check if the port is bleeding > edge that is to try to install the same software using binaries. > (pkg_add -r) If the binaries do not exist or if the version installed > from binaries is older that clearly indicates that the port version is > too new to be trusted. > > I personally found out that Xfce4-panel is not compiling properly on > stable and also Orage (calendar for Xfce) While > problems with Xfce4-panel are not as serious as with Orage (which is > not usable in any shape or form on FreeBSD) they are still serious. > The same packages work flawlessly on the OpenBSD. The problem is that ports is maintained by volunteers who are mostly outside of any kind of freebsd core team. I think it is unrealistic to ask port committers to check anything more than to check that the ports build properly. My personal wish list is that opencascade builds on FreeBSD-7 with the new stlport, and that octave-forge not be in its current "IGNORE" state. But I fully appreciate that I must either wait, or help make it happen. Stephen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?477AA0D7.6060905>