From owner-freebsd-openoffice@FreeBSD.ORG Sun Dec 5 11:02:33 2004 Return-Path: Delivered-To: freebsd-openoffice@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DB8B16A4CE for ; Sun, 5 Dec 2004 11:02:33 +0000 (GMT) Received: from quark.rcac.purdue.edu (quark.rcac.purdue.edu [128.210.189.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E7FF43D66 for ; Sun, 5 Dec 2004 11:02:32 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from quark.rcac.purdue.edu (localhost [127.0.0.1]) iB5B2WHJ020016 for ; Sun, 5 Dec 2004 06:02:32 -0500 (EST) (envelope-from linimon@FreeBSD.org) Date: Sun, 5 Dec 2004 06:02:32 -0500 (EST) Message-Id: <200412051102.iB5B2WHJ020016@quark.rcac.purdue.edu> From: linimon@FreeBSD.org To: openoffice@FreeBSD.org Subject: FreeBSD ports that you maintain which are currently marked broken X-BeenThere: freebsd-openoffice@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting OpenOffice to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 11:02:33 -0000 Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we are attempting to notify maintainers of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc3.3, which is much stricter about such things as function declarations, literal strings constants that continue over several physical lines, and forcing the deprecation of antique header files such as varargs.h (we should now be using stdargs.h). The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. If you need help in one or more build environments that you do not have access to, please ask for help on the freebsd-ports mailing list. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The build errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 4.x/5.x/6.x with target architecture'.) (Note: the dates are included to help you to gauge whether or not the build error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: chinese/openoffice-1.0-zh_CN broken because: Does not compile on FreeBSD >= 5.x build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=chinese&portname=openoffice-1.0-zh_CN portname: chinese/openoffice-1.0-zh_TW broken because: Does not compile on FreeBSD >= 5.x build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=chinese&portname=openoffice-1.0-zh_TW portname: editors/ooodict-all broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=ooodict-all portname: editors/ooodict-bg_BG broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=ooodict-bg_BG portname: editors/ooodict-ca_ES broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=ooodict-ca_ES portname: editors/ooodict-cs_CZ broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=ooodict-cs_CZ portname: editors/ooodict-da_DK broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=ooodict-da_DK portname: editors/ooodict-el_GR broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=ooodict-el_GR portname: editors/ooodict-en_CA broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=ooodict-en_CA portname: editors/ooodict-en_GB broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=ooodict-en_GB portname: editors/ooodict-en_US broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=ooodict-en_US portname: editors/ooodict-es_ES broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=ooodict-es_ES portname: editors/ooodict-hr_HR broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=ooodict-hr_HR portname: editors/ooodict-it_IT broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=ooodict-it_IT portname: editors/ooodict-nl_NL broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=ooodict-nl_NL portname: editors/ooodict-sk_SK broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=ooodict-sk_SK portname: editors/ooodict-sv_SE broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=ooodict-sv_SE portname: editors/openoffice-1.0 broken because: Does not compile on FreeBSD >= 5.x build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=openoffice-1.0 portname: editors/openoffice-1.0-ar broken because: Does not compile on FreeBSD >= 5.x build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=openoffice-1.0-ar portname: editors/openoffice-1.0-dk broken because: Does not compile on FreeBSD >= 5.x build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=openoffice-1.0-dk portname: editors/openoffice-1.0-es broken because: Does not compile on FreeBSD >= 5.x build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=openoffice-1.0-es portname: editors/openoffice-1.0-gr broken because: Does not compile on FreeBSD >= 5.x build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=openoffice-1.0-gr portname: editors/openoffice-1.0-it broken because: Does not compile on FreeBSD >= 5.x build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=openoffice-1.0-it portname: editors/openoffice-1.0-nl broken because: Does not compile on FreeBSD >= 5.x build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=openoffice-1.0-nl portname: editors/openoffice-1.0-se broken because: Does not compile on FreeBSD >= 5.x build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=openoffice-1.0-se portname: editors/openoffice-1.0-tr broken because: Does not compile on FreeBSD >= 5.x build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=openoffice-1.0-tr portname: editors/openoffice-2.0-devel broken because: Bison 1.875a or newer is required, and doesn't work atm build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=editors&portname=openoffice-2.0-devel portname: french/ooodict-fr_FR broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=french&portname=ooodict-fr_FR portname: french/openoffice-1.0 broken because: Does not compile on FreeBSD >= 5.x build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=french&portname=openoffice-1.0 portname: german/ooodict-de_CH broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=german&portname=ooodict-de_CH portname: german/ooodict-de_DE broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=german&portname=ooodict-de_DE portname: german/openoffice-1.0 broken because: Does not compile on FreeBSD >= 5.x build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=german&portname=openoffice-1.0 portname: hungarian/ooodict broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=hungarian&portname=ooodict portname: japanese/openoffice-1.0 broken because: Does not compile on FreeBSD >= 5.x build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=japanese&portname=openoffice-1.0 portname: korean/openoffice-1.0 broken because: Does not compile on FreeBSD >= 5.x build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=korean&portname=openoffice-1.0 portname: polish/ooodict_PL broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=polish&portname=ooodict_PL portname: polish/openoffice-1.0 broken because: Does not compile on FreeBSD >= 5.x build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=polish&portname=openoffice-1.0 portname: portuguese/ooodict-pt_BR broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=portuguese&portname=ooodict-pt_BR portname: portuguese/ooodict-pt_PT broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=portuguese&portname=ooodict-pt_PT portname: portuguese/openoffice-1.0 broken because: Does not compile on FreeBSD >= 5.x build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=portuguese&portname=openoffice-1.0 portname: russian/ooodict-ru_RU broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=russian&portname=ooodict-ru_RU portname: russian/openoffice-1.0 broken because: Does not compile on FreeBSD >= 5.x build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=russian&portname=openoffice-1.0 portname: ukrainian/ooodict-uk_UA broken because: Checksum mismatch build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=ukrainian&portname=ooodict-uk_UA If these build errors are ones that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Every effort has been made to make sure that these build errors really do correspond to a port that you maintain. However, due to the fact that this is an automated process, it may indeed generate false matches. If one of these build errors fits that description, please forward this email to the author of this software, Mark Linimon , so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. From owner-freebsd-openoffice@FreeBSD.ORG Mon Dec 6 11:04:06 2004 Return-Path: Delivered-To: freebsd-openoffice@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D423C16A4CE for ; Mon, 6 Dec 2004 11:04:06 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2C8943D70 for ; Mon, 6 Dec 2004 11:04:06 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iB6B46qG028868 for ; Mon, 6 Dec 2004 11:04:06 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iB6B46fE028862 for openoffice@freebsd.org; Mon, 6 Dec 2004 11:04:06 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 6 Dec 2004 11:04:06 GMT Message-Id: <200412061104.iB6B46fE028862@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: openoffice@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-openoffice@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting OpenOffice to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 11:04:06 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- a [2003/05/11] ports/52068 openoffice portupgrade of editors/openoffice .org-1. a [2003/05/12] ports/52087 openoffice error while building japanese/openoffice o [2004/01/23] ports/61760 openoffice OpenOffice-1.1 still stalls in install on o [2004/03/24] ports/64678 openoffice openoffice 1.1 upgrade fails due to JDK c o [2004/05/31] ports/67413 openoffice OpenOffice 1.1 PDF Export is BROKEN o [2004/10/07] ports/72414 openoffice Precompiled el-openoffice-1.1.2_1 first t o [2004/11/29] ports/74518 openoffice openoffice-1.1 build failure on 4-stable: 7 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/05/10] ports/66480 openoffice openoffice-1.1.1 port uses root's $HOME f 1 problem total. From owner-freebsd-openoffice@FreeBSD.ORG Mon Dec 6 17:14:55 2004 Return-Path: Delivered-To: freebsd-openoffice@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C267A16A4CE for ; Mon, 6 Dec 2004 17:14:55 +0000 (GMT) Received: from smtp.monmouth.com (smtp.monmouth.com [209.191.58.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E32D43D45 for ; Mon, 6 Dec 2004 17:14:55 +0000 (GMT) (envelope-from rrussell@nutran.com) Received: from [209.191.61.215] (bg-tc-ppp466.monmouth.com [209.191.61.215]) by smtp.monmouth.com (8.12.11/8.12.11) with ESMTP id iB6HEqDa012125 for ; Mon, 6 Dec 2004 12:14:53 -0500 (EST) Message-ID: <41B4939A.2090803@nutran.com> Date: Mon, 06 Dec 2004 12:15:06 -0500 From: Rebecca Russell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8a2) Gecko/20040715 X-Accept-Language: en-us, en MIME-Version: 1.0 To: openoffice@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Download will not finish X-BeenThere: freebsd-openoffice@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting OpenOffice to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 17:14:55 -0000 Good Morning! I have been trying to download OOo_1.1.3_FreeBSD410Intel_install.tgz (72 MB), but after 71-72 MB has downloaded, the download stops. OS is FreeBSD 4.7-RELEASE FTP client is GREED 0.81+ STABLE The problem is not the ISP session timeout at 6 h--GREED resumes fine. ISP tech support says the problem is not at their end. GREED reports that the download speed starts at 2.4 kB/s and decreases to approximately 1.1 kB/s, at which point progress stops (GREED just keeps trying). Do you have any suggestions as to how I should proceed? Thank you. From owner-freebsd-openoffice@FreeBSD.ORG Fri Dec 10 00:58:11 2004 Return-Path: Delivered-To: freebsd-openoffice@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85E7416A4CE for ; Fri, 10 Dec 2004 00:58:11 +0000 (GMT) Received: from outside.taborandtashell.net (sub18-33.member.dsl-only.net [63.105.18.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4690A43D3F for ; Fri, 10 Dec 2004 00:58:08 +0000 (GMT) (envelope-from tkelly@taborandtashell.net) Received: (qmail 56374 invoked from network); 9 Dec 2004 16:58:00 -0800 Received: from unknown (HELO ?192.168.0.9?) (tkelly@192.168.0.9) by 192.168.0.2 with AES256-SHA encrypted SMTP; 9 Dec 2004 16:58:00 -0800 Message-ID: <41B8F4A8.9020109@taborandtashell.net> Date: Thu, 09 Dec 2004 16:58:16 -0800 From: Tabor Kelly User-Agent: Mozilla Thunderbird 0.9 (X11/20041112) X-Accept-Language: en-us, en MIME-Version: 1.0 To: openoffice@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: mbr@freebsd.org Subject: OpenOffice "install" question X-BeenThere: freebsd-openoffice@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting OpenOffice to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 00:58:11 -0000 To whom it may concern, I just installed OpenOffice 1.1.3 from ports, and I have a couple comments. First, in order for OpenOffice to build without failure, I had to explicitly install java/jdk14 before hand. Second, I checked editors/openoffice-1.1/pkg-message for instructions on how to finish the OpenOffice install, but it was not clear if I wanted the "Workstation Installation" or the "Local Installation." By the description given in the installation dialog, I wanted the "Local Installation," but installing 211MB of stuff in every user's home directory that wants to use OpenOffice does not jive with the Unix paradigm, so I guessed that the "Workstation Installation" is really what I wanted. The "Workstation Installation" appears to have worked, but I thought you should add a note about this to editors/openoffice-1.1/pkg-message. Thank You, Tabor Kelly PS- Thanks for bringing this great tool to my favorite operating system. PSS- This is on FreeBSD 5.3R. From owner-freebsd-openoffice@FreeBSD.ORG Fri Dec 10 07:12:02 2004 Return-Path: Delivered-To: freebsd-openoffice@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0FF516A4CE for ; Fri, 10 Dec 2004 07:12:01 +0000 (GMT) Received: from mail.sailorfej.net (mail.sailorfej.net [65.102.14.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A56943D3F for ; Fri, 10 Dec 2004 07:12:01 +0000 (GMT) (envelope-from jeff@sailorfej.net) Received: from [192.168.150.40] (doorwarden.sailofej.net [65.102.14.161] (may be forged)) (authenticated bits=0) by mail.sailorfej.net (8.12.11/8.12.11) with ESMTP id iBA7BvX6003698 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 9 Dec 2004 23:11:58 -0800 (PST) (envelope-from jeff@sailorfej.net) Message-ID: <41B94C38.6080604@sailorfej.net> Date: Thu, 09 Dec 2004 23:11:52 -0800 From: Jeffrey Williams User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-openoffice@freebsd.org X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on mail.sailorfej.net X-Virus-Scanned: ClamAV 0.80/533/Sat Oct 16 18:09:44 2004 clamav-milter version 0.80j on mail.sailorfej.net X-Virus-Status: Clean Subject: serious Openoffice-1.1.3-swriter hang X-BeenThere: freebsd-openoffice@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting OpenOffice to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 07:12:02 -0000 Normally I would take this to the openoffice support forum, the problem is unusual enough that I thought you guys might want to know. I could not find any mentions of a similar problem anywhere else. The problem is severe, but has only occurred twice and is not consistent repeatable. I am running FreeBSD 5.3, Xorg-6.7.0, fluxbox-0.1.14_2, and jdk-1.4.2p6_7. I installed Openoffice-1.1.3_1 from the port. When I started "openoffice-1.1.3-swriter", the splash screen appears fine, when the window title bar and frame appears with out contents, and hangs. At this point, the second time it happened I waited for about half an hour with no change. In both cases it was when I tried to kill the process that the fun really began. The following are the processes that appear in the "ps -waux" listing: user xxxx1 0.0 0.4 1672 972 ?? Is 9:42PM 0:00.01 /bin/sh -c openoffice-1.1.3-swriter user xxxx2 0.0 0.4 1672 1000 ?? I 9:42PM 0:00.01 /bin/sh /usr/local/bin/openoffice-1.1.3-swriter user xxxx6 0.0 22.6 98072 58268 ?? S 9:42PM 0:08.81 /usr/local/OpenOffice.org1.1.3/program/soffice.bin -writer Now normally when killing a hung program, will start with the last process created and work my way backwards until the whole thing is gone. However when I tried that this time, the third process could not be killed, even with signal 9. So tried kill the other two, they died just fine, the third would still not die. So I tried shutting down X, which shutdown fine, but still left "soffice.bin -writer" still running, I tried the killing with signal 9 again, again nothing happened. At this the first time, I tried "shutdown -r now", the only unusual message (and this if from memory so forgive me if it is not exact) was at the point where the system drops into single user mode, it was: "some processes would not stop, ps axl notified" at which point it goes on clearing buffers and syncing the disks, the disk sync completes, there is a message about no buffers in use, at which point it hangs, and will not complete the shutdown. The second time openoffice writer hung, instead of trying to shutdown and reboot all at once, I used "shutdown now" to drop into single user mode. In single user mode using "ps -waux" the "soffice.bin -writer" process was still showing up, I tried one more time to kill it, and still it would not die. At this point I tried to complete the shutdown with "halt", as the first the shutdown hung immediately upon completing the disk sync. At this stage in both instances when the shutdown was hung, I tried turning the computer off with the power button on the front (soft power button) in both cases it would not shut off the computer. I got a acpi error message saying that the button was ignored because the computer wasn't ready. In both cases I then resorted to the hard power switch located on the power supply in the back of the case. As I said this problem has only occurred twice but was significant enough I thought you would want to know. It has also only occurred with writer, I have also used calc fairly often with out issue. I have not used any other applications significantly yet. As near as I can remember, in both instances at the time the problem occurred I was also running thunderbird-1.0rc and Mozilla 1.7.3 at the same time. Also I don't know if it would be related but OO has been core dumping whenever I try to print a MS Word doc, however it usually works fine if I save the doc in an openoffice format, and re-open it, and then print. That last is repeatable, and if you want I get you a copy of the core. Feel free to e-mail me, if you have any other questions. Jeffrey Williams jeff@sailorfej.net From owner-freebsd-openoffice@FreeBSD.ORG Fri Dec 10 08:39:25 2004 Return-Path: Delivered-To: freebsd-openoffice@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0DCA16A4CE for ; Fri, 10 Dec 2004 08:39:25 +0000 (GMT) Received: from mx2.imp.ch (mx2.imp.ch [157.161.9.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE62743D83 for ; Fri, 10 Dec 2004 08:39:24 +0000 (GMT) (envelope-from mb@imp.ch) Received: from mx3.imp.ch (mx3.imp.ch [157.161.9.18]) by mx2.imp.ch (8.13.1/8.13.1) with ESMTP id iBA8dHB8021692 for ; Fri, 10 Dec 2004 09:39:19 +0100 (CET) (envelope-from mb@imp.ch) Received: from mx3.imp.ch (localhost [127.0.0.1]) by mx3.imp.ch (8.12.11/8.12.11/Submit) with ESMTP id iBA8dEb6049010 for ; Fri, 10 Dec 2004 09:39:15 +0100 (CET) (envelope-from mb@imp.ch) Received: (from clamav@localhost) by mx3.imp.ch (8.12.11/8.12.11/Submit) id iBA8dEip049006 for ; Fri, 10 Dec 2004 09:39:14 +0100 (CET) (envelope-from mb@imp.ch) Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9]) id iBA8dCUQ026384; Fri, 10 Dec 2004 09:39:14 +0100 (CET) Date: Fri, 10 Dec 2004 09:39:12 +0100 (CET) From: Martin Blapp To: Jeffrey Williams In-Reply-To: <41B94C38.6080604@sailorfej.net> Message-ID: <20041210093703.I68211@cvs.imp.ch> References: <41B94C38.6080604@sailorfej.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Resent: Yes X-Spam-Checksum: 6ed38348dd6aed33446893fe17532162 X-Virus-Message-Status: No X-Virus-Status: No, scantime="0.0282 seconds" X-Spam-Status: No, hits=-4.9 required=5 scantime="3.6542 seconds" tests=BAYES_00 X-Spam-Report: ---- Start der SpamAssassin Auswertung -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] ---- Ende der SpamAssassin Auswertung X-Scanned-By: MIMEDefang 2.49 on 157.161.9.64 cc: freebsd-openoffice@freebsd.org Subject: Re: serious Openoffice-1.1.3-swriter hang X-BeenThere: freebsd-openoffice@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting OpenOffice to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 08:39:26 -0000 Hi, This sounds like a threading problem. Please upgrade your box to FreeBSD 5.3 Stable (there have been removed a lot of edge cases in the threading libraries since 5.3 release. If the problem persists, we will work on that problem. -- Martin > Now normally when killing a hung program, will start with the last > process created and work my way backwards until the whole thing is gone. > However when I tried that this time, the third process could not be > killed, even with signal 9. So tried kill the other two, they died just > fine, the third would still not die. So I tried shutting down X, which > shutdown fine, but still left "soffice.bin -writer" still running, I > tried the killing with signal 9 again, again nothing happened. At this > the first time, I tried "shutdown -r now", the only unusual message (and > this if from memory so forgive me if it is not exact) was at the point > where the system drops into single user mode, it was: > "some processes would not stop, ps axl notified" > at which point it goes on clearing buffers and syncing the disks, the > disk sync completes, there is a message about no buffers in use, at > which point it hangs, and will not complete the shutdown. > The second time openoffice writer hung, instead of trying to shutdown > and reboot all at once, I used "shutdown now" to drop into single user > mode. In single user mode using "ps -waux" the "soffice.bin -writer" > process was still showing up, I tried one more time to kill it, and > still it would not die. At this point I tried to complete the shutdown > with "halt", as the first the shutdown hung immediately upon completing > the disk sync. > At this stage in both instances when the shutdown was hung, I tried > turning the computer off with the power button on the front (soft power > button) in both cases it would not shut off the computer. I got a acpi > error message saying that the button was ignored because the computer > wasn't ready. In both cases I then resorted to the hard power switch > located on the power supply in the back of the case. From owner-freebsd-openoffice@FreeBSD.ORG Fri Dec 10 21:46:07 2004 Return-Path: Delivered-To: freebsd-openoffice@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2221516A4CE for ; Fri, 10 Dec 2004 21:46:07 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C52043D1F for ; Fri, 10 Dec 2004 21:46:06 +0000 (GMT) (envelope-from sander.vesik@gmail.com) Received: by rproxy.gmail.com with SMTP id z35so479416rne for ; Fri, 10 Dec 2004 13:46:05 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=ZmN18Fv3FeWx6dztLM4WZHCPtHvehuV49Y2mspbCMwbteYUyCkffILpX7kPX4k1xXFsuH+RtflG9XoDqweweVAwsVZGFLKuHvbNsQgypJuO8KNK/UjWJrh+hWumBPw0LkF3V5hh5QHshaId/FA//8Ym+Rahhltxfxh9ItKQZh0E= Received: by 10.38.104.13 with SMTP id b13mr684726rnc; Fri, 10 Dec 2004 13:46:05 -0800 (PST) Received: by 10.38.66.64 with HTTP; Fri, 10 Dec 2004 13:46:05 -0800 (PST) Message-ID: Date: Fri, 10 Dec 2004 23:46:05 +0200 From: Sander Vesik To: NAKATA Maho In-Reply-To: <20041202.151042.730570312.chat95@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041201.131943.783371855.chat95@mac.com> <20041202.151042.730570312.chat95@mac.com> cc: openoffice@freebsd.org Subject: Re: m62 break in sw X-BeenThere: freebsd-openoffice@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Sander Vesik List-Id: Porting OpenOffice to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 21:46:07 -0000 On Thu, 02 Dec 2004 15:10:42 +0900 (JST), NAKATA Maho wrote: > In Message-ID: > Sander Vesik wrote: > > > There are however problems with javaldx (which doesn't like the BSD > > way of calling the jdk 1.4.2-p6 or similar and needs patching) and > > something with libxml2.so version. And epm has some more > > complaints.... > > yes. I know about it. > javaldx always fails, as you know jvmfwk is largely changed. > and also recently pythonupgrade cws is integrated... > > thanks, > -- NAKATA, Maho > > A hack like this makes javaldx work: Index: plugins/sunmajor/pluginlib/sunversion.cxx =================================================================== RCS file: /cvs/udk/jvmfwk/plugins/sunmajor/pluginlib/sunversion.cxx,v retrieving revision 1.4 diff -u -r1.4 sunversion.cxx --- plugins/sunmajor/pluginlib/sunversion.cxx 23 Jul 2004 11:52:17 -0000 1.4 +++ plugins/sunmajor/pluginlib/sunversion.cxx 10 Dec 2004 20:38:40 -0000 @@ -243,7 +243,9 @@ m_preRelease = Rel_RC1; else if (! strcmp(pCur, "rc2")) m_preRelease = Rel_RC2; - else if (! strcmp(pCur, "rc3")) + else if (! strcmp(pCur, "p6")) + return true; + else if (! strcmp(pCur, "rc3")) m_preRelease = Rel_RC3; else return false; getting it be a real patch would just be some extra changes to handle the extra _0x and a #ifdef freebsd to surroundit all or very close to that I think