I can confirm it in the openoffice.org-emailmerge package. When
(re)configuring that package from a sudo login, it will fail; when running as
"proper" root however, it works fine.
My home directory is mounted from NFS with the export having the root_squash
option set, so root can't actually write to that directory.
Regards,
Nicos Gollan
===== package information
openoffice.org-emailmerge:
Installed: 1:3.1.1-2
Candidate: 1:3.1.1-2
Version table:
*** 1:3.1.1-2 0
700 http://ftp.de.debian.org unstable/main Packages
100 /var/lib/dpkg/status
===== console output
(with sudo) # dpkg-reconfigure openoffice.org-emailmerge
Adding extension /usr/lib/openoffice/basis3.1/program/mailmerge.py...creation
of executable memory area failed: Permission denied
creation of executable memory area failed: Permission denied
creation of executable memory area failed: Permission denied
creation of executable memory area failed: Permission denied
creation of executable memory area failed: Permission denied
creation of executable memory area failed: Permission denied
creation of executable memory area failed: Permission denied
Extension has already been added: org.openoffice.legacy.mailmerge.py
done.
(with sudo) # su -c "dpkg-reconfigure openoffice.org-emailmerge"
Adding extension /usr/lib/openoffice/basis3.1/program/mailmerge.py...Extension
has already been added: org.openoffice.legacy.mailmerge.py
done.
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Output from apt-get dist-upgrade:
Preparing to replace openoffice.org-filter-binfilter 1:3.1.1-1 (using
.../openoffice.org-filter-binfilter_1%3a3.1.1-2_i386.deb) ...
[Java framework] Error in function createSettingsDocument (elements.cxx).
javaldx failed!
creation of executable memory area failed: Permission denied
creation of executable memory area failed: Permission denied
creation of executable memory area failed: Permission denied
creation of executable memory area failed: Permission denied
file:///usr/lib/openoffice/basis3.1/program/libbf_migratefilterli.so
revoke component
'file:///usr/lib/openoffice/basis3.1/program/libbf_migratefilterli.so' from
registry '/var/lib/openoffice/basis3.1/program/services.rdb' succesful!
[...]
Preparing to replace openoffice.org-evolution 1:3.1.1-1 (using
.../openoffice.org-evolution_1%3a3.1.1-2_i386.deb) ...
[Java framework] Error in function createSettingsDocument (elements.cxx).
javaldx failed!
creation of executable memory area failed: Permission denied
creation of executable memory area failed: Permission denied
creation of executable memory area failed: Permission denied
creation of executable memory area failed: Permission denied
file:///usr/lib/openoffice/basis3.1/program/libevoabli.so
revoke component 'file:///usr/lib/openoffice/basis3.1/program/libevoabli.so'
from registry '/var/lib/openoffice/basis3.1/program/services.rdb' succesful!
[...]
Setting up openoffice.org-filter-binfilter (1:3.1.1-2) ...
[Java framework] Error in function createSettingsDocument (elements.cxx).
javaldx failed!
creation of executable memory area failed: Permission denied
creation of executable memory area failed: Permission denied
creation of executable memory area failed: Permission denied
creation of executable memory area failed: Permission denied
file:///usr/lib/openoffice/basis3.1/program/libbf_migratefilterli.so
register component
'file:///usr/lib/openoffice/basis3.1/program/libbf_migratefilterli.so' in
registry '/var/lib/openoffice/basis3.1/program/services.rdb' succesful!
[...]
Setting up openoffice.org-evolution (1:3.1.1-2) ...
[Java framework] Error in function createSettingsDocument (elements.cxx).
javaldx failed!
creation of executable memory area failed: Permission denied
creation of executable memory area failed: Permission denied
creation of executable memory area failed: Permission denied
creation of executable memory area failed: Permission denied
file:///usr/lib/openoffice/basis3.1/program/libevoabli.so
register component 'file:///usr/lib/openoffice/basis3.1/program/libevoabli.so'
in registry '/var/lib/openoffice/basis3.1/program/services.rdb' succesful!
On Fri, Sep 18, 2009 at 10:21:10AM +0200, Nicos Gollan wrote:
> The same issue occurs with
> - openoffice.org-filter-binfilter (1:3.1.1-2)
> - openoffice.org-evolution (1:3.1.1-2)
> when upgrading packages.
So on all packages using regcomp for registering their components and
for packages using unopkg for registering extensions)
[...]
Thanks, but you do think it's not enough logs by now?
> creation of executable memory area failed: Permission denied
> creation of executable memory area failed: Permission denied
> file:///usr/lib/openoffice/basis3.1/program/libbf_migratefilterli.so
> register component
> 'file:///usr/lib/openoffice/basis3.1/program/libbf_migratefilterli.so' in
> registry '/var/lib/openoffice/basis3.1/program/services.rdb' succesful!
Was this successful really?
Anyway, /me thinks this bug at most is minor and that OOo does not do anything
serious with $HOME except of course trying to access its config (arguably
it shouldn't do on system-wide installs, but then again your $HOME is
bogusly set to your users' home)
If you want this fixed, please file an issue upstream, I don't
want to fight with upstream for this...
Grüße/Regards,
Rene
--
.''`. René Engelhard -- Debian GNU/Linux Developer
: :' : http://www.debian.org | http://people.debian.org/~rene/
`. `' re...@debian.org | GnuPG-Key ID: D03E3E70
`- Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70
What I forgot to mention here:
Well, unopkg might do when it does Java stuff, though. That's why we
nedd to do
/usr/lib/openoffice/program/unopkg add --shared $1 \
"-env:UserInstallation=file:///$INSTDIR" \
"-env:UNO_JAVA_JFW_INSTALL_DATA=file:///var/lib/openoffice/$basis/share/config/javasettingsunopkginstall.xml" \
for calling unopkg in the maintainer scripts since it otherwise can happen
that either javasettingsunopkginstall.xml gets root:root (or even worse,
when there's no profile in $HOME yet it creates the profile dir root:root
and then alsojavasettingsunopkginstall.xml).
> If you want this fixed, please file an issue upstream, I don't
> want to fight with upstream for this...
On the above case, we already discussed that with upstream, and the above
solution was what we ended up needing to do...
> Anyway, /me thinks this bug at most is minor and that OOo does not do anything
> serious with $HOME except of course trying to access its config (arguably
> it shouldn't do on system-wide installs,
I agree that the bug is minor (not sure why I set it to normal when I
reported it). The installation creates (tries to at least) a new
.execoooRANDOM directory in HOME that it removes afterwards.
> but then again your $HOME is bogusly set to your users' home)
I don't think any debian policy says it is bogus (but I agree this
provides an easy workaround, which maks the bug minor).
> If you want this fixed, please file an issue upstream, I don't
> want to fight with upstream for this...
The code is in:
patches/dev300/ooo80816.selinux.bridges.diff
which uses HOME if it exists and /tmp otherwise.
It seems to be from Fedora, not directly upstream. I may try to see with
them if they are willing to change it there, although it is more
complicated than setting HOME to a safe value in the script.
Thank you for your work on openoffice for debian,
--
Marc Glisse