To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=76601





------- Additional comments from [EMAIL PROTECTED] Wed Apr 25 13:04:29 +0000 
2007 -------
Attached is the log for the crash report with ID r5sf9c.

Interestingly, this crashs deep in the Writer core, when saving the final 
document.

I know that a first build of OOF680m15 had an incompatibility which slipped
release engineering's attention, and which lead to a lot of applications
crashing upon saving and/or loading documents. Internally in Hamburg, there has
been a new "hot fix build" of m15, but it might be that the first, corrupted
build escaped into the wild, and that the version you're using is exactly this
broken version.

What speaks *against* this theory is that the build ID is 9140 in my case, too -
and it should be different from yours if we really had different builds.
However, who knows whether RE perhaps forgot to increase the build ID?

What I would suggest for the moment is to wait for m16, and see if the problem
persists.

Alternatively, if anybody who actually encounters the problem has the chance to
verify the following MD5 checksums:

  sw680mi.dll: F5EC193AC830C140200F1C11629035D9
  swd680mi.dll: AAE429795103CC528C8E864C52B400F2
  swui680mi.dll: B4EC991B916C911133C991E439FD15E4

, then this might give us a hint whether the versions we use are really the 
same.

Thanks.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to