From bugmaster at FreeBSD.org Mon Dec 1 03:08:01 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 1 03:09:51 2008 Subject: Current problem reports assigned to openoffice@FreeBSD.org Message-ID: <200812011108.mB1B80CI053824@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/129308 openoffice editors/openoffice.org-3-devel (3.1.20081024) unopkg c o ports/129122 openoffice editors/openoffice.org-3: building OpenOffice.org-3.0. o ports/128176 openoffice editors/openoffice.org-3 - 3.0.0 crash (macro security o ports/127946 openoffice editors/openoffice.org-3 dictionary extension doesn't o ports/126818 openoffice editors/openoffice.org-3 compilation fails on FreeBSD- o ports/124801 openoffice editors/openoffice.org-3 - OpenOffice fails to find li o ports/119204 openoffice [patch] editors/OpenOffice.org-2 v2.3 loops when file o ports/118527 openoffice editors/openoffice.org-2 seg faults when asked to perf o ports/118507 openoffice editors/Openoffice.org-2 2.3.1/AMD64 does not show ODB o ports/117965 openoffice editors/openoffice.org-2 Impress crashes with multiple o ports/117808 openoffice editors/OpenOffice.org-2 seems to be looping o ports/116741 openoffice editors/openoffice.org-2 build errors related to java f ports/112283 openoffice editors/openoffice-2 fails to build with "pyconfig.h: o ports/108313 openoffice editors/openoffice.org port build fails f ports/107229 openoffice sysutils/coreutils: gcp fails to set default ACL which 15 problems total. From chat95 at mac.com Fri Dec 5 02:20:56 2008 From: chat95 at mac.com (Maho NAKATA) Date: Fri Dec 5 02:21:03 2008 Subject: ports/129122: Building OpenOffice.org-3.0.0 fails In-Reply-To: <18739.33257.520856.332827@jerusalem.litteratus.org> References: <200811240850.mAO8o1F1012897@freefall.freebsd.org> <200811291026.mATAQXun013656@jau.iki.fi> <18739.33257.520856.332827@jerusalem.litteratus.org> Message-ID: <20081205.192053.183051086.chat95@mac.com> Hi, I welcome patches and patch submitters should sign to SCA... Best, From: Robert Huff Subject: Re: ports/129122: Building OpenOffice.org-3.0.0 fails Date: Mon, 01 Dec 2008 01:19:21 -0500 > > Jukka A. Ukkonen writes: > > > To make the ports build successful on ACL enabled systems > > while waiting for the real fix you can... > > > > 1) either make the build phase use the native cp in place of > > gcp (labour intensive), > > > > 2) or emulate gcp on top of the native cp (simple), > > Simple for /you/ maybe; not so much for many others. Care to > share the wisdom? > > > Robert Huff > > _______________________________________________ > freebsd-openoffice@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-openoffice > To unsubscribe, send any mail to "freebsd-openoffice-unsubscribe@freebsd.org" > From chat95 at mac.com Fri Dec 5 02:50:03 2008 From: chat95 at mac.com (Maho NAKATA) Date: Fri Dec 5 02:50:10 2008 Subject: ports/129122: Building OpenOffice.org-3.0.0 fails Message-ID: <200812051050.mB5Ao3H4010177@freefall.freebsd.org> The following reply was made to PR ports/129122; it has been noted by GNATS. From: Maho NAKATA To: roberthuff@rcn.com Cc: jau@iki.fi, bug-followup@freebsd.org, openoffice@freebsd.org Subject: Re: ports/129122: Building OpenOffice.org-3.0.0 fails Date: Fri, 05 Dec 2008 19:20:53 +0900 (JST) Hi, I welcome patches and patch submitters should sign to SCA... Best, From: Robert Huff Subject: Re: ports/129122: Building OpenOffice.org-3.0.0 fails Date: Mon, 01 Dec 2008 01:19:21 -0500 > > Jukka A. Ukkonen writes: > > > To make the ports build successful on ACL enabled systems > > while waiting for the real fix you can... > > > > 1) either make the build phase use the native cp in place of > > gcp (labour intensive), > > > > 2) or emulate gcp on top of the native cp (simple), > > Simple for /you/ maybe; not so much for many others. Care to > share the wisdom? > > > Robert Huff > > _______________________________________________ > freebsd-openoffice@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-openoffice > To unsubscribe, send any mail to "freebsd-openoffice-unsubscribe@freebsd.org" > From jau at iki.fi Sat Dec 6 01:20:09 2008 From: jau at iki.fi (Jukka A. Ukkonen) Date: Sat Dec 6 01:20:16 2008 Subject: ports/129122: Building OpenOffice.org-3.0.0 fails In-Reply-To: <20081205.192053.183051086.chat95@mac.com> from "Maho NAKATA" at Dec 5, 8 07:20:53 pm Message-ID: <200812060920.mB69K5Ow039692@jau.iki.fi> Quoting Maho NAKATA: > > I welcome patches and patch submitters should sign to SCA... > Best, > > From: Robert Huff > Subject: Re: ports/129122: Building OpenOffice.org-3.0.0 fails > Date: Mon, 01 Dec 2008 01:19:21 -0500 > > > > > Jukka A. Ukkonen writes: > > > > > To make the ports build successful on ACL enabled systems > > > while waiting for the real fix you can... > > > > > > 1) either make the build phase use the native cp in place of > > > gcp (labour intensive), > > > > > > 2) or emulate gcp on top of the native cp (simple), > > > > Simple for /you/ maybe; not so much for many others. Care to > > share the wisdom? Since patches and sharing of wisdom have been requested... My approach has been simply overriding the true (broken) gcp using a wrapper script to convert gcp command line options to those used by the native cp. This of course is not so much a patch but simply a workaround. See my replacement gcp script at the end. I have put this gcp replacement in my own ~/bin directory and inserted my own ~/bin in the PATH before /usr/local/bin, which is the location of the real gcp. Additionally I have manually edited the configure script to remove the test for real gcp. Another means to the same result is running "make configure" while the replacement gcp is not yet in the PATH. Either way this part has always taken some manual action. As I already have pointed out, the actual patch should go into gcp anyhow. So, I think a workaround is exactly what is needed to get OOo successfully built while gcp remains broken. I hope this helps. Cheers, // jau .--- ..- -.- -.- .- .- .-.-.- ..- -.- -.- --- -. . -. / Jukka A. Ukkonen, Oxit Ltd, Finland /__ M.Sc. (sw-eng & cs) (Phone) +358-500-606-671 / Internet: Jukka.Ukkonen(a)Oxit.Fi (Home) +358-9-6215-280 / Internet: jau(a)iki.fi v .--- .- ..- ...-.- .. -.- .. .-.-.- ..-. .. + + + + My opinions are mine and mine alone, not my employers. + + + + o \ / - X ------------------------- clip clip ------------------------------ / \ O #!/bin/sh #debug=echo GCP_EMULATION_VERSION='cp (GNU coreutils) 6.9' COPYRIGHT_MESSAGE='Copyright (C) 2007-2008 Jukka Ukkonen / Thunderbolt Ltd.' newopts="" _prog=`basename $0` usage() { echo 'usage: '"${_prog}" \ '[-abdfiHlLPpRrstTuvx]' \ '[-t destdir] [-S backup_suffix]' \ 'src ... [dest]' echo '' return 0 } while getopts "abdfiHlLPpRrsS:t:Tuvx-:" opt ; do case "$opt" in \?) usage exit 255 ;; -) case "$OPTARG" in "version") echo "$GCP_EMULATION_VERSION" echo "$COPYRIGHT_MESSAGE" exit 0 ;; "help") usage exit 0 ;; "") break ;; *) echo 'Option "'"$OPTARG"'" currently unsupported.' exit 255 ;; esac ;; a) # same as -dpPR in GNU # In a modern BSD -a works. # We assume an old system. newopts="$newopts -pPR" ;; b) # BSD cp currently has no backup mode ;; d) # -P --preserve=link # emulate as -Pp # -p == --preserve=mode,ownership,timestamps newopts="$newopts -Pp" ;; f) newopts="$newopts -f" ;; i) newopts="$newopts -i" ;; H) newopts="$newopts -H" ;; l) newopts="$newopts -l" ;; L) newopts="$newopts -L" ;; P) newopts="$newopts -P" ;; p) newopts="$newopts -p" ;; R|r) newopts="$newopts -R" ;; s) # BSD cp currently does not create symlinks -> hard-link newopts="$newopts -l" ;; S) # BSD cp currently has no backup mode ;; t) target_dir="$OPTARG" ;; T) # in GNU: treat DEST as a normal file ;; u) # BSD cp currently supports no update mode # Emulate using no overwrite. newopts="$newopts -n" ;; v) newopts="$newopts -v" ;; x) # in GNU: stay on this file system # Not currently supported by BSD. ;; esac done shift `expr $OPTIND - 1` if [ X"${target_dir}" = "X" ] ; then $debug /bin/cp $newopts "$@" else $debug /bin/cp $newopts "$@" "${target_dir}" fi From jau at iki.fi Sat Dec 6 01:30:04 2008 From: jau at iki.fi (Jukka A. Ukkonen) Date: Sat Dec 6 01:30:11 2008 Subject: ports/129122: Building OpenOffice.org-3.0.0 fails Message-ID: <200812060930.mB69U3jH069715@freefall.freebsd.org> The following reply was made to PR ports/129122; it has been noted by GNATS. From: jau@iki.fi (Jukka A. Ukkonen) To: chat95@mac.com (Maho NAKATA) Cc: roberthuff@rcn.com, bug-followup@freebsd.org, openoffice@freebsd.org Subject: Re: ports/129122: Building OpenOffice.org-3.0.0 fails Date: Sat, 6 Dec 2008 11:20:04 +0200 (EET) Quoting Maho NAKATA: > > I welcome patches and patch submitters should sign to SCA... > Best, > > From: Robert Huff > Subject: Re: ports/129122: Building OpenOffice.org-3.0.0 fails > Date: Mon, 01 Dec 2008 01:19:21 -0500 > > > > > Jukka A. Ukkonen writes: > > > > > To make the ports build successful on ACL enabled systems > > > while waiting for the real fix you can... > > > > > > 1) either make the build phase use the native cp in place of > > > gcp (labour intensive), > > > > > > 2) or emulate gcp on top of the native cp (simple), > > > > Simple for /you/ maybe; not so much for many others. Care to > > share the wisdom? Since patches and sharing of wisdom have been requested... My approach has been simply overriding the true (broken) gcp using a wrapper script to convert gcp command line options to those used by the native cp. This of course is not so much a patch but simply a workaround. See my replacement gcp script at the end. I have put this gcp replacement in my own ~/bin directory and inserted my own ~/bin in the PATH before /usr/local/bin, which is the location of the real gcp. Additionally I have manually edited the configure script to remove the test for real gcp. Another means to the same result is running "make configure" while the replacement gcp is not yet in the PATH. Either way this part has always taken some manual action. As I already have pointed out, the actual patch should go into gcp anyhow. So, I think a workaround is exactly what is needed to get OOo successfully built while gcp remains broken. I hope this helps. Cheers, // jau .--- ..- -.- -.- .- .- .-.-.- ..- -.- -.- --- -. . -. / Jukka A. Ukkonen, Oxit Ltd, Finland /__ M.Sc. (sw-eng & cs) (Phone) +358-500-606-671 / Internet: Jukka.Ukkonen(a)Oxit.Fi (Home) +358-9-6215-280 / Internet: jau(a)iki.fi v .--- .- ..- ...-.- .. -.- .. .-.-.- ..-. .. + + + + My opinions are mine and mine alone, not my employers. + + + + o \ / - X ------------------------- clip clip ------------------------------ / \ O #!/bin/sh #debug=echo GCP_EMULATION_VERSION='cp (GNU coreutils) 6.9' COPYRIGHT_MESSAGE='Copyright (C) 2007-2008 Jukka Ukkonen / Thunderbolt Ltd.' newopts="" _prog=`basename $0` usage() { echo 'usage: '"${_prog}" \ '[-abdfiHlLPpRrstTuvx]' \ '[-t destdir] [-S backup_suffix]' \ 'src ... [dest]' echo '' return 0 } while getopts "abdfiHlLPpRrsS:t:Tuvx-:" opt ; do case "$opt" in \?) usage exit 255 ;; -) case "$OPTARG" in "version") echo "$GCP_EMULATION_VERSION" echo "$COPYRIGHT_MESSAGE" exit 0 ;; "help") usage exit 0 ;; "") break ;; *) echo 'Option "'"$OPTARG"'" currently unsupported.' exit 255 ;; esac ;; a) # same as -dpPR in GNU # In a modern BSD -a works. # We assume an old system. newopts="$newopts -pPR" ;; b) # BSD cp currently has no backup mode ;; d) # -P --preserve=link # emulate as -Pp # -p == --preserve=mode,ownership,timestamps newopts="$newopts -Pp" ;; f) newopts="$newopts -f" ;; i) newopts="$newopts -i" ;; H) newopts="$newopts -H" ;; l) newopts="$newopts -l" ;; L) newopts="$newopts -L" ;; P) newopts="$newopts -P" ;; p) newopts="$newopts -p" ;; R|r) newopts="$newopts -R" ;; s) # BSD cp currently does not create symlinks -> hard-link newopts="$newopts -l" ;; S) # BSD cp currently has no backup mode ;; t) target_dir="$OPTARG" ;; T) # in GNU: treat DEST as a normal file ;; u) # BSD cp currently supports no update mode # Emulate using no overwrite. newopts="$newopts -n" ;; v) newopts="$newopts -v" ;; x) # in GNU: stay on this file system # Not currently supported by BSD. ;; esac done shift `expr $OPTIND - 1` if [ X"${target_dir}" = "X" ] ; then $debug /bin/cp $newopts "$@" else $debug /bin/cp $newopts "$@" "${target_dir}" fi From bugmaster at FreeBSD.org Mon Dec 8 03:07:58 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 8 03:09:43 2008 Subject: Current problem reports assigned to openoffice@FreeBSD.org Message-ID: <200812081107.mB8B7vo9015493@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/129308 openoffice editors/openoffice.org-3-devel (3.1.20081024) unopkg c o ports/129122 openoffice editors/openoffice.org-3: building OpenOffice.org-3.0. o ports/128176 openoffice editors/openoffice.org-3 - 3.0.0 crash (macro security o ports/127946 openoffice editors/openoffice.org-3 dictionary extension doesn't o ports/126818 openoffice editors/openoffice.org-3 compilation fails on FreeBSD- o ports/124801 openoffice editors/openoffice.org-3 - OpenOffice fails to find li o ports/119204 openoffice [patch] editors/OpenOffice.org-2 v2.3 loops when file o ports/118527 openoffice editors/openoffice.org-2 seg faults when asked to perf o ports/118507 openoffice editors/Openoffice.org-2 2.3.1/AMD64 does not show ODB o ports/117965 openoffice editors/openoffice.org-2 Impress crashes with multiple o ports/117808 openoffice editors/OpenOffice.org-2 seems to be looping o ports/116741 openoffice editors/openoffice.org-2 build errors related to java f ports/112283 openoffice editors/openoffice-2 fails to build with "pyconfig.h: o ports/108313 openoffice editors/openoffice.org port build fails f ports/107229 openoffice sysutils/coreutils: gcp fails to set default ACL which 15 problems total. From seventhdayslumber at mac.com Fri Dec 12 08:42:37 2008 From: seventhdayslumber at mac.com (Seventh Day Slumber) Date: Fri Dec 12 08:42:44 2008 Subject: SDS Newsletter Message-ID: Your email client cannot read this email. To view it online, please go here: http://www.newsletterserve.com/display.php?M=237843&C=e33131b685feb5353fb6258fe61cc4d2&S=1080&L=200&N=1003 To stop receiving these emails:http://www.newsletterserve.com/unsubscribe.php?M=237843&C=e33131b685feb5353fb6258fe61cc4d2&L=200&N=1080 From office.notice452 at aliceadsl.fr Sun Dec 14 14:35:10 2008 From: office.notice452 at aliceadsl.fr (office.notice452@aliceadsl.fr) Date: Sun Dec 14 14:35:17 2008 Subject: Award Result Notice 15/12/2008 Message-ID: EuroMillones Loteria S.A Madrid, Espa?a. --------15/12/2008--------- Attn: Winner, WINNING PRIZE NOTIFICATION Finally today, the result of winners of the EURO MILLONES LOTERIA E-mail program held on the 1st of December 2008 was announced. Your e-mail address attached to a TICKET Number with REFERENCE Number drew STAR No: 00-00-00-00-00 (coded for Security Reasons) which consequently won in the 2ND CATEGORY, you have therefore been approved for a lump sum pay out of ?975,000.00cents (Nine Hundred and Seventy Five Thousand Euro). !!!!CONGRATULATIONS!!!! The draw was carried out through random sampling (A QUATITATIVE TECHNIQUE) in our computerized email selection programme from a database of over 20,000,000 email addresses drawn from 53 Countries around the World. The online draws was conducted by a random selection of email addresses from an exclusive list of 45,901 E-mail addresses of individuals and corporate bodies picked by an advanced automated random computer search system from the internet. As such no tickets were sold but all email addresses were assigned to different ticket numbers for representation, identification and privacy purposes. Electronic Mail Loteria is approved and Licensed by the International Association of Lottery (IAL). Ensure to keep your winning information in confidence until your award is duly processed and claimed, this is part of our security measures to avoid double claiming or unwarranted advantage taking of the situation by other participants or impersonators in some cases. To begin your claim, you will have to complete a release order form which will be enclosed in the confirmation email from the claim processing agent. Contact the claim agent immediately via email or telephone with the information below: EuroMillones Loteria-Claim Processing Agent Sr. Fernaldo Alberto Email Address: euromlsa_claimagent001@aliceadsl.fr Telephone: +34 651 945 543 You are to send the information below to the CLAIM PROCESSING AGENT via email for the confirmation of your winning. 1. Your full names: 2. Your address: 3. Telephone/fax numbers: 4. Occupation/age: 5. Amount won: 6. Reference Number: Not Included For Security Reasons 7. Security File Number: Not Included For Security Reasons 8. Ticket Number: Not Included For Security Reasons 9. Reconfirm Email Address: 10. Date Notified: Note that all prize money must be claimed within two weeks. Failure to do so your winning amount will be returned to the Ministerio De Economia Y Hacienda as Un-claimed. In order to avoid unnecessary delays and complications please remember to quote your Security File Number in all correspondence with the Claim Officer. Yours Sincerely, Helena Fernado Loteria Coordinator Note: - All claims are nullified after 14 working days from today. - Do inform the claims officer of any change of Names, Address and E-mail. - All winners under the age of 18 are automatically disqualified. ********DO NOT DISCLOSE YOUR WINNING INFORMATION TO ANYONE TO AVOID DOUBLE CLAIM********* From bugmaster at FreeBSD.org Mon Dec 15 03:08:01 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 15 03:09:56 2008 Subject: Current problem reports assigned to openoffice@FreeBSD.org Message-ID: <200812151108.mBFB80Pw005590@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/129308 openoffice editors/openoffice.org-3-devel (3.1.20081024) unopkg c o ports/129122 openoffice editors/openoffice.org-3: building OpenOffice.org-3.0. o ports/128176 openoffice editors/openoffice.org-3 - 3.0.0 crash (macro security o ports/127946 openoffice editors/openoffice.org-3 dictionary extension doesn't o ports/126818 openoffice editors/openoffice.org-3 compilation fails on FreeBSD- o ports/124801 openoffice editors/openoffice.org-3 - OpenOffice fails to find li o ports/119204 openoffice [patch] editors/OpenOffice.org-2 v2.3 loops when file o ports/118527 openoffice editors/openoffice.org-2 seg faults when asked to perf o ports/118507 openoffice editors/Openoffice.org-2 2.3.1/AMD64 does not show ODB o ports/117965 openoffice editors/openoffice.org-2 Impress crashes with multiple o ports/117808 openoffice editors/OpenOffice.org-2 seems to be looping o ports/116741 openoffice editors/openoffice.org-2 build errors related to java f ports/112283 openoffice editors/openoffice-2 fails to build with "pyconfig.h: o ports/108313 openoffice editors/openoffice.org port build fails f ports/107229 openoffice sysutils/coreutils: gcp fails to set default ACL which 15 problems total. From bugmaster at FreeBSD.org Mon Dec 22 03:07:58 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 22 03:09:49 2008 Subject: Current problem reports assigned to openoffice@FreeBSD.org Message-ID: <200812221107.mBMB7vjg061794@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/129308 openoffice editors/openoffice.org-3-devel (3.1.20081024) unopkg c o ports/129122 openoffice editors/openoffice.org-3: building OpenOffice.org-3.0. o ports/128176 openoffice editors/openoffice.org-3 - 3.0.0 crash (macro security o ports/127946 openoffice editors/openoffice.org-3 dictionary extension doesn't o ports/126818 openoffice editors/openoffice.org-3 compilation fails on FreeBSD- o ports/124801 openoffice editors/openoffice.org-3 - OpenOffice fails to find li o ports/119204 openoffice [patch] editors/OpenOffice.org-2 v2.3 loops when file o ports/118527 openoffice editors/openoffice.org-2 seg faults when asked to perf o ports/118507 openoffice editors/Openoffice.org-2 2.3.1/AMD64 does not show ODB o ports/117965 openoffice editors/openoffice.org-2 Impress crashes with multiple o ports/117808 openoffice editors/OpenOffice.org-2 seems to be looping o ports/116741 openoffice editors/openoffice.org-2 build errors related to java f ports/112283 openoffice editors/openoffice-2 fails to build with "pyconfig.h: o ports/108313 openoffice editors/openoffice.org port build fails f ports/107229 openoffice sysutils/coreutils: gcp fails to set default ACL which 15 problems total. From run10kswim at gmail.com Wed Dec 24 07:00:54 2008 From: run10kswim at gmail.com (KenH) Date: Wed Dec 24 07:01:00 2008 Subject: Can't get OO3 to execute on FreeBSD7 Message-ID: <1163b5af-9b2a-43e9-ae97-380dfde3b6fd@a12g2000pro.googlegroups.com> I can't get OpenOffice3 to run on FreeBSD7. Downloaded binaries. Install script runs OK. When I try to execute , I get a message (not an exact quote): "can't display graphics .. error 0x63" or something like that. It core dumps. Sorry, I'm not at that PC right now. My X seems to run OK. My /usr/var/X.log shows some odd problems, related to modules w/in: xf86-video-fbdev-0.3.1_2 Errors such as "can't load module fbdevhw .." At this point, I don't know whether my problem is OO or X. Thx, and have a great '09! From menah101 at brinkshofer.com Wed Dec 24 12:23:32 2008 From: menah101 at brinkshofer.com (Kimberly) Date: Wed Dec 24 12:23:39 2008 Subject: Merry Xmas! Message-ID: <20081224211022.9010609@brinkshofer.com> Kimberly has created for you an electronic greeting card. To view the ecard simply click the link below: http://yourchristmaslights.com/?id=194b12568568de181ba Enjoy! From run10kswim at gmail.com Wed Dec 24 16:00:11 2008 From: run10kswim at gmail.com (KenH) Date: Wed Dec 24 16:00:18 2008 Subject: Can't get OO3 to execute on FreeBSD7 References: <1163b5af-9b2a-43e9-ae97-380dfde3b6fd@a12g2000pro.googlegroups.com> Message-ID: Actually, that X log file is: /var/log/Xorg.0.log and the X log error msgs are: (II) Loading sub module "fbdevhw" (II) LoadModule: "fbdevhw" (WW) Warning, couldn't open module fbdevhw (II) UnloadModule: "fbdevhw" (EE) Failed to load module "fbdevhw" (module does not exist, 0) and the OO message is now: libGL error: open DRM failed (Operation not permitted) libGL error: reverting to (slow) indirect rendering The application cannot be started. The component manager is not available. .. core .. I think the different OO message (from prev) is due to working from a 'user' account this time instead of 'root'. Regards, - Ken H. From bugmaster at FreeBSD.org Mon Dec 29 03:08:00 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 29 03:09:45 2008 Subject: Current problem reports assigned to openoffice@FreeBSD.org Message-ID: <200812291107.mBTB7xDe025686@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/129308 openoffice editors/openoffice.org-3-devel (3.1.20081024) unopkg c o ports/129122 openoffice editors/openoffice.org-3: building OpenOffice.org-3.0. o ports/128176 openoffice editors/openoffice.org-3 - 3.0.0 crash (macro security o ports/127946 openoffice editors/openoffice.org-3 dictionary extension doesn't o ports/126818 openoffice editors/openoffice.org-3 compilation fails on FreeBSD- o ports/124801 openoffice editors/openoffice.org-3 - OpenOffice fails to find li o ports/119204 openoffice [patch] editors/OpenOffice.org-2 v2.3 loops when file o ports/118527 openoffice editors/openoffice.org-2 seg faults when asked to perf o ports/118507 openoffice editors/Openoffice.org-2 2.3.1/AMD64 does not show ODB o ports/117965 openoffice editors/openoffice.org-2 Impress crashes with multiple o ports/117808 openoffice editors/OpenOffice.org-2 seems to be looping o ports/116741 openoffice editors/openoffice.org-2 build errors related to java f ports/112283 openoffice editors/openoffice-2 fails to build with "pyconfig.h: o ports/108313 openoffice editors/openoffice.org port build fails f ports/107229 openoffice sysutils/coreutils: gcp fails to set default ACL which 15 problems total.