Hi Rony,
On 11.02.2014 14:47, Rony G. Flatscher (Apache) wrote:
On 11.02.2014 10:45, Oliver-Rainer Wittmann wrote:
On 11.02.2014 09:55, Herbert Duerr wrote:
[...]
There are hints from other users that the crash after a while may have
to do with the update service having problems. Does the problem persist
when you disable the automatic update check?
(OpenOffice->Preferences->OpenOffice->OnlineUpdate->CheckAutomatically)
Actually, it does not show anymore! :(
Even removed all installed components (AOO, ScriptProvider.oxt), reinstalled
AOO alone, then with
the ScriptProvider.oxt to no avail.
Thats good news and bad news :-)
However, I still have yesterdays DiagnosticReports which I can make available
(at least I can see
three different crashes, soffice with a SIGSEGV (linked to the Java awt event
thread problem),
soffice with a SIGABRT, and a unopkg with a SIGABRT. Altogether I have eleven
crash files created
with the 64-bit version that you have made kindly available yesterday.
Please advise, whether you want all crash files from yesterday and where to put
them (issue, make it
downloadable, send it as an attachment?)!
If you have webspace somewhere then making them available there would be
a good start, especially since these seem to be different problems.
Or:
- Does the crash occur when you check manually (Menu Help - Check for
Updates...) for a new AOO
version?
No crash.
- Does the crash occur when you check manually (Menu Tools - Extension Manager
- Check for Updates?
No crash, but a popup-error dialog with the title "OpenOffice 4.1.0" and the message
"Error reading
data from the Internet. Server error message.".
After pressing the o.k. button, this is followed by another error popup "OpenOffice
4.1.0" with the
message "http://www.rexxla.org/updates/ScriptProviderForooRexx.update.xml does not
exist.", pressing
o.k. yields one error popup after another for each URL that does not exist, e.g.
"http://sourceforge.net/projects/bsf4oorexx/files/ScriptProviderForooRexx.update.html";.
Removing the ScriptProvider extension (not all of its URLs are valid
currently), rerunning the
Extension Manager - Check for Updates yields no updates and does not yield a
crash.
This check for an extension update with bad URLs is the prime suspect
for the crash-after-two-minutes. If you are using time machine then
checking the difference between the current and the older versions of
the ScriptProviderForooRexx extension might be interesting.
Herbert
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
