To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=95496
User mux2005 changed the following:
What |Old value |New value
================================================================================
Assigned to|mux2005 |sb
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Fri Dec 5 11:38:26 +0000
2008 -------
I have now thoroughly examined this issue. The following summarizes my findings
1. The issue affects all builds with --enable-kde. It DOES affect builds
downloaded from http://www.openoffice.org. I have only tested in a KDE
environment, but I guess the issue will NOT occur in a non-KDE environment. Keep
that in mind when reproducing the bug.
2. You can only see the issue if you have changed the icon set from "Automatic"
to something else. That's the reason for my contraditory info on which versions
are affected. In some tests I had a shared extension installed that
preconfigures some OOo settings, including the icon set.
3. This issue is a duplicate of issue 65999. Apparently we made a mistake during
our test to see if the issue was resolved and erroneously closed it. As a
consequence we switched from patching our build to replace all icon sets with
the classic icons to using the extension mentioned in 2. As that extension made
it into our deb install sets we started seeing the issue again but didn't make
the connection until now.
So to repeat: This is not a new issue. This issue has been around since OOo
2.0.2 at least. It seems to have gotten a little milder in more recent versions,
as issue 65999 says that OOo freezes for good, whereas now it can be revived by
calling "soffice".
Anyway, this renewed examination of the issue has had some good at least, since
now we know that it is somehow KDE specific (see 1). Maybe that helps getting it
fixed.
Since this new issue contains all the current information and a ready-to-run JAR
file for reproducing (the old issue had only source which confused the QA person
involved), I suggest keeping this one open rather than reopening the old one and
closing this one as dup. But adjusting the version down to 2.0.2 may be useful.
4. One interesting aspect that I think I haven't mentioned before is the
following: If you call loadComponentFromUrl() and you hit the bug so that
loadComponentFromUrl() hangs and then you wake up OOo by calling swriter, you
end up with 2 unnamed documents. If you close the one created by
loadComponentFromUrl(), the whole OOo will terminate, closing ALL open documents
without user interaction, even if they have unsaved changes! So this issue can
cause data loss.
---------------------------------------------------------------------
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]
