Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | errors in description.xml kill extension manager dialog | ||
---|---|---|---|
Product: | General | Reporter: | joachim.lingner |
Component: | code | Assignee: | thorsten.martens |
Status: | CLOSED FIXED | QA Contact: | issues@framework <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | dirk.voelzke, hj, issues, juergen.fenn, kai.sommerfeld, mdxonefour, mux2005, nesshof, stefan.baltzer, uwe.luebbers, vitriol_vitriol |
Version: | DEV300m45 | Keywords: | data_loss |
Target Milestone: | OOo 3.3 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- | ||
Issue Depends on: | |||
Issue Blocks: | 111112 |
Description
joachim.lingner
2009-04-01 13:26:19 UTC
. Current situation: In OOo 3.1 (currently build OOO310_m9 is announced as RC1) the Writer2LateX extension 0.5 is pre-bundled. Thus clicking "Check for updates" in the Extension manager wil lead by default to an installation of the Writer2LateX extension v 1.0 Beta. There will be no warning, no "are you sure". The W2L page of the Extension Repository will not be shown, so the little warning there "The extension cannot be installed in OOo 3.1 – the Extension Manager crashes permanently" can not be read. After the extension update, the office will crash on EVERY start. And restart automatically into the next crash. This makes this issue Prio P2. I see three solutions so far: (1) Remove pre-bundled W2L extension from Office. This will save "Check for update" users their office. (2) Remove the 1.0 Beta Version from the Ext. Repository until it is replaced with a "3.1 compatible one" (3) Fix this issue before 3.1 Release. Given the state of the release (RC is out), I regard (1) and (2) as feasible. Solution (3) looks risky to me. the writer2latex extension source code is now hosted on source forge and by a look in the source header these are exclusive copyright by Henrik Just. According to our guidelines for bundling extensions we cannot bundle extensions which are not covered by the guidelines to contribute (meaning SCA). So unless these sources will not contributed to OOo (which would be my preferred solution) we need to unbundle this extension. As a side effect this issue will be resolved. anyhow, the initial description was that there is a problem with the description.xml I would be glad if we can Henrik a hint how can this be fixed as his side and if this also is a stopper problem for 3.1 release. @is: please remove from install set. Please do not hijack this issue. It is intended to fix the issue in the extension manager. Please write a new issue regarding the unbundling of the writer2latex extension. BTW, KSO notified the publisher of the problem and he said that he will fix it soon. Obviously there is a difference in DEV300m45 and OOO310m10. In the first the extension manager does not start while in the latter the office "allegedly" crashes. I'll have a look. Until then I will set this issue back to its previous owner (me) and target. . I fully agree with JL. Set this one to target OOo 3.2 again. Follow-up issue is 100836 "Remove writer2latex extension from ooo3.1 installation set" assigned to IS with target 3.1. I created task i100836 to remove the writer2latex extension from ooo3.1 installation sets. if you unbundle it (and IMHO this also should be the fix for Issue 100836) you should remove it completely from the tree. It was since ever a external "extension" (before 0.5 a .uno.pkg/.zip, since 0.5 a oxt) and people who want it can get it from there. Having it in OOos code only make sense if it is bundled, otherwise people can just download it from sf itself. (why is hendrik just CCed here at all?) I have temporarily removed Writer2LaTeX 1.0 beta from extensions.openoffice.org to avoid problems for OOo 3.1 users. I have fixed the typo in description.xml and will release a new beta version when I have tested it against OOo 3.1 rc. I don't have any particular opinion about bundling Writer2LaTeX with OOo or not. I am strongly in favour of bundling w2l with OOo. It has been bundled since OOo 2, and the LaTeX community as well as some publishers rely on OOo coming with LaTeX export filter. So could you please include w2l 0.5 in OOo 3.1. Please cf. also my comments on issue #100836. *** Issue 103541 has been marked as a duplicate of this issue. *** Target 3.3 Retargeting to 3.x. jl: Just encpontered this very nasty problem with dev300 m83 and an extension I just was playing around with. We really should try to fix this for 3.4. Fixed in cws jl155 Please verify and send back to re-verify for cws jl155. md: according to dv this fix has become part of CWS tl88 Checked and verified in cws tl88. Problem with the extension-manager and/or defect extensions seems to be fixed and looks good. However, using the Linux build of this cws and trying to travel to "tausch" within the extension-manager for adding a new extension, leads to a crash. Crash seems to be related to my testmashine only In Win OK too ! fixed in tl88 which was integrated in OOo 3.3 |