Bug#209162: marked as done (openoffice.org: Crash one, crash all)

2004-05-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 May 2004 23:13:56 -0300 with message-id <[EMAIL PROTECTED]> and subject line No crash under OOo 1.1.1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsib

Bug#251408: success with error report

2004-05-28 Thread Jim Watson
if the product is configured with --enable-crashdump=STATIC then the error reporter dialog is displayed and a message was sent to headquarters ;) Please do not do that yet! So the choices are (a) enable crashdump=STATIC and setup a server to receive the error reports at debian and transform to

Bug#241529: possible breakthrough?

2004-05-28 Thread Chris Halls
Hi Matt, Thanks for your extra information. It helps a little, but doesn't provide a lot of extra information. I'll try and explain what is going on. There are 3 ways in which OOo can choose its menu font, and those correspond to the 3 settings of OOO_FORCE_DESKTOP - none, kde and gnome. The k

Bug#201656: Is this still reproducible with OOo 1.1.1

2004-05-28 Thread Andrew McMillan
tags 201656 +moreinfo tags 201656 +unreproducible thanks Hi, I can't reproduce this issue on Debian release 1.1.1-3 Regards, Andrew. - Andrew @ Catalyst .Net .NZ Ltd, PO Box 11-053,

Processed: Is this still reproducible with OOo 1.1.1

2004-05-28 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tags 201656 +moreinfo Bug#201656: openoffice.org: Fonts erratically altered in Draw There were no tags set. Tags added: moreinfo > tags 201656 +unreproducible Bug#201656: openoffice.org: Fonts erratically altered in Draw Tags were: moreinfo Tags added:

Processed: Seems to be covered by this upstream issue

2004-05-28 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > forwarded 193760 http://qa.openoffice.org/issues/show_bug.cgi?id=14163 Bug#193760: Embedded graphics get misplaced in exported EPS files Noted your statement that Bug has been forwarded to http://qa.openoffice.org/issues/show_bug.cgi?id=14163. > thank

Bug#193760: Seems to be covered by this upstream issue

2004-05-28 Thread Andrew McMillan
upstream 193760 http://qa.openoffice.org/issues/show_bug.cgi?id=14163 thanks This issue seems to be related to general problems with the recursive parsing of postscript in postscript, and OpenOffice.org lack of a parser for postscript. Workarounds are suggested in the ooffice issue, but are gener

Bug#241529: possible breakthrough?

2004-05-28 Thread Matt Price
OK, messed around a bit and did NOT solve the problem but can tell you this: -I made a new user "ootest" and ofund that she exhibited the same behaviour as my regular user: -no menus or dialog text visible form within xfce3, xfce4 or enlightenment -works fine in gnome 2.4 (I don't have kde workin

Bug#241529: same bug appears with xfce

2004-05-28 Thread Matt Price
Just fyi -- I fired up enlightenment and the bug persists in enlightenment as well. Please let me know if I can do anything to help you reproduce this -- send you some config file info, etc... I will continue testing... Matt On Wed, Apr 28, 2004 at 02:29:56PM -0400, Matt Price wrote: > hey the

Bug#251408: openoffice.org-crashrep: crashrep does not report

2004-05-28 Thread Jim Watson
On Fri, 28 May 2004 22:46, Rene Engelhard wrote: > > What do you suggest? Disabling this feature for Linux/sparc only and > enabling it for the rest? i think you should not --enable-crashdump for any platforms, as you would need a server to receive the messages such as shown here: http://qa.open

Bug#251408: openoffice.org-crashrep: crashrep does not report

2004-05-28 Thread Jim Watson
On Fri, 28 May 2004 22:46, Rene Engelhard wrote: > Hmm. where does the _with_gtk.bin come from? it is from the crashrep/source/unx/makefile.mk PRJNAME=crashrep TARGET=crash_report.bin TARGET2=crash_report_with_gtk.bin TARGETTYPE=CUI > > What do you suggest? Disabling this f

Bug#251408: openoffice.org-crashrep: crashrep does not report

2004-05-28 Thread Rene Engelhard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 tag 251408 + moreinfo thanks Hi Jim, Jim Watson wrote: > when the product does crash, this is the report: > /usr/lib/openoffice/program/crash_report: line 78: > /usr/lib/openoffice/program/crash_report_with_gtk.bin: No such file or > directory

Processed: Re: Bug#251408: openoffice.org-crashrep: crashrep does not report

2004-05-28 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tag 251408 + moreinfo Bug#251408: openoffice.org-crashrep: crashrep does not report Tags were: sid Tags added: moreinfo > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrat

Bug#251408: openoffice.org-crashrep: crashrep does not report

2004-05-28 Thread Jim Watson
OK, now I did build upstream with --enable-crashdump, but I have only rebuilt modules scp and crashreport yet. The same issue exists upstream and with debian. In both cases the file which is delivered to the program directory is crash_report.bin but is trying to execute crash_report_with_gtk.bi

Bug#251408: openoffice.org-crashrep: crashrep does not report

2004-05-28 Thread Jim Watson
Package: openoffice.org-crashrep Version: 1.1.1-3 Severity: normal Tags: sid -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: sparc (sparc64) Kernel: Linux 2.6.5 Locale: LANG=en_US, LC_CTYPE=en_US Versions of packages o

ANNOUNCE: ooo-build-1.1.56

2004-05-28 Thread Michael Meeks
OpenOffice.org build: This package contains Desktop integration work for OpenOffice.org, several back-ported features & speedups, and a much simplified build wrapper, making an OO.o build / install possible for the common man. It is a staging ground for up-streaming patches to stock OO.o.

Bug#217954: marked as done (openoffice.org: trying to open font files that do not exist)

2004-05-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 May 2004 20:42:57 +1000 with message-id <[EMAIL PROTECTED]> and subject line openoffice.org: trying to open font files that do not exist has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#195239: OpenOffice.org does not correctly parse filenames with ":" in them

2004-05-28 Thread Andrew McMillan
forwarded 195239 http://www.openoffice.org/issues/show_bug.cgi?id=25911 thanks It looks like this will be fixed in version 2. The problem with the filename is that OpenOffice.org is not correctly converting the ":" into a %3A. Several workarounds are available: - manually translate the ":" into

Processed: OpenOffice.org does not correctly parse filenames with ":" in them

2004-05-28 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > forwarded 195239 http://www.openoffice.org/issues/show_bug.cgi?id=25911 Bug#195239: openoffice.org: OO crashes for certain file names Noted your statement that Bug has been forwarded to http://www.openoffice.org/issues/show_bug.cgi?id=25911. > thanks