Your message dated Fri, 25 Apr 2008 11:00:36 +0300
with message-id <[EMAIL PROTECTED]>
and subject line #368574,2.0.2-3 crashes on some documents; 2.0.2-2 is OK
has caused the Debian Bug report #368574,
regarding 2.0.2-3 crashes on some documents; 2.0.2-2 is OK
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 responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
368574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=368574
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: openoffice.org
Version: 2.0.2-3
Severity: important
Hi,
2.0.2-3 on powerpc crashes on some documents; 2.0.2-2 has no problems
opening and working on the same files.
No backtrace, no nothing, and I can't disclose the problematic documents.
JB.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages openoffice.org depends on:
ii openoffice.org-base 2.0.2-2 OpenOffice.org office suite - data
ii openoffice.org-calc 2.0.2-2 OpenOffice.org office suite - spre
ii openoffice.org-core 2.0.2-2 OpenOffice.org office suite archit
ii openoffice.org-draw 2.0.2-2 OpenOffice.org office suite - draw
ii openoffice.org-impress 2.0.2-2 OpenOffice.org office suite - pres
ii openoffice.org-java-common 2.0.2-2 OpenOffice.org office suite Java s
ii openoffice.org-math 2.0.2-2 OpenOffice.org office suite - equa
ii openoffice.org-writer 2.0.2-2 OpenOffice.org office suite - word
openoffice.org recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.0.2-3
>>> No backtrace, no nothing, and I can't disclose the problematic documents.
>>
>> How do you expect someone to help you then?
>
> I was reporting the bug so it wouldn't go unnnoticed and others would
> have had a chance to add some more data before I got the time to do it
> myself (tomorrow being a bank holiday).
Closing the bug report as no new info was added to this report...
--
Lior Kaplan
[EMAIL PROTECTED]
GPG fingerprint:
C644 D0B3 92F4 8FE4 4662 B541 1558 9445 99E8 1DA0
--- End Message ---
