Package: openoffice.org
Version: 2.0.4~rc2-2
Severity: Grave
openoffice.org crashes when opening any file. Have tried with .doc and
.ppt files
Update to openoffice.org-common and openoffice.org-java-common version
2.0.4~rc3-1 did not help! The problem remains.
Package: openoffice.org
Version: 2.
I'm using debian sid an did an upgrade recently.
Openoffice is 2.0.4~rc2-2
For each application, the program startup image appear, a windows wich seems to
be a "recover document" windows brevly appear, and every disapear.
Here is the trace.
$ soffice
This should only happen once
Fatal excepti
Hi there,
I've caught this work-around:
% rm -rf ~/.openoffice.org2 # Sorry, it seems to be necessary
% export LD_ASSUME_KERNEL=2.4.1
then
% ooffice # should work!
Hope this helps!
Regards
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [E
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390128: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390128: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390128: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#389423: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390133: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390128: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390128: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390133: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390106: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390136: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390136: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390133: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390133: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390106: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390106: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390106: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390136: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390106: fixed in openoffice.org 2.0.4~rc3-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 i
Processing commands for [EMAIL PROTECTED]:
> severity 390762 grave
Bug#390762: openoffice.org is crashing on startup
Severity set to `grave' from `normal'
> reaasign 390762 openoffice.org
Unknown command or malformed arguments to command.
> close 390762 2.0.4~rc3-1
Bug#390762: openoffice.org is
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390106: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390136: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390106: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390136: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390133: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390133: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390133: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:00 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#387224: fixed in openoffice.org 2.0.4~rc3-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 i
reassign 390855 openoffice.org
severity 390855 grave
close 390855 2.0.4~rc3-1
forcemerge 390855 390106
thanks
Hi,
Marcus Better wrote:
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1513195296 (LWP 11279)]
> ---Type to continue, or q to quit---
> 0xa721b310 in rt
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390136: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390128: fixed in openoffice.org 2.0.4~rc3-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 i
Processing commands for [EMAIL PROTECTED]:
> nnotfound 390682 2.0.3-6
Unknown command or malformed arguments to command.
> severity 2.0.3-6 grave
Unknown command or malformed arguments to command.
> close 390682 2.0.4~rc3-1
Bug#390682: openoffice.org-writer: 2.0.4~rc2 segfaults when importing .d
severity 390762 grave
reaasign 390762 openoffice.org
close 390762 2.0.4~rc3-1
forcemerge 390762 390702
thanks
Hi,
Tom Epperly wrote:
> It started happening relatively recently. The first problem I noticed
> was that oocalc would no longer open some .ods files if I did oocalc
> foo.ods. If I la
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390128: fixed in openoffice.org 2.0.4~rc3-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 i
nnotfound 390682 2.0.3-6
severity 2.0.3-6 grave
close 390682 2.0.4~rc3-1
forcemerge 390682 390682
thanks
Arthur Marsh wrote:
> Having read the description of bug #390136 "openoffice.org-writer:
> Oowriter dies after startup" I believe that the bug I reported as
> #390682 is the same as #390136 a
Your message dated Tue, 03 Oct 2006 05:05:59 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#341649: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390133: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390136: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390106: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390133: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390136: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390136: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390106: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390128: fixed in openoffice.org 2.0.4~rc3-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 i
Your message dated Tue, 03 Oct 2006 05:06:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390128: fixed in openoffice.org 2.0.4~rc3-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 i
Processing commands for [EMAIL PROTECTED]:
> reassign 390855 openoffice.org
Bug#390855: openoffice.org-calc: segfault when creating/manipulating charts
Bug reassigned from package `openoffice.org-calc' to `openoffice.org'.
> severity 390855 grave
Bug#390855: openoffice.org-calc: segfault when cre
Accepted:
broffice.org_2.0.4~rc3-1_all.deb
to pool/main/o/openoffice.org/broffice.org_2.0.4~rc3-1_all.deb
libmythes-dev_2.0.4~rc3-1_powerpc.deb
to pool/main/o/openoffice.org/libmythes-dev_2.0.4~rc3-1_powerpc.deb
openoffice.org-base_2.0.4~rc3-1_powerpc.deb
to pool/main/o/openoffice.org/openof
openoffice.org_2.0.4~rc3-1_source+powerpc+all.changes uploaded successfully to
localhost
along with the files:
openoffice.org-help-en-gb_2.0.4~rc3-1_all.deb
openoffice.org-qa-tools_2.0.4~rc3-1_powerpc.deb
openoffice.org-l10n-be-by_2.0.4~rc3-1_all.deb
openoffice.org-draw_2.0.4~rc3-1_powerpc
Package: openoffice.org-calc
Version: 2.0.4~rc2-2
Severity: important
calc segfaults when I try to add or change a chart in a spreadsheet.
The simplest way to reproduce it is to make a simple table with some
data, such as this one:
1 1
2 7
3 2
4 4
5 6
6 6
7
Processing commands for [EMAIL PROTECTED]:
> reassign 390562 firefox
Bug#390562: firefox: CPU eating while waiting for passwd
Bug reassigned from package `openoffice.org' to `firefox'.
> severity 390562 normal
Bug#390562: firefox: CPU eating while waiting for passwd
Severity set to `normal' from
52 matches
Mail list logo