Bug#616011: no mediawiki exporter
found 616011 1.1.1+LibO3.4.5-2
tags 616011 + patch
thanks
On current wheezy, I get the same problem: the exporter is not listed, and attempting
to use the "send to" feature yields the same result as OP.
How are exporters supposed to be registered ? Can we manually request a re-registration
of that exporter, possibly with verbose traces ?
Since the last time this worked on this machine (that was last september, and I did not attempt
to use it since then), the following upgrades were done according to aptitude logs:
[UPGRADE] libreoffice 1:3.3.3-4+b1 -> 1:3.4.3-1
[UPGRADE] libreoffice-wiki-publisher 1.1.1+LibO3.3.3-4 -> 1.1.1+LibO3.4.3-1
[UPGRADE] libreoffice 1:3.4.3-1 -> 1:3.4.3-3
[UPGRADE] libreoffice-wiki-publisher 1.1.1+LibO3.4.3-1 -> 1.1.1+LibO3.4.3-3
I get the problem with sun jre 1.6.0_26 and (openjdk from testing but listed as sun) _24, the
previous success was probably with another version,
since no jre was selected any more (this mechanism *does* suck, btw). Switching to "FSF 1.5.0"
(for which there are two identical lines in the dialog...) results in the "send to mediawiki"
turning to non-selectable after restart.
Since it used to work for me with 3.3.3 and problems have been reported with previous
versions, I don't believe that downgrading would be of any help.
René wrote:
>Please don't tell me you did intrusive changes like a complete LibO package
>upgrade while LibO was running? (Extension registration should be ok if
>done via unopkg, but I don't think it will work with the new "preregistered"
>way)
Err... are you saying that no LibO or OOo program should be running during the upgrade
or there is any risk of getting broken in ways noone imagines ? That would sound pretty
broken, and a bold warning should be displayed from preinst, should that be the case.
That said, I regularly launch upgrades while I'm continuing to work, and it surely occured
that LibO got upgrade while it was running. Now what can be done to recover if that was
the source of the breakage ?
Looking at the various installed filters .xcu files, it looks like this one is the only one
using <<oor:op="fuse">>, other (writer2latex, pdfimport) rather use <<oor:op="replace">>.
Now I tried to replace "fuse" with "replace" for a test, and reregistering the thing:
mv /usr/lib/libreoffice/share/extensions/wiki-publisher /
/var/lib/dpkg/info/libreoffice-common.postinst triggered /usr/lib/libreoffice/share/extensions
mv /wiki-publisher/ /usr/lib/libreoffice/share/extensions/
$EDITOR /usr/lib/libreoffice/share/extensions/wiki-publisher/Filter.xcu
/var/lib/dpkg/info/libreoffice-common.postinst triggered /usr/lib/libreoffice/share/extensions
... and guess what ? it just worked :)
Now the export filter is selectable in the export dialog, and "send to" finds it as well...
So one question remains, what was this "fuse" supposed to do ?
--
Yann Dirson - Bertin Technologies
Reply to: