[ Your mail never appeared to me wither in my mailbox nor in the
mailing list archives. Probably eaten by a spamfilter ]
Hi,
sorry for the late answer.
Am Sat, Jun 25, 2022 at 04:50:40PM -0700 schrieb Mark A. Hershberger:
> Found this bug because this is the only hit I found on search engines for the error I was seeing. I have a Debian system.
Obviously, since you wouldn't report here ;-)
> The problem is apparently because /usr/lib/libreoffice/share/extensions is (in my case) a 0-byte file and installing an extension resolves the issue.
Wow the f*? ...
... sigh. I think I see what goes wrong here. How did it appear not in
earlier times (the problematic code is in there since 3.x!).
libreoffice-common has a trigger which is supposed to run
make_lo_sync_extensions to do what it says when a extension is
installed/removed by touching the dir:
$ cat libreoffice-common.postinst
#!/bin/sh
set -e
[...]
validate_extensions() {
INSTDIR=`mktemp -d`
if HOME=$INSTDIR /usr/lib/libreoffice/program/unopkg list --bundled >/dev/null 2>/dev/null; then
HOME=$INSTDIR /usr/lib/libreoffice/program/unopkg validate -v --bundled
fi
}
make_lo_sync_extensions() {
touch /usr/lib/libreoffice/share/extensions
}
if [ "$1" = "triggered" ]; then
for triggername in $2; do
case "$triggername" in
# new "bundled" extensions (since 3.3)
"/usr/lib/libreoffice/share/extensions")
make_lo_sync_extensions
;;
[...]
esac
done
fi
[...]
$
So I guess dpkg removes /usr/lib/libreoffice/share/extensions i(it is
still "owned" by libreoffice-common though. Should it happen?) and
nevertheless libreoffice-common is triggered the touch is fired and you
end up with that 0 byte file :/
Regards,
Rene