Issue 98302

Summary:

Disabling the OOo Feedback Extension causesOOo to stop responding

Product:

General

Reporter:

christian.jansen

Component:

Assignee:

joerg.skottke

Status:

CLOSED FIXED

QA Contact:

issues@framework <issues>

Severity:

Trivial

Priority:

CC:

bjoern.michaelsen, issues, joachim.lingner, kai.sommerfeld

Version:

OOo 3.0

Target Milestone:

OOo 3.1

Hardware:

All

OS:

Mac OS X, all

URL:

http://n2.nabble.com/file/n2187774/xcu%2Bdoes%2Bnot%2Bexist.png

Issue Type:

DEFECT

Latest Confirmation in:

---

Developer Difficulty:

---

Issue Depends on:

Issue Blocks:

90370

Attachments:

Description	Flags
errormessage	none

Description christian.jansen 2009-01-21 08:11:38 UTC

This bug occours with:
OOo_3.0.1rc2_20090112_MacOSXIntel_install_en-US

I was not able to find a OOo 3.0.1 RC2 field in "Found in Version:" thus I've
selected OOo 3.0. Now back to the bug:

Problem:

In 3.0.1rc2_20090112 an attempt to disable the extension causes the
program to stop responding, requiring a force quit. Here's the dialogue that
accompanies the problem:

http://n2.nabble.com/file/n2187774/xcu%2Bdoes%2Bnot%2Bexist.png 

Similarly, an attempt to remove the extension causes a problem.

So, am I fairly stuck with it, or is there a simple approach to dealing with
extensions that can not be removed?

I removed the contents of 
~/Library/Application Support/OpenOffice.org/3/user/uno_packages/cache/ 
and now all that remains are the three spelling-related extensions. I had a
number of others installed, but they're all gone. 

OOo use of a cache seems to differ from my definition of a cache. I never
imagined that clearing a cache could lead to apparent removal of
features/extensions.


Expected result:
- Allow to disable Extensions, even if they don't work correctly.
- Add a Safe Mode to OOo which disable all extensions

Comment 1 christian.jansen 2009-01-21 08:13:20 UTC

cc'ing BjÃ¶rn

Comment 2 Olaf Felka 2009-01-21 09:01:19 UTC

reassigned

Comment 3 bjoern.michaelsen 2009-01-21 10:45:04 UTC

*** Issue 96352 has been marked as a duplicate of this issue. ***

Comment 4 bjoern.michaelsen 2009-01-21 10:57:15 UTC

cc'ing jl (as in Issue 96352)

I think I might have found the reason for this issue:
The extension contains a xcs-File at
registry/schema/org/openoffice/Office/OOoImprovement.xcs in which Registry-Keys
are described for org.openoffice.Office.OOoImprovement/Settings. Trying to
introduce such a xcs in OOo fails because of the failed validation.

I still have to verify if this is really the issue. If so, I would propose that
the Extension Manager would have to validate xcs-Files and reject to install
faulty extensions.

@cj: "Add a Safe Mode to OOo which disable all extensions" Thats a different
beast, please file a seperate bug.

Comment 5 bjoern.michaelsen 2009-01-21 11:19:20 UTC

Created attachment 59562 [details]
errormessage

Comment 6 bjoern.michaelsen 2009-01-21 11:25:13 UTC

I just took a look at the errormessage (and made it an attachment, external link
easily break). It is complaining about a file in "ice-toolbar.oxt', not in
'OOoImprovement.oxt'.

@jl: Is the extension manager mixing up extensions here? Even if the Usage
Tracking Extension is the root cause of this issue, the extension manager should
isolate the issue there, shouldnt it?

Comment 7 joachim.lingner 2009-01-23 12:39:03 UTC

Comment 8 joachim.lingner 2009-01-23 12:39:49 UTC

Comment 9 joachim.lingner 2009-01-23 12:46:30 UTC

Reproduction:
-install OOoImprovement.oxt on Mac.
-restart OOo
-remove extension in ExtensionManager

This issue is actually a crash but the crash reporter does not work properly.
The culprit is the service manager which uses an invalid hash set iterator, when
removing the factories of the services of the OOoImprovement extension.
Therefore this crash can potentially happen on all platforms.

Comment 10 joachim.lingner 2009-01-23 13:15:47 UTC

Comment 11 joachim.lingner 2009-01-23 16:05:13 UTC

@jsk: please verify

Comment 12 joerg.skottke 2009-01-29 10:40:19 UTC

Disabling works, though Tools/Options is not updated on the fly.
I can re-enable the extension without problem. All actions require a restart of
the application.

I cannot deinstall the extension - exception is "Package Instance has already
been disposed".
However, this is now irrelevant as the extension is integrated into the product
(meaning: No longer an extension).

Verified.

Comment 13 bjoern.michaelsen 2009-01-29 10:53:23 UTC

'I cannot deinstall the extension - exception is "Package Instance has already
been disposed".'
FYI, thats another bug - the manifest of the extension was buggy.

Comment 14 joerg.skottke 2009-03-09 09:32:04 UTC

Good in OOO310m4